RandM Thoughts

Last (blog) Post

2013-11-13T16:41:00.000-05:00

I published my first blog post on RandM Thoughts on 18 February 2006. This is my last post. Henceforth, I will concentrate my various blogging activities in a single blog, Transformative Explications. All of the posts from RandM Thoughts have now migrated and merged with those from an earlier incarnation of Transformative Explications and will continue to be made available at the new location.

If you have been following this blog via an RSS feed, or if you’ve just found one of my posts through a search engine, or if you are specifically trying to track down Randy Metcalfe in order to find out what he is up to these days, I invite you to join me at Transformative Explications.

There you will continue to find my infrequent musings on technology, open source software and more. Plus you’ll find posts about literature and creative writing, which, after all, is really what I’m most interested in.

My thanks to everyone who visited this blog over the years and to those who contributed to it through their comments.

Randy Metcalfe

Google Nexus 7, 2nd generation

2013-09-15T10:17:00.000-04:00

I had one of those heavy birthdays last week. The kind of birthday that prompts your spouse to purchase you something geeky and electronic to make you smile and possibly not feel quite as old as you are. (Isn’t every birthday like that?) On this birthday, after some advance negotiations (“I’m not getting this unless you tell me you will definitely be happy with it”), I received the recently released second-generation version of the Google Nexus 7. And yes, I am very, very pleased with it.

For a long time I hesitated between the iPad mini and the Nexus 7. My wife got an iPad a couple of years ago and has been delighted with it ever since. About eight months ago her father got an iPad mini and he too has been delighted with it. And since cost, on this one occasion, was no bar (these heavy birthdays really do only come around rarely) I could easily have gone with the iPad mini. But everything I’d been reading about the new Nexus 7 suggested that it was more than equal to the challenge of the iPad mini. Plus, I was a bit concerned that we were getting painted into a corner here with our iMacs and the iPad; perhaps it was time to branch off into a different paradigm with an Android device (well, actually it’s probably the same paradigm, just a different company/environment). Then there was the much-vaunted beauty of the new Nexus screen. And finally, even though someone else was buying this for me, there was the cost difference, which here is about one hundred dollars. And that does mean something.

Choice made, heavy birthday survived, now it’s time to report on the joys (or not) of actually using the Nexus 7. Reader, I can safely say that it is wonderful.

The set-up of the device was painless. I found the apps I was looking for in Google Play, initially adding them to a wish list until I was ready to begin installing them. I’ve got the apps you might expect, I suppose: Facebook, IMDB, BBC News, LinkedIn, Dropbox, CBC News, Skype, Twitter, Flickr and more. There are a few apps I have installed based on recommendations from across the net. For example, Duolingo, which is a language-learning app, turns out to be fabulous (it is available for the iPad as well). I’m sure I will find lots more in time, but I’ve got enough to be getting on with.

One thing that was expected was how easy the move to Android is if you’ve already been enjoying a variety of Google products. Gmail, Drive (Google Docs, as was), Maps, and such just work the way you would expect. The browser is Google Chrome, which is fine with me. And there are apps for Google Earth, your Gmail contacts, and for Google+ (for which I’ve yet to find a real use).

Of course one of my goals for this device was to use it for reading e-books and other e-materials. To that end I purchased a subscription to The New Yorker magazine through Google Play Magazines. The subscription cost was reasonable and I’ve got to say that the magazine looks great on the device. It is easy to navigate, easy to read, and it has lots of additional multimedia content. I figure this will get me in the habit of reading on the device and that will make the move to reading books here easier. To that end I have added the Overdrive media app, which is what our public library uses. And of course there is also Google Play Books should I wish to purchase any e-books (though I’m so stingy it will take a great deal to break down my reservations on that).

Mostly I’m just having fun with my new Nexus. I still have a bit of a learning curve ahead, no doubt, but that’s no bother. Oh, and one last thing, my Nexus 7 is now housed in a nice Snugg case/cover. I guess I’m set.

Not so much moving on as being pushed – after Google Reader

2013-03-14T09:09:00.000-04:00

Back in July of 2012, Google announced that its much-loved customizable homepage, iGoogle, would be shutting down in November of 2013. Along with others, I searched the heavens for further signs of the end times—a rain of toads, a column of fire, dogs and cats living together. Nothing. Apparently it was just a commercial decision by a large corporation that could no longer see a financial advantage in sustaining the iGoogle environment of widgets and gadgets and whatnot. Not a lot of ad revenue in widgets, I suppose (at least not the ones I was using).

Today, Google has announced that Google Reader—its RSS feed reader—will be shutting down in July 2013. I’ve checked the heavens and once again it appears this is just a corporate decision. Well then.

I’ve never loved Google Reader. It was only ever functional. When I would come across an RSS feed that I wanted to keep track of, I would “subscribe” to it in my Google Reader. It provided a means of grouping one’s RSS feeds, labelling them in a common fashion. But that was never truly useful since Google Reader’s user interface was never convenient for a quick scan of RSS items.

What was useful, however, was the fact that I could take an output feed from Google Reader—a conglomeration of all the RSS feeds to which I had subscribed within Google Reader—and feed it through an iGoogle gadget so that my entire set of RSS feeds would appear on my homepage in abbreviated form (just the feed title). I have no interest in reading the vast majority of items that appear in my RSS feeds. I just scan through the titles of the items and when I find one for which I would like to see the full content, I just click on it. Simple. When I’m done I mark all of the items “as read” and they are whisked away leaving me with a nice clean, empty, Google Reader gadget on my iGoogle homepage waiting for the next batch of items when they arrive.

I don’t suppose I am a big user of RSS feeds. I have 76 feeds currently in my Google Reader. Collectively they produce between 150 to 200 items in my Google Reader gadget on my iGoogle homepage per day. Of those, I probably look at maybe 10 or 15.

But now my need for finding a viable replacement for my iGoogle homepage just moved from “pending” to “urgent”. (Not panicky urgent, just ordinary urgent.) I already know about a few alternatives, but in the back of my mind I’m thinking that I should just do my own thing, probably within a Drupal installation on a site I already use.

Change comes to all of us, with or without heavenly signs. I just don’t enjoy being chivvied.

Producing Open Source Software by Karl Fogel (revisited)

2013-01-30T08:24:00.002-05:00

It seems years ago now since I first read Karl Fogel’s Producing Open Source Software. That’s because it is. The book, made available at producingoss.com in 2005 and published by O’Reilly in 2006, was one of the first to offer an accessible and thoughtful look at how to run a successful free software project. Back in 2005 and 2006, that was something I was keenly interested in, not least because I was working for OSS Watch at the time.

Time passes. Things change. Even the world of free and open source software changes over time.

I was delighted to learn recently that Karl Fogel is setting about producing a revised and updated edition of Producing Open Source Software. What’s more there is an easy way that interested individuals can help this project come to fruition. Karl has posted his project on Kickstarter, which is a funding platform for creative projects. Check out Karl’s video on his project page. And then consider making a small contribution to help kickstart the project. It’s a great opportunity to make a small contribution to the ongoing success of free and open source software.

Plus, just as with the first edition, the new edition will be released online under a Creative Commons Attribution-Share-Alike licence so it too will be freely available to read and share with others everywhere and anywhere.

Very much looking forward to the new edition of Producing Open Source Software.

Distribution Upgrade -- Ubuntu 12.04.1 LTS

2012-09-08T17:34:00.000-04:00

My ageing laptop (2007 Dell Inspiron 1520) has been around the world, literally. It served me well in Kathmandu and Bamako, London and Paris, and even here in Waterloo. A couple of years ago I replaced the keypad. But otherwise it has been rock solid. In the past six months, however, it has developed numerous ailments that probably signal its end time. For example, there is now a constant high pitched whine coming from the hard drive, which I'm sure can only be heard by canines, Superman, and me. More significant, however, is the emergent power conflict such that I can no longer run the laptop plugged into the mains. Doing so automatically leads the screen to very shortly black out. So I am forced to use the machine solely on battery power. And even the battery is now a bit long in the tooth and drops its power rapidly and inconsistently.

Still, it's been a good machine and I've learned a lot with it. But one thing I'd never done was an Ubuntu distribution upgrade. In the past, whenever I wanted to move up to a never version of Ubuntu, I would burn a disc and install the distribution from the disc, entirely wiping out what had previously been on the hard drive. On a whim today I thought I would attempt a direct distribution upgrade. Could my machine manage it with its dodgy battery, high pitched whine, and travel stickers from Nepal?

Yes, it can!

It was touch and go. I started up the machine and went quickly to the software updater. I already knew that Ubuntu 12.04.1 LTS was available for upgrade, so I immediately clicked on the button for distribution upgrade. Then I ignored all the warnings about how long it might take (it said it might take hours) and that I should definitely not attempt it without being plugged into the mains (but hey, what could I do? It's not risk taking when it is your only option.) I then stepped back and crossed my fingers.

Sure, crossing your fingers is probably not best practice for techies, but then it's long been clear that I'm no techie. Initially the laptop claimed to have almost 2 hours of battery life left, and the upgrade was estimating that it would take over 3 hours to download and install everything. But what are numbers, eh? Soon enough the download speed picked up (I had plugged directly in to my router to optimize my throughput). Of course the battery time took a dive as well. After about 30 minutes the laptop was claiming to have just over an hour's worth of battery left, but the upgrade was by then estimating that it needed only slightly less than an hour more.

I should have filmed the sequence because over the next hour the battery jumped down and then up and likewise the estimated upgrade time went up and down. It was like a high (or slow) speed action thriller. In the end, the upgrade completed with less than five minutes to spare on the battery.

Of course the battery life vs upgrade time drama is not really all that significant. Much more important is the fact that the upgrade appears to have gone through perfectly. Even my crappy wireless card continued to work post upgrade. Well done, Ubuntu!

I don't know how many more months this laptop has in it. But till the end of its days it will happily stay an Ubuntu machine.

After iGoogle

2012-07-27T09:30:00.000-04:00

I have been using iGoogle as my personalized homepage for more than five years. I have recommended it to people who also now use it. So I was disappointed to learn at the beginning of July that Google intends to “retire” iGoogle on 1 November 2013.

I suppose I don’t do a great deal with iGoogle. For me there have always been two key widgets: the Google Bookmarks and Google Reader widgets. I have a tidy set of links that I like to have available to me at all times. And I’m a bit old-school (if a non-techie can be ‘old-school’ about something techie) in that I prefer to gather the rss feeds of news sites and blogs that I enjoy and read them in one handy location, i.e. my homepage. Less essential widgets (for me), but still useful, are the French and German Word-Of-The-Day widgets from Transparent Language and the small Google Translate widget. I also use a weather widget that keeps me updated on the state of the rain (or sun) in Oxford, London, and Toronto, but that is only looked at periodically.

One reason that iGoogle has been so convenient is that I often cycle between a variety of browsers, computers, and operating systems. My iGoogle homepage, however, stays constant whether I am using Firefox or Safari or Chrome, or PC, Mac, or Linux.

Another reason for iGoogle’s convenience is its robustness and (in an environment of rapid change) stability. More than five years is a long time these days. And, yes, maybe I’m getting settled in my ways. But still…

Google notes that in the current era of modern mobile apps, “the need for something like iGoogle has eroded over time”. But not for me. My need for it remains exactly the same as when I first started using it more than five years ago. I don’t use “mobile” devices. I use desktops and laptops. I use a web browser. Am I the last one who works this way?

Unfortunately none of the alternatives that Google suggests are terribly convenient. Yes, I could use tabs in my browser for the Google Bookmarks web page and the Google Reader web page, and likewise for Google Translate and other widgets I use daily. But have you looked at the Google Bookmarks web page? Or the Google Reader web page? They are very user-unfriendly, at least a compared with the straightforward way their data is dealt with in my current iGoogle widgets.

As I see it, at the moment, there are two possibilities for how I will organize my daily web use after iGoogle’s demise. I will either have to go with a pre-packaged solution, such as NetVibes. Or I will have to set up my own personalized homepage on one of the domains I manage. Neither is ideal.

I, perhaps naïvely, like Google. I like most of Google’s family of tools (Gmail, Reader, Bookmarks, Calendar, Maps, Docs [now Drive], etc.). And I liked iGoogle.

What would you do?

2012-02-13T10:36:00.000-05:00

The Internet is vast and contains multitudes. It may not need any more content. And yet…

I have been doing a bit of online consolidating. I’d call it Spring cleaning if the temperature hadn’t dipped to -11c yesterday. I now have one fewer web-hosting accounts. Already I feel a bit lighter. But I’ve still got this blog, on which I infrequently consider matters technological and (perhaps) ontological (as when I start ruminating on my personal identity online). I’ve got another blog, Transformative Explications, which has settled into my place for writing about what I’m reading and, sometimes, what I’m writing, again infrequently. I’ve got a domain and some web space for a static frontispiece website for my consultancy. And this year, as a bit of an experiment, I have been active over on LibraryThing posting reviews of each book I read. I draw a feed of those reviews into my Transformative Explications blog.

My Twitter account remains empty. Am I unable to render my thoughts into 140 characters? Or do I not have thoughts worth even those few characters? The truth is that I have not yet thought of a sensible use for the stream of characters that might ensue if I began “tweeting” frequently, or infrequently. One person I follow on Twitter is forever witty and wise. I would (and do) follow her blog and Facebook status updates as well. Another person I follow is just a touch self-important (yes, even in less than 140 characters!). I’m fascinated, even though it feels rather like watching a train wreck. Somehow I don’t see this as the right forum for me.

Yes, of course, I have a Facebook account. I also have a Google+ account. I contribute to them each about the same, i.e. not at all. The Facebook account, however, does keep me in touch (in that tangential way) with a number of relatives and more distant friends with whom I otherwise would have no contact at all.

And that brings us to the unused domain name I have on my hands, along with sufficient web space to do pretty much whatever I would like with it. But what does the Internet need? (Or what do I need?)

I put that question to a few of my friends. Being my friends, a number of them suggested that I use that location on the Internet to post some of my fiction. Well, really, what did you expect them to say? That’s why I call them my friends :-) There were also a few other excellent ideas, at least one of which I’m actively thinking about, though to be honest it would be better if I simply offered to set up that site for the person who suggested it.

Now I’m prepared to open up the question to a wider audience (or smaller, depending on the actual reach of this blog). Suppose, you have an unused domain name, and the wherewithal to set up a blog, or CMS, or what have you. What would you do with that space? What content would you set about creating? And how would you go about thinking about this question?

Single boot laptop - Ubuntu 11.10

2011-10-14T11:38:00.000-04:00

I bought a Dell Inspiron 1520 back in 2007 when my wife and I moved back to Canada. For much of its life it has been a dual boot machine - Windows Vista and whatever the latest version of Ubuntu was. It's not really an old machine, but it has been around the world. Literally. From here to Kathmandu and many stops in between. Throughout these four years I have paid for virus protection (for Windows). But I don't use the laptop so much these days, since I'm not on the road now, and because I've now got an iMac as my base desktop. And even when I do use the laptop, I tend to use it in Linux. So, with my most recent year's licence for virus protection (for Windows) running out, and with a new version of my favourite Linux distribution released (Ubuntu 11.10), I finally made the move and turned this laptop into a single boot machine.

That's no big deal for many Linux users, I'm sure. For me, though, there was always a barrier to such a move. Perhaps if my first Linux machine had not also been a dual-boot machine (with Windows), I might not have developed this psychological dependency on that other operating system. This, despite the fact that I almost never used it. But I knew that I could, if I needed to, right?

It is no surprise to learn that there is a cost to most software decisions. For me the cost of yet another year's licence for virus protection (for Windows) when it wasn't really being used was just too much.

And now here I am with a lovely "new" laptop. So far it seems to do everything I've always expected my Linux installs to do. (The fact that I can listen to the cricket on Test Match Special whilst typing this post is all the evidence I need.) It has been a long time coming, but I can now finally say that I have a Linux machine. Full stop.

iPad experiences

2011-07-27T10:08:00.000-04:00

I never wanted an iPad. When they first came out I thought they would be fun but not useful. It made sense to me that something that might be sitting in your lap ought to be touch friendly. But maybe that's a guy thing. In any case, I never expected to have one fall into my lap. And then one did. So now, after a couple of months of use, I can offer some thoughts.

A lot of people will tell you that the iPad is not a laptop or desktop replacement. Those people are right. This is a product with some distinct limitations. So let's get those out of the way off the top. Printing is pretty much a write-off. Storage is limited (if tens of gigabytes is limited). Editing MS Office documents in anything like a serious way is effectively a non-starter. Some websites built primarily with flash are effectively inaccessible. Okay, so those are the limitations. I say, let's just set them aside and look at what the iPad actually does do, and do well.

First, connectivity to wireless is a breeze. That's not surprising for a Mac; I'm just confirming it. Access to email (thought not necessarily full editing and storage manipulation) is straightforward. Websites (the ones that are not entirely built in flash) load quickly and look beautiful. Once you figure out that the idea of tabs in a browser is not really there, you can bounce around the web about as quickly as you can with any other browser. Oh, and when you get on a plane, switching to Airplane Mode is painlessly simple.

Second, there are lots of apps available for the iPad. For the most part I have only been using those apps that are free. But there are even lots of those. I like the iBook app, and the IMDB app, and the NFB (National Film Board of Canada) app, and BBC news app. Maps, which comes pre-installed, is really useful. And even the Skype app works satisfactorily.

Third, the display is beautiful. Photos, videos, and even movies look great. The latter beat the sad "personal entertainment" screen on the back of the airplane seat hands down. I also bought a splitter for the earphone jack, so my wife and I were able to watch a couple of films together on the plane - films I rented from iTunes for 30 days for 99 cents each.

It is light and (seemingly) sturdy and the battery goes and goes and goes.

The iPad doesn't do everything. So if you want something that does everything, then you need to look elsewhere, and good luck to you. But within its limitations, I have found the iPad to be an excellent travelling companion during more than 4 weeks on the road in the past couple of months.

Refresh rate

2011-03-03T12:41:00.001-05:00

How often do you upgrade your operating system or your computer hardware at home? With me it depends. I like to keep my Ubuntu systems current, which means I will usually make a clean install every six months as the next release comes out. Since I am installing Ubuntu on dual-boot Windows machines, I am not typically refreshing the hardware at the same time.

I tend to only start using a new Windows operating system when I buy new hardware (if the hardware I am buying comes with Windows installed). I get the itch to move after about three years, but it may take four or sometimes five years before I have the spare cash to enable a hardware refresh. And even then I'm only talking about my principal machine, since I tend to keep the older machines running for other purposes. The oldest one I have at the moment is a 2005 Dell Dimension 9100 desktop - still running fine on Windows XP and the latest Ubuntu.

Now that I've made the move to an iMac as my principal machine at home, I thought I was done needing to learn new Windows operating systems. Not true.

My father is about to refresh his hardware and software. He has a ten year old Pentium 4 with 256 MB of RAM running, slowly, Windows XP. It is, for me, almost excruciatingly sluggish. And since his Internet connection was DSL "lite" (many times faster than a dial-up modem!) the combination could quite simply stop you in your tracks. I finally convinced him that it was time to make a change.

I argued that two factors impacted his current user experience. (There's no point making your case if you aren't going to take it seriously and do a thorough job.) One was his Internet connection and the other was the processing power and speed of his computer. To "change his game" he needed to address both factors at once. Somewhat to my surprise, he agreed.

He has already made the call to upgrade his DSL. He should now have a connection roughly comparable to what I'm getting through Bell. He tells me that he already notices the difference. Web pages only take a few seconds to load, as against the 30 or more seconds most pages used to take. When I visit him next, I will install a wireless router to his system. This will not improve his experience. But it will provide a more normal (dread word!) computing environment for his grandchildren who are used to taking their laptops with them when they visit their friends and having full Internet connectivity while they are there.

As for the hardware and operating system refresh, I put forward two recommendations. One was the iMac with which I have been completely satisfied. The other was a mid-range Dell, which of course would mean Windows 7.

Some people are change averse. My father is one of these people. Some people have little if any intuitive grasp of computers. Again he falls into this group. Some people also have little or no interest in learning anything new that has to do with computers (and consequently feel no excitement in the possibility of playing with a new system). Again, that's him. So, no matter what, I will be absorbing a fair portion of the change cost of moving him to a new computing environment.

In the end he chose the less expensive option. Fair enough. He will still have a much, much better user experience than he does currently. It may even give him a taste of some of the fun that is possible with computers. (But I doubt it.) And meanwhile I have started reading this very large book on Windows 7. I'm looking forward to his new computer arriving next week.

Really.

No, really.

"Click here"

2011-02-27T10:04:00.000-05:00

A reputable search engine informs me that there are about 1,320,000,000 results when I search for the phrase "click here". I confess to being astounded. I had been gently chiding a friend who had let this challenge to accessibility creep into his website. It turns out he is not alone.

As far back as 1999 the W3C's Web Content Accessibility Guidelines 1.0 urged web content developers to avoid the use of "click here":

Guideline 13. Provide clear navigation mechanisms.
13.1 Clearly identify the target of each link. [Priority 2]
Link text should be meaningful enough to make sense when read out of context -- either on its own or as part of a sequence of links. Link text should also be terse. For example, in HTML, write "Information about version 4.3" instead of "click here". In addition to clear link text, content developers may further clarify the target of a link with an informative link title (e.g., in HTML, the "title" attribute).

It's a little thing. Yet for me it is something that leaps out when I see it.

So why are there more than a billion instances of "click here" out there in the wild? I don't know. But I think that friends don't let friends introduce further instances.

Syndication - still a lot to learn

2011-02-23T11:39:00.000-05:00

What I don't know about the syndication of content could fill something, but just what I also don't know because that's one of those unknown unknowns. Recently I have been talking with a friend about certain statistics that might help guide her in making her blog better serve its purpose. I find I'm always a touch reluctant to venture outside my comfort zone. Nonetheless I set out this morning to explore one of the options available, namely FeedBurner, which is now well within the Google family.

I have now burned my feeds for the two blogs that I use. You can see a new "Subscribe in a reader" link at the top of this blog. That takes you to the FeedBurner feed. If you are a regular reader of this blog (I'm sure I have at least two - thanks, Mom!) I would encourage you to update the feed now.

As I understand it, the old feed continues to work but the new feed will provide me with much more statistical goodness. Eventually this may lead to such developments as search engine optimization which I'm sure has much to recommend it. Or at least a few more blog posts on technical topics I am struggling single-handedly (but with the aid of a well-optimized search engine) to learn.

Since I am unlikely to ever write anything here that would set the world on fire, I very much doubt I would need the above information to aid monetization (dread word!) of this content. But maybe my friend will become a prolific and well-read blogger. In which case I would at least like to be able to advise her soundly (even if that advice were to find a more competent adviser).

Just the essentials, please!

2011-02-22T08:58:00.000-05:00

There are a lot of useful documents available on how to get an open source project up and running. This short briefing note from Ross Gardler at OSS Watch is excellent: Essential tools for running a community-led project. Ross has years of experience in such projects, notably those that are part of The Apache Software Foundation. He has boiled down some of that experience here into just the nuggets of pure gold (as I mix my metaphors egregiously).

One of the things that I think Ross gets completely right is his stance on communications. He writes:

A second communication channel should only be created when the traffic on your first channel is sufficiently high to justify the split.

Absolutely! Nothing more than is necessary. Best to just head over now and get Ross' take on these things. And while you are there, why not visit some of the other fabulous resources that OSS Watch has to offer.

PIO - an academic question

2011-02-04T09:18:00.001-05:00

Previously I have been thinking about Personal Identity Online (PIO) in terms of how a consultant might shape or influence how he or she is perceived. I took that as a straightforward communications challenge and put forward suggestions on setting up a consultancy website, blogging, tweeting, and more. Now I want to turn to a couple of thorny issues for academics who are thinking about their PIOs. I want to describe two cases: (1) a well-published academic currently unaffiliated with a university, and (2) a tenured faculty member who uses a non-academic email address and/or domain name for his or her academic web page.

The days of completing your Ph.D. and walking directly into a tenured faculty position are long gone (and maybe they were only ever a myth). The norm for the academic career path in the Humanities tends to be Ph.D., post-doctoral research (if you are lucky), sessional or contract teaching (sometimes, sadly, referred to as "casual" staff), a mad scramble for publications, and then (if you are very lucky) landing a tenure-track assistant professorship, followed by another mad scramble for additional publications, high teaching-evaluations, and "service" (which includes administrative duties as well as contributions to one's profession such as peer reviewing submissions for publication). Finally, if all goes well, you achieve tenure. And now you can set out on the longer journey toward becoming a full professor. (NB. these are terms for the progression in North America; in the UK and elsewhere the terminology and the progression varies somewhat.)

Between completing your Ph.D. at one institution and securing tenure at another, the young academic may find himself or herself employed, at one time or another, by a surprising number of academic institutions. They might even temporarily be employed by two or more institutions at the same time, for example if they were contract teaching individual courses at different institutions. There may even be times, despite one's stellar publishing record and high teaching-evaluations, when one finds oneself between institutional employers. In that situation, how does the young academic self-identify online?

There are complications, naturally. Over the years, the young academic may have been given, temporarily, an institutional email address and quite possibly webspace for hosting teaching and other academic information relevant to one's department. These persist as links on web pages or email addresses in colleagues' email clients long after one has moved on. What is the half-life of an institutionally hosted academic web page? And how long will it continue to skew search engine results years after it has become inaccessible to the person who originally set it up?

The self-identification question is one on which I do not have a settled opinion. Recently there has been a move to recognise that a substantial portion of our tertiary teaching population is in some stage of the progression described above. One term mooted for such individuals is "independent scholar". There is even now a Canadian Academy of Independent Scholars. (I think there is still work to be done on thinking this through since one benefit of "full membership" - a library card for Simon Fraser University - requires the scholar to appear "in person" in order to pick up their new library card.) Is independent scholar the best self-describer available? I have also seen individuals self-ascribe by the name of their academic group, e.g. Historian, Philosopher, Physicist, etc. That might not work so well for all groups. How would the researcher in comparative literature self-ascribe in this way?

The second case I mentioned - the tenured faculty member using a non-academic email address - could easily arise out of the academic progression I described. The itinerant academician might have found that a non-academic email address (and also a non-academic domain name for a personal academic web page) is simpler. It saves the need to request an update to one's friends and colleagues' email address books each time one moves on. Even once tenured the academic may find that it is easier to stay with the non-institutional email address and/or web page. (There are also cases where some institutions have less than fully reliable email infrastructure, unlike the rock solid email infrastructure we used to have at the University of Oxford. In such a case, the academic may feel it safer to give out his or her non-institutional email address.)

Again, I do not have, as yet, a settled opinion on this. Clearly, however, the two cases I am describing are related. Here all I have managed, if at all, is to describe the communications challenge. I'll need to do a bit more thinking in order to come up with my preferred solution. But I welcome suggestions. With our universities expanding dramatically, but without a consequent expansion in the numbers of tenured faculty, my suspicion is that the above situations will be faced by increasing numbers of scholars, independent or otherwise.

Skin - Thick or Thin

2010-12-29T10:33:00.001-05:00

Are you the kind of person who tosses and turns at night replaying a minor remark you made at a social gathering? Can you be crushed by a single barbed comment? Do you cringe at the level of vitriol you see in the "readers' comments" section of online news sites? If you've answered 'yes' to any of these questions, I feel for you. Like me you appear to be thin skinned. Are there any strategies that can be deployed in order survive the dangers (to us) of a barbarous world?

Don't go out: As someone short and clever once said, "It's a dangerous business, going out your door." You could try avoiding social gatherings where you have a tendency to embarrass yourself whenever you engage in conversation. You could embrace the honourable role of lurker on the Internet, never succumbing to the temptation to contribute your own input. You could take that one step further and simply lock your front door and disconnect your modem/router. It's the only way to be sure, after all.

Limit your range: If you absolutely must go out, then you could at least stay close to home. What is the absolute furthest you need to walk in order to acquire sustenance? Don't go any farther. The same holds for conversational topics. If you have to converse, you could try restraining your topics to the weather (just agree that the weather is either good or bad, and probably much worse than you remember it being). On the Internet you might want to limit your communication solely to those you know well. Stay away from any form of one-many communication tools like Twitter or Facebook (FB) or blogging. Remember, if possible say nothing.

Stay with your own kind: There is a reason that wildebeests hang out with other wildebeests. I don't know why that is. But on the Internet it seems to be safer to hang out with others who already share exactly your own opinions and have no other opinions. Obviously the easiest way to accomplish that aim is to hang out only with yourself. There are dangers here, of course. It might be a bit lonely. Sometimes hanging out with people just like yourself is called homophily. I once heard Ethan Zuckerman convincingly argue that homophily can make you stupid. Is stupid really that bad?

You may know people who are remarkably thick skinned. I know a few. They make cringeworthy comments regularly and appear to be immune to the whole agonizing tossing and turning thing. Sometimes it is as though they don't even realize that they have said something embarrassing. (Here, I'd like to say, "You know who you are!", but of course you don't.) I'm not sure how they got to be so thick skinned. Is there some equivalent of plunging your hand repeatedly into buckets of increasingly larger grained sand and stones? In any case most people described as thick skinned tend to be a bit too thick skinned for my taste.

I wonder if there is some happy medium between thick and thin that could be reached. It must be nice to always say the right thing, in the right way, at the right time. I suppose there are people like that; I just haven't met any. Failing perfection (which sounds like a good title for a blog) perhaps the best that might be achieved is a kind of gracious humility. I think of this as a certain modesty in one's claims and a ready willingness to acknowledge overstatements and misstatements and rectify them.

If you are thin skinned and not one of the hearty folk there is still plenty of scope for you to step out your door. With a bit of patience and a lot of bravery, there really is no telling where you'll end up. You will still toss and turn at night, but it'll only be because of that dirty great root sticking in your back.

And oh, don't hang out with wildebeests.

Origin stories

2010-12-10T09:03:00.000-05:00

Each of us has a storied past. What else could the past be? Selecting salient episodes for retelling as an illustrative or explanatory tool dramatically highlights current and future motivations, commitments and ideals. These stories say a lot about you. I don't think that I am alone in being fascinated by such stories. There is a subset of these that I find particularly interesting: origin stories told by serious participants in the free and open source software community. These are surprisingly rare. I think it's because serious FOSS folks know it isn't about them, it's about the community. As a result you are more likely to spot one of these origin stories showing up in passing when such a person is writing about something else. One such origin story can be found in Ross Gardler's post on the demise of the Java Community Process.

I was struck by Ross' description of how he learned the value of commitment, teamwork, and collaboration through sport. I wasn't surprised. Nor was I surprised that he has other tales to tell, other experiences that shaded his understanding and provide him with a rich and subtle appreciation of community.

On another day perhaps he would select two completely different episodes as salient in his moral forensics. That too is something each of tends to do. Today I think it was the way my father coached a hockey team I was on as a boy that stands out. Tomorrow I'll think that it was the way he faced and accepted the consequences of each of his decisions. Next week I'll come back to the camaraderie he cultivated in the crew that worked in the bakery. (Not all origin stories are father stories, but mine mostly are.)

The Java Community Process may indeed be dead. I'm not a direct participant in that community so I have to rely on people like Ross to get the straight story. Fortunately I feel like I now have a bit of insight into what drives him, and that convinces me that I was right to trust his lead on this all along.

Still, I wish I'd known him in his Dub Reggae days :-)

First snow shovelling (2010)

2010-12-07T08:28:00.000-05:00

It's a new year for shovelling the walk in front of the house. Although we had only a mild snowfall last night (less than 2 cm), I got out the snow shovel for the first time this year and did my duty (as did my neighbours).

I see that I noted the first snow shovelling of 2009 on 9 December that year, so we are a few days early this time. Fortunately we are in a bit of a clear pocket at the moment. Just an hour's drive west of here they received over 70 cm last night. Now that would be real shovelling!

The Milk Calendar

2010-11-20T08:30:00.000-05:00

Every year around this time households in Ontario (and elsewhere in Canada, I believe), either through their local daily paper or other means, receive a copy of The Milk Calendar. Apparently this started back in 1974 but I only became conscious of it in the '90s. Kathy and I had moved to Oxford, UK, in September of 1994 with little more than one suitcase each. We had a flat in the draughty, cinder-block, married-student accommodations in north Oxford. We didn't know anyone, and we really aren't predisposed to meeting and making new friends (though despite ourselves we did eventually discover the very best of friends). Dreary November and December days stumbled toward the holiday season. But with no funds for travel home or onward we knew we would be left to our own devices.

It must have been some time in December that the package arrived. A well-labelled and multi-stamped box from Kathy's parents. The shipping label declared, unceremoniously, an itemized list of the "Christmas gifts" contained therein. Nothing grand, but we were so grateful to receive this bundle of cares and well-wishes. There may have been tears. It turned out, however, that the greatest gift was not in fact identified on the shipping label. Perhaps including it had been an afterthought. I've never asked. There amidst the crumbled newsprint used as packing material lay The Milk Calendar for 1995.

I'm sure we still have that calendar, though the recipes (yes, recipes!) it contained have long since been transferred to other media. What makes The Milk Calendar distinctive is that it always contains a set of recipes (at least one for each month) for dishes or desserts that are easy to make, taste great, and, naturally, involve milk somewhere in the instructions. What they don't mention is how those recipes can transport you across time and space. In that slender calendar was the essence, or so we thought that winter, of Canada.

I don't recall now how many of those recipes from the 1995 calendar we actually used more than once. But I'm fairly certain we did try each one at least once. I remember writing letters to Kathy's mum to tell her about them (those were the days before email was ubiquitous). Each one a reminder of how that calendar helped us beat off the damp chill of the English winter.

The Milk Calendar for 2011 arrived today. I can't help wondering whether any Canadians far from home will be opening a package in a few weeks and discover within that things aren't nearly so dreary as they imagined. I hope so.

More is easier

2010-11-18T11:14:00.000-05:00

I have a tendency to follow the line that less is more. Maybe it's because I'm short. I like short sentences. Short paragraphs. Bullet points. And one side of A-4, no more!

But sometimes I have to admit that more is better. What would Proust be like without the long, meandering, sentences that wrap you up and spin you round until your own thoughts are as mixed and muddled as the memories his narrator is dancing through? That must be the very effect he is aiming at. More is also sometimes better when it comes to software and learning.

I am continuing up my learning curve with Drupal. It's getting better. (Well, I mean I'm getting better at it.) I'm discovering the efficiency that comes of managing multiple Drupal sites. I've got three live ones on the go at the moment as well a few test sites. For the live sites I'm trying to follow good practice. Part of that is implementing only what you know. The efficiency comes in when I am able to propagate something new across numerous sites. Repetition, as Proust knew well, has a strengthening effect on memory. My learning curve gains breadth as well as height.

Not so long ago I met up with a number of people who make their livings setting up and maintaining Drupal sites. One thing that struck me was how many of them stuck to a very constrained set of parameters for clients. But it makes perfect sense. Their objective is both to provide the client with what he or she wants/needs while at the same time taking advantage of whatever efficiencies they can build into the process in order to minimize the time and labour cost of developing a new site. One person I spoke to said he could produce a new site, top to bottom, in 15 minutes (he was using the Drush Package Manager, which I'm not even thinking about at the moment).

There is a sense in which the more opportunities you have to exercise a new skill the less cost that is needed to reach a satisfactory end point for any of those opportunities. Which sounds rather convoluted. It's probably simpler to say that: less is more and more is less.

Content still matters

2010-11-09T08:17:00.002-05:00

Content is still king. I'm thinking here, initially, about blog posts but I also want to extend this thought to other forms of communication.

An old hobby-horse of mine is the empty, redirecting blog post: I can't stand them. Almost nothing irritates me more than a blog post that is merely a "pointer" to some other content on the Internet. Worse still is the post that is a pointer to a blog post which itself is merely a pointer to some further content. And so on.

I am stressing merely there (and here) because I think there is a useful place for secondary and even tertiary communications. A post that merely points to some other post is little more than a contextless citation. A post that, in the course of making some point or other, provides a link to some supporting documentation or content about which it is commenting employs secondary communication. There are even some sensible posts that are really tertiary communications surveying, often, a set of secondary communications. I can see the point of such posts or even such web pages though, yes, they tend to come from librarians.

But I would maintain that content, i.e. primary communication, is still king. Ultimately no matter how much fluttering you have (or need), communication is still about communicating content. And what is content? It might be an opinion (ideally backed up with reasons, but we can only hope). It might be substantive research. It might be reasoned argument, an amusing anecdote, a description, or a story.

I can illustrate this with the posts from this very blog. Looking at the stats that are available on the blogger dashboard I can see that some posts attract a considerably larger number of views over time than others. (And no, this series on communications is not one of my big hitters.) By orders of magnitude.

Which brings me to Twitter. I was wondering whether or not my observations would hold true in the land of 140 characters. And it seems that even there content rules. If you look at the tweets of those with massive numbers of followers, you will find that only the tiniest percentage of those tweets are pointers to some other content and almost none of them are contextless citations or mere pointers. Even on Twitter, primary communication is still valued.

This might be a good opportunity to raise a related point.

Twitter tweets, and FaceBook (FB) status updates did (although I don't think they do anymore), constrain the tweeter to a limited number of characters. Since some URLs are long, possibly very long, there is a clear need for some way to provide shortened URLs for the links one wishes to share. Fortunately there are very useful services that provide just that: http://bit.ly/ and http://tinyurl.com/ . Using these services you can transform a lengthy URL into something manageable. Great. The downside, of course, is that the now minuscule URL gives no clue as to the site it will take me to if I should click on it. Maybe that isn't a problem for most people, but I like to know where I'm going (as far as that is reasonably possible) on the Internet. Combine an obscured URL with an already constrained communications window of 140 characters and you have a near-recipe for the contextless citation.

It appears I've finally found something I dislike even more than a blog post that merely points me somewhere else. It's a tweet that points me somewhere else and doesn't give me any real clue as to where it is pointing me. Now there is a metaphor for something or other!

Cave imitator. Let the follower beware.

Gathering resources

2010-11-04T08:56:00.001-04:00

So far in this series I have been concentrating on websites and blogs over which I have direct control. It turns out, however, that the Internet, almost inevitably, contains a wide array of sites where you are mentioned or where material you may have written or contributed to appears but over which you have no direct control. Test it yourself by Googling your name, and be sure to use double quotes " " around it for a more useful set of results. (C'mon, you've done this before, you know you have!)

When I did this recently I found out two interesting things: first, there is still a fair bit of dross out there where my name appears but which has absolutely nothing to do with me; second, I re-discovered a number of presentations and articles I had written that I had forgotten about or lost track of. I immediately began to wonder whether it would be useful to draw the latter together in some way in order to make it easy for someone (e.g. a prospective employer, conference organiser, journalist) to get a quick overview of my output in a particular field over the years. A portfolio, if you will, but in particular a portfolio of items which I do not myself have the power either to remove or change.

If your name is more common than mine, or perhaps unfortunately shared with more famous individuals for whom you would not wish to be mistaken, then this might be even more pressing for you.

I have placed links to these presentations, articles, and briefing notes of mine on a Resources page on my main website and made that easily accessible. I suppose if I knew more about search engine optimization (SEO) I would know whether this helps or hinders the relative rankings of those resources in search engines. In any case, I haven't done this to aid search engines, I've done it to aid searchers. It isn't a comprehensive list by any means, but it is a list of resources with which I am proud to be associated. Moreover, if in future other things I write show up on the Internet on web pages I do not myself maintain, I will have a sensible place from which to link to them.

FSOSS 2010 - report

2010-10-29T20:11:00.002-04:00

Today I attended the always interesting FSOSS event at Seneca Centre for Development of Open Technology in Toronto. I had a couple of goals for participating in the event. I hoped to get myself plugged back in to the open source community (at least more than sitting in my office permits) and there were a number of talks (and people) that I specifically wanted to see. Despite some disappointments, the high points more than compensated.

Key for me in the morning set of talks was Dru Lavigne speaking on Finding a Community (Even if You're not a Developer). This was an excellent presentation - thorough, careful, and measured. Plenty here for anyone new to FOSS or anyone still trying to find their niche. Dru spent a fair bit of time outlining how to find a good fit for your skills. Clearly that is much easier if you are a developer and have a specific toolset. That rather narrows the field of projects to which you might contribute. But what if what you hope to offer to a FOSS project is documentation skills, or at least non-coding skills? Here the problem is that your skills are so general that you really could contribute to virtually any project. For me, the way to narrow the decision matrix in such a case is to find a project that you actually use and that you feel passionate about.

I was delighted to finally see Dru speak since I had been hearing her name (and seeing it) for some time. Worth the wait.

In the afternoon I went to a solid talk by Scott Nesbitt on FLOSS Manuals - Too Good to be True. FLOSS Manuals is the brain child of Adam Hyde, a New Zealander with a vision for facilitating documentation. And not just facilitating the creation of documentation, but rather getting documentation done! It is a long-standing truism that documentation is the bane of FOSS projects (well, any kind of project, really). Through the use of book sprints FLOSS Manuals helps with the rapid production and completion of user manuals. Scott detailed the book sprint that had been undertaken earlier in the week to create a user manual for Mozilla Thunderbird. He also pointed participants at the next generation of FLOSS Manuals, called Booki. Booki also has a Mozilla Drumbeat project, Open Web Publishing which is worth a look.

I wondered how the documentation effort in FLOSS Manuals co-ordinates or conflicts with the documentation efforts within a FOSS project. At least in the Thunderbird sprint key Mozilla Thunderbird developers directly participated. I'm not entirely certain I'm clear on whether or not the documentation effort of a FOSS project could get diffused by such work, but it's clear that these are also live questions that are being worked out directly in practice. Scott did a good job encouraging those present to explore FLOSS Manuals further and, if possible, get involved.

The final talk that I want to mention is the one entitled Mozilla Drumbeat: open innovation for all. I had been looking forward to hearing (and seeing) Mark Surman again. I was really hoping he would clear up some muddle-headedness that I'm suffering regrading the Mozilla Foundation Drumbeat effort. I totally get the idea of defending and extending the open web. I don't quite understand the Drumbeat spin on this. Alas, Mark dropped out of the event, apparently having slipped off to Barcelona to help prepare for the Drumbeat Festival due to take place there next week. Okay, fair enough. Barcelona does have its attractions. And it might also be warmer than Toronto at this time of year.

Fortunately (for us) Mark was replaced by Matt Thompson. Matt did a good job in Mark's stead. He gave a nice overview of Drumbeat's goals. He reminded us how Mozilla Firefox defended the open web not by lobbying the powers that be, but by simply building a better browser than the massively dominant IE that was threatening the open web. Today, of course, there are many new threats to the open web, not least the attack on net neutrality. Can the Mozilla Foundation find new ways to defend and extend the open web?

I don't know. The Drumbeat projects highlighted all seemed very cool. I could see how they would garner lots of participation from "the people formerly known as users". But I'm less clear on how they address the very things that Drumbeat itself identifies as threats to the open web. Of course, it could be that what really needs to be translated is the manner in which Mozilla built its fabulous open source browser. But then I would have thought I'd be hearing about a Mozilla Foundation project repository perhaps modelled on the Apache Foundation cohort of projects each of which partake to some extent in the well-tested development methodology found in the server project. There doesn't seem to be that kind of guidance for proposed projects at this time. But perhaps it is just too soon to tell. Matt described the past year as, effectively, Drumbeat in beta test mode. We should look for a major overhaul of both the website and (I think) the movement in the new year. No doubt that has something to do with what will be going on in Barcelona next week. If so, I look forward to the continued sharpening of the aims and objectives, and methods, that Drumbeat will seek to promote. I have a natural fondness for Mozilla, its browser, its Foundation, and a firm belief in its potential for good. I, for one, will be watching Drumbeat with anticipation in the weeks and months ahead.

All in all, it was a good day. I missed the presence of one or more significant keynote speaker. And I really don't need another metal liquid container (which seems to be de rigueur as a participant goodie at every conference these days). And no, an extra-large t-shirt is unlikely to fit me (luckily I managed to make an exchange for a more plausible size). But most important were the people I spoke to, ate with, shared a drink with. Because community really is what FOSS is all about.

Managing a frontispiece website

2010-10-28T11:09:00.001-04:00

With my blogs sorted for the moment, and at least the possibility of a tweet in the future, it behoves me to pay attention to my non-blogging websites. For this I have two (related) domains. One is essentially just a personal site for my friends and family. The content is variable, highly particular, and not really interesting to anyone for whom it was not intended. Unless you really, really want to know how to bake the best chocolate chip cookies in the world, ever :-)

The other domain, which I mentioned in my previous post on this subject, is a frontispiece for a sole-proprietor consultancy business I set up some years ago. Almost any work I do these days is some form of consultancy, so it seemed appropriate. But it isn't something that I intend to build into a vast business empire. So I want to keep that site mostly empty other than for contact details. People find out about me when they meet me in person, or, as per the norm, Google me, and if interested we take it from there. That's enough for me. I've got other irons in the fire that need tending. Still, it would be nice to do something a bit more useful with this site. For example, I would like to write an article on my explorations of Drupal (ongoing) and host it there. That might lead to other articles, maybe even one on thinking through your PIO. So that site might grow. Managing content there might then become an issue.

You do not need to take on a full-blown web-hosting package in order to maintain a small frontispiece web presence. There are numerous no-cost options available. Two that I have looked at are Drupal Gardens and Google Sites. They both have their strengths and weaknesses.

Drupal Gardens is very enticing for anyone who has played with Drupal, is shamefully inept at backend systems administration (as I am), and who longs for the eye-catching goodness of the soon-to-be-released Drupal 7. Of course my claim that one doesn't need to fully grok the Drupal backend is somewhat misleading. Once you get past the incredibly simple steps necessary to create a site, the user still finds himself or herself with a vast array of choices and decisions. Hard decisions. Despite being far more intuitive than the Drupal 6 interface, I think the user here will still want to go through some serious Drupal study and thinking. As per usual, Drupal 7 has almost limitless possibilities, but that may be too much for the simple frontispiece website. Nevertheless I'm going to keep exploring it in hopes that the veil will lift from before my eyes. It really is what I'd prefer to use.

Google Sites is equally easy to use in order to create a simple, or even a modestly complex, website. It is easy to enable co-operative website management. And there is plenty of room for growth beyond the 100MB of webspace a user is provided initially by moving up to the Premier Edition of Google Apps as and when it becomes appropriate. Indeed, if you are really just starting out, I think it would be best to simply start with the standard Google Apps package, which gives you Google Sites as well. The downside, at least for me, with Google Sites is the lack of rigour in its widgets. Whereas Google does a great job with the various widgets in Blogger.com, the comparable widgets in Google Sites are often just not up to the job. At least I've found many that didn't really work. Maybe it is different in the Google Apps version, I just don't know. Nevertheless, if all you really want is a simple frontispiece site, then Google Sites is fully able to provide that.

That brings me back to my thinking about my PIO. Do I really want or need a website that is substantially more than a frontispiece? That, as they say, is the real question.

Municipal elections

2010-10-24T15:15:00.000-04:00

Tomorrow is polling day for our city and region. I am fairly certain that nearly everyone I intend to vote for (for city council, mayor, regional council, and regional chair) will not in fact get elected. I still intend to cast my ballot. I think that's important.

It has been enlightening going through this election. After 3 years back in Canada, I sometimes forget that there are still many differences between here and the UK on which I have not yet had a chance to refresh myself. For example, municipal and regional politics here is not party political. In my ward, there are a large number of candidates for a single council seat. All I have to go on is what the candidates have said in their election materials or at the various of organised debates which have been well-reported in the local media.

There are also a couple of local plebiscites that will be on this ballot, both of which have been divisive in the campaign.

However, without party allegiances to fall back on I have found myself casting about in my own pool of thoughts, principles, and preferences. That has been useful because it has given me a useful matrix against which to test the opinions of those who would seek my support. Some things stand out for me. It turns out I don't really mind paying taxes, or even more taxes, so long as those funds are going to develop and enhance my community. So if your whole reason for being in politics is to ensure that I have an extra 50 cents in my pocket at the end of the year, you really need to look elsewhere. If the first thing you want to do once you get in office is to remove a piece of anodyne public site art, then look elsewhere. If you sign up to an aggressive campaign of fear-mongering pseudo-science, I'm sorry you'll have to look elsewhere. If you confuse public health issues with personal rights issues, again elsewhere.

That's just a sampling of what I've found in my personal selection criteria. It's surprising that there is anyone at all I'm willing to vote for. But I found enough candidates to make the short walk over to the polling station worth the effort. Sure, none of the candidates that I'll be voting for is likely to win. But they still need my vote. And I need it too.

Elections - they can be a useful tool for the personal as well as the political.

Blog use and first thoughts about Drupal

2010-10-23T10:06:00.006-04:00

Still no tweets from me, but I do now have 3 followers. Soon. The anticipation must be killing them. Meanwhile I have been busy sharpening up my various foci of identity online. For example, this blog has returned to its predominant themes of openness, free and open source software, and reflections on such software and the communities that grow and sustain it. Gone is the fun widget from LibraryThing displaying books that I have recently added to my catalog there (if you are reading this via an rss feed you may never have seen that). I have moved that over to my other blog, Transformative Explications, which focusses on books and writing. There is a link here in my blogroll. My thinking is that it is better to give these two passions a separate and distinct location on the web without trying to disguise that they are both a growing part of me.

My other blog is located on a domain I set up back in 2007: www.randymetcalfe.com. I hadn't done much with that domain or with the web hosting package that lies behind it, but I am now actively developing it.

You will notice, if you visit it, that the blog is a WordPress installation. WordPress is just one of an array of software packages available via the Fantastico De Luxe installer that comes with my web hosting package. Since my skills do not lie in system administration, this turns out to be a great way for me to experiment with and commit to using some FOSS. I'm happy with the WordPress install that I have but it doesn't prevent me from also living in the cloud over here at Blogger. Of course my needs are simple; more complex requirements might have necessitated a clear choice.

The other FOSS that I have been exploring of late is Drupal, which is also available to me via Fantastico. After a couple of test installs at different domains, I have committed to exploring Drupal more fully. To that end I have been patiently documenting my learning curve (more on that later) as well as looking for opportunities to engage with the Drupal community.

Drupal is not as simple to use as WordPress, clearly, but its capabilities are vast (limitless?) and to take full advantage of it my learning curve will need to go on for some time. I've made some initial moves on participating in the Drupal community - joining email lists, sitting in on IRC, even attending my local Drupal user group meeting this past week. I was also lucky enough to go to one day of the nearby Toronto DrupalCamp, where I saw Dries Buytaert, the founder of Drupal, give an inspiring talk. What have I learned so far, other than that I have a lot to learn? I've learned that the Drupal community is strong. It has a lot of small and mid-size web consultancy businesses actively participating within it. And there are a lot of people around with, it seems to me, a great deal of technical knowledge. Enough so that it will, I think, be a long time before I manage to find any way to contribute to this community other than by using the software and enthusing, where possible, about it.

If I have sharpened my use of my blogs in the past week, then I will have got somewhere. Still a lot more things to think about in this exploration of my PIO. But until then...