This is a TODO list that I took during the onboarding of legendcas. Opening an issue in case I forget about them - but feel free to pick them up if you are interested to help!
[ ] It’s not necessary to explain everything in the on boarding document. The person doing the onboarding can ask whether the collaborator already knows about each point and skip if they already do. If they have questions, answer them.
[ ] Mention the new 7 day rule, or just add a link to the collaborator guide about the rules
[ ] Mention other commonly used CIs
[ ] micro benchmark
[ ] v8
[ ] custom e.g. internet
[ ] stress test
[ ] citgm
[ ] Mention how to get a git ref to use in the Jenkins build parameters
[ ] The what belongs in Node.js seems a bit outdated? In general we just open issues and discuss on a case-by-case basis
[ ] Mention the travis CI
[ ] Mention the resume build button and the stop button in Jenkins
[ ] Mention how to report issues to the build team: with the machine id
[ ] TODO(joyee): Update node-core-utils recording, and just add a link to the recording to quickly demonstrate how to use it
[ ] Add the github-bot and node-core-utils repo to the "other repos" links, and explain what those are
[ ] Mention the Collboarator github team discussion page
[ ] Mention how security bugs are handled (or a link to SECURITY.md)
[ ] Mention that collaborators can nominate other collaborators (and add a link to GOVERNANCE.md)
This is a TODO list that I took during the onboarding of legendcas. Opening an issue in case I forget about them - but feel free to pick them up if you are interested to help!
git remote set-url origin --push no_push
what belongs in Node.js
seems a bit outdated? In general we just open issues and discuss on a case-by-case basis