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

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

> Recently, FSF has sent the following in the Free Software Supporter
> list:[1]
>
>> ### Give up GitHub: The time has come!
>> 
>> *From June 30 by Software Freedom Conservancy*
>> 
>> [Following GitHub's announcement](https://u.fsf.org/3me) of Copilot as
>> a for-profit product, Software Freedom Conservancy calls on all free
>> software developers to leave and "Give up GitHub!" The campaign page
>> lists major reasons to give up on GitHub. Conservancy says,
>> "developers have been, for too long, the proverbial frog in slowly
>> boiling water. GitHub's behavior has gotten progressively worse, and
>> we've excused, ignored, or otherwise acquiesced to cognitive
>> dissonance." Read about the initiative, join the public mailing list,
>> and learn how you can support the campaign yourself.
>> 
>>   * <https://sfconservancy.org/GiveUpGitHub/>
>
> And GitHub is already listed as being a F grade software forge in "GNU
> Ethical Repository Criteria Evaluations" for atleast more than a
> year.[2]  "GNU Ethical Repository Criteria" says that it's
> unacceptable.[3]
>
> But it is a matter of regret that many (about 133 out of 356 on my
> downloaded archive-contents) GNU Emacs packages on GNU ELPA (let alone
> NonGNU ELPA and MELPA) use GitHub.  What steps should we take about
> them?  (Kicking them out of ELPA is indeed not an option.)

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.

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.

Personally, I don't prefer to interface life or work through a browser,
so the features, or lack thereof, of the Savannah Website never bothered
me. For Emms we use the mailing lists Savannah provides, Savannah's git
repo, and I try to keep an eye on irc for people commenting about
problems and improvements.

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.

-- 
   "Cut your own wood and it will warm you twice"



  parent reply	other threads:[~2022-07-06 13:58 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 [this message]
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
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=87y1x62vic.fsf@rabkins.net \
    --to=yoni@rabkins.net \
    --cc=akib@disroot.org \
    --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 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).