From b7a911cd9a95b799959502ae06f87f5bda953d5f Mon Sep 17 00:00:00 2001 From: Vitaliy Ukiru <33477790+vitaliy-ukiru@users.noreply.github.com> Date: Fri, 29 Sep 2023 23:58:00 +0500 Subject: [PATCH 1/5] docs: add code of conduct Signed-off-by: Vitaliy Ukiru <33477790+vitaliy-ukiru@users.noreply.github.com> --- CODE_OF_CONDUCT.md | 128 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..9052689 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# 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 +create new issues with tag maintainer and prefix "report" . +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 +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](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 +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. From c60f3fd9a87e1a19b41b3a6673ed30f04302f239 Mon Sep 17 00:00:00 2001 From: Vitaliy Ukiru <33477790+vitaliy-ukiru@users.noreply.github.com> Date: Sat, 30 Sep 2023 00:09:09 +0500 Subject: [PATCH 2/5] docs: add security policy (version 1) NEED TO APPEND: reporting section Signed-off-by: Vitaliy Ukiru <33477790+vitaliy-ukiru@users.noreply.github.com> --- SECURITY.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..b9e9ff8 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,17 @@ +# Security Policy + +## Supported Versionses. +At current moment supported only last minor version and v1.2. + +| Version | Supported | +| ------- | ------------------ | +| 1.2.x | :white_check_mark: | +| < 1.2 | :x: | + +## Reporting a Vulnerability + +Use this section to tell people how to report a vulnerability. + +Tell them where to go, how often they can expect to get an update on a +reported vulnerability, what to expect if the vulnerability is accepted or +declined, etc. From 751b635291e410803c9ae4d850b45705063c2a1b Mon Sep 17 00:00:00 2001 From: Vitaliy Ukiru <33477790+vitaliy-ukiru@users.noreply.github.com> Date: Thu, 5 Oct 2023 20:00:31 +0500 Subject: [PATCH 3/5] docs(github): added simple issues templates --- .github/ISSUE_TEMPLATE/bug_report.md | 23 +++++++++++++++++++++++ .github/ISSUE_TEMPLATE/feature_request.md | 20 ++++++++++++++++++++ 2 files changed, 43 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 0000000..2f7821d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,23 @@ +--- +name: Bug report +about: Create a report to help us improve +title: bug +labels: bug +assignees: '' + +--- + +**Describe the bug** +A clear and concise description of what the bug is. + +**Expected behavior** +A clear and concise description of what you expected to happen. + +**Machine (please complete the following information):** + - OS: [e.g. Windows] + - Go [e.g. go 1.21.0] +- Telebot [e.g. v3.1.3] + - Version [e.g. v1.3] + +**Additional context** +Add any other context about the problem here. diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 0000000..31a85a9 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,20 @@ +--- +name: Feature request +about: Suggest an idea for this project +title: feat +labels: enhancement +assignees: '' + +--- + +**Is your feature request related to a problem? Please describe.** +A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] + +**Describe the solution you'd like** +A clear and concise description of what you want to happen. + +**Describe alternatives you've considered** +A clear and concise description of any alternative solutions or features you've considered. + +**Additional context** +Add any other context or screenshots about the feature request here. From 2c817f635791121a0e2028f23ec6426588e92ea9 Mon Sep 17 00:00:00 2001 From: Vitaliy Ukiru <33477790+vitaliy-ukiru@users.noreply.github.com> Date: Tue, 4 Jun 2024 23:34:17 +0500 Subject: [PATCH 4/5] docs(SECURITY): change version policy --- SECURITY.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index b9e9ff8..bfe1f40 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -1,12 +1,16 @@ # Security Policy -## Supported Versionses. -At current moment supported only last minor version and v1.2. +## Supported Versions +At current moment full support presents only for v2.x + +For v1.3.x will release only bug-fixes and possible +service updates for support work. | Version | Supported | -| ------- | ------------------ | -| 1.2.x | :white_check_mark: | -| < 1.2 | :x: | +|---------|--------------------| +| 2.x | :white_check_mark: | +| 1.3.x | :white_check_mark: | +| < 1.3 | :x: | ## Reporting a Vulnerability From 9ee47addda0f610443dee63879fc80501969e3b8 Mon Sep 17 00:00:00 2001 From: Vitaliy Ukiru <33477790+vitaliy-ukiru@users.noreply.github.com> Date: Tue, 4 Jun 2024 23:43:23 +0500 Subject: [PATCH 5/5] docs(SECURITY): fill reporting section --- SECURITY.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index bfe1f40..a07eaf4 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -14,8 +14,9 @@ service updates for support work. ## Reporting a Vulnerability -Use this section to tell people how to report a vulnerability. +You can report on vulnerability via issues +or in PM in telegram (link in my profile). -Tell them where to go, how often they can expect to get an update on a -reported vulnerability, what to expect if the vulnerability is accepted or -declined, etc. +I'm always monitors activity in my repository. +Estimated response time is less than 48 hours. +This time may be increased due to some factors. \ No newline at end of file