From: Phillip Lord <phillip.lord@russet.org.uk>
To: emacs-devel@gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Documenting FSF copyright assignment process
Date: Mon, 15 Apr 2019 14:13:08 +0100 [thread overview]
Message-ID: <87r2a3xvh7.fsf@russet.org.uk> (raw)
In-Reply-To: <jwvmukwnlxj.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 11 Apr 2019 19:53:24 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/
>
> That's not a web form.
Indeed not. I would ask for slightly more than a webform
though. Something which shows the current status of the copyright
assignment and which allows the maintainers to see clearly who has done
which steps. Having a list of aliases that people use would also be
nice, since you often only have git IDs or email addressed to work out
who has contributed to a particular project. I realise that this needs
to be balanced against the right to privacy for developers, of course.
It would also be nice to have something that showed the current status
of peoples copyright assignment -- currently, it is very hard to know if
a assignment has run out, or if the person has moved employer.
I think this is a significant problem as it stands; I managed to get the
copyright assignment done for the 40 developers on dash.el using email
threads and a local org file. But I have failed to update it because of
new developers coming on stream. I wouldn't even begin to think about
starting the process for a project like magit (250 developers).
There are around 1.2k developers who have contributed to MELPA (which is
a good lower bound for the number of somewhat current Emacs-lisp
developers), or 1.8k developers in AUTHORS (which is a good lower bound
for the number of Emacs-lisp developers in all history), or 1.8k who
have contributed to an MELPA package at all (which is another good lower
bound for emacs-lisp developers).
It's a big number. A better system would be worthwhile.
Phil
next prev parent reply other threads:[~2019-04-15 13:13 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
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 [this message]
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=87r2a3xvh7.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--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 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.