#133 Creating summer coding "best practices" docs for mentors
Closed: Stale 2 years ago Opened 3 years ago by jflory7.

[ to be completed later ]


  • Have onboarding guidelines for selected applicants
  • Introduce social communication channels for students.
  • Do research + Use existing documents from other open source communities. eg. Metabrainz has a private communication channel for discussions between mentors
  • Highlight work of selected applicants on Commblog.

[BEFORE UPCOMING OUTREACHY GSOC]

Is this something we want to target for the 2018 Documentation FAD? If yes, we should have a quick discussion in our meeting to brainstorm purpose and objectives like @bee2502 started.

Metadata Update from @jflory7:
- Issue tagged with: GSoC, docs, meeting, needs feedback

3 years ago

Discussed in 2018-02-19 meeting.

Not reinventing the wheel

@skamath shared a comprehensive GSoC mentoring manual by FLOSS Manuals (sponsored by Google). Collectively, we thought it was a helpful resource and should promote it better among Fedora mentors.

Instead of writing our own guide, we thought the best approach is to refer all general advice on mentoring to this manual, and then create a smaller guide that covers Fedora-specific details for mentors (e.g. our own communication places, tools, and/or procedures).

Also, see: How to work with students?

Docs FAD?

We thought this could be a good topic for the Docs FAD. I solicited feedback if this was a good task to bring to the FAD on their mailing list.

Metadata Update from @jflory7:
- Issue untagged with: needs feedback
- Issue assigned to jflory7
- Issue priority set to: critical (next week) (was: no deadline)
- Issue tagged with: FAD

3 years ago

Metadata Update from @jflory7:
- Issue untagged with: meeting
- Issue priority set to: normal (1-2 weeks) (was: critical (next week))

3 years ago

Metadata Update from @jflory7:
- Issue priority set to: no deadline (was: normal (1-2 weeks))
- Issue set to the milestone: Future releases (was: Fedora 28 (to May 2018))

3 years ago

Metadata Update from @jflory7:
- Assignee reset

3 years ago

What if we emailed all mentors from this past cycle and asked them to share their three tips for best practices as mentors? We could try to solicit this feedback to improve the process, but someone would need to drive the conversion of this feedback into the mentored-projects documentation.

cc: @bex @bee2502 @labbott @sumantrom @a2batic @jonatoni

Alternatively, if we cannot find someone to drive this work, I suggest we close the ticket as moved to mentored-projects#13.

Metadata Update from @jflory7:
- Issue priority set to: normal (1-2 weeks) (was: no deadline)
- Issue set to the milestone: Fedora 29 (to Oct. 2018) (was: Future releases)

2 years ago

Metadata Update from @jflory7:
- Issue untagged with: type - FAD

2 years ago

Metadata Update from @jflory7:
- Issue tagged with: next meeting

2 years ago

Discussed in 2018-09-03 meeting.


This ticket will remain open for one more week to find help of someone to write new documentation on Google Summer of Code mentor / student best practices from past mentor feedback. If someone is interested in doing this with or without guidance, please add a comment to this ticket!

Otherwise, we will close this ticket and point to the upstream ticket, mentored-projects#13.

Metadata Update from @jflory7:
- Issue untagged with: next meeting
- Issue tagged with: help wanted

2 years ago

Closing this ticket as stale. :clapper:

Metadata Update from @jflory7:
- Issue untagged with: help wanted
- Issue close_status updated to: Stale
- Issue priority set to: waiting on assignee (was: next meeting)
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata