►
From YouTube: CHAOSS.Community.August.25.2020
Description
CHAOSS.Community.August.25.2020
A
The
community
reports
are
nearly
good
to
go
there's
about
a
12-month
window.
That
will
try
to
be
consistent
for
all
reports
and
we
do
kind
of
have
a
workflow
for
doing
them.
There's
a
little
bit
of
discussion
about
the
design
and
what
kinds
of
information
we
want
to
provide,
but
I
think
mostly
we're
final
and
the
submission
form
that
the
linux
foundation
is
running
for
us
is
isn't,
is
working
and
the
gathering
of
data
and
assembly
reports
there's
a
process
for
that
vanad.
B
Yes,
so
the
process
will
be
like
any
project
or
community
who
wants
to
have.
A
community
report
will
suffer
the
request
on
the
website
and
once
the
request
is
submitted
with
the
desired
information,
they
will
have
the
option.
They
want
the
report
to
be
public
or
they
just
want
a
copy
of
report
and
not
to
be
public
for
everyone.
B
Based
on
that,
the
process
will
be
forwarded,
grammar
chromolab
and
auger.
They
both
will
generate
the
desired
graph
to
graph
some,
both
the
sides
and
once
the
graphs
are
there
I'll,
put
the
graphs
in
the
pdf
format
and
generate
the
report
and
will
submit
it
to
them,
and
if,
if
it
is
made
public,
then
it
will
be
put
on
the
cures
website.
Otherwise
it
will
not
be
there.
A
All
right
that
sounds
good.
Would
you
mind
sharing
the
minutes
on
your
screen,
my
computer
upgraded
to
catalina
overnight,
and
I
have
to
reboot
zoom
in
order
to
share
my
screen.
Apparently,
so,
let's
not
do
that
right.
Now,
it's
just
good
to
have
the
kind
of
agenda
that
we're
going
through
as
part
of
the
recording
makes
it
more
interesting
for
people
they
kind
of
know.
What
we're
talking
about
the
next
thing
on
the
agenda.
Right
now
is
badging
and.
C
We
finished
the
second
pallet
testing,
looks
like
matt
put
his
our
magi
put
his
recommendations
on
here
for
what
we
should
be,
what
he
suggests
for
the
newest
update,
so
we're
looking
at
launching
on
september
14th.
I
think
that
date
is
pretty
set
in
stone
at
this
point
and
exciting
yeah
yeah
we're
really
happy
to
have
the
people
we
did
to
help
build
the
project
and
we're
working
on
getting
reviewers.
D
A
I
don't
think
that
I
think
we
sought
the
assistance
of
somebody
who
understands
matching
colors
to
look
good
for
deciding
on
the
colors
the
logo.
The
letters
in
the
logo
are
just
an
acronym
for
the
working
group
of
the
project,
which
is
community
health
and
open
source
software.
I
think,
is
that
what
it
stands
for.
C
C
A
A
F
A
A
E
What
is
the,
what
is
the
process
going
to
be
to
change
that?
Actually,
because
there
are
I'm
sure
there
are
multiple
multiple
mentions
that
metric
in
yeah
in
other
metrics.
So
so
I'm
just
not
just
changing
three
or
four
metrics
that
use
that
language.
It's
going
to
be
right
going
through
and
almost
every
work
group
is
probably
gonna
have
to
do
it.
Yeah.
B
E
A
A
A
A
Well
so
now
we've
come
full
circle,
because
the
idea
of
so
the
discussion
of
having
a
dictionary
emerged
from
the
confusion
about
the
use
of
this
term,
and
so
we
kind
of
kicked
it
back
to
the
evolution
working
group
to
try
to
come
up
with
a
term
that's
more
clear
and
doesn't
possibly
indicate
something
completely
different,
and
when
we
asked
what
other
metric
terms
that
are
used
are
confusing.
We
didn't
in
previous
calls.
We
couldn't
come
up
with
any.
E
G
Are
there
I
don't,
I
don't
have
a
contacts,
but
I
think
review
is
like
a
pretty
widely
like
used
term,
and
I
don't
know
if
it
I
mean
there
are.
I
mean
it's
not
perfect,
but
I
mean
I
think
it's
going
to
be,
I'm
a
little
worried
that
it
might
create
more
confusion
than
than
than
it's
worth,
and
I
I
think
I
can't
remember
it
was
kevin
or
somebody
else
who
brought
it
up
like
if
it
also
impacts
like
other
working
groups,
then
you
know
forcing
other
working
groups
to
like
to
change
the
terminology.
A
Yeah,
I
I
I
see
that
perspective.
I
have
you,
you
know,
I
only
know
my
own
experiences,
which
are
I've,
only
used
reviews
to
refer
to
code
reviews
and
we
off.
We
get
the
question
a
lot
when
people
first
start
engaging
in
the
evolution
working
group,
they
think
review
means
code
review
to
some
extent,
so.
A
B
E
A
Well,
in
fact
there
is,
you
know,
I
think,
github
as
a
platform
has
begun
to
incorporate
code
reviews
into
the
processing
of
pull
requests.
It's
something
I
think
gitlab
and
garrett
have.
I
think
it's
been
central
to
garrett
from
the
beginning,
as
I
learned
my
garrett
history
from
ildico
and
it's,
I
suspect,
ray
very
commonplace
to
think
of
them.
That
way,
even
though
they're
called
merge
requests
in
the
gitlab
community
that
I
would
be
intuiting
that,
from
your
knowledge
of
gitlab,.
G
G
H
I
don't
know
if
that
view,
point
or
angle
helps
with,
I
don't
know
differentiation
or
figuring
out
how
it's
best
to
phrase
when
it
comes
to
metrics,
but
code
change
is
something
that's
there
and
that
you
view
at
it
and
the
reviewing
is
kind
of
an
action
that
you
go
through
and
provide
feedback
on
the
change
on
again,
whether
it's
code
or
not.
That's
that's
a
sort
of
a
deep
detail
that
we
probably
don't
even
need
to
really
go
into.
E
G
I
mean
the
reviews
could
also
be
done
by
anyone
right.
I
mean
I
don't
think
I
mean
you
necessarily
need
like
a
merge
rights
to
to
provide
a
review.
I
mean
it
depends
on
the
project,
but
I
think
in
most
projects
I've
been
involved
in
anyone
can
chime
in
and
and
provide
a
feedback
like
this
code
is
going
to
break
xyz
and
yeah.
You
don't
need
to
have
like
a
merge
wise
to
do
that,
like
anybody
in
the
community
should
be
able
to
do
it
that
for
for
most
projects
that
I've
been
involved
in.
G
I
mean
if,
if
somebody
has
a
perception
that
review,
we
only
mean
like
code
review.
I
think
it
might
be
better
to
say
well.
Code
review
is,
is
a
component
of
it,
but
it's
review
of
like
anything
right
and
yeah.
So
I
mean
maybe
it's
just
like
an
edification
that
that
we
need
to
do
when
you
people
join,
but.
E
Yeah,
I
mean
that's
just
my
two
cents
but
but
but
once
again
I
would
say:
review
review
handles
that
component
of
from
the
from
the
community
side
right,
it's
the
it's
the
receiving
side,
the
the
person,
the
person,
the
review
itself
or
the
pull
request
itself
is
a
change
that
has
been
submitted
for
review
all
right.
So
there's
there's
two
sides:
it's
the
change
that
has
been
submitted
and
then
the
reaction
to
that
change.
That's
been.
F
F
How
many
people
raise
reviews
on
that
one
thing,
so
I
think
they're
they
could
be
measured
separately
from
the
activity
perspective,
which
would
also
be
nuanced
per
platform.
So
I
don't
want
to
throw
too
much
drama
into
that
because
we're
trying
to
be
consistent
across
as
many
platforms
as
possible,
but
I
think
there
is
still
a
distinction
between
the
thing
and
then
the.
A
A
I
Mentioned
is
very
important
to
pay
attention
of
the
directionality
then
adding
to
like.
I
can
just
borrow
from
the
cathedral
browser
concerning
code
review
or
review
in
general,
where
it
claims
that
many
eyes
can
catch
a
bug
yeah.
So
it
should
really
be
open
to
the
community,
even
though
some
projects
really
like
specify
code
review
as
a
more
technical
incline
thing
which
is
correct
in
that
perspective,
but
only
those
who
really
have
an
expert
knowledge
can
really
do
some
iteration
provide
feedback,
but
based
on
the
fact
that
many
eyes
can
still
catch
the
bugs
better.
A
I
Yeah,
like
the
directionality,
is
what
kevin
mentioned.
I
was
just
saying:
okay,
if
we
look
like
the
cathedral
of
bazaar,
the
award-winning
paper
by
the
linux
foundation,
but
I
think
it
looks
like
over
wait.
Is
that
many
eyes
and
catchy
brick
so
could
we
should
be
open
to
the
community
because
even
a
novice
can
come
in
just
with
a
basic
knowledge
in
let's
a
language
like
pyron
or
c
plus
and
catch
up
a
semi-coma
that
even
experts
have
escaped
it
so
that
iteration
and
then
review
should
not
also
be
limited
to
quote
yeah
yeah.
It's.
A
A
A
E
A
F
A
F
Yeah
I
I
can
raise
that
internally.
I
have
someone
that
I
work
with
at
google.
Who's
been
involved
in
that
initiative,
so
I
can
ask,
what's
the
way
for
for
chaos,
to
support
this
or
or
just
be
engaged,
because
I
think
they
have
a
pretty
extensive
platform
how
they
decide.
Because
right
now
I
saw
some
of
their
notes
and
they're
going
through
user
journeys
and
revamping
some
of
the
common
tables
that
they
have
and
they
have
all
the
analytics
of
who's
actually
been
visiting.
F
What
and
how
so
potentially
changing
some
of
the
dashboards
and
displays
within
devstats
and
trying
to
better
understand
who's
using
it,
and
why
and
so
they're
kind
of
at
more
of
those
formative
conversations.
But
it
seems
like
there's,
there's
still
kind
of
open
road
for
influence
and
discussion,
and
I
I
know
there's
a
lot
of
co-interest
between
these
groups.
So
I
can.
I
can
ask
about
that
and
follow
up
with
this
group
next
week.
A
K
What
are
the
follow-ups
and
what
are
the
rules
against
like
if,
if
anything,
doesn't
happen,
set
of
particular
place?
So
I
I'll
share
the
link
here.
Also,
though,
I
have
been
following
up
with
the
mailing
list
and
recently,
although
I'm
done
with
the
the
two
sections
of
the
handbook,
which
is
the
values
and
the
community
guidelines,
and
now
I
plan
to
work
on
the
section
of
the
working
groups.
So
I
had
some
few
questions.
I
also
kicked
off
the
some
like
thread
like
for
a
discussion
thread
regarding
this
stuff.
B
J
B
That
evolves
over
the
discussion
and
I
can
share
the
example
of
value
working
group
which,
which
was
revamped
recently,
so
in
that
there
were
different
proposals
going
on
for
the
focus
area.
Initially,
everybody
was
proposing
metrics,
but
it
was
not
clear
like
how
it's
going
to
support.
So
the
discussion
was
okay.
We
need
to
have
a
like
focused
direction
where
we
can
see
a
different
group
of
matrix
fits
in
that
so
with
the
discussion
within
the
community,
those
focus
areas
are
decided
or
evolved
once
they
are
evolved.
B
B
K
J
I
can
also
add
some
history
here.
The
first
working
group
that
we
started
at
chaos
was
the
diversity
and
inclusion
working
group
and
the
focus
areas
were
informed
by
research
that
emma
urban
has
done
at
mozilla
and
said.
The
research
showed
that
a
diverse
and
inclusive
community
has
these
aspects,
and
then
we
used
each
of
those
as
a
focus
area
where
we
wanted
to
develop
metrics
to
understand.
If
those
aspects
are
present,
the.
A
Oh,
I
was
the
long
history
is
we
had
a
with
a
software
group
and
a
metrics
group,
and
then
we
developed
these
working
groups,
and
I
remember
diversity
of
inclusion
and
evolution,
which
was
called
growth,
maturity
and
decline
at
the
time
as
the
first
two.
I
don't
remember
the
order
they
emerged
in,
though.
J
J
J
Yeah
they
agreed
both
were
started
after
the
open
source
summit
in
I
forgot
where
I
think
in
san
diego
and
the
way
those
working
groups
started
out,
the
their
focus
areas
was
based
on
focus
groups.
We
did,
I
remember,
sean
you,
let
a
focus
group
at
the
conference.
Maybe
there
was
leadership
summit.
I
think.
B
J
Asking
hey
what
if
you
hear
risk?
What
are
the
different
things
you
think
about
for
risk
and
then,
through
this
working
group,
we
came
out
with
business
risk
and
license
risk
and
all
of
those
different
risk
types
and
those
informed
the
working
the
focus
areas.
And
then
we
started
developing
metrics
for
each
focus
area.
A
A
There's
an
idea
and
a
group
of
people
start
working
on
that
idea
and
forming
metrics
around
it
and
at
some
stage
it
gets
reshaped
or
something
significant
reshapes
it
once
at
least
and
then
the
work
continues.
So
I
think
the
first
phase-
and
I
think
the
case
of
every
working
group
are
common
so
far
has
been
we.
The
group
starts
out
with
one
set
of
ideas
and
by
doing
the
work
that
and
getting
input
from
the
community
that
it
evolves
to
a
separate,
not
always
completely
different,
but
then
it
evolves.
A
J
K
Yeah,
so
what
so,
I
think
like
I
would
require
to
get
through
all
the
stuff
which
is
already
available
on
the
website
or
on
the
repositories
and
understand
this
stuff
again.
So
probably
like
for
writing.
This
particular
thing.
I
need
to
know
each
and
every
aspect
of
the
working
groups
right.
So
that
is
what
I
wanted
to
kick
off
through
the
ruling
list,
like
yeah.
A
I
wonder
if,
through
the
through
the
manual,
if
the
purpose
might
be
to
discuss
how
a
working
group
is
formed-
and
maybe
some
discussion
of
the
experience
of
existing
working
groups
is
that
after
formation,
they
they
go
through
evolution,
they
don't
necessarily
stick
with
exactly
the
same
ideas
that
got
them
started
like,
instead
of
instead
of
trying
to
present
a
handbook
formula
for
how
do
you
curate
a
working
group?
Let
people
know
that
it
can
be
messy.
K
A
Yeah,
I
don't
think
you
want
yeah.
I
don't
know
this
thing.
I
don't
think
you
want
to
make
it
a
history
manual,
but
I
think
presenting
the
idea
that
working
groups
come
together
when
people
think
there's
a
collection
of
metrics
that
belong
in
one
and
often
they.
The
initial
idea
that
got
a
working
group
started
changes
as
that
working
group
does
its
work.
I
think,
setting
the
expectation
that
you're
not
expected
to
imagine
a
working
group
or
contribute
to
a
working
group
and
that
what
that
group
is
focused
on
remains
static.
J
A
J
J
K
A
Really
great
meeting
everyone
good
discussion
about
a
lot
of
important
things,
but
everybody
was
here
and
please
do
if
you
have
the
opportunity
come
to
the
monthly
meeting
next
week
and
we
can
get
a
little
bit
more
discussion
on
some
of
the
more
engaging
topics
that
we
had
to
talk
about
here
today
and
hear
hear
more
exciting
news
about.
What's
going
on
in
chaos,.