…all bugs are shallow

Written by Andrew Rens on September 23rd, 2011

bug n. 3.a : a germ or microorganism especially when causing disease”

Merriam Webster http://www.merriam-webster.com/dictionary

” bug n. An unwanted and unintended property of a program”

Hacker’s Dictionary

Proponents of free and open source software, and of open licences know that many classes of difficult problems are best solved by enabling large numbers of people to attempt solutions in a parallel ad hoc manner. Or to put it another way “given enough eyeballs all bugs are shallow.” With the probable exception of Steve Ballmer very few people disagree.

But there are still some who  claim that however useful an insight it is in regard to software that it cannot be applied to other difficult problems. A recent report in Nature shows just how mistaken that claim is.

In an article in Nature Structural & Molecular Biology entitledCrystal structure of a monomeric retroviral protease solved by protein folding game players‘ researchers report how gamers were able to figure out the molecular structure of an enzyme generated by a virus in only three weeks, solving a problem that had baffled researchers for decades.  The abstract reads:

“Following the failure of a wide range of attempts to solve the crystal structure of M-PMV retroviral protease by molecular replacement, we challenged players of the protein folding game Foldit to produce accurate models of the protein. Remarkably, Foldit players were able to generate models of sufficient quality for successful molecular replacement and subsequent structure determination. The refined structure provides new insights for the design of antiretroviral drugs.”

For those unfamiliar with abstracts of scientific journals this is a remarkably clear abstract, perhaps because the contributors have some experience in explaining their work to a ‘non-expert’ audience.

Teams of people who are not trained in molecular biology were able to produce a far better result than software. Of course the gamers were able to achieve something meaningful only because of the preceding scientific work of researchers, and the software that renders the graphic representation of the molecules and their construction.

I predict that as the news spreads we are going to be subject to two annoying typed of generalisations. The first, intoxicated with technotopian exuberance will declare that we don’t really need expert researcher, teams of volunteers can do science on their own. The second, aghast at everything that has happened since 1987 or possibly 1954 will querulously inform us that they’d rather a medical system run by trained doctors than crowdsourced from hormonal teenagers.*

But to anyone actually paying attention this is not gamers vs researchers it is games and researchers together.

* Ironically medical systems are run by politicians and accountants.

 

The next legal hack: harmonising software contributer agreements?

Written by Andrew Rens on September 8th, 2011

Open licences also known as public licences are an ingenious fix to a legal problem. The legal problem is that the default of copyright law is set to closed. The default setting assumes the kind of hierarchical command and control system that built the pyramids. The pyramids are wonderful artefacts of an ancient culture, but they are also the products of very specific circumstances; agricultural circumstances, absolute monarchy and not least slavery.

There is another way of co-ordinating large public works, the way of voluntary co-operation exemplified by the creation of the largest human knowledge artefacts; Linux and Wikipedia. But copyright law, due to it fraught history, is actually set up to make it harder for people to co-operate voluntarily to create so that it requires an active legal act to enable others to make use of your knowledge, when that knowledge is recorded. People can do this through a legal hack known as a public or open licences. A public license is upfront permission that people can use a contribution to a software project.

There are quite a few flavours of these licences; and each gives different permissions. This has prove surprisingly unproblematic. The hackers and hacker lawyers who work with these licences have devised another hack, contributor agreements. These agreements by contributors give a trusted party additional rights that enable the licensing of the contributions under multiple public licences and sometimes enable the trusted party to sue to enforce the public license.

As an aside although there are several reported judgements in which people were found to have unlawfully included openly licensed work in their works (which they had claimed were their own and “all rights reserved”). However I have not seen a reported judgement in which someone infringed copyright by applying an open licence to work to which she did not own the rights. If you come across a decision of a an actual court which finds that this has happened then please tell me about it.

Not all contributor agreements are the same. This isn’t necessarily a bad thing in itself, any more than that there are competing open licences. Open licences and contributor agreements already enable frictionless co-operation unimaginable to those still trying to make the pyramid system work. But if contributor agreements can be harmonised then even greater co-operation at even greater scales becomes easier.

Harmonisation doesn’t require that all contributor agreements should be identical instead a few standardised agreements that clearly convey both what they require and enable can cover the whole conceptual space in an easily intelligible way.

This is the goal of the Harmony Project. You can generate a contributor agreement on the site. License geeks can join a mailing list to comment on and contribute to the project.

The Shuttleworth Foundation wants to help the Harmony Project grow and is recruiting a leader for the project who will be awarded a Shuttleworth Foundation Fellowship*. You can read about it on Helen Turvey’s blog.

PS. If you aren’t already familiar with the idea of public or open licences for Software take a look at The International Free and Open Source Software Law Book.

* Full disclosure: I held a Shuttleworth Foundation fellowship from 2007 to 2010.