r14 - 27 Mar 2007 - 14:29:05 - PhilippeBossutYou are here: OSAF >  Journal Web  >  DevelopmentHome > ApplicationProject > AppsMeeting20060202

Apps meeting Thursday February 2nd 2006

Agenda

  • Question du Jour
  • 0.7 Planning and Progress
  • Platform team 0.7 projects
  • Misc
  • People

Summary

  • Progress :
    • Lots of progress on the Design front. Things are getting clearer for free/busy, invitation workflow. More work on Dashboard needed.
    • Bug triaging moving forward, more to do
    • 0.6.1 bug fixes on target
  • Plan :
    • Continue progress on 0.7 Architecture tasks
    • Review remaining 0.7 bugs, prioritize
    • Start SWAGging bugs
    • Create a Wiki page for "Geek Talk: subjects for Apps meeting (Philippe)

Minutes

Question du Jour

What's the one thing we should be doing based on the 0.6 debriefing?

  • David : Better identified milestone dates, cleaner milestone stabilization process.
  • Sheila : Better integration with Cosmo and handling of the dependencies.
  • John : More functional tests.
  • Reid : Have one big single design doc or may be an up-to-date living user manual.
  • Alec : More frequent releases.
  • Katie : We should have an IRC channel for meetings.
  • Philippe : I need to write this code so that the "graph" gets updated automatically and be more precise.

0.7

Progress

Progress last week on the following :

  • Triage on going : Using an expanded set of tags for the Whiteboard Status field, triaged John, David and part of Alec's bugs. Goal is to narrow the bug list to what's required to support tenet 3 (dogfood) and identify the one that support tenet 1 (scheduling) and 2 (dashboard).
  • Design : Lots of design meetings, threads and docs. Hard to follow all of it. See individual status here under for more details on design activities.
  • Architecture tasks : Hints notification almost done. Need more progress on the other identified last week.
  • Tenets : Great presentation by Sheila this morning. Concerns on email and some not in 0.7 features : we may want to start planning those earlier for 0.8 (before we're done with 0.7).

Issues :

  • Milestone dates : no datee set yet, we feel it's better to get data rather than throwing dates. Clearly, we need to work forward to get to dates soon! (breaking down in tasks, SWAG, etc...). Philippe to focus on this.
  • Tests and QA : We all want more frequent releases which means more stable code more often so we need ways to test and maintain that. We (devs) all need to write more tests (unit and functional) to support that goal.
  • Implementation Design : We need to start talking about this (iMIP for instance). Philippe to call for dev meetings on these.

New Areas and Components

Katie and Philippe have been working on a first draft here.

What needs to be added? We also need to find owners for components but we intentionally didn't discuss this today. New entries proposed :

  • Calendar : invitation
  • Calendar : free busy
  • Dashboard
  • Search
  • "Communicating items" (?)

Platform team 0.7 projects

Katie gave us an update on the Platform team plan :

  • PJE: Python eggs (mechanism for distribution)
  • PJE: Schema evolution
  • Ted: Domain model improvements (including for Dashboard)
  • Brian: i18n, accept *.po
  • Andi: moving collection to the repo, sorting and searching, merge (for sharing)
  • notification, need a review of collections in the side bar, John to call for a meeting with Andi and Ted
  • Morgen: sharing, autosync in the background
  • Grant: email, calendaring services
  • Bear: Linux distro support
  • Heikki: talkback

See the Platform team page for more details.

Apps team needs to identify which of these projects will have consequences on Apps owned components (UI required, things to change, etc...

Misc

Didn't have time to cover that during the meeting, listed here for as a reminder :

  • Governance: moving irc to freenode soon
  • Demo for the staff meeting?

People

Internship : Philippe created a page to held on going plan, updated list of subjects with Ted, classified subjects by size.


Status

Alec

  • Lots of meetings - interesting and important, but they take time smile
  • added new triage enum and column in the UI, made Generate Items do different triage status
  • reorganize Table/grid widget, and add some abstractions for sections and other arbitrary table transformations
  • implemented strawman sections implementation
  • PTO after staff meeting thursday and all day friday

Bryan

  • Finished the TrunkParentBlock renaming that John started.
  • Refactored the detail-view-building mechanism to make TrunkSubtree (now BranchSubtree) a schema.Annotation on Kind.
  • Working on using indexes for email autocompletion; this exposed a couple of existing bugs that slowed me a bit.
  • Met with Mimi, Sheila, & Philippe re 0.7 detail view requirements; working up a technical-level list of tasks.
  • Fixed (pending review) a 0.6.1 bug 4987, "Detail View can't deal with certain dates".

Philippe

  • Participated to meetings and threads on various 0.7 feature work (DV, Dashboard, free/busy)
  • Bug Council duties : 0.6.1 and untargetted bugs
  • 0.7 bugs triaging
  • 0.7 planning tasks with Katie and Sheila
  • Worked on summer interns : updated list of subjects, plan, met with Lori

Jed

  • Your status here...

Jeffrey

  • Fixed a variety of timezone issues in Chandler and vobject
  • Helped the PyCon organizer fix his ICS files
  • Caught up on email
  • Helped diagnose dogfood share/import issues for Esther and other folks

John

  • 3 days of Jury Duty
  • Refactored mainblocks.py so I can mock up different options for sections in the summary view
  • Helped Andi track down a problem he was having adding an items to a new collection in the Sidebar that doesn't show up.
  • Cleaned up more cruft in Flickr
  • Fixed bug #5091: unable to launch chandler on rev 9247
  • Alecf, Grant and David and I resolved the "hints" design proposal. We also discussed the refactoring necessary for how events are dispatched.
  • Refactored some old event dispatching code
  • Checked in first pass at table sorting. Several problems remain to be solved: selections aren't maintained. Comparison routines don't correctly handle dates and lists don't properly compare with lists or individual items. Finally the sorts aren't stable.
  • Fix a bunch of files with incorrect end of lines.

David

  • worked on Chandler v0.7 wx task planning
  • released wx tarballs 262-33 and -34
    • created a "tarball revision history" wiki page
  • worked on 2-3 wx bugs
  • worked on SWIG v1.3.27 update
  • made a focus-related fix to scripting
  • suffered through some serious Mac laptop problems
    • kernel panics, lost wireless servce, cannot wake from sleep, etc.
  • lots of meetings

Reid

  • More investigation of gdb
    • managed to integrate Robin's gdb scripts
    • can get a Python stack frame while in gdb (but it's slow)
  • Reading a lot of email, esp on the design list
  • Learning more about the ins and outs of wx
    • bought the book "Cross-Platform GUI Programming with wxWidgets"
    • also go "The Official Gnome 2 Developer's Guide"
      • want to learn more about Gtk
  • tried making a wx change, didn't see result in build
    • learned more about builds and how they work
    • Robin pointed out that builds may not all update the chandler/{release,debug} directories; is this true?
  • more notes are on my Chandler work blog

Robin

  • Thorough testing of wxPython built with SWIG 1.3.27.
  • Also added #ifdef's to the code to allow wxPython to still be built with 1.3.24, and also with the upcoming 1.3.28 to help make transitioning again in the future easier.
  • Continued tracking and testing SWIG 1.3.28 developments.
  • Provided a patch, original source, and solution files of SWIG 1.3.27 to David and Heikki.
  • Tracked down the source of a very tricky layout bug with John.
  • Added wxPython wrappers for wxToolbook and wxTreebook.
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r14 < r13 < r12 < r11 < r10 | 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.