►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220715
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220715
A
Hello
and
welcome
everyone
to
our
friday
july
15th
edition
of
the
contributor.coms
group
meeting
as
usual,
a
reminder
that
we
do
have
a
code
of
conduct
which
basically
says
to
be
excellent
to
your
fellow
attendees
and
speakers,
so
we'll
go
ahead
and
get
started.
Like
I
mentioned
before
I
started
recording.
I
went
ahead
and
created
a
notes
section
for
us
for
today.
A
A
All
right
and
before
we
get
into
our
regularly
scheduled
programming.
One
thing
we
like
to
do
at
the
beginning
of
these
meetings
is
invite
anyone
who's
new
to
introduce
themselves
and
tell
us
a
little
bit
about
why
you're
here
totally
optional.
But
if
you
would
like
to
speak
up
now,
please
do.
B
I'm
it's
my
first
time:
hey
caslin,
hello,.
A
B
Of
another
meeting
coming
in
I've,
hadn't
had
a
chance
to
come
in
and
join
y'all,
so
I
really
just
wanted
to
come
in
and
soak
up
all
the
the
cool
things
you
guys
are
working
on
and
then
get
kind
of
get
current.
You
know
me
probably
from
like
sig
release
or
some
of
the
other.
You
know
areas
where
I
try
to
like
step
in
at,
and
I
just
thought
I
would
come
over
and
just
slowly
get
caught
up
and
see
how
I
can
maybe
support
so
pretty
basic.
That's
about
it.
A
All
right
and
feel
free
to
jump
in
anytime.
We
are
a
pretty
informal
group
here.
So
if
you
want
to
say
anything
or
introduce
yourself
or
whatever
have
added
any
time,
we'll
start
off
with
updates
big
wins,
does
anyone
have
any
of
those
that
they
would
like
to
share
with
us?
A
I
suppose
I
can
start
with
one
thing,
which
is
that
I
actually
got
a
few
tweets
out
in
the
last
week.
Frederico
you've
been
doing
a
great
job
at
putting
in
prs
for
content
about
the
annual
report.
So
I've
been
trying
to
get
those
out.
I
meant
to
get
the
ones
out
last
week
out
last
week
and
then
I
see
that
you
added
more
this
week
so
anyway,
I'm
happy
that
we're
making
progress
on
those
thank.
A
I
haven't
noticed
anything
in
particular
in
the
slack
aside
from
those
new
tweets
that
you
submitted,
but
we
discussed
that
anything
else.
A
Cool
doesn't
sound
like
it.
If
there
are,
of
course,
we
can
always
come
back
to
it.
So
let's
go
ahead
and
hop
into
our
table.
I
suppose.
D
A
Oh
yeah,
that's
a
thing
you
could
do
with
that
sounds
complicated.
A
Complicated
and
turns
your
computer
into
a
rocket
ship,
not
so
bad
anyways.
D
A
So
our
first
item
in
our
table-
that's
good
to
move
on
to
yeah
is
hina
and
hina
is
not
here
at
the
moment.
We
discussed
this
a
bit
last
week,
though
she
needed
some
help,
because
she
wasn't
sure
how
to
set
up
the
notification
or
alert
to
our
team
in
github.
When
an
issue
is
filed
for
marketing,
I
suggested
that
she
try
asking
in
the
sig
controbex
channel,
but
I
don't
remember
seeing
that
it's
possible.
I
mean
there.
F
A
There's
a
thread
I'll
have
to
go
back
and
check
on
that
cool.
Thank
you
so
much
for
keeping
an
eye
on
that.
I
missed
it.
So
we'll
move
on
from
that
contributor,
tip
tweet.
This
is
kind
of
on
the
back
burner.
A
For
now
we
discussed
last
week
that
chris
was
cool
with
us
working
on
his
blog
post
and
getting
it
transitioned
over
to
the
dev
site,
but
I
don't
frederico.
I
think
we
decided
not
to
actively
work
on
this
just
yet
right.
A
D
And
let
me
know
when
you
do
do
it,
because
I
can
just
switch
everything
to
point
over
there
and
you
get
all
the
seo
magic.
A
Sounds
good,
and
our
next
item
is
the
two
items
in
this
table
that
are
both
about
buffer,
so
there
are
two
issues
that
we're
trying
to
solve
by
adopting
a
new
tool.
One
of
them
is
something
that
we've
been
trying
to
do
for
a
long
time,
which
is
auto-generating
blog
tweets,
we're
hoping
that
buffer
will
give
us
tools
to
do
that,
and
also
our
current
tooling
in
github
doesn't
allow
us
to
schedule
tweets,
which
is
pretty
frustrating,
so
we
have
the
requested
cncf.
A
A
Most
of
all,
all
right,
so
we'll
move
on
past
that
I
have
a
note
to
myself
to
check
in
on
that
which
I
I
should
do
more
often
next
item
roll
descriptions.
So
last
time
we
discussed
a
role
description
that
I
created.
I
don't
think
I've
seen
any
feedback
on
that,
though
it's
possible,
I
missed
something.
A
So
I
had
submitted
a
oh.
I've
got
three
thumbs
up,
so
that's
pretty
good.
A
I
had
submitted
a
social
media
role
to
our
role
handbook
in
our
github
repo
like
years
ago,
and
I
totally
flubbed
that
pr
just
github
issues,
and
so
it
never
really
happened.
And
then
we
decided
to
switch
to
this
council
thing
where
we
got
rid
of
roles
and
then
we
had
people
where
we
actually
needed
roles
again.
A
So
for
several
months
we've
been
discussing,
this
need
to
set
up
roles
and
shadows
in
our
group,
so
I
went
ahead
and
grabbed
that
old
social
media
role
and
kind
of
revived
it
in
a
hackmd
for
any
feedback
and
since
that's
been
open
for
like
a
week
or
so,
and
I
haven't
gotten
any
additional
feedback.
I
think
I'll
go
ahead
and
create
a
pr
for
that
which
I'll
put
on
my
physical
to-do
list
now
and
avinesh.
I
think
you
were
also
going
to
work
on
one
any
progress.
F
A
With
everyone
in
the
chat,
I
think
this
link
works
right,
haven't
used
hackmd
in
a
bit,
but
there
you
go.
You
can
take
a
look
at.
Oh,
there
is
one
comment,
nice
space
between
channel
and
it
would
be
good
good
catch.
Thank
you.
Imran.
A
So
if
anyone
wants
to
take
a
look
at
that,
they
are
welcome,
we
have
some
other
things
more
in
more
desperate
need
of
review,
which
I've
been
thinking
about
all
week
and
then
we'll
get
to
that.
What
is
next,
though,
anyone
else
working
on
roles.
Currently,
I
don't
think
so
right
sounds
good
and
these
two
have
kind
of
been
combined
into
one.
A
A
Make
a
note
to
do
that
after
the
meeting
yeah,
I
need
to
discuss
the
program
manager
concept
with
hina
and
also
atar.
If
I
had
an
approver
concept,
which
I
think
has
some
overlap
with
the
social
media
role,
but
I
think
it
also
actually
might
go
beyond
that.
So
I
need
to
talk
with
him
about.
A
A
A
It's
needed
work
for
a
while,
so
we'll
move
on
from
that
doesn't
even
want
to
discuss
roles
further
and
we
can
always
come
back
too.
A
A
A
D
D
D
A
A
C
C
Are
well
things
changed
last
week,
fortunately,
so
the
sig
architecture,
one,
is
in
progress.
I've
got
feedback
by
from
john
bellameric,
I
think-
and
of
course
well
now
it's
actually
doing
the
the
the
interview
etc.
C
But
it's
we
have
positive
feedback,
so
it's
in
the
new
stage
and
also
in
the
meantime,
while
I
was
waking
waiting
for
feedback
from
architecture,
I
open
up
the
the
thread
with
the
security
as
well,
which
also
replied
asking
for
some
examples,
and
I
I
provided
those
examples,
so
I'm
waiting
for
some
additional
feedback
there
as
well,
but
they
are
both
advancing
in
and
I
I
I
would
expect
that
next
couple
of
weeks,
one
or
the
other
will
have
a
output,
then
I
will
then
put
in
imd
and
we'll
be
sitting
there
for.
A
C
C
D
C
A
D
C
H
D
D
C
C
A
Also
another
note
on
that
before
I
asked
furnace
war
about
his
is.
We
were
also
talking
about.
Sig
docs
is
working
on
a
new
blog
process
where
they're
trying
to
make
it
a
little
lighter
weight.
They're
like
trying
to
make
the
whole
markdown
before
you
do
a
pr
thing
more
official.
I
think
yeah.
I
Yes,
I
posted
it
on
sick
dogs
on
the
advice
of
him,
and
I
also
got
comments
from
natalie
I'm
doubtful
about
one
thing
like
when
I'm
supposed
to
open
a
pr
like
the
I
guess,
the
academy
has
been
reviewed
by
two
to
three
people
now
and
which
one
I
guess
so
by
tim
it,
I
guess
tim
did.
The
first
review
and
natalie
went
through
it
as
she
left
comments.
I
guess
she
had
went
through
it
and
I
hope
someone
else
might
have
looked
upon
it.
I
A
A
Did
you
have
a
comment?
No
oh
cool.
Well,
I
put
the
hack
md
for
the
sig
storage,
one
into
the
notes
as
well.
So
the
two
that
we
immediately
need
to
review
on
are
furnace
wars,
sig
doc,
sig,
spotlight
and
frederico's,
fig
storage,
six
spotlight
that
correct.
A
I
A
A
Alrighty
I'm
going
to
move
on
to
the
next
item
in
our
table.
We
have
this
katakura
review
thing
still
on
here,
just
as
a
reminder
to
check
in
on
the
kadakota
situation
now
that
we're
doing
anything
with
it,
but
it's
just
really
interesting.
F
But
katakota
is
basically
stuck.
I
need
a
few
people
to
work
on
killer
coda
because
I
don't
have
the
bandwidth
at
the
moment
to
start
the
whole
killer,
coda
thing
myself,
so
yeah.
If
anyone
is
interested,
I
could
help
you
there's
a
migration
guide
from
catacoda
to
killer
coda
and
if
anyone
is
interested,
I
put
a
issue
on
the
contributor
catacoda
github
itself,
so
yeah
you
could
reply
on
that
and
we
could
align
and
work
on
that.
A
F
Could
delete
that
because
I
have
already
merged
that
pr
long
ago,
yeah.
F
F
So
I
don't
know
because
the
visibility
of
this
repo
wasn't
also
very
much
so
I
I
just
it's
like
open
for
help,
but
I'll
seek
some
help
from
like
maybe
I'll
post
it
in
the
slack
contribute
slack.
And
if
I
see
someone.
F
D
A
A
G
A
A
Alrighty,
if
anyone
else
wants
to
help
out
with
the
katakota
killer,
coder
coda
migration,
you
can
ask
debba
in
our
country,
xcom's
channel.
A
A
Ooh
buddy
totally
different
reasons,
but
anyway,
so
we'll
move
on
to
the
next
item.
A
Well,
that's
hina
hello,
hina!
If
you
had
any,
I
think
we
were
good.
We
heard
that
you
put
a
thread
in
sig
contrerbeck's
channel
about
the
the
help
that
you
needed
for
the
notifications
in
github.
If
you
want
to
add
anything
to
that,
I.
J
J
J
A
Enter
oh
okay,
trixie.
I
like
it.
C
C
Yeah
yeah:
well,
I
won't
waste
your
time,
but
it
was
like
a
commit
with
an
app,
but
that's.
It
went
to
like
several
hundreds
of
of
of
people,
the
entire
the
entire
epic
developer
community
received
dimension,
so
some
care
is
indeed
warranted
with
this
kind
of
automation.
D
C
J
A
J
So
I'll
go
ahead
and
try
that
I
will
basically
mention
the
team
and
say
get
support
from
at
contributor.coms
team
on
sending
message.
Blah
blah
blah.
A
A
J
J
Okay,
let
me
let
me
apply
the
first
part,
which
was
the
about
section.
I
don't
know
if
it's
successful,
but
if
it's
not
successful
one,
maybe
everyone
gets
a
ping
and
that's
just
humor
for
a
future
life
where
I'm
like.
I
remember
when
I
was
in
my
30s
and
I
tried
this
and
it
happened
and
then,
if
it
or
we
can
just
tweak
it
because
there
might
be
something.
J
A
A
All
right,
we'll
move
on
from
that
to
the
bottom
of
our
table
almost
which
is
annual
report
stuff.
We
already
discussed
this
frederico
you've
been
doing
great
work,
getting
tweets
into
our
repo
for
that
I've
been
sending
them
out
very,
like
spaced
out
did
say
I
wanted
to
space
them
out
so
that
they
get
more
attention.
So
this
is
a
bit.
C
Yeah
but
I'm
going
to
submit
a
couple
of
more
perhaps
but
also
spaced
out.
It
has
like
two
or
three
per
week
and
that's
sounds.
C
A
C
C
Exactly
so,
I
would
say
that
perhaps
I
don't
know
if
you
as
okay,
if
you
can
change
the
actual
link
when
you
commit
when
you
when
you
review,
maybe
I
don't
know,
I
know
that
I
can't
so.
I
don't
think
I
can.
C
No!
No!
No,
not
at
all,
just
that
note
that
I've
added
one
of
the
advantages
of
the
github
link
is
that
it
actually
allows
you
to
link
to
sections,
whereas.
E
C
E
A
A
A
Alrighty
anyone
else
reminder
there
are
all
sorts
of
links
in
our
table
item
there
on
the
annual
report.
A
If
you
want
to
help
out
with
doing
annual
report,
tweets,
there's
a
doc
where
you
can
find
out
which
ones
need
to
be
done
for
the
help
wanted
and
you're
welcome
to
skim
the
report
and
make
suggestions
for
what
you
would
like
to
see
tweeted
about
it.
Our
twitter
github
situation
is
such
that
contributors
can
submit
tweets
to
be
tweeted
and
you're.
Welcome
to
do
that.
A
All
right
I'll
move
on
from
that.
I
don't
remember
who
it
was
who
had
experience
with
the
validate
issue.
But
let
me
know
if
you
want
to
search.
D
A
Know
that
yeah,
it's
probably
somewhere
I'll
deal
with
that
later,
I
probably
won't.
I
should
make
a
note
I'll
move
on
to
the
next
thing,
though
there
was
an
apac
meet
our
contributors
blog.
I
think
that
went
out.
Didn't
it
dabba.
A
A
It
does
seem
like
an
itarva
and
reshula
kind
of
thing,
the
validate
thing
anything
else
on
that
apac
meet
our
contributors
blog
or
any
others
that
are
in
the
pipeline.
For
that
group,
do
you
know
anything
abnesh?
A
A
And
the
current
one
that
will
hopefully
be
posted
on
monday-
I
guess,
is
china
region
right,
yep,
lovely.
A
All
ready,
so,
unless
you
have
anything
else
on
that
we'll
move
on,
there
was
an
issue
on
the
k,
dev
site
that
pratish
wanted
to
work
on.
A
A
A
I
Yeah
I
was
there
and,
as
far
as
I
could
understand,
bob
told
that
there
is
something
with
golang
and
hugo.
It
needs
to
be
combined
and
something
needs
to
be
made.
I
don't
really
understand
what
you
meant
by
that,
but
something
on
that
lines.
Yeah.
A
I
I
As
far
as
I
search
through
the
nodes,
the
validated
command
comes
under
the
expertise
of
rajula.
I
guess
yeah.
I
D
A
A
Yeah
yeah,
don't
expect
anything
well,
you
can
expect
things
by
next
meeting,
certainly
usually
good
enough
for
that
all
right.
So
I'm
checking
in
on
that
the
k,
dev
site
stuff.
A
What
I
thought
so
there's
this
issue
that
we
were
just
discussing
I'll
put
it
in
the
chat,
there's
an
issue
with
like
scheduling
posts
to
go
out
on
the
kdev
site,
something
about
hugo
or
something
needs
to
be
fixed.
I
don't
know
anything
about
it.
Uh-Huh.
D
A
J
D
A
A
Yeah,
but
we
were
also
saying
that
your
expertise
on
the
k,
dev
site,
is
something
that
is
valuable
and
that
we
should
maybe
make
into
a
role.
A
A
Alrighty
so
move
on
from
k.
Dev
next
item
deba
had
a
blog
in
need
of
review.
F
So
yeah,
I
did
the
review
from
my
end
and
also
the
blog
is
being
reviewed
by
sick
dogs
as
well
so
yeah.
So
the
task
is
completed,
they
needed
reviewers
and
they
have
reviewers.
Now.
E
I
know
hang
on.
E
D
A
A
A
A
So
I
want
to
make
sure
that
I
have
the
time
to
mentally,
like
absorb
all
of
the
things
that
I
have
to
do,
which
we
could
do
in
a
meeting
and
then
josh
wanted
us
to
schedule
that
so
that
he
could
help
us
do
it.
So
I
just
have
to
process
it
just
intimidating.
A
We
would
love
to
help
folks
do
like
a
development
role
for
our
group.
The
issue
that
we've
always
had
with
that
is
that
none
of
our
leadership
of
this
group
have
much
development
like
that.
We
do
normally
at
least
like
we
might
have
some
experience
with
it.
I
I
have
a
little
bit,
but
a
lot
of
the
work
we
do
has
not
been
development.
Focused
rajula
is
the
most
most
kind
of
dev
focused
of
us,
and
you
know
he
has
been
busy.
A
D
F
Just
to
add
one
point
on
that,
mainly
I
have
tried
exploring
a
lot
of
these
things,
being
it
validation
thing
and
the
twitter
and
the
kdf.
The
one
problem
that
I
faced
a
lot
is
it's
very
hard
to
explore
the
code
base.
Basically,
the
documentation
are
not
that
good.
That
can,
you
know,
get
you
explore
the
entire
code
base
and
you
know
things
how
things
are
working.
So
maybe
that's
a
problem
that
we
don't
have
a
developer,
something
maybe.
D
A
K
So
maybe
I
have
a
question
as
well.
Yes,
so
it's
regarding!
So
since
I'm
new
here
I
I
don't
know
much
of
the
topics
so
so
I
can
also
be
maybe
helpful
here.
So
I
have
a
dev
background,
maybe
not
in
the
exact
framework,
but
I
could
also
help
on
this,
but
I
have
to
check
what
it's
exactly
what's
expectation
so.
D
A
B
K
F
F
A
Cool,
so
one
thing
that
I
was
kind
of
thinking
about
earlier
that
feels
good
to
mention
is
frederico.
I
feel
really
bad
that
we
haven't
been
able
to
review
your
blog
post
yet,
but
if
the
blog
team
is
incorporating
this
hackmd
process
into
their
workflow,
we
discussed
last
time.
Should
you
also
ping
in
blog
docs
blogs,
say
doc's
blog
subproject,
and
I
think
the
answer
is
yes
at
this
point.
Okay,
last
time.
C
No,
don't
worry
about
it,
I
I
don't
know
I'm
not
in
a
hurry.
It's
just
it's
good
to
know
the
processes
and
improve
them
yeah.
It's
perfect!
Your.
A
A
A
Yeah
looks
like
he's
not
in
at
the
moment,
so
we'll
go
ahead
and
pass
on
that
for
now
and
then
security
comms
guidelines.
Oh
yes,
so
this
was
something
I
brought
up
last
time.
That
was
something
I
came
up
with
as
an
idea
for
us
to
do
like
a
long
time
ago
and
then
never
followed
through
on
and
avinashi
mentioned,
that
you
are
interested
in
pursuing
this
further
because
you're
already
doing
some
work
with
the
security
sig
for
last
week
in
kubernetes,
okay,
yeah.
F
So
actually
imran
contacted
me.
He
reached
out
to
me
asking
if
he
can
take
this
task-
and
I
said
yes,
but
unfortunately
he
couldn't
make
up
in
the
meeting
yesterday.
So
I
represented
him
and
asked
about
the
guidelines
and
folks
there
were
really
excited
about
the
idea
that
yeah
they
require
a
guideline
for
that
and
the
I.
I
have
shared
the
documentation
for
communication
and
they
said
that
yes,
they'll
they'll
have
a
look
and
do
some
things
and
they
they
might
you.
A
Wonderful
to
recap,
this
idea
here
was
communications
about
security
are
very
sensitive,
and
so
we
want
to
set
up
some
guidelines
on
how
we
communicate
about
security
stuff.
So
we
wanted
to
work
with
the
security
sig
to
kind
of
set
those
guidelines
up
and
document
them.
D
K
I'm
joking
within
a
few
seconds
but
yeah
just
for
since
I'm
newbie.
So
I
was
just
wondering
if
there
is
any
onboarding
for
the
sub
particular
projects
sub
project,
because
I
I
see
too
many
details
in
the
table,
but
there
is
no
tasks
and
expectations.
I
see
the
details,
but
somehow
I
miss
the
big
piece,
the
y
part,
and
how
should
I
approach
because
the
this
particular
piece
about
the
security
guidelines?
I
asked
avinesh
a
sink
and
then
he
could
get
things,
but
I
really
don't
know.
K
A
A
I
put
in
in
the
chat
it's
also
at
the
top
of
our
note
stock.
If
you
yeah.
A
Okay,
perfect,
so
that's
the
main
document
that
we
have
in
terms
of
why
our
group
exists
and
the
general
concept
of
what
we
do
so
part
of
this
whole
onboarding
concept
is
creating
these
roles.
Like
we've
been
talking
about
we're
trying
to
define
what
the
types
of
kind
of
areas
people
do
work
in
are
for
our
group
and
once
we
have
those
defined,
we
can
also
set
up
shadowing
so
that
people
can
work
in
a
specific
area
and
develop
expertise
and
then
over
time
gather
ownership
of
those
areas
as
well.
A
So
that's
kind
of
something
we're
kind
of
in
the
process
of
creating.
So
right.
Now,
it's
more
of
a
general
here's,
our
group,
here's
what
we
do
in
the
charter!
If
we've
had
people
ask
in
this
meeting
before
for
us
to
kind
of
explain
it.
So
we
can
do
that
too,
but
it's
just
kind
of
free
form
at
the
moment,
and
we
would
like
to
fix.