[Design] Fwd: Processing Dogfood Feedback
Mimi Yin
mimi at osafoundation.org
Thu Nov 10 11:13:07 PST 2005
Hi Daniel,
I don't think we have any preconceptions about this. So the short
answer is both: both reactive and proactive.
Reactive, we already have a good sense of what that's like, with the
dogfooding discussions that have been going on. Proactive, ideas for
new designs, we're a little fuzzier on. I think we will need to set
up an area on the wiki where people can file ideas, so we don't lose
them. Then when it's time to discuss planning, we can review the
ideas and suggestions people have contributed and discuss them in the
context of goals and tenets for future releases.
The wiki is an area where we know we need more work, but it's not
clear right now what that work is and who's going to do it or when.
We will keep the list updated on that issue because I believe
expanding the wiki to include active community participation will be
a key piece of our collaborative design process.
Mimi :o)
On Nov 10, 2005, at 11:47 AM, Daniel Vareika wrote:
> Mimi:
>
> How do you envision the relationship with the list, as a reactive
> or as a proactive?
> What would you expect from an ideal scenario?
>
> I am not talking only for myself.
> Thanks a lot,
>
> Daniel
>
>
> Mimi Yin wrote:
>> I think our process of posting mockups to the list has worked
>> pretty well. Periodically I think we should summarize proposals
>> into one email. But other than that, it's been effective thus far.
>>
>> On Nov 10, 2005, at 9:34 AM, Philippe Bossut wrote:
>>
>>> Daniel Vareika wrote:
>>>
>>>
>>>> *Do you plan to do this process in house or do you see viable
>>>> and worthwhile to share it with the design list?
>>>> I mean do you expect imput from people outside OSAF and in which
>>>> way?
>>>> Reactive or Proactive?*
>>>>
>>>
>>> I think Mimi or Sheila should answer that one since they are
>>> driving the design process.
>>>
>>> On the example I gave, it was just that, an example of a past
>>> experience and how having a dozen of screenshots can help shape
>>> the early thinking on a feature. It was not meant to say that
>>> our process should be paper based and among OSAF core team
>>> members only. Sorry for the confusion.
>>>
>>> Cheers,
>>> - Philippe
>>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>>
>>> Open Source Applications Foundation "Design" mailing list
>>> http://lists.osafoundation.org/mailman/listinfo/design
>>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20051110/a40d031d/attachment.html
More information about the Design
mailing list