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 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
Hi all,
Thanks for the replies,
2014/1/9 Bertrand Delacretaz bdelacre...@apache.org
I agree - following the student's work should give you reasonable
assurance that the code is their own, and the intent of the student to
contribute the code to Apache should have been clear from the start,
On Thu, Jan 9, 2014 at 12:28 PM, Benson Margulies bimargul...@gmail.com wrote:
...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
On Thu, Jan 9, 2014 at 1:28 PM, Alexander Broekhuis
a.broekh...@gmail.com wrote:
...What about IP Clearance? Does the same apply (we do know
the code is clean) and can we assume it is ok?...
If committers of the ASF project in question have followed the
development this is not very different
Hi all,
Perhaps this has been asked before, but I couldn't find a complete answer..
This summer a GSoC student implemented something for Celix which we now
want to include. Since this code is written outside of the foundation, I
would assume a standard code grant and clearance is needed.
Is
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.
On Wed, Jan 8, 2014 at 4:32 AM, Alexander
