The “F Word” September 19, 2009Posted by bashboxjones in Uncategorized.
Tags: fork, kde3, kde4
add a comment
I’m trying to get this blog started, I have a lot to do today, and I still haven’t figured out this Word Press thing. So, I’m going to get sloppy. I found a discussion of the future of KDE3 in a Gentoo blog. There’s a lot of good information in it, so I’m just going to quote from it randomly and indiscriminately, without attribution,and then link to the whole thing at the end. It discusses the lack of support that KDE3 is getting upstream. At one point, someone makes a shocking conclusion?
So realistically, KDE 3 devotees have to accept it’s going to disappear
unless someone does a fork, of which there is no sign,
& have to find alternatives, which seem to be available or almost.
YIKES! He said the F word! Really is it really true? In 2008, Aaron Seigo wrote:
Meme 1: What is the future of 3.5?
This year, as with most years since KDE3 emerged, there have been huge deployments of KDE 3 based software. These deployments will not shift for years to come, no matter what KDE4 is. This is because large institutional deployments (government, corporate, educational, etc) typically have 3-7 year cycles (sometimes even longer) between major changes. Patches and security fixes? Sure. Major revamps? No. This alone ensures that KDE3 will remain supported for years. Why? Because there are users. That is how the open source dev model works: where there are users, there are developers; as one declines so does the other. The developers tend to be a step ahead of the users for software that is progressive, but you’ll also find that they have a foot in the here and now too (as well as the past, often).
KDE3 is still open in our svn so that bug fixes, security fixes, etc. can continue to be made. KDE 3.5.x is a rather solid desktop system and really doesn’t need a huge amount of work given what it is today; the work to move it to the next level is what we refer to as KDE4, of course. This means that the efforts needed to put into it aren’t huge to keep it viable. However, efforts that do go into it are welcome.
While the core KDE team will continue to concentrate our work on KDE4 since that is the long term direction of things, it is fully expected that our partners (which include some KDE core team members as employees/members) will continue supporting and even developing on KDE3 issues. The central project will also be around to lend a helping hand with advice and what not; I did that for a person the week before I left for holidays in December, actually, so it’s not wild hypothesis but solid theory.
For those familiar with the open source method, the above probably sounds .. well .. obvious. That’s because it is .. for those familiar with the open source method. We will find in this blog entry that many of the concerns people raise come from not acknowledging how Free(dom) software is created via the open source method.
Well, KDE3 still has a lot of users, probably more than XFCE (Just a guess), but all reports are that it’s not being maintained. so was Aaron only kidding?
The major problem of all of the above is that there’s no one in the KDE team
really using kde3 or its packages.
I think that Aaron Seigo, who, incidentally, has generally been pretty decent in my encounters with him, didn’t anticipate the consequences of changes in the landscape, some of which he helped to bring about. As GNU/Linux becomes increasing accessible and useful to non-programmers, interest by users no longer means interest by developers. It turns out that who the users are is pretty important.
Developers and users have different needs and interests, and I think KDE4 has highlighted these differences like nothing else. Developers are creative and curious, and they need to push things forward, and that’s noble and good. The work that is being done on KDE4 is, in my opinion, necessary and important, but one important reason why it’s necessary is because KDE3 could not be taken forward. In a limited, real-world way, it’s “perfect”. That’s a good reason to start a new project, but it’s a terrible reason to discard the old project.
I would like to be able support the important and necessary work that is being done on KDE4 without losing KDE3 forever. Does that mean a fork? Well, what is a fork?
I think the definition of a fork needs to be downsized a little. If we like what we have, and we just want to hold onto it, this should be such a huge endeavor. If a fork is nothing more than a KDE3 community taking responsibility for KDE3 remaining secure and viable, I say: hell yes. Okay, make that “maybe”, but a definite maybe. Hell, maybe!
Hey, I don’t really know anything about it, but I get the sense that rewriting KDE3 with QT4 is a pipe dream, a red herring, a fool’s errand, a mcguffin. (I have a few more, if you like.) Some people keep reminding us that QT3 is no longer supported by… oh, I forget, whoever it is that used to support it– but let’s remember that QT3 is free software, so no one entity gets to decide if KDE3 is dead or alive.
No one who is a developer is very much interested in KDE3, and that’s only natural. Indeed, the KDE team is tired of hearing about KDE3 and frankly, I can’t blame them. (But I’m pretty sure that if KDE3 is simply allowed to die out with a plurality of devoted users, they will NEVER hear the end of it.) Forking could simply mean no longer looking to the KDE team to take care of our needs, like grownups or something. Since we’re light on developers, it may mean paying someone, in money, to take care of our needs. There I go, mentioning the other “F” word: funds. But it may not come to that.
But we don’t need to reinvent the wheel. We just need to keep the tires inflated, and with a nice tread.
The fear has been that forking KDE will divide the KDE community. Well, I think that’s a done deal. KDE has been forked, the community has been divided, and you did it. You had good reasons for doing it, no choice really. In a limited, simple way, KDE3 was pretty close to perfect. That means it would be a tragedy to let it die, but it also means that a bold new direction was pretty much required. Free software was invented so that programmers could be creative, and without that initiative, I’d be posting this blog through an Internet Explorer window. You developer guys are heroes, and let’s face it, if there was no KDE4, you would have probably broken KDE3 by now. A mathematician might argue that no one really made the decision to fork KDE, that it happened on its own, the way a fork in a river is formed.
Links: The Gentoo forum discusion:
Aaron Seigo’s blog