If the student provides it as a patch, then you are asking the usual question about the quantity of code. There is no hard and fast rule, but unless it's very large, the AL is very clear; patches sent to mailing lists or attached to issue tracking systems or any of that are covered by the AL. If the amount of code is very large, or if the code is not clearly attached to a patch on a mailing list of issue tracker, then you would need an ICLA.
The SGA usually comes into play if the code is not the work and property of an individual. The SGA allows some entity to grant the AL unambiguously. If the code is the work and property of an individual, the ICLA does that just fine. Typically, the SGA is used for corporations donating code to projects. On Thu, Jan 9, 2014 at 5:23 AM, Pepijn Noltes <pepijnnol...@gmail.com> wrote: > Hi, > > > On Wed, Jan 8, 2014 at 3:53 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > >> The standard rules all apply to GSoC students. They should do their code >> in as close to the standard way as possible (which would have precluded the >> code being outside at this point) and they should file and ICLA if they do >> enough to warrant it. >> > > Thanks for the answer. It is not clear for me how the standard way would > have precluded the code being outside. IMO the standard way is to > communicate / discuss by mailing list, developed code outside and accept > it as patch. Then the student could have earned enough karma to be accepted > as committer. But maybe I am missing something? > This is also how we structured the GSOC project and as result the code is > written outside the foundation. > > The questions we are now struggling with are: to accept the donation do we > need an IP clearance?, if yes is a code grant needed? and if yes again who > should sign this grant ? > > Greetings, > Pepijn --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
