►
From YouTube: CHAOSS.Common.April.16.2020
Description
CHAOSS.Common.April.16.2020
https://docs.google.com/document/d/1xsii5tfmmDwWpuhrFcBJMeYeT3RipJdiCdHrbi0NalQ/edit#heading=h.n3rh3l1y6dv7
A
B
A
A
A
So
this
is
a
way
for
us
to
release
metrics
on
a
kind
of
a
faster
cadence
than
the
every
six
months
cadence,
so
the
way
that
it
works
and
we've
kind
of
been
working
through
this
is
the
metrics
themselves
will
be
released,
we'll
get
them
up
on
the
webpage
and
there
will
actually
be
a
small,
temporary
disclaimer
on
that
metric.
That
will
just
say
this
metric
was
part
of
the
continuous
release
it'll
in
is
capable
of
actually
changing
during
that
small
window
before
the
six-month
official
release
or
the
six
month
six-month
release.
A
All
right,
that's
kind
of
the
process
that
we're
gonna
go
through
here,
so
I
I
think.
What
is
this
agenda
item
is
trying
to
put
closure
to
this
metric,
giving
Kevin
the
green
light
to
get
this
metric
up
on
to
the
website,
such
that
it's
part
of
that
continuous
release
and
then
come
July
or
whenever
we
do
our
next
six-month
cadence
release
it'll
kind
of
be
hardened
at
that
point
kind
of
put
the
closure
at
that
point,
questions
on
that
process
and.
B
I
think
in
the
last
meeting
this
is
probably
a
poorly
worded
agenda
item
I
think
in
the
last
meeting
we
did
decide
that
the
thing
metric
was
final
and
that
we
were
ready
for
it
to
be
released,
but
I
think
we
were
trying
to
remember.
We
were
talking
to
Kevin
about
the
best
way
to
do
this.
Is
there
anything
else
you
need
from
us
Kevin?
Sorry,
you
might
need
to
refresh
my
memory
on
what
we
talked
about
last
week.
D
So
in
the
in
the
community
meeting
this
this
week,
we
kind
of
hashed
out
some
of
the
the
minor
details,
so
I
think
the
there
are
two
things
that
we
would
need
from
the
work
group
for
the
metrics
release.
One
is,
we
need
to
add
a
label
to
the
top
of
the
metrics
page
that
states
what
Matt
had
said
earlier
and
then
the
other
thing
is,
you
need
to
create
a
metrics
released
issue.
D
B
D
D
Then
other
than
that
I
suppose
there
there
needs
to
be
some
sort
of
notification
process
which
I
don't
know.
If
that's
just
a
shout
out
to
me
or
a
shout
out
on
to
the
email
list
to
say
that's
going
live
but
either
way
I
can
at
that
point
I
would
once
the
once.
The
message
is
on
there.
I
will
I
will
take
the
the
metric
live
on
to
the
website.
B
B
D
C
D
B
A
A
Mean,
depending
on
when
we
finish
here,
I
could
probably
do
it
today.
How
about
this
I'll
try
to
do
it
today
and
if
I
don't,
if
I
do
and
I'll
ping
you
in
the
actually,
while
we
really
easy
while
we're
here,
could
we
just
for
the
release
notes?
What
do
we
want
to
say,
because
if
we
could
just
write
this
up
now,
then
I
can
get
it
up
in
the
issue,
so
I
mean
that
really
this
is
a
new
metric.
B
A
And
that'll
help
because
the
next
thing
is
to
review
action
items
from
the
previous
week
and
I
didn't
do
mine
from
the
previous
week
and
so
look
at
her
from
the
previous
two
weeks
ago.
If
you
scroll
down
to
the
meeting
minutes
from
April
2nd,
there
were
three
people
that
had
action
items
myself
me
at.
F
F
E
F
B
F
E
F
B
B
F
C
G
Be
there
now
is
this
referred
to
the
host
machine
or
what,
if
you
do
in
bed
development
I
mean
it
has
a
very
different
meaning?
If,
if
you
develop
for
your
main
computer
or
you
develop
on
your
computer,
foreign
language
is
the
hardware
diversity
here.
Is
it
the
Lenovo
or
or
ThinkPad,
or
is
it
the
dragon
board
or
people
phone
or
Arduino?
G
F
G
A
E
A
This
concept
of
the
politics
of
Technology,
right,
mm-hmm,
and
so
not
politics
like
political
but
like
what's
embedded
in
a
technology
and
so,
for
example,
with
a
lot
of
the
homeschooling.
That's
going
on
right
now.
You
know
this
students
being
home
there's
a
lot
of
real
limitations
that
folks
have,
if
they
don't
have
Wi-Fi
at
home.
If
they
have
a
shared
computer
in
the
house
and
what
that
does
to
inherently
limit.
A
Ability
to
get
schoolwork
done
and
it
continues
to
create
a
class
separation
of
have
have
nots
and
that
a
toy
outreach.
He
approaches
this
issue
as
well
I'm
talking
about
what
are
the
minimum
requirements,
technology
requirements
necessary
to
get
work
done
in
your
project
and
I'm
I'm,
wondering
like
almost
from
an
inclusion
perspective
if
open
source
communities
have
really
fairly
high
technical
barriers
to
have
in
front
of
them
to
even
be
a
participant
in
that
community.
So
there's
certain
styles
of
machines
you
have
to
have.
There
are
certain
pieces
of
software.
You
have
to
have.
C
F
A
F
I
hadn't
thought
about
it
that
way,
but
that's
certainly
your
example
of
students
being
at
home
and
having
why
and
technology
gaps
is
very
real
and
I.
Think
the
same
technology
gap
exists
for
any
kid.
You
would
want
to
get
involved
in
open
source
right.
They've
got
to
have
a
certain
level
of
computer
and
a
certain
level
of
internet
connection.
To
do
anything.
E
C
C
We
could
suggest
in
the
Commons
one,
please
fix
it
fix
the
DCO.
If
you
resubmit,
this
seems
to
be
it
more
appropriate
for
the
DNI.
Would
you
mind
opening
a
pull
request
and
three
we'd
like
to
see
a
comment
in
the
pull
request
for
explaining
a
little
bit?
Why
you're
submitting
this
and
what
this
is
doing?
Because,
right
now
the
pull
request
message
is
empty.
So
those
are
the
three
piece
of
feedback
that
I
would.
B
I
almost
wonder
if
this
should
be
if
there
should
be
two
metrics,
so
one
is
like
on
the
DNI
side
and
inclusivity
as
it
relates
to
the
hardware
that's
available
to
people,
but
is
there?
Is
there
another
aspect
of
this
that
should
be
in
another
working
group?
For
example,
you
know
around
like
the
yeah
I,
don't
know
what.
B
B
Guess
let
let
me
let
me
reframe
this
I'm
wondering
what
the
person
who
submitted
this
really
really
intended
for
this
metric
like
do
they
really
mean
it
from
an
inclusivity
standpoint,
or
do
they
really
mean
it
from
from
some
other
aspect
that
maybe
we're
not
understanding
based
on
just
reading
the
the
metric,
because
it
says
the
you
know
like
the
objectives,
determine
what
affects
Hardware
has
on
development.
That's.
F
B
A
B
Yeah
because
you
know
looking
again
looking
at
the
objectives,
you
know
things
like
determine.
If
hardware
has
an
effect
on
frequency
of
development
yeah,
you
could
conceivably
put
some
kind
of
I.
Don't
know
some
kind
of
statistical
model
behind
whether
or
not
your
I
don't
know
if
you
have,
if
you
have
better
hardware,
do
you
have
more
commits
I,
don't
know,
but
that's
what
kind
of
like
determine
if
hardware
has
an
effect
on
the
frequency
of
development,
that's
what
I
think
of.
A
B
D
H
E
B
A
A
Stop
sharing
my
screen
by
the
way
I
did
I
did
look
at
zoom
as
cloud
recordings
and
the
ability
error
a
screen
and
keep
a
grid
view
of
all
people.
Not
done
that
doesn't
happen
can't
happen
so
because,
right
now,
if
we
share
a
screen,
it
shows
the
video
of
the
person
talking
I,
say:
who's
sharing
their
screen
or
the
person
talking.
So,
if
I'm
sharing
my
screen
and
you're
talking,
it
would
show
you,
okay,
I
would
just
cuz
like
right.
Now,
it's
recording
in
grid
view
it's
just.
This
is
I.
A
C
B
C
A
D
One
thing
one
thing
we
might
think
about
as
far
as
connecting
the
video
to
the
document
is
when
we,
after
we
record-
and
we
say
you
know-
welcome
to
the
meeting-
we
usually
put
the
the
link
of
the
document
in
the
chat,
but
not
that
link
isn't
available
in
the
chat
for
the
video
either.
So
perhaps
we
could
just
mention
where
the
where
the
viewer
can
see
the
document.
Okay,
welcome
to
common
the
the
agenda
document
is
available
on
the
website
X
and
the
and
the
link
is
in
the
chat.
C
A
C
A
A
F
A
F
I
C
That
we
were
talking
about
the
what
in
Category
narrow
metrics
what
types
of
contributions
and
we
said
commit
is
so
essential
that
we
should
define
this
and
then
be
stalled
because
we
know
evolution
has
already
done
a
lot
of
work
on
defining
commits,
and
so
this
action
item
for
dawn
is
to
look
at
evolution
and
see
because
there
was
something
we
wanted
to
move
into
common
or,
if
there's
something
we
wanted
to
add.
On
top
of
that,
based
on
the
conversation
beyond
I
see.
A
A
C
E
A
E
A
A
C
A
A
C
C
I
Happening
I
think,
for
example,
we
open
source
software
in
different
different
gauges.
For
example,
kids
have
kid
lab
and
Chinese
Chinese
github.
You
can
see
Kitty
number,
we
open
source
project
post.
All
of
the
all
of
that
kick
code
club
could
cup
so
I
think
it's
a
a
different
platform
for
us
together
to
call
local
collaboration.
I
I
I
E
A
D
D
D
A
C
C
A
F
A
F
F
Do
is
it
like
under
description
yeah.
Those
are
reviews,
because
that
the
review
is
what
we
call
a
pull
request
and
a
code
review
is
something
different
entirely
and
I.
Don't
think
we're
doing
time
you
close
with
code
reviews,
because
that's
not
closing
anything
so
just
say,
issue
review
or
support.
F
A
C
F
F
C
F
A
You
can
clean
up
for
these
things.
Go
I
almost
wonder
so
this
seems
like
at
trick
did
is
gonna
have
a
fair
amount
of
tooling
behind
it
between
grimore,
lab
or
auger.
You
know
what
I
mean
like
this
time
thing
so,
whether
it's
time
to
time
to
close
a
pull
request
or
time
to
close
an
issue,
I'm
wondering.
A
It
seems
like
we're:
gonna
have
under
implementation,
visualizations
and
tools,
providing
the
metric
filled
out
pretty
robustly
right.
So
here's
a
bunch
of
visualization
here's
a
bunch
of
tools
that
will
do
this
so
with
respect
to
data
collection
geez.
When
does
anybody
have
thoughts
as
if
we
would
keep
that
as
a
subsection?
You
know
some
of
the
metrics
have
data
collection
strategies
like
it's
kind
of
a
thorny
metric.
C
Yeah
I,
don't
effort
to
opinions
on
this
one
is
I.
Would
hey
I
would
like
the
metrics
to
be.
You
know
as
much
detail
as
possible
to
describe
someone
how
to
implement
it
and
have
it
stand
right
so
that
we
can
have
those
kinds
of
pickups
that
we
talked
about
a
while
ago.
We
can
pitch
the
different
implementations
and
against
each
other
and
see
how
they
compare
implementing
what
we've
outlined
and
then
the
other
opinion
that
is
opposite
to
that
is:
let's
keep
it
as
simple
as
possible.
F
Okay,
we
have
endpoints
that
reflect
different.
They
essentially
perform
the
same
function,
but
there
were
different
names
for
them
at
different
times
so
issue
duration
is
also
included
and
I'd
have
to
go
back
and
look
at
the
history
of
the
chaos
metric
at
one
time,
both
of
those
things
were
released.
Chaos
metrics,
it
looks
like
issue.
Duration
is
the
one
that
continues
to
be
a
chaos
metric
and
the
other
one
is
not
the
name
of
a
chaos
metric,
so
I
need.
F
Those
are
two
examples
for
shoes
and
I
know:
I
think
it's
in
Andrew
brains,
branch,
the
metrics
that
we
have
for
pull
requests.
We've
developed
a
ton
of
new
metrics
for
pull
requests,
closing
duration
and
first
response
duration.
We
just
haven't
released
them,
yet,
no,
probably
in
our
next
release,
we're
waiting
to
add
things
from
people's
branches,
because
we're
we're
doing
final
testing
on
the
next
next
release.
Okay,.
A
Well,
I
made
a
few
points
and
I
think
we
can
write
pick
this
up
in
two
weeks,
but
we're
just
adding
a
bit
here
to
implementation,
stuff
mm-hmm
with
visualizations
I.
Think
I
can
probably
do
you
know
here
and
just
clean
this
up
yep
and
then
we
can
talk
about
to
your
point
whether
or
not
we
include
data
collection
strategies
to
be
part.
F
Okay,
so
like
it
can
look
sometimes
like
an
issue
gets
from.
We
don't
know
why
it
is
you
get
three
opened
right
and
only
the
the
owner
of
that
repo
understands
their
practices
surrounding
reopening
an
issue.
I
mean,
maybe
that's
a
would
that
be
a
filter,
probably
yeah,
I
think
it
probably
should
be
because
if
you
just
look
at
the
final
closed
date,
you
could
be
missing
like
sometimes
they
read
their
reopens
like
a
long
time
after
their
original
enclosed
okay.
So
you
might
want
an
initial
closed
date
or
you
might
want
final
closed
date.