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


https://bugs.documentfoundation.org/show_bug.cgi?id=134486

--- Comment #30 from Julian Stirling <julian@julianstirling.co.uk> ---
Enterprise customers should be encouraged to pay for support, but this
statement interferes with the fundamental freedoms of open source (even if only
by implication rather than by license). There is no need to have a different
"edition", to differentiate supported copies. You could have a tag line that
says:

"LibreOffice is developed by The Document Foundation, ecosystem partners, and
numerous volunteers. This copy is community supported. For enterprise use we
recommend buying support from a LibreOffice ecosystem partner."

This makes it clear that the copy does not have the available paid support, but
that it is the same copy and you have the right to use it. This doesn't stop
other companies offering support, but it gives something clear for large
enterprises to put in a tender documents so they are more buy from those who
contribute to the source.

Perhaps token based authentication could change the tag line to show that the
version is supported by an ecosystem partner? Not sure if that is an awful
idea.

I know this idea is half baked, but that makes it 50% more baked than a
statement claiming LO is "intended for personal use".

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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.