Introduction

This page details the rules that need to be followed when contributing code or documentation to the Ganeti project.

The first requirement is that either your and/or your employer needs to sign the individual or corporate contributor license agreement. Which one is needed depends on your particular case.

Only project members have commit rights to the repository. In order to become one, you need to do significant contributions first. Also, you need to have a Gmail account. Since the code.google.com project hosting site has the same rights for both wiki and code, we cannot give write rights only to the wiki, therefore all contributors must go through the same join process.

Code

All code must be sent to the ganeti-devel@googlegroups.com mailing list for review first. After you get a positive review, usually indicated by an LGTM response, you can commit your changes (if you have the appropriate rights) or a member of the project will do it for you.

Source tree organization

Development of new features for the next version (N.M) goes on in /trunk/ganeti. Bug fixing and backporting on existing versions goes on in branches, /branches/ganeti/ganeti-X.Y.

Every released tarball has to be made from a tag (/tags/ganeti/ganeti-A.B.C) using make distcheck.

A similar procedure goes for the operating system files which are stored under os-scripts. Releasing os scripts has to be done via the provided Makefile.

Wiki updates

Wikis can be updated by members directly. Non-members need to send their wanted changes to the mailing list, unfortunately.