Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDT/StudentsProgram2009FAQ"
(→How does the program work?) |
|||
| Line 41: | Line 41: | ||
We will pre-publish the evaluation questions for both students and mentors. Mentors will fill out mid-term and final evaluations for their students. Students will fill out a mid-term and final evaluation of their mentors online as well. | We will pre-publish the evaluation questions for both students and mentors. Mentors will fill out mid-term and final evaluations for their students. Students will fill out a mid-term and final evaluation of their mentors online as well. | ||
| + | |||
| + | |||
| + | === Applying to Eclipse PDT Students program === | ||
| + | |||
| + | ====How does a mentoring organization apply?==== | ||
| + | The organization should choose a single administrator to submit its application via the Google Summer of Code 2009 site between March 9-13, 2009. | ||
| + | |||
| + | ====How What should a mentoring organization application look like? ====How | ||
| + | In addition to anything else your organization would like to submit as an application, Google will be asking (at least) the following questions as part of the application process: | ||
| + | |||
| + | Describe your organization. | ||
| + | Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating? | ||
| + | Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. | ||
| + | If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? | ||
| + | |||
| + | How What license(s) does your project use? | ||
| + | What is the URL for your ideas page? | ||
| + | What is the main development mailing list for your organization? | ||
| + | What is the main IRC channel for your organization? | ||
| + | Does your organization have an application template you would like to see students use? If so, please provide it now. | ||
| + | Who will be your backup organization administrator? | ||
| + | What criteria did you use to select these individuals as mentors? Please be as specific as possible. | ||
| + | What is your plan for dealing with disappearing students? | ||
| + | What is your plan for dealing with disappearing mentors? | ||
| + | What steps will you take to encourage students to interact with your project's community before, during and after the program? | ||
| + | What will you do to ensure that your accepted students stick with the project after GSoC concludes? | ||
| + | A few notes on the mentoring organization application: | ||
| + | |||
| + | If you take a look at the program timeline, we've left about a week for students to get to know you before submitting their applications. It is critical that it be obvious how students should reach you to discuss applying to your organization; plan to link this information from your "Ideas" list at the very least. | ||
| + | The email addresses associated with the Google Account information provided during application process will be used as the primary mode of contact by Google throughout the program, e.g. the email address which we will use to subscribe you to the GSoC mentors/admins-only mailing list. | ||
| + | |||
| + | ====What is an "Ideas" list?==== | ||
| + | |||
| + | An "Ideas" list should be a list of suggested student projects. This list is meant to introduce contributors to your project's needs and to provide inspiration to would-be student applicants. It is useful to classify each idea as specifically as possible, e.g. "must know Python" or "easier project; good for a student with more limited experience with C++." If your organization plans to provide an application template, it would be good to include it on your Ideas list. | ||
| + | |||
| + | Keep in mind that your Ideas list should be a starting point for student applications; we've heard from past mentoring organization participants that some of their best student projects are those that greatly expanded on a proposed idea or were blue-sky proposals not mentioned on the Ideas list at all. | ||
| + | |||
| + | ====How does a student apply?==== | ||
| + | Students can submit their applications via the Google Summer of Code 2009 site from March 23 - April 3, 2009. We hear almost universally from our mentoring organizations that the best applications they receive are from students who took the time to interact and discuss their ideas before submitting an application, so make sure to check out each organization's "Ideas" list to get to know a particular open source organization better. | ||
| + | |||
| + | ====What should a student application look like?==== | ||
| + | Your application should include the following: your project proposal, why you'd like to execute on this particular project, and the reason you're the best individual to do so. Your proposal should also include details of your academic, industry, and/or open source development experience, and other details as you see fit. An explanation of your development methodology is a good idea, as well. If the organization you want to work with has a specific application template they would like you to use, it will be made available to you to fill in when submitting your proposal via the GSoC web app. | ||
| + | |||
| + | ====Can a student submit more than one application?==== | ||
| + | Yes, each student may submit up to twenty applications. However, only one application will be accepted. We've heard from our mentoring organizations that quality is better than quantity. | ||
| + | |||
| + | ====Can students already working on an open source project continue to work on it as part of Google Summer of Code?==== | ||
| + | Yes, as long as they meet all other requirements for program eligibility. Students should be sure to note their previous relationship with the project in their applications. New work will need to be done for the project as part of participation in GSoC. | ||
| + | |||
| + | ====Should students begin working on their applications before Google begins accepting program applications?==== | ||
| + | That's up to you. Keep in mind, though, that our mentoring organizations will be publishing a list of proposed project ideas, so you may find that you'll want to revamp your application later, or create an entirely new one to address one of those ideas. | ||
| + | |||
| + | ====Can a student work on more than one project?==== | ||
| + | No, each participant is only eligible for one stipend. | ||
| + | |||
| + | ====Can a group apply for and work on a single proposal?==== | ||
| + | No, only an individual may work on a given project. Of course, students should feel free to collaborate with others to accomplish their project goals. | ||
| + | |||
| + | ====What happens if two students are accepted to work on the same project, e.g. from an organization's "Ideas" list?==== | ||
| + | That's fine, a little duplication is par for the course in open source. | ||
Revision as of 15:47, 20 June 2009
Contents
- 1 Eclipse PHP Development Tools (PDT) Students Program Frequently Asked Questions
- 1.1 About
- 1.1.1 What is Eclipse PDT Students Program?
- 1.1.2 What are the goals of this program?
- 1.1.3 Is this program a recruiting program?
- 1.1.4 How many students does this program to take part in the program
- 1.1.5 When can I apply for Google Summer of Code?
- 1.1.6 How does the program work?
- 1.1.7 How do evaluations work?
- 1.2 Applying to Eclipse PDT Students program
- 1.2.1 How does a mentoring organization apply?
- 1.2.2 What is an "Ideas" list?
- 1.2.3 How does a student apply?
- 1.2.4 What should a student application look like?
- 1.2.5 Can a student submit more than one application?
- 1.2.6 Can students already working on an open source project continue to work on it as part of Google Summer of Code?
- 1.2.7 Should students begin working on their applications before Google begins accepting program applications?
- 1.2.8 Can a student work on more than one project?
- 1.2.9 Can a group apply for and work on a single proposal?
- 1.2.10 What happens if two students are accepted to work on the same project, e.g. from an organization's "Ideas" list?
- 1.1 About
Eclipse PHP Development Tools (PDT) Students Program Frequently Asked Questions
About
What is Eclipse PDT Students Program?
Eclipse PHP Development Tools (PDT) Student Program is a global program that offers student developers stipends to contribute code for the Eclipse PDT project. Through this program, accepted student applicants are paired with a mentor or mentors from the Eclipse community, thus gaining exposure to real-world software development scenarios in areas related to their academic pursuits. In turn, the Eclipse PDT project can more easily identify and bring in new developers. Best of all, more source code is created and released for the use and benefit of all.
What are the goals of this program?
- Get more open source code created and released for the benefit of all
- Inspire young developers to begin participating in open source Eclipse PDT development
- Help our project identify and bring in new developers and committers
- Provide students the opportunity to do work related to their academic pursuits during the summer
Is this program a recruiting program?
Not really.
How many students does this program to take part in the program
We funded 3 student projects this year.
When can I apply for Google Summer of Code?
The student application period begins Monday, June 15, 2009 and ends Friday, July 31st. For full details, see the PDT/StudentsProgram2009timeline program timeline.
How does the program work?
Here are the steps:
- Mentors and Students submit project proposals online to work with particular mentoring organizations.
- The Eclipse PDT community rank student proposals and perform any other due diligence on their potential mentees; student proposals are matched with a mentor
- Students are notified of acceptance
- Students begin learning more about Eclipse PDT and their before coding work starts
- Students begin coding work at the official start of the program, provided they've interacted well with the PDT community up until the program start date
- Mentors and students provide mid-term progress evaluations
- Mentors provide a final evaluation of student progress at close of program; students submit a final review of their mentor and the program
Student submit their work to a bugzilla issue.
How do evaluations work?
We will pre-publish the evaluation questions for both students and mentors. Mentors will fill out mid-term and final evaluations for their students. Students will fill out a mid-term and final evaluation of their mentors online as well.
Applying to Eclipse PDT Students program
How does a mentoring organization apply?
The organization should choose a single administrator to submit its application via the Google Summer of Code 2009 site between March 9-13, 2009.
====How What should a mentoring organization application look like? ====How In addition to anything else your organization would like to submit as an application, Google will be asking (at least) the following questions as part of the application process:
Describe your organization. Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating? Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
How What license(s) does your project use? What is the URL for your ideas page? What is the main development mailing list for your organization? What is the main IRC channel for your organization? Does your organization have an application template you would like to see students use? If so, please provide it now. Who will be your backup organization administrator? What criteria did you use to select these individuals as mentors? Please be as specific as possible. What is your plan for dealing with disappearing students? What is your plan for dealing with disappearing mentors? What steps will you take to encourage students to interact with your project's community before, during and after the program? What will you do to ensure that your accepted students stick with the project after GSoC concludes? A few notes on the mentoring organization application:
If you take a look at the program timeline, we've left about a week for students to get to know you before submitting their applications. It is critical that it be obvious how students should reach you to discuss applying to your organization; plan to link this information from your "Ideas" list at the very least. The email addresses associated with the Google Account information provided during application process will be used as the primary mode of contact by Google throughout the program, e.g. the email address which we will use to subscribe you to the GSoC mentors/admins-only mailing list.
What is an "Ideas" list?
An "Ideas" list should be a list of suggested student projects. This list is meant to introduce contributors to your project's needs and to provide inspiration to would-be student applicants. It is useful to classify each idea as specifically as possible, e.g. "must know Python" or "easier project; good for a student with more limited experience with C++." If your organization plans to provide an application template, it would be good to include it on your Ideas list.
Keep in mind that your Ideas list should be a starting point for student applications; we've heard from past mentoring organization participants that some of their best student projects are those that greatly expanded on a proposed idea or were blue-sky proposals not mentioned on the Ideas list at all.
How does a student apply?
Students can submit their applications via the Google Summer of Code 2009 site from March 23 - April 3, 2009. We hear almost universally from our mentoring organizations that the best applications they receive are from students who took the time to interact and discuss their ideas before submitting an application, so make sure to check out each organization's "Ideas" list to get to know a particular open source organization better.
What should a student application look like?
Your application should include the following: your project proposal, why you'd like to execute on this particular project, and the reason you're the best individual to do so. Your proposal should also include details of your academic, industry, and/or open source development experience, and other details as you see fit. An explanation of your development methodology is a good idea, as well. If the organization you want to work with has a specific application template they would like you to use, it will be made available to you to fill in when submitting your proposal via the GSoC web app.
Can a student submit more than one application?
Yes, each student may submit up to twenty applications. However, only one application will be accepted. We've heard from our mentoring organizations that quality is better than quantity.
Can students already working on an open source project continue to work on it as part of Google Summer of Code?
Yes, as long as they meet all other requirements for program eligibility. Students should be sure to note their previous relationship with the project in their applications. New work will need to be done for the project as part of participation in GSoC.
Should students begin working on their applications before Google begins accepting program applications?
That's up to you. Keep in mind, though, that our mentoring organizations will be publishing a list of proposed project ideas, so you may find that you'll want to revamp your application later, or create an entirely new one to address one of those ideas.
Can a student work on more than one project?
No, each participant is only eligible for one stipend.
Can a group apply for and work on a single proposal?
No, only an individual may work on a given project. Of course, students should feel free to collaborate with others to accomplish their project goals.
What happens if two students are accepted to work on the same project, e.g. from an organization's "Ideas" list?
That's fine, a little duplication is par for the course in open source.