►
From YouTube: Kubernetes Community Meeting 20180125
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
(Sound missing for first 30 seconds, but kicks in right after, sorry about that!)
Notes: https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
B
All
right,
hi
everyone,
my
name,
is
Mario
Lauria
I
will
be
hosting
this
meeting
on
January
25th
2018
I
am
basin
and
I
ruin.
Michigan
I
work
for
a
little
web
company
that
helps
host
web
properties
for
small
medium-sized
businesses
and
I
work
on
kubernetes,
which
we're
using
to
build
the
foundations
as
we
go
toward
the
future.
So
thank
you
George
for
inviting
me
to
do
this
and
let's
get
started
with
a
demo
on
cue
to
hit
ROM
rather.
B
Yeah
we
can
see
that,
and
just
one
quick
note
please
be
mindful
of
your
life
and
needs
like
we
can
hear
these
beautiful
people
talking
as
presenting.
Thank
you.
Okay,.
C
So
before
we
actually
get
started
with
cube
toolkit,
there's
a
small
little
package
that
I'd
like
to
show
you.
It's
called
cube,
exact
and
basically,
if
you're
familiar
with
OS
exec
from
Galang.
This
does
exactly
that,
but
for
remote
community
spots,
so
the
API
is
strikingly
similar
to
OS
exact.
You
define
the
commands,
you
specify
the
standard
into
standard
output
or
standard
error,
and
there
you
just
run
your
command.
So
essentially.
C
C
C
C
C
Essentially,
what
it
wants
it
to
be:
it's
a
toolkit
for
creating
gr
pc-based
alliance
for
ladies,
so
essentially
awesome
tool
for
ladies,
for
example,
cube
CTL
helmet
draft.
These
are
CLI
based
tools
with
the
server
side
component
in
kubernetes,
and
there
are
also
some
other
projects
that
have
also
web-based
in
Poland.
So,
for
example,
for
helm,
there's
a
monocular
component,
that's
a
web-based
component
that
interacts
with
the
with
the
tiller
server.
C
Now
what
this
tries
to
do
is
basically
help
you
get
started
much
faster
with
your
kubernetes
tool
and
not
have
to
worry
about
the
setting
up
the
gr,
PC
client
or
the
server
setting
up
the
communication
between
that.
What
you
do
with
cogeneration
for
the
web
tool
and
stuff
like
that.
So
essentially
it
comes
out-of-the-box.
C
You
have
a
CLI
client,
sorry,
okay,
so
out
out
of
the
box,
you
have
golang
CLI,
it's
a
Cobra
CLI
that
connects
to
a
a
RPC
server
that
sits
in
a
kubernetes
pod
and
basically,
they
talk
through
kubernetes
tunnels,
just
like
helm
does
and
if
you're
familiar
with
helm
or
draft
architecture.
This
would
be
very
very
familiar.
C
At
least
the
client
in
the
server
part,
and
on
top
of
that
there's
also
a
web
dashboard
and
for
the
communication
between
the
web
dashboard
and
the
ER
PC
server,
we
use
gr,
PC
gateway,
it's
a
project
that
creates
a
reverse
proxy
so
that
for
every
J
RPC
service
that
you
create,
you
can
also
automatically
generate
the
gateway,
an
HTTP
gateway.
So
you
don't
have
to
write
another
API
or
write
another
client
that
talks
to
the
server
back.
So,
as
I
said,
the
client
interacts
with
the
server
with
through
job
through
tunnels.
C
C
C
And
it's
now
created:
this
is
the
one
and
essentially,
from
this
point
on,
you
can
interact
with
the
with
it
through
through
the
command
line
interface.
So
there's
a
debug
flag
that
tells
you
to
which
part
it's
talking
to
and
which
local
port
it's
using
for
the
for
the
tunnel
and
essentially
all
it
does
it's
it's
print.
It
prints
the
diversion.
You
can
also
do
a
gr
PC
streaming
with
just
the
implementation
detail
right
now.
C
The
server
is
streaming
data
back
to
the
client
and
basically,
from
this
point
on,
you
only
have
to
implement
your
own
functionality.
There's
you
don't
need
to
worry
about
creating
the
communication
and
doing
channels
and
stuff
like
that,
there's
also
a
proxy
command.
That
starts
a
proxy
back
to
the
dashboards
pod
back
to
the
dashboard
container
and
allows
you
to
access
the
dashboard
on
localhost,
so
proxy.
You
can
specify
the
port
and
right
now
it
started
a
localhost.
C
And
at
this
point
it's
only
the
version
command
implemented
and
it
talks
back
to
the
G
RPC
server
that
educates
the
requests.
So
what
you
would
want
to
do.
You
would
want
to
extend
this
at
this
point.
It's
only
a
starting
point
and
let's
take
a
look
a
little
at
what's
in
the
box,
so
as
I
said,
there's
D.
C
So
if
you
want
to
extend
it
first,
you
have
to
look
at
the
B
protobuf
definition,
and
this
is
the
string
command.
It's
simply
an
RPC
server
stream.
One
note
at
this
point:
it's
using
the
G
RPC
Gateway
project
that
I
mentioned
earlier.
This
is
while
the
gr
PC
web
project,
it's
still
in
private
preview,
so
it's
not
available
to
use
to
use
right
now,
once
the
G
RPC
web
project
is
out.
C
Basically,
we
will
switch
the
G
RPC
gateway
to
just
Jerry
PC
web
and
we'll
be
able
to
do
streaming
on
the
JavaScript
client
as
well.
So,
basically,
if
you
want
to
add
your
functionality,
you
add
it
in
the
protobuf.
You
had
your
method
description,
you
specify
if
you
want
to
expose
it
as
HTTP
as
well,
and
at
this
point
all
we
have
to
do
is
implement
another
command.
This
is
how
the
version
command
is
implemented.
It's
strikingly
similar
to
what
helm
and
drafter
doing
it's
a
simplified
version
of
that
you
implement
the
client.
C
You
also
have
to
implement
the
server.
This
is
basically
the
gate
version
command.
It's
basically
once
you
have
this
project
up
and
running
extending
it
should
not
be
that
difficult.
This
will
also
create
the
swagger
definition,
open,
API
definition
for
you.
So
this
is
automatically
generated
by
this
swagger
code
generator
and,
together
with
the
swagger
definition,
you
also
get
the
typescript
and
angular
code
code
generated
client
and
basically,
all
you
have
to
do
to
extend
the
functionality
is
add
a
new
Cobra
command
and
add
the
new
angular
components
and
that's
pretty
much
it.
C
Everything
else
is
automatically
created
for
you
and
you
can
take
a
look
at
the
makefile.
It's
creates
the
generated
client
for
you,
so
this
is
just
a
toolkit
for
starting
awesome.
Next
kubernetes
tools.
So
if
you
have
any
sort
of
questions,
I'll
be
around
I'll
post
the
links
for
both
projects
on
the
chat
and
just
give
me
any
questions.
If
you
have
thanks.
B
B
D
C
D
The
OCI
and
other
community
work
for
IBM
I
wanted
to
take
just
a
few
minutes
to
make
folks
aware
of
a
unique
opportunity
for
the
kubernetes
SIG's
to
take
advantage
of
related
to
a
very
developer
centric
conference
that
IBM's
hosting
in
the
Bay
Area
next
month
called
index
and
with
that
I'll
throw
a
link
to
the
index
conference
up
in
the
chat.
The
whole
purpose
behind
this
conference
is
to
do
an
unconference.
If
you
will
it's
not
a
typical
IBM
big-tent
brand
related
conference
to
promote
IBM.
D
This
is
a
developer
conference
where
IBM
secured
space
in
the
Moscone
West
the
trap,
chairs,
there's
seven
or
eight
tracks.
Most
of
the
track
hosts
are
non
IBM
developers.
The
tracks
themselves
are
all
focused
on
a
variety
of
talk
topics
across
you
know,
cloud
native,
but
also
a
I,
know,
jazz
foundation
and
all
sorts
of
other
tracked
areas
that
are
of
interest
to
developers.
That's
happening
on
days,
one
and
two
of
the
conference
on
February,
21st
and
22nd
on
day
zero.
D
The
day
before
the
conference,
IBM
is
hosting
some
workshops,
but
also
making
a
big
outreach
to
the
communities
and
offering
significant
resource
in
the
form
of
space
and
the
Moscone
Center
to
hold
whatever
the
community
wants
to
do
so.
I've
been
working
for
the
last
month
or
more
engaging
with
communities
as
wide-ranging
as
Cloud
Foundry,
the
CNC
F,
but
also
others
like
the
open,
API
initiative
associated
with
their
swagger
project,
and
we've
got
a
great
amount
of
interest
in
reaction
and
amount
of
participation.
D
So
what
we're
proposing
for
the
kubernetes
community
is
to
do
a
meet
the
cigs
type
of
kubernetes
community
day
and
sarah
Novotny
is
kindly
agreed
to
act
as
a
keynote
speaker
for
this
community
day
event.
We've
got
a
room:
that's
about
70
by
45
in
the
Moscone
it'll
be
set
up
with
multiple
roundtables
and
so
far
we've
got
the
docks.
Zig
and
we've
also
got
significant
interest
from
that
contra
Beck's.
D
To
consider
joining
we'd
like
to
have
as
many
accommodate
as
many
SIG's
as
we
can
from
the
community
from
the
community,
and
at
that
time
the
cigs
will
be
able
to.
You
know
get
greater
awareness
for
what
their
sig
is
about
and,
at
the
same
time,
people
that
have
been
engaging
in
the
community's
community
and
are
kind
of
ready
to
kick
it
up
to
the
next
level
can
show
up
for
this
community
day
for
kubernetes
SIG's.
D
D
Flyby
I'll
put
my
information
and
contact
info
up
in
the
chat
as
well,
but
if
I'll
pause
for
a
second
and
see
if
there
are
any
comments
or
questions,
I
know
that
sada
EV
from
IBM
has
been
talking
with
the
country
back
sig
I've
been
working
with
the
docks,
Zig
myself
and
we'd
love
to
have
again
as
many
as
spaces
available
for
the
SIG's
to
take
advantage
of
this
Oh.
A
couple
of
other
highlights
the
as
I
get
ready
to
take
a
question
or
two
the
event:
the
Community
Day
event
on
day.
D
B
E
So
if
you
look
at
a
progress
bar
of
the
the
release,
we're
moving
right
along
and
stop
laughing
at
me,
Parris
and
so
feature
freeze
was
supposed
to
be
this
week,
but
due
to
eighth,
a
bit
of
slowness
and
getting
the
features,
repo
populated
with
all
the
current
things
in
the
milestone
we
are
going
to
head
and
push
it
off
until
next
Monday
and
I'll.
Let
her
do
all
that
ski
take
a
moment
to
talk
about
the
features
process
in
general
and
then
I'll
come
back.
So
even
are
you
here,
I'm.
F
Here,
I'd
just
like
to
mentioned
it,
my
lip,
please
drop
in
anytime
yeah,
so
did
the
bad
news
were
that
we
had
to
push
the
features
phrase
in
a
week,
but
the
good
news
is
that
we
are
really
good,
really
good
feeling
this
week
with
the
features
we
have.
Almost
certain
features
that
a
comment
to
cabinet
is
Wanda
generally
is
they're
all
trapped
in
a
feature
spreadsheet.
It
is
available
in
a
link
in
the
meeting
notes.
Again
it's
a
friendly
reminder
for
everyone.
E
And
just
to
give
a
quick
PSA
on
why
the
feature
process
is
so
important,
so
there
the
features
that
go
into
this
repository
really
feed
out
a
lot
of
other
things,
such
as
how
we
market
the
release
and
share
this
information
with
our
community.
So
it's
not
just
a
bunch
of
administrivia
to
serve
some
unknown
purpose.
This
is
really
important
to
the
health
of
the
release
in
our
communities,
so
the
the
features
repo
is
where
we
really
keep
the
record
of
note
on
what
delivery
in
terms
of
major
functionality,
initiatives
are
coming
out
of
SIG's.
E
So
this
is
the
the
direct
pipeline
between
what's
delivered
and
how
the
community
sees
it.
So
again
when
SIG's
participate
in
this
and
provide
more
information
and
help
us
understand
what's
going
to
the
release,
it
helps
us
also
raise
the
awareness
for
SIG's
and
get
more
contributors,
and
it's
a
really
nice
positive
feedback
loop.
E
That's
pretty
much
it
for
the
110
release
on
behalf
of
MIDI
Balu,
who
did
the
when
I'm
to
release.
Thank
you
that
is
really
great.
A
shout
out
all
the
patch
managers
of
current
and
past.
It
is
a
very
long
nine-month
slog
to
be
a
patch
manager.
So
if
you
see
a
patch
manager
around
give
them
the
thanks,
because
it
is
a
very
long
tenure
as
far
as
volunteering
for
that
position,
so
thank
you
to
Metis
and
way
check
and
in
and
gosh
there's
so
many.
Thank
you
all.
E
G
B
G
G
So
we
have
been
stat
set
up
with
sort
of
like
regular
expression
based
parsing
to
look
at
the
first
half
and
derive
the
same
from
that
look
at
the
second
half
and
derive
category
from
that.
So,
if
I
flip
back
to
depth
stats,
maybe
this
makes
a
little
more
sense
where
I
can
see
that
I
have
the
eight
different
categories
on
the
right
and
then
the
second
graph
here
shows
what
those
categories
are
for
a
specific
city.
G
This
graph
is
not
a
hundred
percent
where
I
want
it
to
be,
but
it's
getting
there
the
reason.
The
reason
I
wanted
to
see
this
graph,
just
personally
speaking,
is
I
all
right.
This
is
my
personal
opinion,
not
necessarily
the
opinion
of
the
kubernetes
compute
community,
nor
my
employer
I
think
that's
way
too
many
freakin
github
teams.
This
is
18
times,
however
many
six
we
have,
which
means
I,
think
if
we
have
like
36,
if
I
click
to
kubernetes
and
I
look
at
teams
here,
that's
296
github
teams
for
577
people.
G
G
Now
the
graph
I'd
love
to
be
able
to
show
you,
which
I
kind
of
can't
so
much
is
like
which
SIG's
are
using,
which
of
these
categories,
the
most
so
like
good
job.
The
stakes
here
using
poll
requests
review,
but
unfortunately,
for
me
to
find
which
cigs
are
contributing
to
this
total
graph,
the
most
I
kind
of
have
to
flip
through
this
sig
box.
Here
first
I'm
going
to
change
it
to
aggregate
by
month,
instead
of
a
moving
average
and
then
next
I'm.
Pretty
sure.
G
Cli
was
one
of
the
larger
ones
that
started
using
CLI
significantly
more
than
anything
else,
so
this
was
me
sort
of
cheating
ahead
of
time
and
knowing
that
they
do
that
this
seems
like
a
really
useful
convention.
The
other.
The
misc
thing
is
honestly
again,
it's
the
one
that
I
use
personally
to
like
get
somebody's
attention.
G
If
I
have
a
question
around
like
hey,
is
this
a
good
idea
or
shoot
me
close
this
that's
most
off
on
the
team
that
I'm
personally
using
and
there's
also
like
the
bug
team
or,
like
hey,
I,
think
there's
a
bug
here
now,
I'm
pretty
sure.
The
way
we
have
automation
setup
is
that
if
I'm,
a
member
of
kubernetes
and
I
actually
mentioned,
oh
god,
I've
lost
my
place.
G
If
I
mention
one
of
those
specific
categories
like
at
six
CLI
bugs
the
bots
will
actually
automatically
apply
a
label
to
the
issue
as
well,
and
that
label
will
both
be
like
the
same
label
and
okay.
So
that's
it's
kind
of
where
I'm
at
and
georgeous
raised
his
hand
for
so
long.
Even
my
arm
is
feeling
tired
on
his
behalf
and
I've
noticed
the
China's
kind
of
blown
up
so
I'm
going
to
sort
of
stop
it
there.
But
this
has
been
today's
draft
yeah.
A
We
have
three
sig.
We
have
three
sig
updates,
so
I'm
gonna
hard,
this
cut
off
at
30
after
but
real
quick,
a
question.
If
we're
gonna
be
assigning
code
to
SIG's,
and
things
are
responsible
for
that
bit
of
stuff
and
things
that
are
affected.
Oh
so
it
gets
a
site
to
them.
Can
we
just
naturally
lose
the
these
75
things?
I
need
to
CC.
G
And
then
just
penalty
in
assigning
SIG's
is
SIG's,
aren't
people
things
are
made
up
of
people,
but
they're,
not
people
themselves,
so
those
teams
aren't
I
pointed
you
to
are
intended
to
be
used
for
notification
purposes.
Each
of
those
teams
has
at
least
one
user
that,
like
ends
up
Auto
archiving,
all
of
those
messages
to
a
publicly
available
to
uber.
So
the
idea
is,
if
that
this
was
intended
to
like
help
with
browning
of
notifications
to
the
right
yeah.
A
I
I
get
that
it
just
feels.
It
just
feels
to
me
that
a
lot
of
people
have
found
bankruptcy
on
their
notifications
and
I,
see
it
bugs.
If
it's
just
me,
I'll
shut
up
but
I
see
a
bug.
Sometimes
people
get
confused
and
they
just
CC
them
all
anyway,
and
then
I
look
in
sig
groups
and
it
looks
like
it's
the
same
people
in
all
seven
groups,
so
I'm
just
I'm
wondering
the
value
as
well
like.
G
C
G
They're
used
and
why
they're
used,
but
if
you
are
a
member
of
a
sick,
that's
not
really
using
that
and
you're
not
getting
a
lot
of
value
out
of
it.
I'd
love
to
have
a
discussion
about
this
one,
if
you're
an
IT
staff
mailing
list,
or
maybe
even
the
contributor
experiencing,
because
I
can
say
like
if
I
were
a
name
contributor
to
this
and
I
needed
to
get
somebody's
attention
and
I
had
to
choose
between
one
of
30,
different
SIG's
and
then
I
had
to
choose
between
one
of
eight
different
teams.
G
G
Sign:
okay,
that's
that's
just
great,
so
I'd
like
to
find
a
way
to
to
figure
out
the
counter
to
that
people
who
aren't
actually
using
these
I
want
to
hear
from
you,
people
who
have
found
these
more
effective
and
actually
triaging
routing
notifications.
I
don't
want
to
turn
off
something
that
you
actually
find
useful.
That's
not
my
motives
I'm
here
to
like,
allow
you
to
make
mistakes
and
want
to
meet
what
you
do
so
we
can
go
faster,
and
this
just
seems
like
a
crazy
of
a
point
friction.
G
B
H
So
anybody
that's
not
aware
service
catalog
develops
the
Service
Catalog
incubator
repo,
which
is
an
integration
between
kubernetes
and
brokers
that
implement
the
open,
serviceworker
api
service
broker
is
something
that
offers
a
set
of
capabilities,
and
the
point
of
the
service
catalog
project
is
to
allow
you
to
provision
new
instances
of
those
things
binding
them
in
there
in
your
application,
and
then
you
know
when
you're
done
unbind
and
deep
provision.
So
an
example
of
what
that
is
is
a
service
might
be
database
as
a
service.
H
When
you
provision
it,
you
get
an
instance
of
that
database.
You
get
your
database,
that's
an
instance
of
that
service,
and
when
you
bind
to
that
instance,
you
get
a
connection
string
and
credentials
that
you
need
to
use
the
database
that
you
consume
in
your
app
via
kubernetes
secret.
When
you're
done
you
unbind
and
the
secret
goes
away
and
deprovision
and
the
reefs
the
resources
associated
with
the
instance
of
your
service
go
away.
The
service
broker
handles
implementing
all
of
those
things
and
you
can
plug
any
number
of
brokers
into
the
Service
Catalog.
H
So
I
encourage
all
of
you
to
check
that
out
if
you're
interested
in
the
problem
space
and
thanks
a
lot
Microsoft
for
the
donation,
we're
currently
working
on
improving
code
quality
and
testing
and
have
been
grooming
things
in
our
attitude
o
milestone.
The
big
things
were
kind
of
looking
at
for
the
next
milestone
are
improving
Docs,
improving
the
cube,
CTL
experience
both
with
that
CLI
binary
and
also
by
kind
of
trying
to
move
the
ball
forward
on
the
basic
cube.
Ctl
get
it
get
an
explained.
Experience.
H
Also
a
quote
of
support
and
then
controlling
accesses,
controlling
access
to
services
and
plans.
So,
if
you're
looking
to
get
involved,
it's
a
really
great
time
we're
looking
to
for
folks
to
drive
features
for
the
next
milestone
and
what
we
mean
by
that
is
analyze
the
problem
space
and
make
a
proposal
and
all
forming
consensus
around
that
and
then
implement
or
work
with
somebody
else
to
get
it
implemented.
And
so,
if
you're
interested
in
attending
we'd
love
to
have
you,
our
meetings
are
Mondays
at
4
p.m.
Eastern,
1
p.m.
B
I
I
I
And
in
addition,
in
one
point
and
one
point,
ten
server-side
printing
is
going
to
go
to
beta
I'm,
not
sure
if
the
the
community's
heard
much
about
in
previous
updates
about
the
ktl
proposal
by
a
fill
it
rock,
which
is
a
quite
a
major
change,
discussing
basically
breaking
up
the
monolith
which
is
coop,
cuddle
and
there's
this.
That
still
is
in
the
discussion
of
proposal
stage
and
and
basically
that's
about
all
that
I
have
for
460
Li,
okay,.
G
G
The
first
overview
link
is
a
mail
from
Dan
Khan
to
the
Cuban
any
stead
of
mailing
list,
and
therein
is
a
link
to
a
forum
where
you
can
sign
up
as
presenter
sign
up
a
co-presenter
if
you'd
like
so
on
so
forth,
there
I
also
signed
excuse.
Me
I
also
signed
myself
up
a
couple
other
people
to
do
a
deep
dive
session
on
deaf
stats.
So,
yes,
that's
right.
I
did
this
to
also
selfishly
promote
something
the
deadline.
G
If
you
care
to
register
this
sort
of
thing,
I
personally
found
it
super
fascinating
to
go
to
the
API
missionary
sig
deep
dive
at
last
epic
OOP
common
Austen
I
did
an
e
in
sharing
a
deep
dive
for
sig
testing,
I,
attended,
say,
gaps,
deep
dive,
I
thought
they
were
personally
like
way
more
interesting
than
some
of
the
conference.
If
you
want
to
host
such
a
thing
deadline
is
January
31st
I'm
just
going
to
keep
on
rolling
because
I
happen
to
be
the
next
announcement
item.
Unless
anybody
has
any
questions
on
that
one,
okay,.
G
G
G
B
G
I
did
a
pull
request
to
the
community
repo
to
update
a
gamma
file.
We
regenerated
Docs
and
were
done.
The
decision
was
recorded
in
her
publicly
recorded
meeting,
which
is
posted
to
YouTube,
recognize
that
there's
some
people
who'd
rather
have
like
a
document
to
process.
We
could
follow
going
forward
so
one
of
Eris's
first
action
item
since
the
sigelei
is
to
help
define
and
refine
a
seek
charter
for
contributor
experience.
G
G
J
Thank
You,
Erin,
plus
one
to
everything,
Erin,
said
I'm
on
a
bus
by
the
way.
So
let
me
stop
my
video
really
quick,
plus
one
everything
Erin
said
about
joining
contributor
experience
for
all
things
contributor.
So
one
of
the
things
that
we're
working
on
is
mentoring,
initiatives
and
one
of
those
initiatives
is
a
event
called
meet.
Our
contributors
that'll
happen
at
least
monthly
I'd
like
for
it
to
happen
more
often,
but
that
depends
on
the
amount
of
volunteers
that
we
can
get.
This
will
be
a
30-minute.
J
Ask
us
anything
session
for
contributors
by
contributors
and
then
we'll
end.
The
call
with
a
30-minute
live
peer
code
review.
All
documentation
is
on
the
links
in
the
a
meeting
agenda
today,
looking
for
volunteers
for
two
different
time
zone
sessions,
our
first
time
zone
session
that
starts
at
3:30
p.m.
UTC
is
full,
but
would
love
to
have
more
contributors
on
the
9
p.m.
UTC
time
and
the
signup
form.
That's
a
work
in
progress
is
on
the
agenda
as
well.
J
E
Just
briefly,
I
wasn't
even
gonna
think
about
bringing
up
it
since
we
talked
about
the
contributes
thing
to
I
wanted
to
mention
that,
true
to
the
truth
of
what
was
said,
there's
not
a
real
formalized
process,
but
so
what?
Where
I
could
send
out
an
email
to
the
the
sig?
And
there
was
some
discussion
on
it
and
it
looked
like
it
was
ratified.
K
K
Add
really
quick,
I,
don't
know
if
it
was
announced
in
this
meeting
or
previous
one,
but
we
also
had
a
sig
lead
change
in
cig
scheduling
and
I.
Think
one
of
the
topics
that
came
up
is
there
is
no
formal
process
for
how
we
make
these
changes.
Maybe
in
the
future
there
should
be,
but
Bobby
Salamah
replaced
David
Oppenheimer
as
sig
scheduling,
co-lead.
G
All
right,
I'll,
totally
I'll,
speak
to
it
as
a
steering
committee
member
but
I'm
not
on
like
the
subcommittee.
Yes,
that's
right.
We
have
subcommittees
now
it's
great
it's
working
on
this,
so
it
rock
and
Joe
and
Michelle
in
the
rally
would
be
people
talk
to
you
saw
survey
go
out,
sick
leaves
asking
like
what
would
you
say
you
do
here
and
how
do
you
do
it
trying
to
formalize
like
roles
and
stuff,
because
we
recognize
different
SIG's
were
on
different
ways,
and
there
was
also.
C
G
Set
out
to
kubernetes
to
have,
if
you
are
a
participant
and
six
and
have
feedback
of
how
your
sig
is
running
and
what's
working
well
for
you
and
was
not
we're
trying
to
take
all
of
that
and
compile
like
best
practices.
Maybe
like
a
choose,
your
own
sake,
adventure
type
of
thing,
roughly
speaking,
I,
think
like
every
sink,
should
ultimately
have
a
charter
that
describes
what
the
sake
does
and
what
the
roles
are
within
the
sig
and
some
idea
of
governance
so
like.
How
does
your
cig
want
to
decide
how
to
choose
leads?
G
Do
you
want
the
concept
of
like
terms
for
sickly
and
stuff,
like
that?
I,
don't
think
we're
gonna
try
and
like
enforce
one
common
standard
that
all
states
must
adhere
to
in
terms
of
the
how,
but
it
might
be
like
a
what
like.
So
you
know
today
how
we
sort
of
define
that
like
SIG's,
have
leads
and
since
have
meetings,
and
those
leads
need
to
be
at
least
from
two
different
companies,
and
you
have
to
have
at
least
like
a
mission
statement
of
what
you're
saying
is
about
it'll,
probably
be
like.
G
Okay,
now
have
a
blurb
in
there
about
like
how
your
sink
chooses
leads
and
what
does
lead
mean
to
you
and
you're,
sick
and
things
of
that
nature.
So
this
is
totally
a
problem.
You
have
the
power
to
fix
in
your
own
saying
this
is
why
contributor
experience
like
we
did
it
and
then
we
realized.
Oh
wait.
G
We
don't
really
have
a
process,
so
how
about
we
just
document
what
we
just
did
and
then
we'll
go
from
there,
so
that
when
guidelines
do
come
down
from
the
Standing
Committee,
you
may
already
have
all
the
check
boxes
checked,
but
take
everything.
I
said
with
a
grain
of
salt
because
I'm
not
actually
working
on
that.
So.
B
Awesome
Thank,
You,
Aaron,
all
right,
I
think
that's
about
it.
So,
let's
wrap
up
if
anyone
has
any
questions
or
will
not
feel
free
to
think
people
in
chat
or
follow
them
on
Twitter,
etc
and
I
am
Mario
Lauria.
Thank
you.
Everyone
for
welcoming
me
and
coming
on
in
I'm,
at
Mario
pylori
on
Twitter
and
I
hope
to
be
back
one
day
soon.
So
have
a
good
one
yeah
it
hit
the
+1
from
George.
Thank
you
very
much.
Also
I
live
a
mile
away
from
George
and
he's
making
me
help
them
move
stuff
later.