Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Google Summer of Code 2010 Mentoring Organization Application"
(→What is your plan for dealing with disappearing students? (required)) |
(→What is your plan for dealing with disappearing mentors? (required)) |
||
| Line 48: | Line 48: | ||
==What is your plan for dealing with disappearing mentors? (required)== | ==What is your plan for dealing with disappearing mentors? (required)== | ||
| + | |||
| + | In the past, we've had success with layering our mentors "two deep". That is, we have generally had both a primary and a backup mentor for each student project. We will continue this in 2010. We implemented this to accommodate for vacation time for mentors; while we have not needed this safety need to deal with "disappearing mentors" in the past, it should work well for those purposes should the need arise. | ||
==What steps will you take to encourage students to interact with your project's community before, during and after the program? (required)== | ==What steps will you take to encourage students to interact with your project's community before, during and after the program? (required)== | ||
Revision as of 17:28, 9 March 2010
Contents
- 1 Organization Name (required)
- 2 Description (required)
- 3 Home page (required)
- 4 Main Organization License: (required)
- 5 Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)
- 6 Did your organization participate in past GSoCs?(required)
- 7 If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated (required)
- 8 What is the URL for your ideas page? (required)
- 9 What is the main development mailing list for your organization? (required)
- 10 What is the main IRC channel for your organization? (required)
- 11 Does your organization have an application template you would like to see students use? (required)
- 12 What criteria did you use to select the individuals who will act as mentors for your organization? (required)
- 13 What is your plan for dealing with disappearing students? (required)
- 14 What is your plan for dealing with disappearing mentors? (required)
- 15 What steps will you take to encourage students to interact with your project's community before, during and after the program? (required)
- 16 What will you do to ensure that your accepted students stick with the project after GSoC concludes? (required)
- 17 Is there anything else you would like to tell the Google Summer of Code program administration team? (required)
Organization Name (required)
The Eclipse Foundation
Description (required)
Eclipse is an open source community, whose projects are focused on building an open development platform comprised of extensible frameworks, tools and runtimes for building, deploying and managing software across the life cycle. The Eclipse Foundation is a not-for-profit, member supported corporation that hosts the Eclipse projects and helps cultivate both an open source community and an ecosystem of complementary products and services. The Eclipse community consists of individuals and organizations from a cross section of the software industry.
Home page (required)
Main Organization License: (required)
EPL
Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)
As an organization, Eclipse has benefited significantly from past participation in the GSoC programme. Clearly, we benefit from the immediate value that we get in the form of code contributions. We are shipping code created by former GSoC student participants in our releases today. We also benefit from our ability to work directly with the students, and get to know them. They bring new ideas. In turn, they get to know us as an organization; the goodwill and mindshare that we develop with these experiences benefits us in the long run. Some of our former GSoC students have found employment through the programme (some of whom continue to work on projects at Eclipse). Some of our students have become mentors in subsequent years. GSoC students tell their friends about their positive experiences with us which then helps to grow the pool of people who participate in Eclipse projects and open source projects in general.
Did your organization participate in past GSoCs?(required)
If so, please summarize your involvement and the successes and challenges of your participation.
If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated (required)
e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.
Add a Comment (optional)
What is the URL for your ideas page? (required)
http://wiki.eclipse.org/Google_Summer_of_Code_2010_Ideas
What is the main development mailing list for your organization? (required)
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.
https://dev.eclipse.org/mailman/listinfo/soc-dev
What is the main IRC channel for your organization? (required)
The official Eclipse SOC IRC channel is #eclipse-soc located on freenode.net. Everyone is welcome as it is not restricted to students and mentors.
Add a Comment (optional):
Students can additionally monitor and pose questions on #eclipse.
Does your organization have an application template you would like to see students use? (required)
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.
What criteria did you use to select the individuals who will act as mentors for your organization? (required)
Please be as specific as possible.
In the simplest possible terms, we select only mentors that we know ("we" being the current group of mentors). We're very careful to accept only those mentors who we know are familiar with the necessary processes at eclipse.org, and who will provide the best possible experience for the students. Most of our mentors are committers on Eclipse projects, but not all need be.
What is your plan for dealing with disappearing students? (required)
We will make every reasonable effort chase them down using the resources that are available to us. We will continue the strategy that we've employed in the past: our mentors will make regular efforts to communicate. Ultimately, if a student choses to abandon their work, there's little that we can do about it. If our communication efforts fail, we will reflect the failure on either the mid-term or final report (our mentors take the responsibility inherent in participating in GSoC very seriously).
What is your plan for dealing with disappearing mentors? (required)
In the past, we've had success with layering our mentors "two deep". That is, we have generally had both a primary and a backup mentor for each student project. We will continue this in 2010. We implemented this to accommodate for vacation time for mentors; while we have not needed this safety need to deal with "disappearing mentors" in the past, it should work well for those purposes should the need arise.