Change Details

NOTE: This is an idea for what may be worked on during the 3-week timeboxed period that is reserved for a design exploration this quarter. However, no final decision will be made until after Wikimania. **Design exploration request: **Provide design examples (ideally, with a few versions for how it could work) and a report/summary of learnings on how we could generalize Event Registration so that it can be used for on-wiki collaborations that are not necessarily time-bound. Examples of such collaborations include WikiProjects, a call for collaboration on a wiki around a topic, etc. To do this, users may need to create their activity/collaboration in a different namespace and enter different information. There may also be a different user right than the event organizer right (or maybe not). A useful expansion could also be list-building support (see more details in the background section). **What will we do with the design exploration?:** Once complete, we will share these design concepts with organizers of on-wiki collaborations, such as 'challenge of the week,' WikiProjects, etc. We will see what feedback they have. Then, when Gregory is back from parental leave for a time (before going back on leave), we will share what we learned and then see if he continues/expands these designs or if we pivot to something else. In total, this means that this design exploration will help us determine if we want to proceed to generalize event registration to work for other use cases, namely on-wiki collaboration. **Background:** The Event Registration tool was originally built as a way for campaign event organizers to manage registration, demographics information, messaging of participants and other features associated with events. We have learned that the tool is useful for a variety of use cases, such as many different event types (editathons, hackathons, meetups, community calls). This has led us to wonder: What other use cases could be accommodated if we expanded or changed some elements of the tool? Meanwhile, we have begun thinking about how the larger work of the Campaigns team can help contributors on the wikis connect with one another, so it is easier for contributors to find a sense of belonging and work on tasks together on the wiki. This has led us to wonder: Could Event Registration help with other forms of collaborative activity on the wikis, such as WikiProjects or general collaborations when people are engaged with specific topics/workflows together? This way, we could make it easier for people to come together with other like-minded contributors, so they can work on projects together and find groups/people that can help support them and/or give them more of a sense of belonging on the wikis. As part of this exploration, I think it would also be useful to experiment with how we could include worklists as part of the experience. Basically, most on-wiki collaborations have a list of articles and/or tasks to work on. So far, we have focused more on the registration, discovery, and communication part of the organizer experience. However, I think it may be useful to see if we can ask organizers for a list of tasks to work on & we can think about how we present this information to the participants. Perhaps an expansion of the tooling to accommodate some list-building support can really help transform it from an event registration tool to more of a collaboration tool. The worklist question is a big one, and perhaps it cannot be fully explored within the scope of this ticket, but it could be nice to just think about some options/ideas in a rough and early form. Overall, we would like to explore what an experience could look and feel like if we were to generalize Event Registration for on-wiki collaboration. We want to know what ideas come up and what concerns/issues may arise as well. This can help us think through if such a project could worth considering for the team in the future, and it could help us see what questions and issues we would need to confront and think through early on. The reason why I think this is important is that, once we begin collecting data on what is being worked on during an activity, we can begin tracking and analyzing impact, which is useful for everyone involved in the activity. **Problems we are trying to solve:** For contributors on the wikis, it is often hard to join a group/collaborative activity and develop a deep sense of belonging/identity within the group without substantial work on the part of the contributor. For example: * There is often a subpar onboarding experience, in which people do not always know what to do: ** There is no standard way to join spaces as a member ** There is often no 'welcome' message or structured onboarding after someone joins an activity ** It if often hard to understand the expectations/group norms as a newcomer to an activity ** It is often hard to find how to start/what to do as a newcomer to an activity * Communication ** It is often hard to know how to connect and communicate with other members * Impact tracking ** It is often hard to understand the impact of the activity and how joining in the activity can help For organizers of collaborative activities on the wikis, it is hard to create & manage these activities. For example: * There is no standard way to create spaces for collaborative work on the wikis * There is no standard way to collect participant usernames for collaborative efforts, which makes it hard to then gain data insights on membership * There is no easy way to message and communicate with participants in bulk (such as a mass email) For the Wikimedia movement overall, we have the following problems: * We do not have an easy way of determining how many people are members of WikiProjects and if some WikiProjects are seeing growth/decrease in new membership, which could help us understand trends and see where there may be opportunities or areas we need to improve **Some things to consider:** * We want to design something that works for many forms of collaborations on the wikis. This can be WikiProjects or different forms of collaboration. We should not limit the use case to specifically WikiProjects, but this should ideally also be usable by WikIProjects. * WikiProjects are usually in the project or the WikiProject namespace. * Other forms of collaboration don't necessarily have a namespace. Would a new one be created, such as Collaboration? * On-wiki collaborations may or may not be timebound, so I think dates/times should probably be optional. * Important information to collect from organizer may be: type of collaboration, topics, tasks * Important information to collect from participants may be: what are you interested in working on?, why are you joining? -> it could be a good idea to look at the questions people are asked when they join WikiProjects * A question to consider and explore: If we generalize Event Registration, does it provide enough of a value for organizers and participants of other forms of on-wiki collaboration, or would they need a lot more to be built out? Would there need to be new features? Would we just need something that is totally different from Event Registration?

NOTE: This is an idea for what may be worked on during the 3-week timeboxed period that is reserved for a design exploration this quarter. However, no final decision will be made until after Wikimania. **Design exploration request: **Provide design examples and a report/summary of learnings on how we could generalize Event Registration so that it can be used for on-wiki collaborations that are not necessarily time-bound. Examples of such collaborations include WikiProjects, a weekly collaboration on a topic, etc. The goal is that organizers of many types of collaboration can be able to use our tools in the future. **What will we do with the design exploration?:** Once complete, we will share these design concepts with organizers of on-wiki collaborations. We will see what feedback they have. Then, when Gregory is back from parental leave (before going back on leave), we will share what we learned and then see if he continues/expands these designs or if we pivot to something else. In total, this means that this design exploration will help us determine if we want to proceed to generalize event registration to work for other use cases, namely on-wiki collaboration. **Background:** The Event Registration tool was originally built as a way for campaign event organizers to manage events, especially for in-person events and smaller to medium-sized online events. We have learned that the tool is useful for a variety of use cases, such as many different event types (edit-a-thons, hackathons, meetups, community calls), and we have seen it used for increasingly complex events (such as multilingual events, larger online events, etc). This has led us to wonder: What other use cases could be accommodated if we expanded or changed some elements of the tool? Meanwhile, we have begun thinking about how the larger work of the Campaigns team can help contributors on the wikis connect with one another, so it is easier for contributors to find a sense of belonging and work on tasks together on the wiki. This is because we believe that many contributor are happier and more productive when they have communities and groups that they can rely on and feel like they are a part of. This has led us to wonder: Could Event Registration help with other forms of collaborative activity on the wikis? This way, we could make it easier for people to come together with other like-minded contributors, so they can work on projects together. Meanwhile, our other organizer tools (Event List and Invitation Lists) either already work for collaborations beyond events (such as Invitation Lists) or we are in the process of expanding their focus (such as transforming the Event List into a Community List). Overall, we would like to explore what an experience could look and feel like if we were to generalize Event Registration for on-wiki collaboration. We want to know what ideas come up and what concerns/issues may arise as well. This can help us think through if such a project could worth considering for the team in the future, and it could help us see what questions and issues we would need to confront and think through early on. **User story:** As an organizer, I want to be able to easily create and manage collaborative activities on the wikis, so that I can create a positive experience for my participants and so that I can more easily reach the goals of my activities. **Problems we are trying to solve:** For contributors on the wikis, it is often hard to join a group/collaborative activity and develop a deep sense of belonging/identity within the group without substantial work on the part of the contributor. For example: * There is often a subpar onboarding experience, in which people do not always know what to do: ** There is no standard way to join spaces as a member ** There is often no 'welcome' message or structured onboarding after someone joins an activity ** It if often hard to understand the expectations/group norms as a newcomer to an activity ** It is often hard to find how to start/what to do as a newcomer to an activity * Communication ** It is often hard to know how to connect and communicate with other members * Impact tracking ** It is often hard to understand the impact of the activity and how joining in the activity can help For organizers of collaborative activities on the wikis, it is hard to create & manage these activities. For example: * There is no standard way to create spaces for collaborative work on the wikis * There is no standard way to collect participant usernames for collaborative efforts, which makes it hard to then gain data insights on membership * There is no easy way to message and communicate with participants in bulk (such as a mass email) For the Wikimedia movement overall, we have the following problems: * We do not have an easy way of determining how many people are members of WikiProjects and if some WikiProjects are seeing growth/decrease in new membership, which could help us understand trends and see where there may be opportunities or areas we need to improve **Some things to consider:** * We want to design something that works for many forms of collaborations on the wikis. This can be WikiProjects or different forms of collaboration. We should not limit the use case to specifically WikiProjects, but this should ideally also be usable by WikIProjects. * WikiProjects are usually in the project or the WikiProject namespace. * Other forms of collaboration don't necessarily have a namespace. Would a new one be created, such as Collaboration? * On-wiki collaborations may or may not be timebound, so I think dates/times should probably be optional. * Important information to collect from organizer may be: type of collaboration, topics, tasks * Important information to collect from participants may be: what are you interested in working on?, why are you joining? -> it could be a good idea to look at the questions people are asked when they join WikiProjects * A question to consider and explore: If we generalize Event Registration, does it provide enough of a value for organizers and participants of other forms of on-wiki collaboration, or would they need a lot more to be built out? Would there need to be new features? Would we just need something that is totally different from Event Registration?

NOTE: This is an idea for what may be worked on during the 3-week timeboxed period that is reserved for a design exploration this quarter. However, no final decision will be made until after Wikimania. **Design exploration request: **Provide design examples (ideally, with a few versions for how it could work) and a report/summary of learnings on how we could generalize Event Registration so that it can be used for on-wiki collaborations that are not necessarily time-bound. Examples of such collaborations include WikiProjects, a call fora weekly collaboration on a wiki aroundon on a topic, etc. To do this, users may need to create their activity/collaboration in a different namespace and enter different information. There may also be a different user right than the event organizer right (or maybe not). A useful expansion could also be list-building support (see more detaiThe goal is that organizers of many types of collaboration can be able to use our tools in the background section)future. **What will we do with the design exploration?:** Once complete, we will share these design concepts with organizers of on-wiki collaborations, such as 'challenge of the week,' WikiProjects, etc. We will see what feedback they have. Then, when Gregory is back from parental leave for a time (before going back on leave), we will share what we learned and then see if he continues/expands these designs or if we pivot to something else. In total, this means that this design exploration will help us determine if we want to proceed to generalize event registration to work for other use cases, namely on-wiki collaboration. **Background:** The Event Registration tool was originally built as a way for campaign event organizers to manage registrationevents, especially for in-person events and smaller to medium-sized online events. We have learned that the tool is useful for a variety of use cases, demographics informationsuch as many different event types (edit-a-thons, messaging of participants and other features associated with events.hackathons, We have learned that the tool is useful for a variety of use casesmeetups, such as many different event types (editathonscommunity calls), hackathonsand we have seen it used for increasingly complex events (such as multilingual events, meetupslarger online events, community callsetc). This has led us to wonder: What other use cases could be accommodated if we expanded or changed some elements of the tool? Meanwhile, we have begun thinking about how the larger work of the Campaigns team can help contributors on the wikis connect with one another, so it is easier for contributors to find a sense of belonging and work on tasks together on the wiki. This has led us to wonder: Could Event Registration help with other forms of collaborative activity on the wikis, such as WikiProjects or general collaborations when people are engaged with specific topics/workflows together? This way, we could make it easier for people to come together with other like-minded contributors, so they can work on projects together and find groups/people that can help support them and/or give them more of a sense of belonging on the wikisis because we believe that many contributor are happier and more productive when they have communities and groups that they can rely on and feel like they are a part of. As part of this exploration, I think it would also be useful to experiment with how we could include worklists as part of the experience. Basically, most on-wiki collaborations have a list of articles and/or tasks to work on. So far, we have focused more on the registration, discovery, and communication part of the organizer experience. However,This has led us to wonder: Could Event Registration help with other forms of collaborative activity on the wikis? I think it may be useful to see if we can ask organizers for a list of tasks to work on & we can think about how we present this information to the participants.This way, Perhaps an expansion of the tooling to accommodate some list-building support can really help transform it from an event registration tool to more of a collaboration tool.we could make it easier for people to come together with other like-minded contributors, The worklist question is a big one,so they can work on projects together. and perhaps it cannot be fully explored within the scope of this ticketMeanwhile, but it could be nice to just think about some options/ideas in a rough and early formour other organizer tools (Event List and Invitation Lists) either already work for collaborations beyond events (such as Invitation Lists) or we are in the process of expanding their focus (such as transforming the Event List into a Community List). Overall, we would like to explore what an experience could look and feel like if we were to generalize Event Registration for on-wiki collaboration. We want to know what ideas come up and what concerns/issues may arise as well. This can help us think through if such a project could worth considering for the team in the future, and it could help us see what questions and issues we would need to confront and think through early on. The reason why I think this is important is that, once we begin collecting data on what is being worked on during an activity **User story:** As an organizer, we can begin trackingI want to be able to easily create and analyzing impactmanage collaborative activities on the wikis, which is usefulso that I can create a positive experience for everyone involved inmy participants and so that I can more easily reach the goals of my activityies. **Problems we are trying to solve:** For contributors on the wikis, it is often hard to join a group/collaborative activity and develop a deep sense of belonging/identity within the group without substantial work on the part of the contributor. For example: * There is often a subpar onboarding experience, in which people do not always know what to do: ** There is no standard way to join spaces as a member ** There is often no 'welcome' message or structured onboarding after someone joins an activity ** It if often hard to understand the expectations/group norms as a newcomer to an activity ** It is often hard to find how to start/what to do as a newcomer to an activity * Communication ** It is often hard to know how to connect and communicate with other members * Impact tracking ** It is often hard to understand the impact of the activity and how joining in the activity can help For organizers of collaborative activities on the wikis, it is hard to create & manage these activities. For example: * There is no standard way to create spaces for collaborative work on the wikis * There is no standard way to collect participant usernames for collaborative efforts, which makes it hard to then gain data insights on membership * There is no easy way to message and communicate with participants in bulk (such as a mass email) For the Wikimedia movement overall, we have the following problems: * We do not have an easy way of determining how many people are members of WikiProjects and if some WikiProjects are seeing growth/decrease in new membership, which could help us understand trends and see where there may be opportunities or areas we need to improve **Some things to consider:** * We want to design something that works for many forms of collaborations on the wikis. This can be WikiProjects or different forms of collaboration. We should not limit the use case to specifically WikiProjects, but this should ideally also be usable by WikIProjects. * WikiProjects are usually in the project or the WikiProject namespace. * Other forms of collaboration don't necessarily have a namespace. Would a new one be created, such as Collaboration? * On-wiki collaborations may or may not be timebound, so I think dates/times should probably be optional. * Important information to collect from organizer may be: type of collaboration, topics, tasks * Important information to collect from participants may be: what are you interested in working on?, why are you joining? -> it could be a good idea to look at the questions people are asked when they join WikiProjects * A question to consider and explore: If we generalize Event Registration, does it provide enough of a value for organizers and participants of other forms of on-wiki collaboration, or would they need a lot more to be built out? Would there need to be new features? Would we just need something that is totally different from Event Registration?