zenml-nightly 0.55.0.dev20240124__py3-none-any.whl → 0.72.0.dev20250116__py3-none-any.whl

{zenml_nightly-0.55.0.dev20240124.dist-info → zenml_nightly-0.72.0.dev20250116.dist-info}/WHEEL

@@ -1,4 +1,4 @@
 Wheel-Version: 1.0
-Generator: poetry-core 1.8.1
+Generator: poetry-core 2.0.1
 Root-Is-Purelib: true
 Tag: py3-none-any

CLA.md

@@ -1,110 +0,0 @@
-# Fiduciary License Agreement 2.0
-based on the
-## Individual Contributor Exclusive License Agreement
-(including the Traditional Patent License OPTION)
-
-Thank you for your interest in contributing to ZenML by ZenML GmbH ("We" or "Us").
-
-The purpose of this contributor agreement ("Agreement") is to clarify and document the rights granted by contributors to Us. To make this document effective, please follow the instructions at https://zenml.io/cla/.
-
-### 0. Preamble
-Software is deeply embedded in all aspects of our lives and it is important that it empower, rather than restrict us. Free Software gives everybody the rights to use, understand, adapt and share software. These rights help support other fundamental freedoms like freedom of speech, press and privacy.
-
-Development of Free Software can follow many patterns. In some cases whole development is handled by a sole programmer or a small group of people. But usually, the creation and maintenance of software is a complex process that requires the contribution of many individuals. This also affects who owns the rights to the software. In the latter case, rights in software are owned jointly by a great number of individuals.
-
-To tackle this issue some projects require a full copyright assignment to be signed by all contributors. The problem with such assignments is that they often lack checks and balances that would protect the contributors from potential abuse of power from the new copyright holder.
-
-FSFE’s Fiduciary License Agreement (FLA) was created by the Free Software Foundation Europe e.V. with just that in mind – to concentrate all deciding power within one entity and prevent fragmentation of rights on one hand, while on the other preventing that single entity from abusing its power. The main aim is to ensure that the software covered under the FLA will forever remain Free Software.
-
-This process only serves for the transfer of economic rights. So-called moral rights (e.g. authors right to be identified as author) remain with the original author(s) and are inalienable.
-
-How to use this FLA
-If You are an employee and have created the Contribution as part of your employment, You need to have Your employer approve this Agreement or sign the Entity version of this document. If You do not own the Copyright in the entire work of authorship, any other author of the Contribution should also sign this – in any event, please contact Us at support@zenml.io
-
-### 1. Definitions
-"You" means the individual Copyright owner who Submits a Contribution to Us.
-
-"Contribution" means any original work of authorship, including any original modifications or additions to an existing work of authorship, Submitted by You to Us, in which You own the Copyright.
-
-"Copyright" means all rights protecting works of authorship, including copyright, moral and neighboring rights, as appropriate, for the full term of their existence.
-
-"Material" means the software or documentation made available by Us to third parties. When this Agreement covers more than one software project, the Material means the software or documentation to which the Contribution was Submitted. After You Submit the Contribution, it may be included in the Material.
-
-"Submit" means any act by which a Contribution is transferred to Us by You by means of tangible or intangible media, including but not limited to electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, Us, but excluding any transfer that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
-
-"Documentation" means any non-software portion of a Contribution.
-
-### 2. License grant
-#### 2.1 Copyright license to Us
-Subject to the terms and conditions of this Agreement, You hereby grant to Us a worldwide, royalty-free, exclusive, perpetual and irrevocable (except as stated in Section 8.2) license, with the right to transfer an unlimited number of non-exclusive licenses or to grant sublicenses to third parties, under the Copyright covering the Contribution to use the Contribution by all means, including, but not limited to:
-
-publish the Contribution,
-modify the Contribution,
-prepare derivative works based upon or containing the Contribution and/or to combine the Contribution with other Materials,
-reproduce the Contribution in original or modified form,
-distribute, to make the Contribution available to the public, display and publicly perform the Contribution in original or modified form.
-#### 2.2 Moral rights
-Moral Rights remain unaffected to the extent they are recognized and not waivable by applicable law. Notwithstanding, You may add your name to the attribution mechanism customary used in the Materials you Contribute to, such as the header of the source code files of Your Contribution, and We will respect this attribution when using Your Contribution.
-
-#### 2.3 Copyright license back to You
-Upon such grant of rights to Us, We immediately grant to You a worldwide, royalty-free, non-exclusive, perpetual and irrevocable license, with the right to transfer an unlimited number of non-exclusive licenses or to grant sublicenses to third parties, under the Copyright covering the Contribution to use the Contribution by all means, including, but not limited to:
-
-publish the Contribution,
-modify the Contribution,
-prepare derivative works based upon or containing the Contribution and/or to combine the Contribution with other Materials,
-reproduce the Contribution in original or modified form,
-distribute, to make the Contribution available to the public, display and publicly perform the Contribution in original or modified form.
-This license back is limited to the Contribution and does not provide any rights to the Material.
-
-### 3. Patents
-#### 3.1 Patent license
-Subject to the terms and conditions of this Agreement You hereby grant to Us and to recipients of Materials distributed by Us a worldwide, royalty-free, non-exclusive, perpetual and irrevocable (except as stated in Section 3.2) patent license, with the right to transfer an unlimited number of non-exclusive licenses or to grant sublicenses to third parties, to make, have made, use, sell, offer for sale, import and otherwise transfer the Contribution and the Contribution in combination with any Material (and portions of such combination). This license applies to all patents owned or controlled by You, whether already acquired or hereafter acquired, that would be infringed by making, having made, using, selling, offering for sale, importing or otherwise transferring of Your Contribution(s) alone or by combination of Your Contribution(s) with any Material.
-
-#### 3.2 Revocation of patent license
-You reserve the right to revoke the patent license stated in section 3.1 if We make any infringement claim that is targeted at your Contribution and not asserted for a Defensive Purpose. An assertion of claims of the Patents shall be considered for a "Defensive Purpose" if the claims are asserted against an entity that has filed, maintained, threatened, or voluntarily participated in a patent infringement lawsuit against Us or any of Our licensees.
-
-### 4. License obligations by Us
-We agree to (sub)license the Contribution or any Materials containing, based on or derived from your Contribution under the terms of any licenses the Free Software Foundation classifies as Free Software License and which are approved by the Open Source Initiative as Open Source licenses.
-
-More specifically and in strict accordance with the above paragraph, we agree to (sub)license the Contribution or any Materials containing, based on or derived from the Contribution only under the terms of the following license(s) Apache-2.0 (including any right to adopt any future version of a license if permitted).
-
-We agree to license patents owned or controlled by You only to the extent necessary to (sub)license Your Contribution(s) and the combination of Your Contribution(s) with the Material under the terms of any licenses the Free Software Foundation classifies as Free Software licenses and which are approved by the Open Source Initiative as Open Source licenses..
-
-### 5. Disclaimer
-THE CONTRIBUTION IS PROVIDED "AS IS". MORE PARTICULARLY, ALL EXPRESS OR IMPLIED WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OF SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT ARE EXPRESSLY DISCLAIMED BY YOU TO US AND BY US TO YOU. TO THE EXTENT THAT ANY SUCH WARRANTIES CANNOT BE DISCLAIMED, SUCH WARRANTY IS LIMITED IN DURATION AND EXTENT TO THE MINIMUM PERIOD AND EXTENT PERMITTED BY LAW.
-
-### 6. Consequential damage waiver
-TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL YOU OR WE BE LIABLE FOR ANY LOSS OF PROFITS, LOSS OF ANTICIPATED SAVINGS, LOSS OF DATA, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL AND EXEMPLARY DAMAGES ARISING OUT OF THIS AGREEMENT REGARDLESS OF THE LEGAL OR EQUITABLE THEORY (CONTRACT, TORT OR OTHERWISE) UPON WHICH THE CLAIM IS BASED.
-
-### 7. Approximation of disclaimer and damage waiver
-IF THE DISCLAIMER AND DAMAGE WAIVER MENTIONED IN SECTION 5. AND SECTION 6. CANNOT BE GIVEN LEGAL EFFECT UNDER APPLICABLE LOCAL LAW, REVIEWING COURTS SHALL APPLY LOCAL LAW THAT MOST CLOSELY APPROXIMATES AN ABSOLUTE WAIVER OF ALL CIVIL OR CONTRACTUAL LIABILITY IN CONNECTION WITH THE CONTRIBUTION.
-
-### 8. Term
-#### 8.1 This Agreement shall come into effect upon Your acceptance of the terms and conditions.
-
-#### 8.2 This Agreement shall apply for the term of the copyright and patents licensed here. However, You shall have the right to terminate the Agreement if We do not fulfill the obligations as set forth in Section 4. Such termination must be made in writing.
-
-#### 8.3 In the event of a termination of this Agreement Sections 5., 6., 7., 8., and 9. shall survive such termination and shall remain in full force thereafter. For the avoidance of doubt, Free and Open Source Software (sub)licenses that have already been granted for Contributions at the date of the termination shall remain in full force after the termination of this Agreement.
-
-### 9. Miscellaneous
-#### 9.1 This Agreement and all disputes, claims, actions, suits or other proceedings arising out of this agreement or relating in any way to it shall be governed by the laws of Germany excluding its private international law provisions.
-
-#### 9.2 This Agreement sets out the entire agreement between You and Us for Your Contributions to Us and overrides all other agreements or understandings.
-
-#### 9.3 In case of Your death, this agreement shall continue with Your heirs. In case of more than one heir, all heirs must exercise their rights through a commonly authorized person.
-
-#### 9.4 If any provision of this Agreement is found void and unenforceable, such provision will be replaced to the extent possible with a provision that comes closest to the meaning of the original provision and that is enforceable. The terms and conditions set forth in this Agreement shall apply notwithstanding any failure of essential purpose of this Agreement or any limited remedy to the maximum extent possible under law.
-
-#### 9.5 You agree to notify Us of any facts or circumstances of which you become aware that would make this Agreement inaccurate in any respect.
-
-**You**  
-Date:_______________________________    
-Name:_______________________________   
-Title:______________________________  
-Address:____________________________    
-
-**Us**  
-Date:_______________________________   
-Name:_______________________________   
-Title:_______________________________  
-Address:_______________________________    

CODE-OF-CONDUCT.md

@@ -1,132 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible 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.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders 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, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[support@zenml.io](mailto:support@zenml.io).
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
-
-Community Impact Guidelines were inspired by 
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available 
-at [https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/inclusion
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -1,260 +0,0 @@
-# 🧑‍💻 Contributing to ZenML
-
-A big welcome and thank you for considering contributing to ZenML! It’s people
-like you that make it a reality for users
-in our community.
-
-Reading and following these guidelines will help us make the contribution
-process easy and effective for everyone
-involved. It also communicates that you agree to respect the developers' time
-management and develop these open-source projects. In return, we will reciprocate that respect by reading your
-issue, assessing changes, and helping
-you finalize your pull requests.
-
-## ⚡️ Quicklinks
-
-- [🧑‍💻 Contributing to ZenML](#-contributing-to-zenml)
-  - [⚡️ Quicklinks](#-quicklinks)
-  - [🧑‍⚖️ Code of Conduct](#-code-of-conduct)
-  - [🛫 Getting Started](#-getting-started)
-    - [⁉️ Issues](#-issues)
-    - [🏷 Pull Requests: When to make one](#-pull-requests-when-to-make-one)
-    - [💯 Pull Requests: Workflow to Contribute](#-pull-requests-workflow-to-contribute)
-    - [🧱 Pull Requests: Rebase on develop](#-pull-requests-rebase-your-branch-on-develop)
-    - [🧐 Linting, formatting, and tests](#-linting-formatting-and-tests)
-    - [🚨 Reporting a Vulnerability](#-reporting-a-vulnerability)
-  - [Coding Conventions](#coding-conventions)
-  - [👷 Creating a new Integration](#-creating-a-new-integration)
-  - [🆘 Getting Help](#-getting-help)
-
-## 🧑‍⚖️ Code of Conduct
-
-We take our open-source community seriously and hold ourselves and other
-contributors to high standards of communication.
-By participating and contributing to this project, you agree to uphold
-our [Code of Conduct](https://github.com/zenml-io/zenml/blob/master/CODE-OF-CONDUCT.md)
-.
-
-## 🛫 Getting Started
-
-Contributions are made to this repo via Issues and Pull Requests (PRs). A few
-general guidelines that cover both:
-
-- To report security vulnerabilities, please get in touch
-  at [support@zenml.io](mailto:support@zenml.io), monitored by
-  our security team.
-- Search for existing Issues and PRs before creating your own.
-- We work hard to make sure issues are handled on time, but it could take a
-  while to investigate the root cause depending on the impact.
-
-A friendly ping in the comment thread to the submitter or a contributor can help
-draw attention if your issue is blocking.
-
-### Good First Issues for New Contributors
-
-The best way to start is to check the
-[`good-first-issue`](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Azenml-io+label%3A%22good+first+issue%22)
-label on the issue board. The core team creates these issues as necessary
-smaller tasks that you can work on to get deeper into ZenML internals. These
-should generally require relatively simple changes, probably affecting just one
-or two files which we think are ideal for people new to ZenML.
-
-The next step after that would be to look at the
-[`good-second-issue`](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Azenml-io+label%3A%22good+second+issue%22)
-label on the issue board. These are a bit more complex, might involve more
-files, but should still be well-defined and achievable to people relatively new
-to ZenML.
-
-### ⁉️ Issues
-
-Issues should be used to report problems with the library, request a new
-feature, or to discuss potential changes before
-a PR is created. When you create a new Issue, a template will be loaded that
-will guide you through collecting and
-providing the information we need to investigate.
-
-If you find an Issue that addresses your problem, please add your own
-reproduction information to the
-existing issue rather than creating a new one. Adding
-a [reaction](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
-can also help by
-indicating to our maintainers that a particular issue is affecting more than
-just the reporter.
-
-### 🏷 Pull Requests: When to make one
-
-Pull Requests (PRs) to ZenML are always welcome and can be a quick way to get your fix or
-improvement slated for the next release. In
-general, PRs should:
-
-- Only fix/add the functionality in question **OR** address widespread
-  whitespace/style issues, not both.
-- Add unit or integration tests for fixed or changed functionality (if a test
-  suite already exists).
-- Address a single concern in the least number of changed lines as possible.
-- Include documentation in the repo or in your Pull Request.
-- Be accompanied by a filled-out Pull Request template (loaded automatically when
-  a PR is created).
-
-For changes that address core functionality or would require breaking changes (e.g. a major release), it's best to open
-an Issue to discuss your proposal first. This is not required but can save time
-creating and reviewing changes.
-
-### 💯 Pull Requests: Workflow to Contribute
-
-<p class="callout warning">Please note that development in ZenML happens off of the <b>develop</b> branch, <b>not main</b>, 
-which is the default branch on GitHub. Therefore, please pay particular attention to step 5 and step 9 below. </p>
-
-In general, we follow
-the ["fork-and-pull" Git workflow](https://github.com/susam/gitpr)
-
-1. Review and sign
-   the [Contributor License Agreement](https://cla-assistant.io/zenml-io/zenml) (
-   CLA).
-2. Fork the repository to your own Github account.
-3. Clone the project to your machine.
-4. Checkout the **develop** branch <- `git checkout develop`.
-5. Create a branch (again, off of the develop branch) locally with a succinct but descriptive name.
-6. Commit changes to the branch
-7. Follow the `Linting, formatting, and tests` guide to make sure your code adheres to the ZenML coding style (see below).
-8. Push changes to your fork.
-9. Open a PR in our repository (to the `develop` branch, **NOT** `main`) and
-   follow the PR template so that we can efficiently review the changes.
-
-### 🧱 Pull Requests: Rebase Your Branch on Develop
-
-1. When making pull requests to ZenML, you should always make your changes on a branch that is based on `develop`. You can create a new branch based on `develop` by running the following command:
-   ```
-   git checkout -b <new-branch-name> develop
-   ```
-2. Fetch the latest changes from the remote `develop` branch:
-   ```
-   git fetch origin develop
-   ```
-3. Switch to your branch:
-   ```
-   git checkout <your-branch-name>
-   ```
-4. Rebase your branch on `develop`:
-   ```
-   git rebase origin/develop
-   ```
-   This will apply your branch's changes on top of the latest changes in `develop`, one commit at a time.
-5. Resolve any conflicts that may arise during the rebase. Git will notify you if there are any conflicts that need to be resolved. Use a text editor to manually resolve the conflicts in the affected files.
-6. After resolving the conflicts, stage the changes:
-   ```
-   git add .
-   ```
-7. Continue the rebase for all of your commits and go to 5) if there are conflicts.
-   ```
-   git rebase --continue
-   ```
-8. Push the rebased branch to your remote repository:
-   ```
-   git push origin --force <your-branch-name>
-   ```
-9. Open a pull request targeting the `develop` branch. The changes from your rebased branch will now be based on the latest `develop` branch.
-
-### 🧐 Linting, formatting, and tests
-
-To install ZenML from your local checked out files including all core dev-dependencies, run:
-
-```
-pip install -e ".[server,dev]"
-```
-
-Optionally, you might want to run the following commands to ensure you have all
-integrations for `mypy` checks:
-
-```
-zenml integration install -y -i feast
-pip install click~=8.0.3
-mypy --install-types
-```
-
-Warning: This might take a while for both (~ 15 minutes each, depending on your machine), however if you have
-time, please run it as it will make the
-next commands error-free. Note that the `zenml integration install` command
-might also fail on account of dependency conflicts so you can just install the
-specific integration you're working on and manually run the mypy command for the
-files you've been working on.
-
-You can now run the following scripts to automatically format your
-code and to check whether the code formatting, linting, docstrings, and
-spelling is in order:
-
-```
-bash scripts/format.sh
-bash scripts/run-ci-checks.sh
-```
-
-If you're on Windows you might have to run the formatting script as `bash
-scripts/format.sh --no-yamlfix` and run the yamlfix command separately as
-`yamlfix .github -v`.
-
-Tests can be run as follows:
-
-```
-bash scripts/test-coverage-xml.sh
-```
-
-Please note that it is good practice to run the above commands before submitting
-any Pull Request: The CI GitHub Action
-will run it anyway, so you might as well catch the errors locally!
-
-### 🚨 Reporting a Vulnerability
-
-Please refer to [our security / reporting instructions](./SECURITY.md) for
-details on reporting vulnerabilities.
-
-
-## Coding Conventions
-
-The code within the repository is structured in the following way - 
-the most relevant places for contributors are highlighted with a `<-` arrow:
-
-```
-├── .github           -- Definition of the GH action workflows
-├── docker            -- Dockerfiles used to build ZenML docker images
-├── docs              <- The ZenML docs, CLI docs and API docs live here
-│   ├── book          <- In case you make user facing changes, update docs here
-│   └── mkdocs        -- Some configurations for the API/CLI docs
-├── examples          <- When adding an integration, add an example here
-├── scripts           -- Scripts used by Github Actions or for local linting/testing
-├── src/zenml         <- The heart of ZenML
-│   ├── <stack_component>   <- Each stack component has its own directory 
-│   ├── cli                 <- Change and improve the CLI here
-│   ├── config              -- The ZenML config methods live here
-│   ├── integrations        <- Add new integrations here
-│   ├── io                  -- File operation implementations
-│   ├── materializers       <- Materializers responsible for reading/writing artifacts
-│   ├── pipelines           <- The base pipeline and its decorator
-│   ├── services            -- Code responsible for managing services
-│   ├── stack               <- Stack, Stack Components and the flavor registry
-│   ├── steps               <- Steps and their decorators are defined here
-│   ├── utils               <- Collection on useful utils
-│   ├── zen_server          -- Code for running the Zen Server
-│   └── zen_stores          -- Code for storing stacks in multiple settings
-└── test              <- Don't forget to write unit tests for your code
-```
-
-## 👷 Creating a new Integration
-
-In case you want to create an entirely new integration that you would like to 
-see supported by ZenML there are a few steps that you should follow:
-
-1. Create the actual integration. Check out the 
-[Integrations README](src/zenml/integrations/README.md)
-for detailed step-by-step instructions.
-2. Create an example of how to use the integration. Check out the 
-[Examples README](examples/README.md) 
-to find out what to do.
-3. All integrations deserve to be documented. Make sure to pay a visit to the
-[Component Guide](https://docs.zenml.io/stacks-and-components/component-guide)
-in the docs and add your implementations. 
-
-## 🆘 Getting Help
-
-Join us in the [ZenML Slack Community](https://zenml.io/slack-invite/) to 
-interact directly with the core team and community at large. This is a good 
-place to ideate, discuss concepts or ask for help.