all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sean Allred <code@seanallred.com>
To: emacs-devel@gnu.org
Subject: CLAHub and the FSF copyright assignment
Date: Sat, 13 Dec 2014 11:53:15 -0500	[thread overview]
Message-ID: <2F7CC5C4-503C-4867-87DC-644F8E4862E4@seanallred.com> (raw)

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

Hello all,

This is my first time posting to this list, so bear with me for any conventions I might unwittingly ignore :)

I’m the maintainer (or at least one of them) of `sx.el', a new and quickly growing StackExchange client for Emacs.  (StackExchange includes all the sites similar to StackOverflow, SuperUser, ServerFault, and the host of other specialized sites such as Emacs.StackExchange.com <http://emacs.stackexchange.com/>.)  I would very much like to submit this to the GNU ELPA (and have been invited to do so), but the greatest hurdle to contributing (that I’m sure I share) is the FSF copyright assignment.

Let me be clear: I realize the assignment is an essential and absolutely necessary part of contributing to free software.  There may or may not be discussion on this topic in and of itself — I don’t know — but the underlying concept is crucial.

The foremost reservation I had/have about submitting `sx.el’ is the possibility of hindering development by virtue of the copyright assignment process.  I understand that it’s not a terribly complicated process, but it is also paper-based.  (Disclaimer: I’ve never seen the forms, so I don’t have the experience to base this on.)  This is a terrible deterrent for contributors; it is seen as a significant time investment.

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.

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

All the best,
Sean Allred

[1]: https://github.com/clahub/clahub <https://github.com/clahub/clahub>; https://www.clahub.com <https://www.clahub.com/>
[2]: https://github.com/blog/1935-see-results-from-all-pull-request-status-checks <https://github.com/blog/1935-see-results-from-all-pull-request-status-checks>


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

             reply	other threads:[~2014-12-13 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13 16:53 Sean Allred [this message]
2014-12-13 18:51 ` CLAHub and the FSF copyright assignment 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
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=2F7CC5C4-503C-4867-87DC-644F8E4862E4@seanallred.com \
    --to=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.