TSC: Improving Community Experience (May 2021) #6813
hcgatewood
started this conversation in
Communications
Replies: 2 comments 4 replies
-
Thanks @hcgatewood for being a fantastic TSC chair and for this great summary. 🙏 |
Beta Was this translation helpful? Give feedback.
0 replies
-
the slack community invite does not work unless you have an email address from one of the following domains:
The documentation implies this is an open community - is this an oversight or is it intentional? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Improving Community Experience
Magma community experience was unpleasant and under-productive. We've been working to improve it.
Context
At the formation of the TSC, we identified two key areas where the community was experiencing pain points
To that end, we identified and landed updates to the community experience along 3 axes
💧 Streamline dev process
Pain points
Getting a PR merged requires two things: maintainer approvals and passing CI checks. Garnering sufficient approvals and passing required CI checks was a non-trivial task which authors were often unable to navigate.
Resolutions
Review process
approvers-*
teams)ready2merge
labelPR health
cloud_lint
style and static analysis for Orc8rCI health
session_manager_test
unit test session_managermme_test
unit test sctpd and mmecwag-build
build CWAG containersfeg-build
added a check for container crashloop📝 Document dev process + expectations
Pain points
Contributing to the Magma project is a non-trivial endeavor — it's a project with multiple languages, platforms, and applications, and requires hardware in the validation path.
Community contributors struggled to understand baseline development workflow and expectations around contributions.
Resolutions
General
Onboarding
Contributing
Maintaining
🎙 Publicize project resources
Pain points
While community-facing documentation now exists, it's still siloed in the Magma Docusaurus — which has 130 readme files at the time of this writing.
New community members don't know to sift through the documentation. Instead, we can bring the documentation to them at key touch points.
Resolutions
Conclusion
We're still looking to do more. Please follow up in comments on this post with your feedback, and ways we can improve the process of onboarding community members and communicating developer expectations.
Huge #thanks to @themarwhal and @electronjoe for their fantastic work in driving this effort forward. And big #thanks to @PARitter and Gale for advising and supporting the improvements!
And #thanksteam for pulling together to support the Magma community 💯🌟
Beta Was this translation helpful? Give feedback.
All reactions