Ryan Day

Would it be appropriate to add some info about using this flow on the advanced/security/oauth2-scopes/ docs page?

Adding a comment for searchability. This request was intended to enable GitHub Codespaces configuration. @msander did you ever create a blog post on this?

> @Ryandaydev, maybe you have a chance to merge it after 2 months since it was initially created? @tiangolo merges the PRs.

@gbinal The following can be removed from the list above because they are deprecated: - Corporate Consumer Contact Information - DigitalGov Search API (replaced by multiple APIs) - Non-Gov URLs...

Q1: Communicating stability Some options might be: - A published roadmap with time frames for new features versions, etc. - A general statement like "no changes planned for the near...

Q2a: communicating support Options include: - Some type of agreed stage or title like "alpha, beta, live" - a statement about how quickly you'll respond like "we try to answer...

@pammiller0 Testing and test data is another good topic to discuss and funnel to the standards. Here's an issue I created on that topic: https://github.com/GSA/api-standards/issues/42

@gbinal that is a good idea. I suggest at the same time you change the example from the SAM API to SF Tool because SAM is being deprecated. https://sftool.gov/developer/documentation

Review performed 9/2018. Updates have been made to data.gov, pending the harvest process working correctly.

@gbinal Suggest you update this or close the issue based on our recent inventory sprint.