►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20210319
Description
[SIG ContribEx] Weekly Marketing Meeting for 20210319
A
Welcome
everyone
to
a
friday
edition
your
usual
edition
of
the
upstream
marketing
community
meeting
under
sig
contributor
experience.
We
all
work
under
the
same
code
of
context
so
be
excellent
to
each
other.
Thanks
for
joining
today.
I
I
recognize
all
the
names
here,
slotted
nice
to
have
you
back
man
and
josh
nice
to
see
you
as
well.
A
B
A
Yeah
yeah,
that's
a
big
difference.
I
I
underestimate
an
hour
every
time
until
that
actually
rolls
around,
and
then
I
feel
like
a
zombie
for
a
week
like
well
good,
I'm
glad
it's
working
well
for
you.
That
makes
me
happy.
Okay,
cool
our
normal
agenda.
We
kind
of
kick
off.
Has
there
been
any
big
news,
wins
that
we've
seen
in
the
community
that
we
want
to
highlight.
A
A
A
C
The
I
just
logged
in
this
morning
to
see
what
our
account
was
and
actually
look
at
the
answers.
A
A
Yeah,
thank
you
for,
for
others
to
catch
up,
so
the
contributor
survey
goes
out
every
year.
It's
a
big
part
of
our
feedback
loop,
and
I
think
we
noticed
this
year.
I
think
the
consensus
is
that
people
may
not
have
responded
because
they're,
like
oh
I've,
seen
these
questions
before,
but
tracking
the
delta
over
time
is
really
important.
C
C
D
A
Incentive
of
lying
to
a
survey-
well,
that's
great!
We
we
did
a
little
bit
of
tweeting,
always
with
the
caveat
that
we're
really
asking
for
contributors
to
respond,
but
I
think
the
coolest
thing.
This
is
the
first
case
where
rajula
he
built
this
really
incredible:
multi-channel
slackbot,
where
you
can
send
a
single
message
across
all
the
different
channels
in
our
kubernetes.
A
It's
it's
an
incredibly
powerful
tool
that
you
shouldn't
use
lightly
or
you'd
drive
everybody
nuts.
So
this
was
the
first
actual
use
case
of
it.
That
seemed
right.
It
looks
like
he
sent
it
out
today,
so.
C
A
A
Oh,
that
is
a
moment
like
we
should
all
take
a
moment.
Be
very
thankful.
That's
awesome!
It
is
hard
to
get
people
to
respond
to
surveys
and
yeah.
It's
it's
used
by
contrabex
to
do
cool
things.
I
wish
bob
was
here
to
tell
you
some
of
the
wins,
but
in
short,
it's
important.
If
you
haven't
done
it
yourself,
yet
you
know
what
if
you
you've
all
oops,
I
just
deleted
that
sorry,
man,
let
me
add
the
link
survey,
all
right.
The
link
is
in
the
notes
and
in
chat.
A
If
you
want
to
have
listen
to
me
and
fill
out
that
survey
or
save
it
for
after
this
either
way
is
good
for
me,
it
will
definitely
be
helpful.
Josh.
What's
your
take,
is
there
anything
we
can
do
to
continue
to
be
helpful
there?
I
know
you're
working
hard
getting
this
out
there
to
people.
I
think
you're
on
mute.
If
you're
talking.
C
I
think
we're
approaching
the
maximum
that
we
can
expect
in
a
time
like
this
great.
The
a
lot
of
people
are
freaking
out
about
a
year
of
quarantine,
yeah
and
are
not
necessarily
up
for
doing
any
extra
tasks.
C
So
I
I
would
be
surprised
if
we
were
able
to
get
over
150
responses
total
the
also
there's
nothing,
there's
nothing
new
or
controversial
in
this
year's
survey.
Previous
surveys
have
had
questions
that
people
actually
cared
about
this
year.
Pretty
much
just
has
the
road
questions
and
I
think
that's
the
other
reason
why
why
you
know
we're
seeing
sort
of
lower
numbers
than
we've
seen
the
last
two
years.
A
C
There
was
something
discussed,
but
in
the
end
I
the
steering
decided
that
they
did
not
want
it
in
the
survey.
So
I.
A
Respect
that
yeah,
I
think,
being
kind
to
people's
brains
right
now
is
important,
yep
good!
Well,
hey!
I
just
want
to
shout
out
to
joel
one
more
time.
I
thought
it
was
such
a
great
idea.
We
definitely
saw
a
bump
in
responses
after
the
twitter
post,
saying,
like
hey
we're
at
this
number,
we're
trying
to
get
to
that
number
and
that
little
framing
of
gamifying
it
a
little
and
being
helping
the
team
grow.
It
worked.
So
thank
you
for
that
suggestion
really
good
call
good!
Okay!
Well
one
update
talking
about
articles.
A
We
we
have
quite
a
few
in
progress,
so
the
the
agenda
was
getting
pretty
long,
so
took
the
time
to
reinstate
the
github
project.
You
know,
since
this
group
founded,
we
were
very
heavy
on
github
we've
since
kind
of
pivoted
to
make
sure
that
marketers
and
designers
and
people
who
aren't
in
github
all
day,
don't
feel
obligated
to
know
it.
But
what's
great
about
projects,
is
it
it's
pretty
lightweight
and
we
can
add
cards
after
each
of
this
meeting's
conversations
and
just
keep
it
a
little
like
a
trello
board.
A
A
Okay,
so
if
we
check
out
the
board,
we
go
from
on
the
far
left,
uncommitted
ideas,
just
kind
of
things
that
have
been
floating
around
we've
been
talking
about
all
the
way
to
published
and
in
between
old
habit.
I
go
right
to
left
because
we're
always
trying
to
optimize
for
flow
and
get
things
to
publication.
A
A
A
D
D
D
A
Know
that's
exactly
right:
okay,
yep
yeah,
basically
yeah.
I
open
the
pull
request
and
since
you
don't
have
right
permissions
to
my
branch
and
the
pull
request,
the
right
thing
to
do
is
open
a
pull
request
against
my
repo,
and
this
is
why
git
should
not
be
considered
trivial
knowledge.
French.
First,
exactly.
D
It
took
me
a
good
10
minutes
to
like
figure
out
which
branch
and
fork
and
tree
I
needed
to
do
you
know
what
to
to
make
this
happen
right
because
I
like,
because
github
is
notoriously
bad
at
telling
you
like
this
is
where
it
came
from.
This
is
where
it's
going
to
right,
so
like
it's
very
tiny
print
like
right,
underneath
the
the
label
or
whatever
the
title
of
the
page.
So
it's
like.
E
But
but
essentially
when
yeah
I
mean
agreed,
so
when
somebody's
doing
content
as
a
in
get,
we
essentially
use
their
repo.
We
all
step
on
their
repo
right,
like
it's
matt's.
D
Or
whoever
submits
the
prs
to
the
upstream
repo
to
the
community,
actual
community
communications
repo?
They
need
to
do
it
on
whoever
started
the
original
post
or
the
original
pr
right
like,
and
they
do
it
as
a
pr
and
then
we
do
prs
against
their
their
pr
against
their
fork
and
that
gets
pushed
up
into
the
community.
Hopefully
yeah
so
clear.
G
G
A
D
A
D
Yeah,
you
might
have
a.
I
think
this
could
be
a
better
idea.
Josh.
I
want
to
bounce
it
off
you
could
we
have
like
a
draft
repo
or
like
a
draft
thing
somewhere,
maybe
that
we
could
all
pr
against
all
at
once
kind
of
deal.
C
C
D
G
A
B
Also,
I
guess
it
had
the
option
of
directly
writing
suggestions
to
the
pr
right.
So
I
guess
the
reviewers
have
that
access.
So
you
can,
if
you
want
to
add
a
suggestion,
you
can
directly.
E
D
A
Like
if
I
did
that
clicking
the
suggestion
and
then
adding
new
text,
if
I
hit
add
single
comment,
you
can
then
just
one
click
merge
that
in
as
opposed
to
doing
the
whole
pr
review
system.
E
A
A
A
It's
kind
of
like
a
sign
off
process
where
reviewers
are
requested
and
you're
asked
to
sign
off
on
something
along
the
way
in
your
review.
You
can
click
the
suggest
button
on
a
on
a
block
of
text
or
code
and
then
in
that
snippet
of
the
tilde,
tilde,
tilde
or
tick
tick,
tick
suggestion
you
can
change
that
block.
That
will
show
up
to
you,
chris
as
an
option
to
merge
that
suggestion
in
yeah.
These.
A
Merge
in
yes,
so
when,
when,
when
bob
added
comments
in
here,
you
had
to
do
something
else
in
order
to
get
that
merged
in,
but
I
yeah,
I
think
so.
We
we've
brought
up
a
couple
times
like
what
is
the
path
of
least
resistance,
even
if
it's
not
the
easiest.
Yet
what
is
the
path
of
least
resistance
to
for
our
editor
editorial
flow?
A
We
haven't
documented
this.
I
don't
know
if
the
blog
team
already
has
something
that
we
could
work
from,
but
there's
definitely
a
gap
here
that
we
need
somebody
to
fill
with
our
recommended
like
well,
first
off
just
document
what
we're
doing
and
then
like,
let's
iterate
from
what
we're
doing
to
what
we
could
be
doing.
That
would
be
a
lot
easier.
A
E
E
D
A
A
Cool
all
right
that
was,
we
went,
went
a
little
along
the
side,
but
we
should
add
this
as
a
new
item
like
documenting
our
writing
process
we'll
get
to
that
further,
but
any
other
articles
that
people
are
working
on
that
they
want
to
get
on
the
board,
make
sure
that
we're
tracking
them
and
we'll
just
check
in
regularly-
and
this
is
just
for
personal
accountability
and
so
that
when
you
ask
for
help,
somebody
can
tag
in
pretty
easily.
A
I
I
had
I
had
claimed
the
kubernetes
by
the
number.
Can
I
do
that
now?
Oh
yeah,
so
I
think
one
one
thing
we
do
need
to
get
you
joel,
we'll
need
to
get
you
org
membership
so
that
you
can
start
participating
on
this
board
directly.
I
think,
but
I
would
be
happy
to
do
so.
A
I
have
edit
rights
here,
so
I'm
happy
to
do
so.
Okay,
okay
by
the
number,
do
you
what's
your
joe?
What
is
it.
A
Yeah,
the
first
version
was
tough
to
hear
laughs
by
the
numbers:
troll
byron,
barker,
save
note
and
then
yeah,
there's
you
so
say
and
I'll
just
drag
it
here
it
and
then
I
was
just
gonna
leave
these
evergreen
topics.
If
something
ever
comes
up
where
you
wanted
to
do
a
roundup
of
ideas,
how
to
use
a
feature,
do
a
sig
spotlight,
ideally
we'll
get
to
the
point
where
there
is
documentation
on
what
does
it
mean
to
take
one
of
these
ideas
and
write
about
it?
A
But
for
now
just
documenting
stuff.
We
had
floating
around
into
a
little
bit
of
more
visual
process.
B
Right
and
thank
you
joel
for
the
comments
on
on
my
contributor
story,
so
I
will
put
that
in
by
next
week.
I
should
have
a
pr
open
and
we
can
start
putting
in.
E
While
you're
typing
and
I've
been
talking
a
lot,
so
I'm
self-conscious
about
it,
but
I
did
want
to
say
I'm
really
enjoying
editing
people's
stuff
feedback
about
editing
is
always
very
helpful.
I
can
always
be
better
at
that
and
more
contextual
to
the
project.
So
if
there's
any
critique
of
my
critique
please
please
don't
be
shy
about
that.
A
Very
thoughtful-
I
definitely
missed
some
more.
This
is
ph
mine.
A
Slot-
and
I
know
we-
we
talked
about
it,
so
no
obligation
if
nothing's
happened
on
it,
but
you've.
I
think
you
still
have
a
a
very
cool
story
of
being
a
developer.
Who
wants
to
use
the
this
community
to
learn
some
marketing
practices?
Is
that
still
something
you
might
want
to
explore
as
an
article?
Like
writing
a
few
paragraphs.
A
C
Okay,
probably
people
have
seen
the
issue
already
so
last
week
in
kubernetes.
Development
is
a
newsletter
that
noah
kantrowitz
and
I
have
been
doing
for
the
last
three
years,
actually,
which
is
kind
of
a
scary
thought
that
summarizes
what
happened
in
mostly
core
kubernetes
development.
Over
the
previous
week,
the.
C
We
are
talking
in
a
general
contributor
experience
about
making
it
into
a
sub-project
I,
rather
than
having
it
be
a
completely
independent
thing.
The
and
people
seem
very
positive
to
that.
So
I
wanted
to
bring
it
to
this
meeting.
I
mean
what
that
would
practically
mean
is
moving
it
from
the
namespace
it's
currently
in
to
kubernetes
sigs,
the
realistically.
C
Nothing
else
would
have
to
change,
obviously
noah,
and
I
would
love
to
have
additional
contributors
to
the
newsletter
like,
for
example,
one
of
the
things
we
have
always
wanted
to
do
was
add
some
coverage
of
sort
of
the
close
dependency
projects,
things
like
csi,
etc,
and
we've
never
had
enough
time
to
actually
do
that
ourselves,
the,
but,
but
mostly
it's
just
you
know
to
turn
it
into
an
official
publication.
C
Bob
has
also
made
noises
about
including
a
copy
of
it
in
the
new
contributor
site.
Oh
nice,
the
as
a
way
for
contributors
to
keep
up
with,
what's
going
on,
which
is
what
we
wrote
it
for
in
the
first
place,
so
the
so.
C
I
don't
know
we
need
to
do
anything
other
than
that.
If
you
all
want
to
just
plus
one
it,
then
we
will
take.
C
And
handle
the
namespace
transfer.
C
The
what
we
would
do
is
we
would
just
pick
up
the
stuff
in
the
posts
folder
for
the
contributor
site,
possibly
add
some
additional
metadata
to
them.
If
hugo
needs
that
I
don't
know
if
it
does,
and
and
just
do
that,
we
don't,
we
don't
want
to
take
down
the
original
site
because
it
has
a
lot
of
subscribers.
Now.
C
One
of
the
things
actually
for
this
group
is
that
one
of
the
things
that
we
need
to
do,
which
is
actually
kind
of
pushing
us
to
finally
get
this
done,
is
so
there's
several
mechanisms.
Distribution
of
lwkd,
one
of
them
is
email
right
now
we're
using
mailchimp,
and
we
want
to
get
off
of
mailchimp
for
very
well
publicized
reasons.
C
A
Gotcha
yeah,
it's
it's
something
we
haven't
needed
to
have
an
official
position
because
we
haven't
run
a
newsletter,
but
it's
something
I'd
be
happy
to
yeah
review
the
options
on
I
mean:
there's
some
really
cool
ones
for
markdown.
Only
content
these
days
really.
C
The
at
this
point
we'd
actually
be
rather
more
inclined
towards
one
where
we
paid
a
nominal
fee
yeah,
because
obviously,
as
milton,
has
showed
us,
if
you're
getting
something
for
free,
it's
not
really
free,
the
and
and
don't
have
preferences
right.
It's
it's
super
simple
right.
We've
got
markdown
content
that
we're
pasting
into
newsletter.
It's
going
out
too
much
subscribers
we're
not
doing
any
tracking
the.
C
A
Yeah
yeah,
so
there's
definitely
a
good
newsletter
option.
You
know
something
it's
worth
just
saying
out
loud.
I
don't
know
how
complex
it
would
be
would
be
alternatives
to
mailman
that
I
really
enjoy
is
actually
discourse.
A
A
C
C
The
oh.
G
C
A
E
Can
I
say
a
couple
questions
josh
about
this
is
a
couple
times
this
has
come
up.
One
is
this
is
like
I've
heard
this
a
couple,
other
meetings.
Are
there
any
oppositions
or
anybody
standing
in
the
way
of
doing
this
I
mean,
can
we
okay?
So
let's
we
should
grease
the
bra.
C
C
C
So
at
this
point
it's
probably
about
two
hours
a
week,
each
the
a
lot
of
which
is
reading
all
the
merges
from
the
previous
week,
the
when
we
first
started
it
was
a
lot
more
than
that.
It
was
actually
probably
four
or
five
hours
of
my
part.
E
C
E
C
C
Be
one
of
the
fastest
I
mean
I,
I
honestly
I
started
this
back
when
I
was
the
pr
lead
for
release
1.9
and
decided.
You
know
it
was
silly
to
have
only
the
release
team
aware
of
all
the
pr's
that
were
coming
in
so
the
and
yeah,
and
so
keeping
up
we're
not
planning
on
stopping
maintaining
it.
It
was.
It
was
honestly,
more
of
we've
kicked
around
the
idea
of
making
it
a
sub
project.
C
We
were
waiting
for
the
contributor
site
to
go
live,
and
then
we
were
just
waiting
to
get
around
to
it,
and
this
mailing
list
issue
kind
of
pushed
it
right
because
we're
saying
hey,
if
we're
actually
going
to
be
potentially
paying
a
vendor
for
newsletter
service,
then
maybe
it's
time
to
actually
deal
with
getting
it
made
into
an
official
project
thing.
G
E
But
but
if,
if
josh
and
the
people
who
are
making
that
had
access
to
the
project
thing,
they
could
put
unclaimed
ideas
in
based
on
what's
happening
there.
That
would
inform
what
we're
doing.
I
think
you
could
really
be
a
idea
generator.
C
Yeah
well,
and
it's
actually
it's
a
good
writing
opportunity
for
people
who
are
having
trouble
working
their
way
up
to
a
full
article
because,
like
for
example,
if
somebody's
covering
what
happened
in
csi
last
week,
what
you
really
want
for
lwkd
is
basically
like
three
to
five
lines
rather
than
a
full
article,
and
so
it
can
be
good
writing
practice
for
people
who
are
getting
used
to
writing
for
publication.
A
Hey
started
what
we're
gonna
add.
H
Yeah,
no,
no,
I
was
actually
gonna
say
I
do
a
bit
of
contributions
on
the
release,
notes
and
yeah
kind
of
like
yeah,
so
this
kind
of
you
know
comes
in
line
with
like
having
looked
at
the
release
system,
we're
putting
some
in
in
this.
This
kind
of.
C
C
A
That's
cool,
that's
really
cool!
Well,
this
yeah!
This
is
wonderful
josh!
You
have
our
full
support.
I
think
like
it
sounds
like
infra's
got
to
do
the
heavy
lifting
here
so
just
keep
us
posted
if
we
can
help
that
along.
C
A
Yeah,
okay,
in
the
meantime,
it
sounds
like
why
don't
yeah
reach
out
to
josh
and
and
see
how
you
can
tag
in
and
and
be
part
of
this
I
think
cool.
That's
it.
It's
an
excellent
way
for
you
to
get
involved,
love
it.
Thank
you
josh!
That's
it's
really
exciting
happy
to
be
in
a
place
where
we
can
be
a
a
place
for
new
for
long-standing
projects
to
to
hang
out.
That
makes
a
lot
of
sense.
A
Well,
good,
all
right,
moving
right
along,
we
mentioned
a
couple
times
the
writing
process,
and
I
now
realize
this
isn't
a
new
idea
and
it
was
documented
21
days
ago,
which
is
wonderful,
jason
started
an
issue
and
a
to-do
list
of
oh
yeah,
picking
up
the
to-do
list
of
our
workflow
in
the
storyteller's
handbook.
A
So
there
is
a
there
is
a
place
to
write
that
if
you
have
observed
what
we're
doing
with
writing
and
want
to
just
take
some
notes,
you
can
do
it
right
in
this
github
issue
or
you
could,
if
you're
more
comfortable
with
github,
you
can
pick
it
up
and
and
open
the
pull
request,
but
just
note
that
yeah,
let's
there
is
a
place
for
that
and
I'll
add
that
to
our
tracking
board.
So
we
can
see
that
easily.
A
Excellent,
all
right
going
into
the
back
half
of
the
meeting
we
go
into
improvements.
It
gets
more
into
the
navel
gazi,
how
we're
using
github
and
how
we're
keeping
organized,
if
you're,
here
for
for
content
and
writing
and
want
a
drop
you're
welcome
to
right
now.
That
is
no
problem.
But
if
not
I'm
going
to
say
you
are
hanging
out
for
the
for
the
meta
conversation.
A
One
thing
going
around:
we've
had
these
long-standing
github
issues
around
sig
profiling,
which
really
cool
way
to
have
an
excuse
to
reach
out
to
sigs,
but
it
kind
of
hit
a
dead
end.
It
hasn't
gotten
much
further.
A
couple
months
ago
we
talked
about
transitioning
from
a
long-standing
github
issue.
It's
been
around
for
two
years
to
more
of
something
that
can
work
for
an
editorial
flow.
G
A
Then
we
can
draft
an
article
around
that
we
got
a
very
I
put
together
a
very
loose
structure
of
it.
The
work
in
progress,
sig
profiling
articles
document.
A
A
A
So
you
know
a
v1
in
my
head
might
be
say
you
wanted
to
do
a
profile
on
sig
network
and
they
have
an
h2
header
that
you
can
link
to
and
you
could.
Maybe
maybe
the
standard
is
like
we
comment
on
it.
Saying
like
hey,
joel
is
working
on
this
article.
Please
add
notes
under
here
and
then,
when
you
reach
out
to
people
in
slack,
be
like
hey
sig
network.
We
want
to
talk
about
you,
here's
a
document
where
you
can
drop
some
notes
and
see
if
that
works.
A
I
think
that
that's
the
intention
like
see
if
we
can
get
to
something
to
experiment
with,
because
the
the
process
of
putting
a
lot
of
effort
on
a
writer
to
go
and
reach
out
to
people
and
set
up
calls
has
sounded.
It
hasn't
resulted
in
many
articles
in
the
last
year
so
wanted
to
see
if
we
can
think
of
a
lighter
weight
way
of
doing
so.
A
Very
cool:
okay!
Thank
you
canal,
great
I'll,
I'll,
open
a
github
issue
for
this
specifically
and
tag
you
in
it.
D
I
also
have
a
call
with
kesley
next
week
for
the
twitter
thing:
yeah.
A
That's
wonderful
great
all
right
kind
of
next
up
would
be
we.
We
maintain
a
twitter
bot
for
that
very
purpose,
and
I
wanted
to
tag
in
rajula.
A
I
saw
like
some
some
things
I
hadn't
responded
to
forever.
I
got
a
chance
to
want
to
check
the
issues
on
this
project,
bring
it's
bring
the
attention
to
it
for
people
who
are
unfamiliar,
yeah
and
just
gauge
what
next
steps
might
be.
A
So,
for
those
that
don't
come
every
week
to
this,
the
contributor
tweet
spot
is
a
github
action
that
we
have
forked
and
set
up
in
a
way
where,
when
somebody
adds
a
plain
text
file
to
this
repository,
they
can
once
it's
merged.
It
will
automatically
tweet
from
the
kate's
contributor's
twitter
handle.
A
A
A
Very
cool,
congratulations
to
them,
yeah
all
good!
It's
it's
such
a
really
cool
tool,
and
you
know
it's
awesome
that
that
george
is
interested
in
using
it
for
another
project
too,
so
he's
helping
it
along,
but
yeah.
Just
so,
people
know
what
that
pull
request
is
separately.
There
are
a
few
open
issues.
A
I
A
So
yeah
you're
you're
right
that
the
celebration
page,
I
don't
think,
was
set
up
for
it,
but
I
feel
like
there's
other
pages
I've
linked
to
that
didn't
expand.
I
I
will
I'll
set
I'll
test
it
again,
but
chris
what
we're
going
to
say?
Maybe.
D
A
Good,
I
just
didn't,
want
to
leave
you
hanging
there,
this
very
minor.
I
was
wondering
if
you
can
remove
this
generated
by
thing
here,
but
it's
probably
not
worth
keeping
around.
I
A
We
yeah,
I
looked
into
a
github
issue
on
this
sorry
github
action
and
it
there
wasn't
an
action
that
encapsulated
this
quite
as
well
as
I'd
hoped
we're
like
upon
new
object
on
an
rss
feed.
It
opened
support
request,
so
I
I
got
stuck
there.
I
So
the
thing
here
is,
even
though
we
can
flush
the
rss
thing.
We
need
something
to
run
every
day
like
we
need
to
either
pull
the
event
or
like
understand,
there's
a
trigger
when
a
new
post
comes
up.
So
that's
the
deal
here.
We
can
figure
that
out,
probably
if
someone
is
interested,
they
can
take
it
up.
D
A
G
A
It
would
just
be
like
a
trivial
connector
between
tools
and
it's
like
no,
it's
a
way
to
run
kind
of
complex
software
across
repositories,
but
maybe
one
day.
D
So
for
what
it's
worth
I
during
the
trip
x
meeting
this
week,
I
tagged
myself
for
zapier
helper,
so
yeah
that
might
become
something
we
could
use
in
the
future
so,
but
I
do
have
to
run,
though
I
have
a
live
stream
to
go
to
so
good
luck,
everybody
with
the
rest
of
the
meeting
and
I'll
see
you
next
week
see
chris
have
a
good.
A
One
good
all
right
thanks
for
julia
and
appreciate
us
just
checking
in
on
that
every
every
few
cycles
here
to
make
sure
we're
not
make
sure
I'm
getting
answers
to
you
and,
as
opposed
to
you
having
to
hang
out
in
there
on
your
own
good
all
right.
There
are
links
at
the
bottom.
I've
already
done
the
work
of
going
through
them
and
looking
to
see
if
there's
any
new
open
issues,
but
so
I'll
just
open
it
up.
What
else
is
on
people's
minds.
I
I'm
sorry
I
just
joined
late,
but
the
deadline
for
the
survey
is
21st.
I
want
to
understand
what
what,
where
are
we
at
the
number
of
responses.
A
Oh
sure,
of
course,
the
we
are
up
to
119.
A
I
A
Great
great
question:
josh
was
mentioning
that
he
didn't
expect
more
than
150-ish
responses
just
due
to
the
lack
of
controversy
in
the
questionnaire
and
the
overall
pandemic
life.
So
I
think
with
with
us
getting
that
close
to
it.
Maybe
we
can
do
another
push
over
the
weekend,
saying
like
hey
we're
about
to
close
but
and
get
that
last.
You
know
30
40
people
but
yeah.
I
don't
see
a
reason
to
extend
now
that
we've
jumped
into
three
digits.
I
think
if
it
was
below
we
would
have
said.
That's
not
enough.
I
Yeah,
that's
fine
and
I
was
actually
really
happy
to
use
the
bot
for
the
first
time
in
all
the
challenge.
Yeah.
G
I
Last
year
checked,
I
didn't
find
anything
probably
it's
hard
to
look
at
all
the
channels
and
check
the
replies,
but
there
was
one
thing
I
had
to
join
each
channel
manually
at
the
bot
texas
channel.
So
I
had
to
do
that.
A
A
Cool
thanks,
everybody
that
wraps
up
almost
on
time
and
happy
friday.