<div class="container">
  <div class="row">
    <div class="col">
      <div class="hero-small">
        <div class="text-center m-auto">
          <h1>About the <%= Rails.application.settings['name'] %></h1>
          <p class="lead">The <%= Rails.application.settings['name'] %> is <%= setting(:tagline).html_safe %></p>
        </div>
      </div>
    </div>
  </div>
</div>

<div class="container">
  <div class="row">
      <div class="col-lg-9" data-spy="scroll" data-target="#subnav" data-offset="0">
      <div id="about" class="generic-content-item">

        <%= render partial: "content/about/general" %>

        <div class="alert alert-primary" role="alert">
          <%= link_to "🎉 Volunteer to review for #{setting(:abbreviation)} &xrarr;".html_safe, setting(:reviewers_signup_url) %>
        </div>
      </div>

      <div id="submitting" class="generic-content-item">

        <h1>Scope & submission requirements</h1>

        <p>Not all software is eligible to be published in JOSS.</p>

        <h2>What we mean by research software</h2>

        <p>JOSS publishes articles about research software. This definition includes software that: solves complex modeling problems in a scientific context (physics, mathematics, biology, medicine, social science, neuroscience, engineering); supports the functioning of research instruments or the execution of research experiments; extracts knowledge from large data sets; offers a mathematical library, or similar. While useful for many areas of research, pre-trained machine learning models and notebooks are not in-scope for JOSS.</p>

        <h2>Scope and significance</h2>

        <p>JOSS publishes articles about software that demonstrates clear research impact or credible scholarly significance. Your software should represent a meaningful contribution to the research community rather than being a one-off tool for a single analysis.</p>

        <p>We evaluate submissions based on evidence of research impact, intellectual contribution, and good open-source practices. Some factors that reviewers and editors consider include:</p>

        <ul>
          <li>Evidence of research impact: publications or analyses using the software, external adopters or integrations, or credible near-term significance demonstrated through benchmarks and reproducible materials.</li>
          <li>Design thinking: meaningful architectural decisions, trade-offs considered, and conceptual frameworks that capture domain expertise. We value work that builds upon existing software ecosystems rather than reinventing solutions.</li>
          <li>Open development practices: sustained development over time with evidence of collaborative effort, public development history, comprehensive testing, clear documentation, and pathways for community contribution.</li>
          <li>Whether the software is sufficiently useful that it is <em>likely to be cited</em> by other researchers in your domain.</li>
        </ul>

        <p>In addition, JOSS requires that software should be feature-complete (i.e., no half-baked solutions) and designed for maintainable extension (not one-off modifications of existing tools). "Minor utility" packages, including "thin" API clients, and single-function packages are not acceptable.</p>

        <p>Projects developed privately are not eligible until there is a public record of open development: at least six months of public history prior to submission, with evidence of releases, public issues/pull requests. A history of contributions and engagement from individuals beyond the original team, across organisations, is especially welcome, though not essential.</p>

        <h3 id="ai-policy">AI Usage Policy</h3>

        <p><strong>Author use:</strong> The use of generative AI is permitted for most aspects of a JOSS submission (e.g., software creation and review, generating documentation, assisting with paper authoring), however all such use must be disclosed in an "AI usage disclosure" statement which includes:</p>

        <ul>
          <li><strong>Tool use:</strong> The tools/models used (and versions) and where they were used (code, paper text, docs).</li>
          <li><strong>The nature and scope of assistance:</strong> e.g., code generation, refactoring, test scaffolding, copy-editing, drafting.</li>
          <li><strong>Confirmation of review:</strong> Authors must assert that human authors reviewed, edited, validated all AI-assisted outputs and made the core design decisions.</li>
        </ul>

        <p>AI is not allowed for conversational interactions between authors and editors or reviewers unless it is being used for translation purposes.</p>

        <p>Authors remain fully responsible for the accuracy, originality, licensing, and ethical/legal compliance of all submitted materials. Failure to provide a complete and accurate disclosure of AI usage may be considered an ethical breach. Consequences can include desk rejection, mandatory revisions, and post-publication correction or withdrawal. In cases of intentional misrepresentation or non-disclosure, JOSS reserves the right to notify the authors' institutions, funders, and/or relevant professional or scholarly societies in accordance with standard research-integrity practices.</p>

        <p><strong>Reviewer use:</strong> Reviewers may use generative AI tools to assist with non-substantive tasks (e.g., grammar checks of their review text, contextualizing public materials and code snippets) and must disclose this briefly at the end of their review.</p>

        <ul>
          <li><strong>Accountability:</strong> The reviewer – not the AI – owns the evaluation. All judgements, recommendations, and technical claims must be the reviewer's and verified by them.</li>
          <li><strong>Human-only judgements:</strong> When reviewing JOSS submissions (code or papers), all evaluative decisions – scoring, accept/reject recommendations, and assessments of originality, novelty, correctness, significance, and policy/ethics compliance – must be made by the human reviewer. AI tools may assist with analysis, but they must not render or determine any verdicts.</li>
        </ul>

        <h3>A note on web-based software</h3>

        <p>Many web-based research tools are out of scope for JOSS due to a lack of modularity and challenges testing and maintaining the code. Web-based tools may be considered 'in scope' for JOSS, provided that they meet one or both of the following criteria: 1) they are built around and expose a 'core library' through a web-based experience (e.g., R/<%= link_to "Shiny", "https://www.rstudio.com/products/shiny/", :target => "_blank" %> applications) or 2) the web application demonstrates a high-level of rigor with respect to domain modeling and testing (e.g., adopts and implements a design pattern such as <%= link_to "MVC", "https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller", :target => "_blank" %> using a framework such as <%= link_to "Django", "https://www.djangoproject.com/", :target => "_blank" %>).</p>

        <h2>JOSS submissions must:</h2>

        <ul>
          <li>Be open source (i.e., have an <%= link_to "OSI-approved license", "https://opensource.org/licenses/category", :target => "_blank" %>).</li>
          <li>Have an obvious research application.</li>
          <li>Be feature-complete (no half-baked solutions) and be designed for maintainable extension (not one-off modifications).</li>
          <li>Minor 'utility' packages, including 'thin' API clients, and single-function packages are not acceptable.</li>
        </ul>

        <div class="alert alert-primary" role="alert">
          <%= link_to "👀 Full details about the #{setting(:abbreviation)} submission requirements and submission process&xrarr;".html_safe, "https://joss.readthedocs.io/en/latest/submitting.html" %>
        </div>
      </div>

      <div class="generic-content-item" id="editorial_board">
        <h1>Editorial Board</h1>

        <%- Editor.board.includes(:managed_tracks).order('last_name ASC').each do |editor| %>
        <%= render partial: "shared/editor", locals: { editor: editor } %>
        <%- end %>

        <h2 id="topic_editors">Topic Editors</h2>

        <%- Editor.topic.order('last_name ASC').each do |editor| %>
        <%= render partial: "shared/editor", locals: { editor: editor } %>
        <%- end %>

        <h2 id="editors_emeritus">Editors Emeritus</h2>
        <p><%= Editor.emeritus.order('last_name ASC').collect {|e| e.full_name
}.join(', ') %></p>
      </div>

      <div class="generic-content-item" id="publisher">
        <h1>Publisher</h1>

        <p>
          <%= setting(:abbreviation) %> is published by <%= link_to "Open Journals", "https://www.theoj.org", target: "_blank" %>, an online-only publishing collective <%= link_to "founded in 2016", "https://www.arfon.org/announcing-the-journal-of-open-source-software", target: "_blank" %> on the principle that rigorous, community-driven academic publishing should be possible without article processing charges or subscription fees. <%= setting(:abbreviation) %> is a diamond open access journal (free to read, free to publish) and was the first journal published under Open Journals, created to give research software a citable, peer-reviewed home without the administrative overhead that has historically deterred software authors from publishing their work.
        </p>

        <h2>Peer review</h2>

        <p>
          Every <%= setting(:abbreviation) %> submission undergoes full external peer review, conducted by independent reviewers with relevant domain expertise. Both the paper and the software are reviewed: reviewers evaluate the quality, documentation, and design of the software as well as the accuracy and completeness of the paper itself. Reviews take place openly via public GitHub issues in the <%= link_to "JOSS reviews repository", "https://github.com/openjournals/joss-reviews", target: "_blank" %>, meaning the full review record (all reviewer comments, author responses, and editorial decisions) is permanently and publicly accessible. Full details of what reviewers assess are described in our <%= link_to "reviewer guidelines", "https://joss.readthedocs.io/en/latest/reviewer_guidelines.html", target: "_blank" %> and <%= link_to "review criteria", "https://joss.readthedocs.io/en/latest/review_criteria.html", target: "_blank" %>; see also our <%= link_to "peer-review policy", "#ethics" %> below.
        </p>

        <h2>How JOSS works</h2>

        <p>
          <%= setting(:abbreviation) %> <%= link_to "heavily automates routine editorial work", "https://www.arfon.org/chatops-driven-publishing", target: "_blank" %> (PDF compilation, licence checking, DOI registration, Crossref deposit) so that editors can focus on what matters: ensuring reviews are thorough and that authors receive substantive, constructive feedback. Submissions, reviews, and editorial decisions all take place as public GitHub issues. This approach keeps our operating costs low (see our <%= link_to "cost model", "https://blog.joss.theoj.org/2019/06/cost-models-for-running-an-online-open-journal", target: "_blank" %>) while ensuring every step of the editorial process is transparent and open by default.
        </p>

        <h2>How our scope has evolved</h2>

        <p>
          Since launch, <%= setting(:abbreviation) %> has refined its scope twice in response to changing conditions in research software. In <%= link_to "2020", "https://blog.joss.theoj.org/2020/07/minimum-publishable-unit", target: "_blank" %>, we introduced clearer criteria for what constitutes a substantial scholarly contribution, responding to growth in submission volume and the need for consistent editorial standards. In <%= link_to "2026", "https://blog.joss.theoj.org/2026/01/preparing-joss-for-a-generative-ai-future", target: "_blank" %>, we updated our criteria to focus on human creativity, design thinking, and demonstrable research impact, a necessary response to the emergence of generative AI tools that changed the relationship between effort and code volume.
        </p>

        <h2>Transparency and operations</h2>

        <p>
          We publish <%= link_to "full submission and publication analytics", "https://www.theoj.org/joss-analytics/joss-submission-analytics.html", target: "_blank" %> and a detailed <%= link_to "breakdown of our running costs", "https://blog.joss.theoj.org/2019/06/cost-models-for-running-an-online-open-journal", target: "_blank" %>. <%= setting(:abbreviation) %> is staffed entirely by volunteers drawn from the research software community.
        </p>

        <h2>Fiscal host and publisher address</h2>

        <p>
          Open Journals is an online-only publisher and does not maintain a physical office. Open Journals operates under the fiscal sponsorship of <%= link_to "NumFOCUS", "https://numfocus.org", target: "_blank" %>, a 501(c)(3) nonprofit organisation that provides legal and financial infrastructure for open-source scientific computing projects. Correspondence requiring a physical address may be directed to NumFOCUS in their capacity as Open Journals' fiscal host:
        </p>

        <address>
          NumFOCUS, Inc.<br>
          5900 Balcones Drive #22663<br>
          Austin, TX 78731<br>
          United States of America
        </address>
      </div>

      <div class="generic-content-item" id="contact">
        <h1>Contact <%= setting(:abbreviation) %></h1>

        <p>
          For editorial enquiries (including questions about submissions, scope, review decisions, or editorial policy) please <%= mail_to "admin@theoj.org", "email the Open Journals editorial team" %> at <%= mail_to "admin@theoj.org" %>. This inbox is monitored by the <%= setting(:abbreviation) %> Editor-in-Chief, Arfon Smith, and the <%= link_to "Associate Editors-in-Chief", "#editorial_board" %>.
        </p>

        <p>
          For production matters (DOIs, metadata corrections, archiving), these are handled directly in the paper's GitHub review thread. The Open Journals technical team can be reached by tagging <%= link_to "@openjournals/dev", "https://github.com/orgs/openjournals/teams/dev", target: "_blank" %> in the relevant thread.
        </p>

        <% unless social_media_links.empty? %>
          <p>
            You can also find <%= setting(:abbreviation) %> at
            <%= social_media_links.to_sentence.html_safe %>
          </p>
        <% end %>
      </div>

      <div class="generic-content-item" id="code_of_conduct">
        <h1>Code of Conduct</h1>

        <p>Although spaces may feel informal at times, we want to remind authors and reviewers (and anyone else) that
          this is a professional space. As such, the <%= setting(:abbreviation) %> community adheres to a code of
          conduct adapted from the
          <%= link_to "Contributor Covenant", "http://contributor-covenant.org", target: "_blank" %> code of conduct.
        </p>

        <p>Authors and reviewers will be required to confirm they have read our
          <%= link_to "code of conduct", "https://github.com/#{ setting(:github) }/blob/master/CODE_OF_CONDUCT.md", target: "_blank" %>,
          and are expected to adhere to it in all <%= setting(:abbreviation) %> spaces and associated interactions.</p>
      </div>

      <div class="generic-content-item" id="ethics">
        <h1>Ethics Guidelines</h1>
        <p>We also want to remind authors and reviewers (and anyone else) that we expect and require ethical behavior. Some examples are:
          <ul>
            <li>All authors are obliged to provide retractions or corrections of any mistakes of which they become aware.</li>
            <li>Plagiarism (e.g., violation of another author's copyright), for both software and papers, is not allowed.</li>
            <li>Self-plagiarism (repeated publication of the same work) is not allowed.</li>
            <li>Author lists must be correct and complete. All listed authors must have made a contribution to the work, and all significant contributors should be included in the author list.</li>
            <li>Reviews should be accurate and non-fraudulent. Examples of concerns are: Authors should not suggest reviewers who are not real people or have conflicts (see <a href="https://joss.readthedocs.io/en/latest/reviewer_guidelines.html#joss-conflict-of-interest-policy" target="_blank">conflict of interest policy</a> for details). Reviewers and editors must disclose conflicts. Bribes for authors, reviewers, editors are not permitted.</li>
          </ul>
        </p>

        <b>Allegations of misconduct</b>
        <p>Allegations of research misconduct associated with a <%= setting(:abbreviation) %> submission (either during review, or post-publication) are handled by the Open Journals ethics team. Reports should be sent privately to <%= mail_to "admin@theoj.org", "our editorial team" %> at which point the report will be triaged by the Open Journals ethics officer to determine the nature and severity of the case. Options available to the Open Journals ethics officer range from recommending no action to instigating a full investigation by the Open Journals ethics team which may result in researchers' institutions and funders being notified and the <%= setting(:abbreviation) %> being retracted.</p>

        <p>Although <%= setting(:abbreviation) %> is not yet a member of <%= link_to "COPE", "https://publicationethics.org" %> (application pending), our processes are modeled on the <%= link_to "COPE guideline procedures for ethics complaints", "https://publicationethics.org/files/publication-ethics-editorial-office-cope-flowchart.pdf" %>.</p>

        <b>Complaints process</b>
        <p>Complaints about the conduct or decision making of the <%= setting(:abbreviation) %> editorial team can be sent to the <%= mail_to "admin@theoj.org", "Open Journals governance team" %>.</p>

        <h2 id="ethics-and-malpractice"><%= setting(:abbreviation) %> Publication Ethics and Malpractice Statement</h2>
        <b>Editorial Board</b>
        <ul>
          <li>The <%= setting(:abbreviation) %> editorial board's members are recognized experts in the field. The full names and affiliations of the members are provided on the journal’s website (see <a href="<%= setting(:url) %>/about#editorial_board">editorial board</a>). The individual editors' contact information are provided on that site, via their GitHub pages, and general contact information for the editorial office also on the <a href="<%= setting(:url) %>/about#contact">journal’s website</a>.</li>
        </ul>

        <b>Authors and Authors responsibilities</b>
        <ul>
          <li><%= setting(:abbreviation) %> does not charge any fees for manuscript processing and/or publishing materials, as is stated on the <a href="<%= setting(:url) %>/about#costs">journal's website</a>.</li>

          <li>Authors are obliged to participate in peer review process, as described in <a href="https://joss.readthedocs.io/en/latest/submitting.html#review-process">submission guidelines</a>.</li>

          <li>All authors have significantly contributed to the research. The submitting author is required to be a <a href="https://joss.readthedocs.io/en/latest/submitting.html#submission-requirements">major contributor to the software</a> they are submitting and the review process includes a check that <em><a href="https://joss.readthedocs.io/en/latest/review_criteria.html#authorship">‘the full list of paper authors seems appropriate and complete?’</a></em>.</li>

          <li>All authors are obliged to provide retractions or corrections of mistakes (see <a href="<%= setting(:url) %>/about#ethics">ethics</a> and <a href="https://joss.readthedocs.io/en/latest/paper.html#what-should-my-paper-contain">what should my paper contain?</a>).</li>

          <li><%= setting(:abbreviation) %> papers are required to have a <a href="https://joss.readthedocs.io/en/latest/paper.html#what-should-my-paper-contain">list of references</a>, and <a href="https://joss.readthedocs.io/en/latest/paper.html#what-should-my-paper-contain">financial support</a>.</li>

          <li>Forbidden to publish same research in more than one journal (see <a href="<%= setting(:url) %>/about#ethics">ethics</a>).</li>
        </ul>

        <b>Peer-review process</b>
        <ul>
          <li>All of <%= setting(:abbreviation) %>'s content is subjected to external peer-review. <%= setting(:abbreviation) %> uses an <strong>external peer review</strong> model: reviewers are independent volunteers from the research community, not members of the <%= setting(:abbreviation) %> editorial team. (See <a href="http://joss.theoj.org/about">about</a> and <a href="https://joss.readthedocs.io/en/latest/index.html">docs</a>.)</li>

          <li><%= setting(:abbreviation) %> peer-review is defined as obtaining advice on individual manuscripts from reviewers <a href="https://joss.readthedocs.io/en/latest/editing.html#finding-reviewers">expert in the field</a>. This advice is public, and is given to both the editor(s) and the author(s), with the aim of pointing out issues the reviewers believe are <a href="https://joss.readthedocs.io/en/latest/reviewer_guidelines.html#guiding-principles">insufficiently addressed for publication</a>.</li>

          <li>The <%= setting(:abbreviation) %> review process is clearly described on the <a href="https://joss.readthedocs.io/en/latest/reviewer_guidelines.html">journal’s website</a>.</li>

          <li>Judgments should be <a href="https://joss.readthedocs.io/en/latest/reviewer_guidelines.html#guiding-principles">objective</a>.</li>

          <li><%= setting(:abbreviation) %> reviewers should ideally have no conflict of interest. In practice, this is not always possible. If a reviewer has a conflict of interest, it must be declared and recorded, and the editors may <a href="https://joss.readthedocs.io/en/latest/reviewer_guidelines.html#joss-conflict-of-interest-policy">choose to waive</a> it if this is in the best interest of the review process.</li>

          <li>Reviewers should point out <a href="https://joss.readthedocs.io/en/latest/review_criteria.html#an-important-note-about-novel-software-and-citations-of-relevant-work">relevant published work</a> which is not yet cited.</li>

          <li><%= setting(:abbreviation) %> reviews are public and non-anonymous while in progress and post-review, as they take place via GitHub issues in a public repository.</li>
        </ul>

        <b>Publication Ethics</b>
        <ul>
          <li>All authors are obliged to provide retractions or corrections of any mistakes of which they become aware.</li>
          <li>Plagiarism (e.g., violation of another author's copyright), for both software and papers, is not allowed.</li>
          <li>Self-plagiarism (repeated publication of the same work) is not allowed.</li>
          <li>Author lists must be correct and complete. All listed authors must have made a contribution to the work, and all significant contributors should be included in the author list.</li>
          <li>Reviews should be accurate and non-fraudulent. Examples of concerns are: Authors should not suggest reviewers who are not real people or have conflicts. Reviewers and editors must disclose conflicts. Bribes for authors, reviewers, editors are not permitted.</li>
          <li>Minor fixes are processed by the Editors in Chief (EiCs), and are publicly handled based on requests from the original authors (managed in the GitHub review linked from the paper).</li>
          <li>Major corrections will be reviewed by the EiC and ethics team. If accepted, the paper will be re-published with an editorial note on the GitHub review (linked from the paper page).</li>
          <li>Retractions: EiC team and the ethics team review. If we deem that a retraction is warranted, we will update the paper and leave a retraction notice (<a href="https://joss.theoj.org/papers/c44313ada36f12eebbaff10eb0888071">see an example retraction for the linked paper</a>)</li>
          </ul>

        <b>Copyright and Access</b>
        <ul>
          <li><%= setting(:abbreviation) %> copyright and licensing information is clearly described on the <a href="<%= setting(:url) %>/about#content_license">journal’s website</a>.</li>
          <li>The journal and all individual articles are freely available to all readers.</li>
        </ul>

        <b>Archiving</b>
        <ul>
          <li><%= setting(:abbreviation) %> articles, metadata, and reviews are archived with <a href="https://www.portico.org/">Portico</a>.</li>
        </ul>

        <b>Ownership and management</b>
        <ul>
          <li>Information about the ownership and/or management of a journal is clearly indicated on the journal’s website (see <a href="http://www.theoj.org">http://www.theoj.org</a>).</li>
          <li>JOSS and the <a href="http://www.theoj.org">Open Journals</a> do not use organizational names that would mislead potential authors and editors about the nature of the journal’s owner.</li>
        </ul>

        <b>Website</b>
        <ul>
          <li>
            The JOSS website (see <a href="<%= setting(:url) %>"><%= setting(:url) %></a> and <a href="<%= setting(:url) %>/about"><%= setting(:url) %>/about</a>), including the text that it contains, demonstrates that care has been taken to ensure high ethical and professional standards.
          </li>
        </ul>

        <b>Publishing schedule</b>
        <ul>
          <li><%= setting(:abbreviation) %> immediately publishes accepted articles; it is not a serial publication.</li>
        </ul>

        <b>Name of journal</b>
        <ul>
          <li>
            As far as we know, the journal name (<%= setting(:name) %> (<%= setting(:abbreviation) %>)) is unique and not one that is easily confused with another journal or that might mislead potential authors and readers about the journal’s origin or association with other journals.
          </li>
        </ul>
      </div>

      <div class="generic-content-item" id="costs">
        <h1>Cost and Sustainability Model</h1>
        <p><%= setting(:name) %> is an open access journal <em>committed to running at minimal costs, with zero publication fees (<a href="https://en.wikipedia.org/wiki/Article_processing_charge">article processing charges</a>) or subscription fees</em>.</p>

        <p>Under the NumFOCUS nonprofit umbrella, <%= setting(:abbreviation) %> is now eligible to seek grants for sustaining its future. With an entirely volunteer team, <%= setting(:abbreviation) %> is seeking to sustain its operations via <%= link_to 'donations', "https://numfocus.org/donate-to-joss", target: "_blank" %> and grants, keeping its low cost of operation and free service for authors.</p>

        <p>In the spirit of transparency, below is an outline of our current running costs:</p>

        <ul>
          <li>Annual Crossref <a href="http://www.crossref.org/02publishers/20pub_fees.html">membership</a>: $275 / year
          </li>
          <li>Annual Portico <a href="https://www.portico.org/join/how-publishers-can-join/">membership</a>: $250 / year
          </li>
          <li><%= setting(:abbreviation) %> paper DOIs: $1 / accepted paper</li>
          <li><%= setting(:abbreviation) %> website hosting (Heroku): $19 / month</li>
        </ul>

        <p>Assuming a publication rate of 200 papers per year this works out at ~$4.75 per paper ((19*12) + 200 + 275 + 250) / 200.</p>

        <p>A more detailed analysis of our running costs is available <a href="http://blog.joss.theoj.org/2019/06/cost-models-for-running-an-online-open-journal" target="_blank">on our blog</a>.</p>

        <h4>Income</h4>

        <p>JOSS has an experimental collaboration with <%= link_to "AAS publishing", "https://blog.joss.theoj.org/2018/12/a-new-collaboration-with-aas-publishing" %> where authors submitting to one of the AAS journals can also publish a companion software paper in JOSS, thereby receiving a review of their software. For this service, JOSS receives a small donation from AAS publishing. In 2019, JOSS received $200 as a result of this collaboration.</p>

        <h4>Donate</h4>

        <p>Donations are one way for JOSS to offset our costs: <%= link_to image_tag("https://img.shields.io/badge/Donate-to%20JOSS-brightgreen.svg"), "https://numfocus.org/donate-to-joss", target: "_blank" %></p>
      </div>

      <div class="generic-content-item" id="content_license">
        <h1>Content Licensing & Open Access</h1>
        <p>
          <%= setting(:abbreviation) %> is a <a href="https://en.wikipedia.org/wiki/Open_access#Diamond/platinum_OA" target="_blank">diamond/platinum open access</a> journal. Copyright of <%= setting(:abbreviation) %> papers is
          retained by submitting authors and accepted papers are subject to a <a rel="license"
            href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International
            License</a>.</p>
        <p>Any code snippets included in <%= setting(:abbreviation) %> papers are subject to the <a
            href="https://opensource.org/licenses/MIT" target="_blank">MIT license</a> regardless of the license of the
          submitted software package under review.</p>
        <p>Any use of the JOSS logo is licensed CC BY 4.0. See the <code><a href="https://github.com/openjournals/digital-assets/tree/master/joss/logo" target="_blank">joss/logo</a></code> directory in the <a href="https://github.com/openjournals/digital-assets" target="_blank">digital-assets</a> repository for more information about it.</p>
        <a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons Licence" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a>.
      </div>
    </div>
  <div class="col-lg-3 about-nav">
    <div class="sub-nav">
      <nav class="menu" id="subnav">
        <a class="menu-item selected" href="#about">About</a>
        <a class="menu-item" href="#submitting">Submission scope</a>
        <a class="menu-item" href="#editorial_board">Editorial Board</a>
        <a class="menu-item" href="#topic_editors">Topic Editors</a>
        <a class="menu-item" href="#editors_emeritus">Editors Emeritus</a>
        <a class="menu-item" href="#publisher">Publisher</a>
        <a class="menu-item" href="#contact">Contact <%= setting(:abbreviation) %></a>
        <a class="menu-item" href="#code_of_conduct">Code of Conduct</a>
        <a class="menu-item" href="#ethics">Ethics Guidelines</a>
        <a class="menu-item" href="#ai-policy">AI Usage Policy</a>
        <a class="menu-item" href="#costs">Cost and Sustainability Model</a>
        <a class="menu-item" href="#content_license">Content Licensing &amp; Open Access</a>
      </nav>

      <a class="menu-btn" href="https://joss.readthedocs.io/en/latest/submitting.html">Author information</a>
      <%= link_to "🎉 Volunteer to review".html_safe, setting(:reviewers_signup_url), class: "menu-btn" %>
      <a class="menu-btn" href="https://joss.readthedocs.io/en/latest/reviewer_guidelines.html">Reviewer guidelines</a>
      <%= link_to "✨ Donate to #{setting(:abbreviation)}&nbsp;&nbsp;✨".html_safe, "https://numfocus.org/donate-to-joss", class: "menu-btn", target: "_blank" %>
      <%= link_to "Table of contents".html_safe, toc_index_path, class: "menu-btn" %>
    </div>
  </div>
</div>
