model number of device:<br>

        version number of software on device (if applicable):<br>

        filename(s) of source candidate:<br>

        filename(s) of firmware image (if applicable):<br>

        how the firmware image was acquired (if applicable): [direct from device?  download page URL?]<br>

        text of the offer for source (usually required): [write it out, or attach a screenshot/picture]<br>

        where the source or offer for source was found: [manual in box?  CD?  web page adjacent to firmware download?]<br>

      </code>

      </div>

    </li>

  </ol>

  <p>There are many other ways you can help, regardless of whether you're a developer or not - see our <a href="https://sfconservancy.org/copyleft-compliance/help.html">Help Defend Software Freedom and Rights</a> page for details!</p>

  <section class="mb5">

    <h2 id="candidates" class="f2 lh-title ttu mt4 mb2">Source Candidates List</h2>

    <p>To join the public discussion of these candidates, please subscribe to our <a href="https://lists.sfconservancy.org/mailman/listinfo/ccs-review">ccs-review mailing list</a>.  We re-post especially notable email replies from this community mailing list in the candidate comments, alongside SFC and other official Use The Source comments on each candidate's page linked below.  A "round" indicates how many times we've received new candidates for a given device/firmware - if the round is "of N" it means we don't know how many rounds will be needed before we receive a compliant source candidate for the device/firmware.</p>

    {% for candidate in candidates %}

      <div class="mb3">

        <h3 class="f4 lh-title mt0"><a href="{% url 'usethesource:candidate' slug=candidate.slug %}">{{ candidate.name }}</a></h3>

        <p class="mb2"><em>Released {{ candidate.release_date }}</em></p>