►
From YouTube: CHAOSS.Community.June.2.2020
Description
CHAOSS.Community.June.2.2020
A
All
right,
everybody
welcome
to
the
chaos
monthly
meeting,
so
this
is
where
we
will
kind
of
walk
through
the
working
groups
and
the
software
and
get
updates
from
folks
as
they
are
on
the
line.
B
A
See
why
don't
we?
Why
don't
we
go
ahead
and
get
started?
We'll
start
with
updates
from
metrics
working
groups?
I
might
go
and
slightly
reverse
or
do
not
reverse
order
here,
but
out
of
order,
I'm
gonna
start
with
DNI.
If
that's
all
right
with
you,
Georg
I
know,
you
were
on
the
call
on
last
week
and
I
wasn't
able
to
make.
B
B
On
metrics,
we
have
several
metrics
that
we're
working
on
inclusive
leadership
is
a
metric.
The
post
by
Mr
Irving
they've,
been
working
on
issue
tracker
facility
proposed
by
Marianne.
We
have
been
working
on
the
documentation,
accessibility,
metrics,
which
we're
still
in
the
process
of
breaking
out
into
three
metrics,
the
the
other
thing
that
we
always
talk
about,
the
updates
from
our
go
somewhere
code
and
I
thought
you
student,
but
that
falls
under
badging.
A
B
A
B
A
Good
to
know
the
only
reason
I
asked
I'm
trying
to
get
some
sense
of
what
the
next
release
is
going
to
look
like
now.
Now
that
we're
kind
of
three
weeks
out
from
asking
the
working
groups
to
call
closure
to
some
of
their
work.
So
they
can
release
the
metrics
for
public
comment.
So
all
right,
cool
anything.
A
A
Call
let's
go
ahead
and
do
that
so
you
moved
it
up.
So
thank
you.
So
if
you
take
a
look
at
the
top
of
the
minutes,
we've
always
been
kind
of
talking
about
an
August,
ish
release
and
I.
Think
in
the
last
community
call
I
think
it
was
last
Tuesday
we
kind
of
settled
on
August,
first
thanks,
Garrick
and,
and
that
would
I
guess
first
represents
the
release.
A
A
So
that's
that's
a
four
week
period,
so
you
can
kind
of
see
that
one
week
of
getting
things
onto
the
website
plus
four
weeks
of
public
comment
is
five
weeks,
and
so,
if
we're
aiming
for
an
August
first
release,
we
need
five
weeks
prior
to
August.
First
for
the
work
in
the
working
groups.
To
conclude
so
that's
June
24th,
so
for
each
of
the
working
groups,
DNI
evolution
risk
so
on
and
so
forth.
We
ask
that
each
of
the
working
groups
or
working
group
leads
people
who
are
involved
in
those
working
groups.
A
B
A
I
will
yeah
I
think
that
sounds
good.
We
can
talk-
maybe
maybe
not
now
too,
but
maybe
next
week
kind
of
talk
through
again.
What
that
process
always
looks
like
how
you
move
it
out
of
a
Google
Doc,
how
you
get
it
into
github?
What
that,
how
you
open
an
issue
is
related
to
that
PR.
You
don't
I
mean
just
kind
of
all
of
the
github
parts
that
go
along
with
it.
Yeah.
B
C
Osi
I'd,
my
mic
off
and
I
was
I've,
been
on
the
last
few
wrist
meetings,
except
for
the
one
today,
but
I
can
provide
an
update
on
what
we've
been
doing.
Please
and
I'm
from
the
notes.
So
we've
been
working
on
kind
of
a
crop
of
four
metrics,
less
PDX
approved,
licensed
power,
quest
description
age
of
bugs
in
forks
that
we
have
two.
C
C
C
A
A
C
Got
it
yeah,
I,
think
I,
think
our
focus
right
now
and
our
focus
for
the
future
is
to
be
kind
of
a
kind
of
a
conduit
for
that
information
that
make
sense
and
I
think
I
think
well
we're
shifting
to
in
the
next.
While
we
do
this,
our
what
our
shift
is
going
to
be
in
the
next
release,
at
least,
is
to
be
working
towards
more
security
and
vulnerability
related
risk
information,
because
that's
something
that's.
C
A
A
B
B
A
Well,
how
about
this
think
about
it,
and
maybe
I
hadn't
even
thought
about
it
until
it
kind
of
was
until
I
was
saying
it
right
here
at
the
moment,
so
maybe
think
about
that.
If
something's
gone
through
the
continuous
release
process
prior
to
the
8
and
the
semiannual
release,
does
it
go
back
under
review
so
anyway,
and
then
the
other
one
in
active
contributors?
Is
this
currently.
A
A
A
A
A
There
was
one:
was
it
I,
don't
know
anyway,
there
are
a
couple
couple
still
moving
forward.
I
guess
is
what
I'll
say
there.
I
may
actually
just
recommend
at
this
point
that
instead
of
releasing
metrics
under
a
continuous
metrics
really
cycle,
we
just
hold
them
at
this
point
until
June
24th,
so
maybe
as
you're
in
working
groups
and
somebody's
like,
we
should
try
to
get
this
release
next
week.
A
It's
me,
maybe
just
a
hold
off
and
let's
just
wait
till
the
June
24th
release,
okay
and
then,
lastly,
value
so
value,
I
think
values
undergoing
some
some
changes,
and
we
talked
about
this
in
the
calls
just
the
weekly
calls,
but
I
think
the
biggest
issue
in
value
right
now
is
a
restructuring
of
the
focus
areas,
and
there
have
been
some
recommendations
on
what
those
new
focus
area
names
would
be
and
so
I.
My
guess,
is
that,
as
part
of
the
release
from
value,
it's
gonna
largely
be.
B
A
B
A
So
yep,
that's
kind
of
what
I
think
is
gonna
happen
with
value
there
may
not
be
any
new
releases
released.
Metrics
that
come
out
of
value
would
be
my
guess,
but
I
think
it's
undergone
some
kind
of
maintainer
ship
changes
over
the
course
of
the
last
couple
months
and
just
kind
of
getting
things
reoriented.
There
has
taken
a
little
bit
of
effort,
but
I
do
think
even
doing
the
focus
areas
as
a
I.
A
B
A
Do
you
have?
Do
you
ever
have
a
concern
that,
as
we
start
growing
the
number
of
metrics
it
the
comment
period
like
the?
What
needs
to
be
commented
on
is
too
much
so
I
mean
in
theory.
We
could
have
60
metrics
right,
I
mean
with
the
next
release
and
then,
if
we're
looking
at
the
next
release,
say
in
February
around
FOSDEM
this,
but
it's
quite
possible
we'll
have
50
metrics
that
have
been
released
and
then
there's
another
ten
that
are
being
released
with
FOSDEM
right
I
mean
in
theory.
A
You
could
have
60
metrics
that
need
comment.
I
know
that
not
every
metric
would
change
like
that.
That
gets
to
be
pretty
unwieldy,
so
I
do
have
a
little
bit
of
a
concern
about
how
we
effectively
manage
the
comment
period
without
just
saying
your
60
metrics,
you
just
filter
through
what
you
care
about
and
comment,
or
maybe
we
do
that
I
don't
know
so.
A
B
Way
I
see
it
is
that
we
have
done
a
lot
of
the
commenting
already
in
the
working
groups
and
talking
through
it
here
on
the
weekly
calls,
and
the
four
weeks
is
just
time
for
just
the
back
give
everyone
a
chance
to
take
another
look
another
past
sure
it
becomes
a
lot
but
I
think
the
both
of
the
comments,
and
everything
has
already
been
done
at
that
point.
Okay,.
A
So
is
it?
Is
the
public
comment
period
kind
of
like
a
public
service
like
just
to
make
sure
that
we're
doing
this
in
a
very
transparent
way
and
because,
generally
speaking
over
the
course
of
those
four
weeks,
we
get
very
few
comments
on
the
metrics
to
your
point
that
it's
not
that
they
haven't
been
thought
out
because,
quite
the
contrary,
they've
actually
been
talked
I
mean
like.
If
you
look
at
document,
accessibility
and
D&I
I
mean
that
metric
has
been
talked
about
for
three
months.
A
B
E
B
D
A
A
B
Because
system
working
group
is
has
members
from
the
gnome
and
KDE
communities.
So
that's
why
app
ecosystem,
because
they
have
a
lot
of
distance
and
the
focus
that
this
working
group
takes
is
that
a
foundation
with
many
different
projects
that
they
want
to
keep
track
of
and
to
develop
a
metric
suggestion
or
strategy
for
this
high-level
overview
of
many
different
projects
and
the
work
we've
done
so
far
is
to
define
goals
so
I
think
we
have
16
goals.
B
B
Who
is
doing
mentoring
and
be
connected
these
personas
with
the
goals,
and
that
is
the
work
that
we've
done
over
the
last
two
meetings
and
moving
forward.
Our
next
steps
are
going
to
be
to
dive
into
one
of
these
personas
have
a
rationale
for
why
they
care
about
the
goals,
what
they
want
to
measure
or
what
they
need
to
know
about
reaching
that
goal
and
then
what
measurements,
what
metrics
to
use
and
then
complete
the
dqm
cycle.
The
goal
question
metric
process
there.
So
that's
the
work
that
is
going
on
in
them.
B
A
B
A
F
Yeah
yeah
so
that,
like
I've
I,
came
to
Kaos
I.
You
know
I'm
kind
of
like
trying
to
figure
out
a
lot
about
my
life
and
I'm
working
with
the
Cora
community
that
basically
are
trying
to
improve
things
for
people
with.
You
know:
invisible
disabilities
I
think
that's
the
terminology
used
today
and
every
every
time
I
reflect
on
what
Kaos
does
and
what
communities
like
that
can
benefit
from.
So
the
work
you
guys
are
doing
are
definitely
past.
Just
open
source
projects
and
you
know,
grows
into
open
collaboration
and
I
just
wanted
to
point
out.
F
A
I
like
that
comment,
so
thank
you.
That's
a
good
comment,
so
I
I,
agree
and
I.
Think
one
of
the
things
that
I
think
about
quite
a
bit
is
as
the
work
that's
done
in
the
chaos
project,
as
it
can
provide
insight
into
open
source
communities
or,
as
you
point
out,
Sallah
other
open
communities.
How
do
we
kind
of
effectively
contribute
to
that
to
that
connection
right?
A
So
if
an
organization
or
a
group
is
looking
to
rely
on
the
chaos
metrics
as
meaningful
for
them
and
they're,
not
a
software
development
community,
how
do
we
in
the
chaos
project,
help
build
and
foster
that
relationship
so
that
it's
meaningful
for
those
that
want
to
make
that
engagement?
Does
that
make
sense,
yeah
I.
F
F
The
idea
of
it
being
a
custom
element
is
that
you
could
integrate
metrics
in
any
platform,
any
web
platform
and
you're
no
longer
telling
people
you
need
to
learn
how
to
use
react.
You
need
to
learn
how
to
install
react
but
you're
using
angular,
so
you
have
to
put
both
you
want
to
eliminate
how
metrics
can
actually
be
consumed
as
a
component
and
an
application.
F
Yeah
so
I'll
just
work
from
memory.
I
don't
have
anything
open
to
rely
on
them.
Yeah
we
had
a
I
guess
an
update
meeting.
Yesterday
we
synched
with
you
Matt
and
you
know
told
us
of
Matt's
now
so
at
this
point
we
are
still
looking
at
internationalisation,
platforms
or
services,
or
you
know
the
question
between
Crowden
versus
web
laid
or
other
options.
F
We
are
working
on
trying
to
use
wet
late
as
a
self-hosted
because
of
offers
a
self-hosted
open-source
platform,
and
so
so
we
are
exploring
the
you
know,
I
on
one
front,
the
internationalisation,
toolset
or
you
know
you
know,
tooling,
questions
I,
guess
from
the
other
side
and
I
think
Matt
might
have
more
concrete
words
instead
of
me
just
using
approximate
terms
so
Matthew
wanna.
You
want
to
talk
about
what
you
and
Astor
were
discussing
yesterday.
Yeah.
C
But
right
now
the
most
important
thing
we're
working
on
is
redefining
the
questions
that
we
ask
people
when
they
apply
for
a
badge
and
then
the
checklist
for
the
reviewers
to
be
able
to
follow
when
they
review
that
and
what
we,
what
we
had
include
there.
How
could
how
we
can
improve
it?
A
big
part
of
a
barrier
we've
run
into
is
that
a
lot
of
the
projects,
specific
metrics
haven't
been
defined
very
much
so
we're
going
to
also
work
on
improving
those
metrics
themselves.
C
A
A
G
We
were
talking
about
that
and
we
were
showing
the
features
that
give
songs
in
the
previous
talk
in
la
mitad.
So
it's
been
recorded,
so
you
can.
You
can
check
the
video
when
it's
available
and
doesn't
mean
you're.
The
media
featured
on
the
next
people
lab
session.
I
will
showcase
the
new
version
of
something
cut.
It's
not
really
editing,
but
I
can
so
what
we
have
been
working
on
and
the
next
thing
was
I've
been
also
trying
to
figure
out.
How
much
will
it
cost
to
move
to.
G
I
was
taking:
how
can
we
move
the
continuous
integration
system
to
the
one,
but
good
luck
provides.
So,
as
you
know,
we
we
use
Travis
no
in
github
by
DF
its.
If
we
move
to
good
luck,
we
will
need
to
live
there.
Continuous
integration
system,
so
I
told
me,
has
one
project
something
hard
and
I
tried
to
figure
out
how
it
works
and
how
to
configure
it.
So
he
took
me
just
two
hours
to
understand
how
it
works
and
how
to
do
it.
G
G
G
G
A
G
H
On
my
end,
I
mean
it
seems
perfectly
fine.
Ria
has
been
working
with
us
every
Friday
and
Sunday
and
Monday
/
Tuesday.
All
of
her
blogs
are
being
published
via
socially
constructed.
H
I,
don't
know
if
those
blogs
are
also
going
to
be
published
via
chaos,
communities,
log
from
what
I
understand
one
of
venez
just
went,
live
so
I,
don't
know
what
that
is
going
to
look
like
it
all
that,
having
been
said,
we
are
just
now
moving
into
starting
the
coding
process,
we've
more
or
less
handed
the
work
that
Ria's
doing
over
to
development
and
we're
just
giving
her
basic
here's
how
to
make
the
system
better
until
that
completes
so
on
my
end,
I
think
we're
good
great.
Okay.
Thank
you.
I
I
mean
one
day:
the
each
period
went
well,
so
they
re,
and
then
you
started
playing
with
the
block
components
in
the
case
of
Riyadh.
She
was
also
diving
in
in
the
social
currency
Matic
system,
so
we
set
a
basis
for
the
next
period.
That
is
the
need,
and
so
they
already
start.
They
already
started
working
on
some
tasks
last
time
so,
for
instance,
for
with
respect
to
the
quality
models.
So
the
idea
is
to
understand
how
crucial
works.
I
So
Russell
is
the
component
that
generates
is
quality
models
using
the
metrics
in
remote
lab,
so
we
were
sketching
the
UML
model
and
some
class
diagram.
So
in
this
way
we
are
able
to
understand
how
to
drive
the
daily
factoring
and
then,
with
with
respect
to
RIA,
so
we
are
evaluating
out
to
bridge
what
cream
our
lab
produces,
so
they
like
the
rigid
indexes
to
excel.
That
is
a
that
is
basically
what
is
used
by
this
reference.
Image
exists
and
your
assignment
page.
So
at.
B
The
podcast
is
released
episode
two
on
Friday.
We
will
release
episode,
three,
this
Friday
and
then,
and
then
we'll
finally
get
the
podcast
submitted
to
all
of
our
podcasting,
apps
and
iTunes
and
so
on.
So
then,
cows
cast
is
going
to
go
and
grow
and
be
big
and
amazing.
The
we
have
two
episodes
published.
We
have
five
more
that
are
already
recorded
and
at
some
stage
and
from
not
yet
editor
to
already
fully
edited,
and
we
have
one
more
plant.
Last
week
we
had
a
great
interview
with
Ruth
cheese
Lee
from
magic.
B
Next
week
we
have
an
interview
with
Chris
and
a
check
from
CN
CF,
and
there
is
also
experimentation
with
different
format.
That
is
more
like
chaos,
members
talking
amongst
themselves
about
different
issues,
and
we
need
diving
deep,
like
what
we
did
with
defining
open
source.
Community
health,
vineya
and
Matt
Robert
did
one
on
vanity
metrics,
and
so
it
looks
like
we
may
have
two
different
styles
of
episodes.
One
is
the
indigo
style
and
one
is
the
jam
session.
That's
what
I'm
calling
it
right
now.
Maybe
we
have
a
better
name
for
okay,
cool
and.
A
H
If
I
could
put
it
out,
Jarnell
is
working
on
a
somewhat
strict
schedule,
so
he
kind
of
had
to
front-load
things
for
between
the
8th
to
the
14th.
So
if
anyone
who
wants
to
be
a
part
of
that
podcast,
we
have
a
link
to
a
Google.
Doc
I'll
also
put
it
into
the
agenda
for
you
to
set
that
up.
It's
kind
of
a
hurry-up-and-wait
kind
of
thing
so
try
to
get
the
time
that
you're
available
in
so
we
can
get
the
panelists
and
get
it
going
and
then
we'll
go.
A
A
Did
we
you
put
the
oh
you
put
the
oh
I
see
the
community
handbook
link.
There
is
actually
in
relation
to
the
podcast
I
thought.
Maybe
you
were
talking
to
her,
not
the
other
discussion.
So
there
is
another
discussion
going
on
if
you
haven't
seen
it
about
about
moving
the
community
handbook
so
right
now
it's
in
github
and
moving
the
community
handbook
to
get
books.
What's
it
called
good
good,
good.
D
A
E
B
A
Okay,
I
guess
I
mean
taking
a
look
at
it,
I
think
personally,
I'm
not
averse
to
it
at
all
I
think
having
that
kind
of
documentation
in
a
slightly
nicer
looking
place
than
github
like
a
markdown
file,
is
not
a
terrible
thing.
I
think
Daniel
had
brought
up
the
potential
for
cost,
which
I
don't
want
to
get
involved
in
so
I
think
there
are
a
couple
I
had
emailed
earlier
today.
A
couple
I
was
standing
questions
that
I
still
think
need
to
be
that
weren't
answered
on
the
thread.
A
Okay,
I
think
in
the
past
there
hasn't
been
I
think
it's
just
been
like
a
certificate
of
participation,
okay,
I'm,
not
sure
either.
Okay,
good
I,
think
the
last
thing
on
the
agenda
here
is
the
efforts
to
explore
the
move
from
github
to
get
lab.
We
did
have
obviously
an
update
from
Santi
on
that
Shaun's,
not
on
the
call.
So
I
can't
really
speak
to
that
at
the
moment.
A
A
Lady
and
then
I
think
my
last,
my
last
update
is
we're
starting
to
have
weekly
meetings
with
folks
from
the
Linux
Foundation.
Just
on
the
community
reports,
the
one-page
community
reports
and
I
think
one
of
the
biggest
the
biggest
thing
that
we're
looking
at
is
how
we
can
improve
the
workflow
I'm
collecting
the
required
information
to
build
a
community
report
and
then
integrating
both
augur
output
and
grimore
lab
output
into
that
community
report.
A
C
Speaking
of
season
of
ducks,
we
have
had
a
lot
of
interest
already.
I.
Think
that's
a
good
thing
about
the
season
of
ducks
for
the
badging
and
I
had
just
wanted
to
mention.
We
are
trying
to
expedite
the
process
of
getting
the
marker
tasks
out,
because
we've
heard
a
lot
of
questions
about
them.
Okay
and
I
wanted
to
mention
here.
If
anybody
has
any
comments
or
abused
to
have
for
the
badging
microtasks
for
docs
feel
free
to
say
whatever
you
want
about
it,
I'm
gonna
take
it
into
account.
That's
all
I
have
for
that.
C
A
I'm,
it's
a
little
I
will
just
say
this
in,
like
the
last
minute.
The
way
that
the
way
that
we
did
season
of
backs
was
the
Linux
Foundation
submitted
I
mean
you
know
this,
but
the
Linux
Foundation
submitted,
and
we
were
one
of
the
potentially
many
projects
that
are
under
the
Linux
Foundation.
So
I
am
not
entirely
sure
how
say
ten,
ten
mentees
are
assigned
or
ten
slots
or
assigned
to
the
Linux
Foundation
how
those
would
end
up
in
the
chaos
project.
C
A
E
E
E
E
E
A
If
you
get
the
date,
maybe
you
could
add
it
to
the
minutes.
That
would
be
helpful.
Thank
you.
Okay!
Well
we're
at
1150,
in
the
spirit
of
ending
10
minutes
early
like
to
thank
everybody
for
showing
up
and
coming
it's
good
to
see
people,
and
we
will
see
you
on
many
of
the
other
working
groups,
software
software
projects
and
weekly
meetings.
So
take
everybody
because.