Boris Mann

I'm at Cloud Camp Vancouver today. It's at the Discovery Parks Vancouver venue where we had Barcamp Vancouver 2009. The Twitter hashtag is #cloudcamp #vancouver. I'll be doing updates throughout the day.

I'm kicking myself because I've been taking far too narrow an interpretation of "an open source approach". I've been focused on getting people to release data. That's the data analogue of tossing code over the wall, and we know it takes more than a tarball on an FTP server to get the benefits of open source. The same is true of data.

Open source discourages laziness (because everyone can see the corners you've cut), it can get bugs fixed or at least identified much faster (many eyes), it promotes collaboration, and it's a great training ground for skills development. I see no reason why open data shouldn't bring the same opportunities to data projects.

And a lot of data projects need these things.

I've been saying for a while that open data is a sort of new frontier. Open source is relatively wide spread and there is a general low hum of understanding about it in many places. For me, I sum it up by saying to people that they need to understand that their "code is worthless".

The next step is coming to understand about open data, and why we should care. Why we should convince people that their "data is worthless".

I'm fascinated by tools and experiences that let us "DIY". Whether it's using blogging tools to easily put content online, or cooking things from scratch, I like the fact that many things that seem hard or specialized are in fact things that anyone can do. With the Espresso Book Printing Machine, publishing a printed copy of a book has just joined that list.

Oscar's Art Books in Vancouver is one of only a handful of places in Canada that has an "EBM". The Espresso is made by a company called On Demand Books. They're looking to sell the machines to bookstores, universities, and other places where "like minded" people gather.

The New Year is kicking off with a bang. Bootup Labs moved into our new offices on Sunday (Cambie at Hastings, the Flack Block - come visit!) On Monday morning Danny was in the Financial Post (actually, @trevoro from @layerboom has much longer quotes on page 2). Then on Tuesday (technically yesterday as I'm posting this), I got a call from @lalondetcbc and ended up with a short CBC TV segment talking about whether bloggers should be legally required to disclose payments and other bonuses they receive. I was "opposite" Rebecca / Miss 604. That is, it was supposed to be opposing view points. Rebecca is an excellent blogger. She is a professional blogger (i.e. makes her living from her blogging activities). It's great that she's decided to use CMP.ly to indicate her disclosures: it shows the kind of honesty and transparency that makes her a great blogger. Do we need a law for it? Well, the FTC in the US thinks it does, but the guidelines seem over broad - a $5 discount at a restaurant and a positive review could net you an $11K fine? Of course, they say it will be on a case by case basis. Hmmm ... a law that is hard to enforce and is applied inconsistently? Sounds like trouble to me! I like John Chow's disclosure policy -- everything he posts he's making money from. This is a pure case of media literacy - people need to learn about the sources they are consuming and make their own decisions. Of course, journalists aren't covered under these laws at all. Why not? Good question, and quotes like this one in a Reason Magazine article don't inspire confidence: "Yet I don't remember any reviewer in any print publication ever disclosing that the record, the movie, the meal or the vacation was free." Lastly, it seems like Rebecca and I were set up to have opposing viewpoints, since we seem to be on the same page. Oh well, at least they spelled my name right :P I have a few quotes bookmarked under the tag FTC Endorsement Guidelines for further reading.

But will it actually be "nothing short of Apple’s reconception of personal computing," as Gruber opined? What I think he's getting at is the sentiment embodied by already announced products like the Litl and Google's Chrome OS. This is the middle ground between the desktop and mobile software platforms, which makes perfect sense for a hardware device that fills a similar position. The "reconception" part comes in when you consider how many people really need the power—and the complexity that comes with it—of a desktop platform, and in what situations. As a computer geek watching the Chrome OS introduction video, it's hard not to think about how much easier some people's lives would be (hi Mom and Dad) if they could trade technical complexities they don't care about for vastly increased simplicity and ease of use.

So, that's a wrap: BarCamp Vancouver 2009 is "in the can". I really enjoyed this year's event -- I even went to and gave some sessions! (yes, that's worthy of note - as an organizer, it can be hard to relax and get into the flow)

I attended a great talk by Dustin Sacks on the 10 principles of Burning Man and how they compare / contrast with BarCamp. It was great, and made me think about a ton of things.

One thing that stood out for me is that I think that BarCamp has "moved on" from its original core focus on making code -- in part because of the principle of "radical inclusion". We kept making it more inclusive until lots of people that weren't at the same "level" started coming (in tech, in background, etc. etc.). It's not a problem, per se, it's just evolution.

Yes, I've also read Morten, Todd, and now All Drupal Themes. Here's my take:

The growth of Drupal themes will directly mirror the growth of custom distributions. We are currently in the "it's so easy, we click together lots of Drupal modules from scratch" phase. Once there are more Open Atrium and ProsePoint type of distributions, with known modules / module options and features, then you can build great themes to support those functions.

Form follows function. I've tried to explain this a million times in the D7 process. Having a "great" core theme is impossible when we don't decide what kind of site Drupal should be optimized for out of the box. This same holds true for trying to build and market a theme that will apply and work well with the many vastly different kind of sites that one can build with Drupal.