►
From YouTube: CHAOSS DEI Working Group 3-2-22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
B
So
we
can
start
the
meeting
for
today
welcome
everybody.
I
hope
you
have
you
had
a
good
week
today
we
are,
we
are
starting
our
dni
working
group
meeting.
Please
feel
free.
Everyone
here
feel
free
to
add
your
name
and
the
attendees
and
how
you're
feeling
today
hi
hi
son
and
I'm.
C
C
B
I
was
just
saying
that
we
are
starting
the
meeting
and
I
see
that
you
have
added
your
name
already
here.
The
first
item
on
the
agenda
to
discuss
today
is
for
elizabeth
to
add
facilitation
notes
to
the
community
handbook
document.
D
I
have
a
small
update,
so
actually
a
question
and
a
comment,
so
my
question
to
christy
is:
were
you
able
to
access
that
document?
Was
it
helpful?
Do
we
need
to
make
it
more
clear?
No,
it
was
good
for
the
for
the
facilitation.
D
D
Okay,
perfect
and
then
my
comment
is
that
I
am
not
sure
how
to
actually
add
something
to
the
community
handbook.
I
tried
to
add:
I
merged
in
an
old
pr
from
sean
sean
had
written
up
a
nice
doc
about
for
newcomers
and.
E
D
C
F
C
D
Hopefully,
just
cut
reaches
out
because
I
added
it
actually
adds
an
actual
section
for
newcomers,
a
heading
section
and
a
dock,
so
yeah
it'll
be
great.
If
we
have
that
documented,
it
kind
of
goes
back
to
the
whole.
You
know
handing
off
of
projects
like
if
george
is
the
only
one
who
knows
how
it
works
and
then
he's
not
around
then
like
what
happens,
then
you
know
like
so
hopefully
joshua.
D
That
process
for
us
and
in
future
you
know,
google
summer
code
projects
like
stuff
is
documented,
so
we
know
how
to
continue
the
work
forward
after
they're
gone
so
working
on
it.
A
Yeah
I
mean
listening
to
you
talk.
We
probably
need
at
least
you
elizabeth
probably
need
like
a
master
list
of
like
our
zoom
login,
our
getbook
login.
If
we
go
with
discourse
like
a
discourse
login,
our.
D
Yeah,
that's
kept
in
lastpass
right
now,
so
but
yeah
you're
right,
like
that
stuff
needs
to
be
documented
in
an
internal
place.
E
A
B
D
Get
that
so
it
kind
of
goes
back
to
that
idea
of
having
like
an
internal
wiki
or
an
internal
community
handbook,
that's
private,
but
public-ish
to
a
group
of
a
you
know,
a
fairly
substantial
group
of
of
chaos,
kind
of
core
members.
I
guess.
D
D
A
If
we
get
rid
of
the
mail
list,
then
that's
a
moot
point
there.
What
did
you
merge
in
here?
I'm
not
seeing
any
research.
C
D
A
pull
request
from
sean
from
like
july
of
last
year,
so
thanks
sean
for
doing
that,
but
never
mind.
Yeah.
C
D
B
Okay,
great
so
the
next
item
here
on
the
agenda,
we
have
elizabeth
to
delete
the
old
rebel.
I
think.
D
Well,
I
didn't
because
it's
all
still
in
the
github
history,
so
we
can
just.
D
B
G
Hey,
I
am
here-
I
completely
missed
this
after
two
weeks-
really,
sorry
about
that.
Just
I
got
a
little
overloaded,
so
I
think
this
is
still
valuable
to
pursue,
but
not
necessarily
with
google
server
code
notice.
The
deadline's
been
met.
A
C
C
A
G
What's
that
I
think
2020
we
did
okay,
it
was
really
beneficial
to
the
chaos
project
and
hopefully
the
people
who
were
involved
as
mentors
and
mentees.
So
it
might
be
good
to
do
that
again.
C
B
B
A
H
A
A
C
C
I
C
I
Say
that
again,
yeah
who
is
taking
this
up
on
the
season
of
dogs
who's
going
to.
I
I
D
A
C
A
C
Yeah,
I'm
just
I'm
looking
at
do
we
have
do
you
know
if
we
have
a
community
collective
or
an
open
collective
account
for
chaos?
Okay,
I'll
need
that
information.
Okay,
because.
A
C
C
We
had
to
open
that
because
of
the
google
programs
yeah
and
the
project
will
get
between
each
project
will
get
between
five
and
fifteen
thousand
us
dollars,
and
we
get
forty
percent
after
hiring
the
writer,
okay
and
sixty
percent
after
completion,
which
can
go
through
the
end
of
this
year.
Okay,
cool.
E
C
Yeah,
I
can't
see
I'm
sorry
for
chaos,
but
I
don't.
I
think
everything
that
I
would
need
is
probably
behind
the
sign-in,
but
I'm
checking
probably.
C
C
I
mean
they
might
just
like
yeah
I'll
go
through
it
I'll
go
through
it
and
see
if,
if
I
don't
need
to
log
in,
but
my
guess
is,
there's
probably
something
behind
the
paywall
that
I
would
need,
but
I'll
start
first,
okay,.
C
B
B
B
B
Okay,
so
it
looks
like
the
the
main
idea
to
conduct
this.
These
campaigns
are
to
look
at
what
resources
we
need
to
make
our
work
better.
A
So
I
think
from
my
understanding
is,
he
wants
to
run
a
series
of
interviews
or
something
similar
that
would
talk
to
event,
organizers
and
really
kind
of
help
unders.
So
we
understand
what
the
dei
concerns
are
within
their
own
with
within
their
own
events,
and
I'm
wondering
you
know,
maybe
we
could
submit
to
a
conference
coming
up
where
we
would
do
like
a
focus
group.
You
know
or
invite
event
organizers.
A
G
I've
seen
people
have
a
lot
of
success
with
those,
and
I
I've
been
in
really
good
sessions
like
that.
I
think
it's
important
that
if
we
do
that,
we
need
to
publicize
it
like
way
ahead
of
time
and
say
we're
doing
this
so
that
we
can
ensure
that
people
will.
The
relevant
people
will
show
up
basically
yep.
A
A
So
then
the
question
would
be:
when
would
be
the
next,
maybe
like
chaos
con
oss
eu.
That
could
be
something
that
would
be
submitted
there,
oss
eu's
in
dublin.
In
the
fall
I
mean.
I
don't
know
that
this
is
a
huge
pressing
issue,
just
in
part
of
we'll
talk
about.
Maybe
why
a
little
bit
later
with
technical
debt,
but.
D
D
Yeah,
so
I
think
the
last
comment
we
left-
we
talked
about
it
a
couple
weeks
ago
and
we
decided
at
the
time
to
kind
of
hold
this,
but
the
timing
with
osseu
would
work
or
kscon
would
work
based
on
kind
of
what
our
discussion
was
last
time.
D
Yeah,
it
would
just
be
in
alignment
with
what
our
previous
conversations
have
been
about.
You
know,
because
we
do
have
such
a
cue
already,
and
we
also
have
the
backlog
of
old
metrics
to
review
now.
So
if
we
were
to
do
something
sooner
than
later,
it
would
just
give
us
ourselves
more
work.
D
More
verdict
have
plenty
of
that
already
so
yeah.
B
I
can
also
help
out
here
to
contact
people
that
I
know
that
work
in
the
event
organization,
so.
A
A
Okay
and
honestly
too,
I
mean,
if
we
have
this
set
up
as
a
birds
of
a
feather
session
like
have
a
template
for
questions
that
we
would
ask.
It
would
be
something
that
would
probably
be
easy
enough
to
run
at
you
know,
whatever
mozfest
or
all
things
open
or
any
other
events
that
aren't
necessarily
lf
related
events.
D
E
D
D
A
A
A
A
D
B
D
There
you
go
that's
what
the
dream's
about.
What
was
that
thing
so
that
one,
I
I
don't
know
if
we
put
it
under
completed
yet,
probably
not
because
kevin's
still
doing
his
thing
with
it,
but
I
don't
think
we
need
to
actually
take
any.
Oh.
D
A
A
So
these
are
the
metrics
that
are
released
by
the
the
dei
working
group
and
so
then
kevin
who
really
kind
of
leads
the
effort
to
assemble
all
the
metrics
from
the
different
workings.
He.
He
then
has
just
an
issue.
He
can
go,
look
at
and
see.
Okay,
these
are
the
two
metrics
he
doesn't
have
to
like
dig
through
the
entire
repository
to
figure
it
out.
So
that's
all
that
this
is.
A
Yeah
so
then
he
there's
a
whole
process
by
which
he
kind
of
pulls
the
new
markdown
file
that
was
created
for
that
metric
and
then
gets
it
into
a
pdf
and
gets
it
onto
the
website.
We,
we
have
a
somewhat
automated
process
to
get
parts
of
that
done
so,
and
he
added
this
issue
because,
honestly,
like
a
year
and
a
half
or
two
years
ago,
we
didn't
have
this,
and
I
think
he
spent
like
hours
just
digging
through
repositories,
just
trying
to
figure
out
what
were
the
new
metrics.
It
was
a
real.
A
B
A
A
This
is,
this
is
an
issue
that
I
think
is
ongoing
too.
This
is
just
for
us
to
review
the
old
metrics
so
essentially.
A
In
2022,
we
want
to
do
two
things
in
all
of
our
working
groups.
One
is
that's
fine
as
we
release
new
metrics,
but
one
of
our
concerns-
and
this
is
an
item
on
the
agenda
a
little
bit
later,
but
I
can
talk
about
it
now.
Is
that
as
we
continue
to
release
new
metrics,
some
of
our
metrics
from
three
or
four
years
ago
also
need
to
be
revisited
that
you
know
what
we
wrote
four
years
ago,
we've
learned
a
lot
and
we
write
slightly
differently
after
four
years.
A
I
was
thinking
today
on
when
I
was
taking
a
walk.
I
think
it
would
be
like
writing
a
paper
or
the
first
half
of
the
paper
was
written
like
four
years
ago,
and
you
just
keep
writing
the
back
half
of
the
paper
without
ever
going
back
to
the
beginning
like,
and
then
it
becomes
discombobulated
and
yeah.
E
A
Metrics
and
everybody
agrees-
and
so
elizabeth
pointed
out
in
the
community
call
yesterday
that
by
not
looking
at
our
old
metrics,
we're
really
inheriting
quite
a
bit
of
technical
debt
like
we
just
keep
piling
stuff
on
to
the
pile
without
going
back
and
revisiting.
So
I
think
the
hope
is
is
that
we
can
really
review
those
metrics
elizabeth-
and
I
maybe
I
can
put
this
in
here.
A
We're
going
to
be
looking
at
each
of
the
working
groups
to
take
a
look
at
this
list
of
metrics
here
that
have
been
released
and
we
may
look
at
some
of
them,
for
example,
sponsorship.
I'm
totally
making
that
up,
but
we
may
look
at
sponsorship
and
be
like
that
one's
all
that
one
actually
looks
pretty
good.
It
probably
doesn't
need
to
be
re-reviewed
right
now.
D
And
matt,
I
don't
know
if
you
assumed
the
same
thing,
because
we
haven't
chatted
about
it
since
yesterday,
but
I
was
kind
of
I'm
willing
to
like
actually
go
in
and
make
those
suggested
changes
prior
to
bringing
it
to
the
working
group,
since
some
of
them
are
pretty
straightforward
as
far
as
adding
making
sure
the
disclaimers
are
in
there
etc.
So,
like
I
don't
mind
actually
starting
that
work
on
those
individual.
E
D
A
I
think
too,
I
don't
know
what
your
thoughts
are,
but
you
know
normally
we
like
to
have
our
prs
reviewed.
But
honestly,
if
it's
adding
a
disclaimer,
I
I'm
kind
of
okay
with
you
just
committing.
D
A
A
A
Because,
then,
to
your
point,
then,
then
we'd
have
all
the
headers
in
place.
We
wouldn't
have
to
like
copy
and
paste
it
out
of
an
old
metric
we'd
have
all
the
headers
in
place.
We'd
have
all
the
disclaimers
in
place
like
just
through
a
couple
of
keystrokes
would
be
a
good
idea.
A
A
A
A
A
B
B
D
D
If
we
can
so
please
fill
that
out,
but
a
lot
of
the
work
that's
been
going
on
right
now
is
between
matt
and
enoch,
who
have
been
working
tirelessly
to
improve
the
documentation
around
the
bhaji
badging,
the
packaging,
the.
D
I
Yeah
I
thought
mike
was
going
to
talk
about
that.
I
am
we
have
made
some.
I
could
call
it
a
road
map,
I'm
done.
I
don't
know
whether
the
document
was
actually
shared.
Yeah.
I
Oh
sure
so
we
were,
we
had
made
a
document
that
links
to
very
many
other
documents,
and
that
document
is
actually
having
oh
yeah
sure
there.
It
is
so
like
we,
we
had
shared
last
time,
the
things
we
wanted
to
improve
but
number
one,
most
importantly
and
they're,
listed
in
priority
from
the
start
to
the
bottom
down
here.
But
as
you
go
down
the
list,
you
realize
some
of
the
some
of
the
issues
support
the
other
and
doing
one
will
actually
integrate
into
starting
to
work
on
the
other.
I
So
I
and
mark
are
and
any
other
person
who
may
want
to
join
in
always
meet
on
mondays
to
meet
or
is
in
the
evening,
but
for
mata
and
very
many
others
of
you
it's
in
the
morning
where
we
actually
share
our
our
progress
for
whatever
we've
been
tasked
to
do
within
the
week.
So
we
hope
by
next
meeting
we
shall
have
the
documentation
already
there
and
we
would
be
going
on
to
the
other
items
down
the
list.
I
So,
as
you
see
those
links
there
on
every
task
connect
to
a
certain
document
where
we
shall
be
where
we
shall
be
documenting
everything
and
for
public
consumption
so
that
if
anybody
wants
to
refer
to
them,
they
can
always
follow
up
easily
without
having
a
lot
of
photos
right
now.
There
is
actually
nothing
in
some
of
them
and
but
as
we
go
on,
they'll
be
populated
with
some
information,
but
maybe
then
we
could
find
better
ways
of
tracking
some
of
the
information
that
goes
down
there.
A
This
is
great
thanks,
enoch
and
thanks
for
that,
a
couple
questions
one:
would
it
would
it
make
sense
to
produce
another
project
for
the
badging
in
the
dei
repository.
A
I
A
I
I
Sure,
yeah
yeah-
I
get
that
now.
I
I
had
that
in
mind.
Actually,
the
previous
time
I
was
meeting
with
mart,
I
was
thinking
of
creating
a
project
board,
writing
bridget
hub
and
we
linked
it
to
our
repository,
but.
I
At
the
moment,
since
I'm
we're
not
actually
yet
into,
I
think
that
can
come
in
when
we
are
trying
to
when
we
have
reached
the
execution
of
the
other
items.
But
for
now,
since
we
are
only
working
on
the
documentation,
it
was
something
that
I
actually
didn't
bring
up
too
much
because
I
was
like.
I
think
this
is
too
early
to
bring
up.
But
it's.
I
Thinking
of
to
bring
up
because
actually
it's
easier
to
track
from
a
project
board
and
also
assign
and
link
several
other
things
that.
I
Getting
a
lot
of
documents.
I
A
I
I
Yeah,
I
think,
and
elizabeth
helped
me
out
last
time
was
like
marzi
and
matt
g
yep
yeah,
but
I
was
talking
to
math
c
that
I
think
that's
a
good
idea
that
we
can
have
those
that
this
project
broken
down
into
tasks
and
actually
labels
assigned
to
them
so
that
we
know
how
to
filter
out
the
particular
tasks.
So
I
think
it's
a
it's
a
valid
thing.
I
Yeah
sure
I
think
we
can
bring
it
up
and
see
how
we
organize
it:
okay,
jump
on
it
anytime,
anytime,
we're
ready
to
do
something,
but.
I
Oh,
I'm
sorry
to
interrupt.
I
remember
was
I
brought
this
up
in
the
in
the
budgeting
boat
the
meeting
before
this
one,
and
I
was
trying
to
get
clarity
on
where
actually
this
sorry
about
that.
Well,
actually,
this
should
be
put,
but
elizabeth
and
mark
were
guided
us
on
that
time.
We
can
have
the
deeper
discussions
about
the
badging
updates
and
particularly
the
boat
in
the
other
meeting.
Then
we
can
just
come
here
to
give
just
an
overview
of
everything
so
that
we
do
not.
I
We
do
not
have
two
meetings
for
one
thing,
so
that
was
something
I
just
thought
that
if
we
just
came
here
through
a
lot
of
information,
maybe
we're
like
for
those
who
want
to
know
more.
You
can
come
to
the
meeting
before
this
one
yeah,
but
that's
what
I
wanted
to
put
out.
A
A
D
No,
the
badging
bot
stuff
will
go
with
g-stock.
We
have
a
separate
bot,
that's
a
slack
bot.
A
A
I
do
recommend
that
everybody-
I
don't
have
the
links
in
here.
Maybe
somebody
could
drop
the
links
to
the
pr's
in
there,
but
that
if
you
were
a
contributor
to
one
of
these
metrics-
and
you
don't
see
your
name
listed
in
the
contributors
down
at
the
bottom
of
the
metrics-
just
feel
free
to
add
a
pr
to
include
yourself
as
a
contributor-
no
problem
there.
A
So
I
think
honestly,
I
think
we're
all
good
just
with
respect
to
the
metrics
this
round,
so
just
just
two
yep
and
then
the
technical
debt
concerns
is
something
we
talked
about
earlier,
which
is
the
continued
release
of
metrics
without
the
reevaluation
of
prior
metrics,
but
I
think
we're
building
a
process
to
to
address
that.
D
A
B
Okay,
so
do
you
want
to
maybe
go
quickly
over
the
website
update.
A
Yeah,
I
can
just
say
it
really
quickly.
I
think
a
lot
of
you
know
we're
reworking
the
chaos
website
kind
of
starting
right
about
now,
probably
just
to
talk
about
like
what
are
the
elements
that
we
want.
We
started
talking
about,
say
like
a
a
forum
on
the
website
and
knowledge
bases
like
we've
been
starting
to
talk
about
kind
of
one
of
the
things
that
we
would
like
to
do,
there's
going
to
be
work
on
updating
the
website.
A
That's
occurring
in
the
summer
may
june
june
july
kind
of
thing,
and
I
think
it's
part
of
that
too.
That's
relevant
to
the
dei
working
group.
We
are
really
going
to
think
about
accessibility
on
the
website
and
we
do
actually
have
funds
to
support
people
who
do
accessibility,
website,
accessibility,
work.
I
think
georgia
boolean,
I
think
her
her
team
does
website
accessibility,
work,
christy,
sean
elizabeth,
you
all
know
georgia,
so
we
may
be
working
with
them
to
kind
of
work
with
us
on
accessibility
concerns.
D
And
I
added
that
second
bullet,
because
I
was
talking
to
kevin
yesterday
about
the
knowledge
based
stuff
and
we
got
on
the
topic
of
accessibility
and
he
he's
pretty
certain
that
our
website,
like
whatever
modules
we're
using
for
for
wordpress
those,
have
already
kind
of
passed.
A
first
test.