►
From YouTube: CHAOSS DEI Working Group 5/25/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Matt,
okay,
hi
everybody
welcome
to
our
discussion
today
and
I'm
just
bringing
up
the
meeting
notes.
Let
me
put
this
link
in
the
chat
for
you
nope.
That's
the
wrong
link.
That's
the
octocat
link.
A
A
All
right
and
on
the
agenda
is
project
badging.
Let
me
just
bring
up
open.
Let
me
bring
up
some
matt.
Do
you
want
to
talk
to
hello
who
put
the
action
item
for
project
battery
in
there.
A
Give
an
update,
yeah.
I
know
that
we
talked
about
it
the
last
time
that
we
met,
and
I
think
one
of
the
things
we
were
supposed
to
take
a
look
at
was
the
dei.m.d
and
the
recommended
metrics.
For
for
that
and
sure,
if
you
could,
if
you
stop
sharing,
I
can
share
my
screen.
Yes,
I
can
stop
sharing
I've
learned
a
lot
about
zoom
the
last
two
years.
C
I've
been
making
updates
to
project
badging,
starting
with
the
the
read
me
or
I'm
sorry,
just
with
the
repository.
C
So
I
think
people
just
honestly
just
comment
as
you
see
things.
So
this
is
not
you
know,
set
in
stone
by
any
means,
so
with
respect
to
project
badging,
because
we
are
trying
to
balance
like
the
potential
volume
of
projects
that
may
be
applying,
as
well
as
our
ability
to
review
those
projects
like
in
terms
of
the
number
of
badgers
that
we
have
available
to
us.
C
C
At
with
this,
so
at
this
moment
we
don't
have
additional
levels,
so
the
project
submission
guidelines,
I'll
we'll
take
a
look
at
this
requirements
document
in
just
a
little
bit
so
that
you
have
to
fulfill
these
requirements
before
actually
applying
for
a
badge.
C
I
think
would
it
make
sense
that
we
just
follow
the
same
kind
of
form,
approach
that
we
have
for
event,
badging,
where
we
would
push
people
to
a
link
for
a
form
to
fill
out
like
matt,
I'm
kind
of
looking
at
you
just
in
the
sense
of.
Would
that
be
easy
enough?
Do
you
think
to
replicate
for
project
badging.
B
No,
but
we
have
another
option:
that's
much
better!
Oh
no!
This
is
this
is
brought
up
by.
I
think
aish
had
originally
brought
this
up,
but
github
is
now
supporting
issue
forms
which
is
basically
the
same
form,
but
in
the
submission
of
a
github
issue
which
would
cut
the
middleman
and
also
make
the
process
a
lot
less
a
lot
fewer
steps
to
get
through.
Okay,.
B
B
C
B
Yes,
I
just
dropped
a
link
in
here.
I
turn
it
into
a
link.
B
But
this
is
just
the
github
like
before.
Oh
I
put
the.
C
Okay,
if
anybody
would
like
to
help
me
in
this
like
in
this
like
to
create
a
sample
form.
A
So
it's
it'd
basically
be
a
issue.
Template
type
form
map
is
what
I'm
seeing
here.
B
Yeah,
it's
just
a
fillable
form
and
then
it
turns
it
into
markdown,
just
like
we
were
doing
manually
before.
C
A
I
mean,
I
think
one
one
question
I
would
have
is
if
we've
said
that
the
you
know,
we've
stated
that
we
want
the
repository
to
have
the
dei.md
in
it,
and
a
lot
of
quote-unquote
projects
have
they're.
They
have
a
repo
org
like
badging
or
chaos,
and
they
would
want
to
be
badged
as
an
org.
So
do
we
explicitly
recommend
that
they
create
dot
github,
slash
dei.md?
A
A
So
I
think
just
hold
that
check,
for
it
hold
that
thought
for
a.
D
C
Okay,
just
in
terms
of
kind
of
logistics
as
well,
this
point
three
that
this
was
kind
of
around
the
like.
You
have
the
ability
to
make
the
application.
You
know
what
I
mean
like
you
in
your
community
are
applying
openly
and
transparently
on
behalf
of
your
community,
and
we
had
talked
a
little
bit
about
like
you
remember
this,
like
you
have
to
be
a
proven,
maintainer
or
you
have
to
have
commit
rights,
or
something
like
that.
C
You
remember
that
conversation
from
last
week,
yes
yeah,
so
I'm
not
quite
sure
I
have
that
in
requirements.
But
what
do
people
think
about
this?
That
one
of
the
requirements
is
that
you
have
to
post
an
issue
in
your
in
your
community
issue
tracking
system.
That
says
I'm
applying
for
a
badge
and
I
I'm
applying
for
a
chaos
badge.
D
C
D
Wow,
okay,
great
okay,
so
I
think
that
one
way
that
we
can
do
it
first,
I
think
that
it's
a
very
good
idea
to
publicly
declare
that
communities
applying
for
a
badge
but
other
than
asking
them
to
do
like
a
github
issue.
Maybe
we
can
ask
them
to
link
a
blog
post
or
to
link
any
kind
of
announcement
that
they
have
met
in
the
community
that
they
are.
D
They
are
applying
for
the
badge.
Probably
they
have
shared
it
on
their
social
medias
or
in
discourse.
So
maybe
maybe
not
github
mandatory,
but
any
other
kind
of
announcements
would
work
as
well.
C
E
We
could
also
explain
why
we're
asking
for
that
in,
like
just
a
follow-up
sentence,
or
you
know
a
little
preface
in
order
to
ensure
transparency
and
okay,
something,
like
you
know,
just
so.
People
understand
why
we're
asking
for
it
in
case
they
don't.
E
C
C
Foxy
dog's
asleep
dreaming
next
to
me:
okay,
that's
cool!
Thank
you!
Thank
you
for
that
all
right.
So
then,
this
is
still
just
part
of
the
submission
guidelines.
Make
sure
that
you
communicate
with
reviewers.
This
is
just.
I
think
this
is
normal.
The
review
ends
when
the
checks
are
satisfied.
C
C
C
The
the
repo
can
be
cloned
or
browsed
without
registering
an
issue.
Tracker
is
readable.
Without
registration,
a
communication
channel
that's
easily
accessible.
C
No,
we
certainly
don't
have
the
capacity
to
do
that.
So,
let's
we
don't
have
to
solve
that
now,
but
yeah,
that's
something
to
sort
out
okay!
So
let's,
let's
just
hold
on
to
that
for
a
second
then,
but
that
there
is
a
readme
file
that
clearly
just
defines
the
objectives
of
the
project.
This
is
from
our
conversation
from
last
week
an
osi
approved
license
license,
license,
license
file,
contributing
guidelines,
file
code
to
contact
file,
and
this
is
the
diversity,
equity
and
inclusion
file.
C
A
Is
the
same
thing
as
the
repository
can
be
cloned
and
browsed
without
registration?
Really,
oh,
it's
just
a
is
it
a
private
public
question
yeah,
that's
yeah,
so
I
think
one
and
two
are
actually
this.
I
mean
I
guess
they're
different,
because
the
documentation
has
to
be
publicly
available
and
the
project
contacts
are,
I
would
say,
in
a
repository
or
repositories
that
are
public.
A
That
would
be
a
shorter
way
of
saying
that
can
be
cloned
and
browsed
without
registration,
so
I'm
gonna
need
excited
enough
to
be
logged
into
github.
If
I
want
to
clone
a
repository
on
github,
I
believe.
F
Do
we
want
to
just
do
we
want
to
just
merge
those?
Do
we
want
to
just
merge
those
two
together
and
say
that
the
the
project,
I
think
repo
must
be
publicly
available
or
the
project
itself
must
be
publicly
available?
I
think
there
are
different
things
actually.
A
A
B
So
I'm
not
sure
what
channels
are
that
we're
talking
about
the
stuff
in
more
granular
detail
in
I
I
just
had
a
comment
about.
I
think
it
would
be
important
to
assume
that
the
person
who's
applying-
I
guess
assume,
is
the
wrong
word,
but
but
go
on
start
from
score
one
basically
and
and
provide
the
context
that
may
be
necessary
for
the
for
the
implementation,
specifically
in
question
five
or
section
five,
where
we
have.
B
We
asked
them
for
certain
things,
but
some
of
those
are
kind
of
can
be
considered
jargon
in
some
ways
and
if,
even
if
somebody's
running
a
project,
they
might
not
know
about
things
like
a
contributing
guidelines
file
if
they've
never
done
one
themself
just
to
provide
the
information,
that's
necessary
to
get
those
started.
C
Okay,
so
let
me
let
me
go
to
there's
two
points
raised
here.
So
first,
can
we
I'd
like
to
matt?
I
hear
your
point
and
I'll
get
to
it
in
just
a
second.
So,
but
the
with
respect
to
this
would
it
make
sense
to
say
documentation
for
your
project
is
publicly
available
project
contents
in
a
repository,
that's
publicly
available,
yeah
excuse
me,
okay
and
then
okay,
so
let
me
I
just
elizabeth.
Does
that
address
your
question?
C
C
Okay
and
then
I'm
sorry
and
then
matt
yours
was
about
this
right.
B
In
particular,
actually
all
five
items
probably
need
more
information
that
define
what
we're
looking
for,
because
we
we
have
an
item.
We
say
we're
looking
for
this,
but
what
are
we
looking
for
out
of
it?
Because
I
know
if
somebody
just
makes
the
file
and
leaves
it
empty
or
doesn't
provide
the
correct
information
on
it.
Then
we'd
have
to
call
them
out
on
it
too.
B
So
so
for
the
badging
updated
version
of
the
badging
application,
we
actually
provide
the
metrics
for
context,
and
we
also
and
for
each
metric.
We
also
provide
references
for
for
what
they,
what
it
would
look
like
to
to
be
implementing
this
correctly.
So
I
can,
I
can
put
in
some
references
here
and
there
for
yeah
in
the
I
think.
Maybe
the.
C
Last
point
I
have
because
we
have
a
link
out
to
a
reference,
but
yeah,
maybe
just
like
some
text
at
the
first
four
points
would
be
really
helpful.
Okay
and
is
it
would
it
be
just
like,
and
if
I
oh,
I
see
your
hand
too.
Would
it
be
like
for
the
code
of
conduct
file,
like
example,
code
of
conducts
include.
B
C
G
Yeah,
so
adding
too
much
point,
I
think
like
something
like
a
checklist
just
the
way
we
have
like
on
the
d
I
event
button.
We
have
like
a
checklist
with
like
enough
context
on
how
you
know
each
of
the
metrics
works,
so
something
like
also
like
a
checklist
on
each
of
these
five
items.
I
think
you
know
and
and
resources
like
matt
said
too.
C
Okay,
and
so
are
you
thinking
ruth
about
the
the
checklist
like
during
on
in
the
issue
like
from
a
reviewer
perspective,.
C
C
A
Yeah,
I
just,
I
think
I
think
these
are
the
things
that
matt's
gonna
do
anyway.
Okay,
but
like
the
code
of
conduct,
there
should
be
a
pathway
for
addressing
if
there's
harassment
or
an
issue
in
the
community
in
there,
and
I
think
for
contributing
guidelines.
A
Maybe
the
simple
way
to
evaluate
those
is
there's
some
direction
for
a
newcomer
like
if
I'm
totally
new
to
the
project
when
I
open
contributing
md
on
the
on
the
repo.
I
have
some
clue
where
to
go,
and
this
is
these
are
the
kinds
of
documents
that
it
can
get
tricky
to
distinguish
between,
like
usually
there's
a
primary
repo
or
two
in
a
larger
community
with
many
repos.
C
Okay,
so
so
then
maybe
there
were.
I
think
there
were
two
points
in
what
you
just
said.
So
one
is,
I
don't
know
what
people's
thoughts
are
on
this
but
like,
if,
if
there's
a
code
of
conduct
file
in
the
repository
like
how
deeply
do
we
investigate
the
code
of
conduct
file
like
in
terms
of
enforcement,
so
like
would
there
be?
I
just
I
don't
see
us
having
the
capacity
of
really
getting
to
the
point
like
that
enforcement
doesn't
look
solid
or
I.
A
Think
if
they
have
a
contact
for
enforcement,
that's
steep
that's
deep
enough.
I
I
think
we
could
encourage
projects
to
specify
the
levels
of
response
for
different
kinds
of
activities,
but
honestly,
as
a
project,
chaos
is
just
doing
that
now
ourselves
getting
more
specific,
so
yeah
and
from
a
review
perspective
like
we
would
be
just.
C
C
B
I
still
need
to
add
the
guide
on
what
you
want
to
have
in
the
code
of
content.
This
is
just
the
github
okay.
This
is
just
the
github
guide,
so
I'll
I'll
look
at
what
maybe
a
solid
reference,
because
I
don't.
If
anybody
has
ideas,
please
put
them
in
the
chat
too,
because
I
don't
have
any
specific
things
I'd
put
in.
I
have
in
mind
for
like
how
to
create
a
code
of
conduct.
I'm
thinking.
B
Covenant
could
be
a
good
one
yeah.
I
went
to
that
for
the
first
time
in
a
while,
and
it
looks
like
they're
also
I'll
look
into
it.
I'll
have
more
information
later.
Okay,
thanks
matt
yeah.
C
Okay,
not
that
this
all
right,
so
this
is
all
really.
G
An
example
I
had
something
to
say
for
the
d
I
dot
md
file
describing
attention
to
do
you
want
to
put
the
link
to
the
oh
okay.
G
I
want
that
see
if
you
want
to
put
the
link
to
like
the
page
that
shows
di
working,
good,
metrics
or
something.
But
since
we
have
this
here,
yeah.
C
G
G
C
The
automatic
okay,
so
yeah,
so
there
was-
I
haven't,
updated
that
yet
that
there
was
we
might
want
to
also
include
or
in
lieu
of
something
like
put
like
how
you
support
newcomers
or
the
newcomer
experience
in
here,
and
so
really
what
this
document
is
is
we
would
ask
for
a
document
that
would,
I
think,
look
fairly
similar
to
this.
C
C
There
would
be
a
link
to
each
one
of
these
metrics
as
published
by
chaos,
and
then
really
all
that
we're
asking
for
is
a
narrative
from
the
submitter
as
to
how
the
project
is
addressing
say,
for
example,
project
burnout
or
a
narrative
from
the
submitter
about
how
the
project
is
supporting
the
newcomer
experience.
You
know
what
I.
C
C
Is
it
attendee
and
speaker
democrat,
like
like
event,
demographics.
C
So
when
an
applicant
talks
about
event,
demographics,
it's
often
times
just
about
it's
a
narrative
about
how
the
event
addresses
demographics.
Is
that
correct
and
we
read
the
narrative
yeah
and
we're
like
that.
Sounds
great
or
we
read
the
narrative
and
we're
like
I
don't
this
doesn't
make
sense?
Can
you
provide
more
detail
so
that
would
it's
similar
to
that
that
we're
just
reading
the
the
narrative
provided
by
the
applicant.
C
E
B
B
It
might
be
too
much
with
the
abstract
question
would
be
fine,
and
I
was
you
were
talking
about,
I'm
looking
at
all
the
metrics
we
have
available
to
us
when
it
comes
to
both
project
and
governance
and
we
have
like
we
do
have
project
demographics.
We
also
have
that
code
of
conduct
for
project
under
governance.
That
I
think,
would
be
good
to
ask
more
about
the
code
of
conduct
and
maybe
critique
it
more
once
we
have
those
check.
Those
first
checks
in
line
two,
that's
it
and
yeah
right.
B
I
was
just
thinking.
It
might
also
really
be
good,
like
we've
been
doing
an
event
badging
to
prompt
for
prompt
for
links
or
evidence
of
like
what
they're
talking
about
so
that
they
can
back
it
up
in
their.
A
C
I
like
that,
okay.
E
C
Or
whatever
project
demographics.
C
Right
matt,
you
had
maybe
suggested
this
if
I
understood
you're
right
that
this
could
be
a
place
where
we
ask
for
more
detail
on
the
code
of
conduct.
B
Yeah
and
I'm
thinking
it
doesn't
look
like
we
have
metrics
that
cover
specifically
newcomer
experience
yet
sorry
for
the
background
noise,
but
I'm
a
little
not
too
sure
about,
including
that
before
it's
before
it's
a
metric,
because
this
all
has
to
be
backed
up
by
the
metric.
C
C
C
H
C
That's
fair
shoya.
H
So
if
this
diversity,
this
d
imd
file,
is
something
that
we
are
trying
to
encourage
project
repository
to
have,
because
I
just
I
was
looking
at
some
of
the
github
repository
that
was
almost
the
most
popular
repositories
with
I
just
by
stars.
I
I
was
checking
them
and
I
I
don't
think
even
they
have
this
md
file
right
now,
because
because
this
haven't
been
a
very
prevalent
thing,.
C
C
All
right,
one
other
thing.
C
Me
enough
to
work
on.
I
thought
I
had
one
other
comment,
but
this
is
really
helpful.
So
thank
you,
everybody.
I
will
have
more
next
week.
A
All
right
thanks,
everyone
for
elizabeth.
B
Yeah,
oh
sorry,
I
was
just
saying
I
dropped
that
that
that
sample
and
we'll
drop
it
in
the
chat
here.
I
just
thought
it
was
really
really
cool
and
we
could
really
use
it
as
far
as
that,
the
issue
form
sample
it
turned
out
pretty
good.
B
F
A
Oh
I'll,
let
someone
else
say
it.
There's
matt,
you
shared
a
link
down
here
under
the
the
details.
B
Yeah
so,
as
I
understand
it
kevin
we
were
going
to
be
working
on
like
asking
the
minimal
information
in
the
in
the
opening
questions
and
then
also
once
we
get
into
the
review.
We
start
asking
more
questions
about
what
we'd
like
to
see
in
the
code
of
conduct.
F
F
C
A
C
A
You
everybody
yeah,
so
are
there
any
other
items
we
have
10
minutes
available
if
they're
in
the
past
we've
looked
at
open
issues
in
prs.
I
don't
know
if
we
do
that
every
time,
but
we
could
certainly
do
that.
A
F
Had
an
action
item,
I
had
an
action
item
from
the
last
meeting
to
look
at
time.
Inclusion.
Yes,
there
is
a
pull
request
in
for
that.
Maybe
we
could
look
at
that.
F
E
A
The
other
one
go
back,
sean
okay.
I
was
on
the
wrong
pull
request
this
one
that.
F
A
F
So
so
tejas
had
gone
through
and
made
changes
based
on
matt's
recommendations,
yeah
and
there
were.
There
were
three
recommendations
that
matt
had
made
that
tejas
didn't
didn't
address.
So
I
went
back
and
addressed
those
those
three
issues
and
those
the
maybe
maybe
we
can
peek
at
the
comments
to
see
what
matt's
yep,
what.
A
F
Bandwidth
is
part
of
how
network
bandwidth
is
part
of
the
metric,
how
low
bandwidth
as
part
of
the
metric,
and
then
there
was
an
also
also
an
issue
with
the
the
the
survey
list
for
the
presenters.
F
So
I
added
text
in
the
description
to
account
and
describe
how
network
network
bandwidth
is
an
issue
for
time
inclusion
and
then
I
also
adjusted
the
survey
list
for
the
presenter
to
make
it
a
little
more
explicit
and
to
match
the
attendee
survey
list.
That
was
already
there.
C
F
And
then
I
do
have
a
comment
in
this
pull
request
as
well
like
I
have
added
a
considerable
amount
of
text
about
network
bandwidth,
so
I
am.
I
am
wondering
if
we
have
changed
this
metric
enough,
where
we
need
to
possibly
send
it
back
through
the
review
process
or
if
or
if
this
text
is
just
explicitly
stating
what
was
implicitly
already
there.
A
You've
added
the
detail
necessary
for
us
to
assess
whether
this
this
time,
inclusion
is
really
addressing
the
detail.
I
think
it
was
on
obviously
non-specific
earlier
and
a
reasonable
person
would
think
that
all
these
things
are
part
of.
What's
in
the
less
explicit
statement
that
it's
replacing
yeah.
C
F
Think
when
we're
doing
these,
we
should
we
should
always
have
that
discussion
if,
if
a
block
of
text
is
added.
C
A
A
F
A
Which
would
be
five
you'd
listed
522
yeah
on
the
today's
525?
I
don't
think
it's
important
enough
to
like
modify
the
pull
request
or
make
a
separate
commit.
I
think
we're
close,
and
that
is
when
it
was
edited.
A
So,
okay,
I
guess
before
this
issue
can
be
closed.
Then
we
need
the
metrics
update,
the
spreadsheet
updated
and
the
translations
repository
probably
needs
to
get
a
notice
to
adapt
the
translation
to
the
new
language.
A
A
F
A
F
That's
another
one
that
it's
it's
only
if
we
send
it
back
into
the
release
cycle
so
and
I
do
have
a.
I
have
an
edited
version
of
this
checklist
that
I
have
put
in
a
pr
for
in
I
think
in
the
value
working
group.
Okay,
if
someone
can
take
a
look
at
that
pr,
if
that.
F
I
will
then
go
and
move
that
okay,
I
will
move
it
into
the
community
repo
as
a
template,
and
then
we
can
start
pulling
it
into
the
other
working
group
repos
as
well.
A
Okay,
so
we
don't
need
to
do
that
matt's
going
to
take
a
look
at
it.
Yeah,
okay,
well,
we're
at
time,
then
I
appreciate
all
that
work,
kevin
and
appreciate
everyone's
participation
in
our
discussion
of
project
badging.
I
think
that's
going
pretty
well.
So
thanks
to
everybody
for
that,
anybody
else
want
to
sign
up
to
be
coordinator
next
time.
F
We
need
to
we
need
to
solve
this
sandwich
problem
next,
I
said
a
hoagie
as
a
sandwich
too.
I
put
that
on
the.