Forum: >>> Magnum BBS <<<

Subject: Proposal - Remove requirement that emails be wrapped at 80 cha

From Soren Stoutner@21:1/5 to Debian Vote on Sat Mar 15 11:19:45 2025

This is a multi-part message in MIME format.

--nextPart2776320.hsi8hcfAM6
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"

----- BACKGROUND STARTS -----

The text of the current mailing list code of conduct states:

"Wrap your lines at 80 characters or less for ordinary discussion. Lines longer than 80 characters are acceptable for computer-generated output (e.g., ls -l)."

https://www.debian.org/MailingLists/

There were historical reasons for requiring people to wrap outgoing emails relating to some older MUAs (Mail User Agents also known as email clients) not having the ability to wrap the text of incoming emails and some older screens being limited to an 80 character width.

These historical reasons no longer apply, as every MUA of which I am aware now has the ability to wrap incoming lines.

From a technical perspective, I believe having the sending MUA hard-wrap lines at a particular column is the incorrect approach because there is no single line

limit that works well on all receiving devices. Many cell phones have a display
width of 40 columns or less, while modern desktops have a display width of far more than 80 columns. The only system that knows how big the viewport is where the mail will be displayed is the receiving MUA, so that is where decisions about line wrapping should be made.

Having hard line wraps also causes problem with quoted text, where after multiple replies text will start to break in places that can make some of the quoted text appear to not be quoted. I am sure that everyone on the mailing lists has seen emails exhibiting that problem.

There has is some discussion about this issue on debian-devel beginning at:

https://lists.debian.org/debian-devel/2025/02/msg00302.html

In that discussion, several people have suggested the use of format=flowed as a solution. Format=flowed is an RFC that proposes a system for hard-wrapping text
but including special codes that allow a receiving MUA to unwrap them and then rewrap them to the current viewport.

https://www.ietf.org/rfc/rfc2646.txt

Format=flowed never gained wide adoption by the majority of MUAs. Although I don't have any objections to anyone using it, I don't see it as an appropriate requirement for communication on the mailing lists or a general solution to the problems of hard-wrapped text because it doesn't have wide enough implementation.

----- BACKGROUND ENDS -----

----- GENERAL RESOLUTION STARTS -----

It is no longer required that emails sent to or received from official Debian infrastructure like the mailing lists or the BTS (Bug Tracking System) be wrapped at any particular column, although users and automated systems may choose to wrap emails at any column they prefer. Using format=flowed is not required for emails, but users and automated systems may do so if they like.

The maintainers of the mailing list code of conduct shall update the text relating to the wrapping of emails at 80 characters to be the following:

"There is no expectation that emails sent to the mailing lists are wrapped by the sender at a particular column, but those sending emails may wrap them if they choose."

In the future, they may modify the above text of the code of conduct to meet changing circumstances as long as it does not violate the spirit of this General
Resolution.

----- GENERAL RESOLUTION ENDS -----

--
Soren Stoutner
[email protected]

--nextPart2776320.hsi8hcfAM6
Content-Transfer-Encoding: 7Bit
Content-Type: text/html; charset="utf-8"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>----- BACKGROUND STARTS -----
 The text of the current mailing list code of conduct states:
 "Wrap your lines at 80 characters or less for ordinary discussion. Lines longer
than 80 characters are acceptable for computer-generated output (e.g., ls -l)."
 https://www.debian.org/MailingLists/
 There were historical reasons for requiring people to wrap outgoing emails
relating to some older MUAs (Mail User Agents also known as email clients) not
having the ability to wrap the text of incoming emails and some older screens
being limited to an 80 character width.
 These historical reasons no longer apply, as every MUA of which I am aware now
has the ability to wrap incoming lines.
 From a technical perspective, I believe having the sending MUA hard-wrap lines
at a particular column is the incorrect approach because there is no single line
limit that works well on all receiving devices.  Many cell phones have a display
width of 40 columns or less, while modern desktops have a display width of far
more than 80 columns.  The only system that knows how big the viewport is where
the mail will be displayed is the receiving MUA, so that is where decisions
about line wrapping should be made.
 Having hard line wraps also causes problem with quoted text, where after
multiple replies text will start to break in places that can make some of the
quoted text appear to not be quoted.  I am sure that everyone on the mailing
lists has seen emails exhibiting that problem.
 There has is some discussion about this issue on debian-devel beginning at:
 https://lists.debian.org/debian-devel/2025/02/msg00302.html
 In that discussion, several people have suggested the use of format=flowed as a
solution.  Format=flowed is an RFC that proposes a system for hard-wrapping text
but including special codes that allow a receiving MUA to unwrap them and then
rewrap them to the current viewport.
 https://www.ietf.org/rfc/rfc2646.txt
 Format=flowed never gained wide adoption by the majority of MUAs.  Although I
don't have any objections to anyone using it, I don't see it as an appropriate
requirement for communication on the mailing lists or a general solution to the
problems of hard-wrapped text because it doesn't have wide enough
implementation.
 ----- BACKGROUND ENDS -----
 ----- GENERAL RESOLUTION STARTS -----
 It is no longer required that emails sent to or received from official Debian
infrastructure like the mailing lists or the BTS (Bug Tracking System) be
wrapped at any particular column, although users and automated systems may
choose to wrap emails at any column they prefer.  Using format=flowed is not
required for emails, but users and automated systems may do so if they like.
 The maintainers of the mailing list code of conduct shall update the text
relating to the wrapping of emails at 80 characters to be the following:
 "There is no expectation that emails sent to the mailing lists are wrapped by
the sender at a particular column, but those sending emails may wrap them if
they choose."
 In the future, they may modify the above text of the code of conduct to meet
changing circumstances as long as it does not violate the spirit of this General
Resolution.
 ----- GENERAL RESOLUTION ENDS -----
 -- 
Soren Stoutner
[email protected]
</body>
</html>
--nextPart2776320.hsi8hcfAM6--

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmfVxMEACgkQwufLJ66w tgMV9BAAh4C9bPMM6mwEdjhmoRWBo9BPCAaa4GnwrVdObxwLqrExq9LCvyao2b4G knCVgDazgtSVZ/9x4Y4JOeyjJQp+8hDHBwjn09SYgWdctWIHY7zgtwkZk18KNNxc nV7Nkv6n4otHjtM2Ql9+1TvPzRHft9PyA3wG/kxBLXlx5DVAqO3MPJtdgq2It4Qv Ol5Oc4QLmKtwDOtRXdGlFAg+n4hozY+uFcGZ241yEmyykoThkgqUiPGzL0jt2fbb SKhYiRQqA0RbBq+Q9bLHaDCEdX8y9U1A8XOI0STRfPNhj/iowLdqNq6+DELi/9IK 5huh5mlMXnTfLsK5R3gPKtOeTBPM1AKj9BQIkKGQ9LLBVAUy7jqwX/zNAmrng6xT XqYcXSszwQ1aUIMwahaRT/r84by6jN/oJ3488Pplg5inSCPshS3oCjpVumwUrDnL CK3XxWviAx6u2jwrbsbsWUOA33kaGydKi1XGrStr3sd3A7UwVhxcAeFUBBkd3ZIo WZb1Y7u4L7MVXp4pctU5GzIKxzKpZs3Wrk/mYriWuud2yNFpCrHyl9JD7zDQlnEt eLgF8ygg+755+usEOA69qWz8DSjI9QFXMitIN8hKGdWGxCK0meFj7m4WWVBVwaXb yZ5b7fADs8fp6cjdHG/vCVN8dJoN+U75Cpbxm/iwGfR706U2qCw=
=azsw
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Who's Online
Recent Visitors
- Krenn
  Sun Jun 7 03:07:26 2026
  from Sydney, Nsw via Telnet
- Krenn
  Sun Jun 7 01:30:12 2026
  from Sydney, Nsw via Telnet
- Centurion
  Sat Jun 6 23:27:30 2026
  from Berea, Ohio via Telnet
- Ab Cadd
  Sat Jun 6 15:42:53 2026
  from Sheboygan, Wi via Telnet
- Centurion
  Sat Jun 6 15:32:28 2026
  from Berea, Ohio via Telnet
- Krenn
  Sat Jun 6 11:38:56 2026
  from Sydney, Nsw via Telnet
- Furryboy
  Sat Jun 6 10:56:29 2026
  from Romania, Galati via SSH
- Centurion
  Fri Jun 5 22:28:01 2026
  from Berea, Ohio via Telnet

System Info

Sysop:	Keyop
Location:	Huddersfield, West Yorkshire, UK
Users:	715
Nodes:	16 (0 / 16)
Uptime:	162:16:21
Calls:	12,094
Calls today:	2
Files:	15,000
Messages:	6,517,780

Subject: Proposal - Remove requirement that emails be wrapped at 80 cha

Who's Online

Recent Visitors

System Info