You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Martin Cooper <ma...@apache.org> on 2006/04/18 19:42:14 UTC
Re: JMimeMagic (was [fileUpload] file content-type)
On 4/18/06, Mark <el...@gmail.com> wrote:
>
> I would love to do a fork-release and create a commons project. I
> wonder if the jmimemagic author would be offended though...
That's not possible. Since JMimeMagic is LGPL, any modifications must
result in a library that is also LGPL. As part of the ASF, all Commons
components must have the Apache License.
I do think something along the same lines as JMimeMagic would make a good
Commons component (unless we already have one lurking somewhere that I'm not
aware of). If someone happens to know either of the authors and would like
to open a dialogue with them about either changing the license or possibly
coming to the ASF, I think that would be worthwhile.
--
Martin Cooper
On 4/18/06, Sven Schliesing <sv...@schliesing.de> wrote:
> > I'm not a master in licence-things, but couldn't you just do a
> > fork-release? Maybe other's would appreciate your work, too.
> >
> > Mark wrote:
> > > I never heard back from the author. He has a posting on the
> > > jmimemagic page at sourceforge that says he is looking for feedback,
> > > but has not responded back to any of the feedback posts.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
Re: JMimeMagic (was [fileUpload] file content-type)
Posted by Mark <el...@gmail.com>.
I would really like to start a commons project. It is something that
I have wanted to do for some time. I will try and contact the author..
On 4/18/06, Sven Schliesing <sv...@schliesing.de> wrote:
> But one could simply release the fixed version of jmimemagic "outside"
> of commons. So there would be no problem, would it?
> At least until the original author gives it's ok to "commonize" it.
>
> Sven
>
> > That's not possible. Since JMimeMagic is LGPL, any modifications must
> > result in a library that is also LGPL. As part of the ASF, all Commons
> > components must have the Apache License.
> >
> > I do think something along the same lines as JMimeMagic would make a good
> > Commons component (unless we already have one lurking somewhere that I'm not
> > aware of). If someone happens to know either of the authors and would like
> > to open a dialogue with them about either changing the license or possibly
> > coming to the ASF, I think that would be worthwhile.
> >
> > --
> > Martin Cooper
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: JMimeMagic (was [fileUpload] file content-type)
Posted by Henri Yandell <fl...@gmail.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 <br...@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 != 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
Re: JMimeMagic (was [fileUpload] file content-type)
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----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 != 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?
>
>
> On 4/18/06, Brian K. Wallace <br...@transmorphix.com> wrote:
> Hopefully they'll respond - that would definitely be the best route if
> possible.
>
> During SF's recent CVS outage, I was informed (by another project's
> developer who has worked with both) that their SVN setup was much easier
> to deal with.
>
> Brian
>
> Henri Yandell wrote:
>>>> Definitely - you can always redistribute LGPL/GPL with or without your
>>>> changes, provided you adhere by the licence (which basically means
>>>> provide the source).
>>>>
>>>> Always best to try and work with the original project of course -
>>>> provided the original author is still reading email and they didn't
>>>> host the project on a personal site (making it hard for you to do the
>>>> same).
>>>>
>>>> That's one advantage of tigris/savannah/apache/sourceforge. Others can
>>>> pick it up - shame Sourceforge is so damn slow :) Anyone tried out
>>>> their SVN yet?
>>>>
>>>> Hen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFERTt/aCoPKRow/gARAglXAKDhTCQGXYZBkY3vVmA0ITqxFNWsZwCcCFvZ
7I6QAVcDGXKyfe2W3qbU/CA=
=Qyna
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: JMimeMagic (was [fileUpload] file content-type)
Posted by Mark <el...@gmail.com>.
I have contacted the maintainer of jmimemagic. How long should I wait
before forking and trying to get acceptance into jakarta-commons?
On 4/18/06, Brian K. Wallace <br...@transmorphix.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hopefully they'll respond - that would definitely be the best route if
> possible.
>
> During SF's recent CVS outage, I was informed (by another project's
> developer who has worked with both) that their SVN setup was much easier
> to deal with.
>
> Brian
>
> Henri Yandell wrote:
> > Definitely - you can always redistribute LGPL/GPL with or without your
> > changes, provided you adhere by the licence (which basically means
> > provide the source).
> >
> > Always best to try and work with the original project of course -
> > provided the original author is still reading email and they didn't
> > host the project on a personal site (making it hard for you to do the
> > same).
> >
> > That's one advantage of tigris/savannah/apache/sourceforge. Others can
> > pick it up - shame Sourceforge is so damn slow :) Anyone tried out
> > their SVN yet?
> >
> > Hen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
>
> iD8DBQFERTjWaCoPKRow/gARAkrZAJ4o0eBfc9YIP5LrwwzTN7ukodEi3wCfTIJA
> cyGJG1m0C5ZjUGFmGnpA+SU=
> =i32A
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: JMimeMagic (was [fileUpload] file content-type)
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hopefully they'll respond - that would definitely be the best route if
possible.
During SF's recent CVS outage, I was informed (by another project's
developer who has worked with both) that their SVN setup was much easier
to deal with.
Brian
Henri Yandell wrote:
> Definitely - you can always redistribute LGPL/GPL with or without your
> changes, provided you adhere by the licence (which basically means
> provide the source).
>
> Always best to try and work with the original project of course -
> provided the original author is still reading email and they didn't
> host the project on a personal site (making it hard for you to do the
> same).
>
> That's one advantage of tigris/savannah/apache/sourceforge. Others can
> pick it up - shame Sourceforge is so damn slow :) Anyone tried out
> their SVN yet?
>
> Hen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFERTjWaCoPKRow/gARAkrZAJ4o0eBfc9YIP5LrwwzTN7ukodEi3wCfTIJA
cyGJG1m0C5ZjUGFmGnpA+SU=
=i32A
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: JMimeMagic (was [fileUpload] file content-type)
Posted by Henri Yandell <fl...@gmail.com>.
Definitely - you can always redistribute LGPL/GPL with or without your
changes, provided you adhere by the licence (which basically means
provide the source).
Always best to try and work with the original project of course -
provided the original author is still reading email and they didn't
host the project on a personal site (making it hard for you to do the
same).
That's one advantage of tigris/savannah/apache/sourceforge. Others can
pick it up - shame Sourceforge is so damn slow :) Anyone tried out
their SVN yet?
Hen
On 4/18/06, Sven Schliesing <sv...@schliesing.de> wrote:
> But one could simply release the fixed version of jmimemagic "outside"
> of commons. So there would be no problem, would it?
> At least until the original author gives it's ok to "commonize" it.
>
> Sven
>
> > That's not possible. Since JMimeMagic is LGPL, any modifications must
> > result in a library that is also LGPL. As part of the ASF, all Commons
> > components must have the Apache License.
> >
> > I do think something along the same lines as JMimeMagic would make a good
> > Commons component (unless we already have one lurking somewhere that I'm not
> > aware of). If someone happens to know either of the authors and would like
> > to open a dialogue with them about either changing the license or possibly
> > coming to the ASF, I think that would be worthwhile.
> >
> > --
> > Martin Cooper
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: JMimeMagic (was [fileUpload] file content-type)
Posted by Sven Schliesing <sv...@schliesing.de>.
But one could simply release the fixed version of jmimemagic "outside"
of commons. So there would be no problem, would it?
At least until the original author gives it's ok to "commonize" it.
Sven
> That's not possible. Since JMimeMagic is LGPL, any modifications must
> result in a library that is also LGPL. As part of the ASF, all Commons
> components must have the Apache License.
>
> I do think something along the same lines as JMimeMagic would make a good
> Commons component (unless we already have one lurking somewhere that I'm not
> aware of). If someone happens to know either of the authors and would like
> to open a dialogue with them about either changing the license or possibly
> coming to the ASF, I think that would be worthwhile.
>
> --
> Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org