From: Tim Cross <theophilusx@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Jean Louis <bugs@gnu.support>, Richard Stallman <rms@gnu.org>,
thibaut.verron@gmail.com, Boruch Baum <boruch_baum@gmx.com>,
Emacs developers <emacs-devel@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>
Subject: Re: non-gnu elpa issue tracking
Date: Sun, 13 Dec 2020 02:37:16 +1100 [thread overview]
Message-ID: <CAC=50j_iTUNLNJ_+vAXFpftEPh2q=XvOLSD1=ZMW-Fi=B1r5nw@mail.gmail.com> (raw)
In-Reply-To: <jwv1rfvp246.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1881 bytes --]
On Sun, 13 Dec 2020 at 00:50, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> > The non-GNU ELPA is supposed to be a repository for packages which are
> GPL
> > compliant and it is a reasonable expectation that those who make their
> > packages GPL compliant do so because they support the philosophical goals
> > of the FSF.
>
> The overwhelming majority of ELisp packages out there are hosted on
> Github (that also applies to many GNU ELPA packages, many of them are
> developed by long time contributors to Emacs), so I think the evidence
> shows the above expectation doesn't hold at all.
>
> Maybe. However, it could also be a combination of the fact github was the
first free git hosting environment and is the better known one. Just
because it is this way now doesn't mean it has to be. If the GNU/FSF
doesn't take a clear position on this and do something to discourage the
use of hosting environments that force the use of proprietary software,
this will not change and eventually all we will have are the proprietary
solutions. It may not have been the right decision to allow code which has
assigned copyright to the FSF to remain on Github. However, as non-GNU ELPA
is just getting started, now would be a good time to try and change things.
I'm also not convinced about arguments suggesting too much inertia or too
much hassle in moving to a new hosting platform. Lots of packages which use
to be hosted on sourceforge have moved to Github. There are few technical
barriers to moving git repositories to a new hosting platform. However,
there has to be some incentive to do so. It also seems inconsistent to
have so many packages, both GNU ELPA and non-GNU ELPA packages hosted on a
platform which is so far from being acceptable from a FSF philosophical
perspective. Makes it feel like the FSF fails to eat their own dog food.
--
regards,
Tim
--
Tim Cross
[-- Attachment #2: Type: text/html, Size: 2444 bytes --]
next prev parent reply other threads:[~2020-12-12 15:37 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 12:55 non-gnu elpa issue tracking Boruch Baum
2020-12-09 16:58 ` Stefan Kangas
2020-12-09 19:18 ` Jean Louis
2020-12-09 21:48 ` Stefan Kangas
2020-12-09 23:40 ` Jean Louis
2020-12-09 23:58 ` Jean Louis
2020-12-11 6:09 ` Richard Stallman
2020-12-11 6:05 ` Richard Stallman
2020-12-10 4:32 ` Richard Stallman
2020-12-10 6:28 ` Jean Louis
2020-12-09 19:23 ` Jean Louis
2020-12-09 23:22 ` Thibaut Verron
2020-12-10 0:09 ` Jean Louis
2020-12-10 9:14 ` Thibaut Verron
2020-12-10 11:23 ` Stefan Kangas
2020-12-10 14:19 ` Thibaut Verron
2020-12-10 16:37 ` Jean Louis
2020-12-11 6:10 ` Richard Stallman
2020-12-10 11:49 ` Jean Louis
2020-12-10 14:05 ` Stefan Kangas
2020-12-10 15:48 ` Stefan Monnier
2020-12-10 16:05 ` Jean Louis
2020-12-10 17:35 ` Stefan Monnier
2020-12-11 6:09 ` Richard Stallman
2020-12-11 6:04 ` Richard Stallman
2020-12-11 11:10 ` Thibaut Verron
2020-12-12 5:34 ` Richard Stallman
2020-12-12 6:37 ` Tim Cross
2020-12-12 10:08 ` Thibaut Verron
2020-12-12 15:23 ` Tim Cross
2020-12-12 17:07 ` Thibaut Verron
2020-12-13 4:56 ` Richard Stallman
2020-12-13 5:20 ` Tim Cross
2020-12-13 9:54 ` Andrea Corallo via Emacs development discussions.
2020-12-13 22:59 ` Tim Cross
2020-12-14 0:32 ` Stefan Monnier
2020-12-14 0:54 ` Tim Cross
2020-12-14 4:36 ` Stefan Monnier
2020-12-14 5:45 ` Tim Cross
2020-12-15 5:44 ` Richard Stallman
2020-12-14 10:03 ` Alfred M. Szmidt
2020-12-14 14:57 ` Stefan Monnier
2020-12-14 15:01 ` Alfred M. Szmidt
2020-12-14 15:12 ` Stefan Monnier
2020-12-14 15:52 ` Eli Zaretskii
2020-12-14 0:16 ` Stephen Leake
2020-12-13 4:56 ` Richard Stallman
2020-12-13 8:56 ` Vasilij Schneidermann
2020-12-14 5:50 ` Richard Stallman
2020-12-14 6:45 ` Jean Louis
2020-12-12 13:48 ` Michael Albinus
2020-12-12 13:50 ` Stefan Monnier
2020-12-12 15:37 ` Tim Cross [this message]
2020-12-12 19:54 ` Jean Louis
2020-12-12 20:46 ` Stephen Leake
2020-12-12 21:24 ` Alfred M. Szmidt
2020-12-12 21:48 ` Christopher Dimech
2020-12-13 0:39 ` Tim Cross
2020-12-13 1:28 ` Christopher Dimech
2020-12-13 5:03 ` Richard Stallman
2020-12-13 4:58 ` Richard Stallman
2020-12-12 21:06 ` Dmitry Gutov
2020-12-13 4:58 ` Richard Stallman
2020-12-13 5:27 ` Christopher Dimech
2020-12-12 19:33 ` Jean Louis
2020-12-12 21:24 ` Alfred M. Szmidt
2020-12-13 4:59 ` Richard Stallman
2020-12-13 5:03 ` Richard Stallman
2020-12-14 17:38 ` Jean Louis
2020-12-14 18:49 ` Vasilij Schneidermann
2020-12-14 22:13 ` Jean Louis
2020-12-14 19:10 ` Boruch Baum
2020-12-14 22:17 ` Jean Louis
2020-12-16 5:32 ` Richard Stallman
2021-01-02 5:25 ` Richard Stallman
2020-12-10 4:35 ` Richard Stallman
2020-12-10 5:03 ` Boruch Baum
2020-12-10 5:55 ` Eli Zaretskii
2020-12-10 6:39 ` "Open records", "good government principles", "corporate culture" Boruch Baum
2020-12-10 7:27 ` Jean Louis
2020-12-10 14:08 ` Eli Zaretskii
2020-12-11 6:16 ` Richard Stallman
2020-12-10 6:54 ` non-gnu elpa issue tracking Jean Louis
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='CAC=50j_iTUNLNJ_+vAXFpftEPh2q=XvOLSD1=ZMW-Fi=B1r5nw@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=boruch_baum@gmx.com \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
--cc=thibaut.verron@gmail.com \
/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).