B. Mann Consulting

Well, before I knew it, DrupalCamp Vancouver has snuck up on me. I mean it when I say it snuck up on me: I had pretty much zero to do with organizing it -- massive kudos have to go to Dave Olson, Dale McGladdery, and Ariane K (I know there are others, like the guys from Image X Media and jkparker on kick off party duty and and and...).

DrupalCamp Vancouver is this Friday and Saturday, May 9th and 10th, with a kick off party on Thursday night. As with all Drupal events, it's sold out (how are we ever going to fix this? more training!), and it looks like a great group of people are going to be gathering.

I spent this morning with Dale and Ariane reviewing the session submissions. We have a nice mix of newcomer, developer, and soft topics, as well as 2+ double sessions: one on organic groups, and one on design and theming. I say "2+" because we tried to schedule the talks so they "fit" together nicely -- like the back to back views + arguments segueing into panels 2, or the intro to module development that then continues with forms API advanced development. The sessions are up -- but the presenters are still "in progress" of being contacted.

I'll be doing a talk on install profiles with a couple of co-presenters, and leading a close out session on Drupal 6 and beyond. Frankly, I'm more than a little worried about Drupal 6, while at the same time so looking forward to Drupal 7, testing frameworks, and more RDF. It will be interesting to see how the discussion goes.

There are lots of talks to look forward to (I know lots of people have been asking about an intro to SVN). I've got my eye on the infamous heyrocker -- he's coming up to talk about the gnarly issue of staging Drupal between servers. It would be great if we could pool our solutions and get to more *code* in this area. I think drush is likely the proper building block.

Again, thanks so much to the organizing team that pulled this together: we're lucky to have such a great group of motivated people.

If you are missing DrupalCamp here in Vancouver, the next two I know of are DrupalCamp Toronto May 23rd - 24th and DrupalCamp Seattle June 26th - 27th.

First up, I'm going to do the call out of upcoming Vancouver events:

• Wednesday, April 30th (tonight!) is WordPress Camp, put on by the folks at Tazzu - I've got Dad night every other Wednesday so I won't be making it this time. Maybe someone should set up a Vancouver WordPress Users Group and do this regularly? VanWUG!
• May 9th and 10th is DrupalCamp Vancouver - I'll be talking about install profiles and likely a "getting started with Drupal" talk where I go through all the core modules; more on this in a full post
• early June date TBD DemoCampVancouver07 - back to the "regular" format of 30 second pitches and voting on stage for full talks; maybe we'll do this right after the F&F event

Check Miss 604 for another recent event round up.

In general, I'll mostly be doing full descriptions of events that I'm hosting / help organize around startups will be over at the Bootup Labs blog. Coming soon there is a Vancouver Founders and Funders in June after the Toronto event.

OK, on to the topic of "one calendar". Or rather, a consolidated calendar. There really are a lot of events going on in Vancouver, and it's hard to schedule new ones, it's hard to get a central overview of them, and it's hard / annoying to cross post Upcoming / Facebook / wikis / etc. Several people coming to DemoCampVancouver have said something along the lines of "I'm new in town, how do I find out about more events". Answers like "read these 10 peoples' blogs isn't really a solution.

I had lunch with Rob Lewis from TechVibes the other week. TechVibes continues to work on re-vamping their site (they'll be going through a major re-tooling over the summer) and we came around to the subject of events.

TechVibes has an events calendar, but it's painful. Yeah, they know it :P We talked about adding value there, specifically getting the community involved and providing something of value that the wider community could get involved with and rally around (e.g. not a TechVibes direct "property" per se).

I came up with two concepts.

One is for TechVibes to enable cross posting from TechVibes to Upcoming and other sites (Facebook? can anything post an event to Facebook using the API?). Post in one spot, get cross posting goodness "for free", which sounds like a good reason to post to TechVibes for those of us organizing and promoting events.

In general, I'm a fan of Upcoming. As Brendon said, it's great to use in San Francisco, since it's got full coverage of everything from tech events to arts. Here in Vancouver, coverage is a little spotty. I try and enter everything there because it is on the public web with a permalink (as opposed to Facebook...).

The second concept is around TechCouver. Buzz Bishop is leading the media charge to make this another Vancouver nickname - and that's great. So let's make TechCouver a local aggregator of tech-related blog posts and events.

The map is great as well, and we could use both. Basically, have tech companies and bloggers enter a listing for themselves including an RSS feed. We aggregate all the feeds, and run our own TechMeme for Vancouver. Well, minus the secret algorithm -- I'd like to do voting so we can see "best of" posts as well as the "river of news" of recent stuff.

So, one central spot for tech related postings and events, one central spot we can direct people to, to find out what's happening in TechCouver.

What do you think? Is this interesting? Useful to you? Would you visit it? Would you subscribe to it and/or use the OPML file it would generate? Let's use this TechCouver wiki page to discuss features and such, or comment here.

Looks like I'll be on CTV Newsnet at 12:15pm today, talking about Rogers bringing the iPhone to Canada.

Of course, the funny thing here is that there are many many people in Canada who already have the iPhone, in its "unlocked" edition. John Biehler's iPhone category is my source for all the latest in unlocking and cool applications.

The rumour seems to think that part of the delay and secrecy is because of the possibility that we might get the "new" version of the iPhone, with 3G (which is a faster data network connection). The other rumours about the new model (or models? maybe a "business" version to compete with RIM's BlackBerry?) are things like a much upgraded camera, or even a front mounted camera for video calling.

I'm genuinely happy that we're getting the iPhone "for real" in Canada, but I'm worried about a) the price of the contract and b) the length of any contract from Rogers. We're in a monopoly situation here, since there aren't any other GSM providers in Canada. Expect Telus and Bell to start heavily pushing the HTC Touch and various consumer BlackBerry devices like the Pearl.

Update: here's a direct link to my video clip.

Via INSNA and Mark Surman (who is doing seriously cool things with the Shuttleworth Foundation around Open Everything), I was copied on a request to look at prior art around a Microsoft patent application:

---

Microsoft has a patent application posted on the Peer-to-Patent site for Recommending contacts in a social network.

We are soliciting your help and that of the communities you know in finding prior art that will help the Patent Office to examine this application and determine if it deserves a twenty-year grant of rights to prevent all others from making, using, or selling this invention (this includes any research and R&D that would touch upon the claims of the invention, if patented). Can you let people know about this opportunity? We invite them to submit:

1. prior art
2. to annotate the prior art submitted by others
3. to vote on the relevance of the public submissions, and
4. to suggest fruitful avenues for research for the USPTO when examining this application.

Peer-to-Patent is not just another blog, wiki or website. It is an "extension" of the government institution! Posted information will be forwarded directly to the United States Patent and Trademark Office and be used in the examination process.

Here's a bit more detail about the application and about Peer-to-Patent:

Recommending contacts in a social network

A method and system for recommending potential contacts to a target user is provided. A recommendation system identifies users who are related to the target user through no more than a maximum degree of separation. The recommendation system identifies the users by starting with the contacts of the target user and identifying users who are contacts of the target user's contacts, contacts of those contacts, and so on. The recommendation system then ranks the identified users, who are potential contacts for the target user, based on a likelihood that the target user will want to have a direct relationship with the identified users. The recommendation system then presents to the target user a ranking of the users who have not been filtered out.

After the jump, the email I received from LoadMyTracks -- saying that the Globalsat DG-100 is now supported on Mac OS X with their application. Here are my previous posts about the DG-100.

Yeah, I know, I've been *really* bad about using it. I got busy right when I received it. Now it's time to re-invest some time into using it consistently. I want my Flickr map to have more photos on it (I recently uploaded my 9000th photo).

I just got contacted by ComputerWorld Canada, asking for my reaction to the new MySQL release:

I came across your blog and was wondering if you wanted to share thoughts on Sun Microsystems’ announcement that it will release the next version of MySQL (v. 5.1) in Q2 of this year? Do you see the new version as helping further drive adoption of the open source database, and help promote open source technology in general?

Well, this is good timing. TrevorO and I went down to the Sun Labs Open House (here's Trevor's take on a few things we saw at Sun). We were down looking at a lot of the "cloud" and related technologies that are coming up hot these days.

But back to the MySQL release. I think Sun's acquisition and backing of MySQL is great. I like the fact that all across their product line, Sun is committing to open source. They have everything from services to hardware to back it up, which just makes it easier for large enterprises to adopt open source. Maybe I'm biased, because Sun has been supporting the Drupal community for some time now, and have shown a great willingness to learn from open source communities and get better. Open source databases in general (and perhaps MySQL in particular) still do struggle with marketing perception against Oracle and MS SQL, so anything that can help raise the profile is a good thing.

But all is not great with MySQL 5.1. I don't follow the development that closely, but found an interesting post pointing out that when 5.1 is released, it's only 6 months until 5.0 gets end of lifed (EOL).

Let me close by pointing out the three things that I have been consistently saying to any Sun people that I come across:

1. Improve your social media marketing strategy: my feedback to the Sun Startup Essentials system has been that they should a) start a blog and b) publish weekly architectures of cool Sun software and hardware combinations. Yes, there is http://blogs.sun.com, and lots of high profile individuals from Sun like Tim Bray that are doing a great job, but it seems like next to none of this has trickled into the actual marketing departments. Give me an RSS subscribe widget and kill the email harvesting, people!
2. Fix MySQL clustering: it's hard, it's cranky, it needs improvement so that regular people can snap this together.
3. Open an engineering office in Vancouver: does this need a comment? Sure, it may be entirely self serving, but Microsoft is in town now, and I think you'll find a great base here on the left coast to find great people. Our concentration of open source experience in town will help, as well.

Sun is by no means perfect (they are a big co with all that implies), but I'm still really interested in some of the technology they have coming out of the labs, as well as their move to increased openness.

Last night I ended up staying at the Strutta offices until the wee hours of the morning, cheering the team on as they worked towards their launch today.

I worked with Jordan Behan to do a fun spoof of Michael Arrington (and yes, Strutta got a TechCrunch posting) -- I did the Fox news guy voice over. The posting from Jordan is, of course, meant to kick off a competition for the best Michael Arrington impression. Personally, I think someone should get out the sock puppets... :P

We actually ended up dragging Kevin Marks back to the Strutta HQ, in town for Open Web Vancouver. It was great catching up with him in his new role as Developer Advocate at Google -- oh, and a kick ass paper airplane folder, so I expect him and his sons to compete in the Strutta best paper airplane round. Kevin, you wanted me to complain about Google's messed up identity system -- I did this last January and some pieces are better, but the big thing is that I can't use any of my Google Apps for Domains accounts to sign into Google Groups. Since I don't want to use my personal Gmail account to be on random mailing list, this seriously hampers me pretty much every single day. Please fix :P

Congrats to the Strutta team, I know you've got some Beta Bug-lets, but looks like people are having a lot of fun. We've been amusing ourselves flipping the little Flash widgets back and forth -- there are lots of nice touches like this all over the site.

P.S. Yes, it's Drupal. And, oh, look it's multi-lingual: I predict many more interesting multi-lingual sites as people focus beyond North America.

One of the outcomes from my trip to Victoria last week is some thinking about the social graph.

More specifically, you may recall that I've been using Flock. As it turns out, I recently upgraded my laptop to Leopard, and made Flock my main browser. This has given me increased exposure to their "people bar" -- a side bar that supports a variety of big community websites, like Facebook, Flickr, Twitter, and so on.

As I've been using this feature, and seeing the way that Flock "detects" features of different websites, I started thinking about how every community website could enable this functionality. Right now, the Flock team has to pre-integrate with the specific website's API to enable this functionality. But, just as they "detect" the presence of site-specific search engines, there is no reason that one couldn't expose a link header that indicates the presence of a social graph.

I know what you're thinking: "But Boris, how many people use Flock? Isn't this just browser specific functionality?" Well, no. First of all, Google has a Social Graph API that is already being crawled -- looking at FOAF and XFN.

Secondly, I got to thinking about all these site-specific applications -- like Twhirl that was bought by Seesmic. So, if we had some basic standards about this stuff, it would be simplistic to have one app that let us monitor / notify / update any of these systems. Yes, there will ALWAYS be websites that have more complex APIs with more features -- that are only accessible by implmenting *their* API to talk to them.

But for thousands of other community websites, built in Drupal, WordPress, Joomla, or what have you -- you suddenly have the same rich access to applications as the big guys. How many websites would encourage their users to install Flock or Twhirl if it supported *their* website?

Oh, and I'm completely skipping the linked data / RDF / Semantic Web factor of having community websites expose some part of their social graph, or at least make it available for querying by people that have the right credentials.

OK, so how does this look to the end user? I'll use Flock as an example, since I've got agreement in principle from them that they'll work with me on this, including help in defining some of the formats.

1. User surfs to community website where they already have an account (for simplicity's sake, we'll pretend a session is still open)
2. Flock detects a website that has a social graph available because of a header link that looks something like this:
   <link rel="socialgraph" href="/user/4426/socialgraph.rdf" type="application/rdf+xml" />
   (Note the user ID in there, because the user already has a current session open)
3. Flock does it's fun in browser slide down that says something like "This website supports a people bar. Would you like to add it?"
4. If the user clicks on "yes", then Flock initiates an OAuth request to be allowed to a) fetch the current user's social graph file and b) take actions on behalf of the user such as setting their status or sending a message/poking/whatever another user on the site
5. The user acknowledges the OAuth request and clicks some allow buttons
6. Voila! A fantastic site specific "people bar" right in your Flock browser

So, that was a VERY Flock specific flow, but as I mentioned with Twhirl up above, absolutely no reason that you couldn't do the same thing with those type of people notifier on your desktop apps / widgets / etc. -- just start by typing in the URL of the website, the app would go and discover the social graph link and/or initiate an OAuth request to authenticate, and all of a sudden you're directly monitoring the different community websites you're a part of directly. Bonus points to websites that expose the social graph as an XMPP Pub Sub endpoint so these apps don't need to poll constantly.

Now, I know the first thing we're going to have to do is fight a religious war over the format of the socialgraph file. I'm going to suggest some minimal FOAF format, since I'm a born again RDF fan.I don't want to go spraying email addresses all over the place, so perhaps either local unique user GUIDs or OpenID could be used as identifiers for each person. We actually don't need full "person" information -- a username, avatar, status message, and date stamp for last activity sorting should be the minimal set. Even status message could be option for smaller, less complex sites so almost anyone could support this out of the box: just show everyone on the site (yes, that's right...ignore any sort of "friend" connection) sorted by last active -- which could be a post / comment, or (again, simple support by many sites...) just date stamp of last login.

I'd like to think that the choice of OAuth as credentials for acessing this info isn't controversial at all. Feel free to layer OpenID in here somehow, but for the action-at-a-distance on which cool functionality can be built, this kind of a token system looks to be ideal.

What next? Well, surprise, surprise, I'm going to take a crack at getting this implemented in Drupal. Raincity Studios is already working on the OAuth module, which would be one of the main pre-requisites. Once the format of the social graph file is defined (calling Joshua, Arto, and maybe RalphM...), building the next piece shouldn't be too hard.

Ideally, something like the Gnomepal Drupal distribution would ship with this out of the box (for the really ambitious, Drupal 7 core!). And other systems like Marc Canter's People Aggregator could easily expose this social graph info as well.

I'm excited at the continuing growth of every website as a dynamic web application, and also of the exposure of data and APIs by this web of sites. This feels like the right path we're travelling on to get everything a little bit more interconnected.

Longer post on DemoCampVictoria01 forthcoming over on Bootup Labs, but this was a short little interview I did about the Juliet condo development, where the event was held.

So far, they get the "fanciest DemoCamp ever" award for the nice selection of wine and cheese to kick things off....

David Crow in Toronto picks up the community platform meme and lists some other tools / platforms available in response to Chris Pirillo's announcement regarding the building of Gnomepal on Drupal.

I already commented on Chris' initiative here, but here are some comments I made on David Crow's post:

Now, which of those listed platforms have portable data? Which of them are a suitable platform for building the (invariably) custom pieces that each community may want as they grow?

The tough part with many systems -- especially closed, hosted ones -- is that they provide great initial starting points, but then often lack in customization or growth options. And god forbid that your platform provider "go away" -- then you're completely stuck, and need to start over.

This is why I have chosen to go with fully open systems, because they can grow with communities and can never be locked down or disappear.

@Varun:
Facebook is ultimately closed and not a participant in the "open web". And it's someone else's platform with someone else's rules. I would hope that we steer around such closed instances and strive to connect openly.

@Peter Childs:
"What I’d like to see is a platform that recognizes communities are networks of interests (people & organizations) and doesn’t try to become a destination"

I think this is spot on -- don't try and a become a destination IN AND OF ITSELF -- but rather add value through various aggregation and hub features. This also seems to argue for mini-networks that cross sites.

Open platforms are as important as open data or any other cross site initiatives. I don't care what you end up picking as your community platform, as long as your data and your users can seamlessly interwork with the other systems out there. The network is not the destination.