►
From YouTube: CHAOSS.Community.June.11.2019
Description
CHAOSS.Community.June.11.2019
A
So
a
couple
of
things
that
I
had
today
is
with
respect
to
chaos.
Con
I
don't
know
if
anybody
has
any
pressing
issues
right
now
we
have
our
submissions
therein
and
then
I
think.
At
the
end
of
the
week
the
planning
committee
is
meeting
to
talk
through
those
submissions
and
for
those
of
you
that
are
on
the
planning
meeting.
I,
don't
know
if
you
noticed,
but
I
did
make
a
tab.
That
was
just
kind
of
like
an
approximate
schedule
across
the
two
rooms
we
do
have.
A
A
A
I,
don't
know
if
you
remember
that
it
wasn't
associated
with
OS
SNA
and
Stephanie
at
the
Linux
Foundation
came
back
and
said
you
had
no,
that's
not
because
we're
already
full
on
the
open
source
summit,
North
America,
and
so
there
were
a
hundred
people
that
have
registered
I.
Think
there
were
95
at
that
point.
Wow
yeah
I
know
so.
Naturally,
not
everybody
will
come,
but
still
I
thought
those
were
pretty
pretty
nice
numbers.
C
A
C
A
D
D
A
F
E
A
A
A
I
don't
mean
to
be
creepy
like
I
see
you
registered
now
get
to
work,
but
you
know
if
we
know
people
that
are
nice
and
kind
of
approachable.
It
might
be
something
to
think
about.
But
yes,
I
will
definitely
get
that
list
and
I'll.
Maybe
I'll
try
to
see
if
Stephanie
can't
get
it
to
us
before
we
meet
on
Friday,
okay,.
E
That
would
be
great.
The
other
thing
I
would
be
interested
just
to
look
at
on
the
list
is,
does
it
does
it
seem
like
we
have
the
right
people
registered
already
like
do?
We
have
most
of
the
you
know,
key
maintainer
x'
project
committers,
the
people
who
are
participating
in
the
project
or
do
we
have
a
whole
bunch
of
random
people,
I
registered
or
anything.
A
A
E
A
E
A
G
E
A
A
A
A
A
A
Okay,
so
my
the
other
thing
that
I
wanted
to
bring
out
was
release
of
metrics,
so
that's
kind
of
coming
in
short
order.
It's
one
of
those
things
that
I
think
has
been
sitting
off
in
the
distance
for
a
while,
and
you
know
what
wouldn't
be
hold
here.
We
are
so
the
I'm
gonna
send
out
the
newsletter
later
today
and
I.
Think
we
had
put
the
I
think
I
picked,
the
21st
June
21st
is
kind
of
the
final
like.
A
H
E
C
A
You
meeting
this
Wednesday
or
no
I,
don't
think
I
think
this
is
the
half
week,
okay,
so
okay,
so
if
I
was
to
look
at
that
DNI
of
five
risk
about
a
thousand
seventeen
I
mean
that's
a
lot
evolution,
even
if
it
was
you
know
it's
looking
in
the
neighborhood
of
two
dozen,
which
is
great
I,
think
this
is
so
then
there
are
a
couple
comments
on
this.
One
I
think
this
is
great
for
a
couple
of
reasons.
One
is
it
I
think
it
gives
to
something
to
point
at
which
is
really
nice.
A
This
is
aiming
towards
towards
the
burgeoned
metrics,
which
is
really
cool,
I,
think
that's
a
big
win
and
then
the
other
thing
is
the
other
thing
that
so
I
think
that's
the
nicest
thing
for
me
and
it'll
be
knighted,
something
nice
to
get
out
at
open
source
in
North,
America
and
chaos
con
to
also
point
people
to
one
another
discussion.
That's
kind
of
showing
up
in
the
background
right
now
is
how
to
represent
these.
A
C
A
A
F
D
B
Github
has
a
feature
of
marking
a
specific
commit
as
a
release
commit
and
that
way,
if
you
go
to
the
github
interface
and
look
at
releases,
you
will
automatically
go
to
the
commits
that
the
best
that
would
be
pulling
from
that
maybe
have
a
transparent
way.
Also
in
our
github
workflow
of
saying
this
was
the
release.
A
Okay,
so
if
I'm
getting
this
right,
if
if
there
are
24
metrics
that
are
released,
I'll
just
pick
that
number,
if
there's
24
metrics,
that
are
released,
there
will
be
25
and
me
peoples
on
the
website.
There
will
be
a
page
that
lists
every
metric
and
then
there
will
be
a
page
that
is
the
detail
for
every
metric,
correct,
okay,
okay,
I,
like
that
I
mean
that's
think
that's
preferable.
Does
anybody
have
comments
on
that?
But
this
is
where
things
are
they're
kind
of
tracking
right
now,
I
read
silence
is
that's
a
great
idea.
A
A
F
A
F
F
D
F
I
think
this
would
give
the
general
idea:
okay,
I,
just
dropped
it
into
the
chat.
The
big
question
I
have
about
this
is:
if
we're
releasing
these
and
making
them
available
for
comments.
How
do
we
want
to
handle
comments?
We
just
want
text
in
there
that
directs
them
to
the
email
list.
Do
we
want
to
direct
them
to
a
specific
chat
area?
Do
we
want
to
direct
them
to
the
repo?
A
D
A
D
D
A
G
One
issue
per
per
issue
like
metric:
no,
no
like
one
per
metric
because
think
Dan.
If
you
build,
if
you
do
find
something
you
want
to
change
and
you
build
a
pull
request
off
of
it,
then
you
can
see
it'll
be
transparent
per
metric
okay.
So
we,
this
comment
was
made
in
this
issue.
We
built
we
yeah,
that's
a
good
change.
We
should
make
that
then
we
do
it
flips
back
out.
We
put
the
final
final
out
on
the
website
and
then
you
have
a
historic
link
back
to
the
changes
that
were
made.
I
agree.
G
A
E
E
G
I'm,
pushing
back
just
a
teeny
tiny
bit
on
this,
because
I'm
building
I'm
trying
to
do
the
draft
of
the
metric
today
and
I'm
all
been
tired
and
I've,
already
confused
myself
50
times
on
wait.
What
are
we
talking
about
here
with
organizational
affiliation?
I
just
feel
like
there's
a
chance
for
cross
contamination
on
metrics.
If
we
do
it
by
group,
like
somebody
will
say
something,
and
we
were
not
sure
what
issue
or
metric
they're
talking
about.
G
B
G
F
H
A
Okay
does
so
I
mean
that
was
rid
of
my
two
main
issues
when
was
chaos,
time
kind
of
telling
people
the
status
of
that
and
then
the
other
was
getting
feedback
on
some
of
these
metric
release
issues.
Any
comments
on
either
of
these
two
still
correcting
any
of
the
working
groups
want
to
bring
anything
forward.
I
can
go
one
by
one
or
there's
anything
pressing
on
on
your
mind,
the.
E
A
Guy
loved
consistency,
it's
really
great
I
will
say.
Let
me
am.
Let
me
make
one
comment,
one
of
the
things
that
I
don't
know
how
all
of
the
working
groups
are
working,
but
the
way
that
I
know
a
number
of
them
are
working.
Is
that
if
there's
a
so
you
have
your
obviously
your
github
repository
with
the
table
that
has
the
like
the
focus
area
and
then
the
metrics
in
there
as
you're
building
the
page
that
provides
the
detail
on
the
metrics
I
know.
A
E
A
And
so
then
I
think
doing
the
attention
rate
is.
Then
you
get
the
detail,
kind
of
a
set
in
stone
and
then
just
issue.
One
pull
request
off
that
and
then
you
can
just
do
smaller
PRS.
Just
most
all
our
changes
if
things
need
to
be
updated,
okay,
cool,
you
know
there
were
group
updates,
sounds
like
that's
the
story
to
everybody
check
technology
software
augur
updates,
I,
Shawn
how's,
that
going
that's.
C
A
B
C
C
C
I
committed
the
full
version
of
the
schema
in
preparation
for
describing
the
readme
describing
installation
process
in
a
way
that
people
can
just
sort
of
download
augur
specifying
the
giving
of
organizations
or
give
at
the
point
that
they
want
to
monitor
and
run.
So
that's
that's
where
we're
headed.
Okay,
explain
a
bit
more
later
or
earlier.
So
I
don't
want
to
take
up
a
lot
of
time
before
I
have
more
to
show.
B
So
anyone
who
wants
to
try
the
new
released
metrics
has
like
three
steps:
install
doctor
open
this
dark
container
set
up
your
data
source
that
you
want
to
use.
So
hisses
worked
on
that
I'm
I
met
with
Alberto,
Daniel
and
Michele
today
about
how
we
can
show
in
the
metric
definitions
how
it
is
done
in
I,
agree
more
lab,
so
in
especially
in
evolution,
I
know
we
have
a
section
that
says
known
implementations
and
we
create
a
pull
request
today
to
see
how
we
can
show
that
the
this
metric
is
already
implemented
and
blinking.
C
B
B
A
Thank
you.
So
it
is
this
in
the
neighbor
in
the
other
and
talk
at
grimore
lab
I
have
two
questions
for
the
software
folks,
one
is
on
the
development
of
panels
that
are
representative
I
know
this
is
specific
to
Chrome
or
lab,
but
the
development
of
panels
that
are
kind
of
focused
on
the
working
groups.
I
know
this
has
always
kind
of
been
a
discussion
in
the
the
background,
maybe
that
you
know
like
a
panel
on
evolution
or
a
panel
on
risk
for
a
panel
on
value.
B
E
B
B
A
C
Have
our
main
approach
now
is
to
just
go
after
the
data
from
its
source
and
its
related
in
that
shared
repository
that
the
person
before
logger
will
own.
We
are
also
going
to
provide
a
public
copy
of
gh
time
for
other
users,
just
because
I
think
the
ability
to
compare
your
project
with
any
github
project.
For
me,
it's
useful,
even
though
there
are
limitations
too
much
a
farm
provides.
C
A
B
A
H
A
Very
cool
and
then
I
had
one
other
thing:
the
newsletter
old
and
again
I'm,
getting
that
how
on
Tuesdays
I
continued
to
work
on
keeping
it
short
and
sweet.
Alas,
it's
not
for
folks
I'll
continue
to
ask
for
software
updates
every
week.
If
anybody
has
anything
that
they
want
to
put
out
in
the
newsletter.
You
know
who
to
call
just
give
me
a
ring
and
I'll
get
it
into
the
newsletter.
B
B
A
A
And
just
so,
you
all
know
just
if
anybody's
curious,
I
just
rotate
the
headers
so
communities
at
the
top
this
time
next
week
they
will
move
down
to
second
metrics
moves
down
to
the
third
and
software
moves
up
to
the
tab.
So
that's
fine
I,
pretty
quality
in
the
newsletter.
Little
just
rotate,
all
right
cool
and
by
the
way,
I've
gotten
quite
a
bit
of
personal
I,
shouldn't,
say
quite
a
bit,
but.