From: Jambunathan K <kjambunathan@gmail.com>
To: Sameer Rahmani <lxsameer@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Contributing
Date: Sat, 23 Jul 2011 14:23:25 +0530 [thread overview]
Message-ID: <81aac55qey.fsf@gmail.com> (raw)
In-Reply-To: <4E2A82C3.80603@gnu.org> (Sameer Rahmani's message of "Sat, 23 Jul 2011 12:43:55 +0430")
Sameer Rahmani <lxsameer@gnu.org> writes:
> Hi,
> My friend and i want to contribute to Emacs as much as we can. We want
> to contribute in development and translations.
If your patches are going to be any big, you may want to read the
"Copyright Assignment" section.
http://www.gnu.org/software/emacs/CONTRIBUTE
Since you say that you are interested in translations, I am not quite
sure whether you are a developer or a user.
> 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?
May be you want to share a little more about yourself - your skills and
areas of interest. (Speaking of your areas of interest, think about how
you use Emacs yourself)
If you are unsure where to start, the most effective strategy is to pick
one area that you think needs improvement and improve it (As an Emacs
user, I believe you sure have some share of complaints).
The best way to attract attention your patches and ensure progress is
first to exhibit your wares (even if buggy and less than satisfactory)
and open it for criticism. Bonus points if your wares cannot be cooked
up trivially.
It's easier to find areas of improvement particulary in features that
are new, modules that are big or which have wider user base. You can
hang around in the following mailing list and see what catches your
attention:
Emacs Devel:
http://lists.gnu.org/archive/html/emacs-devel/
Emacs Bugs:
http://lists.gnu.org/archive/html/bug-gnu-emacs/
Orgmode:
https://lists.gnu.org/archive/html/emacs-orgmode/
Gnus:
https://lists.gnu.org/archive/html/info-gnus-english/
Cedet-devel:
http://sourceforge.net/mailarchive/forum.php?forum_name=cedet-devel
If you are unsure where to start you can start anywhere you like and
form opinions as you explore more. Remember, if you would like to
contribute purely for fun - you don't have to be bound by what people
ask of you.
From my own personal experience, I can say that contributing to Free
Software projects and sustaining your motivation levels require certain
discipline, clarity of thought and enough staying power etc.
Good luck with your efforts,
Jambunathan K.
--
next prev parent reply other threads:[~2011-07-23 8:53 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 ` Jambunathan K [this message]
2011-07-25 20:32 ` Contributing Rett Kent
-- 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=81aac55qey.fsf@gmail.com \
--to=kjambunathan@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.