[cle-release-team] [sakai-pmc] Managing CLA's with new contributions

[Neal Caidin]

That's cool and definitely seems like it could be a part of the 
solution/workflow.

-- Neal


> Charles Severance <mailto:cseverance at imsglobal.org>
> March 18, 2014 at 11:26 AM
> It turns out that github has a feature to help in this.    If you make 
> a file called
>
> https://github.com/jquery/jquery/blob/master/CONTRIBUTING.md
> https://github.com/skulpt/skulpt/blob/master/CONTRIBUTING.md
> https://github.com/octokit/octokit.rb/blob/master/CONTRIBUTING.md
>
> It pops up when you do a pull request.
>
> We should use this to (a) insure that all who pull understand that 
> they are licensing their patches to us and (b) promote a CCLA iCLA for 
> those wanting to get more deeply involved.
>
> /Chuck
>
>
>
> Anthony Whyte <mailto:arwhyte at umich.edu>
> March 17, 2014 at 2:25 PM
> -1  Circling back.  I do not agree with this approach.  It introduces 
> fuzzy logic that at some point could catch us out.
>
>
> In my opinion, a signed iCLA needs to be on file before we accept a 
> code contribution, irrespective of its size or character.  It's a 
> simple rule and not all that hard to enforce.
>
> anthony whyte | its and mlibrary | university of michigan | 
> arwhyte at umich.edu <mailto:arwhyte at umich.edu> | 517-980-0228
>
>
>
>
> Kirschner, Beth <mailto:bkirschn at umich.edu>
> March 12, 2014 at 4:39 PM
> +1
>
> This makes sense to me. Everyone who reviews and commits patches 
> should make a judgement call on whether or not the patch constituties 
> significant "intellectual property" or just a 
> bug-fix/minor-enhancement. When in doubt, we should ask.
>
> - Beth
>
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> March 12, 2014 at 4:32 PM
> [Sakai PMC and Sakai Core Team]
>
> Howdy folks,
>
> I've been trying to get my brain wrapped around how to best manage 
> incoming contributions and CLAs. From talking (virtually) with the 
> Apereo Licensing group and based on the Apereo licensing documentation 
> [1] , it seems that the spirit or intention is that small fixes do not 
> need CLA's but larger and more complex contributions do need CLA's 
> (corporate Contributor License Agreements - CCLA's ; and individual 
> Contributor Licenses - iCLA's).
>
> One suggestion from Dr. Chuck is that at some point a "patch" becomes 
> a contribution when it includes new significant IP rather than just 
> fixing a bug or glitch and that it is up to those who have commit 
> privileges to make sure not to commit something large from a person 
> that does not have a CCLA.  Does everyone agree with this 
> characterization?
>
> [1] Apereo licensing documentation - http://www.apereo.org/licensing
>
> Thanks,
> Neal
>
>

-- 
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140318/9c54db80/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140318/9c54db80/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 992 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140318/9c54db80/attachment-0001.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1196 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140318/9c54db80/attachment-0002.jpg