https://bugs.freedesktop.org/show_bug.cgi?id=48463
--- Comment #14 from HarzG <[email protected]> 2012-06-10 14:36:24 PDT --- Maybe a longer explanation could help ... ... it's not my intention to let this issue grow to become a "personal thing" between you and me. So - p(l)ea(s)ce: It's my intention to make LibO / Firefox / whatever FOSS better. The malformed links issue was founded by another user, but he don't reported this on Freedesktop. I did precisely that what you asked for on 2011/06/19: >>What is your vision for the future and/or what would you most like to see >>improved ? >It would be amazing if more people would help in the QA and help the >developers to find bugs much earlier. As usual there never was/is much time for a decision at the office. background: I'm part of a work-group/panel to advice the management of a new public affairs organisation about decisions for a lot of applications (platform independent, cloud, formats, office software etc.) for 100+ clients. In this work-group I'm a little player with a very little chance to promote/advice LibO or other FOSS-applications. My knowledge to integrate "all applications" to a new desktop for all kind of users (Windows/OSX/Linux) is not one as a level of IT-developper / architecture consultant. Sometimes I can only tell the other members about some issues: like "this software we need" and "those won't work" ... because there are some known bug-issues or support-issues imho. That's why I'm a little hasty with the issue. back to LibO calc: My point of view is a user-view and I see other bug-fixes in 3.5.x but I hadn't heard about a decision or time-path to fix the malformed XLS-links or something like "a fix not before" information. Because my user-view I changed the version number, maybe any user will search/filter results with a release number of LibO. Some other users informed me about a new LibO-version and from them I heard "maybe it's fixed now". The user-view about software-issues was/is/will be never the same view as the developer- or helpdesk-view at the same issue, not in terms of importance and also not in terms of communication. I'd changed the version number earlier (2012-04-13) and heard nothing like "don't do this, because this isn't usual" and "produce noise" in LibO-development. If any developer told me "it will take a month or two", it was ok for me. But I heard not so much about the malformed links issue. If users could have some information about the possibility for a fix (like: to fix in version 3.6.* ...), somebody can decide to stay & wait, downgrade to LibO 3.4.6 or test & migrate to Apache OpenOffice 3.4. Maybe it was my own wrong decision at all to start with LibO "at the office". Microsoft Office is also available and can be installed in various versions on a Linux desktop (if Outlook or Access are not necessary). I understand your point "we need more test-results from users / early adopters". And if they respond, maybe they will not respond like you think they should. Only a very small group of users will report bugs at all and within this group much of them "report" bugs in a forum which is not related to TDF. And only some of them will report on bugs.freedesktop.org. I think the chance of a bug-report in a developer-format & tech-language that also fits to the chosen bug-report-platform isn't so big. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
