This guide only covers Mathesar-specific processes and guidelines. For a more general overview of what mentorship entails, please read the Google Summer of Code Mentor Guide.
Mentoring programs are usually structured into the following stages:
- Preparing project ideas
- Applying for the mentoring program
- Accepting contributions from applicants
- Reviewing proposals from applicants
- Choosing mentees
- Planning with mentees
- Working with mentees
We need a list of potential project ideas that applicants can submit a proposal to implement.
Project ideas should be:
- a self-contained feature or improvement for Mathesar
- scoped so that a single person can reasonably implement it in the timeframe of the mentoring program
- For GSoC, this is either 350 hours or 175 hours
- not time-sensitive or critical (there is no guarantee that the project will ship)
- compatible with our existing product roadmap
Once you’ve come up with a project idea, please:
- Flesh it out using our Project Idea Template.
- Add it to the Project Ideas page.
If you’re wondering if your project idea makes sense, discuss it on Matrix with other team members first before writing it down.
See also: The “Defining a Project (Ideas List)” page of the GSoC mentor guide
Once we have fleshed our our project ideas, Kriti will submit Mathesar’s application to the mentoring program. While we wait to hear back, you should:
- create a set of
good first issue tasks suitable for first-time contributors to the codebase.
- mentally prepare to deal with increased communication work.
Once the mentoring program (e.g. Google) announces the organizations participating in the program, potential applicants will start communicating with us. This stage of the program is the most intense.
- welcome new contributors and help them get started with:
- applicant information
- local project setup
- finding issues to contribute to
- review PRs quickly
- answer questions about the project ideas and the product.
- Point people to public channels and away from email and DMs so that others can answer questions too.
- You may get low effort questions like “how do I get started?”. Don’t try to guess what people mean, ask for more specific questions.
- In general, the effort involved in helping someone should be proportional to the effort they put in.
- If you find yourself answering the same questions often, update the relevant documentation so you can point people to it instead.
- Do not give individual applicants information about competing applications (e.g. how many proposals we got for a particular project idea).
Applicants will start working on draft proposals and sharing them with you a few weeks before the deadline. You are responsible for reviewing all proposals for which you are the primary mentor.
- track draft proposals and review status in our our internal spreadsheet
- ask applicants to submit draft proposals directly to you via Matrix and add them to the spreadsheet when you get them.
- review proposals in 1-2 days if possible.
- ask for review from other team members if you think it would be useful.
- Reviewing involves leaving comments on the proposal to help the applicant improve the proposal before final submission.
- Review comments should focus on finding problems with the proposal, not suggesting specific solutions.
- Comments should mostly be in the form of:
- Questions about something unclear.
- 1-2 sentence explanations about why something doesn’t make sense.
- 1-2 sentence statements describing what’s missing in a section.
- Suggestions for areas of the codebase to contribute code to (to strengthen confidence in the proposal).
- Questions to ask yourself during review:
- Does the applicant understand the project idea?
- Is the implementation plan:
- technically feasible?
- technically desirable?
- Is the implementation timeline realistic (including time needed to learn new skills and get familiar with the codebase?
- Does the timeline include concrete deliverables?
- Has the applicant thought through design and UX issues?
- Are the applicant’s code contributions strong enough that you feel confident that they can follow through on their plan?
After the final proposals are in, you’ll meet with the rest of the Mathesar team and decide which proposals are strong enough to accept.
This is an internal decision, we do not communicate with applicants about their proposals at this point.
During this period, you should:
- finalize mentorship for each project
- alk to co-mentors to create a plan for how to collaborate on each project, e.g.
- Will one of you be the primary mentor or will all of you be equally involved?
- How will checkins and notes be shared?
At this point,
- We’ve decided which applications to accept
- The mentoring program has approved our selection
- The accepted mentees have been announced
- Reach out to your mentee ASAP and welcome them to the project.
- Have an introductory call with the mentee and get to know each other.
- Ask them questions about themselves and talk about yourself too.
- Ensure that the mentee is added to our Team Members and has the correct GitHub and wiki permissions.
¶ Finalizing the project plan and workflow
Before work on the project gets underway, you should:
- collaborate with your mentee to finalize the implementation details and weekly deliverables for the project
- create a document to keep any project information and notes, include:
- an up-to-date implementation plan and weekly milestones
- the mentee’s contact information and emergency contact
- all meeting notes
- any other project-relevant information.
- share the project document with co-mentors and the organization admin
- set up regular meetings:
- a weekly video call for the mentors to check-in with the mentee
- a monthly call with the Mathesar organization admin to check in with the mentee.
- decide with the mentee on the workflow the project will follow. e.g.
- Does the mentee understand regular git workflow (e.g. pull requests, branches, reviews)?
- Does the mentee understand the code review process?
- How often should code be committed?
- How often should your mentee give you progress reports?
- What is the best way for the mentee to get your attention when they are stuck?
You’re now ready to mentor!
- Take good notes so that your backup mentor can pick up where you left off easily if you’re unavailable.
- Make sure the mentee is on-track with their weekly milestones and if not, work with them to figure out why and come up with a plan.
- Ask how the mentee is doing generally.
- Praise things they are doing well and provide constructive criticism on the things they could improve on. Both of these are important.
- Review all work/code promptly. You should aim to review within 1 business day.
- If your mentee is blocked on their work for some other reason, help them become unblocked as soon as possible.
- Check in on Matrix with the mentee once every day or two.
- Remember that mentees are inexperienced and may not know they are stuck, when to ask for help, and/or how to articulate problems well.
- Submit your required program evaluations on time.
- Ask for feedback on your mentorship every few weeks.
- Your mentee might like to present their work at a CCI research meeting and get some feedback. It’s up to you to facilitate this.
Talk to the program coordinator proactively if you’re not sure what to do. Some things to pay attention to:
- Your mentee is not active and engaged regularly.
- Your mentee is not communicating enough or misses a check-in.
- You have concerns or even just a bad feeling about something.
- You have feedback or questions about any part of the program process.
- You’d like feedback about how your mentoring is going