feat: add 2022 survey questions #173
There are no files selected for viewing
This file contains hidden or 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,135 @@ | ||
| # Survey April 2023 | ||
|
|
||
| ## Demographics | ||
|
|
||
| - Where are you from? (countries list if possible - or open question) | ||
| - country | ||
|
|
||
| - How long have you been working with Node.js? (numbers list from 0 to 10+) | ||
|
|
||
| - In what kind of organizations are you working in? | ||
| - big tech | ||
| - company | ||
| - startup | ||
| - university | ||
| - individual | ||
| - other | ||
|
|
||
| - Are you part/following some Working Groups? Are you involved in some Node.js community Working Groups ? If yes which one (open question) | ||
|
|
||
| ## Node.js Usage | ||
|
|
||
| - Which constituencies do you identify with? (multiple choice) | ||
| - Direct end users: Users who run tools themselves | ||
| - Application operators: Users who interacts 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 | ||
| - Organization with investments in Node.js (eg: Enterprises, Gouvernement bodies, Startups, Non-profit, Education, Security) | ||
|
|
||
| - Are you part of a constituency not covered ? If yes which one ? (open question) | ||
|
|
||
| - What is your use case of Node.js ? (open question) | ||
|
|
||
| ## What Node.js binaries do you use | ||
|
|
||
| - What is your OS for your local development environment ? (single choice - Other should give an input) | ||
| - Linux | ||
| - Windows | ||
| - MacOs | ||
| - Other? | ||
|
|
||
| - What is your OS in which you are running Node.js in production ? Do you plan to change that in the near future? (single choice - Other should give an input) | ||
| - Linux/Unix | ||
| - Windows | ||
| - MacOs | ||
| - Other? | ||
|
|
||
| - What is your architecture in which you are running Node.js with Node.js ? Do you plan to change that in the near future? (single choice - Other should give an input) | ||
| - x64 | ||
| - ia32 | ||
| - arm | ||
| - ppc | ||
| - s390 | ||
| - Other ? | ||
|
|
||
| - How do you get your Node.js executables? (multiple choice) | ||
| - With a Node.js version manager: nvm, n, nave, nvs, volta, etc. | ||
| - Using the official installer | ||
| - Using package managers like npm or yarn and install Node.js as a package | ||
|
There was a problem hiding this comment. this is kind of a weird choice given that they still have to have node in the first place to get npm or yarn, no? There was a problem hiding this comment. I'm aware of a private package manager that installs the specified version of Node.js in the projects' settings automatically when it installs dependencies. It is similar to a |
||
| - Using a system package manager: apt-get, brew, dnf, yum … | ||
| - Downloading binaries directly from Nodejs.org | ||
| - Building Node.js from Source | ||
| - Other | ||
|
|
||
| - If you use a version manager which one do you use (multiple choice - Other should give an input) | ||
| - nvm | ||
| - n | ||
| - nave | ||
| - nvs | ||
| - volta | ||
| - Other ? | ||
|
|
||
| ## Project Priorities and Direction | ||
|
|
||
| - Are you aware of the defined Node.js [Technical Priorities](https://github.com/nodejs/node/blob/main/doc/contributing/technical-priorities.md)? (single choice) | ||
| - Yes | ||
| - No | ||
|
|
||
| - Which of the current technical priorities are important to you ? (multiple choice) | ||
| - Modern HTTP | ||
| - Suitable types for end-users | ||
| - Documentation | ||
| - WebAssembly | ||
| - ESM | ||
| - Support for features from the latest ECMAScript spec | ||
| - Observability | ||
| - Permissions/policies/security model | ||
| - Better multithreaded support | ||
| - Single Executable Applications | ||
|
|
||
| - Are there technical priorities that you believe are missing (open question) | ||
|
|
||
| - What is important to you ? (multiple choice) | ||
| - Good understanding of the direction of the project | ||
| - Ability to affect the direction of the project | ||
| - Consumable APIs and docs | ||
| - Predictable and stable releases | ||
| - Innovation at a consumable pace | ||
| - Easy Installation | ||
| - Easy issue reporting, resolution and collaboration | ||
| - Broad deployment platform support | ||
| - Broad desktop platform support | ||
| - Consistent and intuitive error handling | ||
| - Runtime diagnostic tooling | ||
| - Development time diagnostic tooling | ||
| - Relevant APIs in core | ||
| - Module/dependency info and management | ||
| - Ways to fund their work | ||
| - Ability to assess impact of changes they make | ||
| - Reasonable resource usage/performance | ||
| - Good security and CVE practices in the project | ||
| - Better CVE management in the ecosystem | ||
| - Good CI infrastructure and experience in the project | ||
| - Supportive Collaborators and Environment in the project | ||
| - Better ways to build consensus in the project | ||
| - Easy contribution workflow | ||
| - Ability to embed and bundle the Node.js runtime | ||
| - A well maintained and secure standard library | ||
| - Assets that show Node.js is a good choice | ||
|
|
||
| - What is important to you that is not in this list? (open question) | ||
|
|
||
| ## Technical Questions | ||
|
|
||
| - Are you using native ESM (e.g. `"type": "module"`, `.mjs` or other solutions) in your Node.js Development? | ||
| - Yes | ||
| - No | ||
|
|
||
| - Are you planning to convert an application to native ESM or use native ESM for a future application? | ||
| - Yes | ||
| - No | ||
|
|
||
| - For those of you wishing to use ESM in an existing application, what have been the pain points or blockers preventing you from doing so (if any)? (open question) | ||
|
|
||
| - Do you encounter any recurring issues when using Node.js that you would like to share with us ? (open question) | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.