連結團隊/註冊
 | 本页概要： |
维基媒体运动中有许多活动，例如维基爱纪念碑、維基差距、#1Lib1Ref、還有更多等等。然而，目前还没有健全的维基活动注册系统。因此，連結團隊的目标是创建一种简便的方式来加入维基媒体活动。
我们邀请您阅读下面的分析，然後在讨论页中分享您的反馈。您的反馈将直接影响我们项目的方向。在此表示感谢！
项目愿景
有了这项新功能，活动组织者将不再需要开发其他注册的解决方案，从而节省时间。此外，他们还能更好地收集有关活动参与者及其需求的数据，同时尊重参与者的隐私。同时，活动参与者只需付出极少的努力就能加入活动，他们在活动中的聯絡窗口将會是有趣以及鼓舞人心的。
对于注册的未来，我们有很大的计划。首先，我们希望将注册功能与现有的跟踪工具整合起来，如计划与活动仪表板和活动指标。这意味着，参与者注册后，他们的用户名将自动推送到组织者指定的跟踪工具中。
其次，我们希望维基上的注册解决方案能够增强社群意识。现在，许多活动参与者不知道还有谁注册了，尤其是当他们通过第三方平台注册时。有了新的注册解决方案，参与者可以看到谁加入了活动，谁与他们有共同的兴趣或动机。
第三，我们设想注册系统将来会成为一个更大的活动平台的一部分。这个平台可以为组织者和参与者提供其他功能，比如活动创建工具和全球维基媒体活动日历。一旦我们建立了注册系统，我们就可以把这个工具作为平台以后的项目和功能的基石。
最后，我们希望这个项目是一项深入合作的努力。在此项目准备过程中，我们咨询了约50名活動组织者。我们要衷心感谢这些组织者，他们让我们对组织者的经历及其面临的最大挑战有了更丰富的了解。现在，我们邀请所有活动组织者在项目讨论页上分享他们的反馈意见！
我们为什么要改进注册工作
我们相信，基于以下原因，注册对于团队来说是一个强有力的项目选择。
- 目前还没有一个标准化的维基系统。维基媒体运动需要一个为其需要而设计的强大注册系统。
- 组织者目前使用的其他登记方式存在许多问题，包括：
- 组织者在配置和管理方面费时费力。
- 数据少。它们提供的有关参与者需求的信息极少，组织者很难了解谁参加了哪些活动。
- 技术难度大，新手注册时容易混淆。
- 与会者很难在注册后编辑信息。
- 无法防止出现同一人多次注册的情况。
- 不是多语种，也不是为不同语言社区而建。
- 没有在参与者中培养社区和包容意识。
- 与维基媒体的价值观冲突（即许多工具要求在第三方平台上披露私人信息）。
- 未与任何维基页面或平台集成，为新用户增加了额外的复杂性。
- 未与现有跟踪系统集成，如“计划与活动仪表板”。
- 组织者、附属机构和其他运动利益相关者希望获得有关参与者及其需求的更好数据。开发注册系统是实现这一目标的第一步。
- 注册是未来工作的基石。一旦我们改进了注册工作，就可以开始将其他功能整合到活动工作流程中，例如改进跟踪工具或通信工具。
- 项目易于管理，在团队的能力范围之内。
我们接触过的几乎每个组织者都设计了自己的注册方案。其中一些解决方案是从其他组织者那里学来的，还有一些则来自以往的组织经验。还有一些则是根据特定的技术要求设计的。我们的目标不是设计第一个注册系统，而是提供一个改进的解决方案，帮助不同情况下的组织者创建一致的工作流程。
活動注册目前的运作方式
我们确定了目前正在使用的几种注册的解决方案，包括：
维基上的解决方案
手动添加用户名
某些註冊流程要求參與者在維基上手動添加其使用者名稱或簽名。例如，請參閱下方的螢幕截圖範例中的2021年摩洛哥人權維基會議或紅色女性活動。此方法的優點在於它能整合至現有的維基工作流程中，且註冊者的資訊對公眾開放（範例）。缺點則是它無法讓主辦單位充分了解參與者的需求，且對新手而言操作不夠直觀。
技术混合型
有些主辦單位針對註冊流程建置了複雜的技術解決方案。例如，CEE Spring便擁有一個跨維基機器人，能彙整多個地方活動的資料。Al Maarifa Project則要求每位使用者建立一個子頁面，再由腳本進行查詢。這些解決方案雖對特定活動頗具實用性，但難以跨社群進行調整或重複使用。此外，它們還仰賴「掌握內幕」的技術志工進行維護，而這些志工最終可能停止維護工具，這將為長期技術支援帶來挑戰。
維基以外的專有解決方案
第三方註冊表單
部份主辦單位會使用第三方表單（例如Google表單）來進行參與者登記。其優點在於，主辦單位容易設定表單、參與者也容易填寫。缺點在於這些表單脫離了維基媒體的工作流程，且其隱私與開源政策各不相同。參與者也無法查看其他註冊者的資訊，因此難以了解如何與其他註冊者建立聯繫。此外，這些平台對語言和文化背景的支持程度不盡相同。在較小的語言社群或面臨風險的環境中，這些工具往往難以在兼顧包容性與安全性的前提下使用。
例如，由奈及利亞維基媒體、African Women on Board以及AfroCROWD共同主辦的「非洲散居社群女性領袖慶祝活動」——這是一場為慶祝非洲散居社群女性領袖而舉辦的「黑人歷史月」活動——便使用了Google表單進行註冊。請參閱下方的螢幕截圖範例。
第三方註冊平台
有些活動會使用第三方平台（例如Eventbrite或Meetup）進行註冊。其優點在於這些平台功能豐富，且能提供高度客製化的體驗。其缺點則與第三方註冊表單相同。
例如，在下方的螢幕截圖中，由維基媒體哥倫比亞特區和維基媒體墨西哥主辦的疫苗安全編輯馬拉松，提供了在Eventbrite註冊的連結。
專為活動追蹤打造的工具
課程與活動儀表板
課程與活動儀表板，是一項由維基教育基金會所開發的追蹤工具。部份主辦單位會使用第三方工具，並在儀表板上進行後續註冊。例如（如下圖所示），您可以在非洲維基挑戰賽中看到這些步驟。在其他情況下，主辦單位則會將儀表板作為唯一的註冊工具。
儀表板的優勢在於它是一款數據分析工具，因此已內建追蹤功能。其主要缺點在於它並非真正的註冊系統。它向主辦單位提供的參與者資訊極為有限，對參與者的支援也相當有限。此外，並非所有活動都會將儀表板用作數據分析工具，因為許多活動傾向採用不同的追蹤系統。
Fountain
Fountain (文檔)，是一款由Le Loy開發、已被某些活動（例如 維基百科亞洲月）所採用的追蹤工具。其優缺點與使用「課程與活動儀表板」時相同。此外，此工具與維基站內註冊機制類似，對新手而言較為困難，最適合由經驗豐富的編輯者使用。
無正式註冊
某些活動並未設有正式的註冊流程，而是透過維基站內工作流程中某項持續不斷的行動來追蹤參與者。
透過上傳進行註冊
這種情況在攝影比賽中尤為常見，例如「維基愛古蹟」或「維基愛民俗」，在這些比賽中，註冊程序基本上已整合到追蹤流程中。當有人上傳照片並為活動追蹤添加標籤時，即視為已完成註冊。這種模式雖適用於某些活動，但並非對所有活動類型都有效，特別是針對新進使用者或撰寫條目類型的活動。此外，此模式亦無法蒐集參與者的額外資訊，這可能使溝通與後續追蹤工作面臨特別大的挑戰。
透過主題標籤進行註冊
對於 #1lib1ref、維基百科頁面需要照片 (#WPWP) 以及其他少數計畫活動而言，主題標籤工具 充當預設的登錄工具。如同上傳流程一樣，其優點在於能記錄貢獻資料。然而，由於主題標籤並未深度整合至編輯介面中，新使用者難以理解此操作；即使是經驗豐富的編輯者，也可能因主題標籤並非其常規工作流程的一部份而忘記添加。此外，主辦單位難以即時追蹤貢獻狀況，且無法直接獲取參與者及其需求的相關資訊。
待解問題
感謝您閱讀我們的分析。現在我們想聽聽您的意見！懇請您在專案討論頁上回答以下問題（或分享任何其他意見！）：
- 您對我們建立活動註冊系統的計畫有何看法？身為活動主辦者及/或參與者，您認為這對您會有幫助嗎？
- 您對我們對現行註冊流程的分析有何看法？是否有任何對您而言重要的環節被我們遺漏了？
- 如果您是活動策劃者，您使用哪種註冊系統？該系統有哪些優點和缺點？如果可以對該系統進行一項改進，您會選擇哪一項？
- 如果我們要建立一個註冊系統，您希望它如何運作？請盡可能詳細地說明您的需求，或者如果您有相關經驗，也請提供您之前使用過的其他註冊工具的範例！
- 我們是一支新團隊（請查看新首頁）。您對我們團隊有什麼期望、疑問或顧慮嗎？
- 還有其他要補充的嗎？
您的回饋對我們非常重要，這將直接影響我們團隊的決策。感謝您我們期待閱讀您的意見！
狀態更新
2025年10月10日：活動註冊存取權限調整更新
「活動註冊」功能現已開放給更多使用者使用。現在，在已啟用CampaignEvents擴充功能的中小型維基站上（請參閱小型維基站清單及中型維基站清單），所有的自動確認使用者皆可使用「活動註冊」功能來作為主辦者。這意味著他們將能夠在活動頁面啟用註冊功能，並使用「活動註冊」工具中的其他功能。若維基不希望採用此變更，可透過建立Phabricator工單並添加CampaignEvents標籤來選擇退出。
在安裝了CampaignEvents擴充功能的大型維基站上（參見大型維基站清單），活動註冊的存取權限將維持不變，這意味著使用者仍需具備「活動主辦人」權限，才能以主辦人身分使用活動註冊功能。若某維基不希望維持現行限制，並希望允許所有自動確認用戶使用活動註冊功能，可透過建立Phabricator工單並添加CampaignEvents標籤來提出此請求。
此變更是在我們發佈公告後進行的(T401445)。您可以閱讀該公告，進一步了解我們進行此變更的原因。我們期待有更多編輯者能夠為其社群和活動試用並運用「活動註冊」功能。
2025年6月26日：事件類型的支援
我們新增了一項關於活動的資料點：活動類型。現在，主辦者可選擇最多2種能描述其活動的活動類型（例如編輯活動、工作坊等）。唯一例外是「其他」類型的活動（此情況下僅能選擇一項）。此資料將顯示於活動註冊流程中的「更多詳情」彈出視窗及「活動詳情」頁面。此外，使用者現在也能在協作清單中透過活動類型搜尋活動。
2025年6月3日：事件註冊的替代命名空間
社群現在可以透過「社群組態」來決定哪些命名空間可進行活動註冊。
我們也更新了預設允許用於活動註冊的命名空間。過去，預設僅允許使用「活動」命名空間。現在，預設同時允許使用「活動」及「專案」（例如：維基百科、維基數據）命名空間。
2025年4月4日：發佈私人註冊更新
關於私人註冊的變更已發佈。您可閱讀3月1 日的更新以獲取更多詳細資訊。
2025年3月18日：關於私人註冊處理方式變更的公告
自3月31日當週起，各維基將可設定哪些使用者群組能在「註冊報名」中查看私人的註冊者，此為CampaignEvents擴充功能的功能之一。預設情況下，活動主辦者與當地維基管理員將能查看私人註冊者。這與現行行為有所不同，現行行為僅允許活動主辦者查看私人註冊者。不過，維基站若希望變更預設設定，可透過在Phabricator中提交配置變更請求（並添加campaigns-product-team標籤）來進行調整。若過去活動的參與者不再希望出現在參與者名單中，可隨時取消註冊（包括活動結束後）。
此變更係應社群要求而實施（參見 T376089）。如此一來，管理員將能更妥善地處理社群問題與爭議，因為他們將清楚知曉哪些人參與了社群活動。與此同時，參與者的隱私仍將受到保障，因為只有活動主辦者以及在維基上擁有特殊權限的可信賴用戶，才能查看其註冊紀錄。
March 7, 2025: Organizers can get copies of emails
We have updated the messaging section for Event Registration. Now, organizers can choose to receive a copy of the email that they have sent to participants, so that it is easier for them to track and manage their email communication.
January 31, 2025: Test and Live event selection
Organizers can now indicate if an event is a test event (such an event that they created in their sandbox) or a live event (i.e., an actual event that will be held). All test events will be excluded from the Collaboration List.
January 28, 2025: Event topic support
We have also added a new data point about events: event topics. Now, organizers can optionally select up to 5 topics that are relevant to their event. These topics are from a predetermined list, and they are the same topics used in other features on the wikis, such as on the Newcomer Homepage. This data will appear in the 'More details' modal and EventDetails page of the Event Registration experience. Additionally, people will now able to search for events related to specific topics in the Collaboration List.
January 14, 2025: Release to more wikis & event wiki support
Since our last update, we have released the CampaignEvents extension to more wikis. From now on, all updates related to the release of the extension to more wikis can be found on the CampaignEvents/Deployment Status page.
We have also added a new data point about events: event wiki. Now, organizers can state if their event applies to no wikis, all wikis, or specific wikis. If the event applies to certain wikis, they can specify these wikis when configuring registration. This data will appear in the 'More details' modal and EventDetails page of the Event Registration experience. Additionally, people will now able to search for events related to specific wikis in the Collaboration List.
June 14, 2024ː Release to Swahili Wikipedia
The CampaignEvents extension has been enabled on Swahili Wikipedia.
June 7, 2024ː Release to Igbo Wikipedia
The CampaignEvents extension has been enabled on Igbo Wikipedia, and we will be releasing to more wikis soon. Our next release will be for Swahili Wikipedia.
May 23, 2024: New feature improvements
In the last few months, we have released some feature improvements to Event Registration, which include:
Event List
There is now a global list of all events that use Event Registration, which can be found at Special:AllEvents. We plan to improve the Event List over time by adding more search filters, such as the wiki(s) of the event and the event topic. To learn more about the Event List and future work we may do for the feature, you can check out T355666 and T362881.
Grant ID support
Organizers will now see a Grant ID field when they configure or edit Event Registration. The Grant ID is found in the Grantee Portal (Fluxx), and it is assigned to programs or events that receive grants from the Wikimedia Foundation. Now, with this update, organizers can associate their Grant ID with Event Registration data, so that it is easier to analyze the impact of their events.
Optional participant questions for organizers
Organizers can now choose which participant questions to enable when they configure registration. They can choose to enable some, all, or none of the questions.
Support for translated pages
For events that use the Translate extension, they can now see the same Event Registration header for the event, regardless of which translated version of the page is being viewed. Meanwhile, organizers can still create separate subpages with different event registration headers.
February 5, 2024: Update to management of the organizer right
组织者权利已更名为“活动组织者”，我们也更新了其管理方式。从现在起，元維基上所有志愿者的权利申请将由元維基管理员管理。同时，工作人员的申请将由維基媒體基金會的信任与安全团队管理。这项工作是作为改变活动组织者权利的管理的一部分完成的，与管理员讨论。您可以阅读关于当前流程及其管理的文档。
November 15, 2023: Participant Questions released
The Participant Questions feature has been released to Event Registration. With this feature, organizers can now include questions for participants in the registration process if they agree to a clickwrap agreement. The questions are optional for participants to answer, and the response data is displayed to the organizer. Some of the information is Personally Identifiable Information (PII), so it is displayed in the aggregate only. The PII information is the gender identity, age, and profession of the participant. Other information is not PII, so individual responses can be viewed. The non-PII information is the affiliate membership of the participant (if any) and their level of confidence in contributing to Wikimedia projects.
October 7 & 10, 2023: office hours & upcoming features
We would like to invite everyone to our upcoming community office hours on October 7 and October 10, where we will demo the latest version of the Event Registration tool. We will discuss the new, already released features (multiple organizer support and P&E Dashboard integration) and upcoming features (organizer can email participants and optional participant questions).
2023年7月21日：註冊工具現已整合至「課程與活動儀表板」
活動註冊工具現已支援與「課程與活動儀表板」整合。這意味著主辦單位在設定註冊流程時，可指定連結至其「課程與活動儀表板」中的活動。如此一來，已公開註冊參與者的使用者名稱便會自動傳送至「課程與活動儀表板」中指定的活動。
April 27, 2023: Registration tool now allows multiple organizers
The event registration tool now includes support for more than one organizer.
December 5, 2022: Office hours and feedback requested
Now that we have enabled the CampaignEvents extension on Meta-Wiki, we would like to invite everyone to our upcoming office hours and to share their feedback on the tool, either on our project talk or in a survey (which is available in Arabic, English, French, and Swahili).
During the office hours, we will demo the tool, answer any questions people may have, and share how people can test the tool on either test wikis (such as the beta cluster, testwiki, or test2wiki) or with real events on Meta-Wiki. The office hours dates and times are:
Session 1:
- Date: December 5, 2022 @18:00 UTC
- Zoom Link: https://wikimedia.zoom.us/j/87853269514
- Language available: Arabic, English, French, Swahili
Session 2:
- Date: December 10, 2022 @12:00 UTC
- Zoom Link: https://wikimedia.zoom.us/j/87853269514
- Language available: Arabic, English, French, Swahili
We hope you can join us!
Additionally, we want to hear your feedback. You can share your feedback on the project talk page, in our V1 feedback survey, or by reaching out to team members directly. The survey and the project talk pages have the same questions, which are available in four languages (Arabic, English, French, and Swahili). Thank you!
November 30, 2022: Meta-Wiki release
We have enabled the CampaignEvents extension on Meta-Wiki, which we will demo in the upcoming office hours.
November 3, 2022: Test wikis release & other updates
We have enabled the CampaignEvents extension on testwiki and test2wiki. This now means that you can test out the tool on these two wikis, in addition to the beta cluster.
Additionally, we have updated our release schedule. Our next release plan is to enable the CampaignEvents extension on Meta-wiki, roughly scheduled for the end of November. You can check out our release plan page for the latest details.
We have written a comprehensive guide on the event registration tool, which will be updated as we release new features for the tool. Additionally, we have posted a blog post on Diff related to our work and plans in Arabic, English, and French.
If you have any feedback on our latest updates, please share them on the talk page. Thank youǃ
October 3, 2022: V0 learnings and V1 launch
Hello, everyone! We have many updates to share with you, including:
- A summary of learnings from our V0 test phase
- An update on the launch of V1 work
- Open questions that we have for volunteers and community members
Please read below to learn more, and we look forward to reading your feedback on the talk pageǃ
V0 learnings
In July 2022, we released V0 on the beta cluster. We collected feedback on V0 in a variety of formats, including: a Google Form, multilingual presentations at office hours and Wikimania, discussions on this project page, communication in off-wiki chat groups, and direct emails sent to us. People provided responses in Arabic, English, French, Portuguese, and Swahili. In total, we heard from over 30 Wikimedians.
We received a lot of positive feedback on V0. For example, when we asked people if they would use the tool, over 80% of the respondents to the question said yes. When we asked Wikimedia organizers if they think access to the tool would make them more likely to organize events in the future, 90% of the respondents said yes. Some common forms of positive feedback included: the tool was intuitive and easy to use, it would save time for organizers, and it would improve organizers’ abilities to collect information on participants. Since this is only an early test version (and we plan to release further enhancements in later versions), it was very exciting for the team to hear that even this version pleased many Wikimedians.
We also received information on how we can improve the event registration tool. Some people said that they already had registration solutions that they preferred or that they only wanted to use the tool after they had more time to test it. We also received many feature requests. Below, we have shared a list of the requests and a note for when we plan to implement the feature, if we do have any plans:
- Integration with the Programs & Events Dashboard (planned for V1)
- The ability for multiple organizers to be associated with an event (planned for V1)
- Geocoding support (planned for V1)
- Automatic confirmation emails after participants have registered (planned for V1)
- Event reminder emails for participants (we will be creating the ability for organizers to email participants in V1; automated reminder emails are not yet in the roadmap, but we may consider them later)
- The ability to set limits on the number of participants (planned for V2)
- Support for creating event pages (planned for a future project focused on event creation)
- An improved event calendar system (planned for a future project focused on an event calendar and/or event promotion support)
These suggestions were very helpful for us, and we plan to incorporate many of them as features in the V1 and V2 release. So, with that being said, you can read a more full breakdown of V0 feedback and a final summary of the V0 work.
V1 launch
We have now officially begun working on V1 of the event registration tool. The engineers are currently working on building out the core features and improvements of V1. We have not set a specific release date yet, but when we do, we’ll be sure to update the release page. However, we can let you know that some core feature improvements in V1 include:
- Support for the organizer to specify an event timezone
- Geocoding support
- Automatic confirmation emails after participants have registered
- The ability for the organizer to email participants (if they email addresses associated with their accounts)
- Integration with the Programs & Events Dashboard
- The ability for multiple organizers to be associated with an event
- Private registration: the option for participants to register and only display their registered username to organizers of the event
To learn more details about our V1 vision, we invite you to check out the V1 summary subpage, which lays out our work in greater detail.
Open questions
- We are currently working on V1 of the event registration tool. You can check out our summary of the project. Is there anything you would like to share with us about the plan, or anything you suggest we do differently?
- In the future, who should be able to access our organizer tools? In other words, how should someone be able to become an organizer with certain privileges on the wikis? For example, should it be a user group? Should it be a right that people automatically receive after making a certain number of edits?
- In the future, we plan to build a feature for organizers to collect information on participants. In that case, what information would you (as an organizer) want to collect on participants before they join an event (such as gender, location, topics of interest, etc)? Do you have any examples of registration forms you have created that ask some of these questions? If yes, please do share them with us!
July 21, 2022: Feedback form ready
Hello, everyone! We now have a feedback form (available in Arabic, English, and French) for people to submit feedback on V0 of the registration tool! We invite you all to fill out the form and/or share feedback on the project talk page. As a reminder, we will be hosting two community office hour sessions to provide training on how to use the tool. The first session will be today at 5 pm UTC, and the second will be on July 23 at 12 pm UTC.
We thank everyone who has provided feedback or support at any point in this project, and we truly look forward to learning from you all during the V0 test phase! Our goal is to continue improving the tool with two more release phases (V1 and V2), so we will be continuing to update this project page throughout the process. In the meantime, we sincerely hope you fill out the feedback form and attend our community office hours. We look forward to hearing from many of you!
July 18, 2022: V0 released on beta cluster
We are very pleased to announce that the registration tool is now available for testing on the beta cluster! You can read Help documentation on how to use the tool on Mediawiki.org.
As a next step, we will be providing training on how to use the tool. For this reason, we cordially invite volunteers to meet the team and participate in a training in one of our upcoming community office hours, which will be taking place on Thursday, July 21 at 5 pm UTC and/or Saturday, July 23 at 12 pm UTC. You can visit the office hours page on Meta-Wiki to sign up for one or both sessions and learn more details.
We are currently finalizing our volunteer feedback form on the registration tool. We will share the feedback form in the upcoming office hours, and we will share it on this project page very soon too. In the meantime, feel free to share your feedback on the talk page, if you would like to check out the tool before the office hours.
In the meantime, thank you to everyone who has collaborated on this project so far, and we hope to see many of you in our upcoming office hours!
July 8, 2022
The team is preparing for the release of V0 to the beta cluster, which will be happening soon. We will update this project page when the release is up on the beta cluster. After the release, we will host two community office hours to provide training and support to anyone who would like to try out the tool and share their feedback. For the most up-to-date information, please visit the Release and training schedule page for the project.
May 23, 2022
Hello, everyone! First, thank you to everyone who has participated in our talk page feedback, office hours, or chat group conversations. Your feedback and insights have been absolutely crucial to our project, and we deeply appreciate it. We also have some exciting updates (and new questions!), which we’ll share below:
Engineering update
The team engineers are continuing to work on building the event registration system. They have built the majority of the back-end infrastructure, and they are now focused on building the front-end (i.e., the user interface). We predict that an early testable version of the registration solution will be available on the beta cluster in July 2022. To learn more about the engineering work, you can check out the definition of our schema on Gerrit.
Prototype updates
We have an updated prototype, which was created by our team designer, for you to check out (see links below). This prototype is for V0 (the first version of the tool that we will be releasing). Please note that these are only prototypes; they are not working software on live wikis. These prototypes give a general sense of how the finished product may look, feel, and function once we do release the registration solution, although there will probably be some changes.
- V0: Create Event Registration Prototype: This is the organizer side of the experience, where the organizer enables registration for an existing event page. Registration can be enabled on any event page, as long as it is in the event namespace. You can also watch a video walk-through of the process to create an event page in the event namespace and to enable registration for an event page on Commons.
- V0: Register for Event Registration Prototype: This is the participant side of the experience, where the participant registers for the event. Note that only the username and timestamp of when the participant registered is collected for V0. You can also watch a video walk-through of the participant registration experience on Commons.
Our release plan
Our release plan: We now have a basic release plan. We plan to release the registration solution in three parts, which we will explain below:
- V0: This is the version of the tool, which we are focused on building now. It will be released to the beta cluster, probably in July 2022. We’re calling it V0 because it is a test phase that will not be released to any live wikis (just a test wiki). The purpose of this release will be to collect user feedback in preparation for the V1 release. In this version, organizers will be able to add registration to event pages and see a list of registered participants. This will be a desktop version only. You can view the prototype example in the links provided above (see “Prototype updates”):
- V1: This version will be an improvement of V0, with the inclusion of more features, such as: the ability for organizers to contact participants, integration with the Programs & Events Dashboard, and geolocation support. We will also incorporate feedback we receive from users in the V0 testing phase. This version will be compatible with both desktop and mobile web versions of the wikis, and we plan to release it to at least 1 live wiki (probably Meta-Wiki). This version is a big upgrade with a lot to discuss, so we’ll dedicate a separate status update to collect feedback on the V1 requirements and prototypes. You can expect this status update on V1 to be posted soon.
- V2: This version will be an improvement of V1, based on user feedback and the addition of more features. We haven’t fully fleshed out the requirements, and we don’t have a prototype yet. You can expect more updates on this final version in a future update.
Requesting your feedback
We want your feedback on event page behavior: In the open questions section, we have shared some questions on how events and event pages should be handled. We would love your feedback (see below):
- For event registration, what is the recommended behavior for blocked users? Should blocked users be able to join campaign events? Why or why not? And does it matter, depending on the type of block (such as hard block, soft block, etc)?
- For event pages in the event namespace, should we allow the pages to be moved?
- If yes: What happens if an event page gets moved to another namespace and it has registered participants?
- If yes: What should be the behavior/warnings to the user if they want to move the page?
- If yes: What should happen if an event page is moved to a namespace where event pages are not allowed?
- For event pages in the event namespace, should we allow the pages to be deleted?
- If yes: Who should be able to delete event pages?
- If yes: What should happen if an event page gets deleted and it has registered participants?
- If yes: If people have registered, what should happen to the data if the page is deleted?
- Is there anything else you would like to add (about the V0 prototypes, release plan, or anything else)?
Thank you in advance for your feedback, and we look forward to reading your responses!
March 4, 2022
Hello, everyone! We have had an eventful past few months, and we are happy to now share some updates. Also, we apologize for the delay in posting an update. Our work slowed down from October to December, both due to the holiday season and new people joining our team. Then, in the new year, we needed time to solidify and finalize our technical plan. However, our work is now picking up pace and the building phase of the project has officially begun. Also, we thank everyone who has shared feedback so far! Now, we invite you to read our new updates and share your feedback on the project talk page. All feedback is helpful, and we hope to continue learning from all of you. Thank you!
Proposal to create new namespaces
The Campaigns team is proposing that we create two new namespaces in MediaWiki, which will be called “Event” and “Event Talk.” You can see the proposal in T302040 on Phabricator. The purpose of this namespace would be a designated place in the wikis for all events, such as campaigns, conferences, meetups, office hours, or other events. We want a way to easily determine what is an ‘event’ page, so that we can:
- Add registration to event pages (and avoid adding registration to inappropriate page types, such as article pages)
- Display all events in an event calendar in the future
- Begin getting more accurate data on event activity as a movement (such as how many events & which types of events are going on)
- Make it easier for everyone to know what is an event page, since right now event pages often look very similar to article pages
- Highlight the fact that organizing or participating in events is a critical form of movement activity, and that someone can be an impactful Wikimedian in more ways than just contributing to the wikis
Engineering updates
Between October and January, three engineers and an engineering manager joined our team. Since that time, we have been able to conduct technical planning and to officially launch the building phase of the project. The engineers will be focused on building the core infrastructure of the campaign events platform and the registration tool. Once they have built something that is testable, we will share it with all of you. In the meantime, you can track our work in the Registration project board and project profile on Phabricator.
Design updates
The design team has developed a new version of the desktop wireframes, based on the feedback we received in usability tests, the project talk page, and other channels. Now, the design team is conducting a second round of usability tests on the new version of the desktop wireframes. Once we have finalized the desktop wireframes, we will share them in a status update. Additionally, the design team is developing the first version of the mobile wireframes, which we plan to share in a future status update as well.
Ambassador updates
Three product ambassadors have joined our team: Antoni Mtavangu (Swahili community ambassador), Georges Fodouop (French community ambassador), and M. Bachounda (Arabic community ambassador). The product ambassadors will be working with the team to conduct outreach and collect feedback from Wikimedia communities, and they will share ideas on the vision and strategy of the project. They will also help us understand the needs of organizers beyond our first project, so we can continue to plan for future work.
Open questions
- Do you think it would be useful to you (or other Wikimedians) to create two new namespaces for Event and Event talk? Why or why not?
- What questions or concerns do you have about creating these new namespaces?
- Is there anything else you would like to share about the status update or project in general?
October 8, 2021
Hello, everyone! We are very excited to share an update on the Campaign Product team’s event registration project. First, we will share our project principles. Second, we will share wireframes for the desktop version (the mobile version will be in the next update). Third, we will provide questions for all of you. Thank you, everyone, and we look forward to reading your feedback on the project talk page!
Project principles
As the project has developed, we have identified several principles that are core to our work:
- In the long-term, we want to build a platform, rather than one tool: Some people asked why we’re not using an existing open source solution for event registration. We’ll certainly examine the options, and nothing is ruled out yet. However, we’ll probably want to build our own solution. Here’s why: We want to build a Campaign Events platform over time—not just a registration solution. In order to build this platform, we’ll need to develop the core infrastructure, and the registration project is the first step in making this happen. To learn more, you can visit the plans & vision section of our team page.
- We want to build for multilingual, diverse communities: Organizers have explained that the existing registration solutions lack sufficient support for global, multilingual communities. We completely agree. For this reason, we won’t consider this project complete until we build a solution that is usable for all language wikis and Wikimedia projects.
- We plan to build in an iterative way: The first version of the registration solution will be very basic. We call it the MVP (or “Minimum Viable Product”), since it will just have the bare essentials to function. We work in this way so that we can collect feedback early on, and we can identify problems before we spend too long on a feature. Once we have released the MVP version, we can develop more advanced versions of the registration feature.
- The MVP will just have the necessities: For the MVP, our goal is to build a simple registration configuration and management tool. The wireframes we have shared below are for the MVP version.
- We will add enhancements later on: After we have built the MVP version, we can include the ability for organizers to add optional questions to the registration form, such as asking for the participant’s gender, location, wiki editing experience level, or why they joined the event. We can also add the ability for organizers to write custom questions.
Wireframes: Desktop version
In the wireframes below, we will share how the MVP version may look for desktop users. Wireframes are a step in product development, where we imagine the potential visual design and workflows of a tool. Wireframes are theoretical; the look may change when the engineers begin to develop the tool. Note that we’ll share wireframes for the mobile version in the next status update.
Creating registration for event
Access Organizer Center: We want to create an “Organizer Center,” where organizers can find tools and resources available to them. For this project, we may create a very basic Organizer Center, which will expand over time. The first tool to be featured in the Organizer Center will be the Event Registration tool. To access the Organizer Center, users can go to Contributions > Campaign Events.
Note that, in the future, the Organizer Center will probably be a part of a larger Campaign Events platform. To learn more, you can visit our plans & vision section of our team page.
Selecting tool to create registration: Once the user is in the Organizer Center, they can choose to create a registration system for their campaign event. To do this, they click “Create registration for your campaigns events.”
Creating registration for campaign event: After the user has chosen to create a registration form, a new interface will appear. The organizer will input the following information: the event URL, event name, date, time, timezone, if it’s online or in-person, which tracking tool will be used, URL of tracking tool instance, usernames of organizers, and a link to the event's chat group. The tracking tool and chat group information will be optional. The user clicks on “Create Registration” when they are finished adding information.
Once the registration creation is complete, a registration interface will automatically appear on the campaign event page. Please refer to the next section ("Registering participants") for more details.
It is important to note that, with this system, organizers will need to create a few things in advance: the campaign event page, the tracking instance (for example, on Programs & Events Dashboard), and the chat group in advance.
For the first version of the registration system, we will only be asking participants for their usernames. This is because it is much easier to implement. However, after the first version is released, we will look into allowing organizers to create more sophisticated registration forms that can ask participants optional questions about themselves and why they are joining the campaign event.
Registering participants
Registration automatically added to the event page: Once the organizer has created event registration, the registration experience will be automatically added to the event page URL specified by the organizer. The registration experience is a bottom sheet that overlays the event page. We chose the bottom sheet design so that it could work for many different types of event pages. In the bottom sheet, there is a button to “Register as userName.” So, if someone’s username was Lola, it would say, “Register as Lola.” The user can click the button to register.
More information: If the user clicks “More Information,” they can see more information on the event, such as the date, location, organizers, and list of participants. They can then click “Register as userName” in this view too. After the user registers, they should see the confirmation message.
Login and account creation support: If the user is not logged in, they will automatically see a pop-up appear when they click “Register as userName.” They can choose to login, if they already have an account, or they can sign up, if they do not already have an account. Once they login or create an account, they will become automatically registered in the campaign event.
Successful registration: After the participant has successfully registered, a pop-up will appear to confirm their registration. The pop-up will automatically disappear after a short time. If they have an email address associated with their account, we would also like an email to be automatically sent, which provides information on the event, such as the chat group that they can join. If participants would like to leave the event, they can click “Edit registration” (via the bottom sheet or side bar), which will then ask them to confirm if they want to leave the event.
In the future, participants may be able to add optional information about themselves when they register (such as wiki editing level, why they are joining the campaign event, etc). If this support is added, participants will also be able to edit this information as well.
Managing registration
View all registration forms: Once the organizer has created the registration form, they will be able to see all registration forms for their events. They can click on one of the forms to get more registration details, including the participant list. They can also easily delete, edit, or close registration forms via this view.
Viewing, deleting, and messaging participants: Once a registration form has been created, any specified as an organizer can view registrant information, including: participant username, and the date and time of registration. They will be able to select some or all of the participants from the list, and they will be able to message them or delete them from the list.
Organizers will be able to send a message to the participants, either on their talk page or to their email address. Depending on the technical difficulty of the work, we may choose to release an MVP version that only sends a message to the talk page, or the MVP version may allow both options. Either way, our plan is to eventually allow both messaging options.
Open questions
- What do you think of our proposed system for creating and managing event registration, as a campaign organizer? What benefits does it offer compared to your current system? What disadvantages does it have compared to your current system?
- What do you think of our proposed experience for registering participants on the event page? What benefits does it offer compared to your current system? What disadvantages does it have compared to your current system?
- We first plan to build a lean version (also known as the “MVP,” or minimum viable product version) of the registration tool.
- What are the essential features this first version needs to have so that you can use it?"
- When you are running a campaign, what information do you typically send to participants, and where do you usually send it (e.g., talk page, email, social media, etc)?
- Do you prefer that we build the desktop version first or the mobile version of the registration system first?
- Is there anything else you would like to add?
Please share your feedback on the talk page; thank you in advance!