[Kde-scm-interest] meeting summary

[Lydia Pintscher]

On Thu, Dec 10, 2009 at 00:03, Oswald Buddenhagen <ossi at kde.org> wrote:
> so i (with jeff's help) set up the system as intended (by johan, i dare
> to claim) and everyone should be happy until something *yet* better is
> added to gitorious. the setup is as follows:
>
> for starters, every project has its own repository (or several of them,
> but let's talk only about the "central" one for now). the definition of
> "project" is still up for debate (see the "splitting up" discussion). as
> of now, i know of exactly one project: amarok.
>
> there are three kde-related groups on gitorious now:
> - kde-sysadmin: well, our beloved admins, as ever.
>  - this group is self-administering
> - kde-developers: this is equivalent with having an svn account.
>  - this group is administered by kde-sysadmin
> - <project>-developers: members of the project, however defined.
>  - these groups are self-administering
>  - the only such group is currently amarok-developers
>
> now, every project can assign three roles to whichever users and user
> groups it wants: committer (push access), reviewer (essentially, getting
> notifications about merge requests) and admin. the assignments for kde's
> setup follow from that naturally: every kde project gives
> - kde-sysadmin the admin role
>  - whether the projects want to give it to themselves as well is still
>    up for debate
> - kde-developers the commit role
> - <project>-developers the reviewer role
>
> so everyone who wants to get notifications about merge requests for a
> particular project has to request from the project's group to be added
> to it. given that almost nobody will be interested in more than 2-3
> projects, this is quite manageable, no matter how many kde projects move
> to gitorious.
> still, the next step would be adding the possibility for everyone to
> configure himself which notifications for which projects he wants to get
> - that's really nothing which *should* require action from anyone but
> the interested person itself. that's the stuff johan is expected to
> deliver at some point, but it is not critical for anything.

Just for the record: This was started without discussion and then
continued despite protest on IRC.
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.
-> I'm not too happy about all this.


Cheers
Lydia

-- 
Lydia Pintscher
Amarok community manager
kde.org - amarok.kde.org - kubuntu.org
claimid.com/nightrose