EFI: Working with the ecosystem

[sheplu]

Motivation

Express (organization) is one if not the largest project part of the Node.js ecosystem. As such, we impact and can be impacted by the full ecosystem, from specific projects using us (like sails or nest.js) or projects that we use (like node.js)
By working with the ecosystem, providing feedback and being provided with feedback we can operate at a better efficiency

Expectation

Have some members of the Express Organization be part of key initiatives from other ecosystem

Implementation

Officialise some members to represent the Express Organization in the Node.js webserver framework group
Officialise some members to represent the Express Organization in the CPC / OpenJS
Officialise some members to represent the Express Organization in other groups (WinterCG for example...?)
Find a good way to share metrics that we can have, from specific builds (performance) or usage based on downloads
Communicate about the initiative, and express as a whole, and be relayed by the ecosystem

Status

Part: Organization

Draft

Express is - and has been - the main Node.js framework for the past decade, and even if REST APIs are still used (and are the norm), some changes happened in how we work around APIs, with new versions of HTTP, GraphQL, gRPC and other technologies like WebSocket.
To stay relevant, Express should be part of initiative like the Node.js web server framework
By having modules covering a vast range of use cases, the benchmarks of all packages can also be used to test regressions (or optimization) part of Node.js

[bjohansebas]

I think we're gradually working quite a lot with the ecosystem. Should we close this? Or do you think there's another group we should be working with?