[Chandler-dev] [Proposal] Criteria for fixing 1.0 Desktop issues

Last week we met to discuss Post 1.0 priorities. Stay tuned on our  
blog for more detailed posts on planning. In the meantime, here's a  
brief summary of where we're headed. Going forward, we are shifting  
developer focus to:

1. iPhone apps and building out UI for configuring and receiving  
notifications from Chandler Hub.

2. Desktop re-architecture project to address performance issues as  
well as to improve overall stability, testability and ease of  
maintenance.

3. Building developer community.

We will continue to support the existing 1.0 Desktop on an as-needed  
basis, but our primary goal for the Desktop is to shift project  
momentum to the re-architected Desktop as soon as possible.

We anticipate rolling monthly releases to fix critical bugs (e.g.  
Chandler won't start, I can't get my data into Chandler, I can't sync  
to Chandler Hub, etc) as well as addressing frequently reported  
usability issues (e.g. What's the Tools menu for? Looks scary.)

Proposed criteria for nominating issues as "Must Fix" for 1.0 Desktop:

1. Issue has a proven history of being a problem. This means many  
users reporting the problem over a prolonged period of time. (Let's  
say half a dozen reports over a period of at least 1 month? The  
significance of the # of reports will change as the size of our user  
population changes.)

2. Issue is a blocker for users to get started with Chandler (e.g.  
App won't download / start. Can't get my data into the app. Can't  
share.)

3. Issue has a clearly spec'd out, low-risk fix, where low-risk means  
fix requires minimal testing and very unlikely to introduce new bugs.  
As a default, let's say issue is fixable with 1/2 day's work. (With  
the caveat that this will vary depending on severity of the problem.)

To clarify, these are criteria for nominating issues we "Must Fix".  
Meaning issues that meet these criteria justify rolling a new  
release. Once we have a "Must Fix" issue, I imagine that other  
smaller fixes will tag along, assuming they are trivial to fix and  
don't require a lot of testing.

Caveat: This is our first try at nailing down criteria for nominating  
"Must Fix" bugs. We will be revisiting the viability of this proposal  
on a regular basis and adjust accordingly.

****

Given these 3 criteria, we have nominated and approved our first 1.0  
Desktop issue: Users have trouble setting up Chandler IMAP folders. I  
will sending out a summary of the proposal for the fix.

Mimi

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

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