►
From YouTube: CHAOSS Weekly Hangout September 18, 2018
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
Know
matt
matt
has
early
meetings
today,
so
he
may
be
showing
up
a
little
bit
late,
but
he
did
want
me
to
share
that
as
of
today,
I
think
the
the
risk
work
group
is
getting
started
based
on
the
the
outcome
at
Kaos
Khan.
During
that
lightning
talk,
Matt,
Snell
and
Matt
German
pray
are
putting
together
the
the
risk
work
group
and
they
have
started
actively
working
on
it
today.
B
A
B
A
C
Yeah
estimation
yeah:
what
we
are
trying
to
do
is
to
create
some
templates
and
cards
for
each
of
the
categories
we
have.
So
this
is
gonna
be
a
tutorial.
Anyone
kind
can
follow
us
in
each
of
the
goals
or
questions
that
we
are
gonna
discuss
there.
So
idea
is
that
we
will
focus
on
a
couple
of
topics
or
main
categories
and
we're
still
ongoing
discussion
and
then
the
people
at
the
LD,
and
they
would
have
some
templates
and
some
cards,
so
they
can
take
notes
or-
and
they
will
have
course
digital
verse.
C
You
know
of
those,
so
they
can
play
with
this,
and
the
idea
is
two
things
well.
First
to
let
people
know
that
this
exists
and
so
on
to
have
a
kind
of
a
cadence,
because
one
of
the
feedback
or
part
of
a
feedback
we
have
really
received.
Was
that
hey
where?
Where,
where
can
I
start
here
or
where?
Where
is
their
starting
point?
So
I,
guess
that
having
these
templates
or
currencies?
Well,
hopefully,
this
this
is
something
useful
for
the
community
and
well,
of
course,
to
have
feedback
from
from
the
audience.
So,
let's
see.
B
I
just
got
done
saying:
I
wasn't
sure
if
you
were
gonna
make
it
because
you
had
meetings
I'm
here
so.
B
D
So
I
think,
as
a
kind
of
officially
today
we're
gonna
start
on
the
risk,
workgroup
right
and
there's
kind
of
two
ways
that
people
have
been
thinking
about
risk.
One
is
maybe
in
the
pathology,
SP
DX,
you
know,
license
compliance,
IP,
sort
of
way
and
that's
actually
what
I'm
more
familiar
with
I
had
done.
Work
in
both
of
those
communities,
so
I
think
that's
probably
where
we're
gonna
our
first
point
of
entry
is
gonna
be,
but
there
were
also
other
discussions
about
risk
at
chaos.
D
Con,
which
is
just
respect
with
respect
to
the
way
understood,
was
with
whether
or
not
a
project
is
risky
to
engage
with,
irrespective
of
the
licensing
or
copyright
in
there.
Nonetheless,
to
start
at
least
my
first
thoughts
are
ways
that
we
can
kind
of
connect
technically,
just
like
the
other
workers
right.
So
what
are
the
metrics
that
were
interested
in
and
how
can
we
deploy
some
of
these
technically
and
I?
Think
a
few
at
least
from
the
license
and
compliance
side
of
things
are
technically
deployable.
D
He
wrote
one
of
the
scanners
called
ninka
so
anyway,
there's
a
variety
of
scanners
underneath
the
hood
of
the
PHP
that
is
facility,
and
so
you
can
send
packages
to
one
of
these
scanners
and
they
will
scan
in
a
variety
of
ways
in
return
identified,
license
information.
So
you
know
if
you're
looking
for
say,
text
in
the
MIT
license
it'll
report
a
particular
file
as
MIT
as
an
MIT
declaration,
so
from
I
think
from
an
order
labs
perspective
that
wouldn't
be
too
difficult
to
take
on
there's.
E
D
So,
anyway,
you
know
I,
think
they're
gonna
be
a
few
technical
issues
here
and
I
from
a
grimore
lab
perspective
and
maybe
a
higher
level
of
maturity
of
perspective.
I,
don't
know
if
this
plays
into
how
you
think
about
projects
and
how
you
think
about
you
know,
code
bases
if
that's
ever
entered
the
conversation
at
all
things
like
reporting
licenses
that
are
evident
within
a
community.
No,
it
seemed
that
would
be
risk
related
right,
I
mean
yes,
I'm
talking
about
actually
starting
the
risk
working
group
right
now.
Sorry
Oh.
F
I
was
trying
to
say
that
when
we
started
talking
about
metrics
and
community
analytics,
actually
every
Marla
was
intentionally
to
bring
around
activity
performance
and
we
did
more
with
community
and
the
people
doing
the
activity
in
the
community.
But
lately,
for
example,
one
of
the
side
projects
of
one
of
our
personal
sin
in
the
company
has
developed
a
tool
that
can
integrate
the
scanners.
F
We
didn't
want
to
compete
with
existing
solutions
in
the
market
ever
when
we
started
the
company,
because
we
we
saw
that
there
is
plenty
of
then
none
of
they
are
100%,
accurate,
anyone,
okay,
another
player
in
the
market
is
line
and
network.
For
me,
and
now
we
are
talking
with
some
people
in
Europe
that
is
trying
to
do
some
kind
of
iteration,
of
also
these
tools
and
more
a
dependency
analysis.
Something
like
that,
and
it's
an
interesting
topic,
of
course,
taking
this
into
mine
people.
Nowadays,
people
start
to
think
about.
F
D
F
G
B
G
A
G
License
for
so
I
guess
like
I'm,
somewhat
concerned
like
do
we
want
to
just
you
know,
spit
out
a
raw
data
on
like
X
percentage
of
the
files
in
the
report
missing,
license
files
or
like
yeah,
yes,
I
mean
some
of
them
do
require
like
interpretation
like
I
mean
it's,
maybe
it's
appropriate.
They
don't
have
like
since
information.
G
Maybe
some
of
these
that
you
need
to
talk
to
the
developers
about
because
they
need
license
files
but
yeah
like
I
guess
like
I'm
somewhat
like
I,
don't
know
like
manrique
I,
don't
know
this
is
where
you're
going
like
integrating
like
fuss
ology
into
grim,
more
lab.
That
seems
I'm
not
sure.
If
that's
necessarily
like
the
best
thing
to
do,
but
because
I
mean
the
answers
are
not
gonna
be
black
and
white
necessarily
right.
Neither.
D
Metric
yeah
either
so
I
think
in
the
risk,
in
the
risk
side
of
things.
What
we're
at
least
in
my
mind,
just
trying
to
move
off
zero
right.
Can
we
create
some
transparency
when
considering
a
code
base
in
a
repository
and
I
totally
agree
with
you?
Ray
I
mean
like
the
normal
scanner,
that's
in
pathology,
but
certainly
not
perfect
by
any
my
or
is
monk
or
is
ninka
I
think
there
are
three
years
in
pathology:
I
mean
we
could
supplement
it,
but
I
think
the
next
be
scanner
is
at
scan.
F
G
F
But
it
is
to
provide
some
some
ways
to
integrate
third-party
scanners.
So
it's
a
proof
of
concept
still
I
would
say
within
that
product
is
to
somebody
who
can
give
more
background
about
things
that
they
want
to
achieve
here,
but
it
was
more
of
okay,
which
code
commits
are
changing,
for
example,
license
in
the
codebase
I'll
say.
D
Also
already,
this
is
an
interesting
conversation
because,
like
what
you
just
mentioned,
Manrique
like
which
licenses
are
changing
on
a
particular
file
or
what
Ray
had
mentioned
to
what
is
the
license
coverage
I
mean
those
are.
Those
are
interesting,
metrics,
I
guess
there
are
a
little
bit
more
granular
than
things
like
here
are
all
of
the
reported
licenses
is
identified
by
normals,
so
I
think
that's
good.
From
my
end,.
G
D
D
G
I
mean
because
I
think
Matt,
you
were
saying
this
you're
I
mean
you
guys
are
obviously
getting
things
started
right,
so
maybe
the
way
to
start
like
we've
done
with
other
like
diversity
and
inclusion,
and
others
is
just
to
find
a
set
of
like
meaningful
things
that
people
want
to
take
a
look
at
and
how
it
gets
implemented.
I
mean
that's
sort
of
next
level:
detail,
I,
guess
right
now,
yeah.
D
B
D
E
D
D
E
E
D
Gpl
so
yeah,
so
both
I
guess
both
just
from
grimore
lab
and
an
augur
perspective.
Just
kind
of
FYI
I
might
be
coming
your
way
with
risk
stuff.
Okay,
are
you
leading
the
risk
group
Matt
well
yeah,
so
this
is
what
I'm
actually
going
to
talk
to
Matt
Snell
about
here
to
today.
So
the
student
here
at
the
University,
so
yep
I,
will
take
the
lead
on
that
one.
D
E
A
A
E
We're
gonna
move
it
over
to
a
branch
of
the
main
metrics
repository.
We
had
to
talk
about
that
during
our
last
meeting.
It'll
make
it
easier
to
integrate
changes
going
forward.
We
did
talk
through
I
think
we're
gonna
follow
for
them.
Conceptually
we're
gonna,
follow
the
structure
laid
out
by
diversity
and
inclusion
in
terms
of
goals
and
use
cases.
E
You
can't
organizers
at
the
top
level,
I
think
I,
think
hey
Suzanne,
I
and
others
in
the
group
generally
agree
that
the
organizers
for
growth
maturity
decliner
are
different,
because
some
of
the
detailed
metrics
are
more
well
defined.
So
I
think
we
have
a
probably
working
from
both
ends
a
little
bit
more
than
diversity.
E
Inclusion,
because
we
have,
you
know
dozens
of
metrics
that
already
exists
in
the
world
that
need
to
be
described
in
a
way
that
art
is
the
chaos
way
with
all
that
nuance
and
then
built
so
we're
coming
in
from
that
top-down
structure,
as
well
as
from
the
bottom
up.
I
think
in
doubt,
I
mean
that's
how
he
characterized
the
main
difference
between
how
those
two
working
groups
operate.
Let.
C
A
A
The
argument
is,
cannot
just
write
one
documentation,
you
need
all
four
and
their
tutorial
the
guides
discussions
and
technical
references,
and
so
I
was
reflecting
on
that
too
we're
creating
with
in
math
in
chaos
and
tutorials.
This
is
Daniela
and
I
are
working
on
for
your
how-to
guide.
That's
what
we
call
the
resource
pace.
We
have
the
sessions
which
we
have
your
channel
and
we
have
the
reference.
That
is
the
implementation
of
the
disparity
in
the
growth
which,
in
decline,
work
group
are
being
worked
on
in
metric
publishers.
A
D
B
A
This
will
include
what
is
your
goal
for
creating
a
report?
Why
do
you
even
want
to
look
at
diversity,
inclusion
in
this
case
and
selecting
the
metrics
that
are
most
meaningful
to
answer
the
questions
that
you
have
specifically
and
then
how
do
you
structure
that?
How
do
you
go
about
collecting
the
data
which
that
part,
we
probably
will
not
be
able
to
go
into
because
we
only
have
90
minutes,
but
we'll
refer
to
our
repository.
D
D
Is
such
a
good
idea?
I
mean
it
makes
me
think
that
in
the
longer
run
you
know,
GMD
could
have
a
similar
output.
You
want
to
think
about
growth,
maturity
and
decline.
Here's
a
way
to
to
report
it
out
and
think
about
it
that
way,
because
those
reports
are
really
cool
because
they
constitute
the
metrics
and
the
software
and
the
data
sources.
They're
they're,
really
the
the
culmination
of
everything
they're,
not
just
they're,
not
metric
forward
they're,
not
software
forward.
D
It's
the
collection
of
all
right
and
really
hones
people
in
on
the
questions
that
they're
trying
to
answer
so
I'm
I,
haven't
said
this
before
I'm
really
excited
about
those
reports.
So
thanks
for
doing
that,
so
these
we
don't
have
examples
we
just
this
is
where
you're
headed
well.
Daniel
has
put
together
an
example
for
the
OpenStack.
Oh
it
done
this
before,
and
so
it
sounds
like
that's
the
frame
that
you
want
to
use.
Okay,
yeah.
A
D
C
A
brief
comment:
yeah,
yes,
come
Europe,
we
keep
looking
for
places
and
the
question
here
is:
do
we
want
to
go
over
function
euros
and
how
many
people
are
reacting?
You
have
because
previous
years
I
think
we
had
something
between
50
and
80
people,
so
I
would
say
we
can
expect
the
same
amount
of
people
regarding
to
the
play.
The
point
is
that
we
don't
have
the
Eevee's.
C
C
C
B
E
C
D
A
F
Just
to
make
it
clear,
I
I,
don't
know
you
can
hear
about
a
data
point
of
view.
We
are
going
to
sponsor
the
event
of
course,
as
we
did
in
Casco,
America
I
think.
The
matter
that
Daniel
wants
to
put
on
the
table
is
that
the
same
place
that
we
used
to
have
in
the
past.
That
is
something
that
was
convenient
for
the
name
of
people,
and
you
can
split
the
room
in
two
places
or
you
can
have
in
the
afternoon.
F
Similar
tutorials
running
at
the
same
time
is
not
available
anymore,
and
we
are
looking
for
alternatives.
We
have
found
that
the
prices
are
much
higher
than
the
past
or
we
have
a
small
place.
I
am
with
you
with
most
of
you
that
the
small
place
is
nice
in
terms
of
pricing,
but
I
think
could
be
to
reduce
in
terms
of
people
that
would
attend
to
the
event
based
on
the
previous
meetings
we
already
have.
So
we
keep
looking
for
private
place
and
let's
see
we
can
get
something.
That's
it.
That's
all
perfectly.
D
A
D
D
That's
good
so
good
job,
so
now
we're
on
just
on
chaos.
So
that's
good
all
right!
Well,
thanks!
Everybody
I
think
this
is
good.
Unless
anybody
has
something
burning,
you
want
to
bring
up
all
right
good.
These
are.
These
are
great.
It's
good
to
see
everybody
again
and
I
will
be
chatting
soon.
All
right,
doctor.