►
From YouTube: Helm Developer Call 201801125
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
So
the
usual
format
for
the
meeting,
which
today
I
should
start
with
the
beginning
right
today
is
January
25th,
the
official
home
developer
call
and
the
official
agenda
for
this
meeting.
As
always
is
people
who
are
core
maintainer,
x'
or
Sega
apps
leads
will
have
a
chance,
as
we
go
around
the
room
to
to
do
they're
sort
of
like
weekly
stand-up,
and
usually
we
have
some
announcements
either
at
the
beginning
or
the
end
of
that,
and
then
we
have
open
discussion.
A
C
No
I'm
here,
I
just
have
my
normal
stand
up
bumping
up
against
this
so
anyway,
just
to
add
on
to
the
discussion
topics.
I
wanted
to
talk
a
little
bit
about,
maybe
like
how
do
we
publicize
our
C's?
That
may
have
prevented
some
of
these,
bugs
that
we
saw
now
with
2.8
and
so
I
just
wanted
to
pull
it
up.
I
had
an
idea
that
I
wanted
to
run
by
everyone
yeah.
C
A
D
E
So
myself
and
Matt
Farina,
the
two
of
us,
went
together.
Impaired
Matt
Farina
was
more
spectating
and
just
kind
of
getting
an
understanding
of
the
release
cutting,
but
we
cut
the
version
to
eight
release
off
the
RC
one
and
then,
as
we
saw,
there's
a
bunch
of
issues
that
are
just
starting
to
pour
in
last
night
and
as
well
as
the
day
before
so
there's
a
couple
of
issues
related
to
1.9
libraries
not
being
able
to
be
used
on
the
1.8
and
all
that
stuff.
E
So
that's
going
on,
but
this
week
has
been
more
issue
triaging
and
the
next
following
week
we're
going
to
be
going
away
to
Bellevue
in
Seattle,
so
we're
not
going
to
be
as
present
but
I'll
be
still
available
on
issue
queue
and
whatnot
and
trying
to
aggressively
review
PRS
and
whatnot,
because
I've
noticed
that
the
PR
queue
is
definitely
something
that
I
want
to
get
a
tackle
on
and
make
sure
that
people
who
are
submitting
stuff
continue
to
submit
stuff
and
contribute
and
there's
the
project
forward.
So
that
is
my
stand
up
for
today.
Michelle.
F
F
I
think
store
money.
Okay,
so,
like
I
get
an
email
every
time
somebody
buys
a
ticket
and
emails
cool.
It's
the
only
reason.
I
use
my
inbox,
but
anyway,
a
44
percent
of
the
available
tickets
for
home
summit
have
been
sold,
and
so
there
is
a
max
capacity
of
20
of
200,
so
we're
gonna
keep
it
at
200.
I!
Think
that's
small
I,
don't
know
correct
me
if
I'm
wrong,
but
anyway
we're
not
trying
to
get
to
100%
or
anything.
I.
F
Just
was
really
excited
that,
like
people
are
so
enthusiastic
about
home
summit,
cuz
I
really
just
thought
it
might
just
be
us
you
guys,
like
just
us
talking
to
each
other.
You
know
people
are,
people
are
excited
and
people
having
different
companies
are
pouring
in
and
speaker
someone
confirms,
and
so
yeah
we'll
continue.
G
Okay,
I
haven't
been
to
one
of
these
in
a
while,
so
I'm
kind
of
just
just
thinking
and
catching
up,
but
yeah
there's
some
interesting
things
going
on
in
the
charts
people
actually
that
Matt
Farina
talked
more
to
that
other
than
that.
G
So
I
actually
commented
on
his
PR
and
I
sent
round
an
email
to
the
chart,
maintainer
'he's
about
this
issue.
One
thing
one
idea
that
I
had
was
to
move
the
common
chart
to
a
different
repository
I.
Don't
really
think
it's
a
good
idea
to
have
it
in
stable,
because
it's
kind
of
a
bad
experience.
If
someone
does
helm,
install
stable,
slash
common
and
it
just
doesn't
work
right
and
also
there
are
some.
G
It
doesn't
really
work
in
the
CI
for
the
task
repo
because
it
obviously
doesn't
install
anything
so
having
a
different
repository
like
tooling
or
libraries
in
the
same
repo
is
kind
of
a
nice
way
to
get
around
that
where
we
can
have
some
specialized
CI
logic
for
those
repositories,
but
it's
still
not
an
incubator.
So
it's
not
seen
as
something
that
isn't
stable.
G
Yeah
and
I
think
to
your
point,
with
the
restriction
of
not
being
able
to
use
an
incubator,
shot,
has
kind
of
stopped
people
from
using
common
at
all.
So
that's
obviously
not
what
we
want
to
do,
and
so
we
should
definitely
figure
out
a
way
to
do
that.
Matt
I
saw
you
mentioned
something
about
the
started
chart.
Well,
maybe
we
can
discuss
this
a
little
bit
more
later,
but
I
yeah.
C
So
once
again,
my
life
has
been
just
home
summit,
we've
been
putting
that
all
together
and
then
I'll
keep
doing
that
for
the
next
foreseeable
future
and
I
should
actually
be
able
to
I
have
to
put
together
finish
putting
together
my
talk.
I
might
reach
out
to
some
of
you
who
were
more
involved
with
helm
to
just
give
at
least
a
once-over
to
my
whole
CRD
proposal,
thing
and
I'll
be
doing
at
home
summit.
C
Just
so,
I
can
get
a
second
set
of
eyes
and
avoid
some
basic
discussion
points
that
I
would
have
caught
had
I
talked
to
people
before
so
I'll
be
doing
that,
and
then
I'll
probably
be
trying
to
take
some
more
beers
after
that.
So
next
week,
I'm
hoping
that
I
should
have
some
more
time
to
start
pulling
on
the
that
thread
and
seen
what
I
can
do
and
then
I
think.
That's
it.
So
that's
all
I
have
Michelle
got
the
rest
of
the
helm
summit
stuff
and,
let's
see
who
hasn't
gone.
D
Yet
so,
to
give
an
update,
I
was
issue
Sherpa
this
week,
so
was
did
a
bunch
of
triaging,
and
there
were
quite
a
few
issues
that
came
in
got
some
help
from
Fisher
as
well.
So
thanks
for
being
on
it
when,
when
I
wasn't
able
to
be
on
it
being
in
the
European
time
zone,
in
addition
to
that,
I
am
in
Germany
this
week
telling
the
rest
of
the
team
here
at
SU
say
about
Helmand
and
how
to
use
it
and
when
and
why
to
use
it
and
folks
have
been
very
excited
and
are
interested.
D
D
B
So
this
week
obviously
found
along
as
we
did
a
release
for
helm
to
learn
how
that
process
works.
It's
nicely
documented
the
one
thing
that
I
noticed
and
it
crept
up
because
I've
been
playing
around
with
PGP
keys
and
things
like
that
is,
and
there's
a
actually
issue
open
about
signing
home
releases
and
so
I've
been
poking
at.
How
could
we
do
that
and
then
how
do
some
of
the
other
processes
work
like
Apache
or
since
we're
part
of
the
Linux
Foundation?
B
B
We
might
have
to
wait
until
Adam
comes
back
to
understand
some
of
this
because
she's
the
one
who
dealt
with
that,
but
it's
a
complicated
web
we
weave
and
trying
to
dig
in
and
then
at
least
help
get
some
of
that,
and
so
that's
been
mostly
my
time.
I'm
a
chart
side.
It's
it's
a
lot
of
the
usual
stuff,
although
we
are
starting
to
document
more
of
our
processes
over
on
charts.
So
that
way
people
have
a
clearer
understanding
of
how
you
do
stuff
and
why
you
do
stuff
and
why
things
are
that
way?
B
B
So
that
way
we
can
track
you
down
on
issues
and
stuff
like
that
stuff,
like
that
we're
starting
to
get
more
documentation
around
these
things
on
what
we
want
to
see
above
and
beyond
the
normal
helm
stuff,
and
so
hopefully
that
will
help
enable
more
people
who
end
up
and
owner's
files
to
have
a
clearer
idea
of
our
expectations.
Stuff,
like
that
yeah
Aaron
has
an
HP,
Cloud
mug,
all
right,
and
so
that's
the
stuff
that
I've
been
kind
of
working
on
I've
got
three
and.
A
A
A
H
H
A
A
A
D
B
I
noticed
a
number
of
things
in
there
are
outdated
and
need
to
be
updated,
like
there's
a
ton
old
sections
on
handling
code
of
conduct,
stuff
and
now
kubernetes
has
that
fairly
well
established,
and
so
that
section
is
just
not
needed
anymore,
and
so
the
question
is,
is
when
we
update
it
and
put
it
somewhere,
should
it
be
checked
into
the
home
project
somewhere?
Where
should
we
stick
that.
E
B
E
E
A
contributing
markdown,
but
that
one's
more
towards
people
who
are
new
at
contributing,
not
necessarily
core
maintainers
and
then
is
there
like
a
Doc's
hacking
in
hell,
because
I
know,
there's
a
release
checklist
in
there,
which
is
more
developers
or
core
maintainer
centric.
That
might
be
a
good
like
in
Docs,
slash
contributing
which
is
not
included
in
Docs.
Tom
thought:
oh
Sh.
As
far
as
I
know,.
C
F
A
B
A
E
H
C
C
Put
zoom
in
gallery
view:
I
never
knew
that.
Well,
thank
you.
I'll!
Do
that
next
time.
So
the
the
other
thing
with
that
is
that
I
just
want
to.
Let
you
guys
know
we
will
be
doing
a
Q&A
with
all
the
core,
maintainer
x'
and
so
I
just
was
making
sure
all
of
you
were
okay
with
that
and
I'm
thinking.
What
we're
gonna
do
is
have
we're
trying
to
find
a
moderator
right
now
Michelle's
looking
around,
so
am
I
because
we
want
to
get
possibly
someone
non-microsoft
if
it's
all
possible.
C
Well,
not
because
we
don't
like
you
guys,
but
because
Microsoft
is
sponsoring
this
and
so
hey,
let's
spread
the
love,
so
we're
looking
for
a
that's,
not
a
bad
idea,
but
sure
I
like
that
idea
and
then
yeah
Michelle.
That
was
the
other
one
Michelle
just
put
in
the
chat.
The
other
thing
we
were
also
talking
about
one
of
the
emeritus,
the
emeritus
maintain
errs
and
so
like
I
was
thinking
like
Miguel,
because
I
think
Miguel's
gonna,
be
there
yeah
anyway.
C
We'll
talk
a
little
bit
more
about
that
offline,
but
basically
we'll
be
talking,
we'll
have
open,
Q&A
and
then
I'll
talk
to
whoever
we
choose
for
our
for
our
moderator
to
kind
of
have
any
like
questions
that
could
guide
as
well.
So
we'll
talk
it
over
amongst
the
rest
of
us
who
are
organizing
this
and
pick
one
but
Scott
Rigby
was
a
good
idea.
That's
a
good
one
to
throw
in
action.
We
can
discuss
it
and
I.
Think
that's
it
for
that
helm,
summit
stuff.
Is
there
anything
I
missed
Michelle.
H
F
There
was
one
thing
that
I
actually
haven't
discussed
with
even
you
Taylor
yeah,
that
I
noticed
on
the
schedule.
We
have
an
unconference
session
and
so
like
will
hold
what
the
work
it's.
The
working
groups
were
like
on
conference
style,
so
we'll
want
someone
to
like
lead
the
organization
of
the
unconference,
and
so,
if
anyone
has
experience
doing
that
and
wants
to
do
that-
or
it
doesn't
have
an
experience
and
like
just
as
really
excited
about
it,
just
like
reach
out
to
him
or
Taylor
and
we'll
coordinate
with
you
on
that.
C
C
A
C
Rc
thing,
which
is
mine,
I,
was
just
proposing
the
idea
of
maybe
I'll
start
in
just
a
helm.
Users
channel,
but
I
want
to
just
kind
of
start
collecting
a
group
of
like
basically
how
empower
users
are
people
who
are
willing
to
try
out
the
new
RC
s,
so
we
can
publicize
it
with
like
a
mailing
list
and
so
I
would
need
help,
probably
creating
a
Google
Group
in
the
proper
fashion,
Michelle
or
butcher.
Whoever's
done
that
before.
C
F
So
I
did
one
thing
that
I
signed
up
to
do,
which
was
contact
Dan
about
the
mailing
list
situation
and
he
said
that
they're
transferring
CMC
up
to
groups
at
I/o
and
so
we'll
get
off
the
you
know
having
to
have
a
gmail
account,
excuse
Google,
Groups
groups
and
stuff.
So
they
said
just
like
hang
on,
don't
do
the
Google
group
thing
just
yeah
and
just
like.
Let
us
do
a
group
stuff
and
then
we'll
make
some
mailing
lists
for
you.
And
so
that's
the
thing
that's
happening.
Who.
B
C
B
Yeah
yeah
I
really
like
the
idea
of
getting
it
out
there,
and
maybe
there
are
more
ways
we
can
get
to
folks
because
catching
this
last
one
with
the
bugs
were
a
problem
and
so
yeah
getting
that
folks
who
are
ready
to
test
and
maybe
I,
don't
know
if
there's
a
way
to
publicize
it.
Instead
of
just
you
know
a
couple
of
tweets,
but
there
are
other
ways
to
say:
go
get
this
RC
I!
Think
kubernetes
has
some
of
these
same
problems,
and
so
it's
not
unusual.
B
C
Open
to
any
of
the
other
ideas,
but
I
was
just
gonna
start
with
at
least
a
mailing
list
and
grabbing
some
people
who
I
could
put
on
there
just
knowing
like
who
they
are,
and
then
companies
as
well
like.
Oh,
we
know
that
Susa,
for
example,
would
be
willing
to
try
it
that,
like
those
the
types
of
things
I
want
to
gather
and
then
we
can
make
sure
people
know
about
it.
So
this.
B
Reminds
me
of
one
of
the
other
things
that
were
brought
up
along
the
way
is
when
you're
running
an
RC.
If
you
grab
a
stable
chart,
it
doesn't
want
to
install
due
to
some
poor
constraints
with
tiller
versions.
We
should
probably
figure
out
something
there
so
that
people
can
go
ahead
and
just
use
things
like
their
regular
old
charts
without
having
to
specify
a
specific
tiller
version
to
catch
an
RC.
So
we
should
probably
deal
with
that.
B
E
And
so
just
on
this
topic,
what
we're
talking
about
the
2.8
release?
Should
we
be
recommending
for
the
time
being
that
anyone
who
is
on
kubernetes
1.8
do
not
use
the
2.8
release.
It
should
only
be
people
who
want
to
use
helm.
2.8
should
be
on
kubernetes
1.9,
because
it
seems
like
1.9
compatibility.
Support
seems
to
be
working
just
fine.
G
B
B
It's
when
upgrading
it
looks
like
it's
the
internal
code.
We
have
in
home,
that's
dealing
with
a
patch,
and
so,
when
we're
doing
a
patch,
it's
the
API,
it's
not
even
calling
out
to
the
server
it's
the
code,
we're
importing
that's
generating
air,
and
so
this
is
until
ur,
somewhere,
there's
being
generated,
not
in
its
communications
to
kubernetes.
C
D
A
So
we
just
need
to,
and
Adam
will
be
back
and
we
can.
We
can
get
his
expertise
back
in
here
and
that'll
help
all
right.
It's
11:00
and
I
know
a
lot
of
us
have
to
have
to
bail.
So
thank
you
all
for
coming
this
week,
Aaron
I!
If
you
really,
if
you'd
like
to
discuss
that
stuff
I
know,
we
would
that's
something
we
can
try
and
get
for
sure
on
the
agenda.
So
we
can
talk
about
it
and
again
next
week
about
half
of
us
will
be
gone
all
site
meeting,
so
I'm.