►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting 20201009
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
All
right
welcome
to
friday,
everyone
happy
to
have
you
here
on
another
upstream
marketing
meeting
working
group
under
contrib
x.
It
seems
like
the
usual
crew
here,
so
no
new
introductions
to
start,
but
please
add
your
name
and
any
notes
you
have
or
or
discussion
points
you
have
to
the
marketing
meeting.
Welcome
welcome
first
place.
We
start
every
week
of
like
what
are
some
big
wins
related
to
what
we're
trying
to
accomplish
anything
new.
That's
happened
that
we
should
celebrate
or
point
out.
B
We
used
rajula's
contributor,
tweets
repository
and
automated
the
tweet
for
working
group
naming
and
that
point
out.
A
I
have
one
more
great
point,
chris
always
worthwhile.
Adding
these
days.
That's
a
very
optional
win.
One
thing:
that's
pretty
exciting,
rajula
kazan
and
I
brainstormed
on
a
topic
and
threw
it
in
kind
of
last
minute
to
the
kubecon
contributor
summit
queue.
I
don't
even
actually
know
when
we're
talking,
but
we
got
it
accepted.
We're
going
to
be
talking
about
this
working
group
and
doing
a
deep
dive
on
the
bots.
That
rajul
was
doing
doing
a
deep
dive
on
the
storytelling
that
caslin's
been
leading
and
I'll.
A
Do
the
overall
vision
stuff
that
jonas
paris
and
I
put
together
from
the
start,
looks.
D
A
Must
have
been
kubecon
had
I
like
that,
I
got
a
talk
approved
and
I
don't
even
know
the
context.
A
Let
me
look
that
up.
You
might.
A
A
I
I
have
I've,
been
I've
been
pretty
late.
Yeah,
it's
gonna
be
cute
clown
cloud
native
con.
We
are
attitude.
C
A
A
C
C
A
Well,
yeah,
we
would
not
be
where
we
are
without
everyone's
contribution.
Bob
you've
been
a
mentor
the
whole
time.
Chris
you've
been
a
mentor
the
whole
time,
george
always
swoops
in
to
save
the
day
when
we
need
him
so
like
there
and
paris
has
been
foundational,
I
mean
so
just
want
a
big,
a
big
hug
it
out
to
everybody,
but
thank
you
for
the
sport
and
yeah.
I
just
wanted
to
give
everyone
a
heads
up
that
we're
gonna
try
to
pitch
that.
A
Neat
yeah:
let's
say
we
made
it
to
the
schedule.
I
keep
going
cool.
A
And
great
all
right,
mbd,
all
right.
Moving
along
to
discussion
items,
the
editorial
is
pretty
quiet.
The
main
thing
in
progress
is
I've
been
collaborating
on
a
pr
that
I
think
merged
in.
I
got
to
double
check
the
status
working
with
sasha
to
get
a
definition
of
technical
lead
into
the
community
repository
and
then
once
that's
approved,
we're
going
to
just
collaborate
on
a
blog
post
to
get
that
onto
a
website.
A
My
my
proposal
is:
it
goes
to
the
contributor
site
as
a
one
of
the
first
ways
of
explaining
like
how
do
you
get
involved?
How
do
you
start
to
elevate
your
responsibility
inside
the
kubernetes
community?
That's
that's
the
only
kind
of
update
on
that
one.
A
D
G
D
Announcements
come
out
monday
afternoon
at
the
public
steering
meeting.
D
The
the
actual
blog
post
that
goes
on
careersnetio
is
has
historically
been
authored
by
the
election
committee.
It's
like
a
copy
paste.
Just
like
you
know,
here's
the
people
who
ran
congrats
to
the
winners.
You
know
the
the.
D
However
many
people
won,
but
that
should
definitely
be
followed
up.
You
know
tweet
and
maybe
open
the
door
to
something
else.
I
don't
know.
A
Okay,
is
there,
is
there
a
pr
already
floating
around
for
that
or.
D
D
For
the
oh,
for
the
for
the
election
is
that.
C
D
Yeah,
the
pr
is
usually
cut,
like
literally
at
the
same
time
that
it's
announced
just
because
of
what
you
know,
but
I
can.
I
can
link
you
to
the
previous,
like
blog
posts
that
have
been
pushed.
A
Cool
yeah,
we'll
grab
it
just
for
visibility,
would
be
helpful,
yeah,
great
and
casual
on
any
any
support
you
need
from
others
to
kind
of
have
that
covered
on
monday
or
chris
recovering
it.
I
just
want
to
take
a
moment
to
coordinate.
G
I'm
thinking,
if
you
bob
oh
there,
it
is
send
the
link
to
the
old
blog
post,
I'll
kind
of
take
a
look
through
that
and
create
a
pr
based
on
that,
and
then
we
can
just
kind
of
make
sure
that
post
is
good
to
go
on
monday
morning.
D
Well,
I
would
reach
out
to
like
josh,
ehrer
and
jace
since
they're
the
election
committee.
Again,
the
results
won't
be
public
until
monday
afternoon,
so
we
can't
like
you
know
you
can't
really
stage
the
pr
or
anything
like
that
until
well.
We.
D
If
you,
if
you
want
to
stage
it
and
then
just
like
as
soon
as
the
the
announcement
is
done,
just
pr
in
the
names
that
should
work
yeah,
actually
I.
G
D
I
think
they
would.
They
would
probably
appreciate
that,
just
because
the
the
election
committee
has
been
a
little
overrun
with
problems
this
time
around.
Oh,
no,
that's
not
good.
G
D
A
G
A
Yeah
cube
results
out,
I'm
just
adding
that
to
my
personal
calendar.
I
don't
think
I'll
set
up.
I'm
just
gonna
try
to
block
some
time
if,
if
anyone
needs
help,
then
but
yeah
also
just
it's
exciting.
It's
exciting.
G
A
C
F
F
G
A
Excellent
moving
right
along
the
our
our
kind
of
how
do
all
the
worlds
collide
through
some
bot
action,
we've
got
the
the
slack
bot
floating
out
there.
I
don't
know
if
we're
using
it
for
anything
yet,
but
just
we're
still
figuring
out
whether
it's
usable,
I
think
the
last
action
item
on
the
slack
bot
was,
I
still
planning
to
put
together
a
short
survey
to
team
leads
or
and
to
sig
leads
to
say
like
hey.
These
are
the
tools
we
have.
A
Would
it
be
helpful
if
we
use
them
in
these
different
ways
and
get
like
a
percentage
of
people
to
say
whether
they're
into
it
or
not
and
adjust
accordingly,
but
just
to
help
us
go
from
like
we've
got
a
nascent
tool,
but
we
don't
quite
have
a
strategy
that
we
know
people
want
to
use,
but
so,
in
the
meantime,
that's
kind
of
on
hold
the
tweet
bot
seems
like
it
just
passed
its
first
beta.
If
you
will,
with
the
working
group
the
naming
working
group
using
it
carthage,
you
brought
it
up.
Is
there?
A
Is
there
anything
you
want
to
note
about
how
people
use
it
the
good,
the
bad
and
the
ugly
of
the
experience
anything
like
that.
B
This
time
I
just
created
an
issue
by
myself
on
behalf
of
the
working
group
naming
and
the
good
thing
is
like
when
I
said
to
them
when
they,
when
the
meeting
was
happening
like
we
were
discussing
how
to
publicize
like
there
is
a
thing
called
working
group
naming
and
the
working
group
naming
handles
these
kind
of
like
starting
from
racial
discussions
to
all
the
offensive
and
non-offensive
inclusive
languages
as
well.
B
So
they
were
like
unsure
how
to
publicize
this,
and
I
said
like
we
have
a
contributors
tweet
handle
and
we
would
do
this
and
the
interworking
group
naming
was
so
happy
to
see
that
that
there
is
something
like
we
could
do.
The
only
thing
is
our
contributors.
Handle
has
very
less
amount
of
followers
compared
to
kubernetes.
B
A
I
think,
what's
what's
been
good
about
it
and
something
maybe
we
can
advertise
to
people
is
that
it
gets
picked
up
more
than
like
people
with
800
followers,
don't
get
50,
retweets
or
100
retweets,
but
that
that
case
contributor
handle
does
so.
I
think
it
it
has
the
right
level
of
influence,
but
definitely
short
on
followers.
For
now,.
A
B
B
So
that
is
one
thing
and
they,
like
the
end
users
of
the
tweet
handle
still
cannot
do
all
by
themselves.
We
need
to
actually
provide
an
issue.
So
that's
where,
like
we
had
another
discussion
like
we
should
automate
the
pr.
So
that's
the
stuff.
I
want
to
do.
A
Oh
okay,
can
you
say
that
one
more
time
automatically.
B
Like
so
when
what
we
want
to
do
is
like
say,
for
example,
if
I'm
part
of
like
working
group
naming
and
I'll
just
reach,
go
to
this
contributor,
tweets
repository
and
I'll
create
a
create
an
issue.
So
this
is
the
tweet
content
that
I
wanted
to
put,
and
this
this
is
probably
my
schedule
that
I
want
that
we
to
get
tweeted
and
then
I
should
do
no
more
than
that
unknown
less
than
that,
then
the
repository
should
have
the
intelligence
by
itself
like
doing
okay.
B
This
is
the
tweet,
and
this
is
the
time
it
should
get
tweeted
or
it
should
do
by
itself.
There
shouldn't
be
any
manual
intervention.
Maybe
an
approval
is
fine.
An
approval
is
required
like
how
we
do
today,
but
rest
of
the
stuffs
should
be
like
easy
for
the
end
users
it
is
so
simply
put.
It
is
not
that
user
friendly
at
this
moment.
A
B
E
B
My
bandwidth
is
like
not
so
great,
so
I
recorded
it
like
as
we
discussed
in
the
last
meeting.
So
if
you
could
share
that,
I
can
walk
through
that
sure.
B
Framework
like,
after
the
pr
this
uses
the
same
framework
as
rajula
have
created
on
the
contributors
repository.
I
did
this
prototype
in
my
own
repository,
so
it
has
a
issue
template
and
we
can
change
the
shoot
a
bit.
However,
we
want,
but
there
is
one
gotcha
like
this
is
something
like
bob
brought
up
last
time.
The
dco
part
I'm
not
sure
how
we
gonna
handle
this
because
we
need
so.
B
The
github
actions
will
check
in
the
file
and
it
will
create
a
pr
so
not
sure
the
developer
certificate
origin
would
work.
A
A
A
B
So
what
I
have
is
like
an
issue
template
where
I
would
ask:
what
is
the
tweet
content
that
you
want
and.
B
Yes,
yeah,
okay,
so
this
is
like
just
a
tweet
on
issue
template
and
when
you
say
like
okay,
create
a
new
issue,
you
will
be
provided
with
the
template
and
I
would
ask
like
okay
input,
your
teeth
content
exactly
below
the
commented
colons.
So
this
is
where
I'm
parsing
the
tweet
content
and
creating
a
file.
So
when
the
user
creates
the
content
there,
that
would
actually
get
into
a
pr
the
later
part,
the
last
one.
The
tweet
schedule
is
not
something
I
have
implemented
because
scheduling
api
is
not
available
in
in
our
twitter
together.
B
So
I
was
thinking
of
doing
a
cron
job,
but
that
is
later
at
some
point
in
time.
So
when
I,
when
the
user
creates
the
tweet,
what
it
does
is
like
the
github
actions
would
actually
without
the
time
the
github
actions
would
automatically
like
validate
the
tweet
length,
and
then
it
creates
a
pr.
B
So
the
moment
you
create
the
issue,
it
would
run
on
the
behind
the
scenes
and
then
it
would
create
a
pr
and
it
would
attach
the
pr
to
this
issue.
So
now,
if
you
look
into
the
issue,
sorry
pr,
you
will
have
this
resource
generator
like
we
can
change
the
comment
I
need
to
cc
the
author.
We
could
add,
assign
a
reviews
or
approvals
and
then
it
would
be
peered
over
here,
and
this
is
the
pr
that
the
user
or
the
approver
needs
to
approve
so
from
here.
B
If
they
approve,
then
rajulaspot
would
automatically
tweet
it
because
it
reaches
the
main
main
repository.
So
this
is
what
I've
done
so
far
and
the
one
other
thing
is
like
the
merge
conflicts.
With
with
this
approach,
we
wouldn't
have
any
merge
conflicts,
because
we
are
actually
adding
new
files
to
the
tweet
folder
every
single
time.
So
there
is
no
merge,
conflicts
or
merge
like
repository
based
or
accurate
at
any
point
in
time,.
D
So
I
I
like
this,
there
is
one
other
idea
I'm
just
thinking
about.
That
would
also
mean
for
things
like
enhancements,
freeze
and
some
of
the
other
stuff.
They
could
essentially
just
be
pre-canned
issue
templates.
So
it's
just
like
okay.
D
Freeze
is
the
state
come
in,
create
the
the
button
or
you
know,
press
the
button
for
enhancements
to
retweet
punch
in
some
of
the
little
other
details
and
go
yeah
the
I
would
definitely
want
so
like
all
the
tweets
to
be
approved,
the
pr
wouldn't
necessarily
have
to
be
approved
but
like
it
should
have
a
label
added
to
the
issue.
D
Even
if
it's
something
like
sort
of
like
you
know
what
we
do
with
needs
triage
right
now.
It's
just
like
needs
coms,
approval
or
something
like
that,
and
then
anyone
that
is
a
member
of
like
that
has
right
access
to
the
repo
or
a
part
of
a
you
know.
A
github
team,
like
our
coms
team,
could
essentially
you
know,
add
that
label
and
then
you
know
the
magic
happens
correctly.
G
Yeah,
this
would
also
be
a
good
opportunity
to
there's
an
issue
that
I
noticed
with
the
repo
is
that
we
need
to
have
a
consistent
naming
scheme.
I
noticed
that.
F
B
B
D
At
least
in
the
future
is
that
we
could,
like
you,
know,
every
year,
archive
the
tweets
that
were
previously
in
the
directory.
So
it's
just
like
you
know:
yeah
yeah,
yeah
well,
we'll
create
like
when
2020
is
finally
over
we'll
create
like
an
archive
2020,
folder
and.
A
B
So
I've
added
a
couple
other
features
as
well
that
I
missed
to
explain
so
I've
already
added
the
tweet
length
validation
in
this.
So
if
it
is
exiting
to
40
characters,
it
would
say,
like
your
tweet
length,
is
exceeding
the
tweet
character
and
then
it
would
ask
you
to
rephrase
it
so
once
you
rephrase
it
all
you
need
to
do
is
like
just
validate
like
slash,
validate
action,
comment
and
then
the
action
command
would
re-trigger
the
flow
flow
again
and
then
it
would
validate,
and
then
it
would
create
a
pr
beautiful.
B
B
And
the
file
name
extensions
like
how
we
wanna
do
as
well.
It
is
also
configurable,
if
you
want
to
say,
like
mmddy
or
bdm.
However,
you
want
it
would
create
in
that
in
that
manner,
but
with
30
characters
of
tweet
issue
title
as
the
file
name,
I
mean
I
don't
want
to
put
the
entire
issue
title
as
the
file
name,
because
maybe
someone
will
tweet
like
this
is
a
tweet
regarding
abc
on
xyz.
B
A
Great,
I
mean
those
are
all
good
assumptions
and
we
can
all
we
can
fine-tune
the
heck
out
of
the
details,
but
I
think
to
comment
on
the
overall
flow
that
you
are
thinking
through,
that,
like
people
can
now
tweet
via
an
issue
with
the
date
associated
with
it,
I
mean
I'm
just
blown
away
at
how
much
smoother
of
an
experience
that
would
be
for
people
that
that's
really
neat
and
like
to
have
the
bot
communicating
with
them
and
they're
able
to
validate
the
time
stamp
like
I
I'm
I'm
blown
away
sick,
it's
awesome.
B
B
I'll
also
do
the
prototype
of
the
crown
job
scheduling,
as
you
said,
and
then
I'll
just
do
a
pr2,
regular
and
then
rajula
can
decide
how
which
one
should
which
action
should
go
first
and
then
I
mean
obviously
regular
section
is
the
last
one
to
go,
because
that's
the
tweets
action
and
then
he
can
rebase
and
merge
it
into
that
contributor.
Tweet.
A
A
F
Okay,
wow:
that's
awesome,
good
work,
karthik.
F
A
I
I'm
very
I'm
100
with
you
and
yeah
cat
cat
who's
like
the
original
product
manager.
For
it
she
she
will
be
blown
away
and
right,
she's
looking
for
stuff
like
this
in
the
wild,
so
yeah
first
things.
First,
we
let's
get
it.
C
A
Yeah,
okay,
anyway
wow
that
was
cool.
So
what
can
I
I
guess?
Is
there
a
issue
in
our
community
repo
kind
of
following
along
with
this
or
is
it?
Is
there
anything
we
can
do
to
help
follow
along
and
keep
this
visible
for,
for
you
and
others
karthikayan
or
rajula.
B
D
I
I
can,
I
can
find
out
a
bit
about
bot
and
cla
stuff.
Okay,.
D
Yeah
we
have,
we
have
a
way
of
of
essentially
like
getting
bot
accounts
waitlist
for
that
sort
of
thing.
Yeah,
cool,
yeah,.
E
E
A
Yeah,
okay
yeah
for
first
things.
First,
like
yeah,
this
idea
of
the
issue
based
template
workflow
instead
of
people
manually
making
the
files
yeah.
I
I
think
I
I'm
like
oh
well,
isn't
that
convenient
enough?
You
don't
need
credentials
or
anything
you're
like
no.
You
just
made
it
infinitely
better,
so
good
deal
any
other
comments
or
questions
or
gaps
that
we
need
to
have.
Somebody
look
into.
A
All
right
next
up,
we've
got
tweet
content
recommendations.
By
is
that
you
rejuva
or.
E
B
I'm
gonna
ask
the
same
name
question
once
again:
sorry
for
asking
this,
but
okay,
so
look
looking
at
50
000
contributors
and
having
like
600
an
odd
tweet
followers
for
twitter
followers
for
kids
contributors.
Should
we
do
something
on
that
to
make
ourselves
more
branded
amongst
our
contributors.
D
That
too,
the
other
thing
I
just
want
to
say
is
like
the
contributors
metric
and
dev
sets
is
anyone
that
has
interacted
with
any
of
kubernetes
repos.
So
if
they've
created
an
issue,
if
they've
re
responded
to
a
comment
on
there,
that's
what's
folded
into
the
contributor
account,
so
don't
be.
I'm
like.
C
D
Our
more
active
base
of
users
is
roughly
around
3
000
people.
Yeah,
like
those
are
the
people
that
are,
I
would
say,
are
consistently
interacting
with
it.
A
Close
to
a
third
of
those
we're
we're
just
shy
of
a
thousand
followers
right
now,
but
I
I
mean
we
can
open
some
pull
requests
for
to.
We
can
just
directly
ask
people
to
follow
us
like
that,
is
a
useful
strategy
in
a
meaningful
way.
It's
like
hey,
if
you're
contributing
to
kubernetes
follow
here
for
the
latest.
C
So
this
week
I
actually
scheduled
a
tweet
of
my
own
for
my
own
account
to
like
go
out
and
say:
okay,
hey,
go,
follow
this
thing
and
like
that,
drew
some
people
to
it.
I
I
can
stuff
this
in
my
newsletter
as
well
this
week
to
just
be
like
hey.
If
you're
a
case
contributor
like
go,
follow
his
twitter
account,
for
you
know
the
latest
and
greatest
kind
of
thing.
D
The
other
thing
we
could
do
is
put
this
also
into
the
new
contributor
workshop
and
we're
making
a
completely
digital
version
anyway,
yeah.
D
As
part
of
you
know
just
like
when
we
list
like
what
you
should
join
like
you
know,
when
you
join
the
kubernetes
dev
mailing
list
or
you
know,
join
xyz,
we
include
you
know
if
you're
on
twitter
follow
the
contributor
account
here.
F
D
You
know
ensure
that
new
people
coming
in
would
at
least
a
greater
chance
of
them,
seeing
it
yeah.
C
Yeah,
I
mean
and
to
be
honest,
there's
only
so
much
we
can
do
right
like
it's
a
new
account.
It's
gonna
take
a
little
bit
of
time
and
twitter
growth
usually
happens
organically.
So
I
mean,
unless
you
have
like
one
big
event,
kind
of
thing
just
happen
on
twitter.
You
don't
get
a
lot
of
followers
all
at
once.
A
Yeah
we're
like
we're
still
so
people
know
about
us
as
an
ex
as
a
group
like
they're,
definitely
fewer
than
961
people
that
know
about
us
and
that's
how
many
followers
you
have
on
that
account.
So,
like
yeah,
we're
we're
in
the
early
stages
of
awareness,
but
that,
that's
not
to
say
we
shouldn't
always
be
keeping
that
in
mind
and
how
to
grow.
A
So
I
think
it's
the
right
question
and
to
take
a
second
to
think
through
that
and
and
brainstorm
different
ideas,
different
ways
to
get
the
word
out
little
competitions
if
we
can
think
of
a
competition
or
something
that
is
fun,
but
within
the
bounds
of
our
community
george.
What's
on
your
mind,.
H
C
D
D
A
C
H
I
gotta
know
oh
and
another.
One
is
to
also
ask
the
company
social
accounts
to
do
that
as
well.
So
like
well,.
H
G
B
F
F
A
Would
love
that
absolutely
yeah?
No,
it's
a
fair
question
because
we
do
try
to
take
our
vendor
hats
off
when
we're
in
sigs
and
working
groups,
and
I
really.
G
A
That
about
this
community
because
we
all
work
at
you
know
frenemies
and
competitors
and
all
of
you,
above
whatever
you
want
to
call
it.
But
at
the
end
of
the
day
I
think
yeah.
Absolutely
it's
still
very
realistic
to
say,
like
those
companies
are
allowing
us
the
time
to
invest
in
this
community
and
as
when
done
respectfully
like
absolutely
right.
Yeah.
A
H
A
Okay
and
who
knows
ian
well.
C
A
A
H
A
Okay,
good
we've
got
some
coverage.
There.
We've
got
a
few
light
ideas.
We've
got
some
longer
term
ideas,
great
current
again
great
call
we're
always
always
good
to
kind
of
invest
in
ourselves.
For
a
moment.
A
Okay,
so
at
the
back
half
of
the
meeting
where
we
normally
look
through
the
recurring
items,
their
calendar
walkthrough
of
email
announcements,
it
sounds
like
the
steering
committee
is
covering
itself,
but
is
there
any
other
big
things
happening
next
week
to.
D
Big
thing
will
just
be
the
the
tweet
on.
Oh,
I
think
on
our
side.
Well,
that
and
castle
said
she's
gonna
draft
the
well
potentially
draft
something.
E
D
D
An
announcement
like
we,
I
don't
remember
it
was
like
me
or
george,
who
authored
the
pr
but
like
we
had
the
the
pr
ready.
G
D
H
D
A
Great
sounds
like
a
plan:
we've
got
some
big
things
in
progress,
good,
we'll
we'll
see.
If
we
can
support
the
syrian
committee
announcements,
some
more
we've
got
julia
rajula
and
carthage
killing
it
with
this
twitter
integration
and
we're
gonna
get
some
growth
on
that
twitter
account,
as
our
focus
and
a
few
of
us
are
gonna,
put
together
a
talk
for
kubecon.
H
C
D
D
C
A
Okay,
well,
hey
I'm
glad
we
identified
that
because
it'd
be
good
to
have
there.
A
Great
all
right
well
moving
along
to
issue
walkthrough,
there's
nothing
standing
out
in
our
main
contrib
com
space
website
has
nothing
in
the
community
space.
I,
the
blue
link.
There
will
drop
you
where
you
want
and
the
only
one
I
wanted
to
bring
up.
I
think
we
have
enough
time
to
at
least
scratch.
The
surface
of
it
was
the
where
we
left
off
with
paris's
request
for
tweet.
Every
time
we
go
live
chris.
I
know
you
looked
into
it.
I
just
wanted
to
see
if
that
discussion
and
sig
contrib
acts.
C
C
C
Could
we,
if
this
than
that
to
twitter,
was
paris
thing,
and
somebody
plus
one
that,
and
that
sounds
like
a
potential
easy
lift
without
integrating
a
third
party
service,
but
would
be
a
third
party
server
like
we
wouldn't
have
to
integrate
it
like
authentication
wise
with
the
youtube
account
right?
It
would
just
be
some
third-party
thing
to
grab
the
email
and
then
send
tweet
kind
of
deal
that
makes
sense.
It
would.
D
Become
from
the
contributors
actually
account
which
we're
already
looking
into
full
with
zapier
for
other
things,.
C
H
B
Automated
that
it
was
account
whoops,
it
was
a
while
back
when
I
was
tried
zapier
for
my
personal
stuff
and
I
recommended
not
recommended.
I
was
discussing
like
pulling
again
like
injecting
the
zapier
into
the
meetings
and
it
was
told
like
we
don't
want
to
integrate
any
other
tool
into
community,
because
zapier
needs
licensing
as
well,
and
I'm
so
happy
because
with
zapier
we
could
do
millions
and
millions
of
automation.
H
D
H
D
The
right
now,
because
this
is
a
tangent
but
splaying
our
automation-
to
get
zoom
to
youtube-
has
been
abysmal
like
it,
it
works.
Maybe
half
the
time.
C
So
is
that
why
I
get
big
dumps
on
like
my
youtube
subscription,
for
that
account.
A
So
I
think
this
scene
has
a
lot
of
interest
in
automation.
I
mean
we've
made
that
pretty
clear,
but
so
george,
where
where's
the
best
place
to
follow
along
if
we
wanted.
H
H
D
Be
good
yeah
and
then
the
the
one
thing
I
will
say
is
like
if
it
requires
authentication
with
the
contributors
ad
account.
That
is
something
we
cannot
pass
around.
Only
three
people
have
access
to
that
account
because
it's
sort
of
the
master
keys
to
the
to
the
universe,
yeah,
just
just
as
a
broad
fyi
wait
keys
to
what
exactly
so.
The
contributor
is
that
to
like
g
suite
every
calendar,
every
yeah.
A
A
A
Yeah
but
I'd
say
you
know,
karthikayan
and
I
are
definitely
interested
so
far
if
others
are
interested
raise
your
hand
as
well,
but
I
really
love
messing
with
zapier
like
I
had.
F
H
F
A
A
It
it's
of
interest,
okay,
so
we're
those
interested.
The
follow-up
item
find
that
issue
in
the
community
repo
and
comments
on
it.
Volunteers
tribute
very
much
how
you
showed
up
here
and
we'll
we'll
tag
on
that
together.
That
sounds
really
fun
and
like
a
great
afternoon
and
I'm
not
being
sarcastic,
but
that
doesn't
actually
sound
cool,
but
with
that
I
think
we're
wrapping
up
right
on
time
for
this
meeting.
Thank
you
all
for
being
here
and
having
some
awesome
ideas,
and
we
will
see
you
next
week
awesome.
Thank
you
all
awesome.