evans-ye commented on pull request #555: URL: https://github.com/apache/bigtop/pull/555#issuecomment-633664880
> 1) Decision on how to store the MPack. I was suggesting it should be an artifact/code base that is part of this project with it's own folder. I have nothing against it being part of Ambari as well, but it's my opinion that it should have it's own code repo in bigtop. I don't see Ambari continuing to maintain a BigTop MPack. This is my opinion and would happily discuss alternatives if there are differing opinions. I stand by the fact that this MPack could be used in "existing installs" and therefore doesn't belong bundled into an Ambari install. Thanks @mattAndruff for the summary. Technically speaking I think put Bigtop MPack in Ambari is the suitable way which increase the touch point we have to the users. The best result for this way is to have bigtop MPack upstream to Amabari. However this might be a strategic thing. Alternatively, we do it in Bigtop. Now we've it built-in with Bigtop built Ambari packages. You're suggesting to make isolated for direct consume. May I know more about the use case and the structure/layout you're proposing. Ex: another git repo or a top-level dir or somewhere else. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
