Our non-profit builds Councilmatic - https://www.councilmatic.org/ - free & open-source tech for city-level civic engagement. Closing the feedback loop with local government, accessible tools for community dialogue.

But in my ten years' experience, here's what I see as the biggest potential for tech for social good: open data standards for constituent communications. Breaking public messages out of the current silo's of individual e-mails, e-petitions, social media, civic tech apps, and issue advocacy platforms. Making possible open structured data on real public priorities and policy preferences in every Congressional district. This never took off because government offices haven't wanted such a level of participatory democracy, and because existing advocacy groups haven't wanted to share membership lists and enable peer-to-peer organizing - it would undercut the business models of e-petition companies and legacy advocacy vendors and VC-backed civic startups. But making public opinion info more free and open for analysis could push forward reforms that have wide support, and are stymied by the current U.S. two-party system: http://www.participatorypolitics.org/open-data-infrastructur...

Indeed, our non-profit project OpenGovernment.org, launched in Jan. 2011, is still available in open-source code for legislative tracking: https://goo.gl/ThcG00. This includes the GovKit Ruby gem, which aggregates open government data with social context to make legislative info more accessible. We're always looking to re-boot OpenGovernment.org (OG for short) to focus on contacting state-level elected officials and discussing issues in the news on the open web - more about our goals of open data at every level of gov't: http://opengovernment.org/pages/about.html. And yes, as Derek said, check out Councilmatic for city-level transparency and engagement.

Great thoughts & articulations, @konklone, wanted to add my support. David here, our non-profit PPF created Contact-Congress project on OpenCongress in 2010 and launched the first version publicly in 2011 to automate delivery of digital messages to Congressional webforms. Really excited to see the evolution of the Contact-Congress toolset, now with the launch of Sina & EFF's & team's Democracy.io.

Our primary goal was a positive user experience for OpenCongress visitors, who mostly arrived via search for official information about bills in the news or legislative issues they cared about - to walk these interested bystanders up the ladder of engagement, enabling them to write an informed letter (using info aggregated uniquely by OpenCongress) directly on the page where they learned about a bill in context (both its official status and social comments / plain-language summaries).

A secondary goal of Contact-Congress was to give users an immediately-shareable permalink to their letter to their members of Congress (if set to public, as opposed to private) - to demonstrate the potential of Congress treating constituent communications in an open CRM, a public queue, with tools to enable constituents in-district to share helpful resources, timely updates, and organize around their initiatives. My PPF Blog post on this potential for in-district organizing, from May 2014: http://goo.gl/gCS0fy

A tertiary goal of Contact-Congress was to demonstrate public demand for open letters and open priority lists for their Congressional offices, and highlight the potential of open data standards for more constituent communications. This is what I've described as the greatest #opengov potential in my nine years in this field (http://goo.gl/crVivS) - better listening tools, as per @cjoh's priority request - I wrote: "Government staff have new access to dynamic, data-rich dashboards for opinions and feelings of their constituents – crucially, that integrate with their official CRM & CMS solutions, so a bigger-picture is generated, gathering more public feedback & specific expertise." Exactly such an open data standard already exists and has been successfully tested, a few years ago, with a U.S. Senate office. So what's holding back development and adoption of such a standard for delivery & verification of more communications, such as petitions, questions, volunteer offers, public testimony, community events? In my view, it's simply a lack of charitable funding support for open-data infrastructure for engaging with government offices - I believe this can implement more & better constituent messages to Congress, including geolocation features for constituent verification in cases where implemented, and better analytics tools for Cong. offices to respond to messages without being buried in a queue.

That’s a huge opportunity for non-profits and for-profit civic startups to provide the next generation of CRMs to government – investing in the infrastructure to make that possible now, by supporting the work of PPF and other non-profits, will help open up that data as widely as possible and ensure the participation tools developed on top of it are, at least in part, open-source for remixing. (My Dec. '14 blog post: http://goo.gl/AprZns).

David w/ the Participatory Politics Foundation here, we created & ran OpenCongress from 2007-2013, and now it lives with the Sunlight Foundation. I wrote about version control for legislation here on OC Blog in May 2012: http://goo.gl/Ll2rDs. I still think it's possible on a site like OpenCongress or GovTrack, it's possible on GitHub, and this non-profit is working on it directly w/ their MADISON platform for text annotation: http://opengovfoundation.org.