|
|||
|
This month, we have two User Group events and one of them is tomorrow! Also included in this issue... Codegeist winners, blogs from our developers and more. Happy reading!
|
||
|
Atlassian User Group Events in Boston and San Francisco Area |
|||
|
Will you be in the Boston area tomorrow? How about in the San Francisco area next Thursday? If you replied 'yes' to either one, come to an Atlassian User Group event! At both of these events, you can network and socialise with peers, developers and other folks with shared interests, including members of the Atlassian team. There is also a set agenda that includes customers sharing their best practices. Here are the event details: Boston Area User Group Conference
|
||
|
Jonathan, our Codegeist ringleader, blogged about all the Codegeist II winners here, here, here and here. But, if you're looking for a quick rundown, see the list of all the winners just below or in the Codegeist press release. This year's winners, broken down by product, include: JIRA Second place: Confluence Portlet for JIRA, written by Tommi Laakanen, displays any Confluence page on the JIRA dashboard, creating stronger integration between the two products. Confluence Second place: Page Tree Search Plugin, written by Shannon Krebs, lets you search a limited hierarchy of pages. Crowd Second place .NET Authenticator, written by Matthew Slater, extends Crowd's services to .NET applications. Bamboo Second place: NAnt Builder Plugin, written by Ross Rowe, allows configuration and execution of NAnt build files for .Net/Mono projects. This year Atlassian opened the polls to its community. Determined by popular public vote, the Community Award went to Jean-Christophe Huet's Links Hierarchy Reports plugin for JIRA, which also swept the JIRA plugin category.
|
||
|
For much of this week I have been taken from my bug fixing work to drag a functional test kicking and screaming across the fine line that separates working from broken. This test was to ensure that JIRA's "Johnson" servlet filter will correctly stop incoming requests from waking up the plugin system or the micro container (picocontainer) while the system is unable to respond. These cases occur when JIRA is being setup, during an import, etc. The result is that JIRA returns a 503 Service Temporarily Unavailable response for SOAP, RSS, AJAX etc. URLs. The functional test is a JWebUnit test which uses HttpUnit underneath so I set HttpUnitOptions.setExceptionsThrownOnErrorStatus(false); to enable my code to assert the 503 response instead of it causing an exception.
|
||
|
We've recently had a couple of problems when developers would keep committing code if the builds are broken on Bamboo. We generally aim to stop all commits until the builds are passing again, since it makes it easier to find the problem as well as making developers think twice before committing ;).
|
||
|
Anyone who has ever had to look at logs from a Confluence instance knows that they are pretty verbose. Yet at times we still wish there was a little bit more information in them, particularly regarding the nature of the web request in which the log message was generated. CONF-7878 was raised by a user exasperated by trying to understand where certain, seemingly ephemeral messages were coming from. Since Confluence 2.4.2 we now have a web filter and an XWork interceptor which add some particularly pertinent information to Log4j's Mapped Diagnostic Context (MDC). The MDC is basically a thread local key value map allowing developers to store information about the code that is executing that can be used to enhance the context of logged messages.
|
||
|
|
||
|
Some blogs and sites we've been tagging to our office del.icio.us stream:
|
||
|
How do you like the new look of our home page? In my experience, home page redesigns are often very contentious processes. That said, this one was (mostly) a snap. We started out with several "lighter" redesigns, then scrapped those and went for something a little more radical. You can't please everyone all the time, and I'm sure there are those who will hate it or at least will find lots to nitpick, but I'm really pleased with the process and outcome. Big kudos to our internal User Interface design team who like to moonlight for Marketing! Look for more changes and tweaks soon. Comments welcome.
|
||
|
I recently joined Atlassian after spending 15 years in large corporates. I was drawn to Atlassian due to its culture and its young, smart people. Indeed, I was one of the younger people in my previous company, whereas I'm now one of the older ones at Atlassian! From Day 1 I noticed how Atlassian was a different company. Not 'different' as intentionally wanting to 'be different' but rather having a willingness to 'think differently' about how things are done. Here are some examples.
|
||
|
Don't forget — the User Group in Cambridge, MA is tomorrow! The one in Palo Alto, CA is next Thursday. Hope you can make one. On a completely different note, how are you using our products? Please let us know — we're interested in hearing your stories. 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 