►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20211210
Description
[SIG ContribEx] Weekly Marketing Meeting for 20211210
A
All
right,
we
are
recording,
welcome
everyone
to
the
december
10th,
2021,
contributor,
coms
or
upstream
marketing
team
meeting,
a
reminder.
We
are
a
project
within
the
cncf
under
kubernetes,
so
we
have
the
same
code
of
conduct,
which
basically
amounts
to
be
excellent
to
each
other,
treat
everyone
with
respect
and
play
nicely.
A
So
today
we
should
probably
start
off
with
any
introductions.
If
there's
anyone
new
to
the
group
who
wants
to
say
hello
and
say
why
you're
here,
what
you're
looking
for,
please
feel
free
to
do
so
now.
A
Okie
dokie
and
if
anyone
wants
to
do
that,
a
little
bit
later
in
the
call
also
feel
free
or
do
so
in
the
chat.
I
think
most
of
us
have
been
here
before,
but
maybe
one
or
two
new
people.
A
So
I
missed
the
last
two
meetings
of
this
group.
So
there
are
some
things
that
might
be
continuing
items
that
you
will
have
to
update
us
on.
So
please
add
anything
that
you
want
to
discuss
to
the
notes
and
make
sure
that
you've
added
yourself
as
an
attendee
as
well
and
we'll
start
off
with
our
updates
and
big
wins.
The
first
thing
I
put
in
there
is
that
it's
almost
the
end
of
the
year
yay
and
one
important
note
on
that.
A
There's
actually
a
good
reason
for
mentioning
that
which
is
cancellations
of
these
meetings
before
the
end
of
the
year,
like
ray
said,
there's
one
on
december
24th,
of
course,
christmas
being
a
very
major
holiday
here
in
the
us
and
in
a
lot
of
places
around
the
world.
We'll
probably
cancel
that
meeting
december
24th
meeting
unless
people
have
any
reason
that
they
really
feel
like.
We
need
that
meeting
if
you're
working
on
anything
that
you
think
will
be
in
action
at
that
time.
A
A
So
add
another
note
and
then
also
the
meeting
next
week.
I
know
that
I
won't
be
here
I'll
have
to
chat
with
the
other
folks
on
the.
A
We
recently
swapped
our
roles
for
this
group
into
like
a
a
leadership
committee,
which
I
don't
remember
what
we
call
that.
B
I
guess
we
should
cancel
for
the
next
week,
because
contributor
celebrations
are
that's.
A
C
Yeah
early
jan
official
start
date
is
still
up
near
what
is
january
3.
It
might
be
january
10th,
that's
still
up
in
here.
Okay,.
A
Of
course
you
are
welcome
to
you
might
want
to
mention
that
you're
part
of
the
upstream
marketing
team,
if
there's
a
spot
for
notes
in
there,
which
I
think
there's
some
sort
of
spot
for
that
and
that
you'd
like
to
help
coordinate
communications
between
the
release
and
this
team.
I
was
a
release
cycle,
calm,
shadow
for
this
cycle,
which
was
really
awesome,
and
I
learned
a
lot
I'll.
A
I
might
try
to
do
that
next
time
as
well,
depending
on
if
that
works
out
for
everyone,
but
that
doesn't
mean
that
someone
else
from
the
team
can't
also
be
on
and
start
learning
those
skills.
I
think
another
cycle
would
help
me
to
solidify
my
understanding
of
all
the
pieces
that
go
into
a
release.
So
I
think
that
would
be
good.
A
C
Yeah
just
for
124.,
so
124
is
going
to
be
big
with
communications
because
dr
shim
has
been
removed.
So
that's.
C
Yes,
I've
actually
highlighted
it
in
all
of
my
interviews
this
week
for
what
that
123
release,
we
tend
to
ask
what's
next
for
124,
so
I
spend
time
on
explaining
the
docker
shim
removal
for
next
year.
A
Yeah
it'll
also
be
a
particularly
delicate,
is
the
right
word
sensitive,
maybe
release
for
comms,
because
docker
shim,
as
we
have
seen
already,
can
cause
a
lot
of
panic
as
people
feel
like.
We
are
deprecating
all
support
for
docker,
which
is
not
exactly
accurate,
but
when
they
first
see
it,
it
makes
people
panic.
A
So
we
have
to
be
very,
very
careful
with
our
communications
with
explaining
why
we're
deprecating,
docker
shim,
why
it's
being
removed
and
what
we
really
need
a
lot
of
communications
about
what
people
need
to
do
to
make
sure
that
their
applications
will
continue
working
with
kubernetes
when
docker
shim
is
removed,
because
docker
uses
the
container
runtime
container
d,
which
is
supported
by
kubernetes.
So
it's
a
little
bit
nuanced
in
terms
of
what
this
means
for
users.
A
A
This
procreation,
cool
and
also
for
1.23,
the
blog,
is
out
which
we
already
tweeted
about
release
blog
and
we
haven't
really
tweeted
about
the
feature
blogs,
though,
which
we
could
probably
still
do.
It's
probably
a
good
idea.
A
Yeah,
which
is
also
a
very
important
change
the
pod
security
policies,
the
current
feature,
which
is,
I
think,
in
beta
with
this
release,
or
is
it
not.
A
I
wrote
that
psps
is
a
big
one
and
they
will
be
removed
in
1.25
and
the
replacement
for
them
is
in
beta
with
1.23
cool.
I
think
that's
all
the
notes
I
have
for
the
release.
A
D
A
C
We're
working
on
the
application
form
right
now,
the
shadow
application
form-
and
we
should
that
should
be
definitely
should
be
a
tweets
out.
Some
kind
of
concept,
good.
A
C
And
one
of
the
things
I
want
to
focus
on
124
is
to
increase
gender
diversity
as
well
for
applicant
for
applicants
so,
and
so
I'm
going
to
probably
reach
out
to
certain
organizations
with
that
application,
but
doesn't
necessarily
have
to
be
straight
from
official
kubernetes
comms.
But
my
partner
has
been
involved
in
that
for
for
as
her
career.
So.
A
Cool
and
for
some
context
for
folks
who
may
be
newer,
I
know
there
are
a
lot
of
folks
on
here
who
are
newer
to
the
community.
The
release
team
within
kubernetes
is
probably
the
team
that
has
the
most
formalized
shadowing
process,
there's
actually
an
application
that
you
have
to
fill
out
to
become
a
shadow
and
then,
as
a
shadow.
A
A
So
we
like
to
have
someone
at
least
on
there
and,
like
we
said
this,
1.24
is
going
to
be
a
big
one
for
comms,
so
it
would
be
nice
to
have
someone
else
as
well.
Two
folks,
two
heads
are
better
than
one.
A
So
we'll
keep
an
eye
out
for
that
application
form
like
you
said:
we'll
need
to
also
communicate
that
to
everyone
and,
if
you'd
like
to
apply
to
it,
feel
free
to
ask
questions
or
and
do
that
when
that
comes
down.
A
So
I'm
going
to
move
on
now.
If
there
are
any
other
questions,
do
you
feel
free
to
put
them
in
the
chat?
The
next
thing
is
that
the
contributor
celebration
starts
next
week.
We've
already
discussed
that
we'll
probably
move
our
meeting
next
week
because
of
that.
A
And
the
contributor
celebration
we've
been
doing
a
few
tweets
about
that.
Chris
has
mostly
been
monitoring
those
tweets
and
like
the
the
messaging
that
we've
been
sending
out
about
that,
but
he's
gonna
be
busy
for
some
amount
of
time
next
week
or
something
so
I'm
gonna
take
over
shepherding
those
efforts.
So
if
there's
anything
that
I'm
likely
to
miss
because
I
miss
things
all
the
time,
please
feel
free
to.
Let
me
know
or
make
sure
that
I'm
aware
of
anything
that's
going
on
in
that
area.
A
And
all
of
you,
please
feel
free
to
take
advantage
of
the
contributor
celebration.
It
is
an
opportunity
for
contributors
to
kubernetes,
to
socialize
and
have
some
fun
great
opportunity
to
network
and
meet
some
other
people
within
the
project
and
just
participate
in
some
fun
activities
ray.
Were
you
gonna,
say
something.
C
Oh,
I
was
gonna
say
that
I
will.
C
C
Right
yeah,
I'm
just
gonna,
say
that
I
will
reach
out
to
you
next
week
on
the
comms
about
awards
as
well.
B
And
also
we
have
this
slack
thing
going
out.
Like
slack
notification,
we've
decided
that,
but
I
guess
we
have
to
wait
in
the
next
meeting,
because
I
brought
it
in
the
five
weekly
meeting
and
I'm
bob
said
to
wait
till
the
next
meeting.
We
have
the
schedule
like
we
don't
have
the
proper
schedule
yet
now
so
after
we
get
the
whole
schedule
thing
done,
because
there
are
some
things
like
you
know,
bake
off
and
all
those
things
and
the
time
has
been
not
allocated
properly
yeah.
Oh.
A
Interesting
so
it'll
be
going
out
for
the
schedule.
When
does
anyone
know
off
the
top
of
their
head?
When
does
the
contributor
celebration
start
exactly.
C
D
A
I'm
going
to
be
out
this
starting
on
the
17th,
so
I'm
going
to
miss
a
lot
of
it
this
year,
which
I'm
very
sad
about,
but
there's
another
group
called
crafterneties
that
I'm
now
part
of
and
we're
trying
to
put
together
some
activity
for
it.
So
that's
why
I
kind
of
giggled
at
the
schedule
not
being
ready
thing,
because
I
haven't
put
in
when
I'll,
do
that.
If
I'm
going
to
do
that
so.
A
Yep,
I
think
there
are
a
couple
in
there
now
as
of
a
couple
of
days
ago,
but
if
I'm
going
to
do
something,
I
have
not
put
it
in
yet.
So
my
bad.
A
Because
we'll
probably
want
to
do
somewhere
on
the
start
of
it
and
then
once
we
have
the
schedule
finalized,
we'll
probably
want
to
do
tweets
for
the
schedule
and
then
for
the
closing
and,
of
course,
one
for
the
awards,
which
we
won't
be
able
to
create
until
the
awards
are
announced,
because
we
don't
want
to
have
that
information
in
a
publicly
visible
space.
A
So
if
we
were
to
put
it
in
the
github
repo,
it
would
be
publicly
visible.
So
that's
one
of
those
things
where
we
have
to
be
careful
about
timing,
so
we'll
have
to
have
someone
on
that
I'll
work
with
kristin.
Whoever
else
wants
to
be
involved
on
making
sure
that
you
get
that
tweet
out
on
time.
A
A
I
know
that
several
of
you
have
talked
about
being
interested
in
shadowing
the
social
media
role,
which
we've
now
changed
for
this
group
generally
working
with
twitter.
D
D
Creating
a
text
out
of
transcribed
text
and
video
and
audio
is
is,
is
the
next
challenge,
so
probably
just
a
shared
experience
with
others
for
for
spotlight
interviews,
shared
text
based
q,
a
works
much
better,
but
I
shared
the
draft
with
with
chris
and
jeremy,
like
from
sigma
multi
cluster.
I
just
wanted
to
get
their
thumbs
up
before.
I
create
a
pr,
probably
they're
a
bit
busy,
so
I'm
gonna
send
them
a
reminder.
Next
week
the
draft
is
ready.
D
So
so,
probably
once
I
get
a
quick
glance
from
them,
I'll
create
a
pr.
A
A
Yes,
committing
to
reviewing
and
anyone
else,
if
you
want
to
take
a
look
at
this
and
kind
of
keep
an
eye
on
the
process
that
this
blog
post
goes
through.
This
is
a
way
to
contribute
that
we
of
course
encourage
basically
our
sig
spotlights
our
sig
spotlight
blog
series.
We've
done
a
few
of
these.
A
So
we've
done,
like
I
said
a
few
of
these,
and
we
always
welcome
more.
We
have
a
list
in
github
of
the
cigs
that
need
blog
posts,
but
the
issue
got
like
deprecated
in
a
weird
way,
so
I'm
not
sure
what
the
status
of
that
is
right
now.
A
But
if
you
want
to
do
that,
I'll,
try
to
help
make
sure
that
that's
clear.
C
B
A
A
B
Yeah
it's
up
and
running.
The
basic
version
is
up
and
running
I'm
working
presently
on
the
windows,
part
which
is
technically
not
an
environment
in
catacora,
but
it
is
the
requirement
of
the
new
contributors.
So
that's
that's
the
scenario
but
yeah.
At
present
we
have
an
official
catacora
tutorial
for
someone
to
start
and
set
up
kubernetes
on
the
local
system.
So
yeah,
that's
that's
done.
A
A
B
Yeah-
or
you
know
like,
I
feel
basically,
students
and
those
who
are
new
to
communities
doesn't
have
the
you
know:
linux
based
development
environment,
so
they
usually
tend
to
start
with
windows
and
stuck
in
wsl.
I
I
guess,
like
windows,
part,
is
more
complex
than
this
linux
and
linux.
It's
very
easy
and.
B
Yeah
yeah
like
it's
basically
running
and
building
the
kubernetes
source
code
in
a
windows
device,
but
for
that
we
need
to
have
a
environment
like
windows,
environment
in
catapult,
which
is
not
there.
So
I
have
to
create
a
custom
environment
which
kind.
A
B
A
A
B
For
campaigns
in
progress,
I
want
to
just
remind
that
meeting
our
contributors
like
meet
our
contributor
blog
post.
That
is
going
on.
Basically,
since
we
don't
have
any
article
second
article,
so
we
haven't
put
here
for
the
review,
but
yeah
we
are
planning
before
this
year
ends.
We
are
going
to
put
up
an
article,
maybe
by
next
week,
yeah.
So
that's
going
on
pretty
much.
B
Yes,
yes,
we
have
plans.
Actually
we
don't
have
much
discussion
about
it
here
now,
because
we
already
have
a
separate
meeting
for
it
that
happens
on
tuesday,
so
yeah.
That's
just
wanted
to
update
that
yeah.
It's
a
long
term
plan
like
we
have
about
releasing
blog
posts
for
each
region,
like
contributors
focusing
on
each
region.
B
At
present
we
are
focusing
on
a
pack,
but
sooner
or
later
we
will
be
moving
on
to
other
regions
as
well
oops,
but
since
it's
the
first
time
so
we
are
dealing
with
a
lot
of
problems
and
yeah.
We
are
just
troubleshooting
them
and
making
a
good
pipeline.
A
If
you
think
that
I
mean
this
is
kind
of
its
own
whole
separate
group
within
this
group,
which
I
love
that
you
all
join
this
and
tell
us
about
what's
going
on,
makes
me
happy
to
hear
your
progress.
B
Yeah-
let's,
let's
look
into
that,
because
the
paris
is
also
working
on
that
origin
will
meet
our
contributors,
part
that
would
start
after
the
k,
dev
migration.
So
maybe
in
next
year
we
might
consider
like
doing
it
as
a
sub
project.
Once
all
the
things
are
in
place,
cool.
A
B
I
guess
we
should
also
look
into
the
like
a
mailing
list.
Comms,
I
guess
gracious
taking
care
of
that
or
paris
herself
is
taking
care
of
that.
We
have
recently
issues
on
communities
less
community
report.
So
maybe,
if
you
want
to
track
about
that.
A
I've
never
been
one
of
the
folks
who
manages
the
k,
dev
emails.
Julia
was
doing
that
I
don't
know,
has
someone
else
taken
over
for
that?
Does
anyone
know.
B
D
B
I
I
am
just
putting
the
iso
link
here
yeah.
This
is
the
iso
link
regarding
comms
and
the
dates
yeah
so
like
at
present.
Paris
is
handling
pretty
much
paris
and
laura.
They
are
handling
pretty
much.
You
know
shifting
it
to
the
domain.
Oh
the
migration.
A
A
B
I
guess
chris
is
on
it
like
he
is
handling
this.
A
Well,
it
won't
be
for
the
next
few
days.
So
if
there's
anything
imminent,
let
me
know
and
I'll
make
sure
that
it
gets
handled.
Yeah
I'll,
probably
keep
an
eye
on
it
too,
but
yeah.
That's
a
big
migration
thing.
That's
been
happening
for
a
while,
at
the
sake
level,
of
course,
you're
always
in
those
meetings,
so
cool
any
other
campaigns
in
progress
items.
A
Okay,
any
new
items
that
we
want
to
discuss
the
new
year
coming
up,
I'm
sure
we'll
have
a
lot
of
these,
probably
in
the
new
year,
but
at
the
moment,
hopefully,
things
are
mostly
winding
down.
Are
there
any
other,
any
new
items
that
we
need
to
discuss?
A
B
I
had
a
doubt
basically
I'm
dropping
the
issue
link
here,
so
this
issue
like
to
solve
this
issue.
We
need
to
basically
change
the
references
from
master
to
main
in
the
diagram.
So
do
we
have
to
like
create
a
new
diagram
all
together,
all
together,
we
can
get
some
like
figma,
link
or
mermaid
link
of
this
particular
workflow
diagram.
A
I'm
not
familiar
with
this,
so
I'm
not
sure
who
would
have
access
to
the
original
diagram.
If
there
is
one
it
might
be.
A
good
question
to
ask.
B
To
someone,
I
guess
quote
for
bob,
because
I
did
update
the
sig,
the
whole
sig
list,
the
new
six
and
the
other
six
part,
so
he
was
having
the
ppt
and
he
said
it
with
me,
which
was
editable
in
both
png
and
svg
format.
So,
yes,
you
should
ping
bob
directly
and
he
might
be
having
trouble
good.
A
And
if
not
him
he'll
be
able
to
point
you
to
someone
else,
but
also
yes,
he's
busy.
So
if
anything
happens
and
you're
not
able
to
get
a
hold
of
him,
which
I
think
he
probably
will
be,
but
as
a
backup
there's,
always
the
sig
contrib
x,
channel
and
slack.
If
you
ask
kind
of
generally
in
there,
someone
should
be
able
to
point
you
in
the
right
direction
as
well.
C
So
for
this
one,
so
kk
has
not
moved
to
maine.
Yet
we
do
plan
to,
I
believe,
between
124
125,
this,
the
contributor
who
created
this
issue.
She,
the
the
contributor,
has
made
some
pull
requests
to
the
k
website
where
we
do
use
main.
So
I
think
there
might
be
like
you
know.
This
flow
is
really
for
kkk,
but
I
might
be
applying
it
for
a
k
website
which
uses
main
so
so
I
mean
like
yeah.
Yes,
it
does
need
to
be
changed,
but
we
planned
for
that
between.
B
A
A
We
really
need
the
scheduling,
a
tweet
function,
which
we
haven't
been
able
to
fix,
which
is
broken
in
our
workflow
because
of
the
way
that
contribution
to
kubernetes
repos
works
and
the
tool
that
we're
using
was
an
existing
tool
that
someone
else
built
that
works
well
with
other
workflows,
but
not
with
ours.
Since
we
always
use
this
staging
branch
before
we
get
our
prs
merged.
B
That
that
thing
is
really
configuring.
Twitter
account
is
really
getting
messy.
So
I
I
tried
to
get
some
guidance
from
rajula,
but
I
think
he's
on
a
leave
or
something
he
hasn't
been
able
to
give
that
much
attention.
But
I'll
get
back
to
that,
because
I'm
working
continuously
on
that
automation,
part.
A
A
B
Yeah
he
just
put
it
in
the
issue
like
he
was
out
for
some
medical
emergency,
but
he's
back
so
he
he
wrote
it
that,
like
you,
know,
he'll
be
walking
in
the
next
few
weeks.
So
I
I
think
you
should
reach
out
to
him
by
next
week
and
see
if
we
can
yeah.
A
B
A
Yeah
he's
the
one
that
originally
put
the
bot
together,
so
he'll
be
the
best
one
rajula
like
reviewed
parts
of
it
and
has
some
understanding
of
it
as
well.
But
karthikeyan
is
the
main
one
who
put
it
together.
B
B
Thing
so
yeah
I
got
kicked
out
of
the
server,
so
does
anyone
have
the
invite
links
once
you
rejoin
it's.
C
Going
to
resend
you
a
new,
a
new
recaptcha,
I
had
the
same
issue
just
going
to
send
you
a
new
one,
to
look
in
your
mailbox
or
or
or
wherever,
that
bot
that
sends
you
the
capture.
It
should
send
you
a
new
one.
B
B
A
B
I
could
see
one
thing
about
like
akrish
put
something
on
the
contrabex
channel
regarding
docker,
sim
faqs.
We
go
through
that
ones.
Yes,
the
last
message
in
the
contracts
link,
I
will
just
copy
paste
the
whole
thing.
Yes,
yeah
that
sounds
good
again,
comps
putting
it
on
the
new
items,
yeah,
there's
that.
A
Yeah,
I
know
what
this
is,
so
I
can
explain,
but
I'll
put
it
in
the
chat
first
so
that
everyone
can
see
what
we're
talking
about.
So
there
you
go.
I
just
posted
in
the
chat,
a
comment
from
chris
shirt
from
the
sig
controvex
channel.
On
slack
he
says:
hey
at
contributor
comms,
I
think,
as
a
standing
rule,
any
post
we
see
about
docker
shim
should
include
a
link
to
the
docker
shim
deprecation
faq,
and
he
has
a
link
to
the
docker
sham
deprecation
faq
right
there.
A
So
this
faq
is
a
communication
that
we
worked
with
several
others
to
come
up
with
when
the
panic
about
docker
shim
happened
earlier
this
year.
A
So
it's
a
really
nice
frequently
asked
questions
of
a
lot
of
points
that
people
need
to
know
about
the
docker
shim
deprecation.
Why
it's
happening
what
it
really
means.
A
If
we
write
some
blog
posts
for
the
upcoming
release
or
something,
this
might
also
be
a
good
standing
rule
to
just
include
this
faq,
so
that
there's
a
link
for
more
information
for
anyone
who
has
questions
about
what
the
docker
shim
application
means,
because
there
will
be
a
lot
of
communications
going
out
from
the
kubernetes
project
about
this
over
the
next
several
months.
A
A
There's
something
in
here
updates
to
work
in
progress,
or
is
this
like
the
standard
thing?
That's
in
there?
Oh
yeah.
This
is
just
like
our
standard
dashboard
thing.
A
I
don't
think
so
cool,
so
our
last
working
session
items-
hopefully
we
can
finish
up.
We
try
to
finish
up
a
few
minutes
early
here.
I
know
that
matt
usually
tries
to
finish
up
10
minutes
early.
Let's
go
for
that.
So
we've
got
like
three
minutes
any
working
session
items
calendar
walk.
Should
I
bring
this
up
and
go
through
it?
A
A
A
Things
open
in
here,
but
nothing
urgently
needing
to
be
tweeted
but,
like
I
said,
we'll
need
to
do
some
tweets
about
the
contributor
celebration
so
I'll
try
to
get
that
lined
up.
B
I
guess
you
just
just
check
one
thing:
that
about
the
morbid
js
article
that
that
we
have
that
come
up
or
not,
if
that
hasn't
so
you
could
just
do
it
manually
about
it.
The.
A
Sorry
he's
a
fantastic
reviewer.
If
you
ever
do
a
blog
post,
you
will
encounter
sf
tim,
whose
actual
name
is
tim
bannister
but,
like
I
always
see
him
on
github,
so
I
always
think
yes,
tim
yeah.
I
will
make
sure
that
we
take
care
of
that.
Thank
you
for
pointing
that
out.
B
B
B
Yeah,
it's
like
it's.
It's
been
months
like
I
haven't
opened
this
thing
since
last
two
months,
but
just
just
recently
they
started
work
on
kpng,
because
at
that
time
they
weren't
working
on
that
they
just
had
a
document
on
that
and
seek
storage
is
taking
care
of
that
and
there
are
enough,
like
you
know,.
A
Okay-
and
we
already
know
what
blog
post
needs-
review
the
sick,
multi-cluster
blog-
it's
not
a
pr
yet,
but
we'll
try
to
review
it
in
hack
md
before
we
pr.
It
is
our
usual
process.
We
try
to
make
sure
that
the
blogs
are
ready
to
go
before
we
put
in
a
pr.
So
the
pr
is
a
little
less
involved.
A
Okay,
I
don't
see
any
particular
issues
in
the
main
project,
at
least
on
our
board,
though
matt
mainly
maintained
our
boards
and
we'll
have
to
change
how
we
do
that.
Probably-
and
I
don't
think
there'll-
be
anything
in
these
repos
either.
At
the
moment,
cool
ran
a
little
bit
long,
maybe
for
our
50-minute
plan,
but
I
think
we
covered
some
awesome
stuff
there,
any
last-minute
items
that
you
wanted
to
get
to
that
we
managed
to
get
to
in
here.
A
I
think
we're
good.
Thank
you
so
much
everyone!
Congratulations
to
demobrata
on
your
your
new
tutorials
launching
and
congratulations
to
ray
on
the
1.23
release
and
I'm
gonna
go
ahead
and
stop
our
recording
happy
new
year.