Re: What does it matter, gitlab.com does not meet C-level for a long time

[Aaron Wolf]

On 2019-10-31 8:09 a.m., Dmitry Alexandrov wrote:
> bill-auger <bill-auger@peers.community> wrote:
>> the answer is most likely that things have changed; and these things need to 
>> be re-evaluated from time to time - evaluations are done by members of the 
>> community - are you volunteering?
> 
> There is actually nothing much to volunteer to, I already mentioned all the 
> essential points: gitlab.com website is unusable without ad-hoc software, 
> which is not free because no sources are provided (sourcemaps are bogus).
> 
>> in my experience, github is very usable without javascript
> 
> There are some issues (long discussions, for instance), but yes, usable.  
> Plus, their official desktop client is nonfree merely to the same extent as 
> Firefox is nonfree, that is because of trademarks.
> 
> What spoils the things is the registration, which contains sophisticated 
> CAPTCHA.  Not the Googleʼs one like on gitlab.com, yet it imposes you to run 
> javascripts, which are not free.  And due to the very nature of CAPTCHA, I 
> bet, there is no chances to work around it.
> 
>> - the list was made several years ago now - probably all of the current 
>> examples should be re-evaluated
> 
> sf.net is also quite freedom-friendly nowadays, except, again, the CAPTCHA 
> while registration.
> 

On CAPTCHA, GitLab is in testing on the roll-out of a different
approach: https://gitlab.com/gitlab-org/gitlab-foss/issues/46548

Once that is complete, we'll have to reevaluate. It may be that this
fixes the primary violation they implemented after our initial grade
years ago.

signature.asc
Description: OpenPGP digital signature