22
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Mar 2024
22 points (89.3% liked)
Opensource
1366 readers
10 users here now
A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!
⠀
founded 1 year ago
MODERATORS
Thats pretty awesome. I read about the agpl and I use it in a project of mine newly.
Do you have any resources to read up about the thought process behind licensing? Because I see two arguments here:
There sure are a lot more ideas to this.
For resources on licenses, off the top of my head there are:
Both sites have breakdowns of each license for the layperson. As always, the GNU Licenses page has others.
In response to your arguments:
The choice is mainly about how much effort you're willing to pour into supporting the project alone if others take interest in it, how much you want others to be willing to pour into supporting your project via contributions or financials, and how you would feel if a more successful fork of your project becomes more restrictive after a license change or organisation restructuring (looking at you, Gitea and RedHat).
My personal choice in license is simple. Most of my software is for me and works on my machines. I also don't want commercial entities providing my software as a service without contributing code back, so AGPL is an easy choice. I do have a disclaimer on my public facing git forge that none of my AGPL licensed projects support dual licensing because I value code contributions more than money, especially if they come from the enterprise sector.
Thats awesome! Thank you so much for taking the time to write this out. I have a good understanding of your pov now and I like it.
Would you mind connecting on dm or matrix if one ever wanted to help? I‘m currently working on a couple projects which require me to step up my game quite a lot. I‘d be interested in your opinion.
Have a good one.