How to handle module contributions
My apologies if this has been asked before or is well documented somewhere. If it is I couldn't find it. What is the process for handling contrib module code donations from an IP clearance perspective? Example #1 (https://github.com/ptgoetz/storm-jms) An individual (me in this case) wishes to donate code that is licensed under the EPL, and has had a few contributions (no CLAs). Is switching to Apache v2 license and adding license headers all that would be necessary? Example #2 (https://github.com/hmsonline/storm-cassandra) Same story as the previous example, except this time it is a corporate entity. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: How to handle module contributions
My apologies if this has been asked before or is well documented somewhere. If it is I couldn't find it. What is the process for handling contrib module code donations from an IP clearance perspective? Example #1 (https://github.com/ptgoetz/storm-jms) An individual (me in this case) wishes to donate code that is licensed under the EPL, and has had a few contributions (no CLAs). Is switching to Apache v2 license and adding license headers all that would be necessary? Example #2 (https://github.com/hmsonline/storm-cassandra) Same story as the previous example, except this time it is a corporate entity. The project has transitioned to the Apache license. In each case, what is necessary to incorporate the code into an incubator project? (Sorry for the double post, I hit send accidentally.) -Taylor
Re: How to handle module contributions
The basic idea is that you have to have the right to incorporate the code and be able to demonstrate that right. For example #1, you can switch your contributions to ASL2 and be good, but you may have problems with the contributions of the others unless the contributions are trivial. For example #2, it is typically necessary to get a specific grant licensing the code to Apache. If the corporate entity were to relicense the code being donated under ASL2, that would suffice, but a letter indicating intent to donate would be nice. Others may have additional opinions so don't assume my answer is definitive. On Mon, Feb 17, 2014 at 3:04 PM, P. Taylor Goetz ptgo...@gmail.com wrote: My apologies if this has been asked before or is well documented somewhere. If it is I couldn't find it. What is the process for handling contrib module code donations from an IP clearance perspective? Example #1 (https://github.com/ptgoetz/storm-jms) An individual (me in this case) wishes to donate code that is licensed under the EPL, and has had a few contributions (no CLAs). Is switching to Apache v2 license and adding license headers all that would be necessary? Example #2 (https://github.com/hmsonline/storm-cassandra) Same story as the previous example, except this time it is a corporate entity. The project has transitioned to the Apache license. In each case, what is necessary to incorporate the code into an incubator project? (Sorry for the double post, I hit send accidentally.) -Taylor
Re: How to handle module contributions
Thanks Ted. Regarding contributions, if someone contributes (e.g. A pull request) to a project with an established license, couldn't that be considered an implicit grant of rights unless otherwise specified (e.g. License headers)? -Taylor On Feb 17, 2014, at 6:19 PM, Ted Dunning ted.dunn...@gmail.com wrote: The basic idea is that you have to have the right to incorporate the code and be able to demonstrate that right. For example #1, you can switch your contributions to ASL2 and be good, but you may have problems with the contributions of the others unless the contributions are trivial. For example #2, it is typically necessary to get a specific grant licensing the code to Apache. If the corporate entity were to relicense the code being donated under ASL2, that would suffice, but a letter indicating intent to donate would be nice. Others may have additional opinions so don't assume my answer is definitive. On Mon, Feb 17, 2014 at 3:04 PM, P. Taylor Goetz ptgo...@gmail.com wrote: My apologies if this has been asked before or is well documented somewhere. If it is I couldn't find it. What is the process for handling contrib module code donations from an IP clearance perspective? Example #1 (https://github.com/ptgoetz/storm-jms) An individual (me in this case) wishes to donate code that is licensed under the EPL, and has had a few contributions (no CLAs). Is switching to Apache v2 license and adding license headers all that would be necessary? Example #2 (https://github.com/hmsonline/storm-cassandra) Same story as the previous example, except this time it is a corporate entity. The project has transitioned to the Apache license. In each case, what is necessary to incorporate the code into an incubator project? (Sorry for the double post, I hit send accidentally.) -Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: How to handle module contributions
Judgement call depending on what you might consider a reasonable size for a minor fix versus an independent work (e.g. new module). The larger the patch the more likely you should consider having the author file some paperwork with Apache to cover the contribution. HTH On Feb 17, 2014, at 7:20 PM, P. Taylor Goetz ptgo...@gmail.com wrote: Thanks Ted. Regarding contributions, if someone contributes (e.g. A pull request) to a project with an established license, couldn't that be considered an implicit grant of rights unless otherwise specified (e.g. License headers)? -Taylor On Feb 17, 2014, at 6:19 PM, Ted Dunning ted.dunn...@gmail.com wrote: The basic idea is that you have to have the right to incorporate the code and be able to demonstrate that right. For example #1, you can switch your contributions to ASL2 and be good, but you may have problems with the contributions of the others unless the contributions are trivial. For example #2, it is typically necessary to get a specific grant licensing the code to Apache. If the corporate entity were to relicense the code being donated under ASL2, that would suffice, but a letter indicating intent to donate would be nice. Others may have additional opinions so don't assume my answer is definitive. On Mon, Feb 17, 2014 at 3:04 PM, P. Taylor Goetz ptgo...@gmail.com wrote: My apologies if this has been asked before or is well documented somewhere. If it is I couldn't find it. What is the process for handling contrib module code donations from an IP clearance perspective? Example #1 (https://github.com/ptgoetz/storm-jms) An individual (me in this case) wishes to donate code that is licensed under the EPL, and has had a few contributions (no CLAs). Is switching to Apache v2 license and adding license headers all that would be necessary? Example #2 (https://github.com/hmsonline/storm-cassandra) Same story as the previous example, except this time it is a corporate entity. The project has transitioned to the Apache license. In each case, what is necessary to incorporate the code into an incubator project? (Sorry for the double post, I hit send accidentally.) -Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: How to handle module contributions
yeah. What Joe said. On Mon, Feb 17, 2014 at 4:27 PM, Joseph Schaefer joe_schae...@yahoo.comwrote: Judgement call depending on what you might consider a reasonable size for a minor fix versus an independent work (e.g. new module). The larger the patch the more likely you should consider having the author file some paperwork with Apache to cover the contribution. HTH On Feb 17, 2014, at 7:20 PM, P. Taylor Goetz ptgo...@gmail.com wrote: Thanks Ted. Regarding contributions, if someone contributes (e.g. A pull request) to a project with an established license, couldn't that be considered an implicit grant of rights unless otherwise specified (e.g. License headers)?
Re: How to handle module contributions
Thanks Ted and Joe for the clarification. It helps a lot. -Taylor On Feb 18, 2014, at 12:18 AM, Ted Dunning ted.dunn...@gmail.com wrote: yeah. What Joe said. On Mon, Feb 17, 2014 at 4:27 PM, Joseph Schaefer joe_schae...@yahoo.comwrote: Judgement call depending on what you might consider a reasonable size for a minor fix versus an independent work (e.g. new module). The larger the patch the more likely you should consider having the author file some paperwork with Apache to cover the contribution. HTH On Feb 17, 2014, at 7:20 PM, P. Taylor Goetz ptgo...@gmail.com wrote: Thanks Ted. Regarding contributions, if someone contributes (e.g. A pull request) to a project with an established license, couldn't that be considered an implicit grant of rights unless otherwise specified (e.g. License headers)? signature.asc Description: Message signed with OpenPGP using GPGMail
