►
From YouTube: Keptn Community Meeting - September 24th, 2020
Description
September 24, 2020
Diary - what happened last week?
Preparation and some work for a 0.7.2 release: Focus Quality Gates
Bridge Evaluation Tile
Lighthouse Evaluation Logic change
CommunityBridge - Mentoring Program from CNCF
https://github.com/cncf/mentoring/blob/master/communitybridge/2020/q3-q4/project_ideas.md#keptn
Angular project - improvements to the Keptn’s Bridge: https://github.com/keptn/keptn/issues/2299
Golang project - improvements to the Keptn CLI: https://github.com/keptn/keptn/issues/2300
Hacktoberfest - we are part of contributing.today
Community Rockstar Award Celebration 🎉
Keptn mailing list / google group: https://groups.google.com/forum/#!forum/keptn
Good first issues: https://goodfirstissue.dev/ or start here
Noteworthy Issues & PRs (Review)
For each PR, please tell us if you updated the docs, or in case it was not necessary please say so.
Florian:
Lighthouse Service: adapt logic of “include_result_with_score” filter https://github.com/keptn/keptn/issues/2388
Better feedback if no project/stage/service could be found for evaluation: https://github.com/keptn/keptn/issues/2365
Configuration Service: Include Git commit ID and Upstream URL in Resource response: https://github.com/keptn/keptn/issues/2307
New Service for retrieving usage statistics: https://github.com/keptn/keptn/issues/2310
https://github.com/keptn-sandbox/statistics-service
Supratik
Improve CLI error handling for failed connections to API https://github.com/keptn/keptn/pull/2373
Andreas:
Fix Helm chart: https://github.com/keptn/keptn/pull/2386
Allow to skip ssl verification: https://github.com/keptn-contrib/dynatrace-service/pull/193
Refactoring, consistently use dynatrace.conf.yaml https://github.com/keptn-contrib/dynatrace-service/issues/185
Ermin:
https://github.com/keptn/keptn/pull/2395 -Enable highlighting in heatmap chart
https://github.com/keptn/keptn/pull/2406 - Evaluation tile rework
Christian:
CI/Automation: Verify helm charts before releasing https://github.com/keptn/keptn/pull/2380
CLI: Improve robustness of generate support-archive https://github.com/keptn/keptn/pull/2375
Johannes: nothing to discuss (issues still in progress)
Roadmap → KEP / SPEC / Issues
KEP 06: The next generation of Shipyard: https://github.com/keptn/enhancement-proposals/pull/6
Work in progress:
https://github.com/keptn/keptn/projects/29
Release-checklist (Christian):
https://github.com/keptn/keptn/wiki/Release-Checklist
https://github.com/keptn/keptn/issues/2404
Backlog Refinement / Next Sprint:
https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Akeptn+user%3Akeptn-contrib+label%3A%22next-sprint%22
Planning Board: https://github.com/keptn/keptn/projects/29
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
A
Okay,
hi
everyone
and
welcome
to
this
captain
community
meeting.
We
have
a
very,
very
large
agenda
for
today.
We
have
a
couple
of
special
items
that
we
want
to
cover
today
and
I
will
write
I
would
jump
in
just
let
me
say
one
thing,
so
we
are
following
here:
the
cncf
code
of
conduct.
That
basically
means
please
be
nice
to
each
other.
We
have
a
couple
of
people
are
joining
as
panelists
with
a
couple
of
people
joining
as
participants
in
the
meeting.
A
So
if
you
want
to
ask
some
questions
to
the
captain
developers,
please
do
this
via
the
q
and
a
section
we
have
disabled
the
chat
and
we
have
also
disabled
for
participants,
video
sharing
and
voice
sharing.
So
just
please
raise
your
voice
by
opening
up
a
question:
q
a
so
that
will
help
us
a
little
bit
with
the
housekeeping
here.
So
first
part
for
today
is
we're
very
excited
to
be
part
of
the
community
bridge.
A
The
community
bridge
is
a
program,
a
mentoring
program
from
the
cncf,
where
mentees
can
apply,
and
they
will
be
then
matched
with
projects
and
basically
they
get
a
mentor
assigned
from
a
project,
and
then
they
can
work
on
open
source
projects.
I
think
there
is
even
a
some
kind
of
a
scholarship
attached
to
this
and
we
really
want
to
help
the
open
source
community
to
contribute
to
open
source,
and
we
are
really
happy
to
help
mentees
to
work
on
open
source
project,
especially
if
they
are
interested
in
captain.
A
We
would
be
especially
happy
so
we
have
listed
here
two
projects
that
we
submitted
to
the
mentoring
program
community
bridge
of
the
cncf.
If
you're
interested,
please
take
a
look
at
these
two
projects.
The
one
is
more
angular
focused.
We
are
looking
here
for
improvements
to
the
captain's
bridge
where
we
basically
want
to
have
a
nice
visualization
of
remediation
actions
that
are
part
of
that
are
part
of
captain
and
for
the
second
project,
that's
more
golang
focused.
A
We
are
seeking
for
improvements
to
the
captain
cli,
where
the
captain
cli
makes
it
more
easy
to
switch
between
captain
installation
by
either
combining
this
with
the
cube
context
or
making
other
possible
implementations
to
switch
the
context
of
different
captain
implementations,
the
sign
up
period.
I
think
it's
until
monday,
so
please
be
fast
and
go
to
the
community
bridge.
It's
this
link
up
here
and
sign
up
and
then
get
yourself
assigned
to
the
captain
project.
A
Another
initiative
that
we
have
during
the
month
of
october,
so
starting
next
week
is
we
are
participating
in
the
hacktoberfest,
that's
an
online
event
and
we
are
part
of
a
sub
event.
There.
That's
called
contributing
dot,
nd
or
their
website
is
contributing
dot
today,
because
nd
was
not
possible
and
we
are
also
listed
there
with
a
very
short
youtube
video
kind
of
introduction
to
the
project
kind
of
skill
set.
You
want
to
have
you
you
should
have
when
you
want
to
contribute
to
captain.
A
A
B
Yeah
sure
so
I
talked
to
andy
about
two
years
ago
in
the
very
beginning
of
of
captain,
and
he
talked
to
me
about
what
the
ideas
of
of
captain
was
and-
and
at
that
point
I
was
I
was
already
interested,
but
then
then
it
started
growing
and
it
started
yeah.
It
really
started
living
so
I
joined,
and
the
first
things
I
I
contributed
to
captain
was
a
lot
of
questions
I
think
on
slack.
B
So
so
those
were
the
first
contributions,
but
but
yeah
then
we
started.
We
actually
started
with
it
in
one
of
our
projects
said:
okay,
let's,
let's
do
this
and
it
was
a
an
azure
devops
pipeline
and
a
very
let's
say,
a
traditional,
more
traditional
application,
not
in
a
in
a
kubernetes
context
context.
Yet
because
we
are
moving
towards
microservices
as
we
speak,
so
I
made
a
small
powershell
script
as
a
first
as
a
first,
but
I
thought
this
is.
B
This
is
very
interesting
material
and
at
that
moment
andy
andreas
already
created
his
his
jenkins
plugin.
So
I
thought
let's
do
exactly
the
same,
but
then
on
azure
devops,
so
so
not
very
unique
but
very
helpful.
And
since
then
we
are.
We
already
have
two
customers
here
in
belgium,
so
our
first
one
which
is
using
it
and
then
another
one
also
which
we
convinced
to
actually
use
captain
quality
gates,
because
that's
that's
what
it
actually
is
about.
So
maybe
I
can
just
share
sure
I.
B
B
B
B
So
currently
it's
a
certain
release.
I
think
1.16,
but
still
still
have
some
things
to
do
regarding
regarding
certainly
captain
captain
seven
or
zero
seven,
and
I
think
five
minutes
ago
I
did
the
k3s
installation
of
the
of
the
seven
of
the
seven
one.
So
so
soon
I
will
be
testing
this
against
again:
seven.
Normally
it
should
work,
but
but
yeah
we're
continuing
to
to
move
in
the
good
direction.
A
D
A
If
someone
else
from
the
captain
community
now
thinks
hey,
I
also
want
to
be
a
captain
community
rockstar.
I
want
to
receive
this
special
t-shirt
that
also
bears
received.
Then
we
kind
of
have
some,
let's
say,
guidelines:
how
to
become
a
community
rockstar,
how
to
be
recognized
by
the
captain
community
just
go
to
uw.com,
slash,
captain
community,
sorry
and
you
will
find
the
latest
community
rockstars
and
you
will
find
those
guidelines
and
yeah.
A
C
A
A
A
Working
with
captain
and
contribute
into
captain
again,
we
have
a
list
of
good
first
issues,
and
I
think
we
even
have
some
of
those
some
first
contributors
on
this
call
today.
I
think
they
also
started
with
this
list
of
good
first
issues,
that
the
development
team
is
always
gathering
and
preparing
for
the
whole
community.
So
with
this
I'm
already
handing
over
to
florian
and
we
will
go
through
the
list
of
noteworthy
issues
and
prs
all
right.
Thank
you.
E
E
So
the
way
this
worked
until
recently
was
that,
if
you
wanted
to,
for
example,
do
a
comparison
based
evaluation
with
past
evaluations
by
setting
the
include
result
with
score
parameter,
for
example,
the
past
the
way
the
lighthouse
service
did,
that
is
it
fetched
the
last
or
for
in
this
example,
with
warning
results.
The
lighthouse
service
fetched
the
last
three
events,
for
example,
with
the
result
warning
and
then
within
those
evaluation
done
events
for
each
sli.
E
E
Actually,
so
now
the
way
it
works,
it
will
only
apply
the
filter
on
the
evaluation
level,
so
it
will
again,
for
example,
take
those
three
events,
but
it
will
not
do
any
further
filtering
within
those
slo
service
level
objectives.
So
now,
in
this
instance,
all
of
those
values
would
be
taken
all
right.
Are
there
any
questions
about
that.
E
G
A
G
E
Send
a
start,
evaluation
event
for
a
project
or
a
stage
or
service
that
doesn't
actually
exist.
So,
for
example,
if
you
do
a
typo
when
entering
the
service
name,
there
really
wasn't
a
convenient
way
of
of
noticing
this
error.
So
what
happened
is
the
evaluation
or
start
evaluation
event
was
sent
by
the
cli
and
the
api
forwarded
it
to
the
lighter
service
and
there
it
kind
of
got
stuck
and
you
didn't
get
any
evaluation
done.
E
But
if
there
is
no
slo
file
available,
it
will
check
if
the
service
or
the
stage
or
the
project
actually
exists,
and
if
they
do
not
exist,
it
will
send
out
an
evaluation
done
event
containing
a
appropriate
message
telling
that
either
the
service
doesn't
exist
within
the
stage
of
the
project
or
the
stage
doesn't
exist
within
the
project
or
the
project
doesn't
exist
at
all.
So
I
think
this
extension
mix
makes
it
a
little
bit
easier
to
debug
those
kind
of
errors
scenarios
all
right.
Are
there
any
questions
about
that.
E
E
Then
the
url
of
the
upstream
repository.
If
you
have
configured
one
and
also
the
branch
this
resource
has
been
fetched
from
so
now,
we
also
do
include
those
informations
within
the
payload
and
yeah.
This
just
gives
you
a
little
bit
more
context
and
makes
it
easier,
for
example,
in
the
case
of
the
lighthouse
service,
because
that
one
fetches
the
slo
file
from
from
the
service
that's
being
evaluated,
and
now
it
would
be
possible
to
also
really
tell
which
version
of
the
slo
file
has
been
used
for
a
particular
evaluation.
F
E
F
E
Because
my
laptop
just
crashed
earlier-
and
now
I
lost
most
of
the
actual
demo
stuff,
I
wanted
to
show
all
right:
let's
go
to
the
releases
yeah
here.
It
is
thank
you.
So
basically,
what
we
get
here
is
you
can
query
the
usage
statistics
for
a
certain
time
frame
by
providing
the
from
and
to
parameter
as
a
unix
timestamp,
and
then
you
will
get
a
result
that
will
look
like
the
following.
E
So
again
here
you
you
get
from
two
time
stems
to
check
if,
if
it
returned
the
correct
time
frame,
and
then
you
get
an
overview
with
the
projects
that
are
within
your
captain
installation
and
the
services
within
those
projects,
and
what
you
can
see
here
in
the
services
is
in
addition
to
the
name,
of
course,
the
number
of
sent
events
for
a
given
type.
So
how
many
approval
finished
events
have
been
sent
for
that
service?
E
How
many
configuration
changed
event
has
been
sent,
etc,
and
you
also
get
the
statistics
of
which
captain
execution
plane
services
have
been
involved
in
this
service
and
how
many
events
of
a
certain
type
they
have
sent
for
your
services.
So
here,
for
example,
the
gatekeeper
was
involved
in
in
the
service
and
it
sent
one
approval
finished,
one
approval
triggered
event
into
configuration,
changed
events
etc,
and
you
also
get
this
yeah,
basically
for
all
execution,
plane
services
that
that
are
somehow
involved
in
the
in
the
task
sequences
for
that
particular
service.
F
G
C
C
A
C
Yes,
so
the
issue
that
that
I
was
working
on
is
just
improves
cnn
error
message
when
the
api
connection
fails.
So
sorry,
this
is
the
issue
yeah
so
before
previously.
What
happened
then,
that
whenever
the
commands
api
kept
an
ad
resource
or
any
other
command
that
interacted
with
the
api?
Where
was
run?
If
the
api
was
not
running,
or
there
was
some
problem
with
the
api,
it
used
to
throw
this
kind
of
errors,
and
sometimes
errors
are
misleading
and
there
are-
and
some
remedial
actions
were
also
not
given.
C
So
you
know
it
was
totally
dependent
on
the
user
to
probe
the
error
and
find
out
what
was
the
problem.
So
so
my
task
was
to
build
a
utility
function
that
could
that
would
actually
ping
the
api
before
going
on
before
performing
the
like,
like
before
going
on
with
the
command.
So
so
here
is
a
bit
of
the
code
that
I
wrote
and
what
it
basically
does
it.
C
C
So
I
exactly
mimic
the
entire
configuration
that
is
actually
used
by
captain
to
interact
with
api
so
that
I
get
the
exact
kind
of
error
that
that
would
have
occurred
if
I
had
been
using
this
add
resource
command
and
in
the
command
itself.
I
incorporated
it
using
this.
This
part
endpoint
error.
It
will
first
check
the
check
whether
what
is
the
status
of
the
endpoint
and
then
it
will
throw
the
like
it
will
show
the
errors.
E
C
With
this,
along
with
that,
it
will
show
some
of
the
remedial
actions
like
this
is
this,
is
that
and
this
is
set,
so
this
is
how
it
works.
So
I
will
just
show
a
quick
demo
of
this.
Let's
say
I
am
using
the
simple
node
service
as
an
example,
and
now
I
have
a
shipyard
of
captain
seven-
and
here
is
a
api
server
running.
So
if
I
yeah
so,
if
I
perform
ad
resource,
it
will
like
the
resource
will
be
added
successfully
because
the
api
is
because
the
api
is
running.
C
But
if
I
shut
down
the
api
and
if
I
perform
the
same
command
it
will,
it
will
tell
the
exact
error
and
connection
refuse,
and
it
will
show
the
possible
reasons.
Actually,
I
messed
up
my
captain
installation
just
before
the
meeting,
so
I
cannot
show
other
kinds
of
errors,
but
you
know
it
will
all
show
what
like
what
are
the
possible
error
and
what
could
be
and
the
possible
reasons
are,
you
know,
are
similar.
F
G
Hi
everyone.
I
also
would
like
to
show
you
three
pdrs.
I
was
working
on
this
week,
so
the
first
one
fixed
some
problems
in
our
hand,
charts
for
example.
Here
we
had
a
space
when
we
referenced
the
distribute
the
image
and
also
environment
variables
have
to
be
of
type
string.
Therefore,
I've
quoted
them
and
yeah
a
small
issue.
The
sea
light
on
that
link
was
not
in
the
values
file,
so
there
was
no
change
and
chance
to
set
it,
and
thanks
to
christian,
we
verify
now
the
hem
charts.
G
I
guess
people
can
live
with
that
spoiler.
My
second
issue
is
is
in
the
dynatrace
service,
as
well
as
in
that
energy
sli
service.
Here
I've
worked
on
an
issue
which
allows
you
to
skip
the
ssl
verification,
so
the
use
case
behind
this
is,
if
you
have
your
dynamics,
environment
secured
using
an
a
self-signed
certificate,
then
we
cannot
do,
of
course,
when
it's
ssn
verification.
G
So
there
needs
to
be
a
way
to
skip
this
ssl
verification
and
technically,
you
can
simply
here
use
an
environment
variable
which
is
provided
in
in
our
deploy
service
jamuns,
and
if
you
set
this
to
into
false,
then
there
will
not
be
an
ssn
verification
and
in
the
source
code.
This
is
simply,
I
create
a
new
transport
object
here
and
set
this
in
the
http
client.
G
G
So,
for
example,
we
had
the
problem
that
one
error
was
locked
six
or
seven
times
here,
and
this
was
almost
impossible
to
find
the
root
cause
only
looking
at
the
logs,
because
there
will
have
been
debug
messages,
info
messages
and
so
on.
And
therefore
I
decided
to
do
a
refactoring
of
this
planetary
service
and.
G
And
during
this
refactoring
I
also
identified
that
senator
is
confirmed,
which
is
a
feature
by
indie
grabner.
This
wasn't
consistently
used,
for
example,
when
you
did
the
configure
monitoring
the
energize,
conf
yaml
was
simply
not
used,
and
so
you
probably
have
configured
against
wrong
dyna
trace
tenant,
and
this
pull
request
also
closes
this
issue
yeah.
H
H
The
first
one
is
enabling
highlighting
in
the
heat
map,
so
the
issue
we
had
was
that
in
the
heat
map,
you
see
the
comparison
of
several
evaluation
events,
and
previously
you
had
no
idea
yeah,
which
one
is
the
currently
selected
one.
So
now
we
have
a
highlighting
here.
Actually
I
will
show
you
a
live
demo
because
yeah
we
changed
some
colors
here
of
the
highlighting
because
it
was
not
for
all
use
cases
perfect
and
the
second
one
is
rework
of
the
evaluation
tile
itself.
C
G
H
To
show
you
a
live
preview
of
the
rework
now
so
now
you
first
of
all
see
the
heat
map
on
top,
where
you
can
now
also
see
the
selected
or
you
see
which
evaluation
is
the
currently
selected
one,
and
then
you
see
all
the
details
about
the
selected
evaluation,
also
with
the
criteria,
for
example,
for
past
and
warning
in
this
case,
when
we
have
a
look
at
the
slo
file,
we
have
the
criteria
that
90
is
passed
and
50
is
warning.
So
for
this
case
we
have
the
result
warning.
H
You
also
see
the
evaluation,
time
frame
and
some
more
information.
For
example,
we
have
also
the
info
here
that
we
convert
with
the
last
past
evolution
also
in
case
that
we
have,
for
example,
configure
to
compare
with
several
evaluations.
So
in
case
the
sli
breakdown,
the
slis
are
compared
with
several
evaluations.
H
D
C
D
F
H
D
H
F
H
F
Thank
you
all
right
so,
as
andreas
has
already
well
I'd,
say
teased
and
not
spoilered.
In
this
case,
we've
implemented
a
travis
ci
task
that
verifies
our
helm
chart
in
this
case
for
the
latest
and
for
the
release
installer,
it's
a
very
easy
call
to
help
template
and
with
the
minus
minus
debug
flag
it
it
basically
passes
the
template
and
doesn't
really
process
it
in
the
sense
of
that
it
installs
it
on
a
cluster,
and
if
that
has
any
error
in
it,
we
just
echoed
it.
F
It
has
an
error
exit
with
a
one
and
by
exiting
with
a
one,
the
travis
script
fails
and
yeah,
so
that
kind
of
should
prevent
us
to
commit
or
to
to
push
invalid
helm
charts
in
the
future.
I
hope
we'll
see
it
definitely
helped
us
in
in
debugging
the
help,
charts
and
find
out
what's
wrong,
and
the
other
issue
I
worked
on
is
this
spark.
F
F
F
F
All
right,
the
other
issue
I
worked
on
is
a
bug
and
improvement.
At
the
same
time,
when
you
call
captain
generate
support
archive-
and
let's
say
you
have
captain
installed
in
a
different
name,
space
then
kept
the
support
archive
would
present
you
an
error
message,
but
no
guidance
on
how
to
fix
it.
Also,
sometimes
the
idea
was
like
what
what
happens
if
you're
not
connected
to
a
kundalinist
cluster
at
all.
F
You
need
to
have
a
better
error
message
and
in
fact
we
do
have
like
in
the
captain
install
command
and
the
cap,
none
install
command.
We
do
have
a
functionality
that
asks
us
if
this
is
the
correct
cluster
that
we're
connected
to,
and
we
also
added
this
as
something
to
ask
the
user
before
we
generate
the
actual
support
archive
and
here
in
the
pull
request,
I've
copied
the
results
that
I
implemented
as
a
demo.
So
if
you
call
generate
support
archive,
it
will
tell
you
hey.
Is
this
the
correct
cluster?
F
But
obviously
this
is
the
error
message
that
the
library
is
printing,
and
this
is
the
error
message
that
that
I'm
then
printing,
like
please
reach
out
to
your
administrator
to
get
a
connection
to
the
kubernetes
cluster.
So
I
I
to
be
honest.
I
don't
like
this
part
very
much,
especially
after
after
I've
seen
what
andreas
has
done
to
the
dynatrace
service.
D
D
I
D
That
is
a
pretty
nice
feature
that
allows
you
to
tag
fine
address
services
with
a
with
a
captain
service
tag
and
also
with
the
the
default
captain
manage
tag
and
when
a
dandruff
service
has
this
tags
on,
then
the
integration
that
address
captain
integration
will
take
this
information
to
create
a
captain
service
based
on
that
one
based
on
that
information
yeah,
and
it
also
will
upload
a
default
slo
for
this
service,
which
will
then
cover
their
cellos
for
a
response
time.
Cpu,
throughput
and
failure
rate.
H
D
G
F
D
C
G
G
H
F
G
D
F
Yep
so
supratek,
who
is
in
the
call
here,
has
suggested
this
on
slack.
I
think
and
he's
posted
the
issue
just
a
couple
minutes
ago,
and
was
he
asked
that
he
he's
assigned
to
the
issue,
so
I've
just
quickly
done
that
basically
and
he's
made
a
valid
point
there.
Our
make
file
is
empty
right
now
and
well.
Let's
fill
it
with
some
content
like
using
gofund
linting,
the
code,
preparing
things
for
a
pull
request,
etc.
F
D
Okay,
then,
let's
jump
to
the
back
clock
here.
I
have
one
issue
that
is
to
some
extent
also
related
to
a
dynadress
integration.
It
is
about
enabling
and
disabling
a
feature
or
features
within
this
integration.
There
is
already
a
ongoing
discussion
and
two
days
ago
there
also
have
been
a
summary
of
what
has
been
discussed.
D
F
F
I
could
probably
also
keep
talking.
The
next
issue
is
also
a
dock
issue,
listing
all
installation
option
that
we
have
in
our
help
chart-
or
at
least
all
that
are
relevant
for
the
user,
because,
like
we
have
the
prefix
path
for
helm,
we
have
the
option
to
enable
or
disable
continuous
delivery
which
will
install
helm
and
jmeter
and
so
on.
We
have
the
api
gateway,
nginx
service
type
that
we
can
configure
and
with
captains
with
the
updates
of
captain's
bridge
that
we
saw,
I
think,
in
in
last
week's
community
meeting.
F
We
also
have
like
the
download
url
for
the
cli
and
some
other
feature
flags
for
captains
bridge.
They
can,
in
theory,
all
be
controlled
via
the
helm,
chart
values.yaml,
but
this
is
obviously
not
documented
right
now
and
yeah.
So
I
propose
that
we
document
this
and
also
I've
pinged
andreas
kimmer
on
this
issue,
because
he
might
know
some
more
installer
options
that
we
could
document.
C
F
D
You
cool
and
then
yeah
the
last
one
that
I
have
prepared
is
actually
preparing
also
the
documentation
for
the
0.72
release,
but
this
is
more
or
less
amid
the
issue
of
issues
that
are
also
addressed
by
other
topics
by
other
issues.
I
just
wanted
to
summarize
what
needs
to
be
checked
and
and
verified
before
we
go
online
with
the
new
documentation.
D
F
That
consists
of
many
many
many
many
many
many
many
bullet
points
that
we
need
to
work
on
for
the
release,
which
is
mainly
because
we
have
a
mono
repo
and
we
have
so
many
micro
services
that
need
to
be
released
and
need
to
be
checked,
and
we
would
like
to
invite
people
to
help
us
with
the
process.
So
basically
there's
a
step
list
and
what
this
requires
is
usually
the
right
access
to
the
git
repository.
So
if
anyone
is
willing
to
help
us,
we
can
obviously
invite
them
with
right
access
and
yeah.
F
If
you
just
want
to
go
over
the
list,
it's
in
our
wiki
on
github.comwiki
and
if
you
are
willing
to
take
any
of
these
just
hit
us
on
slack
and
we
will
get
something
worked
out.
Also,
we've
added
the
automation
wanted
yeah
flag
on
some
of
these.
So
if
you
are
good
with
automating
such
tasks,
just
let
us
know
and
feel
free
to
help
us.