bwh is currently certified at Master level.

Name: Bryce Harrington
Member since: 2000-10-22 06:02:28
Last Login: N/A

FOAF RDF Share This

Homepage: http://www.bryceharrington.com

Projects

Articles Posted by bwh

Recent blog entries by bwh

Syndication: RSS 2.0
Testing, Open Source, and NFSv4

I mentioned a few months ago that NetApp has provided a grant for my NFSv4 testing work, to hire a sysadmin to help build a few server farms for NFSv4 testers to use in analyzing and optimizing the code.

We're looking for an experienced sysadmin/developer in the Portland area who'd like to work on Linux/NFS and other Free/Open Source Software tools and projects. The position is funded to be full time/temporary for 6 months. You'll be a regular OSDL employee, and will have the chance to go to some open source events, go golfing with Linus, etc. ;-)

The work itself involves setting up networks, serial console logging, automating power control and reimaging, setting up kerberos, and creating various bash/perl scripts for operating the machines and so forth. You should know at least the basics about NFS and open source; points if you have any experience with kerberos, ldap, Perl, or gentoo on non-x86 architectures.

Anyway, if you or anyone you know seems like they'd be a good fit, please send your resume and cover letter to resumes@osdl.org, with the subject "Ref. Bryce: NFSv4 SysAdmin Position".

Xara and Inkscape

A couple months ago the CEO from Xara contacted me about open sourcing Xara X (now called Xara Xtreme), and figuring out ways of working more closely with the Inkscape community. He made the case that it was better to collaborate than to compete. While I had some concerns, he sold me on the idea and so I lent him what advice I could.

Thus, I was quite thrilled to see Xara's announcement. The folks in Inkscape were a bit uncertain about the whole thing, so I encouraged the CEO, Charles Moir, to join the Inkscape list and discuss things directly with folks. It's been great the last few days seeing the discussions and ideas flow. It's exciting seeing things come together, people getting onto the same page, and concensus developing about development strategies.

I think the next year or two is going to be extremely exciting from a development point of view. This is going to be a fun trip to be part of!

MythTV - Success!

As Kees has blogged, we've both got our MythTV setups up and running.

Kees actually beat me to it by a long shot because first, he kicks ass, and second, because he was installing onto grungy old hardware while I was installing onto shiny new hardware that KnoppMyth just looks at and goes, "whadafah?"

So after 20 hours invested into KnoppMyth, I canned it and started over with Gentoo. Ahhh, gentoo. I was able to get all the drivers, services, and whatnot installed in a matter of a few hours. Finally finished things up today, scheduled some recordings, and life is good. :-)

I haven't spent as much time on the front end aspects like the remote and the beeboop noises and such, but that's only because my near term ambitions are a bit different - this is going to just be a backend system. I plan on spending a few weeks just sort of experimenting.

I do have to say that MythTV is not for the faint of heart; it's been a pretty good exercise of my Linux skills, especially when using newish hardware. I think if someone was to really polish up the installation experience it would open this to much bigger audience.

I'm really glad I got Kees so gung ho on it; he's figuring out ALL SORTS of nifty tricks, as I knew he would! ;-)

Bloxsom

Finally, this is likely to be my last post to Advogato, as I am starting to switch to Bloxsom. I've enjoyed being part of Advogato, but have sort of outgrown it; mainly I want more features like commenting. I also love how blosxom allows posting to be done through the commandline; finally I can do all my blogging in my favorite text editor. :-)

Anyway, in case anyone has actually enjoyed my rambling posts, you can add me to your aggregators at the following feed: http://www.bryceharrington.org/blosxom.cgi/index.rss

Testing, Open Source, and NFSv4

I gave a presentation today at the Pacific Northwest Software Quality Conference on my work with organising testing efforts for the Linux NFSv4 community.

PNSQC is a pretty heavily industry focused conference (i.e., nearly all Windows), but it was quite interesting to see that they devoted one of their five tracks to Open Source.

Anyway, one of the questions that came up during my talk was really thought provoking. At one of the earlier talks they'd made a point that that the dark side to fixing a bug in software is that it "leaves scars". By this, what they mean is that when a proprietary application is maintained, it gains #ifdefs and other hacky fixes to issues. In that particular talk, their point was that the best way to make good, long lasting software is to not introduce defects into software in the first place, by adopting development methodologies, coding practices, and testing approaches that generate better code from the start. For example, writing tests before writing the code, shifting metrics to not inadvertantly make high bug counts desireable (e.g. ranking testers on how many bugs they find), etc.

Anyway, in my presentation I was contrasting the proprietary model, where users don't see the program until it is polished and "finished", with open source, where your first release is generally buggy and incomplete - but it works, and over time, given an adequate number of actively involved users, it gets better and better.

So someone asked about why it is that Open Source doesn't suffer from this scarring phenomenon that they're accustomed to with proprietary software. Why is it that instead of turning into the proverbial "big ball of mud", an open source project seems to just get _better_ with age? It doesn't suffer from scarring to the degree that proprietary software does, and the bigger and older it gets, the better. Apache, MySQL, Linux, gcc... all the grand daddy's of open source are considered some of the best quality software in open source (and indeed of the whole software industry, according to some studies), but they're ancient compared with their proprietary fellows.

This is a pretty profound observation. I'd love to see someone study this in more detail and see how true it is. A lot of the data for open source quality are snapshots in time, comparing an open source app with the corresponding proprietary one.

Regardless of *why* this happens, if the phenomenon is as true as it appears, it has some pretty intriguing implications. It means that as we go forward, the scales are only going to tilt further and further into Open Source's favor. Proprietary-only software companies will have to work harder and harder to stay ahead.

It also suggests that there is an advantage to getting into Open Source sooner. If the longer your application is available as OSS, the better it gets, then the sooner you open source it, the more time you'll have to accumulate the benefits. Assuming you have a good, active community around it, and that you have a solid architecture and so forth, this could ensure your application will have a long and successful life, and out compete others in the long term.

Of course, this still leaves that question. Why doesn't OSS suffer from "scarring"? I think there's probably several factors that play into this:

First, "maintenance" in open source software isn't really treated that much differently than regular development. If a bug requires a major refactoring of the codebase in order to close it, then rather than simply slapping a hacky work around and forget it, if the maintainer has the time and fortitude, he *does* that major refactoring. It may destabilize the software for a while, but it closes the bug (and often cleans up the code significantly).

There is also a "redo" effect. I suspect there are some gifted programmers who do everything perfectly on the first try, but most of us get it right maybe after the third or fifth try. With a proprietary application, you may only be allocated enough time to do it once, or maybe twice. In open source, there's really no limit to the number of times that something can be redone, and in fact you see people redoing things a LOT. This is bad in the sense of leading to churn, but I imagine it's one way to slough off a LOT of scar tissue.

A third reason is the people. In proprietary software, the testers, maintainers, and developers tend to ebb and flow. The developer that created the highly successful wizbang algorithm is reassigned to some new business critical job (or hired by some other company), and the maintenance of his code handed over to someone else (possibly someone less experienced). This new person may not have the depth of visceral understanding of the code that the original developer did. In the prototypical Open Source project, however, no one gets "reassigned". You might get bored or burnt out, but it's quite common for you to keep tabs on the program for years to come, answering questions as needed or even helping out in architecture issues with your code.

Another effect that I suspect probably helps Open Source avoid "scarring" is what I think of as the coding parallel to Wikipedia's "copyediting". In Wikipedia, there are folks who rather than writing a lot of good articles, just sort of wander around and obsessively clean up other people's work, fixing typos, correcting grammar, and so forth. I think this phenomenon probably also happens with large Open Source software projects. People with an obsession about security flaws habitually look through code for buffer overflows or injection points. People who are anal about coding standards go through and fix tabs and braces. Lots of little things that individually don't seem that important, but together can have a non-trivial impact on the software quality.

At my talk, several of the audience members shared their own ideas for the reasons. One who'd had a lot of experience with gcc pointed out that some projects have extremely rigorous review processes, that keep out bad code from the start. Another pointed out that since the code is public, you have a lot more motivation to make it good than you would in closed software; after all, WHO KNOWS who might look at it, so you better do it as good as you can.

Open Clip Art Library

I volunteered to do the OCAL release for October 1st. It's the 10th... I need to get it finished. There's over 8000 SVG's in the library as of this release. I've been really hammering at getting it cleaned up and better organized. There were 550 unsorted images, but I've hammered that down to 150. I've also added some more categories and cleaned up a *lot* of the keywords. Still a ton of work left to do, but I think I'm going to wrap things up for this month and leave the rest for the future.

MythTV

Ugh... What a pain it's been trying to get knoppmyth installed. I'd initially tried knoppmyth, which worked fine as a livecd, but as a regular distro I wasn't that impressed. Maybe that's just because I don't use debian much so my apt-fu is not so strong. I found that the default kernel included with knoppmyth doesn't support my sound card, which is possibly why mythtv is behaving erratically with its recordings. However, upgrading the kernel turned into a real headache...

Anyway, finally I gave up and decided to start again from scratch, this time with gentoo, which I'm **much** more familiar with. So far it's been going great. I got mythtv emerged a few hours ago, but ran into some trouble installing ivtv so I'll need to look into that a bit more (the ivtv guys apparently decided to rearrange their website, and gentoo can't pull the tarballs).

6 Oct 2005 (updated 6 Oct 2005 at 08:04 UTC) »
H5N1

It's nice to see the media *finally* starting to talk about the 'bird flu'. Of all the possible ways for humanity to off itself, the bird flu's my fave, and I've been keeping an eye on it for most of the year.

Of course, like usual the media's focusing on the hype and the scare, and sometimes missing the details. I'm worried that even though it's getting some attention, since the media has cried wolf a lot (sars, ebola, etc.) people will ignore this one, and won't be prepared.

I've written up some thoughts on preparing for the bird flu.

42 older entries...

 

bwh certified others as follows:

  • bwh certified Malkin as Journeyer
  • bwh certified Shaman as Apprentice
  • bwh certified Kalana as Apprentice
  • bwh certified rms as Master
  • bwh certified jorrit as Journeyer
  • bwh certified zzorn as Journeyer
  • bwh certified novalis as Journeyer
  • bwh certified pato as Apprentice
  • bwh certified Uraeus as Master
  • bwh certified MenTaLguY as Master

Others have certified bwh as follows:

[ Certification disabled because you're not logged in. ]

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!

X
Share this page