Ian Jackson writes:
> This is especially the case since none of the other possible
> candidates for how to set this distribution-wide policy are useable:
> the Policy editors have decided that Policy should lag implementation
> rather than lead it; debian-devel didn't work; and there is no other
> forum or body with sufficient breadth.

I was asked for a discussion on -devel@ by the d-i maintainers before I
filed the bug report to enable this feature.  It is mentioned in the
initial bug report too[1].

  [1] https://bugs.debian.org/839046#5

While you claimed[2] there were negative responses in that particular
thread, there weren't any as far as I could see[3].  Sadly you didn't
bother replying.

  [2] https://bugs.debian.org/839046#94
  [3] https://bugs.debian.org/839046#112

You didn't provide any concrete examples of what would be broken back
then, even when explicitly asked[4].

  [4] https://bugs.debian.org/839046#99

The same pattern seems to continue as you claimed that the "design is
broken" in the request to the ctte[5], but do not want to provide
reasoning why.  Or make claims that there wasn't enough consultation
(even though there was so much discussion that LWN wrote at least one
article about the discussion on -evel@); as usual you do not follow-up
on requests to clarify any of this.

  [5] https://bugs.debian.org/914897#208

(Not that having consensus would mean anything given how you handle that
in [6]...)

  [6] https://bugs.debian.org/850967#42

I'm sorry, but I feel that you are not interested in discussions around
technical problems, but instead (once again) fight for some other reason
(just like in the DUNE bug IMHO)...  The (solvable and minor) technical
problem that was reported half a year after the default was switched was
just a convenient starting point to escalate the issue; it isn't even
mentioned any more: instead you now switch to "social costs".

Here I find it unfair to pressure people into reverting the change /now/
as the freeze comes closer as such reasons would have applied the years
before November as well, and certainly since the default was switched
again in June last year.

Ansgar

Reply via email to