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


I was under the idea that this was the source for LO support.
   
Fortunately this is not an issue of "wait-and-hope-while-my work-stagnates"
issue in a "Professional Work Environment", but I have indicated 3 issues in
the past day, some which may be legit new bugs.

Since this product is out of development it is imperative that users have a
place to ask for support, have potential bugs confirmed, make comments for
about interface issues and to generally offer suggestions to enhance the
product.

Also, since this is a "new" product, the expert userbase is not around to
take up the slack, so it is also important that there is some official
representation for the time being to carry the load.

Thank you,
MRK

-----
LO version as updated via PPA - Ubuntu 10.04 LTS (& Windows XP-SP3) - (1) 2.8 G/2G RAM/ATI 
HD2600,512VRAM/SIS AC97 OB Audio (2) 2.9 G/3G RAM/NVIDIA 9500GT,1024VRAM/SB AudigySE Audio (3) 2.3 
G/2G RAM/NVIDIA FX1500M,256VRAM/Sigmatel HD Audio
--
View this message in context: 
http://nabble.documentfoundation.org/Is-this-the-OFFICIAL-Location-for-LO-users-to-ask-for-help-tp2657083p2657083.html
Sent from the Users mailing list archive at Nabble.com.

-- 
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***

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.