Difference between revisions of "DevelMeetingMay2015"

From Nsnam
Jump to: navigation, search
(Suggested agenda/topics)
(update for past event)
 
(7 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
= Location and Schedule =
 
= Location and Schedule =
  
The meeting will occur Friday, May 15 at CTTC's facilities as part of the ns-3 annual meeting
+
The meeting was held on Friday, May 15 at CTTC's facilities as part of the [https://www.nsnam.org/overview/wns3/wns3-2015/local-information/ 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.
+
= Agenda/topics =
 
+
= Remote attendance =
+
 
+
We will possibly run a Google Hangout; please email [mailto:tomh@tomh.org tomh@tomh.org] if interested to be invited.
+
 
+
= Attendees =
+
 
+
Please add your name here if you intend to attend, and which days.
+
 
+
* Tom Henderson
+
* Peter Barnes
+
* Nicola Baldo
+
 
+
= 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.
+
  
 
# '''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).   
 
# '''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).   
Line 30: Line 14:
 
#* What about Fedora/RHEL (which Vedran has raised in the past)?
 
#* What about Fedora/RHEL (which Vedran has raised in the past)?
 
#* What about distributing Docker containers and Live DVDs?
 
#* What about distributing Docker containers and Live DVDs?
 +
# '''Object stop/start and failure/repair''' Vedran will report on work to implement the stop/start and failure/repair models discussed last year (notes [http://www.nsnam.org/docs/meetings/ns-3-developer-meeting-notes-May14.pdf here]). 
 
# '''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.
 
# '''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.
 +
# '''ns-3.24'''  Review possible work items and how to get them on a schedule for August 2014 ns-3.24 release.
 +
#* Wiki page:  [[ns-3.24]]
 +
# '''Git?'''
 +
# '''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 =
 
= Meeting Notes =
  
Will be posted at a later date.
+
Available from [http://www.nsnam.org/docs/meetings/ns-3-developer-meeting-notes-May15.pdf this link].
  
 
[[Category:DevelMeeting]]
 
[[Category:DevelMeeting]]

Latest revision as of 22:01, 9 June 2015

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 was held on Friday, May 15 at CTTC's facilities as part of the ns-3 annual meeting.

Agenda/topics

  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

Available from this link.