►
From YouTube: Kubernetes Public Steering Committee Meeting 20190328
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
B
E
F
B
B
C
B
E
E
F
So
we
just
received
the
G
suite
from
y'all
it's
contributors
at
kubernetes.
Do
we
thought
that
could
help
us
with
various
things,
so
we're
listed
in
the
proposal
that
I'm
not
gonna
go
through
now,
but
we've
come
into
a
per
ticket
right
now,
where
we
realized
that
Google
support
folks
could
help
us
tremendously
with
coming
up
with
possible
workflows
and
things
that
could
help
us
from
an
operational
perspective,
because
we
have
G
suite
and
as
part
of
paying
for
G
suite.
F
You
get
access
to
support
folks
and
this
kind
of
rolls
into
the
same
with
the
other
community
infrastructure
that
we
manage
with
slack
and
things
like
that.
We
are
operating
proprietary
software
that
has
access
to
support
individuals
that
want
us
to
use
their
tools
right
and
appropriately,
but
we
don't
seem
to
have
like
appropriate
lines
of
communication
to
these
folks
right
now.
F
For
instance,
with
the
G
suite
we
put
in
a
service
the
service
desk
ticket
to
ask
CN
CF
to
help
us
reach
out
to
Google,
because
I'm
not
and
the
contributors
at
is
not
the
primary
on
the
G.
Suite
account
and
Google
will
only
talk
to
people
who
are
primary
points
of
contact
same
with
all
of
our
other
infrastructure
as
well.
F
D
I
joined
us
to
back
parent's
up
on
this.
One
I
actually
run
my
in
on
the
side.
I
run
my
nonprofit
completely
off
of
Google's
G,
suite
and
slack,
and
it's
just
incredibly
convenient.
It
makes
things
much
easier
for
calendaring
and
emails.
I
know,
there's
all
sorts
of
issues
here,
like
you,
don't
want
vanity,
email
addresses
or
anything.
What
I
was
suggesting
is
that
we
have
a
dedicated
G
suite
account
for
each
sig
chair
and
that
chair
is
responsible
for
calendaring
and
taking
email
requests
and
so
forth,
and
setting
up
groups
and
so
forth.
H
E
H
H
D
Yeah
the
issue:
the
issue
is
that,
like
people
are
using
their
personal
email
addresses
for
the
calendars
and
it's
just
it's
a
mess,
and
we
don't
know
where
anything
is
we
don't
have
like
central
Google,
Drive
repositories
for
people
to
find
stuff?
And
you
know
if
this
is
gonna
continue
to
grow.
We
need
to
make
this
an
admitted
process
and
we
need
to
decide
like
we're.
Just
gonna
pay
for
G
suite,
or
are
we
gonna
roll
this
all
ourselves
and
if
we're
gonna
roll
it
all
ourselves,
you
didn't
start
now.
D
E
F
And
we're
fine
doing
the
administrivia
work.
That's
thing
like
the
people
in
the
front
line
want
to
do
the
administrivia
work.
We
just
feel
like
Google
and
other
and
slack,
and
all
these
other
people
that
are
working
the
support
and
the
solutions.
Architects
will
actually
be
able
to
like
architect,
us
out
some
really
cool
stuff
and
like
help
us
with
some
best
practices
of
other,
like
super
large
groups
that
have
that
have
G
suite
and
things
like
that.
I
feel
like
we're.
B
B
B
I
B
To
me,
it
seems
like
we're
kind
of
blocked
on
having
a
conversation
with
the
CNCs
folks,
one
potential
solutions
unless
there's
something
that
we
can
do
here
on
this
call
together.
If
I'm
not
correct,
please
correct
me,
but
if
that
is
the
case,
then
sharing
that
service
desk
account
and
having
brain
and
I
kind
of
jump
in
and
help.
G
I'm
a
little
bit
confused
I
mean:
what
exactly
are
we
asking
for
here?
So
we
want
to.
We
want
to
be
able
to
contact,
Google
support
and
actually
be
able
to
have
a
relationship,
but
is
there
something
concrete
that
we
want
to
ask
Google
support
around
what
I'm
asking
what
I
was
in
for
is
more
accounts.
F
Also
I
want
to
just
give
them
every
I
want
to
give
a
solution
architect.
All
of
in
all
the
inventory
and
everything
that
we're
doing
right
now
to
date
as
far
as
operation
is
concerned,
and
then
we'll
have
someone
go.
No,
actually
you
might
be
better
for
you
to
for
you
to
have
every
sink
chair.
Have
you
know
XYZ,
instead
of
us
trying
to
do
these?
Just
these
like
things
where
we're
throwing
them
out
and
then
failing
and
then
like
having
to
redo
calendars
45
times
a.
E
G
The
thing
that
worries
me
paris
is
that,
like,
I
think,
we're
using
g
suite
in
a
sort
of
non-standard
way
where
we
want
to
use
it
and,
like
we
hit
this
a
bunch
of
different
places
right
we're.
Essentially,
we
want
to
use
it
as
a
place
where
we
can
get
api
hosting
calendars,
post,
mailing
lists
and
but
most
of
the
people
that
are
gonna
be
sort
of
going
through
that
are
going
to
be
at.
That
is
I.
Think
a
bit
of
a
bit
of
a
different
use
case.
G
G
G
H
Regardless
I
think
like
what
we
need
to
get
concrete
about
what
we
need
first,
because
there's
a
lot
of
different
issues
and
it's
really
unclear
even
what
permission
model
we'd
have
in
to
Joe's
point
like
the
G
suite
does
have
a
bunch
of
stuff.
That
also
is
like
sensitive,
like
private
mailing
lists
and
stuff,
and
so
we
just
need
to
make
sure
we
understand
what
the
request
is,
who
needs
administrative
rights
to
what
and
then
we
can
go
from
there.
This
this
conversation,
I,
don't
think,
can
proceed
much
further
and.
F
No
one
is
asking
for
a
more
administrative
rights
like
I.
Think
the
only
thing
I
need
administrative
leer
ight
now
is
for
somebody,
a
Linux
Foundation,
to
tell
Google
that
it's
okay
to
talk
to
me
and
Alex,
and
a
couple
of
people
about
how
our
current
setup
is
and
how
we
can
make
this
better
for
our
SIG's
yeah.
C
G
You
know,
and
and
and
I
get
that
and
I
think
it's
it's
probably
worthwhile
I
guess
what
I'm
trying
to
say
is
I
I
think
we
need
to
be
very
crisp
about
what
we're
looking
for
and
I
think
we
need
to
scale.
Our
expectations
is
what
we're
going
to
get
out
of
a
solution.
Architects,
for,
like
a
you
know,
I
think.
H
G
H
F
The
solution
architect
will
advise
us
if
we
need
more
accounts.
I
mean
I
think,
alex
alex
is
saying
that
he
has.
His
experience
is
eluding
him
to
the
fact
that
we
probably
will
need
more
accounts,
but
his
scale
isn't
necessarily
where
right
now,
but
a
solution
architect
will,
let
us
know
I
mean
we
technically
have
like
40
departments
here
so
like
if
we're
running
this
as
a
business
in
operational
standpoint
like
I,
just
want
other
people
who
are
more
qualified
with
this
stuff
to
help
us
out,
so
that
we're
not
just
continually
making
mistakes
so.
H
F
J
E
It
would
be
helpful
for
the
steering
committee,
as
well
as
for
the
people
who
would
be
involved,
to
have
a
canonical
issue
that
we
can
reference
this
part
of
the
discussion,
because
right
now,
there's
a
lot
of
there
are
bits
of
information,
but
I
don't
have
the
concrete
list
of
the
action.
What
is
the
actual
set
of
issues
that
we
are
trying
to
solve?
I
just
think
it
helps
that
it,
you
know,
educate
everyone
else,
who's
currently
trying
to
understand
the
set
of
problems
that
exist.
H
Okay,
so
to
conclude,
this
conversation
I
think
we
need
to
use
a
concrete
list
of
problems
and
then
get
Michelle
and
I
on
the
service
ticket
and
we'll
try
to
get
either
a
partner,
I'm
alone
expound
ation
to
work
with
paris
to
brainstorm,
how
to
solve
the
problems
and
that
yet
to
be
written
document
or
get
paris
directly
in
touch
through
of
whatever
administrative
contact
update.
We
have
to
do
sounds
like
a
reasonable
plan.
K
F
I
mean
in
this.
This
also
goes
with
slack
too
so
like
if
we
ever
have
a
security
incident
was
slack
like
who
do
we
contact
and
like
anything
else
that
we
pay
for,
like
github
like
or
do
the
people
that
run
github
have
like
the
appropriate
contacts
like
this
is
the
stuff
that
we're
working
on
a
contributor
experience
right
now
with
scaling
our
moderation
and
we're
just
finding
the
pitfalls
in
certain
areas.
So
I
guess
this
is
just
that
I
just
wanted
to
kind
of
bring
this
up.
It's
a
broader
topic
as
well.
F
H
Q4Q
Benetti
I
see
zero
requests
from
as
you
one
request
from
Paris
in
the
kubernetes
request:
queue
in
the
CSS
right
now,
so
either
they're
not
doing
the
right
thing
or
something
messed
up
with
Service
Desk
again
so
again,
could
you
please
take
that
back
or
I
can
send
an
email,
because
every
single
thing
parish
requests
should
end
up
in
these
requests?
You.
F
And
this
is
also
predating
our
like
our
service
deck
artists,
our
need
for
service
desk
tickets
as
well.
It's
just
been
like
I'd,
say
the
last
year
in
general,
with
moderation,
we
just
have
an
issue
with
the
admins
on
the
front
line
being
able
to
move
content,
a
contact
for
whatever
reason,
the
actual
platform
itself.
H
Right
and
I
would
say,
the
state
of
the
art
should
be
the
scenes,
yep
is
being
responsive
and,
if
that's
like,
we
need
to
measure
whether
that's
happening,
and
we
either
need
to
get
this
seen.
So
you
have
to
be
accountable
to
being
responsive
or
we
need
to
figure
out
another
thing:
arrey
no
and
no
data
on
whether
it
being
responsive
or
not
so
could
you
either
gather
that
data
or
yep.
H
C
G
G
Moderation
features
right:
we
could
you
know
we
could
look
at
moving
off
of
mailing
lists
on
to
something
like
discuss.
There's
there's
ways
to
treat
it
like
a
mailing
list.
Similarly,
you
know
slack
is
we're,
obviously
stretching
that
to
its
limits
in
terms
of
what
we
can
do,
there's
no
easy
answer
there
with
respect
to
G
sweet
I
think
you
know,
there's
ways
that
I
think
we
can
make
it
work.
I
mean
I.
Have
a
personal,
G
C
sweet
account
that
I'm
gonna
be
using
in
various
ways,
but
I
think
we
should.
G
G
I
G
B
I
G
G
Of
the
features
that
we're
talking
about
with
G
suite
is
to
actually
use
team
drives
and
you
can't
move
documents
across
organizations
with
teen
drive
so
so
like
as
long
as
people
are
creating
stuff
documents
using
their
their
company
or
even
their
personal
accounts.
We
can't
use
team
drive.
So
that's
just
an
example.
How
that
particular
feature
was
crafted
for
a
use
case
that
doesn't
line
up
with,
with
the
way
that
we
kind.
G
C
M
Our
propensity
to
bike-
that's
all
I,
just
say
I'm
like
we
have.
We
have
invested
time
in
trying
to
look
around
at
our
available
options,
and
this
is
what
we
have
landed
on
with
a
documented
proposal.
And
yes,
this
is
why
we
would
now
like
to
talk
to
you
the
experts
to
figure
out
how
to
make
the
best
use
of
our
product,
accepting
that
it
might
be
a
little
weird
and
wonky.
They
probably
have
more
subject
that
subject
matter
expertise
than
we
do,
and
we
should
let
them
like
shed.
C
Something
that
we
may
have
to
change
our
processes
to
fit
our
requests
and
our
our
tools-
and
that
may
be
the
case,
but
let's
not
change
the
multiple
times,
which
is
what
I
think
Paris's
concern
is.
Is
we
have
tried
a
number
of
different
ways
and
broken
them
a
number
of
times?
So
now
we
really
need
to
bring
in
the
experts.
J
H
E
E
Good
once
twice
three
times
all
right,
you're
good
doors,
past
the
next
one
is
for
those
who
worked
on
steering
car.
Last
time
we
decided
that
we
were
missing
some
milestones,
some
arbitrary
lines
in
the
sand
or
dates
that
we
could
set
that
serves
as
a
forcing
function
for
us
to
rally
and
execution
behind
things,
because
we
had
to
take
propensity
to
just
kind
of
move
things
along
over
time.
So
I
grid
the
backlog
created
a
milestone,
they're
all
pretty
and
colorful
and
I
was
going
to
walk
through
the
ones
that
are
currently
active
today.
E
So
any
questions
there
before
I
start
going
through
it,
so
I
will
walk
through
the
active
ones,
currently
formalized
sub
projects.
We
talked
about
this
I
had
a
request
and
Erin
did
a
PR
to
add
that
capability
and
I
know
that
dims.
You
also
did
a
PR,
which
was
a
little
bit
more
than
that
and
Brian
had
a
comments
talking
back
north
Nikita.
M
L
L
Yeah,
this
is
a
sign
to
me
if
possible,
I'd
like
to
actually
have
someone
from
the
Navy
community
lead
it
and
then
I
can
help
them.
I've
developed
documentation
for
different
governance
pieces
already,
and
this
might
be
a
good
opportunity
to
someone
to
gain
experience
in
this
type
of
work.
I,
don't
know
if.
M
L
L
L
M
E
E
Angier
side
Kim
are
gonna,
give
an
update
during
the
next
steering
committee
meeting
we've
been
talking
and
conversing
about
their
proposals
that
they
have
and
they
want
to
just
basically
give
an
update
to
the
steering
committee.
For
the
most
part,
the
TLDR
from
the
community
perspective
is
that
most
of
the
car
providers
I
think
all
the
co-operators
are
bought
in
and
they
agree
to
the
idea
of
collapsing
and
to
having
mini
sub
projects
and
the
single
sink.
So
things
look
like
they're
on
track.
There
are
there
questions.
G
E
Exactly
last
but
not
least,
was
community
resource
management.
That
kind
of
falls
underneath
that
larger
umbrella.
That
Paris
was
talking
about
earlier,
but
I
think
this
one
was
like
documenting
the
homes
who
actually
hands
the
credentials
and
details
here
was:
was
there
any
update
to
this
Paris?
We.
F
Have
all
of
that
all
of
that
kind
of
documentation
located
inside
of
the
community
folder
and
she's
made
the
communication
folder
inside
of
the
community
repo
I'll
get
the
link
right
now,
I
feel
like
between
that
and
all
of
the
moderation
docs
that
we've
done
recently.
This
meets
the
criteria
for
what
you're
looking
for,
maybe
but
on
getting
that
out
right
now
and
pace
it
and
to
zoom
Chad.
M
I've
had
one
minor
question
that
may
be
answered
by
that
I.
Don't
know
it
feels
like
we
own
most
of
our
assets,
except
for
a
few
things
that
the
CNC
essence
and
I
was
interested.
I
was
trying
to
is
poking
around
the
block
the
other
day
and
it
seems
like
docks,
owns
the
machinery
for
it
and
contradicts
has
some
influence
over
it,
but
both
of
those
explicitly
call
it
out
of
scope.
M
There
is
no
place
that
explicitly
says
who
owns
the
content
on
the
block,
so
I'm,
assuming
it's
like
a
list
of
people
in
the
owners
file
in
the
blog
directory,
and
it
seems
like
those
are
all
linux
foundation.
People
I
just
wanted
to
say
that
out
loud
and
make
sure
we
all
agree
that
that's
the
appropriate
thing
and
that's
correct
the.
D
M
G
M
G
M
M
G
Yeah
and
I
think
some
of
that
is,
like
you
know.
Theoretically,
if
the
steering
committee
wanted
to
actually,
you
know,
exercise
editorial
control
over
the
blog
that
would
officially
be
under
the
purview
of
the
steering
committee
I'm
guessing,
but
because
it's
not
assigned
to
a
sig
and
like
the
Linux
Foundation
does
what
the
Linux
Foundation
does
like.
Where
is
that
reporting
line
of
control
responsibility
oversight
around?
That
is
that
is
that
kind
of
what
you're
getting
at
Erin?
Yes,.
B
So
Erin
do
you:
wanna
should
be
file
a
service.
That's
to
get
your
request,
control
of
the
content
of
the
Cabrini's,
but
I.
Don't.
M
Know
if
I'm
I
don't
know
if
this
needs
a
service
desk
ticket
like
I'm,
happy
to
go,
take
it
to
see
Docs
and
ask
them
I
just
felt
like
it
was
a
useful
discussion
to
have
a
steering
level,
because
I
think
it
is
really
informal
and
the
content
is
run
by
community
members.
I
hear
Dan's
assertion
that
by
having
the
people
who
have
final
say,
work
for
a
vendor,
neutral
organization
helps
ensure
that
the
content
is
vendor
neutral,
but
I
feel
like.
M
We
have
a
wide
variety
of
chairs
and
a
wide
variety
of
SIG's,
and
thus
far,
this
project
has
managed
to
remain
pretty
vendor
neutral,
so
I'd
be
willing
to
trust
any
other.
Chair
of
cig
docks,
not
just
Zack,
because
he
happens
to
work
for
the
Linux
Foundation.
If
I'm
the
only
person
back
off
of
that
man.
I
In
Aaron,
I
didn't
mean
to
imply,
it
was
necessary.
I
was
just
stating
the
way.
It's
worked,
the
last
two
years,
essentially
since
Google
handed
over
control,
the
bob
ski
thing
was
just
an
artifact
of
the
fact
that
he
used
to
be
in
charge
of
it,
and
so
I
mean
it
seems
natural
to
me
fur
to
become
a
subgroup
of
sick
dogs.
Okay,.
G
A
Meat
I'd
like
to
see
her
in
Caitlin's
behalf,
because
we've
discussed
a
blog
that
I
know
she
at
least
would
love
to
have
community
members.
Volunteering
to
help
review
potential
blog
posts.
They've
got
quite
a
backlog
because
nobody's
been
working
on
that,
then
the
so
taking
ownership
of
it.
If
we
don't,
if
nobody's
going
to
staff,
it
is
not
really
gonna
change
things.
I.
D
Guess
I
should
throw
my
hat
in
here.
I
mean
the
reason
I
joined
the
the
all.
These
SIG's
is
to
do
good
blog
stuff
I
mean
if
there
is
no
direct.
If
this
all
flushes
out
and
nobody
else
is
willing
to
do
it,
you
can
hand
this
all
to
me
and
I
can
take
it
over
I've.
Just
I
only
just
started
contributing
so
I
felt
weird
volunteering
I
mean.
G
I'll
throw
something
out
there.
Also
it's
like
you
know
it
would
be
great
if
there
was
a
calendar
in
terms
of
stuff
coming
up
and
the
topics
and
sort
of
who's
proposing
it
were
run
by
the
the
steering
committee,
so
that,
like,
if
folks,
had
concerns
they
could
bring
it
up.
I
think
there's
a
difference
between
you
know
I.
These
things,
which
obviously
is
you
know
a
different
motion
from
just
you
know:
hey
are
the
even
the
things
that
we're
covering
on
the
blog
vendor-neutral.
M
G
No,
no
just
to
be
clear,
I
want
to
be
clear.
This
is
this
is
the
type
of
thing
where
everything
is
under
the
steering
committees:
responsibilities
if
we
can't
find
a
sig
to
own
it
and
if
we
don't
get
sunlight
than
it
actually
devolves
to
the
steering
committee,
and
so
the
question
here
is
like
I,
don't
think
we
should
assign
a
single
person
here,
because
there
is
editorial
control
in
terms
of
like
what
are
the
topics
that
the
blog
takes
up
yeah,
and
so
what
I
would
like
to
do
is
like
hey.
G
D
H
D
F
Bernard
has
all
this
which
keeps
a
schedule
she
keep
like
you.
Can
you
can
go
in
right
now
and
see
all
the
blog's
that
are
queued
up,
because
the
the
contribute
to
contribute
to
a
blog,
you
have
to
submit
a
PR,
and
then
she
changes
the
date.
So
I
mean
they
have
a
process
around
this
stuff.
So
I
don't
know
how,
like
maybe
a
steering
committee
can
be
like
added
into
that
process.
If
that's,
what
y'all
are
asking
for?
Oh,
that
is.
E
Pretty
explicit
and
I
understand
what
she
was
getting
at
is
that
usually
we
have
acetate
ership
right
for
lack
of
a
better
term
and
sibility
the
people
and
other
six
come
and
go.
But
at
least
you
have
a
single
location
which
is
shared
either
as
a
sub
project
of
a
sig
where
the
city
itself
that
held
it
has
the
ownership
of
that
artifact
right
and
I.
Think
what
Joe
is
trying
to
ascertain
and
correct
me
if
I'm
wrong
is
that
we
should
not
assign
this
to
one
person.
E
G
G
If
you
want
to
actually
do
a
big
announcement
do
that
on
your
site,
but
let's
make
sure
that
stuff
that
is
very
much
driven
by
vendors
stays
on
on
the
vendors
blog
and
we
don't
actually
have
that
stuff
go
through
the
kubernetes
blog
of
course,
that
that
PR
in
here
so
over
the
course
of
an
hour.
This
was
submitted
and
approved,
and
so
this
is
the
type
of
thing
where
I
think
we
just
got
to
be
very
careful
that,
like
hey,
that's,
hey,
here's
the
new
features
in
1.14
yeah.
H
N
Can't
I
actually
don't
know
the
history
on
that
blog,
but
Joe
is
referencing,
but
like
I
dunno
there's
a
blog
that
I
know
Alex
and
myself
were
working
on
around
like
a
cute
one
14
feature
I
guess
mutton
I
actually
don't
know
how
blogs
get
solicited.
But
my
experience
has
been
that
someone
from
Siena
is
out
to
an
individual
member.
N
D
M
E
So
we
I'm
gonna
request
that,
as
we
have
notes,
please
don't
put
them
in
zoom
chat
if
we're
trying
to
use
the
issues
as
the
canonical
source
of
reference,
because
a
lot
of
times
I'm
trying
to
put
the
data
into
the
issue.
But
that
way
we
can
actually
just
move
forward
with
that
issue
and
have
all
the
data.
Be
there
that's
possible.
Ask.
J
E
E
E
E
B
B
H
B
F
B
Great
just
hearing
a
note
whenever
you
already,
but
if
there's
anything
I
can
do
to
help
100%.
Thank
you.
E
L
Mainly,
you
know,
I
don't
know
about
the
conflict
resolution
part,
but
as
far
as
staffing
gaps
go,
there
are
efforts
to
define
roles.
We
have
the
rule
board
contributor
experiences,
defining
roles.
I
was
saying
to
be
helpful
to
have
some
suggested
rules
for
SIG's
as
part
of
this
a
governance
information
since
many
sit
most
SIG's
have
not
made
much
progress
on
defining
roles.
M
L
I
think
this
issue
was
pulled
out
of.
We
had
a
number
of
umbrella
issues
with
a
bunch
of
backlog
items
around
the
bootstrap
governance
time
before
the
first
election,
and
that
was
broken
down
into
multiple
sub
issues,
but
this
still
had
multiple
points
in
it.
Obviously,
so
it's
not
it
wasn't
really
well
scoped
or
concrete.
I
would
also
be
fine
with
closing
this
in
favor
of
more
specific
issues.
M
M
If
its
technical
conflict
resolution
it
bubbles
up
through
the
spikes,
all
of
the
SIG's
can't
seem
to
agree
it
levels
up
to
steering
or
effort
gaps.
The
biggest
one
on
my
mind,
is
just
running
the
project,
infrastructure
and
that's
being
handled
through
the
community's
infrastructure,
working
group
or
Cades
infra,
and
we
could
very
much
use
dedicated
staff
for
that
and
we
may
find
we
want
to
come
back
and
ask
for
resources
of
LF
for
that
particular
thing.
But
I
think
we
don't
have
that
concrete.
Ask
great.
E
Job
could
we
outline
because
the
one
thing
that
we
can
agree
upon
that
is
currently
a
problem
that
we
don't
actually
have
any
line-of-sight,
none
other
than
we
have
a
role
board
is
to
take
up
documentation
of
just
outlining.
What
are
the
staffing
gaps
are
how
to
rectify
rationalizing
senator
cetera,
I.
L
So
there
are
two
two
levels
that
we've
encountered
this
in
the
past:
one
is,
or
maybe
three
so
one
is
things
that
need
to
be
done
within
SIG's,
where
they're
not
finding
people
to
step
up
and
own
those
tasks,
and
often
that's
just
because
people
can't
see
the
forest
through
the
trees.
So
that's
why
we
created
the
role
board.
Then
there
is
at
the
higher
level
across
the
project
which
SIG's
are
sort
of
in
most
desperate
need
of
help
or
people
for
new
contributors
who
are
trying
to
find
areas
to
contribute.
L
So
in
the
past,
I
had
surveyed
some
cigs
and
you
know
just
posted
to
kubernetes
dead
of
saying,
hey
you'd
like
to
contribute.
Try
one
of
these
areas.
No,
it's
been
a
long
time
since
I
did
that
for
the
UI
there
was
a
special
effort
to
try
to
solicit
help
with
the
UI
as
well.
So
it's
sort
of
sporadic
and
not
very,
not
very
structured
right
now
and
how
we
do
that
and
then
the
third
area
is
things
that
don't
really
fall
under
any
stake.
L
So
the
infra
working
group
is
one
example
about,
and
you
know
we're
trying
to
reduce
the
number
of
things
that
fell
outside
of
all
the
SIG's,
but
there
are
still
a
few
of
those
things
so
I.
You
know
this
specific
issue
is
really
old
and
it
was
derived
from
something
you
get
older.
So
it's
not
super
relevant
or
specific
itself
at
the
moment,
but
we
still
need
to
try
to
keep
improving
in
these
areas.
I
feel
and
the
stopping
come
from,
and
how
are
you
feel
those
so.
B
Brandon,
eat
whelks
and
I
recently
chatted
with
most
well
a
lot
of
CNCs
maintainers,
and
we
just
can
I
did
a
few
calls
and
got
some
feedback,
and
it
just
really
opened
your
eyes
to
a
lot
of
different
things
that
were
happening.
We
don't
necessarily
to
my
knowledge,
have
a
meeting
with
with
the
sig
sig
lead.
Sig
chair.
Excuse
me
so
I
think
it
might
prove
beneficial
to
like
set
up
those
kinds
of
same
calls
with
sig
chairs.
So
we
can
just
gather
some
feedback
about
what
they
need
and
write
some
stuff
down.
B
E
All
right,
we
are
t-minus
two
minutes:
we've
gone
through
everything,
that's
in
the
current
May
29th
and
it
looks
like
we
actually
are
making
progress.
We've
closed
some
issues,
other
things
people
actually
did
help
us
with
so
I,
want
to
call
out
and
give
props
to
Nikita
she's
been
awesome.
She's
been
helping
out
quite
a
bit
on
helping
to
get
these
pieces
of
place
in
the
community
repository
and
also
thanks
to
Paris
too,
as
well
for
help
and
step
up
on
some
of
these
issues.
O
E
I
E
B
Think,
just
because
this
is
a
like
between
it's
it's
an
issue
that
kind
of
like
is
between
the
steering
committee
and
the
CNC
upon
how
things
work
in
terms
of
branding
we
should.
We
should
just
get
like
you
know,
to
some
majority
or,
however,
we
decided
in
our
charter
to
get
like
about
for
this
topic.
Okay,.