diff --git a/CONSTITUENCY-NEEDS.md b/CONSTITUENCY-NEEDS.md index ea89b19..79993dd 100644 --- a/CONSTITUENCY-NEEDS.md +++ b/CONSTITUENCY-NEEDS.md @@ -115,12 +115,12 @@ to look forward to, what's the project direction). Changes between ## Ways to fund their work * Channels through which they can fund their work -## Ability to asses impact of changes they make +## Ability to assess impact of changes they make * Tools to evaluate impact of updates they make on other packages/applications ## Reasonable resource usage/performance -* Resonable resource usage (cpu, memory etc.) +* Reasonable resource usage (cpu, memory etc.) * Performance ## Good security and CVE practices in the project @@ -130,7 +130,7 @@ to look forward to, what's the project direction). Changes between ## Better CVE management in the ecosystem -* Better ways to deal with reported vulnerabilties +* Better ways to deal with reported vulnerabilities * Better systems of keeping track of dependencies (updates, vulnerabilities and their relevancy, etc) ## Good CI infrastructure and experience in the project @@ -170,5 +170,5 @@ to look forward to, what's the project direction). Changes between * Assets to help demonstrate Node.js is a good choice and that an organization should invest in using and supporting it. -* Assets to help champions within an orgazation advocate +* Assets to help champions within an organization advocate for investing in the Node.js project. diff --git a/collaborator summit/2022-dublin/community-brainstorm.md b/collaborator summit/2022-dublin/community-brainstorm.md index 8041e92..18c3ddb 100644 --- a/collaborator summit/2022-dublin/community-brainstorm.md +++ b/collaborator summit/2022-dublin/community-brainstorm.md @@ -2,12 +2,12 @@ | 2021 | 2022 | Change | |---|---|---| -| Collaborator profile / Growing collaborators / Succession plannig & technical talent pool / existing collaborators | 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? | new | +| Collaborator profile / Growing collaborators / Succession planning & technical talent pool / existing collaborators | 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? | new | | Attracting new collaborators / Making your first contribution / newcomers / Engage and help people wanting to collaborate & help (Collaborator Summit is great but Covid) | 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 | = | | Consensus process / PR review & approval flow | Education | new | | More communication about initiative | Enabling larger initiatives | +1 | | Large & significant changes | Further built in tooling | +3 | -| Mentorship programm is a good idea (but maybe with a bit more follow up) | Being well welcomed in WG / being well welcomed in working group | -5 | +| Mentorship program is a good idea (but maybe with a bit more follow up) | Being well welcomed in WG / being well welcomed in working group | -5 | | Leadership / Leadership model | Faster startup time | new | | Build technology, flow to being able to test | Sustainable outreach / Adjacent community engagement | new | diff --git a/collaborator summit/2022-dublin/technical-priorities.md b/collaborator summit/2022-dublin/technical-priorities.md index 45533c3..2198001 100644 --- a/collaborator summit/2022-dublin/technical-priorities.md +++ b/collaborator summit/2022-dublin/technical-priorities.md @@ -4,7 +4,7 @@ |--- |--- |--- | | TypeScript / Types | ESM support | new | | Serverless | Types in JavaScript (TaC or TS) / Types / Server-Side TypeScript | -1 | -| Web Assembly | 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 | +| Web Assembly | Serverless / Seamless hosting of Node.js server. Support latest version serverless hosting by major cloud providers / Node.js as a cloud function runtime / Cloud deployment | -1 | | Transaction tracing (ex. Open Telemetry) / Tracing | Small footprint JavaScript runtimes | new | | Single Binary | Observability (Otel, prometheus, etc.) | -1 | | CI/CD Automation | Developers-first DX | new | @@ -14,7 +14,7 @@ | Secure Software bill of material | Supply chain security | = | | Pre-compilation | eBPF | new | | Cryptocurrency | Multi-pages Apps (MPAs) / Full-stack JavaScript | new | -| IoT | Edge / Can we lift something from workerd? Are there any approches or features? | new | +| IoT | Edge / Can we lift something from workerd? Are there any approaches or features? | new | | Zero knowledge | GraphQL / gRPC | -5 | | Object capability (OCAP) | Kubernetes / Containerization | new | | Ecosystem Comparability & Maintenance | | | @@ -36,7 +36,7 @@ | ESM | Undici / undici in core | -2 | | Up to date ES version JavaScript support | ESM import mocking | -1 | | Diagnostic tools (log, debugging etc.) | Hot reload / dev server | new | -| Quic | More complet ESM/CJS interop | -2 | +| Quic | More complete ESM/CJS interop | -2 | | Worker Thread support | More assertion for test runners / | new | | fs hooks | python -m SimpleHTTPServer equivalent | new | | Argument Parser | Better support embedding Node.js into other projects (related to build systems support) | new | @@ -46,18 +46,18 @@ | Better installers / binary management | TypeScript integration / TypeScript support | new | | AOT (to v8 snapshot maybe?) | llhttp and its dependency llparse is mostly a blackbox | new | | Current OpenSSL support | Disk backed blob object | new | -| Iteration on policies and/or exposing sandoboxing primitives to scripts | Module quality assessment tool: (eg. check if you have dual exports) | new | -| Alternative SSL support | FetchEvent and familly (CloudFlare workers-like server) | new | +| Iteration on policies and/or exposing sandboxing primitives to scripts | Module quality assessment tool: (eg. check if you have dual exports) | new | +| Alternative SSL support | FetchEvent and family (CloudFlare workers-like server) | new | | | logger | new | | | build in bundler and transpiler | new | -> Documentation is a key point to adress (next-10 initiative on the way) +> Documentation is a key point to address (next-10 initiative on the way) -> ESM seems crucial also (function, doc, recommandation, interop...) +> ESM seems crucial also (function, doc, recommendation, interop...) > Diagnostic seems to be a key concept to improve -> Some functionnalityes landed: `Fetch` & `undici` & `argument parser` & `openssl` +> Some functionalities landed: `Fetch` & `undici` & `argument parser` & `openssl` ## Other diff --git a/meetings/summit-typescript-jul-2022.md b/meetings/summit-typescript-jul-2022.md index f54f671..decde90 100644 --- a/meetings/summit-typescript-jul-2022.md +++ b/meetings/summit-typescript-jul-2022.md @@ -46,7 +46,7 @@ * Jacob * Today you can support TS using esloader with command line loader * Geoffrey shared steps you need to do using ts-node -* Tierney believe goal is to run node test.ts +* Tierney believes goal is to run node test.ts * Michael, not bundling, but if required pieces already installed, then work, otherwise prompt to install pieces. * Jacob, how? @@ -98,7 +98,7 @@ * Wes fundamentally all we want is ability to install something that has the ability to override Node.js execution start. * Tierney, don’t want to do it for anything, ok to limit it down to a limited subset, for now TypeScript -* Jacob, don’t necessarily to need to limit subset, only if we can define a method that is agnostic +* Jacob, don’t necessarily need to limit subset, only if we can define a method that is agnostic * Geoffrey, perspective of maintainers, there are lots of decisions so choosing config etc. as Node.js maintainer, don’t have Node.js make decisions. Just enable people to load easily. This is first decision to make. @@ -108,7 +108,7 @@ * Opt in on a global basis * Don’t violate security expectations * Geoffrey, loaders roadmap has a number of those on the roadmap, PR already open #43973 -* Tieney, +1 being totally configurable, as long as it does not take a lot of energy to +* Tierney, +1 being totally configurable, as long as it does not take a lot of energy to support that and DX is not awful, DX needs to be primary result. Could loader just not provide the configuration. * Jake, busy looking at snippet, talking about putting things in package.json. Do we not care diff --git a/surveys/2023-04/questions.md b/surveys/2023-04/questions.md index a99dedf..5806ab2 100644 --- a/surveys/2023-04/questions.md +++ b/surveys/2023-04/questions.md @@ -21,7 +21,7 @@ - Which groups do you identify with? (multiple choice) - Direct end users: Users who run tools themselves - - Application operators: Users who interacts with existing running applications + - Application operators: Users who interact with existing running applications - Application developers: Frontend tools consumers, backend server authors, tools authors - Library & package authors: Users who write libraries and packages to be included on other applications - Node.js core maintainers: Developers working directly on Node.js, individuals participating in Working Groups @@ -29,7 +29,7 @@ - Are you part of a group not covered ? If yes which one ? (open question) -- What is your use cases of Node.js ? (if multiple use case, separate with a comma) (open question) +- What are your use cases of Node.js ? (if multiple use case, separate with a comma) (open question) ## What Node.js binaries do you use diff --git a/surveys/2024-04/questions.md b/surveys/2024-04/questions.md index ab0c7fa..add411f 100644 --- a/surveys/2024-04/questions.md +++ b/surveys/2024-04/questions.md @@ -39,7 +39,7 @@ - Are you part of a group not covered ? If yes which one ? (open question) -- What is your use cases of Node.js ? (multiple choice) (open question - Other should give an input) +- What are your use cases of Node.js ? (multiple choice) (open question - Other should give an input) - Cli tools - Testing - Development of APIs with Microservices diff --git a/surveys/2025-04/questions.md b/surveys/2025-04/questions.md index 5cf6c6e..c48013f 100644 --- a/surveys/2025-04/questions.md +++ b/surveys/2025-04/questions.md @@ -58,7 +58,7 @@ - sponsors your time to work in the Node.js project - through membership in the OpenJS foundation -- What is your use cases of Node.js ? (multiple choice) (open question - Other should give an input) +- What are your use cases of Node.js ? (multiple choice) (open question - Other should give an input) - Cli tools - Development of APIs with Microservices - Development of APIs with Other diff --git a/surveys/2026-collaborator-health-survey.md b/surveys/2026-collaborator-health-survey.md index 52a65c0..c02ba60 100644 --- a/surveys/2026-collaborator-health-survey.md +++ b/surveys/2026-collaborator-health-survey.md @@ -50,7 +50,7 @@ ### Why did you get involved ? (multi-select question, skip for collaborators who have contributed for less than 1 year OR 1-2 years) -- Hobby, wanted to contributed to a key open source project +- Hobby, wanted to contribute to a key open source project - Using Node.js personally wanted to contribute - Work for a company that uses Node.js, encouraged to contribute - Joined a team at the company I work for that contributes @@ -79,7 +79,7 @@ ### What makes you less likely to continue contributing to the project? (multi-select question) -- Code reviews are to strict +- Code reviews are too strict - Code reviews are too slow - Code reviews are too lax - CI is flaky @@ -112,7 +112,7 @@ ### If you are not able to contribute as much as you would like, what is preventing this? (multi-select question) -- My company actively interferers with Open Source contributions +- My company actively interferes with Open Source contributions - My company does not support my contributions - Competing work or professional obligations - Competing personal obligations