Github user as22323 commented on the issue:
https://github.com/apache/metron/pull/916
Hello, Just wondering what the the /contrib is folder for? If the files in
/contrib is not part of the core maintenance(continuous update for n+1) then
perhaps we can make a reference to the
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/916
@lvets Putting the vagrant file into a /contrib area with a notice that
sets expectation correctly is the way to go then
---
Github user lvets commented on the issue:
https://github.com/apache/metron/pull/916
@nickwallen, @ottobackwards , my 0.02$ :)
> For example, with everything in Metron today, you can stand-up a single
node in AWS and use the Mpack to install Metron. It is not as "push button"
Github user as22323 commented on the issue:
https://github.com/apache/metron/pull/916
Thanks for the great feedback!
Although I was hoping this would make it into the main build, I understand
what you mean by the "Support Burden".
I found a place in the Metron docs to
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/916
I'd be perfectly happy to reference in Metron docs, external
resources/projects like this that community members might find useful. Good
idea @ottobackwards
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/916
Why not add it to /contrib ? Or can we have a way to like to it from docs
or site?
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/916
@as22323 Let me first say that this is a nice piece of work. You've
followed all the existing patterns and your contribution looks solid.
But ultimately I am +0 on this. I want others