►
From YouTube: [SIG Docs] New Contributors Meet & Greet for 20230905
Description
[SIG Docs] New Contributors Meet & Greet for 20230905
A
Okay,
I
see
that
we
have
not
folks
joining
so
usually
what
happens
in
these
calls
are,
first
of
all
we
go
around
introducing
ourselves
and
like
if
you're
someone
who
is
new
to
contributing
to
if
you're,
just
getting
started
with
contributing
to
sick,
docs
or
kubernetes
in
general.
You
can
ask
your
questions
here
and
yeah.
You
can
get
help
one
how
you
can
go
forward
so
I'll
start
by
introducing
myself.
A
C
E
F
So
yeah,
my
name
is
arvind.
I
am
currently
a
p-tech
student
in
India
and
I'm
pretty
much
a
beginner
with
kubernetes
I
just
know
the
basics
of
it,
and
I
just
saw
that
there
was
this
call
of
sick
dogs,
so
I
thought
of
joining
it.
Then
I'm
I'm
willing
to
contribute
to
the
kubernetes
GitHub
project,
so
yeah
nice
job
nice
to
meet
you.
B
A
E
I
have
I
have
taken
an
issue,
but
it
doesn't
go
well.
I,
don't
know
how
to
fix
it
and
the
I
think
it's
for
the
kpng
stick
and
they
asked
they
asked
me
to
update
their
data
action
in
Docs
and
I.
Don't
know
what
to
what
to
update
I
mean
I
can
understand.
The
fires
like
it
was
kind
of
test
scripts
to
get
help.
Action
are
running
but
I,
don't
know
how
to
I
I
don't
have
like
a
example
there
for
me
to
copy
how
to
write
a
good
documentation
there.
D
A
G
A
D
So
the
channel
is
always
best
as
a
broader
as
a
broader
audience,
and
also
link
the
issue
that
you're
talking
about,
so
that
people
can
click
on
it
and
then
understand
the
question
that
you're
asking
that's
always
really
good.
Just
just
saying
like
the
issue
or
PR
number,
it's
we
wanna.
We
want
you
to
make
it
as
easy
as
possible
to
get
help.
So
adding
links
to
the
things
that
you're
talking
about
is
always
worthwhile.
D
You
that's
okay,
it's
but
again
it's
something
that
you're
learning
it's
a.
It
can
be
hard
in
open
source
to
think
that
or
know
that
you
can
ask
questions,
but
the
slack
Community
exists
exactly
for
that,
so
that
collaboration
can
be
easier
and
that
there's
also
a
a
larger,
let's
say
audience
for
collaboration.
So
on
issues
and
PR's.
Unless
someone
is
clicking
into
this
or
maybe
tagged
already
in
that
issue
or
PR,
no
one
else
maybe
will
see
it.
So,
on
the
slack
you
get
a
bigger
audience.
A
A
A
F
F
C
D
Was
about
to
say,
for
everyone
feel
free
to
also
explore
in
the
slack
Community
a
lot
of
the
other
channels
just
to
even
see
how
folks
are
collaborating,
what
kinds
of
questions
they're
asking
a
lot
of
the
times
that'll
help
you,
you
know,
think
about
other
things
that
you
either
possibly
want
to
ask
or
even
learn
some
new
things
as
well.
So
what
sriram
already
linked
and
and
posted
in
the
chat,
the
kubernetes
new
contributors,
Channel,
that's
always
really
good
to
join.
D
There
will
be
a
lot
of
traffic
there.
So
the
one
thing
I
want
to
note
is
that
don't
feel
too
much
pressure
that
you
must
follow.
Everything
I
understand
what
your
own
capability
is
in
terms
of
following
along
with,
what's
going
on,
but
another
really
good
channel
that
you
might
want
to
think
about
joining
there's.
Also,
a
lot
of
different
work,
around
seeker
and
Bex
was
was
mentioned
already
by
Arvin,
which
is
great,
that's
a
great
channel
to
join
and
I'd
even
say
joining
things
like
the
announcements
channel.
D
So
you
can
understand
across
the
project
what
information
is
being
sent
out
and
and
why
we
just
for
example,
we
recently
freezing
the
the
Google
has
package
repositories
for
some
of
the
work
that
we're
doing
across
the
project
and
that
you
know
we're
going
to
be
pushing
it
to
a
different,
a
different
URL
and
a
different
kind
of
namespace.
Now.
So
things
like
this
that
affect
docs,
for
example,
because
we
have
to
update
our
docs
to
reflect
this
and
so
on.
D
E
A
D
That's
a
really
great
way
to
start
contributing
where
you
can
contribute
to
an
update
to
the
documentation
that
you're
using
to
learn,
and
that
could
be.
Maybe
you
think
it's
worthwhile
rearranging
some
of
the
content,
because
it
makes
sense
this
way
better
for
you
or
maybe
you
find
lots
of
spelling
errors,
and
then
you
know
punctuation.
That
needs
to
be
fixed
up
alongside
the
Improvement
to
the
to
the
to
the
page
itself.
We
do
have
a
small
thing
about
trivial
edits.
We
don't
want
you
to
just
fix
one
comma
or
one.
D
A
A
So
I
can
personally
recommend
that,
because
I
had
been
a
PR
final
Shadow
under
Nate,
it's
a
different
member
of
the
feed
dogs
team,
but
you
can
also
work
with
an
athlete
like
in
the
week
that
she
is
the
pr
anger
and
you
can
learn
how
to
cuts
are
reviewed
and
what
it
is
that
the
maintenance
are
like
what
it
is
that
makes
a
PR
good.
Then
you
can
apply
those
to
the
changes
that
you
yourself.
Thank
you.
A
G
G
A
A
This
is
one
way
you
can
be
active
in
the
community
and
find
Opportunities
to
contribute
all
right.
If
you
are
specifically
interested
in
like
a
certain
area,
like
you
said
that
the
code
base
was
you
found
the
code
base
to
be
really
huge
right.
So,
if
you're
interested
in
any
particular
area
like
networking
or
the
CLI,
they
all
have
their
own
special
interest
groups
and
they
have
like
bi-weekly
meetings
and
so
on,
which
you
can
be
part
of.
D
What
that
means
is
that
we
don't
write
all
of
the
docs,
because
when
a
new
feature
is
created,
the
feature
Creator.
The
thing
that
owns
this
needs
to
actually
write
a
lot
of
that
documentation
as
they're
the
technical
owners
of
that
work.
However,
we
own
how
the
style
of
the
documentation
needs
to
go,
we
own
how
people
are
reading
and
consuming
our
documentation.
We
own
how
it's
deployed
via
Hugo
and
netlify,
and
we
own
the
website
itself,
and
we
also
help
the
documentation.
D
Writers,
write
better
documentation,
but
a
lot
of
sometimes
the
content
of
that
that
dot,
that
documentation
is
still
owned
by
the
creators
of
the
code.
So
that's
something
that
is
a
as
an
example,
an
ownership
area
that
we
have,
then
you
have
other
areas
like
Sig
release
is
another
interesting
area
that
special
interest
group.
D
They
own
the
release
process
which
for
kubernetes
we
cut
three
releases
every
year
and
they
also
own
how
the
release
is
structured
and
and
put
together
via
a
release
team
and
that
team
changes
every
release
so
that
we
have
different
members
of
our
community
taking
part
in
helping
kubernetes
push
its
next
release.
We
are
actually
up
to
release
1.29
and
it's
just
started,
and
so
this
will
continue
for
the
next
four
months
until
the
end
of
the
year.
So
that's
another
area
of
ownership
in
the
project,
for
example.
D
D
Yeah
great
question:
if
you
are
joining,
if
you're
in
this
I
really,
firstly
recommend
that
you
join
the
slack
kubernetes
slack
and
then
you
join
the
Sig
docs
Channel,
which
I
would
just
write
out
here
and
then
in
this
specific
Channel,
I'll
link
them
in
the
chat
for
you.
But
we
have
pinned
messages
that
give
you
a
link
to
specifically
our
contribution
guide.
D
D
Docs
that
might
be
of
interest
to
some
people.
We
also
have
a
sub-project
around
localization,
so
our
documentation
is
available
in
15
different
languages
for
kubernetes,
which
includes
English,
but
we
also
have
docs
in
a
lot
of
different
languages
and
if
you're,
a
native
speaker
of
a
different
language,
you
can
look
to
see
if
that
language
is
available
there
for
you
to
also
contribute
there
as
well.
D
We
have
some
languages
that
are
still
launching
and
still
working
as
well,
so
you
can
always
use
the
kubernetes
slack
to
find
your
language
specific
channel
to
offer
to
help
to
see
what
what
good
first
issues
they
may
have
and
so
on,
and
that's
also
another
area
of
docs
that
is
worthwhile
contributing
to.
If
you
have
a
different
language
that
you
speak
and
you're
able
to
review
that
kind
of
work.
A
Yep
and
adding
to
what
Natalie
said
both
these
sick
dogs,
SLS,
the
sick
dogs,
localization
subgroup,
they
have
bi-weekly
meetings
and
usually
it's
like
the
localization.
If
the
localization
subgroup
meeting
is
today
the
six
doc
Smith
would
be
tomorrow
and
yeah.
We
have
the
sick
dogs
meeting
today
in
a
couple
of
hours
and
yeah.
If
you're
interested,
you
can
join
that
as
well.
D
D
I
believe
that
is
I,
believe
that's
a
nicer
time
for
Canada,
but
I
believe
it
is
around
11
or
11
30
p.m,
across
India
as
an
example,
so
you
don't
have
to
join
meetings
that
late
I
just
want
to
be
very
clear,
manage
your
time
as
a
contributor,
but
but
yeah.
Those
meetings
are
always
in
the
agenda
that
I
can
quickly
link
here.
They
are
also
notes
for
taken
in
the
specific
agenda
that
you
can
always
kind
of
go
back
to
and
refer.
A
G
G
A
Knowledge
of
goal
is
not
mandatory,
although
it
would
help
in
some
cases
but
yeah.
You
can
definitely
check
out
other
issues
like
if
you're
trying
to
add
something
to
the
CLI.
Let's
say
you
can
yeah
learn
whatever
you
need
based
on
the
requirements.
I
guess
it
would
definitely
help.
If
you
have
a
understanding
of
the
basics
with
this
website
might
be
able
to
help.
You.
D
So,
for
a
generally
contributing
to
the
project,
it's
worthwhile
understanding
at
a
high
level.
What
kubernetes
is
and
does
so
there's
a
lot
of
interesting
and
good
documentation?
You
can
look
on
our
kubernetes
docs
itself
to
just
generally
understand
what
kubernetes
is
doesn't
mean
that
you
have
to
know
intricately.
How
did
programming
go
just
yet,
but
understanding
the
different
parts
of
kubernetes?
A
And
as
Natalie
had
mentioned
earlier,
you
can
use
the
documentation
for
Learning
kubernetes
and,
at
the
same
time
you
might
find
a
click
when
you're
using
the
documentation
to
learn
kubernetes.
You
can
look
at
it
like
how
would
I
improve
the
recommendation
so
that
somebody
else
who
was
learning
this
for
the
first
time
finds
it
easier.