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

Good morning, Charles,

On 11/3/13 5:29 AM, Charles-H. Schulz wrote:
Hello Ken,

Le Sat, 02 Nov 2013 09:07:57 -0600,
Ken Springer <> a écrit :

On 11/2/13 3:48 AM, Charles-H. Schulz wrote:
Le Fri, 1 Nov 2013 22:59:33 +0000,
e-letter <> a écrit :

On 01/11/2013, Charles-H. Schulz
<> wrote:


I've taken the liberty of snipping the older parts of this subthread, since I won't be addressing any of those points.

First of all: thank you for your advice on the survey! I'm sure we can
improve for the next one :-)

You're welcome.  And I look forward to an improved survey.

As for contacting you via email. This is not how we work as a Free &
Open Source Software project and as a community. You're welcome to
express your views here or even on our discuss list. You can even open
a page on our wiki, keeping in mind that ideas, when they remain ideas
and when no one's working on them, are cheap. Making them real is what

I've learned not all open source projects have this view. Some, much more restrictive in public comments, some just tell you "we don't care if it doesn't work, fix it yourself" or words to that effect. So I chose the conservative approach. <G>

What propels the LibreOffice project are ourselves, which means our
own work; we can't make things happen overnight by shoveling money here
and resources there. We don't have a marketing director (inasmuch as
I'm supposedly in charge of the marketing team with Italo Vignoli) who
can slap twenty market research studies on the table defining where we
should go in the future. We rely mostly on volunteers' work and

Years ago, I learned that in almost anything, you're better off in the long run to do a few things very well, rather than a lot of things just adequately. For LO, I've seen new features added that have issues for some users, while existing issues for users languish.

Those are two bugs I filed via Bugzilla, and noted them in news://$ac7$

I don't expect them to be fixed immediately, but IMO they could've been addressed by now. But, the last time I checked, not even assigned.

Perhaps some may think of it as excuses: they're not. This is how we
work, this is what we do and this is how we are. If things were
different we'd be working in a company developing and selling an office
suite. But we are LibreOffice. And we'd love you to be part of
LibreOffice too. This is where survey comes in...

But I can't give you honest and anywhere complete answers via the existing survey. Hence, my first reply to your post about the survey.

As I mentioned in the post linked (hopefully) above, I've got a list of things that didn't work correctly, at least for me (cross platform development may play a part here, I honestly don't know) in 3.x.x, but haven't retested except for the two bugs above. Which, by the way, still do not work right.

I use my computer and software more as a tool and communications system, I'm not a gamer. Games bore me. But I want to use the tool, not build the tool. I don't mind reporting issues, if the reporting system is easy for the "average" person to use (Bugzilla is not) and confirming a fix works for me. In between, that part of the process no longer interests me.


Mac OS X 10.8.5
Firefox 24.0
Thunderbird 17.0.8

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.