►
From YouTube: Keptn Community & Developer Meeting - April 8th, 2021
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
Join our Keptn community newsletter: https://keptn.sh/community/newsletter/
A
Okay,
recording
is
on
yep,
this
means
hi
and
welcome
everyone
to
the
next
episode
of
the
captain
dev
meeting.
Like
always,
this
is
a
captain's,
a
cncf
project,
and
this
means
that
we
follow
their
code
of
contact,
and
this
means
that
also
that
we
talk
nice
to
each
other
and
be
friendly.
A
We
will
see
today
and
we
should
go
to
them
sooner
than
later,
but
before
talking
about
the
issues
and
features
that
have
been
implemented,
I
just
want
to
mention
that
the
two
action
items
on
setting
up
the
spell
checker
in
the
captain,
github.io
repo,
which
contains
the
documentation
of
captain,
is
in
progress,
and
the
same
is
true
for
the
tutorials.
There
are
two
pull
requests
open
to
add
the
spell
checker
to
the
repo,
as
it
makes
sense
to
have
it
there.
A
Since
there
is
there's
quite
a
lot
of
content
in
written
documents
and
doing
their
spell
check
is
definitely
worth
getting
it
getting.
It
done
right
and,
as
I
know
also
josh
is
helping
out
to
get
the
pull
request
merged,
since
there
are
a
couple
of
questions
open
all
right.
Our
content
and
community
manager.
Jurgen
is
not
today
not
here
today,
and
he
told
me
that
there
were
no
blog
posts
released
this
week
and
no
tutorials
added.
A
I
will
go
first
because
in
this
print
I
sat
together
with
airmen
claus
and
the
path
to
talk
about
their
new
way
of
implementing
the
service
screen,
because
let
me
just
open
the
server
screen
as
it
is
right
now
right
now
you
can
go
to
the
service
screen.
A
You
have
the
chance
to
select
the
service
you're
interested
in,
and
then
you
find
we
call
them
the
root
events
that
kick
off
a
sequence
and
you
will
find
them
here,
stacked
the
newest
one
on
the
top,
and
when
you
click
on
the
root
event,
then
you
will
see
how
this
particular
delivery
was
executed.
A
In
this
case,
it
went
from
a
dev
through
a
staging
production
and,
finally
to
a
pro
customer,
a
environment
and
there
I
have
currently
an
approval
open.
This
is
what
you
know,
but
we
were
thinking
of
changing
this
view
and
also
to
bring
more
focus
on
which
deployments
are
released
and
how
is
actually
my
service
behaving
or
in
which
healthy
state
is
it
currently
and
therefore
we
worked
on
this
issue.
A
A
A
A
Then
you
also
get
the
the
score
of
the
evaluation
in
this
bubble
and
in
case
the
deployment
is
currently
running
in
this
stage,
we
also
show
the
icon,
which
we
use,
to
link
the
deployment
url
so
that
you
can
directly
open
up
the
the
endpoint
of
this
deployment
and
when
you
click
on
one
particular
stage,
then
you
will
get
the
evaluation
in
this
stage.
A
As
you
are
used
to
to
understand
about
more
about
the
quality
and
whether
it's
decreasing
or
increasing
and
yeah,
you
should
then
fix
problems
or
everything
is
on
the
safe
side.
A
As
you
can
see
here
on
the
left,
we
also
reduce
this
list
to
all
deployments
that
are
currently
running
and
not
the
entire
history.
We
just
want
to
focus
on
what
you
get
right
now
and
not
what
has
been
executed
all
right.
This
is
what
we
came
up
with.
I
also
posted
this
captain
huntsman
proposal
today
in
the
slack
channel,
when
you
have
comments,
feedback
or
additional
thoughts.
A
Please
tell
us
your
ideas
so
that
we
can
then
incorporate
those
into
working
on
when
we're
working
on
the
implementation,
and
I
also
want
to
use
this
stage
and
ask
for
feedback
right
now.
What
do
you
use
is
someone
has
someone
on
a
an
idea?
We
should.
A
All
right,
that's
currently
not
the
case,
then,
as
I
mentioned,
feel
free
to
post
your
thoughts
in
the
slack
channel,
so
that
you
can
also
contribute
and
driving
this
screen
to
the
next
level.
A
All
right
yeah:
this
is
what
I
wanted
to
present
today.
This
means
I
will
now
hand
over
to
florian.
B
Okay
in
this
sprint,
I
could
had
enough
opportunity
to
practice
my
helm
chart
building
skills,
so
quite
helm
heavy
the
sprint
for
me.
So
what
was
the
first
issue?
The
first
one
was
to
delete
the
helm
service
and
jamie
the
service
from
our
continuous
delivery,
helm
chat.
B
Is
never
a
good
thing,
so
in
this
issue
the
main
task
was
to
remove
those
two
services
from
the
captain
core
installer
chart
and
what
was
also
necessary
because
of
that
is
to
adapt
the
install
command
of
the
captain
cli,
because
now
it
checks
whether
you
have
selected
the
continuous
delivery
use
case
during
the
installation
and
if
yes,
it.
First
of
all,
it
installs
the
cabin
core
installer
charts.
B
As
you
can
tell,
the
code
for
the
install
command
has
gotten
a
little
bit
more
complex
and
also
for
the
upgrade
command,
of
course,
and
therefore
I
also
took
the
opportunity
to
do
some
refactoring
of
the
install
command,
because
previously
it
was
quite
hard
to
unit
test,
because
the
component
that
downloads
the
helm,
charts
and
applies
them
was
initialized
within
the
function
which
was
annoying
to
test
and
therefore
I
have
now
installed
command
handler,
which
has
the
opportunity
to
inject
the
basically
three
different
interfaces
or
implementation
of
interfaces,
one
that
is
responsible
for
doing
the
helm
operations
during
the
installation.
B
Then
the
other
checks,
whether
the
namespace
for
the
captain
installation
exists
and,
if
not
created,
and
then
one
for
the
user
input,
because
we
also
have
an
interactive
component
in
the
install
command
and
by
injecting
those
fields
into
the
install
command
tender.
It
was
then
easier
to
do
some
unit.
C
B
And
there
I've
added
several
cases
so,
for
example,
the
first
one
is
install
command
for
the
continuous
delivery
use
case,
and
in
that
case,
basically,
I
check
whether
the
download
function
for
the
helm
and
the
jmeter
service
charts
have
been
invoked
and
also
if
they
have
been
applied
by
the
installer,
using
a
chart
function
and
also
for
the
other
case,
if
only
the
control.
C
B
C
B
Missing
or
left.
D
Yeah,
can
we
have
a
quick
look
which
configuration
map
it.
B
E
B
B
And
then,
if
you
wanted
to
deploy
that
service
using
scaffold
with
the
helm
chart
in
of
that
service,
he
ran
into
a
conflict
where
I
told
you
that
you
tried
to
deploy
a
resource
that
is
already
maintained
by
the
captain
release,
and
in
that
case
we
don't
have
that
problem
anymore,
because
now
those
services
are
never
a
part
of
the
captain
helm
release
anymore.
So
we
shouldn't
have
any
conflicts
here,
anymore.
B
D
B
When
doing
the
upgrade
command,
the
operator
will
now
check
first,
if
those
two
services
have
been
installed
previously
and
then
does
the
upgrade,
which
in
turn
leads
to
them
being
deleted,
because
they
are
not
part
of
the
core
captain
release
anymore.
But
since
it
checked
previously,
if
they've
been
installed,
it
will
afterwards
apply
their
helm,
charts
to
make
sure
they
still
are
present
in
the
cluster.
After
the
upgrade.
D
B
Thank
you
all
right.
Then.
If
there
are
no
further
questions
about
that
issue,
I
will
continue
with
the
next
one,
so
that
was
building
a
helm
chart
for
the
dynatrace
smi
service.
So
let's
have
a
look
at
the
issue:
yeah,
basically
pretty
straightforward.
B
So
up
until
now,
we
deployed
the
dynatraces
I
service
using
a
simple
kubernetes
manifest
and
that
has
now
been
replaced
with
a
help
chart
which
will
also
make
it
easier
once
the
core
supports
the
dynatraces
that
I
service
to
be
run
as
a
remote
execution
plane
service
to
to
configure
the
values
required
for
setting
that
up
by
the
helm,
chart
values.
B
All
right,
so
the
kubernetes
manifests
have
been
replaced
and
also
what
was
necessary
here
as
well
is
to
create
a
github
action
that
creates
a
release,
draft
and
uploads
the
helm
chart
as
an
artifact
for
that
release.
So
we
don't
have
to
do
that
manually,
and
this
can
be
triggered
here
under
the
actions
and
then
select
run
workflow
select
with
which
branch
you
want
to
base
it
on
and
then
afterwards
the
release
draft
will
will
be
present
and
with
the
chart
applied
or
added
as
an
artifact.
D
Can
we
trigger
this
now?
I
would
like
be
eager
to
see
it
yeah
sure,
let's
give
it
the
world
and
in
the
meantime
I
I
can
make
one
note
so
that
now
also
requires
that
the
captain,
customer
or
cabin
user
has
helm
locally
installed.
Otherwise
he
or
she
cannot
instantly
then
address
sli
service.
D
B
Exactly
yeah,
so
the
readme
has
also
been
updated
accordingly
and
I've
created
a
pull
request
for
the
tutorials,
where
I've
adapted
those
changes
as
well.
So
this
one
is
our
currently
in
draft
mode
until
we
have
actually
released
a
version
of
that
service
where
we
use
that
helm
chart
all
right
now,
our
release
draft
action
has
been
executed
successfully
and
now,
with
a
little
bit
of
luck.
Yeah
here
we
have
the
release
draft
with
the
helm,
chart
asset.
B
Okay,
that
was
that
and
yeah.
The
next
issue
is
quite
similar.
This
is
a
thumb
chart
for
the
dynatrace
service,
as
apparently
we
have
those
two
different
services
which
are
going
to
be
merged
at
some
point
in
time,
but
currently
they're
separated
so
apparently
yeah.
So
currently
that
one
is
on
the
review.
B
But
what
is
nice
in
that
case
is
that
previously
we
also
had
those
plain
kubernetes
manifests,
but
we
had
basically
two
different
sets
of
configurations
that
were
used
for
this
service,
the
one
that
had
all
the
configuration
features
enabled
so
the
features
for
setting
up
the
problem,
notifications,
the
dashboards,
the
metric
events
etc,
and
the
other
one
with
those
features
disabled
and
we
had
to
maintain
those
two
very
similar
kubernetes
manifests,
and
now
this
configuration
can
also
be
steered
using
the
helm,
values
that
are
provided
in
the
helm
upgrade
command.
B
So
this
one
is
about
the
go
utils
so
here
christian
stumbled
across
a
quite
outdated
function,
with
the
name
get
captain
resource
which
basically
downloaded
the
resource
specified
in
the
input
parameter
from
the
configuration
service,
but
also
stored
that
resource
in
a
file
in
the
local
file
system
and
yeah,
and
some
other
file
io
stuff,
such
as
deleting
directories
and
that's
yeah,
not
really
the
way
to
go,
and
actually
it
was
that
part
of
the
function
wasn't
used
anywhere
and
therefore
we
have
removed
that
I
o
part
of
the
function
and
now
simply
return
the
resource
content
of
the
resource.
B
If
it
was
retrieved
successfully
all
right,
then
I
think
I'm
through
with
all
my
issues.
Are
there
any
questions
about
that
last
issue.
G
Thank
you
very
much.
I
plan
to
present
one
pull
request
today
regarding
captain's
bridge.
It's
about
a
better
sequence
visualization
when
having
more
than
one
sequence
in
a
stage,
and
actually
this
also
improves
the
sequence
visualization
when
having
only
one
sequence
in
a
stage
you
will
see
in
a
minute.
G
So
let's
have
a
look
at
the
issue.
What
the
problem
he
was
is
in
the
case
that
yeah
you
had
multiple
sequences
in
in
one
stage,
configured
yeah.
It
was
just
a
list
of
tiles
and
you
couldn't
tell
which
task
was
no
part
of
the
first
sequence
or
of
the
second
sequence
and
so
on,
and
you
had
also
in
between
tiles,
about
with
meta
data,
about
the
sequence
itself,
but
it
was,
for
example,
not
possible
to
get
the
payload
of
the
first
triggered
event
of
the
sequence
itself
in
this
old
view.
G
Now,
with
the
improvement
you
see
for
each
sequence
tile
in
this
sequences
screen,
and
you
can
expand
that
one
and
then
you
see
all
the
tasks
that
have
been
executed
in
context
of
that
sequence
and,
of
course,
it's
a
lot
easier
to
show
it
in
a
live
demo.
So
I
will
show
it
on
a
demo
cluster
here,
where
we
have
yeah
a
configuration
in
the
production
stage.
G
So
in
the
broad
stage,
with
four
sequences-
and
here
you
can
see-
we
have
delivery
sequence
and
then
we
have
three
canary
faces
which
are
implemented
as
separate
sequences
and
they
all
have
a
release
test
evaluation,
get
the
sli
and
then
an
approval
task,
and,
as
you
can
see
null
yeah,
you
can
have
a
look
at
the
payload
of
the
sequence
triggered
event
itself
and
of
course
you
also
have
the
sequence
finished.
G
So
the
finished
event
of
that
sequence
and,
of
course,
also
of
the
all
the
tasks
in
between,
for
example,
the
release
task
is
actually,
in
this
case
also
handled
by
two
services.
So
you
have
to
start
it
on
the
finished
events
of
the
services
here
with
all
the
details-
and
you
have
one
nice
improvement
we
have
we
see.
Also
here-
is
that
the
response,
so
the
message
here
is
now
also
rendered
not
only
as
a
text
but
also
in
the
format
that
we
get
it.
G
This
was
actually
implemented
by
claus,
but
yeah.
The
main
focus
that
the
main
thing
that
I
wanted
to
show
here
is
that
you
see
now
the
sequences,
especially
in
case
when
you
have
multiple
sequences
in
one
stage.
I
will
just
show
also
in
stitching
the
case
here.
We
have
just
one
sequence:
the
delivery
sequence
itself,
but
still
you
see
that
that's
the
delivery
sequence.
G
Yeah.
Are
there
any.
F
A
Back
when
I
take
a
look
at
this
particular
sequence
now,
then
I'm
wondering
why
is
there
an
approval
triggered
compared
to
the
others
that
just
have
the
task
name.
G
A
Not
a
big
deal,
but
it
kind
of
jumps
into
into
your
eyes
that
all
the
things.
G
G
Yeah
cool,
that's
actually
all
I
wanted
to
present
today
and
I'm
heading
over
to
bend.
E
But
we
took
a
deeper
look
into
the
issue
and
the
problem
was
then
in
the
end,
in
the
distributor,
which
is
also
running
in
this
situation,
remotely
on
the
side
by
side
with
the
with
the
helm
service,
and
the
problem
was
just
that
in
this
set
setup
when
running
the
helm,
the
distributor
remotely
it
was
sending
out
or
forwarding
the
events
sequentially
waiting
waiting
for
the
service,
which
is
processing
the
event
to
finish,
and
then
it
will
forward
the
next
event.
So
that
was
changed
in
this.
In
this
pull
request
here.
E
E
E
So,
within
our
continuous
integration,
our
big
pipeline
we
often
or
we
will
have
the
need
to
trigger
sequences
in
the
kept
installation.
Of
course,
you
can
do
it
as
this
in
a
variety
of
ways.
One
proposal
here
was
to
do
it
via
a
separate
github
action
which
can
be
extended
in
functional
functionality
over
time.
E
For
now,
this
github
action
should
only
be
capable
of
sending
arbitrary,
arbitrary
cloud
events
to
a
captain
installation,
and
that
was
what
I
did.
We
can
take
a
look
at
the
repo.
I
hope
I
find
it
whoops.
E
Come
on
so
yeah,
it's
that
one,
the
github
action
is
living
in
a
in.
C
E
Repository
captain
github
actions
and
event,
we
also
have
another
github
action,
so
the
convention
convention
is
a
captain,
github
action
and
what
the
action
is
actually
responsible
for
here
we
are
sending
events,
so
this
is
the
name
of
the
github
repository.
It's
quite
simple.
The
github
action
takes
three
parameters:
the
captain
api
url,
for
example,
like
this,
so
that's
the
endpoint
of
the
event.
E
So
that's
the
url
of
the
event
endpoint.
It
takes
the
captain
api
token
and,
of
course,
the
event
you
want
to
send.
That's
totally
totally
arbitrary.
You
can
send
any
event
you
want,
so
you
are
not
restricted
to
to
what
you
can
send.
Actually
here's
an
example
how
to
use
it.
Of
course,
this
is
up
to
the
user,
how
you
want
to
trigger
this
github
action,
here's
just
an
example
which
works
on.
Whenever
a
push
happened,
then
we
want
to
send
an
event.
E
Which
looks
you
in
a
configuration
like
here
this
step?
We
want
to
send
the
van
event
using
this
action
here,
because
the
github
actions
and
event
action-
and
we
feed
it
with
these
parameters
which,
in
this
this
in
this
case,
come
from
github
secrets,
but
again
totally
up
to
the
user.
How
you
do
it.
E
So
we
have
an
api,
url
and
token
configured
in
the
git
repository
and
last
but
not
least,
of
course,
the
event.
So
all
of
these
three
are
mandatory
input
parameters,
and
here
you
just
put
your
event
as
usual
in
json
format
that
you
want
to
send
to
the
captain
installation.
E
Yeah,
that's
it!
I
don't
know
how
this
github
action
will
grow
over
time.
There
might
become
more
features
for
now,
it's
quite
flexible.
What
you
can
do
you
just
can
send
any
kind
of
any
kind
of
events
to
a
captain
installation
which
we
will
be
in
the
next
step,
using
our
pipeline.
E
The
logic
of
this
merging
is
actually
implemented
in
hand
service,
which
was
done
by
andreas.
Thank
you
and
what
I
did
is
I'm
just.
I
was
just
doing
the
worker
the
work
around
that,
for
example,
changes
in
the
cli,
because
the
cli
should
also
supports
this
and
so
on.
We
can
take
a
look
at
that,
so
what
what
what's
actually
possible
is
now
is
now
you
can
use
this
command
here.
Captain
trigger
delivery
and
feed
it
with
a
values
flag
where
you
can
say.
Okay,
I
want
to.
E
Change
or
add
a
field
in
the
configuration
change
section
of
the
cloud
event,
you
give
it
a
kind
of
a
json
dot
notation,
so
you
want
to
have
the
field
shipyard
controller
image
tag
to
have
the
value
082
blah
blah
blah.
This
will
result
in
the
send
cloud
event
like
this.
It
will
just
be
translated
to
jason
and
later
on
merged
by
the
helm
service
when
it's
doing
its
stuff.
A
E
E
Maybe
I
forgot
to
mention
why
this
was
not
possible
before
before
it
was
the
case.
If
you
do
something
like
shipyard,
controller
dot
or
just
chip,
yet
controller
and
some
value,
then
everything
beneath
the
shipyard
controller
level
was
overwritten.
So
you
only
have
had
this
value
now
we
have
a
merge
mechanism
in
place
that
actually
the
values
are
merged
to
the
already
existing
stuff,
which
is
which
are
probably
in
the
already
existing
json
things.
D
E
D
E
E
So
that's
ongoing
work
now,
but
we
now
have
a
common
package
in
goyu
tills
which,
where
you
should
actually
put
all
your
code,
which
might
get
reused
all
over
the
places.
For
example,
if
we
take
a
look
at
the
file,
you
deals,
which
is
now
new,
there's
a
function
for
reading
a
file
for
reading
a
file
string
for
checking
if
a
file
exists,
expanding
it
till
the
user,
home
directory
and
so
on.
E
E
I
don't
know
downloading
a
file
using
a
file
downloader
checking
if
a
url
is
valid
and
string,
your
deals
and
so
on.
So
if
you
see
when
implementing
a
new
issue
when
solving
a
new
issue,
if
you
see
kind
of
duplications
which
might
fit
to
this
utils
package,
here
just
add
it
here,
and
I
think
we
can
get
rid
of
a
lot
of
duplications
here
and
there
if
we
are
following
this.
E
Okay,
then
who's
after
me,
close
okay,
so.
C
Screen,
okay,
so
hello,
I'm
basically
at
showing
a
few
things
after
in
the
bridge.
The
first
thing
I
will
show
is
the
slide
breakdown
there.
We
had
an
overlay
to
show
the
target
value
if
the
criteria
failed.
This
was
lost
in
080
and
now
we
introduce
it
again
so
yeah.
When
you
have
an
evaluation
and
the
criteria
fails.
Now
you
can
hover
over
the
fair
criteria
and
see
the
target
value
and
yeah
why
it
failed
basically
and
yeah.
This
was
the
first
rather
small
thing.
I've
implemented.
C
Then,
if
there
are
none,
then
I
will
hand
over
to
the
next
one
to
load
all
the
sequences.
C
So
basically,
we
said
that
we
should
be
able
to
load
more
sequences,
older
ones,
and
this
was
not
possible
before
so
now
we
can
just
simply
click
to
show
all
the
sequences
and
the
next
10
sequences
will
be
loaded
at
first
25
are
loaded
and
then,
with
loading
sequences,
you
can
load
10,
additional
ones
and,
as
you
can
see,
also
the
filter
for
the
sequences
is
refreshing
if
you
load
sequences
that
aren't
there
before
so,
like
it's
create
like
create
and
delete.
C
Additionally,
even
reloading
also
works.
If
you
select.
C
Something
that's
far
away
from
25
to
a
limit.
You
can
also
refresh-
and
this
sequence
is
also
loaded
into
a
bridge
just
a
moment.
Okay,
here
we
are
and
all
the
sequences
that
are
before
this
sequence,
so
yeah
everything
before
and
after
the
25
initially
loaded
are
also
fetched
and
yeah.
This
is
basically
a
feature,
and
if
there
are
none
sequences
left
also,
this
show
euler
sequences
element
disappears.
C
And
yes,
that's
that
thing
and
the
last.
A
One
is
yeah,
can
I
jump
in
when
you
go
to
the
sequence
screen
and
you
click
fuse
sequence
from
one
very
old
one.
C
C
C
The
sources
screen
is
not
adjusted
now
to
that,
because
it's
yeah
it
will
change
now
in
the
future.
That's
why
in
services
it
does
not
proper
work.
I
guess
okay,
okay,
but
you
can
see
just
the
last
sequence
and
with
that
much
also
when
I
reload
it
or
with
the
deep
link
itself,
it's
loading,
the
selected
sequence.
G
C
E
Can
you
go
back,
go
back
to
the
bridge
one
moment?
Yes,
I
have
a
rather
general
question,
which
is
not
so
important,
but
what's
going
on
with
the
colors
here,
because
where,
where
does
this
cyan
color
comes
from
it's,
this
doesn't
fit
so
nice
with
the
bluish
things.
E
The
thing
is
this
because
it's
reminding
me
of
the
dynatrace
ui
look
and
feel:
is
it
because.
A
G
Components
from
the
barista
components,
library,
and
actually
we
haven't
considered
changing
the
colors
there.
The
only
color
that
we
introduced
is
in
the
navigation
bar
on
the
top,
where
you
have
captain
and
the
project
selector
and
there
we
have
this
blue
color,
which
represents
represents
the
blue,
the
captain
blue,
so
our
color
that
we
use
for
the
captain
project.
G
Yeah
when
having
it
in
the
buttons-
and
so
it's
not
that
eye-catching
but
in
case
of
the
notification
bar
yeah,
it's
too
obvious
and
maybe
we
consider
changing
the
color
there.
C
Yeah,
it's
because
this
will
also
be
adjusted
because
it's
for
captain
for
captain
core
and
for
the
bridge
this.
These
are
two
separate
things:
okay,.
C
E
These
buttons
here
in
or
these
components
right
at
the
right
of,
for
example,
delivery
direct.
The
first
thing
here,
yeah
this
one,
those
remind
remind
me
a
little
bit
on
those
buttons
on
the
ios
interface,
where
you
can
swipe
to
the
left
and
activate
it
or
something
like
that.
E
C
It's
just
a
visualization
of
the
text
for
specific
messages,
and
this
was
just
a
simple
change
to
from
a
paragraph
tag
to
a
pre-formatted
text
text
and
that's
it
yeah.
I
don't
really
have.
H
C
G
I
have
just
to
add
one
thing
here
that
popped
up.
Actually
elizabeth
saw
it
in
during
my
presentation.
I
think
we
have
a
encoding
issue
there
and
also,
if
you
have
a
look
at
the
screenshot.
H
C
G
With
the
font
or
something
or
it's,
the
font
could
be
also
yeah.
We
could
check
on
that.
I
will
create
a
follow-up
issue.
Okay,
it'd
be
a
rather
small
thing.
A
All
right,
then,
let
me
finally
share
the
screen,
but
there
are
actually
no
items
left,
meaning.
A
Listening
also
no
question
came
up,
then
I
think
we
yeah
we
can
close
it
for
today,
really
cool
which
progress
had
been
made,
yeah
with
all
the
features
and
enhancements
in
the
last
weeks.
A
Really
great
progress,
awesome.
Okay,
then,
let's
close
it
for
the
day,
thanks
for
joining
in
see
you
next
time.
At
the
same
time,
and
but
next
week
we
invite
the
community
to
join
in
and
also
to
ask
questions
and
to
tell
us
or
to
show
us
their
pull,
requests
and
features.
They
are
working
on
then
a
week
a
week,
then
after
we
will
again
see
which
features
have
been
implemented
from
the
core
team.