From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Malk'Zameth" <malk@zameth.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs as the windows manager for graphical windows, How can I help?
Date: Wed, 03 Apr 2013 15:43:57 -0400 [thread overview]
Message-ID: <jwv6203e8hp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAE5mhfJKcWQ2uQkJdDiLcvs7zVe6x1Z8qatPFBv7OL5nUBUmiw@mail.gmail.com> (Malk'Zameth's message of "Wed, 3 Apr 2013 12:04:35 +0200")
> Well, time to put my free time where my mouth is : I volunteer to work
> on that, giving it all my "sideproject time" from the first of may
> until completion.
Great!
> (maybe there is a welcome guide somewhere?)
Not really, sorry.
> 1. What needs to be done? what "format" does a code needs to conform
> to be acceptable by the mainline Emacs?
Obviously, Joakim knows better what needs to be done, but here are some
comments from "the other end": to be acceptable for inclusion in the
trunk I think the main criteria are along the following lines:
- the new code is unlikely to need to be replaced later on by something
completely different. That is meant to rule out "experimental" code.
Also, while we try to speed it up, Emacs release cycle is pretty
long/slow, so take into account that the code won't be in a release
for at the very least another year, probably two, so try to make sure
it doesn't rely on some external package that will be obsolete
by then.
- the patch should be safe in that most/all the code it touches is
properly #ifdef'd.
- nitpickers are satisfied (send your patch for review, and you'll
see what I mean ;-). Read the GNU coding standards beforehand, since
it describes most of the details we like.
I think the best is if Joakim can give you a "first chunk" to chew on.
> 2. Where do I need to apply to have the right to contribute those
> changes to emacs at all?
I just sent you a private email for that.
Stefan
prev parent reply other threads:[~2013-04-03 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 10:04 Emacs as the windows manager for graphical windows, How can I help? Malk'Zameth
2013-04-03 11:41 ` joakim
2013-04-03 12:44 ` Xue Fuqiao
2013-04-03 19:24 ` Adrian Robert
2013-04-03 19:45 ` joakim
2013-04-04 0:44 ` Stefan Monnier
2013-04-03 19:43 ` Stefan Monnier [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
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=jwv6203e8hp.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=malk@zameth.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 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).