Robert Accettura's
Fun With Wordage

A while back I asked a question about how companies deploy/update Firefox in the corporate environment. I got a fair amount of feedback on the issue. I wanted to post this a while back, but got sidetracked. Anyway here’s what I’ve put together after reading comments and emails about the topic.

Based on what I’ve read, and looking at where apps like Firefox and Thunderbird stand, I see a few possibilities to improve:

Provide MSI’s as a download

From what I’ve read, and some email’s, MSI’s seem to be the vehicle of choice for most looking to deploy an application because it’s fairly easy to use, and pretty common.

Better Documentation for Corporate Deployment

It seems part of the problem is corporate IT departments don’t see clear documentation on “how to”. A fix for this would be some good documentation on “recommended practices”. Some topics to discuss:

• How to disable auto update
• Prohibit installing extensions
• How to deploy updates with popular deployment tools and enterprise tools and technologies like Group Policy
• Discuss how the CCK could be helpful

Upgrade Recommendations

A big problem seems to be keeping things up to date. There are several complicated issues here. To discuss them briefly:

Policy Restrictions
In some cases, computers are locked down enough that auto update in Firefox won’t work since it can’t update files. This means an admin must interfere, and must know that they need to take some sort of action.

Internal Testing
Companies have strong testing policies in place because of internal apps that are business critical. As a result before something like a browser can be updated, it must be tested against these applications. How do we minimize the time from the release of the new version, to when a company actually deploys this. Obviously the less time involved, the better.

Update Notification
With auto-update disabled, how do companies know a new release has been issued? How can they easily keep up to speed, with low noise?

Solution
The first step has already been taken. Mozilla products have a very good versioning scheme and maintenance update release pattern. It’s also good that stable branches live for a while. This is essential for corporate deployments. It allows for some time between moving between versions (such as 1.0.x to 1.5.x). The release cycles work rather well.

There seems to be a need for an IT mailing list, that would notify IT professionals when a release reaches the RC (Release Candidate) stage, allowing them time to test the new version against their systems. Such notification should also contain changes made since the last release, but written in terms of “what to look for when testing” or “what impact these changes could have” (for example a change in how plugins are loaded/handled, requiring testing where Java applets are embedded in web pages). By sending these notifications first during the RC stage, it would allow for some time to do testing, and quicker deployment once the release is official. This is important in the case of security bugs being fixed, when exploits could quickly follow an announcement. The low noise of the mailing list would ensure IT professionals get notifications they need.

Conclusion

I’m curious how these proposals would work for IT departments, from what I’ve read and feedback I’ve received I believe this would allow for much easier adoption, without adding too much of a burden.

The UNIX Epoch is 00:00:00 UTC on January 1, 1970. That’s essentially the beginning of time for UNIX based systems. You know, “In the beginning when Ken Thompson and Dennis Ritchie created the /usr and the /etc“¹.

I’m curious if anyone has tracked down someone (preferably a geek) who was born on the Unix Epoch. I guess we can’t be too exact since the question would be “are you born when your head is out, or when your butt is out? Can the cord still be attached or do you need to be unplugged?” or something to that effect.

All kidding aside, it would be interesting to know if anyone has come to the realization that they are the Epoch Child. I’m not sure (any calendar scholars can help me out here), but it seems the last child to have a time standard’s origin coincide with their birth may have been Jesus (and obviously any other child born that night). In that case, it seems they likely it was rounded as best they could (see Wikipedia discussion of Jesus’s Birth Year and Date).

Remember to account for the timezone. For example if your born in New York, that’s -5:00. So anyone feel like finding him/her? Obviously some proof would be necessary to prove your the epoch child.

It would also be interesting to find some others, but this seems to be the most interesting.

¹ Yea, lame Genesis joke.

This article tries to explain why some websites with really ugly designs do so well regarding usage. I think it dances around the reality of the situation. These sites are ugly because they weren’t professionally designed. They were implemented to be functional and to get into the marketplace (budget/time/resource limitations). The reason they are successful is because they were either: innovative, viral (word of mouth), or just plain useful.

Design doesn’t make or break a website, the ability to expose usability and functionality of your product in a way the user can grasp with minimal effort is what ultimately is important.

The sites mentioned (Craigslist, MySpace, and Google) all have rather humble beginnings. None were started by the big companies. They were created people with an idea, not a design.

I guess it’s all about how you view things. You can either be vein, or be functional. In my opinion the gifted are the ones who are rather balanced between the two.

Looking at this map, it’s clear November 9, 2004 was D-Day for the open source movement. We can’t stop until Steve Balmer is in a hiding in a bunker under Redmond Washington.

Map by Steven Hilton copied per license in image to ensure availability.

I’m curious if anyone has tried Windows Live OneCare (via Amazon note: affiliate link used) with Firefox, and especially with Thunderbird. I personally haven’t tried it. A quick Google search doesn’t turn up to much info. Is it detecting viruses in emails correctly and problem free? Or is it causing chaos? I’d love to hear from someone who has used it.

As a reminder, just because you don’t use Outlook doesn’t mean your immune from viruses. You still need a virus scanner.

This video is priceless. A must see. You can hear everyone laughing in the background. Not to mention he was being very rational about the whole thing and poking holes in the proposed law.

Found here and mirrored below the break since things like this tend to disappear or move over time. This list is pretty good, haven’t verified all the facts, but they seem to be pretty accurate.
(more…)