Open Communities and Closed Law

What does the recent news of a Wikipedia CEO who is also a lawyer, an "oversight" function that makes hidden revisions to Wikipedia, and the threat of the Debian Project severing its relationship with its legally chartered non-profit have in common? A strong indication that open communities with a formal legal standing are a conflicted beast.

The sociologist Max Weber made an important observation of how leadership often shifts from a charismatic leader to a more bureaucratic form of governance as a community matures; Wikipedia is no exception. An interesting question in the Wikipedia case is to what extent can the shift occur while decision making remains in the open, within sight and control of the larger community? The delegation of power from Jimbo Wales to the Mediation and Arbitration Committees is an example of what Weber called "routinization." (You can read more about the governing and leadership structure of Wikipedia in Do as I do: leadership in the Wikipedia.) Both of these committees are open. However, in matters of law, maintaining openness is a difficult task. As Wikipedia has grown in size and repute the likelihood of the Wikipedia being subject to legal action has similarly grown. The tension between openness and closeness in such a community (a topic of study of my colleague Shay David) is no better demonstrated than by the WP:Office action.

On the Wikipedia one is expected to discuss the editing of an article with fellow contributors. Arguments are made in the open with reference to public policies. However, for those with a proprietary interest, this process of reasoned discussion can be circumvented via a call or letter to the "Wikipedia office." And, sometimes, rightfully so. What obligation did Seigenthaler, someone completely unfamiliar with Wikis, have to edit the Wikipedia in order to remove the libelous claim that he was implicated in the assassination of a Kennedy? None. As Jimmy Wales wrote, "The problem we are seeing, again and again, is this attitude that some poor victim of a biased rant in Wikipedia ought to not get pissed and take us up on our offer of 'anyone can edit' but should rather immerse themselves in our arcane internal culture until they understand the right way to get things done."

However, unfortunately, the office mechanism can be abused by those pushing a non-encyclopedic POV (point of view), such as promoting (or censoring negative views of) a commercial product. If such people can't win their arguments on the merits of notability and neutrality, having their lawyer call the office might prompt an office intervention -- such as blanking or deleting the contentious article which should then be labeled with the WP:Office tag.

Something like WP:Office is an unfortunate though (probably) necessary mechanism whereby reasoned discussion is excepted so as to avoid legal problems. Yet, in an amusing and sad irony WP:Office soon became a red flag to those who dislike this intervention or otherwise like to make trouble for Wikipedia (e.g., copying sensitive or contentious materials off Wikipedia to continue to cause trouble). Whereas office actions were intended to quickly and quietly remove a potential liability, they became a flash-point. This led to the genuinely sad case in which office actions were taken without being labeled as such and a "good-faith" administrator was desysopped and blocked indefinitely because he had reverted the hidden landmine of an unlabeled office action. (Fortunately, his response was an exemplar of Wikipedia tact and his position was soon restored.)

This week the realities of this tension between open collaboration and legal action are indicated by two announcements: the appointment to a CEO position who will also act as general counsel, and the deployment of a "oversight" (revision hiding) feature which permits edits to be hidden from an article's history page. Legal threats are clearly a top priority.

Edgar Schein argues that organizations are shaped by the crises they face in interaction with the external environment and how those events are internally integrated within the organization. This integration is not always smooth or successful, particularly for an open community. Another example of this has been the recent dispute in the Debian GNU/Linux distribution project (a community my colleague Biella Coleman has been studying). In a thread entitled Who can make binding legal agreements, the Debian community came into conflict with the SPI Board, it's own legally chartered "umbrella"! Can SPI preempt Debian decision making processes? Can Debian decisions foist liability upon SPI it is unwilling to accept? These are difficult decisions when we lack a legally robust and safe means of the open collaboration that Wikipedia and Debian represent. This has lead Larry Sanger to argue that Collaborative Free Works Should Be Protected by the Law. A proposal that deserves serious consideration.

Comments !