GSA/code-gov-front-end

<h1 id="howombwillassessagencyprogress">How OMB Will Assess Agency Progress</h1>
<p>
  <a href="https://sourcecode.cio.gov/Implementation/" target="_blank">Section 7.7</a> of the
  Federal Source Code Policy states that:
</p>
<blockquote>
  <p>
    Progress on agency implementation of this policy will be primarily assessed by OMB through an
    analysis of each agency’s internal Government repositories, public OSS repositories, and code
    inventories on Code.gov, as well as data obtained through the quarterly Integrated Data
    Collection (IDC), quarterly PortfolioStat sessions, the IT Dashboard, and additional mechanisms
    [..]
  </p>
</blockquote>
<p>
  Generally, OMB's approach to assessing agency progress in meeting the Federal Source Code Policy's
  requirements can be broken into two categories:
</p>
<ol>
  <li>
    analysis of agencies' enterprise code inventories, individual code repositories, and open
    sourced code, with a
  </li>
  <li>
    comparison of that information against overall operational and financial data already collected
    by OMB.
  </li>
</ol>
<p>OMB will provide additional information about its assessment mechanisms over time.</p>
<h2 id="analysisofeachagencyscustomcode">Analysis of Each Agency’s Custom Code</h2>
<p>
  OMB will regularly review each agency’s enterprise code inventory to ensure that the agency is
  satisfying the requirements of the Source Code Policy. This review will include both the agency’s
  internal Government repositories and public open source repositories to ensure that each agency’s
  enterprise code inventory is properly reflected on – and easily discoverable through – this
  website.
</p>
<h2 id="analysisofoveralldata">Analysis of Overall Data</h2>
<p>
  OMB collects agency data through a number of existing mechanisms, including quarterly
  PortfolioStat sessions and the Integrated Data Collection. Much of this data is publicly available
  on <a href="https://itdashboard.gov">ITDashboard.gov</a>. OMB will use this data and other
  relevant information to better understand the overall impact of the Source Code Policy over time.
</p>