Highlights

• Scooby has reached “zarro boogs” and code freeze and in QA for release of 0.1.
• Cosmo has 10 P1 and P2 bugs to fix before release of 0.3.
• Chandler team is at PyCon this week (or enough so that the office feels empty, anyway)

The detailed report can be found on the wiki here

The latest status overview, with quick high points from every project and overall highlights, can be found here.

A bit of a change for status overviews: we experimented with collaboratively creating a status Wiki page. Some are on vacation right now so not all sections are filled in but that’s OK, I am already getting the sense that this can work. Rather than re-post here I’ll simply link to the Wiki page.

Dec 20 OSAF Status Overview

Apologies for the late and less-structured status overview this week. I’ll confine this to what people sent me or posted on the Wiki for recent status.

• Operations meeting minutes
• Engineering Meeting minutes (milestone and release planning)
• Design meeting notes
• QA Status
• Applications Team meeting minutes
• Services and Dev Platform meeting minutes
• Cosmo: “0.2.4 is *just* about ready to tag and roll. there’s only remaining issue: a KEI internal project needs a signup operation added to CMP. i expect that to be done and 0.2.4 to be handed off to QA by the end of day monday.” — BCM
• Scooby:

From Bobby Rullo, Scooby progress:

• removal of events is now asychronous
• localization framework in place
• button drawing client side library started
• client keeps server side session alive by “pinging” every time the user does something on the client side
• Event detail area moved to the bottom of the page
• Resizable area for the all day events started - the same resizable widget will be used for the sidebar later.
• Started work on “all day” support
• Started work on caldav4j

Scooby plans

• finish all day support, as well as support for different event types (all day, any time, point in time)
• drop LocalScoobyService, add initial support for Cosmo instead

IT Status from Jared

• Progress: Full NMAP reconciliation complete. LPFI community technology selected. VPN plan complete, prototype proceeding. KEI mailman instance created. OSAF QA intern set-up.
• Plans: Rework cosmo-demo for new Java 1.5 requirements. Build new colo box for LPFI web site hosting. Close KEI sysadmin hire by mid-December. Review bandwidth shaping progress.
• Personnel: Hire KEI sysadmin and OSAF IT Intern. Jared and Chris have some late December vacation plans.

Highlights

• Chandler milestone 0.5.m7 released. Bug trending towards 0.6 release.
• Cosmo 0.2.3 released (bug and perf fix).

Design

• Progress: Lots of public design discussions and continued work on Nutshell documentation. Scooby design meeting.
• Personnel: Mimi on vacation soon.

Applications

• Progress : Very good bug trend, 21 blocking bugs remaining
• Plan : Focus on blocking bugs, get to zero before ThanksGiving
• Problems : Documentation tasks haven’t really started. We may have to hold the release (2 weeks after branching) if necessary

Services and Dev Platform

• Progress: As usual: bug fixes and performance work
• Plans: Start to tail off performance work with more of an eye to stability. Start documentation writing.

Build and QA

• Progress: Tested milestone 0.5.m7 build on Mac and Linux. Collaborative QA session on IRC for verifying resolved bugs. CATS code review. Daily bug councils.
• Plans: Review non-code release items. Hiring progress.
• Personnel: QA intern Dan Steinicke starts on 11/28

Cosmo and Scooby

• Progress: Cosmo 0.2.3 bug-fix release. CalDAV REPORT implementation progress in 0.3 trunk. Scooby spec writing and work on asynchronous events.
• Plans: Cosmo scalability test writing. Scooby: new design element coding (sidebar, new detail view, tickets UI)

IT

• Progress: Server backup enhancements project complete. Demo broadcast project complete. Silk machine for QA project complete.
• Plans: Continue hiring IT person. Finish VPN plan. KEI time tracking tool work.

Community

• Plans: ApacheCon Dec 11-14: presentation on Cosmo to prepare. Next CSG/WAC meeting first week in January.

Highlights

• Chandler: 202 bugs targetted for 0.6. 10 P1 bugs, 38 P2 bugs.
• Cosmo: 0.2.2 bug fix release in the works — fixes to make dogfooding work.

Applications

• Progress : Bug trend encouraging. Total Apps (P1+P2+P3) under the 100 bar for the first time!
• Plan : Bugs, bugs, bugs…
• Problems : Process perceived as too heavy in some cases. We clarified the “wiggle room” cases.

Services and Dev Platform

• Progress: Bug fixes and PyCon proposals
• Plans: More bug fixes and review recurrence test cases.
• Personnel: Lisa at IETF next week.

QA and Build

• Progress: Functional tests against the checkpoint (10/31) build. IRC bug verification session.
• Plans: Review last-minute design changes in 0.6 and triage P3 bugs.
• Personnel: Interviewing candidates.

Cosmo and Scooby

• Progress: Week-to-week navigation in Scooby calendar view. Some timezone and build work.
• Plans: Solve timezone and build problems in Scooby. Do a 0.2.2 release of Cosmo (a second bug-fix release of 0.2) to solve problems for FoxMarks and cosmo demo server.

IT

• Progress: Halua (cosmo-demo) suddenly unstable; top priority to fix. Now stabilized. Remote management installed at colo; big improvement in manageability. Office bandwidth shaping test servers OS installed.
• Plans: Memory for lots of QA machines. Backups rotation system. Desktop/laptop backups proposal. Office bandwidth shaping prototype stalled while contractor unavailable.
• Personnel: Open positions for KEI sysadmin and OSAF IT intern.

Community

• Progress: Plan to refactor main Web site (move many pages to Wiki)
• Plans: Will host CalConnect HTTP+ Auth meeting in January. Chandler 0.6 release landing page work. IRC office hour this week: QA bug verification.

We’re looking for somebody who has expertise in developing network applications for Palms. The initial goal is to pick somebody’s brains over the difficulty of various calendar related projects that OSAF might consider. Please send mail to lisa@osafoundation.org if you’re this person or can recommend somebody who might be willing to have a couple conversations.

We’ve been debating whether we might expect an increase in volunteer contributions to Chandler once we ship 0.6 with potentially usable calendaring, or perhaps once we do 0.7 which is likely to allow more solid parcel development as well improving calendaring. We threw around some examples, then I thought it might be interesting to actually get a longer list of examples and data about them — an ad-hoc survey of when volunteers make significant contributions to Open Source software.

The survey has only two questions, one for OS project maintainers and one for OS project volunteers, but there was a fair bit of commentary from the people I pinged so far, so I put it into a Wiki page. If you’d like to add more projects or volunteer data, add your own section and lines to the appropriate tables, just by editing the Wiki page.

I probably won’t say much about the results because it isn’t very scientific but I thought people might enjoy.

Highlights

• Chandler: Milestone 6 released, which is feature complete for 0.6 (Scorecard). 210 bugs targetted for final release.

Design

• Progress: Beginning specs for 0.7 (Free-busy viewing first draft, thoughts on markup bar and table cleanup), images for vision and design docs/presentations
• Plans: More spec work, more ACL, triage and free-busy design work

Application

• Plan : Continue making progress on 0.6 bugs
• Progress : Going toward zero, glide path (fix rate - find rate) continue to be good
• Problems : Unclear how we can declare perf bugs “fixed”, need clearer guidelines

Services and Dev Platform

• Progress: Performance: any user action when a large calendar is loaded is much faster. E.g. switching a view.
• Plans: Work on 64 bugs targetted to 0.6

Build and QA

• Progress: Tinderbox perf info — many improvements (still ongoing)
• Plans: Fix build bugs in 0.6 list.

Cosmo and Scooby

• Progress: Week view now has viewing, saving and deleting events from the server. Cosmo 0.3 begun with some bug fixes.
• Plans: Authentication system, multiple user support work. Navigation between weeks. Minical. Recurrence. Make build system more friendly. Cosmo 0.3 feature development.

IT

• Progress: pushed off Bugzilla enhancement projects. VNC server for remote demo viewing been tested. Installed KVM at ISC.
• Plans:
• Personnel: Hiring junior helpdesk person

Community

• Progress: Educause panel and demo last week showed Chandler subscribing to calendars on Cosmo, RPI and Oracle servers. Chandler branding work progress (chose icon).
• Plans: Refactor OSAF Web site (move some pages to wiki, remove others, or update). Making PyCon presentation proposals by Oct 31.

Last week I was at Educause for a couple days, part of a panel o CalDAV implementors. I demonstrated Chandler, and indirectly Cosmo too, to show the university IT audience that CalDAV is real and gaining adoption. François Perrault of Oracle did the first demo, showing Outlook with Oracle’s connected installed client-side, putting a calendar onto the Oracle server (not using CalDAV). But then he showed Lightning could pull down that calendar and view it using CalDAV, and add/change events.

For my part of the demo, I brought up Chandler (m6) with a calendar that had previously been pulled from a Cosmo (0.2.1) server and explained this. Then I subscribed to François’s calendar on an Oracle server, and it showed up in a different colour. Finally I subscribed to a third calendar on an RPI version of UW Calendar, adding a third set of events displaying along with the first two calendars. Except for a mysterious glitch where subscribing to the Oracle calendar didn’t work the first or second attempt but did work on the third attempt, it all went rather well.