►
From YouTube: CHAOSS DEI Working Group 3-31-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Oh
officially,
like
you
know,
is
the
repo
name.
Repo
names
not
changed
yet,
though,
so
I've
been
going
through
and
changing
kind
of
things
that
I
can
change
that
don't
have
significant
cascading
effects.
You
know
so
like
the
repo
any
urls
won't
change
kind
of
like
how
evolution
is
still
growth,
maturity
and
decline.
Right
right,
you
know
a
lot
of
those
urls
are
still
in
that.
A
A
A
So
I
was,
I
had
to
kind
of
hastily
put
together
an
agenda.
I
was
actually
thinking
and
I'd
like
to
bring
this
up
in
all
working
groups
that
we
have
a
facilitator.
That
like
facilitates
like
four
meetings
in
a
row
or
something
like
that
consistency
yeah.
Sometimes
I
think
the
rotating
facilitator
ends
up
being
that
nobody
facilitates
is
how
it
turns
out
or
like
we
forget,
to
assign
a
facilitator
for
the
next
week
and
then,
as
a
result,
we
end
up
with
no
facilitator.
B
I
I
think
that's
I
mean
I
think
that
would
be
helpful
yeah.
Some
of
the
some
of
the
work
like,
I
think
I
don't
know
some
of
the
working
groups
that
I'm
in
like
evolution
and
risk,
there's
a
lot
of
coordination,
work
on
a
lot
of
moving
parts
and
so
I've
just
kind
of
maintained.
The
facilitator
role
in
those
groups
which.
B
I
think
that's
helpful
yeah.
I
mean
I
I'd
carter
done
it
for
a
while
for
last
year,
but
he
graduated
and
starting
new
jobs,
a
lot
of
work
and
stress
so
right.
D
I
kind
of
like
the
dni
badging
how
they
do
it.
They
do
rotate,
but
it's
like
the
very
first
thing
that
that
we
talk
about
is
like
who's
who's
facilitating
next
week,
like
it's
the
first
item
on
the
agenda
and
so
like,
I
think
just
maybe
adding
it
top
of
mind
if
that's
something
that
we
want
to
do,
but
in
that
group
it
it's,
you
know,
matt
can
talk
about
it,
obviously,
but
it
seems
to
be
like
kind
of
a
core
group
that
always
comes.
D
A
I
guess
I'm
trying
to
balance
too,
like
it
is
it's
this
shawn's
one
comment
like
some
sort
of
consistency
like
there
are.
There
are
times
when
I'm
like
show
up
in
a
working
group
and
it's
like
there's
no
agenda
set,
or
I
don't
know
it's
not
all
the
time
it
just
happens
every
now
and
then
so
I
was
just
thinking
about
this
on
my
run
and
maybe
if
we
just
commit
to
doing
a
facilitator
in
every
working
group
every
week,
that
would
your
point
elizabeth.
That
would
be
cool.
A
And
I'll
get
rid
of
that
facilitator
comments
all
right,
I'm
so
in
my
hastily
put
together
agenda.
So
yesterday
we
had
a
a
few
badging
applications,
meaning
like
I
don't
know
ten,
eight
something
like
that.
Oh
eleven,
I
went
the
wrong
direction,
so
we
had
11
badging
applications
that
all
stemmed
from,
I
think
kubecon
right,
they're.
All
kind
of
in
that.
A
Events,
so
do
you
feel,
like
you,
have
the
the
appropriate
number
of
reviewers
to
work
through
the
11.
E
I
reached
out
to
a
bunch
of
people.
Yesterday
I
sent
an
email
and
ccd
with
a
bunch
of
people,
and
I
asked
to
reach
out
to
other
people
one-on-one,
and
I
got
three
people
of
interest,
people
who
are
interested
and
that's
pretty
different,
and
I
and
I'm
reaching
out
to
them.
I
sent
them
out
a
thing
to
schedule:
a
review
orientation.
E
I
think
it's
still
important
to
have
an
orientation
to
make
sure
that
we're
all
in
the
same
place
with
the
reviewing,
but
once
that
once
they're
in
place,
I
think
we
would
only
be
maybe
one
or
two
more.
I
have
a
couple
of
friends
in
the
in
the
space
who
are
also
reaching
out
to
their
friends.
So,
okay.
E
A
All
right,
I
did
have
a
couple
comments
on
this
too,
so
that's
great
and
then
one
of
the
things
that
I
do
that
I
don't
know
how
we
kind
of
keep
keep
our
eyes
on
this.
But
one
of
my
concerns
is
that
from
the
11
applications
that
came
in,
they
came
from
one
person
on
all
of
these
events
and
as
the
11
reviews
occur,
there's
going
to
be
feedback.
A
That's
asked
for
so,
for
example,
I
asked
for
feedback
on
like
speaker
and
attendee
demographic
stuff,
so
like
in
my
event,
it's
actually
not
a
call
for
paper.
So
I
asked
questions
about
remember
last
week
when
he
said
how
do
you
support
diversity
in
the
committee
that
makes
selections
on
reaching
out
to
keynotes
right?
So
how
do
you
attend
to
that?
E
Well,
the
first
thing
to
mention
is
that
I
talk
to
the
person
in
the
comment
on
one
of
the
issues
as
well,
and
they
acknowledge
that
it's
going
to
be
slow
and
that
it's
going
to
take
a
while
for
on
both
sides.
I
think,
but
other
than
is
there
anything
we
can
there's
nothing.
We
can
really
do
for
them.
I
think
it's
on
their
side.
If
they
have
one
person
reviewing
all
of
it.
D
It
might
have
been
helpful
if
they
submitted,
maybe
one
or
two
just
to
see
how
the
process
went
and
then
the
feedback
that
you
know
we
give
to
them,
because
they're
gonna
have
to
go
back
and
change.
D
You
know
if
they
have
to
adjust
something
they're
going
to
have
to
adjust
it
across
the
board
based
on
the
feedback
from
one
event,
so
maybe
we
could
put
somewhere
that
you
know
if
if
there,
if
you,
if
you
organize
a
large
number
of
events,
we
we
recommend,
maybe
you
submit
one
as
a
as
a
kind
of
a
dry
run
or
like
a
pilot,
and
then
you
know
from
then
on
then
they're
then
they're
good.
D
D
E
Oh
sorry,
go
ahead.
Okay,.
F
So
I
think
if
they
like,
if
they
had
like
so
many
submissions,
they
should
probably
have
like
it
seem
on
their
sides
right
so
that
we
don't
know
of
so
we
could
like
ask
either,
as
it
seemed
that
it's
handling
like
the
11,
not
just
one
person,
so
just
be
sure.
So
if,
if
it's
a
team,
we
could,
if
it's
not
a
team,
rather
we
could
advise.
Okay,
you
could
make
this
a
team,
so
you
don't
get
all
the
work.
F
All
the
questions
get
to
answer
so
many
questions,
then,
if
they
do
not
follow
true,
we
could
advise
them.
They
keep
posting.
If
the
questions
are
similar,
I
couldn't
know
to
copy
paste
on
the
answers
right,
but
I
think
they
should
have
it
seen
if
they
were
either.
It
was
something
like
11..
That's
like
some
strength.
A
E
Free
to
include
them,
I
think,
it's
easier
to
say:
11
can
easily
become
40..
I
think
it's
a
really
good
way
to
put
it
and
just
reach
out
to
them
and
make
sure
that
they
have
the
have
the
team
to
handle
that
basically.
E
Do
an
action
item
to
reach
out
to
this
person?
Okay
and
then
I'll
I'll
run
it
by
a
couple.
Maybe
one
or
two
of
you
first
so
make
sure
I've
got
the
right
idea:
hey.
E
E
So
I
think
it
might
have
been
that
they
saw
that
it
was
going
well
for
a
few
of
them
and
decided
to
throw
all
of
them
at
the
program
at
once
tested
metal.
But
I
think
I
don't
know
I
don't
know
for
sure,
though,
so
I
can't,
I
guess,
I'm
just
speculating.
I
guess.
D
There
might
be
something
else
we
want
to
think
about
and
that's
if,
if
we
build
relationships
with
people
who
organize
a
large
number
of
events
like
this,
maybe
we
have
like
a
dedicated
team
of
reviewers
that
kind
of
handles
that
person's
events
in
total.
But
I'm
just
thinking
like
I
imagine
that
the
framework
that
they've
set
up
for
each
event
would
be
similar.
So
if
they're
getting
a
gold
on
one
they're,
probably
getting
a
gold
on
all
of
them.
D
So
I
wonder
if
there's
a
way
that
we
could
maybe
set
up
something
that's
a
little
more
scalable.
You
know
where
they
just
kind
of
submit
their
their
framework
almost
or
or
something
like
that
or
they
have
like
like.
We
have.
You
know
one
or
two
people
at
chaos.
That
knows
the
framework
and
knows
their
events
well
and
has
reviewed
them
in
the
past
and
can
kind
of
just
not
rubber
stamp
them.
A
Yeah
I
like
that,
even
when
you
were
talking,
I
was
thinking
like
like
one
of
the
check
boxes
is,
I
think
ruth
gave
a
thumbs
up
to
like
is
the
code
of
conduct
accessible
and
visible
on
the
web
right,
and
I
mean
like
like
matt
you
or
I
or
elizabeth,
we.
A
All
the
applications
and
just
check
that
box
right,
because
it's
the
same
for
all
of
them,
so
we
may
not
be
able
to
get
full
coverage
that
way.
Elizabeth,
you
know
what
I
mean
but
like,
like
probably
like.
80
percent
of
the
applications
are
the
same
and
check
one
and
it
can
kind
of
cascade
its
way
all
the
way
through.
D
And
really,
if
the
only
difference
between
the
events
is
the
content
and
then
maybe
we
just
have
you
know,
that's
the
piece
that
we
focus
on.
Is
the
content
accessible
and
you
know,
diversified
in
the
ways
that
we
had
recommended
and
the
speakers
and
that
kind
of
thing,
but
yeah
yeah.
A
But
also
to
me,
that
would
also
then
kind
of
it's
really
interesting
because,
like
when
you,
when
you
get
11
submissions
at
one
time,
it
opens
up
a
whole
new
series
of
questions
right
when
it's
just
one
or
two
it.
A
You
can
just
kind
of
work
through
it
with
an
individual,
because
then
the
other
thing
that
had
come
to
mind
is
if,
if
the
events,
I'm
guessing
you're
right,
elizabeth,
the
events
are
really
similar
from
one
to
two
to
eleven
that
if
I'm
doing
a
review
and
asking
for
something
particular
with
respect
to
attendee
demographics
or
speaker
demographics.
A
D
Maybe
there's
a
badge
that
we
want
to
give
to
to
like
an
umbrella,
organizer
or
something
that
they
can
use
for
their
events.
I
I
don't
know
how
I
feel
about
that,
because
then
they
could
kind
of
slip.
Something
in.
I
guess
that
isn't
up
to
snuff
but
like
if
you
have.
D
You
know
that,
like
the
lf
is
running
all
of
these
events,
for
instance,
so
like
we
give
them
a
badge
like
they
just
have
to
go
through
it
once
and
then
you
know,
assuming
that
they're
using
the
same
framework
and
repeating
their
process,
then
we
don't.
They
don't
have
to
keep
submitting
like
they're
kind
of
like
recognized
as
like
a
a
gold
organizer
and
so
like
all.
D
E
So,
as
someone
who
comes
from
a
background
of
cyber
security,
I
have
learned
to
trust
no
one
for
a
long
extended
period
of
time.
I
think
we
could
have
something
where
we
could.
We
could
say
this
is
built
under
this
code
of
conduct,
for
example,
is
built
under
the
saf
and
code
of
conduct,
or
something
like
that.
E
But,
like
I
still
think
this,
we
we
need
to
make
sure
that
stuff
is
there
if
nothing
else,
if
they're,
if
they're
up
to
snuff
and
they
they
have
a
good
process
for
getting
this
down,
and
it
looks
good,
then
we
can.
We
can
go
quickly
through
the
process
and
it
would
be
very
easy
something
maybe
like
they
don't
have
to
accept
the
result
for
it
to
be
badged
as
long
as
it
looks
good
or
something
like
that,
but
I
still
think
we
need
that
peer
review
to
be
to
exist,
no
matter
what.
B
A
Sorry,
but
I
put
a
comment
in
the
notes,
so
I
think
it
would.
I
think,
in
this
case,
for
the
time
being
kind
of
given
where
we're
at
right
now
with
all
these
submissions
coming
in,
but
it
might
be
worth
having
matt
or
me
or
elizabeth
or
ruth
or
whomever
people
who
are
on
the
call
to
look
across
the
reviews.
All
11
reviews
to
make
sure
that
the
requests
are
fairly.
A
Does
this
make
sense
like
we
would
have
a
spreadsheet?
That's
like
across
the
top
could
be
the
different
events.
You
know
each
column
is
an
event.
Yeah.
B
A
Is
all
of
the
like
badging
criteria
and
so
like
for
a
code
of
conduct
visible
like
that's,
I'm
guessing?
That
would
just
be
like
an
x
across
the
row
right
because
all
of
them
have
a
code
of
conduct.
That's
invisible,
hopefully,
the
spreadsheet
that
you're
imagining
in
your
head
is
the
same
one
that
I'm
imagining
in
my
head
and
then
like
the
the
row
for
speaker,
demographics,
we
could,
in
the
cell,
perhaps
put
the
comments
that
are
coming
from
the
reviewer.
A
A
G
Yes,
it
could
also
tell
you
as
a
reviewer
what
to
maybe
some
of
the
things
to
look
for
too
okay.
So
here's
my
experience
from
yesterday
was
for
berlin
buzzwords
I
was
I
was
looking
through
because
I
was
going
to
create
a
social
tile
and
I
sent
elizabeth
to
two
versions
and,
in
my
experience,
I'm
looking
through
the
repo
of
the
different
comments
that
the
two
reviewers
gave
that
particular
event
and
going.
G
G
B
A
The
two
areas
that
I
have
a
tendency
of
seeing
more
comments
on,
or
I
write
more
comments
on-
is
the
treatment
of
demographics,
of
speaker,
demographics
and
attendee
demographics,
and
what
we
ask
people
for
in
that
regard,
so
trying
to
normalize
that
a
little
bit
across
reviewers
would
probably
be
helpful.
A
G
Yeah
that
I
mean
that
that
was
wr
and
there
was
even
discussion
around
you
know
when
was
it
listed,
or
you
know
that
kind
of
thing
kind
of
timing
around
when
you
would
list
things
on
your
event,
side
or
right.
You
know
those
kinds
of
things,
and
I
found
that
really
helpful.
G
You
know
and-
and
then
I
I
think
I've
mentioned
earlier
this
week-
I
kind
of
feel
like
I
have
a
get
out
of
jail,
pretty
good
with
duncan
going
back
to
school.
G
And
you
know
so
I
mean
so
when
matt's
request
for
reviewers
came
along
okay,
you
know
I'm
gonna
end
elizabeth,
I'm
gonna
be
reaching
out
to
you
to
you
too,
but
you
know
I'm
like
okay,
I'm
I'm
you
know
want
to
get
more
involved
and
so
matt's
request
came
came
along.
I'm
like
okay
and
I
want
to
learn
github
a
lot
more.
So
here
we
go
right.
G
C
A
Matt,
so,
okay,
so
I
had
I'm
just
going
to
recap
this
a
little
bit
so
yay.
Thank
you.
Matt
for
reaching
out
to
additional
reviewers
sounds
like
you're
doing
pretty
well,
at
least
in
that
regard,
and
thank
you
for
doing
the
training
or
the
on,
like
the
onboarding
for
the
reviews
so
matt.
A
I
think,
if
see
the
top
of
page
two,
the
action
item
for
you
to
reach
out
to
see
if
there's
a
team
that
can
help
reviews
like
maybe
you
don't
need
to
do
that
right
away,
you
could
kind
of
wait
and
see
if
it
feels
like
the
issues
are
not
getting
responses
or
it
starts
feeling
like
it
might
be
overwhelming.
But
you
could
probably
just
add
something
in
there
to
the
issue.
E
That
makes
sense.
I
might
also
create
an
issue
in
the
repository
to
help
guide
people
who
are
wondering
what
to
do
too,
because
we've
had
that
also
brought
up
when
they
get
to.
E
Not
only
the
application,
but
the
reviewers
too
I'm
going
to
I'm
actually
planning,
I'm
I'm
going
to
be
drafting
an
email
to
like
send
it
to
all
the
reviewers,
invite
them
to
like
a
signal
group
most
likely
and
also
get
trying
to
get
things
coordinated
with
the
review
so
that
everybody's
on
the
same
page,
which
is
really
important
here.
Okay,.
E
A
G
One
of
the
things
that
occurred
to
me,
yeah,
just
one
small
one,
one
of
the
things
that
occurred
to
me
as
I
was
going
through
this
and
creating
this
social
trial.
G
Was
you
know,
and-
and
maybe
we
already
say
this-
because
I
didn't
go
back
to
the
to
the
to
the
reach.
Well,
I'm
missing
the
word,
but
the
reach
out
documentation,
but
in
creating
the
social
tiles
for
berlin
buzzwords
and
getting
the
gold
certificate
or
the
gold
badge
is
it
they
do
get
additional
visibility
or
advocacy
or
marketing
through
the
chaos
project.
G
You
know
whether
whether
that's
intended
or
or
not,
and
that's
one
of
the
benefits
of
getting
the
the
badge
is
not
only
do
they
get
to
reflect
that
you
know
they're
they're,
fostering
these
healthy
de
and
I
practices,
but
that
by
virtue
of
us
putting
you
know
making
this
known
through
social
as
an
example
that
they
get
additional
visibility.
G
A
F
Even
personally,
because
I
I
get
to
like
know
about
these
conferences
right
because
I've
never
heard
of
them
before
so
even
with
us
to
review
us
right-
I
I
got
to
know
about
like
a
couple
of
linux
foundation-
conferences
personally
so
yeah
it's.
I
really
really.
F
G
Yeah,
because
that
could
be
really
attractive
event,
organizers.
E
That's
a
hard
one,
because
we
don't
really
know
where
people
start
most
of
the
time.
The
question
is:
where
do
I
start,
so
I
mean
like
I'll
have
to
think
about
this
one
for
a
second
and
get
get
back
in
about.
E
Like
I
don't
know,
I
I
almost
I
feel
like
there's
a
statement
we
should
be
making
in
person
or
virtually
like
when
we're
talking
to
the
person.
If
we
have
that
opportunity,
but
otherwise
it
would
be
something
to
put
on
like
the
front
page
of
the
event,
diversity
and
inclusion
repository.
A
E
Yeah
it's
hard
because
nobody
really
reads
the
diversity
and
inclusion
repository.
They
always
started,
admit
diversity
and
inclusion,
because
that's
where
they
get
linked,
but
that
makes
a
lot
of
we
can
put
it
in
both
places
it.
We
can't
really
put
it
in
too
many
places.
G
Yeah,
because
you
know
in
like,
for
example,
that
when
we
talked
to
the
comcast
team,
you
know,
and
some
of
the
other
teams,
when
we
reached
out
to
them
the
the
emphasis
it
seemed
to
me
was
on
you
know
what
what's
it
gonna
take
right?
What
what?
What
are
the
resources
needed.
D
I
was
just
thinking
to
that
point.
You
know
having
that
more
streamlined
process
of
like
you
apply
once
and
it
goes
and
then
maybe
we
do
spot
checks
on
their
events
or
something
like
that,
but
that
might
be
something
that
you
know
to
these
larger
organizations
might
be
really
what's
the
word.
I
want
really
attractive
to
them.
You
know
if
they
know
that
they
just
have
to
apply
like
on
an
organizer
level
and
not
like
every
single
event.
I
do
I
have
to
make
another.
D
You
know
what
I
mean
so
just
to
that
point.
That
might
be
another
reason
that
we
we
look
at
or
think
about
doing
like
an
organizer
level
type
badge,
which
is
a
little
more
intensive
and
strict,
but
with
like
periodic
spot
checks
on
their
events,
something.
A
So
I
may
scroll
back
up
to
read
what
they
wrote,
but
everything
else
I
should
be
able
to
find
just
on
the
web
page
like
are
the
diversity
access
tickets
easy
to
find
and
can
you
apply
for
them
easily,
like?
I
don't
follow
a
link
that
they
put?
I
put
go
to
the
web
page
and
try
to
track
it
that
way.
A
So
as
an
org,
you
can
just
basically
say
here
are
the
like
the
10
events
that
are
associated
with
the
thing
that
we're
doing
like
kubecon
and
speaker,
demographics
and
attending
demographics
are
handled
the
exact
same
way
in
every
event.
Here's
how
they're
handled
you
know
diversity.
Access
tickets
were
provided
in
every
event,
but
so
all
I
really
need
is
the
link
to
each
one
of
those
10
events.
D
A
A
E
Much
less
expressed
concerns
more
more
much
expressed
that
I
just
appreciate
everybody
here
and
the
community.
That's
made
this
made
this
possible.
H
Yeah
pretty
much
matt
and
then
I'm
I'm
lately
both
mats.
Are
you
going
to
sign
those
out
to
us
reviewers,
or
do
we
just
grab
one?
How
do
you
want
to
do
that.
E
Oh,
I
I
sent
in
an
email
just
now
that
I
have
a
we're
still
in
review
orientation
sessions
even
for
the
ad
hoc
reviews,
just
just
like
a
15
minute
session
to
get
you
acquainted
with
the
process
and
get
you
on
the
same
page
as
all
the
other
reviewers.
At
this
point,
so
I
sent
you
a
calendly
link,
I
think,
but
once
we
get
that
orientation
session
and
you
join
the
github
team
and
the
rest
is
history,
we'll
assign
you
to
whatever
event
we
like,
we.
E
I
think
we
do
two
maximum,
but
that's
where
we're
at
right
now.
H
E
The
the
that's
I'm
on
the
same
page
there,
because
we
we
didn't,
assign
the
two
people
that
were
assigned
to
that
did
not
get
assigned
anything
else.
We
are
actually
just
moved
to
manual
assignments
so
that
the
bot
doesn't
do
the
picking
people
too
much
thing.
F
A
H
A
I
can
do
that
all
right,
awesome
all
right.
So,
honestly,
just
in
the
last
maybe
a
few
minutes
here,
one
of
the
things
that
has
come
up
that
came
up.
I
don't
remember
where
it
came
up,
but
is
to
standardize
readme
files
across
all
working
groups.
There
was
some
pretty
inconsistent.
A
I
had
actually
kind
of
worked
down
the
readme
file,
so
I
feedback
totally
welcome.
You
can
put
it
in
the
pull
request.
You
can
say
it
here,
it's
completely
fine,
so
the
first
two
top
level
headers
that
I
was
proposing
was
when
we
meet
and
how
to
participate
and
a
link
to
the
agenda
in
the
meeting
minutes.
Just
that's
right
up
right
up
in
the
front.
So
this
was
a
recommendation
that
came
from
the
community
call
yesterday
and
so
just
there
they
are
right
there.
A
A
I
thought
some
of
that
got
kind
of
dated,
or
was
fairly
obvious,
so
I
just
moved
right
into
the
focus
areas,
and
here
we
have
the
focus
areas
and
then
give
a
link
out
to
the
released
metrics
site.
So
when
do
we
meet
what's
the
background,
what
are
our
focus
areas
and
what
metrics
have
been
released
and
then
contributing
like
how
to
contribute?
So
I
got
rid
of
like
related
work
again,
you
can
totally
tell
me
this
is
not
a
good
idea.
B
E
B
A
And
then
the
other,
the
other
thing
I
was
kind
of
angling
towards
was
like
not
having
the
readme
contain
like
time
specific
information,
so
sometimes
the
readmes
will
say
we
have
we're
working
on
11
metrics.
Currently,
like
that's
a
highly
variable
number,
and
it
comes
and
goes
right.
So
I'm
trying
to
reduce
even
the
number
of
focus
areas
like
you
can
just
have
a
focused
area
list
and
people
can
count
by
themselves.
So
I
was
trying
to
get
rid
of
those
time
specific
items
in
the
readme
as
well.
A
A
D
A
A
A
D
Do
we
link
to
the
badging
repo
in
that
as
well
or
mention.
E
A
The
other
thing
that
I
was
removing
was
we've
in
the
readmes
we've
had
a
list
of
contributors
like
by
name,
you
know
like
for
a
while.
We
were
tracking
who
was
contributing
and
that
got
I'm
not
sure
how
accurate
the
list
is.
Basically,
it
feels
old
and
inaccurate.
It's
accurate.
I
guess
to
the
fact
that
these
people
contributed
that
these
folks
contributed
at
some
point,
but
we
don't
really
maintain
it,
so
it
ended
up
just
feeling
kind
of
old
and
we
are
starting
to
track
contributors
to
each
metric.
A
H
A
It
was,
I
think,
so,
yep
and
looking
at
how
they
were
maintained.
They
felt
like
they
were
getting
pretty
old
and
then
the
last
was
we
do
have
a
section
called
maintainers,
and
that
is
a
little
like
contributors.
It
gets
pretty
old
pretty
quickly
and,
like
I
looked
at
who
the
maintainers
were
for
dni
and
on
the
read
me,
I
think
it
says
emma
irwin.
A
It
says
who's
wonderful,
but
you
know,
is
working
on
other
things.
I
think
daniel
squaredo
is
a
maintainer
again
wonderful
person,
but
like
just
in
terms
of
like,
so
I'm
not
quite
sure
how
to
handle
this,
because
maintainership
is
kind
of
important
right
like
who
has
merge
rights
on
the
repository
so
yeah,
it's
10
51..
You
can
think
about
that
for
a
week.
A
D
A
Everybody
thank
you
so
much
for
the
really
thoughtful
comments
on
particularly
on
the
dni
badging.
That
was
really
pretty
amazing
so
and
matt
snell.
Thank
you
so
much
for
all
of
your
work.
In
that
regard,
I
am
absolutely
thrilled
that
this
has
gotten
to
where
it
is
today
and
that
we
have
these
types
of
problems
like
tracking
this
amount
of
work.
That's
awesome!
So
all
right,
thank
you.
Everybody
have
a
great
whatever
today
is
wednesday.