Re: [Repo-criteria-discuss] What's needed to publish the evaluations (aka the longest email ever {aka two specific tasks})}

[Mike Gerwitz]

Attached is the updated page and a diff of the changes.

On Tue, Apr 12, 2016 at 12:59:24 -0400, Mike Gerwitz wrote:
> On Tue, Apr 12, 2016 at 11:52:33 -0400, Zak Rogoff wrote:
>> tl;dr: Mike, all you need to do to the evals themselves before
>> publishing giving to me to publish is update Github's C5 score and
>> update the date on the eval.

I removed the section from the evaluation entirely; choosealicense.org
isn't GitHub.com directly (and does feature GPLv3 as prominently), and
the license list when creating a new repo lists it second, before the
far-more-popular-in-most-communities-today MIT Expat.

But I noticed that the dropdown doesn't work without JS, so I added that
to the list as well.  Of course, they can just add a COPYING or LICENSE
manually.

>  You might want to add your name to it too.
I'm not sure where I'd add my name; we don't really have a spot for
that.  But that's fine.

signature.asc
Description: PGP signature

53c53
<         <th>Version</th>
---
>         <th>Criteria Version</th>
64c64
<         <td><a href="#Gitlab">Gitlab</a></td>
---
>         <td><a href="#GitLab">GitLab</a></td>
72c72
<         <td><time>2015-08-31</time></td>
---
>         <td><time>2016-04-13</time></td>
112c112
< <h3 id="Gitlab"><a href="http://github.com/";>Gitlab</a> — <a
---
> <h3 id="GitLab"><a href="http://gitlab.com/";>GitLab</a> — <a
124c124
<     (e.g. <tt>COPYING</tt>). (<a href="repo-criteria.html#B2">B2</a></li>
---
>     (e.g. <tt>COPYING</tt>). (<a href="repo-criteria.html#B2">B2</a>)</li>
146c146,147
<       <li>Enable and disable project features;</li>
---
>       <li>Enable and disable project features; and</li>
>       <li>Choose a license when creating a new repository.</li>
160,184d160
< 
<   <li id="GitHub-C5">GitHub
<     and <a href="http://choosealicense.com/";>choosealicense.com</a> goes
<     as far as possible <em>against</em> GPL within the bounds of
<     plausible deniability.  In other words, they do the absolute bare
<     minimum to just arguably pass this criteria.  This is the rationale
<     supporting this conclusion: (<a href="repo-criteria.html#C5">C5</a>)</li>
< 
<   <ul>
<     <li>They relegate GPL to the third option;</li>
<     <li>They make the wording to emphasize that Expat/MIT should be
<       the standard default;</li>
<     <li>They assert that <em>the</em> license to use for
<       patent concerns is Apache v2 (and they fail to mention
<       that GPLv3 deals with patents as well);</li>
<     <li>They carefully word the explanation of GPL to avoid
<       reference to passing on freedoms and only make it about
<       contributing code <em>back</em> (which is not actually the
<       correct interpretation of GPL);</li>
<     <li>They push people toward GPLv2, undermining GPLv3
<       adoption;</li>
<     <li>They describe GPLv3 as not an improved license but
<       characterize it to sound like it just has some meaningless
<       jargon most people won’t get or care about;</li>
<   </ul>
249c225
< to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
---
> to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>

signature.asc
Description: PGP signature

GNU ethical repository criteria evaluations

We maintain this evaluation report presenting the compliance level of popular sites to the GNU ethical repository criteria. There are some criteria that we can’t possibly verify, in which case we accept the site maintainer’s word on the matter. This evaluation is done by volunteers and you are welcome to contribute.

Site	Grade	Date	Criteria Version
GNU Savannah	A	2015-10-01	1.0
GitLab	C	2015-11-05	1.0
GitHub	F	2016-04-13	1.0
SourceForge	F	2015-10-07	1.0

GNU Savannah — A

Savannah has already acheived the highest grade for ethical hosting. These are the issues that would need to be addressed for it to earn extra credit:

• There are normal Web access/download logs which sometimes include IP addresses. (A+1)
• It follows EFF’s criteria only partially. Complying with the rest remains in progress. (A+2)
• HTML_CodeSniffer reports dozen of errors and warnings related to WCAG 2.0 compliance on every page. (A+3)
• There is no WAI-ARIA markup in its pages. (A+4)
• Currently there is no way of exporting data contributed by project owners or contributors. (A+5)

GitLab — C

Things that prevent it from moving up to the next grade, B:

• All _javascript_ code served to the client is free, but not LibreJS-compatible. (B0)
• Gitlab does not encourage adding a project license. Further, it does not recognize all existing license files (e.g. COPYING). (B2)

GitHub — F

Things that prevent it from moving up to the next grade, C:

• The following important site functionality doesn’t work without running nonfree or non-LibreJS compliant _javascript_: (C0)
• Change repository name;
• Change repository description;
• Delete repository;
• Add an SSH key;
• Pull request;
• Enable and disable project features; and
• Choose a license when creating a new repository.

Qualified passes for the next grade C:

• Although it doesn't deliberately discriminate any country, specific information may not be available in all countries by legal reasons. See roskomnadzor and export controls for more details. (C2)

SourceForge — F

Things that prevent it from moving up to the next grade, C:

• The following important site functionality doesn’t work without running nonfree or non-LibreJS compliant _javascript_: (C0)
• Create first project; (stumbles in phone verification)
• Upload files, create a folder or use interactive file manager;
• Enable, disable or delete reviews;
• Reply to, link to, edit, delete, mark as spam or add attachments to discussion posts;
• Create, delete, revert, add attachments to, or unsubscribe from wiki pages;
• Access wiki, code, ticket, discussion and blog administration menu;
• Access RW, RO and HTTP checkout commands;
• Browse commits;
• Merge code by merge requests;
• Subscribe/unsubscribe to code commit notifications;
• Add attachments to tickets;
• Bulk edit and move of tickets;
• Column sort and selection in ticket browser;
• Add, delete and edit ticket milestones and searches;
• Moderate or label discussions;
• Administrate forums;
• View statistics graph;
• Set project status;
• Upload a project icon;
• Install tools;
• Set user permissions;
• Its term of use states: (C2)

  Users residing in countries on the United States Office of Foreign Assets Control sanction list, including Cuba, Iran, North Korea, Sudan and Syria, may not post Content to, or access Content available through, SourceForge.net.

Please send general FSF & GNU inquiries to <address@hidden>. There are also other ways to contact the FSF. Broken links and other corrections or suggestions can be sent to <address@hidden>.

Please see the Translations README for information on coordinating and submitting translations of this article.

Copyright © 2015 Free Software Foundation, Inc.

This page is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License.

Updated: $Date: 2015/05/18 06:12:54 $

-- 
Mike Gerwitz
Free Software Hacker | GNU Maintainer & Volunteer
https://mikegerwitz.com
FSF Member #5804 | GPG Key ID: 0x8EE30EAB