►
From YouTube: 5 tips for your first Istio io contribution
Description
#IstioCon2021
Presented at IstioCon 2021 by Albert Sun.
A first commit to Istio.io can be daunting and there is a large amount of learning and commitment required to contribute to Istio.io. By presenting my experiences, I want to encourage both people familiar and unfamiliar to Istio, to contribute. I also hope to give some insight on the PR process for contributing to Istio.io, and show some relatively easy first commit examples. I found a home in the Docs WG, and I hope to help introduce others to this community by helping with their first commit.
A
Hi
everyone,
I'm
albert
a
high
schooler
in
houston,
who
started
working
on
istio
de
io
last
summer.
In
this
talk,
I
would
like
to
share
some
of
my
experience
with
the
istio
community
and
what
I
learned
about
committing
to
istio.
This
talk
is
pretty
introductory
and
geared
towards
beginners,
as
well
as
those
who
are
thinking
about
contributing.
A
So
a
little
bit
about
myself
in
school,
I've
had
some
coding
and
web
development
experience,
but
it
still
was
my
first
step
into
anything
related
to
cloud
computing
over
the
summer.
My
first
commit
was
a
simple
documentation
fix
and,
after
that
I
added
the
automation
indicator
to
a
website
which
I'm
pretty
proud
about.
I
also
started
a
website
homepage
redesign
proposal
which
hopefully
has
helped
the
website
redesign
coming
soon.
So
here
are
some
links
to
the
things
I've
made
and
the
automation
indicator.
Was
this
check
mark
an
icon?
A
I
mean
icon
and
text
on
every
page.
That
shows
if
it's
tested
or
not,
which
I'll
talk
about
later-
and
this
is
a
screenshot
of
the
of
the
mockup
I
did
for
the
home
page
redesign
proposal
and
I
want
to
start
with
quote,
which
is
first
and
foremost
as
a
potential
contributor.
Your
changes
and
ideas
are
welcome
at
any
hour
of
the
day
or
night,
weekdays,
weekends
and
holidays.
A
So
the
first
step
and
the
most
valuable
part
of
working
on
istio
for
me
was
the
experience
and
skills
I
learned
and
still
in
any
open
source
project
is
a
learning
opportunity,
and
even
now,
I've
just
scratched
the
surface,
especially
as
a
new
contributor
issue
is
going
to
be
all
about
the
constant
learning
and
there's
so
much
going
on
on
behind
the
scenes.
It's
still
a
complex
project
and
istada
io
is
a
great
place
to
start
committing.
A
Next
would
be
to
familiarize
yourself
with
the
community
getting
to
know
others
and
reaching
out
to
ask
for
opinions
on
ideas
and
also
don't
be
afraid
to
create
issues
common
on
other
people's
work
and
more
esteal.
Work
is
organized
into
working
groups
and
issue.
The
iowa
falls
under
the
dog's
working
group.
Working
group
meetings
are
every
other
week
and
they
are
a
great
way
to
stay
updated
on
what
other
people
are
working
on
and
to
meet
other
hd
contributors
and
the
people
who
will
be
reviewing
your
first
pr.
A
So
here
are
some
links
to
join
the
discus,
slack
and
team
drive,
and
once
you
join
the
team
drive,
it
will
be
available
in
shared
drives
and
hidden
share
drives
right
here,
and
this
is
our
docs
working
group
meeting
notes
and
every
time
we
write
an
outline
or
an
agenda
here
and
then
during
the
meeting
we
add
notes
so
reading.
This
is
a
good
summary
of
what
we're
doing
every
time.
A
Small
changes
are
to
go
to
for
starters,
and
these
could
include
small
ui
changes
and
documentation
changes.
So
when
you
encounter
any
documentation,
issues
or
angular
parts
don't
be
afraid
to
help
an
example
of
a
small
ui.
Change
could
be
here,
which
is
matching
the
search
results
to
the
dark
theme
and
down
here,
which
is
fixing
the
padding
of
the
search
bar.
A
So
these
are
things
I
see
on
the
current
website,
which
can
be
fixed
and
the
large
changes
include
any
long-term
projects
and
for
those
it
would
be
best
to
create
an
issue
and
ask
for
other
people's
opinions
before
starting
to
work
on
the
commit
and
for
a
certain
large
project.
You
might
want
to
make
a
design
document.
A
A
So
our
website
runs
on
hugo
and
once
you
install
hugo
and
docker,
there's
actually
only
one
command
to
run
the
website
locally,
which
is
pretty
neat
and
the
easiest
way
to
make
a
contribution
or
change
to
change.
Documentation
would
be
go
here
and
edit
this
page
on
github
and
then
down
here,
create
a
new
branch
and
commit.
A
And
it
was
basically
a
dashboard
where
you
would
see
user
statistics
for
people
visiting
steel,
and
this
is
my
design
dock
for
the
main
page
improvements
which
included
the
screenshot
of
the
mockup
I
showed
above
so
another
way
to
help
is
writing
tests.
Recently,
we've
implemented
testing
to
our
website,
which
basically
automates
check
to
verify
documentation,
code
and
snippets
on
the
website.
A
A
You'll
see
that
the
the
code
and
blocks
or
the
commands
match
up
with
these
tips
functions
on
the
snip
style
sh
and
in
the
test.sh
file.
It
calls
the
functions,
and
eventually
the
goal
of
this
website
is
to
is
to
validate
that
you
installed
it
correctly,
and
here
it
will
verify
the
installation
by
running
the
commands
on
this.
A
A
Okay,
in
my
experience,
the
pr
process
is
extremely
smooth
and
everyone
is
helpful
and
for
your
first
pr
we
are
all
extremely
excited
to
help
you
get
it
accepted.
I've
never
worked
on
an
open
source
before,
and
one
thing
that
stood
out
was
how
detailed
the
process
was
after
the
majority
of
work
is
done.
On
the
initial
request.
There
are
always
so
many
new
suggestions
and
ideas
for
reviewers
which
help
a
lot.
A
So
after
you
submit
a
pr
you'll,
see
a
checklist
like
this,
where
everything
needs
to
get
accepted
or
corrected,
and
one
thing
you
one
neat
thing
you
can
do
is
view
view
the
figure
changes
as
if
they're
live.
So,
for
example,
if
we
go
to
the
disco,
this
pull
request,
which
is
the
new
website,
and
we
can
actually
preview
it
by
clicking
here,
which
will
see
the
new
website,
which
is
pretty
cool.
A
And
sometimes
you'll
have
a
lot
of
times.
You'll
have
lint
errors
and
you
can
run
make
lint
locally
to
verify,
changes
and
check
for
problems
and
the
linter
basically
checks
that
there's
no
spelling
errors
and
all
the
links
work
and
you
follow
the
formatting
properly
and
also
don't
forget
to
update
and
or
create
a
test
for
a
page.
If
you
change
the
document
documentation
for
it,.