r10 - 13 Jul 2007 - 10:44:12 - MimiYinYou are here: OSAF >  Journal Web  >  DevelopmentHome > DeveloperPlatformProject > PlatformMtg20060314

Chandler Platform Meeting 14 March 2006

Agenda

Notes

  • Question of the week
    • Why is it valuable to rotate meeting facilitation? Whoever is facilitating has control over what the topics are in the meeting -- might be useful to rotate this to make sure the meeting is useful for the team. As Jeffrey pointed out in his talk about meetings, people who occasionally facilitate meetings can then be helpful later in participating in meetings and making them effective.
    • Brian K, Bear, Ted are interested in facilitating
  • Making chandler lists more effective
    • Katie volunteered summarize chandler-dev list weekly
    • Bear suggested creating a new message/thread when you want to get the attention of new people
    • We could flag the summary line with [QA] or [PPD] to flag the attention of groups who are paying attention to multiple projects
    • Ted is looking at how we can avoid cross-posting
  • IRC chat about scenarios for website/wiki
  • Demos for Thursday? (No)
  • Core sprint week -- probably sometime in April
    • next one probably sometime in April
    • we'll do this 4 times a year
    • purpose: events that take advantage of high bandwidth communication, team building, core development on Chandler, Cosmo and Scooby
    • also may occasionally do self-assigned project work, sprints designed to bring in non-staff members, but this is not the only focus

Status

Katie

  • Progress
  • Plan
    • Help get John Townsend set up (new Cosmo/Scooby person)
    • Stamping design session
    • Long overdue collections summary from weeks ago
    • Frame "dump and reload" requirements/issues for design list
    • Jump into list discussions about sharing format and CalDAV
    • Get phases/milestones plan ironed out

Ted

  • Progress
    • ETech (report forthcoming, generic comments at http://www.sauria.com/blog/2006/03/12#1490
    • Reviews
  • Plan
    • Self review
    • Stamping issues
    • Get portal project rolling, Info Usage Scenarios IRC this Wednesday
    • Mailing list renaming

Brian K

  • Progress
    • Finishing bug:4940 - cosmo should allow properties to be set with MKCALENDAR
    • Finishing bug:5134 - MKCALENDAR needs to support setting of timezone
    • Sent Pycon Report
    • Completed 4 Reviews including self review
    • Researched BitCon? which has been resheduled to June 15th in Taipei
  • Plan
    • Finish off Cosmo tasks including bug:4940 and bug:5134
    • Catch up on .7 spec reading
    • Review .7 plan for milestone deliverables

PJE

  • Progress
    • Implemented a new installation conflict resolution mechanism for setuptools, enhancing compatibility with system packaging tools like RPM, Debian, etc.
    • Implemented proof-of-concept double-click install for .egg files on Windows
    • Checked in first-cut of egg parcel support; no docs or non-trivial tests yet
    • Worked w/bear on build system issues installing/using eggs
  • Plan
    • Egg parcel tests, sample egg parcels, docs

Morgen

  • Progress
    • Finished reviews
    • Went through my backlog of bugs and responded to them.
    • Discussed Sharing Format
    • Added WSGI interface to our (twisted) webserver; also got cherrypy to work in there too
    • Helped a few non-OSAF users on IRC with their calendar publishing issues -- interestingly two different people both wanted the same (until recently, disabled) feature: publishing a monolithic .ics file to a WebDAV server, which I renabled in the trunk.
  • Plan
    • Focus on background sync
    • Continue on the view merging tests
    • Fix a bug in Import/Export framework - iCalendar uses the wrong signature
    • Look at removing .setup( ) from the collection code

Andi

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r10 < r9 < r8 < r7 < r6 | 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.