Next-10 next survey

[sheplu]

Following the last meeting we want to to check multiples points from the initiative

• What's have we done from the first survey (I will do a list that will be easier)

Key Priorities
    Modern HTTP
    Suitable types for end-users
    ESM
    Documentation
    Web Assembly
    Up to date ES JavaScript Support
    Observability
    Permissions/policies/security model
    Better multithreaded support
    Single Binary

• Should we work on the topics we disregarded last year ?

Watch List
    QUIC
    Serverless

review others feedbacks from previous community survey: https://easyretro.io/publicboard/cLBIBu3wA2Um7qIziXq1zmC4gdi1/1db5ea23-fee3-4da0-bb7b-a5ea49d810e7?sort=votes

Do we also want to discuss about the constituency needs ? https://github.com/nodejs/next-10/blob/main/CONSTITUENCY-NEEDS.md

• What key topics contributors want to work on (internal survey)

Old PR #16
https://user-images.githubusercontent.com/4048656/106966137-95bccb80-66f9-11eb-860c-cd6fe7d82790.png

• Propose a survey for all to gather new feedback and check with current / active initiatives

Should we do the same processus as the first survey (05/2021) to ask for contributor first then for community ?
Same or others questions ?

• Find good proposal of topics / dates to send the survey

[sheplu]

Some ideas of questions for the survey. I think it should be a bit different / maybe two part:

• is the effort useful / did people saw results
• questions like a year ago to see the main initiatives

We did work on this list of topic with this current state for each https://github.com/nodejs/next-10/blob/main/TECHNICAL_PRIORITY_WORKING_SUMMARY.md (i will add some color with the result of the sub level initiative - i am not sure yet how to present that correctly maybe a slide ?)

    Modern HTTP
    Suitable types for end-users
    ESM
    Documentation
    Web Assembly
    Up to date ES JavaScript Support
    Observability
    Permissions/policies/security model
    Better multithreaded support
    Single Binary

---

From last year community survey https://easyretro.io/publicboard/cLBIBu3wA2Um7qIziXq1zmC4gdi1/1db5ea23-fee3-4da0-bb7b-a5ea49d810e7?sort=votes
What did we not handled ?

• Node.js Features

Native bundle support (linked to the new SEA group?)
FIPs support
Node-API (bit of discussion during web assembly?)
better installer / binary management (something we will see in the SEA group?)
Current / alternative SSL support 
AOT
Iteration of policies

• Technology trend

Serverless 
Tracing (tooling seems to become more and more complex)
permission / policies (deno like)
graphql / grpc (first citizen?)
ci/cd automation
prometheus style metrics
secure software bill of material
precompilation
IoT
cryptocurrency
zero knowledge (doc??)
object capability (OCAP)
Ecosystem maintenance

[sheplu]

Some questions in mind for the community survey

• Which constituencies do you identify with?
• Are you part of a constituency not covered ?
• If not covered what are you part with ? (open question)
• what need do you have not covered ? (open question)

I suggest we add more questions

• localization / continent / country
• time working with Node.js
• What's your use case of Node.js
• Any recurrent issue with Node.js ? (open question)
• Are you part/following some working groups

Easy retro with the same categories as last year (I think they were great)

• Technical trends
• Node.js Feature
• Other area

[sheplu]

Here is a list of the questions we could be asking for this year survey

Personal question

• Which constituencies do you identify with?
• Are you part of a constituency not covered ?
• If not covered what are you part with ? (open question)
• localization / continent / country
• time working with Node.js
• currently working / where ? (big tech, company, startup, student)

Tech questions

• what's important for you (reuse same list as last year)
• What's your use case of Node.js
• Any recurrent issue with Node.js ? (open question)
• Are you part/following some working groups
• what need do you have not covered ? (open question)

Can we also use easy retro to curate a list of priorities and allow people to just vote (not add some new card) ?

[sheplu]

Todo:

• filtering the results
• publish the result in this repo
• discuss and call to action

[mhdawson]

Reviewed last meeting, good data, closing.