all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sean Allred <code@seanallred.com>
To: bruce.connor.am@gmail.com
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: CLAHub and the FSF copyright assignment
Date: Sat, 13 Dec 2014 23:19:53 -0500	[thread overview]
Message-ID: <26B2438A-62A1-4669-B3C8-719C57B7615B@seanallred.com> (raw)
In-Reply-To: <CAAdUY-KJMX2ozRN2s=WPKLxzNXKtM-JzKC+1qKZmafNdfhw_DA@mail.gmail.com>

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


> On Dec 13, 2014, at 8:25 PM, Artur Malabarba <bruce.connor.am@gmail.com> wrote:
> IIUC, this information you're referring to is whether the author of the pull request has signed the assignment?
> 
Yes, sorry :) IIUC myself of what CLAHub is though, the copyright assignment will have to be binding though CLAHub’s services.  That is, I presume some sort of text field with the contribution agreement and an ‘I understand and agree’ checkbox is provided by CLAHub.  Once the contributor agrees to the CLA, this agreement is reflected visibly on the PR discussion page.

I hope this would not boil down to a ‘CLA’ saying essentially that the contributor has completed the (separate) FSF copyright assignment.  This would degrade the service as a mere convenience rather than an open door for future contributors.

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

  reply	other threads:[~2014-12-14  4:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13 16:53 CLAHub and the FSF copyright assignment Sean Allred
2014-12-13 18:51 ` Paul Eggert
2014-12-13 19:01   ` Rasmus
2014-12-14  1:25 ` Artur Malabarba
2014-12-14  4:19   ` Sean Allred [this message]
2014-12-14  8:15     ` Artur Malabarba
2014-12-14 13:37     ` Stefan Monnier
2014-12-14  4:24 ` Stefan Monnier

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=26B2438A-62A1-4669-B3C8-719C57B7615B@seanallred.com \
    --to=code@seanallred.com \
    --cc=bruce.connor.am@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.