time! I want to know what licence you mostly use for your F(L)OSS projects. Imagine, you don't have to comply with anyone, and you're free to choose. Which one you'll use?

I am also interested, which traits of a licence are important to you. Stating changes? Using the same licence? Attribution?

(Licences sorted from strongest to weakest. A poll can only have 4 choices, so some had to be aggregated; I tried to put the similar ones together)

Follow

I am personally on crossroads with this.

I mean, I kinda do want at least some form of attribution for my work, so Unlicense/WTFPL is a bit too weak for me. GPLv3 looks great in terms of sharing improvements, but it's just too clunky, and it's a hassle to fork such projects as one has to include the copy in literally every file.

So I'm kinda stuck with the MIT. While I like that it's permissive, I sometimes wish it would oblige others to open-source the modifications too

@NickKaramoff

> and it's a hassle to fork such projects as one has to include the copy in literally every file

Really? Does GPL require that? I just put attribution in like one entry point file or don't do this at all

@NickKaramoff you can create your own license. No one is stopping you from.doing that

@lxzio I know — it just takes time and deep understanding of various copyright laws, which I currently do not have :(

@NickKaramoff no no . You can copy the GPL license and remove the parts which you feel is not worth forcing people to follow

Sign in to participate in the conversation
Fosstodon

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.