From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Sean Allred <code@seanallred.com>
Cc: bruce.connor.am@gmail.com, emacs-devel <emacs-devel@gnu.org>
Subject: Re: CLAHub and the FSF copyright assignment
Date: Sun, 14 Dec 2014 08:37:11 -0500 [thread overview]
Message-ID: <jwv4msypd88.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <26B2438A-62A1-4669-B3C8-719C57B7615B@seanallred.com> (Sean Allred's message of "Sat, 13 Dec 2014 23:19:53 -0500")
> 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 still have no idea what "CLAHub" is, but FWIW, the fundamental
requirement is that we need to get one particular copyright assignment
signed and we don't want to trust anyone but the FSF to verify (and store)
this paperwork (especially not a company whose incorporation bylaws make
its aim to be maximizing profits rather than preserve the users's Freedom).
> I hope this would not boil down to a ‘CLA’ saying essentially that the
> contributor has completed the (separate) FSF copyright assignment.
I can't see how it could be otherwise.
Stefan
next prev parent reply other threads:[~2014-12-14 13:37 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
2014-12-14 8:15 ` Artur Malabarba
2014-12-14 13:37 ` Stefan Monnier [this message]
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
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=jwv4msypd88.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bruce.connor.am@gmail.com \
--cc=code@seanallred.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 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).