From: Chong Yidong <cyd@stupidchicken.com>
To: Fabian Ezequiel Gallina <galli.87@gmail.com>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: A new major-mode for Python
Date: Tue, 15 Feb 2011 20:44:58 -0500 [thread overview]
Message-ID: <87pqqsda79.fsf@stupidchicken.com> (raw)
In-Reply-To: <jwvipwkvs9b.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 15 Feb 2011 17:52:41 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> So rather than replace our python.el with yours, I offer you to take
> over maintainership of our python.el. This may sound like a crappy
> offer (why would you maintain some old code you don't like when you
> already have your own that works better, right?), but note that, as
> a maintainer of our python.el, you'll have the opportunity to replace
> pretty much any of "our" code with yours, thus morphing our python.el
> into yours.
>
> Another way to look at it, is that I'm asking you to take a "diff
> old-python.el new-python.el" and cut it into manageable and meaningful
> patches, so it is easier to see that it is moving forward.
100% agreement.
Scanning through your version of python.el, the code looks to be of good
quality. As Stefan said, merging it into our existing python.el is much
better than setting up a wholesale replacement. Among other things,
features won't get lost. So I hope you will agree to take this on.
Should you be willing, we'll need a copyright assignment for your
contributions to Emacs. This can be done by emailing the following
information to fsf-records@gnu.org; they will send you the assignment
form for your past and future changes.
Please use your full legal name (in ASCII characters) as the subject
line of the message. Thanks.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES
[What is the name of the program or package you're contributing to?]
GNU Emacs and python.el
[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]
[Do you have an employer who might have a basis to claim to own
your changes? Do you attend a school which might make such a claim?]
[For the copyright registration, what country are you a citizen of?]
[What year were you born?]
[Please write your email address here.]
[Please write your postal address here.]
[Which files have you changed so far, and which new files have you written
so far?]
next prev parent reply other threads:[~2011-02-16 1:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 8:05 A new major-mode for Python Fabian Ezequiel Gallina
2011-02-15 22:52 ` Stefan Monnier
2011-02-16 1:44 ` Chong Yidong [this message]
2011-02-16 6:46 ` Fabian Ezequiel Gallina
2011-02-16 15:20 ` Stefan Monnier
2011-02-16 15:34 ` Chong Yidong
2011-02-16 14:23 ` Neal Becker
2011-02-17 18:12 ` Fabian Ezequiel Gallina
2011-02-17 4:04 ` m h
2011-02-17 18:36 ` Fabian Ezequiel Gallina
-- strict thread matches above, loose matches on Subject: below --
2011-02-17 3:58 Christoph
2011-02-17 18:22 ` Fabian Ezequiel Gallina
2011-02-18 0:31 ` Christoph
2011-03-28 22:55 ` Fabian Ezequiel Gallina
2011-03-28 23:21 ` Christoph Scholtes
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=87pqqsda79.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=galli.87@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
/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).