On Wed, 22 May 2024 at 10:24, Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > So yes, there may well be a long list of things you want to remove from > core, however, we also have to think about the project's use and why > people use it. It is often because we're able to support many weird use > cases and interesting scenarios that people do adopt and use the > project. I don't want to have a clinical core that is so opinionated > about how it should be configured, people can't innovate or experiment > and go and use other tools and systems.
This and the rest of the message presents the project users' perspective well and the arguments are solid. I don't have any substantial disagreements. What it doesn't do, is acknowledge or mention the maintainers' situation, and the unhealthy dynamic they find themselves in. It's nothing new to you perhaps, but to make it clear: appreciation rarely if ever happens, but complaints and demands come steadily; work has been routine for years; asking for help is met with indifference. All the ingredients for burnout are present. And we're all left to deal with it on our own, developing coping strategies privately. Lately I've been feeling downright *resentful* towards the embedded "industry" and the amount of freeloading they do. So this original email was partly born out of that sentiment: try and see if I can do something that shifts this balance, particularly by being able to say 'no' to some items that are in core but in my view shouldn't be. Mental health is not a privilege. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2015): https://lists.openembedded.org/g/openembedded-architecture/message/2015 Mute This Topic: https://lists.openembedded.org/mt/106239048/21656 Group Owner: openembedded-architecture+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
