View the findings from our community survey (June 2024) #128571
jricciardi
announced in
Announcements
Replies: 5 comments 1 reply
This comment was marked as off-topic.
This comment was marked as off-topic.
-
good one |
Beta Was this translation helpful? Give feedback.
0 replies
This comment was marked as spam.
This comment was marked as spam.
-
One thing I forgot to write in the survey: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We love hearing from our members and we love sharing back what we learned from you from our surveys. Below is an infographic round-up of the key findings and most common feedback from the May-June 2024 Community survey!
Thank you again to every community member who participated! We do look at every single response and use this to inform some of our strategy going forward to make the GitHub Community Discussions the best they can be.
GitHub Community Sentiment Survey June 2024 Edition
Description
The infographic presents results from the Community Sentiment Survey conducted by community.github.com in June 2024. Key statistics and result commentary includes:
7,071 total community solutions
27 hour median time to solution
38 million page views over the past year
66% of respondents say that the space "Meets Expectations" and they have plenty of ideas on how to improve it.
The majority of community members, 76%, primarily visit the community to learn about new GitHub features or share feedback.
Regarding how people want to participate, the community is split between industry discussions (22.4%), networking & group projects (22.4%), challenges & hackathons (20.4%), AMAs (18.4%), and off-topic discussions (16.3%).
Things people like most include being able to help others, warm-hearted users & staff, and that GitHub helps them understand if a problem is known or if GitHub is not acting on it. Verbatim quotes from the survey responses include:
Areas for potential improvement include making the UI/homepage more accessible to users, making it easier to choose the right category names/terms, and frustrations around product feedback feeling unacknowledged by GitHub staff. Verbatim quotes from the survey responses include:
Thank you!
We plan on regularly running this survey to you so we can continuously improve your community experience. Be on the lookout!
Beta Was this translation helpful? Give feedback.
All reactions