+1 to removing CLAs on single licensed modules. This creates an unnecessary barrier to people who may have restrictions from their corporate overlords with the CLA but no issue whatsoever with a pure FOSS contribution.
Trevor On Tue, Aug 19, 2014 at 9:08 AM, Daniele Sluijters < daniele.sluijt...@gmail.com> wrote: > Hey, > > I'm also fairly annoyed by the CLA bot on modules. Most, if not all, > modules have been licensed under the Apache License 2.0 since their > publication on Github. As such, contributions are automatically covered by > this license. It might be worth mentioning this in a CONTRIBUTORS.md but > having the CLA bot involved needlessly complicates the contribution process > to modules. > > I can understand this happening on the core products because they're > dual-licensed, the modules however are not and we should not put up more > obstacles for contributors, we should be removing them. > > -- > Daniele Sluijters > > > On Tuesday, 19 August 2014 15:01:15 UTC+2, Igor Galić wrote: > >> Fellow Humans, >> >> Recently the puppetcla bot has been activated for most >> puppetlabs-modules. >> This has sparked a *lot* of controversies from people who just contribute >> the most trivial of fixes, >> >> * https://github.com/puppetlabs/puppetlabs-apache/pull/775 >> * https://github.com/puppetlabs/puppetlabs-java/pull/63 <<<< >> * https://github.com/puppetlabs/puppetlabs-postgresql/pull/448 >> >> >> Now, ignoring the understandable criticism that PRs should be merged >> faster, >> i think we need to have a discussion on what warrants a CLA signing. >> >> Speaking with my Apache Software Foundation hat on: we only ask people to >> sign a CLA who are committers - or in git terms, those with merge access. >> We entrust *them* to judge patches from third parties. >> We have done this since times immemorial. Before we had git. Before there >> *was* >> git. Before it was *this* easy to contribute a patch. It still is. Random >> drive-by contributions happen every day, some of them even through >> GitHub! >> >> At this point i'm kinda stuck for argumentation, from my perspective, and >> the >> expressed bewilderment of many contributors it seems silly we even have >> to >> bring this up at all. >> >> >> So long, >> >> -- >> Igor Galić >> >> Tel: +43 (0) 664 886 22 883 >> Mail: i.g...@brainsware.org >> URL: http://brainsware.org/ >> GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641 >> >> -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/f2ad6f36-f92b-47be-8151-d751c91e40f3%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-dev/f2ad6f36-f92b-47be-8151-d751c91e40f3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoWw-N6DD9jOqFSVg5kVajQNHPvMBPCTmm8j%2B8R05dVnpw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
