Initial commit

Signed-off-by: Pierre-Samuel Le Stang <[email protected]>

Author: pslestang

.gitignore

@@ -0,0 +1,176 @@
+# Created by https://www.toptal.com/developers/gitignore/api/python
+# Edit at https://www.toptal.com/developers/gitignore?templates=python
+
+### Python ###
+# 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
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__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/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+### Python Patch ###
+# Poetry local configuration file - https://python-poetry.org/docs/configuration/#local-configuration
+poetry.toml
+
+# ruff
+.ruff_cache/
+
+# LSP config files
+pyrightconfig.json
+
+# End of https://www.toptal.com/developers/gitignore/api/python

AUTHORS

@@ -0,0 +1,14 @@
+# This is the official list of Tygenie authors for copyright purposes.
+# This file is distinct from the CONTRIBUTORS files
+# and it lists the copyright holders only.
+
+# Names should be added to this file as one of
+# Organization's name
+# Individual's name <submission email address>
+# Individual's name <submission email address> <email2> <emailN>
+# See CONTRIBUTORS for the meaning of multiple email addresses.
+
+# Please keep the list sorted.
+#
+
+OVH SAS

CONTRIBUTING.md

@@ -0,0 +1,73 @@
+# Contributing to Tygenie
+
+This project accepts contributions. In order to contribute, you should
+pay attention to a few things:
+
+1. your code must follow the coding style rules
+2. your code must be unit-tested
+3. your code must be documented
+4. your work must be signed (see below)
+5. you may contribute through GitHub Pull Requests
+
+# Coding and documentation Style
+
+- The coding style follows `PEP-8: Style Guide for Python Code <http://www.python.org/dev/peps/pep-0008/>`\_ (~100 chars/lines is a good limit)
+- The documentation style follows `PEP-257: Docstring Conventions <http://www.python.org/dev/peps/pep-0257/>`\_
+
+A good practice is to frequently run you code through `pylint <http://www.pylint.org/>`\_ and make sure the code grades does not decrease.
+
+# Submitting Modifications
+
+The contributions should be submitted through Github Pull Requests
+and follow the DCO which is defined below.
+
+# Licensing for new files
+
+Tygenie is licensed under the Apache License, Version 2.0. Anything
+contributed to Tygenie must be released under this license.
+
+When introducing a new file into the project, please make sure it has a
+copyright header making clear under which license it's being released.
+
+# Developer Certificate of Origin (DCO)
+
+To improve tracking of contributions to this project we will use a
+process modeled on the modified DCO 1.1 and use a "sign-off" procedure
+on patches that are being emailed around or contributed in any other
+way.
+
+The sign-off is a simple line at the end of the explanation for the
+patch, which certifies that you wrote it or otherwise have the right
+to pass it on as an open-source patch. The rules are pretty simple:
+if you can certify the below:
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I have
+the right to submit it under the open source license indicated in
+the file; or
+
+(b) The contribution is based upon previous work that, to the best of
+my knowledge, is covered under an appropriate open source License
+and I have the right under that license to submit that work with
+modifications, whether created in whole or in part by me, under
+the same open source license (unless I am permitted to submit
+under a different license), as indicated in the file; or
+
+(c) The contribution was provided directly to me by some other person
+who certified (a), (b) or (c) and I have not modified it.
+
+(d) The contribution is made free of any other party's intellectual
+property claims or rights.
+
+(e) I understand and agree that this project and the contribution are
+public and that a record of the contribution (including all
+personal information I submit with it, including my sign-off) is
+maintained indefinitely and may be redistributed consistent with
+this project or the open source license(s) involved.
+
+then you just add a line saying
+
+    Signed-off-by: Random J Developer <[email protected]>
+
+using your real name (sorry, no pseudonyms or anonymous contributions.)

CONTRIBUTORS

@@ -0,0 +1,7 @@
+# This is the official list of people who can contribute
+# (and typically have contributed) code to the TyGenie repository.
+
+Pierre-Samuel Le Stang <[email protected]>
+Arnaud Morin <[email protected]>
+Clement Contini <[email protected]>
+Julien Le Jeune <[email protected]>