It would ease deployment and updates in the Free section. The Mac App Store will be available January 6, 2011. http://www.apple.com/mac/app-store/
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
This enhancement request/proposal is still valid and, well, reasonable, therefore changed the 'Status' field back to 'NEW'. @Thorsten Behrens: I have inserted you as Mac expert into the CC field. Could you please take a look at this proposal? I don't know all the possible advantages and disadvantages the proposal may have. I just want to invite you to leave a short comment telling if this idea has already been discussed within TDF and/or LibO developers, if it has been rejected for some reasons, or if it could be discussed some day in the future. IMHO this would be interesting for many Mac users. Thank you.
This is not possible as long as LibreOffice is licensed under LGPLv3 (or all contributors accept submission to the AppStore). Thus this is currently unfixable / invalid on a technical level.
(In reply to comment #3) > This is not possible as long as LibreOffice is licensed under LGPLv3 (or all > contributors accept submission to the AppStore). Thus this is currently > unfixable / invalid on a technical level. @Thorsten: Thank you for clarification! This saves us any further discussion.
*** Bug 51024 has been marked as a duplicate of this bug. ***
Note however that NeoOffice, which is licensed using an even more (insert suitable adjective) license (GPL), and includes some code snippets from LibreOffice, *is* going to be available in the Mac App Store soon, according to posts by their developer(s) on their forum.
FYI, NeoOffice is now in the Mac App Store: https://itunes.apple.com/us/app/neooffice/id639210716 .
And look at the sacrifices they had to make in order to get it allowed in the AppStore : http://www.neooffice.org/neojava/fr/macappstore.php - no embedded hsqldb database functionality ; - no Java framework or Java extension functionality ; - no Python extension or Python framework functionality - limited dictionary and language support - virtually no integrated media support Frankly, is it worth it ? Alex
That depends: - for the current users: probably no - if you want to reach the masses: probably yes. My father bought Apple Pages because he couldn't find LibreOffice in de Mac OSX AppStore (THE place to look for Apps).
Note that if one embeds Java in an app there is no problem. Not trivial, but not rocket science either. See http://intransitione.com/blog/take-java-to-app-store/ . Whether that makes sense or not, no idea.
It appears that the effort to dual license LibreOffice under Mozilla Public License v2.0 is such that it will allow for Mac App Store distribution (overturning comment 3). See http://www.libreoffice.org/about-us/licenses/ and https://wiki.documentfoundation.org/Development/Re-Basing#Why_go_with_the_MPLv2_.3F
Has the dual licensing finished? I don't really know how it happens. Anyway, I believe having LO in the Apple Mac Store would really help get LO out to users :).
(In reply to Nicholas from comment #12) > Has the dual licensing finished? I don't really know how it happens. > Anyway, I believe having LO in the Apple Mac Store would really help get LO > out to users :). Yes, licensing shouldn't be a problem any more. It's mostly climbing over the Apple-walls .. I'm pretty sure it's on the todo of some developers..
Adding self to CC if not already on
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.