[Kde-scm-interest] On Amarok Switching to Git

[Thiago Macieira]

Johannes Sixt wrote:
>Thiago Macieira schrieb:
>> Ian Monroe wrote:
>>>>  * the unresolved issue of accountability
>>>
>>> This is the main issue I see. I hear there are solutions though?
>>
>> We have to see whether Git notes solves the problem.
>
>I still don't see a need for this. Just build a network of trust (or
>better, make use of it - because it already exists), with only one or
> two people who can push into "the repository" (that you named
> mainline.git), with their trusted lieutenants, etc, then accountability
> is no problem - you'll always know who pushed the commits. This should
> work particularly well with Amarok.

That won't work in KDE.

Very simple scenario: I build Amarok with Qt 4.5 and fixe an issue there. 
I would like to simply push to the repository, like I do with any other 
part of KDE. If I have to send a patch to someone (who may be away or may 
forget to apply it), I'll be less likely to make the modification.

Even if for Amarok we can have a temporary solution, this won't work for 
other KDE modules. Who will be allowed to push to kdelibs or kdebase? Who 
will make the decision on who those people will be? And how does one get 
added to this "special developers" group?

It's not a technical problem, it's a social one.

Sorry, I think everyone should have push rights. Now, whether we need 
accountability for that, it's a different thing. We can have the server 
publish the push log in a branch (very easy to do), or we can have a more 
complex solution.

-- 
  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/20090119/8b1396b9/attachment.sig