From: Max Nikulin <manikulin@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Why not set Emacs development workflow based on the popular git forges (GitHub, Bitbucket, Gitlab, ect)?
Date: Tue, 7 Sep 2021 22:09:30 +0700 [thread overview]
Message-ID: <sh7vbc$3pv$1@ciao.gmane.io> (raw)
In-Reply-To: <87y28ctpuo.fsf@gmail.com>
On 04/09/2021 20:47, Kévin Le Gouguec wrote:
> Hongyi Zhao writes:
>
>> 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.
>>
>> [1] https://github.com/torvalds/linux
>
> FTR: this is a read-only mirror. As the helpful bot that answers every
> pull request there says:
>
>> Linux kernel development happens on mailing lists, rather than on
>> GitHub - this GitHub repository is a read-only mirror that isn't used
>> for accepting contributions. So that your change can become part of
>> Linux, please email it to us as a patch.
There is a technical reason why github is not suitable for Linux kernel
(and it is hardly to applicable to Emacs): it is impossible to
coordinate several groups of developers responsible for different
subsystems using github flavor of pull requests and bugs. For email it
is simply several Cc addresses:
Daniel Vetter. Why Github can't host the Linux Kernel Community. August
8, 2017
https://blog.ffwll.ch/2017/08/github-why-cant-host-the-kernel.html
Though such reasons were not discussed in Microsoft's proposal to use
"modern" approach for Linux development:
Relying on plain-text email is a 'barrier to entry' for kernel
development, says Linux Foundation board member. Interview with Sarah
Novotny. 2020-08-25
https://www.theregister.com/2020/08/25/linux_kernel_email/
These links are intended just to show that various project may have
quite different reasons to resist development on github/gitlab despite
some demand. I hope, it will not cause Microsoft & Linux flame here.
next prev parent reply other threads:[~2021-09-07 15:09 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 [this message]
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
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='sh7vbc$3pv$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--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).