►
From YouTube: Keptn Documentation Office Hours - Mar 09, 2023
Description
Meeting notes: https://docs.google.com/document/d/156pqw4r_O6O7O-YDm9DfuuBUS3GvAXmvjjDyFEpbwUY/edit
Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews
B
A
I
I
have
no
idea
who
started
it,
because
baby
was
on
the
call
when
I
joined,
but
no
one
was
apart
from
us.
B
B
A
D
B
D
B
B
Actually
lets
me
see
if
it
will.
Let
me
share
my
screen.
B
E
B
Okay,
add
your
name
there.
It
is
so
we're
here.
This
is
my
proposed
agenda.
It's
up
to
everybody
else.
What
we're
going
to
do
this
is
a
community
meeting.
We
can
pretty
much
do
anything
within
reason.
B
I
thought
I
would
briefly
go
over
the
proposed
back
structure
since
it's
pretty
so
you
can
see
that
where
we're
headed,
we
have
finally
got
the
contributing.md
file,
merge
I
thought
we'd,
look
at
it
and
depend
on
who
shows
up.
We
have
a
couple
of
people
who
are
trying
to
contribute
to
the
docs
who
are
pretty
new
to
GitHub
and
are
totally
confused
by
everything.
So
if
we
have
people
like
that
here,
we
can
walk
through
if
not
we'll
just
skip
it.
B
A
mention
about
style
guide,
look
at
a
couple
of
open,
PR's
and
then
discuss
for
how
many
years
I
mean
I,
know:
you've
got
stuff
going.
I
you've
got
open,
PR's
too
right,
you're,
working
away
on
stuff,
yeah.
A
So
I
I
have
I
have
started
working
on
two
things.
The
first
one
is.
A
Restructuring
in
which
I
think
Adam
is
facing
some
issue,
he
is
not
able
to
see
the
difference
between
the
control,
plane
and
and
one
more
thing,
I
forgot,
but
it's
there
I
have
not
changed
anything
I'll,
look
into
it
again,
the
the
pr
which
I
the
link
of
the
pr
which
I
gave
to
you
as
well.
A
And
the
second
thing
is:
I:
I
have
started
working
in
on
the
captain
life
cycle,
12-ft
demo
for
on
killer
Coda,
but.
A
It's
a
little
complex
for
me
because
it
involves
scripting
and
other
things
as
well,
so
I'm
just
looking
into
it
and
at
the
same
time,
learning
so
we'll
keep
doing
and
as
soon
as
I
reach
a
solid
platform,
I'll
I'll,
let
you
know.
B
A
B
And
it's
amazing
how
it
is
I.
You
know
the
first
one
I'm
Donald,
Adam
and
I
worked
on
together
and
all
I
did
all
I
dealt
with
was
content.
It
takes
a
lot
of
work
to
get
the
content
right
and
to
you
know,
there's
places
there
where
you
have
to
wait
for
three
minutes
while
killer
Coda
sets
things
up
so
that
some
people
aren't
just
sitting
there
bored
you
know,
use
the
time
to
give
them
something
to
do
or
something
to
read.
So
it's
a
fun
project.
B
A
Yeah,
so
can
you
just
give
me
the
link
of
this
dog
because
I
always
you
know,
misplace
this
link
now.
B
Okay,
let's
see
if
I
can
get
to
it
all
right,
because
I
have
something
up
here,
telling
me
that
somebody's
running
close.
B
Where
I'm
seeing
I
get
stuff
in
there
there
we
go.
B
It
I
say:
okay,
we'll
get
the
copy
link,
gotcha
yeah,
it's
late
enough
in
the
day,
I
should
be
coming
to
life,
but
I'm,
not
obviously
so
now,
where.
B
A
E
A
I
always
struggle
finding
Zoom
chat
as
well.
B
B
B
This
is
in
an
issue
that
was
approved
a
couple
of
weeks
ago
at
the
refinement
meeting.
I
think
it's
caused
called
anybody
who
wants
to
go.
Look
at
it
from
where
detail
can
later
you
may
I
mean
the
docs
right
now
are
for
klt
are
kind
of
a
mess.
B
This
could
change
in
the
future
or
whatever
it's
probably
not
perfect,
but
it
was
a
structure
that
we
can
get
started
and
get
populated
and
get
some
stuff
written
up,
which
is
amazingly
easy
to
move
stuff
around
later.
If
we
want
to
so
there
will
be
a
getting
started
guide
of
some
sort.
Hopefully
we
will
have
a
killer,
Coda
demo
to
use
there
right
now
we
have
something
which
is
probably
what
so
something
called
the
product
overview
or
intro.
B
Right
now,
it's
called
intro
to
klt,
but
it's
sort
of
a
high
level
overview
of
what
this
product
is
and
why
you
would
want
it
and
probably
some
links.
We
have
a
lot
of
people
who
do
really
good
videos.
They
go
around
to
conferences,
so
we'll
have
some
links
in
there
for
that
functional
architecture,
overview
architecture
and
Amisha
is
working
on
drafting
this
as
we
speak.
B
This
is
the
getting
the
product
overview
is
for
people
who
are
brand
new
to
this
and
want
to
know
the
basics.
The
architecture
overview
should
be
kind
of
a
deep
dive
for
people
once
they
get
knowing
what
they're
doing
they
want
to
know,
what's
really
happening
under
the
hood.
It's
essential.
They
know
that
when
something
goes
wrong,
so
they
can
debug
it.
B
It
will
take
a
while
to
get
this
together,
but
we'll
like
everything,
we're
going
to
make
incremental
improvements
and
we'll
be
surprised
in
a
few
months.
How
much
better
things
will
be
installation
right
now
we
have
almost
nothing
about
installation.
The
getting
started
guide
just
tells
you
how
to
install
what
you
need
for
that
and
there's
a
lot
of
things.
So
we
need
a
whole
section
that
goes
through
every
possible
step
of
things.
B
You
need
to
do
for
installation
again,
we'll
start
with
the
easy
step
and
we'll
keep
adding
that
and
then
there's
the
user
guide
for
how
to
define
and
manage
a
klt
project.
I
call
it
a
project.
It
probably
should
be
called
an
applicant
application,
but
all
the
stuff
about
defining
your
crds
and
putting
it
together
and
all
of
that
and
then
we'll
have
some
reference
pages
right
now
for
definitely
API
crd
reference.
Pages
we're
still
working
on
the
format.
There
are
some
up
there.
We
want
them
to
be
auto-generated
from
the
source.
B
I
want
a
little
more
text
in
than
you
get
so
we're
working
on
how
we
do
that
and
what
those
are
going
to
look
like.
So
we
have
a
start.
There
will
be
a
lot
of
work
coming
and
then
we're
going
to
do
a
contributing
guide
for
those
who
used
to
GitHub.
Traditionally,
every
repo
have
the
contributing.md
file
in
it.
That
tells
you
what
you
need
to
know
to
contribute.
B
Our
story
is
pretty
complicated.
We
end
up
because
we've
got
software
and
docs
in
the
same
repo.
We
have
two
different
contributing
files
and
they've
got
duplication
and
there's
some
in
one
of
them.
That
applies
to
both
and
it's
all
kind
of
a
mess,
and
we
think
it
would
be
cleaner.
If
we
just
had
a
separate
continuing
guide,
we
may
eventually
have
technical
product
information
that
will
be
only
relevant
to
people
who
are
contributing.
B
A
So,
are
you
thinking
about
having
a
separatory
for
contributing
guide
or
or
is
there
anything
in
between
I
missed.
B
A
separate
repo
for
the
docs
okay
yeah.
No,
the
engineering
team-
wants
to
have
the
docs
in
the
same
repo
as
the
software
I
have
some
reservations,
but
but
we'll
work
on
it.
They
it
seems
that
they
feel
it's
easier
for
if
it's
all
in
one
place,
so
so
for
the
foreseeable
future,
they
will
both
be
in
the
same
repo.
B
B
B
Okay,
so
that
is
that
next
up
actually
I
think
are,
are
any
of
you
not
familiar
with
Yasha?
Have
you
done
any
GitHub
before.
E
B
Of
the
people
who've
been
bugging
me
for
this
here,
Blitz
gift
offer.
If
anybody
needs
help,
the
contributing.md
file
for
docs
is
finally
merged
and
beginning
in
line
147..
The
one
thing
I
would
caution:
you
we've
already
had
one
person
get
burned
and
I
myself
have
done
this.
So
when
you
finish
working
on
one
branch
and
you
push
it
and
you
want
to
start
something
new
be
sure
to
go
back
and
pull
down
the
current
version
of
Maine
before
you
before
you
do
your
checkout
Dash
B.
B
Otherwise
you
will
end
up
with
your
next.
Pr
will
have
what
was
in
the
previous
PR,
as
well
as
the
new
one,
the
person
who
did
it.
It
was
fairly
easy
to
clean
up.
She'd
only
done
one
file
when
it
happened
to
me.
I
had
18
files
and
it
was
a
mess,
though
style
guide.
We
don't
really
have
one
I
have
to
confess
that
I'm
not
a
huge
fan
of
style
guides.
They
are
useful.
It's
nice
to
get
some
consistency.
B
I
am
sort
of
proposing
that
maybe
we
just
used,
then
we
can
all
effort
our
own.
It's
pretty
good
I,
don't
know
we're.
Certainly
not
enforcing
you
things,
but
if,
if
you
need
anything,
it
does
have
a
lot
of
good
advice
in
it
and
it
on
its
first
page.
It
says
if
you
make
the
documentation
better
by
violating
the
style
guide.
Please
do
it
so
I
like
their
attitude,
but
it
is
there
if
you
need
help
on
things.
B
One
of
the
things
they
have
is
a
very
nice
comprehensive
list
of
terminology
products
and
actions
and
all
sorts
of
things.
So
if
it's
useful
to
you
use
it,
the
one
thing
that
we
would
that
we
really
do
need
to
do
is
a
word
list
for
Captain
terms,
and
so
in
that
vein,
I
started
and
I
mean
started
a
Google
doc
that
should
be
open
to
everybody.
B
And
basically,
if
it's
something
that
you
want
to
know,
you
know,
can
kubernetes,
does
it
always
have
to
be
spelled
out
or
can
we
use
k8s
the
short
term
for
it?
Helm
versus
Helm
can
I
use
lowercase
Helm
when
I'm
talking
about
Helm
chart
or
only
for
a
command
Proctor.
We
don't
have
a
whole
lot
and
but
the
beginning
section
is
product
and
project
just
Global
stuff,
and
then
we
have
a
section
for
klt
specifics
terms
and
a
section
for
Captain
LTS
words.
B
If
you
have
any
questions,
feel
free
to
add
it
here.
When
we
get
enough,
we
will
either
in
this
meeting
or
community
meeting,
we'll
start
going
through
them,
one
at
a
time
and
discuss
as
a
group
what
we
want
to
do
and
what
we
don't
and
then
I
will
use
that
to
generate
our
own
word
list
over
time.
B
So
but
again,
it's
not
the
end
of
the
world.
Okay,
open,
PRS,.
B
I
have
one
that
I
hoped
was
going
to
be
closed
by
the
time
we
met,
but
it
didn't
work
out,
but
it
will
be
soon
the
for
those
of
you
who
started
with
our
docs.
We
have
getting
started
and
we
have
a
little
intro
to
klt
in
it,
and
so
this
is
and
I
already
pulled
up,
Netflix
on
it.
So
here
we
go,
it's
not
wonderful,
it
needs
to
be
expanded,
but
this
is
the
beginning
of
just
an
introduction
for
new
people
and
it
will
be
merged
soon.
B
B
Okay,
Amisha
you
want
to
share.
Do
you
I
will
stop
sharing?
Do
you
want
to
share
your
screen
and
show
us
what
you're
up
to.
F
So
I
created
a
architecture
related
information
where
I
am
thinking
to
give
the
brief
about
every
directory
is
here
so
I'm.
Thinking
about
this
idea
and
I
want
to
know
if
this
is
good
to
go
or
not,.
F
Yeah
yeah
this
in
this
way,
we
can
like
give
a
brief
about
every
directory
that
what
each
directory
is
going
to
do
with
that
thing,
particularly
so,
is
it
good
to
go
or
not?
I
just
want
the
clarification
about
this.
B
I
like
it,
what
is
everybody
else
like
have
any
of
the
rest
of
you
tried
to
look
at
the
repo
for
the
project.
A
Code
for
the
life
cycle
toolkit
I
have
not
yet
because
I
haven't,
you
know
dive
deep
into
it,
but
I'll
shortly
do
when
I'll
deeply
start
for
making
killer
color
demo.
Maybe
maybe
then
I
will
be
able
to
participate
into
this
issue.
A
You
know
it
will
be
easy
for
me
to
navigate
between
the
files
as
well
right.
C
Because
beginner
also
faced
this
issue
that
which
code
lies
in
which
file
and
in
which
directory.
So
it's
a
good
thing
like
I,
also
like
this
idea
right.
E
F
B
B
D
B
Another
trick
here
too
small.
F
B
B
Small
PRS
are
good.
Incremental
improvements
are
better,
you
know,
there's
you.
B
I
you
know
I
started
out,
I
was
thinking
of
the
term
paper,
I
couldn't
publish
it
until
it
was
complete
and
wonderful,
and
you
know
everything
and
it's
like
a
little
bit
I
think
this
much
will
help
a
lot
of
people
out.
It'll
help
them
out
more
when
you
get
more
populated
in
but
incremental
steps.
So
I
think
this
looks
better
ready
for
review.
Let's
see
what
the
gang
says.
F
And
the
one
more
thing
I
want
to
suggest
that,
like
one
thing,
can
you
see
this
link.
B
F
B
F
So
I
am
thinking
about
the
readme,
also
that
the
readme
is
right.
Now
we
have
a
very
cluttered
readme
with
the
architecture
description.
So
what,
if
we
like
said
the
links
and
all
the
things
with
that
and
remove
the
architecture,
descriptions
and
set
the
links
of
docs
there.
F
That
would
be
more
clear
and
like
more
in
enhanced
right,
because
I.
B
Think,
once
once
we
take
the
part
of
it
is
the
engineers
are
much
more
comfortable,
just
writing
up
what
they
know
in
a
readme
file.
Then
they
are
getting
into
the
back.
So
there's
other
exceptions,
but
a
lot
of
them
in
general.
I
do
not
expect
to
go
to
the
readme
file
and
Wade
through
it
and
find
the
architecture
description
once.
E
B
Get
that
with
and
it
and
they
of
course
they
say
they
want
it
and
read
me
because
it's
easier
for
them
to
keep
up
to
date,
but
you
notice
they
have
not
kept
us
up
to
date.
So
it
would.
You
know
human
nature
and
they're
wonderful
people.
So,
but
when
you
get
this
into
the
documentation
and
we
get
it
updated,
so
it's
accurate
and
we
merge
it.
B
Then
I
think
we
go
back
and
take
that
content
out
of
the
readme,
because
we
don't
you
know
it
will
be
very
confusing
to
people,
because
the
two
are
not
going
to
match,
because
the
readme
information
is
not
up
to
date
and
yours
will.
B
E
B
You
and
you
can't
always,
you
know
very
appropriate
for
readme
file
to
say
if
you're
looking
for
an
architecture,
description
go
here,
it
may
be.
E
F
E
F
For
the
architecture,
I
was
like
I.
The
diagram.
F
I
would
need
to
create
this
recreate
this
with
mermaid,
so
I
will
I
will
recreate
the
component
architecture
with
the
mermaid
feature.
Excellent.
D
Just
just
I
did
not
say
you
should
I
just
recommend
it,
because
mayor
made
this
so
I
could,
if
you
like,
I,
can
also
give
you
a
short
introduction
to
mirror
mate
and
show
you
what
what
it
actually
does.
F
D
Yeah
I
will
show
shortly
there's
a
really
good
live.
Editor
called
me:
I
made
life,
so
I
even
tried,
with
your
graphic,
tried
around
what
we
can
do
and
what
would
be
what
would
be
maybe
a
a
good
way
to
handle
it.
So
there
are
different
types
of
of
diagrams,
so
you
can,
you
can
create
sequence
diagrams.
You
can
create
flow
diagrams
class
diagrams
and
everything
really
as
a
it's.
Not
it's
not.
D
It
doesn't
look
really
beautiful,
but
in
the
end,
but
it
it
it
offers
it
offers
our
basic
basic
needs
and,
for
example,
as
I
choose
now
the
Mind
map,
for
example,
for
for
this
diagram
you
had
because
from
it
it
looked
the
best
compared
to
who
have
the
flowchart
still
the
compared.
So
we
have
here
this.
This
is
some
attempt
what
I
did
with
the
flowchart,
for
example-
and
this
is
as
a
and
this
is
the
attempt
with
the
Mind
map-
and
it's
quite
easy
because
the
mind
map,
for
example,
I,
have
my
beginning.
D
With
my
note,
then
I
say
there
is
the
operator
with
its
sub,
with
its
with
the
operators
with
the
life
cycle
and
the
Matrix
operator
and
I
can
easily
add
here.
Another
operator,
like
the
I,
don't
know,
call
it
tooling
operator,
tooling
operator
and
the
good
part.
I
can
also
add
a
fancy
scheduler
here
and
I
could
add
here.
Another
documentation,
part
and
the
cool
part
about
this
is
this
is
code
and
GitHub
also
is
able
to
render
this
code
so.
D
D
D
So
they
are
actually
able
to
render
those
flowcharts
and
we
can
even
Hugo
is
able
to
render
those
and
those
diagrams
are
easy
to
adapt
because
other
diagrams,
if
we
do
them
with
a
graphical
tool.
It's
always
the
question
which
graphical
tool
was
used,
how
to
store
those
those
files
for
the
graphical
interface
if
we
want
to
extend
them
Etc
and
when
we
write
them
as
code,
we
can.
This
is
easily
read
and
easily
adaptable
for
close
to
everybody.
Let's
say
that
way.
So.
D
B
Can
I
put
it
into
a
markdown
file
yeah.
B
F
D
Tool
to
create
those-
and
it's
and
it's
also
we
can-
you-
can
change
them
in
a
pull
request
easily,
because
you
can
just
suggest
edits
to
the
to
the
markdown
file
rather
than
saying
hey.
We
need
to
do
this
now
differently
or
things
like
that,
because,
for
example,
we
have
this
issue
with
the
captain
documentation
that
some
of
those
some
of
those
charts
are
outdated.
D
Now
somebody
needs
to
find
where
those
are
stored
or
need
to
recreate
them
manually
to
fix
those
issues
in
the
in
the
files
and
with
yes,
they
are
not
as
beautiful
as
you
can
make
them
with
a
with
a
nice
graphical
tool,
but
they
hit
the
purpose
really
well
really
well
too
too
early
really
well,
and
we
can
leverage
a
lot
of
features
from
them
and
they're
really
really
powerful.
E
B
D
D
E
You
know
we
don't.
Okay,.
B
There,
no
we've
got
the
wrong
thing:
okay,
I'll!
Do
it
after
we're
done
here?
Okay,
let's
see
ayush,
do
you
want
to
share
and
show
us
what
you're
up
to.
A
Yes,
I
can,
but
just
a
second
let
me
get
the
correct
yeah.
A
So
I
I
made
this
PR
in
which
I
structured
the
documentation
for
Captain
Helen
play
requisites
and
I
made
few
changes
in
in
in
one
PR,
but
the
mistake
I
did
is
I.
Also,
you
know
made
some
changes
in
contributing
dot
MD.
It
was
just
just
a
type
of
X
which
so,
which
was
not
a
good
practice
and
I'll
keep
in
mind
from
from
the
next
PR.
A
But
the
thing
is
that
so
what
I
did
is
I
basically
merged
two
pages
for
installing
captain
in
your
in
your
local
system
for
help.
So
if
you
go
to
documentation
and
in
installation,
so
I
basically
merged
Captain,
install
Captain
using
the
helm,
chat
and
and
choose
access
options.
So
these
two
pages
have
been
merged,
because
these
two
pages
contain
usually
the
common
content
right.
A
If
you
go
to
this,
you
see
that
there
are
options
given
to
you
to
you
know:
access
Captain
using
LM,
so
you
can
access
it
using
load,
balancer
or
notepad,
or
a
few
more
options,
and
when
you
go
to
LM,
it's
basically
the
same.
So
if
you
go
here,
you'll
get
options
like
if
you
want
to
have
an
Ingress
object
or
setting
up
Captain.
So
basically
it
was
same
and
it
was
using
Helen.
So
I
took
these
two
pages
combined
the
pages
into
one
and
made
a
PR,
but
the
thing
is
I.
A
Think
Adam
is
not
able
to
see
this.
This
part
of
of
the
content
in
in
my
merged
PR,
okay,
so
I
I,
will
I
will
just
say.
If
you
can
just
have
a
look
at
this
PR
and
you
know,
get
your
views
on
it.
I.
B
B
Please
there's
a
little
nasty
issue
here
that
we
need
to
deal
with
sometime
and
I
haven't,
but
that
installation
that's
up
at
the
top
is
not
for
the
latest
release.
A
Yeah,
so
it
was,
it
was
a
common
one.
I
think
it
would
be
applied
to
the
latest
one.
Only
maybe
you
can
have
a
have
a
look.
B
At
it,
it
is
fine
if
you
put
something
in
release-
one,
that's
not
in
the
main
one
up
above,
but
it
should
be
in
release
one
because
I
think
the
the
pre-release
one
docs
may
be
disappearing
fairly
soon,
at
least
from
the
page.
So,
yes,
let
me
go
and
I
will
go
and
take
a
look
at
this
and
see
what
you're
doing
yeah.
So
that
was
a
mess.
So
thank
you
for
addressing
it.
A
The
use
of
Weights
that
it's
for
you
know
proper
stretching
of
the
dog's
section
in
let's
say:
if
you
want
this
file
to
be
above
this
file,
so
you
have
to
give
them
the
weight
in
order.
B
Okay,
the
the
weights
are
not
of
that
that
numbered
list
on
the
landing
page
for
installation
is
not
automatic.
So
if
you
change
the
order
of
stuff,
you'll
need
to
manually,
modify
yeah.
A
So
I
I
I
exactly
did
that
and
explained
Adam
about
using
weights.
So
maybe
you
can
have
a
look
at.
He
mentioned
all
the
things
he
didn't
get
in
this
comment.
Okay,.
B
A
A
B
Yo,
that's
right!
Yes,
it's!
It
is
here,
okay,
good!
Does
anybody
else
have
anything
that
they're
working
on
that
they
would
like
to
show
or
ask
questions
about
or.
C
B
Yeah
that
right
now,
that
is
just
a
working
list,
that's
why
it's
a
Google
doc.
We
will
eventually
and
right
now
it's
it's
questions,
not
answers.
It's
do
I.
Do
this
or
this
or
this,
then,
when
we
discuss
those
at
the
community,
as
we
agree
to
things,
then
they
will
go
into
a
file
that
will
be
part,
probably
part
of
contributing
someplace.
B
C
Yeah
yeah
and
one
more
thing
like
we
can
do
like
this.
We
can
also
make
like
this.
A
captain
word
list,
like
the
CNC,
have
got
glossary
thing.
So
in
the
main
repo,
we
can
add
one
section
of
forward
list
so
that
if
anyone
is
beginner
and
if
anyone
don't
know
the
terms
that
for
can
refer
to
that
word
list
right.
B
Thank
you
and
very
few
people
are
in
fact
I.
Don't
think
anybody's,
yet
added
anything
to
it
except
me
and
I
haven't
been
real
good
about
getting
to
it.
So,
okay,
I'm
gonna,
go
back
and
share
my
screen
for
and
then
some
people
have
joined.
We
may
go
back
and
do
something
else,
but
for
the
contributing
guide
we
have.
B
We
have
what
we
call
an
f8
kit
is
an
issue
that
is
and
contains
a
lot
of
pieces
for
any
of
you
who
are
really
brand
new
to
this
and
are
looking
for
something
that
won't
require
a
lot
of
research,
Etc,
just
a
chance
to
get
used
to
doing
stuff.
B
These
are
some
things
that
would
be
and
we
have
separate
tickets
for
each
of
them
that
that,
basically,
the
information
is
already
written
up
in
one
or
two
contributing.md
files,
and
each
of
these
separate
issues
you
go
in.
You
find
that
information
and
you
turn
it
into
a
page
in
the
contributing
guide
on
the
doc
site.
B
There's
a
couple
where
you'll
need
to
merge
information
from
two
of
them
and
you
might
make
some
edits.
You
may
improve
it,
but
they
they'll
be
basically
simple,
writing
things.
So,
if,
if
anyone
here
is
looking
for
something
simple
to
get
started
with
feel
free
to
grab
some
of
these,
you
can
look
at
them
and
see
what
interests
you
and
ping
me.
B
If
you
have
questions
and
we
need
to
wait,
hopefully
I
thought
that
PR
was
going
to
get
merged
last
night
and
things
happened,
but
hopefully
we
do
need
to
get
the
pr
merged
that
has
basically,
when
we're
done.
Let
me
see
what
it
is
that
I
had
it
opened
up
here.
Yeah,
you
can
see
it
and
where
are
you
yeah.
B
E
B
Knew
it
there
we
go
when
this
is
merged.
The
landing
page
for
the
klt
docs
will
look
like
this,
and
if
you
go
into
contributing
to
Captain,
you
will
find
this
and
there's
nothing
more.
If
you
go
into
one
of
these
you'll
find
nothing
except
the
header
so
to
populate
that.
B
B
If
not
either
you
can
sit
around
and
we'll
do
the
basics,
and
thank
you
all
for
coming
we'll
be
doing
this
meeting
every
week.
At
this
time,
I
will
have
an
agenda
open.
So
if
you
have
anything,
you
want
to
add
to
the
agenda,
go
ahead
and
do
that
and
thank
you
very
much
so
do
we
have
people
here,
I
think
I
see
at
least
one
name
who
would
like
a
walk.
A
basic
walkthrough
of
working
with
get.
B
B
E
B
Have
a
question:
if
you're
really
experienced
with
Git,
we
don't
do
anything
fancy.
The
purpose
of
this
is
I,
admit.
I
have
a
little
cheat
sheet
that
I
keep
with
procedures.
You
know
this
is
basic
stuff
that,
if
you're
not
really
familiar
with
Git,
if
you
do
these
things,
it
will
work
and
keep
you
out
of
trouble.
So.
B
B
Oh
anybody
see
is
somebody
trying
to
put
a
chat
in
there.
I
can't
see
chat
while
I'm
sharing,
apparently
okay,
so
shall
we
just
walk
through
and
do
it
the
first
step?
If
you
are
brand
new
is
you
need
to
go
to,
and
this
is
all
in
the
contributing.md
file,
starting
with
line
147
I
think
so
you
can
use
that
later.
B
And
oh
and
you
being
nasty
to
me,
okay,
I
already
have
a
fork,
so
this
won't
work.
But
if
you
go
to
Fork
it
will
let
you
Fork
it'll,
give
you
a
question.
Oh,
if
you're.
Well,
you
create
a
new
one
right
now.
It's
saying
that
it
should
show
your
GitHub.
You
do
need
a
GitHub
ID.
If
you
don't
already
have
one.
B
Otherwise
you
do
that
and
you
click
and
you
would
get
that
since
I
already
have
one.
Let
me
go
to
mine.
B
And
if
you
click
code
it
gives
you
you
can
access
this
through
either
https
or
SSH.
I
want
SSH
and
so
I
need
that
URL,
so
I
can
clone
it.
So
I
just
click
there
and
it's
copied
they've
made
this
very
nice
lately,
so
I
go
into
my
working
area.
B
Oh
okay:
let's
get
rid
of
some
cover
there
we
go
and
now
what
I
have
done,
I
create
under
my
home
directory
I
have
a
file
I
call
it
code,
but
I
have
all
of
my
repos
underneath
there
and
in
there.
B
Actually,
let
me
go
over
there
and
do
another
one.
B
B
B
So
at
life,
stool
stock
subdirectory,
you
need
to
go
docs
and
then
content
and
then
en
and
then
docs
and
there
you
will
see
what
we
have
and
you
should
recognize
if
you've
looked
at
the
docs
at
all
I.
Oh,
this
is
I'm
on
I
happen
to
be
right
now
on
this
Branch.
So,
okay,
so
let's
say:
I
have
to
have
my
old
Branch
closed
off
and
I
actually
have
my
own
little
cheat
sheet
here.
B
Where
I
keep
this
and
it's
a
mess,
because
it's
just
for
me
so,
but
I
always
want
to
go
back
and
do
a
get
checkout
Main
and
then
I'm
going
to
get
pull
Upstream
Main.
B
And
oh
actually,
before
I
do
that
you
will
need
this
setup
remotes
if
you're
doing
this
for
the
first,
but
I
have
a
remote
I
have
an
upstream
which
is
defined.
That's
the
main
one
and
origin
is
my
particular
Fork
of
it.
That
will
make
sense
now
so
I'm
going
to
pull
Upstream
Main
and
that
pulls
up
anything.
Oh
and
we're
going
to
merge
that
okay.
B
Okay,
sorry
about
that
and
now
I'm
going
to
push
what
is
my
in
my
Fork,
which
is
origin.
B
B
Okay
and
let's
go
in
now
now
you
will
see
that's
good
place.
Three.
There
are
two
different
ways.
You
can
name
your
files
here.
One
is,
you
can
just
do
a
straight,
and
this
is
my
preference.
If
you
don't
have
a
lot
of
Graphics
or
whatever
that
you
want
to
keep
with
it,
you
can
just
make
it
getting
started.
B
Just
make
a
straight
file
there,
whatever
you
do
at
the
top,
you
have
some
metadata,
find
an
existing
file
and
copy
it
and
modify
it.
You
have
the
display
title,
the
link
title,
a
description,
illumination
and
a
weight,
and
that's
going
to
determine
the
order
that
the
different
pages
play
out
in
the
section.
This
is
all
in
contributing.
B
In
this
case,
we
have
a
directory
called
evaluate
and
we
have
an
underbar
index.mdi.
Oh
wait,
a
minute,
that's
got
that
means.
I
have
some.
If
there's
stuff
on
there
really
I
know.
Okay,
I
think,
that's
not
how
it's
right
now,
okay,
this
is
a
bad
place
to
be.
I
should
have
figured
something
out
ahead
of
time.
B
B
I
keep
a
window
with
all
sorts
of
tabs
in
it,
and
inside
I
will
tell
you
most
people
think
it's
much
easier
to
work
with
an
IDE
I
work
straight
in
VI,
but
so
now,
if
I
do
get
status,
we
see
that
I
have
modified,
that
one
file,
so
I'm
gonna
and
there
may
be
a
lot
of
files,
but
I'm
going
to
do
git,
add
dot.
I
can
specify
only
one
file
if
I
want
to,
but
I
want
to
push
I
want
to
make
a
commit
out
of
everything
that
I
made.
B
The
change
I
do
that
now.
I
need
to
do
get
I
need
to
commit
it
and
I
need
to
with
every
commit
I
have
to
do
a
dash
s.
There
are
other
ways,
and
this
is
written
up,
but
basically
with
every
commit.
You
have
to
do
something.
It's
a
legal
document
to
say
that
you
are
surrendering
your
ownership
of
this
intellectual
property
to
the
captain
project.
B
So
we
do
that
and
then
it's
in
VI
and
I
just
make
a
quick,
a
very
short
period
in
title.
B
I
end
that
and
I
write
that
now
I
can
the
lazy
way
I
can
go
just
get
pushed
that
doesn't
work,
but
it
tells
me
it
gives
me
the
command
I
need.
So
all
I
need
to
do
is
I
copy
that
I
paste
it
and
it
executes.
B
G
B
Sometimes
it
gives
you
this
so
remove
period
in
title
for
demo
purposes,
we'll
make
that
so,
if
anybody
sees
it
and
then
here
now,
if
it's
a
substantive
thing,
if
there
is
an
issue
related
to
this,
you
want
to
say
this
is
the
issue.
You
should
write
something
here,
so
that
reviewers
or
anybody
who
looks
at
this
knows
what
you're
doing
and
why
you're
doing
it.
You
can
look
at
example
commits
that
are
there.
B
Oh,
this
is
an
issue
so
I'm
going
to
copy
that
and
I'm
going
to
go
back
to
where
I
am
and
it's
part
of
here
I
am
writing.
I
can
use
markdown
syntax
if
I
want
to.
If
I
want
to
see
what
it's
going
to.
Look
like
I
can
look
at
preview,
When,
You,
See,
It
compresses
that
whole
thing,
but
then,
with
that
I
can
create
a
pull
request.
B
B
B
If
it's
amount
of
work
that
you
would
do
in
a
week,
it's
probably
too
big
for
a
single
PR,
not
always
but
think
in
terms
of
small
stuff,
but
sometimes
if
you
are
working
on
something
you
want
to
get
it
pushed
up
there,
you
want
somebody
to
see
it
actually
or
something
you
might
go
ahead
with
this,
but
it's
not
ready
to
be
merged.
It's
really
not
ready
for
official
review
or
anything,
and
so
you
can
go
down
here
and
at
the
bottom.
B
B
We
can
talk
about
it,
but
if
I
don't
know
what
it's
up
to
I
look
at
it
and
it's
like
hey
I-
don't
need
to
worry
about
this
and
Simon
we'll
talk
later.
But
do
you
see
this
and
you
saw
me,
do
commit
to
HS
right.
D
But
we
can
take
a
look
shortly
when
you
go
scroll
upwards
to
the
top
of
the
pull
request.
B
D
D
D
E
D
B
E
D
B
D
G
D
D
Now
we
changed
something
for
you
if
you,
if
you're
up
to
that,
where
should
I
send
you
chat
messages,
oh.
B
God,
there's
Chad:
okay,
I
can
see
chat,
okay,.
D
So
I
sent
you
something:
okay,
if
you,
if,
if
you
use
that
command
I
just
sent
you
you
will
your
your
main
branch
will
actually
face
to
as
well,
actually
always
update
against
the
Upstream
main
branch
instead
of
instead,
then
you
do
not
need
to
to
to
update
every
time
the
main
branch.
D
So
that
means
your
local
main
will
always
fetch
from
the
Upstream
main
instead
of
your
If.
Instead
of
your
custom
repository
main,
which
make
your
process
a
little
bit
easier
because
then
you
do
not
need
to
to
check
out
Upstream
main
or
things
like
that.
You
do
you
just
to
always
get
checkout
Main
get
pulled,
and
then
you
say,
get
checked
out
new
branch
and
that's
it.
E
D
Maybe
have
changed,
maybe
your
main
branch
is
not
up
to
date
with
the
with
the
with
with
the
Upstream
so
well.
D
D
D
B
We
should
actually
just
as
we're
probably
making
things
worse
than
Justice.
Maybe
we
should
do
this
later.
Okay
hold
on
just
a
second
Justice
and
then
we're
going
to
go
back
and
talk
to
you.
We
thought
everybody
else
had
gone
so
we
started
doing
this.
B
No
just
just
stay
there:
okay,
okay,
Simon
you're
just
lit
just
because
you
were
the
one
you
actually
needed
this
did
that
demo
make
it
any
make
it
clearer
what
to
do.
G
It
really
does
so
so
before
now,
I've
always
been
pushing
to
my
own
repository,
so
I
know
how
to
commute
I
know
so
at
all
I'm.
So
so
it
is
just
you
need
to
from
somebody
else's
repository.
Then
that's.
G
That's
what
I've
been
used
to?
Oh
okay,
so
so
I
really
use
Vin
or
a
VI,
so
I
do
prefer
to
use
my
text
editor,
there's
a
Visual
Studio
code.
So
so
most
times
it's
it's
it's
it's
not
this
complicated.
They
do
so,
but
there
is
really
it
it.
You
don't
have
gained
concerning
upstream
and
oh
yeah
yeah.
So
but
it's
really
helpful.
Thank
you!
So
much
for
okay.
B
G
B
I
say
if
you
totally
contributing
file
until
somebody
starts
changing
it.
It's
at
line,
147
I,
think
all
this
stuff
is
in
there
but
yeah,
but
ping
us.
If
you
have
any
problems
and
yeah
see
if
you
can
get
see.
If
you
can
get
this
working
cloned
and
then
we'll
talk
about
that,
contributing
section
would
be
a
great
place
where
you
could
do
kind
of
a
quick,
PR
and
work
through
the
whole
thing.
G
Yeah
I
lost
you
for
a
sake,
I
guess
it's
my
own
network
that
yeah.
B
These
will
be
easy
and-
and
it's
good
to
get
your
first
one
done
because
the
the
first
one
there's
a
couple-
you
get
blocked.
There's
for
you
know,
so
we
want
to
make
sure
that
we
don't
have
a
hacker
come
in
and
start
throwing
garbage
in.
So
the
first
time
you
make
a
commit
one
of
our
upper.
The
the
head
of
the
core
engineering
has
to
approve
you,
so
there
could
be
a
lag
of
something
there
for
and
then
after
that's
done
once
you'll
be
more
quickly.
So.
B
To
get
your
first
PR
we'll
do
one
of
the
contributing
sections
as
soon
as
as
soon
as
I
get
that
merge,
which
hopefully
will
be
later
today
or
certainly
by
tomorrow,
and
then.
E
G
B
B
E
G
Yeah
before
we
do
call
it
a
meeting,
I
was
expecting
first
to
talk
anything
concerning
G
sub,
but
is
he
not
going
to
be
here.
B
B
B
E
B
Lots
of
people
are
and
we'd
love
to
have
your
participation,
I
think
at
the
community
meetings
there
will
next
week
there
will
be
people
there
who
know
more
about
where
we
are
there's
been
some
administrative
glitches
along
the
way
and
ups
and
downs
and
and
people
are
busy
and
stuff,
but
I
believe
we
are
doing
it.
B
If
you
would
like
to
propose
a
project
you
can,
or
you
can
look
I
think
there
are
some
proposed
projects
on.
If
you
can't
find
it,
let
me
know
and
I'll
send
you
the
link.
We
have
a.
We
have
an
open
PR
in
the
community
thing
where
you
can
log
your
interest.
Actually
you
should
log
there.
I'll
I'll,
send
you
this
in
slack
what
you
need
to
do.
G
B
G
The
not
really
made
a
lot
of
research
on
documentation
so,
but
we
need
to
have
seen
it
looks
like
something
I'm
going
to
enjoy
doing,
though,
though,
but
I've
not
done
it
before
I
have
not
so
I
I'm
gonna
do
a
couple
of
research
on
what
it
enters
and
see.
If
it's
something
I'm
going
to
like
to
okay.
B
B
Okay,
terrific,
we'll,
hopefully,
things
are
going
to
get
clearer
in
the
next
couple
of
weeks,
I'm
confused
too
so
yeah
all
right.
Okay,
thank
you!
So
much
for
joining
us
and
we'll
be
talking
to
you
soon.
Bye.