-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: 2023 vancouver summit community
- Loading branch information
Showing
2 changed files
with
134 additions
and
0 deletions.
There are no files selected for viewing
62 changes: 62 additions & 0 deletions
62
collaborator summit/2023-vancouver/community-brainstorm.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,62 @@ | ||
| ## Key focus area | ||
|
|
||
| | 2022 | 2023 | Change | | ||
| |---|---|---| | ||
| | Increase corporate contributions: getting a few unicorn startups and companies to allocate some engineers to Node.js / Keeping the lights on, build, security releases / Corporate Investment: How do we make it happen? | Increase the outreach to add more collaborators / maintainers / New contributors onboarding / growing long term collaboratos | new | | ||
| | Funnel contributor onboarding into relevant working groups / Communication about initiative and help people to be involved / Could use more followup after Code & Learns / Onboarding the next generation: what happens when we all die | Standards / JavaScript / Introducing and improving standards-based interfaces to encourage their use over existing non-standard equivalents. | = | | ||
| | Education | Balancing evolution and stability | | | ||
| | Enabling larger initiatives | Documentation | | | ||
| | Further built in tooling | Performance | | | ||
| | Being well welcomed in WG / being well welcomed in working group | Community communication | | | ||
| | Faster startup time | Security | | | ||
| | Sustainable outreach / Adjacent community engagement | Observability | | | ||
|
|
||
|
|
||
| > More coordination with new contributor and sharing knowledge | ||
| > Core functionnalities around Observability and security while balancing with stability | ||
| > Standardization and Documentation | ||
| ## Obstacles | ||
|
|
||
| | 2022 | 2023 | Change | | ||
| |---|---|---| | ||
| | Flaky CI / CI reliability / Flaky CITGM / CI time | Node.js core is very complex for new contributors / Mentorship/new contributor on-ramp / Extremely hard ramp up to become a prolific maintainer of Node.js / Maintainer Sustainability / It's often unclear to first time contributors who are the primary reviewers of certain areas of the project. | | | ||
| | Lack of "good first issues" | npm / Lack of standardization/specification of package.json | | | ||
| | Some niche or complicated areas have a really hard time getting reviews | flaky CI / node.js ci / Flaky tests | | | ||
| | Communicating with the community about adding npm module functionalities into core | CI performance, especially on not common combination / CI UX / CI/CD | | | ||
| | ESM and CJS interoperability in npm module: do we have a recommandation for the community? | Bun / other javascript runtime. It's will create confusion for junior javascript dev / Deno | | | ||
| | A lot of different topic, how to prioritize | CJS | | | ||
| | Timezone / Meeting time for WG | rigidly adhering to web api choices adds burden for node users | | | ||
| | Primordials | Slack is quite big and sometimes is hard to know where to ask specific questions | | | ||
| | Money | | | | ||
| | Corporate priorities | | | | ||
| | OpenJS Fundation limitations | | | | ||
| | Burnout | | | | ||
| | Not getting enough contribution from the ecosystem | | | | ||
| | Work more asynchronously | | | | ||
|
|
||
| > Flaky tests and CI are still an issue | ||
| > Hard to onboard / have contributor in specific area | ||
| > Lack of standards and some standards are only for web | ||
| ## Working well | ||
|
|
||
| | 2022 | 2023 | Change | | ||
| |---|---|---| | ||
| | Collaborator Summit | Community | | | ||
| | Onboarding new collaborators | teams and autonmy/indepedence / Working Groups | | | ||
| | PR process | Minimal breakage | | | ||
| | New collaborators (seems a lot new people this year than before) | Collaborator summit | | | ||
| | OpenSSF contribution to make Node.js more secure | Running part of the projects outside of the main repo. As an exapmle, Undici has a steady flow of collaborators and PRs from individuals. | | | ||
| | Making sure the ecosystem is stable and breaking changes are few. Few complaintes from the ecosystem | slack for team | | | ||
| | Automating away a lot of things with labels and GitHub Actions has made the contributing experience friendlier | Youtube/meeting minutes/recording in public | | | ||
|
|
||
| > Async work | ||
| > Collaborator Summit | ||
| > "External" projects |
72 changes: 72 additions & 0 deletions
72
collaborator summit/2023-vancouver/technical-priorities.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,72 @@ | ||
| ## Technology trends | ||
|
|
||
| | 2022 | 2023 | Change | | ||
| |--- |--- |--- | | ||
| | ESM support | | new | | ||
| | Types in JavaScript (TaC or TS) / Types / Server-Side TypeScript | | -1 | | ||
| | Serverless / Seemless hosting of Node.js server. Support latest version serverless hosting by major cloud providers / Node.js as a cloud function runtime / Cloud deployment | | -1 | | ||
| | Small footprint JavaScript runtimes | | new | | ||
| | Observability (Otel, prometheus, etc.) | | -1 | | ||
| | Developers-first DX | | new | | ||
| | WinterCG | | +9 (ecosystem ?) | | ||
| | http 3 | | new | | ||
| | WASM | | -6 | | ||
| | Supply chain security | | = | | ||
| | eBPF | | new | | ||
| | Multi-pages Apps (MPAs) / Full-stack JavaScript | | new | | ||
| | Edge / Can we lift something from workerd? Are there any approches or features? | | new | | ||
| | GraphQL / gRPC | | -5 | | ||
| | Kubernetes / Containerization | | new | | ||
| | | | | | ||
|
|
||
| > | ||
| > | ||
| > | ||
| > | ||
| ## Node.js features | ||
|
|
||
| | 2021 | 2022 | Change | | ||
| |--- |--- |--- | | ||
| | Docs: production ready recommendations / Rustdoc but make it Node.js / Documentation (better documentation for new people) / Docs best practice for module authors / Docs: official tutorials | | | | ||
| | Stable fetch() | | | | ||
| | Undici / undici in core | | | | ||
| | ESM import mocking | | | | ||
| | Hot reload / dev server | | | | ||
| | More complet ESM/CJS interop | | | | ||
| | More assertion for test runners / | | | | ||
| | python -m SimpleHTTPServer <PORT> equivalent | | | | ||
| | Better support embedding Node.js into other projects (related to build systems support) | | | | ||
| | Improving performance of Web APIm WHATWG streams specifically | | | | ||
| | Expanded use of diagnostic channel | | | | ||
| | WASM / WASI status | | | | ||
| | TypeScript integration / TypeScript support | | | | ||
| | llhttp and its dependency llparse is mostly a blackbox | | | | ||
| | Disk backed blob object | | | | ||
| | Module quality assessment tool: (eg. check if you have dual exports)| | | | ||
| | FetchEvent and familly (CloudFlare workers-like server) | | | | ||
| | logger | | | | ||
| | build in bundler and transpiler | | | | ||
|
|
||
| > | ||
| > | ||
| > | ||
| ## Other | ||
|
|
||
| | 2021 | 2022 | Change | | ||
| |--- |--- |--- | | ||
| | Improving CI reliability | | new | | ||
| | Compatibilities with other environments | CITGM (smoke test suite) maintenance | new | | ||
| | | Fuzzing | new | | ||
| | | Competing with Bun and Deno on performances / keep up with them | new | | ||
| | | Vulnerability management | -4 | | ||
|
|
||
| > Vulnerability and security are key | ||
| > global maintenance (on multiples topics) |