-
Notifications
You must be signed in to change notification settings - Fork 6
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
Audit barriers to contribution #67
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
The general rule is to keep barriers to contribution as low as possible in the context. That means, it is understood that if the context is a contribution requires root access to a server, there needs to be a high barrier to make that kind of contribution in that way.
For this issue, a general audit or survey can be conducted to determine the current barriers to contribution across the project. Then a punchlist of items to improve is created. It is understood that lowering barriers is usually an evolving process over time, rather than a one-time overnight experience.
The text was updated successfully, but these errors were encountered: