Define Scope

[arei]

I would like to propose an agenda item for the first meeting wherein the team defines the scope of what we are trying to accomplish and what constitutes a web-server-framework. We have a fine starting place as outlined within the goals, but a more specific scope will help us further narrow the work and expectations of our community.

As a starting place I offer the following questions that I feel should be considered...

1. What is the team specifically trying to accomplish?
2. What qualities define a web server-framework?
3. What are some of the known issues that web-server-frameworks have that could be addressed or advocated by this team?
4. What is the definition of success for this team?

Thoughts and discussion welcome.

[wesleytodd]

This is on the agenda for tomorrow, but I want to be clear, I do not think we should discuss "What qualities define a web server-framework?".

Defining our goals, success metrics and what types of discussions and work is in scope is important, but this is an invitation for bike shedding and I don't see much value in it.

[arei]

I agree completely, almost. I do think defining the scope in very generalized terms could be useful. I’m not talking about a laundry list of features that every framework must have in order to be considered a framework or anything of the such. I agree this will most certainly spin out of control entirely. Instead I am espousing the crafting of a short scope text, say something less than 40 words, that sets the boundaries of what we are trying to do. For example, “The node web-server-framework team provides guidance to the future of node as it pertains to any web server framework that employs http/https/http2/http3 interactions between itself and some client system.” (not a perfect example, but it conveys what i am shooting for.)