Skip to content

Add blog post publishing guidelines #7860

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add blog post publishing guidelines #7860

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 9 additions & 0 deletions GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,3 +88,12 @@ As seen above, the different teams under the Node.js Web Team umbrella are respo
Following this line of thought, the Web Infra Team is responsible for the technical aspects of the Node.js Website (Infrastructure, Framework, CI/CD, etc); The Website Team is responsible for the day-to-day development of the Node.js Website; The UX and Design Team advise on Design Matters and the Web Standards Team advise on best-practices for Web APIs and Web Technologies/Standards.

But above all, the Web Team should work together to better the Web Experience for Node.js, aiming to provide the best experience for Node.js users.

## Blog post publishing guidelines

The following guidelines apply to all blog posts except minor or patch release announcements:

1. each blog post _must_ have a target publishing date and time. If scheduled publishing is not possible, _the author_ (if privileged enough) or another delegated member would be responsible for landing.
2. each blog post _must_ be approved by @nodejs/tsc members _and_ OpenJS Foundation marketing staff.
Copy link
Member

Choose a reason for hiding this comment

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

If we can pull together a nodejs/marketing team that has members from both the TSC and the foundation marketing staff, would it be enough here to say that the nodejs/marketing team must approve it... then that team can work out whatever process makes the most sense to it.

Copy link
Collaborator

Choose a reason for hiding this comment

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

does https://github.com/orgs/nodejs/teams/social suffice?

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 if both the TSC and OpenJS staff are members of the team, technically the TSC could approve this without asking them. This has a different meaning.

Copy link
Member

Choose a reason for hiding this comment

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

Fair. If the new @nodejs/marketing team, then, is made up of Foundation marketing staff, I agree that requiring an approval from at least one person in both the @nodejs/tsc and @nodejs/marketing teams is ideal.

Copy link
Member

@joyeecheung joyeecheung Jun 23, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

Suggested change
2. each blog post _must_ be approved by @nodejs/tsc members _and_ OpenJS Foundation marketing staff.
2. the pull requests adding or changing blog posts should notify @nodejs/tsc and @nodejs/marketing for reviews. In addition, reviews can be requested from teams with corresponding expertise.
- Release announcements: `@nodejs/releasers`
- Website: `@nodejs/website`
- Security: `@nodejs/security`
If there are no change requests and at least two approvals from the reviewing teams, after 48 hours on business days, the blog post is considered approved. If there is only one approval, the blog post needs to wait for at least 7 days. If the blog post needs to be fast tracked, a comment should be posted to request fast track, at least two thumbs up from the reviewing teams to the fast track request are needed to approve the blog post.

Copy link
Member

@jasnell jasnell Jun 24, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

I'm strongly -1 on having an automatic approval after any period of time. Explicit approval should be required.

Copy link
Member

Choose a reason for hiding this comment

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

If there are no change requests and at least two approvals from the reviewing teams,

I think this is clear enough to indicate that the blog post needs at least two approvals from the reviewing teams?


For minor/patch release announcements, the members of `@nodejs/releasers` can land as they see fit.
Loading