Apps meeting Tuesday January 24th 2006

Agenda

• Question du Jour
• 0.7
• OSU
• Misc
• People

Summary

• Plan : Make progress on 0.7 Architecture tasks
• Progress : Sprints were great though not long enough to reach success for everyone (working parcels)
• Problems : Need to make progress on 0.7 schedule

Actions

• All : get the 0.7 Architecture tasks moving ahead (see details in the minutes))
• Philippe : review 0.7 bugs per dev
• Philippe : create a Wiki page for Geek Talk subjects

Minutes

Question du Jour

What did you learn at last week sprint? Should we do this more often? Suggestions for next time?

• David : was time sharing with build crash so not super efficient. liked the community atmosphere
• Jeffrey : frustrated because didn't finish anything. would like days to be in a row.
• John : liked it. looked at Flickr and needed a lot of cleaning. good lessons to improve our framework.
• Aparna : having people to experiment was great. we should do this more often. not a lot of test cases done though...
• Reid : also frustrated because couldn't finish.
• Mimi : good session on data input / output. Paired dev/design is good.
• Alec : great time. nice to have intense sessions on something different.
• Philippe : Python is hackable. Open Source is great. Nice to see remote people all together (felt like "OSAF Developer's Conference"). Should do this on a regular basis (twice a year).

0.7

• New Wiki page to hold the Design Proposals
• There's quite a list of design issues being worked on on the Design List (see Mimi's summary). Please, get involved.
• Review of the Architecture task list:
  • Sheila : Search and Sort : need Design/UI work, Sheila to ask feedback from devs on what speced out
  • Alec : Hints : Alec to bring the discussion to the dev list
  • Jeffrey : Recurrence refactoring : discuss with Grant to check if things can move forward
  • John : CPIA Refactoring : John to finish doc then we'll brainstorm
  • Jed : Minical : Jed to discuss the issue on dev list
  • Philippe : Styles : Philippe to bring the issue on dev list
  • John / Alec : Trunk parent block : finish it
  • Philippe : Bidirectional references for Collection: add to table (Andi, Mimi, John, Katie)

OSU

See Ted's email.

We need to provide more ideas to Ted. Please add them to the thread.

Subjects should be longer term subjects, not 0.7 critical path, e.g.: instrumentation, command recording, security related issues, translitteration of shared items.

Misc

• Functional Tests : Aparna presented during the sprint. Should we do more. Problems writing them. We need to put some thoughts into it. Have an abstract API for it? Someone on the Apps team need to own that.
• Demo for the staff meeting : Alec on the repository editor
• SWIG testing : Robin working with Heikki and Bear on this.
• Kruegel talk on Thursday : Philippe to work on the room, etc...

People

Jed and John on Jury Duty. Bryan on vacation.

Internship : Markku making progress on Visa. Please send me your proposal for internship project ideas! Think about the "Google Summer of Code" project.

---

Status

Alec

• sprinted to make ajax-y repository viewer - got about halfway done, also refactored some code
• investigated Cheetah as a way to simplify the repsitory viewer and make it more reusable for the Doc gen code
• sprinted to make a calendar-view functional test
• cleaned up code and fixed bugs in QAUITestAppLib.py
• re-fixed Bug:2523
• Interviewed two candidates for the Cosmo/Scooby Java Manager position
• Spent some time investigating widget possibilities for "sections" in the table view

Bryan

• Your status here...

Philippe

• 0.7 work: triaged bugs, Dashboard design
• Participated to Sprints: almost done with an hCalendar parcel (possible demo Thursday if I get some snags out). Learnt lots of things in the process (very enlighting)
• Participated to a bunch of brainstorms and meetings on information flow
• Ad hoc meetings with remote people who were in house and overall enjoyed meeting everybody... :)
• Worked on OSAF budget

Jed

• Your status here...

Jeffrey (for the past 2 weeks)

• participated at length in Ars Technica forum on Chandler
• More vobject vcard work, accepted two patches from the community to make vcards and recurrence work better
• long "mailing list dynamics" emails
• planned and gave a facilitation talk
• recurrence next-steps writeup, talked with Morgen about sharing <-> recurrence interactions, emails to ietf-caldav about recurrence subsets
• sprints
• invitations email
• tray email
• submitted patch to dateutil, when it's accepted it should fix bug 4979

John

• Incorporated half of Bryan's comments to my documentation
• Modernized flickr at the sprints
• Attempt fix for Bug #4993: stack trace while running chandler.
• Clean up some global events in Chandler
• Enjoyed the OSAF party on Saturday

David

• released wx tarball 262-32; worked on 33
• participated in various Sprint Week activities
• helped resolve some tbox build issues
• coordinated various SWIG v1.3.27 update activities
• met with Philippe and Reid to plan some near-term wx tasks
• agreed to hold weekly wx-devt meetings on IRC at 10:15AM on Thursday

Reid

• Made tools/do_tests.sh easier to use at the sprints
• started a user feedback parcel with Jeffrey at the sprints
• looking into debugging Chandler (with emphasis on OS X)
  • ddd looks promising
  • ddd debugs C/C++ (using gdb) *and* Python
  • working on a wiki page: DebuggingWithDDD

Robin

• Worked on Bug #4432, update to SWIG v1.3.27. I corrected some SWIG bugs that impacted wxPython builds, as well as issues that Andi raised about PyICU and PyLucene, and have incorporated those fixes into my patch. Waiting for a green light from Heikki regarding m2crypto.
• Also investigated the new features of the upcoming SWIG 1.3.28 and found that there will probably be several compatibility issues to overcome, at least for wxPython. But there are potentially many gains in performance and higher quality generated code, etc. so it may be worth the pain.
• Finished the first pass of proofreading and submitting edits for the "wxPython in Action" book. We were very thorough so hopefully the time needed for the second pass will be minimal.
• Investigated, fixed or delegated several bugs raised on the wxPython-users and wx-dev mail lists.