Program Notes

Questions

• Do we want API.Data.gov to serve as a replacement for API documentation on their sites?
• How do we get more developers involved in API Umbrella?
• What are the goals we'd have other developers involved in API Umbrella?

Documentation To Do

• Agency Best Practices (url structure, usage, ...)
• Be thinking about what long range agency adoption looks like (many APIs across diff. bureaus/offices)
• FAQ, including help questions

Other To Do?

• Memorialize team roles, team processes
• All helpdesk requests through GitHub Issues

Site URLs (aside from agency documents)

• http://api.data.gov/contact
• http://api.data.gov/about/
• http://api.data.gov/docs/
• http://api.data.gov/docs/api-key/
• https://api.data.gov/signup/
• http://api.data.gov/docs/rate-limits/
• http://api.data.gov/docs/errors/

Project Roadmap Notes

3 Month

• Complete the two primary requested features:
  • More granular admin permissions (prevent other admins from viewing other agencies data): https://github.com/NREL/api-umbrella/issues/9
  • Programmatically manage API Keys (generation, block, revoke, etc): https://github.com/NREL/api-umbrella/issues/7
  • MyUSA
• Update the api.data.gov design to match the new Data.gov site.

6 Month

• Scalability and security
• Hackathon/training
• Figure out long-term hosting

12 Month

• GovX team project involvement
• Get others at GSA involved in the development
• Open source outreach

2014 Detail Goals

1. Feature Build Out

Need to represent more of this on a project roadmap to provide insight into this. Issue #91

2. Hardening

Issue #92 for coordinating this.

3. Replacing Self

Issue #90 for coordinating this.

4. Involvement with Team

This seems to be on track.