diff options
| author | antrik <antrik@users.sf.net> | 2010-03-12 17:42:29 +0100 |
|---|---|---|
| committer | antrik <antrik@users.sf.net> | 2010-03-12 17:42:29 +0100 |
| commit | b593f5bd39ef21e58ff90cec504493dd653608e1 (patch) | |
| tree | 81ec720415ef0077db7e582720bcd34891a0e2b9 /community | |
| parent | 3fe2f81d9c0750f555badbb9dd1139c5f836d4d9 (diff) | |
gsoc/organization_application: Reword section on partial results
As we don't focus our participation on code produced during the summer,
partial code is also not the major consideration when a project fails.
Diffstat (limited to 'community')
| -rw-r--r-- | community/gsoc/organization_application.mdwn | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/community/gsoc/organization_application.mdwn b/community/gsoc/organization_application.mdwn index 7023af65..2df2311f 100644 --- a/community/gsoc/organization_application.mdwn +++ b/community/gsoc/organization_application.mdwn @@ -162,11 +162,11 @@ time if things go wrong. If a student disappears in spite of that, there is little we can do. Of course we will try to contact him and find out what the problem is; whether the -project can perhaps be scaled down, or at least wrapped up to bring it in a -state where it is useful even if not finished. - -We will also try to limit damage by insisting that students regularily check in -their work to our source repositories, so that we get partial results at least if someone disappears. +project can perhaps be scaled down, or otherwise salvaged, so that the effort +already invested in the student and the project is not wasted. We also try to +make sure that all important design discussions are archieved, and that all +code produced is suitable for upstream inclusion from the beginning -- to allow +others to pick up the project if necessary, without having to start from zero. * What is your plan for dealing with disappearing mentors? |