Heptapod and Mercurial#

We use Mercurial instead of Git. I (Pierre Augier) think that modern Mercurial with Heptapod can be a good technical choice for this project; in addition, using Mercurial for this project would tend to increase the diversity in terms of versioning tools which is a good thing considering the current situation of Git monopoly.

However, since most potential developers are used to Git, it represents a technical barrier for contribution. We try to make this barrier as small as possible by providing good documentation on contributing with Heptapod and Mercurial.

Important

  • Unless you really know what you’re doing, install and setup Mercurial as described here: Install and setup Mercurial.

  • Unless you really know what you’re doing, before contributing, read at least this page and the first sections of Mercurial workflow.

Get the developer or maintainer role#

No need to fork the repositories to contribute! The first step instead is to log in on https://foss.heptapod.net (one can use a GitHub or GitLab account) and send a message in this issue to get the “developer” or “maintainer” role for https://foss.heptapod.net/py-edu-fr.

Contribute via the web interface#

Once you became “developer” or “maintainer” of the project, you can modify a file via the web interface. Click on edit in the Heptapod interface showing a file, edit the file and commit the changes in a new GitLab branch.

Important

Since the GitLab branch HAS to corresponds to a Mercurial [topic], you HAVE to choose a name in the form topic/default/my-nice-topic-name (replace my-nice-topic-name with something appropriate).

Contribute with local development using Mercurial#

Contribution with a local repository is explained in details in Mercurial workflow but you first need to install and setup Mercurial. For that, don’t try to guess and just follow Install and setup Mercurial.