You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by Niklas Rehfeld <ni...@gmail.com> on 2012/01/30 04:49:25 UTC
contributing code to POI
Hi all,
I have been working on a project that uses a lot of the POI libraries,
and have come up with some code that I think would be useful to
contribute back to the project. The main thing is an implementation of
the DConRef record structure.
Now, I haven't released the project that this is part of yet, and I
haven't decided on a license to release it under. I am a bit confused
by the stuff in the contributing guidelines and the Coding standards.
For instance does it matter what license I release my project under,
in terms of being able to contribute parts of the codebase to the POI
project? I read in one of the parts that none of the code contributed
is allowed to depend on gpl/lgpl licensed code. Does this mean I can't
release my project under GPL and contribute parts of it to POI at the
same time? Or am I completely misunderstanding something?
Also, what license/headers do I need to put at the top of a class when
I contribute it? In some places it talks about "the POI License" and
other places it talks about the ASL and releasing rights to the source
under that license.
Cheers
Nik
p.s. the link to the 'apache software license' in the checklist part
of in http://poi.apache.org/guidelines.html is broken, it points to
"licence-faq" rather than to "license-faq".
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: contributing code to POI
Posted by Dave Fisher <da...@comcast.net>.
All contributions to a project at The Apache Software Foundation are made under the Apache License 2.0. [1]
You are free to offer your own project under whatever license you wish, but you should offer your contribution to the project under the AL2. Here is a FAQ [2]
If your contribution is large then you should consider sending in an Individual Contributor License Agreement. [3]
If you wish, you retain copyright to your contributions.
Regards,
Dave
[1] http://www.apache.org/licenses/LICENSE-2.0.html
[2] http://www.apache.org/foundation/license-faq.html
[3] http://www.apache.org/licenses/icla.pdf
On Jan 29, 2012, at 7:49 PM, Niklas Rehfeld wrote:
> Hi all,
>
> I have been working on a project that uses a lot of the POI libraries,
> and have come up with some code that I think would be useful to
> contribute back to the project. The main thing is an implementation of
> the DConRef record structure.
>
> Now, I haven't released the project that this is part of yet, and I
> haven't decided on a license to release it under. I am a bit confused
> by the stuff in the contributing guidelines and the Coding standards.
>
> For instance does it matter what license I release my project under,
> in terms of being able to contribute parts of the codebase to the POI
> project? I read in one of the parts that none of the code contributed
> is allowed to depend on gpl/lgpl licensed code. Does this mean I can't
> release my project under GPL and contribute parts of it to POI at the
> same time? Or am I completely misunderstanding something?
>
> Also, what license/headers do I need to put at the top of a class when
> I contribute it? In some places it talks about "the POI License" and
> other places it talks about the ASL and releasing rights to the source
> under that license.
>
> Cheers
> Nik
>
> p.s. the link to the 'apache software license' in the checklist part
> of in http://poi.apache.org/guidelines.html is broken, it points to
> "licence-faq" rather than to "license-faq".
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: contributing code to POI
Posted by Dave Fisher <da...@comcast.net>.
On Jan 30, 2012, at 1:28 PM, Niklas Rehfeld wrote:
> Thanks for clearing that up! I always get a bit confused with copyright stuff.
>
>> You should use the same standard Apache License header that's used in the
>> POI source code. I can't spot anything about "the POI license" anywhere, can
>> you point me to it?
>
> In the coding guidelines, http://poi.apache.org/resolutions/res001.html it says
>
>> 1. All classes and interfaces MUST have, right at the beginning, the POI License (see poi/doc/LICENSE).
>
> then, just underneath in the amendments,
>
>> As opposed to the formerly used POI License which was based on the Apache Public License, now that POI is part of Jakarta, use the APL 1.1 for the header. Currently, the Apache
>> Software Foundation requires us to use the full long version.
>
> which seems out of date as well, if we're meant to be using AL2.
POI is over 10 years old at Apache and existed before. Hence POI license to APL 1.1 to AL2.
Thanks for pointing out that we need to edit the site.
Regards,
Dave
>
> Thanks again for the tips. I will try to send in some patches in the next week.
>
> Nik
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: contributing code to POI
Posted by Niklas Rehfeld <ni...@gmail.com>.
Thanks for clearing that up! I always get a bit confused with copyright stuff.
> You should use the same standard Apache License header that's used in the
> POI source code. I can't spot anything about "the POI license" anywhere, can
> you point me to it?
In the coding guidelines, http://poi.apache.org/resolutions/res001.html it says
> 1. All classes and interfaces MUST have, right at the beginning, the POI License (see poi/doc/LICENSE).
then, just underneath in the amendments,
> As opposed to the formerly used POI License which was based on the Apache Public License, now that POI is part of Jakarta, use the APL 1.1 for the header. Currently, the Apache
> Software Foundation requires us to use the full long version.
which seems out of date as well, if we're meant to be using AL2.
Thanks again for the tips. I will try to send in some patches in the next week.
Nik
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: contributing code to POI
Posted by Nick Burch <ni...@alfresco.com>.
On Mon, 30 Jan 2012, Niklas Rehfeld wrote:
> For instance does it matter what license I release my project under, in
> terms of being able to contribute parts of the codebase to the POI
> project?
Nope, you own the copyright on the code you write, so you're welcome to
license it multiple times under multiple licenses. The only requirement is
that you license it under the Apache license when you contribute it to POI
> I read in one of the parts that none of the code contributed is allowed
> to depend on gpl/lgpl licensed code.
Correct, you can't have external dependencies to GPL/LGPL code (and a few
others). That means if you want to contribute your code, it can't depend
on an external GPL project, but that doesn't preclude it being included in
a GPL project (the Apache license is a donor one)
> Also, what license/headers do I need to put at the top of a class when I
> contribute it? In some places it talks about "the POI License" and other
> places it talks about the ASL and releasing rights to the source under
> that license.
You should use the same standard Apache License header that's used in the
POI source code. I can't spot anything about "the POI license" anywhere,
can you point me to it?
> p.s. the link to the 'apache software license' in the checklist part of
> in http://poi.apache.org/guidelines.html is broken, it points to
> "licence-faq" rather than to "license-faq".
Thanks, I've fixed that in SVN, it'll go live the next time someone
builds+deploys the site
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org