[ https://issues.apache.org/jira/browse/METRON-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16098459#comment-16098459 ]
ASF GitHub Bot commented on METRON-1053: ---------------------------------------- Github user kylerichardson commented on the issue: https://github.com/apache/metron/pull/659 Going to run this up now. I'll get my feedback in today. On Mon, Jul 24, 2017 at 10:02 AM, JonZeolla <notificati...@github.com> wrote: > I took a high level look when it first came out - no concerns. I'm mobile > only until Thursday so don't hold this up based on me. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/metron/pull/659#issuecomment-317432077>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AJ6R3VNjA3oLfQnrBkLKm6idoMnLVRDSks5sRKPrgaJpZM4OdCOL> > . > > Relocate Metron Docker > ---------------------- > > Key: METRON-1053 > URL: https://issues.apache.org/jira/browse/METRON-1053 > Project: Metron > Issue Type: Bug > Affects Versions: 0.4.0 > Reporter: Nick Allen > Priority: Minor > Fix For: 0.4.1 > > > 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 > another location to avoid confusing new users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)