Re: Bug#436093: Please decide on the "ownership" of the developers reference
On Sun, 5 Aug 2007 17:24:02 +0100, Ian Jackson <ian@davenant.greenend.org.uk> said:
> So as I understand it:
> * Andreas argues that he became the lead/sole maintainer with his
> commit of 2005-02-02 and that he is therefore the current
> maintainer.
> * Raphael argues that that commit isn't definitive and that we should
> regard Raphael and Andreas as co-maintainers.
> ?
> This is relevant for deciding what the status quo is but not for any
> other purpose AIUI. The TC will probably tend towards the status quo
> by default, but it's certainly not definitive.
> I'd like to ask Andreas and Raphael how they each propose to handle
> the maintainership of this package in future.
> It seems clear to me that Andreas wants to be the primary maintainer
> and to reserve the authority to make changes, grant commit access,
> etc. Andreas: do you have any assistants/colleagues/etc. who would be
> willing to help you with that so that you don't become a bottleneck ?
> Raphael says he wants a team. Raphael: what team did you have in mind
> ? Who will help you ?
If I recall correctly, the package started out as a team
maintained one. I seem to recall having commit access at some point,
though I certainly did not make use of it. So perhaps the original
team could be candidates for the new team (provided, of course, they
are interested -- though it is possible that some, like me, are no
longer interested in the package)
> I'd also like each of you to answer: if the TC rules in your favour,
> how do you plan to deal with your opponent in this dispute ?
> Another possible way for the TC to decide on this kind of question is
> to ask the developers to each prepare a package and then for the TC to
> choose between them. Do you think that would be appropriate in this
> case ? Would it be a fair fight ? How long would you need ?
manoj
--
Intolerance is the last defense of the insecure.
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: