ns-3 is applying to GSoC 2010. Check back to this page for updates. If you want more information about possibly participating in the ns-3 GSoC program, read the below information.
The following are specific items the ns-3 teams requests GSoC applicants include in their proposal.
- About You
- Identity Information
- Name. Yor name
- Date of birth. Your date of birth
- Email. Your contact email
- Country. Your country
- Background. What experience or training do you have that makes you best suited to this project? What is your previous experience with ns-3?
- Education. Include your academic or professional background related to data networking, as well as any software experience with C++ and/or Python. In which school program are you currently enrolled at and what is your specialty there? When did you started your current studies?
- Work. Be sure to denote any work experience you have in relevant areas. Your past work experience does not need to be a job where you got payed, you can mention any projects you have participated in. Have you ever worked in open source projects?
- Research. Be sure to denote any research experience you have in relevant areas.
- Personal Interests. Briefly tell us about the things you are interested in.
- Identity Information
- About The Project
- Project Proposal. What is the specific topic or area of interest you are proposing to work on? Explain what this project consists on.
- Interest. Why are you particularly attracted to this project? What makes you the best candidate?
- Future Plans. We are especially interested in GSoC applicants looking to pursue research or work in related areas in the future, so be sure to note any relevant plans you may have.
- Approach. What is your technical plan for achieving the goals of the project? What components and functionality will have to be developed, integrated, etc? Which development methodology would you use? What testing approach are you going to use to ensure the code quality?
- Deliverables. What do you plan as a mergeable code output of your GSoC effort? Please keep in mind that the program is only 10 weeks long and try to incorporate this realistically in the plan. Try to isolate the project main features, group them into coherent units, and list them as 'milestones' or 'deliverables'. The order in wich you list the deliverables should correspond to the chronological order in which they will be implemented.
- Plan. What is your task schedule to implement your technical plan and develop your deliverables? Try to break down the deliverables into small tasks and assign to each of them the time you think it is going to take you. Make sure you consider the time you will need to test and fix your code after every deliverable is finished. Order all the tasks chronologically and assign a start and an end date to each of them. Verify that the resulting schedule fits into the 10 weeks you will have. It is important to leave some time at the end of the schedule for integrating, testing and fixing the complete project.
- Timezone. What are your expected work hours (in UTC)? What is your physical location for the summer? The project places no requirements on these but it will effect chat scheduling as well as mentor availability and selection.
- Commitments. Do you have any other commitments over the summer that would impair your ability to participate in the project, e.g., classes, thesis defense, existing work commitments, etc? Note: The project does not expect students to take personal vacations during this period; if there is a personal conflict planned, please state when, and how you would make up the time.
Of these, the Approach and Deliverables elements will require significant thought, development, and discussion. Applicants are advised to bring their ideas to the ns-developers list and open up a discussion with the ns-3 team to develop these portions of their application prior to submission. Only applications that have well refined and developed technical objectives and plans are likely to be competitive. The ns-3 team will provide comments and help refine proposals somewhat after they are initially submitted, but obviously the stronger they start the stronger they will be. In the 2008 GSoC, our strongest student proposals were clearly those which had discussed their projects at length beforehand on the mailing list and on IRC.
In addition, once GSoC proposals have been accepted and reviewed, promising candidates will be invited to "meet" some of the ns-3 team and discuss their project further in an IRC chat.