services, repository and dev platform meeting 13 Dec 2005

agenda

• Question of the week:
  • 0.7 platform tenets?
• 0.6 endgame
  • dev docs (ZeroPointSixDocumentation)
  • non-code deliverables (http://chandler.osafoundation.org)
• 0.7 planning
  • BugzillaTracking
  • ZeroPointSevenArchitecture
  • roadmap

platform tenets

For 0.6 release, we had a few "tenets" for the release. We used these tenets to frame decisions about the release, from features that got dropped early on to prioritizing bugs at the end.

The "developer platform" tenet was:

• A python programmer new to the project should be able to develop a Flickr-like parcel without someone from OSAF in the room.

The complete list of tenets: http://wiki.osafoundation.org/bin/view/Projects/ZeroPointSixPlanning

We don't yet have a well formed "tenet" for developer platform/infrastructure work for the 0.7 release. We do have a pretty good idea of projects that we should work on (not a final or complete list, just to give the overall picture):

• PJE: schema upgrade, eggs, cpia refactoring help, maybe undo framework
• Grant: recurrence refactoring, free busy support, CalDAV interop work
• Morgen: sharing refactoring, background sync, freebusy/invitations, maybe wsgi
• Brian: email infrastructure, i18n
• Andi: move collections "below the line", performance, revisit sorted indexes, merge work
• Ted: domain model refactoring, community work
• Bear: release packaging, maybe linux distro work
• Heikki: performance, maybe talkback, security plan, accessibility plan

Philippe has started a list of projects here: http://wiki.osafoundation.org/bin/view/Projects/ZeroPointSevenArchitecture

Some of the work above supports the tenets discussed on the design list (scheduling, dashboard). It would be good to have a tenet specific to our developer platform goals. Ted and I talked about something around clear/clean APIs, but don't have a crisp proposal. It would be great if we could frame it in terms of what a developer would be able to do with Chandler.

notes

0.7 platform tenets?

• A developer should be able to learn and use Chandler APIs in a modular fashion, referring only to a component's dependencies and not the components that depend upon it.
  • "component" ==> "compact, conceptually cohesive units that are able to be separately developed, distributed, and used". Together, these concepts span a lot of the proposed platform-relevant work, including domain model and API refactorings, eggs, moving collections "below the line", schema evolution, etc.
• i18n goal: integrate with python eggs in a modular way, allow modular translations. Swig locale info. Sample translation (French or Spanish). Allow a translation of any of the supported languages.
• email: have a written plan for how we'll deal with imap folders. Answer questions that restrict what we are going to do. (probably related to dashboard goals)
• long running chandler
  • schema upgrade
  • out of control memory usage
• Make it easier to write a parcel that will actually work
• Anything that comes into Chandler can be found by full text search. This implies some UI for search. (Search of non-Lob attributes is supported in 0.6, btw)
• What is the priority of the platform tenet, relative to the other tenets?

Decision about platform tenets:

• The first one listed (modular, api) resonates. Several of the others will probably show up, either as goals that help support the other tenets, or as per-project goals. We'll take the discussion to the list. (Katie will kick it off, but perhaps after holidays).

Bugzilla, wiki for project task tracking?

• Most folks are +1 on using bugzilla
• One -1 on bugzilla (but not a veto)
• One rather strong -1 on both bugzilla and wiki

Decision about project task tracking:

• We'll move to tracking most things in bugzilla
• We'll track repository work, and perhaps some other platform work in the wiki (public goals)

status

Katie

• Progress
  • offsite with ops team (discussed 'crazy ideas', open source governance, and other issues)
  • architecture doc draft
  • brainstormed scripting with ted (KatieParlante20051207)
  • meeting with john, philippe and mitch about cpia goals
  • meeting with ted, mimi, sheila, lisa about open source design decision making
• Plan
  • wrap up architecture doc
  • review other dev docs
  • thursday brainstorm (organized by mimi)
  • custom grid swag brainstorm (to support cpia table)

Brian K.

• Progress
  • Found main Cosmo memory leak in non-released jackrabbit resource and patched
• Plan
  • Continue memory leak and performance profiling in Cosmo
  • Setting up jrockit instance on qacosmo for testing

Jeffrey

• Progress
  • Updated recurrence and iCalendar specs
  • Reviewed documents
  • Talked about 0.7 plans (recurrence, Jabber and email, adding useful tools for working with wx)
  • Talked to Dan Steinicke about writing more tests
  • Moved towards putting vobject on svn.osafoundation.org, now that we're using Subversion
• Plan
  • Get vCard 3.0 working in vobject, clean up and refine vobject
  • Write up ideas and plans about recurrence in 0.7

PJE

• Progress
  • Checked in the final (modulo any review comments) versions of the Parcel Developer's Guide to the Chandler Schema API and the guide to Creating Startup and Background Tasks in Chandler
  • Build sheriff discussions, preliminary automation discussions w/Bear
  • More attempts to debug intermittent TestStartups failures
• Plan
  • Clean up and reorganize the old schema_api.txt doc to focus on internals and repository interface
  • Draft proposal for "tinderbox failure tracking" automation
  • Misc. schema API cleanups on the trunk (rename Role to Descriptor, remove default null view arguments, incorporate new guide doc into unit tests)
  • Implement --single-version-externally-managed option for setuptools install so that Debian management will allow Python eggs as Debian-installed system packages
  • Support building shared libraries in setup.py (so PyICU can be distributed as an egg)

Morgen

• Progress
  • Wrote instructions for rolling your own sharing Format class
• Plan
  • Add instructions for implementing new sharing Conduits
  • Start fixing post-0.6 bugs in the trunk

Grant

* Progress

• • 4824 Transformation error trying to sync a subscribed (.ics) calendar.
  • 3899 zanshin documentation improvements.
  • Ongoing testing of Chandler sharing with cosmo 0.2.x.
  • Updated 0.6 TimeZone^? spec to reflect changes.
  • Experimented with integrating Chandler with Mac OS X 10.4 Sync Services, as a route to being able to sync Chandler with mobile devices.
  • Review of others' 0.6 docs.

• Plan
  • Finish up Sync Services prototype.
  • PTO Dec 12 � 14.