From: Neil Jerram <neil@ossau.uklinux.net>
To: ludovic.courtes@inria.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: NEWS entries -- user-visible?
Date: Sat, 27 Jun 2009 23:05:15 +0100 [thread overview]
Message-ID: <871vp549k4.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <86my84gkh9.fsf@inria.fr> ("Ludovic Courtès"'s message of "Fri\, 19 Jun 2009 20\:13\:38 +0200")
ludovic.courtes@inria.fr (Ludovic Courtès) writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> I'm really not sure. It's an interesting idea. And I think it
>> touches on the part of GNU philosophy that tries not to draw a firm
>> line between users and developers. Do you think it's worth asking
>> people on gnu-prog-discuss?
>
> Yes, why not. Would you like to do this?
I just checked standards.texi before going ahead with this, and
actually it seems pretty clear:
"In addition to its manual, the package should have a file named
@file{NEWS} which contains a list of user-visible changes worth
mentioning. ..."
So I'd say that use of Gnulib (in general) should not be a NEWS item.
I think HACKING would be the right place to mention it - and it would
be just as accessible there (as in NEWS) to blurred users/developers.
Regards,
Neil
next prev parent reply other threads:[~2009-06-27 22:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 18:32 NEWS entries -- user-visible? Andy Wingo
2009-06-14 19:43 ` Julian Graham
2009-06-14 22:41 ` Neil Jerram
2009-06-18 20:48 ` Ludovic Courtès
2009-06-19 17:47 ` Neil Jerram
2009-06-19 17:58 ` Ludovic Courtès
2009-06-19 18:08 ` Neil Jerram
2009-06-19 18:13 ` Ludovic Courtès
2009-06-27 22:05 ` Neil Jerram [this message]
2009-06-27 23:14 ` Ludovic Courtès
2009-06-29 19:19 ` Neil Jerram
2009-06-29 21:01 ` Ludovic Courtès
2009-06-14 20:39 ` Neil Jerram
2009-06-18 20:49 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871vp549k4.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludovic.courtes@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).