For small libraries or small ebsites, I use the DWTFYWTPL: https://github.com/meduzen/canwe/blob/master/LICENSE
For bigger open source projects… I still have to make a choice. I’m only figuring out now I forgot to put a licence on canistop.net .
@celia I'm more of a content creator (videos, photos, 3D designs) than a programmer so I use mostly Creative Commons (CC BY-SA).
@celia Most of the times, other codes which I’m reusing dictate the license for my whole project. For the projects which I build from the ground up, I use LGPL for libraries (or codes which are supposed to be integrated with other projects). This gives the other devs freedom to include it in their own non-GPL-compatible packages and I use GPL for standalone codes.
@celia MPL. Because GPL for Rust.
@musicmatze Sorry, could you please explain your toot? I don't think I understand even a bit of it. 😅
MPL Code can Link to everything, GPL code cannot.
@celia #AGPL #GPLv3 #LGPLv3 because they protect the whole ecosystem from patent trolls, "tivoization", freeloading, trademarks and encourage cooperation.
@federico3 Those seem like huge benefits. Thanks for passing on the link!
@celia For experiments and examples, ISC/MIT/CC0/Unlicense. For user-facing programs, GPL-3.0-or-later, GPL-2.0-or-later or AGPL-3.0-or-later. For libraries, depends on the language and what is acceptable in its community.
@wire If I may ask, why those licenses in particular for experiments/examples?
Depends on the project (e.g. whether it's written content, or software). Typically Creative Commons ShareAlike for the former, GPLv3 for the latter.
@syntax Thanks. GPL/AGPL seems to be very popular!
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.