GnuPG Github mirrors

Werner Koch wk at
Tue Oct 27 16:31:08 CET 2015

On Tue, 27 Oct 2015 11:24, jeroen.ooms at said:

> For example if I currently have a suggestion for a new GnuPG FAQ entry
> I would have to download the code, create a patch, send that to the
> mailing list, and then hope that you are actively reading the mailing
> list, apply the patch and push. In Github I would simply clone the
> repo, commit the changes, and send you a pull request in which we can
> together review/discuss/tweak the changes until you are pleased and

We already discuss patches on the mailing list.  Sending and applying
patches via by mail is a native Git feature and all workflow has been
optimized for this.  Sending URLs is an alien thing and does only work
if you have an online connection.

Prospective developers with a GitHub mindset will have a hard time to get
accustomed to regular Free Software development.  I have seen people
evangelizing for Git but didn't understand the basic commands because
they come from Github.  Sorry, you need to get your feet wet before
diving into GnuPG development.

> this year, Daniel Stenberg (maintainer of libcurl) explains why he

Daniel is not known as a strong supporter of the Free Software idea and
thus he sets other priorities.  Anyway, feel free to mirror stuff
wherever you like - after all this is what Free Software is about.  To
avoid confusion it would be nice to clearly state that the commonly used
GnuPG version is hosted elsewhere.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

More information about the Gnupg-devel mailing list