Hello to OpenBMC Team

[Brad Bishop]

On Wed, 2020-06-03 at 19:36 +0000, Garrett, Mike (HPE Server Firmware)
wrote:
> Hi Brad,
> 
> Our thinking is to set up public forks "close to home" that we can
> work rapidly in 

That makes sense - my dream is that someday everyone could work rapidly
directly in upstream.  We have work to do to get there for sure.    If
ideas come up that could make the situation better please share them
here on the list.

I think it works best for everyone involved when you can commit to
working directly upstream, first.  My observation is that it is
extremely difficult to circle back and incorporate community feedback
after you have something that works for you.  That can lead to problems
like the code not being accepted or introducing fragmentation into the
project.

But I understand that can be really hard and conflicting internal
business pressures are often mitigated with techniques like the one you
have described.  My company maintains forks too.

One last opine just in case its helpful - like security, working in
upstream first isn't boolean - it is a spectrum.  Where an organization
(or a single developer) lands on that spectrum is one element of what
separates those with influence over others from those without.

> and simultaneously work to upstream patches for U-boot, Linux, and
> OpenBMC to the main repos.  

Great!  Looking forward to working with you and the team on that.

thx -brad