►
From YouTube: CHAOSS Weekly Community Meeting 6/7/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
B
A
The
minutes
here
and
I
believe
it's
matt
that
asked
the
question
of.
If
you
could
go
to
space,
would
you
do
it
given
the
chance?
So
you
feel
like
answering
that
feel
free
to
do
that.
I
absolutely
would
not
do
it
because
I
like
earth
and
I
don't
want
to
float
away,
but
other
people
are
more
adventurous
than
me.
So
you.
A
A
A
A
A
D
A
That
is
my
personal
hell.
It's
a
space
tornado!
Oh
my
gosh.
I
can't
I
can't
yeah
anyway.
Now
I
have
that
in
my
head.
Okay,
so
let's
jump
into
our
agenda
now
that
I'm
gonna
be
traumatized
forever.
The
first
one
we
are
going
to
have
matt
g
give
us
a
quick
update
on
the
dei
working
group
and
I
moved
your
project.
Badging
yeah.
C
No
problem
so
we're
like
all
working
groups,
we're
continuing
to
reflect
on
the
metrics
that
have
been
released.
Maybe
I
should
put
this
in
the
minutes,
but
one
thing
is
for
the
working
groups
and
we
can
talk
about
this
in
each
of
the
working
groups.
C
If
you
have
a
metric
that
you
are
just
kind
of
changing
like
doing
some
minor
changes
to
it,
and
then
you
have
another
metric
that
you're
doing
minor
changes
to,
and
you
have
a
third
metric
that
you're
doing
minor
changes
to
if
you
could
just
open
up
a
single
issue
in
the
translations.
Repo
that
says
here
are
the
three
updated
metrics
that
have
minor
changes
to
them.
C
C
Then,
when
you
update
the
or
when
you
post
an
issue
in
the
translations
repo,
could
you
just
do
one
issue
per
major
update
metric,
so
minor
changes,
kind
of
pull
them
together
and
for
major
changes?
Just
one
issue
in
the
translations,
repo
we're
starting
to,
I
think,
gain
some
momentum
on
project
badging.
C
As
a
lot
of
you
know,
one
of
our
challenges
around
project
badging
is
the
volume
of
projects
and
our
desire
to
still
have
an
open
and
transparent
process
by
which
badging
can
occur
so
kind
of
this
large
number
of
projects
with
a
limited
number
of
reviewers.
Those
numbers
don't
go
together
real
well,
so
we've
been
trying
to
think
about
ways
to.
C
C
What
metrics
would
be
in
that
dei
dot
md
file,
but
I
thought
I'd
bring
that
forward
we're
working
with
event
badging
to
update
how
we
request
or
how
a
project
would
request
a
badge
right
now
event,
badging
uses
a
web
form
and
that
web
form
opens
an
issue.
It
looks
like
we're
going
to
be
moving
over
to
just
using
github
to
open
the
issue
and
then
also
how
we
thinking
about
how
we
can
use
the
bots
that
are
developed
in
event
badging
to
kind
of
help
with
the
workflow
over
on
project
badging
as
well.
C
Our
goal
here
is
to
to
not
have
two
different
processes,
one
for
event,
badging
and
one
for
not
how
about
this
not
have
two
fundamentally
different
processes,
one
for
event,
badging
and
one
for
project
batching.
It
would
be
great
if
they
could
overlap
at
least
80
percent
or
85,
or
something
like
that,
so
the
work
could
be
shared
between
the
two
between
the
two
programs.
C
Let's
see
so
with
respect
to
still
with
badging,
you
can
take
a
look
at
that
link
things
I
use
for
putting
that
together.
Let's
see.
C
Is
this
what
you're
talking
about
sophia?
Oh,
oh
you're,
talking
about
the
dei.md
file,
yes,
yeah
yeah!
We
do
when
I
stop
talking
I'll
track
that
down
and
put
it
into
the
chat
in
the
minutes
as
well,
and
so
this
is
ayush's
put
this
together.
So
thanks
ayush!
C
This
is
by
no
means
the
kind
of
what
the
final
submission
would
look
like.
This
is
just
to
kind
of
show
you
that
we
can
do
this
via
github
and
so
we'll
change
this
around
a
little
bit
as
we
kind
of
kind
of
hone
in
on
on
what
the
actual
questions
are
for
the
application.
C
F
Yeah
sorry
I
just
joined
in,
I
want
to
ask
if
this
application
process
would
just
be
for
project
pattern
and
will
you
replicate
with
event
event
button?
That's
the
github
issue
form.
C
C
Yep
and
like
I
was
saying
ruth,
I
don't
know
if
you
had
heard
me,
the
hope
is:
is
that,
like
85
of
the
work
around
badging
in
general
can
be
shared
between
event,
badging
and
project
badging?
There
will
be
some
slight
variations
between
the
two,
but
the
hope
is
is
that
we
can
share
things
like
how
to
create
issues
and
how
to
do
bot
activity
kind
of
the
whole
workflow.
Hopefully
we
can
share
a
lot
of
that
yeah.
C
Right
on
okay,
so
then
elizabeth,
maybe
you
could
just
talk
about
the
appreciation
event.
I
know
that's
I'm
talking.
B
A
So,
just
as
a
reminder
to
everybody,
you're
all
invited
to
this,
it's
just
a
one
hour,
fun
appreciation
event
to
just
show
appreciation
for
our
reviewers,
because
they
are
volunteers
and
it
does
take
some
of
their
time
to
do
it
and
that's
the
whole
they're,
like
the
the
reason
that
the
badging
initiative
is
so
successful
is
all
of
our
awesome
reviewers.
So
we
just
wanted
to
give
a
quick
appreciation
of
it
for
them.
You're
all
welcome
to
attend.
You
don't
have
to
be
a
reviewer
or
be
involved
in
the
event.
A
Badging
initiative
at
in
any
way
shape
or
form
feel
free
to
just
sign
up
right
here.
The
link
is
in
the
minutes
there
and
again
it's
just
an
hour-long
fun
present,
meet-up
thing
that
we're
doing
so.
I
don't
really
know
what
else
to
say
about
it,
but
yeah,
and
we
did
just
include
four
new
badge
event
badgers,
so
hooray,
hooray
and
if
you
are
ever
interested
in
can't
hear
you
you're
you're,
fading
in
and
out.
A
Go
okay,
if
you
are
interested
in
becoming
an
event
reviewer,
you
can
sign
up
with
this
form
here
and
we
will
get
you
trained
and
get
you
all
the
information
you
need
to
be
a
badger.
So
that's
what
we
call
our
reviewers
our
badgers,
because
they're
awesome
any.
If
anybody
has
any
questions.
Just
let
me
know
about
that.
C
Great
thanks
for
that
and
then
ruth
I'm
gonna
kinda.
If
you
wanna
talk
about
the
burnout
and
mental
health
session
on
june
17th,
maybe
you
could
click
that
elizabeth.
F
Yeah
sure
so
hi
everyone
would
be
having
to
er
a
bun
out
session
so
for
more
context.
F
Github
is
hosting
maintenance
month
of
june
and
we
signed
up
to,
firstly,
the
session
on
burnout
and
mental
health
in
open
source,
so
kind
of
like
talk
with
maintain
us
on
how
we
manage
burnout
and
mental
health
and
also
kind
of
be
like
talking
about
the
metric
that
we
have
on
burnout
as
well
and
hearing
from
other
maintainers.
F
So
this
will
happen
on
17th
of
june
there's.
This
is
the
agenda.
We
would
go
through.
We
kind
of
put
up
like
a
slide,
and
this
like
kind
of,
contains
the
bonometric,
the
different
things
we
talked
about
with
bonometric.
F
So
this
would
be
like
a
introductions
and
then
you
know
it's
an
interactive
session,
so
we
once
maintainers
that
attend
the
sessions.
Kind
of
like
give
an
experience,
share
and
burn
out.
You
know
personal
experience
and
we'll
talk
about
the
bonometric
and
then
we'll
let
for
questions.
F
So
please
you
can
attend
this.
We
have
a
keeping
there's.
There
should
be
a
link,
the
google
form
yeah
to
register.
You
can
register,
and
you
can
also
invite
maintainers
that
you
know
you
can
send
the
form
to
them
and
before
june
17,
to
send
in
link
we're
going
to
use
zoom
for
this.
C
Yeah
way
to
go
all
right
he's
awesome.
Thank
you
for
that
ruth
much
appreciated
10
days,
10
days
from
now,
so
that
is
the
dei
working
group
update.
A
G
F
F
F
Yeah
sure-
and
I
think
github
is
also
going
to
be
postponed.
A
Okay,
let's
see
okay.
So
next
thing
is
the
philosophical
question
about
metrics.
A
I
don't
know
if
we
want
to
like
maybe
put
some
constraints
around
this
conversation
because
I
feel
like
it
could
it
could
take
the
whole
thing.
Let's
say:
maybe
like
five
minutes,
I
don't
know
10
minutes.
What
do
you
guys
think?
I
know
we
did
want
to
try
to
meet
with
chaos
khan,
but
also
we
have
a
lot
of
other
things
exciting
to
talk
about.
So
let's
do
chaos.
Con
async
is
that
cool.
D
If
you
look
at
some
of
the
non-trace
data
metrics,
we
have,
for
example,
in
dei,
there's
a
lot
of
clear
specification
of
the
questions
that
would
be
asked
in
a
survey,
for
example,
and
I
think
we're
just
trying
to
get
a
sense
of
what
is
the
right
level
of
insight.
On
the
one
hand,
we
think
many
people
are
coming
to
the
chaos
project
now
looking
for
things,
they
can
implement
right
away,
so
some
direction
in
that
space
is
probably
going
to
meet
the
needs
of
newcomers.
D
On
the
other
hand,
we
don't
want
to
get
too
bogged
down
in
defining
technical
definitions
in
the
metrics
themselves,
and
I
don't
we
don't
have
an
answer,
but
that's
just
kind
of
the
question
we're
wrestling
with
and
we
welcome
any
thoughts
insight
either
here
or
perhaps
asynchronously
in
the
wg-evolution
channel.
On
slack.
D
Implementation,
yeah
yeah,
it's
exactly
the
section
that
that
would
typically
fall
into
and
where
we
see
we
see
just
variation,
not
just
within
our
working
group
but
across
the
community,
and
I
don't
know
that
we
can
get
an
answer
today.
But
it
would
be
good
to
get
some
general
consensus
about
how
to
think
about
that,
and
maybe
it's
something
others
can
take
back
to
their
working
groups
and
put
in
their
head
while
they
go
through
the
metrics.
If
you
process
this
cycle.
C
C
Okay,
generally
speaking,
we've
kind
of
backed
off
that
level
of
specificity,
and
it
does
feel
like,
as
you
mentioned,
like
interview
questions,
they
don't
cover
everything,
but
they
help
orient
a
person.
D
C
D
B
D
I
mean
I
think
we
could
get
rid
of
them
because
it's
well,
it
won't
work
yeah.
It
may
or
may
not
work.
H
But
what
are
those
queries
querying
like?
What
platform
are
they
using.
H
So
it's
an
auger
specific
information.
D
And
and
there's
a
good
chance,
they
still
work,
but
they
should
be
at
least
verified.
B
B
G
Feel
like
there's
always
a
balance
like
I
know.
Sometimes,
if
you
look
at
some
of
the
metrics
descriptions,
if
they're
pretty
general,
if
you
see
an
example
implementation,
even
if
it's
a
query
that
I
can't
run
just
by
looking
at
how
the
query
is
structured,
it
helps
me
understand
what
you're
actually
counting
and
how
you're
counting
it.
G
So
I
think
I
don't
know
I
feel,
like
that's,
not
a
great
answer,
but
I
generally
like
some
detail
around
implementation,
because
if
there's
any
overly
general
language
that
we've
used
in
this
description
to
make
it
as
platform
extensible
as
possible
when
it
comes
down
to
actually
implementing
it,
it
might
be
too
generic.
So
having
implementation,
guidance
or
examples
can
help
to
clarify
how
we've
interpreted
in
this
context.
G
A
I
feel
like
this
would
be
a
really
good
use
of
our
forums
that
the
metric
itself
is
pretty
pretty
bare
bones
or
pretty
you
know
straightforward
and
simple.
I
guess,
but
in
the
forums
is
where
maybe
we
could
have
more
conversations
about
implementation
and
specifics
and
discussion
about
things
around
that
metric.
A
If
there's
a
better
way
to
do
stuff,
if
it
we
have
to
add
now,
because
some
of
them
just
had
grammar
lab,
they
didn't
even
mention
auger
so
like
should
we
have
both,
and
I
don't
know
it
just
felt
like
it's
really
valuable
information,
but
it's
also
something
we
have
to
maintain
in
the
future,
whereas
a
forum,
it's
more
of
like
interactive,
it's
more
fluid
people
maybe
understand
that
this
has
been.
You
know
an
old
post,
so
maybe
these
don't
work
anymore.
H
I
would
like
to
point
out
that,
while
in
the
well
in
the
metrics,
we
have
been
moving
away
from
these,
these
specific
implementations
in
the
models
working
group
we're
going
in
the
opposite
direction
and
we
are
providing
very,
very
explicit,
implementations
or,
or
example,
implementations.
So
the
and
those
are
called
implementations
as
well.
H
So
what
what's
the
difference
between
an
implementation
in
a
metric
versus
a
model
and
and
then
with
the
with
the
model
implementations?
We
do
run
into
a
lot
of
the
issues
that
I
I
believe
that
we
will
run
into
a
lot
of
the
issues
that
elizabeth
just
mentioned.
So
if
we
have
to
maintain
those.
C
I
did
like
sophie-
I
don't
even
know
if
you
know
you
said
it,
but
you
called
it
general
implementation
guidance,
like
I
kind
of
like
that,
it's
a
it
doesn't
have
to
be
that,
but
something
like
that
is
the
heading,
because
implementation
applies.
This
is
the
implement.
This
is
the
implementation
of
the
metric
and
general
implementation.
C
Guidance
is
more
like
what
you
were
talking
about,
like
just
help
me
locate
myself
as
to
how
this
metric
might
live
in
the
world
and
and
how
I,
as
a
person,
might
approach
this
metric
and
like
a
sql
statement,
is
just
kind
of
that.
It's.
C
Guidance
towards
that
metric
and
same
with,
like
the
interview,
questions
they're
just
kind
of
that
as
well
they're,
just
kind
of
guidance
to
help
orient
people
as
to
how
to
think
about
the
metric.
So
maybe
I
like
that.
H
Done
boom,
I
think
I
think
that
adds
some
distinction
between
the
model,
implementations
and
the
metrics
implementations
as
well.
So
that's
good.
H
We
we
may
want
to.
We
may
want
to
change
some
of
the
language
along
with
that
heading.
Just
change,
some
of
the
language
in
that
that
section
to
to
show
that
those
those
implementations
are
example,
implementations
or
so
so
that
might
be
one
way
you
look
at
rather
than
getting
rid
of
the
sql
queries,
just
change
some
of
the
language.
A
C
And
ruth
here
too
so,
starting
in
mid-june,
we're
going
to
be
launching
chaos,
africa
so
to
support
our
efforts
there.
I'm
just
really
really
excited
about
this-
is
that
the
planning
document
that
somebody
just
put
in
there.
F
Yeah
sure
first
is
exciting.
Like
nicole
said
yeah,
it
is
exciting,
so
I
kind
of
start
this
up
and
I'm
happy
to
be
leading
alongside
with
it.
So
the
plans
we
have
here
for
chaos,
africa,
they're
kind
of
like
too
I'll
you
know,
run
them
off
into
one-
is
to
look
for
ways
to
solve
challenges.
F
Community
challenges
here
from
africa
right
using
the
chaos
model,
and
that
creates
new
initiatives
that
solve
challenges
here
related
to
africans
right
african
contributors
and
also
would
also
contribute
to
larger
chaos,
project
software,
documentation,
design
and
other
initiatives
within
chaos,
but
also,
like,
I
said,
allow
the
first
point
to
also
find
ways
to
solve
challenges
facing
african
open
source
communities
right.
So
there
are
a
whole
lot
of
things
I
haven't
planned
and
I
can't
wait
to
meet
everyone
I'll
be
involved
in
this
community
and
plan
together.
F
So
would
start
off
next
week
would
have
weekly
sings
and
would
keep
interacting
with
existing
contributors
africans
within
chaos
and
see
how
to
spread
the
word
and
also
get
like
other
contributors
to
come.
Join
chaos,
africa.
So
this
is
a
strategy
doc.
Still,
if
you
have
any
thoughts,
you
see
justin
put
in
equal
a
lot
of
useful
comments
and
all
that
stuff.
So
if
you
have
any
thoughts
with
this
on
this,
you
can
add
any
comment
or
a
suggestion
and
definitely
would
be
helpful.
C
C
Any
questions
for
ruth
or
the
other
thing
is
like
ruth,
has
kindly
agreed
to
either
through
twitter
spaces
or
some
sort
of
live,
live
kind
of
real-time
approach
to
also
talk
about
the
the
challenges
and
the
successes
and
kind
of
what
what
is
learned
in
this
process
to
not
only
help
improve
cast
africa
but
to
help
other
communities
who
are
looking
to
do
something
similar
and
so
kind
of
learning.
Learning
both
ways
and
just
really
excited
about
this.
I
Yeah,
I
just
want
to
add
this-
will
really
be
a
good
opportunity
for
kiosks
to
extend
and
broaden
its
horizon
across
a
growing
start-up
community,
because
if
you
look
at
the
africa
has
one
of
the
world's
fastest
growing
startup
communities
for
developers
and
software
in
general.
I
They
have,
they
are
taking
a
new
dimension
on
some
kind
of
things,
but
this
african,
I
think
it's
a
very
good
idea
and
it's
something
that
we
should
really
put
our
efforts
to
to
help
it
grow
yeah,
because
it's
an
expansion
and
we
get
more
challenging
tasks
there
to
solve
and
to
collaborate.
It's
something
really
good.
So
thank
you.
Rode
for
this
initiative
too.
A
A
F
A
C
C
C
We
could
do
that
week
and
the
week
before
or
that
week
and
the
week
after
of
just
no
zoom
meetings.
That's
all.
A
A
Do
we
want
so
what
what
we
see?
We
want
to
decide.
D
I
think
trying
to
align
it
with
the
european
vacation
schedule
so
like
something
like
mid-july
to
mid-august
might
just
kind
of
nicely
slide
into
the
european
vacation
schedule.
B
D
D
A
Okay,
so
this
this
week
june
20,
is
that
june
20th
through
the
20th.
Well,
we
don't
have
any
on
mondays
really,
but.
B
A
C
J
H
D
C
C
C
H
C
C
D
C
C
C
D
C
C
A
All
right,
okay,
oh
before
we
forget
this-
is
an
important
thing
that
katie
just
dropped
in
here.
B
A
K
A
A
K
K
So
the
link
is
changed.
It's
still
on
big
blue
button.
It
is
just
a
different
couple
of
letters
at
the
end
now
so
I've
updated
it
on
the
event.
I
put
an
update
in
the
event
like
it
said.
Do
you
want
to
add
an
update,
so
I
added
an
update.
I
think
it
emailed
everybody
who's
already
rsvp'd.
Any
new
rsvps
will
have
the
new
link,
so
I'm
hoping
that
catches,
everyone
and
people
should
be
informed
I'll.
Let
everybody
know
it
meetings
before
next
event
as
well.
K
Do
we
need
to
re-register?
I
don't
think
so
it
I
updated
the
event
and
I
sent
out
an
email
or
I
sent
put
an
update
and
said
it
was
going
to
notify
all
current
registration
people.
Okay,
so
you
should
at
least
I
sent
the
new
put.
The
new
link
in
the
event
update,
and
it
should
at
least
say
my
message
to
everybody-
was
like
we
look
forward
to
seeing
you,
but
the
link
is
changed.
Here's
the
new
link,
please,
please
make
sure
your
event
on
your
calendar
is
updated.
A
Okay,
so
this
we
were,
it
was
just
on
here,
because
we've
talked
about
that,
so
we
just
put
it
in
the
minutes
just
for
reference.
The
only
two
things
left
then
are
mentorship
and
the
next
working
group
update
bernard.
Are
you
okay
to
do
a
value
update
next
week.
C
B
C
H
Well,
aren't:
aren't
we
still
in
the
bonding
period
for
google
summer
of
code,
or
is
that
ended?
We
have.
C
C
But
like
outreachy,
the
first
review
was
yesterday.
Am
I
correct.
D
A
G
A
So
just
everybody
check
slack
if
you're
in
the
chaos
con
committee
all
right
well
anything
else
before
we
go
any
final
questions
comments,
concerns
issues
whatever.