-
-
Notifications
You must be signed in to change notification settings - Fork 27
doc: add minutes for meeting 14 May 2025 #346
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,56 @@ | ||
| # Node.js Next 10 Years team Meeting 2025-05-14 | ||
|
|
||
| ## Links | ||
|
|
||
| * **Recording**: <https://www.youtube.com/watch?v=acpc60ZNXJk> | ||
| * **GitHub Issue**: <https://github.com/nodejs/next-10/issues/345> | ||
|
|
||
| ## Present | ||
|
|
||
| * Michael Dawson (Red Hat) | ||
| * Marco Ippolito | ||
| * Zach Tanner | ||
| * Jacob Smith | ||
| * Erick Wendel | ||
|
|
||
| ## Agenda | ||
|
|
||
| ## Announcements | ||
|
|
||
| * No announcement this week | ||
|
|
||
| * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. | ||
|
|
||
| ### nodejs/next-10 | ||
|
|
||
| * Funding for Node.js project - status updates [#335](https://github.com/nodejs/next-10/issues/335) | ||
| * stalled for now | ||
|
|
||
| * 2025 Survey [#330](https://github.com/nodejs/next-10/issues/330) | ||
| * Marco - survey online, 1300 respondents so far. | ||
| * Agreement it will become banner to help promote | ||
|
|
||
| * Set of base question for collaborators [#329](https://github.com/nodejs/next-10/issues/329) | ||
| * had some questions back to Jean, waiting on that. | ||
|
|
||
| * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) | ||
| * no update | ||
|
|
||
| * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) | ||
| * no update this week | ||
|
|
||
| * Ambassador program | ||
| * Erick | ||
| * Some ideas monthly live streams | ||
| * Have been trying to talk to other Ambassadors | ||
| * Personally have been doing a number of things on Youtube | ||
| * Discussion around doing a livestream on something like a monthly basis | ||
| * Erick to propose program | ||
|
|
||
| ## Q&A, Other | ||
|
|
||
| ## Upcoming Meetings | ||
|
|
||
| * **Node.js Project Calendar**: <https://nodejs.org/calendar> | ||
|
|
||
| Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR I could find is nodejs/nodejs.org#7726. I don't see a subsequent one that makes it a banner nor chatter about making it one. Should we poke the website team?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not just badge because we decide that v18 EoL was more important