[Process] Wiki suggestions to help summarizers

[Paul Patterson]

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:

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
***@laplaza.org

[Chih-Chao Lam]

Hi Paul,

Thanks for the suggestions on how to improve the community wiki.

Post by Paul Patterson
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.

This is a good idea, let me think about it and once we have a few
volunteer summarizes, I'll definitely bounce this idea with them.

Post by Paul Patterson
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.

Do you mean have a section for mailing list links related to each topic?
Yes, that's the intent and in the better defined examples, we've started
it (e.g. Items & Attributes, Security). Please feel free to add this
heading to more topics.

Also, we would like mailing list participants to adopt the convention of
adding the relevant topic name in the mailing list subject headers e.g.
("data model" for data model related messages). Juergen is working on
(among many other things :) a new feature for the Twiki that will
hopefully automate your suggestion. In each top-level topic, we will
have a link to a page containing links to all mailing list messages with
the topic name as part of the message's subject header.

Post by Paul Patterson
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.

[see above comments]

Post by Paul Patterson
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.

My reluctance to add a new topic here is that I feel to be a real
"killer feature", it needs to be really well interwoven and integrated
with the rest of Chandler. Thus, by discussing killer features in an
orphaned section we may unwittingly lose the context of how this killer
feature fits with the rest of the Chandler framework.

For example, we think Chandler's data model and our "item-centric" view
of the world (i.e. agenda-like flexibility) will manifest itself as a
killer feature in many ways. But the deep reason for the killer feature
is the way we organize our data model and hence it's deserving of a
top-level topic.

So, if you have a killer feature proposal, please add it to the relevant
topic or the jungle.

Post by Paul Patterson
5) Add a Queries subtopic to View Issues.

Good suggestion.

Keep the suggestions coming,
chao

[Mitchell Baker]

Post by Paul Patterson
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

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

Post by Paul Patterson
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.
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
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Process" mailing list
http://lists.osafoundation.org/mailman/listinfo/process