►
From YouTube: CHAOSS DEI Working Group 3/30/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Hey
everybody:
this
is
the
dei
working
group
for
march
30th.
We
are
gonna,
be
facilitating
by
committee
today,
so
at
least
until
justin
comes
before
we
oh
justin's,
here
sorry
justin.
We
were
just
about
to
cut
in
on
your
your
action
here.
Let
me
here's
the
minutes.
We
just
started
dropping
some
stuff
in
not
a
big
deal.
A
Let
me
is
it
oh,
he
left
I
was
gonna
say.
Is
there
something
I
can
do
from
my
end,
but
maybe
he's
yeah
he's
rejoining.
I'm
gonna
pause
the
recording,
then,
okay,
now
there
we
go
all
right.
We
started.
B
C
D
Matt
one
cup,
but
it
was
a
very
large
cup.
B
Well,
I
am
like
at
one
one
coffee
and
one
tea,
so
I'm
like
it
right
in
the
middle
okay.
So
since
I
already
was
a
little
bit
late,
we
can
go
ahead
and
dive
in
so
we
can
go
ahead
and
kick
off
with
the
first
part
which
maybe
christy
you
want
to
drive
this
one
a
little
bit
on
the
mentorship
program.
Notes.
E
Yes,
so
I
created
this
document
with
best
practices,
basically
for
some
of
the
projects
that
we
want
to
have
and
that
we
actually
run
in
our
community.
E
What
I've
done
here
is
that
I
have
listed
the
project,
the
timeline,
the
link
of
the
timeline,
the
most
important
dates
like
the
organization
application
when
it
starts
when
the
application,
when
the
organizations
get
their
accepted
emails
and
also
in
this
document,
I
have
edit
with
some
research
that,
with
some
researchers
have
done
online
and
some
articles
that
I
read,
I
listed
here
some
responsibilities
that
the
mentors
might
have
like
during
the
project:
the
responsibilities
that
that
gsoc
students
will
have-
and
also
there
are
some
some
procedures
like
how.
E
What
can
we
consider
in
order
to
see
or
in
order
to
decide
what
application
is
will
be
accepted?
And
what
is
something
that's
really
important
for
us
also,
I
have
listed
some
health
and
system
sustainability,
mentoring
matrix
like
basically
to
know
if
the
project
has
succeeded
or
not.
What
are
we
looking
for?
E
What
do
we
aim
with
this
project
and
so
on?
So
the
first
so
the
mentor
identification
their
responsibilities
and
for
the
mentors
and
the
responsibilities
for
the
gsoc,
I
have
actually
gotten
them
from
the
website
of
the
g-stock
and
the
rest
of
it.
It's
due
to
some
researches
that
I've
done
and
to
what
I
thought.
That
would
be
good.
So
this
document
is
completely
open
for
any
suggestion,
as
suggestions
that
you'll
have
feedback,
and
once
I
collect
all
this,
I
can
go
back
and
put
it
in
order
or
like
do
the
adjustments.
B
A
Before
we
do
that,
I
just
have
a
quick
question:
how
do
we
feel
about
so
we're
right
now
we're
in
the
period
before
the
mentor
the
mentees
are
chosen
and
like
this,
this
part
of
the
process
feels
very
kind
of
like
a
free-for-all.
In
my
mind,
specifically
with
regard
to
getting
people
onboarded
onto
chaos
like
we
keep,
I
feel
like
we
keep
sending
the
same
kind
of
information
out.
A
If
I
look
here
now,
we
have
in
the
outreachy
channel,
we
have
76
people
in
there,
so
we
have
just
had
this
huge
influx
of
interested
people
and
I'm
not
sure
like
does
that
belong
in
a
dock
like
this,
or
is
this
doc
supposed
to
just
take
us
from
okay,
like
we've,
we've
basically
decided
who
we're
going
with
and
how
we
move
forward
like
what
are
you
what's
your
vision
around
this
christy.
E
I
was
thinking
for
this
document
to
serve
more
as
a
guideline,
maybe
to
help
more
the
like
to
help
more
us
in
terms
of
the
mentors
the
organization,
and
maybe
we
can
have
us
a
specific
area
also
for
the
students
or
for
the
applicants
that
are
joining
us.
So,
but
maybe
that's
a
good
point.
Yours
as
well.
E
We
can,
if,
if
that's
okay
for
everybody,
we
can
also
include
like
what
can
be
the
best
way
that
we
can,
that
we
can
approach
these
the
newcomers
in
our
community
and
things
like
that.
So
we
can
definitely
broaden
the
document
in
the
first
part
at
the
mentorship
program.
I
have
just
listed
the
main
programs,
but
I
have
not
filled
them
out
with
the
information,
because
I
thought,
let's
discuss
it
first
and
then
we
can.
A
Do
this,
and
and
some
of
this
might
come
with
as
our
experience
with
these
mentorship
programs
go
like,
I
did
not
realize
I
know,
chaos
has
done
outreachy
in
the
past,
but
I
was
not
around
by
the
time
I
joined
chaos
that
student
was
already
onboarded
and
working.
A
A
So
that's
kind
of
not
been
a
great
experience
for
him
and
for
for
you
know,
for
our
applicants,
like
they're,
trying
to
get
answers
on
things
and
like
he's
the
only
one
that
knows
so,
just
kind
of
being
a
little
more
proactive.
I
think
for
the
next
time
around
and
then
like
chico's.
Africa
is
a
new
program
for
us,
so
we
don't
really
know
what
to
experience
there,
but
maybe
this
doc
can
kind
of
just
be
a
hey
feedback
for
next
time.
Make
sure
we
have.
A
E
B
B
I'm
thinking
this
is
something
that
fits
in
that
context
of
the
handbook
conversation,
because
I
see
a
lot
of
this
really
being
more
like
internal
focused
documentation
to
help
us
be
organized
and
unified
on
like
how
we
approach
things
and
like
what
are
the
goals
and
trying
to
be
clear
on
like
how
these
processes
work
even
internally.
B
So
I
see
that
probably
fitting
into
the
handbook
discussion
and
I
know
there's
some-
we
talked
about
it
before
there's
a
lot
of
like
kind
of
tricky
pieces
with
the
handbook
right
now,
so
I
don't
know
if
it's
something
that
we'd
want
to
like
go
ahead
and
edit
work
on
editing
this
document,
with
the
assumption
that
we'd
integrate
it
as
a
new
set
of
content
into
the
handbook.
B
Based
project-
that's
happening,
I
guess
without
richie
this
summer.
Maybe
it
could
go
with
this,
I'm
just
trying
to
think
like.
So
I
guess
that's
probably
where
this
work
would
be
translated
to
in
terms
of
where
we
take
it
once
we
go
through
it
and
workshop
it
for
a
bit,
it
would
probably
be
like
either
to
the
handbook
or
it's
it's
future
home
the
knowledge
base.
I
guess
is
my
my
thinking
right.
A
Yeah,
I
would,
I
would
plus
100
that
I
think
it
definitely
needs
to
be
documented
and
in
a
place
where
that's
easily
accessible
for
anybody,
so
that
you
know
a
prospective
applicant
can
also
see.
Oh
hey,
it
looks
like
these
people
kind
of
have
it
together.
I
mean
that's
debatable,
but
you
know
like
at
least
we're
all
on
the
same
page
of
like
what
what
are
our
expectations?
A
What
are
the
responsibilities,
so
I
100
agree
and
to
that
point
this
is
off
tangent
just
a
little
bit,
but
I
feel
like
this
is,
I
don't
know,
maybe
the
third
or
fourth
doc,
that
we've
been
like.
Oh
yeah,
we'll
add
that
to
the
knowledge
base,
when
it's
ready
and
now
I
feel
like
I'm
losing
these
docs.
So
do
we
need
to
create
a
like
a
meta
list
of
these
kind
of
pieces
of
information
that
will
eventually
make
it
into
the
community
handbook
like?
Where
can
we
make
sure
that
this
doesn't
get
lost?
A
I
guess
is
my
question
in
this:
like
weird
transition
period
between
old
community
handbook
and
new
knowledge
base,.
B
Yeah,
I
think
we
can
probably
try
to
integrate
this
and
get
real-time
feedback
during
the
process
with
the
current
team,
but
maybe
we
can
use
like
a
since
I'd
see.
This
is
more
of
kind
of
a
dei
topic.
We
could
track
this
in
the
dei
github
and
like
make
a
checklist
of
content
that
we
want
to
advocate
for
or
write
into
the
handbook
and
track
it
there
or
maybe
we
should
do
that
in
the
community
repo,
I'm
not
sure
what
would
make
more
sense.
I
mean
I
see
this.
A
I
think
that's
a
really
great
point
and
I
think,
maybe
that
central
place
in
the
community
handbook
would
ensure
that
it's
seen
and
not
lost
across
the
working
groups
so
yeah.
I
agree
with
that.
I
like
that
idea.
I
don't
know
what
the
rest
of
you
all
think,
but
just
having
like
even
an
issue
where
we
can
just
like
drop
our
notes
or
drop
our
thoughts
in
of
the
as
these
docs
pop
up
that
we
want
to
add
to
the
knowledge
base.
I
think
that
would
be
a
good
place
for
it.
B
Then
what
we
could
do
is
then
I
can
take
an
action
to
open
an
issue
on
the
chaos
community,
repo
for
tracking
tracking.
Basically,
all
things
knowledge
base
that
we
want
to
make
sure
we
we
capture
and
then
maybe
we
can
spend
10
minutes
just
with
that
context
of
like
kind
of
how
we
want
to
frame
this
or
where
this
might
live.
We
could
go
10
minutes
through
this
and
just
do
like
a
first
pass
on
comments
and
and
leave
any
feedback
or
notes
in
the
doc.
E
E
Maybe
we
can
try
to
leave
this
mentorship
document,
probably
for
the
next
time
as
well,
if
matt
and
sean
might
join
just
for
the
document
to
be
more
completed
or
have
some
other
things,
and
then
we
can
discuss
everything
at
the
same
time,
once
everyone
has
put
the
feedback.
A
B
Okay,
so
it's
about
the
same
as
outreachy
too
then
okay!
Well,
we
can
follow
up
next
time
too.
Also,
when
we
have
some
other
folks
who
are
since
we're
spread
pretty
thin
on
from
from
spain,
I
think
so
cool
we
can
go
ahead
and
and
jump
onto
the
next
one
and
I'll
also
just
to
fly
I'll
open
the
github
issue.
Just
so,
we
can
start
tracking
this
kind
of
content
for
the
knowledge
base.
B
A
I
did
not
add
it,
but
I
can
speak
to
it
a
little
bit
somewhat.
Let
me
just
I'll
share,
so
we
can
kind
of
just
show
everybody
what
that
is.
A
So
there
have
been
a
a
group
of
folks
oops
working
on
this.
Oh
here
we
go
a
group
of
folks
working
on
this
to
provide
guidance
for
those
who
are
trying
to
use
and
implement
our
metrics
to
make
sure
that
they're,
mindful
of
the
way
that
they're
collecting
storing
using
that
data,
especially
when
it
kind
of
overlaps
with
personally
identifiable
information
or
pii,
but
we
are
going
to
add
this
statement
to
every
single
metric.
We
have
just
to
bring
it
top
of
mind,
so
anybody
who's
reading
this
metric
any
atomic
metric
regardless.
A
We
just
want
them
to
be
aware
of
the
implications
and
the
ethics
around.
So
this
document
talks
about
like
some
things,
to
consider
some.
You
know
how
we
handle
information,
what
the
sensitivity
levels
are
and
then
we
link
to
some
guidance
on
you
know
different
countries,
etc.
These
links
seem
to
not.
A
Interesting,
I
want
to
look
at
that.
We
might
have
lost
that
in
translation
from
a
google
doc
to
this,
because
I
don't
think
I
can
click
on
any
of
these,
but
anyway.
So
that's
what
this
document
is,
and
we
just
want
to
make
sure
that
everybody
knows
that
we
have
this
document
now
and
that
it's
out
there
and
ready
to
go
yeah.
These
links
seem
fine.
For
some
reason,
these
other
links
did
not
come
through.
So
I'll
actually
add
an
action
item
for
myself
to
double
check
those
links.
B
A
Yeah,
it's
in
the
templates
metric
or
metric
yeah
metric
template,
it's
in
the
metric
template
with
another
kind
of
standard
blurb
about
like
why
they
should
care
and
why
they
should
pay
attention
to
this,
and
we
can
wait.
Let
me
do
this
because
I
can't
do
more
than
one
thing
at
one
time,
because
I'm
limited
in
that
capacity.
A
Let
me
just
pull
up
a
metric
here,
so
you
can
read
that
I
don't
know
if
it's
been,
I
think
it's
been
added
to
some
of
the
newer
ones.
So
part
of
our
task
is
to
go
back
and
add
that
blurb
to
all
the
old
metrics
too.
A
B
A
Longer
yeah
it's
been
going
on
for
quite
a
while
and
because
it
was
a
little
bit
confusing,
because
chaos
also
has
a
data
use
statement
that
we
we
follow.
That
is
like
how
we
use
our
data
in
our
community,
but
we
also
then
kind
of
from
that
branched
out
and
said
you
know
we
should
really
it
because
we're
you
know
offering
advice
on
how
people
can
measure
this
stuff.
We
should
also
offer
advice
and
guidance
on
what
they
should
be
doing
with
this
data
just
to
be
as
responsible
as
we
can.
A
That
would
be
bad
and
you
know,
because
we
were
also
thinking
like
a
lot
of
the
people
who
are
using
our
metrics
are
like
open
source,
maintainers
and
they're,
not
necessarily
lawyers
or
don't
have
that
that
skill
set
or
that
knowledge
about
like
things
that
they
should
be
mindful
of
so
yeah,
and
I'm
sure
that
that
that
document
will
grow,
as
you
know,
as
we
go
on
and
people
contribute
to
it.
But
this
is
definitely
a
good
first
first
pass
so.
B
A
Yeah
for
sure
and
yeah
and
also
yeah,
I
think
also
just
as
one
one
quick
final
final
thing:
we
don't
we
don't
really
like.
We
put
it
in
every
metric,
but
we
don't,
I
don't
think,
identify
those
that
do
definitely
touch
on
pii,
like
some
do
in
the
dei
working
group.
So
I
don't
know
how
we
feel
about
that,
like
we
just
kind
of
leave
that
blanket
statement
in
every
metric,
but
we're
not
like
hey.
This
is
one.
This
is
the
one
that
has
pii
in
it
potentially
like.
A
When
we're
you
know
doing
a
survey
on
psychological
safety,
for
instance
like
so
I'm
not
sure
how
that
fits
into
it,
but
yeah.
B
A
Yeah,
I
added
this
only
because
this
is
the
last
week
to
review
any
comments
or
feedback
we've
gotten
from
the
public
on
these.
So
I
thought
maybe
we
could
just
look
through
and
see
if
we
have
to
make
any
changes
to
these
metrics.
A
Yeah
yeah,
this
is
just
like
the
final,
so
we
like
open
up
all
the
metrics
for
30
days
prior
to
our
release.
Just
in
case
you
know,
it's
like
a
last
call
for
comments.
If
anybody
has
any
additional
feedback
from
the
community
and
sometimes
like
people
from
different
working
groups,
will
jump
back
and
forth
and
look
at
others
metrics
that
they
haven't
seen
before,
and
it
looks
like
on
this.
One
matt
is
taking
care
of
that.
A
No,
the
just
the
month
of
march
is
the
30
day
period,
31
day
period
and
then
because
we
usually
do
a
release
in
april
and
october,
and
so
in
april,
we'll
give
it
like
a
a
week
or
so
to
kind
of
make
up.
You
know,
wrap
up
any
loose
ends.
A
Add
that
link,
for
instance,
do
any
final
things
and
then
kevin
and
the
metrics
release
team
will
do
their
automated
process
of
pulling
all
the
documents
into
that
pdf
and
putting
them
all
on
the
website
as
as
released,
so
they
will
go
from
like
the.
Where
is
that
so
right
now
these
have
tags
that
say
under
review,
so
those
tags
will
go
away
and
this
issue
will
go
away
and
they'll
just
all
look
like
released
metrics.
If
that
makes
sense.
C
A
B
A
Yeah
yeah,
so
this
is
just
a
final
like
again,
a
final
like
last
call
for
anybody
who
had
reviewed
this
metric
that
wasn't
involved
in
those
conversations,
maybe
at
the
beginning,
and
that's
just
kind
of
coming
in
with
fresh
eyes,
and
we
don't
have
any
extra
on
this
one.
So
this
one's
also
good
to
go,
and
also
just
a
point
of
note,
sorry
that
event,
accessibility,
metric
will
also
be
added
to
the
dei
event
badging
program
as
well.
A
So
we
will
be
asking
questions
about
event:
accessibility,
on
applicants
as
soon
as
this
release
gets
released
and
then
we'll
make
the
changes
to
the
dei
badging.
So
it
will
be
a
little
harder
for
people.
You
know
to
get
that
gold
badge
because
we're
going
to
be
asking
them
quite
a
lot
and
in
fact
this
is
actually
going
to
be
a
whole
new
section,
we're
adding
to
the
dei
badging.
A
So
yeah,
we're
really
gonna
make
them
work
for
it
a
little
bit
more
because
there's
quite
a
lot
in
this
metric
that
we're
gonna
ask
them
about
so
yeah.
Just
the
point
of
reference.
B
A
Yeah
yeah,
we
have
been
getting
quite
a
few
that
are
in
person
or
that
have
a
hybrid.
You
know
they
have
both
components
so
yeah,
it's
interesting
to
see
them
come
back.
B
Cool,
I
don't
see
any
other
major
comments
or
feedback
on
the
issues,
and
that
brings
us
to
the
end
of
the
agenda
today,
so
we
still
have
seven
minutes
left
on
the
clock.
I
don't
know
if
anyone
has
anything
they'd
like
to
bring
up
or
or
topics
I'd
like
to
bring
up
for
the
group
or
if
we
want
to
wrap
up
a
little
bit
early
today,.