commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell" <>
Subject Re: JMimeMagic (was [fileUpload] file content-type)
Date Tue, 18 Apr 2006 21:37:13 GMT
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
( 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.


On 4/18/06, Brian K. Wallace <> wrote:
> 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 != 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:
For additional commands, e-mail:

View raw message