initial commit

Author: cmeissner

.gitignore

@@ -0,0 +1,141 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# IDE and editor files
+.vscode/

CHANGELOG.md

@@ -0,0 +1,14 @@
+# CHANGELOG
+
+All notable changes to this project will be documented in this file.
+This project adheres to [Semantic Versioning](http://semver.org/) and [Keep a Changelog](http://keepachangelog.com/).
+
+## Unreleased
+
+### New
+
+### Changes
+
+### Fixes
+
+### Breaks

CONTRIBUTING.md

@@ -0,0 +1,39 @@
+# How to contribute to click-types
+
+## Did you found a bug
+
+* Make sure the bug is not already opened by another user.
+
+* If you can't find an open issue which reflects your observed problem go ahead an [open a new bug](https://github.com/codeaffen/click-types/issues/new?assignees=&labels=bug&template=bug_report.md&title=).
+
+* Provide as much information as mentioned in the bug report template.
+
+## Did you wrote a patch for an open bug
+
+* Open new pull request containing the patch.
+
+* Provide a clear description which describes the problem and the solution. Link the existing bug to the PR.
+
+## Do you want to add a new feature
+
+* Make sure there isn't already a feature request.
+
+* If you can't find an open feature request which describe your feature idea or parts of it feel free to [open a new feature request](https://github.com/codeaffen/click-types/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=).
+
+* Suggest your feature idea within the created feature request.
+
+* Provide as much discribtion as possible to enable others to have a good understanding of what you are doing.
+
+* Point out that you want to start to work on the new feature
+
+## Do you wnat to contribute to documentation
+
+* Write you documentation change.
+
+* Open a PR with your change.
+
+* Discuss with the team about your changes.
+
+## Thank you for any contribution
+
+We will thank you for heed the contribution guidelines and we encourage you to contribute and join the team.