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


On Mon, 22 Nov 2010 22:24:00 +1100, Sean White <runicpaladin@gmail.com> wrote:
One of the things i LOVE about open source software is the ability for me to
ask someone else to code something or port something that i cant do myself.
 So my solution to your problem of incompatible extensions is to set up a
new mailing list for OO to LO extension porting.  the public can send the
extension which the people on the mailing list can then port over.

Sorry, I can't hold back here :).

You LOVE open source because you can ask others to do what you want
without you having to do it yourself? I am afraid that is not going to
work out, people won't work on things they don't want to work on, just
because you tell them so :-).

Besides, resources are scarce. WHY should we require people to port all
hundreds of OOo extensions over to LO (and keep them up to date), just
because you don't like the current numbering scheme? They could rather
work on improving LO at the same time.

Once the code base diverge so much that the APIs become incompatible, we
can talk about porting again, but I don't see the point of porting just
for the sake of it.

Sebastian

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived for eternity ***

Context


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.