Re: Bug#133578: gdm bug #133578. Intend to NMU.
On Thu, Apr 22, 2004 at 02:39:33PM -0300, Daniel Ruoso wrote:
> Em Qui, 2004-04-22 às 06:33, Mathieu Roy escreveu:
> > Well, if a fix is not the cleanest possible but does not break
> > anything, why not applying it? You sure can claim that there is a
> > better to do the same thing but unless you are willing to do it you
> > should not forbid anybody to improve the package.
>
> This is exactly what I'm asking. The question is... I made the same
> question almost a year ago, and nothing happened. What should I do now?
> should I NMU? should i go to tech-ctte?
There is a disagreement among developers. Seems an obvious tech-ctte
thing to me if you're really interested.
6. Technical committee
6.1. Powers
The Technical Committee may:
[...]
2. Decide any technical matter where Developers' jurisdictions
overlap.
In cases where Developers need to implement compatible technical
policies or stances (for example, if they disagree about the
priorities of conflicting packages, or about ownership of a
command name, or about which package is responsible for a bug that
both maintainers agree is a bug, or about who should be the
maintainer for a package) the technical committee may decide the
matter.
[...]
4. Overrule a Developer (requires a 3:1 majority).
The Technical Committee may ask a Developer to take a particular
technical course of action even if the Developer does not wish to;
this requires a 3:1 majority. For example, the Committee may
determine that a complaint made by the submitter of a bug is
justified and that the submitter's proposed solution should be
implemented.
[...]
6.3. Procedure
[...]
5. No detailed design work.
The Technical Committee does not engage in design of new proposals
and policies. Such design work should be carried out by
individuals privately or together and discussed in ordinary
technical policy and design forums.
The Technical Committee restricts itself to choosing from or
adopting compromises between solutions and decisions which have
been proposed and reasonably thoroughly discussed elsewhere.
Individual members of the technical committee may of course
participate on their own behalf in any aspect of design and policy
work.
6. Technical Committee makes decisions only as last resort.
The Technical Committee does not make a technical decision until
efforts to resolve it via consensus have been tried and failed,
unless it has been asked to make a decision by the person or body
who would normally be responsible for it.
I've already made my views on this bug fairly clear, I think; but going
to the Technical Committee is *definitely* superior to getting into an
NMU-fight with the maintainer.
> But I just want to see this bug fixed. I repeat, this bug has a patch
> for more than a year.
The maintainer has repeated that he thinks the patch is wrong; therefore
I don't think it's particularly worthwhile to continue repeating that it
has had a patch. Developers are not obliged to apply any patch they
receive.
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: