docs: Add checklist to GSoC FAQ entry. Students: Read it :-)

doc/sources/faq.rst

@@ -143,3 +143,30 @@ some smaller (or larger, if you can ;-) problems to get used to our
 workflow. If we know you can work well with us, that'd be a big plus.
 
 See: http://wiki.nuigroup.com/Google_Summer_of_Code_2011
+
+Here's a checklist:
+
+    * Make sure to read through the website and at least skim the
+      documentation.
+    * Look at the source code.
+    * Read our contribution guidelines.
+    * Pick an idea that you think is interesting from the ideas list (see
+      link above) or come up with your own idea.
+    * Do some research **yourself**. GSoC is not about us teaching you
+      something and you getting paid for that. It is about you trying to
+      achieve agreed upon goals by yourself with our support. The main
+      driving force in this should be, obviously, yourself, though.
+      Many students come up and ask what they should do. Well, we don't
+      know because we know neither your interests nor your skills. Show us
+      you're serious about it and take initiative.
+    * Write a draft proposal about what you want to do. Include what you
+      understand the current state is (very roughly), what you would like
+      to improve and how, etc.
+    * Discuss that proposal with us in a timely manner. Get feedback.
+    * Be patient! Especially on IRC. We will try to get to you if we're
+      available. If not, send an email and just wait. Most questions are
+      already answered in the docs or somewhere else and can be found with
+      some research. If your questions don't reflect that you've actually
+      thought through what you're asking, that might not be received well.
+
+Good luck! :-)