unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Matthew Wood <doowttam@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Contributing
Date: Sun, 27 Jan 2013 12:36:53 -0600	[thread overview]
Message-ID: <CAJbv8FhmFQmME78YO_RchgG42HbA05Xo0qLSZMx=wsdTkL9-vQ@mail.gmail.com> (raw)
In-Reply-To: <87fw1m337v.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]

Thanks, I'll check out the bug list and some of the bigger packages I rely
on, too.

More information: I'm a web developer working on Linux
and primarily working in Perl, Python, Javascript, stuff like that.
Probably not anything directly applicable, unfortunately.


On Sun, Jan 27, 2013 at 12:12 PM, Jambunathan K <kjambunathan@gmail.com>wrote:

> Matthew Wood <doowttam@gmail.com> writes:
>
> > I'm interested contributing, but don't have a project in mind. The
> > contributing docs mention starting with a message here.
>
> May be you should tell us more?
>
> How do you use your Emacs and to what ends.  Are you a programmer and
> what languages do you program in?  What are your interest areas?  What
> platform do you use - Mac, Linux, Windows etc.
>
> The easiest way to contribute is by filing bug reports, responding to
> and helping others in the MLs, IRC.
>
> You can also contribute to any of the bigger packages like Gnus, Org
> mode, CEDET etc.
>
> If you are serious about contributing, why not submit a(ny) patch of say
> 20+ lines, asssign the copyright to FSF and have it integrated in to
> Emacs proper or GNU ELPA.  See section titled `* Copyright Assignment'
> in etc/CONTRIBUTE.
>
> Whether projects end up in your plate or not, lurking around in the
>  mailing list of Emacs and sister projects can give you good perspective
>  on the goings-on in Emacs world.  You can join in when something rings
>  a bell.
>
> > Looking through the archives, I found a message that basically said
> > that there wasn't a well organized list of projects for beginner
> > contributors. It suggested looking in etc/TODO and etc/NEWS for ideas.
> >
> > Is that still the best way to start? Or is there a better way now?
> >
> > Thanks.
> >
> > Matt Wood
> >
>
> --
>

[-- Attachment #2: Type: text/html, Size: 2384 bytes --]

  reply	other threads:[~2013-01-27 18:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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   ` Matthew Wood [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2011-07-23  8:13 Contributing Sameer Rahmani
2011-07-23  8:53 ` Contributing Jambunathan K
2011-07-25 20:32 ` Contributing Rett Kent

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='CAJbv8FhmFQmME78YO_RchgG42HbA05Xo0qLSZMx=wsdTkL9-vQ@mail.gmail.com' \
    --to=doowttam@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=kjambunathan@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).