Language Selection

English French German Italian Portuguese Spanish

Debian: Call for help from KDE Team

Filed under
KDE
Debian

For quite a while now the KDE team has been severely understaffed. We maintain
a lot of packages, with many different kinds of bugs, but we don’t have enough
people to do all the work that needs to be done. We have tools that help us
automate the update to new upstream releases, but that’s just the tip of the
iceberg of our work and so we are writing to invite more people to get
involved in the team and help us get KDE software in Debian into better shape.

Read more

free desktop environments

I think it is a matter of interest. open source software doesn't lack developers. It lacks interest in working on projects.
Take a look at gnome2. gnome-panel was hardly being developed and people thought gnome project lacked developers. Then gnome-shell was being heavily developed and there were lots of contributions.
Maybe more distributions should contribute upstream.

Desktop environments development

If desktop environments development was to remain stagnant, that would be quite fine because the environments often get in the way of programs (or games). But I guess that what's troubling is applications that stay with old versions of GTK and Qt, or won't patch bugs. I think it's becoming a real problem for both KDE and GNOME, but there are usually new programs arriving to replace stagnant ones (e.g. Konqueror, Thunderbird).

With or without heavy development, GNU/Linux environments are still leading in terms of functionality. For applications, Android is advancing fast.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more