Linux has proven itself as a server platform - no one really questions it. A large chunk (the majority?) of nonprofits already use Linux server-side - either in-house, or if not, their web host usually does. But can it really be a desktop platform for nonprofit organizations?

Linux on the desktop has come quite far, in just a few years. And recently, there is increasing evidence to suggest that it can, indeed in large part, replace Windows on the desktop. Why should it? Linux is more secure, more stable, and can be used on older hardware.

Walmart was selling $200 PCs running gOS (no, that doesn't stand for googleOS, but greenOS, based on Ubuntu 7.10,) and they sold out. If you read the reviews (most of which were quite positive,) the people who liked it were looking at the real functionality (it could edit their documents, it could surf the web, read email, etc.) and those who didn't, seemed not to like it mostly because it doesn't run Windows (although one could install Windows on it - but it's going to be pokey - it's not a well powered machine, but more than enough for Linux.)

So, if students and Grandma can use Linux, can nonprofits?

There is a good whitepaper that was released this fall from Novell, which has a section which talks about what to think about with enterprise migration to Linux on the desktop. It basically echos what I would suggest when thinking about a mass migration:

• Planning is key
• Do a software inventory - figure out:
  • What has a version that runs on Linux
  • What can be replaced by software that runs on Linux
  • What can be run in an emulator such as VMWare
• Identifying types of users (by what they need to do)
• Choose a distribution that makes sense (I wrote up a review of Linux distros recently.)
• Figuring out a clear migration strategy that takes all of this into consideration.

I'll be giving a free 14 week course on the free and open source database management package PostgreSQL under the auspices of Linuxchix. However, anyone can be involved in the course, as long as you follow the Linuxchix motto: "be polite, be helpful."

The course starts on November 19, and will be weekly lessons, with some assignments and discussion.

More info is available on the Linuxchix web site.

The amazing and wonderful folks at the ICT Hub have created a new resource, called "FOSS @ VCS" - which includes resources on services, training and certification.

Definitely a resource to watch.

Today, we're releasing the new version of the tried and true NOSI primer. "Choosing and Using Free and Open Source Software: A Primer for Nonprofits" is a no-nonsense, easy to read report that helps nonprofits understand what free and open source software (FOSS) is, what options are available for their organizations, and how they can access support for using FOSS.

The primer includes all of the basics, and also discusses how to look at TCO and strategic value in making decisions about FOSS. There are many case studies describing the use of various FOSS applications in the sector.

Fabulously, it also includes a live feed via API from Social Source Commons of a particular set of 5 FOSS toolboxes: software for the server, for the web, and for the three flavors of desktops, Windows, Mac and Linux.

The primer won't be printed this time - we have it in HTML format, and PDF. Please check out details on the update plans as well.

We're looking forward to your feedback and contributions!

As you might know, we're updating the NOSI primer, and we've gotten lots of interesting case studies of implementation of free and open source software in nonprofit organizations.

We're looking for one different kind of case study that we would like to write, something that wasn't present when we wrote the original primer: the relationships that have been built between nonprofit technology providers and open source development communities.

If you are a nonprofit-focused technology provider (nonprofit,
for-little-profit, or a big for-profit) and have *significant* relationships with a specific open source developer community (generally, this is because you have chosen to deeply invest in implementing their tool) I'd love to interview you.

By significant relationship - I mean more than submitting a few bugs now and again. Your developers are contributing code, or staff are contributing documentation, you've helped organize events, you've sponsored things. The lead developers are in your "rolodex" because you talk to them fairly often. That sort of thing.

Please email me as soon as possible! Also, email if you think you've got a great FOSS implementation story to tell!