Conversation

Notices

1. Embed this notice
   R. L. Dane :debian: :openbsd: (rl_dane@fosstodon.org)'s status on Thursday, 09-May-2024 16:40:12 JST R. L. Dane :debian: :openbsd:

   • pixelfed
   • :pink_moon_and_stars: Octavia con Amore :pink_sparkles:
   • Stemy

   @OctaviaConAmore @stemy @pixelfed

   Contributor License Agreement. Unlike the license for the code itself, the CLA is a license you must agree to before your code contributions can be accepted into the project.

   Sometimes they're minor, like "this project will always and only be GPL-licensed," or more odious, like "you must resign all rights to the code you contribute to us/public domain"

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Thursday, 09-May-2024 16:40:12 JST clacke

     in reply to

     • pixelfed
     • :pink_moon_and_stars: Octavia con Amore :pink_sparkles:
     • Stemy

     @OctaviaConAmore Here's an essay that goes into more why CLAs are unnecessary to a true and good faith community project and not so much about the risk they pose to a project:

     sfconservancy.org/blog/2014/ju…

     @RL_Dane @stemy @pixelfed

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Thursday, 09-May-2024 16:40:17 JST clacke

     in reply to

     • pixelfed
     • :pink_moon_and_stars: Octavia con Amore :pink_sparkles:
     • Stemy

     The risk, to be brief, is that a CLA provides one community member, usually a founding member that is a corporation, privileges that other members do not have.

     It gives them the power to do a rug-pull and take future development of the software out of the open source world, as we have seen with e.g. MongoDB, Redis and HashiCorp's products.

     @pixelfed @RL_Dane @OctaviaConAmore @stemy