--- Comment #8 from Nemo <> ---
I already said all I have to say about this topic at bug 52442 comment 4 and
below, just a point:

(In reply to comment #7)
> [...] And all this for no good reason,
> since
> at the end the maintainers developing the component are the ones deciding
> what
> goes in it and when. [...]

This is a tracking bug (which also means that usually its priority/severity
fields don't mean much) and part of the rationale provided was:

(In reply to comment #4)
> I believe there's some awful configuration
> variable that needs to be killed in order to resolve this bug. I'll try to
> investigate later.

Configuration matters are not under exclusive control of the extensions'
maintainers. If a WMF/site policy happened to say that a certain configuration
is mandatory, it wouldn't matter much what the authors of the code think about
it and it it takes no intervention on their end to make it happen.

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to