On Wed, 13 Oct 2021 14:32:54 +1100 Yuchen wrote: > based on the ethical > repository criteria[1] it would probably get an F for failing C0, > because with LibreJS on I couldn't register a new account, nor > could I create a pull request.
pagure deserves some defense - the pagure devs have stated willingness to accept any and all patches for librejs - pagure.io logins are managed by fedora though - those are the folks who would need to be convinced to adapt for librejs, if pagure.io fails C0 for that reason the C0 question is essentially: * does any important functionality require non-free software? strictly speaking, a complete API satisfies C0, naturally; but not for the registration process example of important functionality: * can i register with librejs? No. IMHO, C0 is satisfied if either of the following such questions are true of each important feature (register, open a PR, etc) * can i ___ without JS, or without a web browser? Yes. the pagure API supports authenticated pull-requests it is a (non-web) interface to all important features (using the 'curl' web browser) https://pagure.io/api/0/#pull_requests-tab * can i ___ with librejs in a web browser? No. normally, the cause can be upgraded remote dependencies, but the librejs licenses table(s) were neglected - a routine maintenance task - the fixes would be tiny and accepted in short, i dont believe that C0 requires all important features to be exposed via the web interface - a complete API makes C0 a moot point, naturally a trivial example: the VCS server - the VCS server is an important feature (if not THE most important) - the forge is not expected to expose all functionality of the VCS server via the web inteface, nor to mimic a VCS client - i interpret C0 broadly, enough to allow any of all important functionalities to be satisfied by any mechanism operated by the same host - it is not important to me if all functionality is supported via the web interface, as long as it is possible, using some libre tool (eg: the 'git' or 'curl' programs)
