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.ga...@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/1251781699.678.1408453265551.JavaMail.zimbra%40brainsware.org. For more options, visit https://groups.google.com/d/optout.
