Socialtext 2.0 Released

Congratulations to Ross Mayfield, Peter Kaminski, Adina Levin, and all the excellent folks at Socialtext for the release of Socialtext 2.0. Even bigger props for slipping in “Purple Consulting” in the screencast. I’ve been cranking so hard over the past six months, I didn’t have a chance to congratulate them on their Open Source release last July, so now I get to combine my commentary here. (In fact, I’m sitting on a bunch of Wiki-related posts right now that I need to push out; a lot of really cool stuff has been happening.) That’s good, because I have plenty to say.    (L72)

Socialtext 2.0 is an important release for three reasons. First, it doesn’t just look good, it’s highly usable. Adina and Pete deserve big-time credit for this. They’ve spent months painstakingly experimenting and testing the design. More importantly, they haven’t just focused on making it easy to use, but they’ve also agonized over how to accomodate expert usage as well.    (L73)

Have they succeeded? I think the personal home base concept is great. I love the fact that Backlinks are visible on the page and get lots of love. I love their new Recent Changes interface (and I hope to see a Tag Cloud view of the all pages index in the next release). I hate the fact that a Recent Changes link is not on every Wiki page. Both Pete and Adina are well aware of this beef, and I’m also well aware of their reason for not including it. Testing and user observation will tell what’s better.    (L74)

Second, Socialtext 2.0 has a really cool REST interface. Chris Dent has been boasting about it for months, but I didn’t look at it myself until Kirsten Jones walked me through it last week. (Her WikiWednesday presentation from earlier this month is online.) It really is cool, and it’s also useful. Congrats to Chris, Kirsten, Matthew O’Connor, and Matt Liggett for their excellent work!    (L75)

What’s great about this API is that it could very well serve as a standard URI scheme for all Wikis. This would obviate the need for a separate SOAP or Atom API. You just have a regular Web app, and you get the API behavior for free.    (L76)

For example, Alex Schroeder‘s currently going through the same process that Chris went through a year ago with Atom and OddMuse. An easier way around this problem would be to implement these REST APIs.    (L77)

(This is also a great opportunity for me to mention WikiOhana again, which gained great traction at WikiSym last month and which now has a lively Wiki of its own. PBWiki recently announced its own Wiki API, which is a good thing. We are all part of the same Wiki family. Socialtext and PBWiki need to talk about how their two efforts can work together. That’s the WikiOhana Way.)    (L78)

The third important thing about Socialtext 2.0 is that it’s Open Source. (Big props to Jonas Luster and Andy Lester for finally making this happen.) Here’s the thing. I think the announcement a few months back was overblown by a lot of blogosphere hype. The reality of all corporate Open Source releases is that — in and of themselves — they’re mostly meaningless. Mostly, but not completely. The fact that Socialtext 2.0 is Open Source means that other Wiki implementations can benefit from the great work that the Socialtext developers have done, from the APIs to the user interface. That makes for a healthier ecosystem, which is good for everybody.    (L79)

That said, the reason the actual open sourcing of Socialtext 2.0 (and any proprietary software project) is mostly meaningless is that the license is a critical, but tiny part of what makes Open Source software interesting and important. The big part is the community and collaborative process, and a lot of other things besides an open license are required to make that successful.    (L7A)

Before Socialtext went Open Source, I spent many hours talking to a bunch of people there about the impending release. I wanted to know how committed they were to making this a truly open and collaborative software project, because I felt the potential impact on the Wiki community was enormous. The answer I got was complex. The fact that everyone was willing to talk to me with no strings attached, in and of itself, demonstrated a commitment to openness, and I’m still grateful for that. The code itself will be a short-term bottleneck, as it needs a lot of work before outside developers will find it compelling. I also think the licensing terms are weaker than they need to be, although I also understand the outside pressures that make it so.    (L7B)

In short, I think the spirit is strong within Socialtext to fully realize the potential of this Open Source project, but there are also roadblocks. Hopefully, external pressures won’t squash that spirit. If Socialtext ever fulfills its potential as an Open Source company, it will not only help the ecosystem, but it will also tremendously benefit Socialtext as a business.    (L7C)

Video Interview at WikiSym 2006

Morten Blaabjerg, a Danish filmmaker, interviewed me at WikiSym last month and released the raw video under a Creative Commons license. I uploaded a compressed version of the interview (54MB) to Internet Archive. The interview runs about 12 minutes and covers a range of topics: Blue Oxen Associates, Wicked Problems, Wikis, and HyperScope. It’s a pretty good snapshot of what’s in my head these days.    (L6M)

An Evening with Danish Bloggers

https://i2.wp.com/static.flickr.com/62/218801606_2d3d0e5417_m.jpg?w=700    (L3I)

You can’t truly know another country until you know its food and its people. Thanks to Thomas Madsen Mygdal, I had a chance to do both last Friday in Copenhagen. Many thanks to all of you who came (14 in all!) and shared your stories and good vibes (and restaurant recommendations). Evan Prodromou teased me later about having a Danish posse. Well, you all can consider me part of your American posse.    (L3J)

I arrived in Denmark two weeks ago knowing almost nothing about the country, much less the goings-on there related to my professional world (other than Reboot). I left a week later, not only personally and culturally enriched, but also professionally enriched. There is a lot of interesting thinking going on in Denmark, and while the startup culture is not as active as it is in San Francisco or even other European countries, the desire to do with the group I met was very strong. That’s not always the case at these blogger meetups (which is why I generally avoid them, at least here at home.)    (L3K)

The evening began casually (other than a minor mixup over the meeting place) with drinks at the Barbar Bar in Vesterbro. We then walked over to Carlton for an excellent dinner. I had told myself beforehand that I wasn’t going to stay out too late, but I was enjoying myself too much. The whole group shifted to Joachim Oschlag‘s place (which was conveniently just upstairs from the restaurant) for more beer and conversation. It was hyggeligt!    (L3L)

Ah yes, hyggeligt. Hygge is a Danish word for… well, apparently, it’s hard to translate, and I’m not sure I fully grasp it. According to the English Wikipedia, hygge is equivalent to the German word, Gemuetlichkeit. Hygge denotes a sense of intimacy and closeness, and is often used to describe gatherings of people, where you share a sense of familiarity and fun with those around you. Think “hug,” but not as wishy-washy. It’s a sense of wholeness that comes from being around others, and there’s a strong association with the space that helps create this wholeness. You can see why I like this word. The notion of hygge resonates strongly with community, and I would argue that it’s a common pattern in High-Performance Collaboration as well as another aspect of Quality Without A Name.    (L3M)

I’ve got pictures of the gathering buried in my Copenhagen Flickr set. Michael Andersen also posted some pictures as well as a blog entry.    (L3N)

I can’t possibly do justice to all of the conversations I had that night, but here are some highlights:    (L3O)

Reboot and Open Space    (L3P)

A lot of these folks were intimately familiar with Open Space. A few of them knew Gerard Muller, founder of the Danish Open Space Institute and co-facilitator of the Open Space at WikiSym with Ted Ernst. Thomas had tried incorporating Open Space into Reboot a few years back, and it apparently did not work well. We talked a lot about success patterns in group process, especially hybrid processes.    (L3Q)

One of the biggest challenges with network as opposed to organizational events, where your participants feel compelled rather than obligated to attend, is getting people there in the first place. Most people interpret “emergent agenda” as “no agenda,” and they treat such events as networking rather than learning events. This is exacerbated by the length of the event, which is optimally three days for emergent group processes. (See Michael Herman‘s Two Night Rule. I’m starting to realize that many people — even those who are very good at group process — are unaware of the forces underlying the Two Night Rule, and it affects the design process.)    (L3R)

Framing the invitation is a critical component for circumventing this challenge, but it’s not easy. I urged Thomas and the others not to give up on more interactive processes, and suggested as a possible framing question for an event, “What could we accomplish together in three days?” I proposed linking such a Danish event with a similar one here in the States, perhaps associated with our “Tools for Catalyzing Collaboration” workshops.    (L3S)

Semco SA    (L3T)

Several people told me the story of the Brazilian company, Semco SA, and its CEO, Ricardo Semler. Semco is a remarkable study in decentralized, emergent organization. It’s a relatively large company, with over $200 million in revenue and 3,000 employees, and it’s aggressively decentralized and transparent. Employees set their own hours and salaries. Workers evaluate their bosses, and they regularly mix with others, regardless of projects, thus developing multiple skills as well as a greater appreciation for the many roles that are required to make an organization tick. It’s really an amazing story. Semler has written two books, Maverick and The Seven Day Weekend, both of which I plan to read.    (L3U)

I did some followup research, and I was surprised to see how widely known the Semco story seems to be. I follow this space closely, and I also did a considerable amount of research on Brazil for my Brazilian Open Source adoption study published in May 2005, but this was the first I had heard of the company or of its CEO. It’s yet another example of the group being smarter than the individual.    (L3V)

Knowing What We Should Know    (L3W)

Speaking of which, I chatted quite a bit with Raymond Kristiansen, a vlogger, about how to get more people aware of the stories they should be aware of. It’s a very difficult question. On the one hand, the notion of Collective Wisdom does not mean that every individual needs to know everything. On the other hand, it does imply that we should be able to quickly learn what we need to know when we need to know it.    (L3X)

We talked about the Featured Content pattern as a way of trickling up useful content. It’s an especially important pattern with blogs, which are great for tracking conversations, but — like Mailing Lists and forums — tend to obscure older, but still relevant content.    (L3Y)

On a related note, Raymond also kicked my butt about not creating screencasts. I promised Raymond that I’d have my first screencast up before the end of September. There, it’s in writing now.    (L3Z)

Alexander Kjerulf    (L40)

I’m a little reluctant to single Alexander out, because I walked away profoundly affected and impressed by many people. Nevertheless, he and his blog, The Chief Happiness Officer, get special mention (not that he needs it; his blog is far more popular than mine!) and soon, a blog post devoted entirely to our conversations for two very important reasons. First, he recommended a number of excellent restaurants in Copenhagen, and we ended up eating at two of those together.    (L41)

Second, every time we chatted, I found myself scurrying for my pen and notecards. It will take me three freakin’ years to follow-up with all of his stories and ideas, generated over maybe 12 hours of conversation. I plan on trying anyway, because there was a very high degree of relevance and profundity in everything he said. He is a plethora of ideas, knowledge, and — as his title implies — positive energy. I urge all of you to check out his blog, and to make an effort to meet him if you’re ever in Denmark.    (L42)

Denmark Assessment: What a Week

Damn. I’ve been back in the States for a little over 24 hours, and my body is still in pain. My Copenhagen trip last week started off great. It was mellow, I was walking around, exploring a new country, a new city, living in the moment while digesting my new surroundings. Then I started to meet people, passionate people full of energy, enthusiasm, and goodwill. You spend a few hours with these folks, and they blow your mind.    (L2Y)

That’s how it all started. The brain, which I had previously set to passive mode, kicked into active gear. Then WikiSym happened, and for three days and nights, I was constantly surrounded by another group of brilliant, passionate people. The brain kept consuming, and when the little safety valve in the back of my head told me to slow down, the brain kicked that valve shut and kept cranking. After dinner on the last night, slowed by a newly acquired cold and a week of little sleep, my body told me to shut it down. My brain just laughed. “You’ll be traveling for almost 20 hours tomorrow. Suck it up.”    (L2Z)

So I sucked it up. Went out for beers with a large group of people, closed down the bar, then headed to the hotel casino with the remnants of the group for a fresh batch of conversation. Shut down the casino too, and finally went to bed. A few hours later, I was on a train back to Copenhagen, and 24 hours later, I was back in San Francisco.    (L30)

Back in the day, I used to flaunt my endurance. Late night bull session? A mere jog in the park. All night work session? If the work was interesting, I’d gladly go two. Back in the day, I could back it up. Now, not so much. But old habits die hard, and now I’m paying the price. I’m suffering from severe jet lag, the cold has kicked into second gear, and I now have a stack of new information and experiences to digest into knowledge, in addition to the piles of work that were already waiting for me when I returned home.    (L31)

And you know what? I don’t regret it one damn bit. I had an outstanding time in Denmark. I saw many old friends, and made many new ones. My mind is churning with ideas, and I got a lot of work done. Sure, I could have stopped and smelled the roses a bit more than I did, but the roses are still around, and I’m smelling them now. Sadly, my body finally beat my bravado, and I’m missing the one year anniversary of Bar Camp this weekend, but it’s a fair tradeoff. Besides, that’s what the Wiki is for.    (L32)

WikiMania 2006: Quick Hits and Final Thoughts

I really enjoyed Wikimania, but it felt distinctly different than last year. A big part of it was personal. The conference was held in Cambridge, my home for four years, so the location itself was familiar and uninteresting. I was only there for three days, whereas last year I came early for Hacking Days, where I had a chance to get to know people better at my leisure. I also had much more on my mind, whereas last year, I was fully present the whole time — morning, noon, and night.    (L0E)

Part of it was the conference itself. It wasn’t as international as last year, but it was still quite good — one out of four attendees were from outside of the States. There were also more visitors, folks new to Wikis who came to see what this stuff was all about. Several of these people were fairly high-level, described by Jason Calacanis as “folks who ride on the back of builders.”    (L0F)

The same held true for RecentChangesCamp earlier this year, except the spirit was quite different. There, the visitors were eager to learn and to participate, and the community embraced them. Here, many visitors stayed at arm’s length, choosing to observe from afar rather than immerse themselves in this wonderful community. At Wikimania last year, a different group of us would go out every night, laughing, sharing stories, mixing with other groups. This year, there were more clusters, more silos. I saw people — especially the visitors — sticking with the folks they knew, rather than mixing with others.    (L0G)

That is not our community’s way, and I found it mildly distressful. To some extent, it’s the price of success — especially true in the case of Wikipedia — and the result of the culture that those not acclimated to Wikis bring to the table. To a large extent, process is at fault. I find it fascinating that a community schooled in self-organization and the value of emergence continues to organize top-down gatherings. If it’s not careful, Wikimania may eventually go the way of Linux World, Comdex, and many other conferences that began as a wonderful, generative community gathering and eventually became a meeting place for fast-talking salespeople.    (L0H)

Despite my standing in the Wiki community, I’m an outsider to Wikipedia, and I only have three ways of encouraging a shift in how Wikimania operates. The first and best way is to become active in the community and in the planning of the next conference. In an alternative world, this would have already happened, but the reality is that it’s not likely. The second and worst way is to preach to the folks in the community, which I’ve been doing. I find this distasteful. It’s my personality to effect change, not to talk about it.    (L0I)

The third way is to create a space where people can learn for themselves and to catalyze that learning as much as possible. This, in a nutshell, is the purpose of Blue Oxen Associates. I’ve had some success in this area. The FLOSS Usability Sprints exposed some folks to effective collaborative processes, including one of the original Bar Camp organizers. I was then able to point to Bar Camp as a model for the RecentChangesCamp organizers, who wanted to bring Open Space to the Wiki community. Both the usability sprints and Bar Camp helped spawn DCamp, the Bar Camp for the usability community. Our “Tools for Catalyzing Collaboration” workshops have inspired a number of people to pursue similar event models.    (L0J)

In addition to helping the tech community learn about face-to-face collaborative processes, I’ve also helped other communities — from Planetwork to the World Economic Forum — learn how online collaborative spaces can complement physical ones.    (L0K)

All of this is just the start. I have bigger and better things in the works. More importantly, the meme is starting to spread. I’ve helped initiate some of this, but there are many other sparks, and others are starting to fan the flames. We will learn how to collaborate more effectively. But it will take time.    (L0L)

I’m sounding a bit ominous, and it’s an exaggeration of how I actually feel. As I said before, all in all, Wikimania was wonderful. When you bring great people together and get out of the way, great things happen. Even if there are minor obstacles, great people will find a way around them. This has held true not just for the participants at Wikimania, but for the organizers. I am amazed at the efforts, commitment, and passion of Samuel Klein, Phoebe Ayers, Delphine Menard, and the many, many others who worked ridiculously hard to make this conference happen. The whole community deserves tremendous praise. I hope it continues to do what it does well, while unabashedly exploring ways to improve.    (L0M)

One goal that the Wikimania organizers should have for next year is improving conference Wiki usage among the participants. Effective self-documentation via Wiki is a staple of Blue Oxen‘s processes, and we’ve managed to influence many others about it, including Bar Camp and the Aspiration events. But the best Wiki usage at an event I’ve ever seen was at RecentChangesCamp. The community was already steeped in Wiki culture, and the process encouraged self-documentation. The fact that neither Wikimania nor WikiSym has seen effective conference-wide usage of Wikis is an indicator that something is blocking the community’s natural instincts. It’s also a lost opportunity, as those who attend the conference seeking to learn about Wikis miss out on the chance to experience them first-hand.    (L0N)

Quick Hits    (L0O)

  • I was amazed at the number of speakers who exclaimed how honored they were to be there. Some of them were merely experiencing the euphoria of speaking at a gathering of their peers for the first time. Others were hardened veterans of the speaking circuit, including Yochai Benkler and David Weinberger. Yochai even interrupted his traditional two months beach getaway to speak at the conference.    (L0P)
  • Speaking of David Weinberger, I saw him talk for the first time, and now I know what the fuss is about. He’s a wonderful speaker — self-deprecating, sharp wit, great sense of humor, and very thoughtful. He did a Monty Python-like parody of Lawrence Lessig‘s presentation-style that had the entire audience rolling with laughter, and he managed to slip in references to Hegel and Heidegger without sounding pretentious. But I had two beefs with his talk. (Boy, I’m just Mr. Negativity today.) First, he disputed the notion that knowledge is just in people’s head, citing all the knowledge associated with the artifacts that surround us. I understand the point he was trying to make, but I didn’t like how he made it. Artifacts are not knowledge. I generally find myself taking the exact opposite stance as Weinberger — emphasizing that knowledge is in our heads, because it stresses the human element we so often forget when we think about our relationship to knowledge. Second, he made a hypothesis about Wikipedia editing behavior that practically everybody in the room knew was wrong. He admitted that he was speculating, and gracefully acknowledged his error when informed of it, but he never should have made that mistake in the first place. There were many people he could have simply asked before making such a claim.    (L0Q)
  • The best talk from someone I had never heard of was by Seth Anthony, who spoke about Wikipedia editing patterns. See Ross Mayfield‘s notes for a summary.    (L0R)
  • Fernanda Viegas and Martin Wattenberg, the IBM researchers who created History Flow, gave an outstanding talk where they demonstrated some new visualizations of Wiki usage. Some of those visualizations are available in my Flickr collection. I particularly found their visualizations of user behavior interesting, because of past suggestions that such visualizations could be a powerful way to help casual readers determine reputations. The biggest obstacle (besides the computing power required to generate these visualizations)? Privacy. Even though these visualizations were based on public data, that does not automatically make it okay to make those visualizations available. Witness AOL’s recent fiasco (and read Tom Maddox‘s commentary).    (L0S)
  • I caught up with Denny Vrandecic towards the end of the conference, and I’m glad I did. He gave me an in-depth demo of Semantic MediaWiki, which he had first proposed (but had not coded) at last year’s Wikimania. The notion of encoding link types in Wikis is not new, but up until I saw the Semantic Mediawiki, the best implementation I had seen was Evan Prodromou‘s WikiTravel. I think the Semantic Mediawiki is a better approach. It’s less expressive than WikiTravel, but more likely to be widely adopted. I plan on experimenting with it and incorporating some of its capabilities into my own Wikis.    (L0T)