Re: [PATCH 0/1] Move mdadm development to Github

[Jes Sorensen <jes@trained-monkey.org>]

Sorry for the obnoxious top posting, not near a computer right now. 

This was not meant as a signed-off-by, but rather I'm signing off the project. 

Good luck 

Sent from MailDroid

-----Original Message-----
From: Paul E Luse <paul.e.luse@linux.intel.com>
To: Jes Sorensen <jes@trained-monkey.org>
Cc: linux-raid@vger.kernel.org, Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>, Song Liu <song@kernel.org>, Kinga Tanska <kinga.tanska@linux.intel.com>
Sent: Mon, 29 Apr 2024 23:40
Subject: Re: [PATCH 0/1] Move mdadm development to Github

On Mon, 29 Apr 2024 22:52:46 -0400
Jes Sorensen <jes@trained-monkey.org> wrote:

> Disappointed to see this :(
> 
> The github interface is not a favorite. Mailing lists are the way
> open source projects work.
> 
> I haven't had much time to contribute for quite a while now and
> probably won't in the near future. Given this decision was made
> without my involvement, I'll sign off.
> 
> Jes 
> 

Applaud the decision to 'sign off' despite personal preferences. I am
confident if things start going in the wrong direction that Mariusz
will course correct accordingly.

Thanks Jes :)

-Paul

> 
> -----Original Message-----
> From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
> To: linux-raid@vger.kernel.org
> Cc: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>, Paul E Luse
> <paul.e.luse@linux.intel.com>, Song Liu <song@kernel.org>, Kinga
> Tanska <kinga.tanska@linux.intel.com>, Jes Sorensen
> <jes@trained-monkey.org> Sent: Fri, 19 Apr 2024 5:39 Subject: [PATCH
> 0/1] Move mdadm development to Github
> 
> 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.
> 
> As a result of moving to GitHub, we will no longer be using mailing
> list to propose patches, we will be using GitHub Pull Requests (PRs).
> As the community adjusts to using PRs I will be setting up
> auto-notification for those who attempt to use email for patches to
> let them know that we now use PRs.  I will also 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.
> 
> Please let me know if you have questions of other suggestions.
> 
> 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 will wait at least one week with merge to gather feedback and
> resolve objections. Feel free to ask.
> 
> Cc: Paul E Luse <paul.e.luse@linux.intel.com>
> Cc: Song Liu <song@kernel.org>
> Cc: Kinga Tanska <kinga.tanska@linux.intel.com>
> Cc: Jes Sorensen <jes@trained-monkey.org>
> 
> Mariusz Tkaczyk (1):
>   mdadm: Change main repository to Github
> 
>  MAINTAINERS.md | 41 +++++++++++----------------------
>  README.md      | 61
> ++++++++++++++++++++------------------------------ 2 files changed,
> 37 insertions(+), 65 deletions(-)
>