►
From YouTube: Keptn Community & Developer Meeting - Mar 01, 2023
Description
Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/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
A
A
To
this
Captain
community
meeting
today
on
the
1st
of
March
I'm,
your
host
as
I
said
I'm
in
short
notice.
I
could
ask
if
I
can
take
over
from
Moritz
because
he's
steadily
occupied.
A
Well
today
we
have
a
pretty
short
agenda.
So
first
of
all,
Moritz
wanted
to
talk
about
a
little
bit
about
the
klt
status
and
the
captain
V1
status.
This
is
postponed
for
to
the
next
community
meeting.
He
will
share
his
note
as
his
updates
there,
and
if
you
have
questions,
if
you
have
other
topics,
please
add
them
to
the
agenda
at
the
bottom.
We
will
get
to
them
one
after
the
other.
A
So
and
I
will
simply
start
with
the
tasks
with
with
my
agenda
items.
First
of
all,
we
will
take
a
short
look
at
peribolos.
Some
of
you
maybe
have
seen
that
we
have
started
so
that
we
have
started
this
discussion
regarding
pariba
loss
and
are
more
likely.
A
Peribolos
is
a
tool
which
is
kubernetes
using
for
managing
their
organizations
and
the
user
management,
and
we
are
now
in
a
state
where
we
can
say:
okay,
we
can
so
we
have
something
to
show
you,
we
have
tested
it
and
it's
most
likely
ready
to
get
merged
and
it
will
show
it
shortly.
Demo
you
what
we
are
doing
with
this
tool.
A
Therefore,
I
have
created
a
few
pull
requests
as
I
have
created
an
own
organization
called
Captain
period
of
test
communities,
and
let's
say
we
wanted
to
add
a
new
member
to
this
organization,
so
I
have
prepared
a
pull
request
for
adding
for
adding
a
new
member
to
the
organization
in
this
case,
in
this
case
it's
Giovanni
Liva.
He
said
he
is
willing
to
join,
so
we
will
add
him
overall
to
the
captain
team.
So
he
has
access
to
the
captain
team.
He
will
be
part
of
the
lifecycle
toolkit
as
an
approver.
A
He
will
be
and-
and
he
will
join
the
overall
organization
versus
here's-
the
organization
where
we
will
add
him
as
a
member-
and
we
also
add
him
to
the
overall
global
maintainers
and
that's
now
the
whole
pull
request
and
what
what
is
when
we
say.
Okay,
this
is
good
and
somebody
approved
it.
We
can
merge
it
and
this
will
trigger
our
whole
pipeline
afterwards
to
give
him
access,
and
we
can
shortly
take
a
look
at
what's
actually
going
on,
so
we
our
tool,
will
then
fetch.
A
A
I
will
just
minimize
all
those
things
all
the
unneeded
things,
so
we
will
generate
the
peripherals
configuration
and
when
we
take
a
look
at
our
at
our
team.
Currently
we
have
two
members.
There
is
an
open
invite
and
nothing
special
going
on.
But
as
these
two
runs
through
now
and
will
apply
the
configuration,
we
will
soon
see
that
we
will
have
a
second
invite.
Now
it's
for
Giovanni
and
also
this
is
now
the
important
part
where
we
will
wait
to
the
end,
because
we
will
see
that
Giovanni.
A
As
I
said,
his
invite
will
be
also
heavily
improved
because
he
will
also
get
access
to
just
a
second
I
need
to
authenticate.
A
That
he
will
get
access
to
that,
he
will
be
added
to
those
teams
we
configured
in
our
in
our
configuration.
Furthermore,
we
have
seen
these
teams
here,
and
this
teams
also
did
have
this.
Based
on
this.
Based
on
the
configuration
we
saw
that
certain
teams,
for
example
the
captain
team-
has
access
to
those
repositories,
the
maintainers
of
this
team-
and
this
looks
like
it-
looks
like
that
we
have
here
maintenance.
A
We
have
here
this,
this
Captain
group
with
the
approvers
with
serial
members,
but
when
we
go
down,
we
have
here
the
maintainers
where
Mauritius
remember,
and
we
have
the
admins,
where
nobody
is
a
member,
and
those
captain
maintainers,
for
example,
have
access
to
those
nine
repositories
we
configured
with
maintainer
permissions,
and
this
is
now
all
handled
via
githubs,
but
that's
not
everything.
So
if
you
have
questions
you
can
always
interrupt
me
and
I
will
answer
questions
though,
but
that's
not
everything.
A
Additionally
to
this
to
this
configuration,
we
also
included
a
an
additional,
as
we
also
use
the
full
feature
of
periblos
and
said
hey.
Why
not
also
provision
our
repositories
with
that
and
that's
why
I
created
the
team
Love
Boat,
so
I
created
a
team
Northport
which
has
access
to
the
repository
lovebird
with
three
maintainers
in
there
and
I
created
here.
A
There
is
an
own
section
called
repos,
where
we
can
simply
add
repositories
with
a
description
and
the
name
and
as
soon
as
I
merge
this
so
the
build
here
will
fail
due
to
other.
It
will
just
simply
fail
because
it
tries
to
access
a
list
of
a
team
which
was
not
created,
so
the
team
will
be
created
with
this
merge
request
and
merge
this
now
and
we
will
see
other
and
we
will,
when
this
action
ran
through,
we
should
normally
have
a
new.
A
We
should
have
a
new
team.
We
should
have
a
new
repository
ad.
This
team
should
have
access
to
this
repositories,
so
this
allows
us
in
the
future
to
wait
to
easier,
manage
member
assignments
be
more
consistent,
who
has
aware
which
permissions
and
have
a
better
overview
about
actual
members,
contributors,
maintainers
Etc,
where
they
have
access
and
where
they
do
not
have
access
access
to
so
I'm,
just
we'll.
Let
this
run
through
this
should
not
take
that
long.
A
Actually,
okay,
so
here
we
here,
we
have
the
our
configuration.
We
see
already
that
there
are
a
lot
of
Broad
approvers
in
there
with
love
with
a
sub
team
called
log
board
maintainers
with
a
team
called
Love,
Boat
admins,
and
this
configuration
run
is
now
running
and
by
now
we
actually
should
have
here
within
the
peribolas
repositories.
We
should
have
our
Love
Boat,
our
repository,
which
we
defined
should
be
created
and
within
the
settings
we
see
as
collaborators
and
teams
we
see.
A
This
admins
approve
is
that
maintainers
are
here
and
also
the
Loft
board,
admins
The,
Love,
Boat
approvers
and
the
log
board
maintainers.
If
they
do
have
members
or
not
members,
we
do
not
care
more
likely,
but
the
people
get
added
here
with
the
other
teams
get
added
with
their
permissions
I'm
going
to
go
as
I'm
going
to
take
a
look
at
the
at
the
teams.
Actually,
we
should
see
here
also
our
Love
Boat
approvers,
more
likely
and
with
India.
We
have
our
loveport
maintainers
and
the
love
code.
A
Maintainers
consist
of
two
members
no
and
have
access
to
this
repository
log
holder,
that's
peripolos
so
far.
This
is
everything
which
I
wanted
to
show
you
regarding
that,
if
you
have
questions,
feel
always
free
to
ask
important,
it
is
please
take
a
look
at
the
pull
request
within
the
captain.
Repository
I
ordered
that
the
markdown
regarding
Community
membership
Etc
because
it
did
not
reflect
the
current
changes
and
it
would
be
good
to
get
here
input
and
approve
as
an
input
and
feedback
before
we
merge
this.
No
okay,
any
questions
regarding
peribolos.
A
Does
not
seem
like
it
perfect,
then
we
continue
with
the
documentation
setup
so
recently
the
documentation
setup.
We
revamped
it
a
little
bit
and
changed
it.
So
now
our
documentation
is
set
up
a
little
bit
differently.
First,
we'll
start
with
the
easy
changes
so,
and
this
is
actually
so.
This
is
when
you
open
a
pull
request
and
when
you
change
something
regarding
your
documentation.
No,
we
now
enable
you
again
like
it
was
with
the
captain
documentation
that
you
can
have
a
preview
of
your
documentation.
A
There
is
this
deploy
preview
and
we
can
click
that
and
we
will
have
the
full
documentation
built
based
on
your
branch
and
your
changes
on
the
branch.
You
can
click
through
everything.
You
can
take
a
look
and
you
can
inspect
if
something
has
changed
or
not
change.
As
of
what
what
has
changed,
if
it's
rendered
correctly
and
also
it
gives
the
possibility
to
the
reviews
to
verify
that
everything
is
rendered
correctly
and
to
read
the
documentation
more
like
it
will
be
delivered
to
others.
A
That's
the
one
part,
that's
the
easy
part,
so
we
have
again
a
netly
fiber
which
allows
you
to
take
a
look.
Only-
and
that
is
important-
this
page
will
only
generate
it
if
you
change
the
documentation,
if
you
do
not
change
anything
within
the
documentation,
you
will
not
get
this
build,
so
this
will
be
canceled.
A
You
know
the
second
part
of
this
is
now
we
have
this
main,
so
we
have
our
alter
the
the
development,
so
the
the
main
branch,
so
our
staging
environment
or
the
latest
development
branch,
is
also
built
automatically
and
is
accessible
currently
still
within
our
test
domain.
Before
we
set
it
live,
we
I
said
we
need,
so
this
is
more
likely
showing
it
today
today,
showing
it
next
week
and
afterwards
we
will
configure
the
domains
to
be
used
by
the
actual
domains.
A
The
main
branch
will
be
also
always
built
and
be
accessible.
With.
With
this
domain,
we
have
here
a
link
to
the
production
as
a
to
the
production
page
and
back
to
these
documentations
within
within
this
folder.
So
this
means
everything
you
push
to
to
the
main
branch.
You
do
not
need
to
change
it
anymore.
It
will
be
all
as
a.
We
do
not
need
to
migrate
those
files.
A
It
will
be
always
the
main
branch
it
will
be
built
when
you
push
something
to
it,
and
this
means
our
documentation
of
the
latest
development
Branch
will
be
always
stable
and
we
do
not
need
to
move
files
around
do
commits
in
another
repository
or
anything
like
that
and
now
comes
in
and
the
third
part-
and
this
is
the
interesting
the
most
interesting,
but
in
my
opinion,
is
the
the
production
build
before
that
the
production
build
was
delivered
from
a
different,
what
I'm
a
different
repository,
so
we
always
cope
with
the
files
from
one
repository
to
the
other
data
renaming
Etc,
we
needed
to
adapt
the
configuration
file
that
this
releases
our
fixed,
and
this
is
not
the
case
anymore.
A
A
This
allows
us
to
to
reduce
the
reduce
the
now
I'm
missing.
The
word
reduce
the
complexity
with
another
repository,
and
we
can
configure
it
within
here.
Additionally,
this
really
as
a
before
that
we
we
needed
to
configure
this
release
more
like
this
versions,
always
via
yaml
file.
We
change
this
now
and
we
adopted
it.
This
documentation
is
fetched
so
the
that
those
versions
are
automatically
built
based
on
the
directory
they
are
in
so
on,
and
the
one
which
is
the
current
one
was
tagged
with
latest.
A
No,
so
we
have
the
older
versions
where
you
can
see
in
the
bottom
line:
it's
v050
from
the
from
the
documentation
and
the
latest
one
will
be
always
that
box
folder,
simply
without
any
additional
version.
Etc.
This
has
some
co.
It's
regarding
SEO
this
with
that
kind
of
solution.
All
our
backlinks
from
other
Pages
Etc
will
always
point
to
the
newest
documentation,
and
we
do
not
need
to
update
canonical
URLs
and
things
like
that,
and
we
also
have
here
the
link
back
to
the
development
which
is
currently
not
working.
A
A
We
have
multiple
pull
requests
open
of
fixing
those,
for
example,
we
have
one
which
is
adding
all
these
documentation
information
we
have
one
which
will
also
add
HTML
test
that
our
link,
verification,
like
we
know
from
Captain
V1,
is
working
and
everything
like
that
is
in
place,
and
we
have
here
the
two
pull
requests
to
fix.
A
Actually,
the
links
on
top
that
they
are
linking
so
in
the
version
that
the
development
on
the
production
branch
is
linking
to
the
correct
version
and
that
production
on
the
development
brand
as
on
on
the
staging
brand
and
on
the
staging
build
this
link
into
the
correct
version.
B
Many
but
I
will
keep
it
short
and
simple.
If
you
go
to
the
oh
God,
the
production
life
cycle,
Dash
test,
yes,
yeah
and
if
you
press
on
Docs,
yes,
which
version
will
be
this.
A
A
Then,
let's,
let's
do
a
little
dig
in
because
that's
interesting
so
with
a
within
our
build
for
the
documentation.
As
soon
as
a
version
is
released,
we
are
triggering
our
build
and
our
build
create,
something
which
is
really
important
we
create
within
within
the
page
Branch
within
each
directory.
A
Now,
when
we
take
a
look
at
our
at
our
release,
build-
and
this
is
this-
is
there
we
are
utilizing
the
GitHub
API
and
also
this
version
file,
so
I
shortly
go
through
this,
this
step
by
step,
what
we,
what
we
do.
First,
we
detect
the
needed
folder
operation,
so
we
check
up
here.
We
do
as
a
first
letter
a
different
way.
A
First,
we
request
the
GitHub
API
and
tell
them
hey,
give
us
the
latest
version
of
after
the
key
first
version
of
the
latest
release
the
tech
name,
and
we
take
this
and
we
save
this
information,
and
then
we
compare
is
the
version
within
the
input
as
of
which
we
provided
to
this.
Is
this
the
same
version?
So
it's
the
latest
version
the
same
version
we
provide
because
then
we
need,
then
we
as
a
then
we
need
to
do
more
checks,
for
example,
is
the
tech
name?
A
We
provide
not
like
the
current
version,
so
did
we
do
a
version
upgrade?
Then
we
need
to
migrate
this
folder
and
we
Define
this
as
a
migrate.
We
need
to
migrate
the
folder
and
provide
the
version
we
need
to
migrate
to
and
we
Define
to
in
which
directory
we
should
point
this
documentation
to,
because
just
because
we're
doing
a
release
does
not
mean
it's
the
latest
version.
It
can
be
also
a
patch
or
minor
release
for
a
previous
version,
and
we
handle
that
and
then
the
cool
part
is
also
remove.
A
Also,
we
moved
if
we
need
it,
remove
the
old
release,
documentation,
folder
and
then
we
copy
the
configuration.
This
means
all
the
configuration
as
soon
as
we
do
a
latest
release.
Only
when
we
do
a
latest
release,
we
take
the
config
folder
out
of
our
main
branch
and
put
everything
over
the
documentation.
This
means
we
do
not
need
to
maintain
it
in
the
page
folder.
We
maintain
it
in
the
main
folder,
where
all
our
development
work
is
happening,
and
we
can
adapt
this
to
our
needs.
A
How
we
want
to
need
it,
then
we
copy
the
documentation
folder
and
in
the
end,
we
push
everything
to
the
branch.
This
is
the
whole
logic.
It's
a
little.
It's
a
little
bit
simpler
and
smaller
and
more
and
so
and
more
compromised
within
this
repository.
I
did
I
hope.
This
makes
the
process
a
little
bit
easier
than
working
with
multiple
repositories,
coping
everything
totally
totally.
C
Diamond,
could
you
go
back
to
where
you
enter
into
the
top
level,
though,
because
if
I,
if
I'm
doing
a
PR,
that's
making
changes
when
that
opens,
I
am
in
the
current
release.
I
will
not
see
the
changes
that
are
my
PR
so
make
that
clear.
What.
A
C
You
mean:
where
do
you
go
back
when
you,
if
you
go
in
you?
Yes,
where
you
land
that
you're
now,
if
I,
if
this
is
for
my
PR
of
new
changes,
I
need
to
go
to
development
to
see
it.
A
Now,
when
you,
when
it's
open,
it's
for
your
PR,
you
have
let's
I
I
need
to
go
to
this
pull
request
with
the
preview.
So
when
you
go
to
your
PR,
you
have
down
here
under
the
checks
you
have
here,
a
section
called
deploy
and
as
soon
as
you
click
here
on
details,
it
will
open
the
and
it's
a
total
different
domain.
It's
it's
simply
a
really
simple
domain
which
will
guide
you
to
your
preview.
Oh,
so
this
is
the
easiest
way
to
access
your
preview.
A
You
can
okay,
you
can
always
go
to
development
and
to
production,
but
you
will
never
leave
the.
You
will
never
be
able
to
go
to
your
preview
from
the
main
branch
or
from
the
from
the
production
branch.
C
Because
I
freaked
out
more
times
than
I'd
care
to
count
with
I've
got
it
and
I
open
it
up.
And
what
and
nothing
is
there
that
I've
been
changing
until
I
go
to
the
development
branch.
A
Okay,
no
just
locally
yeah
I'm,
just
trying
to
figure
I'm
in
a
branch
currently
I
need
I,
I'm,
switching
to
the
main
branch
and
starting
the
server.
That's
what
I'm
doing
makes
so
that
we
can
take
a
look
at
it.
So
I
started
now.
You
do
not
see
this
because
I
only
shared
a
browser
window,
I
I'm,
starting
I'm,
starting
now,
the
server
with
make
server
and
the
server
is
booting
up
just
a
second.
So
it's
running
now
and
what
that
means
is
on
this
domain.
A
I
have
now
my
documentation
page
as
I'm
the
the
release
page
when
I
click
here
on
box
I
come
into
the
documentation,
and
the
same
thing
applies
for
development
up
here.
Production
will
guide
me
to
the
main
page
rather
to
the
to
the
to
the
official
documentation,
but
development
will
be
local
in
the
local
development
will
be
my
local
branch.
A
C
A
C
A
C
A
D
A
C
Okay,
I'll
check
that
out
later
for
our
new
contributors
here.
Do
all
of
you:
have
a
local
development
Branch
set
up
for
documentation
and
do
if
you're
not
do
you
know
how
to
do
it?
Would
you
like
to
see
a
demo,
a
quick
demo.
B
C
A
Just
checking
so
then
I
should
do
this.
I
assume
just
sure
just
a
second,
so
I'm,
switching
to
my
IDE
and
I
will
do
everything
out
of
the
IDE
and
starting
from
the
beginning.
Okay,
I
get
I
assume.
Although
this
is
a
prequisite
I
assume
everybody
did
they
get
checked
out
and
is
aware
of
how
I
get
checkout
Works
a
basically.
A
A
A
A
C
A
Do
I
get
reset
so
I,
just
put
it
back
into
the
former
status.
I
also
removed
my
inputs
as
I.
Also
remove
my
input.
Parser,
okay,
checking.
Okay,
perfect.
We
are
now
up
to
date
with
the
Upstream
Branch.
There's
not
no
changes
locally.
Etc
and
I
am
on
the
main
branch,
as
you
can
see
here
on
Branch
main
when
I
start
working
on
the
documentation.
The
first
thing
I
will
do
is
I
create
my
own
Branch.
There
are
multiple
Chrome,
you
can
do
it
with
it.
A
What
my
my
my
main,
my
main,
is
my
main
is
link
to
Upstream
Master.
It
fetch
it
Edge
Upstream.
A
A
So
this
will
now
download
my
Google
modules
and
everything
it
will
spin
up
the
server,
so
I
can
verify
the
changes
of
my
of
the
server
in
the
meantime
till
this
is
until
this
is
fully
done.
Oh
it's
already
running.
I
can
I
open
a
documentation
page
like
this
docs
getting
started
now
comes
the
complicated
part.
A
So,
okay,
let's,
let's
do
the
simple
part
here
first,
my
screen
is
too
big
to
share
everything.
That's
why
I'm
not
providing
actually
I
need
to
show
you
that
sorry,
just
a
second
I
need
to
change
my
screen
here,
Advanced
portion
of
screen-
hopefully
this
is
working-
is
something
happening.
A
A
I'm
sorry
now
I
will
share
my
whole
desktop
I'm,
really
sorry
for
the
resolution.
I
hope
you
can
see
something
there.
Okay
I
will
then
later
share
a
separate
window
I'm
on
Linux,
and
it's
not
that
great
to
share
those
kind
of
things:
okay,
okay,
so
I
share.
My
whole
screen
I
will
close
that
in
the
meeting.
A
So
you
should
see
my
on
the
one
side,
my
IDE
and
on
the
other
side,
you,
you
see
the
browser-
and
we
have
here
now
the
documentation,
localhost
the
documentation
available
on
Port
14.-
and
this
is
the
this-
is
the
documentation
we're
going
here
today
to
the
overview
I
see
he
learned
Captain
how
to
use
stocks
on
the
other
side,
I
see
that
my
service
running
and
as
soon
as
it
will
hear
some
changes.
I
will
see
that
a
rewrite
is
triggered.
A
A
Additionally,
we
also
have
some
tools
in
place
which
are
checking
for
certain
violations
of
the
structure,
or
things
like
that.
I'm
also
showing
this
right
currently
because
I
think
that's
quite
helpful.
So
you
see
now
I
used
here
ahead
and
the
second
head
and
we
have
a
tool
in
place
called
macdonlint
which
will
check
if
the
configuration
is
properly
working
or
not
in
Visual
Studio
code,
for
example,
you
can
use
a
plugin
which
will
automatically
pick
up
this
configuration.
It
will
show
you
hey,
there's
something
wrong
with
the
heading.
A
There
should
be
only
there
should
be
only
a
level
of
three
heading
and
not
a
level
four
on
the
other
side-
and
this
is
something
which
is
quite
useful-
we
have
a
tool
called
markdown
link
and
we
can
always
inflict
this
with
the
with
make
which
will
download
the
docker
images
and
run
this
configuration,
and
we
will
see
now
sorry
that
here
it
says,
oh
header,
increment
is
not
working
within
this
file.
There
is
actually
on
line
six
team
as
I
on
in
this
file.
I
hope
this
is
visible.
A
On
line
16,
we
have
an
error
which
needs
to
be
fixed.
We
can
fix
this
manually
or
we
also
have
a
Target
which
markdownlin
offers,
which
is
called
markdown
linfix,
which
we
can
apply,
and
this
will
run,
and
it
is
not
able
to
fix
this
error,
but
it
will
fix
this
error
it
can
it
can
address.
For
example,
if
we
have
an
heading
starting
somewhere
in
the
middle,
it
will
be
able
to
address
those
issues.
A
A
We
have
too
many
blank
clients
and
when
I
say
no
marked
on
linfix,
it
will
apply
and
all
that
which
all
those
who
which
it
can
fix
it
will
be
automatically
fixing
which
should
allow
you
to
have
a
more
consistent
style
in
writing
and
allow
you
to
easier
the
handle
and
also
so
to
have
a
better
overview
and
to
have
a
consistent
start.
Some
of
those
rules
are
fixable,
some
are
not
fixable,
just
as
an
information
yeah.
C
D
A
I
will
show
you
something
additionally
now
which
will
be
soon
get
merged,
which
is
also
important
when
you're
running
the
documentation,
because
soon
I
think
I
will
use
that
now,
just
as
a
preview
for
you
soon,
we
will
have
a
tool
called
HTML
test
in
place.
An
HTML
test
is
a
tool
which
will
verify
the
generated
HTML
for
certain
aspects,
so
we
can,
for
example,
put
here
empty
links.
So
we
put
here
a
text
with
an
empty
link,
for
example,
or
on
just
like
this,
and
now
we
have
the
possibility
to
run
make
HTML.
A
A
A
I
assume
this
domain
does
not
exist.
No,
it
will
check
those
and
we'll
say
hey.
There
is
a
link,
for
example.
Here
you
see
already
hey,
there
is
a
link
with
an
an
empty
link
or
an
empty
hash,
and
it
will
check
for
those
and
will
inform
us
about
any
kind
of
issues
which
makes
it
which
can
cause
problems
in
HTML
and
for
accessibility
up
here.
You
see,
for
example,
hey
I
could
not
get
this
no
such
host.
There
is
no
no
the
host
behind
that.
E
I
just
wanted
to
bring
one
thing
in
in
one
of
the
community
meeting
when
when
we
were
going
through
the
installation
process,
dog
per
Captain,
so
mag
you
noticed
about
the
the
old
diagram
of
of
this
particular
process.
You
know
choosing
access
option
if
you,
if
you
visit
that
link
the
diagram
which
is
there
it's
outdated,
but
not
wrong
right.
E
B
E
Yes,
you
go
to
the
installation
part
and
choose
access
options.
C
E
That
yeah,
so
this
diagram,
if
I,
if
I'm,
not
wrong
this,
this
is
outdated
if
I'm
not
wrong.
X.
A
C
Yeah
I'm,
not
sure
yeah
there
is,
is
a
little
nasty
bit
in
the
current
structure
of
the
captain.
Docs
is
that
when
you
open
them,
you
have
the
concepts
and
installation
at
the
top
and
that
those
are
actually
the
1.19
versions
and
you
need
to
go
under
1.0
or
one
point.
Y
dot
set
I
think
it
says
now,
but
to
get
under
there
and
there
and
you
that's
the
installation
for
one
dot.
Whatever
is
that
your
issue
ayush.
E
E
C
Audible,
hello,
so
so
what
is
I'm?
Sorry
and
I'm?
Not
what's
the
problem
I'm
this
chapter,
this
page
has
some
problems.
What
problem
are
you
seeing.
E
In
one
of
the
meeting,
I
I,
just
you
know
heard
that
this
particular
diagram
is
outdated,
so
I,
if
I,
if
no
just
wanted
to
know
if
you
can
upgrade
this,
this
particular
diagram
or
not,
because
I
I
have
been
working
on
this
particular
section
of
installation.
Oh.
D
E
Yeah
so
I
just
wanted
to
ask
you
know
in
what
particular
section
this
diagram
is
needs
Improvement,
so
maybe
I
can
create
an
issue
and
maybe
you
know
update
it.
C
E
No
I
I
would
be
able
to
locate
this
file,
but
the
actual
changes
which
should
be
done
in
the
diagram.
If
you
can
help
me
with
this.
E
Yeah
so
particularly,
which
point
is
outdated
in
the
in
the
diagram.
If
you
can
help
me
not
in
the
meeting,
but
in
in
the
slack
Channel.
Okay.
C
Let's
see
if
we
get
you
some
I
I
admit
I,
don't
know
how
to
do
it
myself.
Well,
let
me
find
and
the
people
who
might
know,
let's
find
somebody
who
can
help.
C
Do
it's
in
the
there's,
an
asset
subdirectory
to
I.
E
Have
been
I
have
been
working
on
this,
so
I
know
it
it's
in
the.
If
you
go
to
the
access
part-
and
there
is
a
complete
structure
of
the
file.
E
No,
not
here
not
in
the
assets
not
in
the
assets,
just
I
think
it's
in
content.
E
Yeah,
so
if
you
scroll
down
it's
yeah,
it's
oh.
A
Yeah,
it
should
be
in
both
I
thought
here:
I
have
a
click
list,
interior
is
assets,
but
here's
just
a
PNG.
C
Right,
you're,
not
in
what
what's
your
wait
a
minute,
let
me
see
your
path.
A
C
C
A
We
have
mermaid
or
plant
uml
support,
one
of
those
one
of
the
two
so
mermaid
diagrams
mermaid
is
a
language
which
is
also
used
on
GitHub
to
to
create
flowchart.
A
So
you
can
create
you
because
there
is.
Is
there
there's
a
live
editor
where
you
can
easily
create
flowchart
based
on
code,
which
is
really
easy
and
helpful
or
the
other
one?
We
need
you,
we
would
need
to
check,
which
is
supported.
The
other
one
would
be
plant.
You
know
one
of
those
two
I'm
pretty
sure
we
understand
as
a
real
support
yeah,
but
I
cannot
tell
you,
which
one
exactly.
E
A
E
A
D
A
E
Not
sure
just
go
through
the
conversations
on
the
BR,
you
will
get
to
get
an
overview
of
of
the
thing
which
I
have
done.
It's
basically
I
have
merged
the
two
pages
for
documentation
which
were
kind
of
similar
to
each
other
and
I
just
wanted
to
draw
attention
of
Maggie
here,
because
she
she's
an
reviewer
for
this.
For
this
PR.
C
A
E
We
will
be
having
the
talk
for
CLT
in
the
next
meeting
right.