From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Documenting FSF copyright assignment process
Date: Thu, 11 Apr 2019 10:00:25 -0400 [thread overview]
Message-ID: <10979ed1-e762-4574-83e2-ee836d7e422e@gmail.com> (raw)
In-Reply-To: <837ec0645s.fsf@gnu.org>
On 2019-04-11 09:51, Eli Zaretskii wrote:
> So I've included
> that information near the beginning of CONTRIBUTE, which is about the
> first document potential contributors should read before sending
> patches.
Great idea. Thanks Eli.
I wonder if https://www.gnu.org/software/emacs/ could grow a 'Contribute' page. We have a link to https://www.gnu.org/help/help.html under 'Help GNU', but maybe we also want to repeat the Emacs-relevant part of that page on Emacs' website? We could include a link to the repo, a brief description of the assignment process, and a pointer to the CONTRIBUTE file.
Clément.
next prev parent reply other threads:[~2019-04-11 14:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 23:33 Documenting FSF copyright assignment process Konstantin Kharlamov
2019-04-11 13:21 ` [OFFTOPIC] " Stefan Monnier
2019-04-11 13:51 ` Eli Zaretskii
2019-04-11 14:00 ` Clément Pit-Claudel [this message]
2019-04-11 18:03 ` Paul Eggert
2019-04-11 19:08 ` Eli Zaretskii
2019-04-11 23:53 ` Stefan Monnier
2019-04-15 13:13 ` Phillip Lord
2019-04-15 14:23 ` Stefan Monnier
2019-04-15 17:05 ` Phillip Lord
2019-04-15 14:38 ` Eli Zaretskii
2019-04-11 23:49 ` Konstantin Kharlamov
2019-04-12 7:00 ` Eli Zaretskii
2019-04-12 8:57 ` Konstantin Kharlamov
2019-04-12 9:33 ` Eli Zaretskii
2019-04-12 9:42 ` Konstantin Kharlamov
2019-04-12 12:33 ` Eli Zaretskii
2019-04-15 21:04 ` Konstantin Kharlamov
2019-04-16 15:34 ` Eli Zaretskii
2019-04-16 18:03 ` Konstantin Kharlamov
2019-04-16 18:28 ` Eli Zaretskii
2019-04-16 18:55 ` Konstantin Kharlamov
2019-04-16 19:11 ` Eli Zaretskii
2019-04-16 19:18 ` Konstantin Kharlamov
2019-04-16 19:24 ` Eli Zaretskii
2019-04-16 19:29 ` Konstantin Kharlamov
2019-04-17 2:33 ` Eli Zaretskii
2019-04-12 17:30 ` Amin Bandali
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=10979ed1-e762-4574-83e2-ee836d7e422e@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=emacs-devel@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 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).