Community Resources and Partnerships/India General Support Project/IMD-UG:2026 Annual Plan

statusSupported

India General Support Project

IMD-UG:2026 Annual Plan

request IDP-IG-2603-22145

proposed start date2026-07-01

proposed end date2027-06-30

amount requested (INR)5976630 INR

amount requested (USD)48268.76 USD

organization (if applicable)• Indic MediaWiki Developers User Group

Universal Code of Conduct

Applicant information

Organization name or Wikimedia Username for individuals. (required)

Indic MediaWiki Developers User Group

Are you a first-time applicant? (required)

You are applying as a(n). (required)

Wikimedia Affiliate (chapter, thematic org., or user group)

Are your group or organization legally registered in your country? (required)

No

Please provide links to the following documents if they are available

These documentation can be provided in your local language(s), no translations required.

• Organizational website
• Detailed financial reporting and/or audits
• Documentation of the governance structure, board list, governance processes
• Documentation of the general assembly decision on your plan

[1]

Main proposal

1. Please state the title of your proposal. This will also be a title for the Meta-Wiki page. (required)

IMD-UG:2026 Annual Plan

3. Proposed start date. (required)

2026-07-01

4. Proposed end date. (required)

2027-06-30

5. Does your organization or group have an Affiliate or Organizational Annual Plan that can help us understand your proposal? If yes, please provide it. (required)

No

6. Does your affiliate, organization or group have a Strategic Plan that can help us understand your proposal? If yes, please provide it. (required)

No

7.1. Where will this proposal be implemented? (required)

India

7.2. If your project includes in-person activities, are there any international participants travelling to India for them? (required)

No

7.2.1. List all countries of participation. (required)

N/A

7.3. Will the project be transferring funds to any international participants? (required)

No

7.3.1. List all international participants receiving funding and their countries. (required)

N/A

8. What are your programs, approaches, and strategies? What are the challenges that you are trying to address and how will your strategies support you in addressing these challenges? (required)

Intro to the User Group 

Indic MediaWiki Developers User Group is a group of volunteers working on technical issues and the development of tools, with a focus on the needs of Indic language Wikimedia projects. We have been an informal group since 2018 ([2]) and have been formally affiliated with WMF since 2020. During the past few years, we have been engaged in several activities, including active technical development such as Indic Wikisource Stats, Incubator Stats, VideoCut Tools, Wikimedia Community Activity Alerts Tool, Scribe-Org, Lingua Libre, Montage etc. and also outreach to encourage newcomers to Wikimedia technical spaces such as amFOSS hackathon, Small Wiki Toolkits workshop series, Wikimania Hackathon (regional level), mini hackathons, Developer skill Development program, etc.

2024 and 2025 Annual Plan

Two years ago, we applied for our first annual plan grant, with a focus on transitioning the group from doing ad-hoc activities to more planned activities throughout the year, which has been successful to an extent. In 2024, during our first annual plan, the majority of the activities were focused on bringing newcomers through various hackathons and outreach activities IndiaFOSS. During the same time we also had several other initiatives in India come up, like the Road to Wiki program, which has been effective and we have also been supporting it. Keep this in mind, during 2025 we are geared towards mentorship and enabling newcomers to move from beginner to intermediate levels (i.e. contributions beyond good-first-tasks). We are seeing some good outcomes for the same.

Upcoming annual plan:

Strategic Positioning and Framework for 2026:

As we plan for 2026, we recognize the evolving landscape of Wikimedia technical outreach in India. When we first started the UG in 2022, there were not many efforts for technical outreach in India, but with initiatives like Road to Wiki and Wikiclubs emerging across colleges, we are taking this opportunity to think about our long-term goals within the broader ecosystem and where we want to focus our efforts. While multiple efforts are working toward growing the community, we aim to complement rather than duplicate these initiatives. Our unique strength lies in leveraging existing FOSS communities and technical networks to identify potential contributors, and more importantly, in our ability to develop their skills systematically, transforming newcomers into skilled developers through structured mentorship and hands-on technical experiences. While this will further evolve towards the end of the current and early phases of the upcoming annual plan, we will be thinking of a few directions. 

We are planning to adopt an OKR (Objectives and Key Results) framework to organize our work in the following manner: Identification (exploring FOSS communities and educational institutions as partner hubs), Intervention (bringing newcomers into Wikimedia technical spaces through workshops and hackathons), and Integration (developing their skills and making them active community members). While we have been executing activities across these areas, we recognize the need to explicitly document our objectives and connect each program back to measurable outcomes and long-term impact. During the first few months of 2026, before the plan officially begins, we will work on defining specific OKRs in consultation with stakeholders in advisory roles, ensuring that at least 80% of our programs are directly aligned with these documented goals. This approach will help us maintain strategic clarity, communicate our purpose more effectively to the community, and plan activities based on outcomes rather than just events.

• Objective 1: Strengthen technical contributor growth, leadership, and inclusion in Wikimedia technical spaces in India
• Key result A: Developer Skill Development: If we focus efforts on training existing developers who have already contributed to good-first-tasks, into training them to contribute to existing code repos or projects with medium complexity, it will help them grow as open-source contributors and expand the community in India.
• Key result B: National Hackathon: If we adapt the program of the national hackathon that happens to work on tasks with medium to high complexity, it will encourage existing developers to take up relatively complex tasks later.
• Key Result C: Women Technical Leadership If at least two out of eight annual Small Wiki Toolkits workshops are led by trained women mentors, it will increase visible technical leadership, create relatable role models, and encourage sustained participation of women contributors.
• Key Result D: Women-focused Technical Program If we organize at least one women-only technical program or mini hackathon designed and facilitated by an all-women team, it will create safer learning environments, reduce participation barriers, and help build a pipeline of future women technical leaders.
• Objective 2: Increase the number of sustainable partnering organizations in India that can serve as potential hubs for recurring future contributors regularly.
• Key result A: Introductory workshops at colleges: If we deliver 2 introductory workshops at selected colleges/FOSS communities with existing open-source culture and encourage them to apply to our next events like SWT workshops/hackathons, then we can convert them to potential partnerships.  
• Key result B: If we run at least one similar format like the amFOSS Mini-hackathon in this hub, then we can convert them to the first set of contributors for MediaWiki from that hub.
• Objective 3: Support Indic language communities through technical solutions and continuous community assistance
• Key result A: If we develop at least 3 scripts/bots/tools based on inputs from Indic language communities, it will reduce technical barriers and improve the sustainability of community workflows.
• Key result B: If we provide technical support/consultation via IndicWikiTech Forum to at least 2 communities, it will create an accessible and responsive technical support ecosystem for Indian language communities.

Details of activities

For the upcoming year, we will not be expanding activities, but would like to use what we have learned from previous years and standardize the activities for next year's annual plan, which will focus on streamlining our working procedures, improving the outcomes of such activities, documenting processes, and developing sustainability for the group in the long term.

Our work is broadly divided into two groups: technical support and outreach.

1.)Technical support focuses on the active technical development of [[3] tools], [[4] user scripts], and features, helping communities with any technical issues, and documenting technical resources.

2.) Outreach includes workshops targeted towards newcomers, hackathons at regional and national levels, online workshops for Wikimedia communities, and mentoring/supporting Google Summer of Code and similar programs.

For technical support, we plan to take up the following activities:

Technical Requests: The technical requests page ([5]) has been well-received by the community in the past, but there is a decline in the number of requests we have been receiving in recent years. We intend to do more outreach to both the editor and developer communities to increase awareness about it and its usage so that, in the long term, more developers will be actively volunteering to address the requests posted on that page. We observe editors post it in the wishlist and developers picking from phabricator which are two different platforms. Editors cannot explain the issue in technical terms and provide the details requested in Phabricator due to limited knowledge, while developers cannot pick up a task without a proper description and context, which is available in the existing Phabricator tasks. Our community request page acted as a good bridge between both of them, and we plan to revive it.

Community Technical Task Force: 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 ([6]) with five communities to broadly understand the technical issues being faced. For the second iteration, the task force used this as a foundation and started conversations with 2 communities in the 2025 second quarter. Though the goal is to do these for at least three of the four quarters, the first iteration itself made it clear that the format we followed to do this didn't prove to be as effective as imagined. This approach involved prolonged back-and-forth communication to understand issues described in talk pages, attempts to replicate them independently, and coordination to record video demonstrations when replication was difficult almost every time. These recordings then had to be translated into English and documented on Phabricator with appropriate context. This became a burden and a time-consuming process for just two people in the task force.

To address these challenges, we plan to adopt a more scalable and structured model. Instead of limiting consultations to a small number of pre-selected communities, we will begin with broader online outreach. We will post invitations on multiple community talk pages across Indic Wikimedia projects, inviting interested communities to engage with us. Communities that express interest will be requested to nominate one or two point-of-contact volunteers and share a high-level overview of the technical challenges they are facing (e.g., issues related to tools, gadgets, bots, templates, workflows, or platform limitations). Based on these initial responses, we will assess feasibility, scope, and potential impact, and prioritize a smaller set of communities where we believe meaningful technical support can be provided within our capacity. For selected communities, we will create an instant messaging coordination channel including their point-of-contact volunteers and members of our technical task force and use this space to coordinate timings, clarify issues in real time, and schedule calls where necessary for live replication and recording of issues. Internally, responsibilities within the User Group will be distributed more evenly, and members will take turns coordinating discussions, attending and recording issue-replication sessions, translating and documenting issues, and filing or updating tasks on Phabricator or other relevant platforms. This will distribute workload across multiple members and help everyone get an understanding of the issues editors are facing.

GSoC & Outreachy mentorship: Wikimedia Foundation actively participates in Google Summer of Code and Outreachy programs. In the past, we have both proposed projects for potential applicants and mentored students during the technical development of the projects. We plan to propose and mentor at least one project for GSoC and Outreachy every year. In addition, we will coordinate with WMF to engage the GSoC & Outreachy participants from the region, to invite them to participate in our activities. 

For outreach, we plan to take up the following activities:

In 2024 ([7]), we collaborated with amFOSS ([8]), a student-run community with over 50+ members from Amrita Vishwa Vidyapeetham, Amritapuri. This has been very successful, as the students already had exposure contributing to open source projects, and it was easy to onboard them to Wikimedia projects and the technical ecosystem. Some of them continued contributing and were able to participate in further activities. We conducted a 30-hour non-stop hackathon, which was good, but it was also challenging. Choosing Tinkerspace saves budget as it's a free venue. In 2025, we expanded the scope, where we invited members from the entire FOSS community and had it as a semi-workshop and hackathon format. For the hackathon, we had potential tasks listed out along with the call for scholarship applications, rather than before the event. That list is used to ask applicants to indicate interest in contributing to one of them or propose a different task if they have. This ensured that all participants were clear about the work beforehand. Also, clearly marking what is expected to be achieved during the hackathon and post follow-up, if necessary. These pre-hackathon tasks helped to a great extent for the event to be successful and productive. In 2026, we plan to restructure the program into two mini-hackathons. 

Mini-hackathon with amFOSS: In the 2025 Kochi hackathon ([9]), there was a significant proportion of students from Amrita Vishwa Vidyapeetham as participants, along with students from other college FOSS clubs. After this event, we got feedback from the college saying that UG can use the college space for hosting a hackathon, so in 2026, the first mini-hackathon will be conducted at Amrita Vishwa Vidyapeetham in collaboration with amFOSS, primarily targeting students from the college, especially those already active in FOSS communities. We are planning this event in the college with Amrita students.

Mini-hackathon in Kochi (Tinkerspace) with FOSS clubs: The second mini-hackathon will be designed as an open community event, inviting participation from the broader FOSS and Wikimedia technical ecosystem, including students from multiple colleges and independent contributors. This format ensures diversity and that outreach is not limited to a single institution. Similar to the improved 2025 model, potential tasks will be shared in advance, and participants will be asked to indicate their interest or propose their own ideas. Clear expectations regarding deliverables during and after the event will be defined beforehand. 

Together, these two mini-hackathons create a structured contributor pipeline, and participants who demonstrate strong performance will move forward to a Developer Skill Development phase, where they will receive structured mentorship and guidance in preparation for the final hackathon.

Workshops similar to Small wiki toolkits: The user group in the past had experience with organizing lightweight technical workshops for editors focused on minor/beginner-friendly technical topics. We did an iteration of this in 2020 ([10]) and also in 2022 ([11]), both of which received a good response. Although the global SWT initiative is no longer active, we found these small 2-hr workshops on focused topics well received with the community. We resumed the SWT initiative for Indic languages, as more editors would be open to joining more regional and focused ones. We conducted small 2-hour workshops on beginner technical topics, such as templates, using the API, basics of user scripts, etc., to help editors understand technical spaces and if possible, help them with their contributions. We were able to organize 8 workshops ([12]) in 2025 as planned, but we faced some challenges with mentors and inactive participants. To make this efficient, in 2026, we are planning on identifying mentors at the start of the next iteration and making a list of topics they are proficient in. We would also like to collect topics from the audience to understand what kind of workshops they would want to participate in. With this, we will get a clear understanding of what workshops to host and whom to invite. Knowing these in advance will help make a clear schedule for SWT workshops throughout the year and organize them smoothly. We will share post-event recordings and learning resources with participants so that those who miss sessions or want to revisit concepts can continue learning. During live sessions, we will integrate interactive activities such as breakout discussions, live quizzes, structured Q&A segments, and guided exercises to increase real-time engagement. We also plan to incorporate structured activity formats that were previously implemented in our earlier calls and received an overwhelmingly positive response. These formats helped increase participation, reduce hesitation in asking questions, and improve overall session energy.

Introductory/Awareness Talks: Have an introductory workshop about the Wikimedia movement and the technical spaces at an educational institution or related FOSS meetups, such as FOSS-United meetups ([13]). The goal of these is not to be very outcome-oriented, but to keep them lightweight to create awareness about Wikimedia technical spaces, build networks, and tap into any potential opportunities for future years. We planned to do 2-3 of these during 2025, but could only manage one due to challenges with identifying colleges. Next year, we plan to select colleges as soon as possible, get some leads in advance, and finish awareness talks at 3 of them.

Developer Skill Development: In 2025, this program focused on mentoring newcomers to intermediate levels of technical contribution and beyond. Of the 30 people who started with the program, more than 20 successfully completed their tasks and projects (beyond good first tasks). This helps the developers to engage further in Wikimedia technical spaces, but also increase sustainability of the community as they train potential future mentors and contributors.

This workshop will be for about 15-20 existing developers (someone who contributed to a few good-first-tasks), to further improve and refine their skills to contribute to Wikimedia technical areas. For this, we will have an open for enrollment during the first quarter, for developers who already have been contributing to some or the other technical areas. For each participant, we will focus on two things, what can you share/teach & what do you want to learn/contribute to. For example, I know how to develop bots using PAWS and I want to learn about creating web-based tools. Based on the responses received, we will form groups for various learning areas, and provide resources. The resources can be in the form of a trainer from within the group, connecting with an external trainer, or even an online course if need be. We will be mindful of having it lightweight so that the participants can keep up with that along with their other commitments. After starting, this will continue online for 4-6 months depending on the number of people and topics. Towards the end of the program, we will have an in-person gathering to work on something that people have learned about, for example, if their goal was to learn about web tools, then that participant will be working on something related to that during the event. 

The 2025 iteration was successful and we got significant contributions to many projects, also many participants showed potential to become mentors for future hackathons and sessions. We were able to retain some of the interested candidates and make them a part of the user group for the next iteration. We plan to continue this event in 2026 as well because in the long-term this will solve the mentor scarcity problem which has become a big challenge for us.

Hackathons: We plan to organize only one major hackathon in 2026. This will be the culmination of all our activities. Unlike training workshops, only a little time (about 10-20%) is spent on sessions, and most of the time is spent on hacking. For this hackathon as well, we will have potential tasks listed out along with the call for scholarship applications, rather than before the event. That list will be used to ask applicants to indicate interest in contributing to one of them or propose a different task if they have. This will ensure that all participants are clear about the work beforehand. Also, clearly marking what is expected to be achieved during the hackathon and post follow-up if necessary. This year, we are doing one such hackathon towards the end of iteration i.e, between May to June. We plan to continue this year end hackathon in the same fashion for next year as well.

—

Apart from the above-mentioned, we have a few operational and miscellaneous considerations for next year's annual plan:

Expand the Working Group: Currently, the working group’s capacity is limited by the number of people available. As some of our core members are discontinuing from next year, we would like to expand the working group for the activities we are planning for next year. We will also have people sign up to support specific activities, rather than committing to an entire year. This will ensure we will have more organizing support, and also create opportunities for newcomers to exposure outreach.

Long-term strategy for the user group: Something we couldn’t do in 2024, but could lay the foundation for in 2026-27, is to create a longer-term strategy for the user group, with an outlook of at least three years. This will be crucial for the long-term sustainability of the user group and planning for leadership development. This will also include planning for a governance model of the user group.

Wikimania/Wikimedia Hackathon/Regional event scholarship support: Providing scholarship support for members of the technical community and the working group to attend the regional and global events. With the growing community, this will ensure that technical volunteers from India have an opportunity to connect with the rest of the community. 

9. What categories are your main programs and related activities under? Please select all that apply. (required)

Category	Yes/No
Education	Yes
Culture, heritage or GLAM	No
Gender and inclusion	No
Community support and engagement	Yes
Participation in campaigns and contests	Yes
Other	No

Education

9.1.1. Select all your programs and activities for Education. (required)

Wiki Club

Other programs and activities if any: N/A

9.1.2. Select all relevant audience groups for Education. (required)

Vocational, tertiary, or higher education

Other groups if any: N/A

Community support and engagement

9.4. Select all your programs and activities for Community support and engagement.

On-wiki training of community members, Organizing meetups, conferences, and community events, Supporting community members' participation in events and conferences

Other programs and activities if any: N/A

Participation in campaigns and contests

9.5. Select all campaigns that apply. (required)

Not applicable, Other

Other programs and activities if any: Wikimedia Hackathon

Wikimania Hackathon Satellite IndiaFOSS

10. Please include a link to or upload a timeline (operational calendar) for your programs and activities. (required)

added a pdf below

• IMD-UG_ 2026 Annual Plan Timeline - Sheet.pdf

11. Describe your team. (required)

The working group currently has the following members: 

Harigovind C B will lead program planning and workshop design.


Rihaan B H will support event organization and execution, along with technical development.


Navya will provide overall coordination support, planning, and strategic guidance, including coordination with relevant stakeholders.


Gauri Gupta will focus on social media communications and overall event strategy.


Vanshika Rathi will handle documentation and communications.


Parashar Sarthak will serve as the logistics coordinator, supporting logistics, finances, and budgeting.

All existing core group members will transition into advisory roles and will continue to provide strategic guidance and mentorship to the working group as advisors.

1. Jay Prakash
2. KC Velaga
3. Gopa Vasanth
4. Nivas

12. Will you be working with any internal (Wikimedia) or external partners? Describe the characteristics of these partnerships and bring a few examples of the most significant partnerships. (required)

Externally, we will be collaborating with amFOSS ([14]), a student-run community with over 50+ members from Amrita Vishwa Vidyapeetham, Amritapuri, over the last 15 years. The community is very engaged with open source contributions, and we have in the past organized multiple activities with them. The advantage they bring in is that they already have an existing system of open-source contributions and support from the institute, which we will benefit from.

Apart from this one, we are planning to increase the number of sustainable partnering organizations in India that can serve as potential hubs for recurring future contributors regularly. Here is a list of potential institutions we have in mind and will be reaching out to:

1. IIT Dharwaad
2. FOSS club at Delhi Technical Campus
3. Vasireddy Venkatadri Institute of Technology, etc

13. In what ways do you think your proposal most contributes to the Movement Strategy 2030 recommendations. Select all that apply. (required)

Increase the Sustainability of Our Movement, Improve User Experience, Invest in Skills and Leadership Development, Innovate in Free Knowledge, Evaluate, Iterate, and Adapt

Metrics

Wikimedia Metrics

14. Please select and fill out Wikimedia Metrics for your proposal. (recommended)

14.1. Number of participants, editors, and organizers.

All metrics provided are optional, please fill them out if they are aligned with your programs and activities.

Participants, editors, and organizers

Metrics name	Target	Description
Number of all participants	300	(target numbers by activity) Developer skill development workshops: 20*1 workshop = 20 Mini-hackathon  = 30*2 = 60 National hackathon: 40 Small wiki toolkits workshops = 10 * 8 workshops = 80  IndiaFOSS ~ 100 Introductory talks = 25 * 2 talks = 40
Number of all editors	N/A	N/A
Number of new editors	N/A
Number of retained editors	N/A
Number of all organizers	25	From this 25, 10 of them will be new organizers
Number of new organizers	10

14.2. Number of new content contributions to Wikimedia projects. (recommended)

Contributions to Wikimedia projects

Wikimedia project	Created	Edited or improved
Wikipedia
Wikimedia Commons
Wikidata
Wiktionary
Wikisource
Wikimedia Incubator
Translatewiki
MediaWiki
Wikiquote
Wikivoyage
Wikibooks
Wikiversity
Wikinews
Wikispecies
Wikifunctions / Abstract Wikipedia

Description for Wikimedia projects contributions metrics. (optional)

Other Metrics

15. Do you have other quantitative and qualitative targets for your project (other metrics)? (required)

Yes

Other Metrics	Description	Target
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.)	50
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.	15
N/A	N/A	N/A
N/A	N/A	N/A
N/A	N/A	N/A

Budget

16. Will you have any other revenue sources when implementing this proposal (e.g. other funding, membership contributions, donations)? (required)

No

16.1. List other revenue sources. (required)

N/A

16.2. Approximately how much revenue will you have from other sources in your local currency? (required)

N/A

17. Local currency

Indian Rupees (INR)

18. What is the requested amount in Indian Rupees? (required)

5976630 INR

Requested amount in USD

48268.76 USD

19. Does this proposal include compensation for staff or contractors? (required)

Yes

19.1. How many paid staff members and contractors do you plan to cover with this General Support Project? (required)

Operations & Logistics Coordinator: In the budget, we have included a part-time contractor to support operations and logistics of activities at an average of 10-15 hrs/week. In 2024, we realized that for organizing activities (both in person and online) a lot of the volunteer time available is being spent on coordinating logistics (such as travel). This compromised the planning of some of our activities and took time away from spending time on event programming. Having a logistics co-ordinator helped to a great extent and made things easy for us to execute all the programs planned in the timeline. The contractor worked with the event coordinators to take care of the logistics and support with communications, if needed. We wish to continue having a logistics coordinator for the next iteration as well. The current contractor will continue for the next year as well, and we plan to utilise them efficiently compared to the previous year.

Program Co-ordinator: In the budget, we included a part-time contractor to support the program and activities at an average of 15 hrs/week. This is going to help us keep the program on track with respect to the timeline. A lot of our time has gone to doing routine tasks required for the program (such as searching for mentors, adjusting schedules, searching for colleges, co-ordinating through mails etc.), which will become very easy once we have a program coordinator. Since we plan to do a bunch of planning activities at the start of the iteration for multiple programs, having a program coordinator is going to make it smoother. We plan to do an open call for applications and select someone who has a programmatic view of things and some experience/knowledge about the Wikimedia environment.

19.2. How many FTEs (full-time equivalents) in total will be covered with this General Support Project? (required)

None

19.3. Describe any staff or contractor changes compared to the current year / ongoing General Support Project if any. (required only for returning applicants)

In 2025, we hired a contractor for Logistics and Operations. We plan to continue with that and add one more co-ordinator for program support. So, there will be 2 contractors during this proposal period. 

20. Please provide an overview of your overall budget categories in your local currency. The budget breakdown should include only the amount requested with this General Support Project. (required)

Budget category	Amount in local currency
Staff and contractor costs	720000
Operational costs	219500
Programmatic costs	3322072

21. Please upload your budget for this proposal or indicate the link to it. (required)

[15]

Additional information

22. In this optional space you can add any other additional information about your proposal or organization that you think can help us when reviewing your proposal. (optional)

---

By submitting this proposal request you agree with the Institutional Partner Privacy Policy, Application Privacy Statements, WMF Friendly Space Policy and Universal Code of Conduct.

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 application. 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.