[Kde-scm-interest] meeting summary

[Oswald Buddenhagen]

moin,

"quick" update.

On Wed, Dec 09, 2009 at 12:36:45PM -0800, Chani Armitage wrote:
> merge request emails: eean says we could actually use commit-filter
> for this if we wanted. he's the maintainer... but he doesn't want to
> step on johan's toes here.
>
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.

> svn2git import rules: a bit of confusion over whether morice is going
> to be working on this (but he was doing hook stuff this week anyways).
> tz says sho_ might be willing to help. morice will try it.
> 
it's still beyond me what the deal about that is ... did anybody
actually *try* to fix the script to follow project moves and branches in
svn instead of doing everything by hand? did anyone try git-svn with
proper options as an alternative (just to see whether it's wouldn't be a
better start at this point)?

> push log: we still don't have a volunteer for this. :(
> 
as far as i'm concerned, this is a huuuuge ... non-issue:
the post-receive script should send the notification mails in the name
of the person who did the push, as was ever the case in kde (well, since
i (iirc) implemented it, actually, which is longer ago than most here
can remember). that way, the mailing list archives become the push log
and we never have to worry about it.
there are two minor obstacles:
- the post-receive script needs to get that information from its caller,
  however that is done in the end (johan, please answer my last mails to
  this list). technically, it is simple.
- according to johan, gitorious needs to have the right to give the
  pusher's identity to the post-receive hook. no biggie: by requesting
  being added to the kde-developers group you agree to kde's "terms of
  service" to disclose your real name and a working email address. i'm
  sure figuring out a process to get that from kde-sysadmin to
  legal at gitorious.org in a legally binding way is nothing which is
  particularly hard.

> pre-receive hooks: no volunteer either, but the only hook listed is
> "license checker"
> 
well, i'll do that, too, if nobody else screams. don't expect anything
before mid-january, though.