DevelMeetingMay2015

From Nsnam
Revision as of 14:42, 13 May 2015 by Tomh (Talk | contribs)

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

Location and Schedule

The meeting will occur Friday, May 15 at CTTC's facilities as part of the ns-3 annual meeting.

A more detailed schedule will be posted at a later date but the schedule will be primarily driven by who is attending and what everyone proposes to discuss.

Remote attendance

We will possibly run a Google Hangout; please email tomh@tomh.org if interested to be invited.

IRC: #ns-3 on freenode.net

Suggested agenda/topics

Please list suggested discussion topics below and we will build a schedule at a later date. Please also suggest 'read-ahead' items as needed.

The specific time and time allocated for each topic will be agreed on-the-fly.

  1. Packaging and distribution. For a few release cycles now, there have been Debian/Ubuntu packages (most recently for ns-3.17: http://packages.ubuntu.com/source/vivid/ns3).
    • What should we do to help downstream maintainers?
    • How to get bake/DCE into these?
    • How to allow such distributions to evolve?
    • What about Fedora/RHEL (which Vedran has raised in the past)?
    • What about distributing Docker containers and Live DVDs?
  2. Object stop/start and failure/repair Vedran will report on work to implement the stop/start and failure/repair models discussed last year (notes here).
  3. Documenting the maintenance status of our modules. We can do a better job documenting the scope and maintenance status (list of open bugs that users should be aware of) of our modules. Recent work on this regarding wifi could be extended to other modules-- need to discuss further with other maintainers.
  4. ns-3.24 Review possible work items and how to get them on a schedule for August 2014 ns-3.24 release.
  5. Git?
  6. Module status review. Review code status of modules, time and interest-permitting. What are people working on? What important bugs exist and need fixing? Outstanding code reviews?

Meeting Notes

Will be posted at a later date.