all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Emacs TODO List
@ 2013-02-16  0:38 Justin Downer
  2013-02-16  3:48 ` Glenn Morris
  2013-02-16  3:56 ` Xue Fuqiao
  0 siblings, 2 replies; 3+ messages in thread
From: Justin Downer @ 2013-02-16  0:38 UTC (permalink / raw)
  To: emacs-devel

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Emacs TODO List
  2013-02-16  0:38 Emacs TODO List Justin Downer
@ 2013-02-16  3:48 ` Glenn Morris
  2013-02-16  3:56 ` Xue Fuqiao
  1 sibling, 0 replies; 3+ messages in thread
From: Glenn Morris @ 2013-02-16  3:48 UTC (permalink / raw)
  To: Justin Downer; +Cc: emacs-devel

Justin Downer wrote:

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

Thanks! It depends. What are you interested in? What is your level of
experience with Lisp or C (or Texinfo)?

http://debbugs.gnu.org/

is a huge reservoir of things to do as well.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Emacs TODO List
  2013-02-16  0:38 Emacs TODO List Justin Downer
  2013-02-16  3:48 ` Glenn Morris
@ 2013-02-16  3:56 ` Xue Fuqiao
  1 sibling, 0 replies; 3+ messages in thread
From: Xue Fuqiao @ 2013-02-16  3:56 UTC (permalink / raw)
  To: Justin Downer; +Cc: emacs-devel

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-02-16  3:56 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-02-16  0:38 Emacs TODO List Justin Downer
2013-02-16  3:48 ` Glenn Morris
2013-02-16  3:56 ` Xue Fuqiao

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.