These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

Picking a license
Author
Previous Topic Next Topic
Salgare
Center for Advanced Studies
Gallente Federation
#1 - 2016-08-23 16:07:38 UTC  |  Edited by: Salgare
What are the considerations on picking an opensource license?

eta:

Found this site: http://choosealicense.com

I guess there is no reason to not pick the strongest copyleft (gnu) license.
Salgare
Center for Advanced Studies
Gallente Federation
#2 - 2016-08-23 16:56:30 UTC
Also, any help of how to handle CCP license would be appreciated. i.e. logo's required on gui's, reference in source file headers, reference in source root (i.e. license.md's, copy.md's etc.)
Dragonaire
Here there be Dragons
#3 - 2016-08-24 19:03:14 UTC
GPL is usually best and what I've used. If you are looking to release something that is more of an library that a tool or an app might look at LGPL. I decided it was a better fit for Yapeal when I was looking at the same thing.

As far as the CCP licensing I haven't really dealt with that since I'm not doing any kind of app or anything but made sure you've read through the third party licensing stuff from them and work on the principal that it's better to over do copyright notices etc than to under and you should be okay. Hopefully someone else that has done front-end apps can step in with some more ideas here.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.
Salgare
Center for Advanced Studies
Gallente Federation
#4 - 2016-08-25 02:00:19 UTC
Dragonaire wrote:
GPL is usually best and what I've used. If you are looking to release something that is more of an library that a tool or an app might look at LGPL. I decided it was a better fit for Yapeal when I was looking at the same thing.

As far as the CCP licensing I haven't really dealt with that since I'm not doing any kind of app or anything but made sure you've read through the third party licensing stuff from them and work on the principal that it's better to over do copyright notices etc than to under and you should be okay. Hopefully someone else that has done front-end apps can step in with some more ideas here.


Thanks Dragonaire, I noticed you were using the lgpl. I ended up going with this as well. If I understand it correctly, what this means is that any additions/modifications to forked code must give that fork the same licenses, but that the code using said fork can be what ever license it desires. Thus the blood line of the original improves and is available to all, but others using it are not locked down.

In working on github, I found they will host a static domain web server for you and its very easy to use. I went with the "master gh-pages branch" method, which is really cool/easy simply push to the branch and it publishes.

I simply captured some info from posting here that I want to remember/fix up later, but I got my licensing, copyright, twitter, email and now domain all fixed up ... check it out:


https://timpanogos.github.io/crestj - static hosted
https://github.com/timpanogos/crestj - see readme links everything up
Dragonaire
Here there be Dragons
#5 - 2016-08-25 18:09:14 UTC
Yeah it let's them license their app however they like but they have to give back and make sure to let people know about the license on your project which seems a good balance for what I was doing. Looking at what your doing it's also seems like a good match to me.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.
Golden Gnu
Lobach Inc.
#6 - 2016-08-26 19:29:01 UTC
I just wanted to add my 2 cents to this:

Choosing GPL instead of LGPL for libraries force people to use an open source license if they want to use your library, this can help make some software open source, that would have been closed source otherwise. Simplified: more user vs more open source software. There are no wrong chooses, as far as I understand it, it's more about personal preference (what you want to allow). Anyway, I just wanted to add this observation. :)

Creator of jEveAssets - the asset manager

"Download is the meaning of life, upload is the meaning of intelligent life"
Salgare
Center for Advanced Studies
Gallente Federation
#7 - 2016-08-26 20:28:47 UTC
Golden Gnu wrote:
I just wanted to add my 2 cents to this:

Choosing GPL instead of LGPL for libraries force people to use an open source license if they want to use your library, this can help make some software open source, that would have been closed source otherwise. Simplified: more user vs more open source software. There are no wrong chooses, as far as I understand it, it's more about personal preference (what you want to allow). Anyway, I just wanted to add this observation. :)



I think I noted that squizz went full blown AGPL on zkill, at least some of the repo's I looked at.

My choice of LGPL over GPL boiled down to giving a bit more encouragement for others to use my "special snowflake" hehe