changing to H2 tags

Author: shiftbot

_posts/2012-04-25-re-evaluating-code52.md

@@ -9,15 +9,15 @@ comments: true
 
 I've been mulling over the contents of this post over the past couple of weeks - while it's been an amazing experience thus far, a few events behind the scenes have triggered some changes.
 
-### Farewells and Distractions
+## Farewells and Distractions
 
 Last week @aeoth decided to step down from his role co-ordinating and contributing to the Code52 group. He's been a big part in many of the things we've built so far, and we wish him the best with his future endeavours.
 
 @shiftkey will be spending my weekends living in airports as part of the Windows 8 Dev Camps around Australia over the coming weeks - plus some other things which he will talk about in the future - so he will not be as contactable as he has been previously. Once he returns from holidays in July (after [dddSydney](http://dddsydney.com) in fact) the schedule starts to look more like that of a normal person.
 
 So with logistics getting tougher to organise each week, we want to adapt to the situation in front of us - for everyone's benefits.
 
-### Rethinking the process
+## Rethinking the process
 
 So rather than continuing down this path to self-implosion, we want to try some changes to the process: 
 
@@ -26,7 +26,7 @@ So rather than continuing down this path to self-implosion, we want to try some
  - We want to **help people become contributors**
  - We want to ensure that **everyone has fun and learns from the experience**
 
-### Nothing is set in stone
+## Nothing is set in stone
 
 Keep in mind that this is one big long experiment, and **we want you to get involved**. 
 
@@ -38,15 +38,15 @@ With this change, hopefully this frees projects up to evolve at their own pace a
 
 A complementary change to this is how we announce projects. Once we organise a project and a group of people to get involved, we aim to announce ahead of time (a week?) the project. This should give enough time for the group to get the groundwork in place, and give people who are following the action time to declare their interest and availability.
 
-### So what next?
+## So what next?
 
 @shiftkey has something he wants to kickstart - specifically [this idea](https://code52.uservoice.com/forums/143105-code-52/suggestions/2730885-git-heat-map-generator) - but until he gets some spare time (next week at best), now is the opportunity for people to take charge and get involved - **what do you want to build?**
 
 @shiftkey has a number of OSS projects on the go - getting [Markpad](http://code52.org/DownmarkerWPF) in-app updates running, adding features to [Dodo](http://github.com/Code52/dodo), dogfooding [NSync](http://github.com/xpaulbettsx/nsync) on an internal app, reviewing pull requests and answering questions on JabbR - so I'll be hanging out in the [JabbR](http://jabbr.net/#/rooms/code52) room whenever I'm coding in my spare time.
 
 And of course, the [JabbR](http://jabbr.net/#/rooms/code52) room also tracks conversation history - so you can drop in and see what people have been talking about previously or just hang out and chat.
 
-### This week: @shiftkey explains more
+## This week: @shiftkey explains more
 
 Over the course of this week, Brendan will discuss some of the philosophical goals in mind for Code52. While these are relatively simple goals, he will also discuss what we've learned so far and how we can improve things going forward.