meta: public roadmap and user feedback public beta

[MylesBorins]

Summary

npm can mean many things: the cli, the registry, the website, and the team. There are various types of feedback that we can receive that can focus on any number or combination of meanings of “npm”. In order to ensure ongoing customer / ecosystem satisfaction we should have clear and reliable avenues to receive feedback and respond accordingly.

During the beta preview we will being onboarding external developers from the JavaScript community.

Intended Outcome

• The JavaScript community believes that npm and GitHub are listening
• The JavaScript community has faith in npm and GitHub as stewards of the registry
• A transparent and reliable process that gives insight into our decision making process
• Our products continue to improve and solve the problems of the JavaScript ecosystem

How will it work?

GitHub Discussion will be utilized as a platform for receiving this feedback which will be organized on an official npm public roadmap. This process will allow us to show our existing priorities and transparency in which suggested features are selected to be worked on and why. This aligns with the overall GitHub strategy for feedback.

The npm team will aim to respond to all feedback within 7 days. All discussions should be eventually rolled up into a meta issue that will either describe the feature we will be working on or a transparent answer as to why we will not be exploring that specific feature.

[MylesBorins]

Update: October 6th

After deliberation with the team we have decided to delay the launch of the npm feedback process + roadmap. We are releasing npm v7.0.0 next week and want to release the new process in tandem or after the 7.0.0 release.

We will be solidifying the launch plans this week.

[MylesBorins]

We are live!