diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index bbbcfb9..0000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,144 +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 -- 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 -artur.barseghyan@gmail.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. - -Attribution ------------ - -This Code of Conduct is adapted from the `Contributor -Covenant `__, version 2.0, -available at -https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. - -Community Impact Guidelines were inspired by `Mozilla’s code of conduct -enforcement ladder `__. - -For answers to common questions about this code of conduct, see the FAQ -at https://www.contributor-covenant.org/faq. Translations are available -at https://www.contributor-covenant.org/translations. diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 120000 index 0000000..398bf55 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1 @@ +CODE_OF_CONDUCT.rst \ No newline at end of file diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index 6a0d3a1..0000000 --- a/SECURITY.md +++ /dev/null @@ -1,32 +0,0 @@ -Security Policy -=============== -Reporting a Vulnerability -------------------------- -**Do not report security issues on GitHub!** - -Please report security issues by emailing Artur Barseghyan -. - -Supported Versions ------------------- -**Make sure to use the latest version.** - -The two most recent ``faker-file`` release series receive security support. - -For example, during the development cycle leading to the release -of ``faker-file`` 0.11.x, support will be provided for ``faker-file`` 0.10.x. - -Upon the release of ``faker-file`` 0.12.x, security support for ``faker-file`` -0.10.x will end. - -.. code-block:: text - - ┌─────────────────┬────────────────┐ - │ Version │ Supported │ - ├─────────────────┼────────────────┤ - │ 0.11.x │ Yes │ - ├─────────────────┼────────────────┤ - │ 0.10.x │ Yes │ - ├─────────────────┼────────────────┤ - │ < 0.10 │ No │ - └─────────────────┴────────────────┘ diff --git a/SECURITY.md b/SECURITY.md new file mode 120000 index 0000000..a407bf3 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1 @@ +SECURITY.rst \ No newline at end of file