...
- See report that went out in advance of the meeting
- Team mostly focused on bug fixes
- Planning 6.2 release by end of March
- Bug fixes, dependency updates
- New feature: stats reporting - basic stats on content of repository, # of objects: binary vs. non-binary objects, by MIME type, etc.
- Camel toolbox has been released
Contributor License Agreements (Danny)
- Have been maintaining CLAs since project began. Don't have 100% coverage for all small contributions but have CLAs for major contributors
- CLAs falling out of fashion in open source projects, cause drag on project, esp. when large numbers of contributors
- DSpace, RedHat do not use CLAs
- Issues mainly theoretical; in practice, has never been a problem
- See Contributor License Agreements: Do we really need them? for pros and cons
- Some motivations no longer apply given Git/GitHub
- Has Lyrasis consulted legal counsel? No
- Thomas: Would make it easier to change license later on
- Jon: Individual developers employed by institutions not able to enter into legal agreements, CLAs help with this, but still not be a big issue
- GitHub can help automate CLA process (at least individual - not institutional - CLAs) - Samvera is moving to this
- Scott: What are risks of not having CLAs? May want to consult with lawyer
- In Apache Software Foundation, CLAs are required for committers but not contributors (though encouraged for committers) - could be a compromise
- If licensing processes are changed, would update the welcome package/code of conduct to reflect
- Are other updates to CoC necessary?
- Arran will share CLA text with the group to help us fully consider this issue