I must apologize that these results have been so long in coming. The developers did their part and got me their votes on time. But I ended up at Enterprise 2.0 and our Boston Users’ Group last week, which turned out to be pretty all absorbing, leaving no time for Codegeist. E2.0 was an entertaining conference; the collaboration/social-software market has made tremendous strides in the last year. And I really enjoyed meeting many Boston-area customers (and a few plugin developers) at the Users’ Group.
But, to the topic at hand, the winners of Codegeist III. To remind everyone, there is one category for each of our pluggable products, and one winner in each category who will receive all this and more. I’ll be going in reserve chronological order, with our newest product first:
May I have the envelopes, please?


The Plugin Framework in Crucible is brand new. It shipped with Crucible 1.5, which is only a few months old. And the documentation for is still, shall we say, rudimentary. But we wanted to make sure that Crucible was in Codegeist, and that the brave early-adopters could give it a try.
Consequently, we had a handful of solid entries, and one winner: Ross Rowe’s Crucible Reporting Plugin. It allows you to generate reports about previous code reviews for statistics gathering, tracking trends or compliance and auditing reasons. This was a solid entry, exploring the new territory of Crucible plugin development, and demonstrating some of what is going to be possible as the Crucible plugin framework matures.


Fisheye, likewise, has only had its plugin framework for a few months. Shipping with Fisheye 1.5, the plugin framework is going to open new horizons for customization. In Codegeist III, developers got their first chance to explore.
Dan Hardiker of Adaptavist was able to get the very first Fisheye plugin working, the Developer Report Plugin. Like Ross, he started with a simple reporting framework, but he was able to demonstrate the potential of plugins in Fisheye, and point out some valuable directions for further development. He also took the extra step of providing tons of priceless feedback on the process itself, which will help us flesh out the documentation and capabilities of Fisheye plugins.


The Crowd category winner is Graham Bakay’s Grails Integration plugin. This is 1) and incredibly useful plugin that can expand Crowd to lots of new projects, 2) works exactly as advertised 3) is beautifully and throughly documented, and 4) takes advantage of our Atlassian’s recent salivating over the coolness that is Grails. Best of all, active development is continuing at a quick pace and I’m sure this is going to prove to be a valuable tool in the Grails toolkit. Unfortunately, a Crowd Connector Plugin doesn’t lend itself to interesting screenshots, but trust me, the technology is dead sexy.


The first place prize for Bamboo goes to Jonathan Doklovic for his Pre- / Post-Build Command Plugin. This is terrific plugin that enables all sorts of new possibilities for Bamboo. It’s one of those gateway plugins that opens up a whole new category of customizations. It gives admins the tools to connect Bamboo even more tightly to their build process.



As usual, Confluence was our most fiercely contested category, with almost thirty entries. After much discussion and debate, the Confluence developers selected Martin Breest’s Confluence Page State Plugin.


Here are a few of the reasons that the developers liked Martin’s plugin so much:

  • Martin wrote an excellent page describing his plugin. The screen shots that were attached gave a great first impression.
  • The video was excellent and really showed off how to use the plugin.
  • The installation process was smooth. Even though the plugin requires an extra step after installing the plugin (to modify the page template), it was very simple and worked first time.
  • Martin appreciated the wiki philosophy. This plugin is not a workflow plugin, it is simply an extra field attached to a page (along with some awesome support features). It does not break the fundamental idea of a wiki which is: you edit, everyone sees. A ‘rejected’ page is not hidden, it’s simply marked as rejected. You can find similar “flagging” functionality on Wikipedia.
  • The plugin adds some awesome support features. You can receive notifications on page state changes and you can review history of a page’s state.
  • Jira

    The Jira developers selected Sharvin Ragavan’s Scheme Configuration Plugin.

    The Scheme Config plugin is a full and detailed solution to a problem that many instances of Jira with lots of projects run into. A lot of thought clearly went into designing the solution, and the plugin is well documented. Sharvin also made use of several more advanced techniques with ajax interaction. The developer judges even mentioned that they wanted to recommend this to the support team as a diagnostic tool.

    So this officially concludes Codegeist III. Congratulations to all the winners, and a huge thank you to everyone who entered. I’ll be contacting the winners this week about your prizes.
    We were all super happy with the entries this year — we had entries in every category and lots of new ground was broken for plugin development in the new products. We had some very polished plugins submitted for the more established categories. There were lots of first-class entries, and next week I’m going to do another post highlighting some of our favorite honorable mention candidates, so keep an eye out.
    Over the next few days, all of these plugins will be moved into the main Plugin Libraries for continued use and development. In the meantime, feel free to use them and send feedback to the developers — we love to hear how things go in the real world.
    If there is anything that we can do to help you in your plugin development efforts, please let me know. We have big plans for improving plugin development this year. I’d love to hear your feedback on the whole Atlassian plugin process. What can we do better? What could be made easier?
    Thanks again, and I’ve already starting planning for next year’s contest!

    Finally, the results of Codegeist III