►
From YouTube: CHAOSS DEI Working Group 6/8/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
B
Perfect,
okay,
so
welcome
everybody.
I
am
super
happy
that
today
I
will
facilitate
the
meeting
so
before
going
on
with
the
agenda,
I
would
like
to
first
ask
would
like
to
be
the
facilitator
for
next
week.
B
Perfect
so,
and
also
in
case
that
you
still
haven't
added
your
name
at
the
attendees,
please
feel
free
to
do
it
and
also
feel
free
to
add
your
favorite
ice
cream
flavor
since
it's
summer
and
it's
super
hot.
B
That's
such
a
bella.
It's
a
very
italian-ish
like
a
flavor.
I
think
that
it
has
to
do
like
it
has
a
lot
of
milk
and
vanilla.
It's
I'm
not.
B
B
Great,
so
the
first
item
in
the
agenda
today
is
the
badging
updates.
Would
you
like
elizabeth
to
give
us
some
informations
how
it's
going
and
how
was
the
training
session.
D
Sure
yeah,
we
had
a
training
session
and
we
added
four
new
reviewers
to
our
team,
which
is
amazing,
very
very
happy
about
that.
Usually,
if
history
repeats
itself,
we
will
get
a
very
large
influx
of
applications
all
at
once
around
august
or
maybe
early
september.
So
hopefully,
by
that
time,
all
of
those
new
reviewers
will
feel
acclimated
and
we
can
jump
in
then
when
that
when
that
wave
comes
and
if
the
wave
doesn't
come,
we're
still
ready
anyway.
So
it's
totally
fine.
D
We
just
had
our
dei
badging
meeting
a
little
bit
before
this
one,
so
yeah
things
are
moving
right
along
we're,
gonna
be
switching
over
to
so
project
badging
I'll.
Let
matt
talk
about
that
a
little
bit
but
they're
using
a
form,
we're
gonna,
be
using
a
form
that
is
way
easier
for
our
applicants
to
fill
out.
It's
just
going
to
be
an
issue
template
because
github
has
that
functionality
of
having
a
template.
D
That
is
actually
a
form,
and
so
we're
going
to
be
using
that
because,
right
now
the
process
is
a
little
bit
unwieldy
for
applicants.
They
have
to
do
some
copying
and
pasting,
and
it's
kind
of
convoluted
and
it's
very
difficult
to
update
that
form
for
on
our
side
as
well.
So
that's
going
to
be
happening
soon.
We're
also
going
to
be
adding
in
some
of
the
changes
based
on
the
recent
metrics
that
were
released,
especially
around
event.
Accessibility.
D
So
we'll
be
asking
a
bunch
of
questions
around
that
and
what
else
I
think,
that's
roughly
it.
Oh
and,
of
course
the
badge
reviewer
appreciation
event
is
happening
on
june
16th,
I
think
katie
said
we
had
22
people
signed
up
for
that.
So
if
there
are
any
reviewers
on
this
call
that
are
not
signed
up
for
that
and
want
to
be,
we
would
love
to
have
you
there
for
sure.
So
we
can
recognize
you
and
show
our
appreciation
to
you.
D
So
there's
the
link
there
to
register
and
also
to
get
more
information
about
it.
So
yeah,
I
think
that's
roughly
it
did.
I
miss
anything
anybody
with
that
was
on
that
meeting
earlier.
I
think
that's
it
in
a
nutshell.
C
Oh,
that's
good
with
respect
to
project
badging,
we're
really
kind
of
getting
that
going
now,
based
on
conversations
we've
had
here.
So
I
really
honestly
at
this
point.
It's
about
finalizing
that
issue
template
that
elizabeth
had
talked
about
for
projects.
E
C
C
I
mean
we
have
to
have
there's
a
there's,
the
dei.md
file
it
would
be
for
a
project
and
that
just
needs
to
reside
somewhere
in
the
organizational
structure
right
and
then
there
should
be
a
code
of
conduct
that
would
probably
be
at
the
organization
that
just
needs
to
reside
somewhere.
I
can't
imagine:
they'd
have
different
codes
of
conduct
across
repositories.
C
Would
we
have
like
use
the
dot
github
folder
inside
of
an
org.
C
Yeah,
I
don't
particularly
care
where
it
resides.
I
don't
think
as
long
as
it's
available
to
the
community
members
so
like
we
use
a
community
folder,
which
would
be
a
pretty
logical
place
to
put
something
like
the
dei.md
file
to
me,
but
I
don't
know
that
every
project
would
necessarily
have
that.
Folder.
E
G
D
H
H
D
E
So
maybe
we
we
have
them
either
indicate
when
they're,
applying
that,
if
they're
trying
to
badge
a
github
organization
or
they're,
trying
to
badge
a
single
repo
and
based
on
that,
we
give
them
a
badge
that
indicates
that
the
org
is
badged
or
it
just
indicates
that
the
repo
is
batch
depending
what
they
did.
E
Yeah
I
mean
like
chaos
project
it's
one
project
right
with
many
repos
in
it,
and
so
we
would
want
to
badge
the
chaos
project.
We
wouldn't
want
to
badge
each
repo
within
it.
So
what
is
the
place
where
we
would
ask
people
to
do
the
badging
at
that
level
and
the
dot
github
directory
is
the
only
thing
that
I'm
that
github
repo
is
the
only
thing
I'm
aware
of
that
is
a
org
level
repository.
G
E
C
A
few
things
going
on
here,
then
one
is
it's
the
end
of
the
badging
process.
So
that's
one.
So
we
issue
the
badge
right.
Let
me
start
at
the
beginning.
I
guess
so.
The
first
is
an
a
project
is
asking
to
be
badged
right,
and
so
we
are
asking
for
I'll
go
down
to
the
list
here,
sandwich
all
the
things
sam
sandwich,
approximately
these
things
right,
yeah,
okay,
so
and
then
like.
Where
are
you
suggesting?
I
E
I
E
E
F
F
So
I
think
just
saying
that
we
are
badging
hyper
ledger
at
the
organization
level.
I
don't.
I
don't
think
that
would
be
appropriate.
I
do
think
it's
something
more
akin
to
what
sean
was
saying
where
we
asked
them
to
identify
the
main
repo
that
were
that
we
would
be
badging
or
that
that
main
piece
of
software
within
the
hyperledger
project
that
we're
badging.
E
E
E
I'm
fine
with
that.
I
just
I
just
I'm.
My
primary
concern
was
like
somebody
submitting
30
repos
from
a
single
github
org.
Maybe
that
won't
even
won't
ever
happen.
C
But
are
you
suggesting
when
they
submit
30,
we
don't
ask
for
repos,
so
we
ask
for
these
documents
right
which
exists
in
a
repo?
Don't
do
they
not
right?
So
are
you
suggesting
that
it's
possible
that
they
would
say
our
code
of
conduct
is
located
in
this
repo,
this
repo,
this
repo,
this
repo
yeah,
this
repo
and
our
contributing
guidelines,
are
located
in
this
repo,
this
repo,
this
repo,
like
yeah,
I
mean.
E
I
They
would
need
to
have
30
different
dei
dot,
md
documents,
then
in
30
different
ways.
They
say
how
they're
going
to
take
care
of
burnout
and
30
ways
they're
going
to
do
this
because
we're
not
going
to
badge
the
same
document
like
they
have
to
be
individual
documents.
So
that's
going
to
be
a
lot
of
extra
work
for
them
and
if
they.
E
That's
what
I'm
saying
I
may
be
borrowing
trouble
here,
so
I
wanted
folks
to
think
about
it,
but
it
sounds
like
we've
thought
about
it
enough
and
we
can
just
press
forward
shooting
a
project
like
you
know,
you're
going
to
fill
in
the
blanks
and
designate
a
repo
and
that's
where
we're
going
to
badge
it
and
we'll
worry
about
what
actually
happens
when
people
start
submitting
things.
I
think
is
probably
a
better
approach
at
this
point.
Instead
of
using
carrying.
F
G
F
They
they
function
differently.
The
the
the
way
contributions
are
made
is
different.
The
the
organizational
structure
is
different.
F
And
I,
and
I
do
think
we
would
see
that
in
in
other
organizations
as
well,
so
is
the
assumption
that
all
of
the
projects
within
an
organization
are
organized
and
managed
in
the
same
way.
F
If
so,
then
I
suppose
badging
badging
at
the
organizational
level
would
make
sense,
but
if
there's
any
deviation
in
the
way
those
projects
are
governed,
then
then
I
think
it
does
kind
of
become
an
issue
of.
F
E
E
Well,
yeah,
so
it
is.
I
agree,
it's
project
badging
and
I
think
we
should
direct
people,
then
maybe
the
maybe
the
fix
is
simply
to
have
in
the
template
that
which
repository
holds
your
community
assets.
E
F
Maybe
remove
community
from
that
language
and
refer
to
it
as
project
with
the
to
focus
in
on
project
assets
rather
than
organization
or
community
assets.
J
I
was
just
going
to
add
that
there
might
be
an
organization
within
these
various
projects
like
in
the
drupal
community.
There
is
like
a
dei
group
with
their
own
repo,
so
it
might
be.
This
might
sort
itself
out
in
terms
of
the
groups
that
are
working
on
this
within
that
community
or
that
project
where
where
they
would
know
how
to
let's
narrow
this
down
to
where
where
it
could
happen,
could
you
say
that
again
I
didn't.
J
C
Okay,
so
what,
if,
based
on
this
conversation
as
part
of
the
application,
do
you
know
how
like
for
events
one
of
the
questions
on
the
application
we
ask
is
like?
Are
you
an
open
source
project
and
they
just
have
to
click
yes
or
no,
like
it's
just
a
yes,
no
question:
what,
if
we
ask
something
like
the
submitted?
That's
this
the
the
submitted
documents,
the
readme,
the
contributing
they're
applicable
to
all
corners
of
the
project.
C
You
see
what
I'm
saying
that,
like
the
code
of
conduct
that
you're
submitting
is
applicable
across
the
entire
project,
the
dei.md
file
that
you're
submitting
is
applicable
across
the
entire
project,
the
license
that
you're
submitting
or
the
licenses
that
you're
submitting
are
applicable
across
the
entire
project.
You
know
what
I
mean:
it's
just
a
yes,
it's
just
a
yes,
no
question.
E
C
J
Yeah,
that's
a
really
tricky
thing,
because
we
have
like
a
specific
code
of
conduct
that
can
that
covers
the
drupal
like
community
events,
but
it's
a
different
sort
of
code
of
conduct
that
that's
like
within
the
working
with
one
another,
but
there's
like
in
in
an
issue
queue.
But
then
there's
like
a
different
sort
of
like
set
of
guidelines
that
would
be
applicable
to
this
as
well.
That
would
be
like
outside
of
that
too,
like.
J
Well,
see
like
each
like,
say:
there's
a
drupal
camp.
You
know
local
versions,
we
have
our
own
local
codes
of
conduct
and
we,
you
can't
force
everyone
that
creates
their
or
a
lot
of
communities
like
wouldn't
force
their
local
organizations
to
follow
by
necessarily
some
broader
top-down
sort
of
code
of
conduct.
J
J
J
C
Okay,
well
to
sean's
plan
we
might
just
have
to.
We
might
press
on
and
see
how
it
plays
yeah
yeah.
That's
might
be
the
best
way
to
go.
Yeah.
F
I
I
don't
think
you
should
feel
bad
about
bringing
this
up,
though,
because
if
we,
if
we
don't,
have
an
answer
to
this
question,
I
don't
know
that
we
can
really
say
that
we
know
what
we're
badging
right.
We
we
have
to
understand
that
the
bounds
of
the
the
organization
or
the
project
so
and
maybe
we'll
figure
it
out
as
we
go,
but
I
I
do
think
it's
something
we
need
to
continue
to
think
about.
D
I
think
like
we,
we
kind
of
did
answer
if
we
ask
them
exactly
what
they're,
what
they're
intending
us
to
badge,
which
is
like
this
piece
of
your
community
or
these
repos
or
whatever,
however,
that
pans
out.
If
they
tell
us
what
they
want
a
badge,
then
we
can
compare
and
give
them
a
badge.
For
that
part,
maybe.
K
I
B
Great,
so
I
think
that
we
can
go
to
the
next
topic.
I
educated
the
burnout
and
the
mental
health
session.
Actually
it
was
just
as
a
reminder,
because
we
also
discussed
that
in
our
previous
meeting.
B
G
J
Sorry
to
interrupt,
I
just
I
was
gonna
say
I
I
put
together
that
agenda
and
I
kind
of
pieced
it
together
from
the
notes
and
what
not
I
was
mostly
responding
to
the
email.
That
said,
do
you
want
help,
and-
and
I
was
directed
here
so
I
just
I-
I
don't
know
I
I
don't.
This
doesn't
even
all
make
sense
to
me,
but
I
put
that
together.
J
So
if
anyone
else
has
insight
into
this
feedback
or
changes
are,
are
welcome
because
I
just
took
an
outline
turned
it
into
some
slides
and
there
you
go
so
I
just
wanted
to
throw
that
out.
C
C
C
C
L
H
H
Yeah
sure
so
we
are
starting
up
chaos,
africa
and
it's
really
exciting
and
I'm
so
pumped
about
it.
So
I'm
going
to
be
leading
efforts
on
you
know,
starting
up
chaos,
africa,
and
mainly
we
are
going
to
be
focusing
on
you
know,
creating
initiatives
that
all
metrics
that
kind
of
like
focuses
on
open
source
community
challenges
here
in
africa,
right
we'll
be
learning,
and
you
know
creating
initiatives
and
metrics
around
that
and
would
also
be
contributing
to
the
chaos
project
at
large.
You
know
we
have
a
lot
of
things
here.
H
A
lot
of
wonderful
things
here
in
chaos
too,
would
also
be
contributing
our
software
documentation,
design
and
all
of
that
stuff.
So,
while
we
also
create
initiatives
around
focusing
around
open
source
community
challenges
here,
we
will
also
contribute
to
chaos
at
large
and
yeah.
I
would
be
sharing
kind
of
having
doc
a
strategy
doc.
I
don't
know
if
someone
can
put
it
in
there
quickly,
but
yeah.
H
I
would
also
be
sharing
part
of
as
we
as
we
go
as
we
go
right,
it's
going
to
be
like
a
sharing
process
where
we
kind
of
share
what
we
learn
or
challenges.
We
discover,
via
different
social
media,
we're
going
to
be
using
social
media.
Twitter
space
we've
talked
about
twitter
spaces,
even
written
content
as
well,
maybe
through
the
blog
and
conference
sharing
on
conferences
and
events
and
yeah.
H
So
it's
really
nice
to
start
that
up-
and
you
know
we
all
already
have
like
so
many
contributors
from
africa
and
chaos
already,
and
it's
going
to
be
nice
for
those
folks
to
participate
and
get
other
contributors,
so
not
just
the
folks
that
are
currently
contributing
to
chaos,
but
we
also
get
other
participants
in
other
open
source
communities.
I
think
justin
mentioned
he
knows
about
this
cameroon
group,
so
it's
kind
of
like
expanding
beyond
nigeria
as
well,
and
all
that
focusing
on
other
countries.
H
So
yeah,
I'm
excited
to
start
that
off.
I
will
be
having
the
first
meeting
next
week.
I'm
still
trying
to
make
arrangements
for
that,
but
it
will
be
on
the
it
will
be
on
the
calendar,
the
calendar,
the
chaos
calendar.
So
if
you
have
that
added,
you
definitely
see
the
meeting
it's
going
to
be
happening
like
2
p.m,
west
african
time
and
call
for
participation
african
folks
already,
you
know.
H
H
A
H
What
day
ruth
do
you
want
to
do
it
like
this
week,
yeah
this
week?
I
have
that
already
just
to
set
up
that
form.
We
talked
about
on
the
call
so
once
that
is
all
set
up
at
no
ping
view
yeah.
Just
let
me
know.
E
C
G
C
C
Well,
nobody
has
taken
it
over
at
the
moment
so
for
a
while,
we
had
well
not
for
a
while.
We
currently
have
the
asia
pacific
call,
which
is
you
know,
whatever
every
two
weeks
on
wednesdays
and
just
I
was
thinking
that
we
could
just
like
it's
a
bit
of
just
a
rebranding
instead
of
just
thinking
about
it
as
a
call
really
recognizing
the
efforts
that
I'll
show
you
you're
on
so
the
efforts
that
shoya
has
done.
C
For
example,
over
the
last
year
in
china
running
the
the
meetups
and
helping
with
social
in
china,
I
mean
that's
a
really
excellent
thing
and
so
kind
of
doing
a
more
formal
recognition
through
chaos,
asia,
pacific,
that's
not
just
embedded
in
a
phone
call
or
a
zoom
call
right,
and
so
really
recognizing
that
work
and
kevin.
I
was
thinking
like
as
the
website
redesign
happens.
We
might
want
to
think
about
like
how
we
recognize
chaos,
africa
on
the
website,
as
well
as
chaos,
asia,
pacific
on
the
website.
F
I'm
not
sure
either.
Maybe
we
can
discuss
I'll.
Add
that
to
the
agenda
for
the
upcoming
web
content
meeting.
Okay,.
F
It
would
be
nice
to
it
would
be
nice
to
have
a
full
web
page
dedicated
to
them
yeah,
each
of
them
at
the
very
least,
okay,
cool.
C
And
then
I
I
think
it
would
also
be
good
to
have
an
identified
person
for
chaos.
Asia,
pacific
kind
of
as
ruth
is
happy
to
lead
efforts
to
chaos,
africa.
So
if
you
have
an
interest
in
kind
of
being
that
person
not
looking
at
anybody,
but
if
you
have
an
interest
in
being
that
person.
K
K
The
output
is
not
so
stable,
so
sometimes
I'm
I
I
I
don't
feel
very
proud
of
it
because,
but
I
I'm
excited
about
the
rebranding
or
like
have
an
official
grant
grant
thing,
because
this
is
also
a
problem
when
I
started
the
chaos
cast
china
because
I
was
kind
of
concerned,
if,
like
this,
is
a
class
brand
and
how,
where
is
the
limit
to
spread
it
or
to
use
it?
F
Question
what
is
what
is
this?
What
would
we
call
this
lead
person?
Would
this
be
the
community
manager
for
chaos,
asia,
pacific?
Would
this
be?
I
don't
need
any
manager
for
chaos,
africa.
C
C
D
And
maybe
some
kind
of
recognition
on
the
website
if
we
do
have
their
own
page
just
so
people
kind
of
have
a
point
of
contact
as
well
to
go
to.
C
K
Yeah
we
like
gather
the
people
in
a
wechat
group
and
have
that
social
media
on
wechat.
We
named
it
cloudcast
china,
but
I
think
it
would
be
even
better
to
name
it
kills
asia
pacific.
If,
in
the
future,
we
can.
J
K
Folks
in
yeah,
india,
especially
india
and
even
japan,
korean.
C
This
should
be
short,
just
it's
continuing
to
happen,
so
I
think
we
have
a
few
metrics
that
we
have
done
a
review
on
and
kind
of
finalized.
So
thanks
for
the
folks
that
provided
comments
and
I'm
the
person
who's
kind
of
assigned
to
take
a
look
at
the
ei
metrics
and
I'll
just
I.
C
B
C
It's
two
one
is
just
ossna
is
that
third
week
of
june-
and
many
of
us
are
gone
to
that-
so
sometimes
it's
hard
to
coordinate
meetings
and
then
the
second
week
is
the
week
kind
of
leading
into
the
us
fourth
of
july.
C
It's
not
fourth
of
july
is
on
a
monday.
Is
that
right,
and
so
that
just
takes
us
into
that
weekend,
which
is
also
kind
of
a
week
that
we
normally
take
off.
I
think
ossna
is
like
drastically
at
a
drastically
different
time
than
it
is
in
the
has
been
in
the
past.
Am
I
right
on
that?
Wasn't
it
normally
enough?
E
I
don't
know
who
keeps
muting
me
or
if
it's
anyway,
stop
that
it's
it's
always.
It
had
always
been
in
the
fall
and
they
moved
it
to
the
summer,
but
they
started
in
2020.
So
it's
never
actually
happened
in
the
summer.
So
this
is
the
first
time
we're
actually
experiencing
the
change
that
they
made
two
years
ago.
Okay,.
E
F
Just
regarding
the
taking
a
break
from
from
meetings
for
a
couple
weeks
for
if
there
are
any
students,
part
of
google
summer
of
code
or
google
summer,
docs
or
or
outreachy
on
here,
mentorship
will
continue
during
this
time.
So
contact
your
mentors
to
schedule,
meetings.
C
B
Awesome,
and
the
last
thing
to
be
discussed
for
the
meeting
today
is
the
focus
area
updates.
C
So
I
think
that's
pretty
important,
but
we're
down
down
to
two
minutes
and
there's
no
possible
way.
Conversation
could
happen.