Skip to content
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

BUG: update CONTRIBUTING with some community guidelines #293

Merged
merged 1 commit into from
Sep 15, 2020

Conversation

pcmoore
Copy link
Member

@pcmoore pcmoore commented Sep 10, 2020

An initial take of establishing some basic community guidelines and some maintainer rules for what to do when things go wrong. This generally isn't a problem for libseccomp so I'm trying to tread lightly here, but recent events had made it clear we need to be better prepared to handle issues relating to problematic individuals.

@drakenclimber please review and offer any comments, suggestions you may have.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.038% when pulling b42a1f5 on pcmoore:gh-289 into 558382e on seccomp:master.

Copy link
Member

@drakenclimber drakenclimber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me. Thanks for putting this together, @pcmoore

@@ -8,6 +8,20 @@ to the rules described here, but by following the instructions below you
should have a much easier time getting your work merged with the upstream
project.

## Interacting with the Community

> "Be excellent to each other." - *Bill S. Preston, Esq.*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: add a "Community Guidelines" section to CONTRIBUTING.md
3 participants