►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230303
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230303
A
Hello
and
welcome
everyone
to
the
Friday
March
3rd
edition
of
the
contributor
comms
team
meeting
as
usual,
a
reminder
that
we
do
operate
under
a
code
of
conduct
which
basically
says
to
please
be
respectful
of
your
fellow
attendees
and
speakers
and
generally
be
excellent
to
each
other
first
off.
If
there's
anyone
new
on
the
call
today-
and
you
would
like
to
introduce
yourself
and
say
a
little
bit
about
why
you're
here,
you
are
welcome
to
do
so
now
welcome
to
unmute
or
use
chat
or
whatever
don't.
B
Know
hi
I'm
new
here
my
name
is
Chad
Kroll
I'm,
a
devsecops
engineer
for
a
company
called
raft,
Laura
kind
of
gave
me
the
I
guess.
Let
me
know
about
this.
B
And
kind
of,
let
me
in
on
this
the
Sig
so
happy
to
be
here
and
hoping
to
contribute
in
any
way
that
I
can.
A
D
B
I
got
a
brief
overview,
but
if
you'd
be
able
to
provide
more
detail,
I'd
be
more
than
happy.
A
Sure
so
we
are
the
contributor
comms
group,
and
our
mission
is
basically
to
make
sure
that
folks
in
the
contributor
Community
know
what's
going
on
around
the
community
and
to
also
help
communicate
the
awesome
work
that
contributors
are
doing
externally.
So
we
have
the
k8's
contributors
account
on
Twitter
WE
Post
messages
to
the
pay
Dev
mailing
list.
Sometimes
we
help
make
sure
that
blog
posts
actually
get
published,
sometimes
variety
of
tasks
related
to
Communications.
A
We
also
do
a
little
bit
of
work
with
automation,
like
with
our
Twitter.
We
have
some
automation
to
grab
blog
posts
that
are
new
from
either
our
main
kubernetes.io
website
or
from
the
kubernetes
developers
website,
kates.dev
and
just
tweet
about
those.
So
there's
a
variety
of
tasks
in
that
area
as
well.
A
Welcome
and
we're
excited
to
have
you
all
right,
so
I
added
in
notes
for
today
into
the
notes
doc.
Please
do
add
yourself
on
myself
now.
A
A
So
there
is
a
change
going
on.
The
kubernetes
project
has
been
hosting
our
images,
our
container
images
for
kubernetes
itself
on
a
registry
at
gcr.kates.io,
and
we
are
trying
our
best
to
deprecate
that
without
deprecating
that,
for
a
variety
of
reasons,.
A
G
It's
basically
yeah,
so
I
will
clarify
it
right
now.
The
registry
is
Frozen
in
April,
which
means
it
will
not
get
any
updates.
G
However,
we
are
still
on
a
trajectory
to
exhausting
our
budget
right
now
in
I.
Think
it's
like
September
October
and
we
are
the
the
most
likely
option
now
is
that
we
are
going
to
be
removing
non-essential
images
from
the
registry,
which
essentially
means
anything
Beyond
what's
needed
to
bootstrap
a
cluster,
so
things
like
Ingress
nginx,
any
of
the
CSI
drivers,
like
the
AWS
CSI
driver,
the
the
node
local
DNS,
no
local
cache
anything
like
that.
G
This
will
mean
that
while
clusters
won't
fall
over,
if
they
have
references
to
these
images,
they
will
break
and
they
will
have
to
update
their
stuff
to
basically
point
at
the
the
new
one.
That's
so
far
the
least
damaging
path
we've
been
able
to
come
up
with,
because
it's
just
a
essentially
it's
just
like
a
one
line,
not
even
a
one
line
change
you
have
to
change
out
the
registry
address.
G
G
Yeah,
so
that
will
be
in
all
hands
on
deck
all
the
comms
everywhere
as
much
as
possible.
That's
both
you
know
publicly
I
recommend
you
know
letting
letting
your
your
internal.
Your
companies
know
anything
like
that
and
also
check
if
you're,
using
the
old
kate's.gcr.io,
because
it's
going
to
be
going
away.
G
The
other
thing
that
we
could
use
boosting
on
right
now
is
dims
wrote
a
tool
that
will
scan
your
images
in
your
cluster
to
see
if
it
finds
any
references
to
the
old
registry.
It's
a
cube,
cuddle
crew
plug-in,
and
so,
while
he
tweeted
about
it
and
that's,
got
some
attention,
it'd
be
good
to
get
an
official
tweet
from
the
Kate's
Community
account,
because
we
can
boost
that
a
bit
more
widely.
G
D
G
Oh
one
other
thing:
sort
of
related
to
this:
a
blog
post
or
post
related
to
you,
setting
up
like
a
pull
through
cash
or
mirroring
images
for
your.
You
know
for
people
like
to
be
frank,
if
you're
a
company
and
you're,
depending
on
a
Upstream
resource,
to
be
available
all
the
time,
you
really
shouldn't
be
doing
that
you
should
be
mirroring
stuff
and
have
that
available
to
your
your
clusters.
G
And
there
are
several
like
pull
through
caches
available
like
we
set
up,
and
so
just
some
some
guidance
on.
That
would
probably
be
good.
F
G
I
feel
like
I'll,
say.
One
thing
that
hasn't
helped
is
all
the
vendors
like
I've
I've,
looked
at
Red
Hat
I've
looked
at
Google
I've
looked
at
Amazon
as
well
as,
like
honestly,
just
a
host
of
blog
posts
by
everyone
else.
They're
all
referencing
case.gcr.io
yeah.
F
G
We
we
did
update
so
could
basically
update
our
blog
but
yeah
like
there's.
There's
all
sorts
of
references
out
there
to
keats.gcr.io.
H
G
G
E
F
To
explain
this
I
was
explaining
this
to
Corey
Quinn
and
all
the
things
we
had
gone
through
and
finally,
I
was
just
throwing
issues
at
him.
I
was
like
you
can
read
these
80
comments.
If
you
want
to
go
through
all
the
possible
solutions,
right
I
was
like,
but
you
write
a
newsletter
and
have
like
a
reach
to
all
these
AWS
people.
Please
say
something.
H
G
Etc
there
there
is
no
blog
regarding
a
pull
through
cash
and
the
big
thing
is,
we
did
publish
a
Blog
last
year
on
the
new
registry.
I
mean
published
one
somewhat
recently
on
the
freeze,
but.
G
And
the
changes
aren't
fully
decided
yet,
but
we
should
have
that
decided,
probably
by
sometime
late
next
week
or
the
following
week
at
the
latest
and
the
the
thing
is
because
our
time
frame
for
change
is
small.
We
need
to
get
comms
out
as
fast
as
possible
once
that
policy
is
decided.
G
G
Oh,
no,
it's
growing.
Oh,
it
is
growing
yeah.
Like
last
year
we
were
3.6
million
this
year.
We're
four
million.
G
That's
only
to
the
old
registry:
that's
not
even
taking
account
of
the
AWS
bill
yet.
G
This
will
break
people
when
they
go
to
well,
depending
on
on
what
images
we
remove
well
yeah.
It
has
potential
to
break
them
much
more
rapidly.
The
fix
is
a
lot
easier
right.
G
People
are
not
upgrading
past
1.21
because
of
the
the
API
deprecation
and
one
that
22.
damn
that
that
is.
G
We
have
seen
the
numbers
and
that
that
is
the
primary
like
that's
the
primary
version
people
are
running.
The
frustrating
thing
is
that
it's
honestly
not
difficult
to
change
and
fix
the
the
API
like
their
their
all
graduated
apis
in
in
1.22
or
1.21
or
1.20
yeah,
1.22
yeah.
It
just
requires
changing
the
you
know
the
various
animals
to
reflect
the
ga
apis
which
have
a
policy
on
not
changing.
A
So
things
we
need
to
do
imminently
for
Twitter
content
sounds
like
we
need
to
keep
an
eye
on
this,
of
course,
and
tweet
as
soon
as
any
new
decisions
are
made
on
how
we're
handling
this.
F
A
A
So
that's
for
Twitter
content
and
then
for
blogging.
We
want
to
have
at
least
one
more
blog
about
setting
up
mirrors
anything
else.
We
need
for
blogs.
As
far
as
we
can
see
right
now.
Is
it.
H
I
Think
somebody
is
working
on
it.
One
of
the
blogs,
as
I
can
see
in
in
Dev
channel.
Someone
named
laksha
is
working
on
a
Blog
I,
don't
exactly
know
if
it
is
about
particularly
about
the
tool
or
about
the.
H
I
suppose,
in
terms
of
Twitter,
for
example,
apart
from
the
new
tool,
it
wouldn't
be
bad
to
perhaps
retweet
some
of
the
past
topic
tweets
that
we
did
on
this
about
the
blog,
for
example,
the
one
that
explains
exactly,
although
I
suppose
that
the
dims
one
about
the
two
gives
the
necessary
background.
But
if
not,
we
already
I
think
that
the
problem
is
not
so
much
that
there's
information
lacking.
Is
that
that
it
we
don't
have
enough
spreads
and
impacts
in
terms
of
making
people
either
aware
or,
if
aware,
actual
con.
I
G
J
G
The
Beyond,
you
know
tweeting
posts
on
LinkedIn
posts
on
Reddit
like
any
any
place
where
there
is
a
I'd
say.
Kubernetes
community
could
warrant
information
about
this.
H
H
F
G
A
D
F
A
group
of
people
that
there
is
a
large
group
of
folks
that
do
get
their
news
from
LinkedIn
yeah
yeah,
just
because
it's
not
the
social
network,
that's
not
blocked
at
their
company.
G
Trade
that
official
one
I
I
would
say
it
is
it
is
time
to
you
know
basically
create
a
a
like
our
own,
whether
it's
on
hackaderm
or
something
like
that.
That's
fine,
the
the
key
thing
that
I
would
do
is
make
sure
that
we
have
one
of
the
things
to
link
back
the
identity,
to
show
that
it
is
actually
coming
from
the
project.
F
G
E
H
Decision,
then,
for
life
right
exactly
yeah,
even
even
because
the
lifetime
of
Mastodon
service
is
not
exactly
Stellar,
so
I'm,
pretty
sure
that
we
will
outlive
most
of
the
instances,
but
yeah
I
think
it
will
be
important
to
to
start
to
spread
the
to
be
present
in
other
places.
So
yeah.
J
G
I
would
actually
say
this
will
probably
warrant
an
announcement
like
when,
when
we
do
make
this
change
actually
in
the
announcement
Channel
everyone's
concluding
the
project
knows
this
stuff,
it's
just
it's
the
end
users
that
that
don't.
G
Because
a
lot
of
stuff
you
know
is
going
to
be
controlled
by
you
know,
get
some
like
get
up
someplace
or
something
like
that.
So
it's
like
you
change
it
and
that's
going
to
notice
a
diff
and
then
it's
going
to
change
it
back
again.
Yeah.
A
Indeed,
there's
a
lot
to
explore
here
this
active
activity
outside
of
Twitter
conversation
here
as
I
am
the
social
media
lead
I
should
I
should
probably
work
on
creating
those
extra
accounts
where
we
don't
have
them
like
on
LinkedIn,
we
don't
have
like
a
community
account
on
Reddit
as
far
as
I'm
aware,
right,
okay,
so.
F
Yeah,
like
the
official
kubernetes
ones
or
cncf
ones,
that
are
there.
If
there
is
one
there.
C
G
I
would
say
just
use
your
existing
accounts
on
on
Reddit
for
now,
yeah
I
haven't
seen
too
many
vendor
specific
or
even
like
Project
Specific
accounts
on
there.
A
A
D
A
F
A
A
Any
other
new
items
or
updates
big
wins.
A
Because
that's
a
thing
that
exists
I
know
I
still
haven't
moved
a
lot
of
stuff
over
here,
but.
A
We
did
have
one
person
who
tried
to
add
something
but
wasn't
able
to
repost
it
in
the
slack
about
that
just
to
make
sure,
because
we
didn't
expect
them
to
be
able
to
because
I
think
they
were
not
an
org
member.
But
we
posted
in
the
slack
tip,
track
that
and
make
sure.
A
So
shall
we
start
with
the
Sig
Spotlight
Reading
Club?
Well,.
H
C
H
H
This
is
a
draft,
so
there's
not
a
lot.
Actually.
I
will
add
the
description
in
the
description.
I
will
add
the
link
to
the
Google
Docs.
A
H
That's
a
good
one,
perfect
Sig
architecture,
I've
I've
assigned
the
trees
leads.
There
actually
see
all
those
choices
the
to
the
issue
so
and
and
ask
them
again
to
take
a
look,
so
this
one
will
will
at
least
be
useful
to
understand
if
actually
having
a
real
issue
as
any
you
know,
impact
it's.
It's
like
an
AV
deployment
strategy.
We've
tried
without
an
issue
now
we'll
we'll
try
with
an
issue
and
and
see
if
there's
any
actual
difference,
but
apart
from
that
still
no
no,
no
advances.
H
H
The
other
ones
in
draft
they
are
draft
because
supposedly
you
can
click
a
button
and
create
an
issue
with
them.
Although
we're
not
really,
we
can't
bypass
that
and
just
the
delete
them
or
move
move
them
to
them,
and
then
we
have
the
Sig
networking.
One
which
was
being
work
is,
is
being
worked
on
by.
H
A
Tj,
exactly
sorry,
yeah
I
think
CJ
wasn't
able
to
create
this
because
he's
not
the
org
member,
so
yeah
yeah,
but.
E
H
In
in
slack,
and
so
he
has
the
process,
he
has
a
templates
that
we
use
and
is
apparently
well
in
progress
with
with
this
perfect.
H
That
is
one
the
one
that
Avinash
mentioned
last
week,
so
I
I
went
to
the
threads
I
I
I
I
thanked
the
contributor
asks
for
a
link
with
the
ability
to
provide
some
comments
which
they
shared
and
that's
where
we
are
at
the
moment.
So
I
do
have
a
couple
of
suggestions
on
the
on
the
draft.
That's
in
Google,
Docs
I
will
add
them
by
this
weekend.
Avinash
I
think
that
you
also
have
access
right,
I,
I
tested
it
and
it
works
for
me.
So
I
can
add
comments.
H
Essentially
it's
stuff
around
like
linking
to
other
articles
and
stuff
like
that
and
after
that,
I've
also
shared
the
process.
So
we
will,
we
will
convert
to
to
markdown
and
then
open
the
pr
with
with
the
quarters
Etc
so
that
that
this
is
flowing
and
I
think
will
flow
smoothly,
because
the
the
process
is
well
understood.
Now.
A
Sounds
good,
I'm
gonna,
add
little
notes
on
these,
like
I
normally
would
in
the
table
to
keep
track
of
things.
H
Actually
it's,
it
would
be
great
if
to
even
in
a
draft.
You
could
add
like
comments
like
an
issue,
because
that
would
really
allow
us
to
see
the
the
history
of
it.
A
H
H
I
did
yes
because
I,
but
because
I
wanted
to
notify
them
explicitly
so
I
wanted
to
get
this
into
the
ml
box
right.
So
it's
as
you
prefer
cool.
It
does
show
in
the
issue
that
this
is
part
of
a
project
board.
If
you
open
the
issue
in
the
sites,
you
just
click
on
yeah,
you
will
see
their
projects,
which.
A
A
Was
pretty
cool
integration
all
right
other
things
on
here
that
are
in
progress,
adding
use
cases
for
zapier
automation,
Imran.
J
Yeah,
so
there
are
some
I
didn't
link
issue.
Did
I
did
I
yeah,
so
this
I've
added
I've
edited
some
of
the
key
points
which
we
use
and
I
close
the
other
ones.
So
this
yeah
feature
should
get
us
started.
So
I
was
just
waiting
for
atharva
to
get
I,
don't
know.
What's
the
progress
he
made,
he
showed
initially
few
things
and
maybe
we
should
get
started
working
on
it,
I'm
not
sure.
What's
the
current
status,
so
these
are
the
basic
things
like
labeling
tweet
length
and
then
notify
something
fails
and
yeah.
J
J
Are
the
things
currently
in
place
for
the
current
Twitter
bot
or
Twitter
automation,
stuff,
so
I
think
we
should
be
fine.
This
is
a
features.
Let's
say
we
want
in
the
news,
app
automation
and
now
yeah,
let's
hear
maybe
from
arterva.
Let's
see
here,
no
he's
not
there.
So
if
he's
back
sometime
and
we
need
to
see
where
we
stand
in
this
case.
I
No
I
was
talking
about
the
blog,
so
earlier
I
was
able.
It
showed
that
I
come
I
did
a
comment,
but
then
now
I
am
saying
that
I
was
I'm,
not
I'm,
not
given
a
comment
and
I'm
not
able
to
give
that
comment
as
well.
So
there's
something
happening
with
me
in
my
Docs.
I
E
J
Point
regarding
this,
so
he
was
I.
Think
initially
we
discussed
that
we
were
waiting
for
the
zapier
automatic
zapier
account,
which
I
think
he
created
privately
for
testing
purpose.
And
then
there
were
like
discussions
going
on
whether
Bishop
should
create
one
and
then
he
paid
using
his
card
or
we
we
asked
cncf
and
then
something
like
that
and.
J
J
D
J
J
So
it
should
so
the
sub,
so
it
should
be
the
pr
to
tweet.
So
that's
the
thing.
So
that's
the
starting
point
and
in
in
once
a
PR
is
twice
so
it
should
have
a
label,
that's
the
label
thing
and
then
it
should.
We
should
check
for
the
content
in
the
pr
that
the
Tweet
content
stuff
and
if
something
doesn't
work,
we
should
notify
the
you
know:
PR,
Creator
or
yeah,
that
it
doesn't
work
and
then
once
the
pr
is
enabled
and
zapier
puts
it
into
buffer,
then
it
should.
C
A
J
G
E
F
A
J
H
Yeah
we
can
have
new
values
to
the
status
so.
E
F
A
Excited
to
find
out
all
right
so
moving
on
from
the
in
progress
items.
Well,
one
thing:
that's
already
unwieldy,
there's
quite
a
few
things
in
done.
So
it's
hard
to
tell
if
anything
has
been
moved
to
done
in
the
last
week
that
we
don't
know
about
I,
don't
think
anything
has
so
moving
over
to
to
Do's
checking
on
their
progress.
A
There's
a
few
spotlights
in
to
do
which
I
assume
no
one
is
working
on
and
then
the
one
thing
that
I
have
at
least
is
the
kubecon
EU
tweet
planning
I
did
talk
with
sujay
about
this.
He
wants
to
shadow
for
social
media,
lead
so
I'm
gonna
work
with
sujay
on
doing
this
right
after
this
meeting
so
expect
next
week
to
be
able
to
start
working
on
tweets
for
kubeconi
U.
Isn't
everyone
excited
to
do
that
again?.
A
C
Progress
I
had
yes,
and
one
of
the
batch
lead
is
interested
to
interview
I
love.
This
is
it
compulsory
to
only
only
interview
jsr.
We
can
also
interview
batch
leads.
A
Of
like
the
chairs,
yes
yeah,
so
the
way
that
this
originally
was
intended
to
work
was
we
would
reach
out
to
the
Sig
in
their
Channel
and
ask
who
is
the
best
person
to
interview
for
the
spotlight
so
yeah?
If
that's
the
best
person
to
interview
for
the
spotlight,
then
do
it
just
usually
ends
up
being
the
chairs?
A
F
H
The
column
that
should
Exist
by
default,
which
contains
all
the
layables
on
the
settings
of
the
not
on
the
settings
of
the
entire
project,
but
on
the
settings
of
the
of
the
list,
not
sure
it
appears
on
the
board
as
well.
But
but
it
only
it
shows
the
labels
that
are
that
are
attached
to
an
issue
not
to
a
draft.
D
A
A
H
A
H
So
we
did
have
this
meta
discussion
on
whether
we
would
start
creating
issues
for
things
or
if
we
should
just
keep
it
keep
them
as
drafts.
I've
opted
for
most
of
them
through
cryptoness
draft,
except
for
that
sick
architecture,
one
which
I
want
to
test
how
it
works.
Apart
from
that,
if
we
follow
what's
already
done
there,
we
can
create
a
draft
for
each
one
of
the
of
those
ideas
or
we
can
follow
the
same
example
of
the
city.
H
A
Yeah
so,
like
I
think
you
mentioned.
A
Well,
well,
like
you
mentioned,
there's
an
ability
to
convert
to
issue
so
that
answers
the
question.
Registry.Cades.Io
blog
on
mirroring
and
Tim's
tool
is
what
I'm
going
to
call
this
one
for
now,
and
that
is
in
to
do
I'll
create
one
as
well
for
registry.cakes.
A
Dot
IO
social
media
I
was
kind
of
an
umbrella
item.
D
F
No,
no!
No!
No!
You
just
look
through
so
for
whatever
reason,
I
have
levels
of
access
that
are
way
higher
than
my
peers
on
WordPress
for
us,
so
yeah
I,
just
logged
in
and
was
like
hey.
Let
me
just
search
I
need
a
search
with
only
seven
posts
and
I
was
like
hey.
Do
you
have
like
a
import
export
thing?
How
do
you
want
to
handle
this,
and
basically
it
was
do
this
all.
A
Right,
nice,
oh
yeah,
good
work
alrighty.
So
with
that
we're
already
almost
at
time
are
there
any
important
table
items
that
we
need
to
go
over
should
I
just
kind
of
start
running
through
them.
A
This
might
as
well
just
start
running
through
them
so
for
context.
We
just
recently
started
using
the
board,
and
some
of
our
work
is
still
tracked
in
this
table
at
the
top
of
our
node
stock.
A
So
for
the
first
one
this
is
one
of
the
backlog,
Tech
Team
items,
which
we
should
probably
put
into
the
board
as
a
to-do.
Are
you
starting
the
kanban
board
that
is
well
underway?
You
kind
of
you
tweets.
We
will
make
progress
right
after
this
meeting
owners
files.
I
do
still
have
that
one
to
fix.
I
was
trying
to
get
up
early
and
do
that
this
morning,
and
then
it
didn't
happen.
So
I'm
going
to
do
that
right
after
this
as
well,
sigs.yaml
needs
an
upstream
marketing
text.
A
A
We
also
have
that
other
PR
that
came
in
this
week
also
and
other
roll
handbook
PR.
A
It's
done
so
natish
had
found
a
spot
in
our
storytellers
roll
handbook
where
we
referred
to
the
marketing
Council,
which
is
not
a
thing
anymore,
so
they
did
a
PR
and
fixed
that,
and
it's
already
done
so
I'll
update
the
board
with
that
as
well.
A
J
I
have
closed
it.
So
I
have
closed
the
issue,
so
you
can
section
okay
and
it's
done
actually
so
the
issues
close
and
close
the
issue
so.
J
A
D
A
Six
spotlight:
we've
got
several
of
these
in
progress,
kept
Reading
Club,
six
CLI
networking
there's
another
one
architecture
right,
but
these
are
all
on
the
board.
So
we
don't
really
need
this
on
the
table
anymore.
So
I'm
gonna
just
remove
this
from
the
table
because
it
is
effectively
being
tracked
in
the
board
katakata
to
GitHub
code
spaces,
move.
Anyone
have
any
updates
on
that.
Bob
left
already
didn't
he
no.
A
Oh
you're
here
lovely,
please.
D
Anyway,
so.
A
A
Like
at
the
end
of
March
yeah
right
yeah,
that's
what
I
was
telling
them
already.
We
will
keep
an
eye
on
it
and
we
also
need
GitHub
code
spaces,
stuff
separately
for
the
New
contributor
course
before
we
start
talking
about
that
right.
A
A
Fine
I
mean
it's
kind
of
part
of
ongoing
work,
so
I,
don't
think
you
need
to
move
it
to
the
board
on
its
own
okay,
so
I'm
just
gonna
delete
that
one
do
I
need
to
do
that
with
some
of
the
others
that
I
already
passed.
We've
got
three
minutes.
I'll.
Do
that
later.
A
A
It
doesn't
even
need
to
be
moved
to
the
board,
because
we
were
just
kind
of
trying
to
make
sure
that
we
were
supporting
the
blog
sub
project,
so
got
rid
of
that
one
security
comms
guidelines:
let's
move
this
to
the
table
as
a
to-do
that
will
never
actually
get
done,
but
okay,
I'm
gonna
do
that
right
now,.
A
Scheduling
tweets
for
non-contrtributor
comms
members-
that's
tracked!
Otherwise
do
we
have
that
tracked
in
the
board
technically,
at
the
moment,
yeah.
J
A
Perfect
contributor,
podcast
concept-
Mark
is
not
on
here,
so
that
will
continue
to
sit
as
a
concept
we
are
at
9.
00
am
contributor.
Gold
star
is
another
weird
concept
that
maybe
someday
we'll
do
something
with,
but
probably
not
and
deprecating
this
table
in
progress
all
right.
A
So
thank
you.
Everyone
for
joining
today
and
I
will
see
you
all
next
time.