[Kde-scm-interest] meeting summary

[Ian Monroe]

2009/12/9 Jeff Mitchell <mitchell at kde.org>:
> On 12/9/2009 6:48 PM, Lydia Pintscher wrote:
>> On Thu, Dec 10, 2009 at 00:36, Oswald Buddenhagen <ossi at kde.org> wrote:
>>> On Thu, Dec 10, 2009 at 12:14:17AM +0100, Lydia Pintscher wrote:
>>>> Once all of KDE is on gitorious it will be extremely hard to maintain
>>>> the policy of only having these $-developer groups for merge requests
>>>> and nothing else. And the more of those groups we create with every
>>>> project that moves the bigger the incentive will be to not use
>>>> +kde-developers but the smaller group for commit rights.
>>>>
>>> why do you bring +kde-developers in? it is *exactly* the equivalent of
>>> having an svn account.
>>
>> Well yes. That is exactly my point. We only want +kde-developers to
>> commit to "our" code and we want them to have access to all of it, not
>> only a part.
>> With a lot of those small project groups we give the opportunity to
>> give only a small group commit access to a certain part of our code.
>
> I think you're misunderstanding.
>
> The purpose of the small project groups is *only* for review
> capabilities -- i.e. merge requests. So essentially, you join the groups
> to opt-in to the merge request for that group's repositories (and have
> the ability to change the status of the merge requests). That's *all*.
>
> All repositories will have commit access by, and *only* by +kde-developers.
>
> And all repositories will have admin access by, and *only* by,
> +kde-sysadmin. (Should it be renamed +kde-sysadmins? Dunno.)

The permissions and subgroups as a way to decide if you want emails or
not is silly. I don't even see the point of implementing this
temporary solution. The proper temporary solution is for people to do
email filtering or to drop out of +kde-developers until we're ready to
go (we're going to have some system to do mass-adds for sure anyways).

Its just stupid for admins to decide who gets emails. Plus, isn't it
impossible to work with merge requests if you don't have the merge
request bit? Fail. And fail.

So if it wasn't for that last bit we could sign up a mailing list as a
gitorious user and it would be a find temporary solution. But given
that you can't set the status of a merge request, and maybe can't even
comment on a merge request, without a merge request bit, that
obviously doesn't work.

Ian