all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rett Kent <rett.kent@gmail.com>
To: Sameer Rahmani <lxsameer@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Contributing
Date: Mon, 25 Jul 2011 13:32:17 -0700	[thread overview]
Message-ID: <4E2DD2D1.6050903@gmail.com> (raw)
In-Reply-To: <4E2A82C3.80603@gnu.org>

On 07/23/2011 01:13 AM, Sameer Rahmani wrote:
> Hi,
> My friend and i want to contribute to Emacs as much as we can. We want
> to contribute in development and translations.
>
> I read in contributing documents that is better to post here first,
> where should we start? what we can do ? and is there any specific task
> or something?

Hi Shameer,

I sent an email to Stefan Monnier a month ago or so with that same 
question.  Hopefully he won't mind if I share his response.

 >
 > Thanks for your interest in Emacs and desire to contribute.
 > We're not very well organized to answer such a question, I guess, but
 > you could start by looking at the etc/TODO file (tho it's largely
 > a dump of ideas along the lines of "it would be nice, but I'll never get
 > to it" so it may not be that easy to tackle).
 >
 > Most people start by contributing small changes they've accumulated in
 > their .emacs over the years, or bug reports (with or without patches)
 > about problems (actual bugs, or just missing features) they've bump
 > into.  Other things you could try is to go through the etc/NEWS file in
 > the trunk branch and look at the entries that are not yet marked as
 > "done" (i.e. either a --- or a +++ before it) which means that the
 > corresponding change has not yet been reflected in the manual.
 >
 > I'd also recommend to follow the emacs-devel@gnu.org mailing list,
 > although it's pretty high traffic.
 >
 >
 >         Stefan


If you do end up contributing, you should set up a website or blog that 
documents how you actually managed to select something to fix, and 
shepard it into the Emacs trunk.  I tried to start, but I found it a bit 
too daunting for my feeble abilities.



  parent reply	other threads:[~2011-07-25 20:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23  8:13 Contributing Sameer Rahmani
2011-07-23  8:53 ` Contributing Jambunathan K
2011-07-25 20:32 ` Rett Kent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-27 16:57 Contributing Matthew Wood
2013-01-27 17:00 ` Contributing Aurélien Aptel
2013-01-27 17:13 ` Contributing Paul Eggert
2013-01-27 18:12 ` Contributing Jambunathan K
2013-01-27 18:36   ` Contributing Matthew Wood
2013-01-27 19:04     ` Contributing Jambunathan K
2013-01-27 19:57       ` Contributing Matthew Wood
2013-01-27 22:14         ` Contributing Lennart Borgman
2013-01-27 23:56           ` Contributing Xue Fuqiao
2013-01-28  6:40             ` Contributing Dmitry Gutov
2013-01-28  0:52       ` Contributing 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

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

  git send-email \
    --in-reply-to=4E2DD2D1.6050903@gmail.com \
    --to=rett.kent@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lxsameer@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.