Under the Economist’s microscope

Title and Registration

The Economist has a very interesting article on its perceptions of open source from the old skool monetize-your-poo world. Tara puts it best: “There was a study that came out advising against buying small cars, what with all these SUVs on the roads today.”

Hmm. Yeah, you’ll notice that depending on how you frame the question (and depending on which ones you ask), the conversation will take on a vastly different character. Another way to put it: YOMV (your “objectivity” may vary).

So the Economist usually is pretty fair and balanced, so I’ll give them some credit. And I’ll cite some gems:

However, it is unclear how innovative and sustainable open source can ultimately be. The open-source method has vulnerabilities that must be overcome if it is to live up to its promise. For example, it lacks ways of ensuring quality and it is still working out better ways to handle intellectual property.

On describing the open source community ecosystem (similar to my own map of the Mozilla Universe from my Spread Firefox days):

From that core group, the open-source method lets a series of concentric circles form. First, there are around 400 contributors trusted to offer code into the source tree, usually after a two-stage review. Farther out, thousands of people submit software patches to be sized up (a useful way to establish yourself as new programming talent). An even larger ring includes the tens of thousands of people who download the full source code each week to scrutinise bits of it. Finally, more than 500,000 people use test versions of forthcoming releases (one-fifth of them take the time to report problems in bug reports).

On IP woes (with which we’re all familiar):

The question of accountability is a vital one, not just for quality but also for intellectual-property concerns. Patents are deadly to open source since they block new techniques from spreading freely. But more troubling is copyright: if the code comes from many authors, who really owns it?

The reason why CivicForge is necessary:

Rather than a democracy, open source looks like a Darwinian meritocracy. …even though open-source is egalitarian at the contributor level it can nevertheless be elitist when it comes to accepting contributions.

And challenges for the future of open source… can it create a wellspring of sustainable innovation or simply rip off proprietary products’ concepts and interfaces?

Even if the cracks in the management of open source can be plugged by some fairly straightforward organisational controls, might it nevertheless remain only a niche activity—occupying, essentially, the space between a corporation and a commune? There are two doubts about its staying power. The first is how innovative it can remain in the long run. Indeed, open source might already have reached a self-limiting state, says Steven Weber, a political scientist at the University of California at Berkeley, and author of “The Success of Open Source� (Harvard University Press, 2004). “Linux is good at doing what other things already have done, but more cheaply—but can it do anything new? Wikipedia is an assembly of already-known knowledge,� he says.

The second doubt is whether the motivation of contributors can be sustained. …Once the early successes are established, it is not clear that the projects can maintain their momentum, says Christian Alhert, the director of Openbusiness.cc, which examines the feasibility of applying open-source practices to commercial ventures.

And so what I’m left with is uncertainty; yet filled with hope. Clearly they’re on the outside looking in. They’ve grabbed a few butterflies, stuck them to a board and declared that these beautiful little self-organizing creatures are interesting but in all probability, impractical. Not interesting to our captains of industry.
“It just won’t work”, goes the refrain. “How could it?”

→ Begin rant.

And that’s all well and good because it won’t. Not with the old models in tact. Not with DRM fucking everything up. Not with opaque institutions coveting their intellectual property like it was a birthright. Not with your laws that stifle innovation, with your education system that keeps kids thinking in narrow rectangles, keeps down the free flow of work, of play, of curiousity.

What this article fails to do — purposefully — is to recount the story of open source from the perspective of the inhabitants of the bazaar. This is clearly the cathedral view on the open source phenomenon, asking, “How can we learn from their successes and monetize the fuck out of them?” Why not ask about how the proliferation of SUVs made our streets and highways unsafe?

Well, that would expose the fallacy of our faux-capitalist system. It’s not open, not free (enough), not a level playing field. Corruption is the grease on the axles that drive the wheels powered by the diesel of the sovereign state. When you come to our town, we invite you in, we see what you’ve done everywhere you’ve gone, everywhere you’ve been. Yet being open, we let you in. We even sit down and share scotch. But you won’t get it without becoming a part of it.

Not just like that. And not just by opening us up on an examination table, by poking at our vital organs, by studying our work, quantifying our behavior. To benefit from open, you’ve got to be open, believe open, see open, live open, want open.

So thanks, Econ, for stopping through; you’re welcome to return. I’ve always thought that you’ve done good work — but hey, realize that you can’t coopt this by writing about it as though it’s a company to be acquired or business practices to be assimilated. Keep at it, hopefully you’ll get it over time. I wish you well back at the altar.

The microformats-API assembly lines

Microformats x API Assembly Line - Photo: National Archives and Records Administration Still Picture Branch, College Park, Maryland

I was trying to put this point in history into some context and it dawned on me that Ford’s , which had a great influence on production and essentially precipitated the industrial revolution, is somewhat of a precursor to what we have today with open APIs and the potential proliferation of microformats.

Except that, with this combination of remixable and repurposeable data, the whole web community stands to benefit. The interesting issue — is that we must build tools that can interact with and leverage this technological coupling. Ford was no dummy: he sold cars to the people who made them, and put the cost at a level that his employees could afford.

Now if we could spread tools that can make use of microformats as well as produce them invisibly to the end users, this whole assembly line thing might actually take off. Yeh, just mebbe.

Mashpit II coming to South San Francisco

Mash Pit (color)Mashpit II will take place on April 15 at France Telecom’s South San Francisco offices (thanks, Sean!). I’m hoping to see a lot of microformats mashing and extension building, though obviously working on previous and new projects is encouraged as well.

So let me backup and explain a little about Mashpit and how it works (you can also read up on the first one):

  • First, Mashpit is unrelated to Mashup Camp. David Berlind and Doug Gold organized the first one not long ago and will be holding a second soon. Mashpit’s off on its own. 😉
  • Second, our focus is to stay modest and nimble — the first Mashpit had around 12 participants. Mashpit Dallas I had a similarly small number. We like small teams and keeping ‘pits manageable and high productivity is paramount to running a successful event.
  • Third, we focus on human problems. Though the context is certainly high tech geekery, we spec out our work as it relates to some human difficulty (i.e. sharing video with a wide audience or sending someone a message over multiple mediums) rather than expressing a problem in tech terms (i.e. “let’s improve the AJAX performance in the Rails stack”). This enables other ‘pits to carry forward the work begun at our event later on, regardless of technology. We want solutions, after all, to be effective in many circumastances. When you’re mashing, it matters less what tools you use than with the quality and how well your solution works for people.

For Mashpit II (II as in the second ‘pit in San Francisco), we’re hoping to get between 12-44 folks (kind of random, but based on space).

Here’s how I’m thinking it should work:

  • Sign yourself up on the wiki and then add yourself to the Upcoming page (yes, we need a mashup for that!).
  • Propose human problems that you’d like to work on on the wiki (and yes, you can be thinking about a particular mashup that you want to work on — just don’t describe it from a technology-centric perspective)
  • Depending on your interest and availability, get yourself to South San Francisco April 15!
  • We’ll convene, review our options, break out into teams and hack the whole day, reporting back on our progress some time in the evening — documenting everything on the wiki.
  • …Plan the next event?

Food and other good stuff will be provided — and we’d love to have some sponsors who want to pitch in and maybe provide a meal or snacks or coffee or take care of one of our other needs — drop me email at barcamp -at- gmail dot com and we’ll hook something up. It’s totally great to have a partner like France Telecom R&D supporting us — and it’d be great to have other passionate folks getting behind this too (wherever you are — like Barcamp, Mashpit is free to be copied, immitated and spread far and wide!).

Because of open source

Barcamp Austin Panel

I was honored to serve on a panel on open source with such greats as Doc Searls, Matt Mullenweg, Simon Phipps and William Hurley at Barcamp Austin. Organized and moderated by Raven Zachary, we touched on a number of facets of open source development, from the difficulty that Sun’s having open sourcing Java to the impending need for more usability and accessibility design in open source.

Doc’s done quite a bit of blogging after the fact and posted a very interesting and didactic chapter (in draft form) from his book, Open Sources 2.0, called Making a New World:

Note that podcasting became a hot category without the help of a large company. Instead, it began with the demand side supplying itself.

Now watch for big companies to jump in, and for businesses of all sizes to start making money. And watch for most of that money being made because of podcasting’s open standards and open source components, rather than with them.

It will eventually become clear to everybody that there is far more money being made because of open source than with open source. This is what we have to remember every time somebody asks, “How can you make money with (open source product)?” The answer is, “You don’t make money with it. You make money because of it.”

The because of principle is old hat in mature business categories, but it’s new to the software business. Too many of us still want to see “business models” for all kinds of goods that don’t belong on the income sides of balance sheets. Would you ask your telephone what its business model is? How about your front porch? Your driveway? Your clothes? Those things may help us make money; but they are not how we make money. Well, the same goes for open source products. They are means to ends. You make money because of them, not with them.

This line of reasoning smacks at why we need to open source all infrastructure, including OS’, including our economic system, including education, including government and of course, including supplementary enablers like phone networks, WiFi, IP and the entire legal system.

Utopic? Hardly.

So while, sure, it’s hard to imagine where we are today independent of where we’ve been, truly there’s never been a time in history when things have been so different, when anything has been so possible to so many, when the world, quite literally, is at our collective and individual fingertips. And yet we treat infrastructure — which is akin to our modern day waterways and subterranean sewer networks — as proprietary conduits for tranferring “privileged” data.

Think about it this way: if the water that’s piped into your house had DRM on it and only allowed you to use it for showers, how would you wash your clothes? If you were only allowed to make ice cubes, how would you make iced tea? If you had to pay $0.99 everytime you wanted a glass of water?

The whole lot of proprietary infrastructure needs to be open sourced and given back to people. To people over companies. To those who believe in self-determination.

Listen, here’s what’s at stake:

Ideas and hope need to flow like water if a civilization is to continue its ascension toward greatness. Impediments to that flow will stall growth. Fortunately, like a solvent, the culture of open source will continue to expand, will wear away at these impediments, to restore the natural flow of social capital, of ideas, of hope. Those who get this first will rise, and rise quickly.

Don’t think that the owners of the 21st century have been preselected. It may seem that the power brokers controlling the media, the government, our place in  world affairs, will continue to maintain their grip on the plight of our civilization. But I can assure you that that’s not a certainty. That which represented power in the previous century will come to represent weakness, repression, isolation — irrelevance. Civilization will advance not with open source, but because of it.

CivicSpace Announces Hosted Alpha Test

CivicSpace LogoMy buddy Zack Rosen over at CivicSpace Labs has announced an alpha testing period for hosted CivicSpace sites, along the lines of WordPress.com or Bryght. Back when I worked there, this was something that we spent much time discussing, and I’m thrilled to see this available:

Yes, that’s right, we are going to begin alpha testing a hosted CivicSpace service shortly. To say this has been a long time coming is quite the understatement. Three years, 30+ major software releases, thousands of sites, and the shared vision of thousands of supporters have gotten us to where we are today and have (hopefully) prepared us for this next giant leap forward.

The service will be similiar to Drupal hosting offered by Bryght but will provide the CivicSpace 0.8.3 Drupal distribution. In the future we hope to launch the ASP publicly as a low cost service for the non-profit & advocacy sector, but for now we are looking for a few brave CivicSpace community members to help us test it. Please fill out the form if you are interested in participating and we will be in contact with you shortly.

Go sign up!

The jaywalking podcast (GlitchNYC)

Jaywalking podcast - photo by Miss RogueBarcamps NYC and Austin veteran Eric Skiff captured a pretty decent interview with me touching on Flock and microformats while we made our our way back to SXSW from the Spaghetti warehouse yesterday. Give it a listen and then subscribe to GlitchCast. Good stuff — and really good audio quality given the circumstances!

Flock 0.5.13 released with 100% more Photobucket

Flock 0.5.13.2 released

Though we’re still struggling with speed issues on the Mac, we were able to squeeze in our second photo service for uploading and browsing photos: Photobucket! Download the latest release and check it out.

To give this new functionality a go, do this:

Open up Flock’s Preferences dialog, click the Web Services tab, choose Photo Sharing and then select Photobucket from the dropdown menu.

Switching photo services requires Flock to be restarted, and you’ll be prompted to do this after making your selection. After switching services, the Photo Browser and Uploader interfaces will change to reflect the feature set of the new service.

Oh, and we also took care of a nasty bug that would mangle title, description, and tag fields when using multibyte UTF-8 characters in the Photo Uploader.

EFF this, I’m moving to France

EFF the RIAA (clean)

PARIS (Reuters) – France is pushing through a law that would force Apple Computer Inc to open its iTunes online music store and enable consumers to download songs onto devices other than the computer maker’s popular iPod player.

Under a draft law expected to be voted in parliament on Thursday, consumers would be able to legally use software that converts digital content into any format.

It would no longer be illegal to crack digital rights management — the codes that protect music, films and other content — if it is to enable to the conversion from one format to another, said Christian Vanneste, Rapporteur, a senior parliamentarian who helps guide law in France.

French plan would open iTunes to other devices — by Astrid Wendlandt

There’s been a lot of interesting discussion related to DRM and Creative Commons (especially this morning’s Commons-based Business Models panel). If France moves forward with this kind of law, I think it’s only going to make this situation better, more open, more transparent and actually… better for Apple.

While perhaps not hugely impactful over the long term (in a globalized world, one country’s laws really don’t make a massive difference in WTO-scheme of things), setting the example (especially given the path to darkness France was previously on) will be tremendously didactic for the various and soon-to-be-obsolete DRM industries (ok, "soon" as in 5 to 12 years).

technorati tags: , , , ,

Flock ETech presentation available

Flock eTech 2006 slides available

I exported a Quicktime movie of my slides from ETECH (click to advance each slide). I’ll be doing a vidcast of the presentation in a week or two so you can get the full effect (and hopefully I’ll be able to share it in multiple formats).

For the two Demo Time slides, here’re the scripts I would have used if the network would have been less flaky:

Demo One

  1. on a friend’s page, hit the star
  2. rss reading
  3. topic aggregation (om and techcrunch)
  4. now click through to a one of the pages
  5. open the technorati topbar to see what’s going on

Demo Two

  1. open photo browser — look for etech
  2. photo uploading — ok i want to upload my own photos
  3. history search (to find something to blog — like the techcrunch page we saw before)
  4. blogging workflow (of page found through history and then drag in uploaded photo)

Leave me comments if you have any questions.

Update: By request from the management, I decided to remove 3 slides at the end of the presentation about “getting laid” since without context from the in-person presentation, it may seem a bit more lewd than intended.