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


On Wed, 2010-10-13 at 19:09 -0700, Ryan Singer wrote:
On Wednesday, October 13, 2010, Dave Johnson <davefilms.us@gmail.com> wrote:
Can Canonical provide paid support for LibO?

Canonical provides paid support for OOo on Ubuntu. At some point in
the next year or so they will probably also ship and support LibO.



Well can't find a video of that presentation on UStream - drat.

But the problem discussed was not 1st and 2nd line support - it was on
3rd and 4th level support.

Yes we do great at supporting individual users and small business - the
presentation was on supporting medium to large organizations.

Canonical might cover 3rd level perhaps, but would that also be true in
a mixed environment - will they support Windows machines also or Mac?

For instance Canonical also offers support for Lotus Symphony, but you
can be sure that they fall back to IBM for the Windows support and for
4th level support. (meaning when you need to actually get the developers
involved, perhaps with some special feature that needs to get into the
package)

This is where, IMO, we need to focus some thought - how will the
document foundation grow this type support environment.

Drew


-- 
To unsubscribe, e-mail to marketing+help@libreoffice.org
List archives are available at http://www.libreoffice.org/lists/marketing/
All messages you send 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.