I would like to add a few points to this discussion for public record. This is not just about a personal conflict between Sven and me, but between Sven and several core members of the d-i team. There are two other members of the team that have Sven in their killfile and on /ignore on IRC.
As Sven over the last months has also succeeded in alienating me, this
makes working with Sven as a member of the d-i team impossible. As Sven
has also repeatedly shown hostility towards the d-i team and several of
it's members I feel justified in revoking his commit access.
After all, how can you have someone committing to your projects repository
if you cannot communicate with them over policy and the way to resolve
technical issues?
The root of the conflicts are documented elsewhere (I sent a summary to
both the DPL and his SIC during the mediation) and I don't really want to
repeat them here.
There have also been similar issues between Sven and several members of
the kernel team over the past year with pretty violent discussions both
on the mailing lists and IRC, even leading to a request for expulsion of
Sven from Debian as a whole by one of the (by now former) members of the
kernel team.
As to Sven's request to remove some of his contributions from the d-i
repository, IMO there is absolutely no basis for that:
- any contributions to open source (sub)projects become part of that
project
- the relevant components are maintained by the d-i team with Sven as
main developer and Uploader, but the Maintainer is [EMAIL PROTECTED],
although even that is IMO irrelevant
- Sven still has read access to the repository, so if he wants he can
check out and fork the components which means that his rights as a
copyright holder are in no way violated
- as the components are an integral part of the installer, forking them
only makes sense if the whole installer is forked
- the d-i team has at least some say over _any_ udebs uploaded into the
Debian archives as randomly uploaded udebs can interfere with the
working of the installer
- this implies that Sven should not be allowed to hijack the components
A last point is that I'm somewhat surprised that Sven should see removal
of SVN access as unacceptable, as he did exactly the same thing to a
member of the kernel team some time ago after a conflict that, though it
had a technical base, was also mostly personal. The conflict in that case
was only between two individuals about a single bug report instead of
between most core members of the team and an individual. In that case the
_team_ decided to revert the revocation of the commit access shortly
afterwards.
From the #d-kernel IRC logs [1]:
00:19 < jonas> hmm - can someone please grant me write access to SVN,
please - unless of course it is generally agreed that I should no longer
have access
[...]
00:55 < azeem> an admin could try Admin->Project History from the alioth
project page
00:55 < azeem> member additions seem to get logged there
00:55 < azeem> (never removed members from any of my projects)
00:56 < tbm> ah, yeah
00:56 < maks> and what does it say
00:56 < tbm> removed user: js 2006-03-07 18:59 by luther
00:56 < azeem> blah
00:57 < tbm> nobody else got removed (i.e. no clean up took place)
00:58 < dannf> tbm: oh, good catch
00:58 < dannf> i'll just e-mail svenl then
00:58 < tbm> jonas: added back "js"
00:59 < dannf> hrm.. i wonder if its even worth talking to svenl about
this
[1] A more complete log of the discussion about that revocation is
available from:
http://lists.debian.org/debian-boot/2006/05/msg00324.html
pgpyjK4lCZTWX.pgp
Description: PGP signature
