Jump to content

Grants:Programs/Wikimedia Community Fund/Rapid Fund/amFOSS Hackathon + IMD Working Group Meeting - 2023 (ID: 22022902)/Final Report

From Meta, a Wikimedia project coordination wiki
Rapid Fund Final Report

Report Status: Accepted

Due date: 15 September 2023

Funding program: Rapid Fund, Wikimedia Community Fund

Report type: Final

Application

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

General information

[edit]
  • Title of Proposal: amFOSS Hackathon + IMD Working Group Meeting - 2023
  • Username of Applicant: Nivas10798
  • Name of Organization: N/A
  • Amount awarded: 4966.38
  • Amount spent: 4853.89 USD, 403569.91 INR

Part 1 Understanding your work

[edit]

1. Briefly describe how your proposed activities and strategies were implemented

Two activities were proposed as part of the grant application. The first one was a Wikimedia hackathon at Amrita University. For this, we collaborated with the Free and Open Source Software (FOSS) club at the university, the amFOSS. The club has been active for several years and they organize frequent technical events. In the past, when our user group used to conduct hackathons, it was mostly outside an educational institute and we used to invite students from multiple institutes. But this experience has been very different. As the students of the club were already engaged in the open source movement, it had been very easy to motivate and onboard them to Wikimedia technical spaces. This model helped us realize a new model for organizing hackathons, which is to identify existing open-source communities and tap into their networks. The second activity, which is the User Group's working group meeting was conducted in person, which had been very helpful to brainstorm the goals of the user group, define key focus areas and planning a strategy.

2. Were there any strategies or approaches that you felt were effective in achieving your goals? Please describe these strategies and approaches.

We would like to acknowledge the Grants Committee's feedback during the proposal phase on reducing the training time and giving more space for hacking time during the event - it worked really well. Especially as the students were already contributors to other open source projects, they were onboarded to Wikimedia technical spaces very quickly. On Day 1, we introduced the statements to Wikimedia projects, different technical spaces such as tools, user scripts, bots, gadgets, MediaWIki, databases, and APIs. One thing that was helpful is that we allocated some after each topic for students to try it hands-on, for example, after introducing APIs, we ensured the students made a small API request to understand how it works. At the end of Day 1, students formed into various groups and continued working on projects until Day 3. We concluded with a project showcase.

For the user group meeting, we went through our past activities, reviewed what we went well, what could be improved and also what kind of activities do we want to continue further and what activities we might want to drop. We also reviewed and defined our areas work, which gave us more clarity what we were really trying to achieve.

3. Please use this space to upload media and other files that help tell your story and impact.


Field to type in URLs.

https://meta.wikimedia.org/wiki/Wikimedia_-_amFOSS_Hackathon https://etherpad.wikimedia.org/p/amFOSS_x_MediaWiki_2023

Projects worked upon during the hackathon:

4. To what extent do you agree with the following statements regarding the work carried out with the support of this Fund? You can choose “not applicable” if your work does not relate to these goals.

Our efforts during the Fund period have helped to...
A. Bring in participants from underrepresented groups Agree
B. Create a more inclusive and connected culture in our community Strongly agree
C. Develop content about underrepresented topics/groups Neither agree nor disagree
D. Develop content from underrepresented perspectives Neither agree nor disagree
E. Encourage the retention of editors Neither agree nor disagree
F. Encourage the retention of organizers Strongly agree

5. Is there anything else you would like to share about how your efforts helped to bring in participants and/or build out content, particularly for underrepresented groups?

As this is a hackathon, these questions around content may not be very relevant for us. However, some of the projects that we worked on included tools for projects like Wikisource, which support underrepresented content.

Part 2: Your main learning

[edit]

6. In your application, you outlined your learning priorities. What did you learn about these areas during this period?

With hackathon, we learned that organizing hackathons with communities that already contributing to FOSS projects would be very effective in long-term retention. Having said that, it is important to continue hackathons of various kinds - with students, existing content contributors on wikis, and mix of both.

Our main learning and outcomes are reflected in our annual plan: https://meta.wikimedia.org/wiki/Grants:Programs/Wikimedia_Community_Fund/General_Support_Fund/Indic_MediaWiki_Developers_UG_2024_Annual_Plan

7. Did anything unexpected or surprising happen when implementing your activities?This can include both positive and negative situations. What did you learn from those experiences?

n/a

8. How do you hope to use this learning? For instance, do you have any new priorities, ideas for activities, or goals for the future?

We will be incorporating our learnings into the annual plan we are forming.

9. Documentation of resources: Use this space to upload any documents that would be useful to share with others (e.g. communications material, training material, presentations).


Here is an additional field to type in URLs.

N/A

Part 3: Metrics

[edit]

10a. Open Metrics reporting

In your application, you defined some open metrics and targets (goals). You will see a table like the one below with your metric in the title and the target you set in your proposal automatically filled in. Use the tables to report the result. Use the comments column to describe any aspects of this result that you find relevant. If the results were different from the initial target (goals) then you can explain why and what you learned from this. You can also provide any qualitative analysis regarding these results. In the last column please describe the tools and methodology used to collect this data and any difficulties you might have had.

Open Metrics Summary
Open Metrics Description Target Results Comments Methodology
Progress on technical tasks For a hackathon, it is hard to set a target the output, the key idea is learning and awareness of technical spaces for newcomers. However, we would like to target a few outstanding issues. 10 22 N/A Wikimedia Phabricator
Development of annual plan Our main work from the working group meeting is to bring planned structure into our activities. We will be publishing a plan on Meta-Wiki 1 1 https://meta.wikimedia.org/wiki/Grants:Programs/Wikimedia_Community_Fund/General_Support_Fund/Indic_MediaWiki_Developers_UG_2024_Annual_Plan N/A
N/A N/A N/A N/A N/A N/A
N/A N/A N/A N/A N/A N/A
N/A N/A N/A N/A N/A N/A

10b. Core Metrics reporting

In your application, you defined targets for some core metrics and targets (goals). You will see a table like the one below with each core metric in the title and the target you set in your proposal automatically filled in. Use the tables to report the result. Use the comments column to describe any aspects of this result that you find relevant. If the results were different from the initial target (goals) then you can explain why and what you learned from this. You can also provide any qualitative analysis regarding these results. In the last column please describe the tools and methodology used to collect this data and any difficulties you might have had. Note: a table will appear for each Wikimedia project content contribution you defined in your proposal.

Core Metrics Summary
Core metrics Description Target Results Comments Methodology
Number of participants 25 30
Number of editors
Number of organizers 5 6 three from the usergroup and three from the amFOSS club
Number of new content contributions per Wikimedia project
Wikimedia Project Description Target Results Comments Methodology
N/A N/A N/A N/A N/A N/A
N/A N/A N/A N/A N/A N/A
N/A N/A N/A N/A N/A N/A
N/A N/A N/A N/A N/A N/A
N/A N/A N/A N/A N/A N/A

12. Did you have any difficulties collecting data to measure your results? This could include things like a lack of time or resources, or the expertise in your team to collect this data. It could also include difficulties with particular data collection tools.

No

12a. State what difficulties you had.

N/A

12b. How do you hope to overcome these challenges in the future? Do you have any recommendations for the Foundation to support you in addressing these challenges?

N/A

13. Use this space to upload any documents and provide links to any tools you have used that would be useful to understand your data collection (e.g., surveys you have carried out, communications material, training material, program and event dashboard link, project page on Meta).


Here is an additional field to type in URLs.

N/A

14. Have you shared these results with other Wikimedian communities (either affiliates, user groups, volunteers, etc., different to yours)? This can include things such as data and direct outcomes, lessons you have learned, or information on how to run or recreate your programs.

Yes

14a. If yes or partially, please describe how you have already shared them and if you would like to do more sharing, and if so how.


Part 4: Financial reporting and compliance

[edit]

15. & 14a. Please state the total amount spent in your local currency.

403569.91 INR

16. Please state the total amount spent in USD.

4853.89 USD

17. Please report the funds received and spending in the currency of your fund.

17a. Upload a financial report file.

17b. Please provide a link to your financial reporting document.

N/A

As required in the fund agreement, please report any deviations from your fund proposal here. Note that, among other things, any changes must be consistent with our WMF mission, must be for charitable purposes as defined in the grant agreement, and must otherwise comply with the grant agreement.

17c. If you have not already done so in your budget report, please provide information on changes in the budget in relation to your original proposal.

N/A

18. Do you have any unspent funds from the Fund?

Yes

18a. Please list the amount and currency you did not use and explain why.

INR 538.09, approximately USD 6.47 is underspent.

18b. What are you planning to do with the underspent funds?

B. Propose to use them to partially or fully fund a new/future grant request with PO approval

18c. Please provide details of hope to spend these funds.

The underspend is minimal, we can use them with the annual plan

19. Are you in compliance with the terms outlined in the fund agreement?

Yes

20. Are you in compliance with all applicable laws and regulations as outlined in the grant agreement?

Yes

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

22. If you have additional recommendations or reflections that don’t fit into the above sections, please write them here.


Other documents