maintainership of fstests
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 5 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
Thanks for your long time contribution! Even after you leave Red Hat, you still try to keep weekly updating, I don't know how to express my gratitude for that. Rich blessing to you and your family!
Thanks,
Zorro
Quoted 23 lines
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 6 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
Quoted 8 lines
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Hi Eryu,
By thinking about it a while, I get up my courage to apply this job, although I know I'm not the best one can handle this job. Just this project is really useful for my team. Nearly from I joined Red Hat, my jobs started to around the xfstests. It's a great testsuit, which can cover most of our testing. I felt relieved when you toke this maintainer, and admired your courage at that time, that really helps us a lot. No matter what you decide, thanks again for all your help, as previous colleague, as friend.
Thanks,
Zorro
Quoted 14 lines
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 6 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
Quoted 8 lines
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Thank you for your service for all that time! :)
Quoted 5 lines
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Splitting responsibility for maintenance doesn't seem like a huge step to me -- for fs-specific tests, we need the developers for that fs to review test changes. Review for tests/generic/ can be done by the fs{devel,*} community at large, much as it is done now.
The /difficult/ part, I think, is handling things like treewide reorganizations, and integration testing the test suite. That, I think, is what really requires a primary maintainer who has broader visibility into what's going on.
That primary maintainer also has to have time to run a build-and-test farm of all the major fstests clients (ext*, xfs, btrfs, overlay, nfs, what else?) to make sure that new code doesn't break existing filesystems' ability to test themselves.
Granted, (speaking only for XFS, probably btrfs, and maybe even ext*), we seem to notice regressions pretty fast when we download the weekly release, so I think the primary maintainer's focus probably ought to be more towards the non-mainstream Linux filesystems.
Also: over the past 6 years, I have /really/ enjoyed the fact that fstests has small releases every 1-2 weeks as opposed to larger infrequent drops. It's a relief not to have to chase a merge window like I do for the kernel. Thank you a bunch for keeping that going!
--D
FYI: It's Spring Break here in the US, so you might not get much of a response for a week or two.
Quoted 7 lines
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 18 lines · Zorro Lang
Quoted 6 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
Quoted 8 lines
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Hi Eryu,
Quoted 7 lines
By thinking about it a while, I get up my courage to apply this job, although I know I'm not the best one can handle this job. Just this project is really useful for my team. Nearly from I joined Red Hat, my jobs started to around the xfstests. It's a great testsuit, which can cover most of our testing. I felt relieved when you toke this maintainer, and admired your courage at that time, that really helps us a lot. No matter what you decide, thanks again for all your help, as previous colleague, as friend.
Hi Zorro - I'm sure that you would do well as a new maintainer, even if it requires some learning. Every new challenge requires learning. :) If you are able to balance it with your other tasks, I would be happy to see you take this on, if it's something you want to do.
(See also Darrick's suggestion that maintainer tasks could be split up a bit, across the different filesystems.)
Thanks,
-Eric
Quoted 18 lines
Thanks,
ZorroQuoted 14 lines
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 27 lines · Eric Sandeen
Quoted 18 lines · Zorro Lang
Quoted 6 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
Quoted 8 lines
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Hi Eryu,
Quoted 7 lines
By thinking about it a while, I get up my courage to apply this job, although I know I'm not the best one can handle this job. Just this project is really useful for my team. Nearly from I joined Red Hat, my jobs started to around the xfstests. It's a great testsuit, which can cover most of our testing. I felt relieved when you toke this maintainer, and admired your courage at that time, that really helps us a lot. No matter what you decide, thanks again for all your help, as previous colleague, as friend.
Quoted 7 lines
Hi Zorro - I'm sure that you would do well as a new maintainer, even if it requires some learning. Every new challenge requires learning. :) If you are able to balance it with your other tasks, I would be happy to see you take this on, if it's something you want to do.
(See also Darrick's suggestion that maintainer tasks could be split up a bit, across the different filesystems.)
Thanks for your trust, Eric. As you said, it'll be a challenge to me, but I'll try my best if I can have this opportunity.
Thanks,
Zorro
Quoted 23 lines
Thanks,
-EricQuoted 18 lines
Thanks,
ZorroQuoted 14 lines
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 33 lines · Zorro Lang
Quoted 32 lines · Eric Sandeen
Quoted 18 lines · Zorro Lang
Quoted 6 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
Quoted 8 lines
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Hi Eryu,
Quoted 7 lines
By thinking about it a while, I get up my courage to apply this job, although I know I'm not the best one can handle this job. Just this project is really useful for my team. Nearly from I joined Red Hat, my jobs started to around the xfstests. It's a great testsuit, which can cover most of our testing. I felt relieved when you toke this maintainer, and admired your courage at that time, that really helps us a lot. No matter what you decide, thanks again for all your help, as previous colleague, as friend.
Hi Zorro - I'm sure that you would do well as a new maintainer, even if it requires some learning. Every new challenge requires learning. :) If you are able to balance it with your other tasks, I would be happy to see you take this on, if it's something you want to do.
Quoted 5 lines
Quoted 2 lines
(See also Darrick's suggestion that maintainer tasks could be split up a bit, across the different filesystems.)
Thanks for your trust, Eric. As you said, it'll be a challenge to me, but I'll try my best if I can have this opportunity.
Go for it!!!!1!!
--D
Quoted 27 lines
Thanks,
ZorroQuoted 23 lines
Thanks,
-EricQuoted 18 lines
Thanks,
ZorroQuoted 14 lines
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 33 lines · Zorro Lang
Quoted 32 lines · Eric Sandeen
Quoted 18 lines · Zorro Lang
Quoted 6 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
Quoted 8 lines
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Hi Eryu,
Quoted 7 lines
By thinking about it a while, I get up my courage to apply this job, although I know I'm not the best one can handle this job. Just this project is really useful for my team. Nearly from I joined Red Hat, my jobs started to around the xfstests. It's a great testsuit, which can cover most of our testing. I felt relieved when you toke this maintainer, and admired your courage at that time, that really helps us a lot. No matter what you decide, thanks again for all your help, as previous colleague, as friend.
Hi Zorro - I'm sure that you would do well as a new maintainer, even if it requires some learning. Every new challenge requires learning. :) If you are able to balance it with your other tasks, I would be happy to see you take this on, if it's something you want to do.
Quoted 5 lines
Quoted 2 lines
(See also Darrick's suggestion that maintainer tasks could be split up a bit, across the different filesystems.)
Thanks for your trust, Eric. As you said, it'll be a challenge to me, but I'll try my best if I can have this opportunity.
Awesome!! :)
-ritesh
Quoted 34 lines · Zorro Lang
Quoted 32 lines · Eric Sandeen
Quoted 18 lines · Zorro Lang
Quoted 6 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
Quoted 8 lines
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Hi Eryu,
Quoted 7 lines
By thinking about it a while, I get up my courage to apply this job, although I know I'm not the best one can handle this job. Just this project is really useful for my team. Nearly from I joined Red Hat, my jobs started to around the xfstests. It's a great testsuit, which can cover most of our testing. I felt relieved when you toke this maintainer, and admired your courage at that time, that really helps us a lot. No matter what you decide, thanks again for all your help, as previous colleague, as friend.
Hi Zorro - I'm sure that you would do well as a new maintainer, even if it requires some learning. Every new challenge requires learning. :) If you are able to balance it with your other tasks, I would be happy to see you take this on, if it's something you want to do.
Quoted 5 lines
Quoted 2 lines
(See also Darrick's suggestion that maintainer tasks could be split up a bit, across the different filesystems.)
Thanks for your trust, Eric. As you said, it'll be a challenge to me, but I'll try my best if I can have this opportunity.
As his colleague, I see Zorro's great passion, effort and professional in the fs area. It's great to me that Zorro goes for this position.
-Boyang
Quoted 28 lines
Thanks,
ZorroQuoted 23 lines
Thanks,
-EricQuoted 18 lines
Thanks,
ZorroQuoted 14 lines
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 22 lines · Darrick J. Wong
Quoted 6 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
Quoted 8 lines
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Thank you for your service for all that time! :)
Quoted 4 lines
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
Quoted 6 lines
Quoted 1 line
What do you think?
Splitting responsibility for maintenance doesn't seem like a huge step to me -- for fs-specific tests, we need the developers for that fs to review test changes. Review for tests/generic/ can be done by the fs{devel,*} community at large, much as it is done now.
Agreed.
Quoted 5 lines
The /difficult/ part, I think, is handling things like treewide reorganizations, and integration testing the test suite. That, I think, is what really requires a primary maintainer who has broader visibility into what's going on.
Agreed.
Quoted 5 lines
That primary maintainer also has to have time to run a build-and-test farm of all the major fstests clients (ext*, xfs, btrfs, overlay, nfs, what else?) to make sure that new code doesn't break existing filesystems' ability to test themselves.
Yes, that's what I did when I was at RH, I ran regression tests on all major filesystems and on all major arches (x86_64 ppc64(le) aarch64) before pushing new patches to git repo to make sure the new release is in good shape.
And that's the problem for me now, as I don't have such machine resource anymore.. And that's what Zorro has now :)
Quoted 10 lines
Granted, (speaking only for XFS, probably btrfs, and maybe even ext*), we seem to notice regressions pretty fast when we download the weekly release, so I think the primary maintainer's focus probably ought to be more towards the non-mainstream Linux filesystems.
Also: over the past 6 years, I have /really/ enjoyed the fact that fstests has small releases every 1-2 weeks as opposed to larger infrequent drops. It's a relief not to have to chase a merge window like I do for the kernel. Thank you a bunch for keeping that going!
Thanks for all the help and reviews all these years!
Thanks,
Eryu
Quoted 13 lines
--D
FYI: It's Spring Break here in the US, so you might not get much of a response for a week or two.
Quoted 7 lines
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 11 lines · Zorro Lang
Quoted 10 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
Quoted 8 lines
Quoted 4 lines
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Hi Eryu,
By thinking about it a while, I get up my courage to apply this job, although I
Glad to hear that! I'm sure you can do it well!
I'll talk to you to see how to make the transfor of maintainer go smoothly.
Thanks,
Eryu
Quoted 25 lines
know I'm not the best one can handle this job. Just this project is really useful for my team. Nearly from I joined Red Hat, my jobs started to around the xfstests. It's a great testsuit, which can cover most of our testing. I felt relieved when you toke this maintainer, and admired your courage at that time, that really helps us a lot. No matter what you decide, thanks again for all your help, as previous colleague, as friend.
Thanks,
ZorroQuoted 14 lines
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.
Quoted 17 lines · Eryu Guan
Quoted 16 lines · Zorro Lang
Quoted 14 lines · Eryu Guan
Hi folks,
It's almost 6 years since I've taken the maintainership of fstests, and I tried my best to keep the pace of weekly update, or at least bi-weekly update due to something like public holidays.
But it's been a month since last fstests update due to my personal urgent issues, and some patches got no review for more than one month. So I think it's time to re-consider the maintainership of fstests.
I will have less spare time in the foreseeable future, as I have to spend more time on my family, so it's hard to keep the weekly update pace. And six years is a long time, I think it's time to have a new maintainer.
Quoted 7 lines
Quoted 3 lines
Hi Eryu,
By thinking about it a while, I get up my courage to apply this job, although I
Glad to hear that! I'm sure you can do it well!
I'll talk to you to see how to make the transfor of maintainer go smoothly.
Yeah... if you already have a kernel.org account, then you can ignore the rest of this email. :P
First you'll need a *stable* email service of some kind -- this MicXXXXXX crap that increasing numbers of us are being forced to use by corporate IT is not going to cut it. Contributing to the gmXXX-vger mail delay swamp isn't great either. :/
Then you'll need to create a PGP key and get enough of us who already have kernel.org accounts (Eryu, dchinner, me, sandeen, hch, etc.) to sign it to convince the kernel.org admins that you're legit; and so that you can push signed tags to the git tree. I didn't get any hits in pgp.mit.edu or the kernel keysigning map, so I'm presuming you don't already have one...
In the old days a signing party was easy enough when we could do that in person at LSFMM/LinuxCon/etc, but now ... I don't know what the verification process is.
Next you'll want a kernel.org account so that you can push branches to git.kernel.org. You'll also have to ask them to add you to the group that has write access to the fstests repo:
https://korg.docs.kernel.org/accounts.html
In the meantime, if you need help pushing branches, I think at least Eric, Dave, and I all should still have write access.
Anyways, welcome Zorro!
--D
Quoted 28 lines
Thanks,
EryuQuoted 25 lines
know I'm not the best one can handle this job. Just this project is really useful for my team. Nearly from I joined Red Hat, my jobs started to around the xfstests. It's a great testsuit, which can cover most of our testing. I felt relieved when you toke this maintainer, and admired your courage at that time, that really helps us a lot. No matter what you decide, thanks again for all your help, as previous colleague, as friend.
Thanks,
ZorroQuoted 14 lines
Or we could go to the group-maintain way? As Darrick mentioned before (for xfs not fstests, if I recall correctly). Then we need a new primary maintainer :)
What do you think?
Thanks,
Eryu
P.S.
I'll keep the maintainer role and do the review & update as usual until all things settle down.