►
From YouTube: 2020-08-31 Crossplane Community Meeting
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
Let's
go
ahead
and
get
started
on
all
things:
0v0.13
we're
making
a
ton
of
progress
towards
that
we
kind
of
ironed
out
when
the
release
date
will
be
for
that
we've
undergone.
Well,
I
guess
we'll
get
into
all
the
details
there,
but
there's
a
whole
lot
of
you
know
interesting
features
since
refactoring
in
this
release
here,
so
it
did
extend
beyond
the
typical
monthly
release
cadence,
but
the
we're
planning
on
doing
a
release
before
the
end
of
september,
so
september.
23Rd
is
the
targeted
release
date.
A
We
are
tracking
everything
at
the
organization
level
on
our
project
board
here
that
you
can
click
through
and
take
a
look
at
that
for
further
details.
But
let's
jump
into
the
status
of
upcoming
features
that
are
included
and
they're
going
to
be
included
in
this
release,
see,
I
don't
think
nick's
online.
A
Is
he
yeah,
so
we
kind
of
talked
about
this
example
cloud
native
platform
last
last
meeting,
but
so
I'm
just
gonna
just
mention
it
briefly
that
this
is
basically
a
you
know,
a
definition
of
an
entire
platform
with
you
know
it's
configuration
for
a
platform
with
all
of
its
packages,
and
you
know
the
composite
resource
definitions.
All
sorts
of
stuff
has
been
kind
of
defined
here
in
yemo,
and
nick
did
a
very
good
job
of
sketching
out
what
all
the
emma
looks
like.
This
is
basically
kind
of
our
guiding.
A
You
know
where
we're
going
to
with
0.13
like
the
types
and
the
affordances
and
experience
etc.
Nick
did
a
very
good
job
of
explaining
how
everything
is
structured
here.
So
I
would
encourage
folks
that
want
a
good
vision
on
what
0.13
will
look
like
to
take
a
look
at
this
repo
and
kind
of
understand
how
packages
are
structured
and
you
know
all
sorts
of
goodies
in
there,
but
the
idea
is
to
be
able
to
build,
install
and
run
a
platform
defined
by
that
repo
there
in
0.13.
A
So,
let's
take
a
look
at
some
of
the
other
features
to
get
a
update
on
them
as
well.
I
don't
think
casey
is
moving
across
state
lines
now.
So
I
know
casey
is
not
going
to
be
here
and
godspeed
on
your
travels
casey
across
state
lines.
A
So
does
that
anybody
else
have
a
quick
update,
maybe
phil
on
my
code
generation
or
provider
acceleration.
B
Yeah
totally
so
you
know
casey's
moving
ahead
with
terraform
wrapping
of
the
very
lowest
layer
of
the
staple
providers,
so
a
design
dock
for
that
is
basically
should
be
out.
You
might
not
have
published
before
you
left
move
across
country,
but
it'll
be
published
either.
B
You
know
when
he
gets
back
we're
also.
You
know
working
with
some
of
the
large
quad
providers
to
basically
do
code,
gen,
so
they're
codegen
and
like
metadata
sources
for
the
various
cloud
providers,
and
so
basically
just
adapting
those
codegen
pipelines
to
emit
native
crossplane
providers,
and
so
there's
you
know
some
of
the
like.
We
talked
about
before
the
mutations
of
of
terraform,
where
terrorism
doesn't
have
things
like
a
radio
state,
and
things
like
that
that
you.
C
B
Otherwise
get
if
you
had
a
full
data
provider,
so
the
nice
thing
about
the
terraform
it'll
give
us
you
know
90
plus
coverage,
turning
towards
100
percent
coverage
for
all
the
providers
that
tearful
supports,
but
the
native
generated
ones
will
probably
have
you
know
the
absolute
best
user
experience,
but
the
terraform
ones
will
still
be
very
good
and
get
you
most
of
what
you
need
so
yeah
we're,
basically
I'm
doing
a
two-prong
approach
there
and
then
you
know
folks
are
actually
still
contributing
to
aws,
even
though
we
have
that
going
on
to
just
you
know,
contribute
handcrafted
providers.
B
So
there
was
one
additional.
I
think
it
was
for
like
an
elastic
ip
or
something
like
that
to
aws
that
got
dropped
in
last
week.
So
yeah.
B
It's
really
exciting
time
and
yeah
stay
tuned,
and
if
there
are
other
cloud
providers
out
there
that
are
on
the
call,
definitely
reach
out
on
the
provider's
channel
and
crossplan
slack.
And
you
know
we're
working
with
several
already
so
yeah
good
stuff.
A
A
So
then
the
next
section
we
have
here
is
about
a
number
of
renamed
refactors.
So
a
big
push
in
the
0.13
release
has
been
basically
incorporating
feedback
on
the
information
architecture,
terminology,
all
sorts
of
things
that
make
up
the
cross-plane
experience
like
what
are
the?
What
are
the
concepts
you're
working
with
and
the
types
and
you
know
everything
like
that.
So
you
know
one
of
the
things.
A
Is
the
earth,
like
the
alpha
stage,
composition
model
we're
moving
that
towards
the
beta
stage,
so
we
want
to
kind
of
finalize
on
you
know
the
types
and
fields
and
experience
etc.
So
it
sounds
like
in
master.
A
We
have
updated
infrastructure,
definition
and
infrastructure
publication
to
be
a
single
type
now
of
composite
resource
definitions,
and
this
is
how
you
define
your
platform,
api,
your
your
composition
and
you
can
publish
it
all
in
just
using
one
type.
So
that's
in
in
master,
you
know
all
this
is
working
towards
getting
composition
to
beta,
so
there
is
going
to
be
some
churn,
while
it's
all
still
in
alpha
here,
trying
to
land
on
on
the
right
right,
final
types,
etc.
A
Are
there
other
ones
to
mention
here
or
worth
mentioning
dan
demographic?
I
know
you've
been
adding
these.
C
Yeah,
so
we
have
a
few
other
updates
as
well
about
the
composition
like
bi-directional
patches
and
renaming
some
of
the
spec
fields
in
the
composition
object
itself,
not
infrared
or
intra-pub.
A
0.0013
all
right,
I
had
another
point
I
was
going
to
make
on
that.
I
totally
totally
blanked.
Oh
yeah
did
see
all
these
renames
here.
The
terminology
and
information
architecture
et
cetera,
that
is
all
it,
should
all
be
aligned
with
this
example
platform
here
that
we
spoke
about
at
the
beginning,
the
in
the
example
cmp
repo,
so
all
the
types
that
we
landed
on
like
composite
resource
definition,
etc.
A
These
will
be
demonstrated
how
to
use
them
and
what
their
shape
is,
etc.
All
of
this
example
repo
here
that
kind
of
that's
our
our
north
star
there,
like
the
definite
the
direction
in
which
we're
headed
there.
So
you
keep
keep
up
to
date
with
you
know
what
everything
looks
like
in
this
repo
here,
all
right
move
off.
You
want
to
get
us
updated
on
the
cross,
plane
agent.
C
Yeah,
so
the
its
first
initial
pr
has
been
merged,
it
works
and
and
right
now,
with
the
hand,
installed
and
stuff
but
like
since
composed
research
definition
has
landed.
It
needed
an
update
because
it
was
working
like
with
infra-def
and
infra
pub
types,
so
I
just
opened
the
pr
today
to
update
it
for
composite
resource
definition,
and
after
this
there
are
a
few
additional
features.
A
D
For
sure
so,
yeah
there's
a
lot
of
things
listed
here.
The
package
manager
as
it
manages
compositions
and-
and
you
know
the
package
metadata
and
that
sort
of
thing
touches
a
lot
of
different
parts
of
it.
So
the
package
manager,
implementation,
pr,
which
is
the
first
one
listed
here-
is
going
about
kind
of
making
the
package
manager
actually
a
reality.
D
So
that's
adding
the
types
and
the
controllers
for
our
two
variations
of
package
and
package
revision,
which
are
going
to
be
providers
and
configurations,
and
basically
there
is
both
the
on
disk
kind
of
format
of
that
which
would
be
we're
putting
in
the
meta.package.crossplane.io
group
and
that's
basically
what
you'd
author,
as
a
package
builder
to
you,
know,
specify
how
you
want
your
package
built
and
how
you
want
to
unpack
and
that
sort
of
thing,
as
well
as
put
some
metadata
on
it
in
the
design
for
that
which
would
be
package
metadata
design
here,
as
well
as
the
implementation
of
those
types
have
both
been
merged
now,
so
that
is
exciting
to
see
get
in
there.
D
So
now
those
can
be
consumed
by
the
package
manager
and
so
that
that
work
in
progress
pr
will
be
updated
to
do
that.
Essentially,
what
happens
is
those
get
built
into
an
image
that
the
package
manager
then
invokes,
and
it
reads
that
out
as
well
from
the
pod
logs,
as
well
as
the
different
types
that
the
package
wants
to
install,
so
that
could
be
the
new
composite
resource
definition
that
we
just
mentioned
or
compositions
in
a
configuration.
D
So
configuration
is
representing
your
kind
of
like
composition,
package
or
that
could
be
a
set
of
crds
in
the
provider
case
that
you'd
like
to
be
installed
and
then
reconciled
by
the
image
you
specify
in
your
meta
provider
type.
D
So
we'll
have
a
lot
of
stuff
coming
with
that,
along
with
that,
we
are
going
to
start
working
on
the
cli,
the
new
cli,
which
is
called
crank,
at
least
for
now
and
with
those
different
types
being
merged
those
meta
types.
We
can
actually
start
making
progress
on
this
as
well,
so
we'd
like
to
kind
of
abstract
the
the
process
of
you
know
packaging
these
on
disk
contents
into
an
image
from
the
user.
D
So,
ideally,
all
you'll
have
to
do
is
run
crank,
build
and
it
will
kind
of
do
all
this
configuration
for
you
do
some
linting
and
then
allow
you
to
push
that
up
to
any
registry
that
supports
oci
images
and
then
also
install
those
into
your
cluster
and
list
them
and
see
dependencies
and
that
sort
of
thing.
So,
as
these
types
get
implemented
and
we
start
using
them,
we
can
also
start
to
make
progress
on
that.
D
So
we
should
see
some
steps
coming
some
pr's
open
to
kind
of
get
that
initially
bootstrapped
as
well.
So
there's
a
lot
of
different
stuff
going
on
here
and
we'll
make
sure
to
you
know,
have
lots
of
great
documentation
around
this
for
the
next
release.
So
if
you
have
any
questions
leading
up
to
that,
definitely
feel
free
to
to
reach
out.
A
The
big
stand,
that's
you
know
big
surface
area
of
things
that
are
going
on
there,
but
I
think
it's
it's
been
discussed
a
lot
and
it's
you
know
there's.
I
think
a
pretty
good
forward
plan
there
about.
You
know
capturing
a
provider,
defining
providers
and
the
configuration
for
a
platform
and
packaging
them
up
and
the
experience.
A
Come
together
does
see
who's
on
the
call
here,
like
maybe
ryan
or
boss,
or
does
anybody
want
to
give
us
a
quick
update
on
the
kubernetes
runtime
stuff
for
this
release?.
C
Sure
yeah,
I
can
give
you
a
bit
so
in
the
last
few
weeks
there
are
a
lot
of
prs
checking
to
the
om
com,
kubernetes
runtime
and
mostly,
I
think,
if
you
look
at
the
pull
request
there,
maybe
20
30
of
them
get
merged,
but
most
of
them
are
relatively
small.
We
didn't
do
any
because
we
didn't
do
any
really
spec
related
changes.
So
there
are
a
lot
of
clean
house
improvements.
C
Most
of
them
are
minor
things,
the
the
I
think,
any
bigger
ones.
Yeah,
there's
nothing
really
big.
We
improve
the
dependency,
we
improve
the
labels,
we're
going
to
add
labels
automatically
and
the
propagated
labels.
There
are
few
pr's
on
that
and.
C
I
think
the
big
thing
is
we
are
trying
to
get
it
stabilized
so
that
this
can
get
into
b1
beta
1,
at
least
some
sort
of
beta
one
phase
that
we
can
go
with.
I
think
there's
a
cost
plan
release
like
this
this
week
this
month,
right
so
we're
trying
to
get
into
a
stable
release
with
the
cross
plan,
and
so
it
can
be
yeah
used
by
our
users.
A
A
Alrighty
and
thanks
for
the
update
ryan
and
we
already
talked
about
composition
going
to
v1
beta
1.,
a
lot
of
these
things
are
in
service
of
that
that
we
talked
about.
So
let's
get
that
and
let's
just
move
off,
did
you
add
the
provider
to
provider
config.
C
Yeah,
so
we
are
introducing
new
type
provider
conflict
to
be
used
as
old
provider
and
also
like
all
of
the
types
who
refer
to
like
who
had
failed
providers.
C
Now
they
have
both
provider
and
provider
config
graph.
So
we
we're
not
breaking
any
setup,
but
that
field
is
marked
for
deprecation,
so
that
required
some
changes
in
almost
all
of
the
repos
but
yeah
in
one
or
two
releases.
I
believe
we
will
get
rid
of
all
provider
types
and
use
provider
config
to
configure
how
the
controllers
will
connect
to
the
apis.
A
Yeah,
that's
definitely
something
that
we
should
be
very
clear
about.
The
release.
Notes
for
0.13
is
all
the
things
that
are
deprecated
or
obviously
like
the
time
frame
for
when
they'll
be
completely
removed
as
well
too.
So
because
there's
a
lot
of
fair
amount
of
churn
in
this
release
so
being
clear
about
what
the
path
forward
is
and
when
people
need
to
move
to
using
the
new
types
and
stuff
and.
A
As
well
since
there
are
some
of
those
too
be
very
clear
about
those
would
be
really.
D
A
Getting
rid
of
this
confusion,
point
of
confusion
of
like
oh
yeah,
it's
crosstalk
provider
like
wait.
What
is
that
the
one
that
does
code
or
is
that
the
one
that
you
capture
credentials
in?
Yes,
awesome?
Okay,
so
that's,
I
think,
pretty
much
everything
for
0.13.
It's
definitely
one
of
our
bigger
releases
that
we've
had
in
a
while,
so
a
whole
lot
going
on
there.
You
know
if
there's
anything,
that's
unclear.
A
Definitely
there's
time
for
questions
right
now,
of
course,
but
definitely
reach
out
on
slack
or
you
know,
get
some
clarification,
and
you
know
that's
always
something
we
should
be
striving
to
do
is
make
sure
that
the
docs
are
updated
as
well,
because
you
know
it's
one
thing,
two
different
experiences
here:
one
being
a
crosstalk
contributor
and
keeping
up
with
type
changes,
and
things
like
that
is
one
thing.
A
But
you
know,
new
people
coming
to
the
community
are
coming
to
the
project
and
trying
things
out
like
we
always
make
sure
that
the
docs
that
they
try,
that
they
work
that
they
are.
You
know
explanatory
already,
you
know
it's
it's
a
good
experience
there
too,
so
we'll
make
sure
to
keep
all
that
up
to
date
as
well.
B
Jared
towards
the
beginning
of
the
meeting
you're
mentioning
doing
some
work
to
get
opa
working
with
compositions.
Is
that
something
that's
slated
for
0.13
as
well?
Or
could
you
expand
on
kind
of
what's
needed
there
because
it
seems
like
opa
and
the
gateway
our
gatekeeper
could
just
work
with
like
the
standard,
composite
resources
of
their
composite
resource
claims?
B
Just
because
they're,
you
know
crds,
and
you
know
you
can
apply
policy
to
that
stuff.
So
so
can
you
just
say
a
little
bit
more
about
that?
If
that's
in
the
beginning,
yeah.
A
Sure
yeah
it
to
be
very
clear.
There
wasn't
anything,
that's
needed
that
was
needed
to
change
inside
of
the
cross
plane
implementation
itself,
so
I
didn't
have
to
make
any
code
changes.
It
was
largely
around
my
goal
was
to
get
a
example
using
policy
enforcement
with
opa
to
to
work
with
composition
types
and
just
had
that
example
to
show,
and
so
I
took
dan's
tbs
episode,
14
all
the
ammo,
that's
that's
in
there
and
then
updated
them
to
be
used
to
use
composition
itself.
A
So
it's
just
the
ammo
updates
throughout
the
example
having
a
working
example
and
nothing
like
within
the
platform
had
to
change,
because
you
know
open
cross
plane,
they're,
both
completely
pretty
much
completely
agnostic
of
each
other,
basically
right!
So
no
nothing
in
the
code
knows
about
each
other.
It's
mainly
integration
or
interaction
at
the
kubernetes
api
level.
So,
like
you
mentioned
it's
all
crds
right,
so
we
had
nothing
had
to
change
there
at
all.
In
terms
of
implementation,
which
is
nice.
B
Okay
and
then,
if
we
wanted
to
take
a
look
at
that
work,
is
that
going
to
be
posted
somewhere.
A
Yeah,
I
think
I
think
actually
I
I
have
to
look,
but
you
know
dan's
episode,
14
stuff,
like
we'll.
Keep
that
as
it
is.
You
know
as
a
snapshot
and
point
of
time,
so
it
matches
the
episode,
but
I
think
we
have,
I
think,
there's
some
docs
about
integrating
with
oppa
there's
a
you
know
a
section
in
the
docs
about
it.
That
might
need
updating.
I
don't
actually
know.
I
didn't
look
at
that.
B
A
Yeah
there
is
there.
We
hear
a
lot
of
people
talk
about
policy
enforcement
with
this
like
absolutely.
It's
definitely
a
very
reasonable
part
of
the
like
defining
your
own
platform,
it's
possible
too,
so
totally,
but
there
will
be
another
step,
though,
because
I
was
using
crossband
0.12
for
to
get
it
running
with
you
know,
working
codes,
then
this
it'll
need
to
be
updated
again
for,
like
you
know,
composite
resource
definitions
as
opposed
to
infrastructure,
definitions
and
stuff,
like
that
too,.
B
B
D
B
D
Think
right
now,
I
think
right
now
the
docs
might
just
point
to
the
tbs
episode
and,
as
joe
had
said,
a
lot
of
those
things
carry
over,
but
it
might
be
worth
as
opa
becomes
more
like
pervasive,
as
we
were
talking
about
and
as
we
kind
of
like,
develop
more
explicit
association
with
it
for
policy,
it
might
be
worth
creating
like
a
section,
maybe
not
in
the
getting
started
part,
but
in
the
reference
or
whatever.
The
next
section
is
the
docs.
D
A
Okay,
I
think
yeah,
I
think
the
you
know
from
a
landscape
perspective
and
an
ecosystem
perspective
like
it's
it's
I
mean
it's
a
supernatural
super
natural,
a
very
natural
integration
and
one
that
there's
a
lot
of
demand
for
either
way.
So
I
think
that
it
only
helps
the
project
in
the
community
and
users
as
well
to
have
you
know
some
documentation,
explanation
of
and
examples
about
how
to
use
them
together.
A
B
B
To
help
drop
that
too,
if
nobody
else
is
interested
in
here,
yeah.
A
And
with
my
yeah
with
my
recent
experience
with
it
too
I'll,
be
I'd,
be
happy
to
write
up
that
the
invitation
or
do
an
example
for
that
too,
because
I
I
had
a
lot
of
fun
with
it.
It
was
really
it
was
really
cool
to
see
those
two
working
together
right
off
yeah,
it's
different
from
when
you
just
watch
dan
do
a
live
stream
to
when
you're,
actually
on
the
keyboard
doing
it
too.
A
C
D
A
Yeah,
it's
more
fun
to
get
your
hands
dirty.
So
speaking
of
we
did,
did
you
certain
update
on
the
next
tbs
episode
or
is
that
pending.
D
It's
still
pending,
we
have
not
because
we
don't
have
enough
people
interested
but
because
we're
trying
to
decide
which
one
we
want
to
do
first.
So
we
should
have
some
good
episodes
coming
up,
including
potentially
having
marcus
back
on
for
some
more
packet
stuff.
So
some
cool,
some
cool
stuff
coming
up
for
sure.
A
D
Yeah,
I
think
I
think
it'll
be
the
third
time
well.
Actually
he
hosted
one
by
himself
really
early
on
so
so.
A
He's
got
host
and
guest
credits:
oh
yeah,
nice,
wonderful,
okay,
quick
update
with
cncf,
so
we
have
officially
closed
out
the
project
onboarding
issue
here
in
the
toc
repo,
so
that
is
nice.
We
have
kicked
off
that
we've,
given
everything
like
the
the
dns,
the
domain
transfer
code
and
the
zone
file
for
crossplan.io
over
to
the
linux
foundation's
id
wing.
So
they
have
everything
they
need
there
to
get.
A
A
All
right,
yeah
and
then
so
google
analytics,
though,
has
not
been
split
out
from
upon
that
I
already
transferred
over
there.
So
that's
that's
actually
still
pending,
but
that's,
I
think,
the
last
item
I
know
of,
but
otherwise
they
have
everything
that
they
need.
A
So
last
time
we
were
here
on
monday
morning
we
had
done
the
project
office
hours
at
kubecon
eu,
but
we
had
not
experienced
any
of
the
rest
of
kubecon
we're
kind
of
right
at
the
very
beginning
of
it.
So
I
just
wanted
to
open
up
the
floor
for
anyone
or
first
of
all,
thanks
to
everybody
for
the
really
good
talks
that
we
did.
A
Phil
had
a
good
one
on
home
with
savannah
and
me
and
harry
had
a
talk
about
omen,
cross
playing
as
well
hassan
had
to
talk
about,
like
you
know,
cross
playing
architecture
for
hosting
multiple
of
them
in
the
clouds.
There's
a
bunch
of
really
good
talks
that
I
think
I
heard
that
the
talks
will
be
posted
to
youtube
like
not
until
like
the
middle
of
september,
or
so
normally
they're
really
fast
about
it.
A
They
put
them
up
on
youtube
right
away,
but
it's
my
belief
that
it's
because
they
already
had
a
virtual
online
platform.
You
know
at
the
entrato
platform
to
be
able
to
see
talks
like
they're
still
encouraging
folks
to
go
there
and
I
guess,
get
more
usage
of
the
out
of
the
platform
there
before
going
to
youtube.
So
I
don't
think
they'll
be
on
youtube
for
a
couple
weeks,
but
great
job
to
everybody
on
the
talks.
A
I
think
they
were
all
really
strong
and
we
did
a
really
good
job
so,
but
I
wanted
to
open
the
floor
and
if
anybody
had
any
experiences
to
share
lessons
learned
thoughts
on
kubecon
and
eu
that
they
wanted
to
share.
B
I
mean
it
was
super
great
to
kind
of
you
know,
get
some
of
the
energy.
It
wasn't
the
same
as
like
being
there
in
person
or
whatever,
but
you
know
like
after
the
talks
and
having
all
the
questions
flow
in
and
that
kind
of
a
thing
and
they're
having
people
reaching
out
afterwards
that
are
catching
the
replays.
I
guess
that
are
on
the
entrado
platform,
so
yeah
definitely
a
good
kubecon
and
just
makes.
B
B
We
should
do
more
more
kubecon
talks
is
my.
You
know,
takeaway.
A
A
Cool
cute,
I
guess
kubecon
came
in
weights,
it
doesn't
sound
like
there's
a
whole
lot,
a
lot
of
excitement.
I
guess
that
should
be
a
lesson
learned
to
the
to
the
cncf
that
the
virtual
one
doesn't
seem
to
be
quite
as
much
of
a
hit
is
being
in
person.
A
Cool
but
yeah,
I
really
like
the
questions
too.
You
know
people
submitting
their
questions
during
our
talks
and
being
able
to
engage
there
and
having
like,
I
think
it
was
good
too,
to
have
slack
as
a
supplemental
experience
to
the
you
know
live
platform
that
they
have.
A
I,
I
can
only
assume
that
that's
actually
going
to
be
something
that's
pretty
strong
moving
forward
as
well
that
even
if
we
get
to
in
person
kubecons
again
having
that
like
supporting
like
set
of
channels
in
slack
to
have
people
be
able
to
like
find
each
other
and
ask
questions
and
stuff
like
that,
because
in
the
hallway
track,
when
you
meet
people
in
person,
it's
like
it's
super
useful.
If
you
see
them
in
person
but
being
on
slack,
you
have
a
way
wider
net
to
cast
to
like
go
to.
A
Like
a
you
know
the
operations
channel,
the
application,
development
channel
or
whatever
on
slack
and
ask
questions
there
and
you
can
connect
with
a
whole
lot
more
people
that
way
that
are
really
focused
there.
So
I
actually
thought
that
was
really
good
and
I
I
think
that's
gonna
still
be
a
big
thing.
Even
when
we
get
to
in
person
coupons
again.
B
Yeah,
I
I
liked
it
too.
It
was
well
we'll
put
together,
and
you
know,
nancy
and
company
did.
B
Great
job
kind
of
wrangling,
all
of
that
it's
a
big
undertaking.
A
B
A
It's
not
true
good
for
her
yeah,
the
the
the
cncf
events
team
does
amazing
work.
They
really
have
it
together,
like
it
was
pretty
smooth.
It
was
awesome,
especially
for
a
first
time
doing
that
format
and
the
first
time
on
that
platform
it
was
the
cncf
did
a
great
job,
so
good
job
for
them
cool.
We
don't
have
any
specific
prs
or
optional
technical
discussions
on
the
agenda
here.
So
that's,
that's
all
for
the
agenda
did.
Did
anybody
have
something
anything
else
they
wanted
to
bring
up?