►
From YouTube: CHAOSS.Common.March.19.2020
Description
CHAOSS.Common.March.19.2020
B
B
B
A
D
D
D
B
B
D
B
Would
be
easier
if
we
had
if
we
had
more
space
like
the
last
house,
I
lived
in
in
the
US
I
had
you
know
two
extra
rooms,
so
we
can
have
like.
You
know
two
offices,
but
here
we
have.
We
have
one
office,
so
we
just
have
to
we're
literally
sitting
down
at
the
beginning
of
every
morning
and
comparing
calendars
and
deciding
who
gets
the
office
one
because
the
office
is
the
place
that
the
where
you
can
plug
into
the
you
know
directly
into
the
ethernet
cables.
So.
B
E
D
B
E
E
Have
noticed
a
lot
of
my
folks
on
my
projects,
this
is
like
especially
my
colleagues
in
the
motion
picture
industry.
They
I
mean
they've,
basically
like
shut
down
all
of
their
community
meetings
all
week.
Is
there
like
figuring
out
how
they
can
work
for
calm,
because
a
lot
of
those
people
like
work
like
disconnected
from
the
internet
on
big
rendering
farms
and
stuff?
Oh
my.
E
B
D
D
E
B
A
A
B
Okay
and
then
the
other
thing
we
had
so
we
have
the
the
next
two
agenda.
Items
are
kind
of
kind
of
the
same
thing,
so
the
spreadsheet
that
we
have
is
it's
really
just
the
release
spreadsheet.
So
if
you
go
to
the
common
tab,
you
can
see
some
of
the
ones
that
we've
sort
of
been
considering
or
we
started,
looks
like
types
of
contributions.
We
can
move
that
to.
A
B
A
B
B
B
A
This
one
is
yes,
we
looked
at
it
or
commits
RemoteApp
can
go
down
into
the
comments
and
how
many
pints
were
added
to
move
things
and
how
many
files
were
touched.
That
was
enough,
documented
anywhere.
So
the
way
that
I
see
this
is
types
of
contribution
is
apparent
and
then,
underneath
that
for
each
of
the
items
in
our
long
list,
you
can
have
a
separate
metric
that
defines
what
that
data
is
where
to
get
it,
how
to
calculate
it
and
neutral
value
neutral.
A
So,
unlike
diversity,
inclusion
or
we
have
39
go
or
revolution
that
we're
trying
to
understand
how
project
evolves
in
common,
we
can
just
say,
is
the
plumbing
on
how
to
get
the
metric
and
lines
and
files
is
like
the
pile
of
commits
or
types
of
contributions,
as
the
parent
then
commits
as
one
of
the
types
of
funding
with
that
in
mind
and
file
test
piece
of
information
or
sub
metric
of
that.
That's
how
I
see
you?
Okay,.
B
E
A
A
B
Problem
I
have
with
that
approach.
Is
that
we're
going
kind
of
these?
These
are
gonna,
be
a
lot
of
these
are
gonna,
be
really
qualitative
and
sort
of
difficult
to
define,
because
it's
it's
gonna
be
different
for
each
project.
You
know
what
I
mean
like
I
feel
like
we
already
have.
The
data
collection
strategies
are
kind
of
there
and
I.
Don't
know
that
we
need
to
go
into
a
bunch
of
detail
in
each
of
the
individual
contribution
types.
C
A
B
B
F
B
D
Probably
language
distribution,
you
know
we
have
pretty
good
information
about
how
much
of
each
language
is
actually
used.
The
new
particular
project
that
would
be.
That
would
be
something
I
think
it's
a
common
working
group
issue,
we're
looking
at
code,
complexity
and
risk
and
that's
more
of
a
algorithmic
measure.
D
B
C
A
D
A
And
then,
but
maybe
we
can
bring
that
over
to
common,
that
we
have
as
a
funded
reason
a
commit
as
a
type
of
company
and
then
for
the
commit.
You
can
look
at
lines
and
files.
We
can
look
at
ties
and
they're
starting
to
build
a
tree
of
specificity.
I
think
I'm.
Certain
I
have
is
putting
all
that
out
into
different
metrics
or
whether
be
stopped
at
permits
and
make
lines
and
files
and
sighs
as
like.
D
D
On
akavit
guy
by
commit
basis,
but
I
think
pedo
I'm
more
interested
in
those
as
sort
of
aggregated,
metrics
and
I,
don't
know
because
I
actually
think
lines
and
files
are
filters
on
commit.
I'd
have
to
go
back
and
look
so
when
I
think
of
size
of
commit
and
size
of
pull
requests.
I'm
really
thinking
about,
like
a
almost
like
a
mean
sighs.
B
A
C
D
If
I
look
across
what
the
current
state
of
any
project
is
in
that
that
number
doesn't
shift,
the
distribution
doesn't
shift
wildly
over
time.
So,
if
I,
if
I
measure
the
lines
of
code
in
each
language
or
the
number
of
files
in
each
language
at
a
point
in
time,
its
avert
that
those
are
very
slowly
moving
pie,
chart
relationships,
I
guess.
D
Besides
of
I
mean
so
we
get
a
looking
a
little
bit
confused
when
I,
say
distribution
of
language,
but
size
of
commit
is
the
number
of
lines.
Added
number
of
lines
are
moved
number
of
files
added
number
of
files
changed.
You
know,
there's
a
couple
of
different
ways
to
evaluate
it.
The
size
of
size
of
commit
is
some
number.
It's
number
of
files.
A
C
B
D
Yeah
and
right
and
I
think
people
are
not
interested
in
discrete
commit
data
that
are
interested
mean
the
aggregations
across
like
over
a
month
of
commits.
What's
the
average
number
of
lines
added
removed,
whitespace
number
of
files
touched,
and
yet
you
know
so
I.
It
gives
you
a
sense
of
how
the
project
is
working
here.
Who
is
how
different
people
are
working
on
a
project.
B
D
B
Okay,
so
it
looks
like
we
have
three
three
separate
metrics
or
groups
of
metrics
that
we
can
start
working
on
next.
One
is
language,
distribution
commits
or
code
changes,
go
changes,
lines
and
pull
requests.
Does
anybody
want
to
pick
up
one
of
those
and
create
an
issue
and
create
a
dock
for
it
and
get
started
on
it?.
D
C
A
D
D
A
The
office
first
ones
around
evolution
are
just
up
from
back
when
we
started
the
chaos
project.
I
think
we
can
almost
get
rid
of
them
and
just
clean
up,
because
we
have
taken
that
and
created
the
review
points,
and
maybe
one
or
two
that
are
still
like
for
the
first
comments.
I,
don't
think
we
have
an
excellent
review
comments.
C
A
B
D
B
D
What's
been
defined,
our
reviews
accepted
refused
declined
and
reviews
duration,
which
are
not
actually
defining
a
review
right.
So
the
actual
definition
of
a
review
of
a
pull
request,
whatever
I
Ono
there,
no
I'm,
sorry
I,
take
that
back
reviews,
although
I
think
I,
don't
know
what
this
there
is:
a
reviews
metric
or
at
least
I'm,
going
to
look
and
see
what
it
is.
D
D
D
B
D
D
B
B
I'm
I
guess
I'm
sort
of
of
the
mind
that
if
it's,
if
it's
already
been
defined
in
one
of
the
working
groups,
I
wouldn't
worry
too
much
about
moving
it
around
or
I
mean
if
both
Garriga,
both
you
and
Sean,
feel
like
this
is.
This
is
pretty
much
done.
Let's
spend
our
time
in
other
places
and
we
could
always
come
back
to
it.
B
C
D
B
D
B
B
B
D
B
B
D
D
Blah
blah
I,
don't
know
I
guess
there
are
some
kinds
of
events
that
that
occur
and
require
attention,
but
don't
ever
enter
a
closed
state,
so
implicit
in
the
time
to
closes
that
there
must
be
an
open
state
for
an
event.
So
my
comment
on
an
issue
may
require
attention,
but
it
won't
be
closed
ever
so.
It's
a
it's
a
type
of
event.
That's
like
issues
and
pull
requests
are
the
two
I
can
think
of
that.
Have
both
open
and
closed
states.