►
From YouTube: CHAOSS DEI Working Group 9-15-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
B
Yeah,
I
did
just
for
those
who
didn't
hear
the
beginning.
We
were
chatting
about
this
a
little
bit,
but
we
apparently
that
was
turned
on
for
the
dei
badging
meeting
and
it
was
really
cool
a
little
tiny
bit
distracting,
but
super
super
cool,
as
it
would
just
caption
at
the
bottom
of
the
screen.
B
What
was
being
said,
and
it
would
actually
go
back
and
self-correct,
based
on
the
context
of
the
rest
of
your
sentence,
which
was
also
very
cool,
so
it
seems
like
it
might
be
a
good
idea
to
if
we
can
figure
it
out
how
to
enable
it
on
the
chaos
zoom
call
our
zoom
account.
B
I
think
I
think
it
would
be
very
helpful
for
a
lot
of
our
working
group
meetings
and
also
the
community
meeting,
so
I
want
to
just
run
it
past
this
group
and
see
if
that,
if
there
were
concerns
about
it
since
it
is
live,
you
know
there's
no
real
way
to
kind
of
check
it,
but
it
seemed
to
be
okay.
So
I
don't
know
what
this
group
thinks
about.
It's
certainly.
B
A
Distracting
anyway,
let's
go
ahead
and
move
forward
to
the
we.
It
looks
like
we're
going
to
update
the
goals
for
what
we
want
to
do
next
year,
because
our
last
update
to
this,
the
working
group
goals
was
2019..
A
So
I'm
going
to
share
my
screen
here
and
we've
got
a
bunch
of.
Did
you
see
my
the
working
group
goals
for
2019
on
your
screen?
A
E
I
guess
I'd
be
curious
to
know
like
who's
the
audience
of
this
document.
I'm
new
to
this.
E
A
A
So
maybe
for
the
purpose
of
this
meeting,
we
can
kind
of
identify
some
top
level
objectives
that
we
want
to
meet
in
in
the
next
in
the
next
year
and
kind
of
talk
about
those.
A
Sorry
that
was
from
dark
to
light
that
actually
hurt
my
eyes
anyway.
So
let's,
let's
identify
some
objectives:
I'm
going
to
go
on
quiet
and
let
y'all
talk
about
it.
D
D
A
To
add
some
direction
here,
I
guess
the
question
would
be
what
what
is
something
we
could
accomplish
within
a
year
that
wouldn't
be
overwhelming,
but
at
the
same
time
would
be
kind
of
a
landmark
movement
forward
for
the
dei
working
group.
B
I
think,
based
on
the
next
bullet,
maybe
onboarding
like
I
don't
know
if
we
want
to
leave
it
as
general
as
like
improving
the
onboarding
process
or
experience
or
if
we
want
something
a
little
more
tangible,
but
I
think
that's
maybe
something
we
could
do
in
a
year.
B
I
had
another
question
too,
so
we
have
our
internal
reflection,
the
dei
project.
That's
going
on
right
now
and
we're
going
to
be
doing
that
survey
and
then
from
the
survey.
I
assume
that
there
might
be
some
things
that
come
out
of
that,
or
also
some
recommendations
from
the
dei
audit
team
as
well-
and
I
guess
my
question
is:
who
is
responsible
for
implementing?
That?
D
I
think
we
is
this
part
of
that
conversation
like
is
this
working
group
responsible
for
like
doing
dei
related
things
within
the
chaos
project
versus
like
doing
dei
things
that
help
others?
I
know
that,
like
it's,
not
a
super
clear
distinction
between
the
two
and
your
your
comment
was:
does
the
risk
group
do
like
a
risk
analysis
on
the
chaos
project
like
that's?
We
don't
no
right
exactly
you
don't,
but
you
provide
like
insights
into
how
others
could
think
about
risk
and
of
course
we
could
use
that
information
ourselves.
D
D
A
lot
of
the
things
aren't
like:
I
don't
think
that
they're
like
super
dei
like
like
you,
need
it
like
a
lot
of
it
is
like.
Let's
get
this
information
into
the
handbook,
let's
update,
you
know,
let's
take
a
look
at
where
we
think
about
storing
survey
data
like
I
don't
know,
they're
kind
of
like
logistics,
things
sometimes
that
are
that
happen
to
be
about
dei,
so
that
would
be
my
first
thought.
D
And
I
mean
the
other.
The
other
truth
out
of
this
is,
is
that
you
sean
and
myself
have
been
kind
of
a
we've
been
a
member
of
that
reflection
team
for
a
while.
So
I
mean
I
do
think
it's
like
important
for
the
three
of
us
to
provide
some
consistency,
yeah
to
also
be
there,
and
I
would
suspect
that
the
three
of
us
will
do
some
of
this
implementation
would
be
my
guess.
A
It
sounds
like
something
we
want
to
figure
out
is
well
to
reflect
on
the
der
collection.
It's
kind
of
ambiguous,
but
conventional,
provides
in
context.
It
sounds
like
we're
trying
to
figure
out
what
our
role
is
in
been
like
what
what
our
responsibility
is.
As
a
working
group.
D
Yeah,
I
think
it's,
whether
or
not
we
take
on
additional
tasks
in
this
project,
so.
F
F
I've
seen
these
meta
working
groups
emerge
as
kind
of
being
a
bridge
across
many
different
established
groups
in
a
community
and
that
working
group
being
specifically
a
cross-team
or
cross-functional
group
of
people
who
do
some
of
that
going
in
between
to
collect
feedback
like
what
are
some
of
the
things
that
the
risk
group
might
look
at
or
what
are
some
of
the
things
the
dei
working
group
might
look
at
and
then
putting
together
the
actual
implementation
and
proposals
for
how
can
we
implement
some
of
that
feedback
or
best
practices
in
our
own
project?
F
To
give
an
example,
the
fedora
project
has
a
community
operations
team
which
does
this
kind
of
work.
It
goes
between
a
lot
of
the
different
teams
in
the
project
to
help
tie,
tie
things
together
and
implement
some
of
those
implement.
Some
of
these
ideas
and
solutions
that
help
make
collaboration
or
best
practices
easier
in
the
project.
So
maybe
that's
one
direction
to
go,
because
I'm
a
little
bit
right
now,
I'm
kind
of
against
the
idea
of
broadening
the
scope
of
all
the
working
groups
to
do
this
for
the
chaos
community
too.
F
D
I
like
that,
at
the
idea
of
a
community
operations
group,
I
mean
we've
in
a
not
dei
context.
We
were
doing
this
yash
and
ritik
for
doing
this
when
we
were
doing
the
metrics
release
because
they
had
to
coordinate
with
every
working
group
to
kind
of
get
their
repositories
organized
in
a
very
particular
way
encourage
the
working
groups
to
make
changes.
D
You
know
what
I
mean,
so
it
was
an
operations
thing
and
yosh
and
ritik
in
that
case
weren't
necessarily
members
of
any
of
the
specific
working
groups,
but
they
were
very
much
interested
in
the
operations
of
the
working
groups
so
that
we
had
consistency
in
places
where
we
needed
it
for
the
for
the
release
process.
F
A
A
These
groups
like,
like,
like
dustin,
said
that
have
been
kind
of
put
in
place
between
these
working
groups
and
the
bridges
working
groups,
but
like
something
that
kind
of
ties
it
all
together
like
from
this
one
to
this
one,
and
all
that
all
that
stuff,
that's
my
graphic
for
it.
But
that's
what
I'm
hearing.
B
Can
we
add
metrics
to
our
objectives
like
to
continue
to
build
those
out.
D
Yeah,
I
think
metrics
and
the
badging
program
is
a
really
important
thing
that
I
believe
has
a
home
in
this
working
group.
D
I
can't
I
understand
it's
like
that
gray
area
again,
you
know,
but
how
about
this
I
I
think
that
this
working
group
is
always
a
place
to
talk
through
questions
with
respect
to
badging.
A
Okay,
that
works
for
us
and
we
as
a
group
with
our
own
meeting
too
badging,
is
doing.
I
think
it's
doing
really
well,
I'm
glad
to
see
that
it's
doing
well
and
I
think
that
root
in
the
chaos
dei
working
group
is
really
a
big
part
of
it.
B
To
the
point
of
the
metrics,
I'm
looking
at
the
spreadsheet
and
there's
a
section
we
don't
have
any
metrics
for
so
maybe
that's
something
we
want
to
put
on
our
objectives.
It's
recognition
of
good
work.
B
A
Now
that
I'm
in
screenshot,
you
can
see
the
amount
of
random
text.
Other
thing
I
do,
but
that
is
that
looks
like
a
really
good,
like
hot
point,
is
a
recognition
of
good
work.
We
really
need
to
have
some
metrics
in
there,
so.
A
Do
we
have
any
more
to
talk
about
with
this
with
this
set
of
top-level
objectives,
or
should
we
move.
A
Okay,
we've
got
my
action
item
from
last
week.
A
This
this
item
right
here
the
organizational
changes
we
just
I
just
built
that
because
we
just
talked
about
it
as
kind
of
a
separate
topic,
but
as
far
as
the
identifier
problems
and
solutions
and
cast
onboarding,
I'm
going
to
go
over
these
real
quick
just
that
we
have
the
the
three
issues
that
I've
kind
of
realized
and
and
the
ones
that
I've
seen
kind
of
out
working
in
the
chaos
project
is
that
potential
contributors
may
not
know
how
to
enter
the
project
or
how
to
get
involved.
A
They
might
not
know
how
to
start
contributing
once
they
do
get
involved,
how
to
how
to
start
working,
and
they
may
not
have
a
good
avenue
to
ask
questions
as
part
of
that,
and
then
the
the
last
part
is.
What
we
had
just
talked
about
is
that
the
cast
project
is
fairly
segmented,
so
getting
into
one
working
group
is
takes
almost
as
much
work
to
get
into
the
next
working
group
and
so
on,
because
there's
not
not
so
much
that
they're
different
from
each
other,
but
that
they
don't
have
much
of
a
connection
between.
A
Like
kind
of
laterally,
the
solution
I
had
the
first
one
was
simple
direct
and
for
entering
the
project.
Just
simple,
direct
and
centralized
page
for
any
contributors.
A
More
avenues
for
contributors
to
ask
questions
would
probably
help
with
the
start
starting
to
contribute
and
then
the
segmented
nature
of
the
cast
project.
Just
the
what
we
just
talked
about
the
cross
meeting
collaboration.
A
Yeah,
I'm
kind
of
thinking
about
necessarily,
if
these
make
sense
to
people
or
if
they
resonate
with
them
and
seeing
if
they,
if
they've,
had
some
of
the
same
problems
or
kind
of.
If,
if
this
makes
a
lot
of
sense,
then
we
should
probably
I
should
probably
start
building
some
solutions
that
are
a
little
more
concrete,
but
I
I
wanted
to
bring
this
top
level
up
just
to
see
if
this,
if
this
works,
if
this
makes
any
sense.
D
I
think
this
is
good
on
the
with
respect
to
kind
of
the
first
and
the
second
one.
D
We
were
talking
doing
a
debrief
with
some
of
the
google
summer
code
students
because
you
know
they
google
summer
of
code
is
funny
because
they're
they
are
new
contributors
but
they're
coming
in
as
under
a
program,
so
they
have
to
cross
that
bridge
of
not
being
familiar
with
a
project
to
being
familiar
with
a
project
in
relatively
short
order.
You
know,
so
that's
a
and
one
of
the
things
that
came
up
was
the
in
the
repositories.
A
Yeah
and
kind
of
that's
a
great
lead
and
by
what
I've
been
reading
about,
onboarding
and
kind
of
how
to
get
new
people
in
a
lot
of
that
comes
from
having
a
really
good
contributing
guide,
but
then
not
having
any
links
to
it
or
good
ways
to
get
to
it
from
like.
Maybe
the
website
or
the
the
github
page
other
than
just
clicking
directly
on
the
file.
B
Yeah
I
was
gonna
say
that
it
would
be
great
to
have,
like
you
said,
a
centralized
page,
because
I
don't
know
like
we
don't
really
have
the
office
hours
listed
and
except
for
maybe
under
participate,
but
I
think
it
would
be
really
good
to
have
like
have
all
that
stuff
like
if
you're
new
to
the
project
click
here,
you
know
like
one
place
where
someone
can
go
and
see
what
to
do
and
where
to
find
stuff.
So
I
I
think
that's
great.
A
Yeah
and
originally
I
would
be
hesitant
to
put
it
in
a
markdown
file,
but
at
the
same
time,
markdown
is
where
a
lot
of
our
work
lives.
So
that's
something
you
might
have
to
have
some
comfortability
with
if
you're
coming
in
from
you
know,
left
field
looking
at
the
project
as
far
as
the
second
one,
I
don't
necessarily
know
how
to
do
this.
A
A
My
big
concern
with
that.
I
thought
about
that,
and
my
big
concern
is
that
opening
an
issue
to
a
new
project,
especially
as
a
new
contributor
and
even
as
a
new
person
open
source
for
sure
it
can
be
extremely
intimidating.
So
maybe
even
just
having
some
kind
of
anonymous
q
a
or
something
I
don't
know.
What
do
you
think.
E
So
I
guess
I
can
share
my
thoughts
because
I'm
in
that
space
right
now
being
new
to
open
source
and
newer
to
the
community
yeah,
I
definitely
ditto
the
the
intimidating
thing
I
think
like
for
me,
and
maybe
this
is
somewhere
and
I'm
just
not
sure
where
to
find
it
kind
of
to
our
previous
point.
But,
like
I
don't
know
what
to
contribute
necessarily
is
there
a
place
that
we
have
like
here
are
the
things
that
we're
looking
to
do.
E
D
I,
like
that,
a
lot
we
do
focus
a
lot
on
like
how
to
contribute
like
here
are
the
meetings.
Here's
the
mail
list,
twitter
or
whatever
like
here
are
things
and
you
can
attend
these
meetings,
but
I
like
the
what
component
of
here's,
what
you
can
do
you
can,
I
don't
know
we
should
probably
just
have
a
list
of,
and
we
do
have
those
good
first
issues.
You
know
I'm
talking
about.
B
B
I
was
gonna
just
so
back.
I
guess
it
was
probably.
Last
year
we
started
doing
in
the
newsletter
like
a
volunteer
opportunity
of
the
week,
and
it
was
like
had
like
what
it
is,
how
much
time
it
would
take
what
skills
you
need
all
like
all
the
things
in
a
nice
little
package,
but
that
didn't
er,
I
guess
of
the
month.
B
We
did
it
like,
maybe
three
or
four
times
and
then
that
kind
of
fell
away
as
nothing
really
surfaced
as
like
a
we
tried
to
keep
it
in
like
a
nice
little
box,
you
know
something
that
would
be
easy
for
people
to
wrap
their
head
around
and
you
know
contribute.
But
maybe
we
could
kind
of
resurface
that
and
like
take
some
time
to
brainstorm
what
what
those
things
might
look
like,
and
I
can
take
an
action
item
to
to
pull
those
up
for
for
next
time
or
wherever.
B
Whenever
we
want
to
keep
working
on
this,
because
I
mean
we
would
get
like
immediate
responses
when
things
are
very
clear
and
the
boundaries
are
very
clear
of
like
how
much
time
and
what
skills
are
needed
and
stuff.
So
yeah
I'd
be
happy
to
bring
those
back
up
as
just
some
ideas
of
where
we
can
go
with
this
idea.
Lauren,
that's
fantastic!
I
love
that.
D
I
would
is
there
a
possibility
to
on
the
chaos
home
page
too,
like
right
now,
it's
the
header
at
the
top
that
says
what
we
are:
it's
a
list
of
our
software
initiatives
and
working
groups,
which
is
good
and
then
below
that
we
have
that
gray
banner,
which
is
like
chaos.
Con
is
now
back.
You
know
what
I
mean
like.
Would
there
be
a
just?
D
B
No,
no,
I
was
just
gonna,
say
yeah.
I
think
it
absolutely
should
be
there
somewhere,
I'm
not
a
designer,
so
I
don't
know
where.
But
you
know,
maybe
we
could
take
inspiration
from
other
open
source
projects
that
are
larger
and
kind
of
maybe
have
figured
this
out
like
I'm
thinking
of
drupal
in
particular,
because
you
know
they
have
such
a
huge
community
and
a
very
diverse
community
and
they
seem
to
be
doing
a
lot
of
things
right.
So
that
would
be
one
and
maybe
justin
like
in
the
fedora
project.
B
F
Yeah,
actually
there
was
one
thing
I
was
thinking
about
and
I
was
going
to
dig
a
link
up
for
is
that
we
have
this
easy
fix
page.
Let
me
see
I
can
share
a
link
to
the
to
the
page
first,
but
it
all
it
is
it's
a
collection
of
good
first
issues
across
all
of
our
repositories
and
that
work
is
actually
getting
a
revamp.
F
Now
I
think
if
I
share
this
link,
this
is
where
some
of
the
new
code
is
being
written
and
it's
being
written
in
a
way
where
it's
easier
to
repurpose
for
other
communities,
but
it's
still
a
work
in
progress.
But
that
said,
this
is
just
an
automated
way
of
doing
this.
So
it's
a
little
bit
easier.
F
I
think
the
way
that
that
list
was
started.
First
was
it
was
actually
a
a
manually
curated
list
by
a
by
a
human
to
go
into
like
those
good
first
issues
and
it
does
have
a
maintenance
burden,
because
then
those
things
get
closed
and
then
you
have
to
remember
to
update
the
list
and
if
you
have
a
lot
of
different
repos,
that
means
you
probably
need
to
have
a
couple
different
people
who
are
actually
checking
it,
so
it
actually
gets
updated.
F
Well,
someone
has
to
go
update
that
list,
but
so
I
guess
to
that
end,
this
is
one
tool
we
could
use
or
or
or
borrow
from,
but
at
the
very
least,
if
not
if
we
don't
want
to
go
down
the
tooling
route,
it's
just,
I
think,
a
place
of
making
that
space
in
a
visible
location
on
the
site
and
collecting
those
things
and
working
together
with
the
stakeholders
and
like
the
different
working
group
to
the
community
working
group
to
actually
surface
what
those
things
are
over.
C
B
The
drupal
site,
if
you
go
to
their
site,
there's
like
three
clear
buttons:
try
drupal
get
involved
like
those
are
the
three
things
that
you
can
kind
of
do
and
then,
if
you
click
on
get
involved
and
there's
a
really
nice
page
of
like
what
their
values
are,
and
you
know
how
you
know
how
you
can
join
things
that
are
important
to
them
and
then
you
know
different,
there's
some
different
buttons
at
the
bottom
of
like
what
would
be
interesting
to
you,
like
community
working
group,
promote
drupal
whatever
you
know,
mentoring
that
kind
of
stuff.
B
So
it's
it's
almost
like
a
very
good
like
recruiting
page
almost
like
you
know,
you're
going
for
a
job
really,
but
even
though
it's
just
for
volunteers,
obviously
I
don't.
I
don't
know
that.
I
don't
know
how
that
works,
but
but
it's
a
good
page,
so
yeah.
A
It's
gonna,
it
would
involve
some
work,
but
what
about
something
like
twitter
posts
for
good,
first
issues,
that
post
them
or
maybe
even
well?
I
don't
know
that
could
be
done
with
a
bot
it
could
be
done
manually
but
like
maybe
just
some
kind
of
like
showcase
every
once
in
a
while.
This
is
something
that
we
could
get
worked
on.
We
need
help
and,
like
you
said
matt
with
this
banner,
we
can
have
an
optional
banner.
D
D
A
D
B
D
Us
in
in
like
how
do
we
say
it
like
like,
we
need
to
say
it
in
a
way
like
join
us.
Here's
some
some
issues
that
new
contributors
could
work
on
like
we
actually
spell
it
all
out
like
here,
are
if
you're
new
to
the
chaos
like
we
just
say
here
are
issues
for
new
members
or
here
are
things
that,
as
a
new
member
you
could
work
on
like
is
this
just
spelled
out
in
full
in
full
text,
so
that
people
understand
what
clicking
that
would
do.
F
So
you
have
a
question
or
you
want
to
talk
to
someone
about
about
the
project
or
what
you
you
know,
what
you're
interested
in
and
have
a
a
real
human
being
to
talk
that
through
with
that's
where
that
join
sig,
and
also
what
other
communities
I've
seen
where
they've
taken
that
approach.
So
you
can
also
find
all
these
things
if
you're,
if
you're
in
that
self-starter
kind
of
attitude
or
mood,
you
can
jump
in
look
for
the
information
and
and
dive
in
deeper,
but
I
think
sometimes
just
having
that
human
connection.
F
First,
it
may
be
like
don't
know
where
to
begin.
Come
talk
to
a
human
and
get
get
a
little
bit
of
mentorship
like
talk
to
someone
for
30
minutes
or
open
a
ticket
or
a
mailing
list
post.
Where
we'll
we
have
folks
who
are
ready
to
help
newcomers.
That
might
be
one
option.
I
don't
know
if
it's
too
much
of
a
sidebar,
because
it's
kind
of
more
of
a
human
resource
question
than
it
is
writing
text
up
and
and
going
that
way.
F
But
maybe
it
builds
on
the
community
operations
group
or
maybe
that's
the
role
that
a
community
group
could
play.
I
don't
know,
but
that's
one
thing:
I've
seen
that
I've
really
liked-
and
I
think
it
has
made
a
huge
difference
just
by
having
a
human
being
entry
point
into
a
larger
project
like
chaos
over.
A
Another
idea
how
about
a
get
in
touch
button
that
goes
to
schedule
a
meeting
to
figure
out
more
about
the
cast
project
or
something
like
that
or
or
maybe
even
a
set
of
options
and
how
you
can
get
started
with
the
kiosk
project
and
interact
with
the
real
person.
I
really
like
the
human-centered
approach
idea.
F
I
think
office
hours
can
work
for
some
people,
but
I
think,
having
that
explicit
opportunity
of
having
an
unstructured
time,
which
I
mean
I
guess
office
hours
are
unstructured
too,
but
I
know
that
can
also
be
intimidating,
like
bringing
back
some
of
my
experience
with
some
communities
like
when
I
was
new
office
hours
were
just
as
intimidating
to
me
as
it
was
to
go
and
open
a
new
issue
just
because
it's
like,
oh
I'd,
get
nervous
like
what
do
I
talk
about?
What
do
I?
What
do
I
ask
like?
F
I
think
this
mentorship
piece
or
getting
in
touch
needs
to
have
some
structure
in
place.
So
it's
not
like
a
total.
You
know
blank
where
it's
like.
You
have
to
think
of
all
the
questions
you
need
to
ask
in
advance,
which
might
not
always
be
clear
to
you
if
you're
still
very
early
on,
but
I
think
it
needs
to
be
so
structured
where
it's
like.
B
B
Is
there
benefit
in
having
like
hey
here's,
a
here's,
a
team
of
people,
and
then
you
know
we
have
someone
new
that
come
into
the
project
and
then
they
get
maybe
assigned
a
buddy
or
something
that
is
the
person
that
kind
of
like
keeps
them
engaged
keeps
them
involved,
like
checks
on
them
just
to
see
if
they
have
any
questions,
or
it's
just
like
that
one
kind
of
friendly
face
kind
of
like
what
justin
was
saying
of
you
know,
making
it
a
little
more
human-centered,
like
I
wouldn't
mind
doing
that
at
all.
B
I
would
I
would
love
to
do
that.
I
don't
know
if
that's
creepy
or
weird,
like
I
don't
know
like.
Where
does
it
end?
You
know
like
how
much
do
I,
like
you
know,
try
to.
B
Like
I
don't
know,
maybe
it's
a
bad
idea,
I
don't
know,
but
it
just
seems
like
that's
something
that
the
google
summer
code
I.
D
D
A
So
so
it
sounds
like
we
have
a
lot
of
ideas,
I'm
what
my
my
goal
for
the
next
meeting
is:
is
I'm
going
to
come
up
with
a
more
concrete
solution,
at
least
one
of
these
or
just
one
of
these,
and
then
I'm
going
to
bring
it
back
to
the
group
and
say:
what
can
we
do
to
make
this
better
and
how
can
we
implement
it
in
the
project?
That's
kind
of
my
goal
and
then
we
about
the
mentorship
project.
A
Elizabeth,
do
you
want
to
get
in
contact
with
me
and
maybe
anyone
else
who
might
be
involved
want
to
get
involved,
and
then
we
can
just
start
working
out
how
that's
going
to
work.
Sure
cool.
I
really
like
that
idea.
I
think
mentorship
is
one
of
the
best
ways
to
learn.
To
be
honest,
so.
A
Okay,
we
have
a
couple
more
minutes.
Do
we
want
to
go
over
release?
First
few
comments
or
sean?
Do
you
have
an
update
on
the
brand.
C
I
have
a
small
update
that
I
I'd
like
or
a
small
thing
I'd
like
to
ask
of
the
group
I'm
going
around
from
working
group
to
working
group
to
ask
if
your
working
group
wants
to
change
the
name
of
your
primary
branch
from
oh,
you
guys
have
done
it
already,
never
mind.
We
did
this
for
you.
We
did
this
last
week,
never
mind
yeah.
Here
I
am.
C
A
We
have
about
eight
more
minutes.
Do
you
want
to
go
over
the
the
release
updates
for
looking
at
issue
comments
and
see?
If
there's
anything,
we
can
change.
F
D
D
D
A
All
right
and
for
this
meeting
just
postponed
that
metrics
release
comments.
I
we
gotta
stop
using
the
word
tabled,
so
I
use
postponed.