...

Bedework
Calendar user stories
Hosting - the wave of the future
OpenApereo side meeting?
COmanage Future on Sep 1 2014

Agenda - Wednesday

1. I2GS session planning (and dev meeting planning)
   1. Slides due 3/24!
2. Terena travel planning
3. Should mailing lists be objects in COmanage, perhaps tied to groups?
   1. This would allow for additional attributes to be managed explicitly (such as mapping groups to mailing list names, lists of moderators, whether the list should be archived, etc) that can then be passed to plugins such as the SympaProvisioner (CO-674)
4. git branching / management strategy

...

• 0.9 (target release by I2GS)
  • Notifications
  • UI
• 0.9.1 (pre-release for MyLIGO, then functionality freeze)
  • Search
  • Expirations
  • Terena CORE
• 1.0 (the MyLIGO release)
  • Scalability
  • Stabilization
  • Directory 0.2
• 1.1
  • Audit
  • Dashboard
  • Reporting
  • Credential Management
  • Directory 0.3
• Future
  • Directory 0.4

Note: needs more discussion

• CO-801
• Notifications (some will need an ack, some will not, some will not right away; some req an action)
• Release strategy that accommodates the need for something other than 100 issues per release
• What can a CMP admin do?

MyLIGO

When are we targeting a release? May would be great; will be doing a more detailed gap analysis today since the overall framework, incl notifications, is ready. The gap analysis is comparing the current functionality of MyLIGO 2 with what we currently have. No functionality may be lost.
We have to have something called "Directory" available; verify if what we have now will suffice.