Sorry
Sorry for the spate of posts. I just discovered that a bunch of old posts were never actually posted, and posted them, posthumously.
Sorry for the spate of posts. I just discovered that a bunch of old posts were never actually posted, and posted them, posthumously.
Absolutely hilarious.
Okay, bad as I feel about the results of the elections here in America, I’m not leaving because I’m in fear of my life. Puts things in perspective. Maybe there’s hope for America yet.
Bravo for Intelligent Design! Honor to the Flying Spaghetti Monster!
Apparently, the Supreme Court has sided with MGM against Grokster. The key part of the ruling, which I hope comes through in other court rulings, is that Grokster was promoted as being used for copyright infringment. This means that devices promoted soley for thier legal uses should be exempt from this ruling. We’ll see if this is the end of digital recording divices as we know them, or if it ends up meaning nothing. I suspect the little guys will vanish, as they get sued into oblivion, and the big guys will ignore it.
Score one of big business against the little people.
Why should I care about Gnome/KDE integration? Seriously. I haven’t use a KDE app in years, and have no real need to do so now, especially considering the killer Gnome apps that the Novell folks are churning out. Gnome has good infrastructure, KDE has good infrastructure, they don’t really need to share. If too much infrastructure is in common, then there’s no real difference between the two, and either the KDE users have to deal with KDE being like Gnome, or I have to <shudder> deal with Gnome being like KDE.
Sure, as fd.o infrastructure matures (such as DBUS), it may be better than what Gnome/KDE are using now, and will be used. But, I like the Gnome apps, and couldn’t care less if I can cut-and-paste video with KDE apps. Seriously.
I never understood this desire to unify Gnome and KDE. They provide different looks and feels, in different ways, and that’s good, as far as I’m concerned. If I was forced to use KDE, I might as well use OSX or Windows.
Morgan will eat anything, and I mean anything. She loves the taste of my beer, even my stouts. She enjoys capuccino. Spicy thai chicken? Down the hatch. Tomatos, fruit, pickled bologna, cheese, whatever we eat, she loves it, even things I don’t like or things Janette doesn’t like. Down the hatch!
Well, we’ve finally found something she won’t eat: tofu. I got a peanut sauce noodle bowl that has tofu in it, and, since I don’t eat tofu, I thought I’d try Morgan. Well, she spit it out, for the first time ever. Good taste, Morgan!
Well, I just added evince-0.3.1 to the tree. And there was great rejoicing. Took me much to long to figure out why the dvi use flag wasn’t, in fact, enabling DVI support. Turns out, evince depends on kpathsea, which is part of tetex. Ah, well, it’s all sorted out now, and everything appears to be wonderfully happy.
I think you’re missing a couple of things.
First, for many of us, writing documentation is hard. I know it is for me. I write, and it comes out crap. I rewrite, and it’s only slightly better. I work and slave, and spend tons of time, and it never gets better than “decent.”
Second, and partly related to the first, many of us find writing documentation to be less than fun. Personally, I hate it with a passion, and the worst part of any project at work is writing the doc parts of it. I never liked writing in school, and I don’t like writing now.
Third, writing documentation for Open Source projects requres a fair amount of technical ability and a fairly deep knowledge of the software being documented. This generally narrows down the list of people who have the knowledge to write good docs to those who also have the ability to code. And, for the overwhelming majority of us, coding is much more fun than docs. So, we code.
I think maybe a solution is to encourage people to become doc people, rather than devs. Sort of like the AT program, mentor people into the doc program. If there were enough people who could clean up and polish my docs, I might be more interested in whipping up a technical description of something, which would be crap (see point one above), and passing it on to someone who can actually write.
In general, FOSS has been about scratching itches, and the doc itch doesn’t seem to be scratched as much as the code itch. I know, in my case, if worst comes to worst, I can read the code.
Added totem-1.0.3 to portage, and added the xv USE flag to it and totem-1.0.2-r1 to protect the dependency on gst-plugins-xvideo. This is only my second gnome herd commit (and my first with foser’s blessing), but I’m making progress.