[
https://issues.apache.org/jira/browse/APEXCORE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704211#comment-15704211
]
Chinmay Kolhatkar commented on APEXCORE-576:
--------------------------------------------
One can have their extensions in their own github repository and just affiliate
their extensions with Apache Apex via this registry. Because their code resides
in their own open repository, the process of affiliation to Apex is lesser.
This is not a direct contribution to Apache Apex but rather an indirect
contribution to have features with Apache Apex. As the extensions matures, they
can be pulled into mainstream with right standards followed.
> 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)
