►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220624
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220624
A
We
are
a
sub
project
of
controbex,
which
is
part
of
the
open
source,
kubernetes
project
and
as
a
reminder,
as
always,
we
have
a
code
of
contact
which
basically
says
to
be
respectful
of
your
fellow
participants
and
speakers
and
generally
be
excellent
to
each
other
and
to
start
off
for
today,
do
we
have
any
updates
and
big
wins?
That
folks
want
to
mention.
A
B
So
the
ingress
nginx
user
community
user
survey
almost
ready.
They
have
one
revision
to
a
question
and
then
it'll
be
ready.
Today,
it's
a
user
survey,
so
it
would
be
nice
to
boost
it
on
all
channels
because
we
don't
have
a
better
way
to
reach
specifically
ingress
and
gnx
users.
A
B
Probably
just
sig
network
and
kubernetes
users
and
a
couple
of
others,
so
it
doesn't
make
sense
to
use
the
bot.
B
Yeah
but
I
mean,
if
you're
only
doing
three
channels
yeah
the
so
we
haven't
historically
used,
announced
for
surveys
and
and
I'm
not
likely
to
start
make
sense.
The
so.
A
Sounds
good
a.
B
Couple
of
other
businesses
involving
surveys-
if
you
don't
mind,
yes,
please
we're
on
that.
One
is
now
that
I'm
co-chair
and
getting
access
administrative
access
to
our
google
docs,
I'm
going
to
see
about
offering
people
the
alternative
of
having
their
survey
on
google
docs
as
opposed
to
surveymonkey.
B
There's
some
permissions
reasons.
For
that
sharing
reasons.
For
that,
and
also
one
of
the
main
reasons
we
haven't
used,
google
docs
is
that
it
had
to
be
on
somebody's
personal,
google
docs,
which
is
always
a
problem
when
it
comes
to
personal,
identifying
information,
and
you
can't
really
stop
google
docs
from
collecting
that
so.
But
if
we
can
have
it
on
a
project
account,
then
that's
not
as
much
of
a
problem.
B
B
B
Yeah,
although
to
make
sure
everybody
saw
it,
the
idea
of
my
stepping
up
as
co-chair
is
specifically
to
get
us
over
the
hump
of
electing
some
of
training,
some
new
chairs,
because
bob
has
been
chair
forever
and
for
that
matter
actually,
our
tech
leads
have
been
with
us
for
a
really
long
time,
so
everybody
is
actually
looking
to
rotate
out.
B
So,
if
you
you
know,
if
anybody
in
this
call
thinks
that
they
can
make
a
big
bigger
time
commitment
to
say,
contributor
experience
in
the
future,
there
is
a
call
out
on
our
mailing
list
already
by
bob
and
that
sort
of
thing
we've
had
a
number
of
people
step
up
who
are
interested,
but
we're
always
interested
in
hearing
from
others
because,
ultimately,
like
within
a
year,
we
would
like
to
potentially
rotate
everybody.
So,
and
that
means
you
know,
positions
for
at
least
two
chairs
and
and
two
tech
leads.
A
If
someone
could
find
that
link
for
me,
I
would
be
very
appreciative-
and
I
can
put
that
in
our
notes-
yeah.
So
there's
a
if
you're
interested
in
doing
that,
there's
a
form
that
you
can
sign
out
to
say
that
you're
interested
in
either
the
tech
lead
or
the
co-chair
positions
for
signature,
becks
and
they're
going
to
try
to
do
kind
of
a
shadowing
thing
to
get
people
familiar
with
the
roles.
A
A
He
told
us
this
several
months
ago
toward
the
beginning
of
the
year
that
he's
working
on
some
other
projects
that
he
wants
to
dedicate
more
of
his
time
to
so
he
planned
to
step
away
from
our
group
a
little
bit
more.
So
he's
going
to
be
in
more
of
like
an
emeritus
advisor
role,
he's
not
going
away
forever,
but
he'll
probably
not
be
on
our
meetings
as
much
probably
not
take
on
action
items,
but
he'll
be
there
if
we
need
any
help,
and
if
we
have
any
questions
that
we
want
to
ask
him.
A
So
as
we
go
through
our
table
of
tasks
today,
as
we
get
to
chris's
items,
I
want
to
like
go
over
what
we're
planning
to
do
with
them,
because
I've
been
working
with
him
over
the
last
two
weeks.
I
guess
on
what
we're
gonna
do
with
those
couple
of
action
items,
and
it's
not
much
so
I
think
there's
one
thing
remaining
and
I'm
probably
gonna
take
care
of
that
so,
but
we'll
go
for
those
details
in
a
little
bit
miss
becoming
emeritus
advisor.
That's
how
we'll
say
it
in
the
notes.
A
I
was
typing
that
there
are
some
issues
with
permissions
and
information
collection
with
google
forms,
so
a
good
way
to
say
it.
Josh.
B
Yeah,
that's
why
we
need
it
to
be
on
the
on
the
community
account
and
on
people's
personal
accounts,
because,
because,
like
google
collects
your
ip
address
the
and
you
can't
actually
turn
that
off
so.
B
A
So
the
first
thing
is
the
tweet
drafts
for
the
help
wanted
section
in
the
annual
community
report.
We've
been
talking
about
this
for
a
couple
weeks.
That's
very
very
important,
and
I
think
debba
you
added
this
in
because
you
were
gonna-
create
a
dock
for
us
to
do
this
in
based
on
how
we
did
it
last
time.
D
Yeah,
actually,
I
have
created
the
draft.
I
I
just
tried
to
write
two
of
the
tweets
from
the
information
and
I
have
also
created
a
pr
we
could
watch
it
today
itself
regarding
to
see
api
health
wanted
and
similarly
we
have
to
go
on
are
doing
a
few
of
those,
and
even
british
is,
I
think,
helping
with
some
of
those,
and
I
think
he
has
done
a
few
also
so
yeah.
It's
just
like
the
work
is
check.
D
The
draft
see
how
many
tweets
each
sig
needs
and
then
put
a
pr
of
each
like.
We
could
have
a
tweet
each
day
if
you
get
a
pr
like
if
you
get
a
certain
number
pr,
so
each
pr
response
every
day
we
get
a
single
tweet
regarding
this
help
wanted
section.
D
So
that's
the
update.
I
think
it
will
take
a
week
or
two
to
get
everything
out
and
some
of
the
tweets
might
be
required
requiring
to
send
in
you
know
in
the
form
of
threads.
So
I
don't
think
that
will
be
possible
through
the
bot,
so
it
has
to
be
done
manually
like
we
did
last
year
so
yeah.
I
will
identify
that
parts.
A
B
Yeah
related
to
tweeting,
by
the
way,
the
we're
just
waiting
for
steering
to
approve
the.
B
D
F
Okay,
google
docs
documents
link
somewhere
yeah
in
the
box.
F
Yeah,
no
it's
in
the
in
the
doc
yeah.
I
just
saw
it
yeah,
that's
good
yeah,
because
I
had
that,
as
you
mentioned,
that
suggestions
there
in
hackmd
that
I
will
some
of
them
at
least
they
will
try
to.
D
D
A
Awesome
and
the
next
thing
I
think,
josh
you
put
this
in
because
we
discussed
that
at
the
other
meeting,
migration
of
all
things
marketing
to
cons
changing
the
name
of
our
group
from
upstream
marketing.
A
B
We
we
discussed
this
on
wednesday
at
the
time
you
didn't
know
what
the
timing
was
going
to
be,
and
I'm
checking
again
to
see
whether
or
not
you
know
at
this
point
what
the
timing
is
going
to
be.
The
and
the
reason
by
the
way
is
that
we
have
a
whole
bunch
of
links
to
fix.
So,
like
I'm
sitting
on
a
bunch
of
pr's,
and
I
don't
want
to
merge
them
until
I
know
that
other
stuff
has
been
moved.
A
Right
and
chris,
this
is
one
of
the
things
by
the
way
that
I
was
talking
with
chris
about
over
the
last
couple
of
weeks.
The
issue-
that's
linked
in
the
notes
with
regard
to
this
item
is
the
one
that
chris
started
for
us
on
this
renaming
and
two
weeks
ago,
he
went
through
and
put
in
instructions
for
the
rest
of
what
needs
to
happen
with
that
one,
and
that's
pretty
much
his
last
remaining
action
item
that
he
was
working.
A
B
B
At
this
point,
yeah
yeah
related
to
that,
by
the
way,
if
somebody
was
interested
in
becoming
a
reviewer
and
eventually
approver
for
the
contributor
site,
we
we
have
plenty
of
opportunities.
D
Hey,
I
would
like
to
sign
up
for
that.
How
how
do
you
do
that
pretty
much
you
have
every
month
on
that
meet
our
contributors,
log
series.
B
Yeah
I
mean
we,
we
pretty
much,
do
it
asynchronously.
So
let's
continue
this
on.
B
Yeah
and
and
pretty
much
what
it's
going
to
mean
is
picking
up
items
that
have
been
opened
against
contributor
site
and
giving
them
a
review
a
lot
of
what
we
do
honestly
is
copy
editing,
because
people
submit
a
lot
of
things
that
are
good
content
but
need
help
in
terms
of
punctuation
and
grammar,
etc.
B
B
You
know
well
written
and
clean,
so
the
but
yeah
and
there's
a
bunch
of
stuff
to
be
done.
B
For
example,
one
of
the
things
that's
on
my
list
and
I
need
to
create
an
issue
for
because
somebody
else
wants
to
pick
it
up-
is
to
rearrange
how
we
have
the
contributor
summit
on
the
contributor
site,
because
right
now
it's
not
dated,
which
means
we
have
to
go
through
this
annoying
archival
process,
and
the
answer
is
to
have
the
contributor
summits
in
there
by
date
and
we'll
have
to
move
stuff
around
every
time.
The
contributor
summit
finishes
the
particularly
because
you
know
hugo
doesn't
understand
relative
links,
so
the.
D
A
B
A
Sounds
good
all
right.
First,
one
hina,
you
already
created
our
team
in
github,
which
people
can
actually
use
to.
Let
us
know
that
we
have
things
that
we
need
to
look
at
in
github,
and
your
next
item
was
to
update
the
k
community
issues
template
to
make
sure
that
it
does
alert
the
whole
team
when
something
is
created
for
the
marketing
team,
which
also,
we
probably
need
to
update.
C
A
A
As
I
hope
most
of
you
know,
if
you
don't
know,
please
join,
there
is
a
slack
channel
now
in
the
kubernetes
slack
for
our
group,
it
is
sig
contribex,
comms,
oh,
which,
by
the
way
bob
updated
this
morning
and
said
that
the
funding
request
has
been
filed
with
a
ticket
number
for
our
request
for
buffer.
A
Okay,
good,
I
feel
like
I
should
grab
the
can
I
copy
yes,
I
can
copy
the
name
yay,
I'm
gonna
put
that
oh
yay
hina.
You
already
got
it.
Thank
you
yeah.
So
the
name
of
our
channel
is
now
in
updates.
Big,
wigs,
big
wins
section
of
our
dock.
If
you
haven't
joined
that
please
do
last
week
since
we
failed
to
have
a
meeting,
because
I
didn't
wake
up
in
time.
Sorry
about
that.
A
We
kind
of
had
an
asynchronous
meeting
on
that
channel,
which
is
a
great
example
of
one
of
the
reasons
that
it's
really
nice,
that
we
have
this
channel
now
we'll
be
able
to
do
better
asynchronous
communication
across
the
whole
group
without
having
to
ping
insig
controvex
with
our
ads
and
that's
kind
of
easy
to
miss.
So
you
have
a
one:
stop
shop
for
asynchronous
collaboration
across
our
whole
group.
Now.
F
Yeah,
well,
it's
the
it's
not
that
it's
not
you
that
are
on
the
on
on
the
firing
line.
I
think
but
yeah
it's
it's
still
pretty
much
the
same.
So
the
tweet
itself,
as
I
mentioned,
is,
is
ready.
It's
waiting
for
the
actual
approval
of
the
of
the
pr
that
chris
submitted
some
time
ago
and
is
waiting
there
for
right
actions.
I
think,
on
this
side
there
there
have
been
some
some
comments
and
some
changes
asked
by
bob
killen
and
I
think
they
need
to
be.
F
F
A
Lovely,
and
so
the
first
one
is
adding
chris's
article
on
it
as
a
an
article
on
the
website
right.
I.
F
Second,
one
well
not.
F
Not
really,
I
think,
as
a
second
one,
it
just
needs
someone
to
to
to
prove,
because
the
second
one
is
just
a
minor
update
to
the
to
the
guides.
It
doesn't
really
change
that
much.
But
that
being
said,
the
tweet
itself,
which
is
the
start
of
this,
is
also
dissolved
by
about
using
entirely
for
the
for
the
for
for
the
community.
F
So
the
tweet
itself
is
a
different
issue
that
was
cancelled
because
it
pointed
to
a
blog
site
and
not
inside
the
kubernetes
block,
and
that
is
what
led
to
the
to
the
pr
to
the
first
pr.
Okay,.
F
F
I,
if
the
first
pr
is
accepted,
I
think
that
would
start
the
the
process.
A
F
A
A
Yeah
there
is
an
issue
about
it,
though
I
was
looking
at
that
this
week,
which
has
some
additional
information
about
it,
but
yeah
we'll
just
wait
for
buffer
on
that
one.
So
I'll
go
ahead
and
skip
it.
Unless
folks
want
to
talk
about
it,
the
next
one
is
also
about
scheduling,
tweets,
which
is
also
buffer,
so
we'll
be
fixed
by
buffer,
hopefully
by
s
learning
buffer,
which
will
take
one.
A
So
the
next
thing,
avenesh
role,
description
for
the
events
role.
You
sent
me
a
draft
and
I
sent
you
back
a
an
old
pr
that
I
did
trying
to
set
up
a
social
media
coordinator
role
like
a
year
ago,
and
I
sent
that
to
you
after
you've
been
sitting
with
that
men's
role.
Description
for
like
two
weeks,
so
I
apologize
for
that.
Any
updates.
E
It's
it's
pretty
much
same,
but
I
had
a
few
questions
about
this
about
the
role.
So,
basically,
what
I
was
thinking
is:
how
would
when
we
have
this
role?
How
would
so?
How
would
this
role
the
person
a
lot
in
this
world
would
know
that
a
particular
event
is
going
to
occur
in
future
so
whom
to
approach
for
that
event,
or
is
there
something
or
a
calendar
where
we
know
that?
E
Okay,
this
event
would
be
occurring
at
this
particular
moment
so
that
we
could
prepare
it
and-
and
another
thing
to
that,
is
I'm
I'm
trying
to
prepare
our
doc
google
docs,
wherein
we
where
it
would
be
like,
like
a
pipeline
where
everything
would
be
placed
with
with
its
status,
so
I'll
create
a
timeline
kind
of
thing,
so
that
folks
could
help
out
with
this
rule
as
well,
yeah.
That's.
A
So
we
used
to
actually
go
through
that
calendar
in
every
one
of
these
meetings
to
see
if
there
were
any
upcoming
events,
we
haven't
done
that
in
quite
a
while,
but
that
might
be
a
good
thing
to
add.
As
part
of
this
role
to
check
that
calendar
for
events.
A
And
then
the
other
thing
I
wanted
to
share
with
everyone.
I
sent
to
finish
this
old
pr
which
failed,
because
I'm
bad
at
git,
not
because
the
content
was
bad
or
anything
just
because
totally
messed
up
that
pull
request,
but
this
is
an
example
of
a
roll
handbook,
so
you
can
see
that
it
has
sections
of
overview
minimum
skills
and
requirements
for
the
role
expected
time.
A
Investment
in
the
role
general
expectations,
what
you
would
be
doing
and
associates
overview,
but
if
there's
a
shadow,
if
you
had
a
shadow
for
that
role,
what
would
they
do?
So
we
keep
talking
about
roles.
I've,
never
given
specific
guidance
on
what
a
role
should
look
like.
We
actually
have
this
role
handbook
inside
of
our
marketing
team
repo,
which
hopefully
will
change
the
name
of
so
it's
in
what
is
this
kubernetes
community
communication
marketing
team
roll
handbooks
is
where
you
can
find
our
roll
handbooks.
A
A
A
Whatever
my
role
is
of
an
ish,
okay,
cool
and
folks,
your
input
is
welcome.
If
you
see
a
gap
or
something
that
we're
doing
that
seems
like
it
should
be
defined
as
a
role.
Please
discuss
that
with
us,
so
that
we
can
record
this
stuff,
create
shadowing
programs,
make
sure
people
feel
like
they're
owners
of
something
and
generally
support
the
process
of
continuing
on
our
group.
C
A
Yeah
avinesh
was
making
active
progress
on
his
role
description,
so
we
kind
of
broke
it
out
to
call
that
one
out
specifically
also
the
one
two
down
was
kind
of
a
general
placeholder
of
like
we
need
to
define
roles
and
me
and
chris
were
going
to
sit
together
and
just
figure
that
out
at
cubecon.
A
The
next
item
is
tweet
about
future
blogs
that
came
out
after
the
release,
so
these
all
came
out
during
kubecon
and
they
got
kind
of
lost
with
all
the
kubecon
stuff,
and
then
I
was
traveling
for
a
couple
of
weeks
after
that,
but
I
started
setting
up
some
git
stuff
and
learning
some
stuff
about
git
to
try
to
make
myself
more
familiar,
and
I
was
trying
to
decide
if
I
wanted
to
do
these
and
get
or
just
schedule
them
or
probably
actually
just
schedule
them.
A
A
A
A
Need
to
work
out
on
the
strategy
on
the
four
pr's
that
are
needed
and
in
that
issue
which
I'll
add
in
the
chat
as
well
in
that
issue
chris
laid
out
what
exactly
those
four
prs
are
and
a
little
bit
of
information
about
that.
A
So
there
are
actually
several
sig
spotlights
that
I
don't
think
all
have
tables
table
items
yeah,
okay,
so
maybe
I'll
make
this
the
sig
spotlight
like
super
section,
we've
got
sig
docs,
sick
storage,
like
start
another
one
too,
I
think
there's
one
more
in
this
group
at
least.
F
Yeah,
the
sig
architecture
there's
another.
D
Yeah,
I'm
quite
I
was
quite
busy
with
the
announcements,
but
I
will
be
getting
slightly.
A
F
Yes,
so
yeah
I've,
I've
finished
the
the
interview
process
and
I've
uploaded
my
added
copy
of
of
of
it
to
akamdi
and
I've
shared
a
link
and
I've
shared
a
link
in
our
channel
as
well
last
week.
So
essentially
it's
the
it's
in
that
stage
of
pre-editing
before
going
into
a
pr,
so
inputs
obviously
appreciated.
F
I
have
had
some
already
so
and
I've
already
added
some
of
the
of
the
comments
that
the
rishit
sent
my
way
so.
F
No
it's
in
the
architecture
I'm
at
the
very
early
stage
because
they
asked
me
to
wait
until
the
freeze
in
order
to
really
start
it
so
that
I'm
I'm
going
at
it
this
week
and
I
should
have
something
depending
on
their
availability.
Of
course,
in
the
case
of
six
storage,
it
was
relatively
quick
because
yang
was
really.
F
Quick
to
address
and
all
the
questions,
and
so
it
went
really
really
smoothly.
I
don't
expect
this
to
be
the
norm,
but
I'll
I'll
give
more
feedback
on
the
architecture
one
next
week.
A
G
I
actually
added
in
there
I
know,
as
of
yesterday
evening,
the
sig
docs
co-chairs
photo
the
interview
interview
form,
so
the
next
steps
is
for
the
for
the
blog
to
be
written.
A
All
right
I'll
move
on
to
the
next
item.
How
shita
came
in
like
two
or
three
months
ago,
or
something
asked
us
for
a
review
on
a
katakota
that
she
had
created,
frederico
and
avinash.
You
were
going
to
look
into
that
frederico.
I
know
you
did
and
avinesh.
Yes,
you
did
as
well.
I
have.
F
A
dashing
more
than
myself
so
yeah,
I
I've
expressed
some
general
impressions,
but
then
we
were
stuck
with
that
catechol.
The
whole
thing.
G
Roadmap
yeah
so
yeah
and
I
tested
this
scenario:
it's
not
a
the
environment's
not
available
anymore.
The
the
scenario
is
there,
but
we
can't
start
the
environment,
so
this
was
not
part.
So
the
catacottia,
the
team
from
o'reilly,
moved
the
scenarios
from
kubernetes
kubernetes.io,
not
this
one
to
a
separate
public
server
that
still
will
be
available
after
june
15th.
E
G
D
Yeah,
actually
I'm
looking
into
that
it's
it
was
actually.
We
have
started
the
contributor
initially
so
presently
we
have
two
three
other
people
like
other
scenarios
as
well,
that
was
out
of
that
was
not
part
of
upstream
communities,
but
they
want,
like
the
user,
the
end
user
side
of
documentation
or
tutorials,
so
I'll
curate
an
issue
in
kubernetes
community
to
what
what's
the
future
like?
What
do
we
do,
which
one
do
we
like
to
keep
for
which
one
to
discard
and
with
the
contributor
cataclysm?
D
Basically,
I
was
planning
to
moving
into
different
platform,
let
it
be
like
killer
code
or
instructor,
but
yeah
like
there
has
to
be
a
lot
of
people
involved
in
this,
especially
the
tech
leads
for
pontifex.
D
We
have
to
take
the
opinion
on
how
do
we
proceed
so
yeah
I'll,
like
by
next
week,
I'll
put
an
issue,
because
I
I
saw
a
lot
of
issue
on
case
last
website.
Even
tim
has
made
a
list
of
the
external
parties
that
wanted
to
help
so
I'll
also
add
those
things
and
a
link
to
those
issues
in
the
contracts
and
then
now
we
can
have
a
thread
over
it
or
a
given
like
issue
discussion
on
that
decision.
A
D
Yeah,
I
think
this
is
this
has
to
go
through,
but
the
bi-weekly
meeting
once
because,
as
I
said
like,
we
need
to
involve
declaration,
what
do
we
do
next.
A
It's
yeah,
you
know
mentioned
that
this
looks
like
a
done
ai.
I
kind
of
feels
that
way.
Each
time
I
look
at
it
and
then
I'm
like
oh
yeah,
no
there's
our
section
of
it
kind
of
is
done,
but
it's
a
nice
thing
for
us
to
keep
on
here,
so
that
we
keep
track
of
this
katakota
change,
that's
happening.
So
it's
kind
of
nice.
A
D
While
we
are
on
the
tweets,
do
we
tweet
out
about
the
announcement
phrase
or
anything
related
to
the
shadow,
the
release
process?
Sorry.
D
We
didn't
post,
usually
we
go
with
the
code
phrase
one
like
but
announcement
is.
I
don't
remember
last
time
also
did
we
post
it
or
not,
but
yeah
we
usually
do
the
code
raising,
but
if
you
require
the
announcement
also
we
could
do
but
in
twitter
I
don't
need
a
communication
regarding
enhancement.
Please.
A
Yeah,
I
think
we
should.
There
should
be
an
message
in
kdev
that
we
can
base
the
tweet
on.
D
A
F
Would
you
like
to
no
it's
it's
all
the
same
to
me.
It's
I
I
just
stepped
forward
because
the
the
the
silence
was
making
me
uncomfortable
more
than.
F
Yeah,
but
so
I
can
it's
it's
not
it's
not
a
problem.
I
can
submit
it,
but
if
you
prefer
to
do
it,
it's
perfectly
fine
or
anyone.
A
Else
could
I
would
like
it
if
someone
else
would
create
the
I
can,
but
do
you
want
to
do
it.
D
Yeah
I
was,
I
was
not
sure
if
we
had
to
relate
to
the
twitter,
so
yeah
yeah.
Now
we
have
to
do
it
so
then
I'll
do
it.
Okay,.
G
A
A
A
Yep,
I
figure
that's
kind
of
part
of
our
defining
of
roles,
setting
up
shadows
all
of
that
stuff.
That
is
a
good
kind
of
role
thing
that
I'm
going
to
put
into
our
role
item.
A
Well,
granted
we're
getting
buffer
too,
so
hopefully
that
process
will
be
mostly
obsolete,
but
we
do
want
to
keep
it
around.
So
we
do
want
to
train
a
new
approver
for
that,
and
I
think
you
were
interested
in
that
right
yeah.
So
I
guess
I
am
the
person
who
can
do
that.
So
that
is
a
role
that
I
will
help
to
define
and
create
shadowing
processes
for
and
we'll
figure
it
out.
D
No
there's
a
pr
regarding
the
tweet
of
sig
api
machine
review,
which
I
created.
A
Oh
okay,
I
think
I
checked
maybe
it's
a
couple
days
ago.
I
need
to
update
that
all
righty.
Let
me
sign
this
to
myself
in
the
notes.
A
A
A
D
D
A
D
A
Do
you
want
to
grab
the
pr
link
dabba
if
you
can
find
it
and
add
it
into
the
notes?
So
we
have
that
so
we
have
the
hack
nd
link
in
there.
A
A
All
right,
so
that's
it
for
our
table
and
we
are
pretty
much
at
time
so
any
other
last
minute
items
before
I
turn
off
the
recording.
A
E
Thank
you
hina.
If
that
is
completed,
should
we.
C
And
leave
it
blank
until
next
week
and
then
whoever
makes
the
tweet
will
take
the
action
item.
A
Just
checking
to
see
if
we
should
assign
it
to
someone
right
now
and
then
final
review
once
it's
ready,
we'll
want
to
promote
it.
Does
anyone
want
to
specifically
watch
this
because
it's
going
to
be
very
soon?
D
And
I
think
the
timeline
was
of
the
next
week.
I
think
we
had
a
discussion
initially
like
starting
off
next
week
got
the
needs
to
be
in
communication.
That
needs
to
go
out,
because
the
forms
are
really
good.