Skip to content

Commit b8f3b60

Browse files
committed
feat(rfc): establish a performance working group
1 parent 2ee2a5a commit b8f3b60

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

docs/adr/performance-wg.md

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# ADR [Number]: Performance Working Group
2+
3+
## Status
4+
5+
Proposed
6+
7+
## Submitters
8+
9+
- @wesleytodd
10+
11+
## Decision Owners
12+
13+
- @expressjs/express-tc
14+
15+
## Context
16+
17+
Express has traditionally taken a very lax approach to performance. historically this has meant poor outcomes with regard to performance and lack of visibility around how changes
18+
impact performance. The goal of this proposed working group is to centralize discussion so the whole ecosystem of packages can benefit from targeted performance work. The scope of
19+
this WG would be all active packages in the `expressjs`, `pillarjs` and `jshttp` orgs with a special focus on the ones which are direct dependencies of `express` itself.
20+
21+
**Why do we need a working group?**
22+
23+
The current state is we have many open PRs, in flight initiatives, and planned future work. With a loose approach we can easily have duplicated work, conflicting approaches, or
24+
focus on the wrong outcomes. By giving this WG scope over this we can centralize the discussion and plans so that we unlock better and faster work in the individual packages.
25+
26+
## Decision
27+
28+
Similar to the Security WG, we will setup a new repo (expressjs/perf-wg) and corresponding plan of action. The WG will be delegated responsibility for driving concensus around the
29+
current scope and future scope to be determined by the group once setup.
30+
31+
## References
32+
33+
- https://github.com/expressjs/express/pull/6129
34+
- https://github.com/expressjs/express/issues/5998

0 commit comments

Comments
 (0)