On Wed, Jun 15, 2011 at 12:58 PM, drew <drew@baseanswers.com> wrote:
Hi,
Haven't gone back and read the notes/transcript from Mondays meeting but
IIRC the subject of a TDF/LibO presence at OSCON was left for follow up
on the ML - so here we go.
What;s up - Carl, Craig, Dona - how can those of us not in the NW help
to get this off the ground?
I see that the clock is ticking fast on this.
Thanks,
Drew
My recollection of the conversation is that we would discuss on this
list what we wanted to accomplish at OSCON
(http://www.oscon.com/oscon2011), as part of a bigger context of NA
Marketing direction.
OSCON is the premier event for open source in North America. Big names
all around; [?]ubuntu and OpenSUSE have already committed. LibreOffice
is already a well known F/OSS player. What can be done at OSCON to
move LibO forward in NA? Add to developer body? Add to marketing team?
As we discussed on IRC, this is where things need to start...what are
we trying to do overall for LibreOffice in North America?
In my view, the largest opportunities to increase LibreOffice market
share are with Windows and Mac users. Linux users already help brew
the Kool-Aid. OSCON probably won't make much of a dent there.
Carl
Carl
--
Unsubscribe instructions: E-mail to marketing+help@us.libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/us/marketing/
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.