Dev guidelines have been updated
-
https://cwiki.apache.org/confluence/display/METRON/Development+Guidelines
PR is up for the PR checklist change
- https://issues.apache.org/jira/browse/METRON-2107
- https://github.com/apache/metron/pull/1401
On Wed, May 8, 2019 at 10:17 AM
Vote has passed. Voting was:
2 binding +1's (Mike Miklavcic, Otto Fowler)
1 non-binding +1 (Jon Zeolla)
I will start making the changes to the dev guidelines today.
Vote thread -
Good idea - I will make that addendum. I would consider that, ipso facto,
acceptable to everyone on the thread unless they say otherwise -
considering the entire point of this vote is to standardize the diagram
tool, it would be inconsistent with that goal to use the word "should."
"Must" makes
+1 non-binding
I would only prefer that we change "Appropriate architecture diagrams
should be created in" to "Appropriate architecture diagrams must be created
in" but I'm good either way.
- Jon Zeolla
zeo...@gmail.com
On Fri, May 3, 2019 at 10:18 AM Michael Miklavcic <
Yes, it is free James. We made sure of that in the original discussion.
On Thu, May 2, 2019 at 9:33 PM James Sirota wrote:
> i am ok with it as long as we are not forcing people to buy stuff
>
> 02.05.2019, 18:18, "Michael Miklavcic" :
> > Here's the latest discussion on the subject:
> >
>
+1
On May 2, 2019 at 21:18:21, Michael Miklavcic (michael.miklav...@gmail.com)
wrote:
Here's the latest discussion on the subject:
https://lists.apache.org/thread.html/0aa2b0b9ed4a0f0b0d8bb018c618e62de196565f9af71f347e504076@%3Cdev.metron.apache.org%3E
I'd like to propose a vote to change our
i am ok with it as long as we are not forcing people to buy stuff
02.05.2019, 18:18, "Michael Miklavcic" :
> Here's the latest discussion on the subject:
> https://lists.apache.org/thread.html/0aa2b0b9ed4a0f0b0d8bb018c618e62de196565f9af71f347e504076@%3Cdev.metron.apache.org%3E
>
> I'd like to
Here's the latest discussion on the subject:
https://lists.apache.org/thread.html/0aa2b0b9ed4a0f0b0d8bb018c618e62de196565f9af71f347e504076@%3Cdev.metron.apache.org%3E
I'd like to propose a vote to change our dev guidelines which will clarify
the tooling we use to produce diagrams and share the
Based on some requested changes from Otto, I'm pulling the vote on this. I
haven't had a chance to make the revisions yet, and will restart the vote
when I have a chance to get those finished.
On Fri, Apr 26, 2019 at 1:27 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> That works
That works too
On Fri, Apr 26, 2019, 12:20 PM Otto Fowler wrote:
> When I say module, I mean at the root of any module, so each module could
> have it’s own diagrams.
> And the project root wold have diagrams for the ‘overall'
>
>
> On April 26, 2019 at 13:44:30, Michael Miklavcic (
>
When I say module, I mean at the root of any module, so each module could
have it’s own diagrams.
And the project root wold have diagrams for the ‘overall'
On April 26, 2019 at 13:44:30, Michael Miklavcic (
michael.miklav...@gmail.com) wrote:
The convention that seems to have been followed thus
The convention that seems to have been followed thus far has been to plop
the images in the root of the module they're relevant to. Maybe relocating
them to a central place would make it easier. The site-book image link
rewriting might be simpler then as well. The only downside to this approach
- We need to specify the format I think, and then say that draw io is the
tool for the format and not just specify the tool.
- Existing diagrams, in order to be modified, will have to be converted to
this format, there should be jiras for that
2.1 "New features and significant bug fixes should be
I'd like to propose a vote to change our dev guidelines which will clarify
the tooling we use to produce diagrams and share the source files for those
diagrams. The original discuss thread is noted at the end of this email. I
propose the dev guidelines
14 matches
Mail list logo
