gsoc: update questions in organisation application form for 2010

Note: The *answers* aren't updated yet!

1 files changed, 38 insertions, 46 deletions

diff --git a/community/gsoc/organization_application.mdwn b/community/gsoc/organization_application.mdwn
index 9fe3a420..5fdf3837 100644
--- a/community/gsoc/organization_application.mdwn
+++ b/community/gsoc/organization_application.mdwn
@@ -8,22 +8,10 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
 is included in the section entitled
 [[GNU Free Documentation License|/fdl]]."]]"""]]
 
-* Link ID:
-
-hurd
-
-* Group Name:
+* Organization Name:
 
 GNU Hurd
 
-* Home Page URL:
-
-http://hurd.gnu.org
-
-* Public Email:
-
-bug-hurd@gnu.org
-
 * Description:
 
 The Hurd project is a loose community of people sharing a common interest in
@@ -71,7 +59,15 @@ contact with the most distinguished researchers in that field from the
 microkernel operating system groups, and have written a couple of [research
 papers](http://walfield.org/).
 
-* Why is your group applying to participate? What do you hope to gain by participating?
+* Home Page:
+
+http://hurd.gnu.org
+
+* Main Organization License:
+
+GNU General Public License (GPL)
+
+* Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
 
 The primary goal of course is to find and introduce new long-term contributors
 to the project.
@@ -90,25 +86,7 @@ progress is.
 Last but not least, we hope the participation will have a positive effect on
 our community -- new impulses, increased communication etc.
 
-* What is the main public mailing list for your group?
-
-bug-hurd@gnu.org, see http://lists.gnu.org/mailman/listinfo/bug-hurd
-
-* Where is the main IRC channel for your group?
-
-\#hurd on freenode.net
-
-* What criteria do you use to select the members of your group? Please be as specific as possible.
-
-The most important criterium is that the person is involved in the project for
-some time, knowing the ways; so he can actually instruct the student; and if
-there are tough technical questions he can't answer himself, he knows whom to
-ask.
-
-It's also important that the mentors are reliable and helpful, so the students
-won't be left on their own with any problems they face.
-
-* Has your group participated previously? If so, please summarize your involvement and any past successes and failures.
+* Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
 
 In 2006 and 2007,
 we participated under the umbrella of the GNU project, getting one slot each
@@ -143,27 +121,39 @@ hoped of course, but probably as much as can be realistically expected...
 All in all, the participation was a considerable amount of work, but it was
 definitely worth it :-)
 
-* If your group has not previously participated, have you applied in the past? If so, for what sort of participation?
+* If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.
 
---
+* If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
 
-* What license does your organization use?
-
-GNU General Public License (GPL)
+--
 
-* What is the URL to the ideas list of your organization?
+* What is the URL for your ideas page?
 
 http://www.gnu.org/software/hurd/community/gsoc/project_ideas.html
 
-* What is the main development mailing list for your group?
+* What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for GSoC 2010. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.
 
 bug-hurd@gnu.org, see http://lists.gnu.org/mailman/listinfo/bug-hurd
 
-* What is the application template you would like contributors to your organization to use.
+* What is the main IRC channel for your organization?
+
+\#hurd on freenode.net
+
+* Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2010 site.
 
 [[student_application_form]]
 
-* What is your plan for dealing with disappearing contributors?
+* What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible:
+
+The most important criterium is that the person is involved in the project for
+some time, knowing the ways; so he can actually instruct the student; and if
+there are tough technical questions he can't answer himself, he knows whom to
+ask.
+
+It's also important that the mentors are reliable and helpful, so the students
+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
@@ -183,7 +173,7 @@ 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, so that we get partial results at least if someone disappears.
 
-* What is your plan for dealing with disappearing members?
+* What is your plan for dealing with disappearing mentors?
 
 As our mentors all have been with the project for some time, the risk of them
 disappearing is not too big. If one of them disappears nevertheless, it's not a
@@ -193,7 +183,7 @@ We will encourage the students to keep discussions public as much as possible,
 keeping private conversations with the mentors to a minimum, so the transition
 should go smoothly.
 
-* What steps will you take to encourage contributors to interact with your community before, during, and after the program?
+* What steps will you take to encourage students to interact with your project's community before, during and after the program?
 
 We try to make it very clear that we expect the students to get into regular
 contact with us before the end of the student selection process, and won't
@@ -213,12 +203,14 @@ 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.
 
-* What will you do to ensure that your accepted contributors stick with the project after the program concludes?
+* 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
 program, and generally help keeping them involved.
 
-* Please select your backup group administrator.
+* Is there anything else you would like to tell the Google Summer of Code program administration team? :
+
+* Backup Admin (Link ID):