Wackypedia: the Wikipedia fork

The fork occupies an ambivalent place in the world of open source. On the one hand, it is widely perceived as the worst thing that can happen to a project, pitting hacker against hacker, and dissipating coding effort that could be more usefully applied in a united way. On the other, it is the ultimate test and guarantee of openness: if code cannot be forked, it is not truly open. Perhaps most importantly, it is the threat of the fork, hanging over projects like a digital sword of Damocles, that keeps them close to their constituencies, as free software's short history has shown time and again.

The closest that the Linux kernel has come to forking, was during the famous “Linus does not scale” incident that began on 28 September1998 with the innocent question:

Am I the only one for whom 2.1.123 fbcon.c doesn't compile?

and culminated with Linus losing it:

Go away, people. Or at least don't Cc me any more. I'm not interested, I'm taking a vacation, and I don't want to hear about it any more. In short, get the hell out of my mailbox.

At which point senior coders like Alan Cox and David Miller feared that a fork might be necessary if it proved impossible to revise the existing patch submission system that was centred around Linus. Fortunately, that split never happened, not least because its threat was enough to concentrate people's minds on finding a mutually satisfactory solution – in this case, first, to change the way patch submissions were made, and secondly, to use Larry McVoy's BitKeeper for overall source management, later replaced by Linus' own Git.

Ultimately, then, the spectre of a fork proved salutary for kernel development: it forced the main players to confront the growing problems, and find a solution, rather than just carry on and hope for the best.

Given this dynamic, I wonder whether it might be time to start thinking about forking Wikipedia – purely for its own good, you understand.

Some might say that such drastic action is hardly necessary, because Wikipedia is not faced by any looming crisis; on the contrary – it is going from strength to strength, with the English-language version alone storming past the two-million article mark. But there has always been an unresolved tension at the heart of Wikipedia's mission, one that goes right back to its origins.

Before Jimmy Wales's Wikipedia, there was Jimmy Wales's Nupedia, inspired by Dmoz, a volunteer effort to create a free version of Yahoo's hierarchical listings. Dmoz began in 1998 under the name Gnuhoo - which was inspired by GNU/Linux - before turning into Newhoo. It was acquired by Netscape and released as open content. As Wikipedia's co-founder Larry Sanger explained:

Originally [Wikipedia] was the Nupedia Wiki - our idea was to use it as an article incubator for Nupedia. Articles could begin life on this wiki, be developed collaboratively and, when they got to a certain stage of development, be put it into the Nupedia system.

That is, Wikipedia was originally a kind or rough and ready working area, where articles were knocked together and then polished for inclusion in the definitive Nupedia. The free-for-all nature of Wikipedia was one reason why Sanger later decided to set up his own Citizendium project, what he called a "progressive or gradual fork" of Wikipedia. That idea was later dropped, and Citizendium is now essentially a standalone effort to produce an online encyclopedia where the emphasis is on using the knowledge of experts to guide the creation of articles, rather than weighting contributions from anyone equally, as with Wikipedia.

Ironically, though, Wikipedia has been moving steadily towards Citizendium's philosophy. The original claim of being "an encyclopedia anyone can edit" has become less all-inclusive – not so much in terms of who may write, but rather as far as what they can write about. This involves the issue of “notability”:

Within Wikipedia, notability is an inclusion criterion based on encyclopedic suitability of a topic. The topic of an article should be notable, or "worthy of notice". This concept is distinct from "fame", "importance", or "popularity", although these may positively correlate with notability. A subject is presumed to be sufficiently notable if it meets the general notability guideline below, or if it meets an accepted subject specific standard listed in the table to the right.

That is, Wikipedia is no longer interested in accepting entries about any old thing, but requires them to be “notable” in the above sense. Now, that's all very well if you aspire to be a dead serious kind of encyclopedia along the lines of the Encyclopaedia Britannica, but given that Wikipedia offered the hope of something more than just an online version of that dead tree monument to dead knowledge, I'm not so sure this attempt at increasing the respectability of Wikipedia is right.

For a start, it means that I can't just go to Wikipedia and find entries on any old subject: if my query is about something insufficiently “notable”, then it's back to Googling for an answer. But it seems to me that part of the promise and power of Wikipedia is that it could be the ultimate repository of knowledge – all knowledge, not just the serious, notable bits.

Of course, Wikipedia is perfectly entitled to take any direction it wants to, but given that I, at least, want something more, I wonder whether there might be others out there who would also prefer a more inclusive, less picky, Wikipedia – as it was in the beginning - one that routinely has entries on anything and everything. After all, the great thing about such online repositories is that nobody is forced to read stuff they don't care about. You could even offer users “notability” filters, so that you only saw the level of trivia you could stomach.

It would be easy for Wikipedia to accomplish this – it might even regard this rough and ready Wackypedia as the development branch for the “real”, grown-up Wikipedia – just as Wikipedia was originally meant to be for Nupedia. If it doesn't want to do that, fine – but maybe somebody else does: anyone for a fork?

Glyn Moody writes about openness at opendotdotdot.

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

I'm working on a wikipedia fork for open source related articles

David Claughton's picture

Hi,

I've just come across your article, and (although it's still in development) I can't quite resist plugging my own site http://encoresoup.net.

It's a fork of all the Free/Opensource software articles on Wikipedia, with the goal of allowing articles on non-notable projects to be added, and other useful content like usage info and howtos that are also not allowed on WP.

Be warned, it's very rough and not very usable at the moment, I'm in the middle of sorting out the Categories to make them more useful and I have a bunch of block updates using pywikipediabot planned to clean things up a bit, but I would appreciate any comments (particularly whether anyone other than me thinks this is a good idea ;-)

Cheers,

David.

Let a thousand flowers bloom

David Gerard's picture

Complying with GFDL on the Web isn't that hard. Just be sure to list it on http://en.wikipedia.org/wiki/Wikipedia:Mirrors_and_forks .

The main problem is that our English Wikipedia database dumps fail more often than not. This is regarded as a serious problem and attention is being paid to it, but our incredibly small number of tech staff (the joys of being a charity run on a shoestring) are run off their feet so it's not proceeding as fast as we'd like.

A common response to a subject area getting subjected to harsh notability "guidelines" is to create a specialist wiki on the subject. There's lots on wikia.com and elsewhere (e.g. comixpedia.org) started for just this reason. If it's under a suitable licence (dual-licensing under GFDL and CC-by-sa, for instance), then stuff of general interest can easily be copied across to Wikipedia as it's ready.

Thanks...

Glyn Moody's picture

...for the background info.

I'm doing an inclusionist fork of Wikipedia

Philip Hunt's picture

I don't like the notability guidelines on Wikipedia either. And I especially don't like it when articles I've created or worked on get deleted. So I decided to do something about it... I'm currently creating an inclusionist fork of Wikipedia. (It's not going to be called Wackypedia though :-))

Cool

Glyn Moody's picture

When's it appearing?

At least, no one can edit this page

Nightwish's picture

At least, no one can edit this page, otherwise you'd have Jimbo Wales' goons removing any reference to Larry Sager.
The fact that you can't trust the admins of wikipedia at all is the biggest problem with it, really. Everything else could be solved within a trustable organization.

This is the exact reason I

Cezar's picture

This is the exact reason I haven't donated to Wikipedia. It's a wonderful resource, but if it's just going to become the playground of elitists, then I want nothing to do with it.

A wiki for the 5 billion rest of us

Gregory Kohs's picture

There is a highly-functional fork of Wikipedia that carries no "notability" clause at MyWikiBiz.com. It's intended to be a semantic web wiki directory for the 5 billion people and businesses that aren't notable enough for Wikipedia!

The Fork.

Taran's picture

It actually seems like a good idea to me, though I don't see it as pitting two sets of editors against each other (because it ain't code). I might actually start working with a Fork if, as you point out, the notability issue is addressed. 'Dog Poop Girl' is in Wikipedia, but many people who have contributed in positive ways are not in the Wikipedia - as an example. This is partly the 'notability' bias you pointed out.

But there is a deeper problem to Wikipedia. Most monolingual people don't read the entries in other languages - I sometimes do. And they are almost always different, and not because of translation. Thus there is obviously more bias through language/culture, which is also to be expected but should not be present in something which at the least attempts to say it is a reliable source.

And even with all that past us - having 2 references instead of 1 is usually better. Unlike code, content allows people to read and allow critical thinking.

But in the end, I still don't see why I would do all that when I could simply self-publish and derive some trickle income. Until there is an economy around a project, it is implicitly unstable.

Interesting points

Glyn Moody's picture

I like the idea that open content differs from code in that it is additive rather than a question of alternatives. And I agree: there is an extra dimension that comes from the linguistic aspect that is almost totally ignored in Wikipedia discussions.

But I don't think that we do need an economy around Wikipedia - or at least one based on money: open source has already shown that people are happy to code for kudos, and I don't see why that shouldn't be the case for content.

Such a fork already exists

Larry Sanger's picture

Glyn, nice article!

You say: "I wonder whether there might be others out there who would also prefer a more inclusive, less picky, Wikipedia – as it was in the beginning - one that routinely has entries on anything and everything."

Yes, such a project already exists: it is called Citizendium. We already have articles about topics deemed too "unnotable" for Wikipedia. We do not have a notability policy; we have merely a maintainability policy, i.e., if we can reasonably anticipate that, over the coming years, a full complement of articles of a certain type will be able to be responsibly maintained, then you can start in on the first one. For instance, as editor-in-chief, I wouldn't mind if we had an article about each Pokemon card. Some of our editors might complain, but I would insist on it: I'm an inclusionist.

Great

Glyn Moody's picture

I applaud your ambition, although I too might give the Pokemon cards a miss - but that's the point: I can.

White Paper
Linux Management with Red Hat Satellite: Measuring Business Impact and ROI

Linux has become a key foundation for supporting today's rapidly growing IT environments. Linux is being used to deploy business applications and databases, trading on its reputation as a low-cost operating environment. For many IT organizations, Linux is a mainstay for deploying Web servers and has evolved from handling basic file, print, and utility workloads to running mission-critical applications and databases, physically, virtually, and in the cloud. As Linux grows in importance in terms of value to the business, managing Linux environments to high standards of service quality — availability, security, and performance — becomes an essential requirement for business success.

Learn More

Sponsored by Red Hat

White Paper
Private PaaS for the Agile Enterprise

If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.

Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.

Learn More

Sponsored by ActiveState