Outreachy/Round 28
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
Wikimedia took part as a mentoring organization for Outreachy Round 28.
Program timeline
edit(borrowed from https://www.outreachy.org/apply/project-selection/)
January 15, 2024 at 16:00 UTC | Initial applications open |
January 29, 2024 at 16:00 UTC | Initial application deadline |
March 1, 2024 | Project list finalized |
March 4, 2024 to April 2, 2024 | Contribute to projects |
April 2, 2024 at 16:00 UTC | Final Application Deadline |
May 1, 2024 at 16:00 UTC | Accepted interns announced |
May 27, 2024 to August 23, 2024 | Internship period |
Gallery
edit-
Outreachy and GSoC Welcome Session (online) - June 5, 2024
-
Final group picture of our Outreachy Round 28 interns and Google Summer of Code (GSoC) contributors 2024, August 2024
Selected projects
editName | Pronouns | Location | Project | Mentor(s) | Blog Posts | Weekly Updates |
---|---|---|---|---|---|---|
James Okolie | He/him/his | Nigeria | [1] Create tool for informative infographics from structured information from Wikimedia projects | |||
Mahima Agarwal | She/her/hers | Uttarakhand, India | [2] Build a data visualization tool for the evolution of Wikipedia articles maintained by WikiProjects |
Recommended steps for accepted interns
editContact
edit- Outreachy Administrators: Deb Tankersley and Sheila Karuku
- Reach out for general questions on the #gsoc24-outreachy28 Zulip chat (preferred), after reading Outreach programs/Zulip.
- Read how to communicate effectively and get help on technical questions.
We encourage applicants to communicate in the public streams and refrain from sending private emails/messages whenever possible. Open communication allows fellow applicants to learn from your questions. It also gives all community members a chance to answer your queries. This way, queries get answered sooner and the administrators do not become a bottleneck. Also see our communication tips.