Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


It is the case that Stack Exchange is a challenge, although I don't recall 
having all that much difficulty with it.

I concur completely about the desire for forums and the phpBB forums seem to 
work quite well (at least based on the experience with the OpenOffice.org 
Community Forums).  It does indeed depend on the vigilance of volunteers, 
moderators, and administrators.  But Forum governance can work very smoothly 
and it is a great outlet for peer support and the satisfaction of peer 
supporters who advance into volunteer and other categories.

There is one value to Stack Exchange.  It is possible to set a search on Stack 
Exchange questions and watch for ones that are relevant to OO.o and LO.  I 
have done so and I see about one per day.  (I have probably responded to at 
most two of them.)

I suspect it is possible to also create a search that also finds asked and 
answered or still unanswered questions about OO.o and LO.

More eyes on those, especially for those who are enamored of Stock Exchange, 
would be valuable.


 - Dennis E. Hamilton
   tools for document interoperability,  <http://nfoWorks.org/>
   dennis.hamilton@acm.org  gsm: +1-206-779-9430  @orcmid





-----Original Message-----
From: Italo Vignoli [mailto:italo.vignoli@gmail.com]
Sent: Friday, November 04, 2011 13:19
To: discuss@documentfoundation.org
Subject: Re: [tdf-discuss] phpbb for the official LO forums

On 11/4/11 7:56 PM, Florian Effenberger wrote:

many users have made *very* clear to me several times that they want a
"real" forum they know, like phpBB. Otherwise, I would have simply gone
with Nabble, so I'm a bit hesitant...

I agree with Florian. Users want a forum, and this has been made very
clear by many people. After having been accused of ignoring user needs
because we didn't have a real forum, any other solution, at this stage,
would be perceived in a negative way.

Please remember that users are different from developers. As a user, I
find stackexchange simply unacceptable (would really like to know who
has had the idea).

Users do not want to study the solution. They want to write a question,
and get an answer. Simple problem, with a simple answer.

Stackexchange makes it complex, in a useless way. I have been on the
site for ten minutes, and I haven't been able to understand what I was
supposed to do. I am usually considered a power user (sometimes, even a
geek, at least in the marketing environment), and I don't see how
something like stackexchange can be considered a better alternative to
mailing lists and forums.

Best, Italo

-- 
Italo Vignoli
italo.vignoli@gmail.com
mobile +39.348.5653829
VoIP +39.02.320621813
skype italovignoli

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? 
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.