On Thu, 2 Dec 2021 21:26:16 +0100 W. wrote: > Might that make pagure.io C0-conformant?
the formal review has not begun; so i can only speculate - it definitely removes one certain/known point of failure - thanks for the effort i pointed to the registration feature as the only pagure feature which is not accessible via the API - the registration/login process is the most typical point of failure (most websites would fail C0), eg: non-free captcha considering pagure's unique design, that all tickets are stored canonically under git, if the pagure API has reasonably complete feature-set too, i would put the one-time initial registration as the only C0 conflict (IIRC, logins pass already); though others may disagree that philosophical point has been raised only recently - there is not yet any consensus WRT all essential C0 features must work in icecat, or should any libre tools suffice (such as git, curl) if via an adequate, simple, libre-published, network API (or `man git`) - i suspect it may be the former
