csteipp created this task. csteipp added subscribers: Andreasburmeister, csteipp, Tamslo, Liuxinyu970226, Lydia_Pintscher, Aklapper, Wikidata-Quality-Constraints, aude. csteipp added projects: Wikidata, Wikidata-Quality-Constraints, Security-Reviews.
TASK DESCRIPTION In it's current form (for as far as I've gotten in my review), the WikidataQuality extensions implement functionality that could be run entirely off toollabs. If there isn't a strong, long-term goal achieved by having the tools live on the cluster, then running them there needlessly increases our attack surface. It also means that updates to the constraint / validation data must be performed by a deployer, and significant changes in the future will need another security review. @aude / @Lydia_Pintscher, can one of you explain where this fits into Wikidata's long-term architecture, and why these tools need to be run on the cluster instead of a interacting with the wikis over the api? TASK DETAIL https://phabricator.wikimedia.org/T101303 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: csteipp Cc: aude, Aklapper, Lydia_Pintscher, Liuxinyu970226, Tamslo, csteipp, Andreasburmeister, Wikidata-bugs, dominic.sauer, Jonaskeutel, soeren.oldag, Tobi_WMDE_SW _______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
