 So the campaign office hours for us all to learn, connect, share campaigns are a really important part of the little comedian movement and they offer a really especially as movement strategy grows and we'll talk about this a little bit more. We need to find tactics and ways to support the movement for folks to come in. I'm Alex Stinson. I'm a senior program strategist at the Media Foundation and I am based in Uruguay and it's so good to see people from all over the world in the conversation. Next slide please. You'll see some names in the room. We now have two teams at the foundation focused on campaigns. We have a programs team which includes Felix, Narti and myself. We are focused on the kind of social dynamics and systems, the kind of training and capacity building required for people to organize campaigns. We have a product team. You will hear from Alana and Gregory, but I also believe Lauren and possibly Irene are focused on the software side of the house and I'll let Alana explain exactly why and what we're focused on in a few minutes. But if you want to learn more we have a central page on Meta that is focused on campaigns and again it's on the slide deck and if you want to follow along in the notes or ask questions while we're talking feel free to queue them up in the etherpad. Today's topic is software and product development for campaigns and I'm going to do a brief introduction and then we're going to hand it off to the product team to explain what they're thinking about our first feature. Next slide please. So why do we need software for campaigns? Next slide please. So this is a graphic I've been working on recently that's very early drafting in the process but campaigns are complex. We interact at multiple different layers at the international level, at the local level, at the participant level and like other movements and social communities it's really important that we have tools that both connect these different levels but also make it easier to coordinate. There are so many people involved in campaigns Wikipedia pages wanting photos had over a thousand people involved this last round and it's like that kind of coordination right now is really it's running on a very complex mix of kind of on and off wiki tools, social systems and coordination and so again this really drafty map shows just how many different activities there are involved at every level on the campaign and they're really complex. Next slide and so as we think about this we're really excited to have like a technical opportunity of software opportunity right now because the tools we have now are not adequate for that scale of campaign. They're good, we've made do for a long time with kind of volunteer or community built tools that really help us but it's not the like level sophistication needed especially as movement strategy asks us to work on topics for impact at scale. We're going to see more organizers more campaigns more topics which means we need better and more consistent tools that set new organizers especially up for success because we're going to have more and more parts of the movement involved in organizing and so we're going to kind of introduce you to what where that where our current thinking at the foundation is about this and so I'm going to hand it over to Alana who is going to show you what we're up to. Hey everyone, nice to see all of you in the chat. So hi my name is Alana I'm the product manager for the new campaigns team at the wikimedia foundation. So campaigns like Alex said is a new team. We were formed in 2021 where a software and product development team and we're focused on building and improving tools for campaign organizers and participants. Our big goal is that we want to provide software solutions that empower and support campaign organizers. For experienced editors what this really means is we want to simplify workflows and provide more powerful tools and for newer organizers we want to make it easier for them to be effective long-term organizers. Next slide please. So as a team we want to be building solutions that are really useful to organizers so we thought the best way to figure out how to do that was to talk to organizers themselves. So as a first step we set up calls with about 50 campaign organizers in the movement. They worked in different kind of campaigns and wikis and regions and we really wanted to know what was working for them and what wasn't so we could identify the biggest challenges and from those conversations as well as research and information we already had we identified these top 10 sort of like problem or focused areas that were really key for a lot of organizers. So I'll briefly run through some of them and then we'll talk about some of our plans for them later. So first there's the concept of the organizer and action center. So in other words we've heard from organizers that they want a central place where they can find all the tools and resources available to them. So this is what we would call the organizer center. Then there's the participant side of this and that would be a central place where people can learn about campaign events and how to join them. That's the action center. With list building we've heard that people want easier ways to create worklists and more powerful tools to do that. We also know organizers want easier ways to create campaign event pages and register participants. They want easier ways to promote events both on and off wiki and easier ways to communicate with campaign participants. There's also problem area that we're just calling now participants support tools but really it's providing more structured help and guidance to participants during the event. Then there's what we're calling better tracking tool. So this would be improvements to existing tracking tools like the program's events dashboard and event metrics and potentially new ways of also thinking of how we can track impact. And finally there's what we're calling next steps. So this is really how people close out campaigns, how they recognize participants efforts and how after the campaign organizers can take steps to ensure that editors that whether they're new experience feel excited and want to continue as editors in their journey. So next slide please. So there's a lot of different problem areas I just explained tend to you. So rather than just picking one or two and saying okay we're going to focus on these we really want to approach it in a more systematic and integrated way. So one way we're thinking of doing that is by creating what we are calling organizer platform. So this is really where we're thinking of how we can over time work at a lot of these problem areas. So it will be focused on improving and simplifying workflows related to the pain points that I just mentioned the previous slide. We want it to be modular so that means fetch features can be separated and recombined and we want it to be extensible. So that means features can be developed over time and they can be developed by a lot of different groups or people it can be features our team develops it can be features that different communities or volunteers develop but over time the platform will grow and become bigger and more robust. But of course we need a first focus area as our first project and we've chosen registration. Next slide please. So in the previous slide I talked about how we really want to build up a platform over time. So we see that registration is a great first building block to do that. So if you look here you can see this one potential kind of plan or idea of how this could be possible. So what we see here is take for example registration you see that that can with list building lead up to that creation. From there we can have an action or activation center. So we build up over time more and more support so we can have more robust features. One thing to notice too about this kind of layout that we have here is that some problem areas have more arrows attached to them like next steps that has more arrows. So in other words the more arrows there are the more complexity there is because there's more dependencies and more things we may potentially want to build up for. So next steps for example is pretty complex and again next steps is how after the event editors can continue to feel motivated so they stay on as editors and really grow and that's because there's a lot of different things to go to next steps. With the action or activation center you may want to learn what campaigns they can join next. With list building they may want to get a list of other articles that are in their interest area for things they could improve or create new articles for. For tracking it's helpful for them to know what they've already done so they can set meaningful goals about what to do next and then for communication tools would be great if organizers or other people can communicate with them or they can communicate with others about what is good for them to do next and what kind of help they need. So as you can see there's a lot of different like parts that lead up to next steps but we're hoping that we can build up the support over time so we can really have this larger vision of a system of empowerment. Okay so next slide please. So now let's talk about our first project which is registration. Next slide. So our objective is to build an on wiki registration configuration and management system. So in other words that means a way that organizers can create a registration form and manage the registered registration process. Our goal is we want to empower organizers by making it easy to see who is coming to campaign events and how to effectively support them. This way organizers can identify opportunities for growth and re-engagement within their communities and contexts. Next slide. So what are the current registration solutions? There is on wiki and there's off wiki solutions so these top problems you've identified some apply to on wiki, some apply to off wiki and some are kind of a problem for both on and off wiki. So just to quickly go through some of these some problems that apply to a range of solutions whether on or off are they can just be time consuming and tedious for organizers to configure and manage. They're really usually not integrated with tracking tools like the dashboard so a lot of time organizers need to manually add the usernames of registered participants to the dashboard themselves. Now when we're thinking about on wiki solutions they can be sort of technically challenging or not very welcoming to newcomers. They can kind of look and feel outdated. It's not very easy to contact participants especially in a targeted way. For off wiki they're not integrated with wikis. They're not really aligned often with wikimedia values. Participants can't see who else joined. It's difficult for participants to edit their information and they tend to not really be very supportive for a multi-lingual diverse online communities. Next slide please. So the way we want to approach building the new registration solution is trying to find what are the best things for on wiki, what are the best things for off wiki and how can we sort of blend them to get the best of both worlds. So for on wiki some of the benefits are the registration solutions are integrated with wikimedia workflows and privacy standards and you can see everyone who registered. For off wiki organizers can collect rich participant information and it's very easy for participants to register. It's also easy for organizers to configure the form often. So our vision is really to blend the communalism from on wiki solutions. So in other words the fact that everyone can see who joined you're integrated into wikimedia workflows with the ease of use from off wiki solutions. And on top of that we have an added bonus which is integration with tracking tools. So we want usernames that are we want usernames for registered participants to be automatically pushed to the tracking tool choice. So in other words if you're an organizer that's using programs and events dashboard you can specify that when you're configuring your registration form and then participants who register for your events can be automatically have their username pushed to the tracking tool instead of you having to add them yourself. Okay so next slide. I hear a little background noise from someone. Okay cool. So what are the benefits of this new system? So from the organizer side organizers can get an easier configuration experience, more information on participants and their needs, better support for languages, integration with wikis and integration with tracking tools. Participants can get easier event registration experience and easier account creation experience and I mentioned this year because we're hoping to try to find a way in which if users don't have accounts yet we can have ways potentially they're integrated within the form for them to create accounts. We'll have to look into that technically to see what isn't isn't possible. We want to try to simplify that process. A view of other campaign participants and better onboarding onto wikis. Next slide please. So there's a few last things that I will talk about. So the first thing I want to address is a question that we received and this is on the talk page feedback so far which is why we aren't looking at existing open source solutions for registration. So first thing I will say is that we haven't hired our engineers yet we're currently hiring so certain I guess decisions around what back end solutions we will use for creating registration system will need to be determined by the engineers who aren't on yet so still may there may be more that comes about they can assess but from the kind of user experience side we want it to be a platform that's really integrated into the wikis rather than like an external platform off wiki because one of the pain points that we've identified that we really want to address is the fact that now there's this sort of system that isn't really supported on wiki. So that's why we're thinking of an on wiki experience. So now I'll tell a little bit more but we imagine for this kind of future of registration and how it can provide a lot more support on wiki. So overall the way we're building our work is we want it to be agile and iterative that really means that instead of like you know working on a project for a year and then releasing one version that has all the features at once we want to release more often so we can collect feedback and so we can see what's working for people what's not and then we can come out with later versions. So we tend we plan to release earlier and to collect feedback that also means though that our earlier release won't have everything at once we'll have a smaller version that will have the essentials and then over time we'll build it up to have more and more features. But some things that we envision that might not necessarily be in the first release but are still really important to us so we imagine on later releases they'll be available or what I'm going to share right now. So the ability for organizers to ask for optional information such as the editing level gender of the participants why they're joining the campaign organizers can specify which information in the registration form or information collected about participants is public versus private. Organizers can apply search filters in the participant list and send targeted messages based on those filters. Organizers can contact participants based on their method of choice for contacting them. Newcomers can be directed to onboarding tools and resources potentially before the event so they can have some training as newcomers and there'll be a little more prepared and ready when the campaign event starts on the ability to create a sort of standardized like kind of UX redesigned event pages and then other expansions of the organizer platform. So now that is all for me I'll pass it on to Gregory to give you a bit of a taste of the experience that we're imagining. So thank you. Hello everyone. My name is Gregory. I'm the designer on the campaign's team. I'm based in Lagos, Nigeria. I recently joined the team about eight weeks ago and it's been fun learning about Wikimedia and campaigns and it's been interesting working on solutions to help our campaign organizers achieve their goals. So I'll be sharing some of the early ideas we have. I'll be sharing some of the early designs we have for this registration platform. So this design only shows the flow of how campaign organizers get to add registration to their events and it doesn't show the participant side. So these are the final designs. These are just rough early designs and nothing here is fixed and can be changed and so I would love your feedback on how the design or the workflow, how well you think it's going to help you achieve your goals regarding organizing campaigns and registration. So I'll be sharing my screen in a moment. So can you hear my screen? So this is the first page that we can organize as C when the visits come to the registration sites. The idea we have for the first page is C and so it's going to be integrated with Wikimedia. So you can access it from Wikimedia and so if you are signing to Wikimedia, it's your automatically signed into this. You don't have to create a separate login for this. So if you want to be a campaign organizer who, assuming that the campaign organizer has already created an event page and so if they have done that, they can come to this page, click on create events registration. When they do that, they are, sorry, when they do that, they are taken to this page. So this is a page where they enter the general info about their events. The first thing they enter is the event page URL. So when they enter the event page the platform automatically populates the remaining feuds with the information that is on the event page. So if there's information in this form that's going to be put on the event page by the campaign organizer, this system automatically gets that information and the campaign organizer is also free to edit whatever information was automatically added in case it may not be correct or any of that. So once you enter the URL, you can proceed to enter other feuds, the name of events, the time and dates of the campaign events and it also automatically takes the time zone that is set into your Wikimedia account or your campaign organizer is also free to make the assessment changes. So the campaign organizer chooses what type of events it will be, a location, what is going to be an online event and if it is a physical event, the campaign organizer can enter the address of the event. So the campaign organizer can move on to select what tracking tool they will be using and enter the URL. Like I mentioned earlier, the user names of the participants are automatically taken from here to the registration platform to the tracking tool. So the campaign organizer does not need to manually enter that information or pass it on to manually enter that information. So you select the dashboard you are using, the tracking tool you are using and enter the URL and below you can also add user names of additional organizers for the campaign event. So once the campaign organizer is done with this, click on next and it goes to the next page. So if you can see from at the top, you can see these two steps here. So it's taken to the next page which is this page here. So for the future versions, this is the page where the campaign organizer gets to configure the form, the registration form and sets the questions that they would like participants to, or the information that they would like to get from participants. But for this MVP, for this version, the only information that's being collected from the participants will be their user names. So currently for this version, campaign organizers won't be able to modify the form, or I mean modify it or modify it, or the confirmation message. So campaign organizers can go ahead to preview, click on this button to preview how the event page will look like once the form has been created. And then from there, they can move ahead to click on publish form. So when they publish the form they click on publish form, the form is published and they are taken to this page. So when you create the form, immediately you create the form. You wouldn't see this item below because nobody has registered. So you basically see this. So you can copy the link and you can share it on whatever platform or wherever you want to share the URL to. But after people have registered, participants have registered for the events, you can see the user names, details of the registered participants. And if you want to send messages to participants, to remind them about the event or to send them resources or training materials, you can select all the participants by clicking on at the top here, or you can select individual participants, then click on message. So when you do that, when you do that, this sidebar comes up. So you can enter the message you want to send and you can select what means you would like the message to be sent. Either you have user.pages or email or both. You can decide to send whatever method you would like the participant to receive the message. Also, you can also edit the form as you can see at the top. You can also, these details here shows that the form is online and people can register. So if you click on the grab button, it's not shown in this design, but you can be able to close, you see the option to close the form. That is to stop people from registering when it is done. So I'm going to go to the next. So this is the page that, the first time you visit this page is what the user sees. So once you have added your event, you have created your form and you have multiple forms or events. This is how the page will look like. So you can now see the list of all the events you have created. And you can also see the stats. So you can see number of the app registered for your ongoing, for your events. So you can copy, click on this, copy the link to the event and share. And if you click on these three dots here, it's open a menu. So you can click on, you can edit, you can view. You can go to the tracking tool of your choice, the dashboard event metrics or any other tracking tool you might have selected. So you can duplicate the form in case you want to create a new form for an event and the form is similar. So instead of having to recreate everything from scratch, you can just duplicate and make necessary edits. So you can also close the form. In case you don't want people to continue registering and you can also delete it. You can also click here to create a new one. You can search for whatever events you might have created registration form for. And you can also filter based on the currently there's how for the three filter options are. You can filter forms that are online, that is people can actively register forms that are closed. And also forms that drafts that you haven't published yet. So once you're done with publishing the form that was in this page, once you're done clicking on publish, this is how the event page will look like your event page. So currently currently this is how the normal event page looks like. But for this, the current idea for the the only change we have now is this bottom sheet below. So that's the only change that is made to the current design of the event page. So this is added to the bottom of the event page to the bottom of the screen, not the bottom of the event page. So you can scroll on that. So this bottom sheet is always at the over the text. So it's not at the bottom. So whether participants or whether this page can click on this button to join or register for the event. And if the person wants to see more details, can click on the bottom panel or can click on this more details. And it opens up to reveal a side panel like this. So you can see more information about the events, you can see the dates and time, you can see the organizers and you can see the participants who have registered. I can also proceed to, the person can also proceed to register. So we haven't worked on the flow for how participants will get to register. But the current idea is that since currently since we are only collecting the username currently. So the idea is that if the person is already signed into Wikipedia, once the person clicks on this button, the person automatically joins the event. If the person is not signed in, the person is asked to sign in. If the person doesn't have an account, the person is asked to create a Wikipedia account. So that's all for the flow. Just wanted to mention this briefly. So like I mentioned earlier, this whole workflow exists within Wikipedia. So our current idea for how to access this on the Wikipedia pages, the current idea we have. On one of the latest skins, the idea we have is that if you click on this button drop down here, the button to access that page will be somewhere on this list or on the negative vector, I think that was this code. You can click on contributions on the button to access the organizer center campaigns, events, distribution will be somewhere on this list. So this is the current ideas ideas we have for how the workflow will be. Like I mentioned earlier, this is a wireframe and so everything here is liable to change, nothing is finalized. So a lot of the feedback on how this workflow helps you as a campaign organizer. Achieve your goals regarding registration. What do you think works well for you and what do you think could be better improved or added? Thank you very much. Thank you very much, Gregory. Thank you, Ilana. Thank you, Alex, for your presentations. I think at this point we would invite questions from participants on the call. I'd just like to say that nothing is fixed, like Gregory has mentioned and repeated over again. We would invite your feedback and we would be glad to take any comments that you have about these. So I just wanted to share a few more logistical things with you before we leave. So what's next? We are expecting you to go on our project page, read staff on our project page. We'll be giving updates very soon on what we're doing on the project. I think it's also very important to rehash that engineers are not yet here. So feel free to go on our page and add any comments or questions that you may have. I want to also re-emphasize that we are giving you the opportunity to add your comments and feedback to the mirror board about the initial designs of the project and I would invite all of you to visit the mirror board to do that. Please feel free to send us messages on our top page if you have any concerns or comments or suggestions to the team. Thank you very much once again for joining us today and I hope this was what you want.