search

drusepth / Indent

Indent is a set of tools for writers, game designers, and roleplayers to create magnificent universes – and everything within them.
http://indentapp.com
1 stars 1 forks source link

Choose a license #351

Open drusepth opened 10 years ago

drusepth commented 10 years ago

^ title

Cantido commented 10 years ago

How about some discussion?

http://choosealicense.com/

I always pick the GPL, and I don't think you need to worry about having corporate support relying on proprietary spinoffs.

drusepth commented 10 years ago

I absolutely welcome (and recommend) discussion. I typically just throw code at GitHub for myself, so I don't actually know much about various licenses and what they entail.

From the link, I think GPLv3 or MIT look the most solid from the options, but I've heard GPL typically ends up too restrictive or a legal nightmare from others / past companies. Looking at the site I don't see why, but maybe @linuxmercedes or @euank might be able to chime in on that?

LinuxMercedes commented 10 years ago

What do you want to do with Indent in the future? Are you okay with forks? What about companies forking it and making money off of a fork? Or do you want them to be more like an email provider, where they only profit off hosting the software?

I license a lot of my stuff MIT/BSD, but that's because almost all of it is made for me and I don't care what other people do with it beyond that. If you do, MIT/BSD is probably not the way to go (and GPL probably is).

euank commented 10 years ago

I personally like ISC more than MIT/BSD. Apache license is also nice (see the patent issues it solves).

You can also dual-license under GPL + something else where you say "It's GPLv3 ... if you need something else specifically contact me and I can give you an alternate permissive license on a case by case basis".

I really don't know exactly what you want to do, but ISC/Apache are pretty sane MIT-like licenses, and you could also just public domain the whole darn thing (see unlicense).

drusepth commented 10 years ago

What do you want to do with Indent in the future? Are you okay with forks? What about companies forking it and making money off of a fork? Or do you want them to be more like an email provider, where they only profit off hosting the software?

I'm okay with forks, regardless of whether they may make money or not. My views on the subject are that if someone else can fork Indent and make it more successful than the original, more power to them; regardless of who does it, the product gets made.

My personal goals in finding a proper license for Indent are:

  1. To make developers feel more comfortable about contributing under a specific, known license.
  2. To let developers know that they are free to take Indent and run with it wherever they see fit.

However, I'd also be interested in what goals contributors and other developers would be looking for in a license. If it were just me, I'd just say, "Hey everyone, this code is ours!" But I don't know how appealing/unappealing that is towards someone thinking about contributing.