<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi Simon. The goal is to stay as close to master as we can. We’ve done a better job at proving that with our 4.3-4.7-4.10 kernel and 1.7-1.8-2.2 yocto upgrades over the last 1.5 years then with our u-boot. <div><br></div><div>I know we would like to move up on U-Boot and the reason we have not is simply a lack people power. </div><div><br></div><div>I’m sure we can figure out a cadence that would work for you. <br><br><div id="AppleMailSignature">Sent from my iPhone</div><div><br>On Oct 13, 2017, at 6:14 PM, Simon Glass <<a href="mailto:sjg@chromium.org">sjg@chromium.org</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hi Chris,</span><br><span></span><br><span>On 9 October 2017 at 19:04, Chris Austen <<a href="mailto:austenc@us.ibm.com">austenc@us.ibm.com</a>> wrote:</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Greetings,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I received some feedback that people would like to know more about what it takes to become, and duties of, a Maintainer in OpenBMC.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>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.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Steps to get there...</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>1) Pick a project repository that you have matured</span><br></blockquote><blockquote type="cite"><span>2) Sign up for reviews in that repository without being asked</span><br></blockquote><blockquote type="cite"><span>3) provide comments that correctly shape the goals of the repository</span><br></blockquote><blockquote type="cite"><span>4) Be on architecture calls to learn from others</span><br></blockquote><blockquote type="cite"><span>5) Contribute code</span><br></blockquote><blockquote type="cite"><span>6) Contribute socially (IRC, mailing list feedback, writing articles that end up on /. , etc)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br><span>I might be interested in being U-Boot maintainer.</span><br><span></span><br><span>But I'd like to understand how close to upstream you plan to be? Will</span><br><span>you select a U-Boot release and stick with it for a year or more, or</span><br><span>will you try to target each U-Boot release (currently every two</span><br><span>months)?</span><br><span></span><br><span>For U-Boot specifically you could cc the U-Boot mailing list and see</span><br><span>if anyone else is interested there.</span><br><span></span><br><span>Regards,</span><br><span>Simon</span><br><span></span><br></div></blockquote></div><BR>
</body></html>