2 ms·
There's a good reason why you see so few institutional contributors to Chef: Chef Inc. insists that your employer sign a Contributor Licensing Agreement (CLA) b
by chrissnell 12y ago
There's a good reason why you see so few institutional contributors to Chef: Chef Inc. insists that your employer sign a Contributor Licensing Agreement (CLA) before your PR will be merged. That's a big obstacle for many companies. There aren't a lot of legal departments that have the bandwidth to process these agreement forms just so that one of their employees can contribute to some other company's code base.
Back when I worked at Rackspace, I had to jump through many, many hoops [1] just to get my one patch [2] to knife-rackspace merged. And I had it easy: Rackspace already had a running CLA with Opscode because Rackspace needed those patches to flow. Most employers could care less.
[1] https://github.com/opscode/knife-rackspace/pull/42 https://github.com/opscode/knife-rackspace/pull/42
[2] https://github.com/opscode/knife-rackspace/commit/d3943977600c6a31825164684df1584dfa5c2e7e https://github.com/opscode/knife-rackspace/commit/d394397760...
- viraptor 12y agoYes, it's really annoying. Especially if you have things that are literally 1 character issues. The amount of bureaucracy involved is enough that I'm not going to bother. Instead bugs like https://tickets.opscode.com/browse/CHEF-3755 https://tickets.opscode.com/browse/CHEF-3755 get raised and... ignored. Even if fixing it probably takes less time than commenting that it's going to triage. Sigh...