I'm not sure exactly what is meant by that. My guess, having some experience with board-sitter parasites, is they're just appealing to empty principles to create the illusion of being important to the organization, because they're unable or unwilling to make more tangible and substantial contributions.
When somebody can't justify their role with the quality of their work, they look for other justifications instead. Ideological justifications work best because they aren't provable and anybody who questions the value of the supposed ideological contributions can simply be dismissed as being ideologically opposed (see: the sibling comment accusing you of ideological alignment with gamergate, even though libreoffice has nothing to do with gaming.)
For instance, suppose I am a useless parasite who decides to embed myself into the local school board; I have nothing of real value to contribute to such an organization, but maybe I want the role for the clout. Instead of doing something real, I could instead say that my role on the board is to advance the cause of equality. Anybody who says I'm useless can be construed as opposing equality. Anybody who tried to measure the actual equality in the org before and after my arrival can be dismissed because measuring equality is hard to do objectively.
(I learned most of this from a few relatives of mine, who are such board-seeking parasites. By the way, parasite board sitters can use opposition to "woke" in the way they use championing the cause of equality; both cynical empty words used to distract people from the lack of real, substantial and demonstrable contributions. Anybody who complains can be accused of being woke. It works exactly the same regardless of what flavor of disguise the parasite chooses.)
Up until the 2024 board election, the organization ran on meritocracy in the sense that those who contributed the most had the most say.
Equality means here that the organization shifted to everyone present having an equal voice. It was no longer proportional to the work contributed.
StarOffice was a German office suite bought by Sun Microsystems in 1999. Sun open-sourced it in 2000 as OpenOffice.org, which became the major free alternative to Microsoft Office through the 2000s. Sun kept significant control. They owned the trademark, required copyright assignment for contributions, and steered the project's direction. Many community contributors were uneasy with this arrangement but tolerated it because Sun was broadly seen as a good-faith actor.
Oracle acquired Sun in 2010. Oracle had a reputation for being far more aggressive about monetizing and controlling its acquisitions (the Java/Google lawsuit being another example). The OpenOffice.org community had already been frustrated by years of slow decision-making and corporate gatekeeping, and Oracle's arrival made the situation feel untenable.
A group of prominent community members and corporate contributors (including people from Red Hat, Novell/SUSE, Canonical, and Google) announced The Document Foundation in Sep 2010 and forked the codebase as LibreOffice. Oracle eventually donated the OpenOffice.org code to Apache but LibreOffice quickly became the version that mattered.
The reason they had to fork was that a single entity (first Sun, then Oracle) had unchecked power over the project. The Document Foundation was explicitly designed to prevent that. If there's no formal structure, whoever controls the servers, the domain name, the trademark, or the build infrastructure effectively controls the project. A foundation with bylaws, elected leadership, and distributed authority makes it much harder for any single company or individual to take the project hostage.
LibreOffice receives donations, employs some staff, holds trademarks, pays for infrastructure, and sponsors events. Under German law (TDF is registered in Berlin), you need a proper legal entity with accountable governance to do this. You can't just have "some developers" holding a bank account and a trademark informally. The foundation was officially incorporated on February 17, 2012.
That’s nearly the exact opposite of welcoming newbies.
To be perfectly honest, that’s fine: OpenBSD demands a steep learning curve and that you know what you’re doing.
Not sure if you want to count it as a "code of conduct", but it certainly defines rules on how to communicate and contribute to the project.
> ... fine without a code of conduct — in the sense bakugo employed "code of conduct," not in the generalized sense ...
This part of your comment was worthwhile. You should have stopped there, before starting to grind an unrelated political axe. Let's at least try to follow the "Please don't use Hacker News for political or ideological battle. It tramples curiosity." guideline, eh?
Or do you mean scale of organization?
I guess the question is does the size of the organization match the scale of what they want to accomplish?