All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, "Thomas Huth" <thuth@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, Willian Rampazzo <wrampazz@redhat.com>,
	Wainer dos Santos Moschetta <wainersm@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section
Date: Mon, 8 Mar 2021 14:34:06 +0100	[thread overview]
Message-ID: <d451b382-c5dc-2346-a463-e95e48f205e4@amsat.org> (raw)
In-Reply-To: <878s6xam83.fsf@linaro.org>

Hi Alex,

On 3/8/21 12:57 PM, Alex Bennée wrote:
> 
> Thomas Huth <thuth@redhat.com> 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 <thuth@redhat.com>
>> ---
>>  MAINTAINERS | 19 ++++++-------------
>>  1 file changed, 6 insertions(+), 13 deletions(-)


  parent reply	other threads:[~2021-03-08 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 11:34 [PATCH] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section Thomas Huth
2021-03-08 11:57 ` Alex Bennée
2021-03-08 12:33   ` Thomas Huth
2021-03-08 15:12     ` Peter Maydell
2021-03-08 13:34   ` Philippe Mathieu-Daudé [this message]
2021-03-08 15:11     ` Thomas Huth

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=d451b382-c5dc-2346-a463-e95e48f205e4@amsat.org \
    --to=f4bug@amsat.org \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=wrampazz@redhat.com \
    /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.