Trustin Lee schrieb:
On 6/13/07, Richard Wallace <[EMAIL PROTECTED]> wrote:
So let's try and enumerate our options and figure out which ones we like
the most and want to pursue first.

First, there's there "where" of hosting:
1) Apache Labs
2) Apache Incubating
3) MINA subproject

It sounds like the consensus so far is to host it as a MINA subproject.
Should we take a vote on that?

MINA PMC is discussing on this issue right now.  I'll announce the
result in 3 days.

Next, is how we'll get the project started.
1) Start from scratch
2) Copy protocol-dns and build from there, using dnsjava and dnsjnio for
reference.
3) Pursue importing, relicensing under ASL 2.0, and refactoring dnsjava
(http://www.dnsjava.org/index.html), with permission from Brian
Wellington, the author.
4) Import dnsjava under the BSD license, changing the name and package
and making a reference to the original dnsjava in the LICENSE file
(assuming this is the way it works according to the BSD license).
5) Pursue importing, relicensing under ASL 2.0, and building from
dnsjnio (http://sourceforge.net/projects/dnsjnio/), with permission from
the author, Alex.

I like #3 if Brian is willing to contribute the code.  It is mature and
well used by other projects.  It has a good, solid suite of unit tests
that will help in porting it to use MINA.  I don't like the idea of
trying to use dnsjava without Brian's approval even if it is within the
bounds of the BSD license.  So if we can't get approval from him, my
next choice would be #2.  I haven't had a chance to look much at
dnsjnio, so I'm not sure about #5, although Stefano seems to think that
he'd be more willing to relicense his code.

I'm sure there are some alternatives I'm missing.  But I hope this is a
good start at summarizing the options we've come up with so far.

I prefer the option #3, too.  WDYT guys?

Trustin

I have spoken to Brian to in the past about bugs etc. and I whould agree with Stefano that I don't think he will contribute his code. But if you want give it a try.

bye
Norman

Reply via email to