Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add message for Ambassadors to promote #56235

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
+53 −0
Open

doc: add message for Ambassadors to promote #56235

Changes from 1 commit
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
0441d8e
doc: add message for Ambassadors to promote
mhdawson Dec 11, 2024
4cdc743
Update doc/contributing/advocacy-ambassador-program.md
mhdawson Dec 23, 2024
ccdf5f7
Update doc/contributing/advocacy-ambassador-program.md
mhdawson Dec 23, 2024
b878a3d
Update doc/contributing/advocacy-ambassador-program.md
mhdawson Dec 23, 2024
fd2dd58
Update doc/contributing/advocacy-ambassador-program.md
mhdawson Dec 23, 2024
b92538c
Update doc/contributing/advocacy-ambassador-program.md
mhdawson Dec 23, 2024
03b8b74
squash: address comments
mhdawson Dec 23, 2024
b9d966c
squash: make the linter happy
mhdawson Dec 23, 2024
6dc95fa
squash: address comments
mhdawson Dec 23, 2024
56a2697
squash: more fun with the linter
mhdawson Dec 23, 2024
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
43 changes: 43 additions & 0 deletions doc/contributing/advocacy-ambassador-program.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,3 +165,46 @@ Some of the things to highlight include:
#### Project contacts

* @mhdawson

### How things get done in the Node.js project

#### Goal

Help people understand that no people are paid to answer their issues or
implement their pull requests. Things get done based on what volunteers work on
and the best way to get something fixed/changed is to submit a Pull request.

Some of the things to highlight include:

* Nobody is paid specifically to answer issues or implement features.
mhdawson marked this conversation as resolved.
Show resolved Hide resolved
* No company owns/supports Node.js. Most contributions are from individuals
as opposed to organizations.
Copy link
Member

Choose a reason for hiding this comment

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

Perhaps worth expanding here: Even if a company does pay their employee to contribute to Node.js, all contributions are individual. Meaning, that once an individual receives a commit bit, that belongs to the individual and not the company. If they change employers their status does not change and granting the commit bit to the individual grants no rights in the project to the company. Just not sure how to say that succinctly.

Copy link
Member Author

Choose a reason for hiding this comment

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

@jasnell, thanks for the suggestion, added some words, let me know if that is what you had in mind.

* The governance of the project is specifically designed to prevent one or
a small number of companies from dominating the project.
* Decisions are made by the active collaborators, there is no single person
who makes a decision for the project on their own. This can slow down
decision making but most often results in better outcomes.
* The project is open and receptive to contributions. If you need something PR
in a fix or feature.
* Maintainers are people just like you, with many priorities and and goals. We
mhdawson marked this conversation as resolved.
Show resolved Hide resolved
all have the same goal of moving the Node.js project forward but at the same
time we all have other responsibilities that affect how much time we have
available to do so.
* People are volunteering their time to review your PRs and answer questions in
the issues you open. Be mindfull of your asks for their time and acknowledge
the gift of their time.
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if we should say something also about the importance of not overwhelming folks with too many issues/PRs in a short period of time, or about maintaining a good comment/response ratio in discussions. Otherwise well intentioned requests can easily become a burden if there's simply an overwhelming volume of things to look at and review.

Copy link
Member Author

Choose a reason for hiding this comment

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

@jasnell that is a good idea, will add some words to try to capture that.

Copy link
Member Author

Choose a reason for hiding this comment

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

added

* While volunteers work to do the right thing for the community, the project
does not owe anybody anything and does not tolerate abusive or
demanding language in issues, discussionis or PRs. A respectful diaglog will
mhdawson marked this conversation as resolved.
Show resolved Hide resolved
maximize the chances of the outcome you desire.
* If you depend on timely support or an SLA, contract with a company that provides
paid support and will prioritize your issues.
Copy link
Member

Choose a reason for hiding this comment

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

Unrelated but important: We should highlight who to contact if a company has a bug and actually needs a support contract.

Copy link
Member Author

@mhdawson mhdawson Dec 23, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

@mcollina I agree, but I think we should defer adding a list of companies that will provide support in a follow on PR as I think that might be a more complicated discussion.


#### Related Links

* <https://github.com/nodejs/TSC/blob/main/TSC-Charter.md#section-3-establishment-of-the-tsc>

#### Project contacts

* @mcollina
* @mhdawson
mhdawson marked this conversation as resolved.
Show resolved Hide resolved
mhdawson marked this conversation as resolved.
Show resolved Hide resolved
Loading