7 May
2012
7 May
'12
8:12 a.m.
On 05/07/2012 10:07 AM, David C. Rankin wrote:
On 05/07/2012 08:27 AM, E. Liddell wrote:
I mean Tim is implementing the replacement currently with his TDE
hardware library ( this is still beta ).
Given the reasons it's now an orphan, I
don't think it's wise for us
to assume its
maintenance (IIRC, Tim has already said he doesn't want to, anyway).
Best to
move on.
Yep, I agree totally. The big question is my mind is (1) time & (2)
manpower constraints to implement its removal from tde. Every kde3
project that wants to move forward must be addressing this issue. While
it might seem unmanageable for TDE to do it alone, or SuSE to do it
alone, or whoever to do it alone, if we could somehow coordinate TDE,
SuSE and whoever else (need to ID these) so that a common framework is
chosen and the parts of the transition broken down into block 1, 2, 3,
.... so that TDE does 1, suse does 2, and so on -- it starts to look a
whole lot more doable.
Why not have a central halfreetkde3-wiki or something similar that could
host removal standards and server as a patch repository/hub....
Instead of having 10 different projects separately trying to do the same
thing 10 different ways, it is far better to have 10 different projects
contribute to doing 1 thing the same way....
Instead of having 10 different projects, why doesn't everyone else join
Trinity? We are the largest fork of KDE3. Anyone else is getting hung up
on pointless technical arguments. Those people who choose to leave for
those arguments are silly because in the end they hurt themselves more.
KDE3 has a following and splitting the small developer and userbase up
is ridiculous.
Calvin