►
From YouTube: TAG General Meeting
Description
TAG web site: https://tag-app-delivery.cncf.io/
TAG Slack channel: https://cloud-native.slack.com/archives/CL3SL0CP5
TAG git repo: https://github.com/cncf/tag-app-delivery
TAG meeting notes: https://docs.google.com/document/d/1OykvqvhSG4AxEdmDMXilrupsX2n1qCSJUWwTc3I7AOs/edit
C
B
D
E
Too,
you
can
use
a
pillow
background,
something
like
that.
Yeah
there.
B
E
F
D
B
All
right
well
we're
three
minutes
past
the
hour.
We've
got
a
pretty
good
Quorum
here,
I
think
I
think
we
should
go
ahead
and
start
I
pasted
in
the
notes.
If
you
want
to
put
in
your
put
on
your
name
there,
yeah
official
record
of
attendance,
we're
recording
here.
B
Let's
see
a
lot
of
times,
we
start
out.
Is
there
any
anyone
new
here
that
wants
to
introduce
themselves
just
to
give
us
an
idea
of
where
you
want
to
help
or
what
your?
How
come
you're
joining
today,
I
do
see
a
couple
new
folks.
G
Yeah
I
think
we've
been,
we
use
threaten
more
regularly
this
meetings,
sir
Josh.
We
took
a
kind
of
pause,
so
we
are
getting
back
into
the
momentum.
Yeah
I
can
introduce
myself,
and
the
team
from
latest
also
is
here.
Can
I
go
ahead,
introduce
myself
sure
yeah
hi
hi
everyone
nice
to
meet
you
all?
It
was
the
initial
maintainer
founder
co-pounder
of
litmus
chaos
project,
also
Tran
pondered
and
run
a
few
other
companies
before
ending
up
at
running
chaos.
G
Engineering
at
harness
Inc,
currently
apart
from
maintaining
litmus
project,
I,
also
hit
the
chaos
engineering
practice
performance
where
I
work
with
large
Enterprise
customers,
learning
from
them,
and
you
know
trying
to
make
sense
of
what's
going
on
the
chaos
engineering
industry
and
how
we
can
improve
things
to
the
project.
So
that's
my
Charter
I
have
with
me
a
couple
of
other
team
members
from
eight
months
project,
as
well
as
we're
giving
an
update
here
today
we're
doing
Organics.
F
Yeah,
hey
everyone:
this
is
prithvia
I've
been
leading
the
litmus
Community
since
the
last
three
years
and
I
think
even
I'm
joining
this
call
after
a
long
long
time
but
nice
to
see
you
all
and
nice
to
see
the
updates
with
Tag
app
delivery
and
other
than
that
I've
been
working
I'm.
Also
cncf,
Ambassador
and
I've
been
working
closely,
organizing
kcd,
Bangalore
and
other
stuff
in
the
cncf
Paradigm.
Thanks
thanks.
Everyone.
E
Okay,
I
can
go
next
time,
hey
everyone.
This
is
Saina
and
I'm
a
senior
software
engineer
at
harness
and
also
one
of
the
maintainers
of
litmus
kills,
and
it
has
been
like
more
than
one
one.
One
and
a
half
years
I've
been
contributing
to
litmus
thanks
for
having
me
here.
C
C
B
Very
cool
I
was
listening.
I
was
kind
of
walking
around
your
place
to
sit
in
this
office,
I'm
kind
of
thinking.
You
know,
since
we're
already
talking
with
you
all
in
the
litmus
stuff.
Why
don't?
Why?
Don't
we
do
the
project
presentation
first
thing
and
then
the
couple
of
other
items
we'll
do
after
you
guys
want
to
just
get
started.
I
think
I.
Think
we
like
to
allocate
about
15-20
minutes.
B
You
know
and
we'll
ask
questions
as
we
go.
I'm
gonna
go
and
mute.
G
Okay,
hopefully
you're
seeing
the
red
screen
multiple
monitors,
yes,
okay,
yeah
I
have
15
minutes
are
prepared.
I
will
give
a
quick
update
on
the
project
itself.
We
are
an
incubating
level
project
at
cncf,
just
a
quick
background,
this
project-
you
know
we
started
about
six
years
ago,
and
then
we
developed
at
the
company
chaos
native
and
then
it
became
a
Sandbox
project
and
then
incubating
project
around
that
time
the
entire
team
moved
to
harness.
G
Where
we've
been,
you
know
really
busy
learning
from
some
of
the
Enterprise
and
deployments
as
well.
So,
along
with
you
know,
adding
the
same
thing
back
to
you
know
open
source
World,
some
of
them
right,
so
this
project
update
is
primarily
focused
on
you
know.
G
What's
going
on
in
the
community,
you
know
in
the
last
one
year
after
we
became
in
incubating
project
and
also
you
know
some
of
the
main
significant
enhancements
that
we're
doing
the
next
quick
release
is
coming
and
also
in
the
end,
I'll
give
a
very
quick
update
on
the
chaos
in
jingua
group
probably
will
see
some
more
15
minutes
update
in
the
next
meeting
to
provide
a
detailed
update.
So
since
incubation,
the
project
has
been
steadily
growing
in
terms
of
adoption
as
well
as
contributions.
G
G
Just
before
the
incubation
we
generally
reached
out
to
the
community-
hey,
you
know,
if
you're
using
litmus,
please
add
yourself
as
an
adopter.
We're
not
been
doing
that.
Maybe
you
know
before
the
graduation.
G
Will
efforts
we'll
we'll
go
and
do
that,
but
organically
around
eight
new
adopters
have
come
in
and
we
believe
there
may
be
another
50
to
60
out
there
who
would
want
to
come
in
and
you
know
add
themselves,
but
in
terms
of
contributors
too,
we
have
added
around
15
new
contributors
and
they're
about
close
to
3,
000
plus
commits
and
we've
been
adding
new
maintenance.
Some
two
to
three
outside
honest.
G
Then
we
actually
put
in
new
members
as
part
of
our
core
team
right
who
became
maintenance
and
then
slack
has
been
active.
You
know,
there's
there's
a
lot
of
litmus
usage,
but
we
come
to
know
primarily
from
support.
Needs
Community
Support
when
they
come
and
ask
from
slack
channels
and
in
terms
of
adoption,
the
the
growth
has
been
really
good
since
the
early
this
year,
because
some
large
users
have
been
using
litmus.
G
So
if
you
see
the
docker
pulls,
there's
been
a
steady
increase
in
terms
of
you
know
the
usage
of
the
litmus
itself,
so
I
think
you
know
that.
That's
that's
a
good
encouraging
thing
in
terms
of
reaching
about
million
million
poles
on
a
monthly
basis.
G
Now
coming
to
what
we
have
delivered,
I
mean
there
are
so
many
commits
these
are
some
of
the
top
level
enhancements
or
features
that
we
have
done.
A
good
number
of
additions
were
done
to
chaos,
faults
or
chaos.
Experiments.
One
of
the
primary
asks
was
now
that
infrastructure
was
here
all
good.
G
How
can
I
introduce
API
level
chaos
so
for
that
we
have
added
HTTP
chaos
being
used
pretty
much
heavily
and
also
added
some
gcp
and
AWS
related
experiments,
and
one
of
the
community
members
from
Orange
have
contributed
a
whole
set
of
springboard
experiments.
That
was
good
and
some
of
the
larger
users.
Some
banks
have
been
using
litmus
they've,
been
asking
for
Digital
support
and
randomization
support,
so
we
made
enhancements
to
Network
chaos,
Falls
and
runtime.
G
Apart
from
Docker,
we
added
continuity
and
cryo
as
well
and
c
groups
version
2
support
for
stress
chaos,
like
you
know,
CPU
memory
chaos
were
added,
so
these
are
some
of
the
high
level
details
of
how
the
experiments
are
being
improving
themselves.
In
terms
of
you
know,
when
large
number
of
previous
use
they
get
better
and
better
right
and
those
are
around
the
experiment
side
and
on
the
chaos
management.
G
The
orchestration
layer,
ligma
scales,
provides
a
centralized
console
where,
for
an
organization,
you
would
need
only
one
deployment
of
litmus
control
planes
and
then
hundreds
of
clusters
can
be
connected
or
thousands
of
names.
Spaces
can
be
connected
to
the
control
plane
and
they
can
run
chaos
from
it.
G
So
it's
already
a
stable
orchestration
platform
to
that.
We
generally
keep
adding
some
security
enhancements.
Where
how
you
can
configure
the
certificates,
then
some
of
the
apis
were
repacted
to
let
the
users
automate
the
chaos
experiments.
You
know,
as
per
the
regular
interests
and
one
of
the
issues
that
we
encountered
is
when
you
introduce
chaos.
G
You
know
very
aggressively
the
control
plane
agent
on
the
cluster
is
also
undergoing
chaos
and
gets
deleted.
So
some
topology
settings
were
added
so
that
you
know
within
Corden
the
top
or
you
know,
put
it
into
a
separate
namespace
or
a
node,
etc,
etc,
and
important
that
we
added
the
private
chaos
hubs
where
users
can
start
maintaining
their
own
version
of
chaos,
experiments
and
then
you
know,
maintain
it
like
the
code
and
we
also
significantly
improved
how
fast
a
new
chaos
Hub
can
come
on
board.
G
G
Similarly,
on
the
execution
plane
again,
the
major
enhancements
are
asked
from
the
end
customers.
How
can
we
scale
with
helper
pods
being
one
helper
part
for
the
entire
cluster
rather
than
you
know,
one
for
each
experiment
and
we
also
upgraded
to
the
new
SDK
version.
G
So
the
banks
reported
security
vulnerabilities
in
the
images,
so
you
know
we
started
continuously
updating
the
images
frequency
is
getting
done
and
also
some
communities
Community
users
wanted
to
deploy
the
execution
plane
in
an
automated
way
github's
way,
so
the
health
chart,
support
is
added
for
the
chaos
agents
and
also
some
support
is
added
because
we
moved
to
the
newer
operator
in
bigger
version.
There
was
a
support
that
came
into
that
and
again
litmus
CTL,
which
is
the
control
side
component.
G
For
for
litmus
a
more
user-centric
operations
were
added
credit
operations.
They
can
manage
it.
This
is
helpful
for
doing
some
script
based
automation
of
chaos,
so
this
is
again
Community
contributed.
They
went
ahead
and
then
you
know
enable
the
PRS
before
I
go
into
the
roadmap.
Maybe,
but
we
can
talk
about
some
of
the
community
activities
that
we've
been
doing
in
the
last
one
year
between.
F
I
don't
know,
I
can
go
next,
so
I
mean
we
started
off
with
cubecon
I.
Think
post
incubation,
one
of
the
main
things
that
happened
was
kubecon
EU
Valencia
and
we
have.
We
had
a
couple
of
talks
there,
a
maintainer
track
as
well,
and
unfortunately,
a
few
folks
couldn't
travel.
But
again
we
had
Ramiro
from
octeto
he's
been
a
contributor,
since
the
last
three
years
spoke
about
how
chaos
engineering
could
be
brought
to
Cloud
native
developers.
F
It
was
also
owned
by
Uma
and
then
I
think
we
got
some
good
traction
over
the
maintainer
track
as
well,
where
Siam
he's
from
sibo
he's
been
again
a
popular
Community
member.
He
spoke
about
the
use
case
at
CEO
of
equipment
and
again
the
project
meeting
as
well.
We
saw
some
good
amount
of
folks
good
amount
of
traction
coming
in
and
I
think
that
was
same
for
kubecon
n,
a
as
well
where
we
we
had
three
talks
again.
F
One
of
them
was
an
SLO
validation,
so
we
have
been
doing
some
good
work
with
another
cncf
project,
that's
iterate,
so
so
that
that
was
presented
by
shubham
and
srinivas
and
then
obviously
we
had
something
on
the
fintech
domain,
where
FIS,
which
is
one
of
our
adopters
as
well
from
FIS
and
nilanjan
from
the
litmus
Community,
went
on
and
presented
how
chaos
engineering
with
litmus
is
being
applied
on
the
fintech
side
on
my
next
slide,
so
this
cubecon
was
was
a
great
one
as
well
I
mean
in
the
last
few
months
we
have
seen
some
good
adoption
and
I
think
this
Con.
F
We
saw
some
organic
folks
new
folks
coming
in,
and
a
lot
of
new
folks
joining
in
was
the
surprise
because
you
know
have
people
coming
back
is
one
thing,
but
new
people
showing
interest
in
chaos.
Engineering
is
is
another
thing
and
I
think
one
of
the
main
questions
that
we
answered,
so
our
maintainer
track
was
about
security
controls
and
how
how
safe
chaos
experimentation
is
important
security
chaos,
engineering
that
was
about
our
maintainer
track,
but
even
at
the
booth
there
were
a
lot
of
new
questions.
F
Questions
about
Integrations
and
I
think,
overall,
both
the
cube
cons
have
been
pretty
successful
from
a
project
standpoint
and
moving
ahead
as
well
discussing
the
path
to
graduation
other
than
that
litmus
participated
in
chaos.
Carnival
there
were
around
nine
talks
and
a
lot
of
latest
adopters,
like
HCL
folks
from
Accenture
infra
Cloud,
Thailand,
API,
six.
They
they
talked
about
how
they
have
been
using
litmus,
why
they
chose
litmus
there's
been
a
project
comparison
or
there's
been
a
lot
more.
F
That
was
that
was
presented
in
terms
of
use
cases,
how
they
have
built
their
chaos,
engineering,
Journey
so
and
and
it
chaos
Carnival
again.
Litmus
chaos
has
been
a
community
sponsor
to
the
to
the
conference.
We
we
started
off
more
from
a
community
background,
and
now
it's
become
one
of
the
most
popular
chaos,
engineering
conferences
and,
litmus
being
so
evidently
present.
There
I
think
that
was
the
good
part
and
obviously
I
think
around
1000
plus
folks
as
attendees
getting
to
know
the
the
updates
it
has
been
has
been
phenomenal
for
the
project.
G
Yeah
described
to
that,
you
know
first
edition
of
chaos,
Carnival
maintenance
used
to
reach
out
for,
if
you're,
using
litmus
come
present
it.
But
now
we
are
giving
you
know
we
are
getting
more
and
more
cfps
and
we
are
almost
trying
to
choose
the
most
relevant
one,
so
it
definitely
is
acting
as
a
good
platform
for
showcasing.
You
know
how
they've
been
using
litmus
so.
G
F
F
F
So
his
tenure
just
finished
last
month,
I
mean
end
of
May
and
he
was
mentored
by
a
couple
of
maintainers,
Amit
Das
and
sign
Monday,
and
this
is
a
success
story
which
was
published
on
the
cncf
blog
as
well,
and
it's
it's
been
one
of
the
popular
blogs
appreciated
by
the
cncf
itself
that
you
know
a
mentor
coming
from
mentee
coming
from
the
litmus
chaos
project
has
presented
his
success
story
so
and
then
for
this
this
session
as
well,
we
are
having
a
couple
of
new
mentees
joining
us,
so
hopefully
we
will
have
another
successful,
cncflfx
mentorship
program,
yeah,
that's
from
the
community
side,
I.
G
Think
we
have
about
five
minutes:
Joshua
medic
yeah.
So
thanks
for
tweet,
that's
you
know.
We
talked
about
how
the
adoption
has
been
increasing
and
what
are
what
we've
been
listening
to
and
added,
more
support
for
Community
requests
and
then
community
events.
Now
coming
on
to
what
we've
been
working
on
the
last
one
year
as
the
next
victim.
You
know
in
litmus
we're
calling
it
as
litmus
3.0
one.
One
of
the
observations
is
you
know.
G
G
And
also
try
to
add
more
developer-centric
libraries,
so
chaos
for
developers
is
was
an
ambition
five
years
ago,
four
years
ago,
but
now
it's
kind
of
a
requirement
right,
so
chaos
was
used
to
be.
You
know,
break
things
in
production.
Now,
chaos
is
more
of
a
practical
runs
at
pipelines,
and
the
next
thing
is:
hey.
You
know
chaos
in
your
developer
pipelines
right.
So
when
you
submit
some
code,
your
code
gets
built
a
tested
for
chaos,
and
then
your
results
will
come
in
right.
G
So
that's
that
litmus
is
adding
the
infrastructure
support
and
to
make
that
Vision
possible
right.
So,
as
part
of
that,
you
know,
we've
been
adding
some.
This
is
one
of
those
are
the
goals
and
it
must
is
3.000
beta
for
more
than
six
months
now,
and
public
preview
is,
is
coming
up.
You
know
of
this
month
or
early
next
month,
so
primarily
the
large
Enterprise
customers
that
harness
has
been
dealing
with.
G
They
gave
significant
feedback
on
how
you
can
manage
how
you
we
should
be
able
to
manage
the
resilience
probes
or
the
steady
state
conditions.
So
we
are
calling
that
is
resilience
probes
as
managed
resilience.
Probes
that
we
are
upstreaming
into
the
open
source
and
also
the
entire
user
experience
of
chaos
should
be
around
a
resilience
core
right.
Why
are
you
running
chaos
right?
Not
for
breaking
something
but
to
find
how
resilient
the
target
environment
is
right.
G
So
we
are
flipping
the
user
experience
to
resilience,
Centric
and
also
you
know,
hardness
approved
a
lot
of
the
UI
libraries
that
were
caught
up
with
you
know
we're
moving
them
to
apache2
and
you
know
pushing
them
up
so
that
you
know
we
have
a
much
better
experience
for
our
open
source
users
as
well.
G
So
that's
that's
one
of
the
good
things
coming
in
from
honest
and
also
around
one
and
a
half
years
ago
we
have
launched
litmus
chaos.cloud,
which
is
basically
a
hosted
version
of
litmus
litmus
uses,
have
a
choice.
We
can
use
the
item,
chart
and
put
it
on
your
cluster
or,
as
somebody
has
hosted
it,
that
you
can
get
a
pre-controlled
plane
and
then
connect
your
execution
plane
to
that
right.
G
So
that
was
based
on
chaos
native
platform
that
you
know
before
coming
to
Partners.
But
now
we
have
improved
a
lot
of
user
experience.
Related
features
and
we
want
to
merge
that
treatments
chaos.cloud
into
harness,
but
honest,
also
has
Enterprise
version,
so
we
created
a
totally
free
tier
just
like
GitHub,
you
know
or
open
source
users,
it's
free,
so
we
have
a
pre
for
forever
tier
for
litmus
users,
where
the
experience
is
exactly
same
as
open
source
litmus.
G
But
you
know
it's
it's
free
too
for
limited
number
of
Brands
and
then
there
are
some
additional
features.
If
you
want,
you
can
go
and
upgrade
to
the
Enterprise
version,
but
the
pre
forever
version
is
same
as
working
GA
will
be.
So
just
this
is
an
update
to
the
tag
here.
This
is
a
great
thing
that,
apart
from
upstreaming
a
lot
of
code
harnesses
also
happy
to
open
up
whatever
tier
for
Community
users
right
so.
G
So
a
lot.
Lastly,
our
group
update.
You
know
we
did
a
lot
of
user
interviews
last
year,
then
we
took
a
little
bit
of
a
break
because
we
know
how
open
source
users
are
using
it,
but
we
also
wanted
to
make
sure
that
we
resent
to
the
large
Enterprise
users.
You
know
chaos
in
in
scale.
G
What
are
the
requirements,
because
the
charter
goal
here
is
to
publish
a
white
paper
about
best
practices
around
chaos,
engineering
right,
so
we
are
adding
some
of
the
Enterprise
stories
as
well
post
cubecon,
you
know
our
Enterprise
version
also
took
some
time
to
come
in
and
now
we
have
deployments
of
Enterprise
litmus
version.
You
know
in
multiple
places,
so
we're
able
to
go
and
interview
them.
What
do
you?
What
does
chaos
engine
mean
to
you?
What
are
you
planning
to
look
at?
G
How
are
you
planning
to
expand
scale
so
some
of
the
best
practices
we
can
hear
and
then
you
know
get
back
into
the
community
white
paper.
So
we
need
to
collect
that.
Our
other
maintainer
is
on
a
month.
Long
leave
now
so
once
Gothic
is
back
we'll
collate
all
that
feedback
and
take
it
formally
for
public
comments.
The
white
paper
and
the
charter
goal
of
is
to
publish
a
white
paper
which
we
hope
to
you
know.
G
Unless
we
receive
some
significant
comments
in
the
comment
period,
we
hope
to
publish
it
somewhere
in
July,
August
and
training,
so
we'll
provide
a
detailed
update
on
what
this
users
have
been
saying.
And
what
exactly
is
the
white
paper
trap?
So
we
can
present
that
in
the
next
chapter
meeting
yeah
any.
B
First
thing
I
was
wondering,
is
if
you're
seeing
so
you
know
I've
been
kind
of
thinking
about
this
tag
and
the
projects
we
we
Mentor
or
help
with
and
and
test
Frameworks.
You
know,
there's
a
few
of
them.
I
was
wondering
if
you
know
of
other
chaos,
Frameworks
are
they
and
if
they're,
in
cncf
and
if
they're
participating
in
like
your
chaos,
Carnival
and
the
chaos
working
group.
G
Yeah
yeah,
there
are
three
chaos
projects
right,
so
chaos
mentioned
Chaos
Blade.
Somehow
we
got
under
the
Tag,
app
delivery
and
they
went
under
I.
Think
you
know
tag
networking,
not
sure
why
that
happened.
Can.
G
Okay,
chaos,
mesh
mesh,
okay
and
Chaos
Blade.
These
are
the
two
of
the
projects
they
are
in
sick,
Network
or
tag
network
right,
so
they're
being
mentored
or
incubated
there.
G
We
were
the
first
project
and
we
we
got
into
Attack
app
delivery.
This
is
more
of
you
know
how
applications
are
delivered
reliably,
but
chaos
mesh
had
the
chaos.
Experiments
are
more
related
to
networking
in
the
beginning,
so
somehow
they
went
there.
But
yeah
you
know,
chaos
work
group
is,
is
being
participated,
initially
participated
by
all
of
them.
The
invitation
is
open
to
all
three
three
groups
right
and
in
fact,
the
next
shorter
we
will.
We
have
extended
the
signal
invitations.
G
We
have
asked
them
to
do
the
interviews
of
their
own
users,
I
think
one
or
two
of
them
were
done
and
Chaos
Carnival
again
is
an
open
platform.
You
know
it's
open
for
everybody's
invitation.
There
were
one
or
two
presentations
of
others.
G
Other
chaos
Frameworks
there,
but
it's
it's
kind
of
open
thing,
not
only,
for
example,
AWS
FIS
in
Gremlin
they,
the
vendors,
came
and
presented.
So
we
don't
go
and
force
the
invitations,
but
it's
it's
open
for
everyone.
Right
in
chaos,
monkey
yeah
I
know
there
were
not
been
seeing
them
in
the
chaos
engineering
work
group.
It
was
started
by
cncf
and
you
know
we
involved
the
three
projects,
but
if
you
think
that
they
can,
we
can
extend
an
invitation
for
chaos.
G
Monkey
Community
I
believe
there
is
a
new
community
that
is
managing
chaos
monkey
nowadays
or
you
know,
or
was
it
the
old
Netflix
I'm,
not
sure
sorry,.
B
B
I'm
I'm
wondering
how
we
make
sure
I
have
an
idea
here.
How
we
make
sure
that
we're
all
aware
everyone's
aware,
I'm
wondering
maybe
open
a
GitHub
issue
in
the
tags,
repo
kind
of
saying,
hey,
we're
working
on
this
white
paper.
Here's
the
current
state,
you
know
come
join
us.
G
Okay,
I
think
the
the
okay,
a
new
GitHub
issue
for
invitation
is
that.
B
Justin
I
I
would
say
in
cncf
Tag
app
delivery.
It
could
just
say
you
know
white
paper
on
chaos,
engineering
on
best
practices,
kind
of
like
there's
a
couple
issues
open
now,
for
you
know
the
platforms
paper
or
the
the
the
operator
paper
that
would
give
that
would
give
us
like
I
would
put
that
in
the
meeting
notes
here
or
something
in
a
couple
weeks.
If
you
come
talk
about
it,
so
people
know
what's
going
on.
G
Yeah,
okay,
yeah.
We
already
have
chaos,
engineering,
wheel,
group
of
cncf
and
that's
all
right,
sir.
It's
under
cncf
only
so
oh.
B
G
Yeah
yeah
we've
been
working
and
then
you
know
keeping
it
updated
yeah.
We
need
to
update
with
the
latest
things
right.
B
Yeah
I'm
almost
wondering
like
the
way
we're
doing
with
artifacts
and
the
way
that
we
did
with
platforms
and
operators
is.
They
have
like
within
cncf
tag,
Dash
app
dash
delivery.
They
have
a
folder
with
their
Charters
and
things
like
that,
and
then
we
just
tag
the
issues
accordingly,
according
to
the
working
groups
that
they
go
to.
G
Okay,
yeah,
we
can
move
it
there.
This
was
yeah,
it
started
a
little
while
ago.
However,
is
it
okay
to
be
here
or
should
we
move
it
under
tag
ad
I.
G
Yeah,
it's
a
good
solution,
I'll
discuss
with
the
other
maintenance,
and
you
know,
let's
put
that
in
the
notes
and
we
can
can
do
whatever
it
makes
sense.
Yeah,
cool.
B
G
Yeah
so
they've
been
happening,
they
used
to
happen,
but
you
know
not
last
humans.
We
need
to
get
back
and
make
sure
that
we
close
the
charter
and
it's
almost
reached
into
a
reasonable
accident.
So
the
closing
effort
is
what's
needed.
Yeah.
B
All
right
got
it
yeah,
I,
guess,
yeah,
and
that
will
help
us
what
I'm
also
think
all
these
things
come
together
like
just
let
the
make
sure
chaos
Mash
chaos
played,
you
know,
get
it
get
their
eyes
on
that
paper
and
participate
in
the
working
group.
If,
if
they.
G
Find
out
yeah
we'll
invite
it's
a
good
idea,
let's
put
it
into,
let's
create
an
issue
and
then
so
that
we
track
it
through
the
issue
right
so
I'll
I'll.
Put
that
note.
Yeah
awesome.
B
Yeah
very
cool
I
do
have
one
other
question
so,
like
I've
been
thinking
about
How,
We,
Do,
project
meetings
at
kubecon
and
so
I'll
yeah,
one
of
the
ideas
was,
should
we
you
know
if
there's
eight
or
ten
different,
app
delivery
project
meetings
happening?
Should
we
give
an
hour
to
each
one
and
try
to
allow
people
to
go
to
many,
so
that
I
wanted
to
ask
you
like
what
what
do
you
perceive
as
the
main
value
of
those
project
meetings?
Is
it
sharing
information
with
new
users?
G
Yeah
maintenance
to
each
other
was
a
less
of
goal.
You
know
we've
been
having
other
meetings,
but
you
know
people
meet,
but
it's
it's
mainly
about
meeting
the
users
and
even
I
was
thinking
every
project
they
go,
seek
a
room
and
the
people
have
to
choose
which
room
to
go
and
attend
and
then
again
there's
a
tag
up.
Delivery
I
had
to
go
run
from
this
meeting
to
go
and
provide
an
update
to
the
Tag
app.
G
A
G
Yep
yeah
I
think
I
can
take
some
more
questions
on
Zoom
I'll
hang
around
on
the
zoom
chat
here,
but
Josh.
Thank
you
again
for
giving
this
opportunity
and
we
look
forward
to
providing
update
in
the
next
call,
maybe
after
putting
making
some
more
progress,
yeah.
B
B
Yeah,
okay.
So
let's
move
on
to
the
next
item
in
our
agenda,
which
is
really
easy.
It's
just
that
we've
opened
up
tag.
Elections,
I'm
happy
to
see,
Thomas
and
Alex
have
nominated
them,
have
nominated
each
other
yesterday.
So
now
we
have
three
people
nominated
there.
If
you
want
to
nominate
yourself,
it's
it's
open,
it's
a
lot
of
work,
but
it's
very
rewarding
a
lot
of
talking
to
maintainers
and
bringing
them
together.
At
least
for
me.
B
That's
that's
one
of
my
goals,
so
yeah
check
that
out,
yeah
I'm,
not
a
chair
right
now,
so
I'm
not
exactly
running
those
elections,
so
I'm
just
part
of
them.
B
The
last
thing
is
I
wanted
to
share
just
make
sure
everyone
knows
what's
happening
with
the
artifacts
working
group,
I
I.
The
issue
is
well
actually
that's
an
older
issue
that
it's
tagged
in
there
there's
actually
now
the
actual
Charter
is
in
number
409.
So
I'll
link
that
in
here
also.
B
So
it's
the
charter,
we
feel
is
thank
you
for
joining
the
charter.
We
feel
is
in
a
pretty
good,
State
kind
of
describes.
You
know
why
we're
putting
this
group
together,
what
its
initial
goals
and
activities
are
going
to
be.
B
There's
there's
a
lot
about
I
guess,
I'll
share
with
you,
it's
a
lot
about
Gathering
up
like
so
basically,
oci
images
is
very
focused
on
file
system
layers
for
images
and
now
we're
trying
to
use
the
the
core
of
what
this
is
is
to
use
the
same
packaging
mechanism
for
other
kinds
of
binaries
and
config
files,
and
essentially
we're
kind
of
coming
from
the
bottom
up
to
gather.
So,
let's
call
those
media
types
as
in
like
I,
Iana
internet
assigned
numbers,
Authority
media
types.
B
The
goal
is
rather
than
or
in
addition
to
or
while
we're
waiting
for
such
media
types
to
be
registered
or
something
officially
with
the
Iana.
We
want
to
figure
out
ways
to
more
dynamically
discover
them
gather
them
up,
compare
them
to
each
other.
Learn
from
them
establish
some
conventions
around
them,
that's
kind
of
the
first
layer.
We
want
to
build
on
that
to
make
them
more
easily
discoverable
and
searchable,
so
you
know
dig
into
what
those
artifacts
are,
and
there
are
some
other
ideas
further
down
the
line
to
more
unify.
B
You
know,
distribution
and
deployment
of
things
that
are
bundled
in
oci,
bundles
yeah,
the
only
one
last
thing,
and
then
you
know
if
people
want
to
comment
is
we
put
problem
statements?
This
was
a
little
bit
of
a
debate
in
the
discussions
we
had
because
I've
seen
a
lot
of
the
recent
working
group
submissions.
They
start
with
problem
statements,
but
some
people
were
like
no.
The
problem
statement
should
come
after.
We
form
the
working
group
so
they're
in
an
appendix.
H
H
Yeah
I
think
the
the
inaa
thing
I
think
to
be
honest,
like
everyone
ignores
it
like,
it
says,
register
these
things
in
the
ACs
specs
and
no
one's
ever
registered.
Anything
no
one
cares,
but
I
do
I
kind
of
feel
that
the
people
don't
know
what
patterns
to
use
for
doing
anything
in
ACI.
H
It's
very
opaque,
like
there's
a
very
few
examples
and
people
copy
them
a
bit,
but
they
don't
know
what
then,
as
we
find
all
the
examples
and
then
there's
no
examples
for
more
complicated
things,
there's
only
examples
very
simple
things,
and
so
people
don't
know
how
to
do
either
kind
of
more
complicated
things.
I
think
there's
a
lot
a
lot
of
useful
work
to
do
in
like
sitting
down
and
coming
up
with
examples.
B
B
Yeah
and
that's
all
that's
on
our
agenda
for
today-
is
there
anything
else
that
we
should
discuss.
D
I
have
something
that
I
didn't
put
on
the
agenda.
I'm
gonna
put
my
camera
back
on
one
second.
D
What
I
wanted
to
discuss
is
community
outreach,
so
I
had
a
meeting
with
two
folks
who
are
want
to
be
more
active
with
the
platforms
working
group
for
now,
because
they
find
the
whole
group
a
little
bit
intimidating,
which
I
can't
understand,
but
we
have
been
discussing
kind
of
like
how
can
we
activate
the
kinds
of
people
who
might
not
be
interested
or
willing
to
join
this
particular
meeting
but
would
like
to
get
themselves
involved
in
individual
stuff?
D
That's
also
not
big
enough
for
the
working
group
right
so
like
individual
stuff,
so
we've
been
discussing
a
couple
of
things
among
them.
I
think
that
are
fairly
low
hanging.
D
Fruits
are
stuff
like
keeping
our
website
up
to
date
or
structuring
it
in
a
way
where
you
know
stuff,
like
the
Potato
Head
project,
where
we
want
people
to
get
in
on
and
give
us
feedback,
we
could
highlight
those
on
the
website,
so
yeah
I
don't
really
know
I,
don't
I,
don't
have
any
plans
on
like
how
to
do
it
and
what
to
do.
D
I
just
wanted
to
like
throw
it
into
this
group
for
now
see
if
anyone
else
has
any
thoughts,
if
not
I
might
you
know
just
do
something
I
feel
like
this
is
the
best
way
to
get
things
done
is
just
to
start
doing
things
and
then
have
everyone.
Disagree.
I
D
B
That's
awesome,
I
I
actually
like
in
not
a
very
marketing
friendly
way.
We
had
after
kubecon
Amsterdam
we
put
together
this
contributing
dock,
which
maybe
it
will
give
you
some
ideas,
but
I
love
that
you're,
focusing
on
like
that
Persona
and
the
small
bike
kind
of
thing.
It
makes
a
lot
of
sense.
That
would
be
great
I.
D
Know
Thomas
schitz,
you
mean
yeah.
B
D
Yeah
sounds
good,
I
will
just
create
an
issue
and
put
that
in
the
slack
Channel
and
just
you
know
see
if.
B
All
right,
I
think
that's.
It
then
good
to
see
everyone
and
see
you
all
online.