Podcast from Bar Camp NYC

Greg Heller interviewing Chris Messina

Greg Heller interviewed me Sunday morning at the tremendously successful Bar Camp NYC. There wasn’t a whole lot of wine involved this time but I nevertheless ramble on about taking over the world or other dumb stuff. Fortunately Greg did a great job of being provocative and keeping me on my toes! The sound is a little rough, but hey, Greg shoots from the hip and encodes at a low bit rate.

Take a listen and lemme know what you think.

The Case for Community Marks

Executive summary: In recommending the establishment of Community Marks, I propose that an alternative to trademarks is needed for community-based projects like Bar Camp and Microformats. The need for Community Marks stems from the non-commercial focus of these projects and the way these projects spread virally on the web. While we need to protect the integrity of a brand like Bar Camp, licensing and legal enforcement is too costly in terms of time and money to make sense for loosely joined communities. Therefore, if we can leave enforcement up to the community via the Community Marks denotation, we will be able to serve the vital function of identifying a community’s work and projects without burdening that community with undue legal process and enforcement costs.

Community Mark You can’t imagine how excited I am to write this post… not only is it an important one, but I’ve just gotten my busted laptop back and wow (is this bad?) I feel like I have my life back again. Never really thought I’d say such a thing, but eet’s true I teenk.

So I’ve been discussing the idea of Community Marks with a wide number of folks for some time (starting back when I was working on Spread Firefox and preemptively released the hi-res versions of the Firefox logo before I had full authority (that post has since been taken down)). I believe that this idea is an important tool which has grown out of the emergent philosophy that I see in the camps and in community-directed, “unowned” projects like Microformats.

Let’s get into it: I’m not a lawyer and I will never pretend to be, but that doesn’t really matter as far as I’m concerned and I’ll tell you why.

When it comes down to it, law is totally made up by humans. It’s just a system of conventions that codify certain beliefs about morality and righteousness within the context of a given civilization, society or group.

Laws weren’t and aren’t always penned in Congress, either. In fact, unbeknownst to most school children, that timeless classic that tells of the “life of a bill” is simply a story that you can choose to agree or disagree with. For the purpose of this discussion, I disagree with its fundamental premise that all laws (and rules governing trade and so on) must go through that process to become “real” or as enforceable as any other law.

Sure, this could be an academic or artistic inquiry on my part, whatev, that’s fine. Today, I’m interested in a little armchair-legislation, the kind that has no teeth or legal basis in our current legal system, but nevertheless solves an important need with which existing law currently doesn’t deal: the need for community owned and enforced marks (as in an open alternative to trademarks).

I won’t belabor where this all came from, but suffice it to say that the SpreadSpread campaigns (Spread Firefox, et al) have repeatedly encountered problems when commercially valuable trademarks need to be put in the hands of a community and the public domain is not an option.

The view heretofore has been that this is necessary, with dubious restrictions that protect the ability of the trademark owner to enforce their brand and indeed ensure the perceived quality that their logo, wordmark or servicemark represents.

In the case of Firefox or Flock, even though they are the result of countless hours of volunteer effort, you still need to be able to prevent some nefarious hacker in the remote expanses of cyberspace from releasing a spyware-laden version of either browser and calling it by the name of the official binary. Allowing such behavior could conceivably cause confusion in the mind of the consumer and potentially lead to an economic impact on the brand’s reputation. Therefore, it would be legitimate (and legal) for either Flock or Firefox to go after the offender and stop them from continuing such behavior. Just check out the on the lengths one can go to protect their IP in such a situation. Seriously.

And that’s why trademark was created: to make sure the people who own a brand can enforce their dominion over it to keep making money off it unfettered.

Um..

I mean.. uh… “to guarantee the integrity of a brand’s goods or services in order to prevent confusion in the marketplace.” (Stupid Freudian slips!)

So anyway, that’s all good and well, but it’s not enough. And it doesn’t address the issue I’m trying to resolve: the need for a mark that is owned, operated and enforced by a community that isn’t driven by purely economic interest. Instead, the motivation derives from the desire to uniformly represent their work product as the output of a specific community. Period.

So the case for community marks is primarily necessitated by projects like Bar Camp, which collectively is the product of scattered cadres of individuals the world over who take ownership of the brand on behalf of the larger community. None own the name or mark outright, instead they agree to hold an event based on Bar Camp, espousing its primary principles; in that way, they are extending the reach of the mark and therefore have earned a de facto license to use the Bar Camp logo and moniker. Now, should another separate event be created with primarily commercial gain in mind that uses the Bar Camp brand and co-opts the integrity of the name, it would be up to the community to go after and enforce the brand, either through blogging, boycotting or other subversive means. We simply don’t have the financial or temporal resources to go after such an offender, but we do have a small army whose response could be economically devastating to that effort.

I mean, let’s look at two precedents here: Creative Commons and Microformats.

With Creative Commons, you’ve got this idea that maybe not everything needs to be owned exclusively by default… Maybe you can allow for some distributed ownership of intellectual work in order to grease subsequent derivative creative expression. And maybe both the community and the original author will see benefits.

With Microformats, they’re leveraging community behavior to standardize the way we mark up our documents for the benefit of everyone. No one owns Microformats, though Tantek et al do a pretty good job shepherding the community. Nevertheless, the result of their work is something that the community takes pride in, identifies with, would be willing to expend individual effort to defend the integrity of.

And we learn two more things from them: to solve human problems as a primary objective and second to pave the paths of existing behavior. Don’t reinvent everything all the time. Just do what’s simple; just codify what’s already being done.

And gee, we’ve come full circle haven’t we?

Microformats are basically mini-laws for marking up your documents. Hell, go ahead and break them, do your own thing, there’s no punishment because the community doesn’t see punishment as being in line with its sense of justice. But joining up and following the rules, in this case, will actually bring you some benefits and not to mention, make your life (if you’re a user of the web, anyway) a little bit better.

So let’s codify this need to represent community works in a common mark. I want to be able to put a stamp on the work that I do within a community that identifies it to the world — that says: Me and a buncha folks made this and we’re proud of it. We did it not to make money but out of passion and love and because it’s in our nature to create without secondary purposes in mind.

And then let’s call it a Community Mark to make it clear what’s driving our purpose. It’s not tradeit’s the community, stupid! And from now on, if you want to create your own Community Mark, just slap a CM on your mark and hope for the best. Hell, we can’t enforce these things unless we hand them over to a broader community anyway — and since it’s really the community that owns the mark anyway, who better to look out for their wellbeing?

It’s an email, email, email world

I had a very useful and informative call last night with some folks from the Portland Usability group, organized by Frank Spillers of Demystifying Usability (a recording of the event is available for the next month). They had a lot of really useful feedback as they walked through the Developer Preview of Flock, explaining their expectations of certain interface elements and expressing confusion when they couldn’t figure out what terminology like “Star this page” meant or what a “Shelf” might be used for. Feature discoverability was another big problem; for example, they really thought that the history search was an awesome feature… but only once they found it!

On the one hand, a lot of the that I’ve been doing since we launched our Preview Release was validated. Much of the confusion they experienced has been addressed and hopefully resolved, though I look forward to doing more of these events both prior to and after each major release.

And since I was also able to give a high-level overview of where we’re going with Flock and what our vision of the web looks like (more sharing of timely “me-created” content than static-library-lookup-information old skoolness), they were able to point out aspects of Flock that didn’t seem to fit that vision — many areas, again, that we’ve been actively working on.

One thing that I didn’t expect — and this is more due to my own developeresque myopia than anything else — was that sharing to the group implied email! Yeah yeah, I know, what? Of the six people involved (albeit a small sample but nevertheless of fairly technology-familiar folks) only one knew of Del.icio.us… and that was Frank, the organizer. I purposefully chose not to explain what delicious was before we got started, instead interested to see how the group might discover or at some point desire “bookmark sharing”. Well, that never happened. At least in Flock (chalk one up for the Firefox del.icio.us extension).

Everytime they thought of sharing, they instantly turned to email (only Frank had previously blogged as well). So we’d get flows like this: Create a collection… Ok, want to share? “Oh, right click and email it!” Create a snippet in the shelf… Ok, want to share? “Oh, right click and email it!” And so on.

This was fascinating feedback. Apparently we have much to do to evangelize blogging, favorites sharing and similar socially-centric web services (Flickr had no traction with the group either) if we’re going to bring the benefits of Flock to folks who haven’t yet discovered that there’s a rich social social social world awaiting them!

…and yes, this really gave me even more enthusiasm for the direction that Flock is heading. We’re just a couple years ahead of the curve for the quote-unquote longtail, which honestly is a very very good place to be right now.

Hullavu Birthday, eh Matt?

AutomatticWell, I have to say, PMatty is turning out to be quite the quintessential capricorn. On the day that he turns twenny-two, he lands a CEO for Automattic, his new WordPress startup.

…Yeah, and not just any CEO… Toni Schneider of Yahoo, OddPost(read: Yahoo Mail), Konfabulator (read: Yahoo Widgets), et cetera and so on.

And speaking of Yahoo, I take it back. Google doesn’t own my life. Turns out (quite to my surprise mind you) it’s a Yahoo! Yahoo! Yahoo! . . . Yahoo! … world after all. Weird.

On the advent of neue design in technology, open source

Firefox set a good model for the rest of the open source world when it infused simple, clean design into a very useful tool. Seems to me that this trend is tantamount to what is coming up next in the world of technology and online living. Of course, you can’t really have one or the other, but the core differentiator that will set one app above the rest or result in widespread adoption will be rooted in user experience, not in the number of features or power.

So, I hate making predictions, but I think I can make a few observations about how design might well change the software/webapp landscape in the not-too-distant future:

  • Digg is outpacing Slashdot: everyone’s spreading the meme it seems; boy oh boy, ugly never hurt so bad
  • SourceForge will die from a thousand cuts (and it’s about time — no, 8′ tall ads and shiny will not save you from yourself)
  • Flickr and Bubbleshare will continue to gain over Ofoto (Kodak EasyShare Gallery), Smugmug: it’s the social, stupid!
  • Facebook and MySpace destroy the future of Friendster, et al: sorry, but they have their audience nailed
  • WordPress will continue its meteoric rise over more complicated (and ugly! (sorry, Drupal!)) apps like Drupal and Joomla
  • Ubuntu will outstrip RedHat on the personal desktop: Linux for Human Beings, sounds like a good place to start, doesn’t it?

But these are just my humble observations, and given that I’m no analyst, are subject to change, revision, contradiction and further extrapolation.

Mash Pit: Micro-Mashup Camp, renamed!

Mash Pit Logo

To avoid confusion and any potential trademark issues, I’ve decided to redub my previously monikered Mashup Camp as Mash Pit (naming honors go to the original Bar Camp chaperon himself Ross Mayfield).

This decision was made after a discussion I had today with David Berlind of ZDNet, who is planning the real-deal Mashup Camp sometime later this spring. Details will be forthcoming on his blog.

Anyway, our events are different enough to warrant the name change anyway. Whereas my event is more of a one-day micro-hackathon, David wants there to be many more participants (on the order of 25 times as many!) as well as host a number of mashup based contests with cool prizes and whatnot. So hey, I say, the more the merrier. No one can own the camp meme, so the more it spreads and gives regular folks the opportunity to get involved with all this new fangled techie stuff, the better!

If you’re interested in the Mash Pit, drop me an email at barcamp at gmail dot com or give me a couple days to get a wiki setup. Or feel free to start something on barcamp.org. Whatever floats your ship.

The fine art of mashing potatoes at camp

Not surprisingly, my proposed event has some precedents, notably in architecture, called charettes (“a charette is an intense effort to solve any architectural problem within a limited time.”) (via Brad):

There are two main advantages to working in the context of a charette. The first is that a charette operates in a highly collaborative atmosphere. Instead of an architect taking ideas and plans and going away to develop them on his or her own, a charette allows for the participation of everyone involved with the project, resulting in a highly charged and creative atmosphere. The inclusion of many points of view results in well-rounded and realistic proposals, with everyone satisfied that they were able to contribute. Secondly, Charettes are fast, and relatively inexpensive. In the intital stages of a project, the venture is necessarily highly speculative. It is important to keep costs at bay, while also moving forward quickly to take advantage of changing situations and often prohibitory deadlines. Charettes offer the opportunity to work safely and effectively within both of these boundaries.

Not only that, other people have thought hard about this kind of event before (also via Brad):

So it’s clear that we’re tapping into a model that’s already well established. It’s just futzing with the details that makes what we’re doing remotely unique. It brings me back to my ultra geeky days in high school when I was helping to build robots for FIRST: we’d get a bucket of parts, an interdisciplinary team with mentors from local companies and for a couple months we’d get our team prepped for the real competition by building robots collaboratively.

And what was significant about the design of the program were the contraints imposed upon us; we had a box of random metal gadgets and that was it. And yet every year, bigger, badder and more creative solutions would emerge in spite of those limitations. Nay, I daresay, because of them.

And so that’s why I want to limit the coworking event. Yeah, I could get a bigger space, but it wouldn’t be the same. And in the original ethos of creating these events to be repeatable, low-cost and sustainable, I want other people the world over to run their own mashup days…. With their own backchannels. With different communities and projects being represented and brought into the mix. C’mon, the Bay Area chapter of the Brat Pack 2.0 is cool and all, but these events are relevant the world over and we all need more reasons to travel for work. 😉

Whether you’ve got three people or three hundred, you can make an event like this happen. Seriously. And there plenty of people and a litany of historical resources out there ready to help get you started.

Remember the one thing that’s essential to the ongoing life and success of these things (just a little Canterian didacticism): anarchy still reins supreme in the valley of camps.