#210 [RFC] New Mindshare charge: Mentored Projects
Closed: Complete 3 years ago by riecatnor. Opened 3 years ago by jflory7.

Summary

Merge responsibilities of Summer Coding SIG / Mentored Projects into Mindshare Committee

Background

The Summer Coding SIG was founded over a decade ago. But its membership, decision-making, and how to join is not clear. There are no public meetings. The listed places for SIG discussion are mailing lists and IRC, where we encourage students to network with the community.

In my Fedora experience, Summer Coding facilitation and management is juggled by whoever has the passion, motivation, and obligation to work on it. The lack of a defined process indicates fragile support for this work to happen more transparently or openly in the community.

To improve Summer Coding facilitation, I believe we need clear leadership and ownership of these responsibilities in a documented, chartered way. I see the Mindshare Committee as best equipped for this responsibility in the context of the Fedora orgchart.

Details

This ticket is an exploration of merging Summer Coding SIG responsibilities into Mindshare. In my mind, this means the Mindshare Committee (collectively) is responsible for managing and facilitating Fedora's participation in Mentored Project organizations like GSoC or Outreachy.

Merging these responsibilities into Mindshare reduces complexity and confusion. To briefly summarize how things work now:

  1. Outreachy:
    • Technically managed by the Fedora D&I Team, except that is really only for budget approval because the Council determined Outreachy was best expensed on D&I Team budget
    • @labbott or maybe now @riecatnor actually facilitates the harder work as an Outreachy org admin
  2. GSoC:
    • Technically managed by a SIG, but I think it was really that @sumantrom raised his hand first for the work and he convinced @siddharthvipul1 to lend a hand too :smile:
    • Originally it was @bex to some degree before, but what degree that responsibility falls onto the FCAIC position (and thus @riecatnor now) is unknown

This is really confusing! So, I think Mindshare is a better home for this important and valuable work.

Outcome

  • Less work is duplicated for Mentored Projects
  • Easier to avoid accidental exclusion like in #209

@jflory7 Thank you so much for filing the ticket, I completely agree with the points above. I have been actively doing the GSoC OAs and GCI since sometime with Bex and now Vipul. It's a good idea,if we can start owning up the SIG. I am +1 to this.

@jflory7
I have had this thought and have also discussed this with Sumantro but was always short on coming to a conclusion on what should be done
Thank you for the idea
My vote doesn't count, but it's a +1

I'm +1 to this. I think both GSoC and Outreachy would benefit from continuing to work closer to avoid duplication of effort. I'd love to see all potential intern projects submitted by, say, DevConf in January and then have all reviewed to see what projects make sense to go for Outreachy vs GSoC.

facilitation and management is juggled by whoever has the passion, motivation, and obligation to work on it. The lack of a defined process indicates fragile support for this work to happen more transparently or openly in the community.

To improve Summer Coding facilitation, I believe we need clear leadership and ownership of these responsibilities in a documented, chartered way.

I'm +1 and this is the KEY
Regards.,

+1!

Update this page to add Summer Coding:
https://docs.fedoraproject.org/en-US/mindshare-committee/teams/

Update this page to add Outreachy:
https://docs.fedoraproject.org/en-US/mentored-projects/gsoc/2020/

Create a new seat on the committee for a point of contact for summer coding

Document any tasks related to summer coding, such as the intro interviews/posts.

Metadata Update from @riecatnor:
- Issue close_status updated to: Complete
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata