Page MenuHomePhabricator

Design: Develop event mode concept for tracking customization
Open, Needs TriagePublic

Assigned To
None
Authored By
ifried
Oct 16 2025, 8:05 PM
Referenced Files
F71522213: event mode (2).png
Tue, Jan 13, 11:25 PM
F71522208: multiple events.png
Tue, Jan 13, 11:25 PM
F71522200: event mode (1).png
Tue, Jan 13, 11:25 PM
F71522196: turn on event mode.png
Tue, Jan 13, 11:25 PM
F71522189: preferences.png
Tue, Jan 13, 11:25 PM
F66755422: Screenshot 2025-10-16 at 2.32.03 PM.png
Oct 16 2025, 9:33 PM
F66755420: Screenshot 2025-10-16 at 2.32.13 PM.png
Oct 16 2025, 9:33 PM

Description

User story:

Opting out: As an editor who is registered for an event that goes for a long period of time (such as 1 month or 1 year), I don't want to see the modal after every edit during the event period, so that I can easily edit for non-event related content and do not need to constantly state that edit is not part of the event.

Automatic tracking: As an event participant, I want to be able to automatically associate edits with events in a way that is easy and low-maintenance (but with the ability to make adjustments & changes), so that I can focus on the edit rather than the association and so that I don't need to think about the association with each edit.

Background:

Some desires that we know and want to address are the following:

  • Some editors want to opt out of tracking for some events: For example, some events may go on for 1 month or 1 year, and only a small percentage of edits done by the editor are for the event.
  • Some editors want a more streamlined and automated way to associate edits with events. For example, some editors may be doing multiple edits for an event within a period of time, and they would find it annoying or unnecessary to associate an edit with an event after every time they publish an edit. They know what they plan to do, and they just want to set up a tracking system for a period of time and then forget about it (or pay minimal attention to it).
  • Automation needs vary. Some people want all edits during the event period to be tracked for the event. Some editors only want their edits for a short period of time to be automatically tracked.
  • Some editors may want to opt out of any edit to event association at all (whether the modal or event mode). In the current implementation of Collaborative Contributions, there is no way to opt out.

In the past, we explored the idea of allowing editors to set their tracking preferences for each individual event. However, this became quite complex, since editors can be registered participants for multiple overlapping events that end at different times while we only want to associate one edit per event. Due to these circumstances, it can be quite messy to have automated tracking preferences that are set per event.

Instead, we're now considering allowing editors to have 3 main options that apply to all events: modal after edit, event mode, or no tracking system (and they can just manually add edits to events). If they want to use a different system during a certain event period, they can go into preferences and change their selection at any time. But the idea is that they have one main way of tracking event edits, with the new option that we're considering being event mode.

As for how event mode may work, we already have an early concept of event mode that was developed by Alex H. As next steps, we now want to apply what we know about Collaborative Contributions to provide a more detailed and specific plan for how Event Mode could be used to handle the ability to allow automatic edit tracking for an event.

Like the modal after edit, an advantage of event mode is that it is wiki-agnostic. It does not require a specific editing interface to work, so it can also be used on wikis like Wikidata. It is also a separate experience that we can modify, so we can later add an event logo, progress bar, or other visuals.

How it could work:

New section in Preferences for Collaboration statistics:

  • There can be a new section in Preferences > Editing > Collaboration statistics.
  • It will have the following options (with one option selectable at a time):
    • Show modal to associate edits with events
    • Allow event mode to associate edits with events
  • Default state can be modal after every edit, but it can be changed by users

Ability to pick if tracking on/off on per event basis:

  • Editors can choose if they have tracking support enabled on a per event basis via Manage Event Registration, in the following way:
    • Default selection: "Allow me to associate edits with events when I'm editing."
    • Other selection: "Don't allow the association of edits with events when I'm editing."
  • If editors pick "No automatic support," they can still manually add edits to an event
    • For example: Maybe they want the modal/event mode available for a shorter event, but perhaps they only want to do manual edit associations for a WikiProject that they very rarely contribute to or a larger event/challenge that goes on for a long period of time.

How users can learn that they can change tracking preferences:

Maybe there can be explanatory text at the bottom of the modal that says that they can change their tracking options via Preferences, with a link to the Collaboration statistics section.

How event mode can work:

  • If an editor is on a wiki that has an active event with Collaborative Contributions enabled,
    • They can see an indicator in the corner of the screen, where they can turn on Event Mode
      • If one event only:
        • Maybe it can show name of event
        • If selected, event mode is turned on & automatic tracking of event occurs
        • When event ends, indicator for event mode disappears
      • If more than one event: Maybe it can say "Event mode available" or "Pick event"
        • If selected, they choose which event & automatic tracking of event occurs

Visual examples from past work:

Event mode off

Screenshot 2025-10-16 at 2.32.13 PM.png (968×1 px, 669 KB)

Event mode on

Screenshot 2025-10-16 at 2.32.03 PM.png (1×1 px, 680 KB)

Event Timeline

ifried updated the task description. (Show Details)
ifried updated the task description. (Show Details)
ifried renamed this task from Design: Develop event mode concept for customization to Design: Develop event mode concept for tracking customization.Oct 16 2025, 9:56 PM

@JFernandez-WMF: One idea I am thinking about is that perhaps editors can set their preference for modal/event mode in Preferences, but they can determine if they want tracking for an individual event on/off in Manage Registration. The idea behind this is that one tracking preference (i.e., modal or event mode) should be specified, since it is redundant and cluttered to have both. This is a general decision that can be made by all editors. However, an editor can decide if they want the modal/event mode available at all for specific events (i.e., on/off) via Manage Registration. For example, I could see someone wanting the modal/event mode for some shorter events, whereas they may not want it for longer events or activities that have no end date (like WikiProjects), if we provide support to them in the future. In such cases, some people may prefer to manually associate an edit with a group or event, rather than seeing the event/group in a dropdown every time they edit. I added this new idea in the ticket, but wanted to share here in a comment since we didn't talk about it.

Also, this idea could be a bad one, so I am open to any other ideas you have!

ifried updated the task description. (Show Details)

these are the designs for event mode that were worked on to spark a conversation —

in preferences, the user selects that they want to associate their edits with events through event mode:

preferences.png (2×1 px, 568 KB)

event mode is off by default - we can inform that it is available. maybe we can have an info icon that on tap it explains what event mode is, how it works, etc.:

turn on event mode.png (1×786 px, 775 KB)

if only one event active, then when turned on we automatically assign that event to event mode. the user already explicitly turned event mode on, asking them to make again a decision may add friction to the flow:

event mode (1).png (1×786 px, 775 KB)

if there are multiple events that are active, then let the user be able to select which event they want to track their edits towards - we can have a placeholder that says ‘Pick an event’.

multiple events.png (1×786 px, 777 KB)

when the user expands the selector a menu comes up.

event mode (2).png (1×786 px, 783 KB)

^^these designs are exploratory. moving to prod sign off to determine next steps