< CalligraRevision as of 17:56, 6 December 2010 by Cyrille (talk | contribs) (Created page with 'Git is a Distributed Version Control System (DVCS) == Why do we want to move to Git ? == * These kind of systems really help developers, it solves a lot of problems you can fin...')(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Git is a Distributed Version Control System (DVCS) Contents 1 Why do we want to move to Git ? 2 TODO 3 Done 4 After the meeting Why do we want to move to Git ? These kind of systems really help developers, it solves a lot of problems you can find with SVN like merges, and in general working in branches, and keep in contact with the work of others. On the #kde-git channel (irc) and on the scm-interest mailing list, a lot of problems has been exposed, and guys argue on them, trying to find solutions. For instance therereal problems because two things could be done and they have both good and bad points. The problem is : "Should we put every kde modules in one big repository or not". This problem doesn't appear with us because KOffice could easily use a repo. An other problem is with the translation guys, the choose solution is to keep a SVN repo for them. TODO how to move to GIT Converting (Thomas) pushing the converted repo (Thomas) Pointing scripty at the new place and hooks (Jean-Nicolas) Cleaning up in SVN Pointing EBN at the new place Pointing LXR at the new place Documentation (Boudewijn) You can commit with any available address, even if it is not yours. If a problem occur after a push, are we sure we know who makes a mistake, and for example can we find him by mail (Jean-Nicolas. Done Give ownership of KOffice project to kde-developers (Cyrille) Setting up project and repo (http://gitorious.org/koffice) straightening out the various group permission bits on Gitorious kde-developers has commit rights koffice-reviewers has reviewers rights kde-sysadmin has admin rights mail kde-scm-interest () Collecting users (Cyrille) After the meeting After a lot of discussions at the November meeting, we have found those problems: Convert SVN files to Git files. You can commit with any available address, even if it is not yours. If a problem occur after a push, are we sure we know who makes a mistake, and for example can we find him by mail. We need to be able to fetch and build KOffice easily. These points are not real problems anymore, it is just checks to make : A script already exists to convert SVN files to Git files : also known as the svn2git app. Jean-Nicolas (aka morice.net) will make a post commit hook script to solve the second problem. Mickael Mansen had already done a script which is able to make it : http://michael-jansen.biz/build-tool . This info is really a duplicate of techbase Zander 13:48, 23 December 2009 (PST) Retrieved from "https://community.kde.org/index.php?title=Calligra/Git&oldid=6595" Content is available under Creative Commons License SA 4.0 unless otherwise noted.