From: Hannes Reinecke <hare@suse.de>
To: Yu Kuai <yukuai1@huaweicloud.com>,
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>,
Wols Lists <antlists@youngman.org.uk>
Cc: Paul E Luse <paul.e.luse@linux.intel.com>,
John Stoffel <john@stoffel.org>,
linux-raid@vger.kernel.org, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: Move mdadm development to Github
Date: Tue, 30 Apr 2024 13:15:18 +0200 [thread overview]
Message-ID: <85f74f83-bd1b-439d-874c-b3a38bdd2d71@suse.de> (raw)
In-Reply-To: <38770f23-92da-09a6-227f-11f1176294e2@huaweicloud.com>
On 4/30/24 11:26, Yu Kuai wrote:
> Hi,
>
> 在 2024/04/26 16:22, Mariusz Tkaczyk 写道:
>> On Fri, 26 Apr 2024 08:27:44 +0100
>> Wols Lists <antlists@youngman.org.uk> wrote:
>>
>>> On 24/04/2024 13:27, Paul E Luse wrote:
>>>> * Instead of using the mailing list to propose patches, use GitHub Pull
>>>> Requests. Mariusz is setting up GitHub to send an email to the
>>>> mailing
>>>> list so that everyone can still be made aware of new patches in the
>>>> same manner as before. Just use GitHub moving forward for actual
>>>> code reviews.
>>>
>>> Does that mean contributors now need a github account? That won't go
>>> down well with some people I expect ...
>>>
>>> Cheers,
>>> Wol
>>
>> Hi Wol,
>>
>> There are thousands repositories on Github you have to register to
>> participate
>> and I don't believe that Linux developers may don't have Github
>> account. It is
>> almost impossible to not have a need to sent something to Github.
>
> Will it still be able to send and apply patches through maillist? It's
> important for us because I just can't create pr at GitHub in my
> company, already tried with Paul, due to our company policy. :(
> Although I can do this at home...
>
I do think this is a valid point.
(Having been in Beijing recently I do share the pain from Kuai :-)
We really should keep the mailing list alive, and enable people
to choose which interface suits them best.
I don't have a problem in switching to github as the primary
tree, but we should keep the original location intact as a
mirror and continue to allow people to use the mailing list
to send patches.
This is especially important for low-volume mailing lists,
where we have quite a few occasional contributors, and we
should strive to make it as easy (and convenient) as possible
for them.
Cheers,
Hannes
>>
>> Here some examples:
>> https://github.com/iovisor/bcc
>> https://github.com/axboe/fio
>> https://github.com/dracutdevs/dracut
>> https://github.com/util-linux/util-linux
>> https://github.com/bpftrace/bpftrace
>> https://github.com/systemd/systemd
>>
>> I see this as not a problem.
>>
>> Thanks,
>> Mariusz
>>
>> .
>>
>
>
next prev parent reply other threads:[~2024-04-30 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 6:41 Move mdadm development to Github Mariusz Tkaczyk
2024-04-24 12:37 ` Phil Turmel
2024-04-25 21:04 ` John Stoffel
2024-04-24 12:27 ` Paul E Luse
2024-04-26 7:27 ` Wols Lists
2024-04-26 8:22 ` Mariusz Tkaczyk
2024-04-26 10:36 ` Christoph Hellwig
2024-04-27 3:25 ` David Niklas
2024-04-30 9:26 ` Yu Kuai
2024-04-30 11:15 ` Hannes Reinecke [this message]
2024-04-30 20:22 ` Wol
2024-05-06 10:01 ` Mariusz Tkaczyk
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=85f74f83-bd1b-439d-874c-b3a38bdd2d71@suse.de \
--to=hare@suse.de \
--cc=antlists@youngman.org.uk \
--cc=john@stoffel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=paul.e.luse@linux.intel.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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.
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.