unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Akib Azmain Turja <akib@disroot.org>
To: Yoni Rabkin <yoni@rabkins.net>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs packages, GitHub and software freedom
Date: Wed, 06 Jul 2022 21:22:50 +0600	[thread overview]
Message-ID: <87zghm2rlh.fsf@disroot.org> (raw)
In-Reply-To: <87y1x62vic.fsf@rabkins.net>

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

Yoni Rabkin <yoni@rabkins.net> writes:

> Kicking them out would be unkind. But asking that new projects going
> forward use a different backend seems reasonable. That ideally should be
> accompanied with a few recommendations.

And it would be a huge inconvenience for the users too.

> Emms has been always been hosted on Savannah (for many years now), and
> it works well for us. Emms is a mid-sized Emacs package with relatively
> light development work. Savannah has been a stable and reliable home
> over many years.

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.

> As an Emacs package, yes, we have been asked by many people over the
> years why we don't just use github, and I'm sure that Emms is indeed
> mirrored there and therefore has been, without any of the copyright
> holder's consent, been added to microsoft's mass code theft project.

Almost all Emacs related things are mirrored to GitHub by Emacsmirror.

Mirroring to GitHub is obviously a problem, but at least better than
hosting on GitHub, because that means that the project is itself
supporting "evil" GitHub.

-- 
Akib Azmain Turja

This message is signed by me with my GnuPG key.  It's fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2022-07-06 15:22 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 [this message]
2022-07-06 20:52     ` Tim Cross
2022-07-06 22:31       ` Yoni Rabkin
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

  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=87zghm2rlh.fsf@disroot.org \
    --to=akib@disroot.org \
    --cc=emacs-devel@gnu.org \
    --cc=yoni@rabkins.net \
    /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).