This is an automatically generated Meta-Wiki page. The page was copied from Fluxx, the grantmaking web service of Wikimedia Foundation 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.
- Main Wikimedia username. (required)
Indic MediaWiki Developers User Group
- 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)
I'm a group leader of a Wikimedia User Group (submitted to the Affiliation Committee).
- Describe all relevant roles with the name of the group or organization and description of the role. (required)
Jayprakash12345, Nivas10798, Gopavasanth, and KCVelaga are the core working group members of the user group.
- 1. Please state the title of your proposal. This will also be the Meta-Wiki page title.
Indic Wikimedia Hackathon 2023
- 2. and 3. Proposed start and end dates for the proposal.
2023-09-01 - 2023-12-31
- 4. Where will this proposal be implemented? (required)
- 5. Are your activities part of a Wikimedia movement campaign, project, or event? If so, please select the relevant project or campaign. (required)
- 6. What is the change you are trying to bring? What are the main challenges or problems you are trying to solve? Describe this change or challenges, as well as main approaches to achieve it. (required)
Indic MediaWiki Developers User Group, initially started off as an informal group (https://w.wiki/VoX) with an effort to support the technical needs of Indic Wikimedia communities and later evolved as a user group and has been trying to expand by conducting workshops and hackathons and mentoring interested candidates along the way. In the past, the members of the User Group (both individually and combined) have done newcomers-focused activities which helped us to bring in a few more interested students and experienced non-tech volunteers to join us. With our current expertise and strength, we are aiming to achieve the following in the next six months.
- Bridge gap between technical contributors and language/theme-based contributors
- Expand the user group core team, Increase user group strength, and Improve retention of the existing members
- 7. What are the planned activities? (required) Please provide a list of main activities. You can also add a link to the public page for your project where details about your project can be found. Alternatively, you can upload a timeline document. When the activities include partnerships, include details about your partners and planned partnerships.
Onboard interim members and expand the user group: After the User Group has been formed, most of our activities have been focused on supporting existing Wikimedia communities (for example, training existing content contributors on technical areas to deal with basic to intermediate issues), and keeping the current contributors engaged with the movement through hackathons. Although these have been successful for their scope, we realized that there is a need to bring newcomers into the space in planning and continuing the user group. This will ensure the communities that leadership is maintained among all the volunteers and is not vested among one or few individuals. For this, we will be onboarding four community volunteers who have an understanding of Open source and are ideally familiar with tech and language projects. This will help us expand our user grap besides giving an edge to decentralize and conduct activities like hackathons and workshops in their locality in the future which will further help bring in new users to the movement.
Hackathon: We will be having a brief online session on Wikimedia technical spaces and how they can contribute to the movement. We are expecting to have 15-20 participants for the in-person hackathon, both experienced and newcomers. This will be a two-day activity, during which the first day we will be onboarding the participants to MediaWiki basics, Phabricator, Gerrit, Toolforge, and VPS, among others. Once participants get comfortable with these aspects, a pre-curated list which of outstanding tasks will be used to kickstart participants' contributions. This list will consist of tasks which are beginner friendly along with pain points of community members which will be collected through the community consultation process.
- 8. Describe your team. Please provide their roles, Wikimedia Usernames and other details. (required) Include more details of the team, including their roles, usernames, Wikimedia group, and whether they are salaried, volunteers, consultants/contractors, etc. Team members involved in the grant application need to be aware of their involvement in the project.
All the team members listed here will be participating here in their volunteer capacity. For the hackathon: On behalf of the User Group: User:Jayprakash12345, User:Gopavasanth will be leading the program, and User:Nivas10798 will be coordinating, and User:KCVelaga will be providing advisory support.
- 9. Who are the target participants and from which community? How will you engage participants before and during the activities? How will you follow up with participants after the activities? (required)
The target audience are
- Existing developers from Wikimedia communities
- Users with knowledge of technical issues and potential solutions, and
- Developers outside Wikimedia, but interested to contribute to MediaWiki and related areas (for example, students)
We will be having a small orientation session before the hackathon, and post the hackathon, we are planning to engage the participants through a working Phabricator board, and regular community meetups.
- 10. Does your project involve work with children or youth? (required)
- 10.1. Please provide a link to your Youth Safety Policy. (required) If the proposal indicates direct contact with children or youth, you are required to outline compliance with international and local laws for working with children and youth, and provide a youth safety policy aligned with these laws. Read more here.
- 11. How did you discuss the idea of your project with your community members and/or any relevant groups? Please describe steps taken and provide links to any on-wiki community discussion(s) about the proposal. (required) You need to inform the community and/or group, discuss the project with them, and involve them in planning this proposal. You also need to align the activities with other projects happening in the planned area of implementation to ensure collaboration within the community.
- 12. Does your proposal aim to work to bridge any of the content knowledge gaps (Knowledge Inequity)? Select one option that most apply to your work. (required)
- 13. Does your proposal include any of these areas or thematic focus? Select one option that most applies to your work. (required)
- 14. Will your work focus on involving participants from any underrepresented communities? Select one option that most apply to your work. (required)
Age (diversity of age groups)
- 15. In what ways do you think your proposal most contributes to the Movement Strategy 2030 recommendations. Select one that most applies. (required)
Innovate in Free Knowledge
Learning and metrics
- 17. What do you hope to learn from your work in this project or proposal? (required)
We intend to learn the following things from this activity
- organizing hackathons with a mix of existing developers and new developers interested to learn
- a buddy system during the hackathons
- working with potential FOSS groups
- 18. What are your Wikimedia project targets in numbers (metrics)? (required)
|Other Metrics||Target||Optional description|
|Number of participants||15|
|Number of editors||0||not applicable as this is a hackathon|
|Number of organizers||4|
|Wikimedia project||Number of content created or improved|
|Wikifunctions or Abtsract Wikipedia|
- Optional description for content contributions.
- 19. Do you have any other project targets in numbers (metrics)? (optional)
|Main Open Metrics||Description||Target|
|Number of tasks/bug fixes||While this highly depends on how things go during the hackathon, usually we observed this is a good number.||15|
- 20. What tools would you use to measure each metrics? Please refer to the guide for a list of tools. You can also write that you are not sure and need support. (required)
Phabricator, Github and Gitlab issues
- 21. Please upload your budget for this proposal or indicate the link to it. (required)
- 22. and 22.1. What is the amount you are requesting for this proposal? Please provide the amount in your local currency. (required)
- 22.2. 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.
- We/I have read the Application Privacy Statement, WMF Friendly Space Policy and Universal Code of Conduct.
Endorsements and Feedback
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).