BMC/OpenBmc/bmcweb.git/OWNERS, branch master

OWNERS: add myself as a reviewer

2026-09-28T05:31:51+00:00

Add myself to the bmcweb OWNERS file as a reviewer. I have been actively contributing to and reviewing bmcweb changes for more than two months. Contributions: [1] Reviews: [2] [1] https://github.com/openbmc/bmcweb/commits?author=joel-pj [2] https://gerrit.openbmc.org/q/reviewer:joelpj@ami.com Change-Id: Ibf0b3dac335aa4f76ed44b94e2fba25b75f68b04 Signed-off-by: Joel Pullokaran Jesin

OWNERS: add myself as a reviewer

2026-09-26T05:13:34+00:00

Add myself to the bmcweb OWNERS file as a reviewer. Contributions: [1][2] [1] https://github.com/openbmc/bmcweb/commits?author=Yuvakumar-Selvamani [2] https://gerrit.openbmc.org/q/owner:yuvakumars@ami.com Change-Id: Ic5f82102d6883d7de2e5725e410ab62f45fb77e7 Signed-off-by: Yuvakumar Selvamani

OWNERS: prune inactive members

2026-07-31T18:21:09+00:00

Enforce the policy[1] which requires that subproject maintainers are only list developers who have been active in the project. Removed developers that have not been active per that policy from OWNERS. [1]: https://github.com/openbmc/docs/commit/1b531cd0d861d9c1d9ff81fb782e43f15c3c48d9 Change-Id: I752a375a9f080ce4809387405c7ac8b245825145 Signed-off-by: Patrick Williams

OWNERS: Update Gunnar's email address

2024-02-21T17:39:58+00:00

I have multiple email addresses in my Gerrit account but as https://gerrit.openbmc.org/c/openbmc/bmcweb/+/69506 shows my Preferred email has to match the OWNERS file, do that. More discussion in Discord at [1] https://discord.com/channels/775381525260664832/817151035197358081/1209585278025601094 Change-Id: I94ba5bd8d9c2a3c23314aae051b3a083562e43cb Signed-off-by: Gunnar Mills

Remove reference to phosphor-webui

2023-06-30T21:02:48+00:00

phosphor-webui has been replaced by webui-vue. It has been proposed to archive it, no point in referencing it or requiring knowledge of it to be a maintainer. Tested: None. Doc change only. Change-Id: I3fab9eff7960174815cfc822abbb4e0d3f970a5c Signed-off-by: Gunnar Mills

Removed myself from OWNERS file

2023-04-28T19:23:04+00:00

Reason: I will be leaving OpenBmc project soon. Change-Id: I726eaafe38a15636fd855b591bb73b5c62108a5a Signed-off-by: Krzysztof Grobelny

OWNERS: fix minor path issue

2022-11-17T16:15:46+00:00

It's |log_services| not |log_service|. Signed-off-by: Nan Zhou Change-Id: Ic504a3fcc5b69ce4a05de943ebf0d6c95fbdcda4

OWNERS: fix syntax

2022-11-09T18:53:24+00:00

The existing config is missing owners in exact match. Also, onwers have to be array of strings. Reference: [1] https://gerrit.googlesource.com/plugins/owners/+/refs/heads/master/config.md Signed-off-by: Nan Zhou Change-Id: Ic9639f5e6c83d4dee947c3fddc48de43f0d6aa61

OWNERS: nanzhou can own query codes

2022-08-19T20:19:06+00:00

I developed a fair amount of the query parameter codes and had a fair understanding of how it works, what the next steps are, how to review related codes, how to test it. Thus, propose that I own these codes. Signed-off-by: Nan Zhou Change-Id: I9c5a4ca5f7d569f3523afb3d97aa367f46314220

Section out the maintainership of bmcweb

2022-08-17T17:26:19+00:00

As bmcweb grows, it's important that we distribute the load amongst the available community. This commit pivots slightly from our usual process of giving full repo maintainership to a small list of one or two people, and instead proposes passing out smaller pieces of maintainership. The hope is that over time, these maintainers can grow into owning larger portions of the stack. In this way, we can increase our breadth of available maintainers for the things that are straightforward, like adding new redfish schemas or doing migrations, while still keeping a few core maintainers responsible for the core. I've reached out to both Krzysztof and Nan, and asked them which pieces they feel that they're comfortable maintaining, and I've added all components they listed to the OWNERS files. Each has a track record of doing reviews in upstream, and given that Gunnar and myself will still be present and active, this seems like a good thing for the project overall. The specific sections of maintainership for each person is laid out in the OWNERS file, and we can modify over time as each person gets more experience in reviewing and testing. The expectations are that for the files explicitly listed, these new maintainers will be able to handle all reviews that touch those sections of functionality (including reviews not yet merged). Please continue to communicate as you have previously. To those being added, it is expected that if there are core issues brought up in the modules that you maintain, you escalate them to the entire group of maintainers, and remain active on our communication channels. In the past, we've had significant issues where individual modules tried to implement generalized solutions in a handler-specific way, and while most of that has been cleaned up, it caused significant thrash. Lets try to avoid that going forward. I look forward to working with both of you more. Change-Id: I7750a12703af68fc82f84a0e22496dabca582208 Signed-off-by: Ed Tanous