Page MenuHomePhabricator

Design: Participants can indicate contributions in the scope of a collaboration
Closed, ResolvedPublic

Assigned To
None
Authored By
ifried
Aug 23 2024, 10:53 PM
Referenced Files
F57687946: image.png
Nov 7 2024, 7:20 PM
F57687944: image.png
Nov 7 2024, 7:20 PM
F57688005: image.png
Nov 7 2024, 7:20 PM
Restricted File
Nov 7 2024, 7:20 PM
Restricted File
Nov 7 2024, 7:20 PM
Restricted File
Nov 7 2024, 7:20 PM
Restricted File
Nov 7 2024, 7:20 PM
Restricted File
Nov 7 2024, 7:20 PM

Description

User problem:

Organizers do not have a way of easily tracking contributions and then reporting on impact of their organized activity on the wikis. This means that it is harder to share the successes and challenges and learnings of their organized activities, and it is harder to motivate people to join their activities due to unclear understanding of the impact.

Background:

One of the most important tasks related to organizing events on the wikis is tracking and reporting on impact. For events that focus on contributions, this means tracking contribution data, such as: the number of articles created, the number of articles edited, the total number of edits, the number of photos uploaded, etc.

Contribution data is important to many people. It is important to the event organizers and event stakeholders (such as grant officers, partner institutions, host venues), since it gives them an understanding of the impact of their events, their successes, and their gaps/challenges to address in the future. For the prospective participants, they can see impact reporting of past events, which can help motivate them to join future events. For event participants, it can help them feel like their work and time was valued, since they understand the impact of their individual contributions and the impact of the event overall.

However, there is no easy way to track contributions that are in the scope of an activity on the wikis. There are many external tools to track contributions, and different wikis & campaigns use different tools. However, many of these solutions pose challenges, including: they are off the wikis, they do not work well for tracking the contributions of experienced editors, and/or they can be hard to use.

This has made us wonder: Is there a simple, first stab that we can take at tracking contributions in organized activities? This first stab would focus on making it easy for organizers to know which contributions are within the scope of an organized activity.

User stories:

As an organizer of a collaboration, I want registered participants to be able to indicate if a specific contribution is within the scope of the collaboration, so that I can easily see access accurate contribution data and this data can be integrated with wiki workflows and practices.

As a participant in a collaboration, I want to easily indicate if my specific contribution is part of a collaboration, so that I can be recognized for my work and so that work that is not a part of the collaboration remains separate.

As a moderator, I want to know if a certain contribution is a part of a collaborative activity, and I would like to be able to easily access information on the activity (such as the organizer, event type, event goals), so that I can understand more context behind the contributions and who I can contact if issues arise, other than the only the contributor.

Open questions/ideas for further exploration identified via design investigation (see T375683):

  • What if there are edits that should be included in the scope of the event but for whatever reason were not tagged? Can we allow organizers to retroactively tag/connect edits to the event?
  • Allow participants to claim certain articles and/or goals within those articles
  • Allow organizers to assign certain articles and/or goals within those articles to specific participants
  • Allow organizers to reuse worklists from past events
  • Should the tracking/analytics experience be different from the worklist creation experience? Is it okay for all of this to happen in one place?
  • How much should we encourage organizers to create a worklist? Should it be required? It seems like having a worklist with clearly defined goals would increase the impact of any event.
  • We may want to allow a scoring component as another element that is tracked in the future, so judges of contests can score contributions or the overall work of contributors - see example: https://fountain.toolforge.org/editathons/wmid-sm4p-tantangan

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Design explorations

1. Allowing editors to associate an edit with a specific event
We explored various options for how participants might tag edits with an event, so that things are properly tracked. A general idea is that if someone is registered for an event, that event is currently happening, and they are editing a page that is on the worklist for the event, we would automatically add the event tag to their edit summary. They could remove it if needed.

{F57687692}{F57687694}{F57687697}{F57687699}{F57687701}{F57687703}{F57687705}

Something that came up here is that the editing team is potentially exploring making the edit summary more of a rich-text / VisualEditor-like experience, and allowing for @mentions and other things like that. This type of functionality could work well for wanting to add event tags to edit summaries.

2. Indicating edits that are associated with an event
Knowing that an edit is associated with an event might be helpful context for other editors, and might also help to spread awareness about events. Ideally there would be some simple way to display this information on Recent changes, User contributions, etc.

image.png (1×3 px, 722 KB)

Another idea that came up while we were exploring this is a more explicit "event mode". This is a sort of extension of the idea of adding the context of the event into the edit summary. Why not extend the context of the event further, and sort of wrap the entire user experience with that context? Maybe it would help events feel more alive/live, help participants be more excited while they're participating in events, and make it easier for people to quickly access.

image.png (1×3 px, 1 MB)
image.png (1×3 px, 1 MB)
ifried claimed this task.
ifried moved this task from Tracking (in-progress) to Done on the Wikimedia-Design board.

This work is done and it formed the basis of the next stage of work (T391908), so I am marking it as done. Thank you!