4 ms·
How often is pride in the way of building a team of maintainers, which could reduce the risk of burnout? Is this the case here? I don't know.
by eXpl0it3r 2y ago
How often is pride in the way of building a team of maintainers, which could reduce the risk of burnout?
Is this the case here? I don't know.
- szundi 2y agoNot too late though
- raverbashing 2y agoWell, we saw how that went with xz
- eXpl0it3r 2y agoThe GitHub repository has been archived
- portaouflop 2y agoBuilding and keeping a team of maintainers is either a lot of work or you need to get very lucky.
- Timshel 2y agoAfter the author the second most active contributor has only 5 commits so I would say probably not the case here ...
- boesboes 2y agoI think it's more of a question of how often do people just want to make something nice and not deal with managing a community and the idiots making demands and threats that come with it. Mind you, this happens regardless, but it get's harder to ignore if you actively want to build community.
- shadowgovt 2y agoFor a lot of devs, that would exacerbate burnout. I, for one, dabble in small, focused FOSS projects to keep myself sane in a world where working on a team on a feature-creeping project is the norm.
- langsoul-com 2y agoRunning a company (that is a team of maintainers) is wildly different from writing code. Questions raised like how do you find these people, are they paid? Legalities and how to make money. Now you have to organise and lead a group of people. All of that isn't why most people want to write code.
- eXpl0it3r 2y agoLots of open source projects are run by a team of maintainers without having a company behind it