Skip to content
Open
Changes from all commits
Commits
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
74 changes: 74 additions & 0 deletions meetings/2026-07-06.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,74 @@
# Node.js Web Team Meeting 2026-07-06

## Links

* GitHub Issue: <https://github.com/nodejs/web-team/issues/150>

## Present

* Brian Muenzenmeyer @bmuenzenmeyer
* Matt Cowley @MattIPv4

### Observers/Guests

_None._

## Agenda

### Announcements

_No announcements._

### Issues and Pull Requests

Extracted from **web-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.

#### nodejs/nodejs.org

* Define how partners should be ranked [#8995](https://github.com/nodejs/nodejs.org/issues/8995)
* https://nodejs.org/en/about/partners
* Reference: https://github.com/nodejs/nodejs.org/blob/main/apps/site/public/static/partners/constants.json
* Brian could not find anything regarding historic precedence.
* Agreement from Matt that this needs to get written down.
* Do the categories equate to weights? Can some algorithm derive this?
* Should we split `infrastructure` into perhaps 3 - distribution, build, website (in order)
* Why do we have `security` and `ESP`? https://github.com/nodejs/nodejs.org/blob/main/apps/site/types/partners.ts#L32C2-L32C3

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

That was because, at first, we were going to include the companies that provided developers for the security patches (for the blog), and they were also going to be mentioned in the release. But due to legal concerns, it never happened because there were no agreements in place.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

👍 I'll get a PR open to remove these to avoid confusion

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

* Security category is missing entirely from https://github.com/nodejs/nodejs.org/blob/main/docs/partners.md
* Proposal (weights out of 10):
* (Delete) Security
* (Delete) Release
* (4) ESP
* (10) Distribution
* (6) Web site
* (8) Build
Comment on lines +37 to +43

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Let's get foundation + tsc sign off

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeh definitely, I'll follow up on the issue in a bit with the web-admins recommendation, and then get TSC + Foundation involved to seek consensus.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

* ensure weight and logo display is driven off of the above
* How is https://nodejs.org/en/download derived?
* Some partners don't even have a category https://github.com/nodejs/nodejs.org/blob/main/apps/site/public/static/partners/constants.json#L63
* Some partners (especially website), are missing... like Sentry, Crowdin, Chromatic, etc.
* How should we relate to https://github.com/nodejs/build#infrastructure-providers


#### nodejs/doc-kit

* ci: adopt Changesets for versioning and publishing [#855](https://github.com/nodejs/doc-kit/pull/855)
* Verbal discussion: agreement that this is better than what we have today (no git tags, no GitHub Releases, no CHANGELOG.md)
* chore(monorepo): break out generators [#778](https://github.com/nodejs/doc-kit/pull/778)
* wait for other maintainer input

#### nodejs/node

* build, doc: move to redesign [#62045](https://github.com/nodejs/node/pull/62045)
* special mention of proposal to add beta docs to the website proper https://github.com/nodejs/nodejs.org/pull/8998
* current blocker is all page OOM

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

That blocker's been resolved (finally!). New blocker: CI is generating invalid JSX, but I can't reproduce.

* this was removed from tsc-agenda. why?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Removed b/c a few members of the TSC previously decided that they wanted the all.html file to remain, so I worked around the issue by gating the all page

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Ah cool, I don't think we'd seen that update when we looked at the PR.

* Render "About this documentation" as the landing page for the documentation section [#60667](https://github.com/nodejs/node/issues/60667)
* https://nodejs.org/docs/latest/api/documentation.html is not the same as https://beta.docs.nodejs.org/documentation.html
* Concatenated stability index

## Q&A, Other

## Upcoming Meetings

* **Calendar**: <https://nodejs.org/calendar>

Click `Add to Google Calendar` at the bottom left to add to your own Google calendar.
Loading