GSoC ideas list: Additional hints regarding exercise task selection

1 files changed, 12 insertions, 2 deletions

diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn
index 26275377..8c9da038 100644
--- a/community/gsoc/project_ideas.mdwn
+++ b/community/gsoc/project_ideas.mdwn
@@ -31,8 +31,18 @@ for the application to be complete, we require you to make a change to the Hurd
 code, and send us the resulting patch. (This is also explained in the
 [[student_application_form]].) If possible, the change should make some
 improvement to the code you will be working on during the summer, or to some
-related code. The "exercise" bit in the project description is trying to give
-you some ideas what kind of change this could be.
+related code.
+
+The "exercise" bit in the project description is trying to give you some ideas
+what kind of change this could be. In most cases it is quite obvious, though:
+Try to find something to improve in the relevant code, by looking at known
+issues in the [Savannah bug tracker](http://savannah.gnu.org/bugs/?group=hurd);
+by running the code and testing stuff; and by looking through the code. If you
+don't find anything, try with some related code -- if you task involves
+translator programming, make some improvement to an existing translor; if it
+involves glibc hacking, make an improvement to glibc; if it involves driver
+hacking, make an improvement to the driver framework; and so on... Makes sense,
+doesn't it? :-)
 
 Sometimes it's hard to come up with a useful improvement to the code in
 question, that isn't too complicated for the purposes of the application. In