r2 - 08 Mar 2004 - 11:43:00 - DuckySherwoodYou are here: OSAF > Journal Web > MeetingNotes > ZeroPointFourPlanningMeetingNotes20040304
Attendees
MitchKapor, ChaoLam, HeikkiToivonen, KatieCappsParlante, MitchellBakerDate: March 4
Purpose
Using the baseline plan developed by the design group for .4 features (see http://wiki.osafoundation.org/twiki/bin/view/Chandler/ZeroPointFourPlanning), and the ongoing planning within the individual working groups, we tried to identify issues which felt both urgent and important, insofar as:- (1) resolving it involves significant intergroup coordination,
- (2) the issue identifies large amount of work which could have schedule impact, or
- (3) issue affects the critical path, might block lotd of other work, etc.
Decisions and Next Actions
| ISSUE | NEXT ACTION |
|---|---|
| We’d like .4 to include a first pass at access control, authentication, sharing. There will be work required in the Apps Working Group, which has not been planned for yet, to support these new capabilities as well as all of the usual inter-group coordination with RWG, AWG and the Design Working Group. Among issues which must be coordinated are selection of sharing transport and methods of user discovery. | Mitch to check with Andi and Repository Working Group (RWG) at Monday RWG meeting regarding estimating a schedule. |
| A decision needs to be made very early in the .4 process about data model changes. Ted owns this issue. Andi, John, and Morgen should have input. | We will discuss next steps at Monday’s RWG meeting. |
| Possible changes to the threading model will be driven by query work and by apps use of query and could ripple down to possible repository work. | Katie to confer with Ted and John to create a process (owned by Katie) to resolve. |
| Caplets, etc. | Mitch and Katie to meet early next week. Mitch to give Katie brain dump so Katie can write up a proposal covering the following: what is a caplet, relation of caplets and parcels, content model and parcel refactoring for 3rd party caplet support; Registration and discovery of kinds by parcels |
| Setting priorities for content model work in .4. | Katie and Brian to meet to come up with proposed owner(s) and plan. There is a list which lives on the project page which will be used as the basis for the work |
| Rationalizing (user-)collections AKA playlists, smart playlists, and views and the basic UI approach to same. Mitch owns this. Mimi and John will partiicpate/review. | Mitch to come back early next week with a plan to sort this out. |
| HTML editor | We believe the wxWidget which wraps the Mozilla engine supports editing. Heikki to do investigation of whether this is reality and determine wehther we can commit to the base approach to entering and rendering HTML or not. He will create wiki page. Our wxDeveloper, when hired, will have this issue on his/her plate. |
| We decided that work on application registration and a talkback module are not in scope for .4, nor is performance tuning of download footprint (this will begin to happen in .5). | None. |
| Performance tuning, e.g., Chandler slow start, memory footprint, stability and Internationalization. | We will have discussion at management committee next week or week after at latest which will start process as to what we do or don’t do in .4. |
Apps
- deferred bugs - do them? clean up and refactoring (this week)
- .4 UI design & implementation (needs DWG involvement)
- a plan for email
- other wxWindows goals
Repository
- Queries
- Access Control
- PKI and authentication
- Sharing
- Data Model
Community
- Community group itself has projects (oops - can't read my notes) and will work with other groups to help them set their community goals.
- Expectation is to focus on community involvement at repository level.
Design and Product Management
- sample data
- instant messaging
- Documentation for the release (have a plan in the first month)
- Visual Design goas for .4
- end user notification
Release Management and QA
- TK (to come)
Log In
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.
See list of page contributors for attributions.