Just a note: a few mails ago, they were a mention about granting commit
rights. Actually I would suggest a slightly different approach. We don't
need commit rights, at least not directly. If the SIS project goes ahead
with a Git repository, then we only need to clone that Git repository on
our own public server. We can commit whatever we want on that server and
propose that to the SIS project. If it looks good, someone with commit
right on Apache server can "pull" from our server and "push" to the
Apache one. If the proposal doesn't look good, then we can delete our
clone and re-clone with an alternative proposal. Commit right would be
granted on the Apache server only if the SIS maintainer feel tired to
"pull" and "push" :-)
(actually, in the context of Git repository this is not "commit" rights
- everyone have commit rights on his own clone - but "push" rights)
I'm proposing this approach because I think it would be nice if the SIS
maintainer takes his time regarding commit right grants. This apply to
ourselves like anyone else.
Martin
