Hello all, the current maintenance model in openembedded-core is problematic due to lack of well-working process of finding maintainers, and replacing them when they're no longer able to contribute. This becomes especially frustrating when maintainers silently disappear, and perfectly fine patches produced by Auto Upgrade Helper and sent to them via private mail go wasted.
I'm proposing that some of the recipes in oe-core - those that are known to lack an active maintainer - would be transitioned to 'community maintenance'. What this means is that the maintainer's email becomes the oe-core mailing list email, and accordingly monthly upgrade patches will be sent to the list. Then anyone with an interest in those components can pick up the patches, polish/test them as needed and send them to oe-core for inclusion into master/release branches. This opens up an easy path for people to become maintainers, and also highlights what recipes suffer from lack of attention. Let me know, Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137734): https://lists.openembedded.org/g/openembedded-core/message/137734 Mute This Topic: https://lists.openembedded.org/mt/73932965/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/leave/8023207/1426099254/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
