unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Documenting FSF copyright assignment process
Date: Mon, 15 Apr 2019 17:38:45 +0300	[thread overview]
Message-ID: <83k1fvib9m.fsf@gnu.org> (raw)
In-Reply-To: <87r2a3xvh7.fsf@russet.org.uk> (message from Phillip Lord on Mon,  15 Apr 2019 14:13:08 +0100)

> From: Phillip Lord <phillip.lord@russet.org.uk>
> Date: Mon, 15 Apr 2019 14:13:08 +0100
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>
> 
> 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.

If it's possible, I certainly would welcome a more versatile and
dynamic system for that.  But this is something the FSF should do, not
the Emacs project.  We are just one customer of that system.



  parent reply	other threads:[~2019-04-15 14:38 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
2019-04-15 14:23         ` Stefan Monnier
2019-04-15 17:05           ` Phillip Lord
2019-04-15 14:38         ` Eli Zaretskii [this message]
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=83k1fvib9m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=phillip.lord@russet.org.uk \
    /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).