Report on ns-3 participation on GSoC 2010
This report is intended as a reference guide for Organization Administrators (OAs) participating in the Google Summer of Code program for the ns-3 project.
The job of the OA
The OA is the person (or persons, can be more than one) responsible for organizing the project participation in GSoC. This includes announcing important information in the ns-3 mailing lists, interacting with the GSoC team, answering questions and encouraging interaction between students and the ns-3 community, taking care of problems related to the program and most important, making sure deadlines are met by mentors and students.BR Next is the list of tasks performed by the OAs during the program:
First stage of GSoC: The preparation
1. Creating the ns-3 project's ideas page in the wiki. See GSoC 2010's Ideas Page. 1. Creating the ns-3 project student's application template in the wiki. See GSoC 2010 student's application template. 1. Creating the ns-3 project student's guide in the wiki. See GSoC 2010 student's guide. 1. Searching for volunteer mentors and projects ideas. (A good place to start is the ns-3 developers mailing list) 1. Submitting the organization's application to GSoC program. 1. Announcing the ns-3 project's acceptance on GSoC in the ns-3 users and developers mailing lists. 1. Creating ns-3 Organization's Home Page on the GSoC Site. 1. Advertising the ns-3 project participation in the program amongst students 1. Encouraging discussion of students project's ideas in the developers mailing list. 1. Announcing the openning of the student's application period in the ns-3 mailing lists. 1. Verifying that mentors are officialy registrered at the GSoC site before the mentor's registration deadline. 1. Coordinating the review of students projects proposals with the future mentors and OAs. 1. Ensureing that all students proposals are rewieved and ranked, and matched with a mentor before the student ranking/scoring deadline. 1. Attending GSoC's IRC meeting to resolve any duplicate accepted students. 1. Encouraging communication between students and mentors and the integration of students with the ns-3 community during the Community Bonding Period. 1. Defining evaluation instances for student's projects during the program. 1. Setting up the accepted projects page at the wiki. See GSOC 2010 ns-3's accepted projects
Second stage of GSoC: The Coding
1. Ensureing that mentors and students are aware of and meet the midterm evaluation date. See [ student's midterm evaluation questions] and [ mentors's midterm evaluation questions]. 1. Asking for code reviews of the student's project in the developers mailing list. 1. Ensureing that mentors and students are aware of and meet the final evaluation date. See [ student's midterm evaluation questions] and [ mentors's midterm evaluation questions]. 1. Submitting OA final evaluation at GSoC site.
Final step GSoC: The end
1. Updating the project's information on the ns-3's Google code repository. 1. Ensureing that passing students upload their code samples to Google. See the GSoC's 2010 code submission guidelines
The program documentation
It is advisable for OAs to read the available documentation on the program. At GSoC site you will find a description of the program. BR Other important documentation is the GSoC's 2010 User GuideBR Also the mentor's guide is worth reading.