diff --git a/CODEOWNERS b/CODEOWNERS deleted file mode 100644 index 9069743..0000000 --- a/CODEOWNERS +++ /dev/null @@ -1,5 +0,0 @@ -# Code Owners - -# The following individuals are designated as code owner(s) for specific files/directories in the repository: - -* @joostfaassen diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index abfe9d9..0000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,122 +0,0 @@ -## TL;DR - - -Be nice. Provide and accept constructive feedback. Avoid spamming, abusive, trolling, and otherwise unacceptable behavior. Repeat violations may result in a permanent ban. - -## Scope - -This Code of Conduct applies to all persons, including contributors, maintainers, end users, sponsors, etc., who interact with this project. It applies within all community spaces and also applies when -an individual is officially representing the community in public spaces. -Examples of representing our community include using an official email address, -posting via an official social media account, or acting as an appointed -representative at an online or offline event. - -## Our Pledge - -We as contributors, maintainers, end users, and sponsors of this project pledge to make participation in our -community a harassment-free experience for everyone, regardless of age, body -size, visible or invisible disability, ethnicity, sex characteristics, gender -identity and expression, level of experience, education, socio-economic status, -nationality, personal appearance, race, caste, color, religion, or sexual -identity and orientation. - -We pledge to act and interact in ways that contribute to an open, welcoming, -diverse, inclusive, and healthy community. - -## Our Standards - -Examples of behavior that contributes to a positive environment for our -community include: - -* Giving and gracefully accepting constructive feedback -* Being respectful of differing opinions, viewpoints, and experiences -* Demonstrating empathy and kindness toward other people -* Accepting responsibility and apologizing to those affected by our mistakes, - and learning from the experience -* Focusing on what is best not just for us as individuals, but for the overall - community - -Examples of unacceptable behavior include: - -* The use of sexualized language or imagery, and sexual attention or advances of - any kind -* Trolling, insulting or derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or email address, - without their explicit permission -* Spamming issues, pull requests, or community members -* Other conduct which could reasonably be considered inappropriate or unproductive in a - professional setting - -## Enforcement Responsibilities - -Community leaders are responsible for clarifying and enforcing our standards of -acceptable behavior and will take appropriate and fair corrective action in -response to any behavior that they deem inappropriate, threatening, offensive, -or harmful. - -Community leaders 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, and will communicate reasons for moderation -decisions when appropriate. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported to the maintainers or community leaders responsible for enforcement at [engineering@linkorb.com](mailto:engineering@linkorb.com). -All complaints will be reviewed and investigated promptly and fairly. - -All community leaders are obligated to respect the privacy and security of the -reporter of any incident. - -## Enforcement Guidelines - -Community leaders will follow these Community Impact Guidelines in determining -the consequences for any action they deem in violation of this Code of Conduct: - -### 1. Correction - -**Community Impact**: Use of inappropriate language or other behavior deemed -unprofessional or unwelcome in the community. - -**Consequence**: A private, written warning from community leaders, providing -clarity around the nature of the violation and an explanation of why the -behavior was inappropriate. A public apology may be requested. - -### 2. Warning - -**Community Impact**: A violation through a single incident or series of -actions. - -**Consequence**: A warning with consequences for continued behavior. No -interaction with the people involved, including unsolicited interaction with -those enforcing the Code of Conduct, for a specified period of time. This -includes avoiding interactions in community spaces as well as external channels -like social media. Violating these terms may lead to a temporary or permanent -ban. - -### 3. Temporary Ban - -**Community Impact**: A serious violation of community standards, including -sustained inappropriate behavior. - -**Consequence**: A temporary ban from any sort of interaction or public -communication with the community for a specified period of time. No public or -private interaction with the people involved, including unsolicited interaction -with those enforcing the Code of Conduct, is allowed during this period. -Violating these terms may lead to a permanent ban. - -### 4. Permanent Ban - -**Community Impact**: Demonstrating a pattern of violation of community -standards, including sustained inappropriate behavior, harassment of an -individual, or aggression toward or disparagement of classes of individuals. - -**Consequence**: A permanent ban from any sort of public interaction within the -community. - -## Credits - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], -version 2.1, available at -[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html). diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index 62f1b51..0000000 --- a/SECURITY.md +++ /dev/null @@ -1,24 +0,0 @@ - -envoi -============ - -### Reporting Security Vulnerabilities -We take the security of our software and systems very seriously, and we appreciate your help in identifying and disclosing any vulnerabilities that you may find. - -If you discover a security vulnerability, please report it to us as soon as possible by emailing us at security@linkorb.com. Please do not disclose the vulnerability publicly until we have had a chance to investigate and address it. Please provide us with as much detail as possible, including: - -* A detailed description of the vulnerability. -* Steps to reproduce the vulnerability. -* Any relevant screenshots, logs, or other supporting information. -* We will review your report as quickly as possible and will work to validate and address the issue. -* Your name and contact information (if you wish to be credited for the discovery) - -### Our Security Practices -* Regularly updating dependencies and libraries to address known security vulnerabilities -* Conducting regular security audits and code reviews -* Implementing secure coding practices and using secure development tools -* Keeping sensitive data (such as API keys or credentials) encrypted and protected -* Providing timely security updates and patches to address known vulnerabilities - -### Responsible Disclosure -We believe in responsible disclosure, and we ask that you do not disclose any details of a vulnerability that you have discovered until we have had a reasonable amount of time to address it. We will notify users of known vulnerabilities and the steps they should take to address them promptly. We will also publish a public advisory on our website and other relevant channels once a vulnerability has been confirmed and addressed.