Python-GnuPG
github.com
Python-GnuPG
1–10 of 16 posts
Re: Python-GnuPG
#2The source of the fork is this: https://bitbucket.org/vinay.sajip/python-gnupg/ I don't get why the fork was done as this repo seems active.
Re: Python-GnuPG
#3It is really unfortunate that a library is licensed under the GPL. It means any released software that uses this also has be GPL, which restricts the freedom of the downstream developer from making their own software be licensed under their preferred license. This library calls out to the gpg binary, so there is no reason it has to be GPL.
Re: Python-GnuPG
#4The source of the fork is this: https://bitbucket.org/vinay.sajip/python-gnupg/ I don't get why the fork was done as this repo seems active.
Knowing the general open source community, the fork was made because the original is not on GitHub. Unfortunate.
The biggest selling points are "security patches, extensive documentation, and extra features". Shame these weren't just contributed upstream.
Re: Python-GnuPG
#5It is really unfortunate that a library is licensed under the GPL. It means any released software that uses this also has be GPL, which restricts the freedom of the downstream developer from making their own software be licensed under their preferred license. This library calls out to the gpg binary, so there is no reason it has to be GPL.
Yes, that is the whole point...
Re: Python-GnuPG
#6It is really unfortunate that a library is licensed under the GPL. It means any released software that uses this also has be GPL, which restricts the freedom of the downstream developer from making their own software be licensed under their preferred license. This library calls out to the gpg binary, so there is no reason it has to be GPL.
Exactly. The GPL protects freedom exceptionally well as you have noticed.
Re: Python-GnuPG
#7The source of the fork is this: https://bitbucket.org/vinay.sajip/python-gnupg/ I don't get why the fork was done as this repo seems active.
Knowing the general open source community, the fork was made because the original is not on GitHub. Unfortunate. The biggest selling points are "security patches, extensive documentation, and extra features". Shame these weren't just contributed upstream.
[deleted]
Re: Python-GnuPG
#8Standard approach to fix bugs in libraries: 1. fork it 2. fix it 3. post to HN 4. profit. Seriously, I hope this was reported to the original author beforehand.
Re: Python-GnuPG
#9The source of the fork is this: https://bitbucket.org/vinay.sajip/python-gnupg/ I don't get why the fork was done as this repo seems active.
Knowing the general open source community, the fork was made because the original is not on GitHub. Unfortunate. The biggest selling points are "security patches, extensive documentation, and extra features". Shame these weren't just contributed upstream.
I really dislike the monopoly that Github has in many parts of the industry, it substracts from the value of git and the like. Also so many package managers etc. are tied to Github, which is a shame because there's no guarantees that it'll continue to exist or not ever be sold to an indecent investor.
Re: Python-GnuPG
#10It is really unfortunate that a library is licensed under the GPL. It means any released software that uses this also has be GPL, which restricts the freedom of the downstream developer from making their own software be licensed under their preferred license. This library calls out to the gpg binary, so there is no reason it has to be GPL.
Yes, that is the whole point...
For a library LGPL would be a better choice than GPL.