►
From YouTube: TAG General Meeting - 2023-04-05
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
A
So
Josh
I
think
the
kubecon
topic
is
mostly
by
you
right.
B
Yeah
yeah,
so,
let's
see
I
put
up
there
get
stickers
because
that's
just
it
would
be
really
nice,
as
we
discovered
in
our
internal
chats
that
there
are
Tag
app
delivery.
Stickers,
I
just
put
that
down.
If
we
could
get
those
that
would
be
very
cool,
that's
kind
of
minor
the
other
stuff
is
more
significant.
B
So
we
posted
about
our
meetups
that
we're
planning
the
big
one
on
Tuesday
afternoon
and
then
we'll
have
the
booth,
Wednesday
and
Thursday,
which
is
kind
of
ad
hoc,
but
we
also
set
an
hour
at
the
end
of
our
time,
both
both
of
those
days
for
potentially
lightning
talks
and
meetups.
B
If
people
are,
you
know
interested
in
giving
you
know
an
Innovative
lightning
talk
put
that
in
submit
that
I
I
mean
I'll
Retreat
retweet
and
do
the
kinds
of
things
that
I
can
do
on
Monday
I'm,
not
a
huge
marketing
person,
but
whatever
anyone
else
can
can
do
to
to
attract
folks
or
the
idea
is
basically
at
the
Meetup
on
Tuesday
afternoon
to
talk
about
some
of
the
work
we
have
in
Flight
like
platforms
related
work,
maybe
the
artifact
stuff
I
know
Scott.
B
You
all
have
conferences
that
day
too.
That's
the
hardest
part
of
the
whole
pre-day
and
then
have
also
like
part
of
the
time
dedicated
to
lightning
talks
on
innovative
ideas,
and
you
know
just
short
things:
400
level
things
that
might
be
relevant
to
the
group.
Now
we
have
six
I'll
just
say
that
straight
up,
maybe
I
should
but
yeah.
We
want
more
I'll
put
in
some
more.
What
I
was
gonna
actually
ask
is
if
people
want
to
meet
on
next
Monday
or
Tuesday
to
kind
of
finalize.
C
B
C
B
Yeah,
that's
what
I'm
away
for
right
now
too,
but
Tuesday!
So
then,
maybe
Tuesday
at
1700,
which
would
be
I,
think
one
o'clock
or
two
hours
later
than
right
now
sorry
about
11
o'clock.
Right
now,.
A
B
I
actually
saw
kpt,
I
actually
saw
them
in
the
sandbox
like
a
couple
days
ago
and
was
thinking
we
should
invite
them.
Although
Scott
I
know
that
might
be
more
get
Ops
but
I'd
love
to
to
talk
to
them.
You
know
34.,
so
maybe
that's
a
I
love
that
suggestion.
I
always
ask
people
to
present,
maybe
at
the
yeah.
A
And
I
let
the
two
of
us
think
who's
going
to
do
it
today,
we're
not
doubling
work,
but
that
that's
an
idea
I
had
yesterday.
I
was
like
actively
reaching
out
to
them
to
projects
again
because
they
should
actually
pretty
easy.
Yeah
yeah.
B
When
we
could
just
we
can
reach
out
to
them,
we
could
just
ask
them
like
hey.
Would
you
mind
just
I
guess
we
can
even
put
in
for
them
in
the
in
the
cfp
form?
You
know
whatever's
easiest,
trying
to
make
this
productive
for
everyone
and.
A
Even
the
project
reviews
that
we
have
under
attack
app
delivery,
so
that's
Q,
Plus
score.
A
chord
Miss,
obviously
open
feature
is
still
there
go
zero
localhost.
What
was
it?
Captain
Dapper
cross,
plane,
Harbor,
located
review
Kudo
for
sandbox
yeah,
maybe
reaching
out
to
these
projects
and
re-engaging,
and
just
adding
the
link
to
the
meeting
notes.
B
Yeah,
okay
and
if
they
agree
either
they
can.
You
know
that
cfp
form
is
right
there,
just
a
Google
doc,
either
they
couldn't
put
it
in
or
if
you
know
we
can
put
it
in,
although
it's
probably
best
to
ask
them
so
they
feel
committed.
So
then
the
question
is
like:
do
you?
Will
you
reach
out
to
some
of
those
I
mean
I'll,
try
I,
that's
that's
always
the
the
kicker
will
like
will
I
be
able
to
get
to
it
in
time.
So.
A
My
plan
is
I,
would
just
tomorrow
morning,
my
time
just
post
it
on
all
of
the
issues,
so
not
a
big
deal,
a
massive
and
then
looking
at
some
of
the
other
projects.
I
think
we
have
a.
A
B
B
A
Yeah,
let's
think
on
those
and
just
quickly
going
through
some
of
them,
but
these
are
already
in
sandbox,
so
right
they
are
already
accepted
to
sandbox.
That's
why
they're
there
no.
A
A
Yeah,
okay
kpt
would
be
an
obvious
candidate.
The
tour
first
thing
can
once
somebody
does
something
and
reaches
out
the
project.
Just
let
I'll
let
you
know
you.
Let
me
know
so
that
we
just
don't
double
the
work.
B
Yeah
that'll
be
great
yeah,
no
problem
at
all,
so
yeah
and
let's
plan
I'll
send
out
how
to
do
an
invite
I'll,
send
them
an
invite
for
for
Tuesday
at
1700.
To
sync.
You
know
at
least
it's
a
it's
a
it's
a
point
in
the
sand.
If,
if
we
can't
actually
get
on
a
call,
we'll
just
do
an
async,
but.
B
B
Yeah
that
was
I
I
put
that
on
there
just
to
think
about
I'm,
not
even
sure
so,
like
you
know,
we've
got
the
the
chairs.
You
know
some
of
us
will
be
there
I'll
be
there
when
I
can
I
mean
I'd
love
to
be
a
red
hat.
A
little
too
they'd.
Love
me
to
be
you
know:
Thomas
is
gonna,
be
there
some
I
think
Alex
said
he
would
try,
but
if
others
want
to
come
other
people
that
are
participating,
you
know,
maybe
we
should
open
that
up.
B
Make
that
easier,
that
that
was
my
thought
like?
Can
we
get
other
folks?
This
planning
dock
is
open,
so
you
know
if
somebody
wants
to
wants
to
contribute.
I
know:
Abby
bangzer
had
volunteered
she's
she's
been
very
helpful
so
that
she's
gonna
help
me
out
on
Thursday.
If
somebody
else,
you
know
has
some
time
and
wants
it's
a
good
chance
to
be
in
the
project
Pavilion
and
and
meet
you
know,
certainly
sandbox
I
don't
have
a
booze
otherwise,
and
everybody
else
that's
around
there.
B
E
Hey
Scott,
so
I
was
just
I
was
just
noting.
There
was
talk
about
some
dates,
so
I,
just
I
I,
put
one
item
that
way
you
haven't
gone
to
yet
on
the
agenda.
E
There's
not
really
much
to
say,
except
for
open,
git
Ops
is
having
a
project
meeting
on
Tuesday
and
we
really
encourage
everyone
to
come,
but
that's
part
of
so
it's
part
of
saying,
hey,
what's
going
on
with
the
get-ups
working
group,
but
also
just
to
fit
into
if
we're
thinking
about
times
on
Tuesday
just
wanted
to
make
everyone
aware
of
that.
B
Yep,
it's
I
think
it's
worth
bringing
up
with
the
group
here,
like
the
pre-day
I
love
the
prettiest
I
like
to
meet
everybody,
but
it
feels
fragmented,
like
I'm,
disappointed
that
you
know.
I
won't
get
to
talk
to
the
get
Ops
folks,
because
there
will
be
a
flux,
one,
an
Argo
one
and
open
get
Ops
one
and
there's
a
few
others
like
that
too.
So
yeah
there's
actually
openshift
Commons,
which
is
where
I'll
be
in
the
morning
with
Karena,
so
yeah.
It
just
throws.
A
Into
them,
it's
honestly
a
bit
of
a
mess
with
all
the
project
meetings
right
now,
yeah,
because
there's
so
many
of
them
I
think
I'm
I
have
like
four
meetings
in
parallel.
That
I
should
attend
yeah,
which
is.
B
B
If
we
could
do
something
that
you
know
these
could
be
sub
tracks,
I'm,
not
sure
how
to
do
it,
but
somehow
that
we're
all
sharing.
This
is
the
one
chance
that
all
of
us
are
in
one
place.
Yeah,
it's
just
a
thought.
D
A
Can
just
take
one
of
the
slots
I
think
we
should
break
them,
maybe
down
into
smaller
slots
and
then
take
one
I
mean
you
can
basically
show
up
anytime
and
talk
about
it
and
then
feel
free
to
advertise.
It.
D
A
B
Yeah
we
could
take
because
we
we
explicitly
set
a
time
like
the
idea
of
setting
a
time
for
the
Meetup
was
like
okay,
maybe
20
people
will
come
together
around
that
time
and
share
with
each
other
rather
than
you
know,
be
it
scattered
all
over
the
whole
time.
B
So
we
could
try
to
use
that
and
say
this
one's
going
to
be,
if
you're
interested
to
Scott
I'm
kind
of
looking
at
you
like.
If
you
want
to
get
Ops
Focus
theme
from
2
30
to
3
30
on
Wednesday,
you
know
the
advantage
might
be
Tuesday,
not
everybody's
there,
it's
a
little
more
yeah,
but
that
would
be
great
and
make
it
easier.
Yeah.
E
Yeah,
you
know
I
wish
well
not
I
wish
no
time
travel
here,
but
maybe
for
future
kubecons.
We
can
work
with
the
Linux
Foundation
staff
to
event
staff
to
consider.
Maybe
we
could
have
a
room
or
something
per
tag.
You
know
per
active
tag
yeah
that
way
that
way,
it
would
make
it
easier
to
do
these
kinds
of
things
and,
as
as
I
think
was
it
you
Josh
who's.
E
Who
mentioned
you
weren't
going
to
be
able
to
come
to
all
the
get
UPS
things
because
there's
so
many
of
them
right,
yeah
like
we
could,
for
example,
have
at
least
perhaps
consider
a
TR,
whether
it's
a
track
or
whether
it's
just
related
to
the
tag
I
think
there's
there's
real
value
in
having
session
or
sorry
having
in-person
meetings
and
connected
time
that
are
outside
of
the
scope
of
of
presentations
of
scheduled
presentations
during
kubecon.
You
know,
so
that's
why
I
don't
I
think
outside
of
something
like
a
track
for
sessions.
E
It
would
be
good
to
have
something
like
this,
because
we
need
project
meetings.
For
example,
this
get
UPS
meeting
is
primarily
to
discuss
the
topics
that
have
come
up
in
the
discussions
through
the
meetings
from
various
projects.
You
know
so
so
at
least
I
mean,
for
example,
that
one
and
then
I
know
that
there's
platforms,
working
group
and
there's
another
proposed
working
group
coming
up
and
there's
others.
So
maybe
I
don't
know
something
to
think
about.
E
But
for
this
one
I
want
I
wonder
if
we
don't
want
to
fragment
it
even
further
and
just
maybe
ask
the
tag
to
promote,
at
least
for
the
get
up
side
of
things,
promote
the
few
events
that
already
on
the
docket,
including.
E
Because
it's
like
it's
from
eight
to
eight
to
twelve,
so
it's
like
it's
four
hours,
so
I
think
if
people
can
come
in
sometime
during
that
window,
most
like
I
would
think
you
know
and
if
they
can't
I
think
we'll
just
do
whatever
else
we
normally
do.
You
know
what
I
mean
like
just
connect:
async.
B
E
Essentially,
yes,
yeah
to
blog,
post
or,
however
else
we
want
to.
We
will,
however,
else
the
tag
wants
to
announce
things
and
say
here's
our
presence
at
at
at
kubecon.
You
know,
and
that
and
that
for
future
and
I
probably
could
have
summarized
that
a
little
faster,
but
in
for
future
kubecons,
perhaps
we
could
think
more
about
structures
like
that
like
having
perhaps
I'm
just
throwing
it
out
there
like
a
room
for
for
the
tech
or
something.
A
And
we
have
the
project
meetings
but
they're
all
at
the
same
time.
So
that's
something
by
the
way
this
is
the
blog
post,
either
create
your
own
one.
If
you
want
to
or
just
let
us
know
what
you
want
to
add
to
it,.
B
Yeah,
that's
true,
you
could
just
you
could
submit
a
PR
right
because
it's
in
the
it's
in
the
repo
now
we'll.
E
We'll
do
will
do
and
Eloise
that's
exactly
what
I
was
thinking
for
future
is
that
you
know
if
there
was
a
room
for
the
tag
there
would
be
no
chance
of
having
overlap
of
conflicts,
because
the
project
meetings
could
happen
within
that
room
is
what
I
meant
so
yeah.
A
A
All
right
Josh,
what
else
do
we
need
to
talk
about?
Coupon,
related
I?
Think
that's
pretty
much
it
right.
C
Yeah
I
just
have
a
quick
question
for
the
lightning
talks
that
we
want
people
to
give.
When
is
the
time
when
we
let
them
know.
B
Yeah
I
was
actually
thinking
about
that
we
should
I
might
want
to
add
to
the
blog
post
a
deadline
and
then
yeah.
We
need
to
get
back
to
them,
so
yeah,
I,
guess
yeah,
but
in
in
summary,
I
was
hoping
to
get
us
back
together,
Tuesday
or
finalize
on
Tuesday.
You
know
see
who's
submitted,
see
if
we
can
get
a
few
more
Alloys
you're
going
to
reach
out
to
the
projects,
maybe
we'll
pump
it
on
Twitter
or
something
a
couple
more
times
and
then
Tuesday.
Let's,
let's
finalize
the
strategy
and
get
back
to
people.
A
A
B
B
C
Time
slots
I'm
thinking
because
people
are
building
their
schedules
right
now,
like
I'm,
literally
building
my
schedule
right
now
and
just
want
to
know
you
know
how
should
I
prepare
when
should
I
prepare
yeah.
A
C
End
of
next
week,
that's
basically
right
before
the
conference.
Yeah
I
mean
it's
a
lightning
talk
should
be
fine,
exactly.
A
B
A
B
A
A
B
Yeah
I
have
to
come
up
with
mine,
too
cool,
okay,
I.
Think
if
you
all
yeah,
look,
if
there's
more
to
talk
about
speak
now,
you
know.
That's
always
the
last
question.
What
did
I
forget
to
ask.
D
B
Yeah
sure
I.
E
Oh
I
do
have
another
very
quick
question
about
this.
Just
because
of
timing
is
there
are
we
scheduling
the
folks
to
come
in,
be
at
the
booth
During
certain
times
or
is
it
kind
of
you
know,
catch
us
catch
Cannon
or.
C
A
E
Yeah
because
I
I
know
I
definitely
I,
know
Karina.
You
know
this,
but
for
other
projects,
for
example
such
as
Helm
there's
a
spreadsheet
of
like
here's,
all
the
time
slots
that
are
available
for
this
booth
and
we
just
break
them
up
and
then
just
the
folks
who
are
interested,
who
are
would
be
relevant
to
be
there
and
say:
hey?
Can
you
pick
some
slots?
Can
you
make?
Can
you
see
what
worked
with
your
schedule
and
folks
will
just
sign
up?
So
maybe
we
could
do
something
like
that.
B
I
think
that's
a
fair
request.
Yeah
we
can
make
that
table
in
there.
Let's
make
a
spreadsheet
or
or
make
the
table
more
finer,
grained,
okay,
I'll,
take
that
on
I'll.
Take
that
for
me
to
to
create
the
spreadsheet
and
share
it
and
I'll
try
to
get
that
done
by
today.
D
B
Yeah,
actually,
please
come
at
12.
I
mean
come
the
whole
thing,
of
course,
but
in
12
me
and
Abby
bangzer
and
Thomas
Vitale
and
Y
block
and
rafaely's,
but
solely
are
going
to
be
doing
a
panel
on
platforms
and
talking
about
our
paper
and
get
trying
to
get
a
little
bit
of
feedback
to
the
to
the
tag
and
the
working
group.
So
yeah.
We
have
a
brief
slot
there
and
then
we're
going
to
be
running
over
to
the
app
delivery
tag.
Meeting
yeah.
A
B
B
B
B
A
B
Yeah
I
gotta
subscribe
to
the
RSS
feed.
Actually
that
reminds
me
because
that's
what
how
I
would
notice
that's
what
I
was
thinking
like
if
the
RSS,
if
my
RSS
feed
picked
up
the
the
updated
thing
would
be
like
oh
I'll
read
it
again,
then
I
think
it
does
a
lot
of
times.
C
B
B
Yes,
so
I
guess
I'm
gonna
turn
it
over
to
Scott,
but
you
know
Scott
reached
out
to
us.
They
were
looking
to
form
a
group.
That's
working
on
a
project
related
to
you
know,
searching
and
understanding,
artifacts
and
surfacing
their
information
and
oci
is
mostly
focused
on
container
images.
So
they
came
to.
They
came
to
us.
It
seems
like
it
fits
very
well
in
our
Charter.
B
My
main
feedback
was
I'd
love
for
you
all
to
to.
You
know,
don't
just
think
about
this
one
small
part
of
artifact
search,
but
you
know
think
about
everything
related
to
artifacts
and
bring
in
artifact
Hub
and
anyone
else
that's
working
on
this
stuff.
So
we
tried
to
create
a
little
broader
Charter,
but
but
with
the
first
Focus
being
the
search
and
Discovery
stuff
so
Scott,
that's
my
I
guess
my
intro.
E
Great
I'm,
just
I'm
just
posting,
let's
see.
C
B
Yeah
so
yeah
so
Scott
this
morning
was
opening
I
see.
You've
got
the
GitHub
issue
which
you
pasted
in
there
you're
putting
you're
just
sharing
that
I
guess
with
the
yeah
and
then
I'm
also
mailing.
E
List
COC
there
we
go
post,
basically
just
buying
myself
like
10
more
seconds
by
telling
you
what
I
was
adding
yeah
so
so
so
hi
everyone.
There
is
an
interest
there.
Well,
there's
an
ongoing
effort
by
different
people
at
different
companies.
A
number
within
I
would
say
mostly
people
that
participate
within
cncf
and
some
who
haven't
yet,
but
but
will
to
improve
the
support
for
oci
artifacts
Within
Cloud
native
projects.
E
Many
of
them
are
cncf,
or
a
number
of
them
are
cncf
projects
at
different
levels,
from
sandbox
to
graduated,
for
example,
for
example,
Helm
flux,
I,
would
think
Arco
at
some
point
would
want
to
add
something
like
this,
but
potentially
kept
in
and
other
projects.
There.
B
Are
I
mean
just
that
like
Opa
uses,
oci
formats
image
package,
which
is
part
of
Carvel,
does
operator
framework
uses
some
formula
oci
package,
so
there's
a
bunch
and.
E
E
So
so
for
for
anyone
who
doesn't
I
want
to
just
assume
for
anyone
who
might
be
listening
to
this
recording
that
doesn't
know
what
we're
talking
about.
There
is
a
an
oci
artifact
spec
that
you
can
look
up
within
the
oci
within
the
oci
GitHub
repository.
That's
that's
part
of
this.
That's
part
of
the
distribution
spec
as
well,
or
at
least
pointed
to
from
the
distribution
spec.
So
so
it's
definitely
very
official.
It's
been
around.
E
The
initiative
has
been
around
for
three
or
more
years
and
there's
been
a
lot
of
work,
but
it
only
became
very
official,
not
really
that
long
ago,
so
the
actual
you
know
distribute
the
oci
distribution
spec.
That
includes
support
for
artifacts
and
yeah.
So
artifacts
are
really
just
any
so
they're.
They
follow
all
the
same
formatting
principles
and
and
and
specifications
as
the
CI
images,
except
they
don't
have
they're,
not
runnable.
They
don't
have.
You
know
like
root
FS.
E
They
really
just
have
they're
really
just
layers
of
of
objects,
of
layers
of
data
and,
for
the
most
part,
their
forward
and
Cloud
native
applications
they're
layers
of
configuration.
So,
that's
that's
really!
Where
we're
at
it's
be.
You
know.
E
The
value
of
this
has
really
increased
as
as
many
different
businesses,
often
governments
large
financial
institutions,
but
also,
but
also
anyone
else
very,
very
interested
the
security
as
they
are
adopting
this
into
their
workflows
for
applications
that
other
that
previously
didn't
have
support
for
oci
artifacts.
E
That
way,
it
allows
them
to
use
their
workflows
that
they
already
have
had
approved
for
so
many
years.
Basically,
ever
since
they've
we've
been
working
with
containers
right
so
throughout
the
history
of
of
kubernetes
and
CNC
projects
and
and
a.
A
B
Yeah,
like
Scott
the
distribution
spec
is
pretty
much
an
API
for
retrieving
packages
and
like
it
doesn't
really
like
yeah.
There
are
specs
to
talk
about
what's
inside,
which
would
be
the
image
deck
or
the
artifact
spec,
but
like
it's
really
nice
to
reuse,
the
Registries,
which
are
already
set
up
with
these
apis
and
all
kinds
of
extra
goodies
for
security
and
checkings
and
all
kinds
of
stuff.
We
use
it
for
all
the
other
artifacts.
Exactly.
E
Every
two,
every
scanning
and
other
tools
for
signing
and
verification
like
Sig
store
and
just
really
there's
a
there's,
a
lot
of
points
that
that
converge,
Josh
had
noted
elsewhere
that
this
this
has
already
been
very
public
for
a
long
time
that,
even
though
oci
stands
for
open
container
initiative,
it
does.
The
oci
spec
does
also
support
more
than
just
the
image
the
image
can.
The
image
containers
right
and,
however,
the
the
value
of
oh,
the
value
of
sorry.
E
The
focus
on
artifacts
within
oci
is
specifically
out
of
scope
for
the
oci
initiative
and
the
oci
initiative
working
groups,
and
that
kind
of
work
is
supposed
to
be
done
within
cncf.
Cncf's
Charter
also
has
a
very,
very
clear
line
that
says
that
that
cncf
activity
should
exclude,
essentially
oci
shouldn't,
become
part
of
the
scenes
yeah,
but
but
this
has
already
been
like
long
sense
resolved.
E
You
know.
Auras
project
has
been
part
of
cncf
for
quite
a
while.
Its
focus
is
specifically
on
API
apis
and
packages
to
support
working
with
these
kinds
of
artifacts
that
little
segue
was
probably
not
for
any
of
the
people
on
this
call.
That
was
really
for
anyone
listening
in
because
I'm
I
know
you
all
know
about
OCR
effect,
so
I
didn't
mean
to
bore
you
there.
E
So
this
point
really
is
about
asking
the
tag:
the
app
delivery
tag
to
create
a
working
group
for
artifacts
and
that
brief
history
is
initially.
This
was
a
group
focused
on
just
the
next
major
Improvement
for
artifacts,
which
is
for
search
and
Discovery,
but
then
you
know,
through
discussing
with
with
Eloise
Josh
and
Thomas
and
and
publicly
as
well.
E
The
idea
came
up
well,
aren't
there
other
improvements
to
artifacts
that
artifacts
and
packaging
that
folks
are
working
on,
and
that
could
potentially
be
a
good
convergence
here,
and
the
answer
is
yes,
so
that's
what
the
request
is
for
and
oh
thanks,
Leah
I,
didn't
I'm
glad
I'm
glad
that
was
helpful.
Okay,
cool
yeah,
yeah
I
never
mean
to
assume
because
yeah,
unless
someone's
working
with
a
specific
piece
of
technology,
it's
like
yeah.
What
was
that
again
yeah
so
anyway?
That
is
the
request.
E
The
issue
is
open
for
it.
There
is
the
statuses
there
is
a
charter
drafted,
my
understanding,
I
guess:
I
haven't
looked
at
this
piece
of
it,
but
my
understanding
is
Josh
is
sponsoring
this
already.
A
You
I
can
look
into
this
as
well.
I
mean
we
created
some
in
the
past
for
some.
We
got
like
for
the
easier
way,
because
the
official
working
group
to
Creation
involves
obviously
the
TUC
and
what
was
the
official
shares
and
everything
I
think
for
platform.
We
kind
of
like
accelerated
the
whole
thing
a
bit
to
put
it
that
way,
yeah,
but
we
should
I
mean
again
I'm,
also
supporting
it
and
I
can
work
with
the
cncf
and
how
to
get
this
done.
E
E
So
you've
already
essentially
done
what
you
need
to
do
and
the
the
at
Josh's,
prompting
I
think
from
your
prompting
gentle
nudge.
The
the
GitHub
issue
is
open.
This,
the
a
mailing
list,
item
or
post
has
been
created
both
in
this
tag
and
the
T
and
the
TOC
emailing
list.
A
E
E
Please
add
your
thoughts
to
this
GitHub
issue
thanks
and
blah
blah
blah,
so
I
think
we're
I
think
we're
pretty
I
think
we're
pretty
set
on
the
on
that
part
on
and
I
believe
in
terms
of
support,
you've
already
verbalized
it
Josh,
but
you
and
and
others
who
would
be
relevant
if
you
wanted
to
from
the
tag.
If
you
also
wanted
to
support
it,
you
really
just
need
to
list
your
names
in
the
dock
and
that's
it.
A
B
I
am
actually
the
one
who,
who
pushed
a
little
towards
say
your
remit
is
artifact
management.
Generally,
you
think
it
should
be
more
narrow.
A
Fine,
if
you
can
also
have
it
in
the
goals,
but
that's
what
I've
taken
away
from
that
conversation,
I
think
that
we
really
find
how
artifacts
are
actually
created
or
stored,
but
it's
really
about
how
we
handle
them.
Yeah
I
think
that's
how.
But
we
thought
about
searchability,
because
this
is
about
like
standard
metadata
definition.
E
Yeah
the
goal-
the
initial
goal:
well,
basically
like
a
number
of
us,
have
been
working
on
different
pieces
of
improving
artifact
support
within
projects
within
within
Helm
I,
know
well,
I
guess
Karina
Karina
maybe
dropped
off,
but
but
in
any
case,
I,
don't
know
why
I
haven't
really
mentioning
her,
except
for
except
for
like
she
knows
that
there
are
several
people
at
Red
Hat,
including
Andrew
block
who've,
been
helping
who've
been
helping
with
this
I've
been
working
on
this,
and
some
other
folks
at
who
are
still
at
weaveworks
are
have
still
worked
on
this
to
to
really
push
artifact
support
to
to
full
support
within
Helm
as
a
graduated
project,
so
that,
that's
probably
that's
probably
the
most
well-known.
E
Not
probably
it
is
the
most
well-known
example
at
this
point
or
the
most
highly
used
example.
E
But
there,
as
Josh
noted
there
are
others,
and
so
we've
been
trying
to
do
different
things
to
help
end
users
get
what
they
need
to
basically
not
just
augment
But,
ultimately
to
improve
generally
improve
artists,
artifact
support
and
this
question
came
up:
hey
aren't
there
a
number
of
different
package
types
out
there
and
and
I
think
one
of
the
questions
you
know
so
one
of
the
things
that
the
groups
will
seek
to
probably
the
idea
in
its
current
form
is,
as
a
general
as
a
group
to
generally
improve
artifact
support
within
the
cloud
native
Community
I.
E
Think
that's
one
of
the
things
that
we
can
certainly
look
at
is:
what's
the
difference
between
a
package
type
and
a
and
a
transport
type
you
know
or
a
formatting
type
like
so,
for
example,
oci
isn't
just
a
package
type,
it's
a
specification
for
delivering
packages
of
different
types.
E
B
One
of
the
things
that
I
am
seeing
like
from
my
vantage
in
the
platforms
group
like
what
we're
trying
to
look
at
is
each
of
the
capabilities
in
a
platform
and
what's
happening
in
those
areas,
and
how
can
we
reduce
complexity,
make
them
easier
to
use
and
definitely
in
the
artifacts
storage
space,
what
we
see
I,
just
posted
it
and
I
like
to
show
this
one,
the
one
in
artifact
Hub,
where
there's
20
different
kinds.
Some
of
these
are
oci.
Some
of
them
are
format
our
directory
hierarchies
and
GitHub.
Just
some
specific,
you
know
convention.
B
The
question
is:
can
we
find
some
synergies?
Can
we
I
don't
know
if
it's
oci?
Can
we
make
these
more
conventional,
more
close
to
each
other,
so
that
something
like
artifact
Hub
could
crawl
them
easily?
Somebody
can
contribute
new
things
and
that's
just
the
start.
I
mean
I
think
in
the
longer
term,
we'd
love
to
consider
other
kinds
of
artifacts,
whether
that's
software
packages
system
packages,
things
like
that
I
mean
that's
very
far
out.
B
But
how
far
can
we
take
oci,
you
know
and
find
standards
here
you
know
to
improve
security,
to
make
it
easier
to
use.
E
And
there's
just
one
more
point:
I
want
to
mention
that
this
is
not
an
effort
to
there
is
not
as
far
as
I
know.
In
fact,
I
wouldn't
support
an
effort
to
do
away
with
previous
formats
or
previous
weight
methods
of
delivery,
because
there's
still
some
question
in
some
people's
mind
anyway,
whether
whether
whether
oci
is
really
good
for
this
good
for
General
storage
of
artifacts
I
think
I
personally
think
it
is,
and
and
many
other
people
do
too
clearly
and
it's
being
used
very
widely.
E
But
you
know
it's
still
in
some
ways:
it's
still
in
the
early
phases
of
that.
So
the
goal
would
be
to
to
to
try
to
make
potentially
to
try
to
make
a
default
simplification
here
where
but
but
still
support
other
methods
of
installation
and
delivery.
E
Not
say
oh
we're
doing
away
with
everything,
but
you
know
but
Distributing
via
oci,
artifacts
and
I've
talked
with
Sergio
and
Cynthia,
who
who
are
two
of
the
maintainers
of
artifact
Hub,
but
probably
the
people
that
primarily
work
on
it,
who
were
contracted
by
Linux
Foundation
to
create
that
project
initially
and
who
still
do
about
this
and
there's
definitely
a
lot
of
interest.
There.
E
A
Version
negative
importance,
I
think
just
like
looking
at
the
at
the
working
group
goals.
I
think
we
should
be
that
that's
what
I
just
realized,
also
on
another
broken
group
proposal.
This
we
click
on
the
one
on
the
standardized
security
language
for
observability
data,
totally
different
topic
still
I.
A
Think
it's
important
to
say
like
what
is
the
actual
outcome
activities
are
in
there,
which
is
great,
but
maybe
what
are
I
think
what
might
make
sense
is
that
what
are
the
deliverables
and
the
next
step,
because
it
was
one
of
the
confusion
for
the
link-
is
still
one
of
the
confusion,
because
it's
mostly
maybe
a
syntactic
confusion
for
the
time
being
on
the
on
the
obserabilities
are
like?
A
A
I
think
that's!
What's
as
a
first
like
deliverable
is
still
kind
of
missing
the
activities.
Are
there
like
Gathering
stakeholders
and
so
forth,
but
specifying
like
what
do
you?
What
do
we
want
to
build?
And
what
is
it?
Definitely
that
we
do
not
want
to
build
like
I,
think
a
lot
of
actually
what
you
said
in
the
last
20
minutes,
Scott's
I
think
should
be
in
this
document.
E
Okay,
yes,
that
makes
sense.
So
what
I'm
hearing
is?
What's
ins
that
part
of
this
might
be
semantic
in
the
in
so
far
as
activities
could
be,
could
say
and
goals
or
something
like
this,
and
then
we
should
have
an
in
and
out
of
scope,
section.
A
A
A
Things
like
we
figure
out
like
some
use
metadata
that
uses
something
like
name
and
then
just
completely
makes
up
right
now,
others
use
just
entity.
Why
isn't
everything
called
name
things
like
this
I
think
it's
something
we
could
come
up
as
we
work
through
this
then
okay.
A
E
A
Just
saying,
if
you
figure
out,
for
example,
that
in
some
some
for
some
artifacts,
the
metadata
uses,
like
a
term
called
name
for
other
City
uses
a
term
called
and
I'll
type,
whatever
is
actually
the
same
thing.
Well,
this
is
the
entity,
but
it's
just
it's
called
differently.
That
would
be
things
that
could
be
easily
resolved.
E
Okay,
but
thank
you.
B
E
Okay,
so
I
added
this
I.
Thank
you
all
so
much
so
I
added
this
link,
I'll
just
paste
it
in
the
in
the
meeting
here
to
a
comment
where
I
tried
to
summarize
not
all
of
your
feedback.
But
what
you
were
just
asking
about,
and
you
know
I
don't
want
to
take
over
anymore.
That
I
know
you
you've
said
you
feel
it's
an
important
topic,
but
I
think
work
on
these
things.
E
You're
asking
for
about
the
specific
goals
or
work
products,
or
at
least
I,
think
we
have
more
products
but
like
goals
or
success
metrics
and
what
was
the
other
thing?
Oh
and
then,
what's
in
scope,
makes
sense,
and
we
can
do
that
after
the
meeting.
A
Yeah,
it
usually
causes
otherwise
confuses
in
meetings.
That's
what
this
is
to
realize.
Do
you
want
to
define
a
new
format
and
will
everything
know
we
don't
want
to?
We
want
to
do
exactly
this
yeah,
because
people
are
reading
this
stuff
and
it
just
came
that
was
actually
causing
some
confusion
yesterday
in
a
totally
different
topic.
A
I
think
that's
good!
Actually,
we
are
we're
done
with
today,
unless
anybody
has
a
very
original
topic,
just
looking
at
the
time,
10
minutes
to
the
hour.
Thank
you.
E
I
really
don't
think
I
have
any
other,
basically
just
to
kind
of
tie
it,
though,
on
on
this,
it's
just
simply
I
think
the
issues
are
out
there
and
or
the
issue
is
out
there.
The
the
mailing
list
posts
are
out
there
at
least
you've
already
connected
with
with
Toc
folks
yeah.
A
I'll
share
the
link
with
them
to
again
tomorrow,
because
today's
overwhelming
a
little
tomorrow
morning,
okay.
E
So
so
I
don't
think
we're
we're
blocked
in
any
way,
but
it
would
be,
but
the
go.
But
the
really
the
value
of
this
is
to
have
a
central
place
where
people
know
they're
officially
meeting
and
not
just
having
these
kinds
of
DMS
or
you
know,
direct
messages
with
like
groups
of
folks.
We
wanted
to
be
fair,
inclusive
and
transparent,
and
that's
really
the
big
value
of
saying
hey,
let's
make
a
working
group,
so
so
really
I
wouldn't
want
to
rush
the
process.
E
A
Yeah,
maybe
one
last
thing
here:
do
we
plan
to
engage
with
like
representatives
of
all
the
existing
initiatives
on-site
at
kubecon,
because
that
would
kind
of
be
convenient,
because
most
people
are
most
likely
going
to
be
there.
That.
E
Would
be
amazing
if
we
can
do
I
mean
I
know
it's
coming
up
very
soon,
if
we
can,
if
we
can
sort
this
out
before
kubecon,
absolutely,
even
even
if
it's
really
just
meeting
at
the
tag
Booth,
you
know.
B
E
A
E
I
I
just
noticed
Amy
has
joined
the
call
hi
Amy,
hey.
E
Up
yeah,
yeah
you're,
totally
fine
to
just
lurk
I
didn't
want
to
call
you
upper,
but
I
was
just
thinking.
Is
there
in
seeking
to
do
to
set
up
the
working
group
properly?
Is
there?
E
Is
there
anything
that
you
think
we
should
keep
in
mind
beyond
what
we've
already
done,
which
is
drafting
a
charter
connecting
with
looking
at
the
alignment,
the
correct
alignment,
both
the
fact
that
the
the
this
when
we're
talking
about
the
art,
the
proposed
artifacts
working
group,
that
the
alignment
both
that
it
should
be
part
of
cncf
and
that
it
it
makes
sense
to
be
under
Tag
app
delivery?
Not
maybe
some
separate
working
group
under
TSC
well.
F
So
here's
the
thing,
because
I'm
seeing
a
lot
of
comments
come
up
on
the
issue
that
you
should
probably
go
over
and
talk
to:
oci,
yes
and
and
realistically,
like
they
actually
meet
tomorrow
at
10,
A.M
Pacific.
F
They're
actually
going
to
be
meeting
over
at
kubecon
as
well
yeah.
F
Md
for
this
for
for
that
group,
I'm
connected
with
that
group
too,
which
is
why
I'm
like
the
just
so
you
know
they
also
have
an
in-person
meeting
at
kubecon.
So
my
normally
the
advice
would
be.
You
all
are
moving
in
exactly
the
right
direction,
but.
B
F
Because
you're
kind
of
colliding
between
a
couple
different
groups
I
think
it's
best
to
be
able
to
go.
Make
sure
that
you're,
actually
talking
with
oci
oci,
has
a
much
different
and
understanding
around
working
groups
and
how
they're
formed
and
and
what
their
space
is.
So
because
you're
in
this
interesting
place
of
being
able
to
have
like
this
combination
between
the
two
I,
would
suggest
being
able
to
go
and
like
kind
of
just
drop
over
into
oci
and
get
their
take.
E
I
love
that
I
didn't
know
they
were
doing
something
at
kubecon.
There
is
cross-pollination
discussion
already
in
the
interested
parties,
but
yes
think
that
is
really
Sage
wisdom.
Thank
you.
I
think.
F
Touching
so
much
like
oci
oci
is
actually
perfectly
capable
of
being
able
to
do
working
groups.
They
do
do
them
a
lot
but
they're
a
little
more
structured
and
they're
a
little
different.
So
you
know
go
take
a
look
at
that.
Absolutely.
B
Was
just
gonna
chime
in
and
in
explaining
a
little
bit?
This
is
that
I,
you
all
did
work
with
them
on
a
working
group
for
this,
and
this
has
come
up
and
they
actually
asked
for
a
lot
of
this
work
that
happened
in
cncf.
We
should
talk
to
them
again,
I'm,
not
saying
right.
F
That's
because,
like
I,
think,
the
interpretation
on
the
issue
is
the
Tob
has
maybe
evolved
over
in
oci
and
and
it
might
have
been
like
work
that
happened
some
time
ago.
There
was
some
work
that
did
happen
in
red
artifacts
last
year,
but
it's
worth
being
able
to
pull
together
and
see.
Does
this
actually
make
sense
so.
E
So
Amy,
just
in
terms
of
okay,
so
that's
tomorrow
morning
at
10,
you
said:
10
a.m.
F
Yeah
10
a.m,
but
there's
also
like,
if
somebody's
going
to
actually
be
at
capecon,
like
Drop
yourself
on
the
agenda,
that's
also
listed
in
the
the
hack
and
D
for
them
as
well.
E
Absolutely
that
sounds
great
I
will
do
we
know
what
time
zone
we're
talking
tomorrow.
E
You
right
right
right,
right,
right,
exactly
Okay,
so
so
I
will
I
may
join
that
one
a
little
bit
late,
but
I
will
I
will
put
myself
on
the
on
the
agenda
and
I
will
definitely
plan
to
be
there,
because,
if
we're
not
able
to
get
to
that
agenda
item
during
the
oci
meeting,
are
you
saying
that
it
would
be
best
to
wait
until
after
kubecon
to
so.
F
They've
got
a
meeting
they've
canceled
their
April
20th,
but
then
you
can
track
towards
being
able
to
do
probably
like
oh
gosh
tractor's,
like
March
4th
yeah.
F
Least
letting,
like
the
the
folks
on
the
the
issue,
know
that,
like
oh
yeah,
we'll
come
back
and
like
start
looking
at
this
as
well,
might
be
appropriate.
But
up
to
you
thank.
B
Oh
I
think
we
lost
always
so
I
guess:
I
will
help
us
wrap
this
up.
Thanks
Scott
for
all
that,
and
thanks
for
taking
the
lead
on
talking
with
oci
yeah
makes
a
lot
of
sense
good
stuff
all
right.
If,
if
that's
all,
let's
just
wait
five
seconds,
anyone
want
to
bring
anything
else
up.
F
I
think
I'm
actually
running
the
oci
meeting,
so
it'd
be
good
to
be
able
to
have
more
vagina
there.
Oh.