这国刚跟中国签署战机订单 转头就倒向印度一方

Collaborative contributions? project launch

Summary

百度 所以，在主流旗舰机型已经能够完全满足玩家游戏需求时，游戏手机和普通旗舰机型的界限到底在哪里？如果只是内置的那4个小散热风扇，或者机身上那闪闪发亮的灯带，显然难以让用户买单。

Many people edit alone on the wikis, but many people also collaborate. Whether through edit-a-thons, campaigns, contests, backlog drives, or WikiProjects, people come together to work on topics and tasks that they care about.

However, it is often hard to see the impact of these collaborative activities. For this reason, the Connection team plans to create a new way to display collaborative contribution data on the wikis. This way, collaboration can be more engaging and rewarding, which we hypothesize can increase on-wiki collaboration and editor retention.

Project plans

We want to allow editors to associate an edit with an event or group that they’re registered for, and we plan to do this by expanding the functionality of the Event Registration tool from the CampaignEvents extension. Through Event Registration, we already have built the infrastructure to organize an event, register participants, and to specify event parameters (such as the dates, times, and target wikis). We now plan to expand Event Registration to manage not only participant data, but also collaborative contribution data.

For this project, we have four pillars for how we plan to do this work, which are:

• On-wiki: People should be able to see the output of a collaborative activity on the wikis, and this data should be publicly and easily available to all editors. This way, the data can be integrated with editor workflows, align with on-wiki goals, and follow wiki values of both user privacy and contribution transparency.
• Global: We want this impact data, whenever possible, to be globally accessible. For example, people should be able to see the impact of an event that aims to improve data on Spanish and Portuguese Wikipedia (rather than only understanding the impact for one wiki).
• Precise: We want the data to be precise, rather than a “best guess” based on broad criteria. We plan to do this by allowing editors to specifically indicate which edits are a part of a collaborative activity.
• Editable: We want the data itself to be editable. In other words, if someone makes a mistake when associating an edit with an event, the original editor or the organizer of the event can easily fix it.

Design examples

In this section, we will share some designs for how this experience may work:

Option 1? Associating edit with event after publishing

Option 1 (see above)? One way to associate your edit with an event could be after publishing your edit. A dialog would appear asking if the edit you made is correlated with the event. Note that this dialog would only appear if you are registered to the event, the event is currently running on the wiki that you are on, and the organizer has chosen to enable the collaborative contributions feature.

Option 2 - Associate edit with event in edit dialog, before publishing the edit

Option 2 (see above)? Another way to associate your edit with an event can be before publishing, in the "Save your changes" dialog, where you also write the edit summary. Here you would see a checkbox. Both in this option and in the pre-publish option, if you are registered to more than one active event, you will be able to select among them.

Like in Option 1 shared above, this behavior would only appear if you are registered to the event, the event is currently running on the wiki that you are on, and the organizer has chosen to enable the collaborative contributions feature.

Basic version of Contributions tab to show what people worked on

Contributions tab (see above)? Contributions made during an event would be displayed in a new "Contributions" tab in Special:EventDetails. Here a table is displayed with different data, such as the article that was edited, the user who made the edit, in which wiki, etc. You could also have a direct way to thank another participant for their contribution.

Note that there will be special handling for private registrants. Their contribution data will only be visible to themselves, the organizers of the event, and those with permitted viewing rights (which is typically admins, but it may vary by wiki).

Ability to opt out of associating edits with events

Opt out of edit association (see above)? If you are a participant in a collaboration and do not want to be continually required to indicate whether an edit is or is not associated with an event, you can easily choose to opt out, and then opt back in (if you wish), to associating an edit with an activity.

This can be helpful for activities with long timespans, such as a monthly WikiProject collaboration or backlog drive.

Remove an edit association

Remove or add edit association (see above)? If you have associated an edit with an event but you want to change this association (either because you associated it by mistake, or for other reasons), you can do so. You can delete your association. In case you forgot to associate it after publishing your edit, you will be able to add your edit to the event.

Change association from one event to another event

Change edit associations (see above)? We may also create an easy way to change an association from one event to another event, without needing to delete and then re-associate an edit with an event.

Where can this lead? Future improvements

At first, we want to build a simple version of the feature, otherwise known as the MVP (or “Minimum Viable Product.” This way, we can collect early feedback. However, we are interested in expanding the functionality over time to potentially do the following:

• More data: Display more data points about the contributions (such as number of edits, article quality score) and the people who made them (such as number of newcomers, editor retention after 30 days).
• Goals & progress bar: Allow organizers to set an event goal, and then track progress against the goal through a public progress bar. This way, when someone edits, they can see how their individual contribution is helping the larger group effort.
• Event tag in edit change pages: On pages such Special:Watchlist and Special:RecentChanges, display tags for edits that are a part of an event (with a link to the event page). This way, moderators can understand the context behind edits and contact organizers about potential issues.
• Personal challenge: Allow editors to set personal goals, and they could use the tool to track their progress, without needing to create a formal event. Other editors could optionally join or duplicate the challenge, if they want.
• Program support? Allow individual events to be tied to a larger project, program, or initiative, so impact can be viewed at an individual event level or larger programmatic level.
• More recognition pathways: More ways to recognize good work, such as wikilove support within the Contributions tab, a group reward if an event goal is reached, or rewards for organizers after an event ends.
• Notifications: Allow people to opt in to be notified about events that may interest them, with information about the output and goals (ex: “Come join a contest focused on Biology on French Wikipedia – 10 articles have been created so far!” or “Help an edit-a-thon reach its goal of 10 new articles created; 3 more articles to go!”).
• Export support: Allow the data to be exportable, so it can be shared off the wikis.

Strategic framing

Collaboration is a crucial component of editing on the wikis, which has been demonstrated by past research (see Movement Organizers, WikiProjects survey report, WikiProject responses, Topical Neighborhoods, Research: Closing Wikipedia’s Gender Gap(s)?, and Interpolating Quality Dynamics in Wikipedia and Demonstrating the Keilana Effect). When editors collaborate, they can mentor and support one another, figure out complex problems, improve content gap coverage, build community, and accomplish bigger things together. We hypothesize that this can lead to increased editor retention rates. For these reasons, we want to increase the number of opportunities to collaborate and connect on the wikis, as part of WE 1.2 in the 2025/26 annual plan.

If we look at collaboration on the wikis today, we see tremendous successes—but we also see challenges. Some projects and communities are relatively inactive or dormant. Some contests and events are underattended or have lower contribution output than hoped. Editors may rarely organize or participate in collaborative activities.

One of the biggest problem areas is understanding impact, whether you’re an organizer or a participant. On the wikis, it’s easy to track edits made per article and per user. However, it is challenging to track edits made collectively by a group or community around a common goal. This can make it less rewarding to participate in collaborative activities, since it’s often unclear what was accomplished. As a result, people may be less likely to engage in collaborative activities or be recognized for their collaborative work.

We want to help address this problem. We plan to do this by creating a new way to share collaboration impact on the wikis. This way:

• Collaboration can be more enjoyable and worthwhile for all editors.
• More editors may feel inspired to organize groups and events.
• Organizers can more readily report on the impact of their activities.
• Participants can feel motivated by their impact and receive recognition.
• Moderators can receive more context behind edits made in collaborative activities.
• Everyone can better understand the impact of collaborative activities, so they can celebrate successes and address potential issues.

Requesting feedback

We want to know what you think! Please share your feedback on the talk page.

The questions on the talk page include the following:

1. Overall, what do you think of the project vision and plans?
2. What do you think of the two potential methods of associating an edit with an event: 1) a dialog after publishing an edit, and 2) within edit dialog before publishing an edit? Do you think a certain approach is better–why or why not?
3. Which data do you find most essential to display (e.g., number of edits, quality score of articles, number of newcomer editors, etc) in the Contributions tab, if we want to make collaboration more enjoyable and rewarding for editors?
4. Which future feature improvements do you find most compelling and useful, if we want to make collaboration more enjoyable and rewarding for editors?
5. What else would you like to share?