[Kde-scm-interest] meeting summary

[Ian Monroe]

On Thu, Dec 10, 2009 at 6:37 AM, Jeff Mitchell <mitchell at kde.org> wrote:
> On 12/9/2009 8:16 PM, Ian Monroe wrote:
>>> 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.
>
> There's no subgroups. And why exactly is joining a group to become a
> part of the merge and review process silly? We want every KDE developer
> to have commit access, but generally merge requests are better handled
> by the actual maintainers/developers of a particular component.
>
>> I don't even see the point of implementing this
>> temporary solution.
>
> Why is it temporary?

Because it sucks. You talk about "joining a group" as if its something
a user can do on their own. They can't.

>> The proper temporary solution is for people to do
>> email filtering
>
> Yes, you could have everyone set up email filters on all their clients
> -- or you could prevent all that completely unnecessary email traffic in
> the first place.
>
>> 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).
>
> What exactly is "ready to go"? When most of KDE switches to Gitorious,
> at which point everyone will get merge requests for all of KDE? *That*
> is silly.

We aren't going to switch to Gitorious with the current merge request
situation. Its a blocker. Still a blocker.

Ian