24 Jun
2011
24 Jun
'11
12:48 a.m.
On Friday 24 June 2011 04:19:52 Timothy Pearson
wrote:
Specifically, how are you providing Qt4 compatibility?
I ever claimed I patched KDE3 for Qt4 support?
The point of all of the above is to establish who is in control of the
Trinity desktop project. Personally I am sick and tired of hearing that
things "cannot be done"--that is merely what the KDE4 devs have started as
propaganda to promote their new way of doing things.
Rather than criticizing almost every decision we have made, please try to
help where possible and make KDE3/TDE a better desktop environment. If
you see a potential problem, why don't you see what the best alternatives
are from your perspective and mention them on this list, or even try to
put in some work towards fixing the problem?
We have enough idle critics out on the Internet; please don't be one on
this mailing list.
Thanks!
Tim
The integration with KDE3 styles is still far from
perfect.
Don't you think you overestimate your abilities?
No, not really. However I think you do overestimate yours... How are you
improving KOffice to properly read and write standard .ods/.odt file
formats?
I ever claimed that I patched KOffice for ODF support?
By the way, if you succeed to make KOffice to open ODF files, please let
me know.
Have you fixed any of the couple hundred bugs on
the Trinity
bugtracker?
Sorry never looked into Trinity bugtracker in search for bugreports.
I fixed some bugs which I personally encountered and sent you the patches
if they
were connected with the KDE3 source.
All I see you doing is packaging other
people's source and
patching minor compilation issues, without reporting the patches
upstream
via the bugtracker.
I reported the patches which I made here in the list. Of course I can do
it using the
bugtracker if you wish.
There is nothing wrong with having two different
positions here--the
Trinity project is a FOSS project, tasked with new development, general
maintenance, bug control, and project direction management (that
includes
deciding what is part of the project and what is not), and you are a
distribution packager/maintainer, tasked with making upstream FOSS
projects work properly on your distribution. Am I incorrect?
You are correct. So what?