zzz.i2p

Development discussions
Free Software License - Gnufy I2P « Bug Reports and Feature Requests « I2P Help, Hints, Advice
 
Thu, 27 Feb 2020, 09:55pm #1
anonymous maybe
I2P Legend

I2P is a mess of licenses and to summarize that will comment on:

- Public Domain License:

"Public domain software is software that is not copyrighted. If the source code is in the public domain, that is a special case of noncopylefted free software, which means that some copies or modified versions may not be free at all."

Free Software , Free Society v3 page 82 https://www.gnu.org/doc/fsfs3-hardcover.pdf

This is really not nice treatment to i2p devs and their contributors for keeping them always vulnerable to a proprietary fork from whoever for whatever reason. not talking about gratis and money because this can be done as well with free software im talking about software freedom.

- Why not BSD or any noncopyleft free software license:

https://www.gnu.org/philosophy/categories.en.ht...

https://www.gnu.org/licenses/bsd.html

- Better to use Copyleft free software license:

https://www.gnu.org/licenses/copyleft.html

- Best Options available:

GPLv3: https://www.gnu.org/licenses/gpl-3.0.en.html

AGPLv3: https://www.gnu.org/licenses/agpl-3.0.en.html

Fri, 28 Feb 2020, 12:49pm #2
zzz
Administrator
Zzz

This is an 18 year old project.

The theory that "public domain is not a license" was not widely understood 18 years ago.

However it does not make anybody "vulnerable".

It would be impossible to relicense as we would have to contact every past contributor to get their consent

If we did relicense or add a license, it would be one of the CC licenses. Certainly not GPLv3.

Fri, 28 Feb 2020, 01:26pm #3
anonymous maybe
I2P Legend

looking at here: https://geti2p.net/en/get-involved/develop/lice...

essential parts of I2P lead by you (which are enough). i dont see a need to contact contributors from before to license the product into free software license.

> However it does not make anybody "vulnerable".

someone/company...etc forking i2p and making it proprietary software which can be done anytime = This vulnerability im talking about, because it will take my time and effort which i spent here and someone turning it into proprietary.

> If we did relicense or add a license, it would be one of the CC licenses. Certainly not GPLv3.

No problem, but be careful that not all CC licenses are free software licenses. Plus most CC used for web contents (docs,videos,..etc).

also i would like to know why not copyleft compatible license? (gpl,agpl..etc)

or you mean GPLv3 specifically? (if so check v2)

Fri, 28 Feb 2020, 01:26pm #4
anonymous maybe
I2P Legend

looking at here: https://geti2p.net/en/get-involved/develop/lice...

essential parts of I2P lead by you (which are enough). i dont see a need to contact contributors from before to license the product into free software license.

> However it does not make anybody "vulnerable".

someone/company...etc forking i2p and making it proprietary software which can be done anytime = This vulnerability im talking about, because it will take my time and effort which i spent here and someone turning it into proprietary.

> If we did relicense or add a license, it would be one of the CC licenses. Certainly not GPLv3.

No problem, but be careful that not all CC licenses are free software licenses. Plus most CC used for web contents (docs,videos,..etc).

also i would like to know why not copyleft compatible license? (gpl,agpl..etc)

or you mean GPLv3 specifically? (if so check v2)