[jira] [Commented] (APEXCORE-576) Apex/Malhar Extensions

["Sanjay M Pujare (JIRA)" <ji...@apache.org>]

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

Sanjay M Pujare commented on APEXCORE-576:
------------------------------------------

As far as I understand then the main enhancement here is the "registry" and a process to pick items from the registry to merge into the main repository and we will be using the current git process of pull-requests and merging across forks. Are there existing models we can look at for the registry?

A few things that need to be hammered out:
- registry access control, and format 
- criteria for merging external contributions into the main repo (quality, unit tests, demand, licensing)
- level of automation available, or otherwise the manual process used to merge contributions
- dependency matrix management (e.g. an item depends malhar 3.5.0 minimum)
- guidelines for adding items to the registry to be followed by contributors

> Apex/Malhar Extensions
> ----------------------
>
>                 Key: APEXCORE-576
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-576
>             Project: Apache Apex Core
>          Issue Type: New Feature
>          Components: Website
>            Reporter: Chinmay Kolhatkar
>
> The purpose of this task is to provide a way to external contributors to make better contributions to Apache Apex project.
> The idea looks something like this:
> 1. One could have extension to apex core/malhar in their own repository and just register itself with Apache Apex. 
> 2. As it matures and find more and more use we can consume that in mainstream releases.
> 3. Some possibilities of of Apex extensions are as follows:
>     a. Operators - DataSources, DataDestinations, Parsers, Formatters, Processing etc.
>     b. Apex Engine Plugables
>     c. External Integrations
>     d. Integration with other platform like Machine learning, Graph engines etc.
>     e. Application which are ready to use.
>     d. Apex related tools which can ease the development and usage of apex.
> The initial discussion about this has happened here:
> https://lists.apache.org/thread.html/3d6ca2b46c53df77f37f54d64e18607a623c5a54f439e1afebfbef35@%3Cdev.apex.apache.org%3E
> More concrete discussion/implementation proposal required for this task to progress.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)