[Kde-scm-interest] the permissions confusion

[Cornelius Schumacher]

On Saturday 12 December 2009 Oswald Buddenhagen wrote:
> On Sat, Dec 12, 2009 at 10:31:26AM +0100, Thomas Zander wrote:
> > Can we agree that;
> > a) we want all devs to be able to determine themselves which emails they
> > get?
> 
> yes. and we will wait until gitorious implements it properly.
> 
> > b) we want all devs to be able to commit to any kde-developers owned repo
> > and
> 
> mostly. and don't start denying the existence of the svn acl now ...

Wouldn't the special cases like the www part of SVN (are there others?) just 
be a separate repository not owned by kde-developers?

> > likewise, we want all devs to be able to comment on and otherwise process
> > merge requests ?
> 
> no.
> while commenting is allowed at any time (both technically and socially),
> approving lies in the hands of the maintainers of the respective
> subproject. it has never been different in kde. the technical limitation
> of access is a nice indicator of the maintainers' preference.

There are so many cases in the history of KDE where maintainers went away 
without notice, don't care about other people committing to their code, or 
like just informally telling people to go ahead without the need to log in to 
some system, that I would think any technical limitation would seriously 
hamper our workflow.

We should work on the policies, on educating people about how to work with git 
(especially the workflow parts), on maintaining the culture of mutual respect. 
Then we don't need these kind of new technical limitations and can spend our 
time on more central and important stuff.

-- 
Cornelius Schumacher <schumacher at kde.org>