"Nobody has come up with a blueprint that says this is how social media must and will be used in all disasters, because it changes fast. We're trying to figure out how to get into conversations with the public without getting into one-on-one transactions, which would be next to impossible."
-W. Craig Fugate, Administrator of the Federal Emergency Management Agency, The Grill: W. Craig Fugate, ComputerWorld, March 21, 2011.
The use of content management systems in government is a personal and work interest of mine. There is actually a lot of diversity in what governments need their CMS to do and I'm curious to see how well the panel handles that diversity. Tony White, Ars Logica, is the moderator for this panel.
Leaders from Featured CMSes will be on-hand during this panel discussion to participate in a live analysis of the CMSes, asking probing questions of each, to determine how their represented Content Management System (and supporting community and infrastructure) best meets the demands of today's governmental needs, whether at a municipal, state or federal level.
Represented on this panel are: Lee Middleton (SilverStripe), Shaun Walker (DotNetNuke), Brian Colhounyan (TERMINALFOUR), Benjamin Mack (TYPO3), Ken Wasetis (Plone), Jeff Kline (Accrisoft), and Casey Neehouse (Umbraco). The following questions were asked either by the moderator, Tony White, or audience members. The panels' answers to these questions are paraphrased.
What features in your CMS make it a good choice for government?
"Information technology should enable government to better serve the American people. But despite spending more than $600 billion on information technology over the past decade, the Federal Government has achieved little of the productivity improvements that private industry has realized from IT. Too often, Federal IT projects run over budget, behind schedule, or fail to deliver promised functionality. Many projects use “grand design” approaches that aim to deliver functionality every few years, rather than breaking projects into more manageable chunks and demanding new functionality every few quarters.
“In progress.” When it comes to government, we hear those words a lot. It’s no surprise: meeting the needs of a geographically large nation with diverse constituents is challenging. Change and progress require time…and patience.
Technology is one area where progress is evident. Change is afoot everywhere, from optimizing government websites for mobile devices, to coordinated healthcare services and discussions about creating a national dashboard to share meaningful information. The goals are familiar:
Local Florida government delivers innovative Web services via open source CMS
Local governments throughout the country are under continuous pressure to do more with less, and Manatee County, Florida is no exception. They have a tiny IT budget compared to state and national governments, yet they are responsible for the bulk of everyday citizen services. In tight financial straits, the county could ill afford a costly proprietary system plus stiff maintenance fees for their new website IT. They turned their sights to open source alternatives, and found that Magnolia CMS fit the bill.
About Manatee County
I do my best to keep my two IT world's separated. One of those worlds of course is my obsession with content management systems which includes this blog and numerous discussions with almost anyone interested in CMS. The second world is my IT position as a federal employee for a small government field office. In order to avoid conflicts of interest, rarely do I allow those two worlds to cross one another. You'll find very little mention on this blog of my work for the federal government. At the same time, very few people in my agency are even aware of my CMS side hobby.
Earlier this week, Lullabot's Jeff Robbins posted an article about his company giving Drupal on-site training to employees within the Department of Commerce. In his post Jeff discusses the interest those employees have in Drupal as well as mentioning that the door continues to widen for Drupal in the federal government.
We had a great week of on-site training at the Department of Commerce in Washington, DC last week. They've already launched recovery.commerce.gov in Drupal and they're currently in the process of rebuilding Commerce.gov as a Drupal site. We spent the week with their team making sure that they understood not only how to build and present a Drupal site, but also the benefits of the Drupal community. They're a smart bunch and it's always fun to watch the synapses sparking as people realize all of the ways that they can snap together Drupal's pieces to create interesting web functionality.
There seems to be quite a buzz around Drupal in the government and as the Commerce team walked around the building with Drupal books under their arms, they got lots of comments from people in other bureaus, saying, "Oh! Drupal! We're thinking about using Drupal." Word is starting to get around about Drupal as a great platform for government websites.
Jeff Robbins is correct in saying that until recently, there was a lot of hesitation to using open source CMS such as Drupal for government portals and content delivery. I know earlier this decade my agency's Webmaster had considered using Drupal before deciding to build the agency's own CMS in-house. During this time period Drupal 4.5 was available but while my interest in information systems was growing, I had never really looked into Drupal (Mambo was in the open source CMS headlines back then) . However, just the possibility of my agency considering the use of Drupal during that time helped motivate me to learn more about Drupal.
I just finished reading an article from last Friday's Wall Street Journal, Gulags, Nukes and a Water Slide: Citizen Spies Lift North Korea's Veil. The article discusses how collaboration and tools on the Internet allows ordinary citizens to uncover secrets governments wish others not to see. In this case, using collaborated information and satellite images to uncover North Korea's infrastructure.
In the propaganda blitz that followed North Korea's missile launch last month, the country's state media released photos of leader Kim Jong Il visiting a hydroelectric dam and power station.
Images from the report showed two large pipes descending a hillside. That was enough to allow Curtis Melvin, a doctoral candidate at George Mason University in suburban Virginia, to pinpoint the installation on his online map of North Korea.
Mr. Melvin is at the center of a dozen or so citizen snoops who have spent the past two years filling in the blanks on the map of one of the world's most secretive countries. Seeking clues in photos, news reports and eyewitness accounts, they affix labels to North Korean structures and landscapes captured by Google Earth, an online service that stitches satellite pictures into a virtual globe. The result is an annotated North Korea of rocket-launch sites, prison camps and elite palaces on white-sand beaches.
This is a fascinating article from the WSJ and I'm sure this type of tech empowerment has both positive and negative consequences for our world. Having some background in remote sensing, I recall a conversation I had with a landsat specialist several years ago. During the conversation he mentioned the recent launch of some cheap satellites with 1 km resolution to be used for non-military geological surveys. I asked the question, "if a cheap satellite can produce 1 km resolution what resolutions can an expensive landsat satellite produce?". He replied such information was classified. As I said before, that conversation took place several years ago and I can only imagine how much the technology has changed since then.
There has been a huge transformation this year at WhiteHouse.gov. Blogs, RSS feeds, and connections to social networking sites are being fully utilized at the President's website. Those of us that have worked in information technology positions for the federal government have experienced first hand just how slow bureaucracies can be in taking advantage of newer technologies. From my perspective, it is almost surreal to see references to Web 2.0 from a website for an office that once didn't allow the President of the United States to send emails or even use a smart phone.