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

[Dmitry Alexandrov]

Aaron Wolf <address@hidden> wrote:
> On 2019-10-31 10:30 a.m., Dmitry Alexandrov wrote:
>> Aaron Wolf <address@hidden> wrote:
>>> 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).
>>>
>>> On CAPTCHA, GitLab is in testing on the roll-out of a different approach: 
>>> https://gitlab.com/gitlab-org/gitlab-foss/issues/46548
>> 
>> Nice to hear that, yet it does not amend the fact that gitlab.com 
>> webinterface is unusable without running nonfree scripts.
>> 
>
> Please distinguish between "nonfree scripts" and "librejs-unrecognized 
> scripts".

I do distinguish:
| Its web-frontend is absolutely unusable without running ad-hoc scripts, which 
are, of course, not marked as free in a way recognizable by LibreJS or in any 
other consistent way, and actually, they are _not_ free: sourcemaps are bogus.
— <address@hidden>

> "All client-side JavaScript (when served directly or after being compiled, 
> arranged, augmented, or combined), is licensed under the "MIT Expat" license."

A free licence is not enough to make a piece of code free.  The complete 
correspondent source should be provided.

signature.asc
Description: PGP signature