From b112e92e49a95a9bc05801bafd1ed773f98a66da Mon Sep 17 00:00:00 2001 From: Chris Gianelloni Date: Fri, 28 Feb 2025 18:48:32 -0500 Subject: [PATCH] docs: remove coc and codeowners in favor of global versions Signed-off-by: Chris Gianelloni --- CODE_OF_CONDUCT.md | 80 ---------------------------------------------- CONTRIBUTING.md | 63 ------------------------------------ 2 files changed, 143 deletions(-) delete mode 100644 CODE_OF_CONDUCT.md delete mode 100644 CONTRIBUTING.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index 639c0e8..0000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,80 +0,0 @@ -# Contributor Covenant Code of Conduct - -## Our Pledge - -We as members, contributors, and leaders 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, 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: - -* Demonstrating empathy and kindness toward other people -* Being respectful of differing opinions, viewpoints, and experiences -* Giving and gracefully accepting constructive feedback -* 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 -* Contacting individual members, contributors, or leaders privately, outside designated community mechanisms, without their explicit permission -* Other conduct which could reasonably be considered inappropriate 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. - -## Scope - -This Code of Conduct 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 e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at abuse@blinklabs.io. 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. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at . - -Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity). - -[homepage]: https://www.contributor-covenant.org - -For answers to common questions about this code of conduct, see the FAQ at . Translations are available at . diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index fa71ae9..0000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,63 +0,0 @@ -# Welcome to the Blink Labs contributing guide - -Thank you for investing your time in contributing to our project! - -Read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community -approachable and respectable. - -In this guide you will get an overview of the contribution workflow from -opening an issue, creating a PR, reviewing, and merging the PR. - -## Getting started - -To get an overview of the project, read the [README](README.md). Here are some -resources to help you get started with open source contributions: - -- [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) - -Blink Labs repositories use Conventional Commits for all commits. This defines -a standard format for commit messages across repositories and projects. - -- [CODEOWNERS](CODEOWNERS) - -Blink Labs repositories use CODEOWNERS files to provide information on who -should review a contribution. For repositories with regular outside -contributors, they will be listed within this file in the repository or -repositories which they maintain. - -
- -Contributions to open source come in many forms. You can contribute to Blink -Labs projects in several ways. - -### Issues - -#### Create a new issue - -If you spot a problem with a project, search if an issue already exists. If a -related issue doesn't exist, you can open a new issue in the repository. - -#### Solve an issue - -Scan through our existing issues to find one that interests you. You can narrow -down the search using `labels` as filters. As a general rule, we don’t assign -issues to anyone. If you find an issue to work on, you are welcome to open a PR -with a fix. - -### Pull Request - -When you're finished with the changes, create a pull request, also known as a -PR. -- Don't forget to -[link PR to issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) -if you are solving one. -- Enable the checkbox to -[allow maintainer edits](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) -so the branch can be updated for a merge. -Once you submit your PR, a Docs team member will review your proposal. We may -ask questions or request additional information. -- We may ask for changes to be made before a PR can be merged, either using -[suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) -or pull request comments. You can apply suggested changes directly through the -UI. You can make any other changes in your fork, then commit them to your -branch.