►
From YouTube: CHAOSS.Weekly.January.29.2019
Description
CHAOSS.Weekly.January.29.2019
A
The
way
I
have
to
tell
you
that
I
took
I,
took
the
children
to
see
The
Sound
of
Music
in
Kansas
City
last
weekend.
I
had
no
idea
that
that
mr.
von
Trapp
Captain
Von
Trapps
first
name
was
Georg
like
somehow
that
escaped
me
through
many
childhood
watchings
of
that
so
I,
just
like.
Oh
my
god,
I
know
again
in
geared
now.
A
B
B
Okay,
earlier,
though,
we
have
the
application
for
cool
some
of
code,
complete
all
of
the
sections
are
written.
Now
we
just
have
to
wait
for
the
deadline
to
see
if
Google
wants
to
accept
us
or
not.
As
we
are
doing
this,
we
are
also
working
on
the
ideas
which
are
so.
These
are
project
ideas
and
we
are
located
on
github
in
the
governance
repository
and
we
have
one
idea
already
merged
and
then
three
more
in
the.
A
A
Basically,
when
I
did
a
when
I
pulled
the
repository
I
had
an
MP
file,
so
I
filled
the
empty
file
and
all
the
information
was
in
these
other
polar
like
what
other
people
were
doing
worse
in
other
pull
requests
and
is
the
intention.
Then
it
will
have
one
document
at
the
end.
Yes,
we
merged
all
the
doctors
of
emergency.
Okay,.
B
That
the
comment
is
that
the
description
as
it
stands
now
is
very
detailed
and
uses
a
lot
of
lingo.
That
makes
sense
to
us
as
Kaos
project,
but
I
doubt
someone
who
is
from
the
outside
would
have
a
that
is
good
time,
understanding
or
knowing
what
it
is.
Okay,
I
think
we
would
benefit
from
I
want
to
say
dumb
it
down
good.
Take.
A
A
B
B
B
C
A
A
So
do
you
want
to
talk
about
the
distinct
since
you're
on
the
mic?
You're
gonna
talk
about
the
difference
between
work
group
and
working
group,
which
my
simple
mind
doesn't
know
what
the
difference
is,
but
there
must
be
some
sort
of
nuanced
difference.
That's
important
to
somebody
since
it's
a
discussion
item
no
I.
B
A
B
Group
is
more
general,
no
working
group
specifically
is
people
working
together
to
do
something
I
say:
where's
work
group
can
also
refer
to
infrastructure.
You
know
how
Windows
has
work
groups,
yeah,
I,
know
you're,
saying
yeah,
so
it
looks
like
working
group.
Is
the
term
most
used
and
dawn
yesterday
as
well?
So
it
sounds
like.
C
A
C
A
quick
one,
I
did
I,
did
go
ahead
and
schedule
the
new
working
group,
the
common
metrics
working
group.
So
it's
going
to
be
on
Tuesdays
right
before
this
meeting,
but
not
this
week
next
week
and
then
every
other
week
we
have.
We
have
a
bit
of
an
issue
because
I
have
a
conflict
with
this
week.
That's
I
have
some
every
other
week.
Meetings
that
are
on
this
week
and
Brian
profit
has
some
every
other
meetings
that
are
on
the
opposite
week.
So
I
you.
C
C
Safe
but
but
yeah
so
anyways,
it's
gonna
be
starting
next
week
and
it'll
be
the
hour
before.
Where
this
meeting
that's
my
only
only
real
update.
The
other
thing
we
should
probably
talk
about
briefly.
Is
chaos
con.
Unless
are
there
any
questions
about
the
new
working
group
I
think
we
got
the
pull
requests
merged
on
the
website.
I
didn't
actually
check.
I
saw
Kevin's
email.
B
C
And
Sean,
you
should
have
a
look
at
it
as
well,
because
I
changed
bunch
of
stuff
in
your
working
group
because
I
based
on
the
email
that
the
last
email
that
I
had
seen
from
you
about
when
the
meetings
were
we're
not
the
same
as
what
was
on
the
website,
so
I
changed
it
based
on
what
you
had
set
in
the
email.
That's
just
chicken
yeah,
just
don't
check
and
make
sure
I
didn't
screw
anything
up
for
you
I
doubt
you
did
I'll
check
cool
and
I
added
the
compliance
and
risk
subgroup
meeting.
C
A
C
Race,
so,
just
just
as
a
reminder,
chaos
Khan
is
on
Friday.
I
am
going
to
Brussels
tomorrow
me.
A
C
I
have
a
to
do
group
meeting
on
Thursday,
so
I'm
there
for
that
as
well.
So
it's
just
like
so
many
things,
Foss
that
was
just
non-stop
all
all
day
every
day
until
I
leave
but
it'll
be
it'll,
be
fun.
Lots
of
fun
people
going
but
I
think
in
the
last
meeting,
Rhea
agreed
to
basically
MC
chaos,
:
so
he'll
be
introducing
the
speakers
and
helping
everybody
keep
on
time.
C
B
C
A
C
C
C
Sis
has
usually
done
it
because
it
used
to
be
a
kind
of
aperture
gia,
but
they
sort
of
organized
it
in
the
past.
I
think
it
was
in
this
list.
At
this
last
meeting
we
decided
that
Ray
would
do
it
I
think
it
was.
My
preference
is
to
have
someone
more
neutral.
Do
it
someone
who's
not
affiliated
with
one
of
the
one
of
the
companies
that
does
stuff
in
the
space
I
think
so
I.
Think
Ray
is
a
good
device
agreed.
B
D
D
Right
yeah,
it
didn't
fit
into
the
the
mode
of
a
use
case
so
easily.
D
A
A
A
So
the
current
metrics
repository
contains
a
bunch
of
files
for
metrics
that
have
been
renamed
in
the
in
the
growth
maturity
decline,
working
group
specifically,
so
the
the
duplicate
note
quote-unquote,
is
simply
a
an
index
to
which
so
like.
If
you
look
for
the
number
two
there's
in
me
there,
this
might
be
one
where
there's
not
two
of
them,
but
usually
they
are
yeah.
B
A
Just
closed
closed
issues
right
so
it's
it's
essentially
trying
to
maybe
I-
should
have
explained
that
somewhere,
it's
an
index
to
so
that
you
can
see
which
to
that
I'm
saying
are,
are
the
same
and
then
they're
literally
the
same
like
I
opened
up
the
files,
and
the
only
thing
that's
different
in
most
cases
is
that
one
of
them
contains
the
template
about
what
to
put
under
a
heading
and
the
other
doesn't
so.
But
but
it's
the
same,
it
is
the
same
metric.
A
I
was
concerned
that,
without
this
reconciliation,
the
the
working
group
would
start
potentially
working
on
metrics
that,
because
you
look
at
them,
there's
like
60
here
could
potentially
start
working
on
metrics.
That
have
been
renamed
or
70
or
80.
The
head
pins
have
been
renamed
right
and
then
it
would
be
even
more
confusing
cuz
like
no
girls,
much
routing
declines,
not
doing
closed
issues
or
they're,
not
doing
issue
they're
not
doing
closed
tissues.
So
let's
do
that,
but
they
are
doing
issues
closed.
You
know
see
I'm
saying
so.
C
A
D
A
I
think
that
was
probably
better
I
think
there
are
the
one
commit
that
I
think
your
had
a
question
about
was
whether
I
think
the
consensus
is
to
remove
the
archived
metrics
from
this
commit
and
address
them
separately.
So
on
the
growth
maturity
decline
project,
a
number
of
the
activity
metrics
were
quote-unquote
archived
and
put
into
a
separate
folder
yeah.
D
A
D
B
Would
rather
have
everything
in
the
same
branch
if
he
do
need
to
have
an
archive
than
directory
makes
more
sense
to
me,
because
if
I
come
to
the
positive
or
II
I
I,
don't
know
how
I
would
ever
figure
out
that
there
should
be
a
different
branch
except
we
mention
it
in
the
readme,
but
then
aligning
those
again
I.
Think
it's
easier
to
keep
everything
straight
in
one
branch
than
across
branches.
A
So
the
intention
of
the
stated
the
intention
of
the
archive
is
that
at
the
very
start
of
the
project,
we
enumerated
a
lot
of
specific
metrics
I.
Think
in
many
cases,
based
on
things
that
some
people
were
already
calculating
about
their
projects
and
in
the
course
of
creating
the
working
groups,
some
of
them
got
sort
of
archive,
like
we
decided
in
the
work
inserting
a
client
working
group,
but
in
the
diversity
inclusion
working
group
that
we
were
no
longer
going
to
attend
to,
though
metrics
and
yes,
mostly
it's.
A
D
A
C
A
A
C
I
think
that
makes
sense
I
mean
I
I.
I
wouldn't
archive
any
metrics
that
just
because
a
particular
user
particular
working
group
isn't
tracking
those
anymore
because
that's
kind
of
the
purpose
of
the
metrics
apposite
ori.
So
we
should
just
keep
those
there
for
people
to
use
if
they,
if
they
want
them
and
like
you
said
I
mean
augur,
has
already
implemented
some
of
them
so
they're
they
have
their
uses
for
sure.
C
D
Isn't
that
how
a
lot
of
this
stuff
gets
done
right
instead
of
scratching
your
own
itch
it's
taking
drugs
for
your
headache,
yeah.