r7 - 22 Feb 2006 - 04:28:24 - MorgenSagenYou are here: OSAF >  Journal Web  >  DevelopmentHome > DeveloperPlatformProject > PlatformMtg20060221

Platform Meeting 21 Feb 2006

agenda

  • Question of the week: Have you identified dependencies with Cosmo? Apps team?
  • 0.7 Planning
  • No meeting next week due to pycon

notes

  • Q: Have you identified dependencies with Cosmo? Apps team?
    • Heikki: version #s and milestone schedule (getting this ironed out helps manage dependencies)
    • Grant:
      • Free/busy work may or may not depend on cosmo.
      • apps team depends on free/busy, timezone
    • Ted: apps team depends on domain model -- scoped out in table at DeveloperPlatformProject
    • PJE: schema upgrade import/export may have some UI, not scoped yet
    • Bear: the move to cosmo 0.3 will have ripple effects, installers will have dependencies on upgrade plan
  • Linux distribution for 0.7
    • Heikki and Andi summarized the issues well, Heikki will reply to list with summarization
    • Bear and Heikki will update table at DeveloperPlatformProject with working plan of what is getting done when
  • Although timezone UI work is happening phase II, timezone support work is happening in phase I. Sheila agreed to move the timezone ui spec work to phase I.
  • Andi brought up the epydoc bug that prevents some of his api work from showing up (Bug#4702). Bear said that we'll schedule this and a twisted epydoc bug (Bug#4703) for the 0.7 release.
  • Sheila brought up her proposal for non-code release docs. Andi mentioned that as long as we don't have a smooth upgrade path to the milestones, we'll need to support 0.6 derivatives. Katie mentioned that the current stake in the ground is to support an upgrade path between milestones, and that she'll send the list of proposed requirements (buried in dev list thread) directly to design list.
  • PyCon prep
    • Katie will give a lightning talk with a demo of Chandler, and will load up her laptop to do the demo. Katie will demo extension parcels in addition to a bit of calendar. Grant will check in his EVDB parcel. Katie will probably demo off the trunk, not 0.6.1 (but will have both loaded).

status

Katie

  • Progress
  • Plan
    • Wrap up bugzilla components
    • Public osaf channel
    • Send out forms and peer review requests for review process
    • Writeup summary of collections meetings for list
    • Prepare lightning talk for PyCon

Andi

PJE

  • Progress
    • Released setuptools 0.6a10
    • Helped Bear & Heikki design the new tbox notification emails.
    • 4 days off
    • Implemented change request 5188 (__default_path__ item should be created when kind is created).
  • Plan
    • PyCon
    • Help Bear get setuptools 0.6a10 into the build
    • Wrap up the first draft of egg plugin support

Ted

  • Progress
    • replacement laptop ordered
    • committer policy draft posted
    • prototype of community projects list TedLeung20060215
    • DomainModelProject? page and initial draft of Domain Model project work
    • Schema upgrade thread
    • Collections meetings
  • Plan
    • i18n docs
    • PyCon

Grant

  • Progress
    • Demoed a simple app that automatically configures your incoming email, based only on the server hostname. (Source here).
    • Progressing on PyCon presentation; slides should be ready for upload today or tomorrow.
    • Got Chandler running on proposed new way of dealing with floating events.
    • 0.7 planning.

  • Plans
    • PyCon prep & attendance.

Heikki

  • Plans
    • silmut test framework stuff for cosmo
    • Chandler version numbers and milestone schedule

Morgen

  • Progress
    • Worked on the view merging unit test
    • Modified various dialogs to have a modeless option, so that functional tests can use them
  • Plan
    • Continue on the view merging tests
    • Continue developing 0.7 goals and spec
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r7 < r6 < r5 < r4 < r3 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.