[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnulib/README -> gnulib.texi

From: Bruno Haible
Subject: Re: gnulib/README -> gnulib.texi
Date: Sun, 22 Apr 2012 13:20:34 +0200
User-agent: KMail/4.7.4 (Linux/3.1.0-1.2-desktop; KDE/4.7.4; x86_64; ; )

Hi Paul,

Thanks for looking into this doc improvement.

I like the added text to "Target Platforms".

However, I don't agree to putting the contributor's guide into the manual,
simply because that's not the target audience of the manual. It makes no
sense to me to have instructions for contributors located
  - in README-dev for Hello, recutils,
  - in README-hacking for Bison, findutils, gzip, idutils, patch, tar,
  - in HACKING for Automake, gettext, guile, libtool, m4, Octave,
  - in README-hacking and HACKING for Autoconf, coreutils, diffutils,
  - in README-hacking and README-prereq and HACKING for grep,
  - in README and etc/CONTRIBUTE for Emacs,
  - in README.dev for texinfo,
  - on the web (http://gcc.gnu.org/contribute.html) for GCC,
  - on the web (http://sourceware.org/glibc/wiki/#Development) for glibc,
  - and in the manual for gnulib.

And if it needs to go into the manual, it should be in a separate chapter,
near the end - because it is of zero importance to the majority of the
target audience of the manual.

The paragraph about the test suite "The goal is to have a 100% firm
interface..." (which you now have duplicated in two places) should IMO
better be split and rewritten to answer two questions:
  1. What does the test suite mean for the users of gnulib?
  2. What does the test suite mean for the contributors to gnulib?
The text for the users goes somewhere in chapter 1, the text for the
contributors is an addendum to the contributor's guide.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]