[Note: I wrote this in the LXer.com forum in response to Jeff Hoogland's blog posting on #fedora that was linked to LXer.com. I did spell out "asshat" below, where I did not do that in the forum posting. Jeff's blog item is here, and I would invite everyone to read it first before reading my response below. Or not. It's up to you. Also, I fixed the link to the Eric Raymond/Rick Moen tome that's worth a read as well.]
Truth in advertising disclaimer: Many of you already know that I have been an active participant in the Fedora Project for several years; for those of you who don’t, that secret is now out (and, man, do I feel relieved admitting it!). I have also been a regular in many IRC channels, both Fedora and non-Fedora related, though I am not a regular in #fedora — in fact, I avoid #fedora for the same reasons Jeff outlines in his self-proclaimed “rant.”
That said, Jeff accurately points out a situation that has been a sticking point, and one that is being addressed and corrected, in the Fedora Project around the types of caustic responses that sometimes come up in #fedora. Also, while I don’t frequent the channel and usually find answers to my questions elsewhere — a good practice (and more on this later) — I can say that it’s something that has caused some of us in the Fedora Project some concern.
However — and you knew that was coming — just as an observation on my part, it appears Jeff shot from the hip on this one rather than giving it some thought before writing.
Believe me, I am not casting the first stone against this “sin” — I speak from experience here: lots of experience in which I have fired off unretractable words that a walk in the redwoods or shooting a few hoops would have tempered into something more reasonable and justifiable.
So, Jeff, with apologies, I think your blog goes over the top in the following ways:
a.) #fedora has not cornered the market in asshats by any stretch of the imagination, despite our mutual experience in this particular channel. The cantakerous tards who have an inflated self-worth exist in most IRC channels in every distro across the board — maybe not in Bodhi, if their leader has any say in it (I sincerely hope) — but I think it’s more the nature of things like how IRC operates as well as a wake-up call for the need for change, positive change, in this regard.
b.) It’s a little myopic to judge the performance of a distro by the people “representing” it (and, arguably, any bad experience in any distro-related IRC channel does not accurately reflect the community as a whole, but rather reflects personality flaws in those responding to questions, regardless of whether they’re chanops or not). If that were the case, I would never, ever, EVER use PCLinuxOS, since I have had the same experience seeking information from them that we have had with Fedora (and I do have a box in the lab with PCLOS).
c.) An aside: When I first started using Linux, I was told to read this tome by Eric S. Raymond and Rick Moen: “How to Ask Questions the Smart Way” which lives here:
(You may have to copy/paste the link above — there is no space before the ~ though each posting insists on inserting one)
Why this isn’t a README in all distros is a mystery, but it should be. I am not suggesting that Jeff asked the wrong question here, but often times questions are not asked in the most efficient or direct way. But as Jeff points out in his blog, we don’t know the circumstances that the user is facing in finding out an answer, but it does help immensely to ask the right question. Immensely.
d.) Another aside: I can’t imagine Jared Smith of Fedora or Jono Bacon of Ubuntu firing off a rant like this. As a project leader for what I think is an up-and-coming distro, I hope you understand, Jeff, that as a project leader, you’re in the bigs now and what you say and do reflect on your project for better or worse.
For those of you who have gotten this far, thanks for staying awake. I’ll now put on my Nomex and feel free to flame away.
(Fedora ambassador Larry Cafiero runs Redwood Digital Research in Felton, California, and is an associate member of the Free Software Foundation. He is also one of the founders of the Lindependence Project.)
As the sun makes its way over the Santa Cruz Mountains on a Tuesday morning — don’t forget the Farmers Market and the Organic Software table in Felton, folks! — the daily ritual of dragging myself into a new day begins.
Coffee. A look at the news around the world. Then the important stuff: LXer.com for the news of all things Linux/FOSS.
[Incidentally, our friends at Google need to look at something, and I'll bring it to their attention later. Maybe I'll drop a line to WordPress, too. It seems that no matter how I tag my blog, the only way I can get the Alerts to pick up Larry the Free Software Guy for the benefit of those searching for "Linux" is to put "Linux" in the title. Selfish, I know, but maybe you should get used to seeing Linux in the title of upcoming blogs.]
Meanwhile, back at the blog: Here are a few things that caught my eye this morning:
Antiquated? Phoronix publishes an article entitles “How an Old Pentium 4 System Runs with Ubuntu 10.04, 10.10″ and their description of “old” is, “This antiquated system has an Intel Pentium 4 2.8GHz CPU, 512MB of RAM, an 80GB IDE hard drive, and an ATI Radeon 9200PRO AGP graphics card.” Antiquated? Are you kidding me? That’s about as antiquated as a 2006 BMW. C’mon, Phoronix — either do better editing or give us something really antiquated, like a Pentium with Roman numerals.
Ground-floor opportunity, unlimited potential: The VAR Guy writes about the health care track at OSCON next week in Portland. “The health care sector is set for a technology-driven transformation as the federal government pushes adoption of electronic health records and pursues national health information exchange. Hardly surprising, the Open Source Convention (OSCON) has a health care track that will focus on open EHR/EMR software and the government’s standards-based Nationwide Health Information Network (NHIN) among other topics. What’s in it for VARs? Here are some clues.” And the clues follow. But as those who know me know how I can drone on about this, I think health care software is a huge opportunity for FOSS developers, not to mention making open source inroads in an industry that needs to be in the public domain in the first place, and it’s nice to hear it from someone else.
Oh, and it’s not dead yet: While this wasn’t in the news today, I’ve finally gotten over the eye-rolling aspect of, yet again, SCO not fully grasping basic legal tenets in losing yet another case and now plan to appeal Judge Ted Stevens’ ruling upholding a jury verdict made after oral hearings that Novell had retained the copyright to Unix when it sold its Unix business to SCO. According to this brief item on H online, it’s not over yet and the partners at Boies Schiller & Flexner LLP have taken Stick A to beat Dead Horse B.
Felton Farmers Market, 2-6:30 p.m., St. John’s Church parking lot, about 3/4 mile south of the traffic light on Highway 9 (all the directions you need in Felton). And don’t forget — Major League Baseball All-Star Game is tonight. Go National League.
Monday mornings are not as toxic to me as to others, to hear them tell it. In fact, I have a healthy indifference to Mondays; on a work-week landscape where my first day of the work week at the newspaper is a Thursday, Mondays essentially are my “Fridays.” All of which is to say, that’s not so bad.
Still, coffee would be nice, and while sipping a Kona blend, we can review some of the recent past’s events and articles, like . . .
It’s dead, Jim . . . finally: Novell came up the winner in the SCO case, according to Groklaw, and it looks like this is the end of the line for a one-time tech company turned litigation machine. Judge Ted Stewart ruled that Novell’s claim for declaratory judgment is granted; SCO’s claims for specific performance and breach of the implied covenant of good fair and fair dealings are denied. Denied. Did I mention it was denied? Also SCO’s motion for judgment as a matter of law or for a new trial: denied. Deeee-nyed! So that’s game, set, match. Also, on a personal note, as a MoFo — as in a Morrison & Foerster alum, having worked for the firm in Tokyo — I have to say I’m proud of their work in this case.
Well, duh! Chapter One: Dell, which offers Ubuntu (if you want to wait for it — more on this in a minute), gives those thinking about ordering an Ubuntu machine some reasons for making the switch. While those ordering Ubuntu Dells wait — ask me about ordering one for a client and getting a shipment date in about a month, versus a few days for an identical Windows machine — they can take a look at Number 6 on this list: Ubuntu is safer than Microsoft Windows. You think? Sheesh.
Well, duh! Part Deux: What’s the weak link in the national security in relation to cyber war? Easy question, according to a recent ars technica article: Microsoft Windows. Richard A. Clarke’s new book, “Cyber War: The Next Threat to National Security and What to Do About It,” is still making quite a splash. A quote from the article: “While it may appear to give America some sort of advantage,” Cyber War warns, “in fact cyber war places this country at greater jeopardy than it does any other nation.” The enormous dependence of our financial and energy networks on the ‘Net open us up to potentially devastating online attacks. “It is the public, the civilian population of the United States and the publicly owned corporations that run our key national systems, that are likely to suffer in a cyber war.” Yep, that sounds like Microsoft Windows all right.
What’s that? The sky is falling? It figures that the likes of PC World would take a story involving a relatively obscure IRC server, give said IRC server undue credit for popularity, exaggerate the seriousness of the situation and exaggerate how long it went unnoticed all in one article. But that’s what happened when — HORRORS! — an announcement was made on the Unreal IRCd forum that the Linux version of the popular IRC server Unreal IRCd was contaminated with malware in November 2009, without anyone noticing it. Of course, what the article conveniently fails to mention is that unlike the infections automatically started by the mere presence of Windows, this one had to be downloaded, installed, and configured. That point was glossed over. Another glaring omission: How many in the wild security breaches have there been due to this? I’m not linking to the article — PC World is not getting hits from me — but you can go to LXer and see the article, with responses, if you wish.
I need a refill.