0.5 Remaining Business

• Docs: Katie will send out email about which docs we still need to do
• Debrief: we should see what to follow up on from the debrief, and whom

CSG meeting, April 21-222

• Can we have our 0.5 docs in by then?
• Pieter should send information to everyone@osafoundation.org about this meeting...

0.6

Specs

• Restructured text format proposal? This didn't get a lot of support due to perceptions of limited ability, Wiki-like formatting (YAML) and relatively rare use (compared to HTML)
• Why have one format anyway? Why not have each author use their own favorite? Without ruling out alternate formats, we should have one common suggested format, partly for consistency of look (although other formats may be able to translate to the common format), partly because specs may be authored by multiple people (more participatory to have a common format).
• Sticking with HTML: Lisa to produce CSS appropriate for viewing specs

Scheduling/planning

• Repository performance work item needs more definition -- goals -- Katie owns
• Is data upgrade on the 0.6 schedule? Do we do this by exporting/importing a user's calendar data or by doing data migration in code?
• Ted will be owner of Item Collection 0.6 project spec
• Discussions about changing the sidebar for 0.6 and maybe for Kibble -- some disagreements right now about how that should be done.
• The "List 1" bugs are still the top work for the Apps team -- any specs that might involve new UI come after the "List 1" bugs.
• Katie to review Spike and identify what to use in 0.6
• Jeffrey and Sheila will need to work on either a spec on "recurrence" or a more general spec

on import/export of calendar data

• Search GUI: still don't have a resource for this because we're still scoping out "List 1" and how long that will take.
• Services team is working on more detailed estimates based on ZeroPointSixEngineering

Theme

• "Usable Calendaring"? That doesn't quite cover everything we're doing
• "Usable calendaring and developer productivity"? This covers everything except the next steps of i18n support and IMAP support.

Planning for Ted/Phillip's visits

• Code review? Phillip could select some code and describe what he sees in it
• Tutorial? Could be seen as less directly applicable, but OTOH people might be interested in

learning more about Spike, Egg, protocols, or other stuff Phillip's familiar with

Technology upgrades

• Fedora core 2, move to Fedora core 3 or skip to 4? There might be a "rough consensus" on this despite Heikki but we'll wait for him to be back
  • Related issue: support for Debian? We do work on Debian though we don't support it. We can, however, document in release notes or similar location. We are looking for volunteers definitely, because we don't have this very high in our own priority list.
• SWIG version is definitely being upgraded as part of the wxWidgets upgrade already underway
• Python version upgrade? Again Heikki might be the holdout so we'll talk to him. We've seen perf improvements from upgrading python in the past.
• Some discussion about the appropriateness about being risk-averse with technology upgrades: at this phase in our development, moving to new releases of things like Python has fairly low risk.