►
From YouTube: Keptn Community & Developer Meeting - Feb 8, 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
Sign up to our newsletter: https://bit.ly/KeptnNews
A
B
Yeah
am
I
am
available.
B
We
are
using
so
many
meetings,
so
I
just
you
know,
make
different
background
to
different
meetings.
B
My
name
is
aish,
Sharma
and
I'm,
a
student
from
India.
You
know
currently
pursuing
competitions
degree
in
btec
and
I
love,
contributing
to
open
source
I
am
involved
in
various
communities
such
as
cube,
simplify
we
make
devs
and
all
currently
I'm
working
as
a
junior
developer,
evangelist
intern
at
Marico
and
yeah
I,
thought
and
really
excited
to
you
know
contribute
to
Captain
as.
A
C
Yeah
thanks
for
thanks
for
inviting
me
so
hey
everyone
and
I
am
bhavya
and
I
am
currently
in
my
third
year
of
college
and
I,
really
love
contributing
to
open
source
and
highly
involved
with
communities
like
Cube,
simplify.
We
make
devs
and
also
organized
virtual
hackathon
as
well,
and
currently
I
am
working
as
a
junior
developer,
evangelist
at
Marico.
So
yeah
thanks
for
this
and
looking
forward
to
involved
with
Captain
project
and
community.
So
thank
you
so
much.
D
A
A
A
A
We
are
awaiting
for
a
few
bug
fixes
before
we
do
the
official
release-
and
this
will
be
some
bug
fix
for
the
bridge,
some
for
the
installation,
because
we
notice
a
problem
when
you
want
to
use
a
prefix
path
in
your
URL
for
the
bridge
and
something
for
the
lighthouse.
As
soon
as
everything
is
has
been
merged,
then
we
can
push
the
trigger
for
the
next
release
for
the
lifecycle
toolkit
last
time.
A
I
promise
that
the
next
release
will
have
its
own
Helm
chart,
but
we
discovered
yesterday
in
the
technical
meeting
about
refinement
of
Captain,
Pam,
charts
and
operators
do
not
work
well
together,
a
lot
of
shortcomings
and
we
are
evaluating
how
we
can
solve
them
in
the
best
way
heads
up
or
a
bit
of
spoiler.
A
But
we
still
in
the
figuring
out
how
we
should
solve
this
problem.
More
details
will
follow
up
and
for
the
next
meeting,
maybe
we
can
do
a
show
of
The
Matrix
and
the
general
metric
server
of
Captain.
And
how
can
you
use
that
in
order
to
scale
up
your
workloads,
but
here
I
would
like
to
give
them
the
words
to
Brett
and
Thomas
for
G-Shock
I.
Think
Brett
I
see
you.
F
Yep
hi
everybody
I
thought
I
would
do
the
background
as
well
so
updates
for
gsoc.
We
had
an
issue
there's
only
two
org
admins
and
we
couldn't
I
was
trying
to
add
Thomas's
at
Edmond,
but
my
user.
F
There
was
a
bug
with
her,
so
we
actually
couldn't
submit
the
application
so
I'm
talking
with
support
at
the
moment,
Thomas
has
CCN,
so
I
will
get
back
to
you
as
soon
as
possible
with
that
so
I'm
going
to
talk
to
Stephanie,
who
runs
it
and
see
if
she
can
manually
injure
using
there
was
some
sort
of
yeah
bug
that
wouldn't
let
me
submit
it,
so
all
we
have
to
do
is
send
a
the
links
pages
that
we
made
in
the
captain,
Community
repo
and
then
the
number
of
mint
is
and
then
do
two
check
boxes
and
that's
it.
F
But
we
were
getting
issues
so
I'll
update
the
issue,
just
saying
the
problems
and
then
I'll
keep
everyone
updated
on
that
issue.
When
Stephanie
gets
back
to
me,.
A
F
So
we
have
around
three
ideas:
I
know
there's
more,
but
if
folks
can,
please
add
your
issues,
if
you
have
an
idea
that
you
want
it's
not
too
late,
we
can
keep
adding
it
because,
generally
the
gsoc
people,
they
will
take
another
two
weeks
to
even
look
at
this
page
anyway.
So
we
still
do
have
time
to
refine
it
and
make
it
better,
because
we
want
to
make
it
as
good
as
we
can
to
get
accepted
again.
F
A
A
Then
we
have
some
topics:
reorganization
of
this
document.
F
A
Into
that
is
pretty
hard
and
cumbersome
if
you
want
to
see
what
we
discussed
in
the
past,
so
my
suggestion
is
to
now
split
this
document
in
multiple
documents
and
have
one
per
year,
and
we
keep
alive
only
the
current
year
and
the
previous
years
will
be
stored
in
our
repository.
This
way
are
always
accessible
and
you
can
have
a
snapshot
of
them.
F
Yeah
I
think
it's.
We
just
have
to
be
careful
with
Google
how
they
index
the
documents,
because
sometimes
when
people
search
it,
the
old
ones
come
up
before
the
new
ones.
If
that
makes
sense,.
H
G
A
J
A
D
K
Yeah
now
we
could
create
issues
that
are
yeah
an
issue
in
the
community
for
the
community
meetings
for
2022,
and
you
could
have
a
link
to
the
Google
Doc.
If
that
would
help.
K
A
Okay,
red
so
Justin
Mike,
then
next
topic.
So
now
we
are
working
with
big
features
of
the
KL
team,
and
the
question
is
should
be
part
of
the
captain
announcement
proposal
as
a
tool
or
not
because
right
now
we
are
proposing
changes
to
klt
without
going
through
the
normal
process
of
enhancement
proposal
and
the
question
to
the
community
is:
should
we
go
over
this
I
would
say
yes,
because
it
makes
things
more
transparent.
A
We
can
get
more
comments
and
input
from
the
community,
but
beside
being
a
sub
project,
it's
not
necessary
that
we
do
that.
What's
your
opinion!
Now
it's
a
question
to
the
community.
What
would
you
like
to
see.
A
K
A
J
Just
to
clarify
here
we
had
a
I,
remember
a
discussion
a
while
ago
that
we
would
move
to
issues
rather
than
PRS.
Is
it
still
PRS
or
are
issues
acceptable.
A
A
A
A
K
Then
for
implementation
we
would
end
up
then
creating
an
issue
whether
yeah
the
work
of
that
yeah
yeah.
That
sounds
good
to
me.
I'll.
J
F
Like
there's,
probably
a
distinction
between
the
issue
cap
is
probably
more
like
a
strategic,
maintainer
or
someone.
That
knows
it
well
like
strategy
decision
over
issue,
whereas
you
know
spelling
mistake
in
repo
would
obviously
be
an
issue.
So
it's
not
saying
we
have
to
do
a
cap
for
every
single
thing,
but
it
keeps
more
like
strategic,
like
the
whole
solution
of
the
project
or
something
like
an
epic
level
and.
D
J
So,
basically,
for
those
new
to
the
project,
probably
issues
and
then
issues
would
generate
caps
but
like
the
discussion
on
issues,
would
then
become
caps.
Maybe.
L
A
PR
is
a
document
everybody
agreed
on
and
it's
a
fixed
State
versus
an
issue
where
people
can
start
commenting
again
and
then
it
suddenly
reopened,
and
you
are
not
100
sure
what
is
the
final
agreed
status
upon
because
because
it
can
change
with
with
a
git
commit
and
a
pull
request,
you
more
likely
have
a
defined
status
when
it
was,
and
also
when
it
started
through
the
rediscussion.
So
you
have
a
better
better
basis
to
agree
on,
and
people
are
more
on
the
same
page
rather
than
with
an
issue.
In
my
opinion,.
G
L
So
we
as
I,
took
a
look
at
the
user
management,
the
and
the
things
regarding
user
management
and
the
maintainer
file
and
who
is
a
maintainer
and
who
is
a
member,
let's
never
mind.
There
are
some
inconsistencies
regarding
who
has
access
where
and
in
which
type
of
way
they
have
access.
Can
you
open
the
issue
for
sharing
I?
Think
that
would
also
make
it
easier
a
little
bit.
L
L
And
then
there
is
also
the
the
the
level
where
it
comes
to
repositories,
because
just
because
you
are
in
as
a
sometimes
members
of
the
organization
who
have
not
hold
maintenance
status
can
be
maintained,
of
certain
repositories
or
of
certain
groups
of
repositories
and
within
this
proposal,
I
propose
so
I
suggest.
Also,
instead
of
handling
like
kubernetes,
is
doing
this
on
a
repository
basis
to
handle
this
on
repository
groups.
So
we
are
grouping
repositories
together
where
they,
where
it
makes
sense.
L
For
example,
everything
regarding
documentation
like
captain.github.io,
when
the
tutorials
will
be
a
docs
group
where
we
handle,
where
we
assign
people
to
this
documentation
group
and
also
for
klt
for
Captain
itself
for
operational
things
for
organizational
things
and
for
utils.
So
this
is
Justin
naive
proposal
from
my
side,
I'm
not
too
deep
into
the
code
repositories,
and
we
were
then
based
on
this
generated
configuration
where
people
would
be
aligned
to
different
organizations.
This
is
exactly
this
one
this.
L
This
is
how
the
how
the
klt
as
I
don't
know
how
to
calculus
configuration
would
look
like
when
we
do
not
add
additional
tooling
to
it.
So
it's
a
lot
of
manual
effort,
saying,
hey
maintainers
should
be
maintainer
of
this
and
that's
repository
when
you
scroll
a
little
bit
down.
We
also
see
then
special
groups
for
for
the
other
special
settings
for
this
group,
like
the
klt
or
the
Ops
thing
where
we
have
the
maintainers
and
the
approvers,
and
my
suggestion
in
the
next
phase
would
be
instead
of
having
this
one
configuration
file.
L
Where
we
add
the
members,
we
would
generate
Yama
merger
more
likely,
and
we
would
have
our
own
approach
where
we
would
have
one
directory
for
the
organization.
Then
one
directory
for
each
group
with
an
own
dedicated
yaml
file,
where
we
just
mentioned
the
reports,
the
approvers
and
the
maintainers,
and
based
on
that,
we
will
then
generate
our
configuration
with
that.
We
have
an
easy
way
to
handle
it.
We
have
a
git
Ops
way
to
assign
people
to
projects.
L
We
have
some
history
who
assigned
whom
to
which
project
as
a
maintainer
etc
and
who
is
an
owner?
Who
is
a
member
of
the
organization
with
yeah
with
a
kit
history
behind
that
to
easier
figure
out?
Who
is
a?
Who
is
why,
within
that
group
Etc
now
that
would
be
my
proposal
to
what
to
improve
the
membership
organization
within
the
community.
L
I'm
just
I'm
just
presenting
this
here.
There
is
this
issue,
as
mentioned
in
the
community
I'm
looking
for
feedback
well,
I
think
even
deciding
upon
this
within
this
meeting
is
maybe
too
early,
because
we
should
give
other
people
the
possibility
to
to
add
their
feelings
regarding
that
or
their
feelings
or
their
remarks
Etc.
So
please
provide
feedback
within
this
issue
and
we
will
revisit
this
in
a
week
or
so
and
think
about
it.
Maybe
there
are
errors,
maybe
misconceptions
from
my
side,
but
well,
let's
see
how
this
will
turn
out.
No.
A
Thanks
for
the
idea,
I
think
it's
great,
because
right
now,
I
also
a
bit
of
problems
adding
people
to
the
group
when
they
want
to
ask
for
membership.
Things
are
very
not
transparent
to
the
community,
because
they're
to
go
to
settings,
send
the
invitation
and
it's
not
visible
when
this
person
was
added
or
not,
it
happens
behind
the
scene
for
the
community,
and
this
will
make
things
very
transparent
and
also
we
have
the
possibility
to
track
when
people
when
were
added
to
that
specific
group.
With
that
specific
permissions.
L
They're
the
same,
but
the
counts
are
the
same.
It's
just
it
depends.
This
is
something
where
I
did
not.
So
there
is
this
beta
feature
currently
from
GitHub
with
the
with
the
access
tokens
on
the
organization
level
and
repository
level,
which
might
change
things
a
little
bit,
but
I
have
no
experience
with
that.
So
far,
so
no.
I
And
what
kind
of
is
it
just
a
token
that
we
use
to
actually
have
the
githubs
enabled?
So
what
what
does
periputus
itself
use
for
Access
permissions,
I.
L
L
D
I
F
I
I
guess
one
more
quick
note
about
this
is:
if
we
use
this,
you
would
have
to
use
this
like
it's
one
or
the
other.
You
couldn't
then
go
and
manually
update
a
repo
with
someone
else's
value
to
always
have
to
use
the
bot
instead,
because
when
we,
if
someone
does
it
in
kubernetes,
it
screws
everything
up.
L
K
We
have
time
I'd
like
to
since
we've
got
so
many
new
members
here
and
I
know.
A
lot
of
them
have
been
posting
to
slack
at
how
do
I
get
started,
etc,
etc,
and
we're
not
doing
it
trying
to
keep
up
with
all
of
them,
but
I
would
we
might
open
it
up
for
a
chance
for
people
to
ask
questions
and
get
help
and
this
sort
of
stuff,
and
then
it
will
be
recorded
for
the
next
person
who
comes
in.
We
can
tell
them
to
look
at
this.
A
Here
there
is
our
documentation,
and
from
here
you
can
read
about
how
Captain
works
and
all
the
shenanigans
behind
this
project
we've.
Also
the
captain
lifecycle
toolkit,
which
is
a
sub-project
of
the
captain
organization,
so
Captain
itself
was
meant
to
solve
pipeline
issues
and
automation
around
that,
and
instead
the
lifecycle
toolkit
is
a
brand
new
sub
project
that
we
just
recently
created
around
the
cubicle
North
America
of
last
year,
so
only
four
months
old,
where
we
want
to
support
more
the
cloud
native
deployment
of
application.
A
So
this
is
the
difference
between
the
two
projects
and
they
have
two
different
repositories.
Also,
one
is
the
captain
repository
for
the
main
project
and
the
other
one
is
the
lifecycle
toolkit
for
this
new
sub-project
and
yeah.
The
best
way.
A
How
to
start
is
to
read
the
two
individual
documentations
see
which
project
do
you
like
the
most
at
the
moment,
I
think
it's
pretty
clear
that
we
need
to
improve
the
documentation
part
on
the
lifecycle
toolkit,
because,
since
it's
so
new,
we
didn't
have
the
time
to
build
up
as
much
content
as
we
have
for
the
main
Captain
project.
A
We
have
for
Captain,
also
a
killer
Coda
tutorial,
so
you
can
play
with
Captain
interactively.
A
B
Yeah,
so
yesterday
I
was
you
know
going
through
that
pillar
called
integration
of
captain
and
I
was
trying
to
find
the
correct
position
in
the
wrapper.
B
Where
you
know,
I
can
make
some
prevents
in
the
killer
code
event,
because
in
the
in
the
last
field,
when
you
complete
the
pillar
code
tutorial
for
Captain,
there's
an
bug
so
right,
it's
it's
in
the
documentation
that
link
to
the
GitHub
issues,
it's
directing
you
to
the
home
page
of
the
guitar,
but
not
taking
you
to
the
right
link
where
you
can
create
a
new
issue
for
for
the
same
right,
I
was
really
trying
to
find
the
but
I.
Couldn't
you
know.
J
It's
it's
actually
still
on
afterl's
personal
account.
We
need
to
move
that
over
pretty
quick
to
to
one
of
the
captain,
repos
you're,
absolutely
right,
so
I'm
not
surprised,
you
couldn't
find
it
but
yeah.
If
you
ping
me
on
slack
after
this
I'll
show
you
where
you
can
raise
the
issue,
we're
actually
going
through
to
upgrade
that
to
version
1.1.0.
J
So
it's
it's
perfect
time
in
a
way,
because
we
can
do
all
of
this
up
at
the
same
time
and
make
sure
everything's
you
know
kind
of
tied
off.
While
we're
talking
about
killer
Coda,
you'll
notice,
we've
only
got
the
killer
coder
for
Captain
version,
one
or
the
the
main
Captain.
We
don't
have
a
tutorial
for
the
lifecycle
toolkit,
and
that
is
something
I'm
looking
for
someone
to
to
get
involved
with
and
actually
create.
Now
I
can
help
with
the
killer
code
aside
and
obviously
the
the
toolkit
but
I'm.
B
Foreign
ly
look
into
it
and
I'll
try
if
I
can
help
it
help
with
it.
Also
I
have
one
more,
you
know
issue,
but
since
someone
was
saying
so
you
just
can't
you
know
if
I,
if
I
get
time,
I'll
share
it
in
the
last.
K
Sadipta,
do
you
want
to
say
something
because
when
two
other
people
are
working
on
sort
of
getting
a
contributor's
guide
together
and
the
first
thing
is
there's
a
lot
of
ancillary
tax
technologies
that
you're
going
to
need
to
be
familiar
with
to
work
with
this?
And
do
you
want
to
say
where
you
are
with
that
said
dipto
and
where
people
could
see
what
you've
got
so
far,
Etc.
E
Yeah
for
that
I
have
created
an
issue
in
Captain
life
cycle
toolkit
so
that
we
can
aggregate
the
ancillary
Technologies
and
list
them
down
so
that
any
beginner
who
are
trying
to
start
learning
Captain
like
cycle
toolkit
are
kept
on
itself.
Then
they
can
learn
from
the
reference
and
I
am
everything
for
some
comments
on
that
issue.
I
will
mention
that
shortly
in
the
chat.
Okay,
if
you.
K
K
E
Yeah,
definitely
so
for
that
I
think
I
should
create
a
readme
file
and
add
that
to
the
repo
well.
E
K
Okay,
yeah,
because
we
don't
have
a
contributor
guide
set
up.
Do
you
have
any
guidelines?
It's
like
chicken
yeah.
You
know.
K
A
K
K
Depot
is
on
simply
might
be
ahead
of
some
of
you
he's
on
flag
too.
You
can
always
ping
him
and
ask
him
directly.
K
Does
anybody
else
have
any
questions?
Are
you
have
you
found
your
area?
Are
you
busy
finding
things.
B
Can
I
mention
one
more
issue
which
I
face
during
the
installation,
sure
sure
yeah?
So,
while
you
know
locally
implementing
Captain
into
my
system,
it
was
I
was
going
through
the
inspiration,
Doc
and
again,
if
I
just
copy
this
one
paste
it
in
the
chat.
So
I
was,
you
know
installing
the
Helen
charts
and
so
I
am
I'm,
just
aligned
with
Helen
as
well.
So
if
I
am
wrong
this,
this
made
the
correction
for
me
it
in
all
the
options.
B
Let's
say
for
load,
balancer,
not
load
of
Ingress.
It
asks
you
to
directly
install
Helen
Captain
repo
right,
but
it's
it's
not
installing
the
captain
repo
it's
going
to
the
next
step,
which
is
installed.
So
if
you
go
to
the
RT
Hub,
where
all
the
charts
are
being,
you
know
there
for
the
different
organizations.
So
there
are
two
steps.
First,
you
have
to
set
up
the
repo
and
then
you
have
to
install
it
right.
B
I
I
might
be
wrong
here,
but
when
I,
when
I
ran
this
install
hello
installed
command
in
my
in
my
terminal,
it
showed
me
that
you
are
not
visualized
with
the
captain
repo,
then
I
went
to
the
RTF
I
installed,
I
initialized,
the
captain
repo,
and
then
this
command.
It
was
working
fine.
So
if
we
can
make
you
can
test
it,
I
I'm
since
I'm
a
big
man,
I,
might
be
wrong
here,
but
this
was
the
issue.
I
think
this
can
be
improved.
B
If
it's
generally
an
issue
again,
I
was
trying
to
find
this
file
where,
to
you
know,
change
it
or
just
trying
to
see
if
I
can
find
the
same
thing
in
the
repo,
but
I
was
unable
to
and
then
I
contacted
Brad,
but
he
was
even
think
so
now
I'll
get
in
touch
with
Adam
as
well.
For
the
same.
A
M
B
Can
I
arrange
these
two
issues
which
I
just
mentioned
sure
for
you
know
more
discussion
on
it.
A
K
Right
there
click
installation,
the
the
top
of
this
section
over
in
the
left,
I'm,
sorry
and
then
scroll
down.
This
is
this
is
a
problem
with
her.
There
is
here
the
full
list
of
what
you
need
to
do
to
install
captain
in
order
and
I
there's
a
slight.
It
needs
more
testing.
There
may
be
errors
in
it,
but
it
sort
of
tells
you
what
you
need.
What
you
should
do
in
what
order.
B
Yeah
I
was
following
this
complete
installation
process.
K
Okay,
yes,
we
would
like
to
have
issues
and-
and
then
suggest
you
know,
feel
free
to
submit
PRS
that
improve
things
and
and
small
PRS
they're
always
appreciated.
So
you
can
put
one
in
that.
You
know
fixes
a
small
thing
while
you
keep
going
on
and
you
don't
have
to
do
one
huge
PR
that
fits
that
fixes.
Everything
and
that's
will
be
good
work
for
you
to
do
actually
much
appreciated.
A
Okay,
then,
from
the
chat
I
see,
Amisha
provided
a
link
towards
this
ticket
prerequisite
issue.
A
B
When
you
go
to
the
installation,
part-
and
you
know,
go
for
the
create
and
bring
create
or
bring
a
community
cluster
right.
Just
this
I
wanted
to
ask
you
folks
that
openshift,
let's
say
if
I'm
using
Mac,
so
openshift
is
a
different
operating
system
to
work
on
or
we
can
use
openshift
on
Mac
as
well.
B
G
That
should
work,
yeah
I
mean
it
depends.
If
you
want
to
use
open
shift,
3,
11
or
4.x,
so
with
product
X,
you
need
to
use
code
ready
containers.
So
with
that
it
should
work.
I've
tried
it
out
a
couple
of
months
ago
with
openshift
3.11.
You
would
need
to
use
mini
shift,
but
since
that's
not
supported
anymore,
I
think
that
might
be
a
little
bit
complicated
to
set
up.
B
Yeah,
so
I
was
did
the
same
day
when
I
was
trying
to
install
it.
I
I
went
to
openshift,
but
it
didn't
work
for
my
system,
so
I
just
wanted
to
suggest.
If
we
could
do
something
like
this
in
the
in
the
Creator
being
a
kubernetes
cluster,
there
are
few
options
for
you
to.
You
know
bring
in
cluster
on.
A
B
A
M1
Mac
yeah,
then.
Unfortunately,
we
don't
support
that
because
of
bitnami
database
data
store
it's
what
we
use
as
a
database
and
it's
only
available
for
md64
architecture
and
not
arm.
B
Yeah,
so
so
this
this
can
be,
you
know
mentioned
in
the
in
the
documentation.
If,
if
it's
a
good
idea,
because
when
I
was
going
through
I
faced
an
issue
and
then
there
was,
you
know
in
this
small
hint
written
that
if
you
are
on
Mac
OS,
you
need
to
use
this.
Let's
say
for
k3s,
you
have
to
use
multipass
and
all
so
maybe
a
small
hint
for
the
for
the
folks
who
are
trying
to
install
or
the
newcomers
too.
You
know.
B
But
I
was
I
was
able
to
set
up
the
cluster
using
I,
think
a3d.
If
I'm
not
wrong,
did
I
did
I
set
up
here.
It
was
kt3
k3d.
B
So
maybe
we
can
have
a
separate
section
for
separate
section
for
different
operating
systems.
Let's
say
for
Mac
we
can
have
this
option.
K
B
M
A
Yeah,
this
is
something
that
I
discussed
this
morning
with
mag
yeah.
K
I've
got
to
go
look
because
Giovanni
did
a
rewrite,
he
actually
added
more
stuff
for
1.0
and
then
I
looked
and
it's
not
there.
So
I
need
to
go
back
to
PRS
and
see
if
I
can
find
out
what
happened.
A
B
I'll
get
along
with
Adam
and
see
if
more
things
can
be
done
right
for
creating
an
issue
and
I'll
discuss
it
in
the
represent.
Thank
you.
A
A
F
I
was
gonna,
say
cubecon
in
April.
Maybe
we
just
wanna
start
a
document
like
we
normally
do,
for
maybe
you
already
have
one
for
like
the
booth
and
talks
and
things
like
that.
H
I
think
there's
a
there's,
a
PR.
Sorry,
it's
not
a
PR,
sorry
an
issue.
One
thing
is:
we
are
still
waiting
for
the
confirmation
on
the
booth
I
think
today
or
yesterday
we
still
we
got
approval
that
there
will
be
a
con
trip
Fest.
So
basically
that
means
we'll
have
like
a
small
introduction
and
then
there
will
be
like
kind
of
this.
It's
almost
like
a
basically
90
minutes
of
hacking.
So
whoever
is
interested
or
that's
how
they
described
it.
H
Whoever's
interested
can
can
join
in
and
and
basically
we
try
to
resolve
some
tasks
together,
but
this
will
be,
let's
say
publicly
announced
in
in
the
next
few
days
and
also
then
the
topics
and
everything
else
will
follow
in
a
few
days
for
the
kiosk
I'm,
not
sure
when
it
will
be
announced,
but
as
soon
as
I
know
something
I'll.
H
I'll
yeah
I'll
put
it
in
the
the
agenda.
F
There
was
three
talks
accepted
this
year
really
into
kitchen
as
well.