summaryrefslogtreecommitdiff
path: root/community/gsoc
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2009-02-24 08:36:37 +0100
committerantrik <antrik@users.sf.net>2009-02-24 08:36:37 +0100
commit3c6885c6175dc2fb9183d2c93b09b0058fb0a4b5 (patch)
treee98dbd3e8e5ae859a5bf35a8eb21e90ea500d49a /community/gsoc
parentd993f2abad8abc511a343245a10d523125489cf9 (diff)
Mention getting long-term contributors as primary goal of GSoC participation
This will probably make the Google folks happy, as this is officially the main purpose of the GSoC program... More importantly, past experience shows that even very skilled students are seldom able to leave a project in such a state that it is really useful for us without any followup work -- treating GSoC as a way to get code written by means of external sponsoring doesn't really work out. Finding long-term contributors is *much* more useful in the end.
Diffstat (limited to 'community/gsoc')
-rw-r--r--community/gsoc/organization_application.mdwn5
1 files changed, 4 insertions, 1 deletions
diff --git a/community/gsoc/organization_application.mdwn b/community/gsoc/organization_application.mdwn
index fc3ddbe1..9765c500 100644
--- a/community/gsoc/organization_application.mdwn
+++ b/community/gsoc/organization_application.mdwn
@@ -66,7 +66,10 @@ papers](http://walfield.org/).
* Why is your organization applying to participate in GSoC 2009? What do you
hope to gain by participating?
-For one, it is a way to make progress with tasks that require an amount of
+The primary goal of course is to find and introduce new long-term contributors
+to the project.
+
+Aside from that, it is a way to make progress with tasks that require an amount of
focused work, that is hard to do for volunteers working in their spare time
only.