-
Notifications
You must be signed in to change notification settings - Fork 25
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.
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
Node.js Next 10 Years team Meeting 2022-10-26 #169
Comments
PR for minutes - #170 |
ovflowd
added a commit
to ovflowd/node
that referenced
this issue
Nov 1, 2022
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169
ovflowd
added a commit
to ovflowd/node
that referenced
this issue
Nov 6, 2022
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169
ovflowd
added a commit
to ovflowd/node
that referenced
this issue
Nov 6, 2022
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169
ovflowd
added a commit
to ovflowd/node
that referenced
this issue
Nov 6, 2022
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169
mhdawson
pushed a commit
to nodejs/node
that referenced
this issue
Nov 9, 2022
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169 PR-URL: #45270 Reviewed-By: Michael Dawson <[email protected]>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Nov 10, 2022
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169 PR-URL: #45270 Reviewed-By: Michael Dawson <[email protected]>
danielleadams
pushed a commit
to nodejs/node
that referenced
this issue
Dec 30, 2022
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169 PR-URL: #45270 Reviewed-By: Michael Dawson <[email protected]>
danielleadams
pushed a commit
to nodejs/node
that referenced
this issue
Dec 30, 2022
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169 PR-URL: #45270 Reviewed-By: Michael Dawson <[email protected]>
danielleadams
pushed a commit
to nodejs/node
that referenced
this issue
Jan 3, 2023
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169 PR-URL: #45270 Reviewed-By: Michael Dawson <[email protected]>
danielleadams
pushed a commit
to nodejs/node
that referenced
this issue
Jan 4, 2023
Introduces a proper imperative description of how the current API documentation build system works. Refs: nodejs/next-10#169 PR-URL: #45270 Reviewed-By: Michael Dawson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Time
UTC Wed 26-Oct-2022 14:00 (02:00 PM):
Or in your local time:
Links
Agenda
Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/next-10
Invited
*Next 10 years team: @nodejs/next-10
Observers/Guests
Notes
The agenda comes from issues labelled with
next-10-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
link for participants: https://zoom.us/j/99950131676
For those who just want to watch: We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled
The text was updated successfully, but these errors were encountered: