Okay! I will have a look, then submit a patch for jstree first, and we can take it up from there.

In T398898#11150695, @Samwilson wrote:

Not quite, although we could perhaps open separate tasks for the remaining work if you want. That might make it easier for people to pick up bits of it.

I'd to try to tidy up jstree, select2, and jspreadsheet as they are currently documentation-only and contain local modifications that should probably be sorted out.

I want to pick this up later this weekend. Hope it's open.

@Reedy -- This ticket has a related patch in the parent ticket T330430. I don't know if it should still be open since the patch has already been merged.

In T398898#11120765, @Yaron_Koren wrote:

@Collins - thank you for creating this patch! This looks like a big improvement to Page Forms.

In T391414#10724997, @taavi wrote:

The relevant Gerrit group is self-owned so @Eugene233 should be able to do this without needing a Gerrit admin.

In T379996#10330447, @Aklapper wrote:

@Collins: Thanks. https://github.com/Wikidata-Cameroon/WDAudioLex-FE/issues exists. I strongly recommend against having two issue trackers (Github and Phabricator) leading to duplication and discussion fragmentation.

In T379995#10329281, @Aklapper wrote:

@Collins: Which "front end project"? Where to find the related code?

In T379996#10329280, @Aklapper wrote:

@Collins: Set up linting where? Which code project is this about and where to find it?

I will pay attention to extension versions and raise concerns if the MediaWiki version supported by the extension has to be changed.

In T316841#9970901, @Novem_Linguae wrote:

In T316841#9968821, @Samwilson wrote:

Some extensions still have master supporting ME < 1.39 so that should be taken into account with these patches (i.e. either update extension.json, or hold off on the change until the extension is ready to drop support for old versions).

Yeah, MediaWikiIntegrationTestCase->getDb() is @since 1.39, so we need to be bumping the extension.json file versions to 1.39 if it is <1.39 when we do this refactor. Does that make sense @Collins?

We should probably try to catch and -1 this in code review. Do we need to go back and fix any?

In T316841#9970883, @Novem_Linguae wrote:

Feels weird to mass refactor these without marking it as deprecated. They'll just creep back into the codebase if it's not marked as deprecated. Any objections to me writing a patch to deprecate protected $db? I would add something like @deprecated since 1.43. Use MediaWikiIntegrationTestCase->getDb() instead. This will eventually be made private.

In T352494#9388844, @apaskulin wrote:

Hi @Collins, Do you need any help working on this patch?

Hi, tried investigating where I can find the projects listed under the Volunteer section on the task description and I could not find anything.
Please any pointers, if it's not of high priority then it can be left out for now.