Remove project specific community health files (#309)

e511d62 · Jonatan Männchen · 2024-11-11 00:59

2 files +0 -111

Files changed

deleted CODE_OF_CONDUCT.md
+0 −77
@@ -1,77 +0,0 @@
1 −# Contributor Covenant Code of Conduct
2 −
3 −## Our Pledge
4 −
5 −In the interest of fostering an open and welcoming environment, we as
6 −contributors and maintainers pledge to making participation in our project and
7 −our community a harassment-free experience for everyone, regardless of age, body
8 −size, disability, ethnicity, sex characteristics, gender identity and expression,
9 −level of experience, education, socio-economic status, nationality, personal
10 −appearance, race, religion, or sexual identity and orientation.
11 −
12 −## Our Standards
13 −
14 −Examples of behavior that contributes to creating a positive environment
15 −include:
16 −
17 −- Using welcoming and inclusive language
18 −- Being respectful of differing viewpoints and experiences
19 −- Gracefully accepting constructive criticism
20 −- Focusing on what is best for the community
21 −- Showing empathy towards other community members
22 −
23 −Examples of unacceptable behavior by participants include:
24 −
25 −- The use of sexualized language or imagery and unwelcome sexual attention or
26 − advances
27 −- Trolling, insulting/derogatory comments, and personal or political attacks
28 −- Public or private harassment
29 −- Publishing others' private information, such as a physical or electronic
30 − address, without explicit permission
31 −- Other conduct which could reasonably be considered inappropriate in a
32 − professional setting
33 −
34 −## Our Responsibilities
35 −
36 −Project maintainers are responsible for clarifying the standards of acceptable
37 −behavior and are expected to take appropriate and fair corrective action in
38 −response to any instances of unacceptable behavior.
39 −
40 −Project maintainers have the right and responsibility to remove, edit, or
41 −reject comments, commits, code, wiki edits, issues, and other contributions
42 −that are not aligned to this Code of Conduct, or to ban temporarily or
43 −permanently any contributor for other behaviors that they deem inappropriate,
44 −threatening, offensive, or harmful.
45 −
46 −## Scope
47 −
48 −This Code of Conduct applies both within project spaces and in public spaces
49 −when an individual is representing the project or its community. Examples of
50 −representing a project or community include using an official project e-mail
51 −address, posting via an official social media account, or acting as an appointed
52 −representative at an online or offline event. Representation of a project may be
53 −further defined and clarified by project maintainers.
54 −
55 −## Enforcement
56 −
57 −Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 −reported by contacting the project team at
59 −[support@github.com](mailto:support@github.com). All complaints will be
60 −reviewed and investigated and will result in a response that is deemed
61 −necessary and appropriate to the circumstances. The project team is obligated
62 −to maintain confidentiality with regard to the reporter of an incident.
63 −Further details of specific enforcement policies may be posted separately.
64 −
65 −Project maintainers who do not follow or enforce the Code of Conduct in good
66 −faith may face temporary or permanent repercussions as determined by other
67 −members of the project's leadership.
68 −
69 −## Attribution
70 −
71 −This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
72 −available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
73 −
74 −[homepage]: https://www.contributor-covenant.org
75 −
76 −For answers to common questions about this code of conduct, see
77 −<https://www.contributor-covenant.org/faq>
deleted SECURITY.md
+0 −34
@@ -1,34 +0,0 @@
1 −# Security policy
2 −
3 −Thanks for helping make `setup-beam` safer for everyone.
4 −
5 −Find below updated information on our security policy.
6 −
7 −## Security
8 −
9 −We take the security of this software seriously.
10 −
11 −We don't implement a bug bounty program or bounty rewards, but will work with
12 −you to ensure that your findings get the appropriate handling.
13 −
14 −## Reporting Security Issues
15 −
16 −If you believe you have found a security vulnerability in this repository,
17 −please report it to <bryan.paxton@erlef.org>.
18 −
19 −Please do not report security vulnerabilities through public channels, like
20 −GitHub issues, discussions, or pull requests.
21 −
22 −Please include as much of the information listed below as you can to help us
23 −better understand and resolve the issue:
24 −
25 −- the type of issue (e.g., buffer overflow, SQL injection, or cross-site
26 − scripting)
27 −- full paths of source file(s) related to the manifestation of the issue
28 −- the location of the affected source code (tag/branch/commit or direct URL)
29 −- any special configuration required to reproduce the issue
30 −- step-by-step instructions to reproduce the issue
31 −- proof-of-concept or exploit code (if possible)
32 −- impact of the issue, including how an attacker might exploit the issue
33 −
34 −This information will help us triage your report more quickly.

Parents: 5304e04