Add meeting notes for Node.js Web Team on 2026-03-16 (#115)

* Add meeting notes for Node.js Web Team on 2026-03-16

* Apply suggestion from @Copilot

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Copilot: Whitespace removal

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Matt Cowley <me@mattcowley.co.uk>

Author: 4 people

meetings/2026-03-16.md

@@ -0,0 +1,43 @@
+# Node.js Web Team Meeting 2026-03-16
+
+## Links
+
+* **GitHub Issue**: https://github.com/nodejs/web-team/issues/111
+
+## Present
+
+* Aviv Keller @avivkeller
+* Brian Muenzenmeyer @bmuenzenmeyer
+
+## Agenda
+
+## Announcements
+
+* Extracted from **web-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
+
+### nodejs/web-team
+
+* Update our policies on relevancy [#98](https://github.com/nodejs/web-team/issues/98)
+    * Aviv, we should write this "unspoken rule" down
+        * Brian, +1, we should limit PRs to "atomic" changes, that is, changes that can be easily rolled back.
+* Require secondary approval for fast-track [#97](https://github.com/nodejs/web-team/issues/97)
+    * Brian, in the event of an emergency, this will go out the window, but in other cases, oversight is important.
+
+### nodejs/doc-kit
+
+* Monorepo? [#681](https://github.com/nodejs/doc-kit/issues/681)
+    * Aviv, consumers don't need to download _all_ deps for a single generator
+        * Brian, +1
+
+## Q&A, Other
+
+* i18n
+    * Brian, TSC vetoed, any changes will need to be escalated to them
+    * Aviv, why would a given user visit `/[lang]/` if the _content_ isn't in their `[lang]`
+
+
+## Upcoming Meetings
+
+* **Node.js Project Calendar**: <https://nodejs.org/calendar>
+
+Click `Add to Google Calendar` at the bottom left to add to your own Google calendar.