Supported Open Source
I’m at an interesting intersection in my career path. I just concluded eight years at a small, statewide health care reform nonprofit in Massachusetts called Community Partners. I was Technology & Strategy Director there. Like so many orgs around us, we went under a month ago due to the bad economy. Though I am sad to lose my wonderful co-workers, it was coming for a long time, so I was somewhat prepared. A long time ago, other organizations and foundations started asking me lots of technology questions. This has naturally parlayed into consulting.
At this juncture where I have a sense of what it's like to work in a small org and am also looking at and helping larger orgs and foundations to make decisions about tech and use it in smart ways, I’m thinking a lot about something I call "supported open source."
"How do I choose a CMS?" is one of the most frequent questions I get. "Should I go with a closed but well-supported system or should I venture out into the Badlands of Open Source?" There is another way! That is supported open source.
The perception is often that if you choose open source—even if you hire additional expertise to initially build your site—you have to have skills in-house to keep it going after launch. I think the perception that you're on your own with open source is one of the barriers to its adoption for many businesses and nonprofits. But there are companies and consultants that will stick around, long after your site is launched, to give you the help and support you need. And there are different ways of doing this based on your org's budget.
At Community Partners, we ran things on a shoestring. I build web sites, but I don't write custom PHP code. When we wanted to use a profile module to collect contact information from users on our Drupal site and sync it with our Access mailing list database (yes, I know... Old Skool...), I found the module. It didn't work right. This functionality was a priority for us, though. Luckily, we maintained a contractual relationship with a Drupal consultant who would help us out with our site when our budget allowed. We only paid him to help us when something was broken, or when we wanted a new feature we couldn't implement ourselves and we had the funds to do it.
Having someone you can pay to give you support only when you need it is clearly cheapest way to go. If you're rolling in money, however, having a company on-call 24-7 to support you with anything you need is the other end of the spectrum. And everything in between exists. I want to disclose here that at present, I have a paid relationship with a consulting firm called OpenIssue LLC, which offers a spectrum of services for open source CMS platforms. I am working with them because I am becoming increasingly convinced that supported open source is has some serious advantages for our sector.
I am dogmatic about not being dogmatic, and the needs and mission of an org should always determine what technology they choose, not the other way around. You're never married to a piece of software and you should change platforms if and whenever it serves you. But particularly during this time of economic uncertainty, there is something comforting to me about software that's being developed by a worldwide brain trust. Open source software can't be yanked out from under you if funds (temporarily) disappear, or if a contract expires, because we all own it.
Though this community code base can be messy, open source development specialists know how to clean it up for you. So you get that worldwide scope of innovation, plus the focused attention on your org's particular needs. For orgs that want to stay innovative but don't always have cash flow, this can be a great solution. Ongoing support can be stopped and re-started as needed when there are budget troubles.
I know of a few companies out there that explicitly offer ongoing support for open source platforms. My fave among these is PICnet. Non-Profit Soapbox is designed to be an affordable, fully hosted, software-as-a-service (SaaS) way for nonprofits to build sites quickly and easily in the Joomla! CMS. PICnet has been around for a long time, and honestly I don't know why more companies aren't offering open source SaaS for nonprofits. Seems like a great idea to me. Here are a couple more companies that offer ongoing support:
At this juncture where I have a sense of what it's like to work in a small org and am also looking at and helping larger orgs and foundations to make decisions about tech and use it in smart ways, I’m thinking a lot about something I call "supported open source."
"How do I choose a CMS?" is one of the most frequent questions I get. "Should I go with a closed but well-supported system or should I venture out into the Badlands of Open Source?" There is another way! That is supported open source.
The perception is often that if you choose open source—even if you hire additional expertise to initially build your site—you have to have skills in-house to keep it going after launch. I think the perception that you're on your own with open source is one of the barriers to its adoption for many businesses and nonprofits. But there are companies and consultants that will stick around, long after your site is launched, to give you the help and support you need. And there are different ways of doing this based on your org's budget.
At Community Partners, we ran things on a shoestring. I build web sites, but I don't write custom PHP code. When we wanted to use a profile module to collect contact information from users on our Drupal site and sync it with our Access mailing list database (yes, I know... Old Skool...), I found the module. It didn't work right. This functionality was a priority for us, though. Luckily, we maintained a contractual relationship with a Drupal consultant who would help us out with our site when our budget allowed. We only paid him to help us when something was broken, or when we wanted a new feature we couldn't implement ourselves and we had the funds to do it.
Having someone you can pay to give you support only when you need it is clearly cheapest way to go. If you're rolling in money, however, having a company on-call 24-7 to support you with anything you need is the other end of the spectrum. And everything in between exists. I want to disclose here that at present, I have a paid relationship with a consulting firm called OpenIssue LLC, which offers a spectrum of services for open source CMS platforms. I am working with them because I am becoming increasingly convinced that supported open source is has some serious advantages for our sector.
I am dogmatic about not being dogmatic, and the needs and mission of an org should always determine what technology they choose, not the other way around. You're never married to a piece of software and you should change platforms if and whenever it serves you. But particularly during this time of economic uncertainty, there is something comforting to me about software that's being developed by a worldwide brain trust. Open source software can't be yanked out from under you if funds (temporarily) disappear, or if a contract expires, because we all own it.
Though this community code base can be messy, open source development specialists know how to clean it up for you. So you get that worldwide scope of innovation, plus the focused attention on your org's particular needs. For orgs that want to stay innovative but don't always have cash flow, this can be a great solution. Ongoing support can be stopped and re-started as needed when there are budget troubles.
I know of a few companies out there that explicitly offer ongoing support for open source platforms. My fave among these is PICnet. Non-Profit Soapbox is designed to be an affordable, fully hosted, software-as-a-service (SaaS) way for nonprofits to build sites quickly and easily in the Joomla! CMS. PICnet has been around for a long time, and honestly I don't know why more companies aren't offering open source SaaS for nonprofits. Seems like a great idea to me. Here are a couple more companies that offer ongoing support:
- Community IT Innovators (CITI)
- Jazkarta


Comments
Thanks, Thomas. I also have
Thanks, Thomas. I also have to say that my fave open source CMS platforms--Drupal, Wordpress and Joomla--are all written in PHP, and that's important to me. PHP is in wide use and is a very accessible programming language (heck, even I can successfully alter it). I know there are plenty of proprietary systems written in PHP, but I really like that those particular OS platforms use a common, flexible language. In the earlier days, when I didn't know any "Drupal developers" or "Mambo (Joomla)developers" yet, it was still easy to find someone who knew PHP and could help me out.
I was once involved in a the building of a very large, custom open source CMS/website in TCL, or "Tickle," and it quick became an albatross because... well... how much do we talk about TCL anymore? Not much.
Thanks for sharing your vendor, too!
I suspect (hope) that many of
I suspect (hope) that many of the vendors who advertised in the Consultant Directory of Idealware's Comparing Open Source Content Management Systems report would provide these types of services.
One of the benefits of supported Open Source is that if you have a falling out with one vendor, you can always go out and get another one without having to completely redo your site. To be fair, that's not exclusive to Open Source CMS, as some of the larger proprietary CMSes also have networks of vendors/implementation partners, but the selection of say, Drupal developers with nonprofit experience is much broader than the selection of Ektron implementors.
We've been happy with our Drupal vendor, Message Agency. We have a monthly support contract that includes security updates, configuration changes, and user support, and they've also been responsive and very fair when we request enhancements beyond the support contract. Our ongoing need for their help is such that the contract really makes sense, but they do straight hourly for some clients as well.
Thanks Kevin and Marc!
Thanks Kevin and Marc!
Bummer, HREF fail. I'll just
Bummer, HREF fail. I'll just say you can learn more about Rooty Hollow by copying & pasting this link: http://rootyhollow.com/
Also, I have not worked with them, but if our budget for hosting and support were larger, I would check out Advomatic's hosting and/or Drupal maintenance: http://www.advomatic.com/services/drupal-maintenance
Hi Johanna, great post and
Hi Johanna, great post and I'm glad to hear that you've been able to parlay your work at Community Partners into helping other nonprofits take advantage of open source.
Supported open source really does seem like the way to go. I think the greatest misconception that nonprofits can get into isn't that they'll be trapped in Open Source Badlands, but that the site will be "free" after it's developed.
Many organizations, including nonprofits, have invested serious dough into customized solutions and are excited by the allure of getting something built on a free and open platform. You raise an excellent point that nonprofits should be thinking about supported open source.
A few hours of a Drupal developers time are more affordable and go farther than the old customized contractors we're used to. But, nonprofits on open source will benefit from freeing up staff time and budgeting for the eventual white screen or new feature.
I've had a very positive experience working with Jim Taylor at Rooty Hollow on a contract basis for our website redesign and some additional theming and customization.
Johanna, an interesting
Johanna, an interesting option for "supported open source" is Acqui'a Subscription Model for the Drupal CMS. Check out their subscription options: http://acquia.com/product-matrix
You have the setup the site yourself, but then they'll support it.