Category Archives: wiki

Clearspace X Community Software

Yesterday, we issued a press release about Jive Software’s new Clearspace X product. Clearspace X is:

a special edition of Clearspace for companies interested in creating productive and engaging online communities for their customers and partners. In the past, companies have had to “glue together” separate applications for blogs, wikis, documents and forums, resulting in disconnected people and content, and low participation rates. Clearspace X unifies these collaboration tools into one system, bringing them together through a clean, user-friendly interface and integrated incentive system.

Using Clearspace X, companies can quickly and easily create compelling public-facing communities, enabling users to share information and ideas with each other via discussions, structured wiki documents, moderated blogs and even files (like Word, Excel, PowerPoint, and PDF). Users can keep abreast of recent activity in the community through email notifications, instant message alerts and RSS feeds. (quoted from the Press Release)

We use Clearspace internally to manage our company as a community with constant interactions using discussion forums, document sharing, wiki editing of documents, internal blogging, tagging, and much more. This software is the main reason that I was able to be so productive my first week on the job. Clearspace X is similar to our Clearspace product, but tailored to the needs of an external community.

An added benefit of my role as Director of Developer Relations at Jive is that I get to give the product away for free to non-commercial developer teams. This includes open source projects, student coding projects, and other non-commercial teams of software developers. I’ll have a simple web form for requests available on the Jive Software website in the next couple of weeks, but in the meantime, drop me an email if you qualify for a free license of Clearspace X: myfirstname at Jivesoftware dot com.

Dogfood: aka Week 1 at Jive Software

My first week at Jive has been a whirlwind of activity, and I think that I have been super productive for the first 5 days on the job.  I’ve completed a first draft of how we might build Jive’s new developer community on our newly released Clearspace X infrastructure. I am re-working the process for how we give away free licenses of Jive’s Clearspace and Forum products to open source projects. I’ve put together a new demo script for our CEO to use at BarCamp – customized for what I think will be the audience at BarCamp. I was also able to get confirmed speaking engagements at Defrag and OSCON this week.  All this while being constantly distracted with last minute BarCamp details as the co-organizer of the BarCamp Portland event this weekend (note to self: next year, do NOT start a new job the week that you are holding BarCamp!)

How was I able to get all of this done while getting up to speed in a new company?  It comes down to dogfood, specifically, to eating our own dogfood at Jive.  We use the current Clearspace beta product for all of our documents, to hold discussions, for blogging, and more.  Most of the information that I needed was already in Clearspace.  For new information, I just started discussions in Clearspace where I asked other Jive employees about things like what to name the new developer community, how to promote our new developer community, and more.  I posted all of my work as wiki documents in Clearspace, and because everyone uses it, I was able to get feedback and information from across the company.

We are also avid users of our Openfire / Spark IM solution with every Jive employee already populated in our buddy lists from day 1 on the job. I worked with an employee in Canada over IM to help him reproduce an issue that I was seeing in our beta product, discussed our Ignite community with our CTO, negotiated with our web developer on resources to get some web forms completed, and much more.

I have to say that Jive seems to be a great fit for me.  I’m working with people who are just insanely smart, who live web 2.0 technologies, and we’re working on some really cool collaboration software.  Did I mention that we are hiring?

Web 2.0: What CIOs Want vs. What CIOs Have

I was just reading Richard MacManus’ coverage of Forrester’s recent reports about web 2.0 in the enterprise:

“Forrester Research has just released two reports concerning ‘web 2.0’ in the enterprise. Forrester recently surveyed 119 CIOs on the topic and their answers illustrate what IT honchos want – and don’t want – from social software technologies such as blogs, wikis, podcasts, RSS, social networking, and content tagging.

According to the report entitled ‘CIOs Want Suites For Web 2.0’, the enterprise Web 2.0 market “is beginning to consolidate”. Apparently CIOs have a strong desire to purchase web 2.0 products “as a suite, as well as an equally strong desire to purchase these technologies from large, incumbent software vendors.” 61% of respondents indicated that they would prefer both a suite solution and a large, incumbent vendor. According to the report, “integration issues, longevity concerns, and the occasional lack of polish” are counting against small vendors.” (Quote from Richard MacManus on Read/WriteWeb)

The data is interesting, but I am not sure that Forrester was asking the right questions or the right people. My experience with web 2.0, and other innovative technologies (open source, etc.) is that there is a big gap between what many CIOs want / think they have and what is really happening within their organization. Those of us who are passionate about web 2.0 technologies just tend to use them. This often means that we bring things like IM, wikis, and more into our corporate life as productivity tools regardless of whether or not the technology is officially sanctioned. For example, Intelpedia, an internal Intel wiki, was started as a grass roots effort on a test server without “official” buy in because Josh Bancroft and other Intel employees thought that Intel needed an internal wiki to help manage information. A better study might have been to ask people a few levels below the CIO about the web 2.0 technologies currently being used in their organization.

CIOs may want web 2.0 suites from larger, incumbent software providers, but I suspect that the reality of what is actually used within enterprises over the next few years will differ significantly from this CIO vision.

Super Bowl and RecentChangesCamp Weekend

If you are nostalgic for the dot com Super Bowl ads circa 2000, you might want to check out the SuperDotComAds from Meebo, Technorati, and others on YouTube.

Where will I be this weekend instead of watching the Super Bowl? With all of the other geeks at RecentChangesCamp, of course! I just Tivo the game to watch the commercials anyway.

RecentChangesCamp is free, and it runs from Friday morning through Sunday afternoon in Portland. If you are in the area, you should check it out. Proposed topics include wikis, collaboration, identity / OpenID, and more!

Using Wikis for Corporate Collaboration

I just posted an entry on my Intel Trends in Web 2.0 blog about how “Wikis can be a great collaboration tool for use internally within the corporate environment or externally for use with customers or clients.”

If you want to learn more benefits of using wikis and hear about how I have been recently using wikis for collaboration, please visit my Intel Trends in Web 2.0 blog.

The Great Encyclopedia Debate: Wikipedia vs. Britannica

The Wall Street Journal today contains an interesting debate between Jimmy Wales, Wikipedia‘s founder and chairman of the Wikimedia Foundation, and Dale Hoiberg, senior vice president and editor in chief of Encyclopaedia Britannica. Here are a few of the most interesting snippets:

Wales: “We believe that encyclopedias should not be locked up under the control of a single organization, but a part of the healthy dialog of a free society.”

Hoiberg: “But there is little evidence to suggest that simply having a lot of people freely editing encyclopedia articles produces more balanced coverage. On the contrary, it opens the gates to propaganda and seesaw fights between writers with different axes to grind. Britannica draws from a community, just as Wikipedia does. Ours consists of more than 4,000 scholars and experts around the world who serve as our contributors and advisers. … While Wikipedia may welcome scholars, all the reports I’ve seen suggest that most of the work is done by individuals who, though very dedicated, have little or no scholarly background.”

Wales: “Artificially excluding good people from the process is not the best way to gather accurate knowledge. Britannica has acknowledged the value of having multiple contributors, although of course because they are proprietary rather than freely licensed they would have a very hard time attracting the kind of talent that we have. The main thrust of our evolution has been to become more open, because we have found time and time again that increased openness, increased dialog and debate, leads to higher quality. I think it is a misunderstanding to think of “openness” as antithetical to quality. “Openness” is going to be necessary in order to reach the highest levels of quality. Britannica has long been a standard bearer, and they have done a fine job within their model. But it is time to work in a different model, with different techniques made possible by new technologies but the same goals, to reach ever higher standards.”

Hoiberg: “I can only assume Mr. Wales is being ironic when he says Britannica would have a hard time attracting the kind of talent that Wikipedia has. Britannica has published more than a hundred Nobel Prize winners and thousands of other well-known experts and scholars. Contrary to Wikipedia, Britannica’s contributor base is transparent and not anonymous.”

Wales: “We have spoken openly about some of the challenges and difficulties we face at Wikipedia. Not long ago, you suffered some bad publicity due to errors in Britannica. Have you considered changing your model to allow quick, transparent responses to such criticisms as a way to achieve a higher quality level? “

Hoiberg: “I must point out that Mr. Wales’s inclusion of two links in his question to me, one to Wikipedia itself, is sneaky. I have had neither the time nor space to respond to them properly in this format. I could corral any number of links to articles alleging errors in Wikipedia and weave them into my posts, but it seems to me that our time and space are better spent here on issues of substance.”

Wales: “Sneaky? I beg to differ. On the Internet it is possible and desirable to enhance the understanding of the reader by linking directly to resources to enhance and further understanding.”

Quotes from the Wall Street Journal

We have not resolved the great encyclopedia debate, and we probably never will. Both models have their strengths and weaknesses, and as a result, both can probably learn from the other, which is why the title of the WSJ article, Will Wikipedia Mean the End Of Traditional Encyclopedias?, is so misleading. The title implies a black and white solution to an increasingly gray world . We can have both a community encyclopedia and a traditional encyclopedia without having to choose one over the other. This gray world that we live in has enough room for both approaches to continue and thrive.

Collaborative Journalism at Wired

According to Wired news,

In an experiment in collaborative journalism, Wired News is putting reporter Ryan Singel at your service.

This wiki began as an unedited 1,059 word article on the wiki phenomenon, exactly as Ryan filed it. Your mission, should you choose to accept it, is to do the job of a Wired News editor and whip it into shape. Don’t change the quotes, but feel free to reorganize it, make cuts, smooth the prose, or add links — whatever it takes to make it a lively, engaging news piece. (Quote from the Wired Wiki)

Ross Mayfield reminds us that collaborative journalism does not always go according to plan:

Last time someone tried this it was a disaster, but Wired News has boldly put an article about wikis into a Socialtext wiki for anyone to be a Wired editor. … This is of course different from the LA Times experminent as there is a clearly stated goal. It will be interesting to at least watch. (Quote from Ross Mayfield’s Weblog)

I am particularly interested in this experiment, since I am in the process of doing something very similar as part of an O’Reilly Media project. Danese Cooper and I are in the process of writing a book on the Art of Community, which will start as a wiki. We are taking a similar approach by writing an initial first draft of the chapters, posting them to the wiki, and allowing the community to be our editors / collaborators on the project. We are still working on the details, but I hope to learn from the Wired news experiment.

On a related note, I couldn’t help making a couple of edits to the Wired Wiki. This should be fascinating to watch.