Last modified: 2014-10-29 21:39:42 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T74525, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 72525 - harmonize Wikisource namespaces used by the ProofreadPage extension
harmonize Wikisource namespaces used by the ProofreadPage extension
Status: NEW
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: Wikisource 43934
  Show dependency treegraph
Reported: 2014-10-26 09:08 UTC by Ricordisamoa
Modified: 2014-10-29 21:39 UTC (History)
10 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Comment 1 wp mirror 2014-10-26 12:01:57 UTC
The list of non-standard namespaces for Extension:ProofreadPage is given in <> in the array `$wgProofreadPageNamespaceIds'.
Comment 2 Glaisher 2014-10-26 16:13:10 UTC
This is not that simple because we'll have to update the templates and scripts etc across the wikis as well.
Comment 3 Gerrit Notification Bot 2014-10-29 19:23:06 UTC
Change 169779 had a related patch set uploaded by Reedy:
Set a default for wgProofreadPageNamespaceIds
Comment 4 Gerrit Notification Bot 2014-10-29 19:25:11 UTC
Change 169779 merged by jenkins-bot:
Set a default for wgProofreadPageNamespaceIds
Comment 5 Sam Reed (reedy) 2014-10-29 19:27:12 UTC
(In reply to Gerrit Notification Bot from comment #3)
> Change 169779 had a related patch set uploaded by Reedy:
> Set a default for wgProofreadPageNamespaceIds

I'm not sure if 104/106 are the values that we "want" to use, but that is what most sites are using. To that extent, I just made/extracted a default value for these, and removed the "duplicates".

This makes the config clearer, and more obvious to see the anomalies..
Comment 6 Dereckson 2014-10-29 19:28:36 UTC
In this consultation, I note:
- the lack of strong support of Tpt, current current maintainer of Proofreadpage
- the very weak support of the proposal (but yes, it's a current recurring issue these last years)
- the need to take in account the charge in the databases

I consulted reedy on #mediawiki on the matter (who then created the patch noted in comment #3). Reedy considers "they're gonna be indexed updates, so it's a case of doing it as batched queries, waiting for slaves" and to not "see any obvious reason straight off why it shouldn't be doable".

As a next course of action, they suggests to count the number of affected pages, and to "come up with a rough plan of action".

Tpt knows of course well the issue to have play with this idea sometimes these previous years, so they is a good candidate for that.

[Taking back as NEW, the patch were only the first step to make the situation more clear in the configuration]
Comment 7 Tpt 2014-10-29 21:39:42 UTC
I support the project to move namespace ids for Page/Index namespaces to 250/252 that are the ones reserved by ProofreadPage extension. I'll be happy to help system admins in order to see if the migration if feasible on their side.

Note You need to log in before you can comment on or make changes to this bug.