►
From YouTube: CNCF TAG App-Delivery 2022-03-02
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
In
the
meantime,
I
would
have
a
question
I
asked
it
on
on
the
tag
app
delivery
slack
last
week.
I
guess
that
I
run
an
interview
with
guillaume
duper,
who
sent
a
really
detailed
issue
on
how
they
do
multi-talent
delivery
and
so
to
share
it
with
you,
because
it
shouldn't
be
just
my
my
learning,
but
it
could
be
learning
for
the
whole
community
and
the
question
is:
what
do
you
think
would
be
the
best
place
for
it
to
share?
C
A
It
almost
sounds
like
the
cooperative
delivery
working
group
could
do
almost
like
an
interview
style
meet
up
with
him
and
or
just
put
it
into
a
google
doc,
and
that
can
help
to
inform
some
of
the
some
of
the
pros
for
the
white
paper
later
on.
If
he's
willing
to
have
some
of
those
pieces
quoted
but
yeah,
I
think
just
capturing
it
first,
no
matter
how
you
do,
that
would
be
great,
even
if
it's
just
in
a
google
doc
or
something
like
that,
it's
in
a
video!
So
oh,
it's
a
video!
Okay,
sorry!
So.
C
A
Do
that
sure
we
can
stick
it
in
drive,
we
have
a
a
drive
folder
for
the
tag.
If
that's
okay,
we
can
put
it
in
there
yeah
do
you?
If
you
want
to
give
me
a
link,
I
can
download.
I
can
fire
it
over.
What's
that
josh.
B
B
C
A
A
Okay,
so
none
of
the
co-chairs
are
here.
Okay,
that's
great!
We
can.
We
can
kick
off
because
otherwise
it's
it's
gonna
be
a
while.
A
So
from
the
agenda.
The
interview
recording
we've
just
been
through
that
yeah,
let's
go
through,
then
the
captain
incubation
update,
who
wants
to
take
us
away
with
that.
D
I
think
that's
all.
I
guess
it
would
be
me
though
yeah
I
guess
for
alex.
It
wouldn't
be
the
most
exciting
topic,
because
we
already
had
a
presentation
at
captain
advisory
board
and
alex
is
one
of
its
members,
but
for
the
rest
of
the
team.
I
would
be
happy
to
do
a
quick
update,
just
ask
question:
how
much
time
would
they
have
based
on
the
current
agenda?.
A
D
Yes,
it's
okay,
second
time
closing
the
windows.
D
So
yeah
for
captain
incubation
update-
I
did
a
quick
summary
here
one
month
ago
and
after
that,
actually
we
had
a
number
of
improvements.
So,
first
of
all
we
were
talking
abc
to
see
what
are
the
next
steps
for
due
diligence,
reviews
et
cetera
and
we
got
a
feedback
from
carnegie
davis,
so
she's
back
to
the
cf
and
she,
the
user.
D
This
is
my
screen
yeah.
So
basically,
I
have
two
work
streams,
so
the
first
one
is
due
diligence
document,
so
I
did
the
first
round
of
updates.
Firstly,
it's
just
a
facelift,
just
updating
the
current
status,
extending
things
also
based
on
the
feedback
from
carnegie.
I
added
architectural
review
and
I
will
extend
it
because
it
was
one
of
the
key
questions
is
what
actually
what
differentiates
captain.
D
So
we
expanded
the
specification
description
of
components
because
captain
grew
in
terms
of
size
in
terms
of
various
services
available
in
the
system
we
expanded
use
cases
which
was
also
one
of
the
concerns
we
received,
and
I
guess
we
will
have
another
round
of
reviews,
so
you
can
see
that
everything
is
currently
pending,
so
I'm
not
submitting
it
to
the
review
by
talk
up
delivery
right
now,
but
maybe
by
the
end
of
the
week,
I
will
do
it
asynchronously
in
the
chat,
and
I
would
appreciate
the
reviews
I
saved
the
original
document
as
pdf
in
the
community.
D
Okay.
What
else
changed
there
so
big
an
adoption?
One
of
our
highlights,
which
needs
to
be
mentioned
that
now
we
have
captain,
is
needing
this
radio
platform
somewhat
source
project
by
kira
tech.
They
also
consider
applying
to
the
cncf
and
basically
it's
just
adoption
of
captain
as
a
building
block
for
another
open
source
project
through
integrations
we
offer
so
it's
also
quite
a
highlight
for
us,
and
it
also
helps
captain
to
get
a
second
vendor,
because
kirate
is
a
consultancy
company
based
in
italy.
They
have
a
number
of
customers
and
they
provide
enterprise.
D
Support
for
this
platform,
and
henceforth
captains
are
part
of
this
pledge.
So
it's
already
quite
a
highlight
for
us
also
what
changed
in
this
document
we
expanded
security
hardening
because,
as
it
was
discussed
for
it
was
one
of
the
key
obstacles
for
adoption
by
enterprises.
D
So
there
are
multiple
work
streams,
including
security
performance,
authentications
and
sso.
Authorization
is
also
in
progress.
We
improved
our
security
process
and
captain
was
affected
by
a
lock
for
jay
in
december,
because
one
of
the
services
uses
jimmy
there,
which
was
a
vulnerable
vulnerable
due
to
the
dependency
and
also
we
are
still
waiting
for
security
audit.
D
But
in
addition
to
the
security
ordered
by
attack
security,
which
is
delayed
because
of
rbcd,
we
also
did
openness
of
best
practices.
So
we
basically
reached
pricing
criteria.
D
We
will
be
continuing
that,
in
addition,
dynamics
performed
internal
security,
audit
and
third-party
security
audits
for
captain,
because
currently
we
offer
a
product
based
on
the
topological
determination,
so
I'm
waiting
for
details
so
that
they
can
share
more
information
about
what
was
done
during
this
audit
and
what
companies
were
checked.
So,
hopefully,
this
information
will
be
published
to
some
extent.
D
Then
there
is
massive
growth
of
a
system.
So
now,
artifact
hub
is
basically
a
production
radio.
Then
we
have
a
slide
provider
for
datadog.
So,
basically,
you
know
multiple
vendors,
also
asia
data
explorer
is
in
progress,
so
microsoft
is
looking
at
that
microsoft.
People
is
basically
looking
in
adopting
captain.
There
are
multiple
work
streams
with
microsoft
like
backstage
integration,
et
cetera,
et
cetera
for
the
environment.
D
This
is
one
of
the
items
plus
quite
a
bunch
of
services
and
one
of
the
earliest
highlights.
We
have
web
book
integration
service
which
actually
supports
integrating
various
components
through
webhooks.
So,
for
example,
we
integrate
with
slack
with
that
this
github
actions
also,
we
just
put
the
integrations
with
zapier
and
eftd,
so
it
basically
it's
a
support
for
some
like
four
servant.
Applications
over
to
the
support,
for
example,
automation,
engine
right
away
in
captain,
so
those
previous
system,
yeah
community.
So
some
quick
updates
would
happen.
So
we
have
community
roadmap.
D
We
have
some
different
contributing
guidelines,
especially
for
non-code
contributions,
and
we
invest
a
lot
in
apac
region.
So
we
introduce
community
meetings,
developer
meetings
where
we
do
webinars
there
and
we
already
got
some
traction
and
increasing
contributions
in
the
region.
So
we
will
keep
doing
that
plus.
D
D
A
So
I
just
wanted
to
summarize
the
timeline
for
captain
now
you're
going
through
the
due
diligence.
What
is
the
the
time
frame
for
tag
security
to
conduct
the
audit.
D
Then.
Actually
I
even
have
a
slide
that
I
believe
so
I
was
doing
presentation,
definitely
not
very
helpful
for
this
particular
item.
So
what
happened
in
tag
security,
so
they
had
a
bunch
of
unplanned
activities,
including
k
native
et
cetera.
They
also
have
massive
argo
cd
review
and
they
have
limited
bandwidth.
So
currently,
if
you
go
to
attack
security,
they
have
a
roadmap
and,
according
to
this
roadmap,
captain
is
next
in
line.
D
So
currently
they
just
finished
cloud
custodian,
maybe
several
weeks
ago.
So
argo
well
massive
chunk
of
work,
so
they
already
communicated
to
projects
that
argue
is
going
to
take
a
while.
They
will
need
to
break
it
to
multiple
upstream
multiple
work
streams
and
they
need
to
revise
their
roadmap
based
on
that.
So
for
security
review
right
now
there
is
no
eta.
We
are
waiting
for
tax
securities
to
communicate.
A
So
yeah
so
it'd
be
great
to
see
it.
Progress.
D
So
we
have
some
more
obvious
items
on
our
site,
including
security
processes
being
compliant
with
our
openness,
ssf
best
practices.
So
it's
not
like.
We
have
nothing
to
do
there,
but
yeah
for
formal
security
assessment.
We
really
need
security
to
prioritize
that
okay.
D
I
think
I
can
close
down
so
if
you're
interested
there
is
a
presentation
that
summarizes
everything.
I
talked
briefly
on
the
google
doc,
so
maybe
in
fancy
form
but
yeah.
I
just
wanted
to
glance
through
due
diligence
and
show,
what's
changing
so
take
a
look
at
that
and
maybe
worth
mentioning
that
we
actually
expand
the
technical
roadmap.
So
currently
we
operate
in
captain
it's
currently
in
preview
and
it
expands.
D
So
I
believe
that
thomas
was
actually
one
of
the
sponsors
for
this
item
will
be
presented
in
an
eat
lobster
group
and
you
can
see
that
there
are
many
other
topics
like
security
access
control,
extended
documentation
parameters,
integration
flow
et
cetera,
et
cetera.
So
there
is
a
lot
of
things
that
the
community
is
working
on.
D
Basically,
my
plan
is
to
finish
review
of
the
due
diligence
changes
with
the
community.
So
tomorrow
we
have
a
community
meeting
where
I
hope
to
sign
off
the
most
of
the
changes,
and
then
I
will
submit
it
to
the
tag
so
that
we
can
get
official
approval
and
endorsement
of
the
new
version
that
happened
in
september.
A
D
Oh
so
somebody
finally
edited
the
agenda.
I
can
actually
briefly
introduce
it
again.
C
D
Okay,
so
I'm
happy
to
briefly
talk
about
that,
so
actually
I'm
I
contribute
to
the
project.
I
wouldn't
say
I'm
a
founder
of
this
project.
I
just
show
put
and
carry
water
there,
but
yeah.
What
is
this
project
about
so
if
you're
familiar
with
open
telemetry
have
been
a
foundation
technology
that
basically
made
a
telemetry
commodity,
including
traceability,
logs
metrics?
D
There
are
cloud
events
for
events,
and
actually
we
would
like
to
have
the
theme
for
future
flux.
Currently
the
problem,
but
there
are
many
open
source
implementations
available,
but
there
is
none
open
source
implementation,
which
would
be,
which
would
have
open
specification
and
also
we
should
have
wide
wide
adoption
in
the
community.
D
So
we
would
be
interested
to
start
a
project,
creating
new
open
standards
for
future
fact,
management
and
also
providing
unified
sdks
apis,
so
that
any
vendors
can
reduce
them,
and
also
you
want
to
have
cognitive
communication
which
would
allow
users
to
take
these
technologies
and
manage
them
right.
D
Below
the
readers,
but
it's
fully
open
source
by
now.
So
what
we
have?
We
start
putting
specification
research
results.
There
is
a
lot
of
prototyping
being
done,
but
the
project
is
just
starting.
So
if
you
ask
whether
ways
the
reference
implementation
right
now,
it
doesn't
exist,
they
began
the
few
prototypes,
but
we
are
starting
assembling
these
speeds.
So
there
is
specification
we
already
defined
foundation
governance.
D
It
will
be
bootstrap
governance
and
the
intent
to
switch
to
fully
open
governance
within
one
or
two
years,
and
we
already
started
onboarding
interested
parties
for
the
project.
So,
for
example,
we
have
multiple
companies
which
explicitly
dictated
in
just
cisco
dynamics,
github
also
alex
simpson.
Just
some
canonical
would
join
et
cetera,
et
cetera,
so
we
already
just
started
getting
various
end
users
and,
more
importantly,
vendors
interesting.
A
Would
just
like
to
interject,
I
recommend,
as
part
of
the
actions
here
to
interview
people
like
richie,
hartman,
bartek
and
other
people
from
the
hotel
group.
Sorry,
the
the
tag
observability,
because
there
were
a
lot
of
learnings
from
the
hotel
specification.
A
I
don't
want
to
say
specification
wars,
but
the
specification
formation
came
from
a
lot
of
vendor
input
and
you've
definitely
done
the
absolute
right
thing
here
and
get
vendors
in.
I
would
like
to
see
a
commercial
partner
in
there,
a
commercial
vendor
such
as
launch
darkly
or
one
of
the
other
well-known
vendors
as
well,
but
I
think
that
will
be
what
makes
this
key
to
working.
In
fact,
having
one
of
the
cloud
organizations
such
as
aws
have
a
representative
from
a
gateway
perspective
would
be
really
interesting
as
well.
D
So
we
are
working
on
that,
so
there
is
a
lot
of
communications
here
and
there
so
right
now,
yeah,
we
haven't
publicly
announced
the
project,
but
we
are
basically
setting
up
everything
and,
if
you're
interested
tomorrow
at
3pm,
utc
we'll
have
a
keep
off
meeting.
So
if
you're
interested
you
can
just
subscribe
for
news,
so
we
have
a
google
form
referenced
everywhere
on
the
website
here.
So
you
can
sign
up
and
I
will
add
you.
A
If
we,
if
we
extrapolate
this
and
fast
forward
six
to
twelve
months,
would
the
idea
be
that
this
project
becomes
under
the
custodianship
of
one
of
the
one
of
the
working
groups?
Inside
of
this
tag,.
D
Yes,
something
we
briefly
discussed
stomas
with
others,
so
governance
wise.
Yes,
we
would
like
to
be
a
part
of
the
up
delivery
tag.
There
is
no
feature.
Flux
is
clearly
a
part
of
delivery
scope.
Also.
We
have
already
applied
for
cncf
incubation
sorry
sandbox
status,
so
the
new
review
round
starts
on
march,
8th
and
hopefully
we'll
be
accepted
to
the
cf
by
coupon.
So
our
roadmap
that
by
cube
convalence,
we
would
have
a
kind
of
alpha
regression
of
the
specifications
and
pc
reference
implementation
so
that
people
can
start
playing
with
that
providing
feedback.
D
Engineering
efforts,
for
example
banana
trace,
forms
an
engineering
team
to
back
this
effort.
So
it's
not
just
chit
chat.
We
actually
invest
in
that.
D
Also,
we
want
to
have
more
or
less
release
ready
version,
maybe
better
og,
like
you
know
autumn.
So
it's
tentative
one,
I'm
not
sure
how
exactly
it
goes,
because
it
depends
on
the
on
contributions
and
community.
We
will
but
yeah
initial
feedback
was
quite
positive
and
we
actually
talk
to
a
number
of
feature:
flag,
vendors,
also
public
cloud
providers
and
end
users.
So
the
list
will
keep
growing.
A
It
might
be
an
idea
if
you
folks
have
some
sort
of
representation
at
the
cooperative
delivery
working
group,
because
for
now
that's
probably
going
to
be
the
best
bet
on
having
a
regular
cadence
where
you
can
synchronize
with
this
tag.
Also,
because
you
have
you,
know
robert
and
josh
available,
it's
good
to
make
use
of
the
you
know
their
ability
to
help
you
coordinate
with
with
some
of
the
events
in
this
tag.
A
For
example,
the
maintainers
track.
Kubecon
will
be
a
very
good
opportunity
to
talk
about
this
new
project
within
the
tag.
D
I
totally
support
that
making
some
notes.
One
of
the
items
here
that
yeah
we
already
get
initial
due
diligence
by
open,
limited
maintainers.
D
So
we
have
daniel
villa
and
armin
roche,
who
provided
feedback
on
the
governance
model,
etc,
and
here
we
had
these
discussions
and
we
target
a
lot
of
discussions
and
keep
on
and
possibly
cbcon,
because
it's
already
all
scenario
of
overlap
with
the
continuous
delivery
foundation.
So
maybe
we'll
have
it
on
in
both
venues
and
any
feedback
is
home
to
talk
and
what
is
missing,
etc,
is
appreciated
and
feel
free
to
join.
We
also
have
some
roadmap
etc,
which
basically
provides
some
dates.
D
So
what
I've
already
briefly
summarized
but
yeah
again,
we
currently
everything
is
in
plugs.
So
let's
see
how
it
goes.
B
This
might
be
a
good
time
to
ask
and
oleg
you're
the
right
person
to
ask
this.
These
kinds
of
things
do
they
belong
with
us
or
the
continuous
delivery
foundation?
Do
you
have
an
opinion
on
that.
D
So,
in
the
case
of
open
feature,
we
want
to
be
one
of
the
reasons
that
we
target
cloud
native
implementation
and
cloud
native
architecture
for
our
reference
implementation.
So
it's
a
more
natural
feature
for
the
cnc
enterprise
system.
Another
one
is
that
ccf
is
much
more
mature
in
terms
of
a
system
in
terms
of
project
management.
So,
after
some
consideration
we
decided
that
for
this
project
we
would
like
to
go
with
the
things
here.
We
already
have
engagements
with
the
cdf,
for
example,
captain
wants
to
donate
captain
event
specification.
D
We
already
contributed
to
the
events
we
try.
We
want
to
clean
up
up
life
cycle
or
project
specification
to
the
cdf,
so
we
collaborate
with
both
foundations,
and
here
it
is
for
collaboration.
But
for
us
we
decided
to
go
with
the
ccf.
A
I've
got
to
drop
it
half
past,
but
I
just
wanted
to
bring
up
the
last
agenda
point,
which
is
the
I'm
going
to
go
to
operator
day,
which
is
co-located
with
kubecon
and
valencia
to
effectively
get
some
feedback
on
the
operator
white
paper
that
we
produced
last
year.
I'm
not
sure
how
successful
it
will
be.
A
I
will
try
and
run
a
I
guess-
a
kind
of
a
walk-in
affair
where
people
can
say
hey,
I'm
familiar
with
that,
but
the
goal
is
going
to
be
to
refine
and
improve
the
way
that
we
write
white
papers
and
to
see
what
you
know
what
stuff
went
down
well
and
what
stuff
didn't.
I
know
that
folks,
like
daryn
shepard,
gave
some
feedback
around.
A
You
know
it
being
quite
prosaic
in
some
parts
and
I
think
he's
right,
but
overall
I
want
this
to
be
an
exercise
in
helping
us
to
write
better
white
papers
going
forward.
So
that
was
the
only
agenda
item
I
had
for
them.
D
D
Yeah,
so
I
will
keep
talking
here
in
channel,
so
yeah
try
to
do
more.
A
I
really
mean
it
about
looking
at
how
hotel
was
formed
and
what
made
it
successful.
It
was
that
there
were
key
vendors
that
came
together
to
push
it.
D
Yeah
hotel
is
our
reference
model
for
this
project.
We
believe
some
way
in
the
governance
dock.
It's
written,
something
like
open
telemetry,
but
for
future
flags.
So,
of
course
we
will
be
learning
a
lot
from
this
community
also.