Re: [tdf-discuss] Re: On the Future of TDF
2010/12/5 Gérard Fargeot <email@example.com>:
You are dreaming.
In OOo we have so many versions as "distro", LibO is taking the same road.
Each distro (each dev.) want his own built.
We are not able to have 1 same product and you want an association with
This is the big problem of open source.
Not sure if this is a big problem or not... I tend to think
"proliferation" in FOSS world is a big *solution*: there are more
opportunities for new ideas... And all FOSS ideas can be reused.
But yes, IMO the idea to merge all those project it's only a dream...
or a nightmare: how will you convince the GTK programmers to learn Qt
(or vice-versa)? How will you manage to merge a text oriented app like
Writer with a frame oriented app like kword? How will you convince
users of abiword, that only need basic features, to load a full
featured (and resource hungry) word processor with all the features of
Writer and kword? How...?
There are lots of people that will never contribute to a GTK (or Qt)
project because they do not know how GTK (or Qt) works. And that's
perfectly fine: it is called freedom of choice.
If you replace a defacto proprietary monopoly with a defacto
opensource monopoly, you'll still have a defacto monopoly... and
that's not good.
Unsubscribe instructions: E-mail to firstname.lastname@example.org
*** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] On the Future of TDF · AG
- Re: [tdf-discuss] On the Future of TDF (continued)
Impressum (Legal Info)
: 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