Grants:Programs/Wikimedia Community Fund/Rapid Fund/Adiutor Maintenance (ID: 23536312)
Applicant details
[edit]- Main Wikimedia username. (required)
Doğu
- Organization
N/A
- If you are a group or organization leader, board member, president, executive director, or staff member at any Wikimedia group, affiliate, or Wikimedia Foundation, you are required to self-identify and present all roles. (required)
N/A
- Describe all relevant roles with the name of the group or organization and description of the role. (required)
Main proposal
[edit]- 1. State the title of your proposal. This will also be the Meta-Wiki page title.
Adiutor Maintenance
- 2. and 3. Proposed start and end dates for the proposal.
2025-10-01 - 2026-02-10
- 4. What is your tech project about, and how do you plan to build the product?
Include the following points in your answer:
- Project goal and problem you solve
- Product strategy or project roadmap
- Technical approach (infrastructure, tech stack, key tools and services)
- Integrations or dependencies (if any)
The goal of this project is to refactor Adiutor to modern ES6 standards, migrate it to a modular architecture with single-click installation, enforce Wikimedia’s JavaScript coding conventions (e.g. wikimedia-eslint rules), and provide ongoing maintenance so it remains usable and sustainable across multiple Wikipedias.
Problem:
Adiutor is currently unmaintained. Its outdated JavaScript structure makes it harder for communities to adapt or extend. Without maintenance, new communities cannot benefit.
Strategy / Roadmap:
- Refactor the existing codebase to ES6 and a modular structure.
- Build a single-click deployment system to simplify installation across Wikipedias.
- Update documentation and create a migration guide for local adaptations.
- Pilot deployment on Turkish, Uzbek, and Azerbaijani Wikipedias.
- Release the updated version and support additional interested communities.
Technical approach:
MediaWiki Gadgets framework, ES6 modules, OOUI, ResourceLoader.
Dependencies:
None outside MediaWiki core gadget system.
- 5. What is the expected impact of your project, and how will you measure success?
Include the following points in your answer:
- Milestones and progress tracking
- Project impact and success metrics
Milestones:
- Codebase refactored to ES6 and aligned with Wikimedia’s coding conventions (wikimedia-eslint).
- Modular architecture with single-click setup implemented and tested.
- Documentation and migration guide published, pilots completed on at least 3 Wikipedias.
- Public release, announcement, and onboarding support for additional communities.
Metrics:
- Number of Wikipedias adopting the updated Adiutor (target: 3-5).
- Completion of GitHub milestones for refactor, modularization, and documentation (target: 100%).
- Number of active maintainers or contributors engaged after release (target: 2+).
- 6. Who is your target audience, and how have you confirmed there is demand for this project? How did you engage with the Wikimedia community?
Include the following points in your answer:
- Project demand and target audience description
- Links to interaction(s) with Wikimedia community
- Evidence from community consultation such as the [Community Wishlist]
Target audience:
Wikipedia editors and administrators who perform routine maintenance tasks, such as AfD, speedy deletions, revision deletions, and user blocking.
Demand confirmation:
Adiutor is actively deployed and used in 10 communities, including:
- Azerbaijani Wikipedia
- Georgian Wikipedia
- Turkish Wikipedia
- Wikimedia Commons
These communities have expressed continued need for the tool but currently lack dedicated maintainers.
Community consultation:
Feedback and adoption discussions have taken place during Wikimedia CEE events, in Telegram groups, and on on-wiki feedback pages. The previous Multilingual Adiutor for Wikipedias Rapid Fund (2023) also provided a foundation and demonstrated proven demand.
- 7. How will your team predict and manage potential user security and privacy risks, and what risks do you currently see?
Include the following points in your answer:
- The level of in-house or consulted security and privacy expertise you will have available to you during delivery of this project
- How your development, testing, and deployment processes mitigate the introduction of unnecessary security or privacy risks
The gadget does not handle personal data beyond what MediaWiki already exposes, makes no external API calls except to Wikimedia-hosted services, follows Wikimedia security best practices for developers, and will be tested in sandboxes and pilot wikis before production rollout.
- 8. Who is on your team, and what is your experience?
Include the following points in your answer:
- Your experience as a developer, relevant past projects
- Wikimedia SUL (developer), Gerrit, Github, Gitlab or other relevant public account handles
- Other team members, their roles and expertise
Doğu is the primary maintainer and developer, with experience as a MediaWiki contributor, Wikimedia gadget developer, and the original author of the Adiutor gadget.
GitHub: [1]
- 9. How will the project be maintained long-term?
Include the long-term maintenance plan with maintainer(s) in your answer. If you expect the long-term maintenance to incur expenses, please list those and the plan for long-term expense coverage.
The repository is already hosted under the wikimedia-gadgets organization on GitHub, maintenance will be shared with interested community developers, the modular design and clear documentation will help reduce technical debt, and while this refactor should reduce the need for additional funding, future Rapid Fund requests may be considered if substantial new development or maintenance is required.
- 10. Under what license will your code be released, and how will you ensure the product is well documented?
Include the following points in your answer:
- Code license and compatibility with Wikimedia projects
- Documentation plan
The code is licensed under CC BY-SA 4.0 and GNU FDL, consistent with the original Adiutor and fully compatible with OSI requirements, and documentation will be updated on Meta (Adiutor), complemented by code comments in the ES6 modules and a migration guide for other Wikipedias.
- 11. Will your project depend on or contribute to third-party tools or services?
No. Only MediaWiki infrastructure (gadgets, ResourceLoader, OOUI).
- 12. Is there anything else you’d like to share about your project? (optional)
Adiutor has proven community demand and is already deployed on 8+ Wikipedias. Without maintenance, the tool risks being abandoned. This project ensures sustainability and modernization.
Budget
[edit]- 13. Upload your budget for this proposal or indicate the link to it. (required)
- 14. and 15. What is the amount you are requesting for this proposal? Please provide the amount in your local currency. (required)
490000 RSD
- 16. Convert the amount requested into USD using the Oanda converter. This is done only to help you assess the USD equivalent of the requested amount. Your request should be between 500 - 5,000 USD.
4882.78 USD
- We/I have read the Application Privacy Statement, WMF Friendly Space Policy and Universal Code of Conduct.
Yes
Endorsements and Feedback
[edit]Please add endorsements and feedback to the grant discussion page only. Endorsements added here will be removed automatically.
Community members are invited to share meaningful feedback on the proposal and include reasons why they endorse the proposal. Consider the following:
- Stating why the proposal is important for the communities involved and why they think the strategies chosen will achieve the results that are expected.
- Highlighting any aspects they think are particularly well developed: for instance, the strategies and activities proposed, the levels of community engagement, outreach to underrepresented groups, addressing knowledge gaps, partnerships, the overall budget and learning and evaluation section of the proposal, etc.
- Highlighting if the proposal focuses on any interesting research, learning or innovation, etc. Also if it builds on learning from past proposals developed by the individual or organization, or other Wikimedia communities.
- Analyzing if the proposal is going to contribute in any way to important developments around specific Wikimedia projects or Movement Strategy.
- Analysing if the proposal is coherent in terms of the objectives, strategies, budget, and expected results (metrics).
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.