I find it fascinating that programmers like to discuss governance at such great lengths without any reference to the vast knowledge of Political Theory that lies at their fingertips. At the end of the day, I suppose this is simply yet another form of NIH
Python gets a new governance model
131–140 of 191 posts
Re: Python gets a new governance model
#132Earlier quoted context omitted.
> it does speak to potential limitations of the model The parent compared a group of volunteers with the largest open-source company in the world, which is a part S&P 500. No other Linux distribution has a comparable amount of resources. Even Canonical is following the RedHat's lead (systemd, Wayland, PulseAudio).
So by your logic, Microsoft and Apple make better OSes than Linux by several orders of magnitude.
The power and flexibility of Linux comes with the cost of a much lower floor for stability than proprietary operating systems. You can make a rock solid system using Linux, but that requires nontrivial effort and knowledge. I have yet to see an issue on my personal Windows and macOS machines that approached e.g. package management hell on Linux, in terms of complexity and frustration.
For examples of what open source projects look like when they have the backing and resources of large companies, look at LLVM versus GCC, BoringSSL versus OpenSSL and CentOS versus Ubuntu. "Better" would be too broad a description, but if you qualify it to the narrow scope of stability, then yeah I think proprietary resources generally come out ahead. I also don't think that is a controversial observation.
Re: Python gets a new governance model
#133Earlier quoted context omitted.
The alternative to explicit rules, hierarchies and power structures usually isn't harmonious self-organization; it is unspoken rules, implicit hierarchies and hidden power structures.
The other way I've heard this expressed: The opposite of bureaucracy isn't efficiency. It's corruption.
Re: Python gets a new governance model
#134Earlier quoted context omitted.
I'm under the impression that well-described, transparent decision making process has the consequence of increasing cognitive load when it comes to participating in decision making. Given that decision-making in large projects like this is already a significant cognitive load, adding on "did I make the decision following pre-defined process goals" does increase difficulty. Whether or not the tradeoffs are worth it is…
Correct that it involves tradeoffs, though having no process at all for making decisions leads to at worst a free-for-all (which can work for small or non-critical projects, but even so be prepared for inevitable drama), or at best an opaque and implicit process as others here have warned about. To use a HN-friendly analogy, it's like static typing vs dynamic typing: you can either accept pain up-front to avoid pain…
Re: Python gets a new governance model
#135Earlier quoted context omitted.
> 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…
I consider it unfortunate because I think we've all been frustrated by "due process" and having to wait or do seemingly useless tasks when the way to go appears obvious. Being able to say "let's do this" and start hacking right away sounds a lot more fun than "let's submit an RFC and wait for one month for people to comment, then we'll vote and if people accept the proposal we'll implement the unit tests, do the code…
Re: Python gets a new governance model
#136The merits of singular vision, unity of design, counter-majoritarian good judgment, predictability, and decisiveness should really get more credit in these contexts. As should the downsides of bureaucracy and democratic decision making: infighting, politics (the sacrifice of sincerity for popularity), gridlock, disunity of design, etc.
Re: Python gets a new governance model
#137This comment section is proof positive of why the Steering Committee was a good choice.
" to is proof that is good" is among the worst arguments in the world. It applies equally well to any non-unanimous change, therefore it means nothing.
Re: Python gets a new governance model
#138I find it fascinating that programmers like to discuss governance at such great lengths without any reference to the vast knowledge of Political Theory that lies at their fingertips. At the end of the day, I suppose this is simply yet another form of NIH
Re: Python gets a new governance model
#139Earlier quoted context omitted.
> it does speak to potential limitations of the model The parent compared a group of volunteers with the largest open-source company in the world, which is a part S&P 500. No other Linux distribution has a comparable amount of resources. Even Canonical is following the RedHat's lead (systemd, Wayland, PulseAudio).
The way I understood the parent is that the Debian model didn't actually solve the problem it was suggested as a solution for. It merely offloaded the problem to someone else. In other words, it has a dependency and therefore is not a complete solution. That's how I understood it.
Debian isn't more dependent on RedHat than any other Linux distribution is. It has nothing to do with the governance model, but rather with the fact, that multiple open-source solutions created by RedHat employees and firstly released in Fedora have won as currently the best.
Re: Python gets a new governance model
#140I find it fascinating that programmers like to discuss governance at such great lengths without any reference to the vast knowledge of Political Theory that lies at their fingertips. At the end of the day, I suppose this is simply yet another form of NIH