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

Re: [tdf-discuss] Re: Oracle contributes OOo Code to Apache Software Foundation'sIncubator


Delivering sermons to LibreOffice after being humbled by the same community
which you and some corporates didn't even bothered to even hear out, I am
sure you know that OOo has not been accepted as an Apache project yet. So
stop lecturing what we should do , anywayz you guys won't even know when the
Big Daddy changes his mood and you guys are left chewing words.

As for aspersions regarding the name, I am sure that you know that most of
the Linux distros which power >90% of world's linux machines have already
accepted LO and you guys can go ahead and curse the BIG Daddy ...


Thank You

Best Regards
Varun Mittal <http://www.varunmittal.info/>

<https://www.google.com/profiles/varunmittal87>

Google <https://www.google.com/profiles/varunmittal87>
Facebook<http://www.facebook.com/mittal.varun>
   LinkedIn <http://www.linkedin.com/in/varunmittal87>
Twitter<http://twitter.com/varunmittal19>


"Uncertainty is the only Certainty of LIFE"

On Fri, Jun 3, 2011 at 5:30 PM, Harold Fuchs <hwfa.libreoffice@gmail.com>wrote:


"plino" <pedlino@gmail.com> wrote in message
1307086982610-3018856.post@n3.nabble.com">news:1307086982610-3018856.post@n3.nabble.com...

 As a user I wouldn't be happy IF the devs split up between two projects.

The way I see it is IBM and maybe some Oracle devs will work on OOo and
everybody else will work on LO...

The good part (besides the Apache license which allows LO to use what
little
code will be openly contributed to OOo) is that IBM will continue to
develop
ODF, which badly needs it.

I find it a little absurd that the people behind a file format that has
been
under development for years haven't implemented font embedding... Of
course,
fonts are not important for serious business companies :)

--
View this message in context:
http://nabble.documentfoundation.org/Oracle-contributes-OOo-Code-to-Apache-Software-Foundation-s-Incubator-tp3011527p3018856.html
Sent from the Discuss mailing list archive at Nabble.com.


The LO folk left the OOo group because OOo was, in their opinion, going to
be over-controlled (by Oracle). Now that this is no longer true, the LO folk
don't have a case and should return to the fold. So, why don't the LO folk
do a deal with Apache, combine the best bits of OOo with LO to get back to a
single "product" and form jointly with the Apache folk an "LO Foundation".
It seems completely crazy to have two sets of developers and two sets of
code. All that does is sow FUD (Fear, Uncertainty and Doubt) in the minds of
potential users.

Oh, and by the way, get rid of the asinine name "LibreOffice" which half
the world can't pronounce and which three quarters of the world doesn't
understand the meaning of.


--
Harold Fuchs
London, England


--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be
deleted



-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

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.