From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Emacs developers <emacs-devel@gnu.org>
Cc: Richard Stallman <rms@gnu.org>
Subject: Documenting FSF copyright assignment process
Date: Thu, 11 Apr 2019 02:33:21 +0300 [thread overview]
Message-ID: <1554939201.27299.0@yandex.ru> (raw)
I was wondering about that off-list, and I was asked to create a new
topic about that.
I recently went through the signing procedure, and one thing I didn't
like which can be improved: the specific steps up to sending a mail to
assign@gnu.org are not documented. In my case I had to send a private
mail to Eli asking for the assignment form, he sent it back to me along
with further instructions; then I filled the form and sent it to
assign@gnu.org.
This is a roundtrip that takes time for both maintainer and a user.
Additionally, users are not even sure if what they're doing is correct,
e.g. look at the last "assignment"-titled mail on this list, it starts
with "I'm not sure if it's the right place to ask this". Yes, neither
was I! That only adds up confusion and frustration (which is likely
already there because you can't "just contribute" like with other FOSS
projects). Even more so when one has social communication problems,
which I think is not that rare among scientists/developers.
It would really help if the emacs documentation about assignment¹ has
either α) a paragraph with the form to be sent to assign@gnu.org and
according instructions, or β) if it has to be documented on another
site, e.g. FSF's, it would help to put a link to emacs documentation¹
after the words "Copyright assignment is a simple process." (and I hope
that this would-be referred documentation includes α; preferrably with
any legal notes — if there will be any — moved somewhere at the
bottom).
1:
https://www.gnu.org/software/emacs/manual/html_node/emacs/Copyright-Assignment.html#Copyright-Assignment
next reply other threads:[~2019-04-10 23:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 23:33 Konstantin Kharlamov [this message]
2019-04-11 13:21 ` [OFFTOPIC] Documenting FSF copyright assignment process Stefan Monnier
2019-04-11 13:51 ` Eli Zaretskii
2019-04-11 14:00 ` Clément Pit-Claudel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1554939201.27299.0@yandex.ru \
--to=hi-angel@yandex.ru \
--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.