I've made tasks for the first two. I'm not sure about the third--discussion seems to be ongoing in the RfCs in this notice and I'm not clear on what that implies for this bot. Citation bot already uses the pmid, doi, and jstor templates.

It is not clear how the bot is handling the deprecated "coauthors" parameter (in most cases, it seems to convert "coauthor(s)" to "author2"), but that may be part of the issue.

Discussion is ongoing at https://en.wikipedia.org/wiki/User_talk:Citation_bot#Citation_bot_progress . Changes to citation parsing/expansion will probably be needed before automatic submission of citations is allowed.

This is ready for testing on testwiki, as described here: https://github.com/fhocutt/citation-bot

This is ready for testing on testwiki, as commented here: https://en.wikipedia.org/wiki/User_talk:Citation_bot#Citation_bot_progress. I have disabled the second tickybox until it's clear whether I should figure out how to actually make it allow checking wikicode.

Commented asking for testers: https://en.wikipedia.org/wiki/User_talk:Citation_bot#Citation_bot_progress

A complication is that I'm not entirely clear on how it did work before the bot shut-off. My dev version seems to be expanding citations fine, but I don't see anything in the code that allows checking wikicode (as the second tickybox promises), so I am wondering how that actually functioned.

Some combination of Extension:BoilerPlate and Extension:Example are reasonably up to date.

• 1. Possible tasks for Revisionjumper:
• Fix https://en.wikipedia.org/wiki/User_talk:DerHexer/revisionjumper#Revisionjumper_option_in_Firefox_kills_section_anchor_links_to_oldid_revisions
• Write extension based on this

Potential tasks for Quick Intersection:

• Write documentation (probably on-wiki)
• If desired, port i18n capabilities from CatScan.

Potential tasks for Twinkle:

• Support @Huji in i18n/l10n; first, in figuring out a direction and breaking it down into tasks.
  • Investigate using JsonConfig for this
• Clear out the bugs in the issue tracker: https://github.com/azatoth/twinkle/labels/Bug

@Huji: my potentially less biased interpretation of that discussion is that you are correct on that agreement. I look forward to seeing what you come up with! If it looks like that will easily separate into tasks that others can help with, please post them here if you want to bring them to our attention.

Potential tasks for HotCat:

• T86142 - Deprecation of features used by HotCat makes core/extension JavaScript fail
• T103285 - HotCat doesn't load after saving a page in VE
• Refactor and update to use jQuery (if converting to extension, this would be part of that)
• Prepare for extension conversion: request and summarize community feedback for UI changes and any other integrated abilities (as from Cat-a-lot or Commons Commander)
• Convert HotCat to an extension

Potential tasks for Copyvio Detector:

• Find and fix memory leak. Probably not high enough impact.
• Add l10n/i18n support. Question: how effective is the tool for non-English content?
• Integrate Turnitin, as used in Plagiabot.

On exclusions, that seems like something that would be useful, but there would need to be different sub-lists for different uses--for instance, https://meta.wikimedia.org/wiki/Mirror_filter lists sites that are strictly Wikipedia mirrors, but my impression is that Copyvio Detector and Plagiabot also want to exclude sites that are partly mirrors but have some original content as well. I agree that it seems like a centralizable list, though.

Looking around, I've found next to no information or documentation on Quick Intersection and little discussion. It's listed on Wikipedia:Category intersection, but not on any of the pages about CatScan that I could find. It's mentioned on a handful of Commons user pages and a couple of times in various help archives. I couldn't find any references to it on es.wiki. There could be more in other languages, however.

@Magnus: That would be awesome. I'm not sure whether Labs is set up to handle that, but if there's a good base of people interested in a project like this, let us know!

Ways of finding images on or for Commons include the on-wiki search interfaces (Commons, media results in other wiki searches, VE's media search capabilities), associated tools (bots, or Labs tools), and external search interfaces.

@Magnus: There's http://search.creativecommons.org/ , a front-end to a number of CC web searches. It only searches one at a time, but it's at least a single starting point.

There aren't many bugs or feature requests that I could find. There is one bug that doesn't appear to have been fixed: https://en.wikipedia.org/wiki/User_talk:DerHexer/revisionjumper#Revisionjumper_option_in_Firefox_kills_section_anchor_links_to_oldid_revisions

@kaldari: My only concern would be whether the team is in shape to commit to an epic right now, and whether those small tasks will be useful on their own without considerable work being done on the existing gadget. But it's worth trying to find specific areas to improve.

Judging from the talk page, there's no obvious starting point--not much in the issue tracker, no real functionality requests on the talk page, bugs fixed quickly.

PageTriage's Phab tasks: https://phabricator.wikimedia.org/maniphest/query/GzOS3nN6qedA/#R

Thanks for the information, @TTO. That's very useful. We're still very much investigating and prioritizing our early work, but I hope that we'll be able to contribute.

Agree on all counts. We should keep converting it to an extension in mind when we have the capacity to plan for larger projects.

There don't appear to be many open bugs, questions, or feature requests, although there are some.

@Mooeypoo: Can you expand on what would be needed to support HotCat changes?

We are investigating. Please see T108630 and add any information you have.

Options I see:

• Leave it as is, and continue to accumulate hacks. Possibly: modify SecurePoll so poll content works with setlang, set uselang somewhere and pass it around with every request, provide a way for voters to change the content stored in the SecurePoll DB. Pros: If it's not broke, don't fix it. Cons: I'm not sure that condition is true (see the list of bugs above).
• Scrap the custom message system and modify messages through the MediaWiki: namespace. Translations would go at MediaWiki:message/lang for each message and language code in question and would be available through the message system. Pros: Only votewiki admins should have access to edit the MediaWiki namespace, so security should be maintained. Would allow us to use Language and Message as expected. Cons: Unsure how this works on third-party wikis. Probably not an intuitive interface for votewiki admins.
• Scrap the custom message system and put everything through TranslateWiki. Pros: easy to use all around. Cons: Insufficient security?

@Nemo_bis: "The manual language selector for 18 languages is clunky and unfair for the 330+ MediaWiki languages not listed."

@Nemo_bis: Yes. auth-api.php fetches a variety of user settings on the first visit to votewiki, one of which is language.[1,2] I'm not sure yet where this interacts with interface vs. content language. Votewiki language is stored in the voter db table as a "property".[3]

Related: T97923

Fields not rendering wikicode is not related.