Create a new Mindshare Docs page with recommendations / steps to follow when on-boarding a new cohort of Fedora Mentored Project interns
Some time ago, we started a tradition of running interviews with new interns working on Fedora. This has always been a volunteer-led task (to my knowledge). This year, we did a new post to welcome GSoC 2020 interns, but it excludes the four Outreachy interns selected by Fedora.
In previous years, we introduced and interviewed all interns for all programs. So, what changed? Simply someone else took on this responsibility with little guidance or documentation from their predecessor ( :arrow_right: :sweat_smile: :arrow_left: ). So, instead of accidentally excluding people, we should document a process that avoids accidental exclusion.
The short-term fix is writing a new article for Outreachy 2020 interns. But I want this ticket to focus at the root problem, which is, why did this happen in the first place?
I think a long-term fix is publishing a new Fedora Doc page with best practices about Mentored Projects on-boarding practices, and publish it. It does not need to be "complete" or "done" to close out this issue, but publishing a first draft makes it easier to extend and expand by a community.
Avoid accidental exclusion by documenting the best practices and approaches on how we on-board new contributors for Mentored Projects
In this comment, with Mindshare, I mean Mindshare: Mentored project representative
Mindshare: Mentored project representative
This process is to enable summer coding participants to communicate with the community
Within two weeks of announcing accepted students (by GSoC and Outreachy committee), Mindshare coordinates with mentors, students, and general mentors to publish intern introduction blog posts on the community blog for the respective programs.
Mentors ensure that Students are posting a post every 2-3 weeks once the coding period starts. (Can we use fedocal to set reminder and send an email to the summer-coding/outreachy list? - needs discussion) The post should ideally contain
Summer coding showcase session in Flock/One of the monthly Council calls
Post coding period, Mindshare to publish a magazine post with:
@sumantrom @riecatnor @jflory7: does the above look good?
@siddharthvipul1 seems good to me :) +1
@siddharthvipul1: Summer coding showcase session in Flock/One of the monthly Council calls
Presenting projects in a more personalized way to the Council is a creative idea. I'm all for it. Everything else gets a +1 from me too!
this is updated on the PR that will change the landing page of https://docs.fedoraproject.org/en-US/mentored-projects/gsoc/2020/
Link to PR: https://pagure.io/mentored-projects/pull-request/83
Metadata Update from @siddharthvipul1: - Issue close_status updated to: Complete - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.