Suggestion summaries
Posted: Mon Jul 21, 2014 12:01 pm
I've been asked by the devs, if I can make some summary of ideas about the last weeks. And there is this need to avoid those ever ever repeating ideas. (https://forums.factorio.com/forum/vie ... f=5&t=4574)
I'm now thinking about 2 weeks about that problem and this is my provisory result:
- Step #1: we need to cut the ideas out of the threads.
- Step #2: then we can systematically create a "list of suggestions".
Step #1
- someone reads a thread completely.
- he summarizes the ideas in very short words at the end
--- every idea from the thread becomes a special article with a heading "%summary%" or something (there are Plugins for phpbb which enable to tag articles. Several ways to do that. It is only important, that it can be found afterwards with not too much wrong hits and none is missing). In other words: I'm not sure, if that can work as described, cause if there are different opinions you need to write for every aspect a summary article. I let that open, let's just begin and see, what must be changed!
--- ideally it is one sentence, which describes the whole thread (dreaming )
--- it is here NOT important to compare anything. All what is needed is an objective short of the suggestion.
Target for that stage:
- the summary can be discussed again. Is it really objective? Some important thing forgotten?
- those summarized articles can be searched easily.
- all happens in the forum, everyone can discuss.
- "wrong summaries" are deleted, new written at the bottom of the thread.
Step #2
Now when there is no more discussion the work can continue in the wiki.
Wiki, cause that is really open and collaborative work.
- for every idea (=summary articles or whatever) we make an entry into one ore more lists (just copy the summary text).
- in this list we can move the things, which belongs together together, put them on other pages, link exactly and all the stuff, where a wiki is a good use.
- cause that is open, everybody can move the topics, add links, bring things together.
Targets
- we have a validated list of ideas, that are ordered in some way(s)
- the devs have the input to see, what is wanted.
What do you think? Is that useful? Too much work?
I'm now thinking about 2 weeks about that problem and this is my provisory result:
- Step #1: we need to cut the ideas out of the threads.
- Step #2: then we can systematically create a "list of suggestions".
Step #1
- someone reads a thread completely.
- he summarizes the ideas in very short words at the end
--- every idea from the thread becomes a special article with a heading "%summary%" or something (there are Plugins for phpbb which enable to tag articles. Several ways to do that. It is only important, that it can be found afterwards with not too much wrong hits and none is missing). In other words: I'm not sure, if that can work as described, cause if there are different opinions you need to write for every aspect a summary article. I let that open, let's just begin and see, what must be changed!
--- ideally it is one sentence, which describes the whole thread (dreaming )
--- it is here NOT important to compare anything. All what is needed is an objective short of the suggestion.
Target for that stage:
- the summary can be discussed again. Is it really objective? Some important thing forgotten?
- those summarized articles can be searched easily.
- all happens in the forum, everyone can discuss.
- "wrong summaries" are deleted, new written at the bottom of the thread.
Step #2
Now when there is no more discussion the work can continue in the wiki.
Wiki, cause that is really open and collaborative work.
- for every idea (=summary articles or whatever) we make an entry into one ore more lists (just copy the summary text).
- in this list we can move the things, which belongs together together, put them on other pages, link exactly and all the stuff, where a wiki is a good use.
- cause that is open, everybody can move the topics, add links, bring things together.
Targets
- we have a validated list of ideas, that are ordered in some way(s)
- the devs have the input to see, what is wanted.
What do you think? Is that useful? Too much work?