HN user

philipashlock

161 karma

I craft civic technology and coordinate open governance initiatives. I established Open311 which I began at OpenPlans and continued with Civic Commons. In 2012, I was a Presidential Innovation Fellow on Project MyUSA. Currently I'm the Director of the Data & Analytics Portfolio for GSA's Technology Transformation Services which includes Data.gov, the Digital Analytics Program, and Feedback Analytics

- http://phil.ashlock.us

- http://civicagency.org

Posts2
Comments29
View on HN

This is awesome, thanks for sharing! For those interested here are some similar recent or upcoming efforts to encourage more participatory and generative civic engagement:

Speculative fiction + civics

- https://open.usa.gov/national-action-plan/5/pilot-new-forms-...

Art x Climate

- https://www.globalchange.gov/content/art-x-climate-project-f...

- https://www.forbes.com/sites/evaamsen/2023/07/27/the-art-fea...

I Choose Optimism 4 years ago

Ecological and resource extractive debt is not magic, they have limits and externalities that most financial systems don't fully account for in their balance sheets.

For examples of the risk of unmaintained government websites, just see https://www.zdnet.com/article/government-shutdown-tls-certif...

Also note that Data.gov was participating in a Bug Bounty program through HackerOne which means it was actively encouraging people to find vulnerabilities but is no longer able to respond to them - https://hackerone.com/tts

Here's the official statement:

“As data.gov is not a static site, it requires staff monitoring and maintenance to be online,” a GSA spokesperson told FedScoop in a statement. “Because personnel that monitor and maintain the site are currently furloughed, data.gov redirects to usa.gov. The decision to take data.gov offline is consistent with previous funding lapse practices.”

Via https://www.fedscoop.com/data-gov-open-data-offline-shutdown...

@danso thanks for the feedback on data.gov. I'm part of the small (3 person) team that helps to manage it. If you have a moment to chat I'll see if I can reach out to you to see if you'd be interested in participating in some more in-depth user research in the future. Folks can also always leave feedback via email, github, twitter, and other means - https://www.data.gov/contact

The Federal Data Strategy will also be opening up for comments again in October - https://strategy.data.gov/feedback/

Data.gov and Federal agencies use the same metadata standard (DCAT) that Google Dataset Search is using so much of our metadata is also being syndicated there.

Technology Transformation Service (GSA, U.S. Government) | Web developer (frontend or full stack) | REMOTE or Onsite (DC, San Francisco, NYC, Chicago) | Must be U.S. Citizen or National | Full-Time | $103,672 to $134,776

We're hiring a developer to help support efforts to solicit and analyze public feedback on government service delivery.

Applications are due Friday November 10, 2017 11:59pm Eastern. For more details and to apply go to https://18f.gsa.gov/join/feedback-analytics-engineer-gs15/?u...

This position sits within the Data & Analytics Portfolio (Data.gov, Digital Analytics Program, Feedback Analytics) in the Office of Products and Programs - a sibling of 18F within the Technology Transformation Service at GSA.

https://www.gsa.gov/tts

For what it's worth, OMB is overseeing the Executive Order that requires agencies to compile these inventories. You can find more background at:

- https://project-open-data.cio.gov/

- http://www.digitalgov.gov/resources/how-to-get-your-open-dat...

And you can see how agencies are currently performing at http://labs.data.gov/dashboard/offices

Can you point to some examples or links for the .zzz files you mentioned?

I know this is an alpha release, but it's invitation only with the invitation being "help us shape the future of our network"

All of which comes across as being much less open and decentralized than the current web.

Even if the technology itself is more distributed than the common standards we're all using now, this sounds more like a walled garden than a truly open network.

AOL with Tor. Yay.

There's actually already work being done much like what you describe and it involved the first two rounds of Presidential Innovation Fellows - both to help shape the policy and to facilitate implementation. I'm referring to Project Open Data (http://project-open-data.github.io/) which is backed by an Executive Order to get every major federal agency to catalog all their data assets including those that are not and cannot be public. This full inventory is referred to as the Enterprise Data Inventory (EDI) while the portion of that covering anything that should legally be public is called the Public Data Listing (PDL). Every agency subject to this law is required to post their public listing in a standardized json file at the root of their agency website. The PDL is not only meant to point to datasets that are already publicly available, but it also requires agencies to list datasets that should be public, but have not yet been released or are not yet online. The datasets that are not legally meant to be public must be included in the EDI, but it's up to the discretion of the agency whether they want to list any in their public PDL. Some agencies have been doing that though. Otherwise, the full EDI with an accounting of all non-public datasets will really only be overseen by the White House Office of Manage and Budget and it's up to them to determine what kind of information they'll release about the EDI's they receive from agencies.

As agencies continue to release their Public Data Listings you should be able to find metrics about this at https://www.data.gov/metrics In the future that site should also include metrics like the number of unreleased datasets listed in their PDL data.json file.

Thanks for pointing this out. We've updated the highlighted dataset to something that is better maintained, but if you find other problems please do ticket them on github (https://github.com/GSA/data.gov/issues)

These kinds of issues will improve as a new approach to listing datasets is implemented. This is currently underway and is described on Project Open Data - http://project-open-data.github.io/implementation-guide/

We're also working on some basic automated tests to ensure listings have the correct MIME type (which is incorrect far too often) and that URLs aren't 404s or redirects or HTML pages rather than raw data.

For those interested, please do consider applying for the open position - https://www.usajobs.gov/GetJob/ViewDetails/363324500

I'll do my best to answer any questions about the position and the process of applying.

Thanks, that's flattering. I'm happy to try to answer any questions about this position as best as I can. You'd be working with me.

I also try to stay in #data.gov on irc.freenode.net, but haven't really promoted it so it's usually just me.

I would guess it's likely to be produced internally, but much less likely to be public. That said, if there's demand and there's enough good reporting, it seems reasonable to expect something worth reading.

It's also worth noting that Congress is threatening to cut the budget for the project that tracks overspending on IT projects - the IT Dashboard. While the IT Dashboard tool was properly open sourced and the codebase is doing well out in the wild, the continued use of it for the Federal Government isn't totally free, but the very small budget required to keep something like this running can prevent spending hundreds of millions of dollars on excessive IT projects.

For more info on budget cuts that could effect projects like the IT Dashboard, see: http://sunlightfoundation.com/blog/2011/11/16/crunch-time-in...

For information on the open source IT Dashboard project, see: http://civiccommons.org/2011/05/it-dashboard-six-weeks-in/

We hope the traditional procurement story will be improved with the help of Civic Commons, an organization which is very much aimed at leveling the playing field for government software. We want to make it easier for more developers and smart spry development shops to work on software projects for government. We want to give open source the same exposure as proprietary software and generally facilitate software co-creation and reuse across government to make sure things don't get paid for more times than they need to. You can learn more about us at http://civiccommons.org

The Civic Commons marketplace is currently still in closed beta, but it will be opening up very soon. Please sign-up: http://marketplace.civiccommon...