Though it took typing a nasty NVRAM patch into nvedit by hand, I finally got the unbootable G3 to boot NetBSD off of its hard drive. If I'd been able to boot into MacOS, it would have been a few clicks. But I do have a nice collection of Open Firmware links and a deeper understanding of those whacky Macs now... Open Firmware is pretty interesting, really. sigh Too much too learn.
Tried X real quick, and it's working at least. I never did get X to work right on my NetBSD/i386 box at work. I guess I'll have to get pkgsrc onto CD and install some goodies.
July 1 was our first GOVIA developer's milestone. It shouldn't be July 1 already, but there it is anyway, so I'm coming off of a 12-hour hack session. On #govia, I cracked (as surely others have before) "This is the bizarre as opposed to either the cathedral or the bazaar." An observer on the channel, just before that, had said "sitting here _trying_ to read what you two are writing ;)"
I guess our (the two primary developers) communications are reasonably secure by virtue of the natural language er, something or other someone mentioned here recently... And trust there also an issue; have to address it later though.
It was a good 12-hour day... And now, off to sit in front of a different couple of computer for about eight hours!Oh, and how interesting that I should become a 'Journeyer' today, all of a sudden, of all days. Er, thanks, but hm, this thing must be broken! There's one actual Journeyer cert, but the accumulated Apprentices add up to a Journeyer?
The use of the word "trust" is interesting in this context. Is it the same trust I talk about with trust metrics and the like? In one way, yes. The real question is: who do you trust? No sane, thoughtful person would trust the likes of Microsoft and VeriSign. But I think people do trust their social network, and are right to do so. We need massive research to explore how to map social networks into the digital world. I often feel quite alone in thinking about this stuff; very few people seem to understand it. Oh well. I'll just keep pushing it patiently.
For what it's worth, this work you're doing on trust metrics and applying it to the free software community (those of us present here, anyway) is why I'm here. I wanted to see how it worked, which also, of course, helps make it work. Starting a diary to chronicle my minimal involvement with and laughable development of free software wasn't necessarily high on my list of things to do, but I see some real value in this research, just as I see tremendous value in the free software 'movement.'
Far too many folks these days aren't thoughtful people and have no problems trusting whatever corporate entities they're 'supposed' to trust, but if we (er, you? hehe) can develop and demonstrate an alternative that has some basis in our subjective experiences as individuals (rather than as various corporate account numbers), there may be hope. Time may be among the largest problems facing such an effort however. I know I haven't been able to go back and state my certification reasoning and can barely keep up with a diary simply because there isn't enough time to get it all done these days...
Er, that GOVIA developer's milestone set for tomorrow, for instance, should have kept me from even writing this... ;)
Sigh, more later...
Well, how about another section in my notes -- Certification Temptations! Just a spur of the moment thought from a quick perusal of the recent entries... Someone stating they don't deserve a certification, someone a couple of days ago wondering about the value of the certifications... A trend. I figure the more insight I try to provide in how I'm looking at the trust metric, the better. Now if I could just spend more time reading...
"Trust in me..."
Only suitably imagined as sung by Siouxsie on Through the Looking Glass.
Though I'm in fact not 100% finished with the staff activity report web app, everybody's getting training on it today. I even received a couple of changes last night after 5pm, so I actually worked on it a bit at home. Reworked several things while I was at it; think it's a little less kludgy in places now. And my, how much easier it was to actually get some work done at home!
At any rate, no doubt I'll have some tweaking, fine-tuning, bug-fixing to do with it in the next couple of weeks, but I'm just relieved that it didn't blow up this morning. I wouldn't have enjoyed looking like an oaf, and I'm sure my manager (conducting the training) wouldn't have either. Furthermore, the iPaq it's running on is handling the load beautifully... Not that the load is that great, but it had been a concern, simply because I hadn't the foggiest idea of what hardware would really be necessary.
Now let's see if someone here develops some interest in how some freaky-looking kid in tech support did this with free software and a spare machine. The doc root index lists what I'm using, complete with links to the main sites and license information. Even threw the uptime in there... And the page title? LAMP Light @ [my company] :)
Hmm... there was more floating around in my head earlier, but I'm not sure where it went. More later, I guess.
Still making changes, even after starting the after-the-fact spec/requirement document for my pet project. We're still planning on training staff to use it on Friday though. Tomorrow will be a (perhaps long) day of wrapping up many details.
Then I need to rewrite it... It's become a huge mess with all the changes... Rather like I started with something that worked pretty well and have since been making personal preference 'patches' upon 'patches' to the point where it's scarcely the same thing at all.
Still, it's a joy to be doing something I like that much at work.
I really need to put some time in on some GOVIA things... It's been quite a month and I've been quite distracted. We're coming up on the first milestone and aiming at July 1. We can handle that. This weekend, some laundy, some hacking. I can really get things done on laundry days. Built in breaks for reflection when it's time to fold, then nice stretches of coding for the dryer... I mean waiting for the dryer. And thinking about socks.
Anyway, the submission process needs a bit more work and Gist is, although still working, hopelessly broken. Go figure. It was written when we were at, I don't know, version .2 or .3 maybe of the markup language, which we're now calling .6, so...
I was up entirely too late a couple of nights in a row trying to get the new G3 in the family to netboot a NetBSD kernel. I don't even have all the sets to install here at the moment (and I'm on dial-up at home :(), but it's driving me crazy that I can't even get it to boot. Somehow, though I used it a couple of days ago, the floppy drive won't let me insert a disk either, so I'm avoiding the machine entirely for a couple of days (or more, considering the GOVIA work I said I need to do...). I found some information in the port-macppc mailing list archives that suggested I might in fact be looking at a 15-minute wait (?!) for the thing to quit saying TFTP TIMEOUT and finally boot. Dunno, guess I'll find out eventually.
Also, the mailing lists I attempted to start a few days ago (well, no, also the mailing list that's a few months old) don't seem to be behaving. Something I mailed to one list early yesterday morning has yet to arrive at any of my subscribing addresses, and someone told me he attempted to subscribe to one of the new ones, but never got a response.
I've been more than happy with my web host in general, but having mailing lists that don't work doesn't do me any good. We'll see what support has to say. Maybe I did something goofy and broke it myself.
www.highmayhem.com is a pretty interesting site.
Christian Anarchy is a pretty interesting book. You can even read the whole thing online, though I bought a copy of the dead tree edition after I read it online.
Funny, I'm smelling coffee all of a sudden (there's none in the house)... Or am I dreaming, nodding off at work tomorrow already...
Lately I've been using a new alarm clock:
at [?:??] -f CDWAKEUP
Waking up to Clutch's Jam Room is interesting...
Hey hey now, what's that smell? Just like cornbread done too well.
It seems I've acquired yet another Mac, another beige G3. I had it here to try to 'help' it for a friend, but it has something interesting going on and will not boot after installing MacOS 9.2. Just won't do it. Not from the 9.2 CD-ROM, the 8.5 CD-ROM, a slimmed down 9.2-on-a-ZIP... Hangs and hangs and hangs some more, with or without extensions, and I can't even get to OF...
The owner said he'll just wait for his financial aid check in the fall and upgrade to a newer system (I intend to persuade him that his new system should be a GNU/Linux system, and am well on my way, I think), and said he has no use for this G3 since he doesn't want to put any money into it.
I never give up hope, of course... Maybe now it will feel the love of my LAN and consent to boot somehow... At which time it will get some repartitioning and some NetBSD. We'll see.
I've noticed several folks keeping track of who they certify and why. Sounds like a good idea, something that would be good as part of Advogato... ie certification includes "Why?" and insert that info with the list of who I've certified...
Would be beneficial to the metric, I think. As an unknown nobody and not-knowing anything, I'd check out the Recent Log and certify folks (and I have no idea why...will try to remember...), paying extra attention to fellow nobodies...But already since then my perspectives have been shifting...
And those looking at me might think, oh this guy's just certifying people to try to get certified himself and writing silly diary entries to waste bits... And I can't prove otherwise. Whatever's been distilled enough in my head to make it to my diary here is in no way indicative of my thoughts on open source software advocacy...Just informal rambling when I get a moment. But if my reasoning behind certification of so-and-so is exposed, perhaps others will get a better idea of my thinking.
Giving up hope in the trust metric doesn't seem like the best idea; we're learning as we go, no? Why not keep exploring? If some folks are stuck as Observers (I was for a while too), can you tell why? Is it because half of those here are more worried about what everyone else is writing here instead of what everyone else is actually doing?
But only because I have no choice but to be sneaky.
I think the web-based weekly report project is nearing completion. So, of course, that means it's time for me to write a requirements document for it. Interesting, eh? Maybe I'm also sneaking in the 'bad' parts of open source software, projects begun with minimal direction, just a thought, an idea... But hey it works, to a point.
There was a need and an idea. We were given the go-ahead to see what we could do, without using any company resources. I started with what I knew, still learning daily as I went along. A couple of sitdowns, looking at the project with my boss, has refined the idea. Now that we think we have it, we'll "make it official," so to speak, with some documentation.
He gave me an example to go by, so I'll have to take another few glances at that. I hope to be able to emphasize the strengths of the open source stuff used in the solution, but I imagine a lot of it won't be within the scope of a requirements document. There is at least the one: "...without using any company resources." I assume that meant not to place additional demands on our web team, which we have avoided. My salary the past little while has paid for its development, but our department is well-staffed and the payoff will be significant, I think.
Where once several someones were kept busy cutting and pasting Word documents that had been emailed to them (looking back at my old ones, probably 40k average size) those same someones will now click a button. The database right now isn't even 25k (granted, only a handful of people have been using it, more or less as beta testers).
In addition, these serve to inform supervisors of problems employees might be having. We decided to go with an email notification system rather than including that in the report, so our solution facilitates rapid response to any issue an employee may have.
So now to document it. Well, not now, but you know.
Another mini-project to follow will involve keeping us under a maximum number of users at a particular web-based resource we're using in technical support.
In other semi-related news, another department (just barely another department, but it is) is also making use of open source software at the Day Job, putting together some web-based training material. The other Linux freak is over there with his Mandrake laptop, doing graphics with the GIMP, and writing the HTML in something other than vi(m), which he really oughta work on... -grin- A potential convert still harbors a desire to use ASP and a Windows server. Not sure how they'll handle that, what 'resources' are available. I told him the other day that PHP had passed ASP in the number of servers running it...
That's enough for now.
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!