Document ONBOARDING process (also create onboarding process)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 606
- Forks
- 157
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
Refs: https://github.com/nodejs/LTS/pull/223/files#r127595396
It's probably time we tried to write down some more stuff about what happens if you join the team, especially now that it means joining the Release WG as well.
As an aside, (cc/ @MylesBorins) this will mean that we have to be somewhat more careful about adding new CitGM collaborators.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced LTS pull request discussion and reviewing how joining the team and Release WG currently works. Define what the onboarding process should cover, including the care needed when adding new CitGM collaborators. Done means the process is written down and the collaborator expectations are clear.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100