User Tools

Site Tools


developers:git:switch_to_git

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
developers:git:switch_to_git [2017/06/14 11:08] – [What should I do to jump in ?] Xavier Gonzedevelopers:git:switch_to_git [2017/06/14 11:42] (current) – [Introduction] Xavier Gonze
Line 1: Line 1:
-====== Switch from Bazaar to Git : the ABINIT developer path ======+====== ABINIT developer path to Git ======
  
 ===== Introduction ===== ===== Introduction =====
Line 7: Line 7:
  
 So, after consulting the most active developers of the ABINIT community, the decision has been taken in 2015 to switch to git. 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 ?  ===== ===== What should I do to jump in ?  =====
  
-It will take a few hours to learn about git and the future ABINIT development model.  +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 to 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. +  * First step : become familiarized with the basics of git. This means simplyread 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 is quite close to this flow (see later).+  * 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.   * 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]].   * Fourth step, read [[developers:git:specificities_git_abinit#standard_names_projects_branches|the specificities of the use of git for the ABINIT project]].
developers/git/switch_to_git.1497431321.txt.gz · Last modified: 2017/06/14 11:08 by Xavier Gonze