Students
Differences between revisions 1 and 15 (spanning 14 versions)
|
Size: 4197
Comment:
|
← Revision 15 as of 2010-10-22 15:18:12 ⇥
Size: 3344
Comment: edited gsoc content out
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| <<Include(GoogleSoC2010/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| = Google Code In 2010 = ''' NOTE: This page is being updated for this project''' Ubuntu would like to participate in the [[GoogleCodeIn2010|Google Code-in 2010]], and is eager to attract good, capable, eligible students to apply for the projects. If you are a registered student and are 13-18 years of age, you can apply for one of the projects or work on a project for another organization. We would like to select students who are enthusiastic about their projects and are able to commit the time and energy required to make them successful. |
|
| Line 4: | Line 18: |
| Line 5: | Line 20: |
| * Review our [[wiki.ubuntu.com/GSoC/2010/Ideas|Project Ideas]] * Read the Selection Process / Proposals section very carefully * Join the on the #ubuntu-gsoc Freenode IRC channel * Send an email to the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-soc|mailing list]], introducing yourself * Use this [[http://wiki.ubuntu.com/GSoC/2010/StudentTemplate|template]] to create your profile in our wiki page * Prepare an application, discuss and share it with a mentor * Apply from March 29 - April 9, 2010 [[http://socghop.appspot.com|here]] * Rock and Roll! |
* Review our * Read the Selection Process / Proposals section '''very carefully''' * Create your profile in our wiki page: * '''Apply from ''' |
| Line 16: | Line 30: |
| * You need to be enrolled as a student in a college/university * You need to be 18+ |
* You need to be enrolled as a student and have your parents' permission to participate * You need to be 13 -18 |
| Line 21: | Line 36: |
| == Selection Process / Proposals == * We will not accept a proposal that we can do ourselves over a few days, so be detailed. But also, don't be super ambitious - it is be better to succeed with a small idea than to submit a complex project and leave the program * Feel free to submit multiple proposals, but you can only work in one project (Ubuntu) * Applications are for individuals, you can't work in groups * Don't feel stuck to the ideas we have suggested here * If you have new ideas to help us improve our OS and you are familiar with Ubuntu, go for it and propose them! We believe, we'll have loads of applicants for each idea listed on the mentor's page, so keep in mind that your proposals will have less competition * The idea needs to fit in with our project goals, it needs to be specific, and it needs to be detailed * Before sending us the whole proposal, we recommend that you send a summary with your idea to the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-soc|list]] or to your mentor for feedback * Include your IRC nick in the proposal * List your milestones * Be creative, do not copycat * Impress us! * Tell us who you are and why did you choose Ubuntu |
|
| Line 35: | Line 37: |
| == Application Process and Proposal == | |
| Line 36: | Line 39: |
| == Tips for students == * It is highly recommended that you go through [[ http://socghop.appspot.com/document/show/program/google/gsoc2009/userguide|Google's advise page]] * If you have queries, read Google's [[http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs|faqs]] and contact us immediately if your question is not answered there * Try not to get intimidated: Passion counts more than experience * Join the IRC freenode channel, let us know who you are! |
* * |
| Line 44: | Line 45: |
| Line 74: | Line 76: |
| == Time to code! == * Do your best to write good code! * Track your progress: the more detailed, the best chances to your project to succeed * Keep in touch with your mentor all the time * Write reports/updates to your mentors and mailing list * Log your activities somewhere (wiki is great for this, and you can create your own wiki page) |
== Things to consider == * == How to succeed == * Don't overbook yourself. You'll have a lot to learn before you will get to the point where you can begin coding your project, and the projects are all non-trivial. We will provide you with amazing support from the mentors and community, but it is up to you to make sure that you can focus on your project * Your mentor is here to help you; don't be afraid to ask the difficult questions, or even the easy ones! * * Submit progress reports early and often. Use these to honestly reflect on how well you are doing towards your goals, and make adjustments to your project plan to match. |
| Line 86: | Line 100: |
== Ubuntu Projects == The lists of Ubuntu project ideas for Summer of Code 2010 are found on the |
Google Code In 2010
NOTE: This page is being updated for this project
Ubuntu would like to participate in the Google Code-in 2010, and is eager to attract good, capable, eligible students to apply for the projects.
If you are a registered student and are 13-18 years of age, you can apply for one of the projects or work on a project for another organization.
We would like to select students who are enthusiastic about their projects and are able to commit the time and energy required to make them successful.
How to start
- Make sure you are eligible to participate
- Review our
Read the Selection Process / Proposals section very carefully
- Create your profile in our wiki page:
Apply from
Can you participate?
- You need to be enrolled as a student and have your parents' permission to participate
- You need to be 13 -18
- If you are a Google employee, intern, contractor, family member, or resident and national of Iran, Syria, Cuba, Sudan, North Korea, and Myanmar (Burma), with whom Google is prohibited by U.S. law from engaging in commerce, you won't be eligible to participate.
Application Process and Proposal
Reports
We suggest you send the following report to your mentor every 2 weeks minimum
Subject: Project name - Date of report TIME SPENT: approx hours HIGHLIGHTS: what you learnt/ enjoyed the most CONCERNS: what is concerning you that is out of your hands to change WAITING ITEMS: Are you waiting for anyone else to complete a task or are you depending on someone else STALLED TASKS: If you are stuck, please state the factors that delayed those tasks ACCOMPLISHMENTS: List them by importance MINOR TASKS: Any other tasks ACTIONS FOR FOLLOWING WEEK:
If you don't have the time to write a report or you had a busy week, you should at least send an email to your mentor answering the following questions
- What have you done since your last status report?
- In the process of doing it, what did you run into, both positive and negative?
- What did you do about what you ran into, both positive and negative?
- What are you going to do next?
Things to consider
How to succeed
- Don't overbook yourself. You'll have a lot to learn before you will get to the point where you can begin coding your project, and the projects are all non-trivial. We will provide you with amazing support from the mentors and community, but it is up to you to make sure that you can focus on your project
- Your mentor is here to help you; don't be afraid to ask the difficult questions, or even the easy ones!
- Submit progress reports early and often. Use these to honestly reflect on how well you are doing towards your goals, and make adjustments to your project plan to match.
The end
- Keep in touch
- Blog about your experience
- Become part of our community!
Ubuntu Projects
The lists of Ubuntu project ideas for Summer of Code 2010 are found on the
GoogleSoC2010/Students (last edited 2010-10-22 15:18:12 by c-98-195-219-156)