It appears to me – being new to this discussion and still learning the history – that the conversation about the new City of Austin Website is actually several different conversations. It might help the dialog to consider these somewhat independent issues separately. I do not claim to know the answers to most of the questions below, but I have learned that you have to know the questions before you can find the answers.
Question 1: Should the Website be built completely or mostly by Austin-based companies and people?
The answer depends on how you view the trade-off between having the best quality Website to serve the constituents versus investing in the Austin software development sector. The perspective of the Austin taxpayers should carry the most weight if this project is funded solely out of tax money. If on the other hand some organization promoting Austin high-tech wants to contribute funding (e.g. Chamber of Commerce, Austin Ventures), then the project should rightly showcase local talent.
Question 2: What should the Website do?
The city did a survey of nearly 2000 citizens over 18 months ago and produced a PowerPoint showing the results and suggesting feature priorities (available at AustinGO). The OpenAustin group has created a Web presence using IdeaScale, Twitter, and Facebook (none of them Austin-based companies) to allow free and open input about what the site should do.
Input is raw data and is useful but is not the same as a set of requirements. What is the process whereby the input will be converted to requirements? Did the most recent RFP adequately express the right set of requirements? Crowdsourcing approaches can help get more data from more people, but it needs to be processed into requirements.
Question 3: What are the legacy systems that will provide data to and get input from this new Website?
This is not a greenfield project. The city currently has a Web site with 40,000 pages and a great deal of data. How will the new Website integrate with and/or migrate from these systems? How will it pull together the different Websites that the city has today?
Question 4: Should the Website be built, to the greatest extent possible, with Open Source software?
This question is being debated throughout the government and private sectors, and it will not get resolved by this project.
However, I personally believe there is tremendous benefit to using Open Source software for a Website. Some think a project like this will cost a lot less with Open Source. While the overall cost may be somewhat less than with proprietary products, the real benefit is the ability for the city to shift expenditures from the vendor to internal investment. The sometimes very significant money spent with the proprietary vendor can instead be spent on increasing staff skills in understanding, using and modifying the Open Source software. This results in the city having more control over its own destiny. Rather than waiting for the vendor to add features, the city can make any changes it need in the Open Source projects it is using. The city also benefits from changes made by others.
And there are additional benefits to open collaboration. See the next question.
Question 5: Should the work product of the project be released as open source software?
I have a strong opinion on this topic. Regardless of whether the system is built using Open Source or proprietary (e.g. Microsoft, Oracle) software, the work product should be made available to the community as Open Source. For example, if the project builds a particularly clever way to display traffic information or to pay utility bills, then that solution could benefit other towns and cities. Also others may make improvements that the city could benefit from.
If the public is paying for this project, the work product should be public too. One exception might be if the software would expose some aspect of the city’s operation that is confidential. But in an open government policies, then there should be few of those if any. Another exception might be if, during the course of the project, the city made an invention that could be patented and used to generate revenue for the city. But does the city want to be in the software business?
Question 6: What specific technologies should be used in the Website (e.g. Plone)?
Specifying products or technologies that must be used in the solution limits the number of organizations and people who are available to build the solution. Except as it relates to required legacy integrations, the solution provider should be allowed to propose any product or technology. If the city thinks the proposed products and technologies have downsides, that will count against the bid in the review process. The city should let the vendors know what it’s biases will be in evaluating the proposals.
Question 7: Where and when should the Website provide only information rather than functionality?
When should the city spend the time and money providing Web pages for functions and when should it instead only provide data through an API? Going to the City of Austin Website from a browser is natural for many activities, like paying utility bills, getting permits, learning about the workings of the government. But I don’t think about going to the city Website for airport flight info, though it is available in the current site.
In building sites like this, the focus too often is on what will be seen in the browser and not on what can be accessed through an API and Web services. Increasingly users are spending time in sites like Facebook and expecting information they want to come to them. Hundreds of thousands of “mashups” have been built with all sorts of data. For each function in the site, the question should be asked: what is the relative importance of the browser function versus the available data? Given limited resources, some funcitons might be better provided only as API’s, possibly with simple “refereence” implementations to help mashup developers use them.
(Thanks to Dixon Dick for his edits.)