Add community health docs

Author: autarch

.github/FUNDING.yml

@@ -0,0 +1 @@
+github: autarch

CODE_OF_CONDUCT.md

@@ -0,0 +1,65 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers
+pledge to making participation in our project and our community a harassment-free experience for
+everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level
+of experience, education, socio-economic status, nationality, personal appearance, race, religion,
+or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit
+  permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are
+expected to take appropriate and fair corrective action in response to any instances of unacceptable
+behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits,
+code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or
+to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is
+representing the project or its community. Examples of representing a project or community include
+using an official project e-mail address, posting via an official social media account, or acting as
+an appointed representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting
+the project team at autarch@urth.org. All complaints will be reviewed and investigated and will
+result in a response that is deemed necessary and appropriate to the circumstances. The project team
+is obligated to maintain confidentiality with regard to the reporter of an incident. Further details
+of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face
+temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -0,0 +1,20 @@
+# Contributing
+
+Thank you for your interest in contributing to this project. This file contains instructions that
+will help you work with the source code.
+
+Please note that if you have any questions or difficulties, you can reach the maintainer through
+GitHub Issues. Filing an issue is the preferred method for reporting bugs or issues with the
+development tool configuration for this project.
+
+If you'd like to suggest a small change, you can do that by directly creating a
+[Pull Request](https://docs.github.com/en/pull-requests). For larger changes, you are encouraged to
+file an issue first, so we can discuss the change before you spend too much time implementing it.
+
+Please note that the maintainer, Dave Rolsky (@autarch), mostly works on his FOSS projects in his
+free time, which means on weekends and days off. However, he does not work on these things _every_
+weekend, so it may be a little while before you get a response to your issue or PR.
+
+If it's been more than 3 weeks since you submitted an issue or PR, feel free to comment on the
+submission to nudge the maintainer, who is probably getting sucked into some new video game and
+spending all his time there.

GOVERNANCE.md

@@ -0,0 +1,12 @@
+# Project Governance
+
+This repository works through the BDFL – Benevolent Dictator For Life - model. That means that a
+single maintainer, Dave Rolsky (@autarch), holds all of the admin keys and write access for this
+repository. Other users are encouraged to open issues, submit Pull Requests, and to ask for
+recognition as maintainers, but all decisions ultimately lie with the core maintainer.
+
+This maintainer is open to others joining on the admin team for this repository, but prospective
+admins will need a track record of contributions in the form of PRs and issue responses first.
+
+Please see the [CONTRIBUTING.md](CONTRIBUTING.md) file for more details on how to file issues and
+PRs for this project.

SECURITY.md

@@ -0,0 +1,9 @@
+# Reporting Security Issues
+
+To report a security issue, please use the GitHub Security Advisory "Report a Vulnerability" tab.
+
+The project maintainer(s) will send a response indicating the next steps in handling your report.
+After the initial reply to your report, the maintainer(s) will keep you informed of the progress
+towards a fix and full announcement, and may ask for additional information or guidance.
+
+Report security bugs in third-party packages to the person or team maintaining the package.

SUPPORT.md

@@ -0,0 +1,7 @@
+# How to file issues and get help
+
+This project uses GitHub Issues to track bugs and feature requests. Please search the existing
+issues before filing new issues to avoid duplicates. For new issues, file your bug or feature
+request as a new Issue.
+
+For help and questions about using this project, you can use GitHub Issues as well.