Resources.data.gov is an online repository of policies, schema standards, tools, best practices, and case studies to provide agencies a one-stop shop for resources related to Federal data management and use. Resources.data.gov provides the repository requirements of the Foundations for Evidence-based Policymaking Act and supplemental materials for the Federal Data Strategy. Resources.data.gov will evolve over time as a community resource to facilitate adoption of federal data resources. To facilitate collaboration across the Federal Government and in partnership with public developers, Resources.data.gov is published on the developer social network GitHub.
As the maintainers of Resources.data.gov, the General Services Administration (GSA), the Office of Government and Information Services (OGIS) and the Office of Management and Budget (OMB), are dedicated to maximizing openness, participation, and collaboration while ensuring the integrity of the resources hosted within the repository. This page provides information on ways to participate in the Resources.data.gov repository and how GSA, OMB, and OGIS will govern it.
Resources.data.gov is a collaborative, open source project. Both Federal employees and members of the public are strongly encouraged to improve the project by contributing. Fortunately, contributing only takes a few steps. Log into GitHub, click the “Edit this Page” button at the top of any page on this website, follow the instructions to “Fork this repository and propose changes”, make your edit, and fill out the form at the bottom of the page to “Propose file change.” Your changes will appear once they are approved. Ultimately, the goal is for users to contribute to the project by suggesting changes to code/content (making “pull requests”. However, there are many ways to participate:
- Browse. Look around at the different resources available.
- Clone. Copy code/content to your local machine. There is no official record in Resources.data.gov, and others cannot see what you do with the code/content.
- Fork. Copy code/content to your own repo in GitHub, and make modifications there. Record of the fork is seen in Resources.data.gov, and others can see the code/content, but it now resides outsides the Project.
- Comment. Comment on the code/content in Resources.data.gov using the issue tracker function. Others can see your suggested changes in a public log on Resources.data.gov. A moderator must accept, modify, or reject the comment in that public log.
- Contribute. Suggest changes to the code/content in Resources.data.gov by making a pull request. Others can see your suggested changes in a public log on Resources.data.gov. A moderator must accept, modify, or reject the suggested change in that public log before it becomes a part of the official code/content.
Resources.data.gov is managed by GSA’s Office of Products and Programs (OPP), OMB’s the Office of the Federal Chief Information Officer (OFCIO) and the Office of Information and Regulatory Affairs (OIRA), and the Office of Government and Information Services (OGIS). The Data.gov Program Manager, the Federal CIO, the OIRA Administrator, and the OGIS Director will be actively involved, along with members of their team. Approving Changes In GitHub speak, Resources.data.gov is actually a collection of resources managed as an open source project – i.e., users can make pull requests (suggest changes). The owners will collectively adjudicate the pull requests (accept, modify, or reject) in a public log on a standard release cycle.
- Technical Repositories Governance & Review Cycle (e.g., tools, schema standards)– Technical repositories will be maintained by staff within the GSA and OFCIO, with support from technical staff at GSA (i.e., the Technical Review Committee). All comments and proposed changes from the public or other Federal employees will be reviewed regularly by the Technical Review Committee, on monthly intervals. Additional stakeholders will be involved in review processes based on needed subject matter expertise.
- Metadata Schema Review Cycle Changes to the Resources.data.gov metadata schema will be reviewed on an ongoing basis. Starting September 2019 new releases of the schema will only be issued every year, as needed. Suggested changes that alter implementation and structure of the schema will not be merged in-between the regular release cycles, though discussion and commenting during these periods are encouraged. Each version of the schema will have a depreciation date of one year.
- Website Review Cycle Changes to the Resources.data.gov repository website will be reviewed on an ongoing basis. Starting September 2019 new releases of the website will only be issued every year, as needed.
- Implementation Guidance & Release Cycle (e.g., guidance) — Changes to repositories with implications for OMB and OGIS policy must be approved by OFCIO, OIRA, and OGIS policy officials, respectively. All comments and proposed changes from the public or other Federal employees will be reviewed by the appropriate staff on quarterly intervals. Additional Federal stakeholders will be involved in review processes based on needed subject matter expertise.
- Exemplar Resources & Release Cycle (e.g., case studies, playbooks, skill builders) — Changes to repositories that feature best-in-class examples must be approved by GSA, OFCIO, OGIS, and OIRA policy officials. All comments and proposed changes from the public or other Federal employees will be reviewed by the appropriate staff on monthly intervals. Additional Federal stakeholders will be involved in review processes based on needed subject matter expertise.
See our CONTRIBUTING documentation for more information on how to contribute.