A commenter on a previous blog post asked how much use the Atlassian internal wiki gets. I have no idea if these statistics will be interesting to anyone, but somebody asked, right?

A bit of background first. Our internal Confluence instance has been running since late 2003, back when Atlassian had a staff count in the single digits. Since then we've pretty much doubled in size every year to our current total of around 125 staff. In that time we've amassed:

• 65 global spaces, 150 personal spaces.
• 106,600 revisions of 10,400 pages, by 176 unique authors, with 2300 comments.
• 3,000 blog posts by 130 unique authors with 5,700 comments.

In a totally meaningless comparison, that makes our wiki one tenth of one percent the size of Wikipedia. On the other hand, Wikipedia averages only slightly less than two pages for each registered user, so we're a lot busier per capita. :)

The average of ten edits per page seems a little low (Wikipedia averages 16). It might be more interesting to see a distribution graph, since many pages (timesheets and meeting minutes, for example) will 'settle' quickly and are unlikely to see much editing, while at the other end of the scale there are a couple of pages that are updated every day (or even every hour) by automated scripts.

The "busiest" space is our support space, which has 270 pages, but 20,000 edits. In contrast, most personal spaces average two or three edits per page, perhaps reflecting their less collaborative nature.

Most of the 3,000 blog posts have been made in the last year. Blogging only really took off inside Atlassian when we added personal spaces to Confluence mid-2006. By way of contrast, the top ten spaces by page count are all "global spaces", while nine of the top ten spaces by blog-post count are personal.

The most prolific blogger inside the company is me, with 200 posts (and 453 comments) in my personal space. Four spaces have more than 100 posts, 16 more than 50, and 78 have at least ten blog posts. Not a bad participation rate, given half the company wasn't even here a year ago.

(This data was gathered using the Global Statistics Plugin)

The Confluence development team have donned their santa hats, snuck down your chimneys, drunk all your whisky, and left behind a brand new, shiny Confluence 2.1 in your stockings.¹

We're very happy to introduce two highly-requested features, which are sure to prevent future outbreaks of violence around the Atlassian office. Autosave keeps you in touch with the Confluence server while you edit a page, ensuring that even if your browser crashes or Confluence is restarted, you'll only ever lose at most thirty seconds of your work. Meanwhile, concurrent editing notifications will warn you when someone else is trying to edit the same page as you.

For Confluence administrators, we've landed the atlassian-user library. Most customers will see no significant change from this, but if you're interested in integrating Confluence with LDAP, it's a big step forward. (See the release notes for more links on this one.)

There are also some performance improvements, and a double-handful of bug fixes. Not bad for less than a month's work!

You can find more information in the Confluence 2.1 Release Notes. Existing customers can download Confluence 2.1 today, and new customers can try a free, fully-functional 30 day demo.

¹ Four AA batteries required. Not included.

The Confluence User Guide has been updated to cover all the changes we made in Confluence 2.0. If you have any comments, suggestions or corrections, please mail them to confluence-support@atlassian.com, or leave a comment on the documentation site.

Read the Confluence 2.0 User guide...