Feeds:
Posts
Comments

Archive for the ‘gnu/linux’ Category

The personal always trumps the general. So, for me, the big news this morning is not the continuing speculations about whether a Microsoft takeover of Yahoo! would be competition for Google, but that Joe “Zonker” Brockmeier has been appointed community manager at the openSUSE project.

I’ve only met Zonker face-to-face once. It was back in 2001, when I was at the New York LinuxWorld Expo on behalf of Progeny Linux Systems. Progeny was sharing a booth with Maximum Linux magazine, and Zonker came around to ask if the company had any openings for technical writers (it didn’t). But in the following years, I came to recognize him as one of the half dozen or so best professional writers in the business. Then, for large chunks of 2006 and 2007, I interacted with him daily on Linux.com’s private IRC channel, where he went under the nickname of jzb. So, as happens on the Internet, I likely have the impression that I know him better than I actually do.

I suspect that jzb may not completely appreciate what I have to say here, but I hope that openSUSE appreciates what they’re getting. They’re getting a worker so dedicated that he makes me feel like a slacker – and I might as well be chained to my computer desk. I used to joke that Linux.com would fall apart if he ever got a life, and, although that’s not true – as we learned when he left last September to become editor-in-chief at Linux Magazine – it’s true that the channel has been quieter and not as much fun since.

So what else can openSUSE expect? They can expect a sarcastic wit that is acute without being nasty, and a thorough knowledge of science fiction and alternative music. They can also expect a sympathetic ear in private. Perhaps, too, they should expect some surprises, such as Linux.com’s last year when we discovered that he had been half of a long distance, intra-office romance for months without any of us suspecting.

But, most of all, they can expect someone who lives and breathes free software, and is more current about what’s happening in the community than anyone I’ve encountered (he used to regularly claim story assignments before I could, and, while he was aided by being two hours ahead of me, that wasn’t the only reason he consistently scooped me. I swear the bastard never sleeps).

I have no ambitions to be editor-in-chief or a community manager, and I would have personal reservations about working at Novell after its pact with Microsoft, so I can say without envy that I wish him nothing except success. I know that he has definite ideas about how to do things, and I suspect that, before he finishes, openSUSE will be a more organized and better known part of the community. And, for his part, I hope that being community manager is the position he’s been looking for.

The only thing I worry about is whether this is another setup by jzb, like those I’ve been the butt of in the past. You see, my comments about conspiracy theories have already caused some of the foaming mouth brigade to denounce me as secretly pro-Microsoft. By joining Novell, is Zonker arranging things so that Linux.com and Linux Magazine will be added to the Axis of Evil? After all, between the two of us, we must constitute a positive trend according what passes for logic in those circles. And is jzb sitting down in Florida, laughing about it?

You know, I wouldn’t put it past him – even if NOAFD (Not on a First Date), to use an acronym that he helped to coin and made into a punchline on IRC.

Read Full Post »

The fallout from my blog entry, “Conspiracy theorists and free software” continues. With all the people baying for my blood – some of whom, frankly, sound disingenuous in their demands for proof – the entry could easily take over my life, so in the last couple of days, I’ve withdrawn from active discussion of it. Frankly, the discussion is not that interesting to me, and (mercenary soul that I am), if I’m going to participate in more than my courtesy two email exchange with people, I’m going to get paid for doing so. And probably I will in a couple of weeks. Meanwhile, since I have an unexpected free half hour as I wait for a call to be returned, I’ve been reflecting on the various reactions the piece received.

To start with, I notice that Brian Profitt’s suggestion that I was lashing out at some negative criticism I received has been seized on by some commenters as a reason to dismiss what I said. However, although that was a shrewd suggestion on Brian’s part, it’s only true to the extent that the entry was inspired by someone asking me what I meant by conspiracy theory. Going into my fourth year as an online journalist, I long ago became immune to the insults and accusations of bias from both sides that often threaten to overwhelm thoughtful responses and legitimate corrections of mistakes. In fact, I maintain a page on my web site where I list choice bits of abuse for visitors’ amusement. I may sometimes respond, but I’m not much interested in flame wars. I have an anarchistic temperament, and, so long as I have my say, I’m perfectly willing to let others have theirs, even if theirs don’t have a lot of love for me.

That’s not to say that I don’t find people’s reactions fascinating – and more than a little intellectually distressing, since I’m an ex-university instructor who once spend his days trying to help people develop their abilities to argue coherently. A surprising number of people leaped to the conclusion that, despite a clear statement to the contrary, I was only talking about attitudes towards Microsoft (perhaps because I recently wrote an equally misread article that suggested that, since the free software was strong enough to defend itself, we could be wary of Microsoft without being paranoid). Even more seem to think that proving that there were reasons to distrust Microsoft in some way validated the attitudes and styles of arguments that I was condemning. Many, too, do not seem to believe that it is possible to mistrust corporation or organization without expressing unrelenting hate for it.

Clearly, what people brought to their reading was as important – and, in some cases, more important – than what I wrote. That’s their right, but, as I’ve often lamented in the past, if someone wants to disagree with me, I wish they would at least disagree with what I actually said, rather than what they imagine I said. At times, people seem to be arguing with their own reflections to such an extent that I feel extraneous to the process.

But I think my favorite response was from a commenter who assumed the responsibility of giving me elementary advice about how to write. I’m always willing to learn, but, considering that last year I sold roughly a quarter million words about free software, now I know the spirit in which Lauren Bacall responded a few years ago on hearing that she had been voted one of the sexiest elderly women in film. “That will certainly pep up my career,” she said (or something to that effect). “I can’t wait to tell my agent.” While not at the top of my profession, I’m not at the bottom, either, so I can’t help but be bemused by unasked advice from an unknown and relatively unproven writer — especially when I personally wouldn’t give writing advice unless specifically asked.

However, the most troubling thought to me in all the reactions is that I’ve apparently lost my anonymity online. This blog is modestly successful, but its readership is generally many times below what an article on Linux.com or Datamation receive. I thought it useful as a sandbox, a place to express my thoughts-in-progress without any fuss. If anything, I expected to get a few responses from friends and acquaintances.

But, as readers of the entry rise into the thousands, I realize that I was naive. Regardless of what merits I do or don’t have as a writer (and nobody could be more critical of my work than me, believe me), apparently some people do notice what I have to say about free software. Some of them may hate it, but they notice. That’s a humbling and frightening thought (and leads me to mutter repeatedly about the blind leaning the blind).

Even more importantly, it means that, unless I start writing under another name, I have to assume a greater responsibility for what I write publicly. No more working out of ideas publicly for me – from now on, I need to make sure that I state my assumptions clearly, and address opposing views in more detail, and not publish on certain subjects until my ideas are fully developed. People are still going to make invalid inferences, no matter what I do, but I feel the responsibility all the same, even while I tell myself that I’m being arrogant in feeling the obligation.

In a week or so, perhaps I’ll revisit the topic. Meanwhile, thanks for everyone who has commented or blogged in response. It’s interesting, and I’ve learned, even though I don’t have the time to respond in detail to everyone.

Read Full Post »

Today, I had the new experience of helping out with a podcast. Like most people, I hate hearing my voice (it always sounds clumsy and over-precise), and any wishful belief in my own eloquence wilts when I hear all the “ums” with which I punctuate my speech, but I hope I have the chance to take part in another one.

I could hardly be excluded from this one. After all, it was an article I published a few weeks ago, “GNOME Foundation defends OOXML involvement,” that sparked the podcast. Moreover, when Jeff Waugh of the GNOME Foundation first floated the idea, he had me in mind as a neutral third party, and I was the one who pitched the idea to Linux.com, the main buyer of my articles. Admittedly, it was an easy sell, since Robin Miller, the senior editor at Linux.com, is a part time video producer and always looking for ways to extend the print coverage on the site, but I was still the one who got things moving.

After stumbling into the center ring while technical problems occupied Robin and Rod Amis, the producer, and stuttering into the silence, I soon found my tongue. The experience was not much different, I found, from doing an ordinary interview or teaching a university seminar. In all three cases, your purpose is not to express your own opinions, but to encourage others to speak, and to clarify their vague references for the sake of listeners. The fact that there was an audience of about 650 – good numbers, Rod tells me, for a daytime podcast – didn’t really affect me, because I had no direct contact with them.

Jeff Waugh and Roy Schestowitz, the two guests on the podcast, have been having bare-knuckle arguments on various forums, so I was expecting to have to referee the discussion. In fact, the image kept occurring to me of those soccer referees who are sometimes chased off the field by irrate crowds. However, the slugfest I expected never materialized. It’s harder, I suppose, to insult someone verbally, even over the phone, that to fan a flame war on the Internet, and both were more polite live than they had ever been at the keyboard.

Besides, Robin has the voice of someone calmly taking charge without any expectation of contradiction. Perhaps, too, an echo of my old university instructor voice ghosted through my own words.
But, whatever the case, everyone survived. I even think that the increased politeness influenced both Jeff and Roy to make concessions to each others’ viewpoints than they never would have considered online. As a result, I think that the point that the dispute is one of tactics rather than of different goals came through for the first time in the month or more that this dispute has been unfolding. However, I’m not sure that either of the principals has made the same observation.

The show had glitches that better planning might avoid next time. However, I like to think that both sides had a reasonable chance to express themselves, so it could have been worse. The Linux.com regulars are already discussing the possibility of another podcast, and I, for one, can’t wait.

Read Full Post »

Last week, ABC’s 20/20 ran a piece on the murder trial of Hans Reiser, the free software developer accused of murdering his wife in Oakland. I sighed in relief when it ran, because it didn’t include me.

It could have. Since I wrote one piece last year about Reiser’s problems with getting the Reiser4 filesystem accepted into the Linux kernel and another about what was happening with his company in the wake of the murder charges, I’ve fielded eight or nine requests from the mainstream media to talk about the background to the case. Since early summer, several of those requests were from ABC. But I never really felt comfortable doing so, although I made clear that I had no opinion one way or the other about the case, and only talked about Reiser’s work and reputation and what the free software community was like.

At the time, I rationalized my general comments as helping out other journalists. Also, considering that I’ve made a career out of explaining developers to non-developers, I figured that I might be able to see that the community wasn’t too badly misrepresented. And, let’s be honest, I was flattered.

But, simultaneously, I was uneasy, and this uneasiness continued to grow as ABC continued to talk to me. There was even talk of flying me down to San Francisco for a day to do an interview, which provoked a kind of Alice in Wonderlandish feeling in me. Spend the day travelling for something that I wasn’t that interested in? And going to San Francisco – one of my favorite cities – with no time for wandering around struck me as not worth the sense of self-importance such a trip would no doubt give me.

I tried suggesting other people in the free software community that ABC might contact. I even suggested one notoriously egotistical person, figuring that they would be pleased to be asked and would give ABC so much copy that its reporters would have no further need of me.

That only worked for a few weeks, then I received another phone call. At that point, I realized that I didn’t have a valid passport, which Canadians like me now need to fly to the United States. I explained this difficulty to a reporter, and how I didn’t really want the extra hassle of driving across the border and catching a flight in Bellingham – and he returned the idea of flying a camera crew up to Vancouver to talk to me.

I thought that unlikely, so I said that would be acceptable. For a while, I was worried that ABC might actually do it, too, but in the end the producers decided not to bother.

That was just as well, because in the interim, I had resolved to refuse the interview regardless of the condition. I took a while to understand my reluctance, but, what I concluded in the end was this: I didn’t want to feed my self-importance at the expense of the Reiser family. No matter what actually happened, those involved in the case are in a world of pain, and I didn’t want to piggyback on that pain for petty personal reasons.

And, ultimately, my reasons would be personal. No matter how well I can explain the free software community to the public, I’m far from the only one who can do so.

With this realization, I felt such relief that I knew that I had made the right decision. Now, I only hope that I can remain as sensible if someone contacts me about the case again.

Read Full Post »

Today, I received the following e-mail. At the sender’s request, I have removed any personal details:

I was wondering if you had any advice for me about how to perform some marketing/pr for my Linux [project]. I’ve started doing interviews with developers and I have created a community news site.

But is there anyway I could possibly get [my project] mentioned in a
magazine like Linux Journal? Is there any free advertising I could take advantage of on certain web sites? I thought you may have some ideas for me because you have experience with this kind of thing. Any help you
could provide me would be appreciated.

I generally receive about 3-4 requests of this sort a year, so I decided to post my reply here, so I can refer others to it:

You’re not likely to find free advertising on sites that will do you any good, so your best bet is to try to get on the various sites as a contributor. Linux.com only takes original material for its main features, but it does have the NewsVac items, the three or four line link summaries on the right of the page that are very popular. And, of course, sites like Slashdot, Digg, and Linux Today are all about links to already published material.

If you have a solid piece of news — which for a piece of free software usually means new releases and unique features — at Linux.com you can pitch a story and write it yourself. However, you’ll be asked to include a disclaimer
that explains your connection with your subject matter, and the article will be rejected if you are being a fanboy. That means you can’t review your own distro, but you might be able to do a tutorial on a distribution’s packaging system, for instance.

Alternatively, you can send news releases in the hopes of convincing either an editor or a writer to cover your news. However, don’t be pushy. Submitting a news release once is enough, and popping back several times to ask if it was received or whether anyone is interested will probably only guarantee that you’ll annoy people so that they won’t cover your news no matter how big it is.

The ideal is to build up an ongoing relation with a few writers, in which you give them stories to write about — we’re always looking — and they give you the coverage you want when you have news that readers might want to hear.

Of course, you open yourself up to negative comments if the software deserves them, but that’s the chance you have to take. However, for the most part, both commercial companies and large community projects find the
risk well worth taking. It’s not as though any of the regular writers deliberately sit down to review with a determination to be negative (although, conversely, they don’t set out to praise, either: We’re not just fans, either).

This process doesn’t happen overnight, so be patient. But, in the long run, you should get some of the publicity you seek.

I don’t know whether this information is useful to others. To me, it seems that I’m saying the obvious, but part of that reaction is undoubtedly due to the fact that I deal with these things daily. Perhaps to others, these thoughts aren’t obvious, so I’m hoping that someone will find them useful

Read Full Post »

Long ago, I lost any queasiness about the command line. I’m not one of those who think it’s the only way to interact with their computers, but it’s a rare day that I don’t use it three or four times on my GNU/Linux system. No big deal – it’s just the easiest way to do some administration tasks. Yet I’m very much aware that my nonchalance is a minority reaction. To average users, the suggestion that they use the command line – or the shell, or the terminal, or whatever else you want to call it — is only slightly less welcome than the suggestion that they go out and deliberately contract AIDS. It’s a reaction that seems compounded of equal parts fear of the unknown, poor previous experiences, a terror of the arcane, and a wish for instant gratification.

Those of us who regularly try two or three operating systems every month can easily forget how habit-bound most computer users are. The early days of the personal computers, when users were explorers of new territory, are long gone. Now, the permanent settlers have moved in. The average computer user is no longer interested in exploration, but in getting their daily tasks done with as little effort as possible. For many, changing word processors is a large step, let alone changing interfaces. And both Windows and OS X encourage this over-cautious clinging to the familiar by hiding the command line away and promoting the idea that everything you need to do you can do from the desktop. The truth, of course, is that you can almost always do less from a desktop application than its command line equivalent, but the average user has no experience that would help them understand that.

Moreover, those who have taken the step of entering cmd into the Run command on the Windows menu have not found the experience a pleasant one. DOS, which remains the command line that is most familiar to people, is an extremely poor example of its kind. Unlike BASH, the most common GNU/Linux command line, DOS has only a limited set of commands and options. It has no history that lasts between sessions. Even the act of navigating from one directory to the next is complicated by the fact that it views each partition and drive as a separate entity, rather than as part of a general structure. Add such shortcomings to the ugly, mostly unconfigurable window allotted to DOS in recent versions of windows, and it’s no wonder that DOS causes something close to post-traumatic stress syndrome in average users. And, not having seen a better command line interface, most people naturally assume that BASH or any other alternative is just as stressful.

Yet I sometimes wonder if the main reason for nervousness about the command line isn’t that it’s seen as the area of the expert. In recent years, many people’s experience of the command line is of a sysadmin coming to their workstation, opening a previously unsuspected window, and solving problems by typing something too fast for them to see from the corner into which they’ve edged. From these encounters, many people seem to have taken away the idea that the command line is powerful and efficient. That, to their minds, makes it dangerous – certainly far too dangerous for them to dare trying it (assuming they could find the icon for it by themselves).

And in a sense, of course, they’re right. In GNU/Linux, a command line remains the only interface that gives complete access to a system. Nor are the man or info pages much help; they are often cryptically concise, and some of the man pages must have come down to us almost unchanged from the 1960s.

The fact that they are also wrong is beside the point. Many users aren’t clear on the concept of root accounts, file permissions, or any of the other safeguards that help to minimize the trouble uninformed users can blunder into.

The trouble is, understanding these safeguards takes time, and investing time in learning is something that fits poorly with our demand for instant gratification. By contrast, using a mouse to select from menus and dialogs is something that people can pick up in a matter of minutes. Just as importantly, the eye-candy provided by desktops makes them look sophisticated and advanced. Surely these signs of modishness must be preferable to the starkness of the command line? From this attitude, insisting on the usefulness of the command line is an anachronism, like insisting on driving a Model T when you could have a Lexus.

The truth is, learning the command line is like learning to touch-type: in return for enduring the slowness and repetitiousness of learning, you gain expertise and efficiency. By contrast, using a graphical desktop is like two-fingered typing: you can learn it quickly, but you don’t progress very fast or far. To someone interested in results, the superiority of the command line seems obvious, but, when instant gratification and fashion is your priority, the desktop’s superiority seems equally obvious.

And guess which one our culture (to say nothing of proprietary software) teaches us to value? As a colleague used to say, people like to view computers as an appliance, not as something they have to sit down and learn about. And, what’s more the distinction only becomes apparent to most people after they start to know their way around the command line.

Whatever the reasons, fear and loathing of the command line is so strong that the claim that GNU/Linux still requires its frequent use is enough to convince many people to stick with their current operating system. The claim is no longer true, but you can’t expect people to understand that when the claim plays on so many of their basic fears about computing.

Read Full Post »

My review of the latest release of Ubuntu was picked up by Slashdot this week, releasing a flood of criticism.

Although the article praised Ubuntu, it was also one of the first to mention some of its shortcomings, so it probably provoked more reaction than the average review. Much of the criticism was by people who didn’t know as much about a subject as they think they do, and even more was by people who had either misread the article or not read it at all. But the comments I thought most interesting were those who criticized me for suggesting that in some cases Ubuntu made things too simple, and didn’t provide any means for people to learn more about what they were doing. Didn’t I realize, the commenters asked, that the average person just wanted to get things done? That few people wanted to learn more about their computers?

Well, maybe. But as a former teacher, I can’t help thinking that people deserve the chance to learn if they want. More – if you know more than somebody, as Ubuntu’s developers obviously do, you have an obligation to give them the opportunity. To do otherwise is to dismiss the average person as willfully ignorant. Possibly, I’m naive, but I’m not quite ready to regard others that way.

Anyway, which came first: operating systems like Windows that prevent people from learning about their computers, or users who were fixated on accomplishing immediate tasks? If computer users are task-oriented, at least some of the time, the reason could be that they’re conditioned to be so. Perhaps they’ve learned from Windows that prying into the inner workings of their computer is awkward and difficult. We don’t really know how many users will want to learn more, given the opportunity.

Nor will we, until we design graphical interfaces that give users the chance to learn when they want to. Contrary to one or two commenters, I’m not suggesting that every user will always want to do things the hard way and use the command line – I don’t always want to myself, although I gladly do so when typing commands is the most efficient way to do the task at hand.

But where did so many people get the assumption that there’s such a contradiction between ease of use and complexity, that choosing one means that you forgo the other? It’s mostly a matter of tidying advanced features into a separate tab, or perhaps a pane that opens to reveal features that a basic user doesn’t want.

However, when so many people believe in the contradiction, we’re not likely to see graphical interfaces that are as useful to demanding users as basic ones.

Even more importantly, I suggest that giving users the chance to educate themselves is a corollary of free software principles. If free software is only going to empower users theoretically, then it might as well not do so at all. To help that empowerment along, free software has to provide the opportunity for users to learn, even though few may take the opportunity. Yet, so long as the chance exists that any users want the opportunity, it needs to be offered.

Moreover, I believe that, given the chance, many people will eventually embrace that opportunity. The first time that they use a free software interface, they may be focusing mainly on adjusting to so much that’s new.

However, eventually, many of them will learn that they can do things their own way and take more control. And eventually, surrounded by such choice, many may take advantage of it. If they don’t know the choices are available because their desktop has been simplified until the choices are obscured, then the developers are doing them a dis-service.

Some might say that simplification is needed to attract people to GNU/Linux. Personally, though, I doubt that exactly the same thing they can get on Windows is likely to attract anyone. If free operating systems are going to get a larger market share, then it will most likely be by providing a new perspective on computing. I like to think that new perspective should be attempting to accommodate everyone, not just beginners.

Read Full Post »