Bug#436093: Please decide on the "ownership" of the developers reference
On Sun, Aug 05, 2007, Andreas Barth wrote:
> I started to take care of the developers reference in September 2004,
> and have committed changes and uploaded the package regularly since
> then, please see
> http://cvs.debian.org/ddp/manuals.sgml/developers-reference/debian/changelog?rev=1.251&root=debian-doc&view=log
>
> I asked other people to not commit directly to the cvs, but to send
> patches in to allow other people to review their proposal, so that we
> end in high quality.
>
> However, Raphael Hertzog decided to ignore this request, and continues
> to commit changes directly, and now even hijacked the package by adding
> himself as uploader without even considering to speak with me beforehand.
>
> So I want to have a decision based on 6.1.2 of the constitution whether
> I'm currently the lead maintainer of the developers reference or not.
Could we try to first exhaust other means of consensus reaching
before summoning the tech-ctte with this?
You know I am uncomfortable with the concept of package ownership,
and the devref is no exception. I therefore suggest that you split the
two issues at hands here, which are:
1. Raphaël committing changes directly to the CVS
2. Raphaël adding himself to the Uploaders: field
About [1], directly committing changes seems the most reasonable way
to manage such a project. Everything can be discussed and reverted as
if it was first sent to a mailing-list. The difference is dynamism: if
one assumes that the average contribution is positive, the repository
is constantly and sooner in a better state. You always "end" in high
quality anyway, since it is the uploads that determine the state of the
devref, not the repository.
If there are issues with the quality of a user's contribution, then
this is a problem for the whole team and should be discussed within the
team. It is not a problem of leadership IMHO.
As for Raphaël adding himself to the Uploaders: field, I have no
particular opinion about it. I suggest discussing it within the team,
too, and either reverting the change, or reaching a common agreement
about upload rules (which I would obviously prefer).
Regards,
--
Sam.
Reply to: