From: Jiaqing Zhao <jiaqing.zhao@linux.intel.com>
To: Andrew Jeffery <andrew@aj.id.au>, openbmc@lists.ozlabs.org
Cc: Benjamin Fair <benjaminfair@google.com>,
Ed Tanous <edtanous@google.com>,
Brad Bishop <bradleyb@fuzziesquirrel.com>,
Heyi Guo <guoheyi@linux.alibaba.com>,
jebr@google.com, scody@google.com
Subject: Re: Can we improve the experience of working on OpenBMC?
Date: Tue, 9 Aug 2022 16:08:59 +0800 [thread overview]
Message-ID: <77004044-4ea7-8086-eab9-ac3c6d4bd634@linux.intel.com> (raw)
In-Reply-To: <3df049fc-e5ec-449e-b696-a2ca86c37ed3@www.fastmail.com>
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
prev parent reply other threads:[~2022-08-09 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 1:22 Can we improve the experience of working on OpenBMC? Andrew Jeffery
2022-07-29 0:10 ` Brad Bishop
2022-07-29 2:21 ` Andrew Jeffery
2022-08-01 21:34 ` Ed Tanous
2022-08-01 21:27 ` Alexander Amelkin
2022-08-01 21:39 ` Ed Tanous
2022-08-01 22:03 ` Alexander Amelkin
2022-08-09 3:42 ` Andrew Jeffery
2022-08-09 0:44 ` Andrew Jeffery
2022-08-09 8:08 ` Jiaqing Zhao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77004044-4ea7-8086-eab9-ac3c6d4bd634@linux.intel.com \
--to=jiaqing.zhao@linux.intel.com \
--cc=andrew@aj.id.au \
--cc=benjaminfair@google.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=edtanous@google.com \
--cc=guoheyi@linux.alibaba.com \
--cc=jebr@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=scody@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.