<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - UI: Branding: LibreOffice Personal edition" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134486#c38">Comment # 38</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - UI: Branding: LibreOffice Personal edition" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134486">bug 134486</a> from <a class="email" href="mailto:bitigchi@me.com" title="Emir Sarı <bitigchi@me.com>"> Emir Sarı</a> <pre>I fully support getting more development resources for TDF, but IMO, lack of a second "edition" is a marketing blocker for this from the start. 1. Community Edition 2. Enterprise Edition -> a listing of available companies to get LibreOffice from, not an edition from TDF I am aware that these companies already play a big role in LibreOffice development, but I am not sure that directing the enterprise or government folks to 3rd parties would be too appealing for them. It's confession from TDF that they are pulling from the market themselves, and leaving it to 3rd parties, a confession that they are limiting their user base. I hope enough on-site market research is conducted before making this decision. Otherwise we will be reading news that organisations and governments simply switching to different alternatives with better official contact and branding, instead of dealing with a 3rd party providing LibreOffice company other than TDF. Confusion ensues. What would be ideal is, creating an actual "Enterprise Edition", with subscriptions or one-time licence fees, then using this resources to fund (outsource) development. It's okay for Enterprise Edition to come with more features, especially with all the LibreOffice Online perks. Channel all support requests to 3rd parties, why not? But TDF should provide all LibreOffice versions, not fragmentise it. Visual Studio is a nice example. Free for single developers, paid for enterprise. Everyone is happy. Another thing, I am really not happy is that TDF doesn't get to prioritise UX issues. With this model, companies usually tend to fix document-related issues, and UX related issues doesn't get much attention. With all the branding and the funds remaining in-house, TDF can select development priorities, and help to make LO (actually) fun to use on all platforms (looking at you macOS version). Final thing, please don't rush this. It's obvious that this is not researched enough and thought-through, and with the release at the doorstep, it will be a huge chaos and backslash from everyone affiliated.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>