Distributed Bugs-R-Us

I have a decent idea for an open source application. This could be one of the most important pieces of software to assist open source in a long time. I don’t have ideas often for software apps but when I do, normally they’re good ones.However, I don’t have the expertise to program this either. The only thing I have is an idea for bugtracker software…and it operates on the distributed journalism model of digg.

The idea was inspired by the article “10,000 bugs away from World Domination“, specifically these few words:

“My diagnosis is that the problem with Linux is that it doesn’t have anyone pushing to get the newbie bugs fixed first. At Microsoft, we had Program Managers and one of their responsibilities was to be customer advocates to prioritize the bugs for the devs to fix. In many open source groups, it sometimes appears that bugs get fixed when the dev decides to work on it, not because an important user scenario is broken. The Wi-Fi tool was broken in Gnome for any months, but the bugs just sat there languishing in the database. Microsoft or Apple would not have shipped a Wi-Fi UI that was completely broken in that way.”

The author is 100% correct. And since open source communities don’t have program managers that can focus the time needed to prioritize bug fixes, we can make the community become that program manager. Read on for specifics on how to do this.

Continue reading “Distributed Bugs-R-Us”

Fan the Linux Flames

Anyone who knows me knows that I HATE inefficiency. If I find a new way of doing things that eliminates the resources I spend doing that thing, I pounce on it. So when I ran across a nifty little program that makes life managing my two linux boxes easier, I pounced. The tool I’m speaking about is called “Fanterm” and it makes managing a limited amount of Linux boxes a snap. I had forgotten that I had installed this and when I brought up my second Linux box (upgrade motherboard) I remembered reading about it on the web somewhere. A quick google search refreshed my memory…although this article only talks about fanout. Fanterm really brings a powerful tool for smaller network system admins.

So what does it do? It’s pretty easy and straightforward. After you download & install the necessary files, open up an Xterm and use the following syntax to parse your command:

fansetup onemachine anothermachine user@yetathirdmachine

The command above opens up 3 xterm windows in addition to the local one you opened up. Now you type your command in the original and watch as the command is mirrored in the other xterm windows. Making quick changes to smb.conf files works like a top. If you want to know the uptime of all your systems, you’re set. This makes managing a limited number of linux boxes a snap…apt-get update; apt-get upgrade anyone? The thing I like most about it is that I get to SEE what happens on each computer…that way if something goes haywire, I’m not executing a command on a file that doesn’t exist on the remote linux box.

Make sure you give this tool a go, it makes life much easier in small networks. Hope it comes to be as useful to you as it is to me.

ITWire in Australia on the Desktop

The point of all this is that from the standpoint of a new Linux user, having a snazzy looking interface is all well and good but it means nothing if users have to revert to the command line to perform what should be simple tasks. Installing new downloaded software is one of the most common tasks performed by desktop users at home and in small offices. Until the Linux suppliers can make this task trivial, they will continue to miss out on a whole world of users beyond the command line geeks.

NOTE: I normally don’t re-publish news like many of the “blogs” you see out there but in this case the article was pretty good and hits home with a theme I’ve been stating a bit lately.

The article above was taken from ITWire…IT News in Austrailia.

This article was a good read and I believe it to be true. Until Linux can come up with ways to make the user oblivious to what is going on underneath the GUI, it won’t make inrroads to the desktop.

UPDATE: 3/2007

Penguin Pete, the not famous blogger over at penguinpetes blog flagged this post as being the main reason that he no longer posts links to my blog. Interesting in that if anyone were to read this post out of context, they might not know what I was driving at for this post. The main intention of the post is to show that new users need to first feel comfortable in their OS before they drop down and get dirty with the shell. That’s a fact jack. Nothing is going to sway that…I’ve had many users I’ve switched over DESPISE dropping to the shell and cite that as the main reason they go back to Windows. This is what I was agreeing with in this instance…that New Linux users need to be semi oblivious to what is going on underneath and not have to worry about it in their beginnings…not to ‘dumb down’ Linux or remove functionality underneath it.

Of Vista, Linux, and the User Experience

I was reading this article earlier this week and thought that it was interesting. It announced the Windows Vista release as being delayed. I thought that this was just par for the course and something Microsoft always has done and will always do…delay. However, what does this mean for the Linux desktop? Does it mean anything at all? Probably not on the scale most are hoping.

It’s Opportunity, Albeit, a Small One

Does anyone else here smell that? It’s opportunity. Perhaps an opportunity to push Linux just a little while longer and to develop it into what it needs to be before Microsoft once again proliferates itself onto every PC in America and sets the standard to which all things are compared. I can just see it when Vista finally does release…all of the comparison articles that will sprout across the web between Vista and desktops such as Ubuntu and SuSe 10.X. Linux can gain ground only one way; if it can become about user experience versus user function. If it can do that, I think Linux just might gain some ground. Babysteps…that’s what it is all about.

Microsoft’s OS has always been a rip-off of the work others do. OS/2 did things before Microsoft…Macs did things before Microsoft. They’ve been playing constant catch up since Windows began. If developers and users seize this opportunity in Linux to develop their distros in new ways, it can give Linux a slight foothold onto the desktop. Notice I said slight foothold. That’s because Linux will never storm onto the desktop. It will chip away slowly at the desktop until it gains acceptance. Linux has been granted a small door to the desktop and there is a set criteria for those distros that want to go through it. Will your favorite distro be able to go through the door? Can it provide the user experience needed to win people on the desktop over?

Continue reading “Of Vista, Linux, and the User Experience”

Why Ubuntu isn’t for New Linux Users

I was getting a bit tired of saying the same things over and over to friends on the net. I was getting tired of repetitiously posting in forums the same sentiment over and over. Yet, just like getting a second wind in a long and tiring race…my tiredness melts away and I find myself feeling refreshed and anew. What the subject of this rant has to say and what I have to say in the paragraphs below are NOT written to start a flame war. I am a user of Ubuntu and a strong supporter of all Debian based distros. This article is written to allow insight into where I believe Linux needs to go to succeed. I’m not out to win any popularity contests…I’m not out to garner a bunch of page hits to generate ad revenue. I’m just out to help the Linux community and rant a bit when I find a subject that strikes a nerve. The subject at hand is Why Ubuntu is NOT New Linux Users.

Continue reading “Why Ubuntu isn’t for New Linux Users”

The PII 350 MHz Computer Dies?!

I always hate to send hardware off to that big chipyard in the sky. However, the PII 350 MHz PC decided to give up on me. Perhaps that is why I was getting so many errors while attempting to install various distros of Linux (including those optimized for old PCs). So, for those of you that were following along with my little journey, the PII is no more…too many errors began to pop up even in steady Slackware. I made a judgement call and retired the motherboard.

In its place, I forked out 23 bucks for a PC Chips Socket A motherboard. I then slapped in a spare XP 2600 and I have the newest flavor of SimplyMEPIS and PCLinuxOS installed. It’s running like a champ and is turning out to be the best 23 bucks I’ve spent in some time. For those that want a steady board for Linux, check Newegg here.

Alas, the PII was a good board. I knew it well. So glad I didn’t have to put it down and that I could gracefully retire it on a good note. Now the slowest PC I have is the CentOS 4 gateway/firewall with a Celeron 900 (Emachines w/ a refurb Gateway mATX mobo). Works great. Sorry I couldn’t finish out all those other distros.

In the meantime, I’ve made it my mission to document some really simple things using KDE and Gnome (How-Tos) for stuff that you’d normally do in Windows. I’m attempting to track down the easiest way to setup an anonymous share using KDE and Samba (with no smb.conf or smbpasswd or smbuser alteration…no shell). Thus far this has proved quite challenging. Getting Samba to play nice without passwords and users with full write access on a share is murder. If anyone has tips or links to a great how-to, I’m all ears. Thanks for reading.

Creative Commons License
Except where otherwise noted, the content on this site is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.