Meeting Logistics:
Time: 9:00am PDT / Noon EDT
Zoom Meeting URL: https://princeton.zoom.us/j/7739591625
(link will launch Zoom client – if you do not have Zoom, expand the instructions below)
Agenda (meeting notes below)
Making iCLA checking easier Heather Greer Klein
Institutional agreements - existing ones are easier
Individual CLAs more difficult
Can potentially “poison the well” if code is added without CLA
Currently depends on individual people merging code having a sense of who is in the community and likely has a CLA. No automation.
Potential option - https://www.linuxfoundation.org/blog/easycla-beta/
After Tech Call, review analytics PR: https://github.com/samvera/hyrax/pull/5089 - Juliet Hardesty
Moderator: Lynette Rayle
Notetaker: Collin Brittle
Attendees:
Lynette Rayle (Cornell)
Collin Brittle (Emory)
Thomas Scherz (Cincinnati)
Max Kadel (UNC Chapel Hill)
Chris Colvard (Indiana)
Meeting Process
Notes
Making iCLA checking easier Heather Greer Klein
One hurdle is getting a CLA signed. Especially for one-time, or first-time committers.
Also an issue for international contributors
Could we use something like docusign to streamline this?
Is an individual iCLA enough to merge a PR?
A cCLA is necessary as well.
Any contribution not covered with both could poison the well.
Heather is talking with Oasis about whether it is needed at all.
What is the offboarding process?
We don’t have one
The person keeps the iCLA, but the corporate line is replaced with their new employer.
Current process is “I see a PR, I don’t recognize the contributor, ask if they have an iCLA.”
Not automatic, and requires the merger to know everyone.
Linux has an EasyCLA GitHub plugin.
Does this cover cCLAs and iCLAs?
Heather will investigate
After Tech Call, review analytics PR: https://github.com/samvera/hyrax/pull/5089 - Juliet Hardesty