[Chandler-dev] [Proposal] List consolidation

OSAF is now in in a phase of the project with a smaller staff and with a 
need to move quickly and be conservative with our resources. To be more 
focused, my goal is to work as *one* team during this phase, no longer 
thinking of ourselves as separate product, desktop, server, qa, and 
management teams.

We've ended all existing regular meetings, and now have one daily 
meeting with all 10 staff members. We're currently doing this on the 
phone while we get our footing, but may eventually transition to IRC.

I'd like to move our work back to the lists -- they've gone a bit quiet 
since the transition announcement.

At the daily meeting we discussed having fewer lists where we conduct 
daily work. Below is a proposal.

Goals:
- Integrate design and engineering discussions
- Use the same space for "chandler project" discussions, ranging from 
product schedule to design discussions to public strategy discussions
- Keep a separate space for people who are interested in the server but 
not the rest of the project
- Only maintain one list for "core" members to discuss strategy and 
organizational business, including relationships with individual people 
and organizations that might not be appropriate to be public. Note that 
this list would include project members who are not staff members. (As 
always, we want a path to that status for people who have never been 
staff members but grow their role into being key project contributors).

The Proposal: