►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting 20210820
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
So
so
this
was
the
this
was
how
previously
it
was
tracked.
So
this
is
a
table,
and
these
are
the
people
whom
some
who
are
the
interviewees,
so
people
are
reaching
out
to
them.
Coordinators
are
the
one
who
are
talking
to
them
region,
and
this
is
this-
is
just
just
a
general
status,
whether
a
response
is
received
from
them
or
it's.
A
We
have
just
sent
the
former
columns
in
progress,
so
this
is.
This
is
the
kind
of
status
tracking
we
can
do
before.
We
have
something
in
hand
like,
even
if
before
we
have
a
draft
for
the
block,
and
once
we
have
a
draft
for
the
blog
like
teasing
suggested
last
time,
the
better
way
would
be
to
start
with
their
markdown
document.
First,
because
yeah
I
mean
that's
how
they
they
went
dude,
it
did
it
last
time.
So
I
have
added
two
examples
here.
So
this
was
a.
A
This
was
a
markdown
document
from
the
one
himself
when
he
was
doing
a
similar
effort.
So
a
similar
thing,
when
we
have
a
draft
ready
for
the
block,
we
can
provide
this
to
to
the
reviewers
in
the
sick
contact
bricks
to
have
an
initial
review,
and
once
we
have
certain
pointers
to
improve,
and
then
we
know
like
okay,
this
can
be
a
final.
This
is
ready
for
a
final
review.
Then
we
can
raise
a
pr
and
that
can
go
in
the
board.
So
what
do
you
think.
B
B
I
think
from
beginning
to
end
there
should
be
an
issue
right
like
if
we're
tracking
this
right,
like
you,
can
just
drop
the
heck
and
def
like
link
in
the
comments,
and
we
can
work
on
proofreading
it
there
and
just
have
you
know
a
process
of
hey
I've
done
this.
You
know
everybody
checks
in
on
the
issue
itself.
That
has
been
proofread,
because
there
is
some
coordination
that
does
have
to
happen
beforehand.
A
C
Yeah,
I
think
the
issue
is
already
present
in
github.
If
you
could
see
the
board,
the
issue
is
there.
The
conversation
has
also
continued
from
there.
Only
nikita
is
commented
on
that.
That's
why,
where
we
initiated
that,
I
guess,
while
we
put
the
pr
on
we
can
relate
to
that
issue
and
yeah
this
one.
This
is
already
present.
So
when
we
put
here
the
issues,
we
can
just
put
this
issue
number
and
it
gets
tanked
along
with
them.
C
A
That
that
makes
more
sense.
Also.
I
have
one
question
just
just
adding
to
it,
so
it
was
suggested
that
we
will
have
one
block
per
region,
so
we'll
reach
out
to
say
10
people
from
one
country
say
india
and
then
we'll
collect
responses
from
all
those
10
people
create
blog
posts
for
10
responses
and
then
we'll
compile
them
in
one
single
blog.
A
Are
we
going
to
do
the
that,
like
10
people
or
are
we?
Are
we
trying
to
limit
a
certain
number
to
one
blog
and
then
there
will
be
another
yeah
so
because
we
can't
we
can't
wait,
say
we
have
five
responses
and
then
we
know
there
are
two
more
people
we
have
reached
out
to,
and
so
we
we
can't
it
would
be.
It
would
be
useless
to
wait,
keep
waiting
for
other
like
who
are
taking
time.
So
we
can
have
another
run,
another
blog
post.
So
what
do
you
think?
B
Yeah
I
mean
what
the
number
is.
I
kind
of
it
kind
of
depends
on
the
skill
sets
I
feel
like
too,
so
I
don't
know
if
there's
a
magic
number,
but
I
know
that
you
could
have
too
many
chefs
in
the
kitchen
for
lack
of
a
better
term,
so
I
would
say
like
three
to
five:
maybe.
A
Yeah
we
can
do
something
like
maybe
over
over
every
two
week.
We
can
have
a
review.
Okay,
we
have
three
so
three
responses
of
three
three
blog
posts
ready
three
different
responses
per
block
was
ready
and
then
we
can
compare
them
and
then
or
maybe
every
month
we
can
check
okay,
okay,
we
have
five
responses,
so
we
can.
We
can
post
a
block
every
month.
B
B
Of
the
interviewees
in
the
blog
post,
sorry
priyanka-
I
didn't
mean
to
talk
over,
but
to
answer
the
question
in
chat.
Yes,
we
would
mention
the
names
of
the
interviewees
in
the
blog
post.
I
can't
imagine
not
doing
that,
but
if
the
interviewees
are
like
five
people,
that's
going
to
make
it
very
interesting.
I
feel
like
for
the
blog
team.
A
So,
let's,
let's
do,
let's
just
start
with
it,
and
then
we
can
once
we
have
couple
of
blog
posts
ready
like
per
responses.
We
can
try.
Some
formats
have
some
runs
review
ones
and
then
you
can
decide
yeah.
D
So
one
one
personal
experience
has
been
with
sig
note
spotlight.
This
might
be
a
bit
different,
but
when
I
presented
questionnaires
to
four
folks
expecting
like
individual
responses,
two
of
them
were
busy
and
then
the
other
two
divided
up
the
questions
between
themselves
and
they
didn't
answer
two
questions.
D
B
Yeah,
that's
a
good
suggestion
actually,
because
if
we
did
have
five
different
responses
to
the
same
question
and
they're
all
generally
the
same
answer
which
one
do
you
choose
right
or
at
that
point,
you're
now
making
a
more
correct
answer
to
the
question,
which
might
not
be
the
best
thing
for
the
blog
right.
So
that
is
a
good
point
to
want
is
like
actively
split
up
the
questions.
If
you
have
multiple
respondees
to
their
unique
area
of
focus,
if
possible,.
A
Yeah,
that's
something
new.
I
I
I
just
understood
because
so
far
this
while
I
was
understanding
there
will
be
say
five
sections
in
the
blog,
so
every
every
separator
after
every
separator
will
have
a
different
person
responses
in
in
kind
of
a
say,
formatted
manner,
just
cut
like
compact
manner
like
we'll
collect.
Maybe
this
this
big
answers,
but
it
will
just
compacted
yeah,
but
that
that
was
that's
what
I
thought
first
time,
but
now
it
makes
more
sense.
That's
something
we
will
consider.
D
D
I'll
echo,
what
caslin
told
me
and
that's
basically
like
giving
them
more
options.
First,
options
is
in
terms
of
time
frame
so
be
respectful
of
their
time
frame
because
they
have
their
regular
work
so
just
leaving
it
open
that
hey
no
rush,
this
is
just
something
we're
doing
for
xyz
and
feel
free
to.
Let
me
know
an
eta
or
even
not.
The
second
thing
is
providing
flexibility
in
terms
of
type
of
response.
D
Some
of
them
are
comfortable.
Just
writing
the
answers
themselves.
Some
of
them
probably
won't
prefer
writing
they'll
say
I
can
hop
on
a
quick,
10
minute
call
and
I'm
gonna
tell
you
my
answers,
and
could
you
please
do
the
writing
yourself.
So
I
think
if,
if
we
allow
more
flexibility,
that
would
help
us
get
more
answers.
D
B
B
Okay,
so
I
went
to
sorry
priyanka:
are
you
done
with
everything?
Okay,
I'm
like
multitasking,
so
I'm
not
following
along
in
the
dock.
Sorry.
B
Did
I
put
the
dock
doing
so
much
kubecon
stuff
today,
it's
weird,
so
I
went
to
the
retrospective
for
the
121
20
the
122
release.
I
went
to
the
retrospective
and
they
mentioned
they
being
the
release
team
that
one
of
the
positive
things
they
did
was
getting
out
in
front
of
the
deprecations
and
removals
right
so
like
telling
people
in
advance
like
this
is
what
we
have
planned
for.
122..
B
Here's!
What's
getting
you
know
going
from
alpha
to
beta
beta
to
you
know,
ga
whatever
you
want
to
call
it
like.
That's
always
going
to
be
something
that
happens
during
the
release.
From
this
point
forward,
it
sounds
like
like
they're,
going
to
put
out
that
blog
post
in
advance.
I
said
that
we
can
help
with
that
in
the
future,
and
caslin
is
on
the
122
team,
so
that
actually
works
out
pretty
well,
so
she
might
reach
out
to
any
of
us
really
for
help
there
at
any.
B
Given
point
so
just
be
aware
of
that,
and
I
think
that's
all
I
got
folks.
It's
already
11
46.
Well
time
flies
when
you're
having
fun.
D
No,
I
think
the
same
thing
I
mentioned
last.
You
can
measure
to
you
as
well
thanks
for
the
sigma,
the
cluster,
all
the
the
raw
files.
Since
I
already
have
a
hanging
pier
on
sick
node,
I
probably
won't
create
another
pr
and
just
add
to
their
workload.
What
I'll
do
is
probably
ask
around
on
how
we
can
help
sick
dogs
go
over
pr
reviews
faster
and
then
I
can
I
can
like
for
me
it
will
take
half
a
day,
probably
so.
D
B
I'll
put
my
notes
in
here
about
the
retrospective
in
just
a
minute.
After
the
call
anything
else,
anybody
wants
to
bring
out
before
we
wrap
this
up.
A
I
I
just
want
to
repeat
one
thing
so
we'll
do
async
conversations
on
this,
so
if
anybody
wants
to
start
working
on
this,
just
put
a
comment
in
the
thread
that
we
already
have
in
six
contributes
that
okay,
I
am
talking
to
this
person
and
just
put
a
com,
but
just
put
the
relevant
information
in
the
doc
as
well
and
yeah.
So
we
can
take
it
forward
from
that.
C
So
about
what
debase
said,
are
we
going
to
post
some
messages
in
the
respective
channels
about
we
are
looking
for
folks
who
speak
native
languages
so.
A
C
A
Yeah,
I
I
think
I
I
would
suggest,
while
while
we
are
asking
people
for
translation
we
need
to
because
at
the
moment
this
is
particularly
this
particularly
discussed
in
in-depth
channel,
which
is
indian
fox.
So
we
also
need
to
reach
out
to
people
to
participate
as
well.
So
maybe,
while
you
are
drafting
some
words,
maybe
we
could
draft
some
messages
to
reach
out
to
people
who
are
interested
in
participating
or
maybe
who
are
interested
to
interview
or
help
us
with
getting
some
interviews
and
something
like
that.
A
C
Yeah
I
specifically
have
drafted
for
other
languages.
I
have
specifically
mentioned.
We
are
looking
folks
who
speak
mandarin
urdu
yeah,
so
I'm
planning
to
do
that.
So
I
will
draft
a
formal
text
and
will
tell
you
yeah
put
this
under
the
open
discussion
or
suggestion
part,
and
then
you
know,
let's
have
a
discussion
on
that
in
the
or
in
the
slide
and
proceed
with
that.
B
All
right,
I
won't
hold
up
to
meeting
anymore.
Thank
you
all
for
joining.
I
hope
you're
all
well
and
staying
safe
as
possible
out
there.
If
you
have
any
questions,
feel
free
to
reach
out
dwan
and
I
are
always
around
ish
and
obviously
you
can
always
reach
out
to
caslin
or
matthew
or
anybody
else.
That's
on
the
team
here
for
help.
Thank
you,
priyanka
for
all
the
work
you
did
during
the
meeting
and
are
going
to
do
in
the
future.
So
looking
forward
to
that.