Call for maintainers

Joel Stanley joel at jms.id.au
Wed Oct 4 15:54:33 AEDT 2017


On Tue, Oct 3, 2017 at 11:22 AM, Chris Austen <austenc at us.ibm.com> wrote:
> The OpenBMC Project is looking for future maintainers. The amount of code
> now and expected in the near future will be more then any one person can
> continually handle. If you are a subject matter expert in a repo under
> https://github.com/openbmc or cross functional areas then taking on a role
> of maintainer might be appealing. This isn't a paid thing, this is
> completely voluntary opportunity (think Scouts without the camping or School
> volunteer without glue).
>
> So how might you go about getting this type of role on your resume? Start by
> signing up for code reviews
> https://gerrit.openbmc-project.xyz/#/q/status:open. Over the next few weeks
> we will be looking over the reviews for 1) understanding of the components
> architecture 2) Comments focusing on architecture that satisfies the needs
> of all 3) bugs 4) and more. Try to Focus on a single project.

I'd like to put forward two names of significant contributors:

For obmc-console, Jeremy Kerr. He's the author of a large amount of
the code and has helped out with a number of reivews through the 20
comments he's made.

For phsophor-mboxd, Andrew Jeffery. He's spent a lot of time reviewing
patches and helping guide the direction of the project. He's given 166
reviews, and made 207 comments.

I used https://github.com/wikimedia/analytics-gerrit-stats to generate
some of these stats. It could be used to identify other significant
contributors, even if it's simply confirming what we already know.

Cheers,

Joel


More information about the openbmc mailing list