From 3a2b142a9be473c697121f5ad05b014dc8ef7657 Mon Sep 17 00:00:00 2001 From: Jonatan Martens <40060128+JonatanMartens@users.noreply.github.com> Date: Tue, 29 Sep 2020 22:19:38 +0300 Subject: [PATCH] Revert "GitBook: [master] 16 pages modified" This reverts commit 37cfb0a086e7769615fe5ec1d466f4a75556a38a. --- .github/ISSUE_TEMPLATE/bug_report.md | 38 ++++++++++++ .github/ISSUE_TEMPLATE/feature_request.md | 20 ++++++ .github/PULL_REQUEST_TEMPLATE.md | 42 +++++++++++++ .github/README.md | 2 - .github/issue_template/README.md | 2 - .github/issue_template/bug_report.md | 33 ---------- .github/issue_template/feature_request.md | 18 ------ .github/pull_request_template.md | 36 ----------- CODE_OF_CONDUCT.md | 76 +++++++++++++++++++++++ contributing.md => CONTRIBUTING.md | 60 +++++++++++------- LICENSE.md | 21 +++++++ README.md | 50 ++++++++------- SUMMARY.md | 12 ---- code_of_conduct.md | 54 ---------------- license.md | 12 ---- 15 files changed, 261 insertions(+), 215 deletions(-) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md create mode 100644 .github/PULL_REQUEST_TEMPLATE.md delete mode 100644 .github/README.md delete mode 100644 .github/issue_template/README.md delete mode 100644 .github/issue_template/bug_report.md delete mode 100644 .github/issue_template/feature_request.md delete mode 100644 .github/pull_request_template.md create mode 100644 CODE_OF_CONDUCT.md rename contributing.md => CONTRIBUTING.md (50%) create mode 100644 LICENSE.md delete mode 100644 SUMMARY.md delete mode 100644 code_of_conduct.md delete mode 100644 license.md diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 00000000..dd84ea78 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,38 @@ +--- +name: Bug report +about: Create a report to help us improve +title: '' +labels: '' +assignees: '' + +--- + +**Describe the bug** +A clear and concise description of what the bug is. + +**To Reproduce** +Steps to reproduce the behavior: +1. Go to '...' +2. Click on '....' +3. Scroll down to '....' +4. See error + +**Expected behavior** +A clear and concise description of what you expected to happen. + +**Screenshots** +If applicable, add screenshots to help explain your problem. + +**Desktop (please complete the following information):** + - OS: [e.g. iOS] + - Browser [e.g. chrome, safari] + - Version [e.g. 22] + +**Smartphone (please complete the following information):** + - Device: [e.g. iPhone6] + - OS: [e.g. iOS8.1] + - Browser [e.g. stock browser, safari] + - Version [e.g. 22] + +**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 00000000..bbcbbe7d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,20 @@ +--- +name: Feature request +about: Suggest an idea for this project +title: '' +labels: '' +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. diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 00000000..64de1b4a --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,42 @@ +Description of PR... + +## Changes + +- Item 1 +- Item 2 + +## API Updates + +### New Features *(required)* + +This section should include details regarding new features added to the library. +This should include both open and private APIs. If including both, create two +sub headers underneath this one to label updates accordingly. + +### Deprecations *(required)* + +All deprecations should be listed here in order to ensure the reviewer understands +which sections of the codebase will affect contributors and users of the library. + +### Enhancements *(optional)* + +The enhancements section should include code updates that were included with this +pull request. This sections should detail refactoring that might have affected +other parts of the library. + +## Checklist + +- [ ] Unit tests +- [ ] Documentation + +## References + +(optional) + +Include __important__ links regarding the implementation of this PR. +This usually includes and RFC or an aggregation of issues and/or individual conversations +that helped put this solution together. This helps ensure there is a good aggregation +of resources regarding the implementation. + +Fixes #85, Fixes #22, Fixes username/repo#123 +Connects #123 diff --git a/.github/README.md b/.github/README.md deleted file mode 100644 index c41e0e04..00000000 --- a/.github/README.md +++ /dev/null @@ -1,2 +0,0 @@ -# .github - diff --git a/.github/issue_template/README.md b/.github/issue_template/README.md deleted file mode 100644 index 266a81c3..00000000 --- a/.github/issue_template/README.md +++ /dev/null @@ -1,2 +0,0 @@ -# ISSUE\_TEMPLATE - diff --git a/.github/issue_template/bug_report.md b/.github/issue_template/bug_report.md deleted file mode 100644 index 2dea673e..00000000 --- a/.github/issue_template/bug_report.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -name: Bug report -about: Create a report to help us improve -title: '' -labels: '' -assignees: '' ---- - -# bug\_report - -**Describe the bug** A clear and concise description of what the bug is. - -**To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error - -**Expected behavior** A clear and concise description of what you expected to happen. - -**Screenshots** If applicable, add screenshots to help explain your problem. - -**Desktop \(please complete the following information\):** - -* OS: \[e.g. iOS\] -* Browser \[e.g. chrome, safari\] -* Version \[e.g. 22\] - -**Smartphone \(please complete the following information\):** - -* Device: \[e.g. iPhone6\] -* OS: \[e.g. iOS8.1\] -* Browser \[e.g. stock browser, safari\] -* Version \[e.g. 22\] - -**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 deleted file mode 100644 index a141e81b..00000000 --- a/.github/issue_template/feature_request.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -name: Feature request -about: Suggest an idea for this project -title: '' -labels: '' -assignees: '' ---- - -# feature\_request - -**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. - diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md deleted file mode 100644 index 6437e0ed..00000000 --- a/.github/pull_request_template.md +++ /dev/null @@ -1,36 +0,0 @@ -# PULL\_REQUEST\_TEMPLATE - -Description of PR... - -## Changes - -* Item 1 -* Item 2 - -## API Updates - -### New Features _\(required\)_ - -This section should include details regarding new features added to the library. This should include both open and private APIs. If including both, create two sub headers underneath this one to label updates accordingly. - -### Deprecations _\(required\)_ - -All deprecations should be listed here in order to ensure the reviewer understands which sections of the codebase will affect contributors and users of the library. - -### Enhancements _\(optional\)_ - -The enhancements section should include code updates that were included with this pull request. This sections should detail refactoring that might have affected other parts of the library. - -## Checklist - -* [ ] Unit tests -* [ ] Documentation - -## References - -\(optional\) - -Include **important** links regarding the implementation of this PR. This usually includes and RFC or an aggregation of issues and/or individual conversations that helped put this solution together. This helps ensure there is a good aggregation of resources regarding the implementation. - -Fixes \#85, Fixes \#22, Fixes username/repo\#123 Connects \#123 - diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000..ecae3731 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,76 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, 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. + +## Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and unwelcome sexual attention or + advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic + address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project maintainers 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, or to ban temporarily or +permanently any contributor for other behaviors that they deem inappropriate, +threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at jonatanmartenstav@gmail.com. All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see +https://www.contributor-covenant.org/faq diff --git a/contributing.md b/CONTRIBUTING.md similarity index 50% rename from contributing.md rename to CONTRIBUTING.md index a45904c8..c6d8e7a0 100644 --- a/contributing.md +++ b/CONTRIBUTING.md @@ -1,36 +1,36 @@ # Contributing -When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change. +When contributing to this repository, please first discuss the change you wish to make via issue, +email, or any other method with the owners of this repository before making a change. Please note we have a code of conduct, please follow it in all your interactions with the project. ## Pull Request Process 1. Ensure any install or build dependencies are removed before the end of the layer when doing a - build. - 2. Update the README.md with details of changes to the interface, this includes new environment - variables, useful file locations etc. - 3. Increase the version numbers in any examples files and the README.md to the new version that this - Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/). - 4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you - do not have permission to do that, you may request the second reviewer to merge it for you. ## Code of Conduct ### Our Pledge -In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, gender identity and expression, level of experience, +nationality, personal appearance, race, religion, or sexual identity and +orientation. ### Our Standards -Examples of behavior that contributes to creating a positive environment include: +Examples of behavior that contributes to creating a positive environment +include: * Using welcoming and inclusive language * Being respectful of differing viewpoints and experiences @@ -41,36 +41,52 @@ Examples of behavior that contributes to creating a positive environment include Examples of unacceptable behavior by participants include: * The use of sexualized language or imagery and unwelcome sexual attention or - - advances - +advances * Trolling, insulting/derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or electronic - address, without explicit permission - * Other conduct which could reasonably be considered inappropriate in a - professional setting ### Our Responsibilities -Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. -Project maintainers 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. +Project maintainers 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, or to ban temporarily or +permanently any contributor for other behaviors that they deem inappropriate, +threatening, offensive, or harmful. ### Scope -This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. ### Enforcement -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at \[INSERT EMAIL ADDRESS\]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at [INSERT EMAIL ADDRESS]. All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. -Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. ### Attribution -This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, available at [http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4/) +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at [http://contributor-covenant.org/version/1/4][version] +[homepage]: http://contributor-covenant.org +[version]: http://contributor-covenant.org/version/1/4/ diff --git a/LICENSE.md b/LICENSE.md new file mode 100644 index 00000000..cbd3d6ef --- /dev/null +++ b/LICENSE.md @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2020 Jonatan Martens + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/README.md b/README.md index c5fcebe0..4d816721 100644 --- a/README.md +++ b/README.md @@ -1,27 +1,33 @@ -# README +[![Coverage Status](https://coveralls.io/repos/github/JonatanMartens/pyzeebe/badge.svg?branch=master)](https://coveralls.io/github/JonatanMartens/pyzeebe?branch=master) +![Test pyzeebe](https://github.com/JonatanMartens/pyzeebe/workflows/Test%20pyzeebe/badge.svg) +![Integration test pyzeebe](https://github.com/JonatanMartens/pyzeebe/workflows/Integration%20test%20pyzeebe/badge.svg) +![GitHub issues](https://img.shields.io/github/issues-raw/JonatanMartens/pyzeebe) +![GitHub pull requests](https://img.shields.io/github/issues-pr-raw/JonatanMartens/pyzeebe) +![GitHub closed pull requests](https://img.shields.io/github/issues-pr-closed-raw/JonatanMartens/pyzeebe) +![GitHub tag (latest by date)](https://img.shields.io/github/v/tag/JonatanMartens/pyzeebe) +![PyPI - Python Version](https://img.shields.io/pypi/pyversions/pyzeebe) +![PyPI](https://img.shields.io/pypi/v/pyzeebe) -[![Coverage Status](https://coveralls.io/repos/github/JonatanMartens/pyzeebe/badge.svg?branch=master)](https://coveralls.io/github/JonatanMartens/pyzeebe?branch=master) ![Test pyzeebe](https://github.com/JonatanMartens/pyzeebe/workflows/Test%20pyzeebe/badge.svg) ![Integration test pyzeebe](https://github.com/JonatanMartens/pyzeebe/workflows/Integration%20test%20pyzeebe/badge.svg) ![GitHub issues](https://img.shields.io/github/issues-raw/JonatanMartens/pyzeebe) ![GitHub pull requests](https://img.shields.io/github/issues-pr-raw/JonatanMartens/pyzeebe) ![GitHub closed pull requests](https://img.shields.io/github/issues-pr-closed-raw/JonatanMartens/pyzeebe) ![GitHub tag \(latest by date\)](https://img.shields.io/github/v/tag/JonatanMartens/pyzeebe) ![PyPI - Python Version](https://img.shields.io/pypi/pyversions/pyzeebe) ![PyPI](https://img.shields.io/pypi/v/pyzeebe) -## Pyzeebe +# Pyzeebe pyzeebe is a python grpc client for Zeebe. Zeebe version support: | Pyzeebe version | Tested Zeebe versions | -| :---: | :--- | -| 2.x.x | 0.23, 0.24 | -| 1.x.x | 0.23, 0.24 | - -### Getting Started +|:---------------:|----------------| +| 2.x.x | 0.23, 0.24 | +| 1.x.x | 0.23, 0.24 | +## Getting Started To install: `pip install pyzeebe` -### Usage +## Usage -#### Worker +### Worker The `ZeebeWorker` class uses threading to get and run jobs. @@ -49,13 +55,12 @@ worker.work() # Now every time that a task with type example is called example_t ``` Stop a worker: - ```python zeebe_worker.work() # Worker will begin working -zeebe_worker.stop() # Stops worker after all running jobs have been completed +zeebe_worker.stop() # Stops worker after all running jobs have been completed ``` -#### Client +### Client ```python from pyzeebe import ZeebeClient @@ -78,25 +83,22 @@ zeebe_client.cancel_workflow_instance(workflow_instance_key=12345) # Publish message zeebe_client.publish_message(name="message_name", correlation_key="some_id") -``` -### Tests +``` +## Tests Use the package manager [pip](https://pip.pypa.io/en/stable/) to install pyzeebe - + `pytest tests/unit` -### Contributing - +## Contributing Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Please make sure to update tests as appropriate. -### Versioning - -We use [SemVer](https://github.com/JonatanMartens/pyzeebe/tree/4202906527cd989ac80ba738dbb81f20ebf58ff0/semver.org) for versioning. For the versions available, see the tags on this repository. - -### License -We use the MIT license, see [LICENSE.md](license.md) for details +## Versioning +We use [SemVer](semver.org) for versioning. For the versions available, see the tags on this repository. +## License +We use the MIT license, see [LICENSE.md](LICENSE.md) for details \ No newline at end of file diff --git a/SUMMARY.md b/SUMMARY.md deleted file mode 100644 index 2cbe4c51..00000000 --- a/SUMMARY.md +++ /dev/null @@ -1,12 +0,0 @@ -# Table of contents - -* [README](README.md) -* [LICENSE](license.md) -* [.github](.github/README.md) - * [ISSUE\_TEMPLATE](.github/issue_template/README.md) - * [feature\_request](.github/issue_template/feature_request.md) - * [bug\_report](.github/issue_template/bug_report.md) - * [PULL\_REQUEST\_TEMPLATE](.github/pull_request_template.md) -* [Contributor Covenant Code of Conduct](code_of_conduct.md) -* [Contributing](contributing.md) - diff --git a/code_of_conduct.md b/code_of_conduct.md deleted file mode 100644 index 202842eb..00000000 --- a/code_of_conduct.md +++ /dev/null @@ -1,54 +0,0 @@ -# Contributor Covenant Code of Conduct - -## Our Pledge - -In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, 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. - -## Our Standards - -Examples of behavior that contributes to creating a positive environment include: - -* Using welcoming and inclusive language -* Being respectful of differing viewpoints and experiences -* Gracefully accepting constructive criticism -* Focusing on what is best for the community -* Showing empathy towards other community members - -Examples of unacceptable behavior by participants include: - -* The use of sexualized language or imagery and unwelcome sexual attention or - - advances - -* Trolling, insulting/derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or electronic - - address, without explicit permission - -* Other conduct which could reasonably be considered inappropriate in a - - professional setting - -## Our Responsibilities - -Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. - -Project maintainers 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. - -## Scope - -This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at jonatanmartenstav@gmail.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. - -Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html) - -For answers to common questions about this code of conduct, see [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq) - diff --git a/license.md b/license.md deleted file mode 100644 index a46be351..00000000 --- a/license.md +++ /dev/null @@ -1,12 +0,0 @@ -# LICENSE - -MIT License - -Copyright \(c\) 2020 Jonatan Martens - -Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files \(the "Software"\), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -