Would this be a normal component?

Do we have any documentation about JSDuck (no pun intended) like a Wikimedia wiki page that at least explains how JSDuck is used in Wikimedia content?

Searching for jsduck in tasks: https://phabricator.wikimedia.org/maniphest/query/7tuls2.vdwJu/#R

In T134611#2295594, @Aklapper wrote:

Would this be a normal component?

I proposed tag, since it seems to me it is rather cross-component matter, and that's what tags are for...

Do we have any documentation about JSDuck (no pun intended) like a Wikimedia wiki page that at least explains how JSDuck is used in Wikimedia content?

No idea. @Krinkle may have?

Searching for jsduck in tasks: https://phabricator.wikimedia.org/maniphest/query/7tuls2.vdwJu/#R

I've done this search, hence I made the proposal... ;-)

I'm not convinced this tag would be useful. It'd be a lot of needless manual work and overhead to maintain for no benefit. What is the purpose of organising and discovering tasks of this sort? What task would be easier with this tag?

Tasks that relate to JSDuck from the perspective of setting up build/publish pipelines, that falls under Continuous-Integration-Config. It's not much different for CI config to set up JSDuck or any other job, so there's no value in grouping JSDuck-related tasks in CI-config.

Tasks that relate to JSDuck from the perspective of doc issues in specific repos should be filed under the relevant project directly. Perhaps global tags like good first task, JavaScript or Technical-Debt could be used to attract contributors. But I don't see any added value to tracking JSDuck separately.

@Danny_B: Could you reply to T134611#2296983 please?