►
From YouTube: Keptn Developer Meeting - April 9th, 2020
Description
We are talking about https://github.com/keptn-sandbox/keptn-report
Learn more: https://keptn.sh
A
I
think
you
can
see
now
the
github
repo
from
my
captain
report,
utility
and
so
I
created
or
when
we
are
running
captain
evaluations
in
CI
CD
pipeline
and
the
oil
away.
Evaluation
is
part
of
your
acceptance
criteria
of
your
user
story.
Then
you
want
to
save
yes,
the
results
as
yeah
like
PDF,
or
something
like
this.
A
A
Do
me
a
second
go
back
and
it's
already
in
the
captain
sandbox,
so
you
can
can
see
it
here.
You
can
use
it
I
already
compiled
one
release
for
it
and
yeah.
What
is
it's
doing?
As
I
said,
you
can
just
directly
use
your
you
curl
output,
when
you're
asked
the
captain
API
for
the
evaluation
done
event
and
you're
getting
your
result
back,
you
can
pipe
it
directly.
The
captain
report
binary
defining
an
output
and
we
have
it
will
create
his
chart
with
my
project
stage.
B
A
It's
everything
was
in
the
cloud
event
within
the
the
data
which
the
Kepner
API
is
giving
back.
When
it's
saying
here,
the
emulation
is
done
so
I
have
here.
My
indicator
results
like
if
the
overall
relation
was
passed
and
I
feel
my
acceptance
criteria
and
then
I
have
as
well
all
the
previous
evaluations
simulation
history.
So
I
can
use
this
data
points
to
create
my
graph,
so
I
can
see
over
the
time.
How
was
my
horse
my
service,
performing
and
yeah
added
tonight
to
my
chart
here,
which
is.
C
C
A
C
C
C
C
Late
yeah,
because
this
is
this-
is
a
really
it's
really
great-
to
see
that
this
is
kind
of
already
possible,
because
we
have
received
a
lot
of
people
err
King
about
how
can
we
create
visualization
of
the
captain
results
in
other
tools
like
Jenkins,
where
they
want
to
have
the
heat
map
visualization?
Something
like
this.
So
if
the
API
already
delivers
that
data,
then
that's
great,
the
only
as
I
said,
I
I
think
we
just
need
to
figure
out
if
they
need
it.
C
A
It
could
be,
of
course
it
could
be
a
little
bit.
Let's
say
you
have
some
service
where
you
have
a
lot
of
Revelation
detailed
than
the
response
Chasen
or
the
response
cloud
even
could
be
a
little
bit
getting
huge
over
the
time.
So
perhaps
this
would
be
yeah.
That's
in
this
case.
I
only
have
full,
let's
say,
26
a
violation,
history
data
points,
but
when
you're
having
thousands
then
I
guess
it
will
be
a
little
bit.
Yeah.
A
Too
big
the
response,
and
if
you
have
there,
the
ability
to
say
okay
I
only
want
to
take
a
look
in
my
last
10
in
relation
details,
then
or
revelation
history.
This
would
be
beneficial
right
and
I
have
to
as
well.
I
have
to
give
a
big
shout
out
to
your
honor's,
because
I
have
to
say:
I'm,
not
so
familiar
with
go
and
I'm,
not
a
developer
as
well,
but
he
was
always
kind
full
to
to
answer
my
stupid
beginners
questions
so
welcome.
D
B
A
A
The
library
the
most
people
were
using
but
I,
don't
know.
Perhaps
there
is
some
better
charting
library
or
so,
but
this
was
for
me
at
least
the
easiest
way
to
get
these
up
and
running,
and
here
are
some
examples
of
the
chart.
So
it
isn't
I
have
to
say
it's,
it's
not
so
beautiful
my
report,
but
it's
working
I've.
All
the
information
that
I
need.
I
have
a
little
chart.
You
know
for
management.
A
Well,
a
child
is
always
good
and
yes,
so
I'm
using
this
charting
library
from
I
cannot
pronounce
the
name,
sorry
and
the
go
PDF
library
and
yet
then
I
have
my
structure
of
here
which
yeah
it's.
For
me.
It
was
a
really
huge
learning
curve
to
get
all
the
yeah
stuff
up
and
running
and
writing
golang
and
so
I'm
used
the
this
little
utility
here
to
get
my
structure
up
and
running
so
I
just
pasted
it
or
copied
my
my
choice
and
data
over.
A
So
that's
the
reason
why
I've
written
this
and
go,
and
after
yeah
after
the
last
developer
meeting
here
from
the
captain
community,
where
Kristin
was
showing
how
to
write,
go
and
captain
services,
it
was,
and
I
have
a
lot
of
time
right
now,
thanks
to
the
pandemic,
I
was
you
have
thinking
by
myself?
Oh
let's,
let's
try
go
that's
the
only
reason
behind.
B
I'm,
actually
thinking
if
this
is
something
we
can
integrate
in
captain's
bridge,
maybe
not
as
a
binary,
but
maybe
the
PDF
generation,
when
you
maybe
like
the
future
of
captain's
bridge,
could
look
completely
different.
Obviously,
but
when
you
eventually
click
generate
me
a
chart
for
my
service
and
then
you
just
get
the
PDF
download
it
to
your
computer.
It
could
be
something
that
we
can
integrate.
B
A
I
already
had
a
discussion
with
andreas
about
it,
but
I
then
said
to
him:
okay,
just
focus
to
something
different,
something
more
useful
for
for
captain
and
that's
why
I've
made
it
by
my
own.
So
but
in
fact,
but
I
would
more
preferred
to
have
these
if
it's
one
time
implemented
into
captain
directly
into
core
I,
would
more
like
it
to
have
food
by
an
API
call.
B
B
A
D
A
So
we
have
the
ability-
and
this
was
also
something
I
want
to
achieve
or
want
to
achieve.
I
was
playing
around
with
with
swisco
and
I
like
these
piping
stuff
in
under
limits,
and
that's
what's
the
reason
why
I'm
adding
here
also
the
ability
to
pipe
it
over
to
your
binary,
not
only
as
command-line
argument,
so
we
can
also
say
hate
this
Murchison
file.
A
B
Actually,
we
also
got
another
suggestion
from
the
community
that
you
can
have
a
dedicated
URL
if
I
get
it
correct
to
get
in
dedicated,
URL
or
actually
I
can
I
can
promote
the
folks
that
was
asking
these
questions
so
raw.
If
you
want,
you
can
actually
now
ask
the
question
yourself
I
just
on
you
to
do
sure.
E
You
could
also
maybe
have
a
page
that
renders
the
whole
report
in
a
nice
report
that
could
be
a
URL
and
then
that
same
URL.
So
if
you
were
to
use
a
Jenkins
pipeline,
the
Jenkins
pipeline
could
have
the
deep
link
to
the
report.
You
know
I
just
I,
just
don't
know
if
making
a
PDF
file
is
easy
to
try
to
move
around
different
tooling,
where
a
URL
might
be
easier.
So.
A
E
A
E
E
E
A
So
so
you
can
see
here,
let's
say
I'm
doing
some
stuff
like
adding
the
the
captain's
logo,
as
well
as
space
for
46,
encoded
string
and
then
getting
the
data
out
of
the
the
events.
This
just
east
couple
lines,
so
I'm
looping
through
simulation
history.
If
I
have
any
indicator
results,
then
I'm
appending
my
my
time,
ballast,
my
variable
or
to
my
array
here
and
then
I'm
looping
also
indicator
results
and
appending
them
to
my
chart.
A
A
A
If
inhalation
was
passed,
it
will
be
displayed
in
green
and
it's
not
past
it's
red
and
then
I'm
looking
over,
say
the
indicator
results
to
to
also
print
out
the
test
criteria
and
then,
in
the
end,
I'm
adding
the
captain
logo
I'm,
adding
charge
to
my
PDF
and
then
saves
a
PDF.
That's
that's
it
and
yeah
III
know
I.
Perhaps
I
can
or
I
could
move
some
things
out
to
other
functions,
and
so,
but
it's
working
I.
B
E
B
B
That's
pretty
cool!
Thank
you
so
much
preaching
for
for
presenting
this
I
just
want
to
highlight
again
that
these
kind
of
for
community
contributions
they
live
on,
github.com
slash,
captain
sandbox,
so
we
have
created
a
dedicated
repository
for
organization
where
things
like
Christians
in
not
integration
but
like
tooling.
E
B
Is
living?
We
have
other
services
that
integrate
with
and
living
in,
the
captain
sandbox.
So
it's
kind
of
the
starting
point
for
new
captain
integrations
and
new
tools
around
captain
and
with
this
I'm
handing
over
to
the
other
Christian
in
this
meeting,
because
I
think
he's
also
mentioning
maybe
where
what
is
the
best
starting
point
for
for
the
captain
sandbox,
because
we've
also
made
sure
that
we
have
tutorial.
E
B
Here
for
you
so
I'm,
sorry,
if
I'm
maybe
changing
the
agenda
here,
but
maybe
we
can
start
with
showing
where
to
start.
If
you
want
to
start
a
new
integration
and
then
yeah
only
goes
for
explaining
or
kind
of
talking
a
little
bit
about
the
highlights
of
the
captain,
yeah
thanks
yeah.
Let's
start
with
that,
we
do
have
the
captain
sandbox
organization,
there's
also
a
quick
contribution
guide
that
you
should
go
through.
B
This
is
more
about
how
you
contribute
something
to
captain
sandbox,
so
this
is
more
like
a
process,
but
if
you're
just
interested
in
writing
your
own
service
for
trying
things
out
or
for
investigating,
we
have
our
service
templates,
which
is
currently
available
in
go
which
has
been
presented
in
the
last
community
meeting.
So
if
you're
interested
interested
in
that,
just
look
it
up
in
the
last
community
meeting
on
YouTube
just
to
go
through
it,
we
did
have
some
changes
the
last
couple
of
days
because
we
have
to
migrate
some
libraries
etc.
B
But
this
is
now
pretty
much
in
the
final
States
and
it
has
a
quick
read
me
that
you
can
go
through
if
you
just
want
to
try
it
out,
then
the
next
thing
for
you
to
know
is
if
you
want
to
contribute
to
cap
directly,
maybe
instead
of
just
contributing
to
captain
sandbox.
This
is
also
a
possibility
and
we're
inviting
everybody
into
that.
The
first
thing
to
look
at
is
the
captain
captain
repository
where
there
is
contribution
guides.
B
It's
called
contributing
markdown,
and
it
has
some
information
where
to
start
read
the
docs
tell
us
that
you're
working
on
an
issue,
some
information
about
coding
style,
features
that
we're
using
so
that
I'd
also
be
interesting
for
people
that
use
the
captain
service
template
written
in
goal
on
this
review.
Dogging
code
coverage
that
I
know
that
you
can
use
to
monitor
and
improve
your
code
coverage
as
well
as
your
coding
style.
In
addition
to
that,
we
have
some
links.
B
For
instance,
we
have
a
link
to
the
issue
tracker
here,
I
believe
we
also
have
good
first
issue
link
somewhere,
I'm,
not
sure
where,
but
it's
quite
easy
to
to
find
good.
First
issues
by
just
clicking
on
issues
here
and
selecting
the
label:
it's
called
good
first
issue.
We
have
some
issues
that
we
track
by
labeling
them
with
good
first
issue.
B
If
you
have
any
questions,
because
you
want
to
do
them
or
something
just
post
in
the
in
the
issue
itself,
the
question
that
you
have
or
contact
us
why
our
select
channel
some
of
them,
you
might
find-
are
not
good
as
a
first
issue,
because
there
might
be
a
little
bit
more
complicated
or
maybe
you're
missing
some
information.
If
that's
the
case,
obviously
just
go
to
the
next
one
or
ask
us
again,
alright,
so
much
about
contributing.
Should
we
go
over
the
other
topic
as
well.
B
So
while
there
is
good
first
issues,
obviously
right
there,
we
also
have
the
issues
that
are
not
that
good
to
start
working
with
so
issues
for
more
experienced
developers.
Obviously,
you're
welcome
to
join
and
collaborate
with
us
on
these
issues
and
to
do
that,
we
are
having
a
camp
on
board
recalling
each
print.
In
reality,
it's
more
like
a
Kanban
style,
but
we
try
to
organize
ourselves
in
a
sprint
and
currently
has
18
tickets
or
18
issues
on
done
and
16
on.
To
do.
B
That's
quite
simple:
to
explain
because
today
was
our
sprint
review,
so
we
have
reviewed
all
those
tickets
and
we've
closed
them.
I
will
go
over
some
of
them.
I'll
provide
some
highlights
and
we
also
had
them
as
print
planning
where
we
already
defined
the
next
two
weeks
that
were
working
on
with
the
issues
that
are
in
that
to
do
column
so
just
to
go
over
some
highlights:
I'm,
not
gonna,
read
them
one
by
one
I'm
just
gonna
go
over
some
highlights
that
I've
written
down.
B
One
thing
that
we
did
in
this
splint
was
to
refactor
to
go
YouTube's
library.
Essentially,
this
library
was
really
really
big.
It
grew
over
time
and
there
was
a
lot
of
dependencies
and
it's
very
nice
to
see
where
they
go
modules,
files
that
this
is
the
dependencies
it
has
now
so
some
open,
API
or
spec-
and
this
is
cloud
events,
obviously
Google,
UUID
WebSockets
and
some
other
dependencies
yeah.
B
They
just
need
it
and
if
you
look
at
the
release,
zero,
six
one
branch-
so
that
was
the
last
release
that
we
published
this
list
just
grows,
and
there
was
a
lot
of
dependencies
that
we
just
inherited
by
our
indirect
dependencies
and
other
stuff,
and
it's
it
was
really
annoying
for
for
one
because
there
were
incompatible
dependencies,
sometimes
with
our
services
plus.
We
also
had
issues
with
the
size
that
the
binaries
had
when
we
built
anything
with
these
dependencies.
So
we
did
some
refactoring.
B
If
we
have
a
new
package
for
our
CLI,
that's
not
in
go
utils
now
somewhere
else,
and
this
just
helps
us
for
a
refactoring
and
also
the
library
has
been
restructured
a
little
bit.
So
there's
like
an
API
part
where
we
have
models
into
utils
for
API
and
there
is
a
lip
part
which
is
essentially
used
for
writing.
Your
own
captain
integrations
so,
for
instance,
this
would
be
the
part
that
the
template
repository
that
we've
built
is
primarily
using
alright.
B
Another
thing
that
we
did
is
a
huge
step
forward
for
API,
so
I
actually
have
to
find
the
issue
here,
because
there
is
some
nice
screen
and
I
want
to
show
there.
We
go
so
until
0,
6
1,
the
API
was
well.
There
was
a
micro
service,
but
in
reality
it
wasn't
so
micro.
It
did
a
lot
of
stuff
and
it
did
a
lot
of
forwarding
of
HTTP
requests
and
that
actually
stuff
that's
much
better
suited
for
a
web
server
and
instead
of
the
go
micro
service.
B
So
we
did
some
refactoring
and
I
think
I'll
zoom
in
here
and
just
to
give
you
a
high-level
architecture
of
what
is
going
on.
This
is
where
the
actual
API
lives.
So
this
is
our
API
that
we
provide
publicly,
and
this
is
what
it
was
before
and
essentially
we
had
an
is-2
ingress
gateway
by
a
load
balancer,
a
node
port
which
went
to
a
virtual
service
which
went
to
the
API,
and
then
the
API
was
distributing.
The
API
calls
to
the
micro
services.
This
is
suboptimal
because
this
is
a
small
component.
B
It's
a
micro
service
and
it
shouldn't
do
such
a
heavy
task.
Hence,
we've
introduced
an
engine,
X
gateway
or
nginx
proxy
server
in
between
that
is
now
distributing
the
calls
to
the
API
component
and
to
other
micro
services,
for
instance,
the
configuration
service-
and
this
is
not
something
that
Kristin
had
come
and
we'll
probably
start
well
he's
probably
gonna
like
it,
because
I
will
actually
just
show
you
what
the
result
is
in
the
swagger
UI
of
the
of
the
captain
API.
B
So
if
you
go
to
the
swagger
UI,
it's
just
this
URL
of
your
API
endpoint,
then
you
get
like
only
these
couple
of
endpoints
now,
so
you
just
get
the
project
endpoint
and
the
authentication
and
some
endpoints
for
posting
and
retrieving
events,
and
we
now
have
a
drop-down
up
here
where
I
can
switch
to
a
configuration
service
which
is
now
also
exposed
publicly.
Obviously
it's
secured
wire
a
token,
so
you
always
need
that
exto
c'n
still,
but
this
now
exposes
everything
from
the
configuration
service.
Why
are
the
URL
configuration
service
v1?
B
So
it's
the
same
host,
it's
the
API
host,
but
we
have
that
exposed
and
you
can
now
get
like
a
list
of
projects
and
can
get
some
details
for
a
project.
You
can
also
query
and
post
and
update
resources
for
a
project.
So
that's
the
configuration
repository
essentially
that
is
behind
the
repository
and
you
can
get
some
other
information
for
the
stages,
etc,
etc.
B
Essentially,
for
all
that
end
points
of
all
these
end
points
we
have
here,
we
would
have
to
write
something
in
the
API
to
to
kind
of
format
them,
and
we
now
have
a
setting
where
we
just
say:
yeah
forward
configuration
service,
so
slash
configuration
service
format
this
to
the
actual
configuration
service
micro
service
and
we
believe,
with
this
architecture.
We
are
a
lot
more
scalable
than
we
used
to
be,
and
it
will
be
a
lot
quicker
to
write
new
micro
service
endpoints
in
the
future.
B
B
Well
not
allowed.
That
would
say
it
wouldn't
go
that
far
I,
don't
recommend
what
we
don't
recommend
using
internal
endpoints,
we've
marked
them
as
deprecated,
hence
they're
like
strikethrough
and
invisible
kind
of,
but
we
acknowledge
that
all
these
endpoints
exist.
They
are
here
for
internal
use,
they're
here
for
some
other
use
cases
that
you
might
not
know
what
that
you
might
not
think
about.
I
will
give
you
a
short
example.
If
you
go
back
to
API
service,
you
have
this
post
project
endpoint.
That
creates
a
new
project.
B
This
is
the
right
point
for
the
captain
API
on
the
API
service
for
creating
a
new
project.
If
you
go
to
a
configuration
service,
you
will
also
find
a
post
project
endpoint.
So
if
you
just
call
this
endpoint,
this
is
just
the
post
project
endpoint
of
the
configuration
service,
and
it
might
only
do
some
parts
of
what
you
think
it
does,
because
this
really
only
creates
the
new
repository
or
it
fills
the
repository
that
you
need
for
creating
a
project,
but
nothing
else.
B
If
you
go
to
the
API
service,
this
endpoint
for
post
project
also
handles
sending
out
the
cloud
event
for
creating
a
project
it
handles
setting
up
the
MongoDB
data
store
for
a
project
etc.
So
this
is
basically
the
endpoint
that
you
should
use,
and
this
endpoint
is
for
internal
use
and
if
you
actually
use
it,
then
you
might
have
the
reason
to
do
so,
but
we
really
recommend
not
using
it
unless
you
really
have
to
there's
a
couple
end
points
like
that.
We
mark
them
all
as
internal,
so
there
shouldn't
be
an
issue.
B
If
you
follow
the
documentation,
then
you
should
be
fine,
all
right
other
than
that.
So
what
do
you?
What
else
to
be
doing
this
print?
There
was
a
lot
of
bug
fixes
that
we
did
smaller
quality
of
life
improvements,
including
captain's
bridge,
there's
nothing
really
that
I
can
show.
You
I
think,
because
these
are
all
minor
details
that
you
might
not
see,
or
that
only
happened
in
edge
cases.
So
for
me,
captain's
bridge
still
looks
fine,
but
we're
planning
to
release
a
EAP
version.
B
Ok,
that's
it
for
a
sprint
review
now
on
to
sprint
planning.
Basically,
as
I
said
already,
we
have
everything
in
that
to
do
call
Youm
of
our
combat
board
here.
We
also
have
a
more
convenient
way
of
finding
the
issues
that
we
are
doing
in
this
sprint,
which
is
by
going
a
label
and
we've
started
to
label
all
our
issues
with
the
current
sprint
number.
So
this
is
sprint
27
and
if
you
take
a
look,
one
is
already
closed.
B
Obviously,
if
you
want
to
take
part
in
any
of
these
issues,
feel
free
to
contact
us
feel
free
to
write
into
the
issue
or
if
you
have
any
question
or
any
concerns
about
one
of
the
issues
or
some.
Maybe
you
have
an
idea
to
improve
what
we
do
just
write
it
in
the
issue.
That's
fine,
but
basically
that's
what
we
said
that
we
want
to
work
on,
and
one
of
the
key
features
in
this
sprint
is
going
to
be
something
that
you
harness
has
t
said
before:
it's
exposing
captain's
bridge,
Wireless
Eli.
B
So
what
they
basically
plan
is
to
have
like
an
accepting
configure
bridge,
exposed
I
think
it
was,
and
it's
not
working.
Yet
it's
a
work
in
progress,
but
that
would
expose
your
captain's
bridge
and
then
you
could
access
captain's
bridge
wire,
a
public
URL
like
this,
with
the
caveat,
obviously
that
you
still
have
to
introduce
a
basic
authentication.
This
is
basically
configuring
a
secret
in
Cuba
needles.
We
will
document
this,
obviously
in
our
tutorials,
but
it's
quite
easy
and
I
think
this
is
something
I
also
can
show.
B
If
you
have
a
basic
authentication,
then
well,
it
is
already
authenticated.
I!
Guess
let
me
switch
so
if
you
have
basic
authentication.
This
is
what
it
will
look
like.
It
will
just
ask
you
for
a
username
at
the
password
and
you
can
configure
that
all
right.
What
else
are
we
working
on?
We
are
working
on
captain
enhancement
proposal
number
10,
which
is
also
by
our
aloft
contributor,
christen
hekima.
B
It
basically
goes
into
the
same
direction
that
I've
already
shown
with
the
API.
The
API
now
exposes
some
endpoints,
that
you
can
query
projects
etc,
and
piston
has
also
proposed
to
have
like
a
possibility
to
get
like
all
projects,
Wireless,
CLI
and
maybe
also
get
like
which
services
are
on
port
already
in
the
project.
So
some
sanity
checks
in
reality,
because,
if
you're
using
the
captain's
Eli
already,
there
is
almost
no
way
to
directly
check
if
what
we
did
was
successful
or
if
what
you
did
was
correct
and
even
for
pipeline
integrations.
It's
quite
nice.
B
If
you
can
just
check
hey,
is
my
card
service
already
on
board,
if
not
on
body--but?
Now,
just
some
some
minor
details,
but
there
was
the
use
case
or
the
user
story
that
Christian
has
told
we
think
that
kept
and
it's
a
very
nice
cap.
So
if
you
want
to
read
it
up
and
maybe
use
it
as
a
template
for
your
own
kept
and
just
go
to
github.com,
slash
captain
slash
enhanced
and
proposals
and
look
at
the
pull
requests
but
yeah.
B
This
is
something
we're
working
on
in
this
sprint
and
the
next
sprint
and
last
but
not
least,
we're
going
to
be
working
on
some
more
refactoring
tasks,
because
we've
identified
with
the
last
couple
of
refactoring
tasks,
we've
identified
some
other
potential
where
we
can
use
some
refactoring
to
help
us
maintain
our
code
better
because
right
now
there
are
some
parts
of
the
code
that
I
wouldn't
call
them
ugly
or
something
like
that.
But
this
is
how
development
works.
B
You
write
code,
you
copy
code
and
eventually
you
end
up
having
a
lot
of
code
and
then
you
need
to
refactor
it.
Then
we've
identified
some
good
points
to
do
that
now,
and
we
are
hoping
that
this
is
also
finished
in
the
next
sprint
and
it
should
increase
code
quality
over
the
next
couple
of
releases
by
a
lot.
B
Alright
I
think
that
was
it
for
Sprint
review
and
sprint
planning
if
you're
interested
in
more
details
about
what
we're
doing
in
the
sprints
obviously
come
to
us.
Why
I'd
like
to
ask
us
some
questions
or
obviously
ya,
go
why
other
channels,
if
you
have
other
channels
yeah?
Thank
you
so
much
Christian
there
was
a.
There
was
a
lot
of
information
here
and
I
just
share
my
screen
again
real.
E
E
B
A
captain
github
com-
oh
sorry,
slash
captain
slash
community,
so
you
will
find
all
the
links
there.
We
also
provide
you
like
with
the
next
with
the
agenda
of
next
service,
with
the
next
meetings,
and
also
we
will
push.
We
put
the
YouTube
links
there
from
the
recordings.
Then
please
feel
free
to
follow
us
also
on
on
Twitter,
twin
handles
and
captain
project
and
what
we
right
now
are
really
promoting
and
what
we
are
asking
you
to
take
part
in
our
survey
that
we
are
already
that
we
right
now
are
that
we
have
published.
B
It's
really
only
like
a
five-minute
effort
and
it
would,
it
would
create,
would
be
great
for
us
if
you
can
answer
some
of
those
questions.
It's
basically
about
how
you
heard
about
captain
how
you're,
using
captain
which
platform
to
using
captain
on
what
which
features.
Are
you
missing
in
captain
these
kind
of
things?
So
we
can
make
sure
to
provide
you
the
best
captain
experience
for
you
yeah.
You
also
find
the
tweets
on
this.
B
When
you
follow
us
on
Twitter,
we
are
posting
quite
regularly
there
and
if
you
want
to
contribute,
we
have
our
captain
sent
box
project
or
organization.
We
also
have
the
captain
contrib
organization,
where
we
already
have
some
kind
of
promoted
contributions
that
are
used
already
in
captain
installations,
and
also
you
can
yeah
we
would.
B
We
would
appreciate,
if
you
can
star
us
on
github
repository,
that's
kind
of
we
can
see
that
the
community
also
likes
our
project,
and
we
just
appreciate
if
you
give
us
some
feedback
here
since
we're
already
hitting
the
top
of
the
hour
thanks
so
much
everyone
for
joining.
We
got
the
most
of
the
questions.
I
think
we
got
answered
in
this
meeting.
We
got
a
great
feedback
from
the
community
thanks
so
much
for
answering
all
those
questions
and
for
presenting
thanks
to
both
Christians
and
also
to
anonymous
or
taking
the
time
to
present
in
here.