|
|||
|
Welcome to our leap year edition. This month... 21 days of wiki adoption, an illustrated Atlassian fairytale, Clover 2.1 released, win No Fluff Just Stuff tickets and more. Happy reading!
|
||
|
Plugins are arguably the killer feature for Atlassian products, as they allow you to tweak a theme or deploy full-blown applications within a familiar environment and infrastructure. In JIRA Studio, we are working with the common platform of JIRA, Confluence, Fisheye/Crucible, Crowd and Subversion, but the applications the user will visually interact with are JIRA, Confluence, and Fisheye/Crucible. If we want to add a new feature like, say, a top navigation bar, we have to add it to each product as a plugin. Since plugins are tightly coupled to each product's APIs, we have to basically write three different plugins.
|
||
|
|
||
|
At Atlassian we use Maven as part of our development process. The key with Maven is to set it up correctly as a process. In order to do that you need to understand who uses it, what they use it for and what they expect from it. Our Maven users Atlassian's Maven infrastructure has many users. To help understanding our requirements, we divide them into several categories. The core development team is in the Sydney office where we have over 50 people. All product work is done here. Apart from being in the office, quite often we work from home. (The significance of this, as far as Maven is concerned, will become apparent later.)
|
||
|
We came across one of these recently as we get ready to implement Personal Licenses for JIRA 4.0. Very early on in the issue's history (JRA-10393), a user (Zak Nixon) posted some extra incentive to get this feature done (left). Once we finished this feature, another user (Mike Robertson) posted a little 'thank you' that made our day.
|
||
|
"It's funny. One of the first things people say when I talk about the wiki is, 'We can't have something out there that just anybody can edit. Just think of what might happen.' And I say, 'Yeah, just think—people might actually collaborate!'" Read the entire Dow Jones case study.
|
||
|
Atlassian is proud to announce its partnership with No Fluff Just Stuff (NFJS), the premier technical Java/Agility event series. NFJS is truly the conference for developers by developers. Its technical focus and intimate environment (max. 250 attendees per conference) fosters a high level of interaction between the speaker and attendees, making it one of the most dynamic conferences for the development community. Atlassian is giving away tickets to each stop on the NFJS tour! For your chance to win, visit this page and write the most original haiku you can muster about Atlassian, like Grant Burnes did.
|
||
|
Here's what's buzzing around town:
|
||
|
We're happy to announce the release of Clover 2.1, just in time for Valentine's Day! Clover 2.1 allows you to tailor your code coverage reporting even more closely to your needs. Configurable risk metrics let you choose an algorithm that matches your definition of a project risk. 'Coverage Clouds' are now available for every individual package. Building on the per-test coverage that was introduced in Clover 2.0, in Clover 2.1 reports from merged databases now include per-test coverage data.
|
||
|
Here are some sites and blogs we've been sharing around the office:
|
||
|
Don't forget—you have eight days left to enter our groovy t-shirt design competition! Cheers!
|
|||
|
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