Re: Proposal - Remove requirement that emails be wrapped at 80 characters
Hallo! Du (Soren Stoutner) hast geschrieben:
<Listmaster-Hat status=on>
>1. I assume the listmasters are subscribed to debian-devel, so when I posted the original
>discussion there I considered that I was including them.
no, i'm not subscribed to that, you can't assume that, and it is not a
requirement for a DD, and not for a listmaster. (should we read every list we
run? That would be a fulltime job.)
I also think that the discussion is wrongly placed in d-devel and should go to
d-project.
A side-thought: could this change cause problems for people that rely on a
screenreader?
>2. As described in the text that you snipped, this issue is bigger than just the lists. For
>example, it also applies to the BTS. As such, I don’t think the listmasters are the correct
>place to address it for the entire Debian project. I consider the discussion on debian-devel
>to have be the correct initial place, followed by this GR when it became apparent that
>some people were strongly opposed to the proposal and a consensus decision was not
>possible.
Yes, we as the people that run those systems have to check if our tooling
copes correctly with the removal of those suggestions. That involves the BTS,
our archiving software and our filtering software (which contains a scoring
mechanism based on content and formatting)
<Listmaster-Hat status=off>
I'm personally deeply unsympathetic to your proposal.
Your Mails look horrible and are sometimes close to unreadable in my Mailsetup
(mutt in a xterm, I will not discuss this, just a feedback). I usually don't
have the time and the energy to invest in such mails (reformatting so that
quoting/commenting is possible).
Your proposal (and some of your mails with HTML and things) and your approach
feels to me like you are not willing to accept the "rules" that we have given
ourselves.
It is fine to question and also change those, but yet they haven't been
changed, so they should be honored.
It just feels lazy, that you are not willing to invest in producing
'compliant' mails, but instead try to push a change upon the whole community.
A change that you haven't asked the responsible teams for, and that in the
discussion didn't reach some kind of positive leaning consensus. Now it eats
up many man-hours of Developer-time that really could be invested better.
Cord
Reply to: