[
https://issues.apache.org/jira/browse/BIGTOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283038#comment-14283038
]
jay vyas commented on BIGTOP-1604:
----------------------------------
Hi guys ! One final note to folks on this *MAINTAINERS.txt* list.... This JIRA
commits a file which identifies people who will maintain components.
I'd like to suggest that really, there are *two parts to maintaining something*
: defining its role in bigtop, and technically keeping it up to date.
In the best case scenario, the work of a maintainer probably will be a
combination of being an *advisor* as well as doing some *technical stuff* as
well. Even if a technical patch isnt provided, keeping us up to date of you're
components changes might be very useful...
For example, when (hypothetical examples)
- HBase supports an in memory implementation or direct io in alternative file
systems, or
- pig supports spark or ignite or ... or
- SOLR provides a docker deployment option...
In any of these cases, it would be really nice if we can integrate cutting edge
features into puppet and so on, so that they are actually used, rather than
just blindly package them into /usr/lib/ never to see the light of day.
> Create a MAINTAINERS.txt File
> -----------------------------
>
> Key: BIGTOP-1604
> URL: https://issues.apache.org/jira/browse/BIGTOP-1604
> Project: Bigtop
> Issue Type: Bug
> Components: general
> Affects Versions: 0.9.0
> Reporter: jay vyas
> Priority: Critical
> Fix For: 0.9.0
>
>
> Start with 0.9, lets maintain a MAINTAINERS.txt file which has component,
> maintainer names.
> Everybody *please* add entries here for components in bigtop that you will
> maintain.
> I think we Are we in agreement that,
> - Components that *ARE NOT* in this file, can be dropped without much debate.
> No point in releasing something that is maintained by pure chance of
> randomly someone deciding to add a patch.
> - Components that *ARE* added in this file will, for obvious reasons, be
> central to the architecture of the bigtop distribution.
> Componets are : YARN, HBASE, SPARK, HIVE, PIG, MAHOUT, FLUME, (many others
> ...) folks please chime in on what you can maintain in the comments below,
> and I'll craft the file.
> {panel:title=Maintainers list draft}
> tachyon: david capwell, jay vyas
> spark: jay vyas,
> hbase: andrew purtell
> hadoop: mark grover, cos
> hive: mark grover
> phoenix: andrew purtell
> bigtop-deploy/vagrant: jay vyas, evans ye
> bigtop-deploy/puppet: jay vyas, cos, evans ye
> bigtop-test-framework: cos
> smoke-tests(hive,pig,mahout,mapreduce,flume,spark,hbase,tachyon): jay vyas,
> david capwell
> bigpetstore: jay vyas, rj nowling,
> zookeeper: sean mackrory
> gridgain-hadoop: cos
> sqoop: sean mackrory
> maven publishing and packaging:
> test-artifacts and test-execution repos:
> continuous integration infra:
> gradle / build system: cos
> pig: evans ye, daniel dai
> tez: evans ye
> oozie evans ye
> hue: oflebbe
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
