-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Create a nodejs/startup team #35215
Comments
I have a slight preference to bootstrap but not massive. Startup makes me think of a company 😂 |
+1 for creating the team I have a slight preference to |
nodejs/startup-bootstrap it is 😉 |
|
+1 to any name. will this team also focus on the embedding topics, or will stick to snapshoting? |
@gireeshpunathil I think it would be better to have a team dedicated to embedding since it's more than just about startup (e.g. maybe also how the instance shuts down or how a virtual file system can be supported) |
I want to join this team because I'm doing something to modify start up for our own customized Node.js. |
I was about to create the team and then remembered that we still have not settled down on the name. Please 👍 this reply if you prefer nodejs/startup and 🎉 if you prefer nodejs/bootstrap (I assume we are not going to take longer names but feel free to reply if you want to make it a vote option 😂) |
@danbev FYI in case you missed this. I think you were doing some investigation in this area. |
I would be interested in helping out. I have been looking over the startup process myself. |
Thanks, I had missed it. I'd be interested in joining this team. Thanks |
How about pre-userland? |
I created a team with me @danbev and @XadillaX and opened #35406. @drewswanner Since this team will be CODEOWNERS it is reserved for collaborators. Please check out https://github.com/nodejs/node/blob/master/GOVERNANCE.md#collaborators on how to become a collaborator, thanks! |
PR-URL: #35406 Fixes: #35215 Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Shelley Vohr <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Khaidi Chu <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: nodejs#35406 Fixes: nodejs#35215 Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Shelley Vohr <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Khaidi Chu <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: James M Snell <[email protected]>
Hi, I propose to create a nodejs/startup (or maybe nodejs/bootstrap?) team which can be the owner of these files
I have been working on including more of the startup process into the snapshot and supporting userland snapshots (initial goal is to be able to snapshot a warmed-up HTTP server and then dehydrate it from a snapshot during startup), it would be helpful to create a team for collaborators who are interested in the startup process and optimization to join and collaborate.
cc @nodejs/tsc
The text was updated successfully, but these errors were encountered: