Grants:Programs/Wikimedia Community Fund/General Support Fund/Indic MediaWiki Developers UG 2024 Annual Plan/Final Report
|
|
Part 1: Understanding your work
[edit]Per the recent update on the Wikimedia Foundation Affiliates Strategy process, Wikimedia Affiliates that are General Support Fund grantees will fulfill their affiliate reporting requirements through their final or yearly grantee report.
If you are a Wikimedia Affiliate, you will use this form for your affiliate reporting and to address the affiliate health criteria. You do not need to submit a separate report to AffCom. Follow the guidance in the green boxes to report on how you met the corresponding affiliate health criteria.
If you are not a Wikimedia Affiliate, aligning your responses with the affiliate criteria is optional and not required.
1. Please share to what extent your programs, approaches, and strategies contributed to addressing the challenges you shared in your proposal. If they did not contribute as you believed they would, please share what obstacles you faced and what, if anything, you learned from them? (required)
For affiliates, use this space (Question 1.) to address Affiliate Health Criterion 1.1 (Goal delivery). Describe how you actively delivered on mission goals, e.g. content creation.
Before starting to work on the 2024 annual plan, one of our main goals was to bring more structure and organize our activities in a better way, thereby creating a more sustained impact. To expand on that, previously the technical community in India was primarily engaged through several ad-hoc hackathons, workshops and some other conferences every now and then. While the community existed, it was more spread out and lacked coordination. It also became increasingly hard to retain newcomers in Wikimedia technical spaces. Our primary goal for the 2024 annual plan was to facilitate better organization of the technical community in India, support initiatives (by our UG or other stakeholders) to expand the community, and overall have better coordination among technical contributors. We are happy to say that we have done reasonably well in reaching this goal. While it is hard to quantify to what extent, there has been substantial progress compared to 2023.
- Continuous engagement:** Last year, we organized three major in-person activities. The first one is a newcomer workshop combined with a 30 hour non-stop hackathon in collaboration with amFOSS, a community of student developers based in Amrita Vishwa Vidyapeetham. This was followed by a hackathon in Guwahati, which is a mix of both new developers, existing developers and some community members who have knowledge of technical challenges of Wikimedia projects. The last hackathon is a national level event which brought together more than 50+ participants from various backgrounds and experience levels. It was a first of a kind national level Wikimedia hackathon in India.
The way these events were organized such that the interested participants continue to have continuous engagement over an extended period of time, which was a challenge we have been trying to address. The hackathon in May 2024 with amFOSS has been quite productive, as it was a student club already contributing to various FOSS projects and their some knowledge of Wikimedia movement (owing to an activity during the preceding year), has proven to effective in easy onboarding of the students to Wikimedia technical spaces, and organize a 30 hour non-stop hackathon, which we fixed several bugs. While some of the students retained and continued to engage with the community, they were selected (through an open scholarship process) to attend a mini-hackahton at Guwahati in July 2024. This provided a space for new developers to connect with the rest of the community and vice versa.
Post this, we continued to engage the newcomers asynchronously providing mentorship for the projects they have been working on. Towards the end of the year, we culminated all the activities with a national level hackathon, which again provided a space for new developers, not only from the workshops organized by the User Group, but also various other developer outreach programs ongoing in India, such as Road to Wiki, and WTS hackathon. Towards the end of the year, we have a much bigger technical community in India and volunteers willing to contribute than at the beginning of the year. However, it is worth noting that it is a result of combined effort of various stakeholders in working for developer outreach in India, including but not limited to, CIS-A2K Technical Outreach, Road to Wiki program, and Wikimedia Technology Summit by IIITH. We are happy that the User Group has been involved at various levels and provided support to these programs and has been crucial in coordinating across the board.
In addition, some of the activities taken up by the user group are
- Indic Wikimedia Technical consultations 2024
- Representing MediaWiki at IndiaFOSS 2024
- One-day introductory workshop at SATI WikiClub
- Support to Road to Wiki program
- Support to WTS hackathon and conference
We will expand on these activities in the further sections below.
One of the approaches that worked well for us during last year’s annual plan is being flexible with our programs, but not deviating too much from the proposed plan. As last year was our first annual plan, while we had listed activities all throughout the year, as the plan unfolded, somethings didn’t go as planned due to timeline issues, and also we came across new opportunities which we pivoted, and which resulted in better outcomes rather than the one we originally planned for. One such example is, representing MediaWiki at India FOSS 2024. Initially, this activity was planned to be a college workshop, like an introductory session, and when we came across IndiaFOSS - it felt right to pivot to that instead, as it provided a bigger opportunity to create awareness of MediaWiki to a larger audience. It proved to be quite effective -- we had a dedicated stall for MediaWiki, and engaged over 60+ FOSS enthusiasts, and more than 100+ people signed up to know more about the space and potentially contribute.
We have also kickstarted a Telegram group named Indic Wikimedia technical forum, which is a coordination group to bring together not only developers but also editors to share their challenges. The group was launched in October 2025 and has 100+ members. Although we plan to increase its engagement during 2025.
Another one is supporting initiatives by other stakeholders such as Road to Wiki and Wikimedia Technology Summit. India has a huge opportunity to tap into the massive developer population, and it is always good to have multiple stakeholders working towards the goal and coordinate. Even though we didn’t initially plan for our bandwidth to be involved with those programs, supporting them in various roles such as mentorship, hackathon planning, workshops etc. was not only helpful for sharing our experience, but also learning from them. This has also been effective in coordinating across the groups and working towards a common goal.
One of the things we didn’t anticipate, but has significantly cost our bandwidth is the logistics of activities. As we started to organize the activities and overtime, we only realized more and more that organizing logistics (such as travel, accommodation, event spaces etc.) can be very time consuming. It means that we had to allocate less time to other programmatic areas of work such as the hackathon program, overall strategy, follow-up and retention areas. This was crucial learning for us as we move into 2025. We feel that volunteer time is best not spent on organizing logistics as much as possible, and outsource it.
2. Is there a plan to build on the key successes you had? If yes, please describe the plan and if no, please share the limitations to do so. For instance, did the activities lead to any new priorities, ideas for activities, or goals for the future? (required)
We would like to iterate on the continuous engagement part -- although there is a lot of room for improvement, this model is proving to be effective. We have taken our learnings from 2024 and used them in planning and drafting the [[1] 2025 Annual Plan]. The next year’s annual plan focuses on a similar work plan, however, with more emphasis on retention and follow-up in between events. One of the key changes is that, instead of passively letting the newcomers engage in projects, we have planned for a few different initiatives that will help us to actively engage them. For example, the Developer Skill Development program for about 15-20 existing developers, to further improve and refine their skills to contribute to Wikimedia technical areas, and the Community Technical Task Force, a working group formed at the beginning of the year and will be working quarterly. Each quarter the group will consult with one language community, understand their issues, and surface them using Phabricator.
We have planned for the developer skill development specifically to bridge the gap of volunteers contributing to complex tasks and also mentors for newcomers. Currently, the community has a very limited set of people who can mentor during the hackathon and later async hourly. This is not sustainable in the long run as volunteers phase out and may not have enough bandwidth. In addition, most of the work during the hackathons and otherwise is limited to good first tasks, while they are good to get started, overtime we want to get to more complex tasks and these developers feel confident to take up requests from the community. So the developer skill development focuses exactly on that problem. Where we want to take existing developers from the community and train them with necessary advanced skills, and also provide them with opportunities to mentor new projects and take up complex tasks themselves.
As a user group based in India, with one of the primary goals to support Indic language Wikimedia projects, we want to improve our interactions with the communities in the region and establish a solid network with them. In 2024, we initiated technical consultations with five communities to broadly understand the technical issues being faced. By the end of the year, this will help us get a good understanding of the common problems. The technical task force will use that as a foundation, to further have conversations with communities to work on their most pressing issues. The way we are imagining this is to have a working group formed at the beginning of the year and will be working quarterly. Each quarter the group will consult with one language community, understand their issues, and surface them using Phabricator. These will be used not only for hackathons and workshops but also to guide new developers. The goal is to do these for at least three of the four quarters.
3. Please provide a link to reports that detail the activities that took place in the last year. This can include an annual report, Meta pages, and websites. If there are no links available, briefly describe the implemented activities and programs below or upload any files. (required)
For affiliates, use this space (Question 3.) to address Affiliate Health Criteria 2.1 (Affiliate health & resilience), 4.1 (Internal engagement), 4.2 (Community connection), and 4.3 (Partnerships and collaboration):
- Describe your activities engaging new users, new members for your decision-making body(ies), and developing leaders and organizers (2.1).
- Describe your activities creating or hosting spaces to encourage greater collaboration and engagement among your members (4.1).
- Describe how you engage with the contributing community that you serve and/or support (4.2).
- Describe your partnerships with other affiliates or with non-Wikimedia entities (4.3).
Relevant links:
![[3]](https://meta.wikimedia.org/wiki/File:Group_Photo_Wikimedia_Hackathon_Kochi_2024_Event_24.jpg){kind=link}
![[5]](https://meta.wikimedia.org/wiki/File:Day-2_Indic_Mini-Hackathon_Guwahati_2024_16.jpg){kind=link}
![[9]](https://meta.wikimedia.org/wiki/File:Indic_Wikimedia_Hackathon_Bhubaneswar_2024_-_Group_photo_-_02.jpg){kind=link}
Documented work on Phabricator: [13]
Affiliate health related:
2.1: One of the primary goals of our outreach activities is to bring new developers into the community. We believe that in the long term we believe that this is an extremely important aspect for not only affiliate health and sustainability, but also for the overall health of the technical community in India. Apart from engaging the existing community, we specifically think about engaging and retaining newcomers as part of our activities. In addition, we have adopted a model of adopting core and extended working group members. The goal for the extended group is to train future leaders of the affiliate to ensure sustainability. In 2025, one of our goals is to develop a more robust governance model along with responsibilities.
4.1:
- Technical consultations
- One of the projects that our User Group has taken up in 2024 was to recognise the need for a more structured approach to identify common gaps and challenges among the Indic language Wikimedia communities and systematically tackle them. A pivotal component in finding commonalities in technical needs/issues across communities plan is the Technical Consultations 2024, aimed at understanding Indic language communities to gain a comprehensive understanding of their technical needs and obstacles.
- As a pilot initiative we have launched a survey form for five language communities namely Malayalam, Odia, Punjabi, Telugu and Gujarathi — who were part of this, with an active participation from 26 community members to address their technical challenges while contributing to the Wikimedia projects. The Indic MediaWiki Developers User Group has collaborated with the A2K team of Centre for Internet and Society in consolidating the survey results and connecting it to the next steps of Global Majority Wikimedia Technology Priorities
Some of the findings from the survey are as follows:
- 59% of the respondents either do not know about Wikimedia Phabricator or do not know about its use case
- Close to 77% of the respondents reported issues in using the templates on their language project
- One of the projects that our User Group has taken up in 2024 was to recognise the need for a more structured approach to identify common gaps and challenges among the Indic language Wikimedia communities and systematically tackle them. A pivotal component in finding commonalities in technical needs/issues across communities plan is the Technical Consultations 2024, aimed at understanding Indic language communities to gain a comprehensive understanding of their technical needs and obstacles.
- As a pilot initiative we have launched a survey form for five language communities namely Malayalam, Odia, Punjabi, Telugu and Gujarathi — who were part of this, with an active participation from 26 community members to address their technical challenges while contributing to the Wikimedia projects. The Indic MediaWiki Developers User Group has collaborated with the A2K team of Centre for Internet and Society in consolidating the survey results and connecting it to the next steps of Global Majority Wikimedia Technology Priorities
- 59% of the respondents either do not know about Wikimedia Phabricator or do not know about its use case
- IndiaFOSS
- IndiaFOSS 3.0 is the third edition of the Free and Open Source Software (FOSS) conference organised by the FOSS United community annually. The conference took place on 7 and 8 September 2024, at the NIMHANS Convention Centre in Bangalore. This event served as a vibrant platform for developers, enthusiasts, and advocates of open-source software to converge, share knowledge, and collaborate on various projects. Attendees included a diverse mix of software developers, tech entrepreneurs, policy makers, educators, and students, all united by a common interest in promoting and advancing the FOSS ecosystem in India.
- The Indic MediaWiki Developers User Group hosted a booth with the primary objective of increasing awareness around Wikimedia projects and inviting developers to contribute to the technical aspects of the Wikimedia projects. To engage attendees, the user group representatives at the conference organised an interactive session featuring "The Wiki Game," a challenge that encouraged participants to navigate between Wikipedia articles efficiently. Winners of the game were rewarded with exclusive Wikimedia-themed SWAG, fostering enthusiasm and drawing more visitors to the booth. This initiative not only highlighted the collaborative nature of Wikimedia projects but also successfully encouraged developers to explore and contribute to the technical spaces within the Wikimedia ecosystem.
- IndiaFOSS 3.0 is the third edition of the Free and Open Source Software (FOSS) conference organised by the FOSS United community annually. The conference took place on 7 and 8 September 2024, at the NIMHANS Convention Centre in Bangalore. This event served as a vibrant platform for developers, enthusiasts, and advocates of open-source software to converge, share knowledge, and collaborate on various projects. Attendees included a diverse mix of software developers, tech entrepreneurs, policy makers, educators, and students, all united by a common interest in promoting and advancing the FOSS ecosystem in India.
4.3
- CIS-A2K
- The Indic MediaWiki Developers User Group has partnered closely with the Centre for Internet and Society – Access to Knowledge (CIS-A2K) team to strengthen technical and outreach initiatives within the Wikimedia ecosystem. This collaboration has been instrumental in supporting key events such as the Indic Wikimedia Hackathon 2024, held in Bhubaneswar, where CIS-A2K provided logistical support to ensure meaningful participation from diverse language communities. The partnership also played a crucial role in supporting their pilot initiatives like technical consultations where A2K team has collaborated with us in consolidating the responses from community members across five language communities to better understand and prioritise common technical needs.
- Beyond these, the user group has also collaborated in capacity-building efforts, particularly through education and club programs. We have supported the A2K’s initiative with mentorship and worked alongside to co-design the education outreach model that integrates Wikimedia’s technical contributions opportunities. This sustained collaboration has enabled the user group to focus on long-term impact, ensuring that technical contributions are not only inclusive and community-informed but also well-supported through institutional frameworks.
- VVIT WikiConnect Tech
- The VVIT WikiConnect Tech Club at VVIT College, Namburu, marks a significant step in nurturing student engagement with the open knowledge and open source ecosystems. In collaboration with CIS-A2K, a pilot education program was launched to introduce students to Wikimedia’s values and technical spaces. The program currently engages seven pre-final year engineering students, providing them with structured mentorship and training. Through this initiative, students are not only exposed to foundational ideas around open knowledge movements but are also equipped with the technical skills necessary to contribute meaningfully to Wikimedia projects.
- As part of this pilot, the students have been assigned to work on the Indic Community Insights Dashboard — a project conceptualised by the Indic MediaWiki Developers User Group and the A2K team to address the growing need for accessible, community-level data insights. While some high-level metrics are already available through tools like Wikimedia Stats, communities often seek more detailed, granular information to inform local activities, tool usage, and user engagement. The dashboard aims to fill this gap by providing a user-friendly, interactive interface focused initially on Indic Wikipedia projects. This scope allows for resource-efficient development and targeted feedback collection, laying the groundwork for future iterations that can scale to other Wikimedia projects.
- Road to Wiki
- The Indic MediaWiki has also partnered with IIIT-Hyderabad for the Road to Wiki program, which was designed to introduce students to the technical ecosystem of Wikimedia and build capacity for sustained engagement. The User Group has also supported the initial onboarding process by conducting both online sessions and on-campus workshops, ensuring students had a foundational understanding of Wikimedia’s philosophy and infrastructure. Through these sessions, students were introduced to critical components such as setting up local MediaWiki instances, navigating Phabricator for project management, and selecting appropriate technical tasks aligned with their skills and interests.
- Beyond the onboarding, the user group has also played a key role in mentoring and shaping the overall curriculum for the program. This included guidance on the program’s workflow, contribution pathways, and identifying tasks with real-world impact within Wikimedia’s technical landscape. Members of the user group have also provided mentorship to the students enrolled in the program — guiding them in understanding tasks, accessing the right resources, and submitting their first patch requests for their contributions to Wikimedia projects.
4. Are you interested in sharing what you achieved or learned this year with the wider community through different peer learning programs (e.g. Let's Connect program, Diff)? (optional)
5. Did you collect feedback from your community or target groups on how the activities implemented impacted them? If yes, please attach/provide information on the results (e.g. community surveys, stories, impact booklets/reports, interviews with partner institutions, etc). Did you collect other impact-specific data? (required)
For affiliates, the response to Question 5. also partially addresses Affiliate Health Criteria 4.1 (Internal Engagement), 4.2 (Community Connection), or 4.3 (Partnerships & collaboration), where applicable.
- Kochi Hackathon 2024 post event feedback survey: [16]
- Bhubaneswar Hackathon 2024 post event feedback survey: [17]
6. During the fund period, did your efforts do any of the following? (required):
For affiliates, the response to Question 6. also partially addresses Affiliate Health Criterion 2.2 (Diversity balance).
- 6.1 Bring in participants from the following groups: women, people from lower socioeconomic status, young people, underrepresented geographical regions (ESEAP, LATAM, SSA, MENA, SA)
- 6.2 Develop content about the following underrepresented topics or groups of people: other
- 6.3 Support the retention of: Editors, Organizers, Partnerships, other
7. What, if any, effective tactics or approaches can you share that worked well when dealing with the programs under points 6.1-6.3 that you selected? (optional)
optional: n/a (described above)
8. If you developed partnerships, which of the following factors most helped you to build partnerships? Please pick a MAXIMUM of the three most relevant factors (optional):
N/A
Part 2: Metrics
[edit]| Metrics name | Target | Result | Comments and tools used |
|---|---|---|---|
| Number of all participants | 180 | 202 | |
| Number of all editors | N/A | ||
| Number of new editors | N/A | ||
| Number of retained editors | N/A | ||
| Number of all organizers | 12 | 16 | |
| Number of new organizers | 6 | 5 |
| Wikimedia project | Target - Number of created pages | Target - Number of improved pages | Result - Number of created pages | Result - Number of improved pages |
|---|---|---|---|---|
| Wikipedia | ||||
| Wikimedia Commons | ||||
| Wikidata | ||||
| Wiktionary | ||||
| Wikisource | ||||
| Wikimedia Incubator | ||||
| Translatewiki | ||||
| MediaWiki | ||||
| Wikiquote | ||||
| Wikivoyage | ||||
| Wikibooks | ||||
| Wikiversity | ||||
| Wikinews | ||||
| Wikispecies | ||||
| Wikifunctions or Abstract Wikipedia |
Tool used and comments (optional):
11. Did you set other quantitative and qualitative targets for your project (other metrics)? (required): Yes
11.1. Other Metrics.
In your application, you outlined some other open metrics that you would like to measure. Please fill out the achieved results for each of the open metrics you defined.
| Other Metrics name | Metrics Description | Target | Result | Tools and comments |
|---|---|---|---|---|
| Number of newcomers to Wikimedia technical spaces | Number of people who have been introduced to Wikimedia technical spaces | 50 | 75 | Gerrit, GitLab and Phabricator |
| Number of new contributors to Wikimedia technical spaces | Among the "Number of newcomers to Wikimedia technical spaces", the number of people who have contributed to at least one technical task (bug fix, tool development, documentation etc.) | 20 | 40 | Gerrit, GitLab and Phabricator |
| Number of new contributors to Wikimedia technical spaces retained | Among the "Number of new contributors to Wikimedia technical spaces", how many people have been consistently contributing to technical spaces. What is considered consistent will be hard to define, however, it will be a few contributions spread out across the year. | 5 | 10 | Gerrit, GitLab and Phabricator |
Part 3: Skill Development / Capacity Building
[edit]12. Reflecting on your programmatic (external) and organizational (internal) work, did your grant support you to undergo any skill development that made a difference to your success? If yes, what skill was developed, and how did it lead to success? (e.g. received coaching on public speaking, attended training on nonviolent communication, hosted professional development conversations on leadership, learned and used a new tool for project management, etc.)? Can you share any materials? (required)
For affiliates, use this space (Question 12.) to address Affiliate Health Criteria 2.2 (Diversity balance) and 3.1 (Diverse, Skilled, and Accountable Leadership):
- Describe actions taken to prioritize gender balance in affiliate leadership, as well as any areas of diversity relevant to your affiliate's context (2.2).
- Describe the management, financial, or other leadership skills of your affiliate leaders. If you have a succession plan, please include it here (3.1).
- Describe any training or skill development (as outlined in the question above) (3.1).
- Incorporate into the annual report a disclosure of conflict of interests (if any) from the leadership (3.1).
Although we didn’t have any specific skill development program, it would be good to reflect on some of our learnings. Although we are not a registered organization, having a full scale annual plan and budget and year long activities was a great learning experience as a group. The working group has divided responsibilities in a way that at least one from the core group and one from the extended group take up various areas of responsibilities, which include but are not limited to: overall coordination, communications, logistics, budgeting. We made sure that each activity has a mix of both an experienced organizer and newcomer in each of these areas. In addition, we also had some rotations throughout the year to get some exposure to different areas.
13. What is one capacity/skill area that you would like to focus on for the next year? And how do you plan to achieve this capacity? (required)
For the upcoming year, we would like to focus on one capacity/area, which has two sub-areas to say. It is long term sustainability and leadership grooming. Towards the end 2025, apart from the mentioned programmatic goals, our goal is gradually phase out the existing core working group, into more like an advisory and have people from the extended group who have been learning all through this while to take up leadership responsibilities. This is essential as new leadership, along with a growing community is healthy for an affiliate. Connected to that, we want to work on clearly defining the roles of core and extended working groups, along with advisory groups and other governance structures as we feel necessary. So to summarize, we want to work on developing robust governance guidelines and practices that will enable leadership development and transition in the affiliate.
14. If you have additional information or reflections that don’t fit into the above sections, please write them here. Use the space below to upload any additional documents that would be useful to understand your report.
For affiliates, also use this section (Question 14) to fulfill the Affiliate Health Criteria requirements.
- Describe and link to any public-facing documentation for affiliate governance, including affiliate leadership and membership with a breakdown of the demographics; how elections are conducted; how conflicts of interest are declared; and how decisions are made and communicated (2.2, 2.3, 3.1).
- Describe and link to any public-facing documentation for activities incorporating, promoting awareness about, or enforcing the Universal Code of Conduct in your affiliate's activities (3.3).
- Describe and link to any public-facing documentation for internal membership engagement, such as notes from your regular meetings and how you communicate to or involve your membership (4.1).
We actively promote UCoC as part of our communications, during the events but also requirement for participant in our activities. We take explicit agreement to follow UCoC
Part 4: Financial reporting
[edit]For affiliates, also use this section (Part 4: Financial reporting) to address Affiliate Health Criterion 3.2 (Financial & Legal Compliance).
| Description | Planned / received budget for this category (EUR) | Amount spent (EUR) |
|---|---|---|
| Personnel costs | 0 | 0 |
| Operational costs | 480204 | 7208 |
| Programmatic costs | 3040220 | 31780 |
| Total General Support Fund | 38988.49 | 38988.49 |
| Other revenue | ||
| Remaining funds from General Support Fund | N/A |
15. Please state the total amount spent from this fund in your local currency. (required)
38988.49 EUR
16. Please provide an overview of the amount spent from this fund in the following budget categories in your local currency. (required)
- Operational costs: 7208 EUR
- Programmatic costs: 31780 EUR
- Staff and contractor costs: 0 EUR
17. Did you have any other revenue sources (e.g. other funding, membership contributions, donations)? (required): No
- 17.1. Provide the total amount received from other revenue sources in your local currency. (required): EUR
- 17.2. Provide the total amount spent from other revenue sources in your local currency. (required): EUR
18. Provide a financial report document which will provide the details of funds received and spent in the currency of your fund. (required)
- Upload Documents, Templates, and Files.
- Report funds received and spent, if template not used.
18.2. If you have not already done so in your financial spending report, provide information on changes in the budget in relation to your original proposal. (optional)
Note: The receipts and breakdowns have been submitted to the fiscal sponsor Wikimedia Austria.
19. Do you have any unspent funds from this funding?: No
20. Final confirmations (required)
- 20.1. Are you in compliance with the terms outlined in the fund agreement? You must be in compliance with relevant tax laws and regulations restricting the use of the Funds as outlined in the grant agreement. In summary, this is to confirm that the funds were used in alignment with the Wikimedia Foundation mission and for charitable/nonprofit/educational purposes.
- Yes
- 20.2. Are you in compliance with all applicable laws and regulations as outlined in the grant agreement?
- Yes
- 20.3. Are you in compliance with provisions of the United States Internal Revenue Code (“Code”), and with relevant tax laws and regulations restricting the use of the Funds as outlined in the grant agreement? In summary, this is to confirm that the funds were used in alignment with the WMF mission and for charitable/nonprofit/educational purposes.
- Yes
This is an automatically generated Meta-Wiki page. The page was copied from Fluxx, the web service of Wikimedia Foundation Funds, where the user has submitted their report. Please do not make any changes to this page because all changes will be removed after the next update. Use the discussion page for your feedback. The page was created by CR-FluxxBot.