unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: Glenn Morris <rgm@gnu.org>
Cc: xfq <xfq.free@gmail.com>, emacs-devel@gnu.org
Subject: Integrating new "GNU Emacs Contributing Guide" into Emacs web pages.
Date: Mon, 22 Apr 2013 11:54:15 -0500	[thread overview]
Message-ID: <87ppxm33rc.fsf_-_@ktab.red-bean.com> (raw)
In-Reply-To: <8bppxmttfa.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 22 Apr 2013 12:35:21 -0400")

Glenn Morris <rgm@gnu.org> writes:
>> I don't have edit rights on (c), as far as I know, so I hope someone
>
>Anyone with commit rights to Emacs has commit rights to the web pages.
>
>http://savannah.gnu.org/cvs/?group=emacs

Thank you.  

Any objections if I integrate Xue Fuqiao's guide into those pages in
some reasonable way?  (Which I'm not defining here only because I'll
figure it out if/when we're generally agreed this is a Good Thing.)

I think the guide is a very good start.  I might make a few edits before
integrating, and would expect further edits over time, but I don't think
it needs to be perfect to be posted.  It contains a lot of useful
information.  One change I would probably make right away is to have the
document link to the mailing list threads Xue Fuqiao listed in his
original post on this topic.

Xue, what was the original format of the document?  LaTeX or Docbook?
(I think if we integrate it into the web site, we should probably just
use the HTML version as master, to keep things simple, but maybe there
is a reason to generate HTML from another format?)

-Karl



  reply	other threads:[~2013-04-22 16:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 13:05 GNU Emacs Contributing Guide xfq
2013-04-22 16:30 ` Karl Fogel
2013-04-22 16:35   ` Glenn Morris
2013-04-22 16:54     ` Karl Fogel [this message]
2013-04-22 17:09       ` Integrating new "GNU Emacs Contributing Guide" into Emacs web pages Bastien
2013-04-22 17:13         ` Karl Fogel
2013-04-22 17:15           ` Bastien
2013-04-22 22:38           ` Xue Fuqiao
2013-04-22 17:44       ` Glenn Morris
2013-04-22 18:13         ` Karl Fogel
2013-04-22 22:51           ` Xue Fuqiao
2013-04-23  1:00             ` Xue Fuqiao
2013-04-23  3:34               ` Stefan Monnier
2013-04-23  3:32       ` Stefan Monnier
2013-04-23  4:37         ` Xue Fuqiao
2013-04-23  4:49           ` Xue Fuqiao
2013-04-22 16:51   ` GNU Emacs Contributing Guide Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2013-04-23 14:08 Integrating new "GNU Emacs Contributing Guide" into Emacs web pages Jonathan Leech-Pepin
2013-04-23 22:48 ` Xue Fuqiao
2013-04-23 23:15   ` Xue Fuqiao
2013-04-25  7:02     ` Glenn Morris
2013-04-25 13:43       ` Stefan Monnier
2013-04-25 22:34       ` Xue Fuqiao

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=87ppxm33rc.fsf_-_@ktab.red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.org \
    --cc=xfq.free@gmail.com \
    /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).