[
https://issues.apache.org/jira/browse/SPARK-15563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302285#comment-15302285
]
Sean Owen commented on SPARK-15563:
-----------------------------------
I don't understand your comment. I'm saying this is not the place to make that
suggestion, simply because there is no change to apache/spark that would
accomplish it. Use the feedback link on the site. I'm also saying that there is
nothing to assert about the packages, unless we want to get into some kind of
certification process, and that's not the business of ASF Spark, no. There was
no comment on the site itself.
> Packages specification
> ----------------------
>
> Key: SPARK-15563
> URL: https://issues.apache.org/jira/browse/SPARK-15563
> Project: Spark
> Issue Type: Improvement
> Components: Documentation
> Reporter: jay vyas
>
> PROBLEM
> Spark packages should be extensible as a mechanism for individual application
> developers to build productionable blueprints, and should be
> consumable/rebuildable/verifiable by robots. Otherwise, there is a danger
> that a "spark package" might just be a link to a github repo without any
> useful code in it.
> SOLUTION
> The spark-packages guidelines should enforce that either a `build.sbt`,
> `build.gradle`, `pom.xml`, or a `Makefile` present as part of the submission
> process. Although this doesnt gaurantee one step, automatic builds, it is a
> pretty good measure of a projects status as a reproducible, maintainable
> artifact for the community.
> I assume the spark-packages are a community maintained standard so the ASF
> Spark project is a good place to put this into the documentation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
