[ 
https://issues.apache.org/jira/browse/BIGTOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

jay vyas updated BIGTOP-1604:
-----------------------------
    Description: 
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: 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): jay vyas,
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
{panel}

  was:
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: 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): jay vyas,
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
tez: evans ye
oozie evans ye
{panel}


> 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
>
> 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: 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): jay vyas,
> 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
> {panel}



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

Reply via email to