[caption id=”attachment_21645” align=”alignnone” width=”1024”] Photo: Kevin Harber[/caption]
Earlier this year, CityGrows co-founder Catherine Geanuracos proposed values for government technology, and its a great foundation for those serving government or the public to adopt.
These include:
- Transparency
- Interoperability
- Reflective of the community
- Experimentation and iteration
- Portability
- Participatory
- Open source
Catherine and co-founder Stephen Corwin also touch on the term “movement” as it relates to govtech or civictech, and it’s something I’ve been thinking about for a while now. Deeper thoughts on this are for another post, but I don’t think either are movements, particularly because there are no real fundamental principles folks in the community can agree on. In order to be a true movement, there must be hardened principles, and Catherine’s are the beginnings of this.
As Catherine mentions, I’m one who strongly believes open source should be at the top of the list, because this is fundamental to everything else below. Unfortunately, as with most government technology companies, CityGrows’ own statement around open source is fairly noncommittal. As mentioned in the post, they are “far from perfect alignment” with the proposed values, so I hope that over time they start to think more open when it comes to their own code.
For those that provide technology services or products to government in this maker meets creative commons day and age, it’s important to realize we live in different times. If you continue to use proprietary in your lexicon or business model, you’ve dated yourself and placed the emphasis on you, your motives and not those of the public.
While it’s tough to overcome the idea that we must control code to be viable, we must accept that even if your interface is better or you have a solid API, you’re only adding incrementally to the innovation and change that’s desperately needed. Eventually, your proprietary technology will be a just a modernized version of the technical morass government finds itself in today.
Open source isn’t just code, it’s culture. The technology license on your product is inherently attached to the civic culture you cultivate. Applying proprietary technology to government is giving license to closed government.
Catherine’s outline for government technology values is a great start. With more solidity on standards for each of these, govtech and civictech can become true movements. Until then, they’re still just industries with loose standards.