From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: master b341e86 * CONTRIBUTE: Refer to gnulib for request-assign.future.
Date: Tue, 16 Mar 2021 20:37:07 -0400 [thread overview]
Message-ID: <agmtv27gzw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83ft0vdv57.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Mar 2021 16:35:00 +0200")
Eli Zaretskii wrote:
> First, Gnulib is a separate project. Did the GNU Project made them
> responsible for distributing the official up-to-date version of the
> assignment forms? If so, then pointing to them is okay, I guess.
request-assign.future hasn't changed in nine years.
As has been said, "Information for Maintainers of GNU Software" lists
Gnulib as a possible place to get the file.
If it ever changes, I trust the Gnulib maintainers to keep their copy
up-to-date. And if someone fills in an old version, assign@gnu can just
ask for more info.
(I don't know why these files aren't simply hosted on a GNU/FSF website.)
> But if not, then we just told our contributors to go to yet another
> place, unrelated to Emacs, which is one more obstacle, albeit a minor one.
I think fetching a web page is less of an obstacle than posting to a
(moderated) mailing list.
> And what if the Gnulib repository or the Git on savannah in general is
> down?
We might as well ask, what if the emacs-devel mailing list is down?
In either case, I trust the FSF/Savannah admins will fix it, as they
have done in the past.
(Also, the Gnulib git repository is mirrored on non-gnu sites.)
(FTR request-assign.future is not the copyright assignment form, it is
the brief pre-form questionnaire one fills out in order to get a form.)
next prev parent reply other threads:[~2021-03-17 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 14:35 master b341e86 * CONTRIBUTE: Refer to gnulib for request-assign.future Eli Zaretskii
2021-03-16 18:58 ` Michael Albinus
2021-03-17 0:37 ` Glenn Morris [this message]
2021-03-18 5:01 ` Richard Stallman
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=agmtv27gzw.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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.