- ns-3 GSoC/NSoC Student guide
- NSoC Student application template
- NSoC 2011 Ideas page
- GSoC 2010 Ideas page | GSoC 2010 Accepted Projects
- GSoC 2009 Ideas page | GSoC 2009 Accepted Projects
- GSoC Organization Administrator guide
- Get in contact with the ns-3 team: ns-developers mailing list | IRC #ns-3 on freenode.net
This webpage highlights the expectations and requirements for student applicants for ns-3's Summer of Code (NSoC) 2011 effort. These guidelines follow those that we have used in past years for the Google Summer of Code, but readers should be aware that the 2011 program is not affiliated with Google (since we were not selected this year for GSoC), and that in particular, no student or mentor funding is associated with NSoC.
The ns-3 team is looking for three things from every successful NSoC project:
- Developing code that can be incorporated back into the main codebase and utilized by a variety of users.
- Developing new members that will remain part of the team and contribute to the ns-3 effort even after NSoC ends.
- Providing NSoC students with experience and ideas that will be useful to them in their careers and/or research.
- The student will be expected to commit fully to the project, the time effort required from the student will the same as a full time job. Applicants should recognize that being accepted into NSoC is a serious commitment and will be the focus of their time over the duration of the program. Any existing commitments for class, other jobs, etc *should* be discussed as part of your application.
- At the beginning of the program, the student will be required to provide a detailed plan of work covering the 12 weeks of NSoC. This should be developed with the help of the mentor. Students will have to setup a wiki page for their project, and cover important aspects of their proposal's design, the strategy to implement it, a list of deliverables, and lastly, update the wiki page as and when each milestone is achieved. This page along with the code repository allows the community to keep track of the student's efforts.
- The student will be expected to produce mergeable code (either merged completely at the end of the project, partially at the end of the project, or not merged yet but no major roadblocks foreseen to merge shortly after the program ends).
- The student will be expected to follow ns-3 design guidelines (follow coding style, write tests, documentation).
- Students are required to submit weekly reports on the mailing list, covering the progress they've made or the obstacles they've run into. This will help the community keep track of the student's efforts, and help as needed.
- The student will have his or her code reviewed twice by the ns-3 community. The first review will be taken prior to the mid-term evaluations and will look at issues such as scope, public API, test plan, and open issues. The second review will be taken at least two weeks prior to the end of the program and will include review of the produced code for possible merge into the project main tree. All students will be briefed on a checklist of things to prepare for these reviews. Between these reviews, mentors will periodically (at least weekly) review the student's output and will provide guidance where needed, and track this progress in a public place such as a wiki entry or the mailing list.
- If a student drops the project before the NSoC program ends, he/she will be failed.
Students have inquired about what software development background and tools are required. ns-3 development typically requires proficiency in C++ and a debugger such as gdb or ddd. The valgrind suite of tools, and a system profiler such as oprofile, are typically useful. Python may be necessary for some projects dealing with the build system or that involve using Python to integrate ns-3 with other programs, but is generally an optional component.
The Selection Process
Selection of students for NSoC will be competitive; last year, for GSoC, this project saw a 12.5% acceptance ratio.
The students will be selected by a selection committee which will consist of the candidate mentors and selected active maintainers. Students projects will be evaluated and scored according to the following criteria:
- 1) Overall technical quality of application, including whether the project seems feasible and properly scoped, whether the student appears knowledgeable about ns-3, C++, the models that are being proposed, and the project plan including proposed milestones.
- 2) Availability of a mentor for the suggested project.
- 3) Impact and relevance to future users of ns-3? (e.g. does proposed project support an active field of research? Are results of the project broadly applicable? Does it bring unique capabilities to ns-3?)
- 4) Participation and involvement in the community and with prospective mentors.
High scoring applicants may be asked to discuss their project details over email or IRC. When the evaluation process concludes, the organization administrator will determine the highest ranking applicants and if there are close rankings or concerns, hold a meeting among selection committee members to resolve tiebreakers.
List of 2011 mentors and reviewers
Mentors will be paired with students depending on the student applications selected. In 2010, a total of 12 members volunteered to help mentor student projects and/or review student applications. We had more mentors than available student slots.
The list of mentors and reviewers this year are: TBD.
Where to begin
A good starting point would be to read the NSoC 2011 Ideas page. After you decide which idea you would like to work on, join the development mailing list and enter #ns-3 on freenode.net IRC chat to discuss your ideas with us.
How to apply
Information regarding this will be up soon.
While students are encouraged to discuss their technical plans with potential mentors on the ns-developers list, they are under no obligation to share their application details on the list.
- NSoC is an excellent opportunity to gain experience working on an open source project.
- Working with the ns-3 project will allow you to improve your networking knowledge, C++ skills and to be in contact with a highly skilled team of developers and user group.
- This is a great opportunity to contribute to our open source community.
A piece of advice
Based on the ns-3 team's experiences in the 2008, 2009 and 2010 Google Summer of Code programmes, the most important factor in the success of an application and project is communication. That process begins in the application phase. Without joining the mailing list and initiating a discussion of your ideas, it is unlikely that your application will be complete or rich enough to be competitive. Please feel free to discuss your proposed technical approach, plan, and other factors on the mailing list while developing your application. In addition to helping you develop the necessary details, focus, and priorities to write a good application, this will also demonstrate your commitment and willingness to dedicate time to the effort. During the program, every student is expected to communicate regularly with their mentor, announce weekly updates of their projects and participate on the development mailing list and discuss their work over IRC chat.
Additional information about ns-3
Additional slides about the ns-3 GSoC project (from 2009) are also available, from a GSoC Infosession at the University of Washington on March 5th, 2009.