anchor.diff:          <h2>What are your requirements for submission?</h2>
   
           <ul>
  -          <li>Your software should be open source</li>
  +          <li>Your software should be open source as per <%= link_to "the OSI definition", "https://opensource.org/osd" %></li>
             <li>Your software should have a research application</li>
             <li>You should be an author (and copyright holder) of the software you are submitting.</li>
           </ul>
  
positive.code:         <p>We like to think of JOSS as a 'developer friendly' journal. That is, if the submitting authors have followed best practices (have documentation, tests, continuous integration, and a license) then their review should be extremely rapid.</p>
          <p>For those authors that don't quite meet the bar, please try to give clear feedback on how they could improve their submission. A key goal of JOSS is to raise the quality of research software generally and you (the experienced reviewer) are well placed to give this feedback.</p>
  
          <h2>The JOSS 'paper'</h2>
  
          <p>The JOSS 'paper' (the PDF associated with this submission) should only include:</p>
  
          <ul>
            <li>A short abstract describing the high-level functionality of the software</li>
            <li>A list of the authors of the software</li>
            <li>Author affiliations</li>
            <li>A list of key references including a link to the software archive</li>
          </ul>
  
  
negative.code: 
          <p>Before you submit we need you to:</p>
          <ul>
            <li>Make software available in an open repository (GitHub, Bitbucket etc.) and include an <a href="https://opensource.org/licenses">OSI approved open source license</a></li>
            <li>Deposit a copy of your software repository with a data-archiving service such as <%= link_to "Zenodo", "https://zenodo.org/", :target => "_blank" %> or <%= link_to "figshare", "https://figshare.com/", :target => "_blank" %> and mint a DOI for the archive</li>
            <li>Author a short Markdown paper <code>paper.md</code> with a title, summary, author names, affiliations, and key references. See an example <%= link_to "here", "https://github.com/arfon/fidgit/tree/master/paper", :target => "_blank"%></li>
            <li>Ideally we would also like you to create a metadata file and include it in your repository describing your software. <%= link_to "This script", "https://gist.github.com/arfon/478b2ed49e11f984d6fb", :target => "_blank" %> automates the generation of this metadata.</li>
          </ul>
  
          <h2 id="paper_structure">What should my paper contain?</h2>
          <p>JOSS papers should contain the following:
          <ul>
            <li>A list of the authors of the software</li>
            <li>Author affiliations</li>
            <li>A short summary describing the high-level functionality of the software</li>
            <li>A list of key references including a link to the software archive</li>
          </ul>
          As this list shows JOSS papers are only permitted to contain a limited set of metadata (see header below), Summary &amp; Reference sections. You can see an example paper <%= link_to "here", "https://github.com/arfon/fidgit/tree/master/paper", :target => "_blank"%>. Given this paper format it is <em>not</em>  permitted to write a "full length" paper i.e. one that includes software documentation such as API (Application Programming Interface) functionality, as this should instead be outlined in the software documentation.</p>
  
    <pre style="font-size: 15px; background: #efefef; padding: 10px 15px;">
    ---
  