►
From YouTube: Community Meeting, June 21, 2023
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).
B
I
summarized
the
agenda
points
also,
which
war
brought
up
in
the
issue
here
on
the
top
before
coming
to
this
quickly,
highlighting
we
have
a
code
of
conduct.
So
please
keep
this
in
mind
and
yeah
anything
we
want
to
add
today
to
the
agenda,
or
are
these
all
points
we
want
to
discuss
today.
B
I
think,
let's
start
and
if
something
coming
up
in
the
meantime,
we
can
edit
data.
So
potentially,
let's
start
with
the
current
summary,
not
sure.
C
I
can
start
so
everybody
has
seen
we
have
moved
the
governance
to
another
model
like
four
weeks
ago
or
something
so
there's
a
governance
file
in
depository,
which
basically
defines
a
committee
of
three
people,
myself
Andy
and
as
a
starting
set
of
approvers
or
maintainers
owners
of
the
project
and
as
it
also
defined
how
a
transition
will
and
can
take
place.
When
somebody
wants
to
step
up
to
become
a
maintainer,
it's
defined
all
there.
C
We
did
that
and
that
had
basically
agreed
to
give
us
I
mean
permission
to
do
that
and
to
give
us
access
to
all
the
accounts
like
to
the
organization
in
GitHub,
YouTube,
channel
and
other
things.
So
we
have
all
the
keys
to
continue
the
project.
C
This
is
status
quo
and
we
are
working
under
this.
You
know
those
wolves,
basically
for
the
last
week's,
and
we
have
some
plans
yeah
about
the
project
at
the
technical
plans,
but
in
parallel
to
those
we
can
talk
about
them
as
well.
In
a
minute,
some
of
us
are
also
working
on
a
text
for
a
set
box
at
the
submission
for
cncf.
So
this
might
also
come.
Timeline
is
up
in
the
air,
but
we
are
working
on
a
text,
so
this
might
come
at
some
point.
C
B
The
points
which
were
coming
up
today
is
that
Tuesday
is
quite
packed
day
for
some
of
the
folks
who
would
like
to
join,
and
the
proposal
is
instead
of
doing
it,
Tuesday
moving
it
to
Thursday.
So
that's
every
second
week,
Thursday
I
think
it
will
be
in
the
other
week
of
the
cube
Stellar
meeting
at
the
same
time,
so
I
think.
B
Voted
for
this,
if
no
one
has
any
concerns
here,
I
would
propose
that
we
move
into
Thursday
from
the
next
meeting
onwards.
So
in
two
weeks,
so
the
next
week
meeting
will
be
in
two
and
a
half
weeks.
So
Thursday
I
need
to
look
it
up
in
the
comment
now.
B
Let's
start
with
the
one
of
the
main
work
we
started
getting
up
and
own
CI
system,
potentially
Kristoff,
you
can
talk
more
about
woodwork,
I
think
you
did
most
of
the
work
was
done
on
the
CI
and
Pro
Staff
and
how
far
we
are.
D
I,
don't
think
we
need
to
go
into
all
the
detail
that
went
into
building
the
factors
we
now
have
a
pro
we're,
not
relying
on
the
ohm
shift.
Ci
infrastructure,
anymore
and
I
would
call
it
good
enough
for
now
it's
in
the
info
repository
for
kcp.
D
If
anyone
wants
to
make
changes
to
it,
please
open
it
PR
and
right
now
we're
still
hosting
cubester,
but
if
I
understood
Andy
correctly
he's
in
the
process
of
setting
up
a
dedicated
call,
Fork
shipstellar
as
cubeseller
gets
its
own
GitHub
organization
as
well,
but
in
the
meantime,
until
that
is
done,
Cube
seller
jobs
can
also
run
in
the
kcp
plow,
and
that
plow
is
just
a
simple
combination
of
two
clusters
on
Amazon.
D
Nothing,
special,
nothing
fancy
here.
Anyone
has
questions,
please
ask
but
yeah,
just
it's
just
there.
It
works.
D
A
D
The
repositories
have
been
migrated
over
about
one
or
two
are
still
left,
I
think
controller.
One
time
example
code
is
still
to
be
done
because
we
just
recently
gained
kind,
support
and
I
think
one
other
and
then
a
couple
of
repositories
that
aren't
really
that
much
used
like
enhancements
friends,
the
kcp
GitHub
page.
Those
repositories
are
currently
don't
have
12
integration,
because
I
haven't
seen
any
PRS
there
and
I
was
told
they
are
not
that
important.
They
could
easily
be
edited
anytime.
D
C
D
B
Any
questions
someone
has
to
prowl
or
to
the
CIA
setup
or.
D
Well,
I
have
one
while
we
added
do.
We
want
a
slack
integration.
Currently,
it's
disabled,
but
it's
possible
to
send
certain
jobs
in
some
slack
channels,
potentially
post
submits
where
we
build
images.
If
those
keep
failing
it's
it's
not
configured
yet
because
I
couldn't
imagine
how
that
works
and
I
don't
know
how
to
get
a
select
token
for
the
kubernetes
slack.
But
if
anyone
wants
to
have
it,
we
can
just
enable
it.
D
C
D
B
D
Okay,
then
I
think
we.
If
no
one
else,
has
any
plow
comments,
then
we
can
move
on
to
the
next
agenda
item.
B
Yeah
there's
a
proposal
to
cut
the
next
release,
because
I
think
also
you
Crystal
did
most
of
the
work
to
removing
from
the
kcp
core.
A
repository
is
a
TMC
where
we're
coming
late
at
good,
but
as
we
now
have
a
somehow
clear,
State
otlc
I
think
it
makes
sense
to
create
a
new
release
and
create
a
kcpe
0.2
release
so
that
everyone
can
start
testing
and
using.
A
B
D
Thank
we
very
much
would
be
nice
to
have
a
clear
cut
where
we
can
say
this
is
a
d
and
BC
timing
bonus.
A
A
I
think
we
already
removed
TMC
from
our
docs
as
well.
So
question
is:
is
there
anything
else
that
we
want
to
do.
B
A
B
Know
the
release
process
or
how
was
it
done
in
the
past
or
who
did
it.
C
I
think
there's:
isn't
there
a
file
in
kcp
release,
MD
or
something
or
structure
methods
somewhere
just
a
long
list
of
manual
steps?
Basically
I
don't
see
if
it
may
be
in
the
commenting.
The
thing.
A
So
yep
it's
in
the
dark
spot
here.
I
think
this
is
the
page
I
mean
probably.
C
D
D
C
Let's
just
walk
through
that
I
mean
offline,
maybe
MJ,
and
you
can
just
try
it
and
see
where
we
have
to
make
changes.
What
works,
what
doesn't
and
if
we
need
a
like
a
0
21
release,
because
a
20
release
didn't
work
or
something
is
also
fine.
B
Okay,
so
we
have
conclusion
on
cutting
the
release,
any
comments,
questions
to
that.
B
C
B
One
thing
we
realized:
there
are
some
PRS
open,
I,
think
PR's
we're
having
around
about
30
of
them
or
something
like
a
24,
now
open
I
think
that's
still
manageable,
but
over
340
issues
currently
are
open
and
some
are
quite
all.
The
question
is
what
we
do
with
it
and
how
especially,
for
example,
a
lot
of
the
issues
are
referencing
TMC
code,
which
is
not
there
anymore
and
the
questions.
How
do
how
do
we
want
to
go
forward
with
this
Chevron.
C
Grammar
proposal
is
just
to
wait
until
we
have
an
answer
to
GMC,
so
we're
talking
about
it
in
a
second.
If
a
team
C
repository
exists,
we
can
move
over
stuff
and
my
impression
is
in
the
last
months
of
the
projects
like
there
was
a
big
project
management
proof
in
head,
so
lots
of
things
there
are
probably
from
there
like.
There
are
10
epics
issues
below
so
all
of
those
will
move
to
another
repository,
and
then
we
can
clean
up.
That's
not
proposal.
A
C
C
And
yeah
for
those
who
haven't
been
here
before
we
usually
did
some
3F
call
or
some
part
of
the
meeting
at
the
end,
10-15
minutes
where
we
went
through
issues
at
least
those
which
were
new,
and
you
put
them
into
some
labels.
C
C
B
D
B
And
then
we
start
triaging
the
ones
which
are
still
there
and
taking
either
taking
them
10
or
15
minutes
at
the
end
of
the
meeting
or
having
potentially
one
longer
meeting
we'll
try
to
go
over
a
bit
more
issues
to
clean
up
stuff.
B
Yeah,
there
are
also
other
global
global
in
Global,
locals
English
support,
so
I
think
when
we
come
to
the
other
repositories
or
to
the
overview
of
repositories.
What
we
want
to
bullishly
Archive
could
be
that
there
are
more
issues
later
which
are
not
so
relevant
and.
A
C
So
just
a
short
summary
at
some
point:
we
decided
to
basically
drop
TLC
from
the
from
the
main
repository,
so
there
was
a
giant
PR
request,
number
I,
think
removing
everything
also
documentation,
so
all
TMC
should
be
gone.
C
There
is
an
attempt,
I
think
Frederick
is
here
and
MJ
is
not
here.
So
there's
an
attempt
to
to
recover
the
code
into
a
new
repository
called
TMC,
but
basically
building
cleanly
on
top
of
kcp,
so
kcp
would
basically
be
kcp
core,
as
we
have
talked
about
that
before
and
TMC
is
basically
yeah,
it's
it's
based
on
core,
but
it
adds
stuff
by
our
goal
code.
So
it's
not
clean
plug-in
model
or
anything
like
that.
It's
it's
building
its
own
binary,
that's
a
cool
approach.
C
What
I
understood
is
that
there
are
Ambitions
to
make
it
pluggable
so
to
think
how
kcp
could
host
such
a
feature
without
basically
being
forked
being
a
new
binary,
but
this
is
a
more
long-term
goal.
I
guess
so
the
short
term
grower
Frederick,
you
can
say
more
about
that
TMC
seems
to
work
in
that
context.
Right,
that's
what
you
have
done
last
weeks.
A
I
think
it
would
make
sense
to
have
it.
It's
a
nice
use
case
that
we,
when
the
project
was
like
reorganized,
and
no
one
like
majority
of
people,
didn't
have
a
use
case
for
that.
But
it's
still
a
valid
use
case
and
from
the
like
requests
coming
in
I
I
see
that
they're
still
interest
in
it
in
using
it
so
I
think
it
would
be
nice
to
host
it
under
the
kcp
deaf
organization.
B
And
last,
but
at
least
on
this
agenda
Stefan,
you
created
the
summary
of
all
the
repositories
and
also
wrote
down
what
needs
to
be
maintained
and
potentially,
what
could
be
archived
and
some
hours
question
mark
I
would
propose
that
we
go
with
and
making
a
decision
for
each
repository
or
whatever.
What
do
you
think.
C
Now
we
can
go
through
them.
If
anybody
disagrees,
please
raise
your
hand
or
just
comment,
so
we
can
go
through
them,
one
by
one.
So
HMC
I
think
that's
the
easiest
one
NDS
here,
some
others
as
well.
They
have
decided
to
move
to
cubes,
Stella,
so
awkward,
I
think
right,
another
GitHub
organization,
so
let's
decided
and
there's
a
deadline
or
a
timeline
I
think
June
23rd,
which
is
this
week
yeah.
C
Friday
yeah
I
just
want
to
solved,
and
then
we
have
a
couple
which
are
maintained
or
which
I
I
think
we
maintain
and
have
to
maintain
so
code
generator
gets
client
generation
for
cluster
where
clients
info
that's,
obviously
Pro,
so
just
going
through
them.
If
you,
if
you
disagree,
please
speak
up.
C
If
you
haven't
seen
any
at
a
very
small
Library
we
have,
which
is
connected
logically
cluster,
which
comes
below
kcp
at
the
main
repository.
If
you
get
on,
then
you
have
head
chart,
so
MJ
volunteer
to
officially
own
there
to
maintain
that
you
have
client
go
which
is
not
a
fork,
but
it's
just
a
regeneration
of
the
cube
clients
and
from
us
using
the
code
generator.
C
It's
the
same
thing
for
API
extensions,
so
CID
clients
majority
generated
same
thing
as
client
go.
Then
we
have
this
controller
runtime
exam
I
put
maintains.
There
was
more
question
mark
because
I
don't
think
we
have
anybody
really
looking
into
that
plus
we
have
the
controller
runtime
here.
So
I
also
said
maintain
because
it's
kind
of
essential,
I
guess
and
to
my
knowledge,
this
at
the
moment,
is
a
for
of
controller
runtime.
Yep,
so
I
think
we
have
to
come
back
to
those
two,
at
least
at
some
point.
C
Yeah,
maybe
we
should
talk
to
to
Vince
about
those
right
spin.
This
maintain
enough
control
over
time,
so
he
knows
all
of
that
and
I
think
he
worked
towards
all
partly
on
that
and
that
it
was
still
in
kcp
next
one
luxury
cluster.
This
is
our
main
library
for
Zoological
cluster
type.
C
C
C
So
enhancements
not
really
a
lot
of
stuff
inside
we
just
started,
there's
one
enhancement
I
think
not
long
ago.
Kcp
tests
is
the
former
redhead
QE
team,
so
they
don't
maintain
tests
anymore
there.
So
my
proposal
is
to
Archive
sets.
C
And
then
we
have
two
repositories
where
we
wanted
to
connect
to
collect
links
to
demos,
blog
posts
and
stuff
friends
and
awesome,
kcpe
and
I
said
yeah.
But
the
question
is:
do
we
maintain
those.
B
The
question
is:
do
we
need
dedicated
repositories
for
this,
or
is
it
enough
to
have
one
markdown
file
for
collecting
demos,
blogs
posts
and
so
on,
and
one
for
who
is
using
kcp.
D
C
You
might
might
get
feeding
this.
Let's
try
to
minimize
what
we
have
and
kind
of
an
add-on.
We
can
move
those
things
elsewhere
like
like
into
a
awesome,
markdown
or
friends.
B
Question
decision
would
be
weak
archive
this
one
and
moving
this
to
Dedicated
awesome,
markdown
files
and
finds
markdown
files,
if
required,.
C
All
right
and
we
have
C
I,
go
I,
think
that's
the
fork,
I
think
in
the
in
the
conversion
prototypes
and
needed.
We
needed
some
some
features,
I,
don't
remember
exactly
which
I
think
I
Upstream,
probably
first
of
do
you
know
this
is
still
used
in
kcp.
C
B
I
would
exactly
one
is
okay,.
C
I,
don't
think
I
think
they're
technically
different,
but
this
is
something
if
somebody
wants
to
clean
up
and
simplify
documentation
and
website
there
there's
potential
to
do
that,
because
the
website
we
needed
it
quickly
before
the
12
Cube
quite
at
the
time.
So
we
use
some
UI
tool
to
create
it,
not
the
same
technology
behind.
B
I,
just
looked
it
up
the
the
website
as
a
documentation,
kcp
minusdef.kita.io,
this
point
into
the
docs.kzp,
but
it's
in
this
repository.
It's
only
the
redirect
and
the
documentation
itself
is
in
the
kcp
smash,
docs
Repository.
C
B
So
I
would
say
we
can
leave
it
for
now
and
when
we
look
into
the
potentially
in
the
future,
how
to
optimize
or
if
there's
something
to
restructure
on
the
documentation
or
general
website
that
we
can
look
this
up
as
well.
A
Yeah,
so
just
having
a
quick
look,
I
think
kcp.ios,
like
the
the
landing
page
and
the
kcp
def
thing
is
the
documentation
page
which,
as
you
said,
redirects
to
docs.kcp.io
so
I
think
that's
why
there
are
two
kind
of
locations,
one
of
the
landing
page.
One
is
the
documentation
which
is
generated
from
the
kcp
Repro.
A
But
speaking
of
that,
how
is
this
published?
Does
that
mechanism
still
work.
A
C
And
I
guess
at
some
point:
we
have
to
yeah
redesign
or
change
content
of
the
landing
page
anyway.
So
I
think
we
will
come
to
that
and
at
that
point
we
might
so
I
wouldn't
be
unhappy
if
we
get
rid
of
this
landing
page
technology
and
just
integrate
it
into
this
main
page
as
a
docs
page.
C
A
C
Yeah,
the
last
one
cattle
dog
that
was
a
prototype
for
I-
think
it's
still
I
command
and
maybe
some
controllers
to
have
an
API
catalog,
so
something
above
exports.
C
D
B
Move
the
call
to
Thursdays
in
two
weeks
and
see
you
all
in
two
weeks,
Thursday
bye,
thank.