
Austin's Resolution No. 20111208-074 committed the City Council to an Open Government Framework and told the City Manager to draft rules for open data, open source platforms, mobile apps and social media, with priorities and timelines.
What the resolution does
Adopted on December 8, 2011, this resolution is the starting point of Austin's open data story. Rather than ordering immediate publication, it asked the City Manager to work with the Community Technology and Telecommunications Commission on recommendations for an Open Government Framework covering four areas: open data, open source platforms, mobile applications and social media.
For open data, the council wanted rules based on a set of attached principles, along with limits for privacy, security and cost, a method for setting dataset priorities, a publication timeline for each department, a user-friendly portal design and ongoing metrics.
Adoption context
The resolution arrived as Austin was relaunching its website on an open source content platform with a data portal, and shortly after the city entered a partnership with Code for America. It sits among the earlier municipal open data policies in Texas and was one of several city actions in 2011 that treated open data as part of a broader open government agenda.
Key provisions
- A council commitment to transparency, efficiency and collaboration as open government principles.
- Direction to develop open data rules with a priority-setting program and per-department timelines.
- Guidelines for considering open source in procurement and for releasing city-built code for reuse by other governments.
- A request that staff identify funding needs and an implementation timeline.
- Regular progress reports to a council committee.
Guidelines this policy reflects
The original annotators did not tag this resolution in detail, so this index applies a conservative reading: it touches goals and values, prioritization, open code and timelines.
What happened next
Staff followed up in August 2013 with an Open Government Directive, described on the Austin 2013 directive page, which turned the council's goals into department-level deadlines for catalogs and high-value datasets.
Why this matters for your business data
Austin's council asked for priorities, timelines and metrics before publishing anything. A business preparing to monetize data benefits from the same discipline: decide which datasets are most valuable, how often they refresh and how you will measure demand. Start with how to value my data, or request a bid once you know what you hold.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Did the 2011 Austin resolution require departments to publish data?
Not directly. It committed the council to an open government framework and asked the City Manager to develop recommendations, including open data rules, priorities and timelines. Binding department-level requirements came later through the 2013 Open Government Directive.
Why does an open data resolution mention open source software?
Austin treated open source platforms as part of open government: code built by the city could be shared with other municipalities, and civic developers could contribute features. The resolution asked for procurement and release guidelines to support that.
Guidelines this policy reflects
Other policies in TX
Sources
Updated December 31, 2024.