summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/gnumach_cleanup.mdwn
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2009-03-12 04:41:01 +0100
committerantrik <antrik@users.sf.net>2009-03-12 09:17:01 +0100
commit4202d9098226b6715f8a2f368370773964d4f5b0 (patch)
tree0d7e03190fecf0ec5f48a4dede7f9b3a860c55fa /community/gsoc/project_ideas/gnumach_cleanup.mdwn
parent026310e73bb2110db09fe555d5b4d68f5180e7cd (diff)
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.
Diffstat (limited to 'community/gsoc/project_ideas/gnumach_cleanup.mdwn')
-rw-r--r--community/gsoc/project_ideas/gnumach_cleanup.mdwn7
1 files changed, 4 insertions, 3 deletions
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