Grants:Programs/Wikimedia Community Fund/Rapid Fund/TermBox project (ID: 23553622)
Applicant details
[edit]- Main Wikimedia username. (required)
Plantaest
- 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.
TermBox project
- 2. and 3. Proposed start and end dates for the proposal.
2025-11-01 - 2026-01-30
- 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)
TermBox is a tool designed to support editors in the translation process. I would like to quote some information that was originally drafted on the Vietnamese Wikipedia (vi:Thành viên:Plantaest/TermBox), so that readers may better understand the goals of this tool:
During the process of translating articles on Wikipedia, a frequent need is the use of dictionaries to determine how to translate words from the source text, especially technical terms. This work is usually carried out by accessing external dictionaries, including both online and printed ones. Therefore, if there were a dictionary lookup tool integrated directly into Wikipedia's editing tools, it would provide editors with much greater convenience.
In addition, another related need is the consistency in the use of translations for technical terms. This is particularly important for members of specialized WikiProjects (such as biology, music, etc.) who wish to standardize the translation of specific terms. Since certain terms may have multiple possible translations depending on the context, creating a unified approach ensures accuracy and consistency within specialized fields, making it easier for later editors to inherit and continue the work. In such cases, project members may need to create a shared dictionary that establishes agreed-upon translations for their field. This can be seen as a form of community-driven dictionary, collaboratively built and maintained, drawing upon published sources, reference works, and collective discussion.
Furthermore, enabling users to contribute to building dictionaries can also support the development of lexicographical data in Wikidata for Vietnamese, which is currently very limited and in need of expansion. Building lexeme data for Vietnamese on Wikidata will help develop more advanced tools for operating Wiktionary in the future, and may even extend to Wikisource by enabling cross-references within historical dictionaries.
In summary, based on the needs of the Vietnamese Wikipedia community, TermBox will provide three core functions: (1) Allow users to create dictionaries, (2) Enable editors to look up terms during the translation of articles, (3) Facilitate the creation of lexeme data in Wikidata.
In terms of planning, the TermBox project is expected to be carried out over 3 months (approximately 90 days), divided into 3 phases:
Phase 1 (30 days): I will analyze and design the system, then begin developing the core back-end features to ensure that the data is structured properly and accessible through APIs.
Phase 2 (30 days): I will focus on the project's front-end – the part visible to users. TermBox will be presented as a tool embedded alongside editing interfaces such as Content Translation, Visual Editor, and Source Editor on Wikipedia. During this phase, I will implement the planned features, including dictionary creation, terminology lookup, and lexeme generation for Wikidata.
Phase 3 (30 days): I will release a trial version of the project for the community to test and provide feedback. In parallel, I will invest time in writing comprehensive documentation, while continuing to refine features and fix software bugs.
From a technological perspective, I will use Quarkus for the back-end and Vue/Codex for the front-end. The back-end will be deployed on Toolforge, while the front-end will be deployed on the wiki as a gadget.
- 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
I believe there are several measurable outcomes from this project, such as the number of dictionaries created by users, the number of terms contained within each dictionary, and the number of lexeme entries contributed to Wikidata through the tool. These data points can be collected from the software's database. However, it should be noted that such data can only be obtained once the project has been officially released and used by the community for a sufficient period of time.
Regarding "Milestones and progress tracking", I usually maintain a project log on Wikipedia, as this is a small-scale project carried out solely by myself. Nevertheless, if necessary, I will also provide progress updates and documentation on the project's GitHub repository.
- 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]
Initially, the TermBox project will be launched for the Vietnamese Wikipedia community, who are the primary users in need of this tool. I have already initiated a community discussion and received unanimous support. Please see the following page for reference: vi:Wikipedia:Thảo luận cộng đồng/Dự án TermBox.
- 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
I will comply with the security policies of the Wikimedia Foundation and relevant parties such as Toolforge throughout the implementation of this project.
I will make every effort to minimize technical security risks, including carefully reviewing the types of data stored by the tool, controlling access permissions, and securely handling sensitive information such as API keys in accordance with best practices.
- 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
I am the sole developer responsible for implementing this project.
Over the years, I have worked on numerous software projects, which can be found here: Viettech Initiative#Activities & Projects. Among them, three projects have been funded by the Wikimedia Foundation through the Rapid Fund program.
My GitHub profile: [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.
In the long term, the TermBox project will be handed over to the Viettech Initiative group for maintenance and further feature development. Any cost-related matters will also be managed by this group.
At present, I do not yet have a formal long-term plan for the project. However, the Viettech Initiative will take on this responsibility once I have completed the essential work of the project through this grant.
- 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 TermBox project will be released under the GNU Affero General Public License version 3 (AGPLv3).
Regarding documentation, I plan to dedicate significant time – approximately one month – to ensure that users can effectively utilize the tool and that interested developers are able to contribute to the source code. I believe that the guidelines on "Documentation plan" provided on Grants:Project/Rapid/Tech#Documentation are appropriate and will be followed.
- 11. Will your project depend on or contribute to third-party tools or services?
The TermBox project depends on the Toolforge infrastructure for its operation and contributes data to Wikidata through user activity.
- 12. Is there anything else you’d like to share about your project? (optional)
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)
130500000 VND
- 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.
4952.84 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.