[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [Kde-pim] Problems with infrastructure
From:       Nicolás_Alvarez <nicolas.alvarez () gmail ! com>
Date:       2014-12-20 1:24:42
Message-ID: CANPC-tuX+pttARJpUK28rPa9FkvwO9gd1+_VB_-zOjGPcenc7A () mail ! gmail ! com
[Download RAW message or body]

2014-12-19 22:08 GMT-03:00 Kevin Kofler <kevin.kofler@chello.at>:
> Sebastian Kügler wrote:
>> On Tuesday, December 16, 2014 16:12:05 Ben Cooksley wrote:
>>> For deleting branches, I think we can allow this - given some
>>> protection for certain branches (like the KDE/* branches for
>>> instance). Note that courtesy of the backup functionality in our
>>> hooks, no branch or tag is ever truly deleted from a repository on
>>> git.kde.org. I don't know how easy it would be to alter this behaviour
>>> based on the account name of the developer.
>>
>> What I would find helpful, concretely:
>> - being allowed to delete "own" branches
>> - force push for "own" branches since I could delete and recreate a
>> branch, I
>>   may just as well directly be allowed to force-push, this makes it a bit
>>   easier to keep branches as clean as possible
>>
>> where "own" means "branchname starts with username/", for example
>> "sebas/hacking".
>
> Why can't we just allow delete and force-push of all branches for all KDE
> contributors? Hasn't it always been KDE policy that contributors are trusted
> not to do stupid things? Why do we need to enforce this through technical
> restrictions?

The way the hooks work now, I think we should allow delete and not
force-push, because deleting a branch stores a backup ref.

-- 
Nicolás
[prev in list] [next in list] [prev in thread] [next in thread]