Openly structured communities
If someone asks me, âWhat is open source software?â, I have an obvious answer: âSoftware that is licensed as open source and makes its source code available for users to review, modify and share.â Ditto âWhat is open science?â, to which Iâd respond: âScience that is made available to review by anybody and available to reproduce by anyone with the necessary skills and equipment.âÂ
Itâs important to note that open source software and open science can be created by âclosedâ communities. A secretive company that makes all of its employees sign NDAs could create open source software and âthrow it over the wallâ periodically to users, ignoring all bug reports and feature requests. An elite group of researchers could work in isolation and only after finishing publish all their materials in an open access journal.Â
That this doesnât often happen is a testament to the way our values express themselves in all aspects of our lives. Someone who believes strongly in open access is unlikely to enjoy participating in a secret scientific cabal, for instance. But the conflation of âopen productsâ with âopen communitiesâ can cause problems when people assume that all they need to do to foster an open community is create a specific kind of product licensed in a specific kind of way.
Now, secret scientific cabals are obviously not âopenâ, so most open-aspiring communities are unlikely to adopt that structure. But what structure will they adopt? Too often the answer is none. While a lack of formal structure may work for some small projects, it can also cause significant problems, problems which subvert the open and egalitarian aims of community members.
Jo Freemanâs classic essay, The Tyranny of Structurelessness, explains why a lack of formal structure does not prevent structure from emerging:
Contrary to what we would like to believe, there is no such thing as a structureless group. Any group of people of whatever nature that comes together for any length of time for any purpose will inevitably structure itself in some fashion. [...] The very fact that we are individuals, with different talents, predispositions, and backgrounds makes this inevitable. Only if we refused to relate or interact on any basis whatsoever could we approximate structurelessness -- and that is not the nature of a human group.
As long as the structure of the group is informal, the rules of how decisions are made are known only to a few and awareness of power is limited to those who know the rules. Those who do not know the rules and are not chosen for initiation must remain in confusion, or suffer from paranoid delusions that something is happening of which they are not quite aware.
For this reason, many âstructurelessâ communities are less open than even formally structured closed communities. While the latter may have a high barrier to entry, for instance employment at a specific company, at least the route to meaningful participation is clear.
Perhaps you are already convinced that a formal structure for your community is desirable. Excellent! Back to our earlier question: which structure?
The same egalitarian impulses which can lead a person to reject formal structure might also inspire someone to say, âLetâs let the community decide what structure to use!â While, again, this may work for some projects, especially small ones, it can also cause problems. I see two reasons for this.
First, the process of choosing a communityâs structure can be enormously complex. It is a task which requires the cognitive ability to compare multiple abstract systems and select from among them that which best fits your project and community. It also requires the interpersonal social ability of communicating with members of the community to gauge enthusiasm for the proposed structure. If there are pre-existing tensions within the community, you need to know of them and how to navigate them. And of course, you need to feel empowered to do all of this individually or collectively.
Which brings me to the second problem. In some ways, âWeâll let the community choose the structure!â just kicks the issue of structurelessness down the road a bit. Because what does it mean for the community to choose the structure? Which structures will be considered? How will community members give feedback? Who determines who a âcommunity memberâ is as this phase? Who is organizing the feedback process? How will a decision ultimately be made and where does that power come from? You end up needing to pick a structure in order to pick a structure. Itâs turtles all the way down.
In the best case scenario, however, these two problems cancel each other out. Few people are willing or able to take on the social and cognitive burden of setting up an initial structure. Therefore members of a community may be relieved rather than upset when someone steps in to propose an initial structure without consulting them first. So long as that initial structure is itself an open structure, people will often greet it with open arms.
But what makes something an open structure, if itâs not the fact that it creates an open product nor the process by which the structure was adopted? That is, shall we say, an open question. ;) Hereâs one possible answer:
An open structure is transparent. Governance work is done, wherever possible, in open channels: forums, mailing lists, logged chats or in-person meetings where notes are taken. A maximally transparent structure doesnât just take notes, it also summarizes them for ease of reading and crafts communications channels like announcements-only mailing lists where people can learn about major decisions without having to weed through information thatâs irrelevant to them.
An open structure is accountable. It gives community members clear routes to making small and large changes to both the outputs of the structure and to the structure itself. For instance, a structure may have a founding charter from which it derives its authority, and that charter may specify that changes can be made to the charter given a vote of 3/4ths from members, membership being a role also defined by the charter.
An open structure is inclusive. Participation in the community and in the governing structure is limited by behavior rather than by irrelevant personal characteristics such as employment by specific organizations, a lack of educational credentials, or demographic differences like race and gender. To be clear, the characteristics I just listed are only commonly irrelevant. Communities formed around an identity or requiring specific skillsets only taught in certain credentialing programs may find them quite relevant. Restricting membership based on those characteristics may make a community comparatively less inclusive, but they should still be considered under the broad umbrella of âopenâ.
Without a formal structure, it can be difficult for newcomers to tell if a given community is transparent, accountable, and inclusive, and near impossible for them to trust it will remain so.Â
Why would an informally structured community that is currently transparent, accountable and inclusive ever lose those attributes? There are many reasons, but chief among them is the fact that each of the values I listed above exists in tension with other important and desirable values. For instance, âtransparencyâ exists in tension with âprivacyâ. âAccountabilityâ exists in tension with âstabilityâ and âefficiencyâ, as the work of holding leaders accountable can cause unpredictable changes and slow the development process down.
I see âinclusivityâ as existing in tension with a phenomenon that I donât have a pithy one-word label for, and it is the inclination to prioritize the needs and desires of those who are doing most of the work. Like âprivacyâ and âefficiencyâ, this inclination is an inherently positive thing and something that open communities need to respect. If thereâs one person doing 90% of all translations for your documentation, for instance, her opinions on how to change the translation process should count for more than any other random member of the community. But how much more?
Open communities may value transparency over privacy, accountability over stability and efficiency, and inclusivity over prioritizing individuals based on behavior, but they should not always and in all cases do so. Where they draw the line is a judgment call, and having formal discussions and structures which address these tensions help to make this a conscious and ongoing judgment, rather than a hidden and outdated one.
There are many templates out there for making new websites, for drawing up a new open source license, or for setting out to conduct a new reproducible science experiment. I would love to see some templates drawn up for how to create an open community. I think it would be a tremendous help for many people currently struggling to make their communities as open as their products.