all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Filipe Silva <filipe.silva@gmail.com>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: One-click copyright assignments?
Date: Sun, 12 Mar 2017 14:07:48 -0300	[thread overview]
Message-ID: <CAEwkUWPzsaZ4Kmt7scoOotw1zk8du9=g3ALB2c8eNNtWjqvXCQ@mail.gmail.com> (raw)
In-Reply-To: <e4ac74da-847f-3f4a-0072-9d6c535f57f2@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]

This. I'm also curious to know why is the process so bureaucratic as it is
currently. Maybe there's a legal issue or something.

On Sun, Mar 12, 2017 at 8:08 AM, Clément Pit-Claudel <cpitclaudel@gmail.com>
wrote:

> Hey emacs-devel,
>
> Why is the copyright assignment process for GNU software more complex than
> other similar ones ?  I've contributed to various pieces of free software
> in the past, and in most cases (except for Apache) the assignment process
> was little more than a click of a button, possibly followed by an email.
> For Emacs, on the other hand, one needs to send an email to emacs-devel to
> get an off-list copy of a text-based form, then send the completed form to
> assign@gnu, then wait for a PDF (which mentions a monetary transaction of
> $1 that never actually happens), then electronically sign the form using
> PGP (possibly with an entirely new PGP key), then email it back and wait
> for confirmation.
>
> Is there anything specific to Emacs that requires the process to be this
> complicated?  For example, could the entire process not be automated?
> Ideally new contributors would fill a web form on gnu.org/emacs, sign
> with their mouse at the bottom of that form, and confirm their email adress
> by clicking a link in an email.
>
> The existing process could remain in place for e.g. company-wide
> assignments, but for the common case of applying a patch to an ELPA
> package, wouldn't this make things much nicer?  If this can't be done, then
> could we at least automate the part that generates the PDF form, and the
> part that checks the signature, so as to eliminate the copyright assignment
> delay?
>
> Thanks!
> Clément.
>
>

[-- Attachment #2: Type: text/html, Size: 2203 bytes --]

  reply	other threads:[~2017-03-12 17:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 11:08 One-click copyright assignments? Clément Pit-Claudel
2017-03-12 17:07 ` Filipe Silva [this message]
2017-03-12 17:44   ` Stefan Monnier
2017-03-12 17:56     ` Drew Adams
2017-03-12 19:26     ` Clément Pit-Claudel
2017-03-13  0:56       ` Stefan Monnier
2017-03-13 16:57     ` Richard Stallman
2017-03-13 17:28       ` Stefan Monnier
2017-03-14  3:22         ` Richard Stallman
2017-03-13 16:56   ` 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='CAEwkUWPzsaZ4Kmt7scoOotw1zk8du9=g3ALB2c8eNNtWjqvXCQ@mail.gmail.com' \
    --to=filipe.silva@gmail.com \
    --cc=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 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.