Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions proposals/collaborator-mentor-program.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
# Node.js collaborator-track mentee

The number of mentors is limited, and of those, their capacity is also limited. Collaborator numbers are also down. We need to focus on contributors who we see potential to become collaborators.

## The process:

1. A collaborator can privately nominate an active contributor for mentorship (similar to collaborator status nomination, perhaps in the same repo's discussion board).
1. The nomination remains open until either the nomination is blocked or the contributor is accepted by a mentor.

Mentors, their chosen/stated capacity, and their active mentees are tracked privately. This is helpful when deciding whether to nominate a contributor for mentorship (ex if there is already sigificantly more demand than supply).

## Expectations & responsibilities

### Mentor

* Is a collaborator.
* Is reasonably available to guide their mentee.
* Helps find suitable places to contribute.
* Nominates their mentee for collaborator status when they meet the criteria
* nominating a mentee for collaborator status would carry more weight (a mentee is a known talent).
Comment on lines +19 to +20
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this should be a direct consequence.
It would otherwise not feel good in case a nomination would not happen.

Suggested change
* Nominates their mentee for collaborator status when they meet the criteria
* nominating a mentee for collaborator status would carry more weight (a mentee is a known talent).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would happen regardless, no?


A mentor should check in with a mentee who they haven't heard from in a while, but it's not a requirement.

### Mentee

* Checks in.
* A mentee who is MIA (without forewarning) for 3 or more months (baring mitigating circumstances) is dropped and ineligible for the programme for 6 months.
* May withdraw without penalty.
* Makes the contributions.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Collaborators
Collaborators should try not to perform easy tasks (issue/bug/bad condition in an if ...) but more tot ping the mentors who are able to give this task to the right person.
The aim of this is to give mentees simple tasks to familiarize them with the code base. Because often the simple tasks have to be opened within 2 hours by someone with experience.

Example: nodejs/node#56717

I'm not blaming Marco ✨

### Both

* Decide (up front) check-in cadence and level of interaction.
* Can of course be adjusted later; better to have it explicit for a mutual understand.