| Last week we showcased our open-source project, OpenLIT (https://github.com/openlit/openlit), here, and thanks to this incredible community, we hit 300 stars in just a couple of days! One of my mentors, a core lead on OpenTelemetry, suggested we consider adding a Contributor License Agreement (CLA) to our project, similar to what has been done with OpenTelemetry. I understand the potential legal benefits a CLA offers, such as ensuring contributions can be freely used and distributed, which could be crucial for the project's long-term viability and to avoid legal complications. However, I’m equally concerned about the potential downsides, especially regarding community contributions. I worry that a CLA might stop new contributors who prefer to avoid legal hurdles or are reluctant to sign documents. Since OpenLIT aims to be truly open-source and community-driven, keeping the contribution process as straightforward as possible is essential to me. So, I’m turning to you, HN community, for guidance: - Have you implemented a CLA for your project? What impact did it have on contributions?
- As a contributor, do you find CLAs off-putting? Why or why not?
- What recommendations do you have for a CLA that isn't too restrictive but still provides necessary legal protections? I'm also open to tool suggestions for managing CLAs or examples from your own open-source projects that I can learn from. Thanks in advance for your wisdom and advice! |