Tips for ABINIT users and developers

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== ABINIT developer path to Git ======

===== Introduction =====

For a long time, ABINIT has relied on the [[https://en.wikipedia.org/wiki/GNU_Bazaar|"Bazaar"]]  Version Control System (VCS). However, this software project is apparently not maintained anymore.
By contrast, [[https://git-scm.com/|git]] shows advantages with respect to other VCS, in particular, an impressive speed, thanks to its commit storage model. See [[https://en.wikipedia.org/wiki/Git_%28software%29|Wikipedia]]: "The Eclipse Foundation reported <...> that as of May 2014, Git is now the most widely used source code management tool, with 42.9% of professional software developers reporting that they use Git as their primary source control system”.

So, after consulting the most active developers of the ABINIT community, the decision has been taken in 2015 to switch to git.

===== What should I do to jump in ?  =====

It will take a few hours to learn git and the corresponding ABINIT development model. 
  * First step : become familiarized with the basics of git. This means simply: read chapters 1 to 3 of the "Reference Manual" of git, that is available at [[https://git-scm.com/doc]]. Install a version of git on your local development computer, and play a bit with it. This will likely take two hours.
  * Second step : become familiarized with the so-called [[http://nvie.com/posts/a-successful-git-branching-model|gitflow]]. Indeed, the working mode that is adopted for ABINIT is quite close to this flow (see later).
  * Third step : spend some time to get familiarized with gitlab. in particular, please, log in on   page [[https://gitlab.abinit.org]]. In order to do this, you have first to arrange an access with Jean-Michel Beuken (jean-michel.beuken@uclouvain.be) : send him an e-mail and he will create for you an SSH access.
  * Fourth step, read [[developers:git:specificities_git_abinit#standard_names_projects_branches|the specificities of the use of git for the ABINIT project]].
  * Fifth step : you might have a look at the [[maintainers:blueprints:gitlab_specs|blueprint from Yann, entitled "Gitlab specifications"]].
  * Sixth step : practice !