Ben Balter
@benbalter
@benbalter
Why you probably shouldn’t add a CLA to your open source project (TL;DR: a contributor-hostile developer experience w/ significant administrative overhead that shifts legal blame to the least resourced and is ultimately unnecessary w/ the right OS license) https://ben.balter.com/2018/01/02/why-you-probably-shouldnt-add-a-cla-to-your-open-source-project/
❗ Heads up! This Tweet is archived and here for historical purposes. It may no longer be accurate or reflect my views. Proceed at your own risk.
If you enjoyed this tweet, you might also enjoy:
- Why you probably shouldn’t add a CLA to your open source project http://...
- Why you shouldn’t write your own open source license http://bit.ly/2amQuA2
- Why open source? 25 reasons why you and your employer should consume, pu...
- GitHub now shows what open source license, if any, a project is licensed...
- DEVELOPERS DEVELOPERS DEVELOPERS (Atom's now on Windows) DEVELOPERS DEVE...
- Why your agency's first open source project is going to be a flop: http:...
- As open source projects grow, maintainers shift from the technical to th...
- Long Weekend Project: Open Source for Gov. -- A collaborative resource f...
- Enterprise, Open Source, and Why Better is not Enough: http://ben.balter...
- Do open source developers contribute to open source for the lulz? So oth...
- Your project’s README is your project’s constitution http://bit.ly/2pfJQY0