Platform Team Meeting 28 March 2006

Agenda

• Question of the week: What issue or problem is on your mind today?
• 0.7alpha2
  • performance: what are the options for alpha2?
  • designs/plans expected in alpha2: realistic?
    • dump and reload
    • stamping
    • sharing format
    • email
  • do we have all of the tasks captured in bugzilla?
• Example bugs (feeds parcel, flickr, etc.), "Chandler won't start" bugs
• Unit test infrastructure
• Open issues of note
  • multiple threads and notification storms
  • onidle to handle conflicts?
  • What is the current state of cross-thread messaging? In particular, how can the sharing layer keep the main thread apprised of status messages/errors without using repository commits? If the user initiates a subscribe, publish, or sync (which will soon all be running the background), what mechanism should I use to let the UI know when the operation is complete, as well as status info during the operation?

Notes

• Question of the week: What issue or problem is on your mind today?
  • Katie: Notification storms
  • Grant: Flexamerica, and how to subscribe to various calendars
  • Andi: Getting PyLucene to work without SWIG
  • Morgen: How background tasks are going to interact with the main thread? How does the user cancel a background operation?
  • Phillip: How to coordinate Python 2.5, setuptools, and chandler release schedules
  • Brian: Chandler isn't fast enough, what's the email plan?
  • Bear: Fragile sections of the build -- some ideas in mind for how to fix these -- put a bullet to the head of hardhat

• Alpha2 Performance
  • background sync should give the perception of sharing being faster
  • main view as it does a refresh, will notify the main thread about everything coming in
    • refreshed in smaller chunks, the ui will feel less frozen -- would break the way we do view merging
    • perception of the ui being less frozen
    • test a big share with background sync -- big share, 3000

• Design plans in Alpha2 realistic?
  • dump and reload: maybe
  • sharing format: no
  • email: maybe
  • stamping: ??
  • we forgot i18n, presumably yes

• Chandler won't start bugs: these go to Andi. He needs a repository to be able to debug them, though.
• Example bugs:
  • Grant suggested throwing darts to pick who owns them.
  • Morgen suggested giving them to the owners (Ted/Flickr, Morgen/Feeds, etc.)
  • Bear suggested that spreading the bugs around might have other benefits (more people get to understand different parts of the code, etc.)
  • Katie (the 'Examples' component owner) will do some combination of the above.

• Open problems
  • Chandler won't start -- there are deeper issues here, next step is to frame this problem on the dev list
  • We discussed Morgen's questions: he will frame some questions for the design team.

Status

Katie

• Progress
  • prepared product planning process proposal
  • finally wrote up requirements/decisions for collections and notifications
  • reviewed alpha2 bugs with people, reviewed DetailedAlpha2Plan
  • wrote reviews
  • read sharing format thread more carefully
  • dev list summary
  • moved latest architecture doc to trunk (oops)
• Plan
  • frame "dump and reload" requirements/issues for design list
  • finish reviews
  • figure out next steps for product planning
  • come back to stamping, sharing format issues
  • figure out next steps for email plan
  • start collections spec, and/or hand off to alec
  • start interop spec

Morgen

• Progress
  • Worked on a new background sync algorithm (Thanks to Andi for his advice)
  • Background syncing checked in now, experimental still, available via "Test | Sharing | Enable background syncing"
  • Tracked down the fact that certstore causes my sharing view to get refreshed, which fowls things up -- gave zanshin operations their own view for now, which meant moving sslCerticateQuery item to installParcel( )
  • Raised the issue about main-view commits to the dev list
• Plan
  • Start on "Decouple outbound and inbound email accounts"
  • Continue work on background sync

Brian K.

• Progress
  • Checked in and tested bug:4940, bug:4942, and bug:5134
  • Started work on bug:5136 - Ensure that no uses of ical4j Dates expect default timezone is UTC
  • Started work on bug:5133 - New draft -09 timezone element/property behavior to do floating time time-range comparisons is not supported. However, the QueryFilter^? class does support timezones in the actual time-range query to the indexer.
• Plan
  • Finish all outstanding bugs for Cosmo .3 release including bug:5136 and bug:5133

Grant

• Progress
  • Finally got new floating timezone changes in (5444 Traceback when sorting by date)
  • 4994 can't change time zone on event when event started in a non-standard timezone
• Plan
  • Finish a couple of peer reviews I didn't get done before my vacation
  • 5209 Use new smart-naive datetime for all new events
  • Subscription-related fixes for 0.7alpha2

PJE

• Progress
  • Posted plan for egg parcel plugins to Dev
  • Implemented HelloWorldPlugin
  • Helped resolve Linux release problems w/missing setuptools files
  • 20% project work on Python 2.5 (all the items marked "DONE")
  • Implement cloud definition support for Annotations, per John's request
  • Implemented a runtime scheduling API for PeriodicTasks, per Morgen's request
  • Misc. developer assistance
• Plan
  • Help Bear get plugin support into the build
  • get setuptools 0.6a11 out
  • port plugins

Andi

• http://kumu.osafoundation.org/~vajda/logs.cgi