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


I proposed a talk on OOo / LO and plan to attend. Did not put in much time on the proposal so not sure if it will be accepted. If something is happening there, count me in.
On 06/21/2011 02:46 AM, John LeMoyne Castle wrote:
Seems to me this thread used to be longer in Nabble 8-0
I am still interested Drew and I had this thought:
Even if a HackFest can't be drawn together it would be very useful to the
attendees and LibreOffice to have at least a table where people could report
issues (as new or as confirmation of existing issues), get coaching on
appropriate upgrades, and maybe do a little testing around their known
issues, hard to reproduce issues or just visit areas that are important to
them as users.
Seems like an excellent chance for solid feedback from committed and
skillful users.
LeMoyne

--
View this message in context: 
http://nabble.documentfoundation.org/Hackfest-September-9th-Ohio-Linux-Fest-tp3069297p3089492.html
Sent from the Discuss mailing list archive at Nabble.com.

--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
Info:  http://www.pitonyak.org/oo.php


--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
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.