Skip to content

Home

Jump to bottom
Sabine Gillner edited this page Apr 15, 2025 · 13 revisions

Contributing to the Axon Ivy Market

Axon Ivy Banner - Mountain in Summer

🔄 Contributing new content to the Marketplace

Do you want to share your new product in the Axon Ivy Market?
Whether it's a connector, a demo of a smart Axon Ivy solution, or any other kind of software built with Axon Ivy — if it can be coded and wrapped in an Ivy project, it can become a market product! Then the following guide is for you.

It outlines the key steps needed to develop and publish your own market product and make it available to the community.

🚀 Guide Overview

  1. Project Setup
  2. Product Development
  3. Market Integration – This includes everything needed for adding new connectors.

🔄 Contributing to existing repositories the Marketplace

All contributions to existing Marketplace projects must be made via forks and pull requests.
Direct write access to the main branch is restricted. This ensures that every change is reviewed and documented properly.

Please follow the contribution guidelines when submitting a PR. If you have any questions, reach out to the relevant CODEOWNER (check the .github folder to find out who this is).

Roles and Responsibilities in the Marketplace Project

To ensure clear collaboration in the open-source Marketplace project, we define two key roles:

🧭 OWNER (PO Marketplace)

The OWNER is responsible for:

  • strategic direction of the project
  • managing the organization (e.g., roles and permissions)
  • defining processes and quality standards
  • setting priorities and coordinating with CODEOWNERS

🛠️ CODEOWNER

CODEOWNERS are responsible for specific parts of the repository. Their responsibilities include:

  • reviewing code changes within their assigned areas
  • ensuring compliance with coding standards
  • technical ownership of their components
  • providing feedback and support to contributors

Pull Requests that affect CODEOWNED files require explicit review and approval from the respective CODEOWNER.

💡 You can find the CODEOWNERS file in the .github folder of each repository. It defines which user(-group) is responsible for the codebase of the repository.

Clone this wiki locally