Can we improve the experience of working on OpenBMC?

[Jiaqing Zhao]

On 2022-07-27 09:22, Andrew Jeffery wrote> # Problems
> 
> 1. Yocto is hard
>     1. Managing patch stacks is hard
>     2. Yocto-specific tooling is hard
>     3. Finding the right recipe file to inspect/modify is hard
>     4. Yocto has too much documentation
> 2. OpenBMC has too much documentation
> 3. Querying design/implementation/bug properties across the project is hard
> 4. Coordinating breaking changes is hard
> 5. Coordinating tree-wide changes is hard
> 6. Identifying the right repo to file a bug against is hard
> 7. Transferring bugs between repos is hard
> 8. Bug reports are duplicated across repos
> 9. Bug reports are ignored
> 10. Working out where to submit a patch is hard
> 11. Getting patches reviewed is hard
> 12. New repo requests are bottle-necked

I'd personally like to add one item

* Submitting patches across multiple repos is hard, especially when they depends on each other