[Kde-scm-interest] SVN closed for commits and Basic Git Groundrules

Thomas Zander zander at kde.org
Tue Jul 21 13:25:01 CEST 2009


On Tuesday 21 July 2009 13:24:18 Riccardo Iaconelli wrote:
> Hmm... I'm a bit scared of using this approach, where you don't share the
> work directly in the mainline repo, but instead work on your own clones. I
> mean, while being very git-ish, aren't we losing here the social model that
> we all love so much about KDE, and that everyone fears to loose when
> switching away from SVN?

This is a misconception; where the doc mentions private clone its entirely 
correct terminology but confusing.
Let me explain with an example workflow.

* I clone amarok on gitorious.
* I download from my own clone
* I start writing my new feature and push it to my own clone on gitorious
Then I talk on IRC to get feedback for this and point others to this public 
gitorius project.
* Bart downloads my clone and starts hacking on it. 
* I grant him write rights in my 'private' clone and he pushes to it.

After a couple of weeks and maybe more committers on this little project we 
merge it into mainline via a normal local git command and I personally can 
push it to mainline in the master branch.

-- 
Thomas Zander


More information about the Amarok-devel mailing list