doc: add message for Ambassadors to promote · nodejs/node@27b9cfd
@@ -165,3 +165,56 @@ Some of the things to highlight include:
165165#### Project contacts
166166167167* @mhdawson
168+169+### How things get done in the Node.js project
170+171+#### Goal
172+173+Help people understand that no people are paid to answer their issues or
174+implement their pull requests. Things get done based on what volunteers work on
175+and the best way to get something fixed/changed is to submit a Pull request.
176+177+Some of the things to highlight include:
178+179+* Nobody is paid specifically to answer issues, fix bugs or implement new features.
180+* No company owns/supports Node.js. Most contributions are from individuals
181+ as opposed to organizations. When an individual becomes a collaborator
182+ the access and priviledges are granted to the indidual, their employer does
183+ not gain any additional rights in the project.
184+* The governance of the project is specifically designed to prevent one or
185+ a small number of companies from dominating the project.
186+* Decisions are made by the active collaborators, there is no single person
187+ who makes a decision for the project on their own. This can slow down
188+ decision making but most often results in better outcomes.
189+* The project is open and receptive to contributions. If you need something PR
190+ in a fix or feature.
191+* Maintainers are people just like you, with many priorities and end goals. We
192+ all have the same goal of moving the Node.js project forward but at the same
193+ time we all have other responsibilities that affect how much time we have
194+ available to do so.
195+* People are volunteering their time to review your PRs and answer questions in
196+ the issues you open. Be mindfull of your asks for their time and acknowledge
197+ the gift of their time. Too many issues/PRs in a short period of time may
198+ overwelm maintainers leading to less progress versus more, try to pace your
199+ issues and PRs so that you don't have too many open at the same time. The
200+ same goes for comments in discussions, try to avoid overwelming a discussion
201+ with too many responses, even too much useful data can overwelm a discussion
202+ leading to lower engagement.
203+* While volunteers work to do the right thing for the community, the project
204+ does not owe anybody anything and does not tolerate abusive or
205+ demanding language in issues, discussions or PRs. A respectful dialog will
206+ maximize the chances of the outcome you desire.
207+* If you depend on timely support or an SLA, contract with a company that provides
208+ paid support and will prioritize your issues.
209+210+#### Related Links
211+212+* <https://github.com/nodejs/TSC/blob/main/TSC-Charter.md#section-3-establishment-of-the-tsc>
213+214+#### Project contacts
215+216+* @mcollina
217+* @mhdawson
218+* @marco-ippolito
219+220+You can find their contact email in the [`README.md`](../../README.md#tsc-technical-steering-committee)