Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 0.9.0
    • Fix Version/s: 1.0.0
    • Component/s: general
    • Labels:
      None

      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.

      Maintainers list draft

      tachyon: david capwell, jay vyas
      spark: jay vyas,
      hbase: andrew purtell
      hadoop: mark grover, cos, andrew purtell
      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, andrew purtell
      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, oflebbe
      oozie evans ye
      hue: oflebbe
      sentry: Mark Grover

        Issue Links

          Activity

          Hide
          rnowling RJ Nowling added a comment -

          jay vyas I think the JIRA description needs to be updated with a complete list of components so people know what needs maintainers. As people volunteer, can you update the JIRA description to add them?

          Show
          rnowling RJ Nowling added a comment - jay vyas I think the JIRA description needs to be updated with a complete list of components so people know what needs maintainers. As people volunteer, can you update the JIRA description to add them?
          Hide
          jayunit100 jay vyas added a comment -

          Feel free to attach some in a comment, i can update description as well.... Not in a huge rush though because Im pretty sure that if someone needs a reminder of a component in bigtop, then they arent interested in maintaining it to begin with.

          Show
          jayunit100 jay vyas added a comment - Feel free to attach some in a comment, i can update description as well.... Not in a huge rush though because Im pretty sure that if someone needs a reminder of a component in bigtop, then they arent interested in maintaining it to begin with.
          Hide
          jayunit100 jay vyas added a comment - - edited

          For me: packaging around spark, tachyon, BigPetStore, all the gradle based smoke-tests, vagrant recipes.

          Show
          jayunit100 jay vyas added a comment - - edited For me: packaging around spark, tachyon, BigPetStore, all the gradle based smoke-tests, vagrant recipes.
          Hide
          rnowling RJ Nowling added a comment -

          jay vyas I volunteer to help with BigPetStore

          Show
          rnowling RJ Nowling added a comment - jay vyas I volunteer to help with BigPetStore
          Hide
          apurtell Andrew Purtell added a comment -

          I volunteer for all things related to HBase and Phoenix packages.

          Show
          apurtell Andrew Purtell added a comment - I volunteer for all things related to HBase and Phoenix packages.
          Hide
          jayunit100 jay vyas added a comment - - edited

          summary so far hoping more people will also add names as volunteers around for tachyon/spark etc , but i think i can help maintain those.

          tachyon: jay vyas,
          spark: jay vyas,
          hbase: andrew purtell
          phoenix: andrew purtell
          bigtop-deploy/vagrant: jay vyas,
          bigtop-deploy/puppet: jay vyas,
          smoke-tests(hive,pig,mahout,mapreduce,flume,spark,hbase): jay vyas,
          bigpetstore: jay vyas, rj nowling, 
          

          as folks Keep adding info in comments below, ill keep updating ^

          Show
          jayunit100 jay vyas added a comment - - edited summary so far hoping more people will also add names as volunteers around for tachyon/spark etc , but i think i can help maintain those. tachyon: jay vyas, spark: jay vyas, hbase: andrew purtell phoenix: andrew purtell bigtop-deploy/vagrant: jay vyas, bigtop-deploy/puppet: jay vyas, smoke-tests(hive,pig,mahout,mapreduce,flume,spark,hbase): jay vyas, bigpetstore: jay vyas, rj nowling, as folks Keep adding info in comments below, ill keep updating ^
          Hide
          mgrover Mark Grover added a comment -

          I can do hive, sentry.

          I guess is hadoop is kinda important I can help with that but it would be good to have another volunteer for hadoop.

          Show
          mgrover Mark Grover added a comment - I can do hive, sentry. I guess is hadoop is kinda important I can help with that but it would be good to have another volunteer for hadoop.
          Hide
          cos Konstantin Boudnik added a comment -

          I copied Jay's list to the description so ppl can edit it directly before transferred to the file.

          Show
          cos Konstantin Boudnik added a comment - I copied Jay's list to the description so ppl can edit it directly before transferred to the file.
          Hide
          cos Konstantin Boudnik added a comment -

          BTW, it'd be great if we can reach out to the communities in question and offer them to volunteer for the maintenance, don't you think?

          Show
          cos Konstantin Boudnik added a comment - BTW, it'd be great if we can reach out to the communities in question and offer them to volunteer for the maintenance, don't you think?
          Hide
          jayunit100 jay vyas added a comment - - edited

          Ok Sean Mackrory r u ok w the assignments u have in the draft above? Just making sure don't see comment yet........ also @olaf and @evansye we will want to know about maintainer ideas, since they have been instrumental in some new developments to

          Show
          jayunit100 jay vyas added a comment - - edited Ok Sean Mackrory r u ok w the assignments u have in the draft above? Just making sure don't see comment yet........ also @olaf and @evansye we will want to know about maintainer ideas, since they have been instrumental in some new developments to
          Hide
          mackrorysd Sean Mackrory added a comment -

          jay vyas yes - I added those..

          Show
          mackrorysd Sean Mackrory added a comment - jay vyas yes - I added those..
          Hide
          jayunit100 jay vyas added a comment -

          thanks Sean Mackrory !... A few others to spam ... Dasha Boudnik Olaf Flebbe Evans Ye .... probably a few other usual suspects who i've forgotten.

          also like cos said... we can this opportunity to reach out to buddies in the community who might be interested to lend a hand
          with a more structured maintainer policy, i think we may be able to grow,maintain coherent and highly focused bigtop releases.

          Show
          jayunit100 jay vyas added a comment - thanks Sean Mackrory !... A few others to spam ... Dasha Boudnik Olaf Flebbe Evans Ye .... probably a few other usual suspects who i've forgotten. also like cos said... we can this opportunity to reach out to buddies in the community who might be interested to lend a hand with a more structured maintainer policy, i think we may be able to grow,maintain coherent and highly focused bigtop releases.
          Hide
          cos Konstantin Boudnik added a comment -

          I removed an explicit 'puppet recipes' as they are already covered in bigtop-deploy/puppet part, I guess.

          Show
          cos Konstantin Boudnik added a comment - I removed an explicit 'puppet recipes' as they are already covered in bigtop-deploy/puppet part, I guess.
          Hide
          evans_ye Evans Ye added a comment -

          I volunteer for pig, tez, oozie. Since I need time to get familiar with the build stuff, it would be great to have someone to collaborate with(maybe YoungWoo Kim can lend me a hand on pig?). bigtop-deploy/vagrant and bigtop-deploy/puppet are things that I'm much more familiar with, so I definitely would like to be a maintainer.

          Show
          evans_ye Evans Ye added a comment - I volunteer for pig, tez, oozie. Since I need time to get familiar with the build stuff, it would be great to have someone to collaborate with(maybe YoungWoo Kim can lend me a hand on pig?). bigtop-deploy/vagrant and bigtop-deploy/puppet are things that I'm much more familiar with, so I definitely would like to be a maintainer.
          Hide
          jayunit100 jay vyas added a comment -

          thanks evans. thats awesome. also Daniel Dai has mentioned in a private conversation he's willing to pitch in. daniel also please leave a comment about how you can pitch in around pig if you get a chance !

          Show
          jayunit100 jay vyas added a comment - thanks evans. thats awesome. also Daniel Dai has mentioned in a private conversation he's willing to pitch in. daniel also please leave a comment about how you can pitch in around pig if you get a chance !
          Hide
          jayunit100 jay vyas added a comment -

          hi cos. i've sent a few emails out to people in the community and got some responses. Please encourage your buddies to do the same. the more maintainers, the better !

          Show
          jayunit100 jay vyas added a comment - hi cos. i've sent a few emails out to people in the community and got some responses. Please encourage your buddies to do the same. the more maintainers, the better !
          Hide
          daijy Daniel Dai added a comment -

          Thanks Jay. I am not sure what exactly I need to do here, but since I am working on Pig, I can help with anything related to Pig packaging.

          Show
          daijy Daniel Dai added a comment - Thanks Jay. I am not sure what exactly I need to do here, but since I am working on Pig, I can help with anything related to Pig packaging.
          Hide
          jayunit100 jay vyas added a comment -

          okay, ill add you .

          Show
          jayunit100 jay vyas added a comment - okay, ill add you .
          Hide
          dcapwell David Capwell added a comment -

          I can do tachyon and tachyon tests.

          Show
          dcapwell David Capwell added a comment - I can do tachyon and tachyon tests.
          Hide
          evans_ye Evans Ye added a comment -

          Added. Awesome, David!

          Show
          evans_ye Evans Ye added a comment - Added. Awesome, David!
          Hide
          jayunit100 jay vyas added a comment -

          david i added you to smoke tests also, tacjhyon is in there, and you knwo the framework so in a pinch you can probably help with other smoke tests as well.

          Show
          jayunit100 jay vyas added a comment - david i added you to smoke tests also, tacjhyon is in there, and you knwo the framework so in a pinch you can probably help with other smoke tests as well.
          Hide
          dcapwell David Capwell added a comment -

          Show
          dcapwell David Capwell added a comment -
          Hide
          rvs Roman Shaposhnik added a comment -

          Here's what I'd be willing to sign up for:

          hbase
          hadoop
          bigtop-deploy/puppet
          bigtop-test-framework
          zookeeper
          maven publishing and packaging
          test-artifacts and test-execution repos
          continuous integration infra
          gradle / build system
          oozie
          
          Show
          rvs Roman Shaposhnik added a comment - Here's what I'd be willing to sign up for: hbase hadoop bigtop-deploy/puppet bigtop-test-framework zookeeper maven publishing and packaging test-artifacts and test-execution repos continuous integration infra gradle / build system oozie
          Hide
          rvs Roman Shaposhnik added a comment -

          Also, here's a thought: why don't we wikifi the list and get it to the finish line that way? Or is it almost ready to be committed to the repo?

          Show
          rvs Roman Shaposhnik added a comment - Also, here's a thought: why don't we wikifi the list and get it to the finish line that way? Or is it almost ready to be committed to the repo?
          Hide
          oflebbe Olaf Flebbe added a comment -

          I am willing to sign up for "hue" , if noone is stepping in. This definitely should not be on the kill list.

          Can we drop platforms if not maintained?

          Signing up for debian.

          Show
          oflebbe Olaf Flebbe added a comment - I am willing to sign up for "hue" , if noone is stepping in. This definitely should not be on the kill list. Can we drop platforms if not maintained? Signing up for debian.
          Hide
          jayunit100 jay vyas added a comment -

          Hi roman - I will commit it shortly!

          Show
          jayunit100 jay vyas added a comment - Hi roman - I will commit it shortly!
          Hide
          jayunit100 jay vyas added a comment - - edited

          Olaf I think nobody will complain as long as some form of rpm and deb is supported.

          you are probably correct that in time we will just be packaging Ubuntu and Centos, or something like that.... We can drop distros in a natural way, or if you want to make that an official rule, just propose on mailing list and we can discuss.

          Show
          jayunit100 jay vyas added a comment - - edited Olaf I think nobody will complain as long as some form of rpm and deb is supported. you are probably correct that in time we will just be packaging Ubuntu and Centos, or something like that.... We can drop distros in a natural way, or if you want to make that an official rule, just propose on mailing list and we can discuss.
          Hide
          jayunit100 jay vyas added a comment -

          Cleaned up , sorted, and commited as MAINTAINERS.txt to head.

          Thanks guys!

          This should really streamline things and increase our efficiency. No more "does somebody want to do xyz?" instead its "if somebody doesnt care about xyz, we're dropping it"

          Show
          jayunit100 jay vyas added a comment - Cleaned up , sorted, and commited as MAINTAINERS.txt to head. Thanks guys! This should really streamline things and increase our efficiency. No more "does somebody want to do xyz?" instead its "if somebody doesnt care about xyz, we're dropping it"
          Hide
          jayunit100 jay vyas added a comment - - edited

          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 test them, 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.

          Show
          jayunit100 jay vyas added a comment - - edited 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 test them, 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.
          Hide
          cos Konstantin Boudnik added a comment - - edited

          Shall this type of guidelines go to the Wiki's "How to Contribute" page?

          Show
          cos Konstantin Boudnik added a comment - - edited Shall this type of guidelines go to the Wiki's "How to Contribute" page?
          Hide
          rvs Roman Shaposhnik added a comment -

          I've updated the file with what I've signed up for. Quick question for folks: should we strive for formatting similar to:
          https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS
          or is it good enough?

          Show
          rvs Roman Shaposhnik added a comment - I've updated the file with what I've signed up for. Quick question for folks: should we strive for formatting similar to: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS or is it good enough?
          Hide
          cos Konstantin Boudnik added a comment -

          Would be nice, but let's not push it artificially?

          Show
          cos Konstantin Boudnik added a comment - Would be nice, but let's not push it artificially?
          Hide
          apurtell Andrew Purtell added a comment -

          I added myself as alternates for zookeeper and hadoop since the other packages I maintain depend on them.

          Show
          apurtell Andrew Purtell added a comment - I added myself as alternates for zookeeper and hadoop since the other packages I maintain depend on them.
          Hide
          cos Konstantin Boudnik added a comment -

          Guys, this JIRA has been closed and the content was migrated to the actual file in our git repo. Any chances to this JIRA made after Jan 25 won't be reflected in the file. Please do add yourselves to the file directly.

          Show
          cos Konstantin Boudnik added a comment - Guys, this JIRA has been closed and the content was migrated to the actual file in our git repo. Any chances to this JIRA made after Jan 25 won't be reflected in the file. Please do add yourselves to the file directly.
          Hide
          cos Konstantin Boudnik added a comment -

          Closed.

          Show
          cos Konstantin Boudnik added a comment - Closed.
          Hide
          dsetrakyan Dmitriy Setrakyan added a comment - - edited

          Sergey Vladykin form Apache Ignite community will maintain the GridGain Hadoop accelerator component.

          Show
          dsetrakyan Dmitriy Setrakyan added a comment - - edited Sergey Vladykin form Apache Ignite community will maintain the GridGain Hadoop accelerator component.

            People

            • Assignee:
              Unassigned
              Reporter:
              jayunit100 jay vyas
            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development