sprint 2012 11 18

#Sprint 11/18 Agenda

• Previous Sprint sprint 2012-11-01
• Next Sprint sprint 2012-12-06

1. sprint alignment and meetings

• week 1
  • Wed (14:00 CET / 07:00 CDT): SUSE Cloud internal review for previous sprint (with PM)
  • Thu (10:30 CET or later / 03:30 CDT): SUSE Cloud internal planning call (with PM)
  • Thu (15:00 CET / 08:00 CDT): Crowbar sprint Planning (Trello Board)
  • Thu (16:00 CET / 09:00 CDT) Dell Internal Planning
• week 2 (mid sprint)
  • Wed (14:00 CET or later / 07:00 CDT): SUSE Cloud internal review
  • Wed (15:00 CET / 08:00 CDT or later): Live Crowbar Check-Point ("design topics")
    • use IRC as primary. Scheduled Live meeting is available if needed
  • Wed (20:00 CET / 13:00 CDT): Dell Internal Sprint Review

1. 2.0 roadmap (SR, MVP, Release) 1. test coverage

• new code >= 80% coverage
• old code not there yet
• SUSE could help with obtaining metrics

1. Ruby version for 2.0

• SUSE prefers and targetting 1.9.3
• Dell OK with that

1. crowbar.github.com and documentation 1. Dell happy with new organization and homepage 1. Dell has new documentation guy just coming on board who can work on crowbar.github.com 1. agreed that crowbar.github.com should contain polished pages which are well thought out and make it easy for newcomers to join the project as users and/or developers 1. wiki will remain as home for development work, technical docs, work in progress etc. 1. documentation in code repos should be very polished and 100% consistent with code - also enable automatic generation in other formats (HTML) 1. OpenStack releases & CB2.0

1. Build server / Build tooling
2. CI granularity
3. CI gating
4. supported browsers
   1. HTML5 required
   2. SUSE has suggested support matrix
5. crowbar.yml
6. IRC monitors/scheduling/resources
   1. Dell got IRC working (#crowbar on Freenode) and will transition over
7. update on recent Dell work
   1. database UI
   2. CMDB integration
   3. engines and routes / controller namespace collisions

Pending Meetings:

• Progress review
• Maintain legacy code or start clean
  

Parking Lots:

1. BDD testing - Erlang vs Ruby
   1. client API simulator
2. Trello Review & Status
3. installation post Chef-decoupling