feat: add 2022 survey questions #173
Conversation
sheplu
force-pushed
the
survey-questions
branch
from
5707f16 to
2dc6549
Compare
|
@nodejs/next-10 To review for the next meeting #152 |
|
I would add those two questions related to ESM:
|
sheplu
force-pushed
the
survey-questions
branch
from
2dc6549 to
c5eddf9
Compare
|
Just added the two questions. With all the discussion we had but also people talking about that externally this seems to be an issue and having data would help us. Thanks @mcollina |
What are you hoping to learn from these questions? I asked similar questions at the June summit and very few people were planning on converting existing applications to ESM but what seemed like every single hand in the room went up (about 50 people) when asked if they would start their next project in ESM. We could add a third question like “Are you planning to use native ESM for your next Node.js project?” or just replace the second question with this. But either way, what are we trying to learn? That ESM adoption is low? I would be more interested in the follow up, like “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)?” and “For those of you trying to use ESM in a new application, what have been the pain points or blockers preventing you from doing so (if any)?” Questions like these would give us useful information in that we would know what issues need addressing for ESM usability. |
|
I can see to have a unique question for both next project and migration (as this is really linked) Adding a question about the blocker points can be interesting but I am also pretty sure we already know the feedbacks, we mostly all have the same (I think - but can be useful to focus the efforts on the more vocals ones first). What do you think @GeoffreyBooth ? |
Do we? We knew the blockers 2-3 years ago, but hopefully most of those have been resolved by now. I know that lots of people are waiting for the Loaders API to go stable (which should happen soon) but I’m unaware of any other issues. |
|
Let's add it then :) ESM/CJS was a big discussion in Austin and we talked again about it during the Dublin collab summit so let's see what is the new feedback from the community ! |
surveys/2022-12/questions.md
Outdated
| - Application developers: Frontend tools consumers, backend server authors, tools authors | ||
| - Library & package authors: Users who write librairies 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) |
There was a problem hiding this comment.
We should check if there were some that we added after the last survey, I think there was.
surveys/2022-12/questions.md
Outdated
| - other | ||
| - Are you part/following some working groups? | ||
| - yes | ||
| - no |
There was a problem hiding this comment.
Possibly add "If so which ones?"
surveys/2022-12/questions.md
Outdated
| - Relevant API in core | ||
| - Good understanding and process for security and CVE in the ecosystem | ||
| - Loader hook (to allow native typescript support) | ||
| - What is your use case of Node.js ? |
There was a problem hiding this comment.
Should we add a question that lists the titles that we have in an updated version of https://github.com/nodejs/node/blob/main/doc/contributing/technical-priorities.md based on the collaborator summit input?
There was a problem hiding this comment.
add this link and a question about priorities
surveys/2022-12/questions.md
Outdated
| - country | ||
| - How long have you been working with Node.js? (numbers list) | ||
| - 0 - 10+ | ||
| - In what kind of companies are you working in? |
There was a problem hiding this comment.
-companies + organizations
| - company | ||
| - startup | ||
| - university | ||
| - other |
|
It would be valuable to have some data of architecture/OS that people are using to run Node.js and how long do they plan to use it too, to help decide when we are looking into dropping support of a certain platform. |
sheplu
force-pushed
the
survey-questions
branch
from
c5eddf9 to
6cee55f
Compare
|
Everything updated following suggestions |
surveys/2022-12/questions.md
Outdated
| - Using package managers like npm or yarn and install Node.js as a package | ||
| - Using a system package manager: apt-get, brew, dnf, yum ... | ||
| - Other | ||
| - What is your Architecture and OS in which you are running Node.js ? Do you plan to change that in the near future? (open question) |
There was a problem hiding this comment.
I think this question would be better as a multiple choice, using the same names from our supported OS/architecture list.
There was a problem hiding this comment.
Also I would think that lots of people develop in one OS/arch and deploy in another, like develop in Mac and deploy under Linux/Docker.
There was a problem hiding this comment.
Add the question for both
- deployed
- developer
There was a problem hiding this comment.
updated with the two questions. Is the list of architecture supported this one ? Or is there another file containing the list ? https://nodejs.org/api/process.html#processarch
Possible values are: 'arm', 'arm64', 'ia32', 'mips','mipsel', 'ppc', 'ppc64', 's390', 's390x', and 'x64'.
| - How do you get your Node.js executables? | ||
| - With a Node.js version manager: nvm, ns, n, 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 .nvmrc local to a project.
sheplu
force-pushed
the
survey-questions
branch
from
6cee55f to
dafcdf9
Compare
sheplu
force-pushed
the
survey-questions
branch
from
dafcdf9 to
cf18e5a
Compare
surveys/2022-12/questions.md
Outdated
| @@ -0,0 +1,135 @@ | |||
| # Survey December 2022 | |||
There was a problem hiding this comment.
We should probably get this survey out soon 😄
There was a problem hiding this comment.
Haha yeah, I may have to update that :)
a good timeline would be to
- have it finished and published end of feb/start of march
- let it go a "month" until April/mid April
- review the feedback before Vancouver
- discuss about it during the Vancouver event
There was a problem hiding this comment.
I think what we have in the doc makes sense. I think asking for help to do the survey from the Foundation makes senses sooner than later and we can agree on the schedule with them (assuming they can help). @joesepi I know you helped with some past surveys, who at the Foundation do you think we should reach out to for help on the survey?
Co-authored-by: Geoffrey Booth <[email protected]>
|
I'm going to land this and we can PR in any follow on suggestions. |
A draft of the questions we should be asking in our survey.
Some questions are the same as last year, others are new and a few are curated based on last year result.
Of the part
What is important for you ? (Multiple choices)I used some of the choices from last year (especially the ones big the most answers) and added a few based on our cards from the Dublin Collaborator Summit