►
From YouTube: K8s SIG Docs New Contributor Meet and Greet for May 2022
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
Foreign
now
great,
we
are
also
recording
at
the
perfect
time.
Thank
you
for
that,
and
just
before
we
proceed,
this
meeting
would
be
governed
by
the
cncf
code
of
conduct,
which
essentially
boils
down
to
be
respectful
to
each
other
and
be
nice,
which
I'm
sure
you
all
will
so
I'm
done
with
my
introduction,
I'd
like
to
nominate
Divya
next,
who
needs
no
introduction,
but
still.
B
Yeah
I
mean
I
I,
think
I
do
but
still
I
will
go
ahead
and
so
I'm
Divya
Mohan
I'm
the
co-chair
for
sick
documentation
for
kubernetes
one
of
the
coaches,
so
unfortunately
the
other
coaches,
one
of
them
lives
in
a
slightly.
You
know
not
slightly
very,
very
different
time
zone.
He
could
not
be
here
but
I'm
sure
you
know
one
of
them.
B
One
of
these
days
they
will
come
and
you
know,
introduce
themselves
so
I
work
for
Susa
or
Rancher
Labs
as
part
of
my
day,
job
I
am
a
technical
writer
there
before
which
I
did
a
bunch
of
stuff.
In
you
know
the
IT
industry,
as
a
systems
engineer
leading
a
team
Etc
in
the
cloud
native
space
I
just
got
started
two
years
ago,
mainly
worked
in
documentation
and
released
team
stuff
and
yeah.
Here.
B
I
am
after
that
I'm
also
cncf
Ambassador,
and
hopefully
you
know
for
those
of
you
who
are
making
out
to
kubecon
this
next
coming
couple
of
weeks.
I
hope
I
can
see
all
that.
So
right,
let
me
see
who's
the
next
victim
I
think
I'll
go
with
vittal
because
he
was
the
one
who
first
said
hi,
so
we
told
you
want
to
go
next.
C
Yeah
sure,
hello,
everybody
I'm
vital
call
I'm
doing
my
engineering
in
Pune
and
I
I
got
introduced
into
the
cloud
native
space
since
the
last
cubecon
EU
and
now
I
am
trying
to
learn
more
about
this
space
and
I
started
started
my
contribution
Journey
since
kubecon
n,
a
and
I
hope
to
learn
from
all
of
you
and
take
my
contribution
path,
further
away.
B
You
got
to
nominate
someone
better
for
the
next
one.
I
mean.
D
So
hello,
everyone
myself,
I,
am
a
junior.
Pursuing
Bachelor's
in
computer
and
I
am
also
a
Linux
LFX
Manti
at
cncf,
currently
working
with
kubernetes
Sig
network
with
the
Gateway
API
project
and
yes,
I
have
played
a
role
with
kubernetes
1.24
and
1.23
release,
talks,
shadow
and
also
syndox
member.
E
Yes,
hello,
everyone
do
you
hear
me
correctly,
yeah,
so
yeah
I'm
living
in
the
front.
E
So
that's
why
there
is
so
much
sunlight
on
me
and
it's
midday
right
now
so
I'm
walking
at
the
cost
lab,
which
is
a
security
company
in
France
and
I've,
made
some
contribution
actually
to
to
the
kubernetes
website
already
mostly
focused
on
security,
because
I
regularly
attend
the
music
Security,
Group
and
and
yeah
I
I
attend
also
all
the
subgroups
like
security,
tooling
or
security
dock,
with
a
with
some
people
so
yeah,
that's
it
so
I,
don't
know
a
lot
of
people
so
I'm
going
to
go
around
them
here.
E
G
H
By
anything
and
nice
to
meet
you
yeah,
my
name
is
sorry,
a
country
that
I
am
now
taking
care
of
my
baby,
so
yeah,
sorry
for
her,
so
yeah
situation,
but
yeah
I,
contributing
dog's,
Korean
team
and
then
I
started
to
contribute
two
or
three
years
ago,
with
great
reviews
or
purpose.
So
I
started
as
reviewer
and
also
then
I'm
now
approving
some
a
kind
of
well
greater
prerequisition
from
Korean
team.
Now
I
work
in
a
Microsoft,
Korea
and
then
I'm
working
here
as
a
product,
marketing
manager
for
developer
products
and
yeah.
H
Previously
that
I
have
been
contributing
open,
State
internationalization,
as
project
team
lead.
So
I
now
happily
happy
to
continue
my
translation
contribution
to
also
kubernetes
yeah
nice
to
meet
you.
H
I
A
That's
cool.
This
is
what
this
meeting
is
foreign.
We
are
here
to
help.
Could
you
nominate
who's
supposed
to
go
next
after
you.
J
J
Can
you
hear
me
yes,
I'm
I'm,
Chris
nagis
I've
been
working
with
the
kubernetes
docs
team
shadowing
with
mayhaw,
in
fact,
for
the
last
couple
of
releases
for
the
one
two
one,
two
two
one,
two
three
one
two
four
releases
I
was
shadow
I
worked
for
Amazon
web
services
and
kubernetes,
so
yeah
hi
Maha,
though
I've
worked
for
a
a
few
years,
a
couple
years
on
kubernetes.
J
My
background
is
really
mostly
in
Linux
I
used
to
write
lots
of
Linux
books
and
that's
that's
kind
of
what
I
did
I
kind
of
wanted
to
get
on.
This
call,
even
though
it's
very
early
here
for
me,
because
I
feel
like
I'm,
missing
half
the
world
in
in
just
being
awake
during
U.S
time
zones
so
nice
to
meet
all
of
you
and
welcome.
J
Let's
see
is
there
anyone
else
who
hasn't
gone?
Sorry
I
ever
arrived
late
as
well.
F
All
right
sounds
good
hi
folks.
Can
you
hear
me.
F
I
I've
got
a
couple
of
contributions
into
the
project
so
far,
and
my
journey
started
with
coupon
EU,
2021,
yeah,
I'm,
sorry
I'm
losing
track
of
the
years,
but
yeah
I'm
transitioning
into
a
software
engineering
role
with
a
cloud
native
startup
right
now
and
I
figured
it's
it's
a
great
time
to
kind
of
start
ramping
up
my
contributions.
So
that's
who
I
am
here
in
this
meeting,
trying
to
figure
out
where
I
could
fit
in
that's
honestly
about
it?
Little
do
you
want
to
go
next.
A
A
K
My
name
is
Juan
shul
I'm
from
India
I'm,
currently
pursuing
my
bachelor's
in
the
field
of
computer
science.
I
am
current.
I
am
very
new
to
this
whole
kubernetes
and
Cloud
native
ecosystem.
I
have
not
been
very
much
active
in
this,
and
I
have
done
some
contribution
that
are
not
sensible.
Only
documentation,
related
I
am
looking
forward
to
getting
more
roles
in
the
contribution,
and-
and
that's
all
for
my
side.
A
I,
don't
think
there
are
like
any
contributions
which
qualify
as
non-sensible
virtual,
so
whatever
you've
been
up
to
just
keep
up,
and
if
you
feel
like
that's
a
small
contribution
right
now,
then
it
will
definitely
grow
bigger,
as
you
spend
more
time
with
the
project
like
well
I
I'm
sure,
like
a
lot
of
our
first,
like
my
first
contribution
in
open
source,
was
generally
like
a
type
of
fix,
or
something
like
that.
So
this
is
like
nothing
to
be
worried
about
something
like
that
cool.
A
So
I
think
we
have
Donna
like
round
of
introductions,
and
so
my
plan
for
this
call
was
to
like
walk
you
through
walk
like
we
have
a
wide
range
of
expertise
among
us,
so
I
think,
let's
just
like
stick
to
the
most
beginner
friendly
thing
and
I
was
going
to
walk
you
through
like
the
kubernetes
website,
and
see
some
of
the
good
first
issues
there.
A
But
before
that,
like
what
I
had
in
mind
as
a
higher
priority
was
if
any
new
contributor
on
this
call
is
like
stuck
somewhere
or
has
a
gen
question
about
like
contributing
in
general
or
anything,
they
want
to
talk
about
right
now,
which
they
have
a
trouble
like
bringing
up
in
slack
or
they
feel
they
want
to
do
it
in
person
like
this
is
the
call
to
do
that.
So,
if
anyone
wants
to
do
that,
like
the
floor
is
open,
I
see
divya's
hand
is
raised,
so.
B
No
I,
don't
have
a
doubt,
but
just
kind
of
post
stuff
just
got
to
post
the
agenda
documentation
link
over
here
on
the
chat.
I
think
it's
already
gone,
so
it
would
be
great
if
you
know
at
the
start
of
every
meeting,
which
is
going
to
be
on
a
monthly
basis.
You
all
enter
your
names.
Whoever
is
you
know
chiming
in.
B
Secondly,
I
think
it
would
be
good
to
have
a
record
of
the
questions
so
that,
if
you
know
we
can't
answer
them
over
here,
given
that
this
is
like
of
a
limited
time
frame,
we
can
get
to
it
either
on
the
sick,
dog
slack
or
you
know,
probably
Ash
can
take
it
up
separately
with
one
of
you
all
or,
however,
it
tends
to
work.
So
this
is
a
fairly
new
rule
and
we're
all
learning
as
we
go
I'm
new
to
this
role
as
well.
B
So
all
of
this
is
work
in
progress.
So
if
there's
any
way
we
can
better
ourselves,
please
do
let
us
know
and
all
your
questions,
suggestions
or
whatever
before
the
meeting.
If
you
can
think
of
them,
you
know
you
can
add
it
into
the
agenda.
Documentation-
or
else
you
know
during
our
discussion
itself,
we'll
have
one
of
the
you
know:
host
Taco
host
started
yeah.
That's
all
I
had
I'm
sorry
to
interrupt.
A
A
I'm
gonna
take
this
silence
as
a
no
for
now,
but
if
anyone
wants,
if
you
think
of
something
at
any
point,
just
like
feel
free
to
interrupt
and
go
ahead,
so
other
thing
is
like:
has
anyone
been
working
on
any
interesting
issues
like
on
the
kubernetes
website
like
before?
We
start
looking
into
some
good
first
issues
and
what's
all
happening.
So
if
someone
wants
to
share
what
they've
been
working
on
now's
the
time
to
do
that
too,.
A
H
So
he's
still
here,
yeah
yeah,
oh
today,
then
I
attended.
This
I'm
attended
this
meeting
because
honestly
them
yeah
I
have
not
been
attending
such
kind
of
meeting
yeah.
This
is
my
first
time
to
attend
to
for
this
meeting
so
nice
to
meet
you,
although
I
have
been
working
for
I,
I
have
been
contributing
four
years,
it's
my
first
time.
So
thank
you,
and
so
recently
then
I.
H
When
I
leave
you
some
full
requests
from
Korean
localization
team,
then
I
see
that
how
can
I
say
kubernetes
documentation
is
changing
for
every
religious.
So
now
then
I
see
them.
There
are
some
changes
for
this,
for
example
from
previous
version
to
current
version.
So
then
there
have
been
some
changes
on
English
original
version,
so
the
Ordo
Korean
team
translated.
H
They
need
to
see
again
the
changes
and
they
need
to
reflect
so
yeah,
but
so
now
the
main
issue
is
then
the
volume
of
such
change
size
is
getting
larger
and
larger
and
larger
of
for
so
that
I
want
to
just
bring
the
how
other
teams
are
serving
and
facing
such
issues,
so
that
I
want
to
more
learn
how
Korean
localization
team
can
overcome
or
cancel
research
translation
missing
from
previous
version
to
current
version,
so
yeah.
H
That
is
my
what
I'm
seeing
the
con
for
for
Korean
localization
team,
because
there
are
lots
of
previous
foreign.
H
87
line
items
to
be
changed
due
to
the
change
on
the
previous
version
to
new
version
on
English
repository,
so
I
want
to
more
understand
and
then
and
also
I'm,
not
sure
how
other
documentation,
team
or
main
English
contributors
are
recognizing
decision
or
not.
A
I
think
this
is
a
issue
which
has
like
been
brought
up
earlier,
also
and
like
or
like
almost
a
lot
of
the
localization
teams
have
been
struggling
with
this.
But
currently
we
do
not
have
like
a
perfect
solution
for
this,
but
what
I've
seen
people
do
is
that
whenever
like
there
is
a
PR
for
a
particular
language,
they're,
either
like
just
like
sort,
those
PRS
and
then
manually,
they
check
and
have
to
keep
a
track
of
what
PRS
they
need
to
put.
A
But
the
other
thing
is
that
if
they
have
been
like
prioritizing
like
which
change
is
like
crucial
and
all
those
changes
get
added
with
a
label
for
the
localization
too,
so
that
the
localization
teams
can
like
are
notified
and
are
able
to
move
that
because
I
agree
like
merging
like
translating
every
PR
which
gets
merged
into
the
English
talk
into
the
English
docs
localizing.
That
is
just
like
too
much
effort
and
I.
Don't
think
we
have
enough
contributors
in
the
localization
team.
So
that
is
something
like
I
have
seen.
B
Not
really
a
cover
at
all
hush,
but
mostly
it
boils
down
to
you
know
better
coordination
between
the
sorry
between
the
English
and
the
other
localization
teams,
which
is
why
we're
also
trying
to
formalize
the
localization
sub
project.
So
we
are
having
a
sort
of
leadership
for
the
localization
sub
project
in
the
form
of
Abby
McCarthy
and
Brad
Topol.
That's
that's
one
aspect,
but
we
are
trying
to
sort
of
you
know
have
that
Communication
channel
open
for
major
issues.
B
So,
for
example,
you
know
I'm
not
sure
if
this
was
done
for
the
dark
question,
but
but
because
dockershim
was
such
a
huge
change
across
the
website.
What
would
I
mean
it
would
have
possibly
worked
to
sort
of
replicate
those
changes
and
we
have
a
project
board
for
that
specific
effort.
So
you
know
that
notifying
the
English
notifying
the
actual
a
localization
folks
that
coordination
effort
is
something
we
are
looking
to
work
on
more
this
year.
B
But
as
of
now
like
I
said,
there
is
no
specific
One-Stop
shops
One-Stop
shop
for
a
solution
for
everything.
As
of
today.
Localization
efforts
are
largely
contributor,
driven
and
voluntary
like
everything
else
here,
but
given
that
there's
very
little
communication,
currently
it's
difficult
for
us
to
track
issues.
So
so
we
are
working
on
bettering
that
over
this
year
and
thanks
Chris
for.
A
That
time
for
the
link,
so
yeah
I
think
like
project
boards
are
a
good
temporary
solution.
We
can
go
with,
but
I
agree
with
the
well
like,
with
localization
being
a
more
formal
sub
project
and
as
that
thing
grows,
I
think
this
is
something
like
we'll
be
able
to
solve
more
permanently.
A
Does
anyone
want
to
have
like
any
other
things
because,
like
before
we
wrap
up
I
just
wanted
to
for
like
the
new
contributors
like
who
haven't
made?
Any
contributions
like
I
wanted
to
show
them
how
they
can
like
go
ahead
and
like
find
issues
and
good
first
issues
to
get
started
with?
So
we
can
do
that
if,
unless
anyone
wants
to
bring
something
up
so.
A
Okay,
all
right,
let's
proceed,
so
this
is
the
repository
where
the
main
documentation
is
kept
and
there
are
like
guides
and
some
stuff
which
I
would
recommend
you
to
read.
But
I'm
gonna
keep
this
like
super
quick,
since
we
are
short
on
time.
So
as
a
new
contributor,
the
first
thing
I
would
recommend.
A
Is
you
hop
onto
the
issues
section
and
then
go
to
this
labels
thing,
and
there
is
a
label
called
good
first
issues
which
are
issues
specifically
for
new
contributors
and
right
now,
like
as
a
new
contributor,
I
I
feel
I've
seen
some
people
struggle
with
this
is
that
some
issues
have
already
already
been
assigned
and
they
get
confused
if
there
are
for
grabs
or
something
like
that.
A
So
this
particular
issue
is
like
19
days,
was
open
19
days
ago
and
is
up
for
grab,
so
you
could
just
go
to
that
and
read
more
about
it,
and
what
I
would
recommend
is
that
if
you
feel
confident
enough
to
like
like,
if
you
feel
that
you
want
to
take
this
up,
then
just
assign
this
to
yourself
using
this
command
so
that
ways
everyone
in
the
project
knows
that
you
are
working
on
it
and
one
other
thing
I
would
also
like
to
suggest
is
that
for
issues
which
are
like
old
and
you
see,
assignees
feel
free
to
like
start
a
discussion
even
on
those
issues
that
hey
this
issue
has
been
open
for
too
long
like
because
sometimes
people
assign
issues
and
they
like
don't
get
time
to
work
on
it
and
that's
totally
fine,
but
the
assignment
Still
Remains.
A
So
if
you
want
to
pick
those
issues
up,
it's
totally
okay
and
normal
to
have
that
conversation
that
hey
this
issue
has
been
assigned
to
someone,
but
they
haven't
been
able
to
get
to
it,
can
I
work
on
it
instead.
So
this
is
something
like
I
would
totally
recommend.
You
not
hesitate
with,
and
those
were
the
two
main
things
I
wanted
to
talk
about,
because
I've
been
like
getting
a
lot
of
messages.
A
Requests
with
this
like
they
are
not
many
good
first
issues
and
they
seem
to
be
a
sign
like
we
agree
that
like
there
are,
we
could
have
a
lot
more
good
first
issues,
but
for
the
current
ones,
I
would
suggest
this
is
the
approach,
but
other
than
that.
Also,
please
feel
free
to
take
up
any
issues
which
are
have
been
labeled
like
triage
accepted,
because
that
means
that
they
have
been
like
actively
working
us
like
they
have
been
triaged
and
you
can
like
continue
working
on
them.
A
I
would
not
recommend
like
jumping
into
issues
which
have
the
label
need
triage,
not
like.
You
cannot
do
that,
but
I
feel
like
you
would
have
a
easier
time
working
on
an
issue
which
has
been
labeled
with
triage
accepted
other
than
that
you
can
also
filter
issues
by
language.
A
Which
is
just
searching
for
that
language?
Sorry,
what
is
happening
yeah,
so
you
can
search
based
on
what
language
you're
comfortable
with,
and
so
this
is
one
thing
you
can
do
as
new
contributor.
The
other
thing
I
would
also
recommend
a
lot
of
people
do
is
try
reviewing
pull
requests
like
it
might
feel
a
daunting
task,
and
you
might
have
this
notion
that
you
need
to
make
for
few
PRS
or
solve
a
few
issues
to
like
get
started
with
reviewing,
but
that
is
totally
not
the
case
like
a
lot
of
the
times.
A
If
you
like,
review
peers,
you'll
you'll
have
like
some
suggestion,
like
maybe
you
found
a
typo
or
something
you
feel
like
would
be
indented
better
or
something
or
the
other.
You
I'm
sure
you
will
find
in
peers
and,
as
you
look
through
the
pias
and
the
discussions
there,
that
will
also
help
you
to
learn
more.
So
don't
feel
that
you
need
to
stop
because,
like
you
can't
review
prprs
because
you're
just
getting
started
like
I.
Think
honestly,
I
have
reviewed
like
more
of
this
nitpicking
sort
of
thing.
A
In
this
repository,
more
than
like
I
have
made
PRS
to
the
repository,
so
that's
totally
normal
and
if
you
feel
like
you
don't
like
reviewing
big
PR's
is
like
tough,
then
you
can
sort
by
these
labels
like
excess
means.
It's
a
very
small
line.
A
Change,
so
just
go
with
that,
and
the
way
to
review
PRS
is
that
you
go
to
files
changed
and
see
all
the
changes,
and
if
they
look
good,
then
you
unofficially
like
approve
them
by
saying
L,
GTM
I'm,
saying
unofficially
here
because
like
to
add
this
label,
actually
you
might
need
to
be
a
reviewer
for
the
repository
which
you
are
not,
but
even
if
you
like,
are
not
and
still
put
that
label
I'm
telling
you
that
that
is
helpful
for
other
reviewers,
because
more
eyes
on
a
PR
is
always
good.
A
So
those
were
the
main
things
we
wanted
I
wanted
to
cover
in
this
call,
and
since
you
were
running
short
on
time
and
I,
don't
want
to
like
barge
on
anyone's
calendars
anymore.
I
think
like.
If
anyone
has
any
questions
like
we
can
do
that
and
then
end
the
call.
A
Or
I
know
questions,
then
cool
I
think
we
can
like
if
we
start
to
see
more
attendance
and
like
the
introductions
taking
a
lot
of
time,
we
can
start
to
increase
the
meeting
length,
but
for
a
couple
of
months,
let's
see
the
kind
of
attendance
we
get
and
stick
with
this.
A
So
let's
continue
all
the
discussion
asynchronously
on
slack.
If
you
have
any
questions,
doubts
as
all
this
is
like
post
on
the
sick,
docs,
Channel
or
DM
me,
if
you're
more
comfortable
doing
that,
although
posting
on
the
channel
is
recommended,
but
when
you
contributors
it's
totally
fine.
A
That
was
it
hope
to
see
a
lot
of
like
contributions
from
you
all
and
if
anyone
wants
to
like
any
new
contributor
feels
like
they
want
to
like
help
other
contributors
and
lead
this
meeting
or
something
then
also
that's
totally
doable
just
reach
out
to
me,
I
feel
like
the
more
people
we
have
helping
others,
the
more
we'll
grow
as
a
community.
So
that
has
been
it.