metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zeolla@GMail.com" <zeo...@gmail.com>
Subject Re: [DISCUSS] Synopsis of Community Meeting on 8/22/2017
Date Wed, 23 Aug 2017 10:08:34 GMT
Was there any discussion about future features of Metron aside from
777/942? In the initial announce thread the agenda mentioned where want to
take the project long-term and feature requests and comments on existing
features.

My thoughts on the topic are that I would like to see a move quickly after
0.4.1 to upgrade the stack, from centos 7, to elasticsearch 5, bro 2.5.1,
HDP 2.6.1, etc.  There's a growing list of issues due to the older
platforms we use.  I have already started work on some of this, and I know
we have a PR open for an ES upgrade as well.

More forward looking, I would also like to see a push for exactly once
processing through the stack, which I expect will be available with HDP
3.x?

I wholeheartedly agree that we should get back on top of the community
demos.  They have been helpful for me to watch and are very good materials
for pointing people new to the project to, in addition to our site-book.

Jon

On Tue, Aug 22, 2017, 15:00 Casey Stella <cestella@gmail.com> wrote:

> Introduction by James Sirota and hand off to me.
>
> Topic: Apache Administrivia
>
>    - We have passed our 3 month window of submitting board reports without
>    any serious incident
>    - We need and want more committers.  Anyone who is so inclined and
>    interested should pitch in, even without code contributions
>
> Topic: Release
>
>    - General consensus that a release is in order
>    - The release should be a point release and pre-777
>
> Topic: The Next Steps for METRON-777
>
>    - Proposed: We should move METRON-777 and METRON-942 into a feature
>    branch
>    - Proposed: Once working sufficiently, the first milestone is for Otto
>    to create a youtube video showing off his work and have a discuss thread
>    for a second pass of architecture/feature review
>    - Proposed: This feature branch should have no less stringent
>    requirements than we have for master
>    - Proposed: Documentation, testing, and the normal accompanying
>    artifacts for any other feature should be in place before we merge.
> Other
>    more feature-specific criteria should be discussed in separate discuss
>    threads.
>    - No dissenting opinions on the call.  Otto to create a discuss thread
>    about the feature branch and the mechanics of actually creating it.
>
> Topic: Community Demos
>
>    - Proposed: We should have community demos again on a monthly basis.
>    - General assent to this as well.
>    - James to set up a webex for one month hence.
>
> Anything that I got wrong or missed, please respond to this discuss thread.
>
> Best,
>
> Casey
>
-- 

Jon

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message