My daughter is fairly proficient in Python (only language she has been learning for a couple of years) and I'd love to get her to contribute to open source projects as a way to get real-world, team-collaboration exposure.<p>I thought I'd find open source mentorship programs online but to my surprise I found zero. I think young kids interested in CS majors will benefit from open source mentorship programs as a way to learn the craft and get real-world experience. I see so many college students reaching out for internships - instead, they should just contribute to open source!<p>Thoughts?
No offense, but you sound like one of those pushy parents. If she enjoys it then she'll figure it out on her own. Why does it need to be forced? I too was writing code at that age and managed on my own, all I needed was an Internet connection, a warm home, and food on the table.<p>Like other comments say, forcing it is a surefire way to kill any interest. And giving your daughter autonomy over her own learning is a very valuable lifeskill.
Does she want to do open source work? Great way to kill a kids interest is get overly involved in it.<p>If she's not interested you could alternatively offer some funding for hosting and other services to let her build something on her own.
The simplest way is to get her (if she isn't already) to use a free (and open source) program, and when she gets used to it, get her to build it from source and tinker around, see how it works and how it can be modified. Maybe get her to fix a bug and contribute the patch upstream - that could be a memorable experience.<p>Thankfully, a lot of free (and open source) software is written in Python, so the choice is wide.
Google summer of code, Linux Foundation, Mozilla have programmes for students.<p>There are also organisations like <a href="https://aossie.gitlab.io" rel="nofollow">https://aossie.gitlab.io</a> and fossasia.org<p>Also check out Python Foundation if they have programmes for students.<p>One organisation whose name slips my mind at the moment is from the US which helps school students collaborate on projects and even funds them to make that project into a business.
I'd ignore the question of the in-project mentor and suggest filtering projects based on their open source community style of governance and supporting foundation and look through their actual collaboration communications to make sure their style is right for a young entry level contributor.<p>From those she can look at what interests her and why first bugs list they have, etc.<p>If they are a properly in the open she doesn't really need their mentoring as opposed to mentor like interactions from you, or any other people who would have time to review and discuss with her the ticket progress, her changes, etc.<p>She could end up having more connection to the project and mentoring they provide but she may also find other projects that are more interesting to her and realize the project she started on isn't motivating. It is hard to bring a dependence on a mentor that is helping because of one project with you.
Check out <a href="https://opensource.guide/how-to-contribute/" rel="nofollow">https://opensource.guide/how-to-contribute/</a> as well. It's a general guide though, doesn't seem to have links for mentorship programs.