On 21 October 2011 08:12, Marcin Bukat <marcin.bukat_at_gmail.com> wrote:
> I generally find this policy sensible. This is how current git-svn
> users work anyway.

Right. The idea is to allow some more complex things to be done than
svn/git-svn allow, but not turn into a confusing mess right away. We
can always relax restrictions later if we feel it's warranted; it's
less useful to start with few restrictions and then try to add some
later, since history will already be a mess then :)

> Although I use git a bit I would very appreciate
> git commands examples for each point in this document.

Yes, I am intending to make an actual tutorial/example document, and
I'll insert appropriate examples into the guidelines at that point.
This was just to start discussion of what the policy should be, so
that people can talk about it while I work on other steps of the
migration.

> Other than this
> I think that maybe allowing push-merge should be one time permission
> to avoid situation that someone forget about having push-merge
> privilege. As I understand push-merge will not be so common anyway.

I don't think we can easily enforce this, but we could encourage it.
You are able to remove yourself from the group as easily as you can
add yourself, so if people want to remove themselves to protect
against mistakes that's no problem.

-- 
Torne Wuff
torne_at_wolfpuppy.org.uk