services, dev platform and repository mtg 16 Aug 2005
agenda
0.6 topics
recurrence, timezone
sharing, zanshin
sets, collections
i18n
certs, ssl, tls
dev platform
runtime performance, memory footprint
m5 milestone next week
notes
Set integration: the app comes up now on the branch (well, most of the time). ItemCollection has been replaced with Collection variants. Notification work remains, which might be a bit tricky. Its likely that we'll end up pushing out the milestone, as we'll want a bit of a buffer between the merge of the branch back to the trunk and the milestone. The developers working on the branch will make sure that unit tests and AcceptanceTests pass before merging the branch back into the trunk.
Documentation: Jeffrey noted that it would be helpful to have high level documentation about where to find what in Chandler, Katie noted that we intended to do a pass at documentation at the end of 0.6. (Dev platform/extensibility task)
Accessibility: Heikki described 3 accessibility guidelines (he already sent an email about this to the dev list). One of them was about not using color as the only means to convey information. We discussed the example of color used in overlays. Mimi worked with Bear to choose colors that work for people with colorblindness. Bear mentioned that allowing the user to pick custom colors can also help. Heikki mentioned that reasonable defaults and a way to customize colors are listed in federal accessibility requirements. (Such requirements may eventually apply to us, especially for universitites who use Chandler).
Meeting effectiveness: We had a discussion about whether or not it was a good thing for the meeting to focus on status reports. Katie said she would send out the link earlier in the week, so that people could get the status up earlier and people could review others' status before the meeting. Phillip noted that he found the earlier dev platform meetings more useful because we discussed issues and collaborated on problems (more useful than status). Jeffrey and Brian noted that it was helpful to hear status to know what was going on in the project, and others noted that sometimes it prompted useful questions and discussions.
status
Katie
Progress
We decided to create a new set branch (essentially pulling the repository from the trunk). Ted, John, Morgen, Alec and others are getting work done in the branch, including Trash and Sharing.
We decided to remove all parcel xml, Phillip is coordinating from here. Alec and Phillip ran with a proposal to make it easier to create block instances (and other cases where one wants to create a lot of instances in parcels). We're waiting for some of this to land after we merge the set branch back into the trunk.
Met with Ted, Phillip and Morgen to talk about the content model, the flattening project, and APIs. Phillip will write up more about that in a bit.
Met with Brian Kirsch and Sheila to talk about i18n strategy, Brian to write a draft.
0.7/0.8 planning: looks like focus is going to be "plausible dashboard".
Plan
Diagrams of the current content model to facilitate discussions with Mimi and Sheila. See Lisa's DiagrammingContentModels.
Created I18nLoader code logic and migrated to i18nmanager
Migrated image and html resources out of application
Updated locale logic to leverage i18nmanager
Updated Utility.py to use unicode filesystem pathing
Started migrating CPIA code to use OSAFMessageFactory?
Augmented all Chandler Dialog code to work with LocalizableStrings?
Changed all code calling dialogs to leverage LocalizableString?
All resource retrieval in Chandler now going through i18nmanager
Worked with Heikki in integrating new SSL code with mail and mail dialogs
* Plan
i18n documentation updates to reflect additions and changes to i18n architecture
Create the i18n roadmap wiki page based on discussions Friday with Sheila and Katie
Work with Andi to move displayName to a Text alias and condense description, examples, and issues
Continue migration code base to leverage OSAFMessageFactory? for translations
PTO August 17 and Floating Holiday August 19th
Heikki
Progress
New SSL certificate dialogs in, some other related polish
Put up simple accessibility template and notified Mimi as well. Some new rules of thumb besides keyboard access: no blinking, nothing should be distinguished by color only.
Gave ACL preso, planning and working on impl.
Plan
Get some new ACL code checked in
Checkin the beginnings of ACL design doc
Look at problems with testing SSL connections which can put up multiple cert dialogs