From 4202d9098226b6715f8a2f368370773964d4f5b0 Mon Sep 17 00:00:00 2001 From: antrik Date: Thu, 12 Mar 2009 04:41:01 +0100 Subject: Gnumach cleanup GSoC task: Reworded section on things to do More explicitely state that the student should look at the code to find stuff to fix -- mention possible things only as examples. --- community/gsoc/project_ideas/gnumach_cleanup.mdwn | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'community/gsoc') diff --git a/community/gsoc/project_ideas/gnumach_cleanup.mdwn b/community/gsoc/project_ideas/gnumach_cleanup.mdwn index c11defe5..280371e5 100644 --- a/community/gsoc/project_ideas/gnumach_cleanup.mdwn +++ b/community/gsoc/project_ideas/gnumach_cleanup.mdwn @@ -31,9 +31,10 @@ It's rather hard to make modifications -- to make better use of modern hardware for example, or even to fix bugs. The goal of this project is to improve the situation. -The task starts out easy, with fixing compiler warnings. Later it moves on to -more tricky things: removing dead or unneeded code paths; restructuring code -for readability and maintainability. +There are various things you can do here: Fixing compiler warnings; removing +dead or unneeded code paths; restructuring code for readability and +maintainability etc. -- a glance at the source code should quickly give you +some ideas. This task requires good knowledge of C, and experience with working on a large existing code base. Previous kernel hacking experience is an advantage, but -- cgit v1.2.3