diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md deleted file mode 100644 index 91cf9ffc..00000000 --- a/.github/pull_request_template.md +++ /dev/null @@ -1,22 +0,0 @@ -# Pull request - -## Proposed changes - - - -## Types of changes - - - -- [ ] New feature (non-breaking change which adds functionality). -- [ ] Enhancement (non-breaking change which enhances functionality) -- [ ] Bug Fix (non-breaking change which fixes an issue). -- [ ] Breaking change (fix or feature that would cause existing functionality to change). - -## Checklist - - - -- [ ] I have read the **[README](./README.md)** document. -- [ ] My change requires a change to the documentation. -- [ ] I have updated the documentation accordingly. diff --git a/CHANGELOG.md b/CHANGELOG.md deleted file mode 100644 index 1d013ff9..00000000 --- a/CHANGELOG.md +++ /dev/null @@ -1,6 +0,0 @@ -# Changelog - -All notable changes to this project will be documented in this file. - -The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), -and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index 912492f7..00000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,128 +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 -wbaldoumas.github@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][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. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index c2a4fd16..00000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,15 +0,0 @@ -# Contributing - -When contributing to this repository, please first discuss the change you wish to make via an [issue](https://github.com/wbaldoumas/coding-blog/issues). - -Please read the [code of conduct](CODE_OF_CONDUCT.md) and follow it in all your interactions with the project. - -## Pull Request Process - -1. Ensure any local development artifacts are removed (or appropriately added to `.gitignore`) before pushing your feature branch to remote and creating a pull request. -2. Fill out the pull request template with details on the proposed changes and testing performed. -3. You may merge the pull request once all required status checks have passed and you have sign-off from an approved reviewer. - -## Deployment - -After merging your pull request, create and push a new tag to trigger a deployment. Be sure to increase the version numbers in any examples files and the README.md to the new version that these changes would represent. The versioning scheme used is [SemVer](http://semver.org/). diff --git a/README.md b/README.md index 81103aa7..729aed22 100644 --- a/README.md +++ b/README.md @@ -10,29 +10,3 @@ A coding blog. Check it out [here](https://wbaldoumas.codes/)! [![Maintainability](https://api.codeclimate.com/v1/badges/9189fd933b39c21a49bb/maintainability)](https://codeclimate.com/github/wbaldoumas/coding-blog/maintainability) [![Coverage Status](https://coveralls.io/repos/github/wbaldoumas/coding-blog/badge.svg?branch=main)](https://coveralls.io/github/wbaldoumas/coding-blog?branch=main) - -## Support - -This project is maintained by [@wbaldoumas](https://github.com/wbaldoumas). Please understand that individual support via email will not be provided. Assistance is much more valuable if it is shared publicly, so that more people can benefit from it. - -| Type | Platforms | -| ------------------------------------- | -------------------------------------------------------------------- | -| 🚨 **Bug Reports** | [GitHub Issue Tracker](https://github.com/wbaldoumas/coding-blog/issues) | -| 🎁 **Feature Requests** | [GitHub Issue Tracker](https://github.com/wbaldoumas/coding-blog/issues) | -| 🛡 **Report Security Vulnerability** | [GitHub Issue Tracker](https://github.com/wbaldoumas/coding-blog/issues) | - -## Contributing - -Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on the code of conduct, and the process for submitting pull requests. - -## Versioning - -Use [SemVer](http://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/wbaldoumas/coding-blog/tags). - -## Authors and acknowledgment - -See also the list of [contributors](https://github.com/wbaldoumas/coding-blog/graphs/contributors) who participated in this project. - -## License - -This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index 543fea12..00000000 --- a/SECURITY.md +++ /dev/null @@ -1,27 +0,0 @@ -# Security Policy - - - -## Reporting a Vulnerability - - - -Please use the [GitHub Issue Tracker](https://github.com/wbaldoumas/coding-blog/issues) to report vulnerabilities.