On Thu, 2024-05-23 at 10:35 +0200, Alexander Kanavin wrote: > On Wed, 22 May 2024 at 10:24, Richard Purdie > <[email protected]> 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.
My suggestion is to only take on the things which you're happy and able to work on. If for example ppc or mips is breaking, just leave those bits and let someone else deal with them. Post the patches and just make it clear those pieces break. The dilemma of whether to take them or not becomes mine and really isn't your problem, I can try and find help to fix the remaining issues, merge it and break something or find some other path. I appreciate you don't want to push that work to me, equally, I cannot reasonably expect you to do it either and you have every right to only work on the pieces that you want to. I've made my position clear as there was no other way to change it without people knowing but that doesn't mean things like that can't be pushed back to me and I have ways to handle it. I have been feeling bad for a while about replying with the long lists of test failures for changes people submit, it is quite hard to make changes to some areas of the project now due to the shear complexity and diversity of use cases we support. I wish I had good answers to some of this. I will say you're not alone with those resentment feelings, I know others have them and I've shared my own thoughts on the topic too. I'd highlight that it isn't just about old things either. Rust in particular showed up as a particular pain point in this regard too recently - several different requirements (reproducibility, automated testing, upgrades, intermittent failures) all combined to make something particularly horrible to wrestle. As for saying "no" to things in core, I have a list of things I really dislike in there too. I've come to accept that many of them are extremely useful and appreciated/used by others though. I try and avoid them where I can, sometimes my expertise is needed to fix them though and I usually do. rm_work comes to mind as an example. Our ecosystem works as it is bigger than any one of us and it would be strange if we actually liked everything in there so compromise is needed in places. So I come back to where I started, just focus on the things you are interested in and happy to work on. The other pieces will resolve themselves one way or another over time. Finally, and this applies to everyone, please do look after yourselves! That should be a priority for everyone. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#199786): https://lists.openembedded.org/g/openembedded-core/message/199786 Mute This Topic: https://lists.openembedded.org/mt/106239266/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
