►
From YouTube: Keptn Community Meeting - March 5th, 2020
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
A
B
A
B
A
Well,
we
will,
we
will
make
this
Swift
and
we
have
a
lot
of
content
to
cover,
but
I
think
we
can
also
go
through
it
and
cover
that
of
the
most
important.
Things
is
a
reminder
for
folks
that
are
online
right
now
and
I
see
a
list
of
people
use
the
Q&A
feature
or
the
chat
feature
to
ask
any
questions,
especially
at
the
end.
We
want
to
have
it's
an
open
discussion
about
what
they
are.
What
are
the
other
use
cases
when
it
comes
to
chat
bots
with
captain?
A
So
please
give
us
feedback
if
you
are
watching
this
offline
later
on,
please
join
the
captain's
like
channel.
This
is
your
opportunity
to
get
in
touch
with
us
so
today,
a
couple
of
topics
but
I
really
want
to
go
into
the
first
point
for
like
what
a
quickly
captain's
like
bot
so
for
this
I
want
to
switch
over
to
the
slides
that
we
have
here
and
I
want
to
say.
You
know,
thanks
to
so
hype
and
also
your
game
and
I
completely
forgot
to
put
uragan
on
it.
A
The
reason
I
put
our
picture
on
there
earlier
I
wanted
to
make
sure
that
you
are
on
there
in
case.
You
know
something
happens
with
the
power,
but
you
know
most
of
the
of
the
credits
obviously
go
to
you
because
you've
built
as
at
the
captain
bought
for
slack,
but
also
your
gets
us
to
affirm
who
is
today
busy
with
another
meeting,
it's
kind
of
guided
you
through
the
process
and
that's
great
now.
B
So
at
Citrix
we
have
developed
number
of
chat
parts
and
they
do
number
of
operational
tasks
for
us
on.
You
know
we
have
actually
good
few
of
them.
So,
especially
in
this
use
case,
we
have
self-healing
workflow,
which
we
kind
of
integrated
with
dynaTrace,
and
so
this
works
with.
We
have
AWS
lambda
working
as
a
web
hook
into
the
slack.
Then
we
have
a
bot
that
auto
remediate
and
it's
helping
us
a
lot
in
the
way.
B
If
something
goes
wrong
in
a
lifetime-
and
you
know
it
gets
out
a
remediate,
so
we
don't
get
phone
call
might
to
fix
something
so
yeah.
We
also
have
other
use
cases
where
we
have
varsity
to
the
you
know:
monitoring
services.
You
know,
monitoring
is
a
cell
service.
You
know
the
teams
they
can.
They
can
monitor
that
their
service
without
without
logging
in
to
the
VPN
or
you
know,
link
to
the
office
or
something
they
can
do
with
the
phone
as
well.
B
So,
in
this
use
case,
bots
can
go
ahead
and
discover
services
we
have
and
then
you
can
use
the
service
name
and
you
can
actually
QED
performance.
It
helps
and
helps
other
teams,
you
know,
so
they
can
actually
check
the
performance
of
their
own
services
in
Sana'a
can
goes
hey.
Can
you
let
us
know
what
is
going
on
under
the
hood?
They
can
actually
just
basically
cure
it.
Mm-Hmm
yeah
completely
bypassing
us
yeah,
and
it's.
B
Exactly
I
mean
this
is
really
good.
As
a
cell
service
I
mean
they
don't
need
they're,
not
depending
on
me
to
provide
them
some
metrics,
you
can
ask
the
bot
and
bot
is
working
on
them
on
our
behalf.
Technically
so
you
know
the
bot
is
doing
the
work.
We
have
some
of
the
use
cases
implemented
of
clearing.
B
We
used
to
get
a
lot
of
requests
where
they
want
to
clear
some
cache
theta,
because
in
the
development
side
or
in
a
QA
environment,
we
just
make
the
cell
service
as
well
to
go
ahead
and
and
Kure
that
you
know
a
part
we'll
go
ahead
and
execute
our
scripts
and
solve
their
problem.
So
the
idea
is
that
make
things
kind
of
automated
in
a
way
that
we
can
spend
our
time
on
the
enhancing
the
systems
rather
than
doing
the
repetitive
tasks
mm-hmm.
B
This
is
yeah,
so
this
is
Nestor
my
mentor,
he
you
know
he's
very
futuristic
when
it
comes
to
use
cases.
He
inputs
a
lot
and
you
know
they
and
we
collaborate
and
we
go
ahead
and
develop
these
things.
So
even
we
have
scenario
if
we
want
to
kind
of
Curie
one
of
the
service
but
tell
us
where
the
response
times
going
under
the
hood
and
I'm
11.
Let
us
know
what
node
is
timing
out
as
well.
You
know
this
way.
We
can
actually
have
it
hoc
self-healing
commands.
B
We
could
say
hey
at
Ultron
self-heal
this
node
mm-hmm.
You
know
if,
for
example,
if,
if
I'm
on
call,
if
one
of
the
node
is
down
and
if
it's
a
midnight,
if
the
bot
can
fix
it
good,
but
we
have
a
use
cases
where
we
can
actually
doing
the
ad
hoc
self-healing
mm-hmm,
will
you
give
the
command
and
it
will
go
ahead
and
sell
for
you.
A
B
Is
if
the
if
the
one
node
is
down
Bart
will
try
to
self
heal,
and
then
we
have
a
flag
setup
that
it
would
not
do
it
again,
because
if
the
one
cell
field
isn't
fix,
then
wouldn't
do
the
second.
So
in
this
way
we
disabled
the
flag,
you
know
so
these
are
some
cool
use
cases
that
we
actually
do
that,
even
during
the
day
office
hours,
we
give
a
command
to
a
selfie.
You
know
at
Hawks
cell
feeling
we
don't
need
to
log
into
the
systems
and
they
just
I.
A
Think
I
hope
that
I
know
that
a
couple
of
the
captain
engineers
are
listening
to
this
and
we're
in
Captain.
We
also
working
on
the
auto
remediation
capability
that
is
currently
mainly
triggered
by
you
know:
problem
detected
in
production,
let's
say
by
dynaTrace
or
through
a
Prometheus
event,
but
I
think
this
use
case.
We
said
a
talk.
You
want
to
execute
a
talk.
A
This
is
kind
of
the
the
use
case
that
also
inspired
us
to
implement
captain
and
its
way
to
evaluate
SL
is
against
SL
O's,
and
so
captain
has
been
having
this
capability
for
a
while
and
the
typical
use
case
how
this
works.
If
you
have
installed
captain,
then
and
as
a
standalone
quality
gates
with
its
standalone
called
the
gate
capability,
you
can
say
captain
start
evaluation
for
this
particular
time
frame
for
this
service
and
also,
first,
you
have
to
specify
SLI.
A
So
what
are
the
metrics
that
are
important
for
you
from
any
atul
out
there
and
also
not
only
give
me
the
raw
data,
but
already
do
some
evaluation
very
dated
against
my
objectives
and
what
happens
is
from
the
workflow
perspective.
I
tell
cap
and
start
my
evaluation.
Then
captain
pulls
this
information
from
the
different
tools
where
we
have
different
SLI
providers
already.
A
You
know
weeks
and
months
ago
we
said:
wouldn't
that
be
cool
if
we
can
just
instead
of
just
giving
our
engineers
a
CLI
which
they
most
likely
liked
as
well,
but
most
of
them
live
in
slack,
and
so
why
not
to
provide
this
capability
in
the
captain
bot
or
through
a
captain
jet
bot?
That
is
then
just
taking
this
and
then
communicating
with
captain
to
do
all
these
things
and
I
think
that's
actually
exactly
what
you
guys
build
right.
That's
what
you
built!
You
built
a
front-end
chat,
bot
solution
for
that.
B
A
Cool
now
we
want
to
switch
over
to
the
demo
before
we
go
to
the
demo,
a
quick
overview
of
what
we've
actually
prepared
the
what
actually
Jurgen
and
you
have
prepared.
So
there
is
an
ich
ich
es
cluster
that
runs
captain
quality
gates,
there's
also
another
cluster,
where
Jurgen
has
deployed
a
very
simple
sock
shop
card
application
that
is
monitored
by
dynaTrace.
A
So
that's
kind
of
this,
this
dheere
dheere
dheere
here
is
you
have
a
system
that
is
already
been
monitored
and
then
you
have
captain
quality
gates,
and
then
we
have
your
slick
way
of
your
select
service.
That
is
also,
in
this
case
installed
in
the
same
aqueous
cluster,
where
captain
runs,
but
it
could
essentially
I
would
I
would
assume
run
anywhere.
B
A
So
then,
let's
quickly
jump
into
let's
let
me
show
you
what
we
really
have
here
so
I
told
you
we
have
this
app.
It
doesn't
matter
that
the
app
might
not
be
full
like
a
full-featured
app
with
multiple
microservices.
If
we
want
to
show
that
the
showcase,
so
this
is
the
the
cards
app
also,
we
have,
in
our
case,
dynaTrace
monitoring
this
in
case
you're
using
dynaTrace
for
monitoring.
What
do
you
need
to
make
sure
it?
A
Obviously
manager
is
monitors
this
particular
service
of
these
services,
where
you
want
to
get
automated
feedback
back
to
their
developers.
Also
very
important
you'll
need
to
put
tags
on
your
services
now,
in
my
case,
remember
we're
talking
here
about
the
quality
gate
only
use
case.
This
is
not
where
captain
did
the
deployment.
A
This
is
a
use
case
worse
where
a
version
a
service
was
already
deployed,
maybe
you've
deployed
it
through
Jenkins
or
through
other
means,
but
the
importance
still
is
that
you
need
to
put
tags
on
your
services
because,
later
on,
when
we
want
to
query
and
define
our
sls
and
it
slows,
we
need
to
say
okay,
we
want
to
have
a
certain
metric
from
a
service
that
analyze
monitors.
That
has
a
certain
tag
on
it
like,
in
this
case,
captain
quality.
A
It's
gate
take,
so
this
is
monitored
and
just
to
show
you,
we
have
some
data
because
I'm
running
some
basic
load
in
the
in
the
backend.
Now
what
uragan
has
also
done?
He
has
set
up
captain
as
I
said
earlier,
I
just
zoom
in
hello.
It
makes
a
little
bit
of
bigger,
so
he,
when
you
use
captain,
you
know
that
captain
has
a
github
repo,
and
this
is
where
Mike
is:
we've
specified
an
upstream
git
repo
where
all
the
assets
are
replicated
and
what
you
can
specify
them,
which
is
going
quickly
back
to
master.
A
It
was
basically
a
this
is
kind
of
also
a
best
practice.
I
would
say
just
a
single
stage
pipeline,
because
the
real
only
use
case
is
I'm.
A
developer
I
know
if
a
system
that
is
already
monitored
somewhere,
but
what
I
want
is
I
want
to
get
feedback
whenever
I
like
it
so
I
don't
need
captain
for
full
delivery
here,
I
just
say:
I
have
a
pre,
prod
environment,
so
I
specify
a
single
stage
pipeline
or
a
single
stage
shipyard
file,
then,
for
this
single
stage,
pre
prod.
A
This
is
where
all
the
relevant
config
files
are
stored.
So
we
have
the
one
cards
service,
and
this
is
where
your
again
specified
the
sighs.
This
is
exactly
where
we
have
what
metrics
are
actually
relevant
and
I
think
this
is
cool
the
way
we
do
it
in
captain,
so
here
you're
completely
flexible
right.
A
A
B
The
reason
is
like
we
need
just
those
three
metrics
yeah
and
those
three
metrics
very
much.
You
know
pretty
much
care
about
the
team
I
work
with,
and
so
that's
why
they
hired
code
it,
but
I
know
it
would
be
much
better
to
having
a
configurable
where
users
can
I
sleek,
invigorate
their
own
metrics
or.
A
A
So
so
this
is
right,
it's
completely
flexible,
sync
it
so
everybody
can
edit.
So
this
is
the
list
of
metrics
that
are
important
for
you,
but
the
list
of
metrics
is
not
alone
or
the
list
of
the
slic
service
level
indicators.
The
other
thing
that
is
important
is
to
specify
an
SLO
the
service
level
objective.
A
This
is
actually
where
you
say:
hey,
which
metrics,
which
s
allies,
are
really
interesting
for
you,
and
you
can
also
specify
whether
captain
should
automatically
compare
a
metric
with,
let's
say
and
a
hard-coded
threshold
that
you
have,
or
even
with
a
previous
comparison,
that
you
ran
so
with
the
previous
build
or
with
the
previous
evaluation
that
you
ran
so
the
here.
We
give
you
the
option
of
either
absolute
values,
a
criteria
for
pass
and
winning
or
relative.
A
If
you
want
to
learn
more
about
this
and
also
the
total
scoring,
we
have
more
material
out
there,
but
I
just
want
to
show
you
the
stuff
we've
done
here,
the
youngest
on
here.
He
set
up
a
single
stage
pipeline
or
single
stage,
they'll
file
with
captain
and
here's
a
sock
shop
as
a
sample
service,
and
he
has
the
SL
eyes
defiant
5
of
5
in
total
and
DSL
O's.
A
A
B
A
B
A
A
A
B
A
So
what
we
see
here
also
so
what
what
really
care
what
the
body
is
sent
in?
Is
he
using
the
API,
the
captain's
API
started,
an
evaluation
you
calculated
at
the
timeframe
start
and
end
time
now,
what's
important
to
you
to
understand
this
is
UTC
time
so
1609
because
I
mean
in
an
Austria
right
now,
so
it's
1720,
so
it's
like
in
an
hour
like
anyway
to
TC
time
right,
10
minutes
the
last
10
minutes.
What
do
I
make
this
more
complicated
as
it
is?
It's
just
10
minutes
now,
while.
A
Course,
yeah:
let's
go
to
the
bridge,
so
I
got
my
captain's
bridge
here,
yeah,
so
that
it's
1719
we
have
to
start
evaluation
event
exactly
so
that
means
this
is
where
you
sent
in.
This
is
also
great
I
love
the
bridge
for
multiple
reasons,
but
this
is
also
great
because
we
have
all
the
raw
cloud
events
here
so
in
case
somebody
else
wants
to
build
an
integration
with
captain
using
the
API
is.
This
is
a
great
way
to
learn
what
events
are
actually
sent
back
and
forth
and.
B
A
B
B
A
A
Cool
and
that's
also
the
link
to
the
bridge-
this
is
also
great
from
here
like
get
me
to
the
bridge.
I
know
we're
working
on
deep
links,
so
it
would
be.
We
will
it's
at
some
point
in
the
future,
get
a
link
here.
They
get
you
directly
to
that
kept
in
context,
because
if
you
are
scrolling
back
in
history,
you
get
a
link.
You
always
want
to
go
directly
to
that
captain
context,
but
that's
great
before
I
showed
this
stuff
here.
I
want
to
show
something
else
and
not
a
comment.
A
B
B
B
B
A
Perfect
so
this
means
it
will.
Basically
it
assumes
the
current
day
and
then
it
sends
out
the
evaluation
and
now
look
at
this.
This
was
super
fast,
because,
obviously,
that
data
is
available
already
and
so
I
immediately
get
the
data
back
and
the
good
news
is
I
pass.
So
what
that
means
is
all
of
my
metrics
that
I
have
specified.
All
of
my
slides
have
been
evaluated
against
my
solos
and
I
get
a
past
comment.
That's
awesome.
A
I
also
want
to
quickly
show
the
bridge
again
right,
the
in
the
bridge.
What
we
see
here
now
I
am
on
the
list
that
is
accentuate
the
monitor,
just
executed,
1724
same
thing,
evaluation
and
then
I
end
up
on
the
evaluation
done
here.
I
see
really
all
the
individual
s
lies
that
are
specified
with
the
well
value.
This
is
great,
but
what
I
really
love
is
this
here?
You
can
go
to
evaluation
comparison,
and
now
this
gives
me
an
historical
overview
of
all
of
my
evaluations
that
I've
done
and
on
top
we
have
a
square.
A
This
is
the
the
the
square
that
we
calculated
based
on
all
the
SL
SLO.
They
finish
and
all
the
objectives
and
then
on
the
bottle
and
the
other
ones
are
all
the
metrics
that
you've
specified
in
their
self
and
now
you
may
wonder
why
there's
only
one
line
with
color
only
response
time
and
the
others
are
gray,
because
these
are
informational
because
remember
if
I
go
back
to
my
definition
here
in
my
SLO
I
may
have
only
I
can
I
can
specify
just
metrics
where
I
don't
really
want
them
to
be
valid
against
the
threshold.
A
Maybe
I
don't
know
the
Thresher,
maybe
it's
your
relevant,
but
I
still
want
to
get
the
data.
This
is
why
they
show
up
in
in
an
informational
and
all
the
others
are
going
to
be
included
in
the
overall
score
calculation.
Now
the
cool
thing
is
I.
Can
click
here
and
I
see
every
single
value
on
the
bottom
right?
I?
Can
click
through
and
I
see
why
some
of
these
have
failed
right?
Maybe
there
was
no
data
available,
I
selected
a
time
range.
It
was
invalid.
A
I
specify
the
wrong
time
frame,
but
what's
also
great,
you
can
switch
here
between
heat
map
and
chart,
and
this
is
now
where
we
can
also
say.
I
want
to
chart
the
response
time
over
time.
Right
so
I
can
you
can
chart
any
type
of
metric
and
you
see
really
they
they
the
time.
That's
the
history
right,
that's
what
it
is
historical
chart
of
every
metric,
so
it's
pretty
cool
so
so
wipe
coming
back
to
your
chat
bot.
A
B
Yep,
so
here
and
you
you
define
the
bridge
URL
and
that's
a
variable
in
Captain
API
token,
which
you
can
take
it
instructions
or
above
and
you
can.
You
need
a
slack
token
in
order
to
have
a
part
communicate
to
your
slack
tenant.
So
these
are
the
required
bridge.
Url
is
optional.
If
you
don't
want
to
give
it
because
some
people
don't
have
it
I'm
open
publicly,
so
it's
optional
yeah,
it's
optional
variable.
So
these
are
the
only
things.
B
A
That
means,
if
you
install
it,
if
you
install
it
in
the
same
kubernetes
cluster
as
Captain
runs,
and
you
can
actually
keep
this
empty
and
I
think
it
says
it
up
here
right,
you
can,
you
can
keep
it
empty
and
then
it
just
assumes
the
default
naming
scheme
of
the
API.
But
if
you're
running
outside
you
obviously
to
specify
the
end
point
of
the
API
and
that's
it
yeah
cool.
A
That's
awesome
cool,
so
is
there?
Is
there
anything
else,
and
although
this
was
kind
of
the
first
iteration
but
I,
think
it's
it's
a
great
use
case
that
you've
implemented,
especially
the
you
know:
I,
don't
wanna
talk,
I,
don't
wanna
I,
don't
want
to
have
to
go
to
somebody
that
gives
me
the
relevant
data.
I
want
to
define
what
relevant
is
for
me
in
a
config
file
like
a
slice
and
a
solos
and
I'm
just
using
a
slag
pot,
and
this
pot
gives
me
the
data
back,
and
this
is.
A
Pretty
cool
feedback,
so
I
want
to
have
a
quick
discussion
here
or
ask
people
for
feedback
on
other
use
cases
that
you
would
like
to
see
and
also
so
way.
We
discussed
about
this
really
in
preparation
of
this
call.
What
would
be
the
next
use
cases
that
you
and
uragan
had
in
minds
so
that
we
can
give
folks
that
are
on
the
line
right
now?
Some
some
food
for
thought
and
I.
B
A
A
And
the
use
case
I
think
that
once
we
talked
about
this
is
now
the
start
evaluation.
So
just
give
me
some
data
from
a
particular
time
frame
and
evaluate
against
SLIC
solos.
But
I
would
also
like
to
see
is
the
the
new
artifact
like
the
complete
deployment,
then
run
the
test
and
evaluate
at
the
whole
the
whole
thing.
A
I
would
also
like
to
see
something
like
I
want
to
ask
the
captain
bot
hey,
which
services
have
which
in
which,
in
which
versions
of
my
in
this
case,
cart
service,
ever
deployed
in
a
certain
stage
and
which
ones
have
a
good,
a
good
rating
so
that
they
can
potentially
be
promoted
into
the
next
stage.
In
case
they
don't
have
automated
promotions.
I
would
like
to
say
captain
bought
give
me
the
versions
of
cards
that
have
they
have
successfully
passed
the
quality
gate
and
then
maybe
the
captain
part
returns
in
the
last
day
or
two.
A
You
had
version
2
and
version
6,
which
one
do
you
like
me
to
promote.
So
there
would
be
nice
conversation,
and
then
you
know
that
pot
can
say
well.
I
can
take
the
pot,
please
promote
version.
6
because
that's
obviously
the
better
one
and
a
newer
one
and
then
the
captain
part
could
then
do
a
new
artifact
event
for
the
next
stage.
So
I
think
there
would
be
a
nice
one.
I
think.
B
A
B
A
Go
for
it
yeah
another
another
thing
that
comes
to
mind
would
be
editing,
adding
or
removing
a
sizing.
It
slows
through
the
chat
right.
If
I
need
a
new
metric,
guys,
I
see
it
has
five
metrics,
but
what
if
I
want
to
get
a
sixth
one?
Maybe
I
don't
know
where
this
github
repo
is
I
want
to
just
tell
the
board
hey
from
now
on.
Please
also
add
this
dynaTrace
query,
or
this
Prometheus
query
to
the
air
slice
and
I
want
to
see
it
as
informational
or
here
is.
My
here
is
my
my
threshold.
B
That
would
be
really
cool,
like
anything
any
use
case
that
can
actually
help
users
to
kind
of
make
it
easy
for
them.
You
know
they
don't
need
to
dig
down
deep
configs
or
anything.
They
could
simply
just
ask
the
bot
to
do
that
for
users
yeah.
You
know
this
is
a
mindset.
We
have
yeah
make
it
easy
simple.
A
A
May
a
that
a
good
to
know,
for
me,
I
mean
I,
couldn't
probably
look
it
up
in
the
captain's
bridge,
because
this
is
where
this
information
will
also
eventually
show
up
nicely
on
like
overview
dashboards,
but
this
is
also
information
that
I
want
to
know
as
a
developer.
How
often
in
the
last
week
ever
tried
to
deploy
it
and
how
often
have
I
succeeded
all
only
10%,
that's
actually
pretty
bad,
and
and
why
now,
which
metric
reach,
which
metric
failed
all
the
time?
A
A
But
these
are
the
things
right
you
want
to
know.
You
want
to
know
as
a
developer.
What
what
should
I
focus
on?
What
should
my
priority
be?
Should
my
priority
be
fixing
response
time,
but
if
response
time
is
actually
only
contributing
10%
to
my
overall
SLO
but
I
have
let's
say
a
different
problem
with
memory
is
more
important,
then
captain
should
tell
me
no.
You
should
focus
on
this,
because
this
is
the
metric.
That
is
the
biggest
impact
right
now,
while
you're
not
meeting
your
SLO
and
so
not
a
problem.
B
A
You've
seen
the
the
bridge,
the
new
bridge,
that
I
shown
the
new
bridge
is
also
available
as
early
access
and
I
know
that
the
guys
are
working
very
heavily
and
fast
on
the
next
release
of
captain
open
6.1,
whether
the
new
bridge
will
become
the
default
bridge.
So
that's
great,
but
in
case
you're
on
Oh
6o
right
now
make
sure
to
check
out
the
early
exits
version
of
the
bridge.
It's
awesome
also
keep
an
eye
on
the
captain
enhancement
proposals.
A
This
is
where
you
can
put
in
your
proposals
on
what
you
would
like
to
see
like
bigger
proposals
and
really
explain
your
use
case
and
how
you
would
like
this
to
to
be
implemented.
Then
uragan
did
a
great
job
in
writing.
A
blog
post
based
on
the
previous
community
meeting
we
had
with
unleash
where
they
showed
future
toggling
and
self-healing
with
feature
toggling
framework.
So
there's
a
blog
out
there
on
medium,
so
check
this
out.
A
Obviously
useful
links
us
like
button
service,
that's
useful!
We
have
an
Outlook
on
future
community
meetings
that
will
come.
We
will
have
Hendrik
from
Neil
T's
coming
in
on
his
SLI
providers.
We
will
have
Christian
from
ERT
coming
in
I
also
talked
with
the
election
guys
because
Rob
with
Atlassian
built
integrations
with
the
bitbucket
pipeline,
and
we
will
also,
as
you
can
see
here
soon
start
besides
these
community
meetings
that
are
more
focused
on
end
users
and
that
are
using
captain
and
I
can
on
how
we
can
use
these
use
cases.
A
A
Hopefully
not
more
will
follow,
but
we
will
try
to
keep
a
list
here
of
where
we
are
and
also
make
sure
you
just
you
know,
follow
us
on
Twitter
and
join
the
slack
channel
that
is
hugely
important.
Join
us
like
channel
is
the
way
you
can
get
in
touch
with
us
and
be
is
good
and
nice
is
so
hype
and
contribute.
That
would
be
awesome,
but
will
be
perfect
good.