From: Ben Mezger <me@benmezger.nl>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: Why not set Emacs development workflow based on the popular git forges (GitHub, Bitbucket, Gitlab, ect)?
Date: Sat, 04 Sep 2021 11:04:42 -0300 [thread overview]
Message-ID: <m2k0jwtoxm.fsf@benmezger.nl> (raw)
In-Reply-To: <CAGP6PO+VUxYLQNL4gQAidiVneTfLH13ApcjY5_HMgQMB-8rkog@mail.gmail.com>
I don't think a follow-up in this thread is necessary, as there is a
huge thread already in place concerning this discussion, but:
> OTOH, Linux kernel [1] has already adopted GitHub as its development
> platform, which is also complete free and a classic example of
> successful free software.
Not really, no. The Linux's Github repo is only a mirror of the
repository, however, no PR, discussion happen there, and those that do
happen, are ignored.
Hongyi Zhao <hongyi.zhao@gmail.com> writes:
> On Sat, Sep 4, 2021 at 7:24 PM Po Lu <luangruo@yahoo.com> wrote:
>>
>> > Nowadays, the large software projects often conduct the development on
>> > the workflow supplied by git forges (GitHub, Bitbucket, GitLab,
>> > etc.). But it seems that Emacs is still developed directly on git, as
>> > described here [1], which makes maintaining GNU Emacs development a
>> > lot of extra work.
>>
>> GitHub, Bitbucket and GitLab require their users to run non-free
>> software, which already disqualifies them for the development of GNU
>> software.
>
> If so, I don't think there is such a complete free platform in the
> world, even the SourceHut you mentioned below, which is also operated,
> at least in part, as a commercial product. OTOH, Linux kernel [1] has
> already adopted GitHub as its development platform, which is also
> complete free and a classic example of successful free software.
>
>> There was recently a discussion (perhaps it is still in progress? I
>> don't know) about moving to SourceHut, but I don't think it's gone
>> anywhere. The problem seems to be that the present system exists and
>> works, while nobody has sat down and completed the work required to
>> migrate to a new one.
>
> I can't say anything. Almost all Emacs developers and users are
> excellent programmers/scientists/engineers. But excellent people also
> have their own beliefs, quirks and their inner bottom line. Sometimes
> it may not be consistent with the prevailing trend, just like the
> existence of Emacs itself.
>
>> Would you like to volunteer? :D
>
> Technically speaking, I think there are so many guys in Emacs
> community have enough ability to do this.
>
> [1] https://github.com/torvalds/linux
>
> Best, Hongyi
--
Kind regards,
Met een vriendelijke groet,
Atenciosamente,
Ben Mezger
https://seds.nl
https://github.com/benmezger
prev parent reply other threads:[~2021-09-04 14:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 6:55 Why not set Emacs development workflow based on the popular git forges (GitHub, Bitbucket, Gitlab, ect)? Hongyi Zhao
2021-09-04 7:13 ` tomas
2021-09-04 11:24 ` Po Lu
2021-09-04 11:34 ` tomas
2021-09-04 11:38 ` Po Lu
2021-09-04 12:11 ` tomas
2021-09-04 12:51 ` Po Lu
2021-09-04 12:50 ` Hongyi Zhao
2021-09-04 13:28 ` Po Lu
2021-09-05 0:56 ` Hongyi Zhao
2021-09-05 3:16 ` Po Lu
2021-09-05 4:29 ` Hongyi Zhao
2021-09-05 7:34 ` Po Lu
2021-09-05 8:02 ` Hongyi Zhao
2021-09-06 1:06 ` Po Lu
2021-09-04 13:47 ` Kévin Le Gouguec
2021-09-04 13:58 ` Hongyi Zhao
2021-09-04 23:25 ` Philip Kaludercic
2021-09-07 15:09 ` Max Nikulin
2021-09-08 2:02 ` Po Lu
2021-09-08 17:34 ` Max Nikulin
2021-09-08 22:49 ` Tim Cross
2021-09-09 6:12 ` Eli Zaretskii
2021-09-10 3:39 ` Richard Stallman
2021-09-16 17:24 ` Max Nikulin
2021-09-16 21:03 ` chad
2021-09-19 17:01 ` Max Nikulin
2021-09-08 17:38 ` Dmitry Gutov
2021-09-04 14:04 ` Ben Mezger [this message]
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=m2k0jwtoxm.fsf@benmezger.nl \
--to=me@benmezger.nl \
--cc=emacs-devel@gnu.org \
--cc=hongyi.zhao@gmail.com \
--cc=luangruo@yahoo.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.