You Got A Question? Ask    GNOME Community!

 14188   |  Oct 25
 10177   |  Aug 25
 9800   |  Mar 17
 8872   |  Mar 28

GNOME is now available on GitHub!

This post was made with an older stylesheet

If you pay a visit at you will find all the GNOME modules available for cloning! This is not the first time that GNOME uses GitHub, there is also the GNOME Design Team repository –which is not official GNOME. This work was made by Alberto Ruiz and Andrea Veri around a month ago.

GNOME and GitHub

GNOME is not just about free software but also is an independent foundation that provides independent -free- software. They (GNOME) don’t use out sourcing services and they have full control of their software stack, at least as much as this is possible.

Github is a close source service and GNOME’s choice of using it might get criticized.

A few things. First this is nothing but a mirroring from GNOME Git, and GNOME isn’t relying on Github for any of their activities. Second, this is a good way of promoting Free Software through a closed source service, and not the other way around.


After all, Github is a large contributor of Open Source and more importantly it provides an excellent infrastructure that devs use daily to write and provide free software.


People can get all the goodies that Github offers, like activity diagrams while most of us are used to read commits in Github format rather in G-Git. At the same time Github provides a backup solution in GNOME Git in case that things go wrong in main servers.

Of course the real goal here is for GNOME to attract new contributors. Find a small tiny bug, clone the repository in your Github account, fix the bug and file a bug report in bugzilla with your github repository commit. There is git-bz to submit patches directly to Bugzilla, but I guess none will blame you if you submit a Github link :)

For more details:


Issues and wikis are disabled and all the pull requests will be ignored. So basically GNOME don’t intend to make any changes to the existent contribution/review workflow.

How it works

What happens behind the curtain is a mirroring script that makes use of the ‘git push –mirror ssh://destination‘ git feature with some dirty tricks to create the repo if it’s missing etc.

In any case you can safely use Github to clone your GNOME Modules as the mirroring becomes instantly from GNOME Servers.


If you want to learn more about the GNOME Infrastructure is a good idea to watch Andrea Veri and Sriram Ramkrishna speech in GUADEC.

If you have missed the link, you can watch all talks of GNOME devs at:

  We can't watch comments unless G+ provides an API or if you send a notification, e.g +World Of Gnome
     Sometimes is better to place your questions on GNOME Community
  • Adonis K. (Varemenos)

    If issues, pull requests and wikis are disabled/ignored what’s the purpose of it? It’s just like making social profile that you will later ignore…

    • alex285

      Speaking about my self, I quit visiting after this. I have github always on browser anyway;)

      General speaking, time will show if this will increase forks, watches and stars.

      • Adonis K. (Varemenos)

        But lets say you want to contribute to gnome’s repository, your only choice is therefore making github pointless. Personally I’d like for them to use github fulltime because I use it daily as well, otherwise they should quit it.

        • alex285

          “But lets say you want to contribute to gnome’s repository, your only choice ”

          Not really, only regular contributors have git access. If you want to contribute a patch, u need to submit in bugzilla with git-bz or clone a repo in Github and pass the patch link. Having GNOME in Github is a great convenience in the second option.

        • Eduard Gotwig

          github is proprietary, so no.

          Don’t switch, and there is no need for that. Also GITHUB has a lot of unexpected downtimes.

        • foobar

          It depends on the maintainer, really. I also accept patches via email and fill out bugs in bugzilla based on them. I don’t mind how I get changes. However, this obviously only works for smaller modules.

  • gerardogc2378

    Evince PDF viewer is slow with mupdf, I’ll love mupdf render into Evince.