From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: linux-raid@vger.kernel.org
Cc: Hannes Reinecke <hare@suse.de>,
Paul E Luse <paul.e.luse@linux.intel.com>,
Paul Menzel <pmenzel@molgen.mpg.de>, Song Liu <song@kernel.org>,
Kinga Tanska <kinga.tanska@linux.intel.com>,
Jes Sorensen <jes@trained-monkey.org>
Subject: Re: [RFC PATCH v3 0/1] mdadm: Change main repository to Github
Date: Wed, 15 May 2024 11:23:56 +0200 [thread overview]
Message-ID: <20240515112356.00002dfe@linux.intel.com> (raw)
In-Reply-To: <20240507153509.23451-1-mariusz.tkaczyk@linux.intel.com>
On Tue, 7 May 2024 17:35:08 +0200
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com> wrote:
> Thanks to Song and Paul, we created organization for md-raid on Github.
> This is a perfect place to maintain mdadm. I would like announce moving
> mdadm development to Github.
>
> It is already forked, feel free to explore:
> https://github.com/md-raid-utilities/mdadm
>
> Github is powerful and it has well integrated CI. On the repo, you can
> already find a pull request which will add compilation and code style
> tests (Thanks to Kinga!).
> This is MORE than we have now so I believe that with the change mdadm
> stability and code quality will be increased. The participating method
> will be simplified, it is really easy to create pull request. Also,
> anyone can fork repo with base tests included and properly configured.
>
> Note that Song and Paul are working on a per patch CI system using GitHub
> Actions and a dedicated rack of servers to enable fast container, VM and
> bare metal testing for both mdraid and mdadm. Having mdadm on GitHub will
> help with that integration.
>
> Patches sent to ML will be accepted but Github Pull Requests are
> preferred so please use mailing list only if it is necessary. I will
> setup GitHub to send email to the mailing list on each new PR so that
> everyone is still aware of pending patches via the mailing list.
>
> As a kernel.org mdadm maintainer, I will keep kernel.org repo and Github
> in-sync for both master/main branches. Although they will be kept
> in sync, developers should consider GitHub/main effective immediately
> after merging this patchset.
>
> I have strong confidence that it is good change for mdadm but I
> understand that review flow will be worse.
>
> Thanks all for comments!
>
> Cc: Hannes Reinecke <hare@suse.de>
> Cc: Paul E Luse <paul.e.luse@linux.intel.com>
> Cc: Paul Menzel <pmenzel@molgen.mpg.de>
> Cc: Song Liu <song@kernel.org>
> Cc: Kinga Tanska <kinga.tanska@linux.intel.com>
> Cc: Jes Sorensen <jes@trained-monkey.org>
>
> v2: Highlight that linux-raid@kernel.org remains as main place for
> questions and discussions.
> v3: Accept patches sent through Mailing List and missed RFC tag.
>
I'm scared that I'm doing it but I need to finish what I started.
I know that I'm pushing some of you to make it happen. I don't feel comfortable
with this but changes like this requires some self-confidence. I believe that it
is right thing to do.
This is not one way ticket, we can always take step back if after the time we
will realize that my decision was wrong or review flow is awful. There will be
adjustments for sure.
Thanks you all for helping me to make this happen. I will not push you to use
Github but I encourage you to try if you can.
Applied!
Thanks,
Mariusz
next prev parent reply other threads:[~2024-05-15 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 15:35 [RFC PATCH v3 0/1] mdadm: Change main repository to Github Mariusz Tkaczyk
2024-05-07 15:35 ` [PATCH v3 1/1] " Mariusz Tkaczyk
2024-05-14 9:00 ` [RFC PATCH v3 0/1] " Mariusz Tkaczyk
2024-05-15 9:23 ` Mariusz Tkaczyk [this message]
2024-05-15 15:23 ` Jes Sorensen
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=20240515112356.00002dfe@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=hare@suse.de \
--cc=jes@trained-monkey.org \
--cc=kinga.tanska@linux.intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=paul.e.luse@linux.intel.com \
--cc=pmenzel@molgen.mpg.de \
--cc=song@kernel.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.
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.