summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2009-03-10 07:23:22 +0100
committerantrik <antrik@users.sf.net>2009-03-10 23:56:46 +0100
commit1ba6e35d1b1bf2c2a1bc198a01949f1893b8ad24 (patch)
tree91b470f0a0ef994c2f3d51ddde49e7c2e9cc0873
parent5fe31c43d7445d820df4fdef044b765372872ba1 (diff)
File locking GSoC task: Update exercise suggestion
While the suggestion is certainly good as an exercise, it is probably not suitable for producing an actual patch quickly. Warn about this, and explicitely mention that finding a different task might be necessary.
-rw-r--r--community/gsoc/project_ideas/file_locking.mdwn11
1 files changed, 9 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/file_locking.mdwn b/community/gsoc/project_ideas/file_locking.mdwn
index ca3c28ed..b20b82fd 100644
--- a/community/gsoc/project_ideas/file_locking.mdwn
+++ b/community/gsoc/project_ideas/file_locking.mdwn
@@ -26,5 +26,12 @@ Possible mentors: Samuel Thibault (youpi)
Exercise: Find one of the existing issues, either by looking at the task/bug
trackers on savannah, or by trying things out yourself; and take a go at it.
-Probably you wont' be able to fix the problem in a limited amount of time, but
-you should be able to do a detailed analysis of the issue at least.
+Note though that most of these issues are probably not trivial -- it's quite
+likely that you won't be able to actually fix any of them in the time available
+during the application process. However, you might be able to spot something
+else that could be improved while looking into this.
+
+If after trying for a while you haven't found anything easy enough to improve
+in the locking-related code, talk to us about some alternative exercise task.
+Perhaps you actually find something you could do while looking through the bug
+tracker or trying stuff yourself in search of locking issues :-)