all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Akib Azmain Turja <akib@disroot.org>,
	Arvid Krein <arvidkrein@zedat.fu-berlin.de>
Cc: guix-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: guix emacs package MELPA/ELPA
Date: Sat, 3 Dec 2022 08:57:07 -0800	[thread overview]
Message-ID: <CADwFkm=U5xq+tZL10dtRCOL_LPQQx+cwkTZZm9iuDzMpqKhjSw@mail.gmail.com> (raw)
In-Reply-To: <877cz8r1al.fsf@disroot.org>

Akib Azmain Turja <akib@disroot.org> writes:

> GNU ELPA (elpa.gnu.org) is not the correct place for guix.el.  GNU ELPA
> is for the packages that are part of GNU Emacs but not distributed with
> Emacs; therefore FSF holds the copyright of those packages.
>
> NonGNU ELPA is the correct place, it is for all types of free software
> Emacs packages that are not part of GNU Emacs.

Thinking of this in terms of "being part of Emacs" or not doesn't
necessarily help make things clearer, in my opinion.

The main difference between GNU ELPA and NonGNU ELPA is that the former
requires all copyright to be assigned to the Free Software Foundation,
whereas the latter does not.  So if the copyright of guix.el is
assigned, it could be added to GNU ELPA.  Otherwise, it would have to go
to NonGNU ELPA.

There are also ethical requirements for both archives, of course.  These
are mainly that packages must be free software, and not recommend using
non-free software.


  reply	other threads:[~2022-12-03 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 23:26 guix emacs package MELPA/ELPA Arvid Krein
2022-12-03 14:48 ` Akib Azmain Turja
2022-12-03 16:57   ` Stefan Kangas [this message]
2022-12-03 17:56     ` Eli Zaretskii
2022-12-04 23:14     ` 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='CADwFkm=U5xq+tZL10dtRCOL_LPQQx+cwkTZZm9iuDzMpqKhjSw@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=akib@disroot.org \
    --cc=arvidkrein@zedat.fu-berlin.de \
    --cc=emacs-devel@gnu.org \
    --cc=guix-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/guix.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.