First iteration of the rewrite

Signed-off-by: Bernat Gabor <[email protected]>

Author: gaborbernat

.github/CODEOWNERS

@@ -0,0 +1 @@
+*       @gaborbernat @asottile @obestwalter

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,10 @@
+---
+name: Bug report
+about: Something that does not works as expected
+title: ""
+labels: bug:normal
+assignees: ''
+
+---
+
+When submitting a bug make sure you can reproduce it via ``tox -rvv`` and attach the output of that to the bug. Ideally, you should also submit a project that allows easily reproducing the bug. Thanks!

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,10 @@
+---
+name: Feature request
+about: Suggest an improvement for the project
+title: ""
+labels: feature:new
+assignees: ''
+
+---
+
+Describe what improvement you want and how would this be used. Thanks!

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+## Thanks for contributing a pull request!
+
+If you are contributing for the first time or provide a trivial fix don't worry too
+much about the checklist - we will help you get started.
+
+## Contribution checklist:
+
+(also see [CONTRIBUTING.rst](../tree/master/CONTRIBUTING.rst) for details)
+
+- [ ] wrote descriptive pull request text
+- [ ] added/updated test(s)
+- [ ] updated/extended the documentation
+- [ ] added relevant [issue keyword](https://help.github.com/articles/closing-issues-using-keywords/)
+      in message body
+- [ ] added news fragment in [changelog folder](../tree/master/docs/changelog)
+  * fragment name: `<issue number>.<type>.rst` for example (588.bugfix.rst)
+  * `<type>` is must be one of `bugfix`, `feature`, `deprecation`,`breaking`, `doc`, `misc`
+  * if PR has no issue: consider creating one first or change it to the PR number after creating the PR
+  * "sign" fragment with "by :user:`<your username>`"
+  * please use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files - by :user:`superuser`."
+  * also see [examples](../tree/master/docs/changelog)
+- [ ] added yourself to `CONTRIBUTORS` (preserving alphabetical order)

.github/config.yml

@@ -0,0 +1,5 @@
+chronographer:
+  enforce_name:
+    suffix: .rst
+rtd:
+  project: tox

.gitignore

@@ -0,0 +1,31 @@
+# python
+*.pyc
+*.pyo
+*.swp
+__pycache__
+
+
+# packaging folders
+/src/tox/version.py
+/build/
+/dist/
+/src/tox.egg-info
+
+# tox working folder
+/.tox
+
+# IDEs
+/.idea
+/.vscode
+
+# tools
+/.*_cache
+
+# documentation
+/docs/_draft.rst
+
+# release
+credentials.json
+
+pip-wheel-metadata
+.DS_Store

.pre-commit-config.yaml

@@ -0,0 +1,48 @@
+repos:
+-   repo: https://github.com/psf/black
+    rev: 19.10b0
+    hooks:
+    -   id: black
+        args: [--safe]
+        language_version: python3.8
+-   repo: https://github.com/asottile/blacken-docs
+    rev: v1.6.0
+    hooks:
+    -   id: blacken-docs
+        additional_dependencies: [black==19.10b0]
+        language_version: python3.8
+-   repo: https://github.com/asottile/seed-isort-config
+    rev: v2.1.0
+    hooks:
+    -   id: seed-isort-config
+        args: [--application-directories, "src:."]
+-   repo: https://github.com/pre-commit/mirrors-isort
+    rev: v4.3.21
+    hooks:
+    -   id: isort
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v2.5.0
+    hooks:
+    -   id: trailing-whitespace
+    -   id: end-of-file-fixer
+    -   id: check-yaml
+    -   id: debug-statements
+    -   id: flake8
+        additional_dependencies: ["flake8-bugbear == 20.1.4"]
+        language_version: python3.8
+-   repo: https://github.com/asottile/pyupgrade
+    rev: v2.1.0
+    hooks:
+    -   id: pyupgrade
+-   repo: https://github.com/pre-commit/pygrep-hooks
+    rev: v1.5.1
+    hooks:
+    -   id: rst-backticks
+-   repo: local
+    hooks:
+    -   id: changelogs-rst
+        name: changelog filenames
+        language: fail
+        entry: 'changelog files must be named ####.(bugfix|feature|deprecation|breaking|doc|misc).rst'
+        exclude: ^docs/changelog/(\d+\.(bugfix|feature|deprecation|breaking|doc|misc).rst|README.rst|template.jinja2)
+        files: ^docs/changelog/

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# 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, 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:
+
+* 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 [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems 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][version]
+
+[homepage]: https://www.contributor-covenant.org/
+[version]: https://www.contributor-covenant.org/version/1/4/