Page MenuHomePhabricator

Investigation: explore permitting usage of campaign tools in other namespaces [3 days]
Closed, ResolvedPublic

Description

User story

As an organizer of a WikiProject (or other collaborative activities on the wikis), I want to be able to organize events with Event Registration in the namespace where I do my normal collaborative work, so that I can take advantage of the organizational and promotional features from Event Registration and the Collaboration List while still working in the spaces where my communities and contacts come together.

As a wiki admin, I want to be able to determine which namespaces are permitted to have Event Registration, so that will-intentioned organizers can use CampaignEvents tools in the spaces where people on my wiki usually collaborate together while bad actors are prevented from augmenting pages that should be left untouched by CampaignEvent tools.

Background:

We would like to make Event Registration usable for people who organize events outside of the Event namespace. The most common example would be WikiProjects, which often organize events (such as a monthly collaboration), but these events tend to be in namespaces such as: Wikipedia, Project, WikiProject, and sometimes even in the main namespace (in the case of Meta-Wiki). To do this, we need to allow organizers to add Event Registration to pages that are outside of the event namespace.

As an example, in italian:

Event page for a specific university: * https://it.wikipedia.org/wiki/Progetto:Coordinamento/Universit%C3%A0/UniCampania/Storia,_memoria_e_immagine_del_territorio_con_i_progetti_Wikimedia

For the MVP, we will only allow Event Registration to be added to an event page by the page creator -- in other words, we will keep the current status quo. So, if a WikiProject wants to use Event Registration, someone will create a subpage of the WikiProject and then enable registration. However, we may consider allowing other people to augment pages with Event Registration later on, especially in T385342.

We will only have automatic pop-ups for Event Registration on pages in the Event namespace. For alternative namespace pages, there should be no pop-up, since these other namespaces have many uses other than simply organizing events and collaborative activities.

This is a potential use case for Community Configuration, since different communities will probably want to whitelist different namespaces. We can perhaps have a default list of namespaces, but admins can change it.

If an admin removes a namespace that previously permitted Event Registration, I think we will probably want to keep the existing event data but prevent any future augmentation of pages in the namespace with registration data.

The goal should be to determine how to build a first quick version of this feature, which we can iterate on later.

Documentation & links:
Acceptance Criteria:
  • Investigate how we could allow organizers to enable event registration in alternative namespaces, so that:
    • A set of namespaces can be whitelisted to have the page creator add Event Registration
    • There should be no automatic pop-up, but the organizer should have a way to enable Event Registration
  • Consider how this could be done to have a default set of whitelisted namespaces, but with the option for admins to change the default via Community Configuration
    • Think about how things could work if an admin removes a namespace from the list that was previously allowed. If events were organized in that namespace before the removal, it is perhaps best to keep data from the old events but to not allow the creation of new events with event registration in the removed namespaces.
  • We would also want some logging in place so we can report on which namespaces are being used. For example, in March, we had X number of events, with Y number in the event namespace and Z number in the Wikipedia namespace.
  • Share any project risks, dependencies, or concerns that should be raised
  • Provide a technical proposal and/or rough prototype for how this could be done

Event Timeline

Dumping random thoughts:

  • Probably shouldn't be possible to remove Event: namespace?
  • Watch our for existing event pages in namespaces that were later disallowed (don't fail hard)
  • Make sure no "enable registration" popup/header on non-Event: pages.
    • Maybe idea for future: less visible entry point on non-Event: pages where registration is allowed
  • Re "everyone can enable registration for page even if not creator": watch out.
    • Maybe a separate user right given to admins?
    • Would make us reconsider assumption where page creator = primary organizer --> can't remove primary organizer from event
  • Generally watch out for existing assumptions and how we feel about them. Could help us think about T385342
ifried renamed this task from Investigation: explore permitting usage of campaign tools in other namespaces to Investigation: explore permitting usage of campaign tools in other namespaces [3 days].Feb 4 2025, 4:38 PM
ifried updated the task description. (Show Details)
ifried added a project: Campaign-Registration.

Change #1122207 had a related patch set uploaded (by Mhorsey; author: Mhorsey):

[mediawiki/extensions/CampaignEvents@master] [WIP] Enable creation of events outside of event namespace

https://gerrit.wikimedia.org/r/1122207

Tasks have been written for this epic, so I think this can be moved to product sign-off

This epic is now being actively worked on, so I'm marking this investigation as done.

Change #1122207 abandoned by Mhorsey:

[mediawiki/extensions/CampaignEvents@master] [WIP] Enable creation of events outside of event namespace

Reason:

no longer required

https://gerrit.wikimedia.org/r/1122207