►
From YouTube: CHAOSS DEI Working Group 4/27/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
On
our
agenda
today
is
just
google's
season
of
docs
first,
so,
for
we
have
the
deadline
of
may
4th
and
matt,
I
think
you
did
take
care.
I
think
you
took
care
of
the
whole
application
process
for
this
one,
so
we're
ready
to
handle
large
volumes
should
those
occur.
B
Yeah
one
question
that
came
up
in
slack:
is
there
no
application
like
portal
at
google
sean?
Do
you
know
this?
It's
a
good
question.
I
the
way
that
you
know
yeah
season
of
code
has
an
application
portal
and
then
you
apply.
B
B
D
B
C
A
B
A
You
know
I
I
actually
just
apply
for
that
by
may.
Something
may
12th,
I
believe,
is
the
deadline,
but
I'm
going
to
do
it
this
week
because
well,
you
can't
do
it
until
we.
A
D
B
C
D
B
D
Okay-
and
maybe
we
can
put
that
in
the
newsletter
in
the
community
meeting,
but
I
didn't
know
if,
like
I
mean.
A
D
A
A
Yeah
we
need
to
set
up
the
the
cold,
though
I
need
to
do
the
open,
collective
part
by
may
12th,
and
then
we
hire
the
mate
we
have.
We
have
to
hire
the
technical
person
by
may
16th
and
after
we've
completed
that
one,
we
email
an
email
address
I'll
see.
The
first
email
will
be
sent
once
tackle,
writer's
been
hired
starting
on
june
9th,
and
we
must
submit
our
expense
for
this
email
by
email
june
23rd
and
then
the
second
one
has
to
be
cemented
by
june
21st
or
december
21st.
A
B
B
A
A
B
A
B
A
D
A
B
A
B
A
A
B
B
C
A
Yeah,
okay,
yeah
very.
C
A
And
I
I
think,
oh,
I
think
google
season
in
boxes
widely.
I
mean
sorry,
google
season,
google
summer
of
code
is
really
well
established
and
well
known,
and
lots
and
lots
of
students
that
like
pass
it
on
at
universities
and
outreach,
is
similar.
In
terms
of
its,
I
mean
I'll
reach
into
something
with
publicity
this
year.
That
really
made
things
much
bigger,
but
I
think
season
of
docs
is
maybe
a
less
well
understood
or
recognized
program
to
guess.
A
All
right,
so
I
think
we
have
that
item
cover
project,
badging
meetings,
elizabeth.
D
I
just
wanted
to
mention
so
at
the
dei
event
badging
meeting
we
had
this
morning.
We
were
hoping
to
start
so
we're
to
be
alternating.
It's
going
to
turn
into
a
weekly
meeting,
but
we'll
alternate
project
event,
project
event,
we're
looking
for
a
time
that
does
not
conflict
with
anything
else
at
chaos,
so
that
meeting
will
change,
but
we're
hoping
to
kind
of
kick
these
off
after
the
event
appreciation
event
after
the
badging
appreciation
event
in
on
june
16th.
D
D
A
D
A
task
to
get
some
blocks
and
then
we'll
see
what
kind
of
works
with
the
group,
but
right
now
that
meeting
conflicts
with
the
asia
pacific
meeting
on
the
off
weeks.
So.
A
Whatever
I
mean
find
out
what
works
for
the
people
who
are
most
active
on
that
and
I
would
say,
directed
from
there
around
the
other
chaos
meetings,
if
9am
would
work
every
other
every
wednesday,
then
I
think
that's
open.
D
Matt
g
does
that
kind
of
align
with
like
what
your
take
is
on
the
all
in
stuff
and
like?
What's
what
do
you
feel
about
that.
D
D
B
Yeah
that
does
work
for
me
and
with
the
semester
ending
that'll
be
good,
because
I
I
did
have
a
meeting
that
would
appear
at
nine
o'clock
before
this
one
often,
but
that
won't
be
the
case
from
this
point
forward.
Nine
o'clock.
D
Okay,
let
me
just
jot
that
down
and
then
again
this
won't
start
until
the
end
of
june,
so
yeah.
E
That's
perfect:
okay,
cool.
C
A
That
was
all
all
right,
and
this
this
next
item
was
left
from
the
last
time.
Do
do
we
want
to
spend
10
10-15
minutes
on
this
or
do
folks
feel
like
you
got
finished
with
it
last
time.
B
B
C
All
right,
open
issues.
A
Don't
know
if
we
have
any,
but
but
we
do
have
some-
we
have
a
several
opened
by
matt
german
pray
eight
days
ago.
Are
these
ones
that
you
want
to
review.
B
Might
be
useful
if
we
could
have
maybe
some
volunteers,
just
somebody
who
isn't
there,
the
originator
of
the
issue
kind
of
make
some
updates
or
just
kind
of
attend
to
the
updates
so
like
when
elizabeth
puts
hers
into
evolution
like
I
could
be
the
person
you
know
what
I
mean.
We
just
have
two
sets
of
of
people
taking
a
look
at
it,
yeah
two
sets
of
eyes
and
then
for
that
second
person.
B
If
there's
there
is
a
fundamental
change,
you
know
like
the
objective
needs
to
be
written
or
something
like
that
yeah
then
maybe
you
bring
it
back
to
the
committee
or
to
the
working
group
and
say:
okay,
folks,
let's
all
take
a
take
a
run
at
this.
C
B
A
Yeah,
you
could
go
in
like
event:
demographics,
family
friendliness,
code
of
conduct
so
like.
If
I
went
into
family
friendliness-
and
I
I
wanted
to
okay
I'll
say
this
one-
I
would
click
assign
yourself
and
then
that
person
would
be
responsible.
A
So
what
is
the
tang
on
there?
I
forgot
like
revising
metric.
B
E
Just
a
question
for
the
review
process:
are
we
looking
at
just
the
revisiting
metrics
or
some
of
the
older
ideas,
or
was
it
a
specific
subset
of
metrics?
We
were
looking
at.
B
A
So
I
think
the
answer
it.
The
idea
is
that
there
are
individuals
who
are
reviewing
different
working
group
metrics
for
items
like
those
that
are
in
in
here
and
then
creating
issues
for
them,
follow
and
then
including
this
checklist
in
the
issue,
and
you
could
tag
all
of
the
metrics.
If
you
you
know
in
a
working
group,
if
you
think
they
all
require
some
kind
of
minor
revision
or
major
revision
or
you
could,
as
matt's
done
here,
identify
the
ones
that
actually
are
required
to.
A
B
Yeah
we
have,
we
have
actually
assigned
people
to
each
working
group.
So,
like
I'm,
taking
a
look
at
the
doing
a
first
pass
on
the
dei
metrics
elizabeth
was
doing
a
first
pass
on
the
evolution,
metrics
sean.
I
think
you
were
taking
a
first
so
so
the
original
issue
should
come
from
really
just
five
people,
so
that
that's
our
first
hope
so,
like
I
think
elizabeth
you
have
done
this
in
the
evolution
working
group,
and
so
only
only
once
the
issue
is
created.
A
B
A
E
A
Fact
we
could
put
this
on
our
chaos
organization,
page
with
a
list
of
the
working
groups
where
people
could
be
looking
for
issues.
Tagged
like
this
or
put.
B
A
B
B
C
A
E
A
A
A
It's
cool
I
hit
refresh
and
this
all
the
work
was
completed.
I
maybe
we
can
do
that
with
other
things,
all
right.
The
next
topic
that
again,
I
pulled
from
last
week-
and
I
just
kind
of
called
people
who
were
here
last
week-
are
there
further
points
of
discussion
regarding
our
code
of
conduct.
I
know
part
of
our
diversity.
Equity
inclusion,
advisory
board
had
a
discussion
about
code
of
conduct
earlier
this
week.
A
B
D
A
A
I
think
I
think
it's
about
being
able
to
have
a
remediation
for
violations
of
acceptable
behavior.
On
behalf
you
know,
and
at
the
same
time
representing
chaos
in
a
public
venue
that.
B
D
B
To
them
yeah
another
an
appointed
representative
of
the
chaos
project,
so
we
may
want
to
take
a
look
at
this.
Maybe
we
could
give
an
action
item
and
maybe
we
could
talk
about
it
a
little
bit
next
time,
all
right.
Everybody.
D
C
B
B
E
C
E
E
To
look
at
for
how
they've
approached
it,
but
I
was
also
just
trying
to
get
more
context.
I
missed
is
the
question
just
a
review
of
our
current
code
of
conduct,
or
are
there
specific
things
we're
looking
at
more
closely
related
to
it.
B
Yeah,
the
the
recommendation
that
kind
of
came
was
essentially
to
ensure
that
we
don't
have
two
codes
of
conduct
like
one
for
events
and
one
for
project
and
that
we
don't
do
we
we
have
in
the
past
so
and
just
to
ensure
that
our
single
code
of
conduct
is
very,
very
clear
as
to
what
is
covered
by
our
code
of
conduct.
So,
like
chaos,
meetups
chaos
cons
like
it's
just
everything
that
goes
in
here,
because
the
argument
is,
is
that
you
know
bad
behavior
is
bad
behavior.
E
Have
a
comment
that
makes
sense
so
I'll
add
links
to
the
fedora
and
sustain
oss,
oh
code
x
and
the
dock.
But
one
thing
I
think
is
just
to
highlight
that
I
think
was
was
really
nice,
that
both
of
them
also
have
a
clarifying
clarifying
notes
and
statements
or
an
faq
that
go
along
with
it
so
kind
of
like
with
a
legal
document
or
a
license.
E
A
B
A
Think
so
the
yeah,
I
think
it's
a
little
a
little
bit
off
because,
what's
what's,
I
think
missing
is
the
explicit
inclusion
of
contributors.
You
know.
Basically,
anybody
participating
in
the
project
is
expected
to
follow
our
code
of
conduct
and
that's
the
part
that
I
think
is
not
very
clear
like
if
you're
just
when
you're
participating
with
chaos,
the
code
of
conduct
is
something
you
need
to
follow
period.
A
I
I
do
think
with
the
project
maintainers,
I
think
failure
to
enforce.
A
It
would
be
wrong
on
my
part,
to
not
request
an
enforcement
action
when
one
obviously
should
be
requested
or
filed,
and
I
shouldn't
rely
on.
I
shouldn't
sit
back
and
not
take
responsibility
for
engaging
this
process.
I
think
that's
what
that
project.
Maintainer
piece
is
where
I
think,
there's
enough
narrative
history
in
open
source,
where
the
maintainer
had
a
history
of
simply
taking.
A
No
action
when
there
were
violations
and
then
that
that
really
becomes
a
culture
in
the
project
which
is
not
the
culture
we
want
so
like
I'm
not
against
the
maintainer
language,
but
I
also
think
with,
but
I
think
we're
missing
the
I
think
we're
missing
clarity.
Around
contributors,
like
all
participants,
are
subject
to
the
code
of
conduct.
A
B
A
Yeah,
oh,
so
that's
a
good
question.
Is
it
enforcement,
like
I,
I
think
yeah
this
might
not
belong
here.
This
might
be
an
expectation
up
above,
but
I
just
think
it's
saying:
there's
a
high.
There
is
an
expectation
that,
if
you're
a
maintainer
of
one
of
our
repos
that
you
will
you
know,
make
a
you
know,
file
a
complaint.
A
B
Maybe
what
I
can
do
is
I'll
move
this
to
a
google
doc.
Okay,
so
that.
A
Yep
just
kind
of
think
through
the
language
of
this
so
and
I
think
it
was.
It
was
basically
these
three
sections
that
were
the
the
ones
that
were
we
discussed.
Specifically,
that's
yeah,
that's
my
feeling,
but.
A
All
right,
so
I
think
so.
The
plan
is
basically
the
plan
plan
make
google
doc
and
edit
during
meeting
on
may
3rd.
First
to
sunday,
4th.
A
Yep
all
right
did
you
just
create
that
doc,
matt
yeah,
okay
and
then
I
just
wanted
to.
I
realized,
but
we
didn't
say
anything
about
it
ahead
of
time,
but
chaos
partnered
with
risa,
which
is
a
research
software
association
and
the
organizations
that
are
focused
on
research,
software
engineering
as
a
role
in
discipline
in
academic
settings.
A
On
a
workshop
in
lorenz
in
the
netherlands,
whose
his
subject
was
re-centering
open
source,
scientific
software,
around
diversity,
equity
and
inclusion,
and
it
was
a
four-day
workshop
with
25,
local
and
35
remote
participants,
there
were
stills
going
through
the
process
of
trying
to
understand
why,
but
our
remote,
our
virtual
participants,
felt
very
engaged.
A
We
got
a
lot
of
really
positive
feedback
on
how
engaged
the
remote
participants
felt
and
we
had
very
consistent.
Like
engagement.
People
are
online
the
whole
day
every
day
and
I
think,
what's
notable
is
after
after
four
days
of
discussing
this,
the
really,
I
think,
a
pretty
deep
understanding
of
what
we
need.
A
The
center
of
organizing
open
source
scientific
projects
in
this
case
and
making
that
part
of
the
mission
of
the
research
software
engineering
role
as
it's
evolving,
is
really
about
recognizing
the
significance
and
centrality
of
diversity
to
community
and
then
centering
the
whole
project
around,
not
just
the
code
and
one
of
the
remote
participants
summarized
this
is,
I
think,
one
of
the
things
that
we
do
in
scientific
open
source
is
we
sort
of
fetishize
the
software
that
that
this
focus
on
code
as
law
is
not
really
how
open
source
is
successful
and
some
of
the
most
successful
open
source
projects
do
have
their
community
at
the
center,
and
so
the
actions
moving
forward
will
hopefully
include
inclusion
of
some
new
chaos.
A
A
Ultimately
I
mean
it
ended
up,
resonating
well
and
being
well
understood
by
the
group
and
it's
the
first
large
meeting
I've
been
in
where
there
was
a
lot
of
shared
clarity
around
what
motivates
that.
A
A
E
A
All
right
so
and
then
elizabeth,
she
code,
africa,
you're
not
as
time
constrained
as
you
were
in
the
general
meeting.
So.
D
Yeah
things
are
going
really
really
well
precious,
a
and
midi
are
powering
through.
They
already
have
a
working
demo
for
us.
We
are
meeting.
I
know
we
are
meeting
next
week.
When
I
say
we
I
mean
the
mentors
of
the
program.
So
myself
and
ruth
and
matt
c.
We
are
meeting
on
wednesday
and
they're
going
to
walk
through
their
demo
with
us,
they're
they're
doing
great,
and
it's
been
really
interesting
because
we
didn't
start
out
with
two
participants.
D
D
My
only
my
only
struggle
is
that
we
don't
have
all
the
documentation
ready
yet
for
them
to
point
to
so
the
things
that
they're
pointing
to
will
probably
change
as
we
go
through
our
google
season
of
docs
and
our
knowledge
base
stuff
that
we're
working
on
this
summer,
so
that
that
part
is
a
work
in
progress,
but
the
bot
will
be
ready
to
go
and
from
what
I
understand
it
can
also
be
a
little
interactive.
D
So
the
the
newcomer
person,
whoever
they
are,
can
have
a
kind
of
a
conversation
with
that
slackbot
and
ask
questions,
and
they
can.
The
bot
can
dig
a
little
deeper.
Oh.
C
D
As
far
as
I
understand,
I
don't
know
if
we're
there
yet
as
far
as
the
the
way
it's
the
demo
will
show
that
yet,
but
as
far
as
something
we
can
do
so
that's
great.
A
D
D
Yeah
so
they've
they've
been,
I
get
bits
and
pieces
in
the
in
the
she
there's
the
she
code,
africa
slack
channel
for
anybody
who
wants
okay,
bye
matt
for
anybody
who
wants
to
join
and
and
watch
their
progress,
but
yeah.
It's
it's
been
great
and
I'm
really
really
really
proud
of
them.
They're
just
they're
amazing.
So
that's
all.
D
There
is,
it
is,
I
think
we
just
called
it.
So
it's
in
the
chaos
org
it's
this
okay.