Home

Contributing to the Axon Ivy Market

🔄 Contributing new content to the Marketplace

Do you want to share your new product in the Axon Ivy Market?

Whether it's a connector to another 3rd-party-system, a demo of a smart Axon Ivy solution, or any other kind of utility implemented with Axon Ivy — if it can be coded and wrapped in an Ivy project, it can become a market extension!

The following guide outlines the key steps needed to develop and publish a brand new market extension and make it available to the community.

🚀 Guide Overview

1. Project Setup
2. Product Development
3. Market Integration

🔄 Contributing to existing repositories the Marketplace

All contributions to existing Marketplace artefacts 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 the following key roles:

🙌 CONTRIBUTOR

Contributors benefit in several ways when participating in the community. They gain visibility and recognition, get early access and deeper insights into the platform, and can help shape the direction of the project. They also receive valuable feedback from experienced developers and strengthen their portfolio with real-world contributions.

CONTRIBUTORS can support the project in various ways, such as:

• fixing bugs and improving existing features
• adding new functionality
• writing or enhancing documentation
• developing new Market Extensions
• sharing feedback and ideas through discussions or issues

🛠️ 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
• code maintenance (e.g., release updates for their components)
• handling incidents
• implementing change requests

🧭 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
• getting feedback from stakeholders
• facilitating community contributions and engagement

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.