13 ms·
Councils, committees, multiple obtuse voting systems, governance documents, 'courts' of appeal... Why are they so keen to construct such a grim bureaucracy for
by chrisseaton 8y ago
Councils, committees, multiple obtuse voting systems, governance documents, 'courts' of appeal... Why are they so keen to construct such a grim bureaucracy for themselves?
- deleted 8y ago[deleted]
- claudiawerner 8y agoZizek is famous for pursuing a line very much against the grain; people intellectually similar to him argue for a society organised informally and locally, like a commune - but he argues that he'd rather be living in a bureaucracy in which he doesn't have to worry about all the smallest decisions and direct democracy. To him, the trouble of the USSR wasn't all the bureaucracy, it was that it wasn't bureaucratic enough to the point where it was easy to game the system. >Žižek now believes that efficient bureaucracy is the necessary corollary of any successful future state. While often alluding to the utopian impulse that imagines a political community beyond “what is”—including Derrida’s “democracy of the future”—such imagining should not exceed the strictures imposed on the world by technological complexity, sprawling populations and megalopolises. In fact one should be able to take utilities and health services for granted. Freedom of choice should not have to extend to one’s electricity vendor and Internet provider, or even what hospital one wants to convalesce in.[0] and, >I think he agrees with Laclau and Mouffe, that every radical solution is temporary, 'lives in borrowed time'. This means that an 'organizational structure' must not become sedimented, but remain open. This probably sounds a bit abstract, but it matters, as it assumes the position opposite of e.g. Stalinism.[1] On some level I agree with him, as much as it's contrary to the self-organizing semi-anarchist hacker spirit. [0] https://criticaltheoryresearchnetwork.com/2017/08/10/bureaucratic-socialism-zizek-illusion-future/ https://criticaltheoryresearchnetwork.com/2017/08/10/bureauc... [1] https://www.reddit.com/r/zizek/comments/6mmtpg/what_kind_of_organizational_structure_does_zizek/dk2rn7m/ https://www.reddit.com/r/zizek/comments/6mmtpg/what_kind_of_...
- Fnoord 8y ago> Zizek Who? This person? [1] I'm at a loss. Could you explain what this has to do with this topic? From what I understand it seems to be in agreement with the principles of Hakim Bey's Temporary Autonomous Zone [2]. "The book describes the socio-political tactic of creating temporary spaces that elude formal structures of control.[1] The essay uses various examples from history and philosophy, all of which suggest that the best way to create a non-hierarchical system of social relationships is to concentrate on the present and on releasing one's own mind from the controlling mechanisms that have been imposed on it. In the formation of a TAZ, Bey argues, information becomes a key tool that sneaks into the cracks of formal procedures. A new territory of the moment is created that is on the boundary line of established regions. Any attempt at permanence that goes beyond the moment deteriorates to a structured system that inevitably stifles individual creativity. It is this chance at creativity that is real empowerment." [1] https://en.wikipedia.org/wiki/Slavoj_%C5%BDi%C5%BEek https://en.wikipedia.org/wiki/Slavoj_%C5%BDi%C5%BEek [2] https://en.wikipedia.org/wiki/Temporary_Autonomous_Zone https://en.wikipedia.org/wiki/Temporary_Autonomous_Zone
- claudiawerner 8y agoHe's a continental philosopher who specialises in political philosophy, a topic which is very relevant to methods of governance in society (most generally) or smaller units (like programming projects). In particular, his concern in this scope is questioning the extent to which critiques of current methods of governance and the organisation of society (e.g as highlighted by the Frankfurt School's critical theory) are relevant to any future methods, and whether questioning government philosophically rules out a bureaucratic governance. In particular his position is interesting in contrast to others in the anti-authoritarian Marxist tradition. I hadn't heard of Hakim Bey or TAZ, so thanks for pointing that out to me.
- AstralStorm 8y agoThis does not close nor stifle creativity at all, unless your point is that any majoritarian system does so. There is a balance involved, too much chaos and everything explodes. You're free to fork your own python like language and get buy in as long as you do not infringe the trademarks. Or make experimental branches and proposals.
- nabla9 8y agoThat's how societies work. Informal organizatios are not transparent.
- cousin_it 8y agoThe grandparent comment wasn't about formal replacing informal, it was about bureaucracy replacing dictatorship. I don't think that's always a good thing. If the organization has some urgent goal, like winning a war or putting a man on the Moon, some dictatorship is needed to keep bureaucracy in check. But when there's no more urgent goal than well-being of the organization's members, that's when dictatorship fades and the subcommittees begin to sprout.
- exo762 8y agoI wonder if programming languages might be considered a type of a project where comfort of members is of less importance than other goals (mindshare?).
- pas 8y agoIs this really true? Does this work in every kind of war or Moon-race? Control is important, but so is individual initiative. The front line needs the latter the HQ needs the former. That's why "aligning goals" is the important thing, not just rules for power's sake. (That's authorianism of course.)
- JadeNB 8y agoTo be clear, pas's comment is replying to an earlier version of cousin_it's: > Correction - that's how organizations work when their goal is making members happy. If the organization has an external goal, like winning a war or putting a man on the Moon, it needs to be more authoritarian. (EDIT: cousin_it's comment changed again while I was writing this, somewhat closer to the original. Anyway, probably just keep in mind that any now-nonsensical response may be to an earlier version.)
- deleted 8y ago[deleted]
- detaro 8y agoTwo common and tested-in-practice voting systems: one to select members of a group, one to decide between multiple options inside that group (which isn't the same problem, so it makes sense to vote differently). One committee to replace what before was a BDFL who resigned and thus needs to be replaced, ideally in a way that doesn't make discussions worse than they are (so transparency and clearly defined rules for edge cases are important. A BDFL can afford to be somewhat intransparent and inconsistent, an elected group can not)
- ghaff 8y agoExactly. As someone who is on the board and used to be the chair of a non-profit, rules and procedures tend not to matter much. Until they do. You hit some edge case where people seriously disagree and things like voting rights, proxies, the process for bringing an issue to a vote, etc. suddenly matter if you don't want to just leave decisions in the hands of whoever has the loudest voice and/or feels most entitled to having the final say.
- lourenchord 8y agocan't you just fork it, if it becomes too shitty ?
- rthomas6 8y agoYes, but the real strength of Python (as with most popular languages) comes from its community. The reason why I end up using it so much is because somebody already made a good library that does what I want, and because it's much easier (for me) to tell what the hell is going on in other peoples' code compared to JavaScript.
- jetrink 8y agoThe alternative to explicit rules, hierarchies and power structures usually isn't harmonious self-organization; it is unspoken rules, implicit hierarchies and hidden power structures.
- chrisseaton 8y agoI think a new BFDL would be a worse-is-better solution than all this play-government formality, to be honest. It seems to be an effective system for many languages, including Python in the past.
- SolaceQuantum 8y agoI believe a concern would be a single point of failure and burnout, the consequences of which would be massive losses of organizational, directional, and domain knowledge.
- kibwen 8y agoBDFLs only work when they're the founder of the language, or a well-respected community member who is explicitly appointed by the prior BDFL. Without a clear line of succession, you get all the same destructive infighting and power struggles that real-world dictatorships experience.
- simias 8y agoA good benevolent dictator is often more efficient than a more decentralized and democratic system but you have a single point of failure and you need to be able to find said dictator in the first place. A bad or incompetent not-so-benevolent dictator can be absolutely terrible for a project and cause a lot of long-term damage. For such an important project unfortunately I think a certain amount of bureaucracy and paperwork is not only unavoidable but actually necessary and important.
- kibwen 8y ago> unfortunately I think it's curious that commenters (this is not aimed at you specifically) don't dare to even indirectly praise bureaucracy without couching it with words like "unfortunately", because there's nothing unfortunate about having a well-described and transparent decision-making process. Python has had bureaucracy for decades, e.g. the entire PEP process, so it's too late for us to be wringing our hands about tainting the Python project with the bogeyman of government.
- cyphar 8y agoPlay-democracy is a well-known problem in a lot of projects. OpenSolaris had the same issue, and it had some pretty disastrous consequences (though they modelled themselves after Apache which isn't really the best model). Honestly, I think it comes down to the fact that democracy is definitely sexy. The idea that any individual could gain the power they want through based on public recognition, where the public has a say on who is in power, is very attractive (and is one of the reasons many governments are democratically elected -- because there would be an uprising otherwise). And obviously it's great for societies where the decisions can very much be a matter of life or death -- but for projects that are trying to get a very specific thing done you can end up in a death-by-bureaucracy system. Also, democracy is one of the easiest ways of getting out of having to solve an issue -- just let the people decide. There were several completely different PEPs that outlined new governance models, and due to lack of consensus this model was adopted since it can be used to get any other model (and in the Preamble they state that this new governance model could be used to pick a different one). EDIT: "The people" could be any subset of people -- not just the general public or users of software. Several democratic systems (Westminster-like and the American primary election system) work in the same manner -- where only a subset of people make decisions about the country or party.
- kibwen 8y agoI suspect you're being downvoted because these models don't particularly resemble democracy, which would presumably involve having the users of the software vote, rather than the developers of the software.
- cyphar 8y agoIn Westminster-style democracies, party members elect their party's leader (the general public don't get to decide who the leader of a particular party is). In America, you can only vote in primaries (that is, choose presidential and other candidates) if you are a registered voter of that party -- which means that it's also restricted to a subset of the public. So I'm not sure I agree it is a mismatch to most democracies. Obviously there is a difference, but it's still clearly democratic in spirit (and actually matches how some real democracies work in some aspects).
- sytelus 8y agoHow Python would have looked like if it was designed by a committee? Something to reflect on...
- kibwen 8y agoPython has been designed by committee for decades now. The PEP process was introduced in 2000, and even before that the language was being designed by the members of the python-dev mailing list.
- scott_s 8y agoTake out the word "grim", and I would say because that's how large groups of humans have figured out how to civilly work together over the long term.
- rleigh 8y agoPolitics in organisations is pretty grim. But, what would you have as an alternative? Decisions need to be made. Disagreements need to be resolved. Ad hoc resolutions to problems doesn't scale with increasing team size. Neither does anarchy. I don't think many people relish the idea of imposing such bureaucracy upon themselves and their fellow developers. However, when you have a sizeable organisation, there needs to be transparency and accountability so that the developers as a whole can see that proposed directions are properly discussed and agreed upon, without ideas being unfairly dismissed or accepted without due criticism. Hierarchies are intrinsic to the ordering of our society and our functioning as a species. They will crop up inevitably, so a formalising of this is a better alternative to an unaccountable hidden hierarchy which would come into being in its absence. As for voting, voting prevents obvious domination of the decision making process by individuals, allowing all participants to have an equal and democratic say in decisions. “Democracy is the worst form of government, except for all the others”, as Churchill said. It's not perfect, but until we can do better, it's the least bad way of doing things. This is why BDFLs are rare in projects. Like Tito and Yugoslavia, or the Kims in North Korea, it only works while the strong minded influence of the leader is tolerated by those who are subject to their whims. For a technical project, the leader must be consistently technically adept, and maintain the goodwill of the contributors, or be replaced or burnt out with exhaustion. Can you see an obvious replacement dictator for Guido, or Linus? Me neither. Bureaucracy allows an organisation to outlast an individual by providing a structure for the replacement of leadership over time.
- deleted 8y ago[deleted]
- deleted 8y ago[deleted]
- deleted 8y ago[deleted]
- wool_gather 8y agoThe reason you lay all this stuff -- especially the "if something goes wrong" plan -- out in excruciating detail in advance is extremely simple. Otherwise, every time there's a decision to be made, you will have to have arguments^Wdiscussion^Warguments not just about the substantive content of the decision, but about the process of making the decision too. This goes double for the stuff like "votes of no confidence". If it comes to that point, the group is already in deep enough trouble as it is. The last thing you need is to add a debate about the means to handle the trouble on top of the discussion of the actual trouble. You spell these things out in advance so that when questions arise in the course of the group making choices, the fundamental question of "how are we going to go about finding the answer to this question" is already settled.
- ubernostrum 8y agoThe new Python model is pretty similar to what Django has been using for years (and even admits that it copy/pasted significant chunks of text from our model). I didn't realize how grim things were! I've served on Django's technical board -- its equivalent of the new Python "steering council" -- for several years. The technical board has the following responsibilities: * Act as a final tiebreaker for any decision that the dev mailing list can't manage to make through normal discussion * Review major proposals for changing Django or Django's processes (DEPs, our equivalent of Python's PEPs), with the ability to veto * Review proposals to add new Django committers, with the ability to veto The first category has never, as far as I can tell, come up, and for the other two the technical board has never vetoed a committer or a DEP. There also aren't many of them -- 24 in a bit over four years. I'm trying to push through a significant change to how Django works, but it wouldn't do away with the technical board; instead it acknowledges that the in-practice way Django runs -- discussion on the dev mailing list, open to everyone, with a couple people whose job is to merge PRs -- is working well enough that we no longer need to give special privileges to a large group of committers.
- xyzzy123 8y agoI think the unspoken need is to protect the organisation (and maintainers) from the plague of recriminations and identity politics.
- qwerty456127 8y agoAt least I hope they will give the obscure old-fashioned communication model (mailing lists, Usenet newsgroups, yet another bug tracker for everybody to register at (which doesn't even work right now - it's Error #502)) up and embrace GitHub issues and pull requests system like Rust and C# teams do.