|
|||
|
Welcome to the January issue. To kick-off the year... we're in Facebook, we're in Poland, we're looking for a killer Atlassian T-shirt design from you, and lots more. Happy reading!
|
||
|
Say "G'Day" to our newest developers in our Eastern European office. It's a bit early for a press release to announce the new office — we should probably wait for them to finish unpacking! — but we thought it was a good time to start spreading the news.
|
||
|
We're pleased to announce that EditGrid has created a plugin of their online spreadsheet that is now available to Confluence Hosted and Confluence Enterprise Hosting customers. What could be better than that? Well how about that the plugin is completely free to all Confluence Hosted and Confluence Enterprise Hosting customers. Where to next?
|
||
|
For those that don't know, Facebook's feed shows you activity (any form of action taken really) of all your friends across various different functions in a single place. Or alternatively, it looks like this (right). Why can't you do something similar for a development team? I played with this in Fedex VI with my Atlasbook project. While it was fabulously interesting (and could generate all manner of activity feeds), it is a little heavy weight for a normal development team and relied on replicating too much data to be practicable. So how could we build something similar into JIRA itself? With our upcoming JIRA Studio service, I've been championing a new feature that shows a stream of activity across various development applications in a single place. We're calling this the "Stream plugin".
|
||
|
Over the past year (or more) we've been working to transition our internal development from Maven 1 to Maven 2. As we've been going through that transition for our internal development, it's also effected our external development. With the Confluence build process in particular changing a lot from release to release, the process of building plugins became somewhat complicated. So we started working several months ago to totally revamp the plugin development process to take advantage of the tools that came with Maven 2. It proved to be a much bigger undertaking than I had anticipated, but with lots of help from our Maven experts we released our brand new Maven-savvy plugin documentation:
|
||
|
|
We're looking for a new and cool Atlassian T-shirt, and we want you to design it! Until February 28th, design a T-shirt or slogan for Atlassian, upload it to Confluence, and then call all your friends and have them vote for it. The selected winner has the choice of either an 8GB iPhone or a 16GB iPod Touch, your choice. It's that simple (well, almost). For all the details, click here.
|
||
|
For the last five months we have been interviewing people for the position on our shiny new QA team. Creating a QA team is a part of our plan to:
There are many factors that contribute to achieving such a goal:
Of course, being the engineers that we are, we would like to get a quantitative measure of quality as a starting point.
|
||
|
Jon and I decided to create this video as our project for Fedex Day, Atlassian's version of Google's famous 20% Time (where engineers spend one day a week on projects that aren't part of their usual responsibility). Jon interviewed me about the video for AtlassianTV, and the result is Wikipatterns.com: Eating our own dog food.
|
||
|
See some blogs and sites we've been tagging in the office:
|
||
|
See our goofy, personal side... Better yet, be our friend in the Atlassian Facebook community! And, as always, thanks for reading.
|
|||
|
Other ways to keep on top of what's happening at Atlassian: |
|||
Read or subscribe to our 
See what everyone's talking about on the Atlassian 
Get a 