diff options
Diffstat (limited to 'community')
| -rw-r--r-- | community/gsoc/organization_application.mdwn | 23 |
1 files changed, 12 insertions, 11 deletions
diff --git a/community/gsoc/organization_application.mdwn b/community/gsoc/organization_application.mdwn index a2c65581..32a76b1c 100644 --- a/community/gsoc/organization_application.mdwn +++ b/community/gsoc/organization_application.mdwn @@ -77,7 +77,7 @@ Aside from that, it is a way to make progress with tasks that require an amount focused work, that is hard to do for volunteers working in their spare time only. -Also it is a good possibility to get valuable input from new people, as well as +Also it is a good opportunity to get valuable input from new people, as well as spreading technical and other knowledge about the Hurd among actual and potential contributors. More generally, participation should help raising awareness among people who might know about the existence of the Hurd, but @@ -156,8 +156,8 @@ won't be left on their own with any problems they face. * What is your plan for dealing with disappearing students? -The plan is mostly to avoid that happening in the first place. For that, we -will be particularily careful with the selection of the students: Making sure +The plan is mostly to avoid that happening in the first place. To this end, we +are particularily careful with selection of students: Making sure that they have no other obligations during that time; that they are motivated enough; that they actually have the necessary skills to complete the task; that they fit in our community. @@ -191,24 +191,25 @@ contact with us before the end of the student selection process, and won't consider their applications otherwise. This way we know that the students are able and willing to communicate with us in the first place. -After the selection, the regular contact will be kept up: We require the +After selection, the regular contact is kept up: We require the students to participate in weekly IRC meetings, where we ask the students actively about the work they do, problems they face, decisions they take etc. -Furthermore, we will ask them to hang around on IRC most of the time while +Furthermore, we ask them to hang out on IRC most of the time while working on their projects, so we keep in close contact. We also require the students to join our main development mailing list, so any -design questions etc. can be discussed there. We will encourage them to take +design questions etc. can be discussed there. We encourage them to take part in other conversations, not directly related to their projects, as well. -After the program we continue the regular meetings, still discussing the -projects: The application of the code created, future directions etc. +After the program we continue the regular meetings, discussing the further +development of their original projects; as well as new projects, after the +original ones are done. * What will you do to ensure that your accepted students stick with the project after GSoC concludes? -We will try to invite all participating students to a conference afterwards, -where we will discuss the projects, as well as other Hurd-related topics. We -hope this will motivate them to follow up on the work they have done during the +We try to invite all participating students to meet us at conferences afterwards, +where we discuss the projects, as well as other Hurd-related topics. This should +keep them motivated to follow up on the work they have done during the program, and generally help keeping them involved. * Is there anything else you would like to tell the Google Summer of Code program administration team? : |