On Fri, 2026-02-06 at 08:52 +0100, Koen Kooi via lists.openembedded.org wrote:
> > Op 5 feb 2026, om 16:12 heeft Ross Burton <[email protected]> het
> > volgende geschreven:
> > For example:
> >
> > - Full automated build testing before patches are merged, to ensure that
> > nothing breaks
> > - Support for multiple architectures, so that BSP vendors can use the
> > recipes and extend them easily as needed
> > - Every recipe has an active maintainer
> > - Removal of obsolete recipes from master
> >
> > This would mean we can consolidate common recipes, without the risk of
> > turning into a collection of obsolete unmaintained software that BSP
> > vendors forked from the year before.
> >
> > Does this sound like a direction that would be acceptable?
>
> I already had this written down:
>
> "Vendor specific changes need careful consideration, backports should
> be fine, but changes under upstream review or unsubmitted changes
> should live in their vendor layer as bbappends."
It that instead of, or in addition to the things Ross mentioned? I
think there are a few key things which need to be written down up front
to make this successful. Vendors specific changes are definitely one of
them.
> As for maintenance, I'd really like to be able to use git{hub,lab}
> like pull requests to have proper 2 way communication, but I suspect
> a separate mailinglist with patchwork+b4 would get us most of the way
> there.
I think that is up to the maintainers as they are the ones who "live"
it day to day. Keep in mind that git{hub,lab} work well for
communication with one maintainer or a small number of them, it doesn't
work well for wider review. That is probably fine here but I want
people in general to understand that key difference in the wider
project context!
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#2251):
https://lists.openembedded.org/g/openembedded-architecture/message/2251
Mute This Topic: https://lists.openembedded.org/mt/117540395/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-