anchor.diff:  
     <p>The focus of OSW is answering questions and to answer questions, we need to focus on data. The rest of the conversation will center on acquiring data, setting up infrastructure, and tuning our system.</p>
   
  -  <h2 id="infrastructure-capacity-and-cost-per-request">Infrastructure: Capacity and Cost per Request</h2>
  +  <h2 id="getting-started">Getting Started: Developing the Data Acquisition Process</h2>
   
     <p>We believe that developers should be able to see updated information from when they begin their work day to when they finish. For that reason we initially selected an <strong>8 hour window</strong> as our target.</p>
   
  
positive.code:         <li>Vrr-OOM! 1,000,000 Requests</li>
        </ul>
      </li>
      <li><strong>Rendering the Data</strong>
        <ul>
          <li>Putting our Thinking Caps Back On…</li>
          <li>Can we Cache the Query?</li>
  
negative.code:         <li>The Code: Tuning and Dequeueing</li>
        </ul>
      </li>
      <li>
        <a href="future-work">
          <strong>Future Work and Lessons Learned</strong>
        </a>
      </li>
    </ol>
  
    <h2 id="how-it-all-began">How it all Began</h2>
    <p>Open Source Watch started as a collaborative idea between <a href="<%= info[0][:email] %>"><%= info[0][:name] %></a>
    and
    <a href="<%= info[1][:email] %>"><%= info[1][:name] %></a>. We wanted to gauge the activity of open-source projects on Github and find out who the heroes of open-source are.</p>
  
    <p>The questions we asked were:</p>
  
  