Platform Group Meeting 24 Jan 2006

Agenda

• Question of the week: How did sprint week go? Name one thing that went well and one thing we should do differently.
• 0.7 Planning
• OSU student projects
• Hiring: Java dev manager, mobile, interns, wiki/website info architecture

Notes

• Question of the week: How did sprint week go?
  • It was great for getting quick answers to questions, great for serendipitous conversations
  • It would be more satisfying to finish something, one day was not enough time to sink into a problem and really finish it
  • It was good to have everyone out at the same time, good to see everyone
  • Several people expressed interest in doing it again sooner than 6 months: would be nice to have people in the office quarterly.
  • Didn't seem to be much breathing room -- would be better to pick a full 5 day week
  • Would be great to have some sprints that involved design team
  • Would be good to have two sprinting days back to back
  • Would be good to have talks separately from the sprints (separate room/separate time)
  • Would be good to have cosmo and scooby sprints in same room as chandler
  • Would be good to plan out projects ahead of time to encourage people to venture outside of comfort zone and what they already know
  • Would be good to have some opportunities for structured knowledge transfer: coaches, focused mini sprints
  • Would be good to have a focused goal and have more directed work on a problem that we really want to solve (instead of just what is cool), get a large # of people working on some hard problem that needs attention
  • Talks + sprints created an atmosphere of "osafcon" which was cool
  • Perhaps do lightning talks: life hacks, environment/debugging, etc.
• Jeffrey will hand ownership of recurrence to Grant, so he can focus on apps work
• Grant will be the owner of scheduling platform support (invitations/freebusy)
• Grant is the new owner of email
• The proposed 0.7 goal for i18n is: Be able to accept translations from community in .po format.

0.7 Tasks

• PJE
  • schema evolution -- downgrading and upgrading
  • eggs/setuptools
  • cpia refactoring help
  • maybe undo framework
  • maybe domain model help
• Grant
  • recurrence
  • free busy support/invitations
  • CalDAV interop work
  • timezone
  • email reply, reply all, fwd infrastructure (support dashboard)
• Morgen
  • sharing refactoring
  • background sync
  • conflict resolution framework
  • user notifications
  • maybe command line ui
  • maybe integrated data in/out
  • maybe wsgi
• Brian K
  • i18n
• Andi
  • move collections "below the line"
  • performance
  • revisit sorted indexes
  • merge work
  • support search
• Ted
  • domain model refactoring
  • add contacts to domain model
  • community work
  • maybe scripting (scripting plan)
• Bear
  • release packaging
  • egg/setuptools support
  • general build improvements
  • mac intel
  • linux distro work
  • maybe instrumentation framework
• Heikki
  • performance
  • maybe talkback
  • security plan
  • accessibility plan
  • maybe CalDav^? ACL
• Jeffrey
  • vobject timezone bugs

0.7 planning questions

• Content model and table relationship?
• Item notification?
• What should the 0.7 goal be for caldav interop?
• Does background sync overlap with jeffrey's plans for import in background thread?
• Exceptions, translations, i18n?
• i18n open bugs?
• Are we doing instrumentation framework and who is doing it?
• When is the switch to 0.6.1? Plan for ubuntu depends on this.
• Timeframe for Panther, OSX?
• Have to build our own Python (packaging issue) -- this an obstacle to linux distributions
• Talkback -- server end problems
• Is Cosmo going to have ACLs by the time we ship 0.7?

0.7 planning next steps

• Sidebar/collections code review
• Get to next level of granularity with scheduling tasks
  • Thursday open design meeting about scheduling (freebusy/invitations)
• Schema evolution: Please review pje's writeup
• Timezone: proposal is circulating on the design list, needs to get written up
• Resolve schema display name -- required for i18n
• Propose i18n goal for 0.7: Accept translations from community in .po format
• Domain model conversation (Ted, Mimi, Sheila)

Status

Katie

• Progress
  • 0.6 debrief: ZeroPointSixDebrief20060109
  • sprint week: JanuarySprints2006
  • started RDF export parcel, will work on this in spare time
• Plan
  • get 0.7 plan together
  • get 0.7 bugs targetted correctly for platform folks (move bugs we're not planning on fixing to 'future')
  • brainstorm projects for OSU students
  • interviews

Brian K

• Progress
  • Worked w/bkirsch to draft API and data structures for i18n of messages and resources in eggs
  • Worked with BCM to come up with .3 Cosmo Plan
  • Various Email discussions and meetings for .7

• Plan
  • Document .7 i18n plans including new egg translation model
  • Short write up on i18n bitcon conference in Hong Kong
  • Read Lisa's WebDav^? book and start looking at Cal Dav standards
  • Review Cosmo code base and set up Cosmo development environment

PJE

• Progress
  • Worked w/Bear to get setuptools (egg support libraries) into Chandler
  • Worked w/Bear to clarify build-system goals for eggs in 0.7 and beyond
  • Worked w/bkirsch to draft API and data structures for i18n of messages and resources in eggs
  • Got egg shared library support working on Linux, rough (unfinished) support for Mac
  • Developed draft (unfinished) code for discovering egg parcels and loading or updating them
  • Misc. assists during sprints, gave doctest presentation

• Plan
  • Learn to use a Mac so I can finish shared library build support on Macs
  • Continue work on egg parcel loader and egg i18n
  • Look deeper into cross-egg shared library issues raised by Andi, and begin to define a better shared library build API for the distutils/setuptools to better support Chandler's more complex build requirements

Morgen

• Progress
  • Migrated the feeds parcel to use twisted. Added a unit test for this.
  • Sprints: XML-RPC / Dashboard / IMAP server
  • Met with Sheila, et al, to discuss 0.7 goals, which appear to include not only include async sharing, but a conflict resolution framework, and user-level Notification framework (could be as simple as a special FeedChannel^?)
  • Met with Mimi, et al, to discuss DataInOutOfChandler
• Plan
  • Work on 0.7 sharing spec
  • Incorporate Grant's previous work on async sharing

Grant

• Progress
  • 4980 Don't allow PROPPATCH failure to railroad calendar sharing
  • 4998 zanshin can't sync with twisted dav server
  • Participated in parcel writing sprint; wrote & demoed a simple parcel to query for events from eventful.com.
  • Participated in QA sprint; wrote some WebDAV tests with LisaDusseault.
  • Many meetings, including Email design discussion.
  • Started work on a small program to execute HTTP/WebDAV tests written in xml (from Lisa).

• Plan
  • Figure out what I'm doing for 0.7.
  • zanshin bug fixes/improvements.

Ted

• Progress
  • Lots of sprint week community discussions, particularly with Cosmo and Scooby team
  • Quicksilver -> XML-RPC connector; simple command line interface
  • Revive RSS Stress test
  • Worked with UCB guys on parcel
  • Worked with John Anderson on modernizing Flickr
  • Discussion on getting data in and out of Chandler
• Plan
  • 0.7 plan
  • MSN Search Champs

Andi

• svn and bug activity