Call for Summer of Code mentors 2022! #10728
Description
Hi all 👋
We have applied to GSoC and we have been accepted to Outreachy 🎉 . We are hereby looking for folks interested in mentoring both or either of these programs, this coming summer. We have been participating in both programs for a several years now.
Outreachy internship period this year is 30th May - 26th Aug-- full timeline
GSoC internship period is 20th May - 12th Sept-- full timeline
N/B: both programs are allowing for an extension of the internship period this round
Last year's proposals for Outreachy are here and for GSoC here
We especially welcome people from groups underrepresented in free and open source software!
It's very important to us to have diverse representation in our mentor group just as in our participant group. And remember -- our community aspires to be a respectful place. Please read and abide by our Code of Conduct
We are calling for individuals who would like to be mentors for this round.
Projects:
Here is the list of potential projects for the summer round(additions are ongoing)
And here is the discussion issue for this summer's projects
To participate as a mentor:
We're asking for mentors that have taken some of the following steps to be part of our community:
- Solve a first-timers issue. Provide the link to the first timer issue's pull request (PR) once it's merged. In case, you are not able to find any first-timer issue, solve issue marked as
fto-candidateorsupport, these issues may require little more work, but we'll try to help. - Solve a help-wanted issue. Help wanted issues are issues which are neither labelled as
fto-candidatenor asfirst-timer-only. Provide link to such issues' merged PR.(Make sure you claim the issue first by commenting on issue you are planning to solve) - Make a first-timers issue. Use the extra friendly template which we generally use for creating our first timer issues. Provide the link to the first timer issue which is created by you.
What do mentors do:
Mentors check in with a student at least once per week roughly from May-Sept(refer to exact timeline above), and offer some project management guidance and encouragement... while relying on the chatroom and the
reviewers group to provide code-specific input, so that we share the burden of specific technical support. We have weekly Check-Ins on GitHub (#9600) as well, and mentors are expected (along with students!) to be in the rotation to post these occasionally.
Remember that to be a mentor you don't necessarily need to know how to code -- we also need mentors who know Public Lab's community and practices well, and who can encourage students to speak up when they get stuck, and to ask the community for input and testing of their work. Students often get stuck when they don't know how something should look, or how a feature might be used by the community -- contextual info!
If you're interested in being a mentor, please leave a comment here, fill in this form and read over our software outreach resources to get an idea of how we work!
Helpful resources on mentoring:
- Summer of Code workflow
- Extra notes on our approach
- Different ways to mentor -- we need various types!
- Outreachy Mentor guide
- What reviewers do day-to-day on Public Lab code projects
- Our commitment to modularity, very important in how we ask contributors to work
- Check out our growing list of software outreach strategies
cc: @publiclab/mentors @publiclab/reviewers
Many thanks and appreciation to mentors of the past year
🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟
@RuthNjeri @jywarren @pydevsg @divyabaid16 @noi5e @SidharthBansal @gautamig54 @TildaDares @Tlazypanda @coderjolly @namangupta01 @keshavsethi @grvsachdeva
🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟 🌟
We are happy to answer questions, please leave a comment below if any!