kodurusivakumar34 commented on PR #41556: URL: https://github.com/apache/airflow/pull/41556#issuecomment-2295543149
@potiuk Thank you for your feedback on the pull request for the Magento provider. I understand the concerns raised and would like to address them with two proposed solutions: **Option 1: Separate Repository for Third-Party Providers** I propose creating a dedicated repository for third-party providers that are less central to the core Airflow functionality. This repository would serve as a central location where users can find and review all available third-party providers. It would also simplify the process for contributors to add new providers and for users to discover them. **Pros:** - Keeps the main Airflow repository focused on core providers. - Provides a single location for all third-party providers. - Simplifies contribution and discovery of third-party providers. **Cons:** - Users would need to check a separate repository for third-party providers. - Requires additional effort to maintain and coordinate updates across repositories. **Option 2: Separate Folder with Flag in `provider.yaml`** Alternatively, we could maintain third-party providers within a designated folder in the main repository and use a flag in the `provider.yaml` file to distinguish between core and third-party providers. This approach would keep everything within the main repository while clearly indicating the status and type of each provider. **Pros:** - Keeps all providers within a single repository for easier access. - Allows clear differentiation between core and third-party providers. - Immediate awareness of third-party providers through the `provider.yaml` flag. **Cons:** - Potential for increased clutter within the main repository. - Requires additional management for the flag system in `provider.yaml`. I am open to discussing these options further or considering any other recommendations the community may have. My goal is to contribute to Airflow in a way that aligns with best practices and meets the needs of the community. Thank you for your consideration. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
