►
From YouTube: CHAOSS Weekly Community Call 6-3-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
Okay,
welcome
everyone
to
the
june
1st
community
call
for
chaos,
we're
very,
very
happy
to
see
all
of
you
here.
This
is
technically
the
first
weekly
meeting
of
the
month,
so
we
usually
try
to
do
a
quick
round
up
of
what's
going
on
with
all
the
working
groups.
B
So
that's
on
the
agenda.
If
we
don't
have
much
to
report,
that's
also
cool,
no
big
deal.
We
put
the
I'll
put
the
minutes
in
the
chat
one
more
time,
just
in
case,
if
you
feel
like
adding
your
name.
I
will
also
add
my
name,
because
I
did
not
do
that
yet.
B
And
we
can
go
ahead
and
get
started
with
the
first
item,
so
we
just
want
to
mention
that
we
are
starting
our
office
hours,
we're
calling
them
for
lack
of
a
better
term
next
monday.
They
will
happen
every
monday
from
9
00
am
to
11,
am
us
central,
which
is
chicago
time,
and
you
can
just
join
the
zoom.
B
The
regular
chaos
zoom
chat,
if
you
have
any
questions
or
if
you're
new
to
the
project-
and
you
want
to
just
have
a
place
to
to
ask
those
questions
and
and
not
be
in
a
in
a
group
of
you
know:
12
15,
people
totally
fine,
so
matt
and
sean,
and
I
will
be
hosting
those.
We
also
have
a
sign
up
sheet.
If
you
are
already
a
member
of
the
community-
and
you
would
like
to
take
one
of
those
mondays,
that
would
be
amazing.
B
So
there's
the
link
there
in
the
in
the
minutes.
Thank
you
for
sharing
those
too
by
the
way,
sean.
I'm
always
really
not
good.
At
sharing
my
screen.
So
I
appreciate
when
it's.
B
B
So
yeah
anyway,
if
you
would
like
to
sign
up
there's
a
sheet
there
feel
free
to
just
add
your
name
and
if
you
don't
mind
putting
your
email
address,
that
would
be
great,
and
then
I
can
add
you
I'll
send
an
invite
to
you
for
your
own
calendar
just
to
make
sure
that
you
have
that
on
your
calendar
as
well.
E
B
Yeah,
I
love.
I
love
that
idea.
Actually
I
love
it
just
from
the
beginning,
because
I
think
that
that
would
be
an
interesting
thing
to
keep
track
of.
Is
you
know
even
just
like
how
many
people
come?
You
know
I
mean
we
are
in
the
business
of
metrics.
I
guess
so.
I
would
really
like
to
be.
I
would
be
interested
in
just
kind
of
tracking
that
and
and
what
topics
come
up
and
what
questions
come
up
from
the
very
beginning,
so
somebody
could
add
an
action
item
for
me.
B
I
can
set
that
sheet
up
or
that
doc
up,
maybe
I'll
add
the
the
number
of
people
who
pop
in
to
the
spreadsheet
that
we
have
for
cyanide.
B
B
Awesome
all
right.
The
next
thing
we
wanted
to,
let
you
know,
as
we
made
a
few
changes
to
the
getting
started,
with
contributing
to
open
source,
slash
auger
workshops
that
sean
is
running.
We
added
one
on
june
8th,
which
is
a
week
from
today
on
it's
one
of
the
basic
ones
on
just
getting
set
up
and
configuring
your
computer
getting
ready
to
contribute
from
the
from
the
start.
B
So
we
just
want
to
add
another
one
of
those
in
the
next
one
we
had
was
not
until
the
end
of
july,
so
we
decided
to
add
one
in
for
next
tuesday
morning
and
that
will
run
from
7
30
a.m,
u.s
central
chicago
time
to
9,
30,
u.s
central
chicago
time,
and
I
think
I
put
the
red
yes,
I
did
put
the
registration
there
if
you
would
like
to
sign
up
for
that.
That
would
be
awesome.
Shawn.
Do
you
want
to
add
anything
to
that.
A
No,
I
I
decided
to
do
another
getting
started
with
your
computer
and
programming,
which
really
applies
to
any
of
our
our
software
in
the
chaos
project,
but
more
generally,
to
get
newcomers
off
off
of
start
with
a
lot
of
the
tools
that
we
have.
You
know
how
to
configure
your
environment.
I
think
it's
especially
useful
with
some
google
summer
code,
students
on
boarding
to
our
projects
now.
A
I
have
done
some
that
way
and
I
have
done
others
that
the
recording
wouldn't
be
useful
because
it
ends
up
being
very
individualized.
So
I
think
in
this
case
I
will
prepare
enough
material
so
that
the
beginning
of
the
recording
is
just
sort
of
a
straight
out
lecture
kind
of
thing
and
then
I'll
leave
the
recording
on
for
any
troubleshooting.
That's
individualized.
A
A
Yeah,
no,
it's
a
really
good,
really
good
idea,
but
it
hasn't
always-
and
I
think
elizabeth
and
I
are
sort
of
we've-
been
shaping
these
and
learning
from
the
experience
of
them
so
yeah.
I
think
I
think
this
would
be
a
good
one
to
record.
B
A
I'm
communicating
with
a
couple
people
who'd
signed
up
for
it.
B
Okay,
perfect,
so
if
you
were
planning
on
signing
up
and
you
hadn't
yet
please
do
not
do
that
because
it's
not
gonna
happen
on
that
day.
So
you
will
be
all
alone
by
yourself,
but
we
will
definitely
let
you
know
when
that
gets
rescheduled.
B
B
Yeah,
I
know
the
feeling
okay,
so
the
next
item
on
the
list
is,
we
can
go
ahead
and
just
do
working
working
group
updates.
I
don't
think
we
had
anything
else
and
I
don't
think
the
google
summer
of
code
students
really
have
any
updates.
Yet
we're.
B
Okay,
so
we'll
probably
add
that
if
any
google
google
summer
code
students
are
on
the
call
we'll
probably
add
that
as
a
as
a
recurring
agenda
item
every
week.
Just
so
you
can
touch
base
and
let
us
know
what
you're
working
on
and
how
it's
going.
But
obviously
we'll
skip
this
week
because
there's
it's
still
pretty
early
in
the
process.
So
yeah.
E
E
Past
many
years,
we've
always
asked
our
google
summer
of
code
students
to
blog
about
their
work,
and
I
don't
see
why
there
would
be
any
change
in
that
this
year.
So
I'd
just
like
to
put
that
out
there
that,
if
you're
mentoring,
a
google
summer
of
code
students
or
if
you
are
a
google
summer
of
code
student
on
this
call
right
now,
we've
always
used
blogging
in
the
past,
and
I
think
google,
the
summer
of
code
program,
really
likes
that
as
well.
And
so
it's.
B
That's
it
and
to
add
to
that,
then,
if
you
would
feel
like
adding
that
to
or
sending
it
out
through
the
mailing
list,
that's
always
appreciated
as
well,
because
there's
a
lot
of
people,
obviously
who
are
on
the
mailing
list
and
aren't
able
to
make
the
calls.
So
we
can,
you
can
like
broadcast
it
a
little
bit
that
way
and
also
we
can
share
it
on
twitter.
If
you
tweet
it
and
just
let
us
know
we'll
retweet
it
from
the
chaos
twitter
account
as
well.
B
So
we
want
to
help
you
have
some
visibility
into
your
work
as
well.
It
just
kind
of
helps
everybody
and
we're
super
interested
in
seeing
what
you're
working
on
so.
E
G
A
I
think
I
think
what
you
what
we
look
for.
You
include
our
reflections
on
the
technical
work
that
you're
doing
and
how
it's
connected
to
the
work
of
the
chaos
community.
A
G
E
I'll
go
track
down
I'll
track
down.
I
think
venue
had
done
a
really
nice
job
blogging
I'll
track
his
down
and
just
put
it
in
as
a
total
example.
Yeah,
that's
a
good
idea.
He
did
a
nice.
B
B
Okay,
all
right,
so
I
think
we're
ready
to
go
on
to
the
working
group
updates.
So
first
off
is
the
dei
working
group
and
the
first
one
is.
We
did
have
a
new
metric
for
release.
I
think
we
mentioned
it
here
on
the
call
before
but
documentation.
Discoverability
has
been
released
into
the
continuous
release
process.
B
Continuous
release
process
is
that
right,
so
you
can
go
look
at
it
and
make
some
comments
on
it.
If
you
have
any
and
then
the
next
update
is
that
that
we
kind
of
rearranged
our
focus
areas
and
they
are
listed
there
on
sean's
screen
in
the
agenda
matt,
I
don't.
I
was
not
part
of
those
conversations,
so
I
don't
know
if
you
or
someone
else
who
was
has
anything
to
add
to
that
or
some
reasoning
or
like
context
around
that.
E
I
don't,
I
don't
think
they
have
changed
unless
I
have
missed
something,
but
I
think
the
suggestion
was
for
each
of
the
working
groups
to
just
always
kind
of
reevaluate.
Your
focus
areas,
because
just
because
we
set
them
early,
meaning
like
three
years
ago,
doesn't
mean
that
they
need
to
become
institutionalized
in
the
project.
If,
if
they're,
not
working
or
if
metrics
just
don't
seem
to
be,
you
know
finding
their
way
into
those
focus
areas
so,
and
sean
had
pointed
out
that
evolution
has
done
this
and
risk
and
value.
B
Okay,
I
must
have
misunderstood:
justin
sent
an
email
around
and
I
thought
he
said
new
focus
areas,
but
I
completely
missed
that,
so
my
apologies.
So
anyway,
there
are
the
the
focus
areas
for
the.
B
Existing
ones
just
reinforcing
just
reminding
everyone
that
they're
there
so
we'll
move
on
to
talk
about
the
survey
matt.
You
want
to
talk
about
that.
E
E
And
so
it's
a
survey
about
how
the
members
of
the
chaos
community
feel
that
they're
able
to
make
contributions,
how
they
feel
included
just
kind
of
how
they
feel
about
dei
related
issues
with
respect
to
the
project.
And
so
we
had
worked
up
the
survey.
E
So
I
think
we've
worked
through
that.
So
look
for
something
soon
and
if
you
have
questions,
don't
hesitate
to.
Let
me
know.
B
Does
anyone
have
questions
for
the
dei
working
group
on
what's
going
on
there.
E
B
Okay,
okay,
I
guess
we'll
move
on
then
to
risk,
and
I
am
going
to
let
sean
talk
about
that.
A
Yeah,
just
I'll
run
through
risk,
real,
quick
and
then
evolution
for
risk.
We
have
talks
proposed
that
we
prepared
in
our
last
meeting
last
week
for
oss
eu
seattle
and
osbokon
we're
actively
developing
dependency
metrics
during
meetings
in
the
upcoming
weeks,
targeting
the
next
release
that
we
have,
and
our
next
meeting
is
at
2
p.m
and
I
think
that's
7
p.m.
Utc
on
june
10th.
A
C
I
guess
I
have
one
we
had
drafted
proposals,
but
did
you
end
up
submitting
them
because
I
know
we
were
still?
I.
A
Haven't
submitted
any,
I
haven't,
spent
any
yet
because
I'm
holiday
weekend
and
securing
the
name
speakers
well.
C
A
And
then
for
evolution,
we're
developing
a
new
metric
in
the
last
few
meetings,
based
on
the
concept
of
how
contributor
credit
is
granted
on
a
project.
This
credit
involves
a
contribution
actually
doing
something
requesting
credit.
Sometimes
just
making
the
commit
or
the
pull
request
is
the
request
for
credit,
sometimes
if
you're
tracking
event
participation
or
talks,
then
someone
has
to
go
request,
credit
and
then
someone
peer
reviews.
A
The
credit
drupal
has
a
nice
working
example
of
how
credit
recognition
is
handled
on
their
open
source
project
kind
of
using
that
as
a
model
for
something
in
the
event
for
evolution,
metric
right
now
and
focus
on
the
next
release,
and
the
next
meeting
is
june.
9Th
at
9
am
cdt
2
pm
utc.
If
my
time
zone
conversions
are
accurate,.
B
K
Yes,
so
for
the
value
working
group,
we
have
been
working
on
two
metrics
one
for
the
academic
focus
area,
which
is
on
the
impact
factor
and
which
is
like
more
about
a
academician
developing
the
software
and
what
is
the
impact
of
those
contributions
for
the
academicians
and
for
organizational
value?
We
have
worked
on
the
organizational
influence
metric,
so
these
two
are
in
the
development
phase
and
also
in
the
valley
working
group.
K
K
What
can
value
working
group?
How
value
working
group
can
be
helpful
to
the
open
source
community
like
where
this
talk
is
based
on
the
survey
which
elizabeth
arranged
on
the
twitter
on
that
feedback?
A
small
lightning
talk.
E
B
Okay,
common
who
would
like
to
chat
about
comments.
E
B
No
one
has
questions
for
matt
awesome,
okay,
so
we're
at
the
end
of
the
agenda
24
minutes
in
not
too
shabby
who
else
has
something
to
bring
up
before
we
dismiss
everyone
and
use
the
rest
of
the
time
to
plan
chaos
con
for
those
on
the
planning
committee.
E
E
Venue
you
joined,
can
you
hear
me
hi,
hey,
can
you
do
you,
have
your
link
to
your
old
blog
post
that
you
used.
E
Yeah
yeah,
I
have,
can
you
put
that
in
the
minute,
so
I
thought
it
was
really
nicely
done.
Oh.
H
Okay,
so
I
have
like
made
reports
out
of
it
so
I'll
put
that
report
reports
link.
Where
do
I
have
to
put
it.
E
J
E
A
J
Okay
yeah,
so
you
want
to
look
into
a
project.
The
kind
of
languages
that
are
using.
Are
you
aiming
to
see
the
let's
say
the
prevalence
of
these
languages
over
time,
yeah
how
the
culture
of
computing
itself
is
influencing
them,
or
something
like
that.
E
A
J
Metric
that
we
can
really
run
because,
for
example,
as
you
speaking,
you
see
like
the
culture
of
the
time,
the
complexity
of
computing,
you
might
be
putting
a
language,
for
example,
python,
on
an
advantage
just
because
of
the
libraries
that
it
uses
that
there
are
certain
things
that
have
been
existing
for
a
very
long
time.
Let's
say
in
the
language
like
java,
javascript
or
julia,
but
people
are
not
even
aware
of
it.
So
how
we
give
visibility
of
this
thing
can
be
really
informative
than
just
telling
people
what
they
already
know.
A
A
E
Matt
you
go,
I
was
gonna,
say
I'm
sorry
if
you,
if
you,
if
you
think
the
what
you
were
just
talking
about,
isn't
captured.
Could
you
put
a
note
in
the
okay?
Oh,
that's
right.
Yeah
yeah
just
take
a
look
at
like
even
just
the
description
and
the
objectives.
You
know
I
mean
that'd,
be
helpful
cool.
Thank
you.
H
H
Initially
we
used
to
have
a
command
line
tool.
Now
we
we
are
developing
a
web
app
where
you
can
add,
delete
and
manage
all
these
identities.
Using
you
know,
web
interface
so
and
yeah
and
bestiary
is
pretty
much
used
for
configuring.
All
these
are
moderate
configurations,
so
yeah
the
work
is
going
pretty
slow.
I
mean
it's
not
like
too
rapid,
so
I
just
thought
of
no
information.
E
What
is
is
the
sorting
hat
work?
Is
that
part
of
the
google
summer
of
code.
H
Yeah
yeah
we
have
a
student
who
will
be
working
on
sorting,
hacks
cool.
B
Thank
you
for
that
update
venue.
Does
anyone
have
questions
besides
matt,
who
already
asked
us
any
other
questions,
revenue.