nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2025-11-02 19:18:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update operations-manual.md

Browse Source
This commit is contained in:
Yoni Goldberg
2018-09-15 17:48:07 +03:00
committed by GitHub
parent d2cfc0dd96
commit dafaf80d8f
1 changed files with 12 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
.operations/operations-manual.md
View File

@ -4,18 +4,20 @@ Building a community and knowledge by efficiently handling issues
## Handling issues and PR
<br/>
In a nutshell, every issue and PR should get tagged by one of our core team and routed to the person who specializes in the related topic. This person then, will warmly welcome and kick the discussion shortly (hopefully within 48 hours). The goal of each issue/pr is to learn, improve and join the opener to our forces.
In a nutshell, every issue and PR should get tagged by one of our core team and routed to the person who specializes in the related topic. This person then, will warmly welcome and kick the discussion shortly (hopefully within 48 hours). The goal of each issue/PR is to learn new thing that might improve our repo and try joining the opener to our forces.
We count on our core team to visit almost everyday and route inquiries - this way the workflow is not depend upon any specific person rather on our entire team.
There is no specific person on call who assigns inquiries rather we count on our core team to visit almost everyday and assign issues/PR - this way, the workflow is not depend upon any specific person rather on our entire team.
Any new content should conform to our writing guidelines
Any new content should conform to our (writing guidelines)[https://github.com/i0natan/nodebestpractices/blob/master/.operations/writing-guidelines.md]
## Monthly maintenance
<br/>
On every month a maintainer on call will open an issue for maintenance work and record within all the actions to perform by the end of the month (e.g. assign flower to a contributor). On the end of the corresponding month, the maintainer will run the following checklist
Each month, a maintainer on call will open an issue for maintenance work and record within all the actions to perform by the end of the month (e.g. assign flower to a contributor). On the end of the corresponding month, the maintainer will run the following checklist
Maintainer on call: @someone
---
**Maintainer on call**: @someone
**Updates**
@ -32,6 +34,9 @@ Maintainer on call: @someone
- @someone1
**Core Team**
- @someone1
--
| Month | Maintainer on call |
|---------|--------------------|
@ -56,11 +61,11 @@ Maintainer on call: @someone
|--------------------------|-----------------------------------------------------|------------------------------------|
| Code standards and fixes | Code typos, code standards, examples refinements | Bruno |
| Translations | Adding new language, merging language PRs | Monthly rotation October - Yoni |
| General Writing quality | Typos, text clarift | Bruno |
| General Writing quality | Typos, text clarify | Bruno |
| Javascript runtime | JS runtime, syntax correctness | Sagir |
| Devops | Monitoring, hardening a production site, deployment | Kyle |
| Architetecture | Project structure, microservices | Yoni |
| Testing | CI, linting, testing | Yoni |
| Performance | Efficient code, inspecting processes on fire | Sagir |
| Security | Security packages, secured code | Kyle |
| General inquires | Ideas, requests to contribute, etc | Monthly rotation October - Bruno |
| General inquires | Ideas, requests to contribute, etc | Monthly rotation October - Bruno |