-
Notifications
You must be signed in to change notification settings - Fork 134
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
doc: add minutes for meeting 24 Apr 2024 #1539
Merged
Merged
Changes from 1 commit
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 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,118 @@ | ||
| # Node.js Technical Steering Committee (TSC) Meeting 2024-04-24 | ||
|
|
||
| ## Links | ||
|
|
||
| * **Recording**: <https://www.youtube.com/watch?v=l0K4MYF5nZA> | ||
| * **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1535> | ||
|
|
||
| ## Present | ||
|
|
||
| * Antoine du Hamel @aduh95 (voting member) | ||
| * Yagiz Nizipli @anonrig (voting member) | ||
| * Benjamin Gruenbaum @benjamingr (voting member) | ||
| * Ruben Bridgewater @BridgeAR (voting member) | ||
| * Joyee Cheung @joyeecheung (voting member) | ||
| * Chengzhong Wu @legendecas (voting member) | ||
| * Matteo Collina @mcollina (voting member) | ||
| * Michael Dawson @mhdawson (voting member) | ||
| * Moshe Atlow @MoLow (voting member) | ||
| * Rafael Gonzaga @RafaelGSS (voting member) | ||
| * Richard Lau @richardlau (voting member) | ||
| * Robert Nagy @ronag (voting member) | ||
| * Ruy Adorno @ruyadorno (voting member) | ||
| * Paolo Insogna @ShogunPanda (voting member) | ||
| * Michaël Zasso @targos (voting member) | ||
| * Rich Trott @Trott (regular member) | ||
|
|
||
| ## Agenda | ||
|
|
||
| ### Announcements | ||
|
|
||
| * Next major (22) release is in progress today. | ||
|
|
||
| ### CPC and Board Meeting Updates | ||
|
|
||
| *Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. | ||
|
|
||
| * No updates this week | ||
|
|
||
| ### nodejs/node | ||
|
|
||
| * lib,src: remove --experimental-policy [#52583](https://github.com/nodejs/node/pull/52583) | ||
| * Was added as an FYI for awareness, proposal is to remove it. | ||
| * Of the 13 TSC members in the meeting, there were no concerns. Richard mentioned that | ||
| we should doc deprecate as soon as possible. | ||
| * was doc deprecated in <https://github.com/nodejs/node/pull/52602> based on the suggestion | ||
| * Also going to be discussed in next security-wg as there had been some interest from the | ||
| Microsoft in terms of the feature. | ||
|
|
||
| * tools: change inactive limit to 9 months [#52459](https://github.com/nodejs/node/pull/52459) | ||
| * Yagiz - want to explain reasoning, originally was towards security. But realized that main | ||
| motivation is not security but something else. In reality the bar to stay as an active | ||
| collaborator is very low, committing one commit or reviewing one commit. So easy to | ||
| extend. This gives the false view that Node.js has lots of maintainers, also gives false | ||
| view of what kind of support people can expect. It is easy to come back from Emeritus. | ||
| * Pushing now for 9 months to see where the TSC stands | ||
| * As Michael mentioned, concern may be that life events may make the 9 months too short | ||
| * Benjamin, if security is the issue, other approaches such as limiting who really needs commit | ||
| bit versus removing collaborators | ||
| * Benjamin, In terms of the view of collaborators, reviews are most important to me, so making | ||
| sure we can retain maximum reviews may push against removing people | ||
| * Joyee, if we want to depend only on commit queue, we need people maintaining the commit | ||
| queue it is not stable enough to depend on. | ||
| * Matteo: Is the ability to run jenkins is it tied to the commit bit or the ability to write to the repo | ||
| * Richard, today there is a group which determines both write access and ability to launch CI | ||
| runs | ||
| * For request CI, it would be based on the same team | ||
| * Joyee, either you are a contributor or not. So if you are off having a kid, etc. Should not really | ||
| factor in whether you feel included etc. You have already opted out. If contributing to Node.js is still part of your life, you won’t be able to refrain yourself from doing at least one review, one commit in that year. | ||
| * Benjamin, getting reviews is already hard, keeping people as collaborators I think will help | ||
| getting reviews | ||
| * Joyee, can still ping subsystem teams | ||
| * Benjamin, there are some areas where we are thin on people, chance of getting a review is a | ||
| lot better while they are still part of the project. | ||
| * Yagiz, to summarize we have 100 collaborators, if become inactive move to emeritus. Home | ||
| page advertises that it’s not. Don’t think 12 months is right, also don’t think 9 months is right. | ||
| Is it fair to other collaborators to make it appear that people are contributing when they are | ||
| not? | ||
| * Benjamin, what if we keep the duration, but increase the requirement the amount of work | ||
| * Ruy, reminds people about conversations in the past. There are people who contribute in | ||
| many areas but never get to be core collaborators | ||
| * Matteo, going to propose an experiment. We list the number of people that have passed the | ||
| 9 month barrier (as well as 6 month, etc in terms of what people want to propose) and at the | ||
| mark of 12 we see how many of them have returned, then we will have actionable data to | ||
| work on. | ||
| * Benjamin, what if we ask people after 6 months, and automatically remove after 12 | ||
| * Yagiz, have been a TSC member for a year, and a collaborator a year before that. Don’t remember | ||
| a person to come back. 2 or 3 weeks bargained and compromised on 12. Called for vote as | ||
| I believe the worst decision is better than no decision. Need more strong and opinionated | ||
| Pushback in the TSC so believe we should vote. | ||
| * Antoine, if you call for vote with any data to back up claim, then believe likely lose vote, just | ||
| FYI. | ||
| * Matteo, don’t believe that changing this improves security posture, that is not a reason | ||
|
|
||
| * deps,lib,src: add experimental web storage [#52435](https://github.com/nodejs/node/pull/52435) | ||
| * On the board meeting agenda to ask about getting approval for License. | ||
| * Meeting is this Friday | ||
|
|
||
| ### nodejs/TSC | ||
|
|
||
| * Update meeting times? [#1528](https://github.com/nodejs/TSC/issues/1528) | ||
| * Michael will propose times based on updated data | ||
|
|
||
| * Node.js Collaborator Spotlight Proposal [#1474](https://github.com/nodejs/TSC/issues/1474) | ||
| * FYI, now documented and open for nominations | ||
|
|
||
| ### nodejs/admin | ||
|
|
||
| * Events / Collaborator Summits for 2024 [#814](https://github.com/nodejs/admin/issues/814) | ||
| * Next step is to run survey to see who can make it. | ||
|
|
||
| ## Strategic Initiatives | ||
| * skipped as we ran out of time | ||
|
|
||
| ## 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.
I honestly cannot believe we're adding statements like this in TSC meeting notes.
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.
Honestly I’m having a hard time with the exclusionary attitude as well in terms of what the project values have been historically.
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.
I'll apologize in advance if I paraphrased incorrectly in this case.
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.
Thinking about it further I'm going to remove that line from the minutes as regardless of what the discussion was I probably should have edited more appropriately.