| 29 | | This software development session provides an opportunity for GENI developers to collaborate informally. Topics are TBD based on topics raised by the GENI developers in attendance. |
| | 29 | This software development session provides an opportunity for GENI developers to collaborate informally. At this GEC, the Developer Roundtable will cover two primary topics; (1) tasks and |
| | 30 | communication modes for maintaining GENI, and (2) GENI enhancements to adopt and develop now. |
| | 31 | |
| | 32 | We will first discuss how the developer community will operate in the near future as GENI changes into operations and maintenance mode, and GECs become less frequent. What mailing lists, issue tracking, or meetings will we use? What tasks must we perform to make GENI software maintainable and transitionable? Should we follow a more formal decision process? |
| | 33 | |
| | 34 | We will then discuss tying up loose ends in GENI development, and addressing low hanging fruit that are potential big wins for experimenters or for making GENI more maintainable and transitionable. The people in the room will decide what topics these are, but topics may include: |
| | 35 | * Status updates on recent development |
| | 36 | * Speaks For roll-out |
| | 37 | * Stitching (multi-point in the core, OpenFlow stitched VLANs, etc) |
| | 38 | * AM API deployment status and draft proposals |
| | 39 | * Adding new resource types to GENI |
