I definitely like the idea of a Q & A tool, especially building it based on Habari.
I think we should define the line between documentation and support. Questions can come into the Q&A tool, where one-off questions will be answered. For questions where a definitive tutorial would be useful, then a wiki entry could be created. Otherwise, I'm not sure one-off questions belong on the wiki. On Jun 1, 2009, at 10:32 AM, Owen Winkler wrote: > > Chris J. Davis wrote: >> >> So I would like to propose that before you answer any questions here >> on the list, please take the time to create a page on the wiki for >> your answer and then link to it. I am not sure how we should organize >> it, but I am sure we can come up with something that will make sense. >> Maybe a tips and tricks section that contains all these little >> nuggets >> of wisdom that seem to get lost in the noise. > > I won't dismiss the importance of sharing information, although I > would > like to be careful how much chaos we add to the wiki before we make a > real attempt at organizing things. > > Michael Harris has taken some time time to write up this plan for > organizing the wiki: > http://wiki.habariproject.org/en/Wiki_Structure > > Perhaps if we're going to put tips into the wiki, we should allocate > space for them and put them there to start with? > > [As an aside: I really like the idea of an "Incoming" area in the > wiki > for things where you have no idea where they're supposed to go. > Someone > who can figure that out can periodically look through and move them to > where they need to be.] > > And on that topic, I had some thoughts about building a > StackOverflow-like system of requesting help and selecting answers. > While the wiki works better for the short term, it might be useful to > produce a kind of help-desk area where people could ask questions > (posts) and then they and others could vote (commentinfo) on the best > working answers (comments). > > Similarly, these could be used to keep track of frequently searched- > for > or asked questions (postinfo), and could be consulted during > development > to determine Habari's weak areas; where changes need to be applied to > improve the product. > > Obviously, that's a lot more work than just putting the tips into the > wiki, but I think it's a better potential workflow for users. And it > also would demonstrate how Habari can be used in a non-blog context. > > Just a thought. > > Owen > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
