Skip to content
GitHub no longer supports this web browser. Learn more about the browsers we support.
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

Web Frameworks Team #459

Closed
wesleytodd opened this issue Jan 3, 2020 · 38 comments
Closed

Web Frameworks Team #459

wesleytodd opened this issue Jan 3, 2020 · 38 comments

Comments

@wesleytodd
Copy link
Member

@wesleytodd wesleytodd commented Jan 3, 2020

We would like to kick off a new team. The scope of the team would be as follows:

This WG would be focused around how the core http(1/2/3) and other related apis fit the needs of the web frameworks (express, fastify, restify, hapi, koa etc). It would also give the maintainers a forum to discuss and collaborate on issues which span the projects.

The first things we will need are a team and a repo. The working name is "Web Server Frameworks", so it would make sense to me to start with web-server-frameworks as the repo name (assuming it is not a problem to change the name if we land on something more fitting).

So far the initial list of members are:

@wesleytodd
@dougwilson
@jasnell
@retrohacker
@mcollina
@Ethan-Arrowood
@ghermeto
@hueniverse
@JozefFlakus
@delvedor
@sheplu
@ayenisholah
@niftylettuce
@fed135
@DonutEspresso
@AlexZeitler
@arei
@gireeshpunathil
@RamirezAlex
@drawm
@MarcinHoppe
@Alyssa-Cooper
@antsmartian
@kamilmysliwiec
@ronag
@LoicPoullain
@mhdawson
@bajtos
@raymondfeng
@blakeembrey

I only listed those who explicitly said they want to be involved in nodejs/TSC#795 or at the Collab summit.

I am sure there are others, so if you see this and are interested please comment and I will add you to the list above, but here are some others who might also want to be:

@LinusU
@jonathanong
@dead-horse
@hekike
@hacksparrow

@hueniverse

This comment has been minimized.

Copy link

@hueniverse hueniverse commented Jan 3, 2020

I am certainly interested in learning more about such effort.

@JozefFlakus

This comment has been minimized.

Copy link

@JozefFlakus JozefFlakus commented Jan 3, 2020

Interesting idea, I'm curious about the topics that will be covered there. As a framework author you can add me as well.

@wesleytodd

This comment has been minimized.

Copy link
Member Author

@wesleytodd wesleytodd commented Jan 3, 2020

For those who follow here, just to be clear, if you express interest I will add you to the list of members above. If you do not want this, please be clear about your intent. @JozefFlakus and @hueniverse are both added to the members list!

@delvedor

This comment has been minimized.

Copy link
Member

@delvedor delvedor commented Jan 3, 2020

I'm very interested as well, great initiative! :)

@sheplu

This comment has been minimized.

Copy link
Member

@sheplu sheplu commented Jan 3, 2020

Not a web framework dev but using them on serverless most of the time.
So if I can help I will be very interested !

@MylesBorins

This comment has been minimized.

Copy link
Member

@MylesBorins MylesBorins commented Jan 3, 2020

I think this is an awesome idea and am happy to help in anyway y'all need to be successful.

I do want to suggest that this effort be framed as a team to start. To become a working group involves creating a charter and being given clear authority over specific work areas of the Node.js project. While I see this effort as massively improving our ecosystem I do not yet see clarity on what exactly the group would like authority over, and as such a team makes more sense while that spins up.

Some historical bits to keep in mind. The modules team, is still a team after 2+ years of active work on ESM and is only now starting to discuss chartering. The release working group started as the lts team and only chartered in 2017 2+ years after it's formation.

I mention these two instances not to create any sort of barrier, especially time wise, but more to point out that both of these initiatives were extremely successful in making large / impactful change in Node.js, and it was only at the point that there was no questions regarding ownership (release) or that something significant had shipped (modules) that chartering was actively discussed.

@wesleytodd wesleytodd changed the title Web Frameworks Working Group Web Frameworks Team Jan 3, 2020
@Xstoudi

This comment has been minimized.

Copy link

@Xstoudi Xstoudi commented Jan 3, 2020

@RomainLanz and @thetutlage should be listed in here IMO

@wesleytodd

This comment has been minimized.

Copy link
Member Author

@wesleytodd wesleytodd commented Jan 3, 2020

@MylesBorins I agree and have updated the request. I am not sure we would ever want specific authority over work in Node.js and I agree that chartering would serve no purpose for us now. One thing to point out, while this process has been done a few times there are no docs, only docs for starting a WG (see nodejs/TSC#795).

@ayenisholah

This comment has been minimized.

Copy link

@ayenisholah ayenisholah commented Jan 3, 2020

I am interested. I love Node.js

@MylesBorins

This comment has been minimized.

Copy link
Member

@MylesBorins MylesBorins commented Jan 3, 2020

@wesleytodd I think I found the documentation

TL;DR

  • Make issue to make a new repo (this one)
  • Request team to own new repo
    • if no team exists request to make a new one
  • In 72 hours if there are no objections team + repo are made.

Seems like you've done all the heavy lifting already! I can help with making the repo + team in 72 hours if there are no objections

@niftylettuce

This comment has been minimized.

Copy link
Member

@niftylettuce niftylettuce commented Jan 3, 2020

I'd be interested, actively building Lad

@wesleytodd

This comment has been minimized.

Copy link
Member Author

@wesleytodd wesleytodd commented Jan 3, 2020

Also, how do people feel about changing the name to Server Frameworks Team? It was brought to my attention that Web Frameworks strongly implies the front-end ones (react, vue, etc), which is not my intended focus.

@retrohacker

This comment has been minimized.

Copy link

@retrohacker retrohacker commented Jan 3, 2020

A quick sampling of some framework home pages:

Express calls itself a web framework
Fastify calls itself a web framework
Restify calls itself a web service framework
Hapi calls itself a framework
Koa calls itself a web framework

I have a preference to keep "web framework" in the name since it seems to be rather standard across the ecosystem. But ultimately don't care too much about what color we paint this shed 😄

@wesleytodd

This comment has been minimized.

Copy link
Member Author

@wesleytodd wesleytodd commented Jan 3, 2020

Web Server Framework?

@fed135

This comment has been minimized.

Copy link
Member

@fed135 fed135 commented Jan 3, 2020

This is very relevant to my interests!

@niftylettuce

This comment has been minimized.

Copy link
Member

@niftylettuce niftylettuce commented Jan 3, 2020

HTTP Framework is pretty simple/focused, and doesn't limit us to just Web since a lot of these also serve as API frameworks. But then do people consider API part of Web? What about using one of these frameworks as an API for a React Native iOS/Android app?

Web Server Framework is 👍

@wesleytodd

This comment has been minimized.

Copy link
Member Author

@wesleytodd wesleytodd commented Jan 3, 2020

I really dont want to limit to http. I think protocol doesn't really matter as long as the domain is the server framework. And for sure api servers fit within this fully. It looks like atleast a few gave "Web Server Framework Team" the 👍, but does anyone have other ideas (or object to that name)?

@JozefFlakus

This comment has been minimized.

Copy link

@JozefFlakus JozefFlakus commented Jan 3, 2020

I would say that, as far it is visible under @nodejs organization it carries the domain implicitly. If it will stay as Web Frameworks Team everyone will recognize the domain properly, and it will be easier to remember and operate in the future.

@DonutEspresso

This comment has been minimized.

Copy link

@DonutEspresso DonutEspresso commented Jan 3, 2020

I am interested too.

@AlexZeitler

This comment has been minimized.

Copy link

@AlexZeitler AlexZeitler commented Jan 3, 2020

I would be interested, mostly from a Hypermedia perspective in web frameworks.

@arei

This comment has been minimized.

Copy link

@arei arei commented Jan 4, 2020

Interested.

@gireeshpunathil

This comment has been minimized.

Copy link
Member

@gireeshpunathil gireeshpunathil commented Jan 4, 2020

request to add me to the team. my motivations:

  • to help the middleware abstractions of these frameworks are well aligned / stacked up with node core functions
  • consider these frameworks as the prominent node.js workloads, gather usage insights and feed it back to the core
@RamirezAlex

This comment has been minimized.

Copy link
Member

@RamirezAlex RamirezAlex commented Jan 4, 2020

I would love to help :)

@drawm

This comment has been minimized.

Copy link

@drawm drawm commented Jan 4, 2020

Count me in. I would love to get involved!

@MarcinHoppe

This comment has been minimized.

Copy link

@MarcinHoppe MarcinHoppe commented Jan 5, 2020

I will definitely be following this effort and will try to contribute if anything security related pops up.

@Alyssa-Cooper

This comment has been minimized.

Copy link

@Alyssa-Cooper Alyssa-Cooper commented Jan 5, 2020

This is a great initiative. I'd love to contribute!

@antsmartian

This comment has been minimized.

Copy link
Contributor

@antsmartian antsmartian commented Jan 5, 2020

This is a great initiative. I'm someone who involve myself with load of web development in my day to day life, would love to contribute in this idea. Count me in.

@kamilmysliwiec

This comment has been minimized.

Copy link

@kamilmysliwiec kamilmysliwiec commented Jan 5, 2020

Great idea, I'm happy to help as well! (NestJS)

@mcollina

This comment has been minimized.

Copy link
Member

@mcollina mcollina commented Jan 5, 2020

I’m in!

I would also invite @ronag, who has done extensive work on http in core.

@ronag

This comment has been minimized.

Copy link
Member

@ronag ronag commented Jan 5, 2020

I'm interested as well.

@LoicPoullain

This comment has been minimized.

Copy link
Member

@LoicPoullain LoicPoullain commented Jan 6, 2020

I'm interested as well! (FoalTS)

@mhdawson

This comment has been minimized.

Copy link
Member

@mhdawson mhdawson commented Jan 6, 2020

I'm in as well.

@bajtos

This comment has been minimized.

Copy link

@bajtos bajtos commented Jan 6, 2020

I'd like to join too (https://loopback.io)

@raymondfeng

This comment has been minimized.

Copy link

@raymondfeng raymondfeng commented Jan 6, 2020

I'd like to join too - LoopBack.

@blakeembrey

This comment has been minimized.

Copy link

@blakeembrey blakeembrey commented Jan 6, 2020

Thanks @wesleytodd, I'd love to be involved.

@wesleytodd

This comment has been minimized.

Copy link
Member Author

@wesleytodd wesleytodd commented Jan 6, 2020

Ok, I have added everyone who has posted. According to the docs it needs to wait 72 hours without objection, and I posted 3 days ago, so I guess we are good to go!

Thanks everyone for the interest and once we get the team and repo setup I will post a doodle so we can pick a time for our first meeting.

@MylesBorins

This comment has been minimized.

Copy link
Member

@MylesBorins MylesBorins commented Jan 6, 2020

thanks @wesleytodd for pinging the thread. I'll go ahead and spin stuff up.

@MylesBorins

This comment has been minimized.

Copy link
Member

@MylesBorins MylesBorins commented Jan 6, 2020

Team created, Names in the list in original post have been added to that team. I've also made the repo and kicked it off with basic a basic README, code of conduct, license, and starter governance (including process for adding new members).

Gonna close this issue so y'all can take convo to the new repo

https://github.com/nodejs/web-server-frameworks

@MylesBorins MylesBorins closed this Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.