<html><body><p><font size="2">Greetings, </font><br><br><font size="2">I received some feedback that people would like to know more about what it takes to become, and duties of, a Maintainer in OpenBMC.</font><br><br><font size="2">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. </font><br><br><font size="2">Steps to get there...</font><br><br><font size="2">1) Pick a project repository that you have matured</font><br><font size="2">2) Sign up for reviews in that repository without being asked</font><br><font size="2">3) provide comments that correctly shape the goals of the repository</font><br><font size="2">4) Be on architecture calls to learn from others</font><br><font size="2">5) Contribute code</font><br><font size="2">6) Contribute socially (IRC, mailing list feedback, writing articles that end up on /. , etc) </font><br><font size="2"> </font><br><br><br><br><font size="2"><br>Chris Austen<br>POWER Systems Enablement Manager <br>(512) 286-5184 (T/L: 363-5184)</font><br><br><img width="16" height="16" src="cid:1__=09BB0B26DF9076838f9e8a93df938690918c09B@" border="0" alt="Inactive hide details for Chris Austen---10/02/2017 08:52:46 PM---The OpenBMC Project is looking for future maintainers. The a"><font size="2" color="#424282">Chris Austen---10/02/2017 08:52:46 PM---The OpenBMC Project is looking for future maintainers. The amount of code now and expected in the n</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Chris Austen/Austin/IBM</font><br><font size="2" color="#5F5F5F">To: </font><font size="2"><openbmc@lists.ozlabs.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">10/02/2017 08:52 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Call for maintainers</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><font size="2">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 </font><a href="https://github.com/openbmc"><font size="2">https://github.com/openbmc</font></a><font size="2"> 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). </font><br><br><font size="2">So how might you go about getting this type of role on your resume? Start by signing up for code reviews </font><a href="https://gerrit.openbmc-project.xyz/#/q/status:open"><font size="2">https://gerrit.openbmc-project.xyz/#/q/status:open</font></a><font size="2">. 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. </font><br><br><font size="2">Feel free to ask any questions. </font><br><font size="2"><br>Chris Austen<br>POWER Systems Enablement Manager <br>(512) 286-5184 (T/L: 363-5184)</font><br><br><BR>
</body></html>