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


On Tue, 2011-09-27 at 10:27 +0200, Florian Effenberger wrote:
Hi Drew,

thanks a lot for all your work on Nabble! (And of course, all your other 
work ;)

drew wrote on 2011-09-26 04:33:
1 - a few weeks back Nabble switched from a totally free (as in Ad Free)
service to one that now includes Ads. This is a bit of a problem IMO.
[For instance having a MSO on the bottom of a page with LibO
header..well, that is just darn right unseemly]

To me, there are two easy options:

1. We invest $125 for the ad-free service. Sounds like not too much 
money, and we could have a vote on the steering-discuss list about that.

It looks to be that $125.00 would turn ads off for around 18 months,
assuming the increase in usage continues at the same rate I've seen to
date.


2. Look for another service, maybe something self-hosted.


My idea would be to combine #1 and #2. First, invest the money to have 
no time pressure, but then in the mid-term, investigate other solutions 
and use these.

That makes the most sense IMO.

//drew


-- 
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
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.