[Kde-scm-interest] Distributed model VS accountability

[Thiago Macieira]

Em Friday 23 November 2007 16:40:43 Johannes Sixt escreveu:
> At a higher level, trust must be implemented such that each person can
> change (basically) only his own repository. For this reason, it is good
> that in your earlier proposal access rights to certain repositories were
> very limited. BD and lieutenants will only pull from such restricted
> repositories.

I understand that.

But the question I am asking is: how can we have accountability in a 
repository where everyone in the project can push to the repository?

I simply do not see a way of KDE having restricted repositories, at least not 
if we want to have a smooth transition any time soon. The social trust 
network model will not work in KDE since we've been for 10 years allowing 
anyone to commit anywhere.

But maybe I have the answer: the kde-commits mailing list. For every commit 
(or any push), we'll have an email sent. That contains the identity of the 
person who did the commit/push. And the list is archived for anyone to see. 
If later we need to determine who added some code, all we need to do is find 
the email that added such a commit.

It's just too bad that the accountability is not built-in to the VCS tool in a 
model such as ours.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20071123/6af60a0c/attachment.pgp