| Message ID | 20240507153509.23451-1-mariusz.tkaczyk@linux.intel.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | mdadm: Change main repository to Github | expand |
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 add missed RFC tag. > > Mariusz Tkaczyk (1): > mdadm: Change main repository to Github > > MAINTAINERS.md | 41 ++++++++---------------- > README.md | 86 ++++++++++++++++++++++++++++---------------------- > 2 files changed, 61 insertions(+), 66 deletions(-) > No new comments. I'm going to apply this tomorrow! Thanks, Mariusz
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
On 5/15/24 05:23, Mariusz Tkaczyk wrote: > 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. I still think this is a huge mistake, and it will only hurt the project. There has been plenty of feedback on the list supporting my view. However you own it now, if you wish to burn down the house, you are free to do so. > Applied! :( Yes I think I have a github account somewhere, however, it's been years since I last logged into it. Moving mdadm to github will not change this, I am simply not planning to make anymore contributions to this project. Good luck! Jes
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. Mariusz Tkaczyk (1): mdadm: Change main repository to Github MAINTAINERS.md | 41 ++++++++---------------- README.md | 86 ++++++++++++++++++++++++++++---------------------- 2 files changed, 61 insertions(+), 66 deletions(-)