Richard Stallman [2025-11-13 00:19 -0500] wrote:
> > Therefore, I think it would be okay to allow other formats.
> I think it is ok to include markup if it is in a format
> that people can easily read without any special software.
>
> Mardown seems to qualify.
> > I like the
> > idea of a symlink, but those can't be included in releases [2].
> I can't make sense out of that. What, concretely, do you propose?
Perhaps something as simple as the following as a start:
diff --git a/doc/standards.texi b/doc/standards.texi
index 05178fc507..f5d532d4c9 100644
--- a/doc/standards.texi
+++ b/doc/standards.texi
@@ -3596,11 +3596,11 @@ NEWS File
@cindex @file{NEWS} file
In addition to its manual, the package should have a file named
-@file{NEWS} which contains a list of user-visible changes worth
-mentioning. In each new release, add items to the front of the file and
-identify the version they pertain to. Don't discard old items; leave
-them in the file after the newer items. This way, a user upgrading from
-any previous version can see what is new.
+@file{NEWS} (or @file{NEWS.md}) which contains a list of user-visible
+changes worth mentioning. In each new release, add items to the front
+of the file and identify the version they pertain to. Don't discard old
+items; leave them in the file after the newer items. This way, a user
+upgrading from any previous version can see what is new.
If the @file{NEWS} file gets very long, move some of the older items
into a file named @file{ONEWS} and put a note at the end referring the
@@ -4384,8 +4384,8 @@ Releases
source files by programs under the control of the Makefile.
@cindex @file{README} file
-The distribution should contain a file named @file{README} with a
-general overview of the package:
+The distribution should contain a file named @file{README} (or
+@file{README.md}) with a general overview of the package:
@itemize
@item the name of the package;
Those projects that opt into using the .md name(s), whether exclusively
or via symlink, will be in a better position to suggest further concrete
changes to tooling and documentation as needed.
Some changes needed in Gnulib to accommodate a NEWS.md file are already
being discussed here:
https://lists.gnu.org/r/bug-gnulib/2025-11/msg00109.html
Thanks,
--
Basil
