From Nsnam
Revision as of 05:00, 15 November 2013 by Tomh (Talk | contribs) (Once you're there)

Jump to: navigation, search

Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects

Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers

What is a sprint?

A sprint is a scheduled time for ns-3 contributors to gather and focus their undivided attention on improving the code, documentation, or tests.

Sprints are open to anyone, and are conducted on IRC, and if needed, other virtual meeting technologies.

  • IRC channel is #ns-3 at irc.freenode.net

The Django project has a good reference and links to some presentations all about coding sprints.

A summary of the results of sprints will be shared with other developers on the ns-developers mailing list.

Upcoming sprints

  • Friday November 15, 14h00-20h00 UTC (note: attendees are welcome to attend a subset of the 6-hour slot, if so desired)
    • Topic: Documentation improvement. https://www.nsnam.org/bugzilla/show_bug.cgi?id=938. In particular, we will work on reducing the number of doxygen warnings that are generated due to missing Doxygen. This is a long-standing issue that just requires group effort to resolve.
    • Organizer: Tom Henderson
    • Preparation:
      1. Read the general preparation below
      2. Make sure you have Doxygen installed on your system, and can run the shell script 'doc/doxygen.warnings.report.sh' (it may take a while to run, and should generate a lot of warnings)
      3. Contact ns-3-users mailing list or the organizer for help if you have trouble with the above
    • Tasks: Fix as many of the doxygen warnings as we can. The current count of warnings (by module) can be seen here: http://mailman.isi.edu/pipermail/ns-commits/2013-November/014304.html. There is a full log generated that can be used to identify what is the error, and then it can be fixed with a text editor. How this is planned to work is that contributors who show up will be assigned a file or set of files (that they are comfortable with documenting) and will try to clear the errors in that file, producing a patch that can be merged to ns-3-dev.
    • Coordination: We will use IRC and Etherpad to coordinate the work (make sure multiple people do not work on the same file).

General preparation

  • Make sure that you can join the IRC channel in advance
  • Make sure you can checkout the development version of ns-3 (we will use ns-3-dev)
  • Familiarize yourself with how to generate a patch against ns-3-dev. Patches you write can be uploaded to Bugzilla or sent to one of the maintainers.

Once you're there

  • Check in on IRC by letting others know that you've joined and are ready to contribute, and a maintainer will go from there