Per this discussion, I opened https://github.com/apache/metron/pull/659. Please take a look when you get a chance.
On Thu, Jul 13, 2017 at 1:49 PM, zeo...@gmail.com <zeo...@gmail.com> wrote: > I agree to moving it to a contrib or contrib-like area. > > Jon > > On Thu, Jul 13, 2017 at 12:38 PM Kyle Richardson < > kylerichards...@gmail.com> > wrote: > > > I completely support the idea of moving metron-docker down in the tree. I > > do like the idea of a contrib/ area for things like this that are not as > > frequently updated or maintained. Are there any other pieces of the code > > base that would fit into this type of area? > > > > -Kyle > > > > On Thu, Jul 13, 2017 at 12:30 PM Laurens Vets <laur...@daemon.be> wrote: > > > > > On 2017-07-13 09:04, Nick Allen wrote: > > > > Having metron-docker at the top-level of the project seems to catch > the > > > > attention of new users. Some then start using metron-docker to > > > > explore/try-out/demo Metron. > > > > > > > > The metron-docker code that we have is not well-suited for this > > > > purpose. > > > > It is only really useful for development. It is not regularly tested > > > > and > > > > maintained like our Vagrant environment. > > > > > > > > I am proposing that we move the top-level "metron-docker" directory > to > > > > live > > > > under "metron-deployment" to avoid confusing new users. This also > > > > seems > > > > more logical to me. I would also pair this move with some better > > > > "Getting > > > > Started" steps for new users in the top-level README. > > > > > > > > cd $METRON_HOME > > > > mv metron-docker metron-deployment/docker > > > > > > > > > > > > Do you agree/disagree? Is there a better solution? > > > > > > Maybe under "Other Examples"? > > > > > > -- > > Jon >
