Hello, Ganeti community! As discussed at GanetiCon last year, we are happy to announce that Ganeti’s GitHub repo [1] is now the authoritative repository for Ganeti. With this change, we are also adapting the development process to use pull requests [2] instead of mailing list patches. We believe that these changes are going to make it easier to contribute to the Ganeti project while also encouraging a better review process. The new contribution process is described in the CONTRIBUTING.md file, which is currently being reviewed (or meta-reviewed, if you like) on [3].
This means that from now on all the patches should be sent to review via GitHub instead. We are not going to migrate the patches that are pending in the ganeti-devel mailing list, so we ask the contributors to migrate them to GitHub if needed. New issues should also be filed on our GitHub repo instead of code.google.com. We are working closely with the code.google.com team to migrate the existing issues to GitHub as well. Now that we are migrating to GitHub, we also plan to use other tools of its ecosystem to improve the maintainability of the project. We have a few working already: - Travis-CI [4] runs the tests on every commit and every Pull Request. This helps us to identify bugs earlier. - The Google CLA bot identifies the contributors that need to sign the Contributors License Agreement, notifying both the contributor and the reviewer in case any action is required. We understand that parts of our documentation might still point to the old repo. If you find such an error, please feel free to open a pull request. You can even do so using the GitHub web editor! Cheers! Rafael Marinheiro [1]: https://github.com/ganeti/ganeti [2]: https://help.github.com/articles/about-pull-requests/ [3]: https://github.com/ganeti/ganeti/pull/39 [4]: https://travis-ci.org/ganeti/ganeti
