►
From YouTube: 2021.4.16 Cloud Native SIG
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).
A
C
A
Actually,
after
submission
of
my
proposal,
one
contributor
commented
on
it
and
I
had
questions
related
to
that
that
I
wanted
to
ask.
So
if
that's
fine
I'll
go
ahead
and
ask
them
yes,.
B
D
D
B
E
E
A
C
A
C
I'm
so
sorry
for
the
issue
actually
yeah.
Would
you
like
to
put
a
link
in
the
chat.
A
Okay,
so
if
it's
scroll
down
to
page
number,
four.
A
Yeah
so
jesse
commented
saying
that
a
similar
plugin
act
does
not
exist
in
jeff
229
so,
and
we
had
this
in
our
mind
that
it
exists
and
we'll
replace
it
with
jenkins.
So
actually,
if
that
is
not
true,
then
the
half
of
my
deployment,
part
of
the
project
becomes
wrongly
or
invalid.
Then
how
I
mean.
F
So
do
I
need
to
be
very
no
so
so
jake's
jx
release
version
is
a
plugin
for
jx
and
it
is
available,
but
it
can
also
run
out
of
github
action
to
determine
the
next
version
and
because
it's
run
as
a
game
of
action,
it's
possible
to
integrate
it
with
a
jep
229
stuff.
F
But
I
could
see
it
becoming
that
in
the
future
and
it's
it's
a
bit
up
in
the
air,
because
the
current
method
of
versioning
rejected
9
uses
like
the
number
of
commits
since
origin
and
a
git
sharp
to
produce
something
unique
and
unfortunately
it
produces
non-semantically,
versioned
or
versions.
So
it
means
it's
kind
of
quite
it's
not
very
useful
for
plug-in
developers.
F
You
have
to
have
to
provide
back
ports
for
them
when
there
are
fixes
that
need
to
be
done
or
security
releases,
so
yeah
and
it
they
are
properly
semantic
semantically
versions.
So
I
think
they
need
a
different
way
of
doing
it.
We've
we've
heard
from
mark
that,
like
certainly
on
the
git
plug-in
switching
to
cura
jet,
two
to
nine,
as
is,
is
not
going
to
work
for
them.
They
need
a.
They
need
a
way
of
doing
semantic.
Versioning,
okay,.
A
B
Do
you
does
that
give
you
enough
information
to
to
move
ahead
with
this
and
to
think
about
how
you
the
work
you're
going
to
do?
Do
you
have
any
more
questions.
B
A
Yeah
this
comment
so
of
course,
as
far
as
I
understood
it,
it's
like
we
are
complicating,
or
what
I'm
proposing
is
a
very
complicated
approach
and
a
rather
simple
cli
tool
would
do
the
job
so.
A
I
actually
did
not
include
that
in
the
proposal
and
it
can
be
done
a
simple
cli
tool.
So
shall
we
modify
the
approach
or
I
should
shall
I
add
that
thing
in
the
timeline.
F
So
that
that
is
about
writing,
so,
whatever
file
that
you
potentially
read
the
version
from
that
is
about
writing
the
version
back
into
the
file
as
like
an
optional
thing
right.
Yes,
so
yeah
that
I
mean
that's
valid,
we
will
need.
We
need
a
way
of
doing
that.
There
will
be
certain
builds
that
will
want
to
have
that
in
place.
F
A
So,
like
writing
back
into
the
form
file
or
the
gradle
file,
is
not
needed
and
writing
a
text
file
where
the
way
he's
suggesting
that
is
so
I
actually
I.
F
Think
you
probably
want
to
do
both
like
you
may
find
that
you,
you
may
find
that
so
within
the
context
of
buildings,
for
instance,
drinking
plugins,
they're
they're,
either
gradle
or
maven
and
they're
pretty
straightforward,
builds,
you
could
write,
writing
and
or
updating
the
poem
would
be
fine.
F
Creating
a
tag
would
be
again
also
would
be
fine,
it's
pretty
simple,
but
what
we're
seeing
is
the
use
for
this
in,
like
more
much
more
complex
builds
where
you
may
be
wanting
to
trigger
a
make
file
or
something
else
or
another
process,
you
may
need
those.
You
know
those
variables.
So
writing
writing
a
file
with
the
version
in
is
going
to
be
handy
for
some
people
updating
a
file
that
you've
you
know
really
or
just
echoing
it
to
the
screen.
That
also
might
be
useful.
F
F
F
I
think
it
just
passes
the
version.
That's
all
it
does
so,
okay,
I
would
probably
go
with
like.
Maybe
I
don't
know
what
we
do
with
the
actually.
I
don't
know
how
this
works
cara,
but
would
it
make?
Would
it
simplify
things
if
we
could
rename
the
proposal
slightly
to
conventional
commits
plug-in.
B
I
think
we
we
have
space
to
alter
the
work
that
is
done.
I
don't
think
we
can
rename
it
under
g-stock.
The
proposal
is
not
submitted
and
that
deadline
is
passed,
but
in
this
community
bonding
period,
of
course,
you
know
the
understanding
of
the
problem
space.
The
exact
work.
That's
going
to
be
done.
That's
fine
for
that
to
evolve.
B
So
that's
good,
thanks
for
being
here
we're
talking
about
a
semantic
versioning
plug-in
for
jenkins
proposal
for
g-shock
and
going
over
some.
F
G
Yeah,
just
to
clarify
the
current
state
with
g-shock,
the
proposals
have
been
submitted
on
april
13th,
and
it
means
that
basically,
you
have
a
final
version.
You
cannot
modify
it
anymore
and,
as
we
discussed
at
the
office
hours
on
wednesday,
we
will
be
basically
making
decisions
and
reviewing
the
version
of
proposals
submitted
on
april
13th.
G
So,
for
example,
when
we
publish
a
project
page
on
genki
style,
we
can
apply
another
name,
and
we
can
even
ask
google
support
to
change
the
name
on
the
jsoc
website,
though,
usually
people
don't
do
that
but
yeah
until
the
project
begins
may
here.
Basically,
whatever
you
change
is
just
preparation
for
the
next
phases.
If
the
project
gets.
G
Sorry,
if
my
comment
was
a
bit
out
of
context,
but
you
usually
when
we
talk
the
students,
they
want
to
modify
proposals
later.
G
Yeah,
so
right
now,
you're
welcome
to
do
anything
in
the
jenkins
community,
basically
as
common
contributor,
if
you
want
to
keep
enhancing
your
proposal,
etc.
You're
welcome
to
do
that.
We
will
just
reviewing
the
version
which
was
submitted
but
yeah
after
that.
These
comments
can
be
integrated
into
the
plan.
A
Okay,
I
mean
thank
you
garrett
for
helping
me.
I
have
no
more
questions.
D
D
B
B
Okay,
well,
don't
hesitate
to
ask
in
the
get
our
channels
and
we
welcome
your
participation,
we're
very
excited
about
you
suck.
So
thank
you
both.
G
Yeah,
just
one
side
note,
so
if
you
don't
know
exactly
what
to
do
with
regards
to
json
in
the
coming
months,
one
of
the
things
you
could
consider
is
basically
focusing
on
your
study
definition
cup.
Whatever
tasks
you
have
there,
because
if
you
get
the
selected
to
jstock,
then
you
will
be
able
to
dedicate
more
time
and
if
you
don't
get
selected
to
jsoc
again
it's
something
that
is
useful
for
you.
G
B
Okay,
if
we
don't
have
any
more
questions
about
g-suck
it
was
there.
Were
there
any
action
items
or
things
you
wanted
to
bring
up
about
the
tecton
client
plug-in
gareth.
F
F
No,
I'm
not
sure
what
the
current
state
on
that
is.
It
would
be
really
good
to
get
a
and
get
it
working
in
a
pipeline
with
a
form
of
end
to
end
test,
so
we
can
kind
of
cut
a
you
know,
version
one
release
or
something
that's
less
of
an
alpha
release,
at
least.
B
B
C
G
Yeah,
so
just
quick
update
on
the
governance
site.
One
month
ago
we
voted
for
accepting
the
project
as
official
junk
sub
project,
so
it
was
agreed
and
it
was
effective
on
that
date.
After
that,
the
victor
schwab
team.
They
made
some
updates
on
the
websites
and
they
also
created
the
request,
update
jenki
scion,
so
it
has
been
landed,
and
yesterday
we
have
published
an
official
blog
post
and
you
can
always
find
it
in
linkedin.
We
will
also
do
something
about
twitter
within
the
next
few
hours,
but
yeah.
G
The
project
is
now
effectively
a
part
of
well
doing
this
project
like
it
was
before,
but
in
more
official
studies
we
will
also
work
with
the
team
to
integrate
the
jinx
current
separator
into
the
roadmap.
There
was
ongoing.
There
was
a
discussion
about
open
governance
for
the
project,
which
kind
of
fell
apart
because
red
hat
decided
to
proceed
with
its
own
operator
at
that
point,
but
we
will
need
to
recover
this
discussion
and
to
see
how
we
could
improve
it.
G
Okay,
so
let's
say:
let's
have
red
hot
separator
right
now,
it's
a
hard
fork
on
junk's
kubernetes
separator,
which
is
no
longer
fully
compatible
and
it
evolves
in
a
different
direction
why
it
happened
because
red
hat
has
its
own
interests,
mostly
on
the
openshift
platform.
G
When
they
were
trying
to
contribute
to
jenkins
operator,
it
wasn't
possible
to
integrate
changes
because
maintainers
were
not
available.
Then
there
were
disagreements
on
the
roadmap.
We
tried
to
mitigate
it
by
in
the
jenkins
governance
board,
but
getting
call
science
on
in
the
discussion.
I
we
offered
the
open
governance
proposal.
Then
it
was
supported
by
red
hat
by
the
jenkins
governance
board,
but
first
up
at
the
point
was
was
not
available.
G
So
finally,
red
hat
decided
to
press
it
with
its
own
operator
and
again
vs
jinx
project
supported
that
so
right
now
there
are
two
operators.
One
is
called
the
zinc
separator,
which
is
now
official
sub
project.
Another
one
is
jenkins
automation,
operator
vertical
correctly
or
something
like
that,
which
is
basically
a
red.
Hat's
project
is
being
developed
again
as
a
part
of
the
jenkins
project,
but
yeah
these
operators
are
not
compatible
with
each
other.
B
Okay,
well
we're
at
the
half
hour.
Thank
you
all
for
being
here
and
again.
Thank
you
very
much
for
your
gsoc
proposals.
I'm
very
excited
all
right
have
a.