|
Size: 1673
Comment:
|
Size: 2216
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| What software are you creating? Why is it interesting? What language is it written in? How is it going to change the world? | Tell the students a bit about your organization. Here's some questions you might want to answer: * What software are you creating? * Why is it interesting? * Who uses it? * What languages is it written in? * How is it going to change the world? |
| Line 14: | Line 19: |
| Any special instructions/info about communicating: e.g. what time zones are your mentors in? do you prefer it if gsoc students introduce themselves first or just dive in? | Include any special instructions/info about communicating: e.g. what time zones are your mentors in? do you prefer it if gsoc students introduce themselves first or just dive in? are there any common mistakes students make when making a first impression? |
| Line 17: | Line 22: |
| Links to setup instructions go here. | Links to setup instructions go here. Some suggested things to answer: * Where is the link to a setup guide for new developers? * Are there any unusual libraries/applications that need to be installed first? * What type of source control do you use? (include links to help and setup guides!) * What's the process for submitting your first bug fix? |
There are not very many strict requirements for Google Summer of Code Ideas pages, but there are some things that students often ask us for. This page is intended as a starting template for organizations so you don't forget those things.
Warning: In 2014, many orgs got rejected because their ideas pages were offline when google checked. Make sure your ideas page is hosted somewhere that Google's Open Source Programs Office will be able to access when they check!
About MyOrg
Tell the students a bit about your organization. Here's some questions you might want to answer:
- What software are you creating?
- Why is it interesting?
- Who uses it?
- What languages is it written in?
- How is it going to change the world?
Contacting MyOrg
IRC channel:
Mailing list(s):
Include any special instructions/info about communicating: e.g. what time zones are your mentors in? do you prefer it if gsoc students introduce themselves first or just dive in? are there any common mistakes students make when making a first impression?
Getting Started
Links to setup instructions go here. Some suggested things to answer:
- Where is the link to a setup guide for new developers?
- Are there any unusual libraries/applications that need to be installed first?
- What type of source control do you use? (include links to help and setup guides!)
- What's the process for submitting your first bug fix?
Writing your application
Links to advice about applications and the application template goes here.
Project Ideas
1. Project name
Project description: Make sure you have a high-level description that any student can understand, as well as deeper details
Related Readings/Links: was there a mailing list discussion about this topic? standards you want the students to read first? bugs/feature requests?
Skills: programming languages? specific domain knowledge?
Difficulty level: Easy/Intermediate/Hard classification (students ask for this info frequently to help them narrow down their choices)
2. Project name
- As above. etc.