-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Determine what a realistic foundation/cpc review process could look like #982
Comments
I've always through that an NPS survey to the projects with a few simple questions in terms of the value they get from the Foundation would be a useful value to track. It would be a quantifiable datapoint that could be used to get feedback from the projects and to track if the value perceived by the projects is going up/down each year (hopefull up :)). |
as an aside, I've always found NPS to be pretty useless - its only value seems to be that it's something quantifiable, but everyone who's ever done a few can instantly recognize one, which makes them easy to game and hard to get a representative sample. |
@ljharb i agree you need to be careful in how you use them, but I think they are still useful and relatively easy to implement and many organizations get value from having the data they provide. If we can do something better that's great but I'd prefer having NPS values versus nothing or waiting for a long time to get something better. |
We discussed in the CPC meeting today. I think we mentioned that we'd send the nps survey to the "leads" for each project. For example in the Node.js project the TSC. |
Doc to work on questions created by @lukeschantz https://docs.google.com/document/d/1WEWB_ZcwUAXGX7uAe2jXk2HviuN5ep6Dq9mopy0seUA/edit?usp=sharing |
We decided to aim for a survey in the fall and work back from there once we have more bandwidth. |
Closing in favor of #1253 |
This has been a goal since early days of the foundation as evidenced by the issues below. Let's discuss what is realistic now that we have been doing this for a while.
You can find more context and commentary in the following issues, which I will now close in favor of this new issue:
#592
#676
#677
The text was updated successfully, but these errors were encountered: