►
From YouTube: Keptn Documentation Office Hours - Mar 23, 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
Yes,
ayush
is
on
it.
We've
had
a
couple
of
technical,
basically
just
learning
killer
Coda,
rather
than
any
kind
of
Captain
technical
issues.
So
yeah
there
was
a
few
people
wanting
to
get
involved.
I,
don't
know
where
they've
all
gone,
though.
Obviously,
that
issue
is
what
I'm,
using
as
the
source
of
Truth
so
yeah.
It's
still
it's
still
as
far
as
I'm
concerned,
the
more
the
merrier
it's
open
to
everyone,
but
as
I'm
as
far
as
I'm
aware,
it's
only
ayush
working
on
it
at
the
moment.
Okay,.
B
B
And
did
you
see
the
items
I've
got
so
for
season
of
Docs
I,
don't
know
how
many
projects
we
can
do
and
do
we
propose
as
many
as
we
do.
We
propose
some
that
we
might
not
do
or
should
we
just
propose
the
ones
that
we
think
we're
gonna
do
or.
C
A
Well,
I
I
think
we
I'm
confused
as
well
to
be
honest,
I'm
happy
to
so
the
not
the
Google
summer
of
code.
Let's
leave
that
aside,
the
Google
summer
of
Docs
I'm
happy
to
Mentor
something
around
the
life
cycle.
Toolkit
I
think
we
need
some
good
or
better
installation
docs,
because,
as
you
saw,
the
video
that
I
put
together.
B
Has
tons
of
stuff
that
aren't
in
the
dark,
yeah,
yeah,
yeah,
I,
agree
and
I
think
that's
a
high
priority
and
it's
a
good
writing
a
couple
of
the
others
that
I've
got,
aren't
really
ready
and
we've
got
a
couple
of
Hardcore
writers
here
who
want
to
do
docs,
so
yeah,
Asha,
you're,
still
speaking
to
me.
After
what
I
did
to
you
on
your
PR.
C
B
C
B
Adam
Yash
did
what
we
all
did.
He
did
a
PR
that
should
have
been
about
nine
or
ten
PR's
so
and
I
I
kind
of
hated
to
do
it
because
we've
all
done
it
and
I
know
what
it
feels
like
when
they
come
back
and
say
no,
you
have
to
redo
this,
but
also
figured
that
everybody
has
to
do
that
Josh
when
I
did
it.
It
was.
Yours
is
not
going
to
be
terribly
hard
to
clean
up.
Mine
was
a
nightmare
to
clean
up
and
I
swore
at
the
person.
B
A
A
B
It
really
is,
and
it's
important,
like
I,
already
got
caught
on
one
where
I
had
split
out.
The
What
is
the
klt
from
the
getting
started
stuff
and
then
people
were
messing
around
with
little
Picayune
comments,
and
then
you
know
waiting
two
weeks
to
come
back
to
approve
the
fix
and
stuff,
and
you
came
in
and
added
all
that
great
stuff
for
the
intro
parts
and
I
ended
up
with
you
know.
If
you
know
all
those
unresolved
things,
so
that's
another
thing
is
that
getting
them
reviewed
and
merged
quickly
is
a
good
thing.
A
B
A
B
D
B
That
you
know
the
more
eyes
you
get
on
this,
so
yeah
now
I,
don't
know
what
we're
recording
and
it's
six
minutes
after
I
thought
more
would
come,
but
Yash
I!
Guess
it's
just
you
did
you
have
anything
that
you
wanted
to
discuss.
C
B
C
Would
like
to
discuss
the
one
p
issue
that
you
have
raised
so,
alongside
with
the
LTI
stock,
I,
can
also
contribute
over
there.
I
had
asked
a
question
over
there
over
the
issue.
B
A
B
Bring
me
up
to
speed
and
when
I'm
about
to
what
I'm
sharing
here
is
it
gonna
help?
There's
our
let's
put
in.
D
B
B
B
There
was
a
pick,
so
this
is
the
Epic.
It's
basically
taken
the
tons
of
stuff
that
we've
got
in
the
two
contributing
MD
files
and
we're
going
to
move
them
out
into
this
contributing
guide
that
will
be,
and
then
the
contributing
MD
files
will
have
links
to
the
appropriate
sections
in
there.
But
so
we
have
this,
and
so
we
had
all
of
these
tasks
and
Yosh
basically
did
all
of
these
tasks
in
one
PR.
B
And
Amish
has
been
a
couple
of
I
think
a
couple
of
other
people
have
worked
on
them,
Etc,
it's
a
party
so
okay!
So
yes,
yes,
speak
to
us.
What
would
you
like
to
discuss
so.
C
I
would
like
to
create
separate
PR,
the
one
which
have
been
not
created
or
by
the
folks,
so
I
will
go
through
all
the
PRS
which
have
been
listed
and
will
make
the
specific
PR,
which
are
which
needs
to
be
which
need
to
be
made.
So
I
have
seen
a
two
to
three
PR's
have
been
raised
from
this
year.
From
this
whole
epic
issue.
So
I
will
neglect
the
three
ones
and
work
on
the
remaining
issue
which
have
been
not
worked
upon.
B
Okay,
good
work
in
with
each
of
them
also
like
if
it's
something
you
can't
like
the
ones
for
it
would
not
hurt
to
have
a
fresh
set
of
eyes
like
the
one
for
working
with
GitHub
to
click
through
those
instructions
and
see
because
every
time
I
go
through
it.
I
find.
B
Oh,
we
forgot
to
say
this
so
look
and
see
if
there's
stuff
missing
or
if
it
works,
sure
and
there's
still
everybody
I
talk
to
has
a
different
theory
of
what
is
the
best
to
put
your
brand
Etc,
so
yeah,
so
good
work
and
yes
and
feel
free,
the
ones
the
other
ones
that
are
coming
up
out.
There
also
be
great
if
you
reviewed
their
work
too,
if
all
you
guys
reviewed
each
other
and.
B
So
does
that
do
it
for
that?
Let's
see.
C
B
The
merge,
quick
and
oh
and
that's
also
attributing
guy
but
we're
with
just
here
on
there
are
you
interested
in
g-stock
or
G
the
season
of
Docs
I'm,
trying
to
remember.
B
You're
interested
in
gtax,
okay,
do
you
have
we
have
a
few
things
here
we
can
discuss?
Do
you
have
any
projects
in
mind.
C
Especially
for
captain.
C
B
D
B
B
Oh,
let's
see
proposed
doc
structure.
B
B
So
we
propose
these
are
the
major
titles
there'll
be
a
getting
started,
which
hopefully
is
going
to
include
a
killer,
Coda
based
exercise,
some
product
overview,
or
some
of
these
titles
may
change
what
is
klt
whatever
functional
architecture
overview,
an
installation
section,
people
like
the
topic
user
guide.
Basically,
how
do
you
create
and
run
and
manage
kept
in
a
life
cycle,
toolkit
application,
and
then
there
will
be
some
reference
pages.
C
No
basically
yeah
we'll
we'll
go
through
this
issue
and
we'll
let
you
know
I
will
go
to
the
issue.
First,.
B
What
are
your
particular
documentation
interests?
Are
you
by
the
way
hi
Simon
I
was
waving
at
you,
but
I
didn't
have
my
camera,
and
so
that
doesn't
help
you
a
lot.
Does
it
so
back
up
to
where
we
are
Lord.
B
Are
you
are
you
well,
let's?
Well,
let's
walk
through
what
we've
got
killer
Coda
exercises
Adam.
You
want
to
speak
briefly
about
what
sort
of
projects
we
can
and
then
we'll
see
where
there's
interest
and
then
we'll
write
up
a
few
more
specifics
in
the
next
day
or
two
for
each
of
these
that,
if
there's
any
interest,
but
do
you
want
to
talk
about
that
yeah.
A
Sure
so
so,
as
most
people
will
probably
know
by
now,
we've
got
a
killer,
Coda
exercise
for
Captain.
What
we're
calling
Captain
V1,
which
is
the
end
browser
you
know,
play
around
with
Captain
in
a
browser.
We
don't
have
that
yet
for
the
life
cycle
toolkit.
A
So
that's
basically
what
we
need
to
build,
but
also
obviously
document
that
and
and
make
sure
that
people
can
find
it,
and
it
explains
it
so
we'll
need
a
page
on
the
main
docs
that
just
maybe
even
a
paragraph
that
just
explains
it
before,
with
with
a
link.
Basically,
none
of
it
exists
at
the
moment.
A
So
that's
that
that
would
be
the
project
is,
is
two-pronged,
first,
to
actually
create
the
thing,
and
ayush
has
actually
started
on
that
technically,
but
then,
of
course,
if
no
one
can
understand
it
or
use
it,
then
it's
pretty
pointless.
So
we
would
need
that
blurb
and
that
page
and
that
structure
on
the
documentation
to
go
with
it.
A
B
Yeah
and
the
other
one
that
I'm
that
the
one
thing
that
bothers
me:
I
love
these
killer
code
exercises,
but
I'm
always
there's
I'm
going
back
and
like
oh
God,
they
did
that.
What
exactly
was
the
command
and
I
have
to
go
back
into
the
exercise
and
Page
through
it
till
I
get
to
the
thing
that
I
wanted
and
I
may
or
may
not
be
able
to
copy
paste.
So
there's
a
part
of
me
that
wants
accompanying
doc.
That
goes
the
whole
way,
but
I'm
not
sure.
A
Well,
well,
actually,
that's
a
very
good
point.
Another
part
of
this
is
the
captain.
V1
killer
code
is
currently
sitting
on
a
third
party
person's
GitHub
I
know:
we've
discussed
moving
that
into
an
official
Captain
repo
and
that's
going
to
come
with
the
Perry
bolo
stuff
that
Simon's
doing
everything
should
live
under
Captain
though,
and
then
we
can
at
least
point
out
because
all
of
the
killer,
Coda
stuff
fundamentally
is
either
a
markdown
file
or
a
shell
script
behind
the
scenes.
That's
all
it
really
is.
A
So
in
your
scenario,
we
can
actually
point
to
the
the
repo
that
contains
the
tutorial
and
say
you
don't
have
to
page
through
the
tutorial
and
wait
for
it
to
load
and
install
here's
the
shell
script
or
here's
the
here's,
the
command,
for
example,
but
but
I
agree,
it's
it's
a
bit
clunky.
We
need
to
figure
out
a
nice
way
to
do
that
and
and
if
that's
duplicating
or
if
that's
pulling
that
into
docs,
then
then
that's
the
way.
We
do
it.
Yeah.
B
Yeah,
okay,
so
the
next
one
is
to
work
on
the
landing
page
here,
which
is
kind
of
wild
and
kind
of
a
mess.
B
Nobody
we've
added
stuff
and
taken
stuff
away,
but
nobody's
looked
at
it
as
a
whole,
I
personally,
don't
care
for
the
Aesthetics,
the
the
blue
and
the
back
I
like,
but
the
rest
of
this
to
me:
it's
messy
Etc,
but
and
then
up
on
here,
we've
got
now.
We've
got
a
link
to
Integrations,
which
is
nice,
but
that
also
shows
up
in
the
docs.
So
do
I
really
need
it.
There
I
don't
know
I
mean
it
involves
some
judgments.
B
We
still
have
a
link
for
tutorials,
although
we
have
almost
no
tutorials
here
again.
Is
that
worthy
of
being
there
for
her
thing?
And
if
you
get
to
the
tutorials,
you
see
you
don't
have
a
really
good
way
out.
Unless
we
go,
oh,
no,
we
go
up
there.
No,
we
have
no
way
out.
Do
we
I
have
to
go
back
here,
really
hate
that
when
I
can't
get
back
where
I
was
resources,
this
was
done
when
I
think
this
was
put
together
when
Captain
was
first
starting
and
a
lot
of
this
material?
B
E
B
B
You
get
the
idea
and
then
you
go
here
and
you
get
to
Captain
V1
Docs,
and
then
you
go
into
the
life
cycle
toolkit
and
look
at
what
we
have
here.
We
have
a
link
to
releases.
B
Oh,
do
we
get
one
more
thing?
If
we
go
into
development?
Yes,
then
we
get
here.
We
will
put
a
link
to
the
contributing
guide
that
you're
currently
working
on
actually
but
other
than
that
gee,
even
from
there.
Okay,
at
least
I
can
go
back
to
there
and
get
to
the
docs,
but
I
sort
of
lose
any
of
this
stuff
there.
So
there's
a
lot
of
stuff,
it's
not
defined.
B
A
If,
if
I
could
actually,
because,
obviously
Yash
and
rakshit
have
come
to
Captain
and
the
project
as
a
whole,
but
you
know
more
recently
than
we,
we
have
right
what
what
gentlemen,
what
would
you
or
what
did
you
expect
that
you
didn't
see
what
would
be
a
good
flow
if
you
just
came
to
the
captain
website
for
the
first
time?
A
B
B
B
The
next
one
is
a
Simon
one,
so
why
don't
you
describe
this
Simon?
What
this
would
be
is
a
season
of
docs
project.
B
We've
lost
Simon,
Okay
I
suspect
he
will
be
back
one
more
I'm
back
sorry,
oh
gory,
okay,
I
heard
my
name.
Yes,
the
the
season
of
docs
proposal,
the
tooling
for
the
for
the
CI
and
et
cetera.
Do
you
want
to
speak
briefly
what
that
project
would
be.
E
Oh,
do
we
have
a
link
for
that
I
I
wrote
something
somewhere.
I
know
that
but
I'm
not
sure
so
I
know
I
know
what
we're
talking
about.
So
the
the
part
is
you.
E
The
thing
I'm
I'm,
remembering
the
part
where
what
we
are
talking
about
is
actually
we
do
have
a
lot
of
of
naming
conventions
or
things.
How
are
we
have
certain
names
we
want
to
use
in
certain
capitalizations
and
things
like
that,
and
we
are.
We
are
lacking
actually
a
tooling
to
enforce
that
and
to
take
a
proper
look
at
it,
so
that,
for
example,
we
always
write
Captain
the
same
way,
that's
always
with
a
capital
K
and-
and
things
like
that.
E
So
there
is
a
lot
of
a
lot
of
two
two
involve
what
we
assert.
There
are
a
lot
of
potential.
What
we
can
do
with
our
tooling
to
improve
it
also
spell
checking,
for
example,
is
another
certain
topic
which
would
be
good
to
have
solidarity
bot,
for
example,
so
prevention
to
I
saw
a
tool
to
enforce
inclusive
language
so
that
we
are
not
using
master
and
slave
and
all
those
kind
of
things.
E
B
E
B
B
So
and
we
started,
we've
got
a
couple
of
them
in
there
now
that
probably
need
some
refinement.
A
So
Simon
Just
quickly.
Are
you
aware
of
any
tools
that
do
that,
or
would
this
be
like
to.
D
E
E
E
Then
there
is
Mark
down
spell
check
actually,
which
can
do
spell
check
where
you
can
Define
Words,
which
should
be
used,
and
you
can
Define
your
own
dictionaries
and
it
will
be,
it
will
suggest
you
think
the
questions
also,
if
it's
feasible,
because
most
dictionaries
out
there,
which
are
used
and
often
do
not
contain
all
that
technical
words
and
things
like
that.
So
you
need
to
define
a
basic
setup,
then
there's
theoretically
also
c-spell,
which
is
another
tool
for
spell
checking.
So
there
are
a
few
out
there
which
can
help
us
and
guide
us.
E
B
Engineers,
what's
the
ending
style?
Oh,
the
question
of
underlying
style
guide.
I
have
proposed
that,
rather
than
do
our
own,
that
we
use
the
Google
style
guide,
but
we
haven't
really
had
a
discussion
on
that.
That
has
a
very
nice
long
list
of
terminology
of
General
terminology
and
I
think
there
are
tools
out
there
that
check
for
that
it
does
not
give
us.
We
do
not
have
a
definition
of
terminology
for
our
stuff,
I
mean
there's.
Even
there
are
some
people
who
say
the
logo
doesn't
capitalize.
Captain
that
we
should
not.
B
You
know,
I
think
Captain
used
in
text
should
be
capitalized
unless
it's
the
commands,
but
we
have
to
have
an
agreement
of
that
and
other
terms,
can
we
say
klt
or
do
we
always
need
to
spell
out
Captain
life
cycle
toolkit
or
lifecycle
toolkit
when
we
talk
about
quality
Gates?
B
Is
that
uppercase
lowercase
whatever
so
that
is
part
of
that
is
we've
I
put
up
this
word
list
to
start
doing
stuff
and
I,
don't
I,
think
I'm
the
only
one
who's
contributed,
anything
to
it
and
I
haven't
done
as
much
as
I
should
have
on
it.
So
that
would
probably
be
part
I
mean
we
can't
start
enforcing
stuff
until
we
have
an
agreement
on
what
we
have,
what
we
want
to
enforce
so
yeah.
So
that's
that's
a
big
juicy
fun
thing
to
do:
okay
and
then
the
last
one
Adam.
B
Why
don't
I
throw
up
my
epic
that
I
did,
but
you
talk
about
it
and
we'll
you
guys
probably
noticed
that
the
installation
docs
are
not
adequate.
Shall
we
say.
B
A
B
B
B
A
This
is
better
than
than
I
saw
to
be
honest
to
start
with,
but
even
there
what
you've
got
on
the
screen
you've
got.
The
Manifest
file
is
at
version
0.7.0
and
then
you've
got
a
big
title
that
says:
install
version.
Six
and
oh
see
I
see
what
that's
saying.
If
it's
version
six
and
earlier
then
you've
got
to
include
cert
manager
and
presumably
there's
a
header
above.
B
A
Seven,
if
you
scroll
up
a
little
bit.
B
But
we
don't
have
anything
well,
I,
think
I,
suppose
I
don't
know,
I've
got
to
think
some.
The
Assumption
I
think
for
production.
Installation
is
that
you
have
a
kubernetes
cluster,
where
you're
running
your
Argo
CD
or
your
flux
or
whatever
and
you're
going
to
add
this
to
it.
B
But
you
know
it
doesn't
have
to
be
in
its
own
namespace
or
its
own
pot.
You
know
when
you
do
that
and
then
the
whole
thing.
What
if
you
want
to
do
a
version?
That's
just
for
yourself,
study
and
demonstration,
so
I
think
right
now
it
looks
like
it
we're
so
we're
mostly
using
kind
for
that.
I,
don't
know
what
we're
doing
with
k3s
k3d.
We
did
used
to
use
those
a
lot
for
Captain
V1
and
all
that
we
need
information.
We
need
the
a
document
like
we
have
for
captain
that
talks
about.
B
What
do
you
need?
What
sort
of
resources
do
you
need
to
read
this,
to
use
this
and
to
list
releases?
So
all
of
that
sort
of
full-fledged
installation
and
then
I
Adam,
you
may
disagree
to
me.
I
think
part
of
the
installation
set
should
be.
If
you
put
Captain
into
your
cluster,
where
you're
running,
Argo
or
flux
or
whatever
you're
running,
then
how
do
you
introduce
klt
to
your
our
go
flux?
How
do
you
hook
those
up
and
also
your
SLI
engine,
your
Prometheus,
your
I,
guess
Prometheus
today
to
try.
B
A
You,
you
dropped
out
a
lot
there
and
you
kind
of
slowed
down,
but.
B
Oh
I'm,
sorry,
but
how
you
would
hook
if
you,
if
you,
if
you're
a
production,
environment
and
you're
running
Argo,
CD
or
flux
or
whatever,
how,
once
you
install
klt?
How
do
you
connect
the
two
of
them
to
each
other
I'm.
D
B
A
Know,
yes,
right,
I
think
the
ratchet
you
were
saying
it
doesn't
necessarily
belong
in
this
page,
but
it
does
belong
somewhere
and
then
is
it.
D
Is
we
can
have
a
section
like
Integrations
like
how
to
integrate
and
then
reference
the
different
page
into
the
installation
so
like
I,
have
a
different
reference
to
another
page
in
the
installation
for
integration,
yeah.
B
A
But
you're
right
then
installation
on
on.
Well,
it
does
does
that
change,
because
anyone
can
go
and
run
a
Helm
command
on
any
tiny
little
cluster
for
a
demo.
Does
the
installation
does
your?
Do
you
con
considerations,
change
if
you're
doing
this
for
real
in
a
production
environment?
Do
you
need
you
know
and
and
what
changes
so
that
might
be
extra?
It's
it's
not
really
good
enough!
A
Just
to
have
the
helm
commands,
it
would
get
you
up
and
running,
but
would
you
then
hit
issues
and
have
to
redo
everything
because
you
need
more
space
or
you
know
whatever
the
case
may
be
so.
B
Right
and
yeah
and
disk
space
Also
as
well
as
you
know,
for
different.
A
B
A
Have
any
docs
for
and
I
don't
know
if
this
goes
under
installation,
but
how
to
write
or
even
really
how
to
use
in
klt
the
service.
The
the
providers
for
for
metrics.
B
A
Well,
I
think
from
what
ayush
was
doing.
He
is
just
literally
at
the
moment
trying
to
get
whatever
we
have
in
the
standard
demo.
Okay,
ordered
into
killakota.
B
B
Well,
we
don't-
and
this
is
on
also
on
my
cue-
we
do
not
have
a
place.
We
don't
step
through
then
how
you
implement.
You
know
what,
when
you
you,
we
have
a
you
know
some
reference
material
about
some
of
the
crds,
but
we
don't
have
in
anything
of
you
know,
basically
a
use
case
where
you
step
through
and
what
order
you
know
you
do
this,
and
this
and
now
test
it,
make
it
work
and
now
we'll
add
this
and
this
or
whatever.
B
A
B
That's
what
there's
that's,
what
I'm
not
clear
about
either
so
I
think,
but
we
propose
what
we've
got
our
best
stuff
and
so.
B
C
B
B
Okay,
Rashi
do
any
of
these
sound
interesting
to
you.
B
D
A
Is
a
very
good
question
because
at
the
beginning
of
the
call,
Meg
and
I
were
saying
we
are
confused
because
we
I
originally
proposed
a
project,
but
then
I
heard
that
it's
actually
really
got
nothing
to
do
with
us.
Google
take
the
mentees
proposals
a
lot
more
seriously,
I'm
going
to
catch
up
with
Brad
who
will
know
this
and
I
will
make
a
note
to
get
back
to
you
and
everyone.
A
Frankly
on
on
that
exact
thing,
because
I
thought
we
were
all
done
for
gsoc,
but
but
apparently
the
mentees
I.E
yourself
has
to
actually
raise
the
proposal
and
then,
as
mentors
we
come
along
and
say:
Yes
I
want
to
do
that.
So
yeah
there's
a
bit
of
confusion.
Let
me
get
back
to
you
on
that.
One.
B
B
Necessarily
this
so
and,
of
course,
the
slack
channels.
So
do
you
have
anybody
reviewing
what
you've
got
so
far
Rock?
Do
you
have
a
name
at
all.
D
Hello,
hello,
yeah,
sorry,
I
didn't
get
you.
Can
you
repeat.
D
I
like
just
wanted
to
get
reviewed
about,
like
do
I,
have
the
technical
thing,
or
do
my
ex,
like
my
milestone,
match
up
with
the
expectations
of
the
project.
I
just
wanted
to
get
review
on
that
thing.
B
D
B
A
A
As
as
I
understand
it
and
what
certainly,
what
happened
last
year,
the
scope
of
the
project
once
once
things
have
been
approved
by
Google
and
kind
of
we
as
the
captain
Community,
are
off
and
running
it's
really
between
yourself,
the
mentee
and
the
mentors
to
really
scope
the
project.
It's
the
mentor's
job
to
say
that's,
you
know,
that's
too
big,
try
try
something
smaller
or
you
know
that
that's
not
big
enough.
Let's,
let's
try
and
push
out
the
boat
a
little
bit.
A
It's
your
job
as
the
mentee
to
then
bring
ideas
or
or
be
flexible
and
shrink
it
down.
But
but
that's
an
agreement
between
you
yeah,
the
the
individual
project
right.
A
A
That
is
purely
for
that
there's,
no
coding
there's
no
documentation.
It's
purely
meeting
the
mentors
and
the
mentees
getting
comfortable
with
each
other
and
agreeing
the
scope.
I
know
we
I
had
a
lot
of
back
and
forth
meetings
to
do
exactly
that
to
figure
out
well,
what
can
we
achieve
in
the
time
so
that
there's
plenty
of
time
is
is
what
I'm
trying
to
say?
Don't
don't
stress
too
much
about
that.
B
Yeah
yeah,
like
we
did
a
lot
of
like
setting
of
milestones
in
those
first
couple
of
weeks.
You
know
the
specific
Milestones
but
I
think
the
proposal
is
supposed
to
sort
of
say
you
know
well
I
think
this
will
change
two
weeks
in
this
to
a
week
and
by
the
middle
of
the
project.
I
expect
to
have
this
done,
but
then
we
can
refine
that
in
those
first
couple
of
weeks
of
the
project
so.
B
A
C
B
Right
or-
and
you
could
see,
if
more
wanted
to
do
it,
but
it's
not
gonna
work
out
words
I!
Don't
because
he's
about
to
go
on
paternity
leave
too.
So
it
may
not
be
a
good
time
for
him,
but
we
might
be
able
to
get
him
in
as
an
advisor
or
something
to
check
the
fine
points.
So.
B
I
do
apologize
that
there's
so
much
confusion
this
year,
but
there
are
things
going
on,
and
part
of
this
is
that
this
year,
we're
having
we're
in
under
cncf
is
doing
the
administration.
So
we
don't
have
anybody
as
Captain
specific
person
doing
the
admin,
but
do
you
do
you
have
any
more
questions
that
we
can
help
you
with
today.
D
B
B
So
we
we
don't
need
to
look
at
open
PR's.
That
was
something
I
had
on
there
if
we
needed
something
to
talk
about
with
a
bigger
group,
but
you
guys
both
know
what
you're
doing
right
now
so.
B
E
Yeah
I
can
I
can
show
the
pull
request.
What
we're
doing
with
the
latest
pull
request
more
likely,
where
we
switch
from
markdown
link
CLI
to
markdon
Lane
CLI
too?
Okay,
why
don't
I
stop
sharing
that's?
How
I
can
show
that
it's
not
like
I
need
not
to
who
from
just
a
second
I
need
my
time
to
get
my
screen
ready
for
sharing,
because
you
do
not
like
a
one
as
a
49
inch
screen
to
be
shared
as
a
whole.
E
E
I
do
have
too
many
pull
requests
open
here
we
are
perfect.
So
actually,
what
we
are
doing
here
is
we
are.
We
are
adding,
as
we
are
changing
from
markdown
link
to
markdown
link,
CLI,
there's,
no
big,
just
fixed
a
lot
of
errors.
Here,
there's
no
big
difference.
E
We
just
change
the
configuration
from
this
marked
on
linked
Yamato
and
then
marked
on
linked,
ignore
file
where
we
Define
what
is
ignored
and
where
we
Define
The
Roots
into
a
marked
online
CLI,
two
armor,
where
you
can
have
the
ignores
Etc
in
one
place
and
additionally,
we
are
adding
custom
rules
here
and
those
custom
rules.
We
have
a
follow-up
topic
if
somebody
wants
to
take
a
look
at
it.
The
follow-up
issue
is
regarding
updating
them
automatically.
E
We
have
them
currently
added
into
our
Repository,
and
those
two
rules
are
actually
marked
only
to
minus
X1
sentence
per
line
is
actually
a
rule
which
will
split
up
sentences
based
on
certain
configuration
into
multiple
lines.
So
we
do
not
have
this
long
500
line
Center
paragraphs
and
they
will
be
split.
We
can
change
how
we
want
to
do
that.
Actually,
we
can
provide
more
line
endings
and
things
like
that.
It's
a
little
bit
configurable,
but
this
will
automatically
split
long
sentences
into
that's
a
lot,
not
long
paragraphs
into
multiple
lines.
E
They
will
be
still
rendered
the
same
way
and
the
other
rule
we
are
added
is
GitHub
admonition.
So
a
lot
of
people
are
writing
admonitions,
like
this
style
or
when
they
want
to
improve
point
something
out
or
something
important
like
with
this
node
and
with
the
two
two
asterisks
or
even
The
Warning
part
is
also
possible
and
when
we
write
it,
the
correct
way
like
GitHub
is
suggesting
either
in
one
line,
but
the
node
type,
the
specific.
Then
we
will
get
rendered
in
this
nice
syntax
down
here.
E
Well,
oh,
it's
on
a
I
think:
that's
not
it
I
need
to
go
to
the
development
yeah
getting
started.
You
know
and
the
API
reference-
and
here
even
here
you
see
that
those
are
specially
formatted
and
highlighted
now,
not
just
written
in
bowl
or
things
like
that,
so
they
have
a
better
meaning.
There
are
two
based
on
this
marked
on
the
GitHub
admonitions.
E
There
GitHub
supports
currently
two
different
type
of
things:
that's
node
and
warning
so
to
to
highlight
this
differently,
and
this
is
something
which
is
handled
within
that
pull
request
to
be
added
and
the
follow-up
task.
Regarding
this,
the
follow-up
task
we
regarding
those
routes,
because
we
added
them
as
files
to
make
the
tooling
easy
that
people
can
use
markdown
land
even
within
the
visual
studio
code
and
get
this
information.
E
We
created
an
own
task
that
we
upload
update
those
files
automatically
I
can
even
show
you
how
this
looks
like
in
Visual
Studio
code,
if
you
like,
to
make
it
easier
for
you
to
work
with
I.
Think
that's
a
cool
little
gimmick
too!
So
I
will
shortly
start
into
set
up.
My
visual
studio
code,
sorry
and
I
share
now
Visual
Studio
code
share
screen.
B
E
It
switch
mark
down,
mark
the
maintenance
CLI
too
perfect,
so
another
good
example:
I
have
installed
for
visual
studio
code,
the
markdown
mid
plugin,
so
that
it
that
it
will
also
check
my
markdown
link
files
and
I
will
simply
edit
the
readme
and
add
at
the
end,
some
things
which
should
not
be
done.
E
For
example,
I,
add
here
a
heading
we
had
here
two
headings
and
now
I'm
jumping
as
a
heading
of
the
level
two
and
I'm
jumping
now
here
to
a
heading
of
the
level
of
level
four
and
it
when
I
hover
over
it
will
say:
Hey
you
incremented
the
heading
in
a
wrong
way.
Same
thing
is
when
I
wrote
right
here.
My
note.
E
This
is
a
note,
will
say:
hey
you,
you
see
wrong.
Github
admonition
and
I
can
even
do
click
here
on
quick
fix
and
fix
the
violation,
and
it
will
put
me
into
the
right
right
how
to
say
right
to
text
here
and
the
same
thing
applies
also
for
four
sentences.
So
when
I
write,
hero,
GitHub
GitHub
sentence,
one,
it's
GitHub
sentence,
two
GitHub
sentence
three,
and
it
will
complain
here:
hey
there
is
maximum
sentence
per
line.
E
You
violated
this
here,
but
there
is
a
quick
fix
for
that
and
I
can
set
quick
fix
this
violation.
It
fixed
it
for
here,
so
I
can
fix
it
per
per
violation
it
discovers,
or
what
I
can
also
do
is
when
I
run
my
make
markdown
manners
picks
command.
Is
it
the
make
Command
it
will
run
through
that
and
it
will
fix
it
and
put
all
the
three
sentences
on
a
separate
line.
For
me,
it's
still
the
same
paragraph,
rendering
wise
it
will
not
change
itself
and.
B
E
E
Admonitions
within
markdown
are
really
a
high
topic
with
a
lot
of
discussions.
I
checked
the
common
Mark
common
Mark
is
more
likely
the
the
institution
which
defines
how
markdown
looks
like,
and
there
are
a
lot
of
different
ways
of
doing
admonitions.
So
this
is
just
more
opinionated
rule.
We
can
always
deactivate
it
and
regarding
the
sentences,
this
is
more
like
more
a
guidance
which
should
prevent,
as,
for
example,
in
the
community,
which
should
prevent,
as
we
prevent
the
the
cluttering.
We
do
not
say,
people
should
write
a
sentence
per
line.
E
B
Okay,
but
that's
what
my
question
is:
how
are
we
deciding
this
so
when
we're
so
we're
going
with
the
GitHub
standards,
not
the
Google
style
guide
on
this
stuff
right.
E
E
Do
I
opened
the
pull
request
and
said:
hey,
we
can
look
it
up
in
admonition
like
this
and
taking
a
look
at
it.
So
there
was,
the
rule
was
just
more
likely
invented
after
invented.
The
rule
was
done
after
the
pull
request.
So
because
I
opened
a
pull
request
of
me.
E
E
E
B
E
For
this
rule,
I
took
this
based
on
the
improved
node
and
the
other
one.
This
is
the.
This
is
a
little
bit
more
tricky
because
we
I
think
we
had
this
discussion
within.
More
of
it
wants
did
a
pull
request
and
we
started
this
discussion
within
the
pull
request.
This
was
actually
bad
because
we
did
not
extract
it
into
an
own
into
an
own
ticket
or
make
it
made
it
more
visible.
Besides
that
there
is
a
ticket
for
that
even
part,
we
have
this
ticket
work,
markdown
link.
E
E
A
E
Yeah,
it's
it's
actually.
The
markdon
lint
extension
is
actually
also
from
the
guy
who
writes
smackdownlin,
CLI
2
and
from
the
person
who
wrote
it's
the
same
person
who
wrote
Mark
donlint.
So
this
is
David
Anson
and
he
he
did
a
lot.
So
he
he
it's
not
an
organization,
it
says
private
account
and
a
lot
of
people
always
say
well.
This
is
this
is
just
a
user
and
not
an
organization,
but
this
is
the
official
markdown
link,
no
JS
package
ecosystem,
no
yeah.