Cosmo 0.5 Debrief

Please take the time and ask yourself the following questions:

• What should we be doing "more of"?
• What should we be doing "less of"?
• What should we do the "same as"?

Feel free to add some of questions at the bottom of this page. The idea is to phrase feedback about the project in a constructive way.

A short list of topics to seed the discussion:

• Planning and specs
• Design sessions
• Design List
• Cosmo-dev list
• Development projects
• Testing and the automated test framework
• Release process, bug councils

More of

• more checkpoints
• priss: we got more organized with bug councils, etc.
• more documenation - we need more tech proposals - so far with 0.6 this has been good.
• more collab w/ Chandler folks
  • for dependencies
  • earlier testing and integration
  • make sure Chandler folks test their stuff in Cosmo earlier, keep them informed of protocol changes, etc.
    • eg. Free Busy
• more insight, transparantness into test plans
• make sure we test with SSL, on remote machine
• verify all bugs
• twl - more handoffs in the mailing lists, more status, letting people know where you're at
  • on the mailing list of course
• cowbell
• more questions, less declarative statements.
  • i.e. don't jump 2 conclusions
• QA needs to understand releases to JSON-RPC methods
  • send mail when changing RPC stuff, it's a public API
• we should link all our wikipages to planning pages
• need to document as we write the code
• need to allocate time to doc code
• need more unit tests ('specially on the JS side)
• stage QA throughout release cycle w/ checkpoints
  • relesase notes in checkpoints for new features?
    • can gen through SVN, bugzilla
• when you finish a UI feature use HumanSpeech^?(tm) to "talk" to Priscilla

Less of

• less "kitchen sink release" -- took too long
  • bcm wouldn't have done that differently though in this case
• priss - we need more clarity around roles

Same as

• [edit here]

Questions/Notes

• Do we need a 'Demo machine' for significant launches? Should it be different from osaf.us? If so, who will maintain it?
  • bcm - sure but dev should not own it
  • mikeal - create a test ticket/account for everyone to test
  • Bear to own this, will coordinage w/ adam who will write scripts
    • note if we use QA cosmo it will be behind firewall
    • Jared - cannot use qa-cosmo, will be some other box.
• Update Cosmo release page: http://wiki.osafoundation.org/bin/view/Projects/CosmoReleaseProcess I didn't see it till after 0.5 launch.
• Jared is concerned about migrating
  • don't wait till last minute (or last week for that matter) to test
  • twl will start a discussion on the list about timing for testing migration
  • jared will make snapshots of osaf.us data availble to devs for testing migration

-- BobbyRullo - 16 Nov 2006