Call for maintainers

[Chris Austen]

Greetings,

I received some feedback that people would like to know more about what it
takes to become, and duties of, a Maintainer in OpenBMC.

A Maintainer is a lead position in the project who is intrusted with
architecture and stability.  In return you will have a say in the future
architecture.

Steps to get there...

1) Pick a project repository that you have matured
2) Sign up for reviews in that repository without being asked
3) provide comments that correctly shape the goals of the repository
4) Be on architecture calls to learn from others
5) Contribute code
6) Contribute socially (IRC, mailing list feedback, writing articles that
end up on /. , etc)





Chris Austen
POWER Systems Enablement Manager
(512) 286-5184 (T/L: 363-5184)



From:	Chris Austen/Austin/IBM
To:	<openbmc at lists.ozlabs.org>
Date:	10/02/2017 08:52 PM
Subject:	Call for maintainers


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.

Feel free to ask any questions.

Chris Austen
POWER Systems Enablement Manager
(512) 286-5184 (T/L: 363-5184)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20171009/4a4d0c5d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20171009/4a4d0c5d/attachment.gif>