Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of flamefew@gmail.com designates
 64.233.166.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Z7q/kn46szb79PSPOfTJVfSME32v8c4gA+IUqT2iVwya6bcVOkT+g4N6ABRjYaeQigXN9AxZQ/255T2gXyFJW2DixWZjh8vX5MVGSRALHolqdyF/JWrRcTHoxQDXPceLv+k3UBUs8vSPAnFwfNmy6xJ6kf8ed5BP0joAA60UGq0=
Message-ID: <31cc37360604181437k2cddb35dlc6e57a8a56750fc7@mail.gmail.com>
Date: Tue, 18 Apr 2006 14:37:13 -0700
From: "Henri Yandell" <flamefew@gmail.com>
To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Subject: Re: JMimeMagic (was [fileUpload] file content-type)
In-Reply-To: <44453B7F.4060403@transmorphix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <16d6c6200604181042i61cb3b92pa01a5344ff184acb@mail.gmail.com>
	 <44452785.30405@schliesing.de>
	 <31cc37360604181159o74ac162dj7bfbbb9b3bad39f2@mail.gmail.com>
	 <444538D6.6040001@transmorphix.com>
	 <9f066ee90604181211m1259d221wa3878ccbba398c0c@mail.gmail.com>
	 <44453B7F.4060403@transmorphix.com>

Right. There are legal bits and policy bits entwined here.

The ASF doesn't distribute software under licences other than the ASL.
It's not a solid policy - but I doubt we'll ever stretch it to involve
us shipping under strong copyleft licences. As with any group of 1000+
people, we don't agree on much, but we do largely seem to prefer the
gift style of BSD licence (makes sense, wouldn't be here otherwise).

We can't legally change the licence on the code - so wouldn't be able
to take a fork into Commons (for example). The original author(s)
would need to relicence (to BSD/MIT/ASL equivalents), or we would need
to start afresh.

Cliff Schmidt has outlined a solid policy for us
(http://people.apache.org/~cliffs/3party.html). It's still getting
agreed upon (and argued upon), but now that I think about it, that
actually would allow us to depend on JMimeMagic. We wouldn't be able
to ship it with our fileupload binary etc, but we don't ship
dependencies with our binaries anyway.

Hen

On 4/18/06, Brian K. Wallace <brian@transmorphix.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Just be conscious of the fact that, with all open source projects, time
> is usually volunteer/as available/as the urge strikes. I wouldn't start
> to get anxious for a couple of weeks. (some take longer, but I'm anxious
> by then)
>
> As for forking -> commons, remember licensing issues. GPL/LGPL !=3D ASL.
> In order for ASL to come into the picture you'd have to not fork but
> start from scratch. IANAL, but that's how it's been presented before.
>
> Brian
>
> Mark wrote:
> > I have contacted the maintainer of jmimemagic.  How long should I wait
> > before forking and trying to get acceptance into jakarta-commons?

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org