[Netarchivesuite-devel] contribution to Netarchivesuite

[Søren Vejrup Carlsen]

Hi Lam.
I think you should just use the master branch as the starting point for your development.
Otherwise the merging procedure could be more complex.

Best regards
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Søren Vejrup Carlsen
svc at kb.dk
Det Kongelige Bibliotek
Afdelingen for Digital Pligtaflevering og Bevaring

________________________________
Fra: Netarchivesuite-devel [netarchivesuite-devel-bounces at ml.sbforge.org] på vegne af khanh-lam.mai at bnf.fr [khanh-lam.mai at bnf.fr]
Sendt: 13. juli 2016 14:47
Til: netarchivesuite-devel at ml.sbforge.org
Emne: [Netarchivesuite-devel] contribution to Netarchivesuite

Hello,

L would like to contribute to Netarchivesuite code on GitHub.
I have forked NAS code into my personnal GitHub account https://github.com/bnfklm/netarchivesuiteand I will work on this fork in order to submit a pull request to the main repository.

The main goal is to report all of these changes into the main repository :
https://github.com/netarchivesuite/netarchivesuite-svngit-migration/pull/5/files

I would like to know which is the best branch and/or tag to start my developpements, so it will be easier for you to integrate my future pull requests ?
Should I work directly on the master branch from the last commit, or should I start from the tag 5.1 (creating a new branch or not) ?

Best regards,

Khanh-Lam Mai
khanh-lam.mai at bnf.fr<mailto:khanh-lam.mai at bnf.fr>
Bibliothèque nationale de France<http://www.bnf.fr/>
________________________________

Expositions :
La franc-maçonnerie<http://www.bnf.fr/fr/evenements_et_culture/anx_expositions/f.franc_maconnerie.html> - jusqu'au 24 juillet 2016 - BnF - François-Mitterrand

Avant d'imprimer, pensez à l'environnement.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.sbforge.org/pipermail/netarchivesuite-devel/attachments/20160713/e4a91be3/attachment.html>