Re: Wiki suggestions to help summarizers

Mitchell Baker <Mitchell-6zGkXsw2EZWGJGYlWa3Ukdi2O/[email protected]> Thu, 09 Jan 2003 22:59:23 -0800
Newsgroups gmane.org.osaf.process
Organization OSAFoundation
Message-ID <[email protected]>
Paul Patterson wrote:

> Hi Chao
>
> Congratulations on the Chao Topic Schema and the Wiki.  A  nice piece 
> of work.   My understanding is that you don't want people to add pages 
> to the Wiki at this time, but to feed ideas to you.  Because I see a 
> wiki as particualrly good at refactoring a discussion, I have a few 
> suggestions.  The volunteer summarizers may have a less comprehensive 
> or  up-to-date view than staff members.  To help them, I suggest:


Actually, I didn't mean to discourage people from adding pages to the 
wiki.  The changes that you suggest are structural in nature, so it does 
makes sense to discuss these with us.  
But as people develop content or proposals or summaries that warrent new 
pages in the wiki, etc we hope those new pages will be added.  

And if people aren't sure if some particular piece of content fits in 
the Discussion Topics, please add it to the Jungle, point us to it and 
ask.  

Mitchell

>
>
> 1)   Create one page summarizing the currently established goals, 
> philosophy, principles, target audience, as lists of one-liners 
> (bullets).  This is meant to support your summarizers in developing 
> well-reasoned responses to OSAF positions  in their topics.  A 
> volunteer summarizer can go to one place to refresh their 
> understanding of stated project principles.  And it will make it easy 
> to find   an addition or change, for example, a new target audience. 
> This summary page would then link to the topics which develop these ideas.
>
> 2)  Add a sub-heading of "Probably relevant Maiing List  messages" in 
> the as a place for one summarizer to alert another of a message or 
> thread that  crosses into another Topic.
>
> 3)  Request someone to tentatively  factor threads (or messages) to 
> Topics, before a summarizer has looked at them in detail.  These can 
> go into the  "Probably relevant Maiing List  messages" sub-heading. 
> This gets more data  into the wiki earlier and helps a new summarizer 
> get started.  The mailing lists are already  huge and rapidly 
> growing.  You will get more from your volunteers if they don't have to 
> review the whole lists to get started.
>
> Other wiki suggestions:
>
> 4)  Create a topic for discussion of Killer Feature Candidates, 
> perhaps in the Jungle.  If it is in the jungle, link to it from your 
> Key Topics page.  This is the vaguest part of the First Product 
> Release statement, and it is very important. It needs to stay in front 
> of the community for consideration.
>
> 5)  Add a Queries subtopic to View Issues.
>
> Thanks,
>
> Paul Patterson
> [email protected]
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Process" mailing list
> http://lists.osafoundation.org/mailman/listinfo/process
>
>



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

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