A inhibitor of LibreOffice progressing into enterprise is the limited control over installed program modules. A current trend in streamlining the activities and procedures of users is to minimalise the amount of information presented to a user to only that needed for their tasks. e.g. MS File Server Access-based Enumeration. Installing a full office suite for every user is counter-intuitive to the Microsoft Office installation choices, and is contrary to current enterprise practise. Schools are also restricted as to the type of software allowed to students in certain situations. e.g. Exams. Supporting two office software variants for use in different situations is equally as counter-intuitive. Further, being unable to isolate a particular module or feature also hampers reactivity when mitigating security concerns.
please, read this: https://wiki.documentfoundation.org/ReleaseNotes/4.2#Installer_.28Windows_only.29
I'm aware that 4.2.0.1 removed the Program Modules features because "just the Start Menu icons/shortcuts were suppressed". Though this isn't actually the case, because the "source of bugs" was due to modules also being removed which were depended upon by modules still to be installed. e.g. bibliography in Writer relies upon Base module. The decision to remove the program modules features was a good decision in this case because it mitigated faults, but it isn't a permanent solution because removal of this feature has resulted in the details of this bug report not being satisfied. This should be a parent bug to specific child bugs detailing the individual faults encountered - i.e. dependencies were unsatisfied - with this bug being resolved once the Program Modules features have been re-introduced after all the cross-dependencies have been understood and either components with unmet dependencies are disabled during installation or the code is improved to remove unnecessary dependencies.
(In reply to Matthew Millar from comment #0) > A inhibitor of LibreOffice progressing into enterprise is the limited > control over installed program modules. > > A current trend in streamlining the activities and procedures of users is to > minimalise the amount of information presented to a user to only that needed > for their tasks. e.g. MS File Server Access-based Enumeration. Is that for security reasons, or training reasons, or? Status -> NEEDINFO > Installing a full office suite for every user is counter-intuitive to the > Microsoft Office installation choices, and is contrary to current enterprise > practise. 10 years ago, using Free/Open Source Software in the enterprise was probably not seen as "enterprise practice," but times are changing... > Schools are also restricted as to the type of software allowed to students > in certain situations. e.g. Exams. Supporting two office software variants > for use in different situations is equally as counter-intuitive. For better or worse, LibreOffice is an integrated suite. If schools want to have students take a writing test on a computer rather than in a bluebook, I don't see how having access to Impress and Calc is going to be a problem. There are a number of text editors like GEdit which might be even simpler for longhand writing. > Further, being unable to isolate a particular module or feature also hampers > reactivity when mitigating security concerns. I'd have to see a specific example to understand how isolating parts of LibreOffice for security reasons would justify the added expense of separating and maintaining the components separately. Of course, backend cleanup (accompanied by appropriate tests to make sure we don't break current functionality) is something that I'm sure the devs would love to review.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team This INVALID Message was generated on: 2016-05-09