►
From YouTube: Kubernetes SIG Service Catalog 2018-06-11
Description
sig-service-catalog proposed charter
security contact maintainer
upstream k8s 1.11 release notes
help-wanted labels
helm chart situation
A
A
So
we
took
the
the
template
from
the
steering
committee
and
then
Jonathan
took
basically
everything
about
how
our
sig
works
today
and
put
it
in
there
and
then
layered
on
top
of
that
and
commits
is
individual
changes
to
that.
That
propose
that
we
do
things
a
little
bit
differently.
Some
of
that
just
brings
us
more
in
line
with
what
has
been
suggested
by
steering
committee
another.
A
It
is
just
like
how
do
we
explain
how
to
do
things
like
a
comma
means
you
become
a
chair,
decide
that
you
hate
Service,
Catalog
entirely
and
run
away.
Things
like
that
are
being
put
into
the
Charter,
we're
using
lazy
consensus
for
this,
or
at
least
trying
to
so.
If
you
follow
the
mailing
list,
you'll
have
seen
the
message
about
that.
So
please
leave
comments
on
that
pull
request
and,
if
you
don't
mind,
I
just
want
to
go
through
like
at
a
high
level,
some
of
the
very
exciting
things
inside
our
Charter.
Oh.
A
A
And
then
otherwise
we
interact
with
the
OSB
working
group
to
kind
of
provide
reality.
Checks
feedback
feature
requests
bugs
that
kind
of
stuff
we
have
maintained
errs.
We
don't
do
what
kubernetes
does
and
the
point
of
this
isn't
to
change
it
to
that
in
the
first
go
if
we'd
like
to
adopt
what
they're
doing,
maybe
that
would
be
in
secondary
steps
to
our
charter.
A
Essentially,
maintainer
x',
you
know
approve,
do
PRS,
do
polar
costs,
help
out
on
slack
and
label
issues
and
bad
new
issues
and
help
people
out
some
of
the
things
that
got
clarified
a
little
bit
in
the
turner
is:
how
do
you
get
to
be
a
maintainer,
so
you're
nominated
by
a
chair?
And
if,
for
some
reason,
someone
isn't
really
doing
the
job
I
mean
here
anymore,
they
can
be
but
not
nominated,
to
be
removed.
A
So
what
are
chairs
chairs
are
maintained,
errs
who
have
an
additional
set
of
project
administrative
roles.
They
are
not
more
awesome
or
powerful
than
a
maintainer.
They
just
have
taken
on
the
care
and
feeding
of
our
seg
to
make
sure
that
we
are
rolling
smoothly
and
they
also
responsible
for
giving
our
updates
to
like
the
sig
community
meeting
SiC
leadership
stuff,
like
that,
a
big
change
that
we
did
is
incorporated
some
of
the
decision-making
processes
from
the
upstream
templates
from
the
steering
committee
how
to
make
decisions.
A
We
kind
of
thing
you
have
like
different
ideas
about
like
sometimes
make
a
decision.
This
way,
sometimes
that
so
I
put
out
there
as
part
of
the
proposal
to
do
lazy
consensus
with
a
fallback
to
1/3
2/3
majority
room
which
I'll
refer
to
later
on
is
lazy,
2/3
and
it
just
for
simplicity's,
so
that
you're
not
always
like.
How
do
we
decide
things
each
time,
this
kind
of
lays
it
out.
You
can
nominate
other
chairs,
nominate
new
cheers.
A
Cheers
can
step
down
if
they
want
to
Andi
they've,
moved
on
their
company
or
gone
somewhere
else
to
do
exciting
things
before
they
step
down.
They
can
submit
somebody
else
and
propose
that
they'd
like
a
replacement
and
they
get
to
vote
on
the
replacement.
But
it's
the
same
thing.
Those
lazy,
two-thirds
chairs
would
need
to
be
active
in
the
project
administration
role.
On
top
of
you
know,
maintainer,
and
if
they
kind
of
do
other
things
were
very
long
for
you
to
time.
The
chairs
could
vote
them
off
the
island
essentially,
and
then
also.
A
A
Erin
suggests
it
emeritus
chairs
the
idea
being
that,
after
someone
is
put
in
and
say
like
two
years
of
hard
labor
on
making
our
sig
amazing
and
keeping
it
rolling
when
they're
ready
to
step
down.
This
is
a
way
to
indicate
and
thank
them
for
all
the
past
service
without
forcing
them
basically
to
cut
off
all
ties
to
the
sig.
They
no
longer
have
chair
responsibilities
or
privileges,
but
they're
still
mentioned,
and
they're
always
welcome
to
hang
with
us
at
UConn
and
stuff
like
that,
and
then
security
contact
is
a
new
role.
A
We
don't
have
one
yet
this
is
something
that
is
being
rolled
out
to
all
the
SIG's,
and
the
text
of
this
is
pretty
much
happy
pace.
A
must
and
should
the
capitalization
of
that
kind
of
stuff,
basically
right
out
of
there
and
they're
the
person
who
essentially
is
on
point
to
hear
top-secret
security
stuff
related
to
our
sig
and
keep
their
mouth
shut
about
it
until
we
can
get
things
patched,
you
want
to
know
more
read
the
embargo
policy.
A
We
really
need
that's
another
thing
on
the
agenda,
but
I'll
just
say
now:
we
really
need
someone
to
to
step
up,
submit
a
pull
request
and
put
their
name
in
here.
You
yeah
maintainer,
in
order
to
be
a
security
contact,
and
that's
it.
So
if
someone
would
like
to
try
that
out,
please
do
so
because
we
can't
really
mark
it
as
down
and
tell
the
leadership
about
that
until
we
get
at
least
one
person
in
their
organizational
management
just
goes
over
how
we've
been
doing
everything
so
far.
A
It
has
that
one
extra
provision
that
we
talked
about
couple
weeks
ago
now
about
when
you're,
representing
the
sig
officially
like
you're,
doing
like
this
is
the
sig
deep-dive
like
uconn,
or
this
is
the
sig
one
come
be
a
contributor
for
our
sig
kind
of
thing.
Give
everyone
else
on
the
in
our
sig
a
chance
to
throw
an
extra
information.
In
fact
check.
Oh
hey!
A
Maybe
you
didn't
know
about
this
as
well,
that
kind
of
thing
so
that
everyone's
pretty
pumped
about
how
we're
being
represented-
and
we
talked
about
our
weekly
releases
and
kind
of
how
we
do
things
our
technical
processes.
This
works
through
like,
for
example,
right
now
use
looks
good
to
me,
1,
&,
2
and
I
know.
We've
talked
about
changing
it
to
do
full
prowl.
Basically,
my
planning
for
now
is
just
a
document
what
we
do
and
whenever
we
managed
to
get
switched
over
to
prowl
we'll
go
through
the
process.
A
A
So
we'd
like
to
get
everyone
who
is
a
chair
access
to
each
one
of
these
things,
so
that
a
chair
can
always
kick
a
build
or
fix
a
messed
up
image
and
Quay,
or
something
like
that
or
or
it's
the
network
I
build
or
things
like
this,
so
we
working
to
fix
that
if
there's
any
other
assets.
Let
me
know
this
is
all
I'm
aware
of
and
that's
it
any
questions
or
concerns
about
the
Charter
people
would
like
to
argue
about
in
real
time.
B
B
A
A
A
B
That's
a
lovely
image:
no
I
just
wanted
to
I
didn't
realise
Paul
was
away,
so
we
can.
We
can
probably
leave
it
until
he's
got
time
to
look
at
it.
I
just
I
I,
don't
I
feel
like
we
discussed
this
in
the
past.
I
just
don't
know
when
and
I
couldn't
find
it
in
our
our
document.
History
and
I
was
just
gonna
close
it,
but
yeah.
You
know
he
has
it
so
I
did
one
who
just
loves
it.
So.
A
B
D
C
E
E
C
A
B
A
I
deal
with
the
lazy
consensus
is
that
if
no
one
says
anything
to
object
and
we
kind
of
address
all
feedback,
then
that's
what
we're
happy
with.
If
they're
still
active
concerns,
we
can
extend
it
or
just
have
a
vote.
There's
a
definition
of
lazy
consensus,
I
thought
but
I'll
link
that
to
to
explain
that's
a
little
better
yeah.
C
Just
gotta
be
a
little
careful
cuz.
It
lazy
consensus
when,
when,
in
the
summer
time
is
a
little
bit
interesting
because
people
going
on
vacation
and
stuff
they
may
not
know
so
it
may
feel
like
we're.
Rushing
things
through
people
when
they're
not
even
around,
to
notice
the
email,
just
something
to
think
about
yeah.
A
Good
point
I-I've
seen
other
SIG's
have
a
really
short
turnaround
like
72
hours
and
I
was
kind
of
leaning
towards
more
like
I'm
in
a
moment
of
two
weeks,
so
that,
like
someone's
out
there
able
to
catch
something
anything
longer
than
that
I
think
almost
we
expect
people
to
be
like
seriously
out
for
a
month
or
longer
than
that.
Maybe
we
need
to
have
them.
C
A
A
Okay,
next
up
sounds
like
this
actually
isn't
a
problem,
but
Nick
chase
was
asking
if
we
had
anything
for
the
1.11
release,
notes
I
honestly
had
no
clue
that
we
ever
had
anything
for
the
release,
notes
so
I'm,
just
gonna.
Let
him
know
we
have
nothing
to
report
at
this
time
and
yeah
leave
it
at
that.
Unless
people
want
to
communicate
something
else.
Morgan.
B
B
A
B
A
How
are
you,
and
then
okay?
So
unless
there's
any
other
things,
if
there
is
ping
Nick
chase,
but
I'll,
let
him
know
about
our
minimum
I
just
want
to
make
people
aware.
I
posted
this
on
the
list
too,
that
we
have
been
top-secret,
Lee
wrote
a
series
of
new
labels
and
ways
of
unborn
a
new
contributors
that
was
so
successful
that
the
rest
of
kubernetes
noticed
and
asked
that
we
write
that
up
for
them
so
that
they
can
adopt
it
or
main
kubernetes
and
encourage
other
things
to
do
the
same.
A
So
there's
now
two
issue:
labels,
Help
Wanted
and
good
first
issue.
We
used
to
call
it
good
first
PR,
but
the
github
standard
is
good
first
issue,
so
we're
gonna
go
with
that
and
the
idea
is
basically
that,
instead
of
marking
something
as
Help
Wanted,
because
we
are
stuck
on
an
issue,
the
the
goal
is
use
it
in
the
more
common
sense
across
github
witches.
A
These
are
great
places
for
people
who
aren't
core
contributors
to
be
able
to
pick
up
an
issue
that
has
been
explained
sufficiently,
that
someone
could
just
jump
in
and
help
with
it.
One
example
is
like
PI,
seeing
with
a
bunch
of
the
CLI
issues,
they're
very
straightforward,
to
be
able
to
say
this
is
the
exact
behavior
and
here's
the
code
and
here's
the
test.
A
So
there
may
be
extra
questions
coming
from
people
working
on
good,
first
issues
and
K
back
for
all
of
this
is
that
we've
done
a
really
great
job
of
having
new
contributors
come
on
in
one
give
us
positive
feedback
and
then
two.
They
are
then
immediately
going
while
that
soft
and
never
coming
back
so
the
investment
on
those
first
couple,
p
ARS,
is
paying
off
and
we're
now
getting
people
coming
back
for
the
second
third
PR
and
kind
of
sticking
around,
which
is
really
the
point
and
putting
in
all
that
extra
work
on
those
issues.
A
So
just
making
me
aware
of
what
they
are.
If
you
see
stuff
that
has
those
labels
and
they
don't
have
any
helpful
information,
though
that
people
would
mean
or
in
chocolate,
either
add
that
in
Florida
strip
that
that
label
off
we're
asking
people
to
do
that
across
all
the
kubernetes
repos.
Actually
they
just
not
even
just
our
sake
so.
C
A
A
It's
definitely
something
that
someone
could
pick
up
without
having
to
ask
for
help
on
the
weekend
and
usually
they're
working
on
the
weekend.
We're
working
on
the
week
so
giving
all
the
questions
answered.
Upfront
makes
these
especially
good.
First
issues
for
people
to
grab
and
work
on.
Does
that
kind
of
clarify
for
you.
C
A
Another
this
is
set
in
stone.
It's
just
basically
sig
sig
contributor
experience
notice
how
many
new
contributors
were
giving
and
said
what
are
y'all
doing
and
so
I
wrote
down
what
we've
been
doing
and
they
were
really
excited
about
it.
I
decided
to
adopt
it.
So
this
is.
This
is
what
we
have
been
doing.
So
that's
a
January
change
for
us
other
than
the
name
of
the
issue
label.
A
Cool
the
plot,
it's
a
intestine
front,
which
plugin
does
the
enforcement
and
it's
not
configured
yet
it's
slash
help
and
it's
explained
in
here
under
commands.
If
you
scroll
up
a
little
bit,
it'll
tell
you
what
the
prowl
commands
are
good
first
issue
and
slash
help
and
it
will
handle
the
fact
that
there
are
subsets
of
each
other.
So
if
you
remove
help
it'll
automatically
remove
the
first
issue
for
you
as
well
I
think
we
would
need
to
turn
that
on
for
ours,
like
I,
think
we
didn't
turn
on
kitten
and
dog.
B
B
J
talked
about
last
couple
of
weeks:
we've
had
problems
with
the
film
chart
because
the
helm
tried
server
was
down
and
the
helm
chart
server
is
down
because
they
moved
to
some
different
system
and
they're,
relying
on
the
projects
to
be
hooked
into
that
yeah.
You
know
your
project
specific
system
and
I've
had
a
discussion
with
thick
this
morning
and
then
I
left
and
we
never
caught
back
up
and
I
didn't
get
him
yet,
but
basically,
there's
we're.
B
Gonna
have
to
have
Travis
call
our
chart
pushy
thing
and
do
that
so
I'm
not
I'm,
not
hundred
percent
sure,
on
what
the
actual
steps
need
to
be
taken.
But
I
think
we
have
access
to
Travis
I,
don't
have
access
to
much
else,
but
I
think
I
have
access
to
Travis.
So
I
can
continue
with
this,
but
he
has
this
document,
so
he
can.
He
was
guy.
He
said
he
might
come
and
leave
notes
and
he
might
leave
APR
on
our
repo
at
some
point.
B
A
B
A
B
Cit
server
that
the
fix
running
anymore
right
right,
that's
that's
what
I'm
I'm
under
the
impression
that
they
took
it
down
because
they're
not
using
it
anymore,
because
they
have
some.
They
have
an
actual
token
that
they
they
hand
out
for
people
to
use
to
to
push
to
that
that
particular
GCS
bucket
or
whatever
it's
called
I.
Don't.
F
F
Pretty
open
this
week,
okay
I
think
it
probably
depends
more
on
nah.
Okay.
How
late
are
you
willing
to
stay
up?
I
guess,
I
I
could
make
a
time
that's
better
for
an
all,
but
I
would
prefer
not
to
go
past.
Like
8
o'clock,
Eastern
Time
in
terms
of
starting
I
could
I
could
do
an
hour
at
eight
o'clock.
Eastern
Time
like
as
probably
the
latest
that
I
could.