Martin Vidner write: > Why > --- > > Git is better. Git enables fearless hacking, power to the people, > easy merging. Being distributed, Git enables you to commit often to > your local repository and only publish the changes once you are > satisfied with the code. The tool supports you even if you do not > have write access to the master repo (yet), which lowers the barrier > to contribution. > > http://whygitisbetterthanx.com/ > > How > --- > > 1) > - I convert the SVN repo locally > - once it looks usable enough, let people clone it for more testing > > 2) > - make sure everyone feels comfortable with Git; educate and help > the newbies > Hi, I think that move to git is a great step forward. > 3) > - work out the remaining conversion issues > - Where: select a hosting service (gitorious, github, elsewhere?)
I think it is not important as git allow to have it everywhere. What is just needed is to select authoritative source. > - adapt devtools Good idea, but don't reinvent wheel. And if you find something useful try to push it upstream ( like tag and push) > - decide how to split it (platform - modules - libyui?) I think in ideal case we should have everything separated and for dependencies use git submodules - http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html > - consider the commit/push policies, and their enforcement via Git > hooks; for example: > - git-flow > - whitespace rules > - .changes ordering Absolutely agree. Git hooks is great tool and we should benefit from it. > > Who > --- > > I want to do it, but I could use a helping hand, both for the > details and making sure the project keeps moving. I recommend set list of tasks, so we can easier pick something if anyone have time. Pepa > > When > ---- > > If maintenance work permits, rather soon. Unlike the rest of the > Amaranth project, this can go forward before we decide the language > and architecture. > > -- Josef Reidinger Appliance Toolkit team maintainer of perl-Bootloader, yast2-bootloader and parts of webyast and SLMS -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
