►
From YouTube: Kyma SIG Core community meeting 20180912
A
Hello,
everyone
in
our
first
keema
Korsak
meeting
I
will
introduce
introduce
you
to
the
agenda
first,
and
we
have
some
points
here
and
the
first
one
I
will
talk
just
a
short
proposal.
Back
of
that
seek
then
Ralph
Hoffman
will
show
was
the
kima
kima's
vision.
Then
the
next
topic
will
be
presented.
Bio
category
needs
K,
which
is
the
overview
of
kima
project
in
github,
focusing
on
our
main
repositories
and
how
they
are
organized.
Then.
A
Maybe
four
for
that,
and
the
next
point
is
that
I
will
show
you
the
proposals
overview
in
our
seek
where
they
are
placed,
why
we
are
putting
them
there
and
what
they
are
about
and
at
the
end
of
course,
will
have
had
questions
and
feedback
slot.
Okay,
then,
let's
today
I
mean
the
moderator,
of
course,
and
Matias
talk
will
take
notes
and,
let's
just
go
with
their
proposed
in
the
comeup
project
organization.
In
the
community
repository
you
can
find
the
second
working
groups
directory
where
the
first
seeker
is
created.
A
Of
course
that's.
They
said
all
all
of
the
repositories
under
the
organization.
Besides,
the
community
belongs
to
the
Sikh
core
and
yeah.
That's
about
the
purpose
of
the
city.
Core
I
will
just
briefly
go
with
some
information
that
are
also
placed
in
that
directory.
You
can
find
the
slack
channel
where
you
can.
We
can
talk
about
the
kima
and,
of
course,
we
also
prepared
a
google
group
where
we
will
use
for
the
discussions,
also
some
announcements
about
the
new
versions
or
bigger
changes.
A
Please
sign
in
to
that
group.
Of
course,
you
can
also
find
the
open
community
issues
requests
with
label
a
succour
right
now.
What's
right
now
it's
empty
and
also
the
meetings
here.
We
are
using
some
frequency
we'll
talk
later
about,
and
you
can
find
also
the
meetings,
notes
and
agenda
for
the
next
meetings
here
about
the
leaders.
We
have
four
leaders
right
now
in
that
sig
core,
which
is
me
and
Matias
talk,
ahmed
abdullah
and
pookas,
goodnight,
ski
and.
B
B
It's
pretty
much,
eighteen
months
ago,
when
we
started
that
idea
on
solving
the
problem,
how
we
can
extend
and
customize
our
existing
enterprise
applications
we
have
over
there,
which
are
pretty
much
based
on
how
to
read
technology
stack,
so
we
can
extend
them
and
customize
them
and
just
improve
that
process,
because
everyone's
and
users
have
seen
okay,
it's
a
complex
process
to
do
that
any
said.
Okay,
how
can
we
achieve
that
to
make
that
a
little
bit
easier
and
better?
B
So
there
was
a
lot
of
neat
there
how
to
do
that
and
that's
even
getting
more
complicated
in
an
heterogenous
deck
and
then
the
other
thing
we
we
came
up
there
because
we
had
always
a
kind
of
ecosystem
outside
there
with
customers
and
partners.
Everything
we
want
to
do.
There
is
pretty
much
based
on
all
but
standards.
It's
based
on
openness,
so
everyone
in
that
area
can
even
reuse
that
stuff
and
use
it
and
even
extend
it
on
their
own.
B
B
If
a
effective,
we
want
to
have
that
in
a
good
shape
there,
so
that
was
pretty
much
the
motivation
when
we
started
there
it's
18
months
ago,
and
it
took
quite
some
while
to
convince
people
about
the
project
and
it
took
some
PCs
and
stuff
like
that
till
we
started
that
project
and
then
builded
the
first
release
of
kima.
At
that
time
it
had
even
another
name
and
it
changed
a
lot
there.
The
other
thing
I
can
add
there
from
the
beginning
on.
B
We
had
always
the
plan
to
open-source
kima
from
the
beginning
on
to
say.
Okay,
if
we
have
that
part
I
go
system,
custom
a
go
system
there,
it
would
be
good
to
drive
adoption
and
give
partners
even
the
freedom
to
say.
Ok,
they
can
extend
that
stuff.
They
can
use
it
for
their
own
purpose
and
we
have
been
even
thinking.
Customers
and
partners
might
even
come
up
with
some
other
extensions
in
ours.
We
might
have
never
thought
about,
and
why
should
we
limit
these
guys
doing
that
stuff
and
at
that
I'm?
B
Pretty
much
open
sourcing
was
put
on
a
timeline
saying:
okay,
we
might
do
that
in
a
year
or
a
little
bit
later,
when
we
have
four
more
stay
then
about
four
months
ago
we
met
some
folks
from
Google
and
they
introduced
their
project,
which
is
called
K
native
and
Canada
at
that
point
in
time
had
even
another
name,
and
it
was
pretty
much
focusing
on
doing
surveillance
development
on
top
of
kobani.
It
is
and-
and
we
have
taken
a
look
at
that
project-
a
lot
of
stuff.
B
Doing
that
extensive
validity
and
stuff,
like
this,
give
you
kind
of
vision
what
we
are
working
on.
We
still
have
a
longer
list
of
features.
We
want
to
implement
functionality.
What
we
want
to
implement,
but
priority
number
one
on
our
side,
is
aside
that
we
want
to
get
out
with
Betar
there
and
stuff,
like
that.
It's
very
much
saying
we
want
to
align
with
the
K
native
technology
there
and
that's
where
we
are
working
on,
and
the
first
approach
is
that
we
align
our
messaging
infrastructure.
B
What
we
call
the
eventbus
internally
in
kheema
with
what
cloud
native
is
providing
there
and
our
current
implementation
we
are
using
internally.
There
is
a
process
and
some
alignment
going
on
with
the
K
Native
community
there
that
we
want
to
contribute
that
to
native,
and
it
might
be
an
alternative
implementation
to
what
Canada
is
right
now
providing
there
and
might
be
useful,
then,
for
customers
and
stuff
like
that,
what
are
you're
using
there
right
now
with
and
the
overall
vision
there
from
driving
kima
forward
is
pretty
much
that
extensibility
story,
but
a
sighted
open-source
project.
B
What
we
are
planning
to
do
is
in
the
future
to
offer
to
have
an
offer
the
uncommercial
offer
for
our
customers
and
stuff.
Like
that
saying,
okay,
we
want
to
offer
kima
even
as
a
service,
and
so
customer
can
get
kima
even
as
a
managed
service
from
us
and
that's
pretty
much
saying:
okay,
it's
based
on
the
open
source
project,
but
we
are
adding
some
managed
service
around
that.
B
So
we
take
care
about
managing,
updates
and
stuff
like
that,
but
it's
all
based
on
the
open
source
and
everything
we
are
doing
there
and
open
source
will
be
fully
committed
to
what
we
do
there
in
the
new
project
there
with
our
service
offering
yeah.
That's
it
pretty
much
from
Mouse
my
side.
What
we
are
doing
there
so
I
can
hand
over
to
PK
again.
I
think
it
would
be
the
next
time.
A
You
think
you
are
else
I
just
want
to
add
one
more
thing,
that
for
all
the
attendees
I'd
like
to
ask
you
to
go
to
our
Google
group
and
this
list
yourself
with
the
location,
because
it
could
help
us
with
making
the
timing
for
the
night
next
meeting.
Just
for
reminder,
Google,
Doc,
sorry
I
send
a
send
a
leak
to
you
and
you
cash.
You
can
continue
the
presentation
with
came
other
of
you
right
already.
A
D
B
C
Perfect
and
also
ping
me
whenever
I
start
sound
like
robots
or
whatsoever,
so
yeah
hi,
guys,
I'm
I'm
mukesh
one
of
the
sick
leaders
and
also
a
product
owner
working
on
on
kimmm
and
I'll.
Just
give
you
a
brief
introduction
to
the
organization.
It
have
organization
that
we
have
so
just
explain
you,
the
structure
and
the
most
important
how
you
can
contribute
to
the
project
so
first
things.
First,
the
most
important
and
the
core
of
the
project.
Real,
is
in
kima
repository.
So
it's
where
ya.
C
Without
this
repo
there's
no
kima
by
the
way
the
the
next
one
is,
the
the
console
repo,
the
console
repo,
contains
everything
related
to
the
to
the
UI
that
we
have
in
the
console
in
the
in
the
in
the
kima
and
it's
a
console
UI.
So
the
wrappers
called
console
both
of
those
Rebels
follow
a
mono
repo
structure,
so
you're
gonna
find
in
keema
a
bunch
of
different
components
and
the
same
in
console.
You're
gonna
see
a
different
views
in
one
repo
and
then
the
next
one
is
the
community
community.
C
C
C
So
it's
a
place
where
we
have
sources
for
our
micro
fondant
framework
that
we
will
use
in
console
UI
in
kima
to
orchestrate
the
in
the
UI
and
to
bring
extensibility
to
the
UI
and
most
important
info.
Why
it's
separated?
Why
it's
not
in
console
or
kima?
So
it's
worth
to
go
there
into
the
wrapper
read
about
it,
so
they
think
about
Luigi
is
that
it
can
run
also
without
kima.
So
it's
not
really
dependent
on
kima.
You
can
use
it
without
c'mon
squad.
C
So
that's.
If
it
comes
to
the
basic
structure
of
those
seven
repos,
then
the
most
important
ones
for
the
contribution
is
this
kima.
So
let
me
just
go
a
little
bit
into
details
of
the
structure
of
this
mono
repo.
So
it
comes
consists
of
three,
the
most
important
parts.
So
the
the
go
code,
the
the
whole
code
for
our
controllers
operators
and
everything
that
makes
kima
running
and
useful.
So
it's
a
components
directory
then
also
we
have
all
the
acceptance
tests
that
we
use
for
testing
kima
cluster
and
the
whole
functionality
is
also
located
here.
C
If
it
comes
to
the
contributions
and
then
the
resources
directory
also
contains
all
the
Adams
arts
that
we
use
to
deploy
all
those
components
into
the
kubernetes
cluster
to
make
kima
functional.
Then,
if
it
comes
to
second
most
important
repo
for
contributions,
is
the
console
one
what's
important
to
notice
about
it.
Is
that
it
one
thing
what
I
mentioned
already
its
mana
rapport?
But
what
you
should
know
is
that
it's
we
use
two
different
technologies
to
provide
views,
so
it's
angular
and
react.
So
some
of
the
confidence
are
in
angular
someone
in
react.
C
We
also
started
doing
the
approach
that
we
don't
want
to
duplicate
the
components,
but
also
in
the
components
directory.
We
are
going
to
notice
that
we
started
providing
a
generic
components
that
can
be
reused
across
views,
so
that's
a
place
where
you
can
contribute
if
it
comes
to
the
UI
of
kheema
now
yet
the
most
important
thing
so
how
to
contribute,
of
course
like
in
any
other
github
project,
always
the
main
entry
for
the
contribution
is
the
contribution
md.
So
I'm
not
gonna
show
you
the
file,
because
you
can
check
it
on
your
own
later.
C
The
most
important
I
want
to
point
you
out
the
locations
where
to
contribute.
So
if
it
comes
to
the
content
contribution,
so
you
know
that
you
can
specify
something
more
or
you
notice
a
bug
in
documentation.
The
sources
of
the
of
the
documentation
are
stored
in
kima
repository
in
Doc's
directory.
So
the
whole
documentation
that
you
can
normally
see
here
on
kima
project
dialogues-
page
that's
all
taking
from
markdown
from
here.
So
whenever
you
want
to
contribute
to
those
markers
on
Fiverr,
so
just
feel
free
to
do
that.
C
C
That's
the
same,
we
also
made
sure
that
the
even
though
we
have
different
views
in
different
technologies,
we
managed
to
configure
everything
with
one
of
the
really
cool
tools
called
Glenna
and
to
make
a
development
environment
also
kind
of
unique
for
any
technology,
so
also
go
to
console
and
with
the
development
guide,
and
there
are
two
also
important
things
you
should
know
as
a
contributor,
and
we
are
of
course
aware
of
those
two
things
and
we
are
addressing
them.
One
is
as
a
contributor.
C
Obviously
you
want
to
make
sure
that
your
pro
request
is
tested
against
our
CI.
At
the
moment
we
are
still
having
a
CI
kind
of
hidden
from
you.
We
did
not
yet
move
to
prowl
and
we
still
have
our
internal
CI.
So
just
please
keep
in
mind
that
if
you
want
to
contribute
to
the
code
at
the
moment,
whenever
you
raise
a
pull
request,
just
yeah
be
patient.
C
C
We
are
aware
of
that
and
we're
also
addressing
that
part.
So,
just
please
be
patient.
Just
look
on
our
slack
channel
you're,
going
to
notice
that
we're
pretty
quickly
responsive.
So
whenever
you
want
to
contribute
to
a
specific
component,
feel
free
to
ping,
us
on
slack
I'm
sure
that
any
of
kima
developer
will
will
be
glad
to
join
you
with
your
contribution
and
explain
you
the
basic
structure
of
a
given
component.
So
it's
easier
for
you
to
make
a
first
contribution,
and
last
but
not
least,
contribution
is
not
only
documentation
and
code.
C
It's
also
issues
where
you
can
report
bugs
and
also
even
ideas
for
some
enhancements,
so
just
be
aware:
we're
using
github
issues
fully
at
the
moment,
so
just
go
to
team.
Our
project
raise
an
issue
and
if
you
want
to
see
more
information
about
who's,
delivering
a
given
feature,
if
it's
addressed
and
processed
be
aware
that
we
were
using
Zen
hub
to
kind
of,
let
say,
enhance
the
github
issues,
functionality
so
just
installs
and
a
plugin,
then
you're
gonna
see
much
more
sophisticated
details
of
a
given
issue
in
which
backlog
it
landed,
etc,
etc.
A
D
Thank
you,
Peter
I
hope
you
can
hear
me
so
just
very
shortly
about
the
akima
community,
because
we
had
a
lot
of
explanation
also
now
from
pietà ,
Ralf
and
Luca.
So
far,
so
every
of
the
sick
core
meetings,
we
will
have
a
slot
related
to
the
governance
of
keema
keema
community.
So
every
time,
if
you
have
any
question
related
to
how
do
I
create
an
issue,
what
is
the
release
process?
D
How
do
I
report
a
bug
where
do
I
report
about,
even
though
it
has
been
explained,
please
Ida
delve
into
the
community
repository
into
the
documentation.
Everything
is
there
or
simply
send
us
a
question
on
slack
also,
we
would
like
to
invite
you
to
follow
us
on
Twitter
and
LinkedIn
visit
the
website
for
some
more
news,
blog
posts
and
tweet
about
kima.
Tell
us
about
your
experiences.
What
were
your
experience
with
him?
Where
do
you
have
problems?
What
are
your
ideas
of
using
or
using
kima,
and
that
would
be
great
support
for
all
of
us.
D
A
Okay,
then,
the
next
point
is
about
our
meeting
when
it
will
happen
in
the
future
and
we'd
like
to
offer
that
it
would
be
on
Wednesday
as
it
is
today,
but
we'd
like
to
start
with
3
p.m.
the
Europe
time
and
do
that
at
the
beginning
be
weekly,
and
that
also
the
reason
we
we
asked
you
to
provide
that
information
from
which
locations
you
are
because
we
can
analyze
it.
We
can
even
then
think
about
the
pool
in
our
slack
channel
or
in
our
group
that
we
can
of
course
change
it
for
now.
A
That's
the
the
information
about
that
think
and
I
will
I'd
like
to
show
you
the
next
item,
which
is
our
proposals.
Then,
let's
back
to
the
C
core
directory,
where
you
can
find
2
and
sub
directories
proposals
and
decisions
about
the
decisions.
We
are
read
the
outcome
of
proposals,
we'll
talk
about
that
in
the
next
six
core
meeting
right.
A
Let's
right
now
focused
on
the
proposals
itself,
that's
the
place
where
we
can
provide
some
smaller
or
bigger
proposals
about
the
improvements
about
some
components
or
even
bigger
stories
that
are
really
related
to
many
components
and
I
just
want
to
show
you
one
of
them
which
is
modular
ization
and
we
have.
We
will
also
provide
soon
or.
C
A
The
template,
I
guess
for
the
proposals
that
we
can
see,
who
really
was
working
about
that
proposal
was
the
status
that
it's
proposed
or
accepted
about
the
acceptance
act
expectation.
We
will
talk
later
about
the
decision
records
next
meeting,
and
then
you
can
find
some
motivation
that
in
that
case,
we
want
to
make
him
a
more
modular.
That
means
we
can
skip
installation
of
some
of
the
components
where
you
can
find
the
goal,
the
current
situation
and
the
proposal
itself,
and
in
case
of
that
one,
it's
really
as
an
outcome
of
that
one.
A
A
A
E
A
Guess
we
can
use
many
channels
right,
of
course,
just
slack
itself.
We
have
a
sick
or
slack
channel
where
we
can
always
talk
about
them.
We
can
use
Google
Docs,
where
we
can
start
bigger
discussions.
Maybe
more
focused
on
that
topic
and,
of
course,
when
the
new
proposals
arrive,
they
are
also
under
the
pre
quests
and
we
can,
if
the
comments
inside
my.
E
F
Four
four
new
ones,
usually
you'll
start
with
the
poor
requests
and
send
that
that
includes
proposal
decision
and
send
it
on
the
mailing
list
at
the
start
and
yeah,
preferably
are
the
final
state
of
the
proposal.
Is
the
pro
request
itself
how
the
discussion
there
may
be,
but
you
can
also
have
discussions
like
channel
or
on
the
mailing
list.
F
A
Okay,
maybe
into
addition
what
Lukesh
was
presenting
us
about
that
come
up.
You
can
of
course
try
it
by
your
own.
You
I,
don't
remember.
If
we
cash
mentioned
that
that
you
can
install
the
Kimmel
locally
I
mean
you
get
faster,
then
you
can
feel
it
how
it
works,
and
you
can
get
more
feelings
about.
What's
that
about,
we
also
provide
the
local
UI
with
accessible
almost
one-to-one
with
the
CLI
API
then
feel
free
to
to
try
it.