Revive the WG #92
Comments
|
Wow, @sheplu you have read my mind. I was also thinking it was about time to revive this as well. I was going to post an issue just like this after I finished working on the import maps pr and one other project. Glad to see I was not alone in thinking about this, and would love to see action in this space. |
|
next step add a meeting on the node.js calendar every two weeks and start some initiatives? |
We should review the stuff we had from before, I believe at least some of it is still good ideas most folks will agree with. |
|
I was also thinking maybe this would be a great way for @ShogunPanda to make some good progress with milo. The hard parts there afaict are resolving backwards comapt. If we want a new high level http api, we could avoid some of those compat issues under a new module namespace. |
|
@wesleytodd initiatives could be also something from the backlog, we just need to start from somewhere 😄, some ideas from nodeconf where to create a v2.0 of tls, net and http modules |
|
I think a good first talk would be to share some point of the discussion we had during NodeConf and see what we want to do from that. This groups seems to be intersecting with a few other ideas / projects / next steps |
|
We had discussed a strategy for this in #55 I think. It did not fully cover tls and net but was more about the http part. I wasn't there for the collab summit (sadly, especially hearing this stuff I care a lot about was discussed), but I assume since @jasnell was there that he was part of the convo and I am sure remembers that plan we had worked on. Since then I was actually thinking one way we could do this is introduce a new |
|
We can try to schedule a first meeting in december and see what we want to do. Between Thanksgiving and some event elsewhere, maybe we can squeeze a one hour call between the 11th and 15th ? |
|
@wesleytodd Actually Milo had a callbacks styles similar to llhttp so I was able to integrate pretty quickly (in static linking, WASM is still missing). But thanks for caring about me. ❤️ In general I wouldn't limit this to a Anyway I'm totally in for this WG! |
I think we should spend some time thinking about what should be included here. Some things like cookies have been brought up and I feel like
Yeah I think this is the next question. Since it sounds like we have consensus on reviving this group maybe the next is to open an issue for picking at time. @sheplu since you took the initiative here, do you want to run the meetings? I assume you have all the accounts right? Back when I ran them with the openjs logins, which can only have one meeting at a time IIRC so we need to schedule around other meetings. |
|
I will create an issue and poll to find the best time - at least for the first meeting and then we can see when to schedule it. I should have all access, both on zoom and YouTube but I will have to check |
|
Completely forgot about the web-framework, sorry folks ! https://doodle.com/meeting/participate/id/azBRp7Za @nodejs/web-server-frameworks @wesleytodd @jasnell @wesleytodd @mhdawson @joyeecheung @marco-ippolito @RafaelGSS @ShogunPanda @mcollina |
|
I think if we wanted to have a kickoff just to discuss why we are reviving it and what we want to propose for initial work in the new year that's fine but I wouldn't expect a large participation or deep discussion. I am also fine personally if we hold off until next year. |
|
🫡 Interested and added my availability to the doodle. I am no longer a maintainer of Fastify, but still very much an HTTP nerd and would happy to be apart. |
|
It seems the best time would be today end of day (french time) - with all (5) voters being available. edit: and @marco-ippolito :) |
|
@sheplu Can you clarify "End of The day"? I Have a meeting between 18:30 and 20:00 CET. |
|
Best time seems to be 21h-22h (Paris time) tonight @ShogunPanda |
|
Oh, it absolutely works for me then! Let's rock it! |
|
It's hard to be consisten with this time slot in the long run, usually other wg are around 4pm (Italian time) |
|
@sheplu what time exactly? I can use my Vercel zoom account to host the meeting. I'll plug it into a timezone converter too so we can al be on the same page. |
|
Ethan Arrowood is inviting you to a scheduled Zoom meeting. Topic: Web Server Framework WG Join Zoom Meeting Meeting ID: 845 9480 3440 One tap mobile Dial by your location Meeting ID: 845 9480 3440 Find your local number: https://vercel.zoom.us/u/kdkXseXpLv |
|
Just noticed this, will try to make the next meeting in the new year. |
|
We have notes and a recording we can post. I think we have a lot of agreement from the outset on what needs to be done. |
|
closing as we are now alive again :) |
Following a good discussion during NodeConf EU, it would make sense to try to revive this initiative
Some topics were discussed around the
netstack but also the same idea to work with HTTP 1 / 2 / 3 and find a way to integrate that.Tagging some folks that could be interested
Feel free to add other people :)
The text was updated successfully, but these errors were encountered: