IT Infrastructure and Software Development from the Customer's Perspective
The CBC like many media outlets has been in crisis recently. On top of repeated cuts in government funding over the last twenty years, they’re suffering from the collapse of advertising revenue to traditional media, due to the television services’ dependency on ad revenue.
(U.S. readers: The CBC is the government-funded public television and radio broadcaster in Canada, like the BBC in the UK or the ABC in Australia.)
To me, the role of the CBC is to provide channels for Canadian cultural expression. Market forces will inevitably regurgitate what is produced by the massively-productive American media machine, so we need someone to provide the infrastructure for cultural dissemination. Nothing in that says that the CBC has to be a radio or television network in the traditional sense.
In the post-network, post-newspaper world, I think there are a lot of exciting opportunities for public broadcasters to facilitate even greater promotion of Canadian (or British, or Australian, or South African or New Zealand or …) culture. So here’s my road map for CBC over the next decade. It consists of two themes, distribution and production:
It should be obvious that people don’t think of network television or radio as their primary way of getting information or entertainment anymore. Music comes on a iPod. Video comes from YouTube. I want to listen to my local CBC radio morning show on my iPhone, because that’s what I take with me when I walk my dog. And I want to view CBC TV on all those devices, too.
CBC should stream all its content, in local timezones, and in open source formats. This means CBC should support open source projects that develop and/or package codecs and whatever other software is needed to ensure that users of all platforms have access to CBC audio and video content: Mac, Linux, Windows, iPhone, Blackberry, Android and other phone platforms. A lot of this technology is available already, but much of it is only accessible to us hard core geeks. It needs to be really easy for anyone to use.
Even more exciting is the possibility for production: Enable the public to produce their own high-quality podcasts and video. This means, again, funding open source projects to develop and package audio and video production tools. Having done a bit of screencasting, I know it’s not easy for the general public to do today, but we’re not a long way from it being easier.
The CBC, or Canadian universities, could also produce a series of screencasts or videos to show people how to produce content: A sort of on-line journalism and documentary production school. And there’s no reason to limit this to news and documentaries. The CBC, NFB and universities
This is technically feasible. I believe it’s economically feasible within a budget that CBC has or could get. Maybe they can cut real costs (rather than cutting services) from the traditional parts of the broadcast system by moving programs around on the Internet, instead of via satellite or other dedicated pipes. Maybe they can increase their budget, by showing the government they’re more relevant than they’ve been in years (not likely with Harper as PM, but he’ll be gone someday).
As I’ve been blogging about recently, I’ve been building a Drupal-based website for my son’s school’s Parent Advisory Council (PAC). As a geek, the technical nature of putting together a content management system like Drupal for a site is interesting, and I learned a lot. However, what really interested me is the social aspect of it.
You can’t have a business it seems without having a website. That must mean there’s value for a business to have a website. But is there value for a grassroots group to have one? If technology truly is neutral, then grassroots groups must be able to benefit from websites. (I’m not sure technology is inherently neutral, but that’s another topic.)
When we started, the PAC has a static HTML website updated infrequently by a parent who knew some HTML and how to FTP files to his server. It was out-of-date, since the parent’s children had moved on to high school and he was obviously not so active in the PAC. Members of the PAC did want some place to post meeting dates and minutes, and to publicize their activities, so I offered to help out.
We set up a committee with four members. I built a test site under my company’s site (jadesystems.ca) and we started to work.
Right from the start a few people really took to it and started to use it in ways that I couldn’t keep up with. This included translation into Chinese, especially after I enabled the translation modules in Drupal.
I also set myself up to do screencasts, and posted a number of them. It’s still early, but I’ve got some feedback from people that they find them very useful. For grassroots groups, where you don’t site face to face with people every day, I think screencasts are going to prove to be an excellent tool.
I think the main lesson I’ve learned so far is this: I like Drupal and it’s allowed me to do a lot. However, I can’t help feeling that I’m writing in assembly language for content management. What I mean is that I’ve had to learn too much about how the system works to get it to do what I want. We’re still a long way from grassroots groups being able to set up a website without someone with technical skills.
My dream would be something analagous to blogging. You simply go to a website and create your own community site. The task is inherently more complicated than setting up a blog, so it will never be as simple, but the skill set should be relatively similar. You should be able to pick and choose based on functions the user wants (e.g. a list of upcoming events), not functions based on how the programmer delivers them (e.g. a Views module with an obtuse and fragile configuration screen that lets you cobble together a list of upcoming events if you bang your head on it long enough).
The Parent Advisory Council (PAC) website is live at http://hastingspac.ca/ and is in a relatively stable form. Much work remains on the translations, but the bones of the site are there and it’s up to everyone else to put up the content (muscle).
I think we’ve got a pretty good site for a volunteer group. Our goal is to increase participation in the PAC to benefit the education of our children.
I’ll be posting more about the technology behind the site (Drupal and content management systems) this morning.
I’d love to hear comments and ideas you might have about the site.