From: Yoni Rabkin <yoni@rabkins.net>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs packages, GitHub and software freedom
Date: Wed, 06 Jul 2022 18:31:25 -0400 [thread overview]
Message-ID: <87y1x527r6.fsf@rabkins.net> (raw)
In-Reply-To: <87czeikkzw.fsf@gmail.com> (Tim Cross's message of "Thu, 07 Jul 2022 06:52:53 +1000")
Tim Cross <theophilusx@gmail.com> writes:
> Akib Azmain Turja <akib@disroot.org> writes:
>
>>
>> Savannah is obviously a good host, but it's not newbie friendly IMHO.
>> FSF has a plan for a new forge. Let's wait and see what they give us.
>>
>
> They do? Any link to information on that?
>
> Two points to note which I think are relevant
>
> 1. This was all brought up quite some time ago and RMS basically came
> down saying that on balance, we have to accept people will host packages
> on github and that being hosted there was not to be an impediment to
> being included in ELPA or nonGNU ELPA. This might seem contradictory
> given FSF statements about github, but the world is full of
> contradiction. The FSF even has a link to Paypal on their donations
> page despite their position on not encouraging the use of non-free JS.
>
> 2. Until there is a solution which does provide high level functionality
> similar to that provided by github, you just yelling at the wind. If you
> really want people to stop using github for Emacs packages, you need to
> either look at developing higher level functionality which sits on top
> of sevannah or help add functionality to other forges, like gitlab or
> sourceHut so that these other forges become as appealing to these
> developers.
>
> 3. If you try to control where packages are hosted/developed by
> restricting access to ELPA/nonGNU ELPA, all you will do is encourage
> repositories like MELPA, which provide no assurance regarding package
> licenses. At least ELPA/nonGNU ELPA are all libre. licensed.
My understanding of their request, is that Eli asks that this discussion
continue on the emacs-tangents mailing list.
--
"Cut your own wood and it will warm you twice"
next prev parent reply other threads:[~2022-07-06 22:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 13:32 Emacs packages, GitHub and software freedom Akib Azmain Turja
2022-07-06 13:45 ` Stefan Kangas
2022-07-06 13:58 ` Yoni Rabkin
2022-07-06 14:29 ` Gerry Agbobada
2022-07-06 14:33 ` Bozhidar Batsov
2022-07-06 16:17 ` Akib Azmain Turja
2022-07-06 16:24 ` Eli Zaretskii
2022-07-06 18:03 ` Akib Azmain Turja
2022-07-06 18:48 ` Stefan Monnier
2022-07-06 18:48 ` Yoni Rabkin
2022-07-06 19:10 ` Eli Zaretskii
2022-07-06 19:28 ` Yoni Rabkin
2022-07-06 19:06 ` Eli Zaretskii
2022-07-08 3:32 ` Richard Stallman
2022-07-08 8:11 ` Akib Azmain Turja
2022-07-08 8:18 ` Po Lu
2022-07-08 10:33 ` Eli Zaretskii
2022-07-06 15:22 ` Akib Azmain Turja
2022-07-06 20:52 ` Tim Cross
2022-07-06 22:31 ` Yoni Rabkin [this message]
2022-07-08 3:32 ` 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=87y1x527r6.fsf@rabkins.net \
--to=yoni@rabkins.net \
--cc=emacs-devel@gnu.org \
--cc=theophilusx@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 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.