presidential-innovation-fellows/code-gov-web

<h1>What’s Required?</h1>
<p>
  The Source Code Policy was issued on August 8, 2016 and requires both agencies and OMB to take specific actions within 90 and 120 days, as well as on an ongoing basis. This section is meant to help agencies meet those deadlines and boot up their overall source code strategy.
</p>
<h2>Milestone - 90 Days</h2>
<p>
  November 6, 2016 will mark 90 days from the issuance of the policy. By November 6, 2016, the following must be accomplished:
</p>
<ul>
  <li>
    OMB must:
    <ul>
      <li>Launch <a href="//Code.gov">Code.gov</a></li>
      <li>Provide content on <a href="//Code.gov">Code.gov</a> regarding:
        <ul>
          <li>
            How best to measure source code (<a rel="noopener" pageScroll [routerLink]="['/policy-guide/policy/open-source']" href="#pilot-program-publication-of-custom-developed-code-as-oss">Section 5.1</a>)
          </li>
          <li>
            Advice on how agencies can strengthen internal capacity to efficiently and securely deliver OSS as part of regular operations (<a rel="noopener" pageScroll [routerLink]="['/policy-guide/policy/implementation']" href="#roles-and-responsibilities">Section 7.1</a>)
          </li>
          <li>
            Advice on existing code repositories and common third-party repository platforms that agencies can use to satisfy the requirements of this policy (<a rel="noopener" pageScroll [routerLink]="['/policy-guide/policy/implementation']" href="#code-repositories">Section 7.4</a>)
          </li>
          <li>
            Advice on various open source licenses that agencies can use when releasing custom-developed code as OSS (<a rel="noopener" pageScroll [routerLink]="['/policy-guide/policy/implementation']" href="#licensing">Section 7.5</a>)
          </li>
          <li>
            Insight into how agency implementation of this policy will be assessed by OMB (<a rel="noopener" pageScroll [routerLink]="['/policy-guide/policy/implementation']" href="#accountability-mechanisms">Section 7.7</a>)
          </li>
        </ul>
      </li>
    </ul>
  </li>
  <li>Agencies must:
    <ul>
      <li>
        Develop an agency-wide policy that addresses the requirements of the Source Code Policy and correct or amend any policies that are inconsistent with the requirements of the Source Code Policy (<a rel="noopener" href="/#!/policy-guide/policy/mplementation/#agency-policy">Section 7.6</a>)
      </li>
    </ul>
  </li>
</ul>
<h2>Milestone - 120 Days</h2>
<p>December 6, 2016 will mark 120 days from the issuance of the policy. By December 6, 2016 the following must be accomplished:</p>
  <ul>
  <li>
    OMB must:
    <ul>
      <li>Provide content on <a href="//Code.gov">Code.gov</a> regarding:
        <ul>
          <li>
            Metrics to assess the impact of the pilot program (<a rel="noopener" pageScroll [routerLink]="['/policy-guide/policy/open-source']" href="#pilot-program-publication-of-custom-developed-code-as-oss">Section 5.1</a>)
          </li>
          <li>
            Metadata schema to help agencies fill out their enterprise code inventories (<a rel="noopener" pageScroll [routerLink]="['/policy-guide/policy/implementation']" href="#code-inventories-and-discovery">Section 7.2</a>)
          </li>
        </ul>
      </li>
    </ul>
  </li>
  <li>
    Agencies must:
    <ul>
      <li>
        Update their enterprise code inventories using the metadata schema provided by OMB (<a rel="noopener" pageScroll [routerLink]="['/policy-guide/policy/implementation']" href="#code-inventories-and-discovery">Section 7.2</a>)
      </li>
    </ul>
  </li>
</ul>
<h2>Day 121 and onward</h2>
<p>After these initial deliverables have been met, OMB and agencies will work together to implement the policy and build overall capacity for code reuse and open source across the Executive Branch. Generally, agencies should plan to:</p>
<ul>
  <li>Update, refine, and expand their code inventories to promote government-wide sharing and reuse of code; and</li>
  <li>Build their internal open source pipeline in order to efficiently develop and publish open source code as part of the Open Source Pilot Program.</li>
</ul>