Call for maintainers

[Simon Glass]

Hi Chris,

On 14 October 2017 at 04:33, Chris Austen <austenc at us.ibm.com> wrote:
>
> 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.
>
> I know we would like to move up on U-Boot and the reason we have not is simply a lack people power.
>
> I’m sure we can figure out a cadence that would work for you.

OK, let me know who to connect with / what to do.

Regards,
Simon

>
> Sent from my iPhone
>
> On Oct 13, 2017, at 6:14 PM, Simon Glass <sjg at chromium.org> wrote:
>
> Hi Chris,
>
> On 9 October 2017 at 19:04, Chris Austen <austenc at us.ibm.com> wrote:
>
>
> 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)
>
>
>
> I might be interested in being U-Boot maintainer.
>
> But I'd like to understand how close to upstream you plan to be? Will
> you select a U-Boot release and stick with it for a year or more, or
> will you try to target each U-Boot release (currently every two
> months)?
>
> For U-Boot specifically you could cc the U-Boot mailing list and see
> if anyone else is interested there.
>
> Regards,
> Simon
>
>