You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by Otto Fowler <ot...@gmail.com> on 2017/12/14 20:43:35 UTC
[DEV COMMUNITY MEETING] Call for Ideas and Schedule
Dev Community Meeting Call
I would like to propose a developer community meeting.
I propose that we set the meeting early next week, and will throw out
Monday, December 18th at 09:30AM PST, 12:30 on the East Coast and 5:30 in
London Towne.
This meeting will be held over a web-ex, the details of which will be
included in the actual meeting notice.
Please reply to this with scheduling concerns and topic suggestions.
Potential Topics
- Call for reviewers, ideas how to get more involvement, what people can
do to help
- Feature branches : we have two now, what are they and how are we going
to work on them
- Extension Repository: Default deployment and installation of parsers
as it relates to ‘777’
- General ‘777’ discussion
Developer Community Meeting Disclaimers
- Developer Community meetings are a means for realtime discussion of
development issues
- These meetings are not specifically aimed at demonstrations, unless
one is required or requested as part of such discussion
- These meetings are geared towards Metron development issues, not user
issues with deployment or shipped functionality
- There are *NO* decisions made in these meetings. The mailing list is
the official communication record of the Apache Metron Project, and as such
all public decisions are to be made on the list, as to give the greatest
opportunity for community involvement.
- There *ARE* proposals that can be made and discussed in these
meetings, that will then be discussed on list for decision.
- Notes will be taken of these meetings, and they will be posted to the
list
- There may also be breakout posts to the list per proposal or topic,
for more detailed discussion
Re: [DEV COMMUNITY MEETING] Call for Ideas and Schedule
Posted by "Zeolla@GMail.com" <ze...@gmail.com>.
I like your list of potential topics. I'm also in to attend - that time
works well for me.
I would be interested in talking about our release process, as I would like
to suggest that we formalize upgrade and installation instructions to be
included as a part of a release, and talk through any concerns/questions
with the secondary repo. I know I have at least one discussion point on
each of those suggestions.
Also, maybe we can chat about adding security scanning to our code base,
including on PRs.
Jon
On Thu, Dec 14, 2017, 15:43 Otto Fowler <ot...@gmail.com> wrote:
> Dev Community Meeting Call
>
> I would like to propose a developer community meeting.
>
> I propose that we set the meeting early next week, and will throw out
> Monday, December 18th at 09:30AM PST, 12:30 on the East Coast and 5:30 in
> London Towne.
>
> This meeting will be held over a web-ex, the details of which will be
> included in the actual meeting notice.
>
> Please reply to this with scheduling concerns and topic suggestions.
> Potential Topics
>
> - Call for reviewers, ideas how to get more involvement, what people can
> do to help
> - Feature branches : we have two now, what are they and how are we going
> to work on them
> - Extension Repository: Default deployment and installation of parsers
> as it relates to ‘777’
> - General ‘777’ discussion
>
> Developer Community Meeting Disclaimers
>
> - Developer Community meetings are a means for realtime discussion of
> development issues
> - These meetings are not specifically aimed at demonstrations, unless
> one is required or requested as part of such discussion
> - These meetings are geared towards Metron development issues, not user
> issues with deployment or shipped functionality
> - There are *NO* decisions made in these meetings. The mailing list is
> the official communication record of the Apache Metron Project, and as
> such
> all public decisions are to be made on the list, as to give the greatest
> opportunity for community involvement.
> - There *ARE* proposals that can be made and discussed in these
> meetings, that will then be discussed on list for decision.
> - Notes will be taken of these meetings, and they will be posted to the
> list
> - There may also be breakout posts to the list per proposal or topic,
> for more detailed discussion
>
--
Jon
Re: [DEV COMMUNITY MEETING] Call for Ideas and Schedule
Posted by Otto Fowler <ot...@gmail.com>.
I am still waiting for info on the zoom room. I will have an email out by
the end of the day with information, one way or another.
On December 15, 2017 at 18:15:21, Otto Fowler (ottobackwards@gmail.com)
wrote:
Great guys,
I’m going to leave the call OPEN for ideas, but at this point let’s say we
are going to schedule it for that time.
I will send the announce when I hear back form James about the room
On December 15, 2017 at 15:44:59, Michael Miklavcic (
michael.miklavcic@gmail.com) wrote:
Sounds good Otto. We probably also want to touch on the ES 5.6 upgrade
along with our current release status and short-term release roadmap that
Nick Allen has been guiding.
On Fri, Dec 15, 2017 at 9:02 AM, Laurens Vets <la...@daemon.be> wrote:
> I'll try to attend :)
>
>
> On 2017-12-14 12:43, Otto Fowler wrote:
>
>> Dev Community Meeting Call
>>
>> I would like to propose a developer community meeting.
>>
>> I propose that we set the meeting early next week, and will throw out
>> Monday, December 18th at 09:30AM PST, 12:30 on the East Coast and 5:30 in
>> London Towne.
>>
>> This meeting will be held over a web-ex, the details of which will be
>> included in the actual meeting notice.
>>
>> Please reply to this with scheduling concerns and topic suggestions.
>> Potential Topics
>>
>> - Call for reviewers, ideas how to get more involvement, what people
>> can
>> do to help
>> - Feature branches : we have two now, what are they and how are we
>> going
>> to work on them
>> - Extension Repository: Default deployment and installation of parsers
>> as it relates to ‘777’
>> - General ‘777’ discussion
>>
>> Developer Community Meeting Disclaimers
>>
>> - Developer Community meetings are a means for realtime discussion of
>> development issues
>> - These meetings are not specifically aimed at demonstrations, unless
>> one is required or requested as part of such discussion
>> - These meetings are geared towards Metron development issues, not user
>> issues with deployment or shipped functionality
>> - There are *NO* decisions made in these meetings. The mailing list is
>> the official communication record of the Apache Metron Project, and as
>> such
>> all public decisions are to be made on the list, as to give the
>> greatest
>> opportunity for community involvement.
>> - There *ARE* proposals that can be made and discussed in these
>> meetings, that will then be discussed on list for decision.
>> - Notes will be taken of these meetings, and they will be posted to the
>> list
>> - There may also be breakout posts to the list per proposal or topic,
>> for more detailed discussion
>>
>
Re: [DEV COMMUNITY MEETING] Call for Ideas and Schedule
Posted by Otto Fowler <ot...@gmail.com>.
Great guys,
I’m going to leave the call OPEN for ideas, but at this point let’s say we
are going to schedule it for that time.
I will send the announce when I hear back form James about the room
On December 15, 2017 at 15:44:59, Michael Miklavcic (
michael.miklavcic@gmail.com) wrote:
Sounds good Otto. We probably also want to touch on the ES 5.6 upgrade
along with our current release status and short-term release roadmap that
Nick Allen has been guiding.
On Fri, Dec 15, 2017 at 9:02 AM, Laurens Vets <la...@daemon.be> wrote:
> I'll try to attend :)
>
>
> On 2017-12-14 12:43, Otto Fowler wrote:
>
>> Dev Community Meeting Call
>>
>> I would like to propose a developer community meeting.
>>
>> I propose that we set the meeting early next week, and will throw out
>> Monday, December 18th at 09:30AM PST, 12:30 on the East Coast and 5:30 in
>> London Towne.
>>
>> This meeting will be held over a web-ex, the details of which will be
>> included in the actual meeting notice.
>>
>> Please reply to this with scheduling concerns and topic suggestions.
>> Potential Topics
>>
>> - Call for reviewers, ideas how to get more involvement, what people
>> can
>> do to help
>> - Feature branches : we have two now, what are they and how are we
>> going
>> to work on them
>> - Extension Repository: Default deployment and installation of parsers
>> as it relates to ‘777’
>> - General ‘777’ discussion
>>
>> Developer Community Meeting Disclaimers
>>
>> - Developer Community meetings are a means for realtime discussion of
>> development issues
>> - These meetings are not specifically aimed at demonstrations, unless
>> one is required or requested as part of such discussion
>> - These meetings are geared towards Metron development issues, not user
>> issues with deployment or shipped functionality
>> - There are *NO* decisions made in these meetings. The mailing list is
>> the official communication record of the Apache Metron Project, and as
>> such
>> all public decisions are to be made on the list, as to give the
>> greatest
>> opportunity for community involvement.
>> - There *ARE* proposals that can be made and discussed in these
>> meetings, that will then be discussed on list for decision.
>> - Notes will be taken of these meetings, and they will be posted to the
>> list
>> - There may also be breakout posts to the list per proposal or topic,
>> for more detailed discussion
>>
>
Re: [DEV COMMUNITY MEETING] Call for Ideas and Schedule
Posted by Michael Miklavcic <mi...@gmail.com>.
Sounds good Otto. We probably also want to touch on the ES 5.6 upgrade
along with our current release status and short-term release roadmap that
Nick Allen has been guiding.
On Fri, Dec 15, 2017 at 9:02 AM, Laurens Vets <la...@daemon.be> wrote:
> I'll try to attend :)
>
>
> On 2017-12-14 12:43, Otto Fowler wrote:
>
>> Dev Community Meeting Call
>>
>> I would like to propose a developer community meeting.
>>
>> I propose that we set the meeting early next week, and will throw out
>> Monday, December 18th at 09:30AM PST, 12:30 on the East Coast and 5:30 in
>> London Towne.
>>
>> This meeting will be held over a web-ex, the details of which will be
>> included in the actual meeting notice.
>>
>> Please reply to this with scheduling concerns and topic suggestions.
>> Potential Topics
>>
>> - Call for reviewers, ideas how to get more involvement, what people
>> can
>> do to help
>> - Feature branches : we have two now, what are they and how are we
>> going
>> to work on them
>> - Extension Repository: Default deployment and installation of parsers
>> as it relates to ‘777’
>> - General ‘777’ discussion
>>
>> Developer Community Meeting Disclaimers
>>
>> - Developer Community meetings are a means for realtime discussion of
>> development issues
>> - These meetings are not specifically aimed at demonstrations, unless
>> one is required or requested as part of such discussion
>> - These meetings are geared towards Metron development issues, not user
>> issues with deployment or shipped functionality
>> - There are *NO* decisions made in these meetings. The mailing list is
>> the official communication record of the Apache Metron Project, and as
>> such
>> all public decisions are to be made on the list, as to give the
>> greatest
>> opportunity for community involvement.
>> - There *ARE* proposals that can be made and discussed in these
>> meetings, that will then be discussed on list for decision.
>> - Notes will be taken of these meetings, and they will be posted to the
>> list
>> - There may also be breakout posts to the list per proposal or topic,
>> for more detailed discussion
>>
>
Re: [DEV COMMUNITY MEETING] Call for Ideas and Schedule
Posted by Laurens Vets <la...@daemon.be>.
I'll try to attend :)
On 2017-12-14 12:43, Otto Fowler wrote:
> Dev Community Meeting Call
>
> I would like to propose a developer community meeting.
>
> I propose that we set the meeting early next week, and will throw out
> Monday, December 18th at 09:30AM PST, 12:30 on the East Coast and 5:30
> in
> London Towne.
>
> This meeting will be held over a web-ex, the details of which will be
> included in the actual meeting notice.
>
> Please reply to this with scheduling concerns and topic suggestions.
> Potential Topics
>
> - Call for reviewers, ideas how to get more involvement, what people
> can
> do to help
> - Feature branches : we have two now, what are they and how are we
> going
> to work on them
> - Extension Repository: Default deployment and installation of
> parsers
> as it relates to ‘777’
> - General ‘777’ discussion
>
> Developer Community Meeting Disclaimers
>
> - Developer Community meetings are a means for realtime discussion
> of
> development issues
> - These meetings are not specifically aimed at demonstrations,
> unless
> one is required or requested as part of such discussion
> - These meetings are geared towards Metron development issues, not
> user
> issues with deployment or shipped functionality
> - There are *NO* decisions made in these meetings. The mailing list
> is
> the official communication record of the Apache Metron Project, and
> as such
> all public decisions are to be made on the list, as to give the
> greatest
> opportunity for community involvement.
> - There *ARE* proposals that can be made and discussed in these
> meetings, that will then be discussed on list for decision.
> - Notes will be taken of these meetings, and they will be posted to
> the
> list
> - There may also be breakout posts to the list per proposal or
> topic,
> for more detailed discussion