On 10/28/2010 04:21 PM, Drew Jensen wrote:
Religious organizations are another are where costs and document portability might not be a
major concern because everyone is using the
Small non-profits tend to have big issues with compatibility, because
they typically use old software that is no longer supported.
Those microsoft grants are not all that they are cracked up to be. So
much so, that even with a grant, the costs involved in complying with
the terms of the grant are such, that the organization would be better
off refusing the grant.
same thing so there are no problems
have met many people from small congregations in the forums
One of the big hurdles that FLOSS advocates have to face, when trying to
migrate religious organizations to FLOSS, is the lack of usable software
that is functionally equivalent to their (usually pirated) Windows product.
The significant software there is the one that handles membership data,
scheduling, sermon preparation, service co-ordination, lyric
presentation, and any number of church stuff that nobody but the church
secretary, the board of elders, and the pastor know about.
jonathon
--
No human will see non-list, non-bulk, non-junk email sent to this address.
It all gets forwarded to /dev/null
--
E-mail to marketing+help@libreoffice.org for instructions on how to unsubscribe
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.