►
From YouTube: Kubernetes SIG Contributor Experience 20190417
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
A
A
B
Session
was
similar
over
a
hundred
people,
I
think
our
last
three
or
four
events
have
gone
over
a
hundred,
so
we're
reaching
some
kind
of
thing
here.
A
little
bit
I
do
want
to
add,
is
I
did
file
a
ticket
for
CN
CF
that
these
we
would
like
to
request
like
a
slide
like
when
you're
sitting
at
cute
card.
You
know,
and
they
show
those
slides
to
kind
of
get
more
eyeballs
on
the
programs,
and
things
like
that,
so
things
are
looking
pretty
good
with
that.
B
A
C
I'd
say
just
to
remind
people
to
sign
up
for
the
contributor
summit.
I
think
it's
one
of
the
recurring
items
on
there.
Yeah.
A
D
So,
on
Monday
this
week
we
spent
a
lot
of
time
going
over
the
columns
for
Barcelona,
so
making
sure
that
we
have
the
the
right
comms
going
out
in
advance
to
all
the
attendees
people
who
are
attending
the
workshop
or
attending
the
the
cig
face-to-face
meetings,
making
sure
that
all
volunteers
know
what
they're
doing
we
spent
a
lot
of
time
going
over.
That
I
were
still
finalizing
that
so
that's
not
complete,
yet
contributor
summit
right
now
has
202
people
approved
by
my
last
count.
D
We've
got
30
people
for
the
one-on-one
session
and
44
for
the
201
session,
and
we
got
a
crazy
number
of
people
joining
us
for
Sunday,
which
is
a
hundred
and
eighty
four
people
joining
us
on
Sunday
for
the
the
little
celebration
there
so
with
this
is
really
good.
We
also
talked
to
Deb
regarding
how
many
people
are
registered
for
the
event
and
we're
roughly
halfway
there.
D
So
I
think
we'll
we'll
see
a
little
spurt
here
in
in
registrations
as
well
for
sig
face
to
faces
dawn,
has
updated
the
issue
tracking
that
we
now
have
confirmation
regarding
times
for
all
sig
face
to
face
meetings.
So
we
will
be
updating
sched
with
that
information
shortly
and
I.
Think
that's
it
for
now.
A
A
A
A
So
we've
got
one
thing
in
block:
I,
don't
think:
there's
gonna
be
any
movement
on
that
for
a
while
I'm
gonna,
I'm
gonna
take
a
look
at
that
issue
and
see
if
we
can
just
move
that
back
to
like
not
in
progress,
because
it's
just
it's
just
not
being
prioritized
right
now.
So
as
we
need
to
speak
about
a
recurring
Liam
block
going
into
our
in
progress
stuff,
the
slack
impre
sub
project
into
contributor
experience.
I
know:
there's
been
some
updates
there.
F
Yeah
I'll
do
it
so
the
project
also
known
as
temp
Ellis,
which
is
I
believe,
is
it
Greek
for
lazy.
Aka
slacker
is
in
full
effect.
So
right
now
we
have
already
been
submitting
PRS
to
create
channels
and
create
user
groups.
So
we've
created
a
YouTube
admin
user
group
and
a
zoom
admin
user
group.
We
have
also
delegated
control
of
all
sig
Docs
star
sig
Docs.
F
F
We
were
I
I,
think.
As
far
as
like
contra
Bex
and
slack
infer
goes,
we
were
still
trying
to
figure
out
where
the
project
or
officially
make
it
a
sub
project
and
I
think
we
were
waiting
on
Paris
and
LC
to
give
a
+1
in
that
PR
am
I,
remembering
this
right,
I
think
so
yep.
It
is
linked
in
the
notes,
excellent.
F
What
is
upcoming
as
far
as
slack
infra
goes.
We
are
also
looking
ways
to
let
people
link
their
github
identity
to
their
slack
identity.
It
will
be
entirely
optional,
but
currently,
if
we
create
a
user
group,
we
actually
require
the
the
github
username
of
the
person
and
we
link
it
in
a
file
called
the
users
DML
to
their
machine-readable
slack
ID,
which
is
like
this
7
or
8
character.
String.
G
Their
thing
on
the
sub-project
I
feel
like
when
I
originally
proposed
this
sub
project,
I
included
both
the
Reaper
name
and
the
fact
that
it
would
be
a
separate
project
called
slack
infra
and
I
got
plus
ones
from
I.
Guess
else:
II
didn't
explicitly
+1
it,
but
I
got
plus
ones
from
everybody
else.
Who
is
a
tech
lead
in
Paris
and
nobody
objected
and
I
waited
over
72
hours
and
I'm
curious?
Why
we're
revisiting
this
decision.
H
F
G
We're
we're
over
by
exciting
we
can
move
on
I.
Just
like
mine
was
a
process.
Question
I
thought
I,
went
through
the
process
and
was
confused
about
what
I
could
have
done
better
to
move
us
forward
more
expediently,
and
it
feels
like
perhaps
I
wasn't
clear
enough
in
both
the
repo
and
the
sub
project
in
the
initial
email
and
I
will
find
a
way
to
highlight
that
the
next
time
I
put
out
a
vote.
A
A
A
G
It
should
be
named,
I
explicitly
haven't
sent
an
email
trying
to
clarify
whether
people
feel
like
it
needs
to
be
renamed
before
taking
it
or
glide.
But
I
would
maybe
that's
something
you
should
do.
Maybe
you
just
do
it
and
ask
for
forgiveness.
I,
don't
know,
I
also
share
the
not
too
strong
feelings.
A
A
H
Regarding
this,
our
project
details
at
60,
ml,
I've,
thinned
Erin
and
Tim
to
ask
if
we
can
close
this
I
think
it's
like
a
decision
from
steering.
If
we
can
place
this
and
regarding
the
working
groups
influence
extra
ammo,
there
are
two
PRS
that
are
still
left
to
be
merged.
One
just
requires
a
route
approval
and
another
is
also
good
to
go,
but
just
requires
a
rebase,
so
I
think
it
can
stay
in
progress,
and
we
can
close
this
out
pretty
soon.
I.
J
A
K
Sauce
out
of
here,
it's
thanks
yeah,
so
on
the
key
Nikita
I
under
on
the
team-building.
Not
much
updates
I
think
we
pretty
much
finalized
on
for
people
so
far,
very
sneaky
done
myself
and
I
forgot
the
member
he's
also
in
the
assignee
here
in
this
issue.
So
we
basically
wanted
whoever
wants
to
be
part
of
the
team
just
assigned
themselves
for
one
of
us
will
assign.
K
So
if
you
scroll
up
crystal
means,
then
you
see
the
fourth
name:
there
100
the
assignee,
oh
I'm,
great
I,
need
yeah
I
think
so
we
have
yeah
right
so
yeah,
the
first
one,
that's
the
name
I
was
trying
to
find
out.
I
think
he
is
also
part
of
the
triage
team
in
release,
so
I
think
for
people.
We
initially
decided
three
to
five
people,
so
I
think
it's
good
enough
team.
We
just
need
to
start
working
so
I'm
trying
to
create
a
triage
guidelines.
K
Can
you
know
customized
to
the
communities,
contributed
experience,
Singh
and
I
know?
Some
more
discussion
is
needed.
There
are
we
creating
a
PR
this
week
with
some
initial
thoughts
and
changes?
You
know
we
already
have
a
triage
guidelines
for
the
bigger
one
right
for
the
Cuban.
It
is
repo
humanistic
abilities,
but
so
it's
big
some
of
this
thing
but
does
not
really
apply.
You
know
what
a
particular
seek
for
country
X,
for
example.
So
what
we
decided
pair
is
Nikita
myself.
K
A
B
A
A
A
L
So
sorry,
my
microphone
was
off.
That
was
me,
so
YouTube
I
have
a
PR
open,
35
42
to
get
like
that.
Youtube
team
all
shaped
up,
I
need
to
apparently
put
it
someplace
else,
and
actually
it
had
committed
correctly,
so
I
might
reach
out
to
for
help
on
that,
because
I
never
followed
this
workflow
before
and
Karen
sue
has
also
volunteered
to
help
with
bumpers.
So
we're
gonna
talk,
that's
radios
and
see
who
can
make
what
wait.
C
L
L
A
Great,
so
there's
nothing
else
on
the
agenda,
so
I
will
open
it
up
to
the
floor.
If
anybody
has
any
topics
they
want
to
raise
or
discuss
now
drop
I
really
just.
H
Have
one
question
I'm
like
looking
at
the
mailing
list,
kubernetes
dev
having
this
discussion
regarding
the
comment
message
like
disallowing
at
mentions
and
keywords
which
closed
issues
and
commit
messages,
so
Josh
I
think
your
else
on
the
call
you
mentioned
that
we
should
yeah.
E
E
Do
it,
anyway,
all
the
time
and
and
it
becomes
a
real
problem
during
the
late
stages
of
the
release,
because
tests
are
broken,
people
submit
fixes
sometimes
even
speculative
fixes,
and
then
those
fixes
don't
work.
But
the
issues
market
is
closed,
which
means
the
release
team
loses
track
of
the
issue
until
they
notice
that
the
test
is
flaking
again
so
and.
E
E
E
A
Yeah,
if
there's
like
it
is
a
specific
proposal
for
how
you'd
like
that
to
look
I,
think
that
that's
definitely
something
that
contra
bucks
would
be
interested
in
and
and
we
can
fact
that
I
would
like
how
much
work
is
that
what
is
the
trade
off
of
such
a
proposal
in
that
kind
of
stuff?
So,
if
release
has
specifics
around
that,
I
think
that
we
should
just
have
that
as
a
separate
component.
G
G
So
it's
it's
in
the
made
milestone,
there's
an
umbrella
issue
that
was
proposed
about
30
days
ago,
and
there
was
much
discussion
by
people
who
were
really
excited
about
the
possibility
of
creating
new
standard-issue
triage
workflow
using
a
label
called
needs.
Sig,
triage
and
I
was
curious,
where
we
were
with
that
I.
K
G
Okay,
cool
I
into
it.
Well,
hey
heads
up
everybody:
the
needs,
re
based
label
is
no
longer
gonna,
be
great,
it's
gonna
be
red
because
it
prevents
merged
and
then
I
realized
needs
kind
and
needs
sake,
also
prevent
merge,
but
only
for
kubernetes
kubernetes
and
then
that
gets
into.
Why
do
we
need
issue?
G
Why
do
we
need
kind
and
stick
labels
on
PRS
and
kubernetes
kubernetes,
and
it
turns
out
that
it's
related,
so
the
release
teams
issued
triage
workflow,
which
led
me
to
this
issue
about
redoing
the
issue,
triage
workflow
for
everything,
and
should
we
make
kind
and
sync
and
priority
labels
for
everything?
Merge
blocking
I
have
no
idea
so
I'm
gonna
stop
and
this
tree
base
is
turning
the
color
red
and
soon
it
will
be
called.
Do
not
merge,
need
three
base.
I'll
talk
to
you
later.
B
B
G
Process
process
did
to
just
put
out
there.
Christoph
I
really
appreciate
you
walking
us
through
the
contributor
experience
project
for,
however,
I
feel
like
that
project
port
is
not
in
sync,
with
the
milestone
called
May,
and
there
are
a
lot
of
issues
in
the
milestone
called
May
I'm.
It's
unclear
to
me
whether
or
not
the
milestone
is
intended
to
be.
If
whether
we're
talking
May,
1st
coop
Connie,
you
may
or
end
of
May
as
the
deadline
for
closing
out
all
these
issues,
but
there
are
a
lot
of
them
in
there.
G
H
General
I
think
we
should
go
through
the
milestone
because
we
have
lots
of
project
for
it's
like
they
have
a
community
management.
We
have
a
good
health
management
project
board
and
we
miss
issues
that
are
on
those
project
boards.
But
if
you
go
through
the
milestone,
we
can
go
through
all
the
relevant
issues.
G
L
H
A
Yeah
I
think
we
got
consensus
around
that.
It's
just
like
crafting
up
the
proposal
of
like.
What's
the
time
horizon,
how
do
we
determine
who's
inactive
and
what
do
we
send
out
and
to
who
about
that
inactivity
like
all
of
that
those
kind
of
pieces
around
it
need
to
just
get
written
down
somewhere.
So
we
have
a
defined
policy
and
that
we
try
it
out.
G
B
B
Like
we
don't
have
to
discuss
it
now,
but
I
don't
know
just
a
reminder:
I
still
would
like
to
go
through
the
Charter
and
be
scope
we
could
set
especially
Anor
like
a
live
vs
code
thing
have
everyone
connect
and,
like
argue
over,
every
single
sentence,
or
we
could
do
that
I,
just
kind
of
wanted
to
say
that
you
know
I'm
still
very
interested
in
making
things
more
explicit
in
there.
If
anyone
else
is
interested
in
doing
that,.
B
J
B
G
This
is
following
up
specifically
on
the
slack
moderation
thing:
I
also
have
a
bone
to
pick
with
them.
Christophe
and
I.
Both
just
came
from
the
Kate's
in
for
working
group,
where
we
I
have
a
bone
to
pick
with
them
around
G,
suite
and
I
think
that
ties
into
some
other
requests
around
automating
user
management,
mailing
list
management
and
stuff.
It
sure
would
be
easier
to
do
this
stuff
with
api's.
G
J
B
F
I
G
Ops
is
fundamentally
an
amazing
model
for
everything,
but
the
scale
of
the
size
of
our
mailing
lists
does
not
mesh
well
with
the
concept
of
a
free,
unpaid,
G,
suite
instance,
and
the
cost
of
all
of
those
users
is
maybe
more
than
this
project
is
willing
to
bear.
So
it's
about
like
finding
the
appropriate
compromise
that
allows
us
to
use
the
right
set
of
api's
for
all
the
things
like
we're
very
much
locked
into
the
use
of
Google
Groups
for
document
editing
for
permissions
and
stuff.
That
seems
to
have
worked
very
well
within
this
community.
G
But
yes,
get-ups
for
all
the
things
I
can
I
can
get
behind
that.
It's
just
about
the
engineering
efforts
actually
implements
that
get-ups,
let
alone
the
operational
effort
to
run
set
pieces
of
infrastructure
if
you're
interested
in
helping
out
with
all
this
WG
kate's
infra,
where
we'll
run
the
slack
stuff,
eventually.