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

Re: [tdf-discuss] AskLibO blitzes


Hi Marc, *,

On Sun, May 20, 2012 at 6:39 AM, Marc Paré <marc@marcpare.com> wrote:
Would it be a good idea to organize a monthly call for a AskLibO blitz?

I think this would solve some of the outstanding unanswered questions queue.
We could all agree on maybe a 2-day spree where we could all check in and
answer as many questions as possible. The 2-day spree would also allow for a
return to those who answered just in case of a need to update and reply to
the answer.

While this will bring the # of unanswered questions down, I'd rather
have people who ask question also answer other ones :-)

People don't make enough use of their votes yet, they are not really
familiar with the system yet.

What I'd like to avoid is that there will be 10 people answering all
the questions...

But going though the unanswered ones (preferrably in "oldest first"
order) is of course a good idea, but hopefully it will not be the same
people doing all the work.

ciao
Christian

-- 
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.