I got two requests consecutively about adding Growth features to Wikisource.
This task's goal is to coordinate the thinking around Growth features and Wikisource.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T284485 Think about Growth features being used by non-Wikipedias | |||
| Open | None | T290441 Think about Growth features being used by Wikisource |
My notes from the Growth features workshop scope planning for Indic communities meeting:
Regarding SE tasks:
Pages of a book are connected through an Index. Maybe have a way to select Indexes of books that can be safely reviewed? They are categorized at most Wikisources. Going to the next task should rely on the table of content of a book, to give the next page to the user.
There is no structured content at Wikisource, it is just text. Querying validation work is done though checking on revisions, which are all stored at the same place. You can't get easily who validated a page for instance. It may be complicated to show the number for validations of a given user, compared to the number of edits.
Mentor module, Impact module and help panel (without SE guidance) seem okay to be deployed.
Two possibilities for the next steps:
It is still possible to deploy the features at a given wiki only for experienced users ("dark mode").
A broader consultation would to find new ideas would be nice.
There is no structured content at Wikisource, it is just text. Querying validation work is done though checking on revisions, which are all stored at the same place. You can't get easily who validated a page for instance. It may be complicated to show the number for validations of a given user, compared to the number of edits.
To know more,
for SuggestedEdits (SE), it is confirmed that Topics as they are designed now won't fit. Instead, it could be adapted to general topics: fiction, non fiction, poetry... There is a categorization of texts (style, author, etc.) at some Wikisources, but not all.
If we wanted to replace ORES topics (on some wikis) with some alternate framework with any kind of search-based topic system (categories, namespaces, templates etc), it would require some legwork but it's not conceptually hard. It would have to be something you can express via a search query, though.
Maintenance templates won't work, because there is none. There is actually not much templates and they are for content.
Same here (except the legwork part as it's mostly done already), as long as task types are based on something that can be expressed via search, it's not hard to add them.
deploy Growth tools, minus SD
T273837: When wgGEHomepageSuggestedEditsEnabled is false, homepage has a big blank space is probably a blocker to that.
Perhaps it would be possible to embed a condensed version of a community portal page https://en.wikisource.org/wiki/Wikisource:Community_portal as the main content area when suggested edits are not available.
Alternatively, one can copy/paste wikitext into the Banner module page; that could potentially work.
I just create a project page about Wikisource and Growth. Comments are welcomed at the talk page!
Not all books’ pages. On some Wikisources like French or Hindi, almost all pages are backed by ProofreadPage and its index pages, but others like Serbian or Hebrew have hardly any PP-backed works (statistics). For works not backed by ProofreadPage, its statistics are obviously of no use. Instead, some wikis have a {{TextQuality}} template, which may be useful to determine how ready these works are. (Although such works are much less useful for beginners: to proofread them, one needs to access the original work somehow, e.g. by finding a library that has it.)