Org Admin Tasks to prep for 2020 (discussed at GSoC Mentor Summit '19)
Dr-G opened this issue · 1 comments
Dr-G commented
Make sure we have a directory of mentors & their sub-orgsdirectory of sub orgs on homepage- @Dr-G to read thru full NF GSoC repo and make edits for language
Make sure repo points to NF Code of Conduct#327- Hold a call in February to get all sub-org mentors on the same page about the 2020 program, i.e. - outreach efforts (diversity especially), answer questions about how NF is approaching the process and our internal requirements for students, take ideas from mentors, etc. [This is absolutely required to be done]
- Discuss whether to hold a session for prospective students, "Intro to GSoC with NumFOCUS" with best practices for applicants; tie to diversity outreach efforts (could be a Twitter chat?)
- Student mailing list? (linking all students under the NF umbrella)
- Find opportunities for students to present their work (i.e. at PyData meetups or conferences, at the conference of their project such as JuliaCon)
- Emphasize that students should communicate with mentors in open channels rather than private messages/emails, to integrate them more into the community and help retain them after the program (also good to get them used to the culture of "work open")
- Make sure that regular project contributors know that the project is participating in GSoC, in advance
- Should we have any meetings of ALL NF umbrella students together? (e.g. - once during the bonding period to have questions answered, once at the end for students to do lightning talks on their work)
- Update example student applications in the NF repo (make sure we have strong examples from the many sub-orgs/projects)
- Sub-org mentors should help us to clearly define prerequisite domain knowledge for their projects (e.g. "students should have taken at least two core classes in Economics in addition to experience programming in Python")
- Ensure mentors are up to date and on board with helping Org Admins to keep students on-track with their responsibilities (e.g. blog posts)