Here are the reports for Make GNOME Platforms demos for Workbench
Some rough notes on internships in general (sorry if it’s out of scope)
Project length variable is unclear. One of the student selected “medium” instead of “large” because they thought it would increase their chance of getting accepted. On the side of mentors, it took us too long to realize the project length wasn’t the same as for the other students.
Not all regions were represented in GSoC applicants. My impression is that some university networks are better informing/preparing students about it than others.
Overall, it was very smooth. Thank you, @felipeborges !
The split between GSoC / Outreachy seems unnecessary. Can we merge everything under the same umbrella on the GNOME side?
The whole show seems to be run by @felipeborges (thank you!). I can tell it’s a lot of work and Felipe has been asking for support. I think we should create a team/committee responsible for internships.
2 of our interns were already GNOME enthusiasts, one of them had never used Linux before.
I think there is room for improving the project ideas list. Curation, project length, requirements, etc and maybe even combine with Welcome to GNOME – Overview - I’d be happy to help.
Very few applications were good. It makes it easier to choose interns but I feel like we’re missing on a lot of potential. I think we should have some kit that we can send organizations on preparing students for internships at GNOME.
Outreachy bi-weekly emails are very useful and great guideline.
Outreachy review form is well-made, better than GSoC
We received too many not-so-great applications from Outreachy. Including rude applicants and AI generated PRs.
Mentors / developers are busy people who are probably doing this on their free time. Don’t be shy, go ahead, ask questions, make mistakes, learn, repeat, move forward. Seek help from the community too.
Consider co-mentoring. It was such a relief to have a backup when needed.
Don’t send endless wall of chat text to your students on how to do something, document it in your repo/wiki instead and send it to them.
If you have multiple mentors/interns, consider creating a private room with your student(s), at least at the beginning, so they have a safe space to ask questions.
A good contributing / getting started guide is absolutely necessary. Here is ours: https://github.com/sonnyp/Workbench/blob/main/CONTRIBUTING.md - consider the troubleshooting section too.
If you don’t have a “one command works for all” setup for your project, fix that before taking interns.