►
From YouTube: /lgtm with SIG Release
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
Hello
and
welcome
to
lgtm.
Today
we
are
talking
with
some
members
from
sega
relief
about
contributions
to
the
kubernetes
project.
Before
we
begin
there
is
a
little
bit
of
housekeeping
first.
This
is
an
official
live
stream
event.
That
means
an
official
cntf
live
stream
event
and,
as
such
is
subject
to
the
cncf
code
of
conduct.
So
please
do
not
add
any
chat,
anything
to
the
chat
or
questions
that
would
be
in
violation
of
this
code
of
conduct,
basically
be
nice
and
respectful
of
myself
and
my
guests
and
everyone
else
in
the
chat.
A
Okay.
Now,
as
I
said
today,
we
are
talking
about
sega
release
and
I
have
three
fantastic
members
of
the
team
here
to
talk
to
us.
Could
we
please
just
take
a
wee
moment
to
introduce
each
other,
not
each
other
yourselves
and
we'll
start
with
ray
in
the
corner.
There
look
then
to
saunder
and
then
across
the
devil,
please
ray.
B
C
Hi
everyone-
I
am
so
excited
to
be
here,
so
I
am
based
in
india
and
I
have
recently
graduated
from
my
bachelor's
professionally.
I
am
working
as
a
developer
relations
engineer
at
tendermint,
an
open
source,
blockchain
company.
Apart
from
all
this,
I
am
involved
in
different
open
source
organizations.
C
From
the
past
four
years
I
started
with
mozilla
firefox
got
involved
into
cncf
kubernetes
and
also
recently,
I
started
working
on
css
standardization
in
chromium,
geeko
and
webkit,
the
three
main
browser
engines
yeah
and
in
my
free
time
I
sleep
a
lot
and
you
should.
D
Hello,
everyone.
I
am
really
sorry
if
my
net
is
glitchy,
so
apologies
for
that
in
advance.
I
have
a
bit
of
a
network
issue
going
on
at
my
place
and
we've
just
called
the
guys
to
fix
it.
D
But
notwithstanding
the
network
issues,
I
work
with
hsbc
in
my
day
job
and
I
got
involved
in
the
cncf
sphere
of
things
because
you
know
I
wanted
to
learn
more
about
kubernetes,
so
yeah
mainly
got
involved
with
the
kubernetes
project
as
a
release,
shadow
and
you
know
making
edits
and
documentation,
and
once
that
was
done,
I
guess
you
know
I
got
hooked
on
to
staying
on
in
the
release
team
because
it's
it's
such
an
awesome
place
to
learn
new
things.
D
So
I
was
one
of
the
release:
lead
shadows
in
this
gone
cycle.
That's
1.22
and
we
had
an
awesome.
You
know
time
there
and
yeah.
Apart
from
that,
I
work
on
litmus
chaos
and
love.
Speaking
about
you
know
my
experiences
within
the
projects
specific,
so
yeah,
that's
what.
A
All
right,
thank
you
very
much,
and
and
thank
you
all
for
being
sick
release
members.
I
don't
think
people
really
really
really
appreciate
just
how
much
work
goes
into
cutting
a
new
release
of
the
kubernetes
project
and
I
think
after
today's
conversation
we
can
hopefully
give
people
a
little
bit
of
insight
and
perspective
into
how
this
all
works.
A
B
Sure
so
sig
release
is
a
kubernetes
special
interest
group,
and
the
mission
of
sig
release
is
to
ensure
the
production
of
quality
kubernetes
releases
on
a
reliable
schedule
and
starting
with
1.22.
B
We
changed
to
three
releases
a
year,
cadence
from
four
so
1.22
was
just
released
on
august.
4Th
and
1.23
is
scheduled
to
be
released
on
december
7th
part
of
sharing
high
quality
of
kubernetes
releases.
The
group
is
also
likes
to
maintain
a
consistent
group
of
members
as
well
to
support
the
release
process
because
it
does
take
quite
a
quite
a
bit
to
to
release
kubernetes.
B
A
A
Could
we
be
like
so
I
I
served
on
stick
release?
I
think
it
was
around
12
months
18
months
ago
and
of
memory
of
sergeant
wales.
There
are
different
teams
within
the
sick
release
group
that
all
focus
on
different
responsibilities
for
each
release,
which
groups
were
you
all
members
of,
and
can
you
maybe
share
a
little
bit
about
what
their
responsibilities
were.
C
Yeah
so
in
the
cuban
it
is
1.22.
I
was
a
ci
signal
shadow
where
I
had
to
make
sure
that
the
ci
is
always
green
to
monitor
the
jobs
in
the
dashboard
flag,
any
type
of
blockers,
and
also
to
make
sure
that
all
the
e2e
tests
are
passing
before
this
release.
I
was
part
of
release,
notes
for
1.20
and
1.21,
and
at
that
time
my
duty
was
to
review
and
create
pull
requests
for
every
alpha
beta
minor
release
of
kubernetes.
D
So
I
started
off
with
dogs
really
because
docs
is
something
that
I
really
think
contributes
to.
The
value
of
a
project
in
general,
after
which
I
decided
comms
was
a
much
better
avenue
for
me
to
contribute,
because
I
think
I
mean
at
least
I
feel
that
I
am
a
little
better
at
communication
than
I
am
at
other
aspects
in
the
project.
Currently,
so
I
decided
I'd,
give
it
a
shot
and
I
had
a
really
really
great
mentor,
even
with
dogs,
even
with
firms.
D
So
savita
was
my
first
lead
with
talks
and
she
taught
me
a
lot
about.
You
know
the
whole
documentation
process
within
the
release
within
the
release
of
thing,
and
I
had
a
mentor
in
the
form
of
joseph
for
coms,
after
which
I
transitioned
to
leading
comms
in
the
1.21
cycle
and
in
this
current
cycle
that
just
ended
two
days
back.
I
was
one
of
the
lead
shadows,
which
means
that
I
was
leading.
D
D
Lead
honestly
is
a
lot
more
responsibility
and
I'm
sure
ray
has
a
lot
more
knowledge
than
on
that
because
he's
he
is
the
1.23
lead,
but
it's
it's
a
lot
more
challenging
than
the
individual
roles,
because
it
involves
overseeing
everything
that
is
there
within
the
release,
and
I
got
to
personally
learn
a
lot
more
as
a
release
lead
shadow
than
I
did
when
I
was
a
part
of
either
role.
I
mean
it's,
it's
it's.
D
It
was
like
a
huge
learning
curve
from
being
a
lead
for
a
particular
sub
team
role,
and
you
know
transitioning
to
the
release
lead
shadow.
It
was
a
huge,
huge
learning
curve
for
me,
because
I
got
to
learn
about
all
the
other
aspects
of
the
project,
so
yeah
that
that
was
my
journey
within
cigarettes.
B
Yeah,
so
I
started
with
kubernetes
1.18,
with
the
release
notes
and
with
release
notes
you
collect
and
you
fine-tune
the
release
notes
using
using
a
tool
called
corel,
which
is
the
kubernetes
release
toolkit
there's
a
sub
command
in
krell.
B
It's
called
release,
notes
and
that
actually
came
about
from
118
just
from
shadows
that
actually
worked
on
the
release.
Notes
team
before
it
was
a
different
process,
so
that
118
shadow
team
was
was
actually
took.
The
effort
to
help
with
automating
release
nets
and
developing
that
tool
shout
out
to
adolfo
and
james
from
the
from
the
who
also
shadows
with
me
on
118..
B
I
was,
I
was
kind
of
a
lurker
in
sick
docs
before
joining
the
release
team,
so
that
that
was
pretty
natural
for
me
to
go
to
docs
and
docs
is
responsible
to
coordinate
all
the
documentation
updates
for
it.
For
the
new
release
like
there's
a
new
feature
and
and
that's
go,
that's
alpha
or
changes
in
the
behavior
or
any
features
going
to
ga.
B
There
has
to
be
documentation,
that's
updated
or
feature
gates
as
well,
so
we
make
sure
there's
high
quality
of
standard
for
the
documentation
and
that
it
also
follows
the
the
kubernetes
style
guide.
So
after
docs,
like
I
mentioned,
lead,
docs,
1.21
and
1.22
as
part
of
enhancements
and
enhancements
collates
all
the
enhancements
that
is
targeted
for
the
for
the
release.
So
this
could
be
new
features.
Start
in
alpha
features
might
going
to
beta
graduating
to
ga
or
deprecations
as
well.
B
So
that's
that's
fairly
big,
especially
in
1.22,
so
with
enhancements.
You
also
verified
that
the
enhancements,
which
has
a
proper
kubernetes
enhancement,
a
proposal
called
a
cap
and
make
sure
updated,
is
maintained
properly
and
also
has
a
production
readiness
review
which
up
our
prr
and
make
sure
that
enhancements
merging
into
kubernetes.
It's
that
it's
up
to
you
it's
up
to
you
to
prod
standards,
that's
observable
scalable
and
supportable.
So
so
after
enhancements
someone.23,
I
will
be
the
release
lead
for
1.23.
A
Nice,
I
think
we
heard
a
good
array
of
the
different
teams
there
right
so
docs,
I
think
was
mentioned
a
couple
of
times,
which
I
always
think
is
a
really
fantastic
way
for
people
to
get
involved
with
the
project
without
having
to
write
code.
Kubernetes
is
a
huge
project
and
writing
code,
for
it
can
be
a
bit
cumbersome.
A
A
Ci
signal
you're
brave,
so
yeah.
That's
I
always
found
that
the
most
intimidating
team
within
sick
release
when
I
was
on
it
because
they
just
it
seems
like
they
had
so
much
to
do-
is
that
just
my
perspective
is
wrong,
or
is
it
just?
Is
that
one
of
the
tougher
ones?
Do
you
think.
C
Well,
I
won't
say
it
was
a
tougher
one
personally
for
me
when
I
started
with
1.20
I
I
was
kind
of
a
lost
person.
You
know,
maybe
you
can
say
because
of
the
size
of
the
community.
Everyone
around
you
is
so
experienced
that
feeling
nervous
around
them
is
quite
normal.
Now
so
for
ci
signal,
I
would
say
you
know
you
will
be
you're
going
to
have
a
proper
onboarding.
C
Our
team
lead
is
here
to
help
you
out,
and
you
know
we
rotate
our
duties
weekly
so
that
everyone
knows
you
know
how
they
are
doing.
Also.
It
helps
us
to
not
to
pressurize
over.
You
know
over.
E
C
A
Yeah,
maybe
we
could
dig
into
that
and
I'd
love
to
get
everyone's
perspective
on
it,
but
you
know
signing
up
for
being
a
member
of
secret
release.
Is
that
a
large
time
commitment?
Is
that
something
you
felt
affected
your
job
or
were
you
quite
comfortable,
merging
them
or
mixing
them
or
juggling
them
together
to
keep
things
going?
What's
your
perspective.
C
I
would
say
it's
a
tricky
question,
but
I
would
say
you
know
specifically
for
the
team
leads.
It
is
definitely
a
time
commitment
thing
and
for
the
different
teams.
You
know
you're
not
going
to
have
a
lot
of
work
around
the
whole
three
months
for
some
of
the
teams
it
is
around
the
it
is.
C
You
know
around
the
initial
phase
for
some
of
the
teams,
it
is
around
the
bug,
fixing
phase,
so
you
know
it's
going
to
depend
and
sometimes
there's
a
huge,
a
lot
of
work
that
got
compiled
at
the
last
and
we
somehow
have
to
you
know,
push
and
maybe
take
help
from
other
contributors.
C
So
and
personally
for
me
right
now,
my
graduation
was
going
on
and
I
had
so
many
interviews
this
time.
Definitely
I
missed
so
many
meetings,
yeah.
A
D
So
I
unfortunately
have
never
had
the
opportunity
to
you
know,
work
on
kubernetes
as
an
upstream
contributor
via
my
job,
like
as
part
of
my
job.
I
don't
do
that,
so
I
actually
have
to
take
out
time
specifically
for
anything
that
I
do
within
the
kubernetes
community
and
it
at
times
does
get
overwhelming
it's
extreme.
D
It
was
extremely
overwhelming
for
me
as
a
lead
shadow,
because,
like
I
said,
I
was
aware
of
only
certain
aspects
of
the
project
and
I
was
not
able
to
sort
of
grasp
the
other
areas,
but
as
a
shadow
or
as
a
lead.
That's
that's
what
your
you
know.
Fellow
members
in
the
team
are
there
for
so
you
sort
of
bank
upon
each
other
as
a
community
to.
D
People
are
very
helpful
people
you
know,
are
responsive
and
maybe
not
immediately,
but
they
do
respond,
but
it's
very
intimidating
when
you
are
doing
this
over
and
about
your
job,
because
you
feel
like
you're,
not
able
to
give
the
exact
time
commitment
that
the
role
deserves,
and
I
constantly
kept
feeling
that
throughout
the
cycle,
because
some
of
the
meetings
like
everybody
here
knows
some
of
the
meetings
are
not
held
in
an
exactly
you
know:
apac
friendly
time
zone.
D
So
it's
very
difficult
during
some
days
to
actually
attend
and,
having
you
know,
a
personal
life
and
doing
the
having
a
daily
job
and
working
with
an
open
source
is
a
totally
different
ballgame
than
what
I
anticipated
it
to
be.
D
B
Yeah,
so
I've
been
pretty
lucky
where
I
I've
had
lots
of
support
from
the
company.
I
work
with
susa
and
rancho
labs.
They
totally
supportive
of
me
contributing
to
upstream
and
and
know
that.
Sometimes
I
have
to
block
off
some
time
to
work,
to
work
on
upstream
with
the
meetings
involved
and
with
just
the
tasks
involved.
So
I've
been
really
lucky
with
that.
I
do
encourage
that
as
well.
B
Just
to
you
know
every
before
every
release,
you
know
I
just
kind
of
paint
my
thing
my
manager
and
say
I'm
doing
this,
and
this-
and
this
is
like
yeah-
it
sounds
great
and
like
sonia
mentioned,
some
teams
are
the
time
committed.
The
time
commitments
are
different,
like
enhancements
is
very
front
of
the
really
cycle
heavy.
So
you
with
enhancements
you're
very
busy
from
from
the
first
few
weeks
up
to
probably
middle
of
the
release
cycle.
B
Docs
is
very
it's
much
more
middle
to
late
to
release.
Heavy
release.
Notes
is
much
more
late
release
heavy,
but
it
gives
you
that
time
to
ramp
up
during
release
notes
to
get
comfortable
with
krell
to
get
comfortable
with
with
the
with
the
sub
command.
B
As
well
also
make
improvements
as
well,
so
so
each
release
each
team
or
sub
team
in
the
release
team
has
different
time
commitments
and
when,
when
those
time
when
those
time
commitments
are
so,
what
I
like
to
say
is
that
you
get
out
of
the
of
the
release
team
and
seek
release
and
what
you
get
out
of
it
correlates
to
how
much
you
put
in
so
also
like
you
know,
as
if
you
put
a
lot
into
into
the
work
or
into
the
community
involvement
with
the
release
team,
you
are
going
to
get
so
much
out
of
it
as
well,
so
just
learning
the
different
repos
and
learning
the
different
processes.
B
If
you
spend
the
time
to
be
active
and
to
learn
about
about
the
release
process,
you're
going
to
get
a
lot
out
of
it,.
A
All
right,
thank
you.
What
I
what
I
find
interesting
so
far
is
we've
heard
parts
like
intimidating
and
we've
heard
words
like
a
lot
of
work
and
we've
heard
words
like
you
know
that
it
also
takes
a
lot
of
time,
but
also
you've.
All
just
told
me
that
you've
all
signed
up
for
multiple
releases,
like
some
of
you,
went
back
to
118.
Somebody
said
120
like
so
this
is
clearly
something
that
you
all
feel
is
maybe
challenging
or
difficult
as
it
can
be
or
time
consuming
must
be
rewarding.
B
B
A
All
right
well,
I
have
very
kindly
set
up
a
little
short
link
which
will
take
you
directly
to
the
google
form
to
sign
up
for
their
become
a
really
shadow.
So
please
check
that
out
I'll
leave
that
up
for
just
a
few
minutes
I'll
try
to
I'll
cover
my
own
head.
I
don't
want
to
cover
you
david
there
we
go
so
can
we
just
then
for
the
people
that
are
curious?
Being
a
shadow
is
not
a
released
team
lead
right,
you're
there
to
watch,
understand,
contribute
and
learn.
B
It
was
very
intimidating
because,
because
when
I
first
thought,
release
notes
was
gonna,
be
you
know
the
easiest
and
it
might
be,
I'm
not
too
familiar.
I
wasn't
part
of
every
single
team
and
they
released
seen,
but
it
was
very
intimidating
knowing
all
just
knowing
all
the
different
repos
plus
when
I
was
in
there
118.
There
was
a
change
into
the
process
of
generating
the
beauty
steps.
So
you
have,
to
you
know,
build
the
the
curl
tool
locally
on
your
on
your
local
machine.
B
Make
sure
you
have
the
proper
version
go
as
well,
so
there's
a
lot
of
dependencies
involved
with
it
so
also
yeah,
so
it's
very
intimidating,
but
the
people
on
your
team,
the
other
shadows,
your
team
lead,
is
they're
super
helpful.
They
they're
very
encouraging
my
my
my
first
release
notes.
B
Team
lead
was
very
encouraging
to
to
me
and
encourage
me
to
like
to
to
step
up
a
little
bit
and
to
play
around
with
the
tool
to
generate
the
release,
notes
so
and
the
in
the
other
shadows
as
well,
and
and
tell
your
truth.
We're
still
the
other
shadows,
we're
all
still
pretty
good
friends
that
we
haven't
met
each
other,
but
we're
all
you
know
pretty
good
friends
and
slack
and
yeah,
and
also
we
all
we've
also
continued
with
the
release
in
sig
release
as
well.
B
So
it
was
very
intimidating,
but
after
after
spending
a
little
bit
of
time
as
several
zooms
with
just
to
get
familiar
with
with
the
process,
it
got
easier
and
easier
and
the
more
the
more
time
you
spent
in
you
know,
with
the
release
team,
it
just
gets
easier
and
easier
as
well.
Even
though,
even
if
you
jump
from
one
team
to
another,
you
still
yeah
it's
good
to
get
that
insight
of
what
the
other
teams
do
in
the
release
team
process
or
in
their
release
process
as
well,
but
yeah.
B
It
wasn't
tim
danny
first,
but
I
highly
suggest
you
know,
don't
be
discouraged,
there's
a
lot
of
people
to
help
you
out
if
it's,
if
it
is
intimidating
same
with
the
time
commitment
as
well,
there's
there's
so
many
people
on
on
your
team
to
help
you
out.
If
you
have,
you
know,
life
happens,
so
you
know.
There's
life.
There's
unexpectancies
with
life,
and
so
it's
totally
fine
and
there's,
and
it's
such
a
welcoming
team
and
community
that
encourage
every
everyone
to
apply
and
don't
be
intimidated.
A
C
C
Also,
we
had
a
conference
called
kubecon
last
year
and
during
my
mentorship
program
we
used
to
invite
a
lot
of
guests
who
were
directly
involved
with
cncf
projects
and
at
the
time
nikita
and
nabaroon.
I
got
in
touch
with
them
and
they
mentioned
to
me
about
this
program.
A
C
A
Yeah,
it
sounds
like
the
people
almost
kind
of
come
first
in
the
project,
and
the
code
comes
second
like
I
think
so.
Many
friendships
happen
from
getting
involved
with
protests
like
this,
and
I
love
hearing
other
people's
stories
just
about
how
they
stealthy
and
chat
with
people
that
they're
working
for
a
little
bit.
What
about
you?
What
was
your
first
release
team
like.
D
So
my
first
release
was
with
I
mean,
was
shadowing
savita
of
the
dogs.
It
came
full
circle
when
I
shadowed
savita
as
a
lead
this
time
around.
But
honestly
for
me
personally,
I
treasured
that
experience
and,
like
ray
said,
it
was
simultaneously
intimidating
as
well,
because
savita
according
to
me,
knew
everything
about
documentation.
D
When
I
you
know,
and
as
compared
to
that,
I
barely
knew
anything
and
I
was
like
what
exactly
is
git
push,
because
in
my
day
job
we
really
don't
use
github
at
all.
So
I
had
to
start
with
the
very
basics
of
github.
Learn
that
understand
what
a
brand
sync
was.
So
we
do
that
integration
branding
quite
a
few
times.
D
D
You
know
section
and
ask
to
be
a
shadow
there,
because
I
did
not
feel
as
intimidated
as
I
did
when
I
started
off,
and
the
reason
why
I
got
interested
in
the
very
first
place
was
I
recently
transitioned
into
a
management
role
at
my
work,
and
I
did
not
know
this
back
then,
but
I
wanted
to
gain
some
sort
of
leadership
experience
outside
of
my
job
to
understand
what
leadership
would
look
like
if
I
actually
managed
to
do
it
at
my
job
as
well.
D
It
sounds
stupid
right
now,
but
I
think
leading
the
calm
cycle
ahead
of
my
promotion
this
year
really
helped
me
understand
and
develop
an
empathetic
attitude
towards
people.
D
People
across
different
time
zones,
even
when
I
was
leading
comms
in
my
day
job
though
I
don't
have
to
really
work
across
time
zones.
It's
it's
more
of
a
indian
specific
team,
but
it
helped
me
develop
a
more
empathetic
and
you
know
so.
I
wouldn't
want
to
put
this
because
it
sounds
very
cliche,
but
solvent
leadership,
sort
of
a
role.
It
helped
me
develop
that
when
I
actually
transitioned
to
a
more
management
role
within
my
team,
so
yeah
that
that
was
my
aim.
A
That's
really
cool.
I
had
never
thought
about
that
approach
before,
but
I
mean
if
we
think
about
traditional
workplaces-
and
I
use
that
phrase
that
I'm
not
terribly
a
fan
of,
but
we
talk
about
nine
to
five
in
an
office,
communicating
with
people
that
are
across
the
table,
signing
up
to
the
release
team
and
working
in
a
truly
distributed
asynchronous
way.
It's
a
really
interesting
way
to
kind
of
adapt
and
pick
up
some
new
skills
that
are
required
and
get
familiar
with
remote
work.
A
B
A
B
E
B
Covid
and
we
extended
that
release
like
that
release
cycle
quite
a
bit
as
far
as
for
additional
pressure
personally,
no
but
it,
but
what
it
did
give
me
was-
and
I
guess
with
also
with
remote
work
as
well.
It
gave
a
sense
of
more
normalcy,
of
making
friends,
through
slack
and
through
the
release
team,
and
it
kind
of
helped
me
out-
I
guess
through
through
through
these
times
with
kobe
19,
because
you
can
you
communicate
more
with
with
others.
B
You
make
good
friends
going
through
this
release
process
and
there's
a
positive
outcome
like
you,
you
helped
produce
a
kubernetes
release
as
well,
so
so
so
for
me,
it
helped
me
so
so
I
don't
know
if
it
was
almost
to
the
height
of
I
guess
of
of
therapy
for
for
for
sheltering
players
in
coca-19.
But
for
me
it
certainly
helped
me
out
throughout
this
whole
pandemic.
C
Yep,
actually,
I
also
have
same
opinion
as
ray.
The
only
downside
for
me
was
the
you
know:
time
zones
they
were
not
ist
time
zone
friendly,
but
apart
from
that,
you
know,
I
made
good
friends
also,
while
reading
the
enhancement
proposals,
I
came
to
know
what
are
the
features
we
are
going
to
have
in
the
kubernetes,
how
the
whole
structure,
how
the
whole
routine
structure
is
going
to
have
so
also
that
added
a
great
into
my
resume
as
well
and
opened
a
lot
of
job
opportunities.
D
Not
really
because
I
think
ray
and
sonia
covered
at
all,
but
what
I
would
say
you
know
is
a
big
is
a
big
plus
one.
I
think
jim's
who's,
like
the
most
famous
member
of
kubernetes
and
sorry
dance.
If
I'm
calling
you
the
oldest,
but
the
oldest
member
as
well.
D
In
terms
of
the
number
of
years
he's
been
with
the
community,
he
said
that
you
know
come
for
the
contribution
stay
for
the
community
or
come
for
the
swag
and
stay
for
the
community.
He
retreats
this
in
every
conference
that
he
goes
to.
So
I
would
really
say
that,
wherever
or
whatever
outlook
you
have,
when
you
start
off
with
community
contributions,
so
I
started
off
with
an
end
goal
of
developing
better
leadership
skills.
D
D
Learning
and
gaining
a
lot
more
than
what
you
came
for
so
with
respect
to
comet.
It
saved
me
and
helped
me
stay
safe.
So
a
lot
of
like
a
lot
of
fathers
across
the
world
we
lost
some.
I
mean
I
lost
some
dear
members
of
my
close
family
and
friends,
and
this
community
helped
me
stay
sane.
D
I
wouldn't
recommend
my
working
hours
to
anyone,
but
it
definitely
helped
that
you
know
I
had
something
and
something
other
to
look
into
when
I
had
that
phase
going
on
in
my
life
last
year.
So
it
was
really
helpful
and
I
would
highly
recommend
you
know
joining
the
release
team,
but
definitely
not
my
working
eyes.
So
please,
please,
don't
copy
paste
the
exact
version
of
my
working
house
anywhere
so
yeah
kobet.
I
mean
it
saved
me
from
staying
safe.
D
I
mean
it
saved
me
from
the
going
insane
during
this
pandemic.
So
really
thanks
thanks.
I
am
I'm
actually
thankful
to
a
lot
of
people
who
helped
me
get
started
so
that
will
probably
take
up
another
25
minutes
of
your
show.
So
I
think
I'll
just
give
it
back
all.
A
Right,
thank
you
and
I'll.
Also,
just
I
wouldn't
be
brave
enough
to
say,
dems
is
the
oldest,
but
I
will
say
that
dems
is
probably
one
of
the
most
helpful
mentoring
welcoming
people
in
the
kubernetes
community
yeah.
Definitely
thank
you
tim
for
all
your
your
hard
work.
Okay.
What
about
for
people
that
are
watching
that
are
like
they're
now
sold
right?
I
think
we
give
them
a
nice
compelling
story
of
the
the
beauty
of
working
and
joining
sig
release
and
all
the
benefits
to
it.
What
prior
knowledge
do
they
need?
A
B
Yeah
personally,
I
don't
think
you
need
to
be
a
kubernetes
expert
or
to
be
a
developer
to
contribute
to
sig
release.
Sig
release
is
a
great
opportunity
for
for
no
code
contributions
to
to
the
to
the
community.
It's
it's
helpful.
I
mean
personally,
I
I
am
a
kubernetes
user
use
it
almost
every
day
professionally.
I'm
sorry.
B
Yeah
but
yeah,
so
it
does
help
out,
but
you
don't
need
to
know
kubernetes,
but
you
will
learn.
You
will
certainly
learn
a
lot
about
kubernetes.
Once
you
are
part
of
sequence,
you
don't
need
to
have
any
coding
experience
or
no
kubernetes
or
being
expert
in
kubernetes,
but
yeah,
but
you'll
certainly
learn
a
lot
about
it
and
afterwards.
So.
C
Yeah
so,
first
of
all,
hey
fox,
thank
you
so
much
for
joining
and
listening
to
this
live
stream.
I
would
like
to
say
it's
okay
to
not
know
anything
to
feel
intimidated
at
the
first
look
of
the
cumulative
ecosystem
to
get
lost
you
know
to
to
from
from
where
to
start
from,
I
would
say
just
gather
enough
courage
and
say
hi
on
the
slack.
There
are
lots
of
abundant
resources
and
the
people
who
will
help
you
to
get
started.
C
We
have
a
place
for
everyone,
no
matter
what
your
background
is.
Even
you
are
not
from
the
tech
industry.
Also
yeah.
The
applications
are
open.
Just
just
go
through
them.
Ask
questions
in
the
slack.
If
you
are
having
any
kind
of
doubt
ask
for
review,
maybe
you
know
and
yeah
just
hit
the
submit
button.
D
Yeah
just
a
perspective,
that's
a
little
different
from
sonya
andre,
but
I
think
it
does
a
plus
one
to
what
they
said.
You
don't
need
any
coding
experience
or
any
kubernetes
experience,
but
you
do
need
to
have
the
hunger
to
learn,
and
you
also
need
to
ensure
that
you
have
the
time
to
actually
commit
to
that
particular
area
of
the
release,
because
I
don't
know
who
said
this
around
a
while
back.
D
So
you
basically
need
to
put
in
that
time
commitment
without
having
any
you
know
any
inhibitions
or
anything,
because
only
when
you
put
in
that
time,
commitment
to
learn
and
to
understand
more
about
the
kubernetes
ecosystem
isn't
going
to
reap
benefits
in
any
sphere
or
whether
it
be
in
terms
of
learning
whether
it
be
in
terms
of
you
know,
a
job
whether
it
be
in
terms
of
anything
you
need
to
have
that
will
to
learn,
and
you
need
to
have
the
time
commitment
back
down,
because
if
you
don't
do
that,
you're
not
going
to
get
anything
out
of
the
release,
sure
you
will
be
a
really
shadow
according
to
the
line
you
put
on
your
resume,
but
if
you're
actually
looking
to
gain
something
or
that
is
more
tangible
in
terms
of
experience
or
in
terms
of
you
know,
learning
you
need
to
put
the
time
and
you
need
to
put
in
that
work
hours
to
actually
understand
the
ecosystem.
D
That's
when
it
pays
off.
So
I
would
definitely
encourage
everyone
to
like,
but
also
be
mindful
that
it's
it's
it's
a
it's
a
burden
on
your
time.
It's
it's
a
commitment
of
your
time
I
wouldn't
say
burden,
but
it's
a
commitment
of
your
time
and,
if
you're
not
able
to
make
that
time
commitment
whatever
that
you
do
is
not
going
to
reap
any
benefits.
D
So
this
comes
from
personal
experience
because
I
have
made
a
mistake
not
with
relevance
not
with
kubernetes
specifically
but
with
other
open
source
projects
where
I
couldn't
dedicate
the
time-
and
I
used
to
be
frustrated
last
year-
that
I
couldn't
understand
a
lot
of
the
projects
that
I
was
getting
into.
D
So
unless
you
are
willing
to
put
in
the
time
it
will
not
be
much
of
a
you
know,
beneficial
activity,
if
you
get
in
and
you're
not
you're,
not
doing
anything
so
it'll
be
a
good.
A
Awesome,
thank
you
all
right,
I'm
going
to
give
you
the
question
to
think
about
for
the
next
few
minutes
and
then
I'm
going
to
well.
These
are
thinking
I'm
going
to
ask
a
question
from
the
chat
and
then
we'll
be
finishing
up
for
today.
So
what
I
want
you
to
think
about
for
the
next
couple
of
minutes.
A
What's
the
thing
you
enjoyed
most
about
working
on
the
release
team
and
what
one
piece
of
advice
would
you
give
to
anyone
watching
that's
going
to
sign
up
for
123.,
so
think
about
that
and
now
I'll
handle
the
question
that
we
have
in
the
chat
so
annaberg
annaberden
has
asked.
I
have
applied
to
be
a
release
shadow
on
123
for
sick
docs.
Could
I
have
a
brief
overview
of
what
I
will
do
and
what
I
will
be
doing.
If
I
get
accepted,
does
anyone
remember
their
responsibilities
for
sick
dogs?
B
Yeah
so
with
so
with
sig
docs.
First,
you,
you
kind
of
you
start
more
in
the
middle
of
the
release
cycle.
So
the
first
few
weeks
might
be
a
little
quiet
with
sig
docs.
Is
that
it's
kind
of
a
handoff
from
the
enhancements
team,
so
once
the
enhancements
collate
and
gather
what
enhancements
are
going
to
be
targeted
in
1.23?
B
What
the
doc?
What
the
docs
team
does
is
to
verify.
If
there's
any
documentation
updates
needed
for
each
of
those
enhancements
that
will
be
targeted
in
1.23
once
they
confirm
that
they
they
go
through
and
they
follow
that
that
life
cycle
of
that
documentation
update.
B
So
they
make
sure
that
there's
a
pr
made
for
the
kubernetes
website,
repo
targeting
the
right
branch
for
one
1.23,
make
sure
that
that
it's,
that
is
up
to
review
by
a
certain
deadline,
to
make
sure
that
that
review
is
done
either
a
technical
review
or
it
will
have
a
technical
review
and
a
documentation
review
as
well.
B
And
you
could
also
do
the
review
yourself
and
then
finally
is
to
merge
that
documentation
update
into
the
one
dab,
123
branch
of
kubernetes
website,
which
is
the
repo
for
the
kubernetes
website,
then
there's
quite
a
bit
more
on
and
towards
the
end
of
the
release,
a
lot
of
git
as
well.
So
so,
if
you're
not
familiar
with
get
with
git,
it's
totally
fine
and
people
will
help
you
out
and
learn
and
teach
you
how
to
do
syncs
for
the
integration
branch
so
part
of
it.
Also,
you
maintain
an
integration
branch.
B
Then
you
have.
This
integration
branch
will
be
will
be
merged
into
the
main
branch
on
release
day.
So
you
maintain
that
integration
branch
by
doing
branch
syncs,
so
there
might
be
some
merge
conflicts
during
when
you
do
these
things,
but
people
will
help
you
and
walk
you
through
these
merge
conflicts,
so
don't
be
scared
of
merge
conflicts.
B
The
reason
why
we
we
constantly
sync
and
maintain
this
integration
branch,
because
we
don't
want
merge
conflicts
on
the
very
last
day
release
day
so
make
sure
we
handle
them
before
that.
After
that,
yeah
the
release
day,
you
merge
you,
you
merge
the
integration
branch
with
the
main
branch.
The
new
documentation
is
updated
on
the
kubernetes
websites.
You
also
do
some
git
tagging
as
well
to
create
the
the
initial
or
the
last
snapshot
of
the
last
release.
Initial
tag
of
the
new
release
as
well.
A
Awesome,
thank
you
I'll
just
share
one
thing
on
my
screen
for
people
that
are
watching.
There
is
a
repository
on
github.
It
is
kubernetes,
slash
release
and
if
you
go
into
your
release
teams,
the
handbooks
for
all
of
the
roles
are
here.
I
would
strongly
encourage
everyone
to
come
in
and
just
read
through
these
and
see
which
roles
appeal
to
you
and
apply
for
the
ones.
A
D
Please
sorry
yeah.
So,
honestly
speaking
and
I
want
to
be
brutally
honest
here,
please
please
please
be
very
specific
about
what
you
want
to
apply
for
why
I
will
also
give
the
reasoning
it
it
does.
I
mean
applying
for
multiple
roles
might
increase
your
chances,
no
doubt
about
it,
but
you
also
need
to
be
aware.
D
After
reading
the
you
know,
handbooks
that
I
think
david
just
showed
now
about
what
you're
interested
in
because,
like
I
said
it's,
some
roles
are
more
demanding
in
times
of
term
commitment
as
opposed
to
others.
So
if
you
are
applying
for
every
single
role,
that's
there
on
the
you
know,
form
and
you
just
end
up.
You
know
confusing
every
enrollee.
That's
there
in
this
cycle.
D
It's
a
big
chance
that
you
are
going
to
be
picked
by
some
team
that
actually
does
not
cater
to
your
strengths
and
to
your
skill
sets
and
you
will
probably
not
have
a
great
experience
and
might
feel
demotivated
at
the
end
of
it
all
so
very
practical
advice-
and
I
don't
know
if
anybody
here
agrees
with
me,
but
I
would
say,
be
very
specific:
read
the
role
handbooks
and
then
apply
because
sure
you
know
applying
for
multiple
roles
makes
sense.
You
put
your
eggs
in
different
baskets.
D
All
of
that
makes
sense,
but
if
you
actually
do
not
specify
it's
going
to
be
an
experience
that
you
are
not
going
to
treasure
or
you
are
not
going
to
get
much
value
out
of.
A
B
To
try
again
or
there's
many
different
ways
to
be
part
of
the
kubernetes
community
join
join
us
sig
join
the
sig
meeting,
see
if,
if
you,
if
you,
if
that
interests,
you
as
well
like
like,
if
you
want
to
make
some,
if
you're
a
technical
writer
or
want
to
do
some
technical
writing,
join
a
sig,
docs
meeting
it's
on
tuesdays
and
you
can
find
out
what
the
what
what
time
that
is
in
your
time
zone
and
I
just
encourage
people
to
don't
be
discouraged
if
you're
not
selected,
to
try
again
and
to
look
and
there's
a
lot.
A
Yeah
we're
going
to
do
our
best
on
lgbtm
to
get
more
of
those
no
code
contribution
methodologies
across
to
people,
so
there'll
be
plenty
of
ways
for
you
to
contribute
to
kubernetes.
I
think,
as
we've
all
said
at
one
point
during
today's
session,
there's
like
it's
a
huge
project
and
there's
lots
of
ways
to
contribute,
recycle
releases
of
one
of
one
of
many
all
right.
A
Let's
finish
up
with
the
the
two
questions,
can
I
from
each
of
you
have
what
did
you
enjoy
most
from
being
a
member
of
second
release
and
one
piece
of
advice
for
people
watching
we'll
start
with
you
ray
and
then
lebron
again,
please.
B
So
for
me
what
I
enjoyed
most,
it
gave
me
a
lot
of
confidence
in
the
community
to
because,
when
you
first
start
you're
shy
to
you
know
to
do
slack
messages
to
make
comments,
because
you
know
not
as
experienced
but
as
you
build
your
you
ramp
up
and
you
build
experience.
It
gave
me
a
lot
of
confidence
so
and
sick
release
has
also
led
me
to
contribute
to
other
sigs
as
well.
Sig
docs,
I'm
a
sub
project
owner
with
security,
as
well
so
kind
of
led
to
those
other
contributions.
B
So
one
piece
of
advice
as
well
is
to
is
put
some
time
into
it.
If
you're
selected
on
a
release
team
as
well,
you
know
that
devotes
a
devoted
time
into
learning,
that
role
and
and
reach
out
to
others.
Since
there's
two
pieces
of
advice
reach
out
to
others
as
well.
If
you,
if
you
need
any
help,
people
are
willing
to
help
you
so
everyone
who's
in
from
the
person
who's
been
part
of
sick
release.
B
The
longest
dim
super
super
helpful
yeah,
so
everyone
will
help
out
and
everyone,
if
not
yeah,
someone
will
help
out
and
just
reach
out
all.
C
Yeah,
so
for
me
I
will
say
it
adds
a
lot.
It
added
a
lot
to
me
in
terms
of
personal
development.
I
improve
my
communication
skills.
C
You
know
how
to
reach
out
to
people
and
yeah,
and
if
I,
if
I
go
technically,
I
got
to
know
how
the
whole
kubernetes
reason
structure,
how
we
are
improving
the
release,
tooling,
the
artifacts
that
are
generated,
how
you
know
we
are
having
it
up
to
the
level
so
yeah.
Apart
from
that
the
friends
the
people
that
I
that
I
got
connected
to,
that
was
one
of
the
best
thing
happened.
C
Well,
I
would
say
you
know
when,
if
you
join
to
the
community
kubernetes
community
connect
to
the
people
reach
out
to
them,
don't
be
shy
to
ask
questions
because
the
more
you
will
ask
the
more
you
will
grow.
D
So
I
think
I'll
go
over
the
advice,
but
first
because
everybody's
spoken
about
the
good
things,
so
my
advice
would
be
the
rt
shadowing
process
is
a
very
competitive
one.
So
there's
a
chance
that
if
you
apply
we
get
like,
I
think,
last
cycle
we
got
around
100
plus
applications
for
around
30-ish
rules,
so
you
can
understand
the
amount
of
competition
that's
there,
and
this
is
not
just
from
one
specific
country
or
one
specific
continent
it's
from
across
the
globe.
So
please
don't
be.
D
You
know
demotivated
if
you
don't
get
it
at
the
very
first
try.
There
are
other
opportunities
like
I
think
david
and
ray
spoke
about,
and
there
are
several
of
them
across
the
kubernetes
community.
It's
it's
arty!
So
really
steep!
Sorry,
I
don't.
I
I
keep
on
jumping
back
to
my
nomenclature.
Release
team
is
not
the
do
all
and
end
all
of
everything
you
do
have
other
avenues
to
get
involved
in.
So
please
don't
get
demotivated
and
feel
like.
Oh,
I
didn't
get
into
our
team.
D
Maybe
I
should
not
try
at
all.
Please
don't
do
that.
Ask
around
there
are
all
these
folks
to
help
you
out
and
if
you
find
anyone
please
feel
free
to
you
know,
post
on
in
I
mean
respective
slack
channels,
suppose
you're,
you
know
talking
about
documentation
or
you're
interested
in
documentation
post
on
the
respective
slack
channel
and
people
will
get
back
to
you
and
there
are
a
lot
of
resources
with
respect
to
good
first
issues
and
stuff
like
that,
and
I'm
sure
david
will
cover
all
of
them.
D
But
yeah
don't
get
demotivated
if
you
do
not
get
it
at
the
very
first
try.
I
know
it's
a
very
sad
thought
to
end
this
thing
on,
but
please
don't
get
demotivated.
If
you
don't
get
into
the
hearty
shadow
process
because
trust
me
it
took
me,
two
tries
so
it
was
not
at
the
first
try.
I
ended
up
not
getting
it
and
it
was
only
in
190
that
I
got
in.
D
Finally,
so
please
don't
get
demotivated
and
continue
trying
if
release
team
is
your
end
goal
you,
you
will
end
up
getting
it
at
some
point
in
time,
but
also
explore
other
avenues
within
the
project,
because
there
might
be
something
that's
more
suitable
for
you
out
there
as
well
yeah.
That's
about
it!
For
me,.
C
Actually,
I
want
to
add
one
more
thing
here.
There
were
when
I
was
in
the
release
notes
team.
There
were
some
of
the
contributors
who
didn't
got
accepted,
but
you
know
they
were
there
as
a
contributor,
not
at
not
as
a
release
shadow,
so
yeah.
You
can
always
contribute
to
the
team.
You
don't
need
to
have
the
release
shadow
tag
and
also
it's
gonna
increase
your
chance.
Whenever,
for
the
next
time
you
are
going
to
apply.
A
Awesome
all
right
great
advice
all
around
there
lots
of
positive
energy,
but
the
things
that
you
enjoy.
I
love
the
focus
on
people
as
well
at
this.
I
think
that's
what
this
community
is
built
on,
and
it's
lovely
to
see
some.
So
much
of
that
here
I
want
to
say
thank
you
all
for
your
contributions,
ray
best
of
luck
with
123..
D
Yeah,
I
actually
wanted
to
thank
you
for
inviting
us
on
to
your
show.
So
thank
you
and
thank
you
for
having
all
of
us
and
it's
been
a
pleasure
speaking
with
you
and
seeing
all
of
your
faces
because
it's
been
the
pandemic
and
I've
not
seen
faces
for
a
really
long
time.
So
yeah.