Hi Mark, > On Jan 21, 2019, at 10:50 AM, Mark Thomas <ma...@apache.org> wrote: > > On 21/01/2019 17:59, Roy Lenferink wrote: >> I think it is an excellent idea to suggest submitting an ICLA to >> contributors when they submit a contribution. > > Generally, adding barriers to participation reduces contributions rather > than increases them.
I agree. Requiring ICLAs should be done only when the size of the contribution warrants it. > > If folks want to submit an CLA then of course they can (and there is no > harm in pointing this out to a new contributor) but it should remain > optional until someone is made a committer. Well, the criteria we have used in the past is not "someone is made a committer" but "the size of the contribution would make it difficult to unwind". > > I'll go further and say that I have seen some projects require CLAs from > contributors for some/all contributions and I think that is adding > unnecessary barriers to participation. I agree with this. Casual contributions should not require ICLAs. But I think that we can use a request for an ICLA not as a barrier to contributions but an incentive to more involvement. "We have noticed your contributions to Apache Foo and value your involvement in the project. We would like to invite you to submit an ICLA to cover your contributions. This is not required, but demonstrates your commitment to Apache Foo." Wordsmithing may be needed here. > >> CNCF is using a bot on their GitHub repositories which adds a label to >> every pull request whether the contributor has a cla on file [1][2]. >> More info on this here [3] >> The cla label is checked before the PR can be merged. >> >> As we're moving to a broader GitHub integration maybe it is an idea to use >> a technology like this as well. > > That would make CLAs mandatory and I disagree very strongly with any > move in that direction. > >> I can foresee a small problem with this, as AFAIK all CLAs are still >> processed manually, but correct me if I'm wrong. > > CLA processing is largely automated and work is in hand to make it more so. Well, not so much yet. There is tooling but there is also substantial human involvement in the process, which IMHO is essential to preserve the integrity of our records. Craig > > Mark > >> >> What do you think? >> >> [1] http://home.apache.org/~rlenferink/img/cncf-cla-message.png >> <http://home.apache.org/~rlenferink/img/cncf-cla-message.png> >> [2] http://home.apache.org/~rlenferink/img/cncf-cla-reporting.png >> <http://home.apache.org/~rlenferink/img/cncf-cla-reporting.png> (last >> job: cla/linuxfoundation) >> [3] >> https://github.com/kubernetes/community/blob/master/CLA.md#the-contributor-license-agreement >> >> <https://github.com/kubernetes/community/blob/master/CLA.md#the-contributor-license-agreement> >> >> - Roy >> Craig L Russell Secretary, Apache Software Foundation c...@apache.org <mailto:c...@apache.org> http://db.apache.org/jdo <http://db.apache.org/jdo>
