►
From YouTube: Keptn Community Meeting - June 4th, 2020
Description
Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit#heading=h.1070l61b3zho
June 4, 2020
Good first issues: https://goodfirstissue.dev/ or start here
Keptn mailing list / google group: https://groups.google.com/forum/#!forum/keptn
Noteworthy Issues & PRs (Review)
Christian K.:
Remove “fixed host header” api.keptn: https://github.com/keptn/keptn/pull/1854 and https://github.com/keptn/go-utils/pull/160
Release of Dynatrace SLI Service 0.4.2 (Main Author: Andi Grabner)
https://github.com/keptn-contrib/dynatrace-sli-service/pull/57
Florian:
Delivery Assistant for CLI: https://github.com/keptn/keptn/pull/1865
Fixed ‘configure domain’ command for installations with NodePort gateway https://github.com/keptn/keptn/issues/1796
Ermin:
Display service out-of-sync info https://github.com/keptn/keptn/pull/1877
Andreas:
Provide scaling remediation action in Helm-service: https://github.com/keptn/keptn/issues/1817
Fix access of configuration-service: https://github.com/keptn/keptn/issues/1861
Correct request approval: https://github.com/keptn/keptn/pull/1875
Johannes:
Creating a project with Git up-stream is the recommended approach: https://github.com/keptn/keptn.github.io/issues/550
Christian H.:
CLI: Implement get projects, services, stages https://github.com/keptn/keptn/pull/1811
Roadmap → KEP / SPEC / Issues:
KEP 09 - Spec change of remediation action config
SPEC 31 - Implementation of spec change as proposed in KEP 09
#1848: Keptn Core (MongoDB/configuration-service): Manage open remediation workflows in the materialized view managed by the configuration-service
#1849: Keptn Core (remediation-service): React on problem.open and process predefined workflow: trigger action, wait, evaluate, continue remediation or send a remediation.done
#1846: Testing: Platform/integration test for self-healing use case
#1847: Testing: Integration test for use-case of scaling a pod based on a Prometheus alert
SPEC 30 - Add ProblemURL as optional field to problem.open event
#1694 Add ProblemURL to the keptn problem events
Work in progress:
https://github.com/keptn/keptn/projects/29
Backlog Refinement / Next Sprint:
see 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
Attention: new date for upcoming community meeting
Wednesday, June 10 (!)
All subsequent meetings will be again on Thursdays
Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
B
B
A
C
A
Captain,
let's
just
search
for
captain,
you
will
find
an
entry
for
captain
and
it
will
list
the
last
couple
of
good
first
issues,
so
I
think
by
default
its
maximizes
to
ten
issues.
So
you
can
take
a
look
here.
So
that's
one
of
our
efforts
to
help
the
community
getting
started
with
captain
if
you're
interested
and
if
you
want
to
take
a
look
at
full
list,
we'll
also
link
it
here.
So
you
can
find
this
document
on
our
github
site
gives
up
a
comm,
slash,
captain
slash
community.
A
C
A
Get
started
and,
of
course,
it's
joining.
These
kind
of
meetings
is
always
a
good
start,
because
you'll
get
directly
in
touch
with
the
developers.
You
can
ask
the
questions
and
get
started
with
contributing
to
captain
another
thing
that
we
set
up
for
us
to
make
it
easier
to
reach
out
to
you,
but
also
for
you
to
stay
up
to
date
and
get
all
the
news
and
updates
and
announcements
and
questions
directly
into
your
inbox
without
having
to
sign
up
for
let's
say,
slag
or
any
other
external
tool.
We
have
created
a
Google
group.
A
So
if
you
go
to
this
group
group,
you
will
find
already
a
couple
of
entries
in
this.
It's
basically
a
mailing
list
and
if
you
sign
up
for
it,
I
think
for
you,
there
might
be
a
button
for
sign,
sign
up
or
join
something
like
this.
Then
you
will
just
receive
those
emails
and
you
can
decide
if
you
want
to
have
them
like
monthly,
weekly
or
like
regularly
or
as
the
media
as
the
announcements
come
out.
A
So
for
you
to
decide
how
often
you
want
to
get
informed
about
captain-
and
that's
pretty
handy,
you
interest
the
creator
talking
here
and
ask
questions.
If
there's
more
than
one
on
one
discussion
or
back
and
forth
discussion,
then
we
might
take
it
over
to
slack
but
feel
free,
also
to
use
this
form
of
communication
with
the
captain
team
and
also
to
reach
out
to
us
via
the
Google
Group
and
by
the
mailing
list.
So
with
this,
these
were
two
very
short
announcements
for
the
captain,
community
and
I.
A
Think
with
this
I'm
handing
over
to
Christian
to
discuss
some
noteworthy
issues,
NPR's
thanks,
Ian,
so
yep
should
be
able
to
see
my
screen.
I
have
two
things
to
mention
today
and
basically
the
first
one
is
not
quite
refactoring
in
terms
of
code
refactoring,
but
in
terms
of
architecture
refactoring,
we
used
to
have
the
host
header
set
to
API
dot,
captain
for
many
of
our
requests
that
we
made
with
the
captain
API,
and
we
basically
removed
that.
A
So,
as
you
can
see,
it's
only
like
removing
that
line
of
code
here
and
we've
removed
that
in
go
utils
as
well
as
within
captain
itself.
In
captain
itself,
this
was
removed
in
some
go
code
in
llamó
file
that
manages
the
captain
ingress
manifest
and
in
the
installer
for
open
shift.
We
also
had
like
a
second
route
for
a
pirate
captain
that
essentially
I
think
you
can
go
to
the
issue
itself
as
well
yeah.
A
Essentially,
this
means,
if
you
access
captain
by
a
normal
means,
so
that
would
be
your
domain.
For
instance,
then
the
host
header
is
automatically
set
by
your
HTTP
client
library
to
this
name,
and
we
don't
need
to
override
it
manually
and
if,
for
whatever
reason,
you
need
to
override
it
manually,
if
that's
still
the
case,
obviously,
then
that's
a
different
story,
but
for
a
default
installation
that
would
be
the
default
installation
options
that
this
host
header
and
everything
works
and
that's
how
HDB
works
and
has
worked
for
years
so
yeah.
A
Essentially,
let
me
check.
Yeah
I
can
actually
just
check
the
release,
notes,
we're
improving
logging
a
little
bit
for
fetching
secrets.
We
have
fixed
an
issue
when
actually
it
wasn't
an
issue,
it
was
a
read
media
documentation
issue,
but
we
fixed
the
documentation
regarding
the
format
of
the
secrets
that
we
use
for
dynaTrace.
We
fixed
an
issue
with
character,
encoding
I
think
that
yet
is
an
issue
link
there.
A
Also,
we
had
a
check
for
T
and
time
and
basically,
when
you
do
a
start
evaluation-
and
you
have
the
end
time
set
in
the
future-
maybe
not
on
purpose
but
by
accident,
because
your
local
client
PC
is
maybe
two
seconds
in
the
future
or
whatever.
Then
the
dynaTrace
is
why
service
would
have
returned
and
ever
we
have
removed
that
now,
because
maybe
it
is
a
client
configuration
issue
or
whatever.
But
we
can
handle
this
in
a
much
nicer
way,
because
we
can
just
wait
until
the
end
time
has
passed.
A
A
B
Yeah
all
right
well,
the
first
thing
I
want
to
show
you
today
is
the
deliberate
assistant
for
the
captain
CLI.
So
what
is
that?
So?
If
you
recall
from
previous
meetings,
I
showed
you
how
to
use
the
CLI
to
first
retrieve
all
open
approval
events
from
the
captain
API
and
then
use
the
CLI
to
approve
them
using
the
idea
of
the
respective
approval
event.
B
It
will
again
fetch
all
the
open
approvals
and
then
list
them,
as
you
can
see
here,
see
for
each
open
approval,
universe,
optioned
and
image
tag
that
used
to
be
approved.
For
that,
so
this
entity
will
also
have
the
result
of
the
evolution
that
has
been
calculated
by
the
nikon
service.
After
that,
the
sea
like
world
interactively
ask
you
to
provide
an
option
which
approved
you
want
to
approve,
and
you
can
select
that
and
then
it
can
either
choose
to
approve
or
to
decline.
B
B
All
right,
if
not
I,
would
like
to
proceed
with
the
second
issue.
I
want
to
discuss,
so
this
one
was
hurt
when
actually
that's
wrong.
This
one
was
about
that
occurred
when
you
execute
executed,
captain
configure
the
main
in
an
installation
worried
about
the
Gateway
set
to
a
note
board.
So
let
me
just
issues
twisting
has
already
provided
the
very
nice
summary
of
the
problem.
B
So
basically,
when
you
execute
it,
captain
configure
the
main
port
you
weren't,
able
to
talk
to
the
API
or
the
CLI
wasn't
able
to
talk
to
the
API
anymore,
because
North
Port
hasn't
been
set
correctly
in
the
config
map.
That
holds
the
required
configuration
for
Eli
to
work
correctly,
and
that
has
not
been
fixed.
E
Thank
you
very
much,
Robin
I'm
planning
to
present
you
some
improvements
in
the
bridge
today.
It's
this
place
service
out
of
sync
info
in
the
environments
screen,
and
yet
the
requirement
here
is
always
to
show
the
information
that
the
service
is
out
of
sync
and
to
display
the
deployable
artifacts
for
that
service.
So
when
there
is
an
open
approval
for
several
versions
or
for
at
least
one
version
of
a
service,
then
currently
we
display
that
information
into
the
environment
screen
and,
of
course,
I
will
do
a
short
live
demo.
E
So
when
you
click
on
the
environment
screen,
currently
you
saw
there
there's
a
chests
and
the
deployed
services,
and
now
you
also
have
a
overview
about
problems,
evaluation
and
open
deployments
in
that
stage,
and
when
you
click
on
a
specific
stage,
then
you
see,
on
the
right
hand,
side
the
list
of
all
the
services
and
also
the
information.
For
example,
with
this
blue
icon,
you
can
see
that
the
card
service
has
a
deployable
artifact.
E
That
is
out
of
sync.
So
the
next
step
here
would
be
to
do
a
manual
approval,
also
from
the
bridge
for
this
functionality.
I
will
have
to
leave
this
poor
request
actually
open
until
the
changes
to
the
public
API
are
also
merged,
and
he
also
will
be
a
slight
change
necessary
in
retrieving
this.
The
list
of
deployable
artifacts
to
make
sure
that
the
list
is
the
same
as
you
see
in
the
CLI.
E
Evaluation
triggered
events
yeah.
We
will
change
that
as
well.
Here,
that's
important,
also
because
yeah,
based
on
a
discussion
with
johannes
that
I
started
just
a
couple
of
minutes
before
this
presentation.
There
might
be
a
point
that
we
have
rollback
on
a
specific
stage
and
also
open
approvals
and
yeah.
That
logic
should
be
shifted
to
the
api
when
an
open
approval
should
be
yea
dismissed
from
that
list.
A
E
Yet
the
current
version
of
the
bridge
is
in
development,
so
this
will
be
available
with
the
release
of
0-7,
but
we
will
provide
at
the
end
of
next
week
and
yet
a
piece
on
early
access
preview
of
the
bridge,
but
I
think
this
feature
that
I
presented
right
now
will
not
be
in
that
EAP
version
yeah,
but
some
other
features
will
make
it
there.
Yeah.
A
That's
correct,
so
we
have
a
lot
of
bug,
fixes
and
smaller
improvements.
That
I
mean,
as
shown
over
the
last
couple
of
weeks.
They
will
be
in
their
early
access
version,
but
what
you're
seeing
here
is
basically
part
of
this
delivery
assistant
use
case
that
we're
working
on
it.
It's
obviously
a
breaking
change
and
it
won't
work
with
your
old
captain
version.
So
yeah
we
will
only
provide
an
EAP
that
is
still
compatible
with
0-6
Thank
You.
Having
the
answers.
The
question
thanks:
yeah.
D
So
I've
worked
on
a
preparation
task
for
the
closed-loop
remediation
and
the
task
was
to
move
on
remediation
actions
which
are
currently
implemented
in
the
remediation
service
to
dedicate
that
service
and
I
took
care
of
the
scaling
action
and
this
scaling
action
has
to
be
implemented
in
the
Health
Service
open.
This
issue.
D
D
The
second
issue
was
effects
for
for
our
commute
ins,
so
we
provide
in
our
commuters
utility
functions
for
accessing
the
configuration
service,
and
we
here
have
to
differentiate
better.
The
request
is
coming
from
the
API
from
the
outside
or
from
the
send
captain
and
depending
on
where
the
request
is
coming
from.
We
have
to
to
change
the
URL,
and
this
was
fixed
with
this
PR.
D
Basically,
when
you
are
using
an
authenticated
project
handler
yeah
I
am
assuming
now
that
you're
accessing
from
the
outside
and
advice
from
with
some
captain.
So
this
was
the
second
one
and
finally
I've
corrected
a
small
part.
In
the
request
of
approvals,
you
detail,
if
you,
for
example,
have
defined
an
approval
strategy
defined
in
the
staging
stage.
The
first
step
which
should
be
executed
is
requesting
this
approval
and
if
you
have
a
look
at
the
approach,
you
can
see.
F
F
Because
captain
does
not
does
not
provide
a
backup
of
your
git
repository
and
the
only
way
so
to
say
is
the
upstream
repository
that
then
works
as
a
backup
worried
for
you
and
now
I
did
an
update
of
the
documentation
to
make
it
clear
that
the
recommended
approach
is
to
set
up
get
upstream
and
just
for
a
demo
or
lab
environment.
It's
okay
to
create
a
project
without
backup
yeah
provided
by
an
upstream
you're.
Gonna
think
this
is
also
important
for
the
tutorials,
because
we
should
at
least
mention
a
note
there.
F
C
A
C
F
C
C
The
end
it
was
florian
gave
me
an
example
for
the
plural
entity
stuff,
and
I
I'm
good
and
copy
and
pasting
so
I
covered
in
places
and
adapted
it
for
the
for
the
other
three
or
two
remaining
things
here.
You
can
see
the
aliases
command
line
43
and
then,
because
of
the
sona
type
here,
what
it's
called
the
code
coverage
report
where
you
have
to
duplicate
findings,
to
avoid
this,
when
it
can
scroll
a
little
bit
more
down.
I
have
time
yes,
so
I
have
here.
C
C
Output,
I
just
have
here
implemented
a
little
if
statement
if
the
project
needs
to
be
printed
out
or
not.
If
there
is
some
project
name
given
in
the
command-line
arguments,
it
should
print
out
the
project.
If
the
project
name
is
as
not
passed
over
as
the
command-line
argument,
it
should
print
out
all
projects
and
if
not,
it
should
print
nothing
out,
and
the
same
is
for
really
services
second
service.
C
In
the
end,
it's
the
same
for
services.
If
service
name
is
set
and
it's
matching,
then
it
should
print
out
service
and
if
not,
there's
a
service
name,
it's
that
when
the
project
name
is
a
matched
and
it
will
print
out
the
services,
all
the
services
for
the
project
and
if
no
project
name
and
no
service
name
is
set,
then
it
will
return
all
services
from
captain
which
are
on
board.
A
F
F
The
implementation
of
the
remediation
edge
configuration
that
we
are
now
going
to
support
in
ordered
seven
and
last
time,
I
mentioned
that
a
couple
of
github
issues
needs
to
be
clarified
and
created,
but
now
we
we
worked
on
them
and
they
are
well-defined
now
and
you're
in
the
backlog
refinement.
We
can
then
take
a
look
on
those
issues
that
we
can
then
talk
about
that,
and
this
brings
me
directly
to
the
work-in-progress
items.
F
F
B
B
B
B
B
F
A
C
B
A
I
agree,
like
suggestion
that
we
can
keep
some
issues,
and
next
week
is
a
short
week,
at
least
in
Austria,
because
we
have
a
public
holiday
and
then
so
in
two
weeks
time,
like
the
the
weekly
meeting
comes
quite
quite
fast,
because
it
will
be
only
three
to
four
hour
work
days
or
days
next
week,
so
we
can
keep
some
of
those
and
then
may
be
presented
in
two
weeks
time.
If
it's
interesting
yeah,
it's
fine
like
the
person
can
decide
whatever
they
want
to
present
it
or
not.
F
B
E
E
We
have
already
a
review
for
that
also
and
it
could
be
merged,
but
we
will
wait
at
least
one
week
yeah
with
that
one
and
the
second
one
is
the
implementation
of
unit
tests
in
the
bridge,
so
I
provided
some
unit
tests
made
the
basic
set
up
and
also
some
unit
tests
in
the
bridge.
There
is
an
open
pool
request
that
needs
to
be
reviewed.
F
A
A
E
F
Well,
then,
on
to
my
issue,
its
documentation:
how
to
reset
the
captain
API
token
I
have
provided
the
documentation,
but
I
forgot
the
Windows
folks
out
there
and
the
commands
to
create
a
token
on
a
Windows
machine,
but
I
added
this
those
instructions.
And
now
this
pull
request
is
ready
to
get
reviewed.
F
Okay,
then
we
can
go
on
to
the
next
column.
It's
the
column
of
issues
that
are
assigned
and
committed
I
think
we
don't
need
to
go
through
those.
Just
one
note
Thomas
mentioned
that
he
will
find
time
to
work
on
this
issue
on
next
week
because
he's
very
busy
right
now,
but
he
told
me
that
next
week
he
can
work
on
that.
One.
F
All
right
yep,
then,
let's
jump
over
to
the
backlog
and
to
talk
about
the
issues
that
are
ready
to
get
started
the
first
one.
It's
a
kind
of
preparation,
work
for
implementing
the
remediation
use
case
very
similar
to
what
we
did
with
the
approvals
where
we
now
store
open
approvals
in
a
materialized
view.
We
also
now
need
to
store
remediation
actions
that
got
triggered
and
are
still
going
on.
F
We
need
to
store
them
also
in
a
materialized
view,
just
open
that
one
for
a
second
yeah
it
is
specified
what
what
need
to
put
need
to
be
implemented.
It's
all
about
retrieving
the
remediation
tour
triggered
events,
then
storing
them
and
whenever
remediation
finished
comes
in,
then
we
close
and
open
remediation
yeah
in
the
materialized
view.
F
F
F
Well,
don't
want
to
read
out
this
specification
because
it's
it's
lengthy
and
I,
don't
want
to
waste
your
time,
but
we
have
prepared
a
very
well
defined
event
stream
for
implementing
the
remediation
workflow.
It's
explained
in
this
issue
and
then
our
thanks
to
andreas
who
specified
and
clarified
a
couple
of
scenarios.
F
We
talked
a
lot
about
splitting
this
issue
into
multiple
sub
elements,
but
this
was
actually
not
really
useful
because
there
are
it's
just
one
implementation
and
we
we
could
not
find
meaningful
or
a
point
where
a
split
makes
makes
sense.
This
is
the
reason
why
we
still
consider
it
as
as
this
one
very
big
issue
who
is
going
to
take
that
one?
F
C
F
Info
button
in
the
bridge
that
tells
the
user
that
then,
for
example,
EAP,
is
there
it's
available
and
then
there
should
also
be
a
direct
download
link
or
a
link
to
the
documentation.
That
then
explains
the
user,
how
to
install
the
EAP
version,
and
the
same
is
true
for
any
update
on
on
captain
itself.
In
other
words,
when
I
kept
note,
7
should
is
available,
then
use
the
user
should
get
notified
about
that.
F
This
issue's
also
explained
here
what
we
are
going
to
introduce
is
the
user
icon
on
the
top
right
corner,
the
user
I
can
stay
user
menu
and
also
the
captain
version,
as
well
as
the
version
of
the
bridge
should
be
displayed
in
this
user
menu
and
then
on
the
bottom
of
this
menu.
You
get
the
option
to
turn
on
or
turn
off
this
feature
and
patterning
it
on
a
daily
check
will
then
verify
whether
your
bridge
is
on
the
latest
version
or
a
new
one
is
available.
F
That's
a
good
question.
Yes,
we
plan
to
also
show
earpiece
there,
because
what
what
need
to
be
done
is
that
here
and
there
is
a
configuration
stored,
that
that
lays
out
which
version
is
VP
and
a
stable
one
and
also
for
an
EP.
We
just
have
to
mention
it
here
and
then
the
daily
version
check
will
figure
out
whether
Yippies
are
there
and
what.
C
I
mean
with
it
is
just
that
I
can
select
if
it
will
show
the
if
there
isn't
so
just
show
me
some
new
version
information
if
I
want
to
have
stable
versions,
updated
or
AP
versions
as
well
like
and
other
tools.
I
can
select.
Ok,
give
me
all
updates
from
stable
channel
or
key
we've.
All
update
from
stable
and
development
like
this.
F
F
C
A
So
many
tools,
as
christine
has
already
mentioned-
we
would
use
the
term
channel
for
that
there
would
be
a
release
channel
or
a
stable
channel,
rata
and
I.
Don't
know
EAP
channel
and
alpha
channel.
Maybe
so
maybe
it's
not
just
a
toggle
button,
but
maybe
it's
a
drop-down
or
check
box
or
check
box
whatever.
F
A
Because
alpha
in
our
case
could
be
our
nightly
builds
so
to
say,
if
anyone
really
wants
to
be
informed
about
that.
I
I
doubt
that,
although
at
least
at
the
current
state,
but
maybe
in
the
future-
and
the
EAP
version
would
be
something
we
can
tell
the
use
of
wire
our
version
dot
Jason
that
there
is
a
new
version
for
the
EAP
Channel
I.
A
B
F
C
F
A
If
you
can
open
that
issue
and
the
Travis
CI
link
in
that
issue,
basically
integration
tests
are
failing
for
some
days
now
again,
and
it's
also
blocking
me
as
I'm
working
on
some
other
integration
tests,
so
I
guess
I
will
take
it
anyway.
I've
triggered
the
test
a
little
bit.
If
you
can
scroll
down
so
they're
failing
on
Chiqui
right
now,
but
mini
shift
and
micro
communities
seem
to
be
working
manually
started
them.
A
A
Think
if
you
go
back
to
the
issue,
I
didn't
add
much
information
in
it
other
than
to
the
Travis
share,
link
and
the
definition
of
done,
and
basically
it's
to
fix
the
integrate
tests
and
to
also
improve
the
logging
of
the
integration
tests,
because
it's
really
hard
to
find
out
why
a
test
is
failing
right
now,
as
I
said,
like
the
mini
shift,
the
test
is
working,
but
the
full
test
before
boarding
is
not
working.
So
it's
probably
something
with
the
onboarding,
but
it's
not
like
open
the
Travis
CI
page
and
find
out
what's
wrong.
A
Yeah
almost
I
can
do
it
anyway,
so
maybe
I
can
also
talk
about
the
next
one
allowed
to
specify
an
upstream
gift
for
existing
projects.
So
right
now,
if
you
can
open
the
issue
right
now,
if
you
create
a
project,
you
have
the
choice,
to
not
use
the
git
user
and
give
token
and
to
get
remote
URL,
and
this
obviously
would
assume
that
you
might
be
able
to
update
the
project
and
set
the
get
user
token
a
remote
URL.
A
Afterwards,
we
don't
have
that
functionality
right
now,
but
there
are
many
many
issues
that
come
with
that
and
being
able
to
update
the
project
with
that
configuration
is
it's
a
major
thing?
It
shouldn't
be
too
hard
to
implement,
but
it's
really
really
important
to
have
it
yeah.
The
project
name
would
be
good
to
you.
So
basically,
what
we
need
is
CLI
command
to
update
the
project.
We
already
have
create
and
delete
project,
so
we
can
also
update
the
project.
A
That
is
what
we
have
to
do
in
a
CLI
and
I.
Think
if
you
scroll
down,
we
have
yeah.
We
have
the
tasks
on
how
to
implement
it
or
what
we
think
is
a
good
way
to
implement
it.
We
first
of
all,
as
if
you
update
the
repository,
the
target
repository
aptitude
is
empty
so
similar
to
what
we
had
with
create
project.
A
We
need
an
empty
repository
and
we
believe
that
it
should
be
enough
to
just
copy
the
code
from
the
create
project
parrots
of
the
CLI
of
configuration
service
and
go
utils
and
to
implement
the
update
project
method
in
there.
So
it
should
be
very
similar
to
create
project
and
an
important
message
here
that
we
have
in
a
last
line
here.
It
will
not
be
possible
to
update
the
shipyard
with
that.
It's
really
just
for
updating
the
git
remote
repository
configuration
and
not
the
content
of
the
repository.
A
C
A
A
A
F
A
Also,
we
are
happy
to
know
how
other
projects
deal
with
role
based
access
control,
so,
like
nuts
will
use
some
role
based
access
control
issue
will
do
it,
etc
and
yeah
we're
happy
to
get
to
know
how
I'd
approach
its
deal
with
that.
So
we
don't
want
to
make
like
our
own
little
universe.
Here.
I
can
do
the
research
cool.
F
D
A
F
B
F
F
A
D
F
F
A
A
We
will
be
June
10th
and
then
other
following
all
the
other.
Following
meetings
will
be
again
on
Thursdays,
so
it's
just
next
week
it
will
be
on
Wednesday.
If
you
already
subscribe
to
the
captain
community
calendar,
it
will
be
updated
for
you,
so
it's
already
there
and
you
should
see
it
and
again
we
have
this
captain
mailing
list
now
out
there,
so
you
can
also
sign
up
for
the
mailing
list.
The
link
is
on
the
top
of
this
document
and
on
the
top
of
the
agenda
for
today.