[jira] [Commented] (AIRFLOW-299) Evaluate a plugin architecture to replace contrib

["Sergio Kef (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940126#comment-16940126 ] 

Sergio Kef commented on AIRFLOW-299:
------------------------------------

I would agree to remove "extras" from airflow and keep the core scheduler. That said, there is already AIP-21 [https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-21%3A+Changes+in+import+paths] which decides on merging the contrib with the main modules.

I think this ticket can close, and a new AIP can be created if one feels like proposing a new restructuring

> Evaluate a plugin architecture to replace contrib
> -------------------------------------------------
>
>                 Key: AIRFLOW-299
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-299
>             Project: Apache Airflow
>          Issue Type: Task
>          Components: contrib
>            Reporter: Dan Davydov
>            Priority: Minor
>              Labels: contrib
>
> We should take a look at the usefulness of a plugin architecture similar to tools like Jenkins for the contrib folder. This way we can delegate/scale committers for contrib, keep the git history/repo size/tests of the repo smaller, allow users to publish operators without waiting for their commits to be merged by a committer etc.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)