►
From YouTube: Keptn Documentation WG Meeting - Mar 23, 2022
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
Okay,
thanks
everyone
for
joining,
so
today
we
have
out
of
order
meeting
focused
on
documentation
and
yeah.
They
will
discuss
a
cool
summer
of
code,
google
season
of
docs,
then
a
new
documentation
engine
with
a
prototype
of
the
kosarus
rajiv.
Are
you
ready
to
present
today.
A
A
And
then,
let's
begin
so
for
google
summer,
of
course,
actually
nothing
changed
significantly
over
the
past
week.
So
we
are
still
looking
for
potential
project,
ideas
and
mentors
if
somebody
wants
to
come
up
with
new
ideas
and
for
existing
ideas.
Momentous
are
welcome
and,
more
specifically,
students
are
welcome
to
submit
their
ideas
to
discuss
them
in
the
chat
and
if
you
have
draft
proposals
ready,
also
feel
free
to
publish
them
so
that
we
can
discuss
so
no
new
projects.
A
A
And
let's
go
to
google
season
of
logan
so
for
google
seasonal
dogs.
Here
we
have
just
two
days
until
the
submission
deadline,
and
the
question
is
whether
we
want
to
submit
this
time
so
we
have
who
is
interested
in
participating
as
mentee.
We
have
america
as
potential
mentor.
Well,
I
could
be
a
potential
mentor
too
time
compass,
of
course,
assuming
that
I
find
enough
capacity
to
do
that.
So
the
question
is
whether
we
have
enough
to
apply
from
your
point
of
view
and
whether
we
should
apply
well.
We
should
apply.
C
A
So
gsoc
should
be
programming
g
such
should
be
documentation
and
for
documentation.
Of
course
it
could
be
a
lot
more
focused
on
the
content,
so
we
can
move
the
project
idea
over
here
and
then
we
can
see
whether
it
would
be
accepted
just
to
show
you
how
the
forms
look
like.
So
this
sort
application
process
is
slightly
different.
A
It's
not
going
to
work
like
that,
but
here
the
idea
that
for
google
seasonal
docs,
we
will
have
to
find
maintenance
on
our
own
and
submit
a
budget
application.
A
But
to
do
the
that
the
first
item
for
us
would
be
to
agree
on
the
project
and
I
think
that
the
project
we
should
focus
on
is
actually
reworking
the
documentation,
content
structure
so
basically
supporting
the
documentation
engineering
work
because
they
will
be
definitely
plenty
of
work
on
improving
our
documentation.
Migrating
into
new
formats.
Adopting
documentation
is
code,
doing
various
kinds
of
indexing
rearrangement,
so
it
definitely
constitutes
a
full
google
season
of
docs
project
and
yeah.
This
is
the
idea
with
precedence.
D
Yeah,
I'm
not,
I
don't
we're
not
allowed
to
submit
the
same
idea
to
both
gs
summer
code
and
summer
dogs
right.
A
Well,
we
cannot
because
the
scopes
are
different
but,
for
example,
documentation,
structure,
content
work
are
completely
different
from
the
documentation
engine,
so
yeah.
This
work
can
happen
in
parallel,
but
the
projects
are
different.
C
A
Exactly
so,
we
will
have
to
work
on
that,
regardless
of
whether
we
have
a
google
season
of
docs
projects
or
not
this
year.
So,
let's
say
probability
of
being
accepted
is
let's
say
20
to
30
percent,
but
if
you
accept
it,
it
would
give
some
additional
bandwidth
to
work
on
the
documentation.
D
D
A
A
So
this
can
what
can
be
done
without
engine
at
all
and
once
engine
is
done.
Of
course,
we
can
do
more,
focusing
on
documentation.
D
D
So
maybe
we
have
somebody
work
on
installation
or
quick
start
tutorials
we're
already
we're
doing
a
lot
of
work
on
the
reference
pages
with
people.
Just
we
could.
E
D
A
Well,
we
definitely
need
one
description
which
would
be
focused
on
documentation,
restructuring
et
cetera
so
like.
If
you
would
be
willing
to
write
it
up,
it
would
be
great
yeah
but
yeah.
Then
it
would
be
nice
to
have
it
by
tomorrow,
so
that
we
can
have
application
going
with
this
project.
D
A
That's
right
and
again
for
gsoc
for
json,
it's
something
dynamic,
so
you
can
change
the
scope
as
the
project
goes
and
there
is
no
problem.
A
So
then,
if
you
could
write
it
up,
it
would
be
great
and
I
will
prepare
all
the
application
form.
D
A
Okay
and
yeah,
one
question
which
was
brought
up
is
about
catecholam
because
currently
we
have
cataclysm
in
g-shock,
but
there
was
a
question
whether
it
rather
fits
g-shot.
A
So
when
we
were
discussing
it
with
absal,
it
seemed
that
it
would
be
a
lot
of
coding
there
and
hence
it
would
be
rather
as
part
of
google
season
of
code
and
sort
of
google
summer
of
code.
But
again
this
is
the
case
when
the
project
again
can
be
represented
as
coding
site
or
as
documentation
side.
D
I'm
thinking
yeah
that
everything
becomes
both
we
need
to
we.
If
we
want
to
go
dakota,
we
need
to
get
it
set
up.
So
we
have
a
generic
playground
up
there
and
then
instructions,
because,
as
we
go
through
and
do
individuals
say
tutorials,
we
would
need
mo.
You
know
we
would
need
a
specific
catacota
playground
that
had
what
you
needed
for
that
particular
exercise
right.
D
So
yeah,
I'm
thinking
that
I'm
I'm
thinking
that
way
too,
that
we
should
do
the
coding
part
now
to
get
that
up.
Be
very
sure
that
the
definition
is
part
of
that
is
to
provide
good
instructions
for
anybody
who's,
trying
to
do
a
specific
exercise
and
would
need
their
own.
You
know
to
create
a
separate
catacota
sandbox
that
would
just
support
their
exercise.
D
That
would
have
everything
installed,
that
they
need
and
that
that
that
that's
it
for
this
summer
and
then
other
people
can
work,
and
it
might
be
that
you
know
whoever
works
on.
If
somebody,
if
one
of
the
google
summer
doc
things
we
do,
is
tutorials
and
example,
projects
that
it
is
understood
that
after
the
summer,
somebody
might
implement
the
catacode
of
sandbox.
Is
that
reasonable?
But
it's
not
part
of
summer
of
docs.
A
I
think
so
so
yeah
there
is
a
discussion
in
the
chat
whether
it
could
be
a
combination
of
both.
Unfortunately,
this
is
not
how
google
summer,
of
course,
and
google
season
of
docs
work.
So
of
course
you
can
put
some
bits
of
documentation
in
gsog
and
this
what
we
will
expect.
So,
whatever
your
work
should
on
should
be
properly
documented
and
presented
to
the
community
and
for
google
season
of
dogs.
A
It
could
be
the
same
so
some
scripting
like
let's
say
demos,
etc,
they're
appropriate
there,
but
you
cannot
put
both
coding
and
documentation
as
key
deliverables
because
there
are
expectations
in
the
program.
So
in
google
summer,
of
course,
students
expect
to
code
most
of
the
time
in
google
season
of
dogs.
You
expect
documentation
and
tech
writers
to
participate
and
to
first
mostly
work
on
the
content.
A
D
We
could
yeah
and
let
me
understand,
I'm
thinking
that
if,
if
one
of
our
summer
of
docs
projects
were
to
be
these
projects,
tutorials
these
sorts
of
things
that
part
of
the
definition
of
that
should
be
a
spec
for
what
would
need
to
go
into
a
sandbox
so
that
you
know
it
needs
disintegration.
D
This
service,
it's
a
shipyard
file
that
looks
like
this.
You
know
to
have
just
that
specification.
It's
it's
not
tied.
I
mean
it
wouldn't
even
be
tied
to
catacota.
It
would
be
if
you
were
going
to
make
a
sandbox
for
this.
This
is
what
would
need
to
be
included,
and,
and
that's
it
we
might
even
come
up.
You
know
that
might
not
be
a
bad
idea
if
the
directory
that
had
this
documentation
source
had
that
spec
of
what's
needed
for
any
sandbox
that
you
execute
this.
D
A
Reasonable
or
well
it's
reasonable
to
say,
but
I'm
not
sure
that
it's
how
it's
going
to
work
so
yeah,
you
create
all
this
specification,
but
users
cannot
use
it
until
the
engine
is
created
right,
so
it
will
have
a
limited
community
value.
So
in
this
case.
D
It
would
be
there
for,
but,
but
it
would
be,
as
opposed
to
somebody
else
coming
in
and
having
to
read
the
tutorial
and
say:
oh
okay,
they're
assuming
a
shipyard,
I've
got
to
build
a
shipyard
file
in
there.
They've
got
to
go
through
and
figure
out
what
needs
to
be
in
that
shipyard
file
that
the
writer
of
the
tutorial
could
define
what
is
needed
to
make
this
work.
D
E
D
A
Yeah,
I
think
it
should
be
a
rather
separate
yeah,
okay,
so
basically
what
the
conclusion.
So
I
think
we
should
keep
catacotta
as
this
in
google
summer
of
code
for
documentation.
It
makes
sense
to
have
something
on
the
ideas
list,
but
I'm
not
sure
it
would
be
for
google
season
of
docs
this
year.
It
can
be,
let's
say,
lfx
mentorship
in
autumn
et
cetera,
but
right
now
I
wouldn't
rather
see
it
as
a
g-shot
project.
D
I
no
I
I
agree,
implementation
definitely
not
spec.
Maybe
I
would
argue
that
spec
would
be
part
of
defining
this,
but
let
me
let
me
write
it
up
and
we
can
look
at
it.
We
don't
need
to
argue.
A
So
anything
else
on
google
seasonal
talks,
or
should
we
place
it
with
the
documentation
engine.
A
B
A
B
Okay,
so
so
just
to
be
clear.
E
B
Engine
is
not
part
of
a
google
summary
of
talks.
What
is
particularism
of
google
summary
of
fox
is
what
goes
inside
katakura
the
way
the
tutorials
are
designed
right.
That
is
where
the
technical
writing
part
comes
in.
A
Well,
mostly
still
providing
tutorials,
because
you
need
to
remove
tutorials
so
that
they
follow
katakura
as
one
of
the
options.
So
you
can
you
actually
use
it.
It
will
require
some
examples,
some
configurations
and
ultimately,
a
lot
of
documentation
like
step
by
step,
guys,
descriptions
etc.
So
this
part,
which
could
be
a
part
of
g
sort
or
another
project
plated
this
year,.
D
What
we
currently
we
currently
a
number
of
tutorials,
etc.
They
there's
a
lot
of
issues
with
a
lot
of
them,
but
the
current
way
of
doing
the
tutorials
is
we
have
the
files
you
need
for
sample
projects
are
in
github
and
part
of
your
instructions.
You
have
to
go
through
and
you
have
to
either
bring
or
create
a
kubernetes
cluster,
and
you
have
to
install
and
the
cli
and
captain
itself
and
create
a
an
instance,
and
then
it
tells
you
to
download
this
stuff
from
github.
D
So
you
have
to
set
all
of
that
stuff
up
so
that
whole
process,
and
then
you
get
to
do
the
exercise
and
actually
learn
something.
D
But
if
we
never
group
catacota
or
until
we
do
catacota,
they
still
got
to
do
the
exercise
they're
just
going
to
have
to
download
everything
from
github
and
install
everything
for
themselves.
So
catacota
is
better,
but
the
basic
the
information
is
right
there.
D
So
part
of
the
and
one
of
the
things
I
think
is
we
a
lot
of
these
tutorials
were
done
by
somebody
very
smart
at
one
moment
in
time,
and
they
just
created
everything
and
made
it
work,
but
then
somebody
else
comes
in
and
they
don't
understand
what's
in
the
project,
what
has
to
be
in
that
project
to
make
it
work
and
it's
making
maintenance
and
updating
keeping
it.
You
know
really
tough,
so
it
may
well
be
the
important
thing
to
make
these
sample
projects.
D
Work
is
to
have
whatever
you're
doing
when
they
get
here
to
do
the
exercise.
They
need
to
have
this
stuff
set
up
so
yeah
there,
but
that
all
of
all
of
that
stuff
is
independent
of
whether
or
not
we
do
catacota
so.
D
A
Basically,
we
have
three
deliverables,
firstly,
specification
as
mentioned
with
all
these
requirements,
etc.
Then,
engine
that
allows
to
implementing
these
specifications
and
then
the
actual
implementation
with
all
the
documentation.
B
You
got
it,
thank
you
and
max.
So,
basically,
even
if
there's
some
technical
stuff
involved
in
the
documentation,
we
are
fine
with
it
as
long
as
documentation
is
the
main
focus
and
that's
how
we
basically
include
it
in
the
boundary
of
google
summer
of
talks,
yeah
right.
A
Right
so
here
we
are
talking
about
technical
writing,
so
it
means
the
technical
writers
are
expected
to
actually
be
able
to
run
the
product
to
relate
it
to
the
current
real
user
and
developer
experience
and
yeah.
It
would
be
a
wrong
expectation
if
you
just
set
a
writing
infrastructure
and
documentation
without
ever
launching
a
captain
very
nice.
So
this
is
definitely
something
my.
D
My
biases,
but
but
I
think
one
of
the
issues
with
our
current
tutorials
is
it's
a
lot
of
do
this.
Do
this?
Do
this?
Do
this
and
then
everybody
sit
back
and
go
wow?
It's
not
necessarily
a
good
first
learning
step.
D
It
doesn't
say:
okay,
we're
going
to
do
this
because
we
need
such
and
such
and
in
this
example,
we're
doing
this,
but
you
could
also
you
know
in
this
example
we're
using
prometheus,
but
this
would
also
work
with
datadog
and
dynatrace
and
this
and
that,
but
you
would
have
to
do
this.
D
D
I
got
red
and
green
squares
on
my
display,
but
I
didn't
really
learn
anything
and
that
that's
where
the
real
writing,
skill
challenge
and
frankly,
interest
interesting
work
here
would
be
is
for
somebody
to
put
that
richness
into
the
text
which
is
pure
writing,
but
pure
writing.
Based
on
running,
of
course,
the
things
so.
D
E
B
The
problem
I'm
hearing
meg
is:
how
do
you
give
a
more
holistic
understanding
from
a
quick
start
right
or.
B
D
By
the
way,
I
don't
know
that
I
speak
officially
for
anybody,
it's
just
my
opinion,
but
there
I
yeah,
let's
not
go
down
too
far
down
the
rabbit
hole,
but
but
it
is
there's
there
is
a
place
for
demos
that
are
sort
of
pre-sales
where
you
just
get
people
interested-
and
you
say
you
know
our
pre-implementation
but
say
you
know,
look
at
you
can
make
it
do
this
and
this
and
this
and
that's
sort
of
to
me
the
tutorials
that
I've
looked
at
that's
sort
of
where
they
are
there's
the
other
one,
that
this
is
how
you
really
get
started
using
this,
and
it
includes
you
know
in
most
cases
it's
going
to
be
the
happy
path,
you're
not
going
to
give
them
at
least
the
first
level
of
tutorials.
D
It's
not
going
to
be
something
difficult,
but
you're
going
to
warn
them.
You
know
this
is
a
complicated
project
and
you
have
to
be.
You
know,
don't
do
this
because
it
could
do
it.
Could
you
know
cause
a
little
bullet
to
go
through
your
big
toe
so
yeah,
so
that
that
would
be
a
lot
of
the
art
of
the
writing
and
and
one
of
those
things
that
we'll
figure
out
as
we
go
along
so.
B
Also,
I
think,
raised
a
question
about:
where
does
the
katakura
project
area
go
into
the
the
ancient
idea
going
to?
Does
it
go
into
g-shock?
Are
we
planning
to
do
it
as
a
part
of
lfx.
A
A
Yes,
so
these
parts
have
to
go
to
gsoc.
Well,
it
can
be
lfx
mentorship
because
in
lfx
mentorship
we
are
more
flexible
in
what
is
the
project
scope,
so
we
can
have
hybrid
projects,
documentation
and
coding.
A
A
D
So
we
could
work
on
the
tutorials
on
the
content
on
the
writing
on
the
projects,
get
interesting
projects
with
interesting,
rich
commentary
for
it
and
the
instructions
for
doing
everything
the
hard
way,
which
is
basically,
you
set
up
your
own
environment
to
run
it
in
and
then
somewhere
in
the
future.
If
we
had
something
like
catacota,
there's
actually
other
options,
but
whatever
that
we
could
go
in
and
make
it
so
they
didn't
have
as
much
work
to
do
to
set
it
up.
E
D
Put
it
another
way,
if
you
take
exactly
what
we've
got
now
for
tutorials
and
we
had
catacota
up
and
you
could
run
them
on
catacota,
I
still
think
they
would
be
unsatisfactory
as
tutorials
and
that's
the
work
to
be
done
in
google
summer
of
docs
is
to
get
that
content
and
the
writing
up
to
snuff,
and
then
it's
a
tooling
issue
of
how
we
get
them,
how
we
more
easily
and
reliably
get
them
into
an
environment
where
they
can
do
the
exercise.
B
A
Oh,
thank
you
so
for
that
yeah,
for
I
think
we
keep
it.
So
we
don't
remove
the
project
idea
and
let's
see
whether
we
have
potential
mentees
who
are
interested
in
this
project
yet
and
looking
forward
to
proposals.
F
Yeah,
yes,
I
actually,
I
missed
some
of
the
points
I
actually
came
here
late.
I
joined
here
there
actually
considering
about
category
like
for
this
watch.
F
All
of
your
opinions
like,
should
we
consider
this
project
for
g-shock
or
g-sword,
or
maybe
I
was
wanting
like
on
this
live
channel
or,
like
you
just
like
asked
like,
could
it
be
another
project
idea
for
g
sword,
then
I
thought
like
yeah
it
could
be,
then
maybe
we
can
ship
this
to
g
sort,
because
if
you
consider
other
tutorials
like
videos
and
writing
some
refactoring
existing
talks,
so
maybe
we
can
extend
those
idea
and
consider
it.
A
You
mean
consider
this
part
for
g-shot
yeah.
I
was
asking:
should
we
consider
or
something
my
understanding.
That
would
be
a
great
one,
that
okay,
we
keep
the
current
id
in
g
soap.
Yeah,
I
mean
the
idea
which
was
represented
here.
We
can
find
you
the
unit
to
emphasize
that
it's
small,
scripting
etc,
but
we
keep
this
id
here
and
for
g
sort.
A
We
actually
might
want
to
create
summary
of
what
could
be
done
with
tutorials
et
cetera,
and
it
would
include
katakuri
as
one
of
sub
items
but
yeah
right
now.
We
wouldn't
put
a
special
idea
just
for
kadakoda.
A
Yeah,
so
it
makes
sense
to
mention
katakura
there,
but
regarding
full
fledged
project
id.
I
think
that
we
first
need
an
engine
to
be
ready.
D
A
A
A
Now,
basically,
one
of
items
we
need
to
agree
on
is
what
would
be
our
future
engine.
So
initially
I
proposed
anteroid
because
I
do
have
experience
with
it.
I
think
it
fits
the
use
keys
well,
but
we
had
a
discussion
whether
you
would
like
to
press
it
with
the
enterer
or
maybe
with
docker
servers
who's
more
designed
for
markdown,
and
this
way
we
stay
at
the
moment.
A
So,
right
now
again
it's
up
for
discussion
up
for
proposals,
so
everyone
can
make
a
proposal
for
antera
for
locus,
arrows
or
basically
for
any
other
engine
you
can
come
up
with.
I
just
I
just
asked.
Please
do
not
suggest
wordpress
other
things
we
can
really
discuss
and
really
how
we
implement
worked.
D
A
Yeah
and
actually
so
now,
I
think
that
we
should
just
give
floor
to
rajiv
because
he
created
the
prototype
for
the
kuzarus.
So
we
can
take
a
look
together
and
see
whether
we
can
focus
on
it
as
one
of
the
ways
to
go
again.
It
doesn't
put
interval
of
the
table,
but
at
least
it
would
provide
some
insights
for
those
who
consider
docus.
G
B
G
Yeah,
hello,
everyone,
I'm
rajiv,
I'm
a
final
year
student
from
india,
so
I'm
going
to
give
a
poc
on
docker
service
and
this
all
discussion
will
be
based
on
like
we
are
discussing
revamping
the
captain,
dockside
and
so
let
me
say
the
screen.
A
Yeah
so
so
baby
uses
web
htc,
and
sometimes
there
are
issues
with
it
because
super
pc
with
well
with
all
respect
to
the
technology,
still
not
100
stable.
It
also
requires
a
lot
of
permissions
and
browsers
like
chrome,
so
sometimes
it
doesn't
quite
work.
A
A
Yeah
so
well,
while
we
wait
for
a
gif,
I
can
actually
show
it
to
you.
So
currently
we
use
baby
provided
by
the
cncf,
so
they
have
community
portal
there.
You
can
host
various
virtual
and
hybrid
meetings.
Well,
bell
itself
isn't
well
designed
for
hybrid
meetings.
It
just
can
be
a
platform
like
meetup.com
in
this
case
and
for
video
it
supports
up
to
50
hosts
with
voice
and
video,
so
for
various
kinds
of
meetups
project
meetings
and
for
webinars.
A
G
D
G
Okay,
so
my
proposal
is
for
docuseries,
so
the
I
wa,
so
all
the
links
and
all
the
docs
to
discuss
is
already
in
the
meeting
now,
so
I
can
go
through
that
and
slack
threats
and
all
so.
I
have
first
doc
like
like
difference
between
the
and
torah
and
all
docusaurus
and
other
engines.
So
all
the
points
related
to
it,
I'm
not
going
through
that
like
why
we
need
and
torah
why
we
need
docker
servers.
My
like
dakosaurus,
I
think
antora
will
be
given
by
oled
okay.
G
So
so
the
two
reasons
why
I'm
it
is
like
the
takosaurus
has.
G
Like
things
like
different
pages,
now
you
can
data
properly
and
all
markdown.
So
that's
one
feature.
So
if
you
want
to
design
some
example
like,
I
want
to
show
some
animations
I
wanted
for
some.
G
Let's
get
that
inside
the
markdown
docs
we
have
mdx.
Support
of
supporting
taco
is
like,
obviously
in
now
most
of
the
dog
site
is
a
bit
more.
It
will
be
so
change
something
else.
It
might
be.
You
know
one.
G
They
have
a
markdown
to
content
so
to
one
side
to
another
side,
because
I
have
a
markdown
in
case
of
antora.
I
think
we
don't
have
a
markdown
support
properly,
I'm
not
sure
so.
That's
a
two
real
taco
sodas
yeah.
Are
there
any
other
reasons
to
I
like
the
features
of
docosaurus
like
we
in
the
top
of
like
we
have
a
that
like
we,
we
can
have
a
live
score
on
this
weekend.
G
We
can,
we
can
see
on
docs,
we
have
a
public
up
because
obviously
it's
based
on
react.
So
we
have
easy
to
seo
friendly
this
I've
already
discussed
power
powered
by
mdx
for
powerful
search.
So
we
can.
We
can
use
a
search
support,
but
we
can
use
algolia
on
top
of
it
to
search
our
contents,
so
search
tool,
document,
versioning,
again
versions
of
docs.
So,
okay,
if
you
can
see
like
I
have
like
poc
website
here,
I'm
running
locally.
We
can.
G
G
You
can
have
versions
of
dogs
like
oh
and
like
i18
support.
We
have
language
supports
different
language
supports.
G
Obviously
I
can
classify
reloading
it's
easy
to
use
like
we
don't
have
to
care
much
about
the
code
if
you
want
to
like
you
can
but
like
it's
just
a
markdown
base,
so
easy
to
use,
and
all
that,
like
about
the
docker
service,
like
it's
a
tool
for
easy
building,
deploying
and
maintaining
open
source
project,
facebook.
G
So
now
I
will
give
a
like
thing:
the
button
of
docs
and
black
support.
That
means
we
can
be
able
to
like.
Can
we
able
to
pull
the
pull
the
dogs.
G
So
first
I
will
show
the
versioning,
so
we
have.
I
have
created
two
one
point:
one
zero
and
one
two
point:
zero.
Okay,
so,
like
you
can
see,
this
is.
G
G
So
we
have
one
point,
two
point
one
point
zero.
So
it
will
duplicate
the
this
dot.
So
what
we
have
so.
G
So
our
version
you
are
created,
we
don't
take
much
take
care
of
much
like
this
or
docs
1.2.0,
and
this
this
is
the
new
docs
1.3.0.
All
the
all.
The
documents
of
this
is
duplicated
in
1.3.0,
so
when
we
go
to
that
local
site,
so
we
can
see
one
point
here.
I
think
if
we
depress
it,
I
think
I
think
we
have
to
restart.
G
Okay,
so
we
have,
we
got
a
1.3.0,
this
repo,
and
this
will
be
same
as
the
current
version
like
because
we
have
to
the
current.
This
is
the
later
we
can,
if
you
want.
We
can
like
hide
this.
Also
this
these
are
messages
we
can
just
edit
it
like.
If
you
want,
this
is
not
unstable
version.
G
Anything
we
want
to
put
it
like.
We
can
like
this
is
the
current,
and
this
is
all
the
version.
This
is
the
like
the
current
and
the
latest
latest
one
if
you
want
to
showcase
like
if
you
want
to.
G
I
will
put
a
will
be
only
the
lay
and
only
that
different
version
will
showcase
like
like
this.
This
is
the
wait,
a
minute.
G
Okay,
we
we
don't
the
current
work
done,
so
we
can
configure
accordingly.
So
this
is
very
easy
to
use
nothing
you
have
to
if
you
want
to
edit,
like
you,
can
go
to
that
folders
and
if
you
want
to
organize
like
like,
if
you
wanted
to
case
like
I
want
to
showcase
here,
like
1.2.0,
not
one
point,
so
you
can
easily
configure
it
in
sidebar
like
accordingly,
one
point
you
just
rename
it
or
just
hierarchy,
wisely,
okay.
G
So
now
the
second
like,
I
think,
like
the
two
things
were
mentioned,
more
focused
on
this
versioning,
and
I
think
so
this
next
I
showcase
this
and
now
the
one
like
we
have
a
dark
side
so
like
you
want
to
focus
all
other
repo
docs
in
the
same
dark
side.
So
how
do
you
do
it
so
I
have
like
we
have
this
person
on
the
slag.
G
You
can
find
on
that
put
the
links
in
the
caption,
noting
meeting
notes,
so
the
possible
solution
like
given
by
asuras
and
even
so
like
we,
we
can
write
a
github
actions
to
pull
the
talks
from
different
repo
and
just
present
to
the
like
that.
Captain
dark
site,
like
my
approach,
was
to
like
having
a
docker
site
for
each
repo
like
we
on
dock,
we
can
just
that
is
a
very
cumbersome
process.
Even
I
am
not
supporting
this.
I
just
put
it
here
thing
is
that
we
can.
G
We
have
a
plug-in
for
the
rocker
servers
which
pulls
a
docks
from
other
repos.
This
is
called
docker,
such
plug-in,
remote
content.
G
I
think
I
have
to.
I
think
we
need
one
more
poc
on
there
now,
because
I
found
a
different
way
to
pull
the
docks
and
that's
a
is
a
zero
md
tool
like
it's
a
tool
which
can
pull
a
mark
down.
We
can
we
which
can
pull
the
docks
from
dock
and
we
can
render
it
to
different
markdown.
I
have
I
I'll
showcase
this.
How
I'm
doing
this?
So
let
me
go
to
so
you
can
see
this
right.
G
I
didn't
I
just
pulling
it
from
redmi.
So
if
you
change
here,
it
will
change.
There
also
show
you
how
I
am
doing
it,
so
this
is.
This
is
the
one
point
I
mean
the
one
point,
1.1.0
version,
and
this
is
the
intro
mdx
file.
So
this
is
I'm
pulling
this
readme
this.
So
if
you
want,
if
I
want
to
pull
some
something
else,
I
want
to
showcase
it
like.
I
want
to
pull
change
log
like
many
times.
G
You
want
to
showcase
all
the
changes
along
to
the
website,
so
I
will
see
else
url
and
I
will
change
the
readme
to
now.
It
should
profile
error,
oh
call
change
log,
so
we
can
so
now.
I
am
showcasing.
G
Well,
it
won't
be
able
to
find
in
this
this
here
because
I'm
not
pushing
it
to
the
airport
tree.
I
think
this
we
can.
I
think
this
is
a
one
way
to
pull
the
dogs
from
one
to
one.
G
Like
this,
I
have
to
pull
the
docks
from
one
place.
I
just
entered
it.
You
know
we
just
use
this
image,
I
just
simple
html,
I'm
just
using
the
zero
md
to
pulling
the
docs.
So
this
is.
G
Even
now
also,
we
should
focus
on
this.
I
have
to
try
this
the
docker
service
plugin
and
even
the
github
actions
thing.
G
This
is
like
something
a
lot
of
discussion
needed
here,
so
I
think
the
two
things
we
this
is
worsening
and
still
done
and
completed
other
than
that,
like
other
things
of
markdown
docker
services,
since
we
we
want
to
pull
docks
from
other
repo,
so
we
want
to
so
now
the
power
of
create
custom
email
pages
like
we
have
a
blog
pages
so
like
that
we
can
here
in
the
in
the
top
bar.
G
We
can
create
all
the
docs
of
other
reports
like
to
so
that
is
more
like
more
suitable,
like
we
can
create
here
our
custom
pages
and
like
this
we
have
a
sidebar
accordingly.
So
that's
that's
why
the.
G
Scalable
thing,
so
that's
about
other
links,
meeting
notes.
A
Thanks
for
the
demo,
indeed,
it
should
be
able
to
work
in
our
case.
One
question
is
about
scalability,
because
if
you
talk
about
pulling,
let's
say
a
limited
number
of
files
like
changelog,
etc
from
external
repositories,
it's
one
of
the
questions,
but
if
we
assume
that
we
would
be
pulling
thousands
of
files,
sometimes
folders,
then
the
question
is
whether
this
approach
would
actually
work.
G
Like
like
yeah
and
that's
that's
a
question
when
I
was
thinking
like
you,
we
don't
want
anyone
single
file,
you
want
a
lot
of
like
whole
repo
and
we
also
have
to
see
like
where
we
are
pulling
the.
G
Like
we
have
to
try
things,
I
think
that
doctors
are
just
plugging.
I
think
I've
gone
through.
G
C
G
No
no
versioning
like
it
will
create
a
new
whole
folder
on
like
a
new
version,
so
in
that
everything
will
be
there.
What
what
we
have
like
a
whole
new
docker
structure
of
that
so
inside
that
structure,
only
we
will
be
using
yeah.
C
C
G
Yeah,
that's
what
I
are
going
to
say.
Like
the
plug-in,
I
saw
you
docusaurus.
It
has
a
the
versioning
thing
in
that,
but
like
pulling
a
door
with
a
with
the
version
thing
like
we
can
use
what
talking
we
should
use
the
docker's
plugin,
not
this.
This
is
just
a
showcase
like
this
is
achievable,
and
even
that
question
is
like
that
is
also
like
soluble
by
using
the
docuseries
content.
Plugin
and
like
you
can
go
to
the
show,
I
will
showcase
the
site
which
is
high.
A
Yeah
also
so
one
of
the
things
we
could
always
consider
is
git
sub
models,
because
many
items
could
be
potentially
just
rebuilt
from
using
by
using
some
models.
You
can,
let's
say,
github
repositories
by
specific
version,
specific
branch.
You
can
also
use
dependable
to
automatically
update
these
dependencies.
A
A
A
The
first
one
is
markdown,
because
markdown
is
arguably
easier
for
developers
than
a
ski
doctor.
Well,
ascii
doctor
is
just
well.
It
has
a
lot
more
features,
but
if
you
don't
use
them
ask
your
doctor
is
also
quite
simple,
but
there
are
features
that
are
available
for
professional
editors,
for
example,
templating,
macros
and
other
things,
and
well
basically
ask
a
doctor
comes
with
for
functional,
complete
programming
language,
so
you
can
do
a
lot
of
the
things
today.
If
you
really
want.
D
Okay,
go
ahead:
okay,.
A
So
in
this
case,
we
are
rather
talking
not
about
pure
markdown,
but
about
extended
markdown,
because,
for
example,
hugo
supports
templating
markdown
here
you've
presented
the
mdx,
which
is
also
done
with
some
extensions
with
references
with
plugins
can
be
connected,
and
so
it
wouldn't
be
correct
to
just
compare.
D
D
Yeah,
getting
away
from
mark
down
to
me
is
a
plus,
but
I
don't
I
don't
know
what
these
ex
ones
that
bother
me
are.
The
cross,
referencing
facilities
and
markdown,
especially
internally,
are
weak
and
somewhat
unreliable
ditto
the
ability
to
put
comments
inside
a
file
just
fraud,
shall
we
say
with
markdown,
although
I
I
do
know
that
some
work
has
been
done.
You
know
externally.
D
D
D
So
I'm
just
saying
just
you
know
just
cons.
I
think
I
don't
know
if
I
care
about
this,
that
much
but
with
markdown
you
have,
I
think
you
can't
indent
a
table
a
good
table.
You
know
you,
you
have
some
formatting
ascii
doctor
does
more
formatting
has
more
formatting
options.
If
you
want
to
exercise
them,
and
I
can
go
pro
and
con
I
mean
you
can
go
too
far
with
all
the
formatting.
D
Well,
issues
like
whether
whether
it
can
has
to
be
flushed
to
the
left
margin
or
it
can
be
centered
or
to
the
right.
You
know
I
think
in
marked
in
basic
markdown.
At
least
you
don't
have
any
choice.
You
can't
control
how
that
plays
out.
As
I
say,
not
a
huge
thing,
just
an
issue
in
general
markdown
is
considered
to
be
not
appropriate
for
longer
files
and
right
now
we
don't
have
longer
files,
but
I
can
anticipate
going
forward
that
we
may
have
some
longer
files.
D
Part
of
that
is
because
the
internal
cross
referencing,
you
know
with
a
long
file.
You
want
a
good
internal
table
of
contents
at
the
top.
So
and
to
me
I
don't
know,
maybe
I'm
insensitive
here.
I
don't
think
ascii
doctor
is
really
more
complicated
than
mark
down.
It's
just
the
people.
Now
people
know
mark
down
and
ascii
doctor,
but
they're
very,
very
similar.
They
are
not
radically
different.
It's
not
like
going
to
say
giroff
it's
much,
it's
the
same
principle
and
in
general
I
think
most
engineers.
When
they're
writing.
D
You
know
sort
of
take
a
doc
that
looks
sort
of
like
what
they
want
and
just
copy
that
formatting
and
turn
it
over
to
professional
writers
if
they
want
to
get
fancy
so,
but
but
but
my,
I
would
vote
to
get
away
from
markdown
and
use
ascii
doctor.
But
that's
what's
up.
What's
the
counter
argument,
what
are
the
other
than
not
having
to
convert
out
of
markdown?
What
are
the
advantages?
Docusaurus
do
other
things
that
ascii
doctor
does
not.
B
I
guess
that
I
guess
the
question
here
is
how
how
does
mdx
that
is,
the
extended
markdown
compare
with
the
ascii
talk
and
how
easy
slash
difficult.
It
is
to
use
one
over
other
and
for
which
user.
B
So
the
second
question
is
who
is
going
to
be
contributing
to
the
box
and
on
the
basis
of
that,
I
think
we
should
look
at
making
a
decision
because,
like
meg
said,
if
you
say
it
from
a
technical
writer's
perspective,
maybe
ask
the
doctor
something
that
offers
more
features
and
more
complete
set
of
features
so
to
say,
and
but
if
you
look
at
it
from
a
developer's
perspective,
that's
just
adding
one
extra
wall
to
contribution,
because
then
you
have
to
go
and
look
at
some
kind
of
cheat
sheet
for
ascii
doc.
A
Well,
basically,
ascii
doc
is
also
supported
by
github
web
interface.
So
you
can
edit,
you
can
preview,
you
can
open
a
reference
sheet
from
github,
but
I
think
that
in
any
case,
supporting
markdown
will
be
a
table.
Stick
requirement
for
us,
because
I
do
not
see
how
we
integrate
all
the
ecosystem
to
ask
a
doc
overnight
and
I
don't
see
how
we
could
get
all
the
maintenance
involved.
A
So
for
me,
even
if
you
have
ascii
doc,
let's
say
as
a
course
let's
say
for
new
tutorials
for
new
documentation,
many
integrations
etc
will
stay
as
marked
down
basically
like.
If
you
take
jenkins
example,
it's
basically
the
same
the
most
of
three
mds
for
plugins,
the
remaining
markdown,
because
it's
simple
condensed
documentation.
So
why
not
well.
A
B
What
happens
to
them
the
main
captain
ripple?
Do
we
also
keep
that
in
the.
B
B
Yeah
yeah
yeah
because
I
think
developers-
and
this
is
just
my
opinion-
I
would
be
more
comfortable-
writing
readme
vision,
which
sits
closer
to
the
code
in
markdown,
and
then
we
basically
use
ascii
talk
for
the
real
tutorials
for
the
new
users
and
all
of
that
which
developers
might
not
write
and
we
see
a
way
to
convert
the
markdown
into
ascii
talk
becomes.
D
Like
the
readmes
readmes
can
be
an
either
markdown
or
ascii
doctor
and
my
impression
in
jenkins.
I
think
we
have
quite
a
mix
of
them.
Don't
we
no.
A
No
so
yeah,
actually
as
a
developer,
I
prefer
ascii
doc
still
but
yeah
markdown
disadvantages,
of
course,
low
operator
entry
native
support
by
github.
A
So,
let's
see
I
expect
that
we
would
have
to
support
both
languages
in
am
right
in
case,
but
yeah
for
complex
documentation
like
tutorials
et
cetera.
I
would
rather
start
looking
in
a
ski
dog.
D
Another
consideration
in
here
I
honestly
do
not
know
if
markdown
holds
up,
but
the
other
thing
that
I
am
sort
of
seeing
is
that
other
products
that
are
you
know
not
not
part
of
captain
might
include
some
captain
and
might
want
to
include,
might
want
to
be
able
to
pull
in
sections
of
kept
in
documentation,
for
instance,
the
reference
pages
about
the
files,
although
they
might
not
do
the
same
tutorial
information,
because
you
would
you
know
on
that
product
on
prometheus
or
dietrich
or
whatever
you
would
use
it
differently.
D
I
think
ascii
doctor
could
support
that
easily
and
be
it
would
even
be
if
they
wanted.
You
know
they
could
use
their
own
product
name
or
something
it
could
be
set
up.
That
way.
If
we
want
to
and
part
of
me
shudders
at
the
possibility
of
having
to
do
that,
but
I
think
we're
going
to
get
called
for
that
now.
How
well
would
docusaurus
support
somebody
pulling
in
some
of
the
kept
in
documentation
into
their
own
product,
documentation.
D
They
don't
want
to
do
that
once
they
want
to
do
that
constantly
so
that
when
we
upgrade
when
we
update
those
stocks,
they
get
the
updated
version.
That's
the
issue!
It's
it's!
Not
it's
a
question
of
constantly
importing
our
docs
and
not
stealing
them
for
one
time
and
then
taking
off
and
maintaining
them
on
their
own
and.
C
But
to
your
question:
if
you,
if
you
just
reference
the
documentation
from
the
current
source,
which
would
be
the
captain,
so
for
instance,
then
it
would
always
render
the
latest
information
coming
from
that.
If
you
fetch
the
data
and
host
it
yourself,
then
it's
a
different
story
right.
So
if
you,
if
someone
just
want
to
link
it
to
our
doc,
they
would
just
reference
it
and
then
it
it
will
be
always
the
latest.
D
I
am
hearing
rumblings
from
places
that
they
may
want
to
be
able
good,
there's
an
argument
and
again
I'm
I'm
not
real
sure
I
buy
it,
but
there
there
are
a
sizable
number
of
people
who
say
that
if
I
pay
for
an
enterprise
product,
I
want
all
the
documentation
that
I
need
to
be
in
their
set
that
I
do
not
want
to
be
sent
linking
over
to
the
open
source
documentation
all
the
time.
I'm
I'm
not
really
convinced
of
that.
There's
an
argument,
but
but
there
are
a
sizable
number
of
people
who
make
that
argument.
D
So
yeah,
that's
yeah,
I'm
I'm
kind
of
with
you
in
my
heart.
It's
like
the
our
docs.
Are
there
if
you
want
to
reference
them.
E
D
But
for
these
people
who
say
they
need
to
import
them,
it's
worth
considering
how
well
whatever
and
support
that,
and
it's
got
it's
not
just
the
markdown
versus
ascii
doctor,
it's
what
the
engine
does
for
them.
A
Okay,
so
yeah,
we
are
going
seriously
over
time.
So
for
me,
the
takeaway
that
docusaros
is
more
than
viable
and
that
we
need
to
continue
prototyping,
maybe
as
a
part
of
community,
bonding
first
implementation
phase,
and
they
will
make
a
final
decision
what
we
want
called,
but
for
now
for
me,
because
of
this
is
a
viable
option.
We
just
need
to
bring
up
questions
and
see
how
we
answer
them
and
I
believe
that
antarctica
will
have
to
answer
the
same
questions.
D
Yes-
and
I
will
volunteer
at
some
point-
maybe
not
tonight,
because
I've
got
another
project,
but
if
we
would
like
to
take
a
small
sample
of
our
stuff
and
run
it
through
pandoc
and
then
I
would
volunteer
to
go
through
and
do
the
manual
cleanup
and
from
that
and
time
it
to
see
you
know
for
this
size
file.
It
took
me
this
long
to
clean
it
up
if
chicken,
if
to
use
pando,
to
convert
from
markdown
to
ascii
doctor,
because
it
sounds
like
that's
one
of
the
considerations
right.
A
D
C
D
And
but
my
I've
I've,
actually
you
know
I've
been
through
a
couple
of
similar
ones.
I
didn't
find
it
onerous
and
mostly
stocks.
I
mean
I
spent
more
time
because
I
had
to
read
everything
I
couldn't
ignore
all
the
grammatical
and
syntactical
and
spelling
errors
that
you
ran
along
the
way
I
usually
spent
more
time
cleaning
those
up,
but
but
it's
worth
the
test
that
you
know
we
should
have
data
here
to
make
this
part
of
this
decision
as
to
whether
the
conversion
to
ascii
doctor
is
onerous.
D
A
D
To
google
doc
in
the
next
couple
of
hours,
with
a
rough
suggestion
of
potential
projects
for
google
summer
docs,
please
vote
fast.