 All right. Hello, everybody. Hello, everybody. Welcome to our monthly activities meeting. My name is Sasha Ritkina. I'm the front office coordinator here at the San Francisco office. I've been here actually one year tomorrow. I survived! And has loved every minute on it and still am. And I would like to introduce my lovely co-host for today. We're continuing with our doc theme. This is Fawzi. Hope you all you can see him. Fawzi is a Samoyet. He's about seven years old. And he joined the foundation this past summer with his lovely human Amelia. And he's missing her right now. And he's a loyal supporter and member of our legal team. So we're going to get started. Our agenda for today will have a movement update as usual. We will have a presentation from Margi Novotny about who are our Wikipedia users in India. And an update from our Wikimedia 230 movement strategy team, as well as time for questions, discussions, and as usual, wiki love. So without further ado, our movement update. So we have some new leadership appointments here at the foundation. We welcome Jeanine Uzell as our Chief Operating Officer and Valerie DeCoster as our Chief of Community Engagement and Lisa Lewin as our new trustee. We have an ongoing proposal, brand proposal for 2030. And we have begun our consultation with the community on Meadowiki. We're also changing our password policies to evaluate new credential against those that are compromised and require that enforce a minimum eight character password for any newly created account. So that is our quick update. We also have some events coming up. We have the Wikimedia Summit in Germany on the 29th to the 31st of March. The wiki education conference in San Sebastian Spain on April 4th. And one of our favorite events, the hackathon happening in Prague this year on May 16th to the 20th. And without further ado, I'm going to introduce Marguina Vatni. She will be presenting on our Wikimedia users in India. Thank you. Hi, everybody. Okay. Thanks for showing up at this month's activities meeting. I'm here to present some work that we did. We started last spring. And you may you may remember that Daisy Chen had done a presentation back in August last year around the mobile personas work we did for the U.S. So in that in that project, we had developed six different personas showing kind of a range of uses, challenges and motivations for people across kind of across the technology like technology savviness spectrum across the language spectrum and kind of distributed geographically. In a follow-on effort, we did the kind of the same project, but in India. In this case, we ended up with six different personas, which I'll give you sort of a high-level orientation to. And then we did the same project in India. In this case, we ended up with six different personas, which I'll give you a high-level orientation to. Of these personas, all but one are multilingual. In each case, for each of a translation is a really big deal. Three of the six contribute in some way, either small edits or all the way up to kind of being organizers. Of the six, there's varying degrees of awareness of Wikipedia. And by that, I mean even all of these are frequent Wikipedia users, but some of them aren't even aware of Wikipedia as a brand or that they're using Wikipedia necessarily. And then among these six, there's also varying degrees of trust in Wikipedia. And we can talk about that in a second a little bit. So this project took place in over kind of four different regions. We worked with a group out of Pune called Herio, a user experience consultancy that we had worked with before in the past on another project. Herio organized an eight, kind of eight location project north, south, east, and west. And we were looking at different contexts of use, so both very what they call tiers one, two, and three cities, as well as rural context. So the tiers refer to the level of kind of economic development and general literacy in the populations. So we were looking for a sampling from a range of these different tiers, as well as users nearby who are in more rural contexts. And overall, we spoke to 50 participants. Of these 50 participants, we had seven languages covered. So the main two were English and Hindi. But we also spoke to people that were using Kanata, Odia, Punjabi, Marathi, and Urdu. So when we take on a project like this, there's always a stakeholder group of designers and product managers and community folks who are consulted about what are the dimensions that the research or that the stakeholders are most interested in learning about. So for this project, these were the main dimensions. So they were how the, how a different, how each, these different user types use language day to day, whether it's English primarily, whether they're switching back and forth between English in a second language or a third language, whether they're using their regional language first or whether they're using a regional language only. Of course, their comfort level with technology is very important. Their access to the internet is critical. And their awareness of Wikipedia, as I mentioned, can be, can range from, you know, zero to very high. And then lastly, we were looking for people who were strictly consuming to people that made small incremental contributions all the way to people that were trying to organize other people to contribute. And so you may remember from the last presentation that the way we think about these personas is that we kind of try to cover, cover the map of these different dimensions by, you know, looking for combinations of these different characteristics. So I've only showed the colored lines here show three different personas of the six that we have. So just to give you an idea of how we think about making sure that when we finish a set of personas, they are actually a comprehensive, as comprehensive as they can be in terms of covering all the dimensions that our stakeholder group is interested in. So these are our six personas. I'm just going to give you some very high-level anecdotes about each one. And I will point you to the full report and the detailed persona documents which are on meta. So just kind of as a highlight, high point that kind of goes across all of these personas, it was interesting to learn that most of the users preferred the mobile desktop to the application either because they had very limited storage on their phone or because limited storage on their phone or because they just didn't really understand, they didn't really have the tech savviness to really understand the app model at all. So it was either a lack of awareness or just a preference for using the mobile app. So starting at the left side, left side is the new editor is Suje. He's super motivated to edit, but is really challenged by the editing policies and by trying to edit via the mobile desktop on his phone. Sultana is someone who likes to prove a point. She's constantly online looking for sources to justify her arguments. So she's using Wikipedia a lot, half the time without realizing it. But when she's asked about whether or not she believes in the content, her take is that she can't trust the content because she doesn't trust the editing process. She thinks the editing process is faulty. Kartik is a movement organizer. He's an open source proponent. So he's like quite a zealot and evangelizer for the product. He edits a lot but finds it really challenging to do on the app. Ipsita is a tiger mom. She hovers around her kids as they're doing homework and she's constantly trying to help her kids by looking up translating terms from the regional language into English or Hindi. Especially where very little regional content is available. Sukvinder is constantly using Wikipedia to translate terms he's using in school and in his regional language. He's very motivated to contribute because he realizes the deficit in regional content. And finally, Rupinder has a very limited English vocabulary, knows a few words that she can use to search in order to find images that she uses in her business. She speaks and reads a regional language but uses voice search basically to access Wikipedia. So I'm not going to go into a lot of detail on each of the personas. I'm just going to explain how they're organized and you can dive in and take a look at them. But so for each of these personas, there's basic demographic information on each. There's a scale of level of comfort with technology. How much Wikipedia use is a part of their overall internet use? Which devices they have? What their goals and challenges are? And then there's a contextual narrative for each persona. In this study we had to make kind of a change to our typical persona format because we found through the research that two of the personas have kind of what we called kind of split personalities. So there were two flavors effectively of Sujay and of Sita. And they differed in the way that you can see on the diagrams to the right and left. So for example with Ipsita, there are two versions of the Tiger Mom persona. One that is completely tech savvy, completely comfortable on the internet all the time, has several devices, speaks, is bilingual and switching back and forth. And the other Ipsita is doesn't have constant access, has one device, is working from a rural context, has limited understanding or ability to move between languages and limited tech comfort. So we can see with Sujay, so the way to look at these split personas is to say that on this is to read the main page which has all of the key information and then on the second page it shows how the two flavors of persona vary. And finally, the other great bonus of doing this kind of persona work is that you pick up a lot of anecdotal information and recommendations about kind of the pain points and opportunities that each of these user types experience. So the main recommendations that came out of this study were that people wanted to be able to listen to Wikipedia and they wanted it to be easier to do voice based searching on. The academics that we talked to wanted a Wikipedia that was reliable and acceptable as a reference. Several folks wanted to understand how better how the Wikipedia content was created and we saw a relationship between their understanding of how it's created, the process by which stuff is verified, and their level of trust in the content. There was overwhelming desire for a better mobile editing experience so because most of the people weren't using the app they were really struggling with the mobile desktop on the phone and that just doesn't work. Also the new editors, similar to everywhere else, new editors just need ways to get help along the way. One of the anecdotes was that after watching a four hour video one of these editors still was not able to do basic edits. They wanted to have regional articles suggested if they were searching on something in English Wikipedia and there happened to be a regional article available they wanted to know about that instead. And the big piece was in order to drive regional content there was a lot of enthusiasm for partnering with institutions to make sure that contribution is part of the educational experience in India. So the report, the full report is on Wiki, Metawiki and there's a link to it in the stock. So I invite you to go in and read all the good details. Thank you. Alright, thank you Margie and we're going to move on to our next set of speakers which will be our Wikimedia 2030 movement strategy team that is Tanvir Karel and I think we have some guests as well and they will talk about what's going on and please let me know if you need help with the slides. Hello, hello. So Wikimedia 2030, it's about Wikimedia 2030 and we are here to talk first about what is going on and probably you know that already but I just want to remind you that movement strategy this is exciting stuff and I'm really excited to talk about the exciting parts here. For me, there are two things that I want to highlight this month and one of the things that is really exciting for me and what I really like about this process is that we are using the working group model. So we have working groups. Actually we are bringing the diversity that we have in our movement across projects, user groups, bigger chapters also Wikimedia Foundation into the center of movement strategy process with the working group model and these are really great discussions that are going on in the working groups. I hope that you already know by heart the list of working groups. If not, you can go to 2030.wikimedia.org see what are the thematic areas that we are having these discussions on. What I want to talk about here today is the scoping process. I don't know how many of you have heard about this but we have been doing the scoping for the working groups and thematic areas in the recent months and what does the scoping really mean? It's actually three areas that we have been working on. First of all, we have been exploring the thematic area so what should the discussion be about and then there has been work done in defining the exact scope of the working groups. Hence the term scoping and now we are actually in the end phase of this all so it's all about summarizing and delivering the first output from the working groups and this is really great and for this reason I actually have invited to this call two of the working group members. We'll see there were some technical issues so we'll see if they will be available to talk a bit more about what the scoping has meant for their working groups in action. So first up would be Irina. I don't know if she's available. So Irina, are you there? We're still having some technical difficulties. Is there some from strategy you can... Okay, from the silence I can understand that we are still experiencing difficulties so unfortunately I have to fill in. Hopefully you can meet Irina elsewhere and talk about the roles and responsibilities working group. So yes, she's in that working group and what are they really talking about? So these are a couple of scoping questions from that group and it just gives a rough idea what are the discussions about. So the first one being what governance and organizational structures do we need to support the delivery of a strategic direction so really looking at the movement governance, organizational structures, all that. How do we ensure that our governance and operational structures can adapt to social, technological and political change? So this is what the Wikimedia 2030 is also about, adaption and change. And the third one is what is the future structure for the Wikimedia movement that will create less friction and more synergies. So these are the kinds of things we are looking at in the strategy process and in this group. One of the activities what this group has gone through is that they have steady online interaction. They have bi-weekly meetings. They also have working sessions where they are working on concrete topics. They have been preparing the scoping document and one interesting thing that this group has done is that they have gone out there on the field and they have made interviews with people in the movement and actually the summary of these interviews was just uploaded on Meta today so look at the Wikimedia for a link or go browse Meta yourself. So this is really interesting thing and I suggest that you should be reading these interviews if you are interested in that topic. And also they have done a survey to collect some basic information on how different groups in our movement function and this is just an idea of how the working groups are ensuring that they are well informed and up to speed in their discussions. Now looking at the concrete, one concrete task that this group has been doing is actually working on mapping the roles and responsibilities in the movement. So really creating a clear map of who we are today. What are the existing roles and responsibilities and also looking at roles really looking at official and non-official responsibilities related to these roles. Also they have looked on challenges, the good and pain points between different roles and they have done some mapping across the groups to understand what is the originating point of the good or even more the pain points. So to understand that and to ensure that with these movement strategy discussions we can actually initiate structural reform to overcome these challenges and release energy stuck in the challenges. So this is what has been a concrete work of roles and responsibilities working group. And now I'm happy to hand over to Oscar Costero from capacity building working group. Oscar, I hope you are there. Yes, thank you. Thank you Karel, thank you Tambur. I'm going to talk a little bit about the working group and specifically about the work that we do in a subgroup called the Glossary Group. Next slide. Well, first this is like Karel mentioned the scope. That was after months and months of work. We come up with this definition of questions basically asking them to be resolved in the future. The first one is will we just stakeholders should be part of the capacity building efforts but to contribute as well as receive them. The second one, what processes will be needed to build or change it for the specific capacity building efforts. And the third one, how do we make capacity building inclusive and available in a credible way? This is to start with you a lot of long ago I think in August we started with the work. The first task was to know what areas okay parties we have in our work and what was missing basically. We compiled a roster of competencies and based on that we started the work. Then we started to discussing what capacity building was, the definition, what was their internal argument about how capacity or community had to deal with the capacity building if that community have a community in the movement or whether this working group should be designed or recommend anything for her to enter from the scratch. So we have like a formal definition that was work a lot of capacity building and I'm going to read that. It was discussed a lot again for meeting and meeting ends. It is the activities and communication that systematically build, obtain, stranger retain and show knowledge, skills, belief, tools, processes and resources for all Wikimedia stakeholders to move towards our strategic direction to knowledge as a service and knowledge equity. So that was the definition and was part of the subgroup also the whole movement the whole group to work. Later on we decided to debug the work in a small group. One of those small group was the glossary group and I'm going to share with you a lot of findings, few findings that we have for all these months. Yes, next slide. The first one is that capacity building is more than a list of resources. It means extending human connection. This meaning that we see experience in things in the same way or in different ways that another person, another person from another country experienced that experience. The capacity or the glossary group help starting to using a common language because we learned that a work can have multiple definitions depending on the culture or the person where it's from. Also, the capacity building we discovered that it's more like a content meaning best practice, guidance, training, templates and processes that assume human connection to share. And in the end, I think the most important thing of this finding is that capacity building is a work of trust. That is that we naturally develop a trust with each other and help to complete a better work. And I think with this Resonance that we're trying to deliver a capacity building that needs to be for the people when the most needed. In that sense, I think trust is crucial and I think it's something that we need to focus in the next phase that we're going to work working for now. So, yes, that was all. Thank you. Thank you so much, Oscar. So, this is the work that the working groups are doing and this is happening in all of the nine working groups. Everyone has kind of their own path in getting there and you heard the two stories we have from the scoping phase. Now, the big question and exciting question for me to you is how to be involved in the process. And the main point here is that regarding the process, one of the things is that I think the process itself is reimagining ourselves as a global community. So, this is what we are doing and this is what is the idea of the movement strategy process. Also, this means that you are the one who are going to make this happen. So, each one of you, each individual, you are part of the community, the global community that they have and I really would like to see you participating in the conversations and then also implementing the changes in our movement to strive towards the strategic direction. So, this is my hope. And also, we know that communities are the ones that make wiki happen and each one of you are a member of our big global community. So, now we have scoping documents from all the groups and we are now in the phase of making these documents available and hopefully this will happen mid-March. We are also looking into translation options to have them available in a variety of languages and we are also looking finally to kick off a community conversation. So, the scoping documents are kind of the basis of the conversation and we can build on that and have a conversation around that. And you can choose the plan that is suitable for your strategy needs. So, you can go light and just answer to a survey with up to three essential questions from the working groups. You can answer to the questions from just one working group or to the full board and answer to the questions of nine working groups or you can use the pro model for your strategy needs and really dig into it, discuss scoping documents with your communities, your peers and engage also in global conversations. This will happen on different platforms. It will be certainly on meta but we are also looking forward to using social media channels and different discussion platforms. And for this, we are also happy to announce that we are looking for strategy liaisons. So, the call for organized groups has already gone out there. We will also be looking for volunteer community liaisons. We are currently recruiting for nine strategy liaisons for bigger or more notable language communities. So, this is some of the work in the pipeline and you can really be part of that being the kind of coordinating or center point in your community, helping to surface the real key ideas from your own community or from your group. So, this is a possibility for you. So, I'm looking forward to your engagement and I really hope that this will be as exciting for you as it is for me. And you can be in contact with us. So, here are the emails from the presenters today. I'm really sad that Irina had technical difficulties but don't hesitate to reach out to her. She's really a great working group member from Uganda in the Rosinals Responsibilities group and I hope that she can present and share her thoughts some other time on some other platform. Thank you so much. Let's be in touch. All right. Thank you everybody from Movement Strategy and our started working groups Irina, Oscar, Karel and Tanvir. We're going to move on to the next section of our program which is question and discussion. So, if you have questions for any of the presenters, if you have questions for anybody here in the room, do we have anything on IRC Rowan? No. All right. There's also a microphone in the room. You can come up and ask questions. Thank you, Joe. I have a question for Margie on her interesting research. I was very interested to see and I guess a little surprised to see the emphasis on spoken input and output. I guess particularly I was curious why people would want to listen to Wikipedia since it seems like a relatively inefficient or slow way to get information. So, can you say more about what the user's needs and use case is there? Hello there. Sorry about that. Margie? Yes. Sorry about that. So, Joe, I think I caught the gist of your question. So, why would people want to listen to Wikipedia? I think part of it was wanting to have the ability to do to access content while in transit and sometimes it's just easier and hands-free situations like commuting. But then other times was just like to have spoken like the persona of Rupinder liked using the voice search capabilities and would have preferred to have the results kind of read back to her in some cases in her regional language. And that was the case also for, I think it was the mom, the hoverer mom. When you say in the original language, does it mean from an article in that language or does she want translation on the fly in audio? They talked about translation on the fly as well as just reading back just having an audio version without translation as well. Thank you, Margie. Any follow-up questions? Do we have any more questions on? Not a question, but I would like to follow with something that Margie mentioned. This is coming from the experience that I have working with Indian languages. One of the reasons why people prefer to have audio input is because typing in Indian languages is very, very problematic. There is no good script that allows for easy typing and easy access of search words. Hence the request and the idea that audio becomes more important. Thank you. Thank you. Margie? Thanks, Tampere. We have a question on IRC. Hello, yeah. On IRC, Pine says, I will ask a brief question for Carol. Is there a timeline that he can share for upcoming milestones? I guess the timeline will have estimated dates, and that's fine. Yeah, I was just checking if it's on meta, so I will also follow up on IRC. But the current timeline, as it is, is that from mid-March to mid-April, we'll run the community conversations. And also the Wikimedia Summit is part of that, so Summit will this year be dedicated more to the strategy, and there will be more discussions around that. It's Affiliate Conference, so this is for organized groups, but this is kind of in the center of community conversations, and community conversations are built around that. And then we actually go to the analysis phase with the working groups, and we look forward to having draft recommendations delivered for Wikimedia. So this is the timeline we are working with. I will just check what is the current timeline on meta, and we will follow up also on IRC. Thank you for your question, Pine. Thank you, Karel. Any questions on the room? IRC? Going once? Going twice? All right. Hendix. Oh, this is from Margie's presentation. Margie, did you want to speak to this? I can't see what this is. Okay. Oh, okay. All right. Oh, so last but not least, or actually not last, make sure if you want to present, if you want to participate in the monthly activities meeting that you sign up on meta, our next meeting will be on March 26, I believe. So just a month away from today, and make sure to sign up. We have March 28. Thank you. I knew it was the same date. And we're going to move to WikiLove. So I just want to express some WikiLove for my co-host right here, who if you can't see has made my pants a lot more white. He's a lovely, lovely office dog, one of our many, and he offers really good therapy. When you need a stress reliever. Anybody else in the room? IRC, our presenters. Some WikiLove. Please use the microphone on the side of the room. Thank you. Hello, everyone. I'm Katie Love, and there are three people that I wanted to say thank you to and appreciate their contributions. The first is Chris Schilling on the Community Resources Team, who has just wrapped up a round of project grants and these grants that have just been approved and will be announced tomorrow are some fabulous community-led projects on increasing the visibility of some of our more marginalized communities and underrepresented communities. They are projects doing all sorts of cool technical projects. It's just a fabulous cohort of folks. So when you see the announcement come out, please do take a look at some of those projects and say thank you to Chris for his amazing facilitation of that participatory grant committee. And then I wanted to say thank you so much to Thomas, who's been a huge supporter to the Community Engagement Department over the last few months and just a fabulous addition to our department, Thomas E. Rock. And finally, I wanted to say thank you to my wonderful co-partner in all things strategy, which is Sati Houston, who has done such a fabulous job in helping move forward a number of many projects on our team and who has done so with patience and grit and compassion and so much grace. That's it. So there's one on Google Hangout that says lots of wiki love and wiki courage for Oscar. He has attended all the meetings despite the difficult situation in Venezuela. I just want to say thank you to Sasha and Robert for the lovely loose leaf tea in the office. It makes me a little bit more happy every time I drink it. Thank you. And it comes in cute jars. Yeah, thank you for the tea. I love it too. And wiki love for Winifred for being an amazing friend and being supportive through challenging situations. All right. On IRC, Quiddity gives wiki love to the admins and contributors who deal with on wiki spam and vandalism, in particular to all the stewards on meta wiki and users clump and Shira Yuki on media wiki wiki. And Pine gives wiki love to Dario for his years of service and congratulates Leila on her promotion. Anyone else? I also want to give wiki love to this entire foundation and this office who welcomed me a year ago and still continue to be a lovely work family and wonderful friends. And thank you to Amelia, Fawzi's human. She's somewhere in the office for letting me borrow him and bringing him to the office and all of our other dog owners who bring their, or other dogs who bring their humans to the office. All right. All right. Last call for wiki love or questions. Miss Kate. I wanted to say thank you to analytics engineering and particularly Luca and Andrew who have been doing an amazing job reaching out to product analytics and giving us a heads up about some of the changes and we really appreciate that extra communication. Some more wiki love from Maria. Yes. Lots of wiki love for Abby who is super supportive of new design research projects and is inviting people to think from a design perspective and I really appreciate it. All right. Going once, going twice. All right. Well, thank you everybody for coming. Thank you for the comms team for giving me the opportunity to host this and we will all see you next month on March 28th which is 11 a.m. Pacific 1700 Universal Time Universal Time I got to remember my European time and oh, one more. And one more because this tree might be a little bit behind. Okay. Thank you. Caitlin Cogdale sends wiki love to Jessica Robell on the fundraising team for managing translations in dozens of languages right now thanks to our characteristic patients and Grace. Woo! All right. Thank you everybody for coming and we will all see you next month. Bye-bye.