diff --git a/GSoC2011Ideas.wiki b/GSoC2011Ideas.wiki
index da2dc62..da640d7 100644
--- a/GSoC2011Ideas.wiki
+++ b/GSoC2011Ideas.wiki
@@ -27,30 +27,6 @@
 = Idea Details =
 ----
 
-=Testing, Code Guru, Code Quality Assurance=
-
-===Description===
-
-Melange is sorely lacking tests, and it's hurting our development speed significantly. What we need is a extensive set of unit tests for our logic and views, as well as functional tests to make sure that all views work as expected. This will require learning the codebase first, so as to know what something should do. Test-based exploring would be most suitable (learning how the codebase by writing tests that confirm that things work a certain way). We want test coverage such that it is possible to refactor a core function without doing any manual testing, and still be fairly certain that everything works as expected. On top of that, we want to be able to start doing TDD, which is a lot easier if there are a lot of tests already. All developers will be asked to include tests with their changes as soon as we start doing TDD, so once the momentum picks up things should get easier.
-
-A lower priority, that can be pursued once we have decent test coverage, is to make sure that all pylint errors are fixed, and that all warnings are fixed or suppressed as appropriate. This way we can require that each commit introduces no new pylint errors, which will ensure some level of code quality.
-
-===Skills===
-
-  * Python
-  * Django
-  * Testing
-
-===Difficulty===
-
-Moderate, but requires a lot of effort
-
-===Mentors ===
-
- * Leo (Chong Liu)
- * Sverre Rabbelier (SRabbelier on #Melange)
-
-----
 =Better Google Code-in module=
 
 ===Description===
@@ -160,7 +136,34 @@
   * Sverre
   * Mario Ferraro
   * Daniel Hans
+
 ----
+
+=Testing, Code Guru, Code Quality Assurance=
+
+===Description===
+
+Melange is sorely lacking tests, and it's hurting our development speed significantly. What we need is a extensive set of unit tests for our logic and views, as well as functional tests to make sure that all views work as expected. This will require learning the codebase first, so as to know what something should do. Test-based exploring would be most suitable (learning how the codebase by writing tests that confirm that things work a certain way). We want test coverage such that it is possible to refactor a core function without doing any manual testing, and still be fairly certain that everything works as expected. On top of that, we want to be able to start doing TDD, which is a lot easier if there are a lot of tests already. All developers will be asked to include tests with their changes as soon as we start doing TDD, so once the momentum picks up things should get easier.
+
+A lower priority, that can be pursued once we have decent test coverage, is to make sure that all pylint errors are fixed, and that all warnings are fixed or suppressed as appropriate. This way we can require that each commit introduces no new pylint errors, which will ensure some level of code quality.
+
+===Skills===
+
+  * Python
+  * Django
+  * Testing
+
+===Difficulty===
+
+Moderate, but requires a lot of effort
+
+===Mentors ===
+
+ * Leo (Chong Liu)
+ * Sverre Rabbelier (SRabbelier on #Melange)
+
+----
+
 = Other ideas =
 
   * integrate OpenSocial into Melange