You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2016/06/30 20:18:10 UTC
[jira] [Commented] (AIRFLOW-299) Evaluate a plugin architecture to
replace contrib
[ https://issues.apache.org/jira/browse/AIRFLOW-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357778#comment-15357778 ]
Chris Riccomini commented on AIRFLOW-299:
-----------------------------------------
Sounds good. A design doc (one-pager on the wiki) would be useful for this.
> 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
(v6.3.4#6332)