What a wierd post, Jacek! I tend to side with the dev viewpoint because of personal background, but I'm going to have to play devil's advocate here.<br><br>To paraphrase it rather uncharitably, you seem to be saying "Our community is happily communicating using our ad hoc medium X, but we want the straightjacket medium Y which is better for developers, feedback please". You give no justification for Y as a community medium, and there is no indication whatsoever that the community outside devs has the remotest bit of interest in Y. I'm sure that you have good dev reasons for Y, but unless the community shares those reasons, you're not heading for a winning strategy,<br>
<br>Now I understand the purpose of an appropriate medium for development, or several of them, because development is a very focused discipline. But that is leagues away from a friendly community medium, and I think you may be mixing the two in your mind. The vast majority of Impy and future Kokua "feedback people" are not going to be developers, they're going to be users with varying degrees of technical awareness. Devs are the minority. You need both. You need the buzz of non-devs chatting to each other and reinforcing their interest.<br>
<br>The blog is not a community medium. It's a top-down announcement delivery system which marginalizes the community, because all community input is effectively lost as soon as the next blog post appears. It would be a severe mistake to replace the forums with the blog, exactly the same mistake that Linden Lab made. Their old forums were extremely vibrant and full of detailed community communication, whereas their new "forums" (which are really just a blog) are completely and utterly useless except for a few people who use them for ranting. Linden wanted control and focus, and as a result they now own a wasteland.<br>
<br>Imprudence has a great community at present. Don't lose that just because you feel a manager's need for restructuring.<br><br>Dev and community communications don't work the same way. I would not advise trying to merge them into a single "efficient" system, because you risk losing something valuable.<br>
<br><br>Morgaine.<br><br><br><br><br>=============================<br><br><div class="gmail_quote">On Mon, Apr 11, 2011 at 9:48 PM, Jacek Antonelli <span dir="ltr"><<a href="mailto:jacek@kokuaviewer.org">jacek@kokuaviewer.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">As you know, I've been working on redefining and documenting our<br>
communications policy, including the purposes of our many<br>
communications channels (issue tracker, wiki, etc.). Now I'm<br>
contemplating the forums, and trying to decide what their purpose is<br>
(or should be), and what to do with them. I would very much appreciate<br>
your thoughts and feedback about this topic.<br>
<br>
Consider that right now we have 5 forum sections (not counting "Off<br>
Topic"), and 4 of them are pretty much obsolete:<br>
<br>
* Viewer: This is where people would post ideas, feature requests,<br>
etc. But we're now using only the issue tracker for feature requests.<br>
* Problems & Troubleshooting (previously "Bug Reports &<br>
Troubleshooting"): This is where people would post bug reports,<br>
problems they are having, and provide feedback about releases. But<br>
we're now using only the issue tracker for bug reports, and blog posts<br>
for general feedback about releases.<br>
* Development: This is where people would discuss development-related<br>
stuff, technical discussions of features, get help compiling the<br>
viewer, etc. But we're now encouraging use of the mailing list and IRC<br>
for those things.<br>
* Project: This is where people would discuss project organization<br>
issues and report problems with the website. But we're now using the<br>
issue tracker for website issues, and project organization discussion<br>
is done via the mailing list and meetups.<br>
* General: All other discussion. The only reason this isn't obsolete<br>
too is because its purpose is so vague.<br>
<br>
My instinct is to archive (lock to prevent new posts) all the current<br>
forum sections and create new sections with new purposes. But, I'm<br>
having a hard time thinking of what those purposes would be.<br>
<br>
In the past, I've argued that the forums are useful as a social hub<br>
for the community (see e.g. <a href="http://www.plurk.com/p/amzlet" target="_blank">http://www.plurk.com/p/amzlet</a> ). If that's<br>
true, then the new sections would be social-oriented. But aside from a<br>
section for general Kokua/Imp-related discussion, the only things I<br>
can think of are a place for people to introduce themselves, and<br>
possibly a place to ask for help from other users. (But for the<br>
latter, we already have inworld groups and a Q&A site<br>
<<a href="http://support.kokuaviewer.org/qa/" target="_blank">http://support.kokuaviewer.org/qa/</a>>.)<br>
<br>
So, my question is: do the forums provide any real use or value in the<br>
new organization? Should we keep them, or archive them completely? If<br>
keep them, for what purpose(s)? What sections should there be?<br>
<br>
- Jacek<br>
_______________________________________________<br>
ImpDev mailing list<br>
<a href="mailto:ImpDev@lists.imprudenceviewer.org">ImpDev@lists.imprudenceviewer.org</a><br>
<a href="http://lists.imprudenceviewer.org/listinfo.cgi/impdev-imprudenceviewer.org" target="_blank">http://lists.imprudenceviewer.org/listinfo.cgi/impdev-imprudenceviewer.org</a><br>
</blockquote></div><br>