Hello Bigtop community! My name is Chinmay Kolhatkar and I am a committer in Apache Apex (incubating) project. Our website is at: http://apex.incubator.apache.org/
We want to explore and integrate Apache Apex into the Bigtop as a component. Please treat this mail as a continuation of a mail thread: http://mail-archives.apache.org/mod_mbox/bigtop-dev/201601.mbox/%3CCA%2B5xAo20CAHuYtdxw3mtH2X9whREKd7fLdz4xmuTMqkaTiiskg%40mail.gmail.com%3E We're currently confirming with requirements for components and making sure that we meet the expectations: https://cwiki.apache.org/confluence/display/BIGTOP/Requirement+for+adding+a+new+component+to+Bigtop+distribution Once requirements are through, we're planning to add component into Apache Bigtop in following phases (as separate patches/pull requests): 1. Packaging - Creating of package i.e. rpm & deb files. - documentations/READMEs, LICENSE, DISCLAMER, NOTES etc if any needed. - Any documentation that need to be added to distribution of our software. - Any license information of dependencies required to be added to package 2. Smoke tests - Adding smoke test for packaging. 3. Puppet recipes for automatic deployment and configuration - Add puppet recipes for automatic deployment 4. license clearance: - Run 'gradle rat' to make sure all new stuff is compliant with ASF license requirements. Please share your thoughts on above approach. If the approach seems fine, we can create a Jira items and corresponding subtasks to start working. Thanks, Chinmay.
