Services, Repository and Dev Platform Mtg 2 Aug 2005

Agenda

• 0.6 topics
  • recurrence, timezone
  • sharing, zanshin
  • sets, collections
  • i18n
  • certs, ssl, tls
  • dev platform
  • runtime performance, memory footprint

Status

Andi

• Progress
  • fixed bugs: Bug#3501, Bug#3539, Bug#3628, Bug#3641 (fix is commented out)
  • performance: path processing is now twice as fast
  • reimplemented monitors using a ref collection and items
  • added forced monitor deletion code to Item.delete()
  • added overlooked support for copying abstract set instances
  • added iterSources() and iterSourceItems() to AbstractSet
  • fixed bug in mapChanges() with self._log changing during iteration
  • added 'domains' aspect as per Jeffrey's request
  • meetings about well known items, sets and set wrapper items
  • pyICU: announced PyICU project on freshmeat.net, reviewed pyicu-dev list and created pyicu.osafoundation.org homepage
• Plan
  • on vacation for 2 weeks, reading mail daily and taking some time out from vacation for blocking bug fixes

Brian K

• Progress
  • Meet with Q/A regarding i18n test plan. Aparna will begin the test plan design and consult with me as needed.
  • Fixed Bug 3294
  • Corresponding with Mimi on bug 2879. Need to determine what the appropriate error conditions are to result in the accounts dialog display
  • Further refined gettext API and LocalizableString^? interaction. A bit more to do here however.
  • Updated i18n .6 spec to include an initial Unicode UI input and display test scenario

• Plan
  • Need to finish off the _() interation with LocalizableString^? logic for .6 and beyond. Still to be determined:
    • Which is better a central file ie. message.py for all global message strings or an addition to the _() syntax ie. _(u"This is a global message", global=True)?
    • What will _() return if the pygettext utility not run yet? Traditionally gettext returns the string inside _() but we want it to return a LocalizableString^? from the Repository. However that string is not created yet. It is the chicken and egg problem. Options: * Return a Python unicode object with the defaultText. This would be an issue if a developer is assuming the type is LocalizableString^? * Raise an error if no LocalizableString^? found asking the developer to run the utility * For go the pygettext utility all together and add the LocalizableString^? to the Repository the first time it is encountered in a _()
    • How should _() be handled in .6. Initial thoughts are have a single ref-collection where all LocalizableStrings^? keyed on defaultText. Then when Python eggs come in to play refine. In .7, the LocalizableString^? needs to know the path to its parcels translation files.
    • work on bug 3583, 2584, 3585
    • Finish off bug 2879
    • Update i18n spec with LocalizableString^? schema and decisions
    • Catch up on new schema and architectual changes in Chandler.

Katie

• Progress
  • discussions about set integration, well known items, i18n parcel loading, dev platform plan
  • 0.7/0.8 planning with Sheila and Mimi
  • upcoming design work: KatieParlante20050801
• Plan
  • get head around open content model issues
  • get i18n strategy written up
  • get "addressing" strategy written up
  • get dev platform list written up

Morgen

• Progress
  • Added osaf.app parcel, moving various xml-defined data items to python
  • Migrated CurrentPointer to Parcel.Reference
  • Added Unpublish feature
  • Better unicode support in servlets
  • CalDAV support: I was able to sync with the rpi.edu CalDAV server; individual iCalendar files can be imported/exported
  • Photos: image data now lives in 'body' attribute
  • Hosted a code review of Sharing / Zanshin
• Plan
  • Complete CalDAV work:
    • autodetect when to read/write in CalDAV mode
    • move Chandler XML down a level
  • Work on sharing dialogs based on feedback from Mimi and Sheila
  • Modify the ContentItem.isAttributeModifiable( ) logic to take into account the "direction" (inbound vs outbound) of the shares an item participates

Grant

• Progress
  • Added basic CalDAV support to zanshin.
  • Held zanshin code review (jointly w/ MorgenSagen -- Sharing).
  • Awaiting review: Bug:3667 (Handle default timezone), Bug:3668 (Timezone drop-down in calendar view).
  • Discussed options for resolving potential na�ve datetime issues with AndiVajda.
  • Flailed away to implement a first cut at timezone-related functionality (calendar view & detail view). Hacked around some problems, which I'll write up and discuss with various component owners.
  • Fixed Bug:3578 (Parcel Loader support for LocalizableString and Text).
• Plan
  • Incorporate zanshin/Sharing code review feedback.
  • Write up timezone issues.
  • Attend OSCON Wed�Fri

PJE

• Progress
  • Replaced TwistedReactorManager and osaf.framework.wakeup with osaf.startup
  • Helped define and design new addressing schemes, including Reference, ns, etc.
  • post initial contentmodel->pim flattening proposal
  • Port certstore.data to use Python instead of XML for loading
  • Added forward reference support to Python item creation tools
  • Help others with porting parcels to Python
• Plan
  • flatten contentmodel
  • add __version__ support to installParcel
  • investigate possible repository-to-Python code generator or export facility

Jeffrey

• Progress
  • importing recurring events now create recurring events in the repository
  • lots of feature additions/bug fixing on changeThis for recurrence so that basic recurrence UI is reasonably usable
  • talks with Alec and Bryan about shifting recurrence implementation slightly to work better for UI
• Plan
  • Proxies. Yes, really, this week, I mean it, it's really going to happen, I'm not going to put it off any longer. Really.
  • tzinfo -> PyICU^? code

Heikki

• Progess
  • Working on ACL stuff
• Plan
  • More ACL
  • Switch to newer M2Crypto
  • Investigate SSL regressions