licensing - Base Action URL

Base Action URL

Sign in Subscribe

licensing

A collection of 4 posts

Contributor License Agreement landscape

Contributor License Agreement landscape

In which I survey the landscape of Contributor License Agreement practices. Motivation This post is supporting background for some conversation and formation of opinions. This post isn't those conversations or opinions. See also * Analysis of Apache Foundation practices around CLAs [http://apetro.ghost.io/apache-contributors-no-cla/] * Proposal to adjust

Why bother stopping hassling Apereo contributors for ICLAs?

Why bother stopping hassling Apereo contributors for ICLAs?

You might wonder why getting Apereo to [https://groups.google.com/a/apereo.org/d/msg/licensing-discuss/c1puG3RKZcA/Tonk3d23AQAJ] be more like Apache [https://apetro.ghost.io/apache-contributors-no-cla/] and stop hassling contributors to sign ICLAs, and to stop hassling committers to check whether would-be contributors have signed ICLAs, is important

Apache contributors need not sign a CLA

Apache contributors need not sign a CLA

In which I observe that the Apache Software Foundation does not require code contributors to sign Contributor License Agreements. I am not a lawyer and this is not legal advice. As always in this blog I speak only for myself and not for my employer, organizations with which I work,

Parable of the web framework selection

Parable of the web framework selection

In which I work an example of how important ICLA gravitas is to adopters of open source software. Disclaimer As always on this blog I speak only for myself and not for my employer, the organizations and projects I work with, etc. Background Sometimes open source projects require [https://julien.