community design participation

There have been a bunch of working decisions made by OSAF, but they have 
not yet been compiled into a single structured document. The web site, my 
weblog, and posts by me, Andy, and other OSAF staff in this list and in the 
dev list all contain many individual pieces. It's obviously much too 
unwieldy, incomplete, unworkable, and even incoherent as is. A working 
decision is just that -- something we think we're going to do and the 
reasons why. Some decisions will be easy to change, others not at all, 
depending on how central they are.

We have the beginning of a plan to address this and some related issues by 
creating a topically organized wiki as a collaborative document to 
represent the current state of thinking and discussion about Chandler 
design. The wiki will include both design commitments and summaries of 
major design issues being discussed on the list. In this way, someone who 
has an interest in a particular area can consult the wiki as a starting 
point and from there dive into discussion threads on the list relevant to 
that topic. We hope this will facilitate community participation in the design.
How will we do this? We'd like the wiki to be open to volunteer editors who 
want to take responsibility for tracking a certain area. OSAF staff will 
also actively participate in editing and keeping it up do date. I'm waving 
my hands here as this is a part we haven't yet worked out. Obviously, a lot 
depends on having a logical topical organization overall and editors who 
can succinctly summarize different points of view about particular issues 
as they are written up in the design list.

The details of the plan will be worked out on the process list once we can 
put up a strawman draft, which will be shortly. We're all going to learn 
together how to do this.

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

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