This fits squarely into a pattern that open source people deal with all of the time. Namely that someone tries to gain control of a project by appeals to "community", while subtly insulting the people who actually did the work. The result is toxic politics that, if it is left to stand, drives away technically competent contributors. And which makes leading that project a misery.
If you don't want to come across this way, you absolutely need to get rid of rhetoric like the paragraph beginning with, "The last year has seen several BDFLs act like Mad Kings." Anyone who has encountered this antipattern will see exactly what that leads to. It is a rhetorical club that can be levied against any technically competent person who objects to something based on technical concerns. The self-proclaimed "community leader" doesn't need to address those technical concerns. They just need to imply the ad hominem. Suggest that the contributor is the would-be Mad King. There are a number of ways that this can end. All of them are bad.
Now I'm not saying that you are bringing up an unimportant issue. But you REALLY need to check your tone if you wish to convince the people that you are supposedly addressing.
Lately, I’ve taken to labelling these different behaviors with D words: Doers, Discussers, Deciders, etc.
It’s amazing to me how often people want to create a specialty for themselves, where the doing is relegated to the doers, but all the doing is dictated by others.
This happens in businesses, NGOs, communities, churches, just about everywhere.
There is a natural competition to become an "idea person" in an organization. If the project goes well, the idea person gets the credit. If the project goes poorly, the people who actually built it get the blame. And it takes far less work to produce promising ideas, than to actually build stuff. The result is that succeeding in getting other people to implement your ideas becomes a fast track to promotion. Unfortunately, the farther that you get from the actual implementation, the worse your ideas get. Compounding that is the fact that the ideas that convince executives far too often are the ones that play buzzword bingo in the right way, rather than the ones which are grounded in pragmatism.
This is why I've learned to be suspicious of anyone with a job title of "architect". Some are amazingly good. But most that I've dealt with, are decidedly not. But when you hear them talk about it, they always sound like they are amazing.
Oof this hits hard. So true. My first job as a developer at a corporation was moving from paper forms to digitally signed forms. We worked really hard for a year integrating with vendor products, saved millions of dollars in work time and error reduction a month, recurring, forever. We even got a nice call out at a town hall from the CEO.... we thought until the name that was called who "brought it all together" was some person none of us on the team had ever met, was never in any meetings, never did any work. But they probably pitched the idea two years ago.
For that, it helps to have good sounding ideas, some existing successes that can be claimed, and to have good people skills. These things wind up being more important in the end than technical competence.
(I gained an appreciation for these dynamics from working at Google back in 2010. Everything that I've seen since has confirmed the importance of this dynamic.)
Wordpress is some legal issues that is going to result in a law suit and some word press developer having to work overtime. Ruby Bundler has some people losing maintainer access and some hurt feelings.
Lets not compare apples and oranges here.
Or oranges and ICBMs.
This is why I think the article is a bit of misdirection. Your criticism is about project governance not about project succession.
You want the leaders of WordPress and Rails to step down now because you don't like how they behave in power, not because of the danger that the leaders might die or disappear and leave a power vacuum. I feel that the Mastodon example is a red herring here.
This happened with iojs... Which is where Node as an org today came from. It happened with xfree86 to xorg...
It also fails plenty... I'm the the, you are not entitled to someone else's work. Make your own, or if the license permits, create your own fork... And if you lack the technical ability, sucks to be you.
Do you have any model to propose? Because most democratic models you would see for country governance (to which you drew parallels) rely on some key characteristics that don't apply to open source governance, making them not really transferable.
A few projects have a clear set of members. Most projects don't; they have contributors of code/documentation/triage/community/etc, but no clear delineation of who is or should be an enfranchised member of the project. Often, projects don't end up defining this until they need it as part of establishing some preferred form of governance.
Exactly.
I'm not too versed in political theory, but one thing from my perception that provides coherence/continuity in nations is the immobility of participants (for better or worse of the individual). E.g. if you have 70/30 election outcome you still have to factor in the needs of the 30% as they may provide important economic functions and can't just leave on election loss.
In contrast, in an open source project, even if you can clearly delineate membership and based on that voting rights for a democratic process there is very little preventing the "losers" from forking (it almost entirely comes down to brand). The outcome of that would just be an empty brand shell with a good chunk of their contribution activity gone.
Any co-op, limited company, charitable association, etc can provide a good model - depending on the nature of the project.
As I say, it is probably overkill for most OSS projects. But once you get to a certain size, I think it is obvious that you need a way to ensure the project's longevity.
The death or disgrace of a CEO rarely destroys a company. There's a board their to temper their behaviour, a structure to ensure succession, and (most importantly) a set of expectations upon which their community can rely.
I'm not saying that's the only way to do it. I'm not even suggesting it is the perfect way to do it. But I think it is better than hoping the BDFL doesn't implode.
If the community agrees with you that the original author is doing things wrong, and your new approach is better, they will move with you to the fork.
If the rest of the community doesn't agree with you, they will stay. If some stay and some go, it means only some of them agreed with you.
That's the thing about open source - you don't actually have to form a consensus. You can split off whenever you want.
This is true and is a key property of open source.
But it's also true that network effects and economies of scale are key for how open source projects provide value to their users. Those effects mean that the value an open source project provides to its community is often super-linear relative to the number of users.
A concrete example: If someone writes a blog post about how to use some feature, every other user of the feature can benefit from it. But also every user can potentially write this kind of documentation. So the value people provide through documentation is very roughly quadratic in the number of people reading and writing docs.
Because value like that scales super-linearly with the number of people in the ecosystem, breaking a community in two can result in less total value even if the total number of users of both communities put together is the same.
If you fork and the forks diverge, now a given bit of documentation may only be relevant to one side of the fork. A given person writing some docs may documenting things that are only true for one fork.
Now, since then, the structure has obviously changed... bit it definitely didn't start as a coup d'etat... Debian now has a leadership structures where voting members are defined as well as how leadership positions are voted for. That's far different than a handful of people trying to unseat or take the project away without that infrastructure.
BDFL is perfectly fine as long as original ownership/management has interest in maintaining said position.
But Eugen Rochko was not replaced. He voluntarily stepped down from power because he was personally dissatisfied in the leadership role. Nobody was calling for his ouster. He could have continued as leader of Mastodon for many more years with nobody batting an eyelash. So again, Mastodon is a red herring.
Many projects start as someone's project, but become bigger than the one person.
If they keep it as one person's project, that's clear.
If there are other contributors, that's less clear.
If the project has a formal organization with governance, it's not the person's project. They might be grandparented in, like a vestige of a past monarchy, but the governance will evolve, to elections. The royalty will be kept for the tourism dollars.
A great reason for NOT having a formal organization with governance
Not true at all. They have copyright to any code/docs they contribute. Things like CLAs distory this legal reality by forcing you to relinquish your rights and enabling BDFLs to act as if they personally wrote all outside code.
To say nothing of norms of social reciprocity...
poor, according to whom?
I'm not sure how moral posturing fits into this.
“If you have a case where the law is clearly on your side, but the facts and justice seem to be against you, urge upon the jury the vast importance of sustaining the law. On the other hand, if the law is against you, or doubtful, and the facts show that your case is founded in justice, insist that justice be done though the heavens fall. If both the law and the facts are dead against you, in that case, talk around it, and the worse it is, the harder you pound the table.”
If the facts are with you, pound on the facts. Else if the law is with you, pound on the law. If neither is with you, pound on the table.
I gave the short version in addition to voting you up because it is memorable, and I thought that someone out there might wonder why it sounded familiar.
As one of them I want to state that others, including you, are not entitled to decide how I run my project. I want to express that I am thankful that this one is phrased as suggestion.
But I utterly reject that open source project is substantially similar to governing a country in responsibility and preferred setup.
So I reject your analogy and suggestions as highly flawed.
Maybe in a sense requesting your project have its own life-after-death counts as "shot calling" from your perspective because it's still essentially about what "they" want rather than a sober reflection on your time/capacity/interest, but I think at least that it's different from ordinary feature requests.
If that is the attitude that you take towards everyone who contributes to your project, then you probably aren't a very good leader. That is, of course, your right.
But if you were interested in the long term survival of your project and attracting other developers to contribute, then it behooves you to consider the desires and needs of the community of contributors.
> But I utterly reject that open source project is substantially similar to governing a country in responsibility and preferred setup.
"Consent of the governed" is about countries, it is about leadership and where the privilege of leadership comes from. If you are leading a software project, does your authority come from god? Or does it come from the willingness of the people working on that project to listen to you? That is "consent of the governed".
Word "decide" was there deliberately. I am not fully opposed to consideration of suggestions made by others.
Though I may consider them and reject, like here.
And I will take opinions of contributors into much serious considerations than this blog post, for multiple reasons.
From position of maintainer in one of projects: primary risk to the project is main author running into too many annoying people and focusing on other hobbies.
And I in fact did it with one of projects. Some other maintainers also left. The same people who caused this by their entitlement are now complaining about project being stagnant.
> Or does it come from the willingness of the people working on that project to listen to you? That is "consent of the governed".
Major difference is that for countries if someone does not consent to decisions of ruler/parliament/etc. they have little to no recourse.
It ranges from extremely hard to impossible to change law or national policies or migrate to another country.
In comparison the worst case of forking open source project is much easier.
Control of open source project is much weaker and people forced to contribute are fairly unusual and rare (though in such cases I would consider my responses to blog post to be not applying, my comments were more focused on hobby projects).
If someone does not want to participate they may easily stop. This does massively differ from countries.
So as long as license is good and there's no CLA, everything is fine.
They had a great discussion with Kelsey Hightower about it[^1], and his answer (which I liked a lot) was basically just that maintainers’ only real obligation was to be transparent about governance. If you want to be a dictator and ignore bugs and contributions that aren’t personally compelling to you, that’s fine—but please just put that in the repo. That way, people who are trying to build a business on open source work and want customers, or to build trust with users for any other reason, can distinguish themselves from maintainers that don’t care (as is their right). Otherwise the reputation of Open Source as a whole suffers.
[^1]: The whole episode is good but here’s the part where Kelsey argues that people just need to be transparent: https://youtu.be/13ctYOu8TsA?si=cI8TwHX6tAaCwH6o&t=1320
I'm specifically talking about the community of people who do contribute. If you look at the recent shenanigans of WordPress and Ruby, they are causing discontent within the existing organisation of contributors.
Those contributors are, of course, free to fork off if they want. But if you're trying to build a long-term viable project, then you need a way to ensure that the people working with you are treated fairly.