[
https://issues.apache.org/jira/browse/APEXCORE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704203#comment-15704203
]
Chinmay Kolhatkar commented on APEXCORE-576:
--------------------------------------------
The malhar is rich ecosystem right now, but I doubt this would dilute the
existing ecosystem. The idea is to provide contributor an way to affiliate
their code with Apache Apex (I believe affiliate is the right word). Once their
components matures, they can chose to raise the pull request to malhar (i.e.
mainstream) with proper standard. For involving to mainstream, the standards as
they are currently remains intact.
> 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)
