all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xue Fuqiao <xfq.free@gmail.com>
To: Justin Downer <downer@moxie.cs.oswego.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs TODO List
Date: Sat, 16 Feb 2013 11:56:15 +0800	[thread overview]
Message-ID: <20130216115615.f6d06d1ee76bcd183d321333@gmail.com> (raw)
In-Reply-To: <201302160038.r1G0cbEi029860@moxie.cs.oswego.edu>

On Fri, 15 Feb 2013 19:38:37 -0500 (EST)
Justin Downer <downer@moxie.cs.oswego.edu> wrote:

> I'd work on this.  I am not sure where to begin.  Any advice?.

1. Contributed code should follow the GNU Coding Standards and
the "Tips and Conventions" Appendix of the Emacs Lisp Reference.

2. For non-trivial contributions to GNU Emacs we require that the
copyright be assigned to the FSF.

3. You'd better write your patch based on the latest version (bzr
trunk).  Then bundle your patch, description, ChangeLog up in a
mail message and send it to the developers.

4. Or you can creat a task branch, work on it, and publish it on
Launchpad[1].

5. You can also request for inclusion of the Emacs group in
Savannah[2].  If you are a member, you can merge to the upstream
master directly.

6. As for which task to take, it depends on your Emacs knowledge.
There are simple tasks like remove leading `*'s from defcustom
doc-strings.  There are also important features like removing the
limitation that window and frame widths and heights can be only
full columns/lines.

7. If you don't know what to learn, you can have a look at this
thread:
http://lists.gnu.org/archive/html/emacs-devel/2013-01/msg00631.html

8. If you think of new features to add to etc/TODO, please
suggest them too.

9. As Glenn said, you can also fix bugs in debbugs.

HTH

[1] bzr push lp:~USERNAME/emacs/TASKNAME
[2] https://savannah.gnu.org/project/memberlist.php?group=emacs

-- 
Best regards, Xue Fuqiao.
http://www.emacswiki.org/emacs/XueFuqiao



      parent reply	other threads:[~2013-02-16  3:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-16  0:38 Emacs TODO List Justin Downer
2013-02-16  3:48 ` Glenn Morris
2013-02-16  3:56 ` Xue Fuqiao [this message]

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

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

  git send-email \
    --in-reply-to=20130216115615.f6d06d1ee76bcd183d321333@gmail.com \
    --to=xfq.free@gmail.com \
    --cc=downer@moxie.cs.oswego.edu \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.