• 2 Posts
  • 52 Comments
Joined 21 days ago
cake
Cake day: February 26th, 2025

help-circle
  • If you plan on making money off of your software, dual license AGPL and commercial. True open source developers can benefit from your work for free and contribute, while clients that would rather not have GPL can pay you.

    The reason for AGPL is to prevent people taking your GPL code, changing it, hosting it as SaaS, and never disclosing their changes as technically they’re not distributing the software.

    Also, your non core business libraries are the most prime candidates for GPL/AGPL. You want to benefit from community contributions to those, not bear the full cost of development and give it away for free without getting anything in return.



  • An organization pivoting hard on their entire software stack because someone didn’t like a word in a message somewhere… someone powerful in there didn’t arrive by competence alone.

    Considering there’s no incentive for a developer donating their work for free to add thin-skinned users to the masses demanding features and fixes, I can’t say I disavow them. Anyone can just fork their project to change the name, and handle the hassle.