KDE Hopes for a Flood of Ideas
A project that has no goals — no bugs to fix, no features to implement — has only stagnation to look forward to. The best prevention for this kind of stagnation is an active community of users who are quick to share what they want with the developers — even if there is the occasional users vs. devs feature stalemate. The KDE Project has no shortage of community-contributed ideas, and to keep the concepts flowing freely, the powers-that-be have implemented a new feature of their own: A designated section of the KDE Community Forums christened The "Brainstorm" Forum.
What exactly will be taking place in this special forum? A mix of things really. The initial step will resemble a digital suggestion box, with users encouraged to post their hopes and dreams — well, alright, most desired features — which will then go into a moderation queue. Forum staff will perform a triage of sorts, reviewing all submissions and removing duplicates, spam, and such — though not explicitly stated, one presumes removals will be limited to such "clutter" and will not involve decisions on legitimate requests. Once a request has been approved, it will move to community voting, where other members of the KDE community will have the opportunity to support or oppose the feature request — within the bounds of the community's Code of Conduct, of course.
At regular intervals, the most-supported requests will be passed to the KDE developers for consideration. Of course, whether the feature is implemented will still hinge on the availability of a developer to code it and the willingness of the developers as a whole to permit it. However, by organizing feature requests apart from the developers — rather than mingling them in a bug-tracker — the community reduces the administrative workload on its programmers, providing them with more time to code the requested features.
Moreover, having an organized system of community voting will make the community's wishes much clearer, and perhaps reduce the number of features doomed to the dreaded "wontfix" pile. It's easy enough to toss aside something with supporters measured in single digits; it's altogether another when it's double-digits — in percentages. After all, if enough users want something, they'll eventually get it, one way or another.
For now, the system is being described as a "first public test run" — a beta, if you will — and all KDE users are encouraged to visit the new forum, try it out, and share their thoughts on the process. A reminder, though, from those powers-that-be: The Brainstorm is for feature requests only — crashes, crunches, and other miscellaneous catastrophes should continue to be fed to Bugzilla.
Justin Ryan is a Contributing Editor for Linux Journal.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Designing Electronics with Linux
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Kernel Problem
4 hours 24 min ago - BASH script to log IPs on public web server
8 hours 51 min ago - DynDNS
12 hours 27 min ago - Reply to comment | Linux Journal
12 hours 59 min ago - All the articles you talked
15 hours 23 min ago - All the articles you talked
15 hours 26 min ago - All the articles you talked
15 hours 27 min ago - myip
19 hours 52 min ago - Keeping track of IP address
21 hours 43 min ago - Roll your own dynamic dns
1 day 2 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
My idea: No more KDE!
This is a rant! :)
Before the arrival of KDE4x I had used KDE for about 10 years non-stop on different distros, and no intention to change. At work I am looking after 50-60 (development) linux desktops, and could mostly rely on, that when you updated the machines the functionality would be roughly the same.
The update to KDE4x came as a shock, and we had user questions/complaints to no end. One week we decided to bite the bullet. While some users actually quite appreciated the eye-candy, but when it came down to taking part of the systems performance, many got stroppy, because they could do the work no longer the way they used to. There were also issues and comments about the interface intuitiveness or the lack thereof. So finally we decided to do without KDE, and for me it was a sad day. From my point of view it looks like great effort by the KDE developers, but straight over the heads of my users, so it appears.
Within 1 week we migrated all machines to Gnome and installed from there Xfce. Contrary to Gnome and KDE, Xfce does not come with a lot of applications, but it looked robust and functional enough to satisfy our needs. The application problems we solved by installing desktop-independent substitute tools, with functionality comparable to the old KDE35. Wow, its been a bit of a ride, but so far we are going strong.
To the KDE-folks: whatever the problems with KDE3.5 were, to my users they appeared to have been smaller than the issues with the new desktop.
My idea for the KDE devs: next time you intend to radically change the user interface, give the users a choice, in case they think there wasn't so much to improve on in the first place.
My idea
My idea for you, since you are obviously a sysadmin for a large company is this: why the deuce did you decide to update to KDE4 despite all of the messages you, as a professional, _must_ have had before 4.2 was released which was, clearly, announced as the first release of KDE4 for the majority of end users. Which it simply is. If offers compelling advantages over any other desktop environment. KDE 3.5.10 was only released last year, in August.
You were using Fedora, perhaps? And blindly updating to the latest version whenever it came out? You failed as a professional, really. And now you take a completely unrelated news item to trot out the same tired, uninformed rant that's been posted all over the internet by a smallish group of people who should have know better, could have know better and frankly, must have known better: I don't believe their protestations of ignorance for one moment.
Because of your lack of professionalism, dear Anonymous, you have saddled your users with an inferior working system.