unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: bug#19299: 25.0.50; "Contributing" button in *About GNU Emacs* no longer works
Date: Mon, 08 Dec 2014 18:12:48 -0600	[thread overview]
Message-ID: <85r3w9adfj.fsf@stephe-leake.org> (raw)
In-Reply-To: <slsigpq0hz.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 08 Dec 2014 16:45:28 -0500")

This is being discussed on emacs-devel, so I'm copying it there.

Glenn Morris <rgm@gnu.org> writes:

> PS perhaps there is some confusion as to the purpose of this file.
>
> The intended audience for etc/CONTRIBUTE is people who are not Emacs
> developers and do not have write access to the repo. So it
> specifically does not talk about how to commit things to Savannah, etc.
> (People may have added bits of such information to the file in error.)
> Many people just want to send a patch, not get write access.
> That was why CONTRIBUTE needs to be in the installed Emacs.

There is now developer stuff in CONTRIBUTE.

I suggest we move the "for non-developers" info into the Emacs manual
Contributing section, and keep CONTRIBUTE for developers.

Hmm; I'm assuming the Emacs manual is always installed with Emacs; is
that true?

> "What people who commit to Emacs need to know" is a much more lengthy
> document, and IMO should be a separate one. (IIRC, Xue Fuqiao wrote a
> version of it the last time this came up; see emacs-devel archives.
> I have to say that I didn't like that version much.)
>
> Such a document is obviously long overdue.

Yes, and the consensus here seemed to be it should be in CONTRIBUTE.
Apparently we forgot the rationale for CONTRIBUTE.

Which is a _very_ good argument for using texinfo for CONTRIBUTE; you can
put rationale in comments.

-- 
-- Stephe



  parent reply	other threads:[~2014-12-09  0:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <21636.57684.129193.880930@a1i15.kph.uni-mainz.de>
     [not found] ` <l7egsaulbz.fsf@fencepost.gnu.org>
2014-12-09  0:06   ` bug#19299: 25.0.50; "Contributing" button in *About GNU Emacs* no longer works Stephen Leake
     [not found]   ` <slsigpq0hz.fsf@fencepost.gnu.org>
2014-12-09  0:12     ` Stephen Leake [this message]
2014-12-09  0:21       ` Alexis
2014-12-09  4:43         ` Glenn Morris
2014-12-09  8:37           ` Stephen Leake
2014-12-09 16:22           ` Eli Zaretskii
2014-12-09 17:55             ` Glenn Morris
2014-12-09 18:12               ` Eli Zaretskii
2014-12-10  9:34                 ` Stephen Leake
2014-12-10 16:18             ` Richard Stallman
2014-12-10 17:15               ` Stephen Leake
2014-12-15  8:39                 ` Richard Stallman

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85r3w9adfj.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).