User stories:

As an event organizer, I want to be able to set a goal for my event, so that participants are motivated to join and contribute based on the goal, and so that I can have a clear story of the event outcome based on the goal.

As an event participant, I want to know how my contributions help accomplish the goals of the event, so that I can understand the impact of my edits and of the event overall.

Background:

When editors first create accounts, there may be some basic milestones for them to reach that are accompanied by simple notices, such as reaching 100 edits or 1000 edits. But what about after that? How can editors continue to feel motivated to edit, and how can they have goals that are meaningful to them and/or the communities they collaborate with on the wikis?

One way we are thinking of addressing this question is by allowing editors to set goals, either as individuals or for a larger group. For this epic, we will focus on events for an event. With event goals, organizers can tell a more inspiring and data-driven story of what they hope their events will accomplish. Meanwhile, participants can feel more motivated to join the event, since they understand the overall vision or goal. They may also feel more motivated to contribute during the event, since they will understand how their contributions feed into a larger goal. Finally, outside observers of the event (whether funding partners or any editors who may take an interest in it) can have a more clear understanding of what was or was not accomplished.

Examples of existing events with goals:

• 100wikidays: A personal challenge in which a person aims at the creation of (at least) one article per day for 100 days in a row. The general theme and rules follow the idea of the “#100happydays” challenge. Here is a Diff blog post on the challenge and some people's motivations behind it.
• Wikipedia:The UK and Ireland 20,000 Challenge: Aiming to reach 20,000 article improvements for the UK and Ireland long term. Anybody can contribute any article on the UK and Ireland to add to this list independently whenever they feel like it.
• Wikimedia conferences, often have challenges for conference attendees, such as the 2024 editing challenge at WikiConference North America (" ...everyone who fills 7 out of 13 tasks will receive a special and unique WikiConference North America barnstar") and the 2023 Wikimania editing challenge (" ...everyone who fills 8 out of 16 tasks will receive a special and unique Wikimania barnstar.").
• WikiCup: A championship that has taken place every year on Wikipedia since 2007. The Cup is played and won by skill of editing. The purpose of the Cup is to encourage content creation and improvement and make editing on Wikipedia more fun. Contestants may earn "round points" by submitting quality content, Main Page content, or quality-content reviews. It has also inspired smaller, more localized challenges, such as the Michigan Wikipedians 2011 Challenge.

Goal metrics:

• Total articles created
• Total articles edited
• Total edits
• Total bytes added
• Total bytes removed
• Total links added
• Total links removed

Design examples:

• Organizer sets a goal (in the Enable event registration form)
  • Chooses the goal type (e.g. articles edited, bytes added - data points that we track already).
    • Sets the target (e.g. edit 25 articles)
      • Option to show/hide a public progress bar on the event page.

Progress against the goal will be displayed in (in order of priority):
a. Contributions tab
b. Event page
c. Event association dialog

Progress bar:

We're planning on using the ProgressBar component. Right now, the component supports only an indeterminate version (used mostly for loading), so I've created a task to add a static variant that represents completion/achievement/progress. See: T407638: Create a static progress bar variant in Codex.

Flow	Mockup
Organizer sets goal in Enable event registration form
Progress against goal in Contributions tab
Progress against goal in Event page
Progress against goal in association dialog