all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Sean Allred <code@seanallred.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: CLAHub and the FSF copyright assignment
Date: Sun, 14 Dec 2014 01:25:45 +0000	[thread overview]
Message-ID: <CAAdUY-KJMX2ozRN2s=WPKLxzNXKtM-JzKC+1qKZmafNdfhw_DA@mail.gmail.com> (raw)
In-Reply-To: <2F7CC5C4-503C-4867-87DC-644F8E4862E4@seanallred.com>

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

On 13 Dec 2014 14:53, "Sean Allred" <code@seanallred.com> wrote:
> I post here to bring to discussion a resource called CLAHub [1].  This
service integrates with GitHub (the repository host for `sx.el’ and a host
of other packages on the MELPA) to provide pull request statusing akin to
Travis CI and Code Climate. With GitHub’s recent blog announcement [2],
this information will be visible on the pull request’s page as the merge is
discussed.

IIUC, this information you're referring to is whether the author of the
pull request has signed the assignment?

> Can GNU/the FSF use this resource to fulfill its copyright assignment?

From what I understand, there are quite a few gnu elpa packages which are
developed on github. So I'm sure this convenience would be of interest to
some authors, me included.

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

  parent reply	other threads:[~2014-12-14  1:25 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 [this message]
2014-12-14  4:19   ` Sean Allred
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='CAAdUY-KJMX2ozRN2s=WPKLxzNXKtM-JzKC+1qKZmafNdfhw_DA@mail.gmail.com' \
    --to=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 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.