RFC Introduce MAINTAINERS file to IGT
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest1 patch 15 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | MAINTAINERS: Introduce MAINTAINERS fileMAINTAINERS | +201 | 9 replies |
Reviews trailers per patch
The patch has no Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Harry Wentland | Melissa Wen |
|---|---|---|
| Series | A-b | A-b |
| 1/1 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [igt-dev] [RFC i-g-t 0/1] Introduce MAINTAINERS file to IGT
Hi,
IGT is becoming more generic, and multiple vendors are adopting it. For example, AMD fully upstream all of its internal changes last year, and now we are relying on IGT from the upstream. Additionally, thanks to the ChromeOS project, we have other vendors working on the KMS tests as well. At this point, I believe that we need some mechanism to better contact developers that care about some specific tests or even provide an easy way for other people to find the right stakeholder for dealing with some particular issue.
Imho Linux Kernel already has a good solution codified in the MAINTAINERS and get_maintainers files. One of the best things about this approach was adding reviewers and maintainers (and other options) to the specific part of the code and using the get_maintainers tool to extract the right people to be part of the series. With this idea in mind, I created this RFC that introduces the MAINTAINERS file in IGT, and I have already added some entries to this file. My approach was:
* Petri and Hiler are the maintainers, and for this reason, their contact will be displayed for every patch.
* I add Mark Yacoub as a reviewer for every KMS test.
* I added some AMD folks as reviewers in some specific KMS tests that we run in our CI.
* I added some AMD maintainers to amdgpu tests.
If you want to try it in your local repository, you will need the get_maintainers script from the Linux kernel, and you can use this command:
perl /PATH/TO/get_maintainer.pl --no-tree --separator , --nokeywords --nogit --nogit-fallback --norolestats -f <TARGET_TEST>
Anyway, this is just an idea that I want to discuss with the community. What do you think about having a MAINTAINERs file? Do you want to add your name as a reviewer to some specific test if you like the idea? Any other comments or ideas?
Best Regards,
Siqueira
Rodrigo Siqueira (1):
MAINTAINERS: Introduce MAINTAINERS file
MAINTAINERS | 203 +++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 201 insertions(+), 2 deletions(-)
Signature · 1 line
2.25.1