Feature fraud detection 1.2.0

.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -0,0 +1,42 @@
+name: "\U0001F41B Bug Report"
+description: Submit a bug report to help us improve our tutorials
+labels:
+  - bug
+body:
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Description & Reproduction
+      description: |
+        Provide a short description of the problem you are facing and a numbered list of steps that one can follow
+        to reproduce this behavior.
+      placeholder: |
+        Provide a short description of the problem.
+
+        Steps to reproduce the behavior:
+
+          1.
+          2.
+          3.
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected behavior
+      description: "A clear and concise description of what you would expect to happen."
+      placeholder: "I would expect to..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: system-info
+    attributes:
+      label: System Info
+      description: Please share your system info with us. Always use code blocks to keep everything clean.
+      placeholder: |
+        - EzAF version: `1.0.0`
+        - Notebook image: `gcr.io/mapr-252711/kubeflow/notebooks/jupyter-data-science:ezaf-fy23-q3`
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/enhancement.yaml

@@ -0,0 +1,23 @@
+name: "\U00002728 Enhancement"
+description: Improve an existing tutorial/demo
+labels:
+  - enhancement
+body:
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: |
+        A clear and concise description of the enhancement proposal and why this is important.
+    validations:
+      required: true
+
+  - type: textarea
+    id: contribution
+    attributes:
+      label: Contribution
+      description: |
+        Is there any way that you could help, e.g. by submitting a PR?
+        Make sure to read the [contribution guidelines](https://github.com/HPEEzmeral/ezua-tutorials/blob/develop/CONTRIBUTING.md).
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature-request.yaml

@@ -0,0 +1,23 @@
+name: "\U0001F680 New tutorial/demo"
+description: Submit a proposal/request for a new tutorial/demo
+labels:
+  - enhancement
+body:
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: |
+        A clear and concise description of the proposal and why this is important.
+    validations:
+      required: true
+
+  - type: textarea
+    id: contribution
+    attributes:
+      label: Contribution
+      description: |
+        Is there any way that you could help, e.g. by submitting a PR?
+        Make sure to read the [contribution guidelines](https://github.com/HPEEzmeral/ezua-tutorials/blob/develop/CONTRIBUTING.md).
+    validations:
+      required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+Provide a clear and concise description of the content changes you're proposing. List all the changes you are making
+to the content.
+
+- Updated section ___ with ___.
+- Added new subsection ___ under ___.
+- Removed outdated information from ___.
+- ...
+
+Closes #...
+
+> If there is no issue related to this PR, kindly create one first to describe the motivation behind these changes.
+
+Checklist:
+
+- [ ] I have checked that my enhancements are not duplicates of existing content changes or additions.
+- [ ] I have tested the changes in a working environment to ensure they function as intended.
+- [ ] I have followed the [style guide](https://github.com/HPEEzmeral/ezua-tutorials/blob/develop/CONTRIBUTING.md#style-guide)
+      outlined in the contribution guidelines.
+
+Reviewer's Tasks (for maintainers reviewing this PR):
+
+- [ ] Verify that the tutorial functions correctly in a live environment.
+- [ ] Verify that the updated content aligns with the [style guide](https://github.com/HPEEzmeral/ezua-tutorials/blob/develop/CONTRIBUTING.md#style-guide)
+      in the contribution guidelines.
+- [ ] Check for consistency, grammar, and clarity throughout the updated content.
+- [ ] Check that the related GitHub issue is up-to-date.

.gitignore

@@ -1,10 +1,212 @@
+# Created by https://www.toptal.com/developers/gitignore/api/python,jupyternotebooks,spark
+# Edit at https://www.toptal.com/developers/gitignore?templates=python,jupyternotebooks,spark
+
 ### JupyterNotebooks ###
+# gitignore template for Jupyter Notebooks
+# website: http://jupyter.org/
+
 .ipynb_checkpoints
 */.ipynb_checkpoints/*
 
 # IPython
 profile_default/
 ipython_config.py
 
-# Idea
-.idea
+# Remove previous ipynb_checkpoints
+#   git rm -r .ipynb_checkpoints/
+
+### 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
+
+# Jupyter Notebook
+
+# IPython
+
+# 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/
+
+### Spark ###
+*#*#
+*.#*
+*.iml
+*.ipr
+*.iws
+*.pyc
+*.pyo
+*.swp
+*~
+.DS_Store
+.classpath
+.ensime
+.ensime_cache/
+.ensime_lucene
+.generated-mima*
+.idea/
+.idea_modules/
+.project
+.pydevproject
+.scala_dependencies
+.settings
+/lib/
+R-unit-tests.log
+R/unit-tests.out
+R/cran-check.out
+R/pkg/vignettes/sparkr-vignettes.html
+R/pkg/tests/fulltests/Rplots.pdf
+build/*.jar
+build/apache-maven*
+build/scala*
+build/zinc*
+cache
+checkpoint
+conf/*.cmd
+conf/*.conf
+conf/*.properties
+conf/*.sh
+conf/*.xml
+conf/java-opts
+conf/slaves
+dependency-reduced-pom.xml
+derby.log
+dev/create-release/*final
+dev/create-release/*txt
+dev/pr-deps/
+docs/_site
+docs/api
+sql/docs
+sql/site
+lib_managed/
+lint-r-report.log
+log/
+logs/
+out/
+project/boot/
+project/build/target/
+project/plugins/lib_managed/
+project/plugins/project/build.properties
+project/plugins/src_managed/
+project/plugins/target/
+python/lib/pyspark.zip
+python/deps
+python/test_coverage/coverage_data
+python/test_coverage/htmlcov
+python/pyspark/python
+reports/
+scalastyle-on-compile.generated.xml
+scalastyle-output.xml
+scalastyle.txt
+spark-*-bin-*.tgz
+spark-tests.log
+src_managed/
+streaming-tests.log
+unit-tests.log
+work/
+docs/.jekyll-metadata
+
+# For Hive
+TempStatsStore/
+metastore/
+metastore_db/
+sql/hive-thriftserver/test_warehouses
+warehouse/
+spark-warehouse/
+
+# End of https://www.toptal.com/developers/gitignore/api/python,jupyternotebooks,spark