Katie,

I´ll answer between lines.

Katie Capps Parlante wrote:
 In other words, the wiki is good for capturing a proposal and being the record of the current state of the proposal, and the list is better for discussions about the proposal.
+1
To repeat Mimi's point about welcoming proactive ideas, we're definitely open to proposals and ideas from any interested party -- a good idea is a good idea, whoever proposes it. ;) Just as we would do with code submissions, we want to make sure that any design proposal has merit and fits with the overall goals and design of Chandler before adopting it. As Mimi mentioned, we're trying to work out a process that allows for collecting a variety of ideas, and then evaluating and iterating on those ideas. The process for incorporating design ideas will differ from the processes we will use for patch code submissions.
The process of sending out ideas in the wild, through the mailing lists, might not be (as you say) the best form to propose ideas, though on the other hand its by far the easiest.
I have not tried myself editing wiki, but I will.
Periods of time where all the development effort is put to debugging and achieving a milestone maybe are the worst to post ideas in the wild.
I have been responsible of that in the past weeks although I never meant to.
My apologies to the development team at OSAF for this.

We have a few next steps that should help:

+ Refine the wiki organization and process for capturing proposals, so that they don't get completely lost on the wiki
I find that it´s somehow difficult to find things in the OSAF wiki. I don´t know if it´s through my inability, because I did not have much time to search thoroughly.
+ Document Chandler's goals and design more clearly and make that easily accessible (not lost in the wiki), so that people have that information when participating in disucssions and formulating proposals
+1
+ OSAF discussions about the design (as well as development) should be held publicly on the list so that people who are not in the building in SF can participate effectively
Thanks! Thanks! Thanks!
We're working on it! We appreciate the recent activity on the list, it has been very constructive.

Cheers,
Katie

Have now Idea how much it is welcome.
Thanks once again,

Daniel

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

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

Reply via email to