►
From YouTube: CNCF TAG App-Delivery 2022-01-19
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
B
B
A
A
A
B
A
D
A
A
D
C
Yeah
just
wanted
to
open
it
back
up.
I
know
we
had
submitted
for
sandbox
in
october.
I
think,
and
then
there
was
some
questions
that
we
answered
and
then
I
just
was
curious.
If
there's
feedback
or
any
kind
of
direction,
this
this
group
can
provide
as
to
where
what
we
should
do
next,
because
we
haven't
heard
anything,
we
haven't
received
any
official
email
or
communication
about
the
application,
and
we
don't
really
know
what
to
do.
D
C
Yeah
we
we
just
followed,
I
think
there
was
a
google
form
that
we
submitted
and
then
that
went
in
and
then
we
haven't
heard
anything
back
since
that
submission,
or
at
least
I
haven't.
C
C
When
I,
when
I
met
with,
I
came
back
to
this
group
kind
of
to
because
I
heard
there
were
some
questions
about
our
submission
and
then
I
try
to
take
notes
on
some
of
the
things
that
were
discussed
and
then
I
put
together,
I
put
in
the
chat
here
a
link
to
this
a
follow-up
where
we
basically
tried
to
answer
all
the
questions
that
were
asked
and
then
I
think
I
think
it
was
aloise
who
said
you
know,
give
us
a
little
bit
of
time
to
review
this
here.
C
A
D
Okay,
so
just
to
clarify
the
assets
that
you
have
submitted
were
the
form,
and
this
email
then,
and
that's
where
we
did
the
like
so
far-
is
that
where
you
have
like
conversation,
start
of
it,
okay,
I'll
just
double
check,
because
this
is
the
beginning
of
the
year.
I
need
just
to
find
the
there
is
somewhere
like
with
instructions
on
like
what
how
to
to
make
this
sandbox
submission.
D
I
don't
know.
Maybe
there
is.
I
think
there
was
a
pr
you
would
make
and
then
that
would
encourage
the
discussions,
but
I
need
just
to
double
check,
but
we
can
take
a
look
thanks
for
like
coming
back
to
it,
because
I
haven't
had
seen
this
one.
D
E
So
the
qc
told
us
throw
the
ball
on
us
and
said
we
should
try
to
find
out
if
they,
if,
if
conveyor,
could
live
outside
of
of
openshift
right,
and
I
think
there
were
some
other
questions
which
I
can
remember.
C
Yeah,
so
there
were
three
three
three
questions:
one
was:
how
could
it
ever
move
beyond
sandbox
to
a
graduated
state?
The
second
was
the
conveyors
project,
support
non-vendor
provided
kubernetes,
and
the
third
was:
are
there
examples
of
github
issues
associated
with
the
project,
and
so
I
for
all
three
of
those
in
that
email.
I
replied
and
kind
of
explained
how?
Yes,
I
believe
it
could
move
beyond
the
graduate
to
to
a
graduated
state.
Yes,
it's
it
runs
on
non.
C
It
runs
on
other
kubernetes
distributions,
like
you,
could
just
pull
upstream
cube
and
run
it
and
then
third,
is
I
put
a
list
of
pull
requests
that
we've
had
from
outside
of
red
hat
so
from
you
know,
various
digitalocean
and
other
folks
who,
like.
E
So
we
discussed
this
a
bit
in
the
in
the
in
our
group,
so
otherwise
I
think
me
a
bit
and
I'm
currently,
to
be
honest,
I'm
not
sure
what
the
other
two
thing
think
of
it
from
for
me.
I'm
I'm
also
thinking
a
bit
like
that.
E
You
see
that
I'm
not
sure
if
the,
if
the
project
itself
in
this
constellation
could
move
beyond
beyonce
and
books,
and
for
me
it's,
but
that
that's
only
my
impression
conveyor
is
a
is
kind
of
a
set
of
tools
which
is
used
to
uplift
to
to
onboard
your
community's
apps
or
to
move
move
them
replay
from
apps.
E
But
what
what
I
was
missing
on
the
whole
tool
set
was
the
link
being
was
the
link
between
the
tools,
so
you
know
to
to
say
it
in
a
in
a
pretty
hard
way,
and
please
excuse
me
for
this-
it's
it's
from
for
me.
It
would
be
the
same
if
I
took
my
my
set
of
shell
scripts,
put
it
in
a
git
repository
and
create
a
cncf
project
out
of
this,
and
for
me
for
me,
the
link
between
the
tool,
tooling,
is
missing.
E
E
I
think
this
is
the
thing
I
have
to
discover.
I
also
have
to
discuss
with
alice
and
aaron
ciao
and
also
alex,
but
this
was
the
impression
I
had
when
I
take
a
look
on
conveyor.
So,
as
I
said,
please
excuse
me
that
I
said
it
in
such
a
hard
way,
but
that's
what
this
was.
The
impression
impression
I
got
through
this.
E
Jen,
please
let
let
let
me
don't
forget
that
we
take
this
off
in
the
next
in
our
next
meeting
and
then
we'll.
E
Then
everything
everyone
will
be
there
and
we
have
a
common
common
opinion.
C
D
I'm
sorry
I
was
muted.
I
just
shared
my
screen
here
with
some
note
puttings,
I'm
just
putting
some
notes
here.
First,
I
have
this
as
an
action
all
right.
So
I
guess
we
go
to
the
next
item.
Olek
for
captain
incubation
status
and
due
diligence,
follow-ups,
I've.
D
He
will
try
the
meeting
in
about
15
minutes
right:
okay,
okay!
Well,
let's
go
to
the
next
part
here:
potato
head
admin,
triage.
E
This
is
a
pretty
hard
part.
I
think
george
brought
this
up.
Currently
we
have
some
pure
requests
pending
and.
E
And
yes
well,
let's
say
one
in
the
tag
and
the
second
one
is
chris
and
therefore
I'm
trying
to
get
the
to
get
the
permissions
at
the
moment
and
then
we
can.
We
can
do
all
of
this.
D
Okay
sounds
good,
since
oleg
is
not
here
just
a
few
updates
that
we
discussed
to
today
what
we've
been
doing
so
one
thing
we
we
are
trying
to
get
more
into
social
media
and
the
this
is
a
desire
from
last
year.
Since
our
talks
on
kubecon
n,
a
and
china
many
people
didn't
didn't
know
like
the
tag
existed.
D
So
we
are
getting
a
twitter
handle.
We
got
actually
twitter
handle
for
tag,
app
delivery
and
we
are
going
to
write
a
blog
post
on
introduction
to
app
delivery
and
we're
going
to
put
it
try
to
first.
Do
it
on
github
pages.
D
We
also
would
like
to
have
a
discussion,
but
we
are
going
to
do
it.
Perhaps
in
the
next
meeting
regarding
the
basically
governance
and
access
that
for
for
chairs
working
group
chairs
and
the
maintainers
we
need
to
just
to
have
we.
D
We
are
going
just
to
put
on
a
on
a
page
on
our
github
project,
the
the
current
process,
how
it
is
like
how
the
structure
is
basically
the
working
group
chairs
they
have
merged
to
ma
to
main
permissions,
but
others
can
only
pr-
and
just
maybe,
for
you
all
to
think
about
like
to
or
to
propose
to
us
or
like
explain
how
you
govern
your
own
communities.
I
know
that
githubs
and
the
open
githubs
have
their
like
they,
they
do
their
own
stuff
as
well.
D
So
maybe
we
can
have
a
bet,
a
discussion
on
the
best
way
to
govern
these
and,
at
the
same
time,
not
being
like
making
people
stuck
and
having
somebody
just
like
gatekeeping,
but
at
the
same
time
keep
things
just
like
have
some
sort
of.
D
E
Also,
currently,
it's
mainly
about
it's
mainly
about
how
our
tech
works,
how
working
groups
work
because
we
we
are
attack
which,
which
consists
of
of
of
some
working
groups,
but
we
have
no
defined
process
for
that,
and
these
are
things
we
should
describe
in
the
future
and
should
should
raise
some
clarity
about
how
arched
repo
works,
how
or
how
the
commissioning
works
and
how
we
get
to
working
groups
and
how
chairs
are
elected
and
so
on.
D
Yeah
we
are
getting.
We
are,
I
think,
the
the
tag
that
has
like
quite
a
few
working
groups
active
at
the
moment,
so
we
are,
but
we
need
to
think
about
away
because
it's
a
bit
of
yeah
like
sometimes
it's
not
so
clear.
Like
thomas
said
and
yeah,
we
don't
want
to
make
it
be
like
gatekeepers.
D
Another
thing,
oh
yeah,
and
the
thing
is
that
we
need
to
deal
with
the
limitations
of
github,
because
github
doesn't
have
yeah
like
the
way
we
do
permissions
and
stuff
that's
on
a
repository
level,
it's
a
bit
of
a
limit,
a
limited
thing.
Another
thing
that
I
forgot
is
that
I
spoke
to
the
chaos
engineering
working
group
and
their
charter
is.
They
believe
there
is
ready,
but
they
are
just
going
to
review
the
last.
D
They
acted
upon
the
latest
observations
that
the
other
tags,
because
chaos
engineering
is
like
cross
tag
as
the
the
working
group.
That's
more
crosstalk,
so
the
other
tags
gave
their
observations
on
the
charter.
If
you
would
like
to
take
a
look
and
they
will
discuss
more-
like
define
just
the
final
draft
on
their
next
meeting
on
friday.
D
So,
after
that,
we
should
be
able
to
just
make
a
formal
proposal
for
the
tlc,
even
though
they
are
already
running,
but
just
so.
We
have
it
also
the
same
way.
The
other
tags
are
formally
on
the
toc
and
also
bring
them
under
our
on
under
our
project
as
well.
A
D
So
that
is
it
on
my
side
of
updates?
D
So
please
yeah,
we,
we
are
ready
to
hear
your
incubation
status
and
follow-ups.
F
So
actually
we
briefly
discussed
the
meeting
on
january
fifth,
but
it
was
rather
unprepared,
so
I
can
summarize
what's
going
on
now,
we
are
still
waiting
for
the
cftoc
to
review
the
application
and
to
provide
feedback
on
the
due
diligence
document
sent
off
by
the
delivery.
F
The
initial
expectation
was
that
it
would
happen
on
january
18th.
So
that's
why
I
was
optimistic
about
today's
meeting,
but
actually
the
tvc
meeting.
Yes,
they
didn't
happen.
So
this
is
basically
the
same.
If
you
go
to
the
proposal,
there
is
update
with
the
current
status,
so
the
second
link.
F
Basically
what
happens
on
the
captain
side,
we
are
working
on
tracing
feedback
from
the
track,
including
having
public
roadmap.
We
expanded
to
include
more
items
with
regards
to
community.
We
are
talking
about
technical
roadmap,
so,
for
example,
thomas
came
up
with
a
proposal
for
guitars
for
captain
cap
65
and
we're
currently
discussing
crediting
to
the
roadmap.
I
think
for
other
technical
topics.
We
also
work
on
growing
system
integrations
with
other
cncf
projects,
including
somebody
related
to
application
delivery,
and
hopefully
it
will
be
more
integrated
with
the
captain
ecosystem
and
withdrawing
adoption.
F
Last
but
not
least,
we
are
working
on
getting
contributors
and
maintainers
from
other
companies
so
that
it's
more
diversified
in
terms
of
contributions
and
company
investment,
which
is
again
a
strong
requirement
for
graduated
projects
in
the
sincere.
But
we
are
working
ahead
so
that
we
can
build
a
sustainable
community
soon,
so
we
already
have
jurgen,
who
is
now
employed
by
microsoft.
F
F
So
this
is
an
update
generally
being
the
queue.
So
since
you
have
to
see
reviewed,
multiple
sandbox
applications
and
soon
they
should
start
these
incubating
projects.
The
next
meeting
is
february,
2nd,
I
believe-
and
hopefully
the
captain
application
will
be
reviewed
by
that
time
and
yeah
fingers
trust.
We
will
get
a
decision
by
kubecon,
because
if
it's
accepted,
cryptcon
will
be
a
target
for
marketing
etc,
and
we
also
plan,
like
captain
community
day
at
kubecon
in
valencia
in
may,
to
be
announced,
stay
tuned,
but
just
in
case
everyone
is
welcome
to
join.
E
Question
yes,
I've.
E
Okay,
we
discussed
another
thing
today
and
I
think
chris
or
joshua
might
have
an
opinion
on
that.
So
we
saw
that
they
are
it's
george,
okay,
so
we
saw
that
that
the
cncf
preferables
are
takes
and
so
on
to
have
their
meetings
not
in
soon,
but
in
it's
called.
How
is
it
called.
E
A
E
B
E
Okay,
good
thing:
I
think
we
should
discuss
this
further.
Another
thing
chris,
I
think
you
are
there
for
the
foreign
group.
Is
there
any?
Are
there
any
updates
on
the
working
group
or
about
the
voting
process
of
the
new
working
group?
Here.
E
B
We
have
that
governance.
Actually
I
have
it
pulled
up,
I'm
sure
it
linked
real,
quick
as
soon
as
I
can
find
it.
The
the
election
process
is
defined
in
the
docs
thanks.
Thankfully,
it's
not
like
we're
missing
governments
there.
It's
just.
I
have
to
find
the
tab,
which
basically
means
open
a
new
tab
governance,
so
yeah
there's
the
actual
link
to
the
elections
section.
So
I
think
we're
waiting
for
nominations
right
now.
I
just
self-nominated
myself
yesterday
afternoon
and
I
think
voting
will
start
next
friday.
B
E
So
please,
please
don't
forget
to
notify
us
when,
when
this
is
elected,
because
we
also
have
to
pay
this
to
the
qc,
so
at
le
at
least
we
will
announce
the
new
member
in
the
next
year's
meeting
after
this
is
voted.
E
D
No
not
at
the
moment
yeah
not
yet
sorry.
My
internet
went
down.
D
E
Thank
you
for
your
time
and
thank
you
for
attending
today's
meeting.
Yes,
we
will,
we
will
try
to
find
out
how
to
proceed
with
conveyor
and
just
see
you
again
in
two
weeks.