From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Siqueira Jordao <rjordrigo@amd.com>,
Petri Latvala <petri.latvala@intel.com>,
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Cc: Qingqing Zhuo <qingqing.zhuo@amd.com>,
igt-dev@lists.freedesktop.org,
Solomon Chiu <solomon.chiu@amd.com>,
Sean Paul <seanpaul@chromium.org>,
Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>,
Mark Yacoub <markyacoub@google.com>
Subject: Re: [igt-dev] [RFC i-g-t 1/1] MAINTAINERS: Introduce MAINTAINERS file
Date: Mon, 07 Feb 2022 14:31:03 +0200 [thread overview]
Message-ID: <87sfsurh88.fsf@intel.com> (raw)
In-Reply-To: <3af10091-6a1f-0d13-944f-7f7833837e1e@amd.com>
On Thu, 03 Feb 2022, Rodrigo Siqueira Jordao <rjordrigo@amd.com> wrote:
> On 2022-02-03 6:03 a.m., Petri Latvala wrote:
>> On Mon, Jan 31, 2022 at 09:28:18AM -0500, Rodrigo Siqueira wrote:
>>> IGT is growing in terms of new vendors actively using it. Right now, we
>>> only have Intel CI to validate new patches, which can create a situation
>>> where bugs get accidentally introduced to other vendors. To alleviate
>>> this problem and also making easy for other developers to be aware of
>>> some specific changes, I'm proposing the introduction of the MAINTAINERS
>>> file as the one used in the Linux kernel. With this approach, we can
>>> have multiple enginers from different companies as reviewers for
>>> specific tests, and contributors should use get_maintainers script to
>>> find the right people to address their changes.
>>>
>>> Cc: Arkadiusz Hiler <arek@hiler.eu>
>>> Cc: Petri Latvala <petri.latvala@intel.com>
>>> Cc: Mark Yacoub <markyacoub@google.com>
>>> Cc: Jessica Zhang <quic_jesszhan@quicinc.com>
>>> Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
>>> Cc: Melissa Wen <mwen@igalia.com>
>>> Cc: Sean Paul <seanpaul@chromium.org>
>>> Cc: Harry Wentland <harry.wentland@amd.com>
>>> Cc: Sun Peng Li(Leo) <sunpeng.li@amd.com>
>>> Cc: Chao-kai Wang (Stylon) <stylon.wang@amd.com>
>>> Cc: Wayne Lin <wayne.lin@amd.com>
>>> Cc: Nicholas Choi <nicholas.choi@amd.com>
>>> Cc: Martin Peres <martin.peres@mupuf.org>
>>> Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
>>> Cc: Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
>>> Cc: Qingqing Zhuo (Lilian) <qingqing.zhuo@amd.com>
>>> Cc: Solomon Chiu <solomon.chiu@amd.com>
>>> Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
>>
>>
>> A tentative ack on this effort from me, for getting more contact
>> points formally documented.
>>
>> As for the implementation of it, I know this is copied from the kernel
>> so I know the reason why they're there, but reduce the useless
>> complexity in the documentation comment like the type of version
>> control in a subtree, and things that just aren't true for IGT, like
>> asking for testing from 4 or 5 people.
>
> Hi Petri,
>
> Thanks for your feedback. I just copy-paste most parts of this kernel
> MAINTAINERs file since this is just a prototype. I will prepare the
> first version of this patch and submit it again; in this new version, I
> will drop some part of the documentation which does not make sense for IGT.
FWIW, if I were to do this, I'd do it in yaml and implement it in
python+strictyaml with a schema. No need to import a monster perl parser
from kernel or implement our own.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-02-07 12:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 14:28 [igt-dev] [RFC i-g-t 0/1] Introduce MAINTAINERS file to IGT Rodrigo Siqueira
2022-01-31 14:28 ` [igt-dev] [RFC i-g-t 1/1] MAINTAINERS: Introduce MAINTAINERS file Rodrigo Siqueira
2022-02-03 11:03 ` Petri Latvala
2022-02-03 14:35 ` Harry Wentland
2022-02-03 18:56 ` Rodrigo Siqueira Jordao
2022-02-07 12:31 ` Jani Nikula [this message]
2022-03-02 12:09 ` Petri Latvala
2022-03-02 12:56 ` Jani Nikula
2022-03-16 13:10 ` Rodrigo Siqueira Jordao
2022-03-16 13:29 ` Petri Latvala
2022-03-16 13:39 ` Jani Nikula
2022-01-31 15:11 ` [igt-dev] [RFC i-g-t 0/1] Introduce MAINTAINERS file to IGT Sean Paul
2022-01-31 18:19 ` Mark Yacoub
2022-02-03 9:18 ` Petri Latvala
2022-02-02 16:23 ` Harry Wentland
2022-01-31 15:12 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-01-31 16:19 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-03 12:50 ` [igt-dev] [RFC i-g-t 0/1] " Melissa Wen
2022-02-03 18:59 ` Rodrigo Siqueira Jordao
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=87sfsurh88.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=bhawanpreet.lakha@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=markyacoub@google.com \
--cc=petri.latvala@intel.com \
--cc=qingqing.zhuo@amd.com \
--cc=rjordrigo@amd.com \
--cc=seanpaul@chromium.org \
--cc=solomon.chiu@amd.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.