►
From YouTube: [SIG ContribEx] Weekly Meeting 20200127
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
Okay,
we
are
now
recording
the
cloud
hello
everyone
and
welcome
to.
Oh,
my
god.
I
don't
know
what
day
it
is
january.
27Th
2021
weekly
contributes
meeting,
I'm
your
host
bob
killen,
one
of
the
co-chairs
as
a
general
reminder
to
folk.
A
A
The
commits
haven't
happened
yet,
but
you
know
you're,
you
can
put
your
chair
crowd
on
the
the
next
thing.
As
sort
of
general
controbex
news,
I
sent
an
email
out
to
the
list
about
possibly
changing
the
time
of
this
meeting
to
moving
it
a
half
hour
earlier
folks
have
been
pretty
positive
on
that
for
a
variety
of
reasons.
For
me
personally,
it's
a
bit
better
and
I
now
have
a
permanent
conflict
at
the
the
top
of
the
hour.
So
I
wouldn't
be.
A
A
Office
hours,
I
know,
happened
and
went
pretty
well.
George
is
working
on.
You
know
getting
more
people
involved
as
potential
handoff.
As
he's
you
know,
stepping
a
bit
more
away
from
the
the
project.
A
Excuse
me,
but
I
don't
really
have
any
other
updates
there
on
that
one.
A
The
community
meeting
you
might
have
saw
that
it
was
canceled
for
this
month.
There
are
some
various
issues
that
we're
encountering.
The
public
google
group
is
the
kubernetes
dev.
Google
group
is
now
large
enough
that
we
can't
send
invites
to
it.
A
In
fact,
I
can't
export
the
list
of
people
that
are
on
it
either.
It's
just
too
big.
A
This
is
the
same
problem
we
saw
with
you
know,
trying
to
get
the
email
addresses
for
the
steering
election,
but
now
it's
getting
a
you
know
it's
impacting
a
bit
more,
but
there's
also
a
general
discussion
going
on
on
the
overall
value
of
the
community
meeting
people
like
the
release
updates
but
they're
shifting
to
email,
we'll
we'll
see
it
is
going
to
be
a
topic
for
discussion
actually
well
before
we
discuss
that
on.
Like
the
steering
side.
Does
anyone
on
the
contribute
side
have
any?
C
The
community
meeting
was
the
possibility
of
instead
asking-
and
you
know,
scheduling
somebody
would
have
to
follow
up
on
this
sigs
having
a
public
meeting
on
their
own
schedule
where
they,
where
they
went
over
the
update.
Instead
of
you,
know
a
joint
community
meeting
at
the
time
we
decided
that
it
was
actually
easier
for
the
attendees
to
have
those
lump
together
in
a
community
meeting.
But
if
we're
considering
dropping
the
monthly
community
meeting,
then
maybe
we
want
to
reconsider
that
other
idea.
D
So
another
idea,
the
the
openstack
community.
We
do
like
project
updates
too
that's
the
equivalent
of
the
stick
updates
and
lately
since
we're
not
like
meeting
in
person
to
do
them.
At
events
we
have
just
put
like
calls
out
for
people
if
they
want
to
do
an
update
and
record
it
and
then
we'll
like
promote
it
for
them,
and
then
it's
like
you
know
a
10
minute,
recording
or
whatever
that
we
can
put
in
like
a
playlist
on
youtube
for
somebody
to
go
watch
through
all
of
them.
If
they
want.
A
Sorry
I
I
missed
that
a
little
bit
because
I
was
trying
to
also
handle
notes.
I
I
realized
I
didn't
ask
for
a
note
taker
first
of
all,
and
so
you
were
typing
in
there
as
another
comment,
so
I
wasn't
wasn't
quite
sure.
D
We
have
switched
from
doing
them
like
in
a
community
meeting
or
like
at
an
event
to
basically
just
putting
a
call
out
to
like
the
leaders,
the
equivalent
of
like
the
sig
chairs
and
being
like,
if
you
want
to
record
a
like
five
to
ten
minute
thing,
we'll
promote
it
for
you
to
like
the
rest
of
the
community
and
outside
the
community
and
then
just
making
like
a
youtube
playlist
and
then
like
we
for
our
first
round,
because
we've
only
done
one
round
of
these
like
it,
it
worked
pretty
well,
there
was
pretty
decent,
like
involvement.
D
We
did
end
up
having
some
sort
of
like
public
forum
for
questions,
but
we
didn't
actually
get
that
many
questions.
So
if
people
or
if
the
sig
chairs
after
they
like
got
to
the
end
of
their
content,
they'd
just
be
like
join
the
channel.
To
like
ask
us
questions
on
these
things
or
whatever,
like
that,
would
probably
work
too.
A
Yeah
sort
of
like
we
could
everyone
could
record
the
quarterly
update
yeah
and
then
it
just
becomes
the
you
know:
kubernetes
quarterly.
You
know
process
update
or
you
know
you
know,
sig
update
whatever
yeah.
D
E
While
accidentally
hijacking
bob's
brain,
I
was
trying
to
write
out
some
thoughts,
and
you
know
I
I
hadn't
even
thought
about
the
idea
that
the
the
meeting
could
go
away,
which
is
just
a
sign
to
me,
like
I
thought
of
it
as
like,
an
essential
kind
of
point
in
which
we
converse
with
each
other,
but
trying
to
break
down
like
the
things
that
came
to
mind
that
I
think
of
the
community
meeting.
E
As
like
the
first
thing,
I
recommend
community
members
to
go
to
to
get
like
a
little
bit
of
a
snacking
of
all
the
different
sigs
and,
what's
going
on
so
while
a
little
overwhelming,
I
still
think
of
it
as
kind
of
the
front
door
to
the
community
and
then
for
current
members,
which
you
know
if
we
can
break
google's
member
list.
We
have
a
lot
of
it's.
It
really.
E
Is
that
like
check-in,
getting
beyond
your
like
myopic
view
of
kubernetes
and
seeing
the
bigger
picture
of
it
and
I'm
trying
to
think
of
you
know,
would
we
be
able
to
keep
those
those
same
sort
of
feelings
in
different
places
like
if
we
change
the
medium?
I
lean
too
much
on
podcasts.
Personally,
I
was
like
do
we
just
need,
like
a
community
podcast,
that's
the
official
update
and
we
interview
some
people
I'd
be
down,
but
also
is
that
good
or
yet
another
thing.
A
You
can
you
can
toss
on
an
idea,
the
I
know
people
would
listen
to
the
community
meetings
previously,
so
the
it
wouldn't
necessarily
be
a
podcast,
but
possibly
going
back
to
like
the
openstack
recording
of
the
community
updates
might
be
a
way
that
could
be
consumed.
That
loses
the
user.
A
About
the
dialogue
like
where's,
the
dialogue
happen,
the
the
big
problem
is
like
most
of
the
community
meetings
turned
into
like
there
wasn't
discussion,
and
that
was
like
a
complaint
we
heard
like
on
the
sig
leads
list.
A
Is
the
the
value
to
the
contributor
base
is
lost
because
it
is
just
like
tuning
in
and
you're
listing,
someone
read
it
off
and
there
is
no
like
any
there.
There
is
an
actual
discussion.
E
A
And
that's
that
is
from
a
more
senior
contributor
perspective
and
not
necessarily
a
new
contributor
looking
to
get
like
a
snapshot
of
the
community.
If.
E
You,
if
we're
starting
like
a
little
side,
conversation
or
a
doc,
to
explore
what
our
options
are
and
like
the
thoughts
and
feels
there
and
I'd
love
to
be
involved.
Okay,.
A
I
know
it's
going
to
be
a
topic
of
discussion
at
the.
I
don't
know
if
it's
the
next
steering
meeting
but
a
starting
meeting,
and
we
were
going
to
like
surface
some
of
the
questions
and
comments
from
from
this
up
there,
as
well
for
a
couple
ideas
when
it
comes
to
fixing
the
mailing
list
invite
right
now.
Our
only
real
solution
is
to
port
everyone
over
to
a
g
suite
managed
mailing
list.
A
A
Not
at
this
point
in
time,
we
should
create
one
though
there
there
wasn't
a
after.
We
noticed
that
the
the
counter
invite
wasn't
actually
going
out.
We
didn't
follow
up
with
creating
one
so
there
there
should
be
one.
F
A
E
Okay,
I'm
sure
yeah,
let's
separate
the
fix
from
the
re-architecture
yeah
like
we
got,
the
sounds
like
you've
got
to
deal
with
the
fix
first,
okay,.
A
So
any
other
questions
comments,
concerns
regarding
the
community
meeting
or
that
other
fun
stuff.
A
Okay,
I
have
no
comments
regarding
contributor
summits.
We
were
asked
if
we
wanted
to
potentially
do
something
for
kubecon
eu,
but
I
think
at
this
point,
if
we
do
do
something,
it
will
just
be
fully
independent
of
any
sort
of
keep
con
up
until
they
are
in
person
again.
A
I
think
tying
it
to
a
a
a
cube
content
will
just
be
more
stressful
for
everyone
involved.
Allison.
B
I
just
have
a
question
about
that
towards
the
end
like
I
know
there
was
some
discussion
around
the
calendar,
invite
stuff
and
I'm
not
sure
if
it
updated
to
my
calendar
if
we
changed
it.
So
any
update
on
that
because.
A
Okay,
it's
okay!
No,
no!
No
yeah!
We!
We
don't
have
a
meeting
for
that
one
currently,
just
because
there
isn't
any.
You
know
upcoming
event
that
we
have
scheduled.
If
we
do
decide
to
do
an
event,
it
will
not
be
a
part
of
kubecon.
It
will
not
be
adjacent
to
kubecon
itself.
A
A
Okay,
mentoring
meet
our
contributors,
paris
isn't
on
the
line.
I
believe
she
is
still.
You
know
chris
chimed
in
on
the
list,
but
I
think
she's
still
looking
for
other
people.
Excuse
me
that
might
be
involved
in
helping
with
the
meet
our.
A
Okay,
playground
just
see:
outreachy
ighor.
I
think
you
have
an
update
just
on
the
deadline
for
this.
F
Yeah,
just
a
brief
update.
I
just
wanted
to
the
late
smelling
list
a
few
minutes
ago
that,
if
you
plan
to
participate
as
a
mentor
and
you
plan
to
and
you'd
like
to
propose
a
project
for
mentoring
for
this
lfx
mentorship
cycle
process,
known
as
community
breach,
the
deadline
is
january.
A
Yeah
we
talked
about
a
few
ideas
in
the
last
mentoring.
Slash
new
contributor
workshop,
but
I
don't
know
if
there
like
is
enough
time
for
us
to
really
like
execute
on
those
before
honestly
the
end
of
the
month,
we'll
see.
F
A
Cool
having
a
little
bit
of
wiggle
room
is
nice
any
comments
or
questions
on
that.
B
I
I
haven't
caught
off
on
that
because
I
haven't
been
able
to
attend
because
the
meetings-
so
I
think
josh
can
take
over
on
this
one.
Okay,.
C
Okay
yeah,
the
work
is
slow.
People
have
been
vaguely
working
on
different
segments
for
it.
The
main
progress
has
been
with
the
new
zealand
lab
contingent,
hippies
crew
of
people
who
have
been
putting
together
an
interactive
environment
for
build
and
test.
C
C
The
for
the
rest
of
it,
you
know
we
we
have
our
usual
issue,
which
is
that
for
everybody
involved
in
in
producing
segments
for
that,
it's
you
know,
priority
number
13
or
something.
C
Yeah
the
so
I
know
for
the
segment
that
I'm
on.
I
got
as
far
as
writing
a
script
for
a
new
version
of
that
segment,
but
not
actually
recording
it
because
recording
it
will
take.
You
know
an
entire
day
day
and
a
half.
C
So
that's
kind
of
progress
allison
may
suggest
we
really
should
have
a
mentoring
meeting
on
the
other
side
of
the
clock.
Do
you
want
to
throw
out
a
doodle
for
that?
Do
you
want
me
to
throw
out
a
doodle
for.
B
If
you
could
a
doodle
for
that,
that
would
be
awesome
and
then
just
flick
that
in
and
contrabank
so
on
the
mailing
list,
yeah.
C
A
A
F
A
Stuff,
okay,
off
to
community
management,
so
we
actually
have
a
pretty
full
need
to
know
email
list
already.
If
folks
want
to
take
a
look
at
that,
the
stuff
we
have
on
deck
is
the
party
one
is
just
like
like
so
the
we
still
need
to
establish
the
release
schedule
for
2021.
A
A
The
kubecon
eu
maintainer
session
deadline,
the
sick
annual
reports
and
then
the
last
one
on
the
list
is
the
proposal
to
increase
like
increase.
Reliability,
increase
the
bar
of
reliability
for
kubernetes,
and
you
might
have
seen
that
go
across
a
couple
lists
josh.
I
know
you've
taken
a
look
at
it.
It's
been,
I
know
it's
been
updated
sort
of
recently.
A
Okay,
but
yeah
the
the
tldr
is.
There
is
potential
to
actually
prevent
the
merging
of
prs
or
blocking
of
features
unless
they
get
their
tests
and
flakes
addressed.
C
I
you
know,
as
you've
probably
seen
from
the
comments
in
the
document,
I'm
against
it
yeah
it's
essentially
a
collective
punishment
model
and
those
pretty
much
never
work.
I
mean
in
the
past.
We
used
to
the
release
team
used
to
be
a
lot
more
active
in
halting
merges
if
test
grid
was
terrible,
but
the
only
reason
why
that
worked
is
that
we
had
a
few
contributors
like
dims
and
liggett,
who
would
pitch
in
and
fix
things
whenever
that
happened.
C
It
wasn't
the
same
people
who
worked
on
the
features
who
were
actually
fixing
things
and
the
thing
is
dims
and
liggett
can
pitch
in
regardless
of
whether
or
not
we're
halting
prs
the
yes.
C
No,
but
what
I'm
saying
is
the
idea
of
okay
we're
going
to
block
all
pr's
from
a
specific
sig,
because
we
think
that
sig
is
responsible
for
severely
flaky
tests
is
both
going
to
create
a
lot
of
bad
feeling.
C
A
As
as
far
as
I
know,
outside
of
paying
people
in
the
mostly
on
the
leads
list
and
then
talking
to
sig
arch
in
a
few
other
places,
I
think
it
has
gone
out
to
k-dev
as
well
a
couple
times
for
initial
review.
C
A
That
either
way
I
would,
I
would
probably
go
to
you
know
k-dev
after
this,
but
yeah
going
back
to
the
the
need
to
know
list
itself.
I
think
you
know
it
needs
to
be
known
more
of
the
chairs
and
folks
need
to
see
this
and
re
take
a
look
at
it.
A
So
I
know
that
kind
of
scrolled
a
little
bit
off
the
initial
you
know
need
to
know,
but,
like
I
highly
recommend
everyone
taking
a
look
at
it,.
A
A
You
know,
there's
a
lot
more
pii
involved
and,
depending
on
how
you
phrase
your
questions,
just
judging
by
you
know,
the
general
diversity
of
our
contributions
would
be
much
easier
to
identify
specific,
potentially
much
easier
to
identify
specific
contributors,
which
is
not
what
we
want
so
josh
and
I
have
largely
worked
on
coming
up
with
some
fairly
neutral
phrasing,
and
it
is
currently
off
to
the
code
of
connect
committee
to
just
like
review
and
sort
of
see
the
state
of
this.
A
This
is
largely
because
we
as
a
community
want
to
do
significantly
more
in
terms
of
dni
outreach
this
year,
but
we
also
sort
of
need
to
get
like
a
pulse
of
what
our
current
community
is
and
sort
of
see.
If
you
know
whatever
we,
we
do
end
up
doing
this
year.
Whoops
winds
up,
you
know
in
you,
know,
improving
the
situation
or
you
know
where
it
improves.
C
Can
we
interrupt
between
items
and
actually
do
intros?
We
just
had
somebody
ping
on
chat
who's.
Actually,
a
new
person
to
this
meeting.
A
Oh
yeah
sure
I'll.
C
Go
I'll
start
off
I'll,
go
ahead
and
introduce
myself
I'm
josh
burkus.
I
work
for
red
hat.
I've
been
participating
in
this
group
for
a
long
time,
mostly
doing
stuff
on
mentoring.
A
I'll
go
next
time.
Bob
killian,
mr
bobby
tables
across
get
you
know,
preach
all
the
things.
I
am
a
co-chair
of
the
sig
contributor
experience.
G
Yeah
ma
hi
bob
hi
josh.
Thank
you
for
providing
me
the
opportunity
and
I
I've
been
working
with
a
hot
star
and
I've
got
total
four
years
of
experience
and
basically
I'm
a
kubernetes
practitioner
and
recently
you
know
I
just
learn:
go
stuff
to
you
know
start
contributing
to
kubernetes.
A
G
G
Yeah
I
have,
I
have
submitted
that
form,
but
I'm
not
sure
when
this
will
be
a
result
will
be
announced.
I'm
not.
A
Sure,
okay,
well
cool,
thank
you
for
swinging
on
by
and
if
you
want
like
again
feel
free
to
ping
any
of
us
in
slack.
If
you
have
any
questions,
we
are,
you
know
I'll
preach,
always
happy
to
help.
This
is
sort
of
sort
of
the
best
place
it
gets
like
you
know,
if
you're
not
at
home
here,
we'll
try
to
help
you
find
a
home
in
another.
A
Okay
back
to
community
management
for
at
least
another
minute,
does
anyone
have
any
questions
or
comments
about
any
of
the
community
management
stuff
before
we
move
on.
A
Okay,
I
don't
have
an
update
on
dev
stats.
I
know
lori
was
working
on
something,
but
I
don't
have
anything
there.
Marketing.
E
Ahoy
hoy,
we
are
cruising
along.
My
tab
keeps
crashing
so
give
me
a
second
before
I
pull
that
up,
but
the
main
thing
we're
kicking
off
the
year
with
a
push
for
content,
just
getting
people
to
write
more
and
our
meetings
on
friday
morning
have
been
partly
working
sessions
so
that
we
can
kind
of
collaboratively
work
on
stuff
and
you
know
feel
like
we're
getting
some
stuff
done
along
the
way.
E
The
big
ones
right
now
got
a
idea
for
people
sharing
their
contributor
stories
to
kick
off
the
blog
on
kubernetes.dev,
so
chris
short
signed
up.
He
wrote
something
on
non-code
contribution
to
kubernetes,
because
that's
how
he
sees
himself
and
what
and
I
think
that's
a
really
cool
story
to
get
other
people
who
don't
feel
like
they
code
to
contribute
to
kubernetes
mine's
more
of
a
story
of
time
and
like
limiting
how
much
time
and
still
being
effective
along
the
way.
E
And
then
a
new
contributor
actually
reached
out
saying
he
showed
up
to
the
marketing
meeting
and
said
he
wants
to
join
that
meeting,
because
he
wants
to
learn
more
about
marketing.
He's
a
developer
in
the
day
job,
and
I
thought
that
was
a
really
cool
angle,
too.
So
open
invitation.
If
you
want
to
write
a
few
sentences
to
a
pair
to
a
couple
paragraphs
on
your
contributor
story,
I
will
help
you
get
that
published
and
I'm
wanted
to
get
a
couple
out
there
before.
E
I
do
like
a
broad
push
and
and
try
to
get
more
people
in
the
community
right,
but
that's
what
we're
working
on.
We're
also
asked
to
write
something
up
on
psb
and
its
deprecation.
So
there's
a
collaborative
article
that
bob
was
a
part
of
that
is
pretty
far
in
progress.
Caslin
is
going
to
bring
it
over
the
finish
line,
but
that's
where
we're
at.
A
One
actually
one
note
on
the
psp
thing.
I
discovered
like
last
night
that
six
security
and
sig
auth
are
working
on
two
potential
proposals
as
a
replacement
for
psps,
oh
cool.
A
They,
I,
I
think,
they're
going
to
be
discussing
them
on
the
in
the
sigoth
meeting
soon.
But
if
you
pop
into
the
six
security
channel,
I
think
those
are
the
two
links
in
there
from
tabby.
E
A
E
Cool
yeah
that
sounds
great
okay
and
last
but
not
least,
I
mean
based
on
this
conversation,
I
at
least
want
to
bring
up
the
future.
The
community
meeting
on
friday
see
if
anyone
wants
to
kind
of
talk,
talk
through
it
in
some
way
and
if
anything
comes
of
it,
bobble
and
allison
will
send
it
your
way
before
you
keep
going
with
it.
Okay,
thanks.
A
Okay,
contributor
docs-
I
don't
have
any
real
updates
here,
at
least
nothing
since
last
week.
One
note
you
might
have
missed
is
that
we
do
plan
to
migrate
the
community's
contributor
website,
repo
to
kubernetes
from
kubernetes
sigs.
So
we
can
reuse
the
sig
docs
localization
teams
to
start
working
on
the
localization
of
that
content.
A
Okay,
github
management.
We've
done
our
annual
cleanup
of
the
work
of
removing
inactive
users.
We
do.
This
is
a
potential
opportunity
for
folks.
If
they're
interested,
we
do
need
help
in
cleaning
up
all
the
associated
associated
owners
files.
A
They
are
the
various
owners
files
and
who
needs
to
be
removed
are
all
linked
in
the
issue
that
I
linked
in
the
document
as
well
as
a
few
example,
pr's
of
what
that
looks
like
right
now,
it's
I
think
it
was
like
60
people
on
the
nose,
but
sort
of
the
little
background
of
this
is
if
you've
had
no
activity
within
the
org
for
or
any
one
of
the
kubernetes
orgs
for
18
months.
That's
commenting
on
you
know
issues
pr
is
doing
like
even
reacting
with
a
like
emoji
in
github.
A
If
you
have
no
events,
then
we
will
move
to
remove
you
from
the
kubernetes
org
for
and
clean
the
owner's
files
to
just
like
you
know,
reduce
the
potential
blast
rays
for
security
and
make
sure
that,
like
people
are
actually
getting
assigned,
active
reviewers.
G
Yeah
bob,
so
that
this
cleanup
will
be
manual
or
are
we
going
to
build
some
automation
around
this.
A
So
that
one
like
there
is
going
to
be
automation
long
that
we
want
to
do
long
term,
the
automation
regarding
the
owner's
files
themselves
would
be
difficult
in
this
current
stage.
The
the
main
thing
we
were
thinking
of
doing
was
doing
automation
regarding.
A
G
A
Cleanup:
okay,
one
other
github
thing,
and
this
comes
from
eor-
is
in
my
meeting
with
github
this
morning.
There
is,
and
we
like
we,
the
github,
has
done
all
the
stuff
regarding
the
branch
rename
automation.
A
A
Especially
with
how
costly
some
of
the
the
kubernetes
ci
is,
so
we
will
probably
hold
off
on
migrating
kk
until
they
have
that
resolved.
I,
the
club
management
team,
is
probably,
I
think,
they're
the
meeting
for
that
is
tomorrow,
but
we
will
be
talking
about
the
migration
of
master
domain.
There.
C
We
finished
renaming
the.
C
Resulting
in
actually
a
a
troll
taking
on
noah
but
the
he
knows
how
to
deal
with
that.
A
A
Okay,
that
takes
us
to
open
mic.
I
tossed
two
items
on
here.
One
is
we
tried
the
whole
slack
meeting
style
thing
and
I
wanted
to
get
some
feedback
on
that,
since
there
wasn't
too
much.
I
don't
think
anyone
responded
on
the
list
directly
outside
of
you,
josh.
C
A
A
Yeah,
so
the
the
first
time
it
happened
was
because,
like
several
of
us
immediately
had
a
conflict
and
so
just
like.
Well,
let's
try
the
slack
stand
up
yeah
this
time
around
and
we
didn't
set
the
bounding
times
for
it.
With
the
second
meeting
we
had
the
predefined.
This
is
when
it
starts.
This
is
when
it
stops
conclude
your
conversations
by
this
time,
and
I
think
that
is
you
know
if
we
are
going
to
move
forward
with
it.
I
think
that's
what
we
do.
F
B
If
we
like
move
forward
with
it,
one
thing
yeah.
If
we
had
like
a
separate
channel
for
those
kind
of
meeting
notes,
so
they
don't
get
lost
or
people
don't
feel
like
they
can
send
messages
in
the
contracts
channel.
While
the
meeting
thing
is
going
on,
because
that
might
help
improve
quality
of
life
and
like
searching
back
through
the
notes.
B
C
A
That's
why
I
think,
like
you
know,
if
we
do
have
a
separate
channel
for
essentially
the
meetings
where
you
know
you
could
have
it's
not
necessarily
each
bullet
point
item,
but
you
could
have
separate
threads
for
you,
know
more
of
the
topics
and
essentially
like
here's,
the
start
date.
Here's
the
end
date.
The
conversations
between
here
become
the
notes.
Can.
C
A
A
Probably
yes,
I
think
so
what
probably
wound
up
happening,
though,
is
just
like
one
of
the
leads.
That's
essentially
consolidating
the
notes
would
just
like
copy
and
paste
it,
and
then
because
we
we
do
clean
up
of
the
of
the
notes,
the
way
before
to
put
them
back
into
our
doc
and
send
them
out
to
the
list.
Yeah.
A
C
A
C
The
right.
A
C
A
A
A
Yeah
contributex
has
been
and
like
this
is,
you
know,
also
very
much
like
my
fault,
we
we've
been
a
lot
of
decisions
made
in
meetings
without
the
actual
follow-up
to
the
list,
and
that
is
something
trying
to
improve
upon
this
year.
F
C
If
you
are
going
to
object
or
comment
on
one
of
these,
you
have
48
hours
before
their
final
and
that
would
be
sort
of
a
minimum
effort
way
of
doing.
A
C
G
A
We
yeah
we'd
have
to
through
this,
so
we,
since
our
slack,
has
like
a
hundred
and
twenty
thousand
people
on
it.
Okay,
we
are
very
restrictive
of
what
integrations
we
like
allow
to
happen
with
slack.
A
We
actually
have
a
so
we
have
like
an
entire
slack
admin
team
and
like
to
with,
like
we
have
an
issue
template
for
proposing
bots
and
all
that,
so
what
we'd
probably
do
is
review
the
bot
and
then
propose
it
to
the
slack
admins
for
feedback
on
it
on
a
github
issue.
There.
G
A
A
C
C
A
A
I
don't
want
to
spend
too
much
time
on
that,
just
because
we
only
have
a
few
minutes
left,
but
on
these
remaining
open
items,
I'm
thinking
we
just
put
them
over
to
the
121
milestone.
He's
like
this
should
get
done
soon.
Allison.
I
know
we're
going
to
work
on
this
one
as
we
go
through
you're
on
boarding
as
a
new
lead,
and
this
should
also
get
done
soon.
It's
blocked
on
on
me
so
are
folks
comfortable
with
just
moving
these
things
to
the
121
milestone
and
closing
this
one
out.
A
A
A
Time,
I
think
we're
pretty
good
there
for
the
most
part,
especially
once
we
roll
on
the
other
ones
and
again
the
the
new
contributor
workshop
will
100
be
the
priority
for
this
cycle.