Hi Alex, On 3/8/21 12:57 PM, Alex Bennée wrote: > > Thomas Huth <[email protected]> writes: > >> The status of the gitlab-CI files is currently somewhat confusing, and >> it is often not quite clear whether a patch should go via my tree or >> via the testing tree of Alex. That situation has grown historically... >> Initially, I was the only one using the gitlab-CI, just for my private >> repository there. But in the course of time, the gitlab-CI switched to >> use the containers from tests/docker/ (which is not part of the gitlab-CI >> section in the MAINTAINERS file), and QEMU now even switched to gitlab.com >> completely for the repository and will soon use it as its gating CI, too. >> So it makes way more sense if the gitlab-ci.yml files belong to the people >> who are owning the qemu-project on gitlab.com and take care of the gitlab >> CI there. Thus let's merge the gitlab-ci section into the common "test and >> build automation" section, > > I have no problem with this, might as well keep it all together. > >> and change the status of myself to a "reviewer" >> there instead. > > Can we not have multiple maintainers? Considering how important keeping > the testing green should be wouldn't it help to keep the bus factor > lower (not to mention holidays/breaks and just plain busy with other > things periods). It shouldn't be to hard to track as long as we mention > when we queue things to our trees?
I'm OK to be listed as backup maintainer as I do have a genuine interest in CI/testing. It will be in my scarcer personal time although, so better if another maintainers with more resources could pop up along instead. >> While we're at it, I'm also removing the line with Fam there for now, >> since he was hardly active during the last years in this area anymore. >> If he ever gets more time for this part again in the future, we surely >> can add the line back again. >> >> Signed-off-by: Thomas Huth <[email protected]> >> --- >> MAINTAINERS | 19 ++++++------------- >> 1 file changed, 6 insertions(+), 13 deletions(-)
