v3.8.0 - Announcing the conductor-community repo

[apanicker-nflx]

IMPORTANT

Move community contributed modules to conductor-community

---

This discussion was created from the release v3.8.0.

Purpose

Community

The number of community contributions, especially newer implementations of the core contracts in Conductor has increased over the past few years. We love that Conductor is finding use in many other organizations, and that these organizations are submitting these changes back to the community version of Conductor. There is interest in the community to contribute more implementations. To streamline the support and release of the existing community-contributed implementations and future ones, we are creating a new repository dedicated to hosting just contributions. Conductor users who wish to use a contributed module will have a dedicated place to ask questions directly to fellow members of the community.

Maintenance

This increase in engagement and growth of the community, while incredible, is a double edged sword. By no means does the Conductor team want to slow or limit these contributions, but the integration of third party implementations has been slower than we would like due to the team’s bandwidth.
This change allows us as maintainers to easily manage and direct Issues/PRs/Discussions across modules. All pluggable module-related items will be grouped together under one repository and the management of requests and release processes can be streamlined.

Support

Users looking for support can easily ask questions/raise issues. We can further aid the support requests using GitHub features (labels, templates, etc) to group together issues related to components and provide a better user experience to the community.

Build and Release

With all the community modules under the same repository, it becomes convenient to version control and trigger builds and releases as part of the main repo which triggers releases in this community modules repo.

Package Names

We will publish using the same package names to the same Maven coordinates - com.netflix.conductor

Governance model

This repository will be co-managed by both Orkes and Netflix. Responsibilities for managing PRs and issues will be shared between Netflix and Orkes and the Community members.

Please see ReadMe for the details on the modules and release details. You can also find FAQs that address the most common questions.