Overall/Coordination
We have rough dates for beginning and ending implementation of milestone 0.5.03: May 2 to May 30. The end date may vary because milestone 0.5.03 will be driven by feature/task completion. After that we will integrate and fix bugs for probably a week then begin 0.5.04 for another four weeks of implementation. The current design process is covering both milestones. Beyond that we know we have more work for 0.6 goals but we aren't certain yet exactly what that will be -- planning continues.

Everybody is writing plenty of performance reviews. Did you know everybody is picking two peer reviewers plus their manager picks two peer reviews? Plus everybody reviews his or herself, his or her manager and all direct employees. That is at least 94 reviews by my count (not counting very new people), so if you're only writing six reviews you're under average and can be grateful. Right?

Design Team
Progress:
Many useful design meetings held so far. Some specifications (Sharing, recurrence, detail view) are already well under way. CVS has a place (/docs/specs) to check specs into now, several are incoming. Answering questions from Apps team about their current work and focus (e.g. in List One bug comments). Discussions on Item Collections.
Plans: Continue detailed work on specs and publish them via CVS. Work starting on defining 5 personas related to our existing use cases, as a tool for communicating and illustrating design issues and choices and workflows. Review bevelling with Jed. Plan sidebar cleanup for 0.6 with John. More Item Collections discussions.

Applications
Progress
: Constant progress fixing bugs on the "List One" of tasks, including: column header, calendar view displaying conflicting events, mouse handling, send button, committing changes in detail view. Bottoms-up estimate for time to complete this list is now in Philippe's hands.
Plans: Continue progress on List One and work with Sheila on specs for certain of those tasks and post-List-One features.

Services
Progress:
Most of the visible work lately is in planning although some bug fixes (account management, iCalendar import/export) have recently gotten done.
Plans: Each developer is working on detailed estimates for at least the 0.5.03 milestone if not beyond. Jeffrey to produce engineering spec for recurrence. General spec/design participation. Specific proposal for defining parcel Kinds in python code is well underway.
Other:
Lisa vacation: Apr 20-May 4; Brian to return from conference/vacation Apr. 13.

Repository
Progress
: Item cloud management and tracking fixes. Item Collection redesign/redefinition underway. Work to allow parcel Kinds to be defined in Python code is underway -- e.g. "headless items" or items without a view associated.
Plans: Ted in office next week, in-person design and architecture discussions. Continuing work on parcel definition changes and Item Collections (expect spec by end of month)

Server (Cosmo and Scooby)
Progress:
Proposed a code name for WebUI project: "Scooby". Jackrabbit integration work. WebUI improvements (e.g. refactoring, displaying login info). Tested Cosmo and Chandler interoperability and addressed issues that arose. Tested Jackrabbit compliance to WebDAV and communicated this to Jackrabbit developers. Established Cosmo mailing list. Coordinating with Chandler sharing developers on plans and dependencies. Bugzilla usage begun (Product=cosmo).
Plans: Work with Sheila on a planning page. Get TODO list published outside of CVS somehow (Bear + RSS?). Fix bugs in Bugzilla. Update docs. Use whatever license Sheila chooses. Install Cosmo on OSAF host for Chandler test/use. Work with Bear on build/test automation.

QA
Progress:
Design involvement ongoing; demoed SilkTest. Smoke tested build dated 20040411 and tested detail view changes.
Plans: Start writing test plans based on spec output. Ongoing: test each week's quality checkpoint build; devote 30% of time minimum to automated tests.

Build
Progress:
Weekly quality checkpoint builds -- which are not milestones -- are already under way. (The first two were called 0.5.01 and 0.5.02 although we'll be reserving those numbers for milestone builds from here on.) Fixes affecting "developer quality of life" (e.g. cygwin) are being finished and underway.
Plans:
Upgrade wxWidgets (skipping a version), Python and Twisted imports to newer versions -- all targetted for 0.5.03 milestone. Initiate automated build/test of Cosmo server.

IT:
Plans:
Interview candidates for OSAF-focused IT lead.

Community/Communications:
Progress:
Prepared for Educause Web presentation involving Mitch and Lisa.
Plans:
CSG meeting next week, Apr 20-21.

----

Small print: This status overview is not guaranteed to be either complete or accurate. Sources for this information include the owners for each of the above areas. If you find errors or omissions please respond publicly with addendums or corrections or process ideas -- or privately to me if you prefer. If you find this useful let me know because we can continue doing this on a somewhat regular basis if it's useful enough.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to