Page MenuHomePhabricator

RFC: Support for user-specific page lists
Open, Stalled, LowPublic


  • Affected components: TBD.
  • Engineer for initial implementation: TBD.
  • Code steward: TBD.


(Define the problem you are seeking to solve.)


(Specify the requirements that a proposal should meet.)


(Proposals and considerations will be documented here.)

Take MediaWiki's implementation of watchlists and abstract it in to a more generic facility for working with user-specific lists of pages. Add wl_tag and wl_timestamp fields to watchlist table.

Event Timeline

tstarling raised the priority of this task from to Needs Triage.
tstarling updated the task description. (Show Details)
tstarling added projects: TechCom, TechCom-RFC.
tstarling moved this task to Inbox on the TechCom board.
tstarling changed Security from none to None.
tstarling subscribed.

ArchCom: defer due to lack of availability of Adam Wight.

Jdlrobson subscribed.

Wondering what this is blocked on... this is something mobile is keen to explore.

Unless anyone objects I'm keen to have a good at implementing this cc. @brion @ori

daniel subscribed.

JDlrobson's change Id31349cfa0d was abandoned. What's the status now?

So the Gather extension is currently in the process of being built. I'm hoping through that we can develop requirements and a proposal for how to structure a Watchlist 2.0 table at the end of this quarter.

I think iterating within the Gather extension is far safer than iterating on established stable code. We are hoping to build Gather with a database table that is compatible with the existing watchlist table with the view that in future we could import existing watchlist entries over to it. Does this sound a sane approach?

Nemo_bis removed a project: Gather.
Nemo_bis updated the task description. (Show Details)

Do we have a list of the existing list-like things in the MediaWiki universe? What comes to mind:

This RFC seems to be stalled. If there is currently no interest in driving this further, it should for now be removed from the RFC work board.
If there is interest in continuing the RFC process, please let us (TechCom) known who will be working on this RFC, and who commits to implementing it if approved, and in what time frame.

Perhaps it would be more useful to discuss how this relates to T164990: RfC: Reading List service, especially considering that reading lists is intended to allow offline pages to be updated when needed - which is equivalent to watchlist functionality (notification of edits).

The reading list service is cross-wiki and as a consequence it does not deal with "pages" in a way that would be meaningful for MediaWiki, just title strings. It would be nice to have a concept of remote pages but it's blocked on a large number of things (wikifarm support in MediaWiki sucks; most Wikimedia projects are not interwikis of each another; things like title validation are hard-coded to use the config for the current wiki etc) so I don't think it's a good idea to complicate this discussion with it.

@Tgr To me, what you just said is a very good reason to have that complicated discussion and remove those blockers. There doesn't seem to be enough "drive" behind the request for multiple traditional watchlists. Perhaps synergy with offline reading capabilities would fix that.

@Tgr do you think it is useful to keep this in the RFC process as it is now? Is there any commitment to work on a solution? If not, the RFC should be removed from the process for now.

@Tgr do you think it is useful to keep this in the RFC process as it is now? Is there any commitment to work on a solution?

If someone is interested in figuring out what exactly would be needed to cover both this and cross-wiki lists like the reading list service, I can work on that. If you mean commitment for actually developing that functionality, I don't think so (although maybe easier to say once we know what it is).

I still think a separate RFC about foreign pages or wikifarm configuration management would be easier to handle though.

In T1352#3888362, @Tgr wrote:

I still think a separate RFC about foreign pages or wikifarm configuration management would be easier to handle though.

Which have significantly more opportunities for synergy as well (shadow namespaces for global templates / gadgets / whatever in the first case, third-party wikifarm management in the second).

daniel changed the task status from Open to Stalled.Jul 22 2019, 5:05 PM

Closing as stalled, since nothing seems to be driving this.

JTannerWMF subscribed.

The Growth-Team is moving this to external as this seems to belong to TechCom

Krinkle renamed this task from RFC: Support for user-specific page lists in core to RFC: Support for user-specific page lists.Apr 3 2020, 9:44 PM
Krinkle updated the task description. (Show Details)
Krinkle subscribed.

This RFC was marked as stalled last year. The old RFC above is from 2013 and describes a specific implementation in fine detail. What's lacking is someone to drive the proposal and/or the implementation, starting with picking one or two use cases that it unlocks so that we contributors here on the task can work together towards making that possible (with that implementation or with something else).