[Kde-scm-interest] the permissions confusion

[Jeff Mitchell]

On 12/12/2009 1:48 PM, Oswald Buddenhagen wrote:
> On Sat, Dec 12, 2009 at 07:12:13PM +0100, Thomas Zander wrote:
>> On Saturday 12. December 2009 19.02.14 Oswald Buddenhagen wrote:
>>> Whoopsie! Looks like this project has chosen to restrict commit access.
>>>
>> Then it would not be a kde-developers project.
>>
> well, actually, most likely it would. the hook would allow
> foo-developers through without a question, while kde-developers would
> get the blurb. after all, the restricted group still needs the ability
> to force a push, and kde-developers is just perfect for that.

But why? I honestly don't understand it. Why, if the fix needs to go in,
couldn't the kde-developer person simply submit a merge request to
foo-developers? Isn't that kind of the point?

You mentioned not wanting to have an "impenetrable lock" -- but AFAIK,
we already have that (assuming the normal repo maintainers can't be
found/have disappeared) -- in the form of a request to kde-sysadmin
asking for temporary push access to a repository to commit said urgent
patch.

To me it seems like the situation you are describing is something we
already have a system for dealing with...what am I missing here?

--Jeff

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20091212/117a3110/attachment.sig