Question of the week: If our goal is to get people outside of OSAF using Chandler in Q1 2007, what should we be doing more of/less of?
0.7alpha3
Code freeze: tomorrow?
Notes
Question of the week:
Bear: add tasks, tasks and contacts allow the pim folks to latch on to the project -- trifecta! We're in the summer doldrums, we're sort of inefficient. Limit the big source code changes, focus on stability while we're in the summer doldrums. wx seems to be breaking things in the UI.
PJE: go faster!
Grant: more engineering dogfooders.
Katie: more testing/dogfooding of background sync
Travis: dogfooding sounds like a good suggestion, comment on what needs to be done
Worry about landing the tarball, will cause a few days of chaos, still one functional test
Python 2.43 upgrade landing -- testing on windows
Officially swapped the licenses to Apache 2.0 this afternoon
notices file
copyright dates -- preserve original copyright marker -- causes extra work -- keep for each file independently
Status
Katie
Progress
sent out emails to my network recruiting for cosmo and scooby positions, talked to suzette about hiring
tried dogfooding the trunk, ran into Bug:6081
chandler-dev summary
read dashboard spec, sat in on spec review
alpha2 got patched with a timeout
proposed that we live with disabling stamping of already shared items for alpha3
facilitating apps meetings while philippe is away
Plan
work with Jared on hosted service roadmap
propose qa irc office hours to get more bgsync testing 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.