►
From YouTube: SIG Contributor Experience Weekly Meeting 20200930
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
Hello,
everyone
and
welcome
to
the
weekly
signature
experience
meeting.
I
am
your
host
bob
killen
one
of
the
co-chairs
and
just
to
remind
folks
that
these
meetings
are
recorded
and
we
abide
by
the
cncf
code
of
conduct
which
can
essentially
boil
down
to
please
be
excellent
to
each
other.
A
Today,
we're
going
to
try
and
blitz
through
most
of
our
sort
of
like
stand-up,
ish
type
things
and
then
get
right
into
visiting
our
sort
of
cycle
planning
for
1.20.
A
Oh,
I
completely
overlooked
something:
is
there
any
new
contributors
online
that
might
be
introduced
or
interested
in
introducing
themselves,
if
not
no
big
deal?
We
can
also
revisit
it
later.
A
Okay,
we'll
kick
right
over
to
events.
George
had
to
step
out
at
the
last
minute.
I
don't
know
of
any
updates
regarding
office
hours
or
the
community
meetings.
A
Okay,
contributor
summits,
we
sent
a
small
survey
off
to
the
leads
list
just
to
see
if
anyone
is
actually
interested
in
potentially
doing
one
and
that
will
sort
of
drive
our
decision
later.
If
we
want
to
do
something,
if
we
do
it'll,
probably
be
much
smaller
than
a
you
know,
regular
computer
summit
initiative.
A
A
B
A
Out
of
curiosity,
how
many
people
have
been
needing
to
get
a
new
email
sent
a
new
ballot
sent?
I'm
sorry.
B
20,
something
I'm
gonna,
look
for
an
exact
count,
yeah
20,
something
the.
Unfortunately,
I
think
that's
because
a
lot
of
people
just
haven't
actually
checked
the
I.
I
fully
expect
to
get
some
requests
for
replacement
ballots
too
late.
C
B
Yeah,
the
on
a
somewhat
sour
note,
the
our
plans
to
use
community
bridge
to
get
an
intern
to
build
this
new
voting
app
are
not
going
to
work
out
because
community
bridge
the
community
bridge
application
is
broken
and
we
were
unable
to
get
any
valid
interns
applying.
A
That's
weird,
or
do
you
have
any
details
on
that.
E
So
I
missed
the
conversation
except
what
was
the
question
I
missed.
A
The
conversation
I'm
sorry,
oh
there
was
an
issue
with
the
community
bridge
and
the
voting
up
rewrite.
E
A
Process
are
there
any
other
event
type
things
people
want
to
talk
about,
or
should
we
kick
on
to
the
next
section.
A
Okay,
we'll
go
into
the
next
section,
with
mentoring
meet
our
contributors,
see,
I
don't
think
paris
is
on
the
line.
A
So
I
think
we'll
just
skip
over
that
one
for
now
playground
just
to
see
outreachy,
we
sort
of
just
touched
on
the
the
outreachy
thing
briefly,
at
least
for
the
election
app.
Are
there
any
other
updates
there?
You
are.
A
Okay,
I
think
we'll
just
move
on
to
that
to
the
next
thing
new
contributor
workshop.
Let's
see,
I
think
alison,
do
you
wanna
take
this
one.
F
Oh
hello,
so
new
contributor
workshops,
so
the
current
status
of
the
new
contributor
workshop
is
that
everyone
is
signed
up
like
this
well
in
terms
of
how
it's
voting
we've
got
most,
if
not
all,
of
the
different
segments,
we're
planning
to
record
they've
been
all
signed
up
for
and
now
we
need
to
set
a
deadline
in
terms
of
when
we
should
have
things
recorded
by.
A
B
That
yeah,
that
we
wanted
to
have
at
least
everything
but
the
recording
by
the
end
of
the
month
october.
That
is
you
know,
so
for
people
who
are
revising,
slides,
etc,
to
to
at
least
have
that
by
the
end
of
october.
A
G
So
I
submitted
a
a
a
segment
idea
on
that
doodle
bob
that
you
sent
out
there
yesterday.
I
think
it
was
I'm
just
wondering
just
checking
in
to
see
if
you
got
it.
A
A
A
Okay
need
to
know
chairs
list,
I
think
most
times
we
start
talking.
There's
the
issue
triage
and
the
survey
stuff
and
a
few
other
like
little
notes.
But
does
anyone
have
any
other
things
they
want
to
possibly
send
out
the.
A
A
Okay
with
that
we'll
kick
over
to
apec
coordinator
update
nikita.
H
Yeah,
so
yang
was
away
for
the
last
few
months
because
he
was
busy
at
his
deja.
Vu
is
back
now
so
yeah
on
that
and
the
last
meeting
we
decided
to
finally
decide
some
deadlines
for
the
blog
post
series,
so
we
we're
targeting
october
8th
for
collecting
responses
we're
reaching
out
to
kubernetes
contributors
in
apac
regions,
and
we
are
gonna,
collect
we're
targeting
october
8th
for
collecting
all
the
responses
and
then
finally
publishing
the
series
by
november
15th
and
some
more
milestones.
A
It
cool
does
anyone
have
any
other
comments
for
apec
coordinator.
A
Okay,
moving
right
along
deaf
stats,.
I
So
short
update
from
my
side,
so
sergey
proposed
a
new
reporting.
So
at
the
moment,
nikita
and
but
another
nikita
are
supporting
him
to
reshape
the
document
and
then
also
reach
out
to
the
six.
And
then
we
will
give
an
update
how
everybody
is
responding
and
so
on.
D
Yeah
so
there's
a
thread
in
the
channel
where
we
talked
about
the
template
for
reaching
out
to
the
chairs
and
leads
with
a
compelling
message,
and
so
I
think
that's
what
jenny
is
working
off
of
with
sergey
right,
yeah,
basically
iterating
on
that,
and
I
gave
them
some
leads
for,
like
no
pun
intended,
but
actual
leads.
Who
might
be
most
receptive
to
this?
D
If
you
also
have
folks
in
mind
for
them
to
talk
to
these
would
be
people
who
you
think
are
going
to
be
receptive
and
interested
in
and
interacting
around
the
data
points
they
would
like
to
access
for
their
sig
for
their
for
their
workflow
and
sig
health.
Please
share
that
information
with
jenny
and
sergey
and
nikita
you
know.
I've
only
been
around
for
a
few
months.
Some
of
you
have
been
around
a
lot
longer.
You
have
longer
relationships,
but
with
those
folks.
So
this
might
be
our
breakthrough
moment
here.
D
And
thanks
to
the
three
of
you
for
all
of
your
efforts,
this
is
really
great
that
we've
really
turned
this
whole
dev
stats
data
issue
into
a
team
effort.
So
well
done.
Oh.
D
Yeah
we've
had
several
people
involved
here,
shaping
the
user
personas
into
something
actionable
so
plus.
D
Too,
and
for
action
items
I
still
need
to
follow
up.
I
don't
know
if
a
camera
bob
wasn't
at
the
meeting,
it
was
september
9th,
but
basically,
you
and
celeste
might
be
able
to
help
us
understand
how
to
embed
charts
on
a
website.
J
K
A
D
Yeah,
of
course,
yeah,
so
so
I'll
do
that
after
the
meeting
okay
and
then
I
don't
think
we
have
nicholas
and
josh
here
today.
Do
we
neither
here,
okay,
I'll,
follow
up
with
them
to
work
on
the
contributor
persona,
so
this
would
be
basically
you
know
anybody
who's
participating
contributing
code.
What
data
would
they
like
to
see
and
same
with
paris
for
stir
co?
D
We
might
have
covered
most
of
that
through
the
chairs
and
leads
work
that
jenny,
sergey
nikita
are
doing
so
I
would
just
think
it
might
be
a
slightly
expanded
version
of
that
persona
and
then,
finally,
there
was
this
note
that
laura
might
be
a
good
person
for
us
to
add
a
small
company's
element
to
the
existing
open
source
program
manager
persona.
So,
basically,
what
would
that
person
want
to
see
in
terms
of
data?
What
would
they
want
to
have
readily
accessible?
I
don't
know
laura
who
is,
can
someone
offline?
D
Joel
is
fascinated
by
this:
yes
join
our
party,
so.
J
I
I
I
will
dive
back
in.
I
got
pulled
into
some
other
stuff
and
I
I
feel
bad
because
I
made
some
commitments
and
then
ghosted
pretty
effectively,
but
I'll
come
back
and
follow
him.
A
Here
I
know
they're
revisiting
the
multi-channel
communications,
workflow
plan
and
sort
of
just
a
continuing
ongoing
business
at
the
moment.
A
Excuse
me,
let's
see,
and
that
takes
us
over
to
contributor
documentation,
contributor
guide.
A
Rin
has
been
going
through
and
updating
each
page
as
part
of
the
season
of
docs
program,
and
this
is
just
applying
a
style
guide
to
give
everything
a
consistent
tone
and
voice
outside
of
that.
There
isn't
too
many
updates
there
that
should
we
kick
it
over
to
developer,
guide.
L
We
haven't
made
any
updates
to
the
developer
guide
since
the
last
pull
request
got
integrated.
I
don't
think,
but
I
do
know
that
the
end-to-end
testing
part
of
the
developer
guide
is
probably
gonna
need
some
more
updates
really
soon,
since
the
cube,
test2
stuff
is
still
kind
of
like
congealing,
and
I
don't
know
anything
about,
I
guess
what
I
need
to
do
is
go
talk
to
some
sig
testing
people
and
figure
out
what
their
plans
are
for
the
next
release
to
see
what
would
need
to
be
updated.
A
A
There
were
a
lot
of
flake
and
testing
issues
that
occurred
during
the
later
half
of
the
119
release,
so
the
the
the
better
documentation
we
can
write-
or
even
you
know,
just
any
documentation
when
it
comes
to
to
testing
and
best
practices,
will
probably
have
a
very
large
impact.
So
that's,
okay,
those
are
big
ones.
There.
L
All
right
I'll
take
a
look.
It
yeah,
the
the
the
testing
stuff,
is
really
fascinating
and
I
mean
cube
test
two.
It
looks
like
they're
using
it
now,
but
it's
not
even
done
so
that
seemed
it
so
I'll
I'll,
look
and
see
what
I
can
do.
M
M
A
Awesome,
thank
you.
I
actually,
I
remember
jordan,
mentioning
it
at
one
point,
but
I
I
don't
know
how
widespread
you
know.
It
was
one
thing
with
like
youtube
videos,
especially
if
they
don't
have
like
many
comments
on
them.
They
aren't
super
discoverable.
That's
probably
like
docs
makes
it
a
lot
easier.
M
M
L
Good
idea,
okay,
cool
I'll,
take
a
look
at
that
and
see
if
any
of
that
can
be
integrated
into
the
documentation
and
what
we
can
do.
A
Okay,
other
little
win
is
the
blog
post
went
live.
You
know
I'm
this
week
on
monday.
L
Cool,
well,
I
hope
that
it
gets
I
I
hope
that
it
gets
a
lot
of
traffic.
A
Then
yeah
the
it's
cross
post
on
raise
the
I
o
will
will
go
out
tomorrow.
Yes,
tomorrow.
J
This
might
be
just
before
we
move
off
the
topic.
This
might
not
be
the
right
place,
so
maybe
bob
you
can
just
provide
guidance
as
to
where
but
it'd
be
interesting
to
kind
of
look
at
how
to
improve
the
workflow
of
how
changes
trigger
documentation
changes.
So
you
don't
get
so
far
behind
in
the
future.
A
Yeah
we
can.
We
can
definitely
chat
a
little
bit
about
that.
I've
talked
to
a
few
other
sort
of
key
maintainers
on
the
project
about
that
too
in
the
past.
So
that's
something
we
can
definitely
sink
on.
A
Contributor
site
outside
of
the
blog
post,
there
isn't
too
much
going
on
there
at
the
moment.
Its
goals
are
still
the
same.
We
want
to
surface
more
stuff
there.
One
actually
key
thing
is
that
looking
at
the
metrics,
people
have
definitely
been
using
the
release
page.
So
if
you
go
to
kate's
dot,
dev
slash
release,
that
is,
that
is
getting
significant
traffic,
which
is
which
is
nice
and
okay
that
takes
us
to
github
management
nikita.
Do
you
want
to
take
this
one.
H
Why
don't
you
take
the
first
one
at
last
one,
so
the
cube
aws
reaper
was
the
last
incubator
that
was
the
last
data
reaper
in
the
kubernetes
incubator
oil,
so
that
got
archived
an
incubator
is
also
being
rolled
out
as
we
speak,
so
that
will
be
done
today.
Finally,
after
I
don't
know
two
years
or
something,
so
that's
that's
pretty
good
and
yeah.
Why
are
you
reading
the
first
two
points,
because
I
know
you've
been
working
on
those.
A
Okay,
big
thing
is
later
today:
the
new
issue-
triage
workflow,
not
just
issues
triage
workflow-
will
be
rolling
out
to
kubernetes
kubernetes.
You
might
have
seen
the
email
to
catev
about
that.
Essentially,
all
new
issues
and
prs
will
have
a
needs
triage
label.
This
is
intended
to
be
used
by
sigs
for
their
issue
triage
processes.
A
It
does
not
block
prs
being
merged.
That's
one
of
the
the
big
things
to
remember.
I
do
expect
us
to
probably
want
doing
a
little
bit
more
outreach
and
how
to
use
that
label
properly.
I
know
some
groups
are
already
interested
in
integrating
it
with
their.
Oh,
I'm
totally
blanking
on
the
name
name
of
the
triage
party.
There
we
go,
I'm
integrating
it
with
with
the
triage
party.
D
So
keep
me
in
the
loop
on
that,
because
I've
also
been
collecting
data
around
which
things
are
currently
doing
any
sort
of
triage
and
meeting
with
them
one
by
one
when
they
are
interested
to
go
over
that
and
help
them
sort
out
their
triage
process.
Definitely
I
think,
together
we
can
really
make
make.
K
A
Okay,
other
update,
github
related
update
is
that
at
this
point
in
time
we
are
not
going
to
be
naming
our
default
branch
and
github
from
master
domain,
just
at
this
point
in
time,
after
syncing
with
github
and
discussing
a
little
bit
further
until
we
can
actually
fully
test
it,
we
just
don't
want
to
do
it
at
this
point.
A
There
are
some
other
complications
like
we'd
also
have
to
update
our
or
what
you
might
call
it.
A
A
A
couple
quick,
open
items
we'll
see
this
a
little
bit
more,
not
just
zoom,
but
like
all
our
community
management
tools,
we're
going
to
be
going
through
and
auditing
who
has
access?
Are
they
still
active
or
do
they
still
want
to
be
an
admin
in
for
the
the
past
a
couple
months,
it's
sort
of
just
fallen
on
to
a
couple
of
us
to
handle
a
lot
of
that
stuff.
A
A
A
A
A
A
I
should
be
shout
out
and
then
like
thanks,
for
you
know,
you
know
nikita
for
always
offering,
like
you
know,
awesome
reviews,
and
then
that
will
bubble
up
in
her
like
user
hover
card
and
also
be
viewable
at
the
repo
level,
with
the
eventual
intention
of
being
able
to
aggregate
them
aggregate
them
up
to
the
org,
as
well
as
having
them
be
visible
on
the
user
profile.
A
A
If
there
are
other
repos
that
are
interested
in
it,
we'll
be
sending
out
like
an
email
to
kdev
to
see
if
more
people
are
interested
in
opting
in,
but
for
now
that's
sort
of
our
our
goal
with
it.
A
A
Oh,
that's
I'm
going
to
do
this
for
my
audio
system,
one
sec.
A
A
A
So
you
pop
in
here
you
know
we
closed
a
113
issues
in
prs.
There's
only
18
left
open.
So
all
in
all,
I
think,
like
that's
a
pretty
good
win.
If
we
look
at
like
sort
of
our
past
history
with
going
through
all
this
stuff
and
some
of
the
open
items
honestly
can
should
probably
actually
be
closed.
A
And
what
I
would
actually
like
to
do
to
start
the
120
milestone
has
been
opened
and
we
can
go
through
each
one
of
these
and
sort
of
see
if
we
want
to
bump
them
off
to
the
120
milestone.
If
we
can
think
we
can
get
them
done
essentially
by
the
end
of
the
year
or
you
know,
putting
in
the
the
backlog
and
milestone.
A
I
think
this
was
done
lori,
you
got
your
the
the
big
pr
in
a
while
ago.
Updating
one
of
this
stuff.
What.
A
D
Maybe
you-
and
I
should
just
sync
tomorrow
or
friday
and
then
just
create
our
game
plan.
A
A
Check
permissions
on
all
the
mailing
lists.
I
believe
this
is
actually
done.
A
There's
yeah,
so
the
security
audit
one
has
been
closed
down
for
the
most
part
and
the
only
one
is
the
policy
working
group,
and
at
this
point
I
I
hate
to
sort
of
look
over
in
your
direction
nikita.
That
is
a
steering
issue
because
they
have
not
been
responding
to
us
at
all.
H
Yeah
christoph
has
been
planning
to
follow
up
with
them.
A
A
A
E
D
A
2019
survey
results
honestly.
I
think
this
is
something
we
just
close.
It's
a
bit
too
late
to
actually
have
a
blog
post.
This
might
be
something
we
roll
into
the
next.
A
D
I
can't
remember
what
the
survey
contains
if
it's
about
anything
workflow
related
like
I.
I
don't
remember
if
I
ever
looked
at
it,
but
if
there's
anything
we
don't
have
to
go
over
it
right
now,
but
if
there's
anything
related
to
the
workflow
efforts
we're
pursuing
at
the
moment,
that
might
be
helpful
but
like
a
source
material.
A
Yeah,
so
you
can
find
the
survey
results
in
the
contributor
experience
directory
and
surveys.
It
does
cover
some
workflow
type
things
and
what's
the
priorities
for
like
you
know
what
people
find
useful
documentation
has
been
number
one,
but
as
this
is
just
really
focusing
at
this
point
on
posting
the
results.
Oh.
A
A
Then
pr
lifecycle,
stats,
automation
and
leadership
notifications.
This
is
sort
of
an
ongoing
effort.
Oh
lori,
you've
you've
done
some
work
in
this
space.
I've
done
some
work
in
the
split
this
space.
A
few
others
have.
D
A
A
Okay,
I'll
bump
this
off
to
you,
120.
one
thing
we
might
want
to
consider
is
just
sort
of
like
going
back
into
this
issue
and
deciding
what
done
actually
is
because
I
don't
think.
E
A
The
next
two
are
both
regarding
oh
one,
sec,
my
screen
locked.
A
Are
both
related
to
getting
splain
set
up?
We
held
off
on
this
for
a
while,
because
spain
has
been
fairly
unreliable.
We
can
probably
move
forward
with
it
again
and
sort
of
see
what
happens.
We've
also
sort
of
been
on
the
side,
looking
at
other
potential
options.
E
A
Yeah,
I
I
think
at
this
point
with
the
when
the
pr
is
merged
later
today.
We
can
call
this
one
done.
A
Improved
process
for
requesting
zoom
youtube
automation.
We
we
punted
this
one
because
splain
was
having
problems
and
it's
sort
of
lumped
in
with
the
other
ones.
I
will
we
do
plan
on
revisiting
this
stuff,
so
I
will
bump
it
over
to.
A
1.20.
this
I'm
thinking
honestly,
we
just
close
it's
sort
of
been
an
ongoing
thing
without
much
in
terms
of
you
know,
there's
like
checklist
items
here,
some
things
that
are
essentially
like
out
of
like
we.
We
can't
necessarily
do
we've
pinged
people
about
them.
A
J
A
A
I
am
thinking
retitling
this
and
moving
it
over
to
the
120
milestone
just
for
updating,
essentially
the
procedure
docs
for.
A
A
A
A
But
I'm
not
sure
if
there
is
any
sort
of
done
state
with
this.
A
What
do
folks
think.
H
I'm
meeting
with
addison,
so
I
can
check
with
her
and
see
if
we
can
come
to
a
consensus
at
our
intensity
or
we
could
just
place
it
out
to
start
work.
Okay,.
A
A
Contributor
bill
of
rights-
I
remember
I
remember
this
coming
up
a
while
ago.
Essentially
I
think
it
was
defining
the
escalation
paths
nikki.
I
know
you
and
I
talked
about
it
a
while
ago.
H
Why
don't
we
bump
it
over
just
to
at
least
see
you
if
we
can
close
it?
Okay,
what
we
can
do
to
close
it.
H
A
Yes,
the
only
thing
is
we.
We
do
technically
need
to
update
our
zoom
guidelines
now
to
include
a
passcode,
but
that
is
a
separate
issue.
A
A
A
I
I
do
think
this
is
sort
of
a
duplicate
of
our
current
new
contributor
workshop
stuff.
A
A
Transition-
I
th
this
one,
so
this
is
mostly
actually
a
github
admin
team
thing.
I
believe.
A
A
A
This
one
going
to
punt
to
the
next
milestone
and
I'm
at
the
baseline
expectations,
I'm
actually
just
going
to
go
ahead
and
move
over.
There
is
what
I
would
like
to.
A
A
So
we
have,
we
have
five
minutes
left
to
clean
today's
meeting.
We
did
kind
of
take
it
up
a
lot
with
just
getting
through
our
weekly
work,
just
because
we
missed
last
week.
A
A
A
Okay,
we
will
call
it
there
then.
A
Thanks
all,
I
know
it's
not
the
the
the
most
fun
part
of
attending
these
meetings
going
through
the
issue
backlog-
and
you
know
eventually
we'll
get
to
looking
at
the
boards,
but
that
should
hopefully
be
a
bit
better.
Once
we
clean
up
some
of
the
issues.
A
I
want
that
we'll
call
it
done,
and
I
will
see
you
all
in
slack
or
at
next
week's
meeting.