►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220610
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220610
A
Hello
and
welcome
everyone
to
the
friday
june
10th
edition
of
the
contributor
comms
still
currently
called
upstream
marketing
sub
project
of
the
kubernetes
special
interest
group
for
contributor
experience,
a
reminder
we
do
have
a
code
of
conduct
which
basically
says
to
be
respectful
of
your
fellow
attendees
and
speakers
and
generally
be
excellent
to
each
other
and
to
start
off
today,
we
like
to
open
up
with
an
opportunity
for
any
new
folks
to
introduce
themselves,
and
let
us
know
why
you're
here,
what
you're
interested
in
and
doing
with
us
also,
let
me
put
in
a
link
to
the
notes
if
anyone
has
any
items
that
they
want
to
add
in
to
the
notes
for
us
to
cover,
please
go
ahead
and
do
that
and
add
yourself
as
an
attendee.
A
A
I
also
thought
I
might
post
the
the
team
charter
in
the
chat.
I'm
thinking
lately
that
maybe
it's
a
good
idea
in
case
any
new
folks
are
here
and
want
to
learn
what
our
group
is.
So
we
can
go
to
the
charter
and
find
out
so
I'll
do
that
as
well.
I
could.
C
A
A
D
Yeah
this
is
ray.
I
added
this
for
prince
war,
the
next
six
spotlight
blog
the
interview
with
the
sigdoc's
co-chair,
scheduled
for
next
friday.
D
A
A
Sometimes,
when
you
do
a
recorded
vocal
interview,
we've
had
in
the
past
that
get
kind
of
delayed
just
because
people
can't
take
the
time
to
write
down
everything
that
happened
in
the
recording,
but
then
again
the
other
way
also
has
delays
and
issues,
because
a
lot
of
the
time
people
are
busy,
so
they
don't
fill
out
the
google
doc
and
you
gotta
remind
them
multiple
times,
so
both
ways
have
their
ups
and
downs.
So
whatever
works
for
the
folks
doing
the
spotlight
is
what
it's
all
about
cool.
I'm
excited
that
that's
moving
forward.
D
Yes
did
finish:
reviewing
the
blog
post
for
the
apac
meet
our
contributors,
for
that
is
done
that
wasn't
in
a
hack,
md.
I'm
not
sure
if
it's
a
pull
request
yet,
but.
A
Lovely,
I
know
we
mentioned
that
on
the
contrabex
meeting
as
well.
That
was
in
progress
good
to
hear.
I
know
I
think
we'll
come
across
that
in
our
table
too,
and
I'll
update
it
there
as
well-
and
I
also
wanted
to
mention
frederico-
is
working
on
a
a
sig
spotlight
as
well.
Would
you
like
to
give
an
update
on
that.
E
Yes,
so
I've
I've
targeted
six
storage,
mainly
because
there's
a
lot
of
fixed
storage
caps
in
this
release
cycle
and
I've.
Well,
I
use
I
use
the
google
docs
sync
routes
and
I
think
that
time
next
week
we
will
have
something
up
and
running.
I
I
I
liaison
with
shang
jing,
I
think,
which
is
the
co-share
of
the
of
the
sixth
storage,
and
I
think
I
have
ninety
percent
of
the
questions.
E
They're
already
answered
doing
as
a
async
questions
is
interesting,
but
in
a
certain
way
it's
limiting
because
there's
a
lot
of
stuff
that
that
you
get
in
the
reply.
That
should
promote
the
follow-up
question
as
well.
So
I'm
I'm
on
that
process,
but
they
were
extremely
supportive
and
very
quick
in
in
addressing
it.
E
A
A
And
then
you
share
that
with
the
group
for
review
and
then
once
that's
been
through
like
a
rough
early
round
of
review,
then
we
go
ahead
and
make
the
pr
which
helps
us
to
make
sure
that
the
pr
is
minimal
in
terms
of
the
changes.
A
A
A
I'm
sorry
I
found
it
in
the
notes.
I
need
to
chat
with
the
tarva
too
and
see
if
he's
all
set
up.
Also
another
update
on
that,
which
I
I
think
is
a
nice
thing.
Well,
I
was
helping
frederico
with
explaining
the
the
process
and
the
concept
and
everything
I
also
went
ahead
and
made
a
pr
to
our
repo
with
some
additional
instructions
about
the
sig
spotlight,
blog
post
creation
process.
A
Just
the
usual
notes
that
I
give
to
people
like
you
can
do
vocal
or
async
blog
or
interview,
and
we
recommend
doing
async,
and
we
do
a
round
of
reviews
with
the
markdown
document
before
doing
the
pr
which
we
usually
recommend
with
hackmd
or
google
docs
yeah.
So
those
kinds
of
basic
concepts
we're
putting
into
a
page
in
our
repo
is
the
idea.
If
I
can
get
that
pr
done,
which
I
think
it's
in
a
good
state.
I
just
have
to
actually
deal
with
git,
which
is
fun.
A
B
So
I
don't
know
the
current
says
this,
but
something
that's
currently
up
for
discussion
is
the
moving
of
the
enhancements
freeze
deadline.
Ray
do
you?
Are
you?
Have
you
been
actively
involved
in
that
discussion?.
D
Yeah
nothing's
official,
yet
I
will
let
upstream
marketing
know
if
anything
is
official.
We
have
there's
some
discussions.
There's
an
issue
created
for
this
specific
release
for
the
announcement
deadline
possibly
being
moved.
Then
yeah
I'll
update
the
group
here.
D
B
Yeah,
it's
it's
more
like
just
to
try
and
like
essentially
as
soon
as
it
happens
to
you
to
boost
it
as
as
much
as
possible,
with
both
twitter
and
mass
slack
messaging.
B
I'm
trying
to
get
update
right
now.
It
looks
like
it's
still.
I'm
looking
at
the
issue
doesn't
consensus
on
it,
but
still.
A
B
A
A
Such
as
scheduling
with
large
groups
right
yep,
just
the
way
it
works,
okey-dokey,
so
campaign's
in
progress
open
a
eyes.
A
I
added
the
note
about
maybe
adding
a
charter
link
to
the
calendar,
invite
kind
of
a
cool
idea.
I
like
that.
I
feel
like
a
lot
of
the
time
new
folks
joined
and
they're
like
what
is
this
group?
I
don't
really
know
so.
Maybe
that
could
help
which
we're
happy
to
explain,
of
course,
but
also
maybe
we
could
add
some
useful
information
there.
A
G
Yes,
please
so
I
saw
a
pr
open
in
contributor
pete's
I'll
share
the
link,
but
I'm
not
sure
who
should
I
mean
the
pr
is
currently
looking
for
an
approval.
I
guess
yeah
me
and
chris.
G
G
A
I,
like
that,
you
added
the
it
was
the
tarva
it's
the
time
even
on
today.
No,
but
I
like
that,
he
added
the
good
first
issue
tag.
A
It
looks
like
someone
wanted
to
help
out
interesting,
interesting
note
for
our
group
in
this.
If
we
add
good
first
issue,
we
will
attract
the
attention
of
people
looking
for
good
first
issues
that
should
be
obvious
might
be
a
good
way
to
let
people
know
that
a
lot
of
the
work
we
do
is
is
very
welcoming
for
newcomers.
B
One
thing
I
will
say
like
having
a
lot
of
good
first
issues.
B
A
A
A
It's
a
good
thing
to
keep
in
mind.
We've
mentioned
periodically.
I
think
in
the
contributor
experience
group
how
good
first
issue
is
a
great
tool
for
us
to
use,
but
it's
also
underused
in
the
community,
and
I
feel
like
this
is
a
good
example
for
me
of
that,
like
I
don't
think
about
using
good
first
issue,
a
lot
of
the
time,
a
lot
of
the
time,
the
things
that
we're
doing
are
pretty
quick
and
they
don't
need
a
lot
of
extra
help.
A
A
A
Cool
so
I'll,
look
at
that
yeah
I'll.
Look
at
that
link
later.
I
guess
I
should
put
that
in
the
chat
as
well.
If
anyone
wants
to
look
at
this,
is
that
the
issue
yeah,
that's
the
issue
and
then
there's
a
pr
for
a
new
tweet
or
well
updating,
broken
links.
I
guess
in
this
repo,
isn't
it
yeah
updating
programs
in
this
repo.
A
Cool
look
at
that
later.
I
don't
want
to
spend
too
much
time
on
it
right
now,
so
we'll
head
on
to
the
table
again
feel
free
to
stop
me.
If
you
have
anything
else,
you
want
to
add
hina.
Ahina
is
not
here
again.
I
think
I
was
thinking
last
week
at
the
end
of
our
meeting.
Actually,
the
next
piece
of
the
github
team
thing
that
hina
was
working
on.
It
was
dependent
on
the
first
piece,
but
the
first
piece
is
done.
A
A
A
A
All
right
so
we'll
move
on
to
the
next
item,
the
contributor
tip
tweet.
Sorry,
I
didn't
reach
out
to
you
on
this
this
week.
Frederico
was
there
any
movement
on
this.
A
B
A
Cool
yeah
I'll
check
with
frederico
on
that
later,
so
we
can
move
on,
looks
like
there's
an
open
pr
related
to
it
and
I'll
work
with
him
to
figure
out
exactly
what's
going
on
there
later.
A
If
we
need
any
helpful
thing,
everyone
auto-generating
blog
tweets.
This
is
just
buffer.
We
discussed
that
in
the
contrib
x
meeting
just
need
to
get
that
going
again.
I
wouldn't
guess:
there's
been
any
movement
on
that
since
tuesday
wednesday.
One
of
those
meetings.
A
Thus,
it
kind
of
got
dropped
because
kubecon
so
we're
working
on
picking
that
back
up
and
the
one
after
that
is
one
of
those
gaps
which
is
scheduling
tweets
because
our
github
repo
can't
currently
do
that
so
that'll
be
fixed
when
we
have
buffer
as
well
so
we'll
go
ahead
and
skip
that
item
as
well
avinash.
I
didn't
set
up
a
meeting
with
referral
description.
A
Pr,
sorry
about
that,
is
there
anything
you
want
to
share
in
terms
of
updates
there?
I
know
we
talked
last
week
about
your
concepts
for
the
role
definition,
which
I
think
sound
great.
We
just
need
to
word
it
up
into
a
pr
and
I'm
sorry.
I
didn't
schedule
that
time
with
you,
I'm
actually
working.
G
On
it-
and
you
can
expect
me
sending
you
the
initial
part
by
tomorrow,
I
guess.
A
Okay,
that
works,
so
we
can
work
on
an
async
like
that
works
for
me.
Thank
you.
Avinish
really
appreciate
your
work
on
that
you've
done
a
lot
with
tracking
down
what
this
role
could
look
like
and
should
look
like
and
wording
that
up
into
something
that
we
can
keep
around
and
make
into
a
process,
and
I
really
appreciate
that.
G
Also
to
add
something
on
that
we
are,
we
are
having
a
community
meeting
this
16th,
I
guess
all
right,
so
I
need
to
reach
out
to
laura
asking
for
if
something
some
tweets
are
probably
needed
to
go
out.
Let's
see.
A
Yeah,
that's
actually
a
campaign
in
progress
kind
of,
because
we've
been
supporting
the
community
meetings.
Is
there
anything
that
you
any
action
items
that
you
want
us
to
track
here
for
you
in
terms
of
doing
community
meeting.
A
Welcome
back,
there
was
one
item
with
you,
which
I
skipped
which,
if
you
want
to
give
any
updates
on
the
contributor
tip
tweet.
I
didn't
chat
with
you
about
that
this
week.
No.
E
Yeah,
so
it's
I've
been
monitoring
it
and
it's
still
same
there
are
some.
As
far
as
I'm
able
to
understand
the
situation.
There
are
some
comments
from
josh.
I
think
in
the
initial
submission
by
chris
that
I
think
still
requires
some
resolution
before
they
they
get.
That's
the
brl
before
the
pr
gets
accepted
and,
and
that
is
a
dependency
on
the
actual
tweets.
So
I'm
I'm
essentially
waiting
for
that
in
order
to
use
the
same
tweet,
but
with
an
updated
address.
A
Right
we
were
gonna
move,
chris's
blog
post
on
that
into
the
developer
site
sounds
good.
I
would
ask
chris
about
the
status
on
that,
but
he
has
disappeared
and
he's
just
a
roaring
fire
and
an
aws
logo.
So.
B
E
It
was
me
sorry,
it's
I'm,
I'm
I'm
messing
with
pulse
audio
and
it's
it's
it's
it's
much
more
complex
than
kubernetes,
so
yeah.
A
True,
that's
quite
true.
Yes,
very
true
yeah,
my
partner
has
a
steam
deck.
We've
been
hacking
away
on
that
interesting.
I.
E
A
Thank
you,
avanesh
for
your
work
on
the
events.
Roll
again
can't
say
it
enough,
and
the
next
thing
is
the
feature
blogs.
I
was
supposed
to
work
on
getting
those
tweets
out.
I
have
put
it
on
my
to-do
list
for
today,
because
fridays
are
the
days
when
I
have
actual
time
to
do
things
and
I
didn't
get
it
done
last
week,
so
I
can
do
that
today.
If
anyone
else
wants
to
help
out
you're
also
welcome.
E
A
Future
blogs
of
the
release
yeah
right
right
yeah.
We
have
a
list
somewhere
of
all
the
blogs
that
came
out
as
part
of
the
release,
feature
blogs
and
a
lot
of
them
came
out
around
that
kubecon
time
period.
So
we
kind
of
missed.
D
A
To
catch
up
on
that
right,
I
can
just
do
that.
That'd
be
the
easiest
thing,
so
I
have
that
on
my
to-do
list.
That
means
it
will
happen
today
or
as
soon
as
I
can
get
to
it.
At
least
next
thing
review
repo
look
into
adding
a
description
of
what
roles
mean.
Avinash
is
already
making
great
progress
on
that
with
the
events
role,
which
I
should
reflect
here,
somehow,
oh
yeah,
it
is
reflected
here,
nice,
it's
right
there
and
hina
also
wanted
to
well.
A
F
A
It
is
now
that
time
next,
one
updating,
github
repo.
I
should
also
put
that
on
my
to-do
list
to
actually
go
over
that.
I.
F
B
A
A
Make
the
change
right
so
and
when
we
do
put
in
that
pr
to
make
that
change,
we'll
have
to
review
that
I
might
change
how
long
it
will
take
to
actually
get
the
change
done.
That's.
A
F
F
F
F
A
A
A
Zig
spotlight:
we
already
did
updates
on
that.
So
I'll
move
on
from
that
tarpa
hasn't
joined
us.
Has
he
nope?
So
I
should.
I
will
put
that
on
my
to-do
list
right
now
to
reach
out.
A
A
Katakota
review
frederico.
You
gave
us
some
nice
updates
on
that
last
time.
Avinash
had
also
done
some
work
on
that.
E
I
shared
my
comments,
true
slack
with
arshita
and
and
that's
pretty
much
it.
I
don't
have
any
additional
feedback
for
that.
I
would
say
avinash
if
you
could
share
me,
the
pr
that
you
mentioned
last
time
or
perhaps
even
to
add
it
to
the
table
items
as
a
reference,
because
you
mentioned
that
there
was
a
pr
associated
with
this
and
with
some
discussion
going
on
in
there
and
my
google
foo
was
not
enough
for
me
to
get
there
so.
D
So
I
added
in
notes,
since
the
catacotta
will
be
shut
down
for
public
june
15th
in
the
scenarios
on
catacota.com
kate's
contributors
will
not
be
on
will
not
be,
I
guess,
live
after
june
15th.
I'm.
F
D
Familiar
with
the
with
the
contrabex
scenarios,
but
I
know
that
the
ones
on
thecubenets.io
will
will
survive
past
june
15th
from
era
from
o'reilly.
A
So
if
this,
so
I
guess
this
one
is
going
into
kate's
contributors
or
is
it
set
up
to
go
to
kubernetes.io?
Do
we
know
guessing
it's
in
that
pr
somewhere.
A
H
I
have
a
doubt
like
how
do
we
move
now
like
if
we
get
it
move
to
gates
for
io
itself,
like
we
have
to
get
it
to
kubernetes
class
website
or
like
how
do
we
or
we
make
a
separate
repo
in
under
kubernetes
github
itself?
So
that,
like
what
I
read
from
the
comment
of
some
from
someone
from
corelli,
they
are
creating
a
separate
server
for
communities,
but
I,
which
github
account,
are
there
supporting.
So
that's
that
I
was
confused.
H
Yeah,
yes,
so
if
they
are
allowing
a
particular
organization,
so
any
repo
under
that
organization
would
stay
for
that,
like
you
know
it
would,
it
would
work
so
since
it's
in
communities
dots
like
community
six,
if
they
are
allowing
and
kubernetes
so
we
could
just
get
it
shifted.
D
Oh
yeah,
I
just
actually
the
last
part
answer
my
question:
if,
where
the
current
candy
county
scenarios
are
and
they're
in
the
kubernetes
six,
they
see
it
also
on
the
dock.
Okay,
so
would
have
to
what
would
happen
move
to
kubrick
to
kubernetes
websites.
D
A
H
Also,
there
were
like
I
was
mentioning
in
that
contribution.
There
are
some
end
user
based
category
scenarios
that
require
to
be
preserved
as
well,
but
at
the
moment
we
don't
support
the
maintenance,
and
you
know
everything
we
don't
take
ownership
for
that,
but
if
caterpillar
shuts
down,
if
there
is
a
chance
they
are
supporting
us,
we
could
also
keep
that
because
the
communities
playground
of
orally
is
quite
famous
in
catacora
people
who
use
that
a
lot.
A
Yeah,
that
is
a
good
question
as
well
like
how
does
the
support
of
this
work
going
forward,
because
I
guess
that's
going
to
be
on
us
somewhere.
I
don't
know
who's
managing
this
change.
D
Yeah
the
migration
was
done
by
o'reilly,
but
that's
really
good
question
on.
If
on
how
we
how
we
manage
this
in
the
future.
So
I
have
some
thoughts
on
it
from
the
sigdoc's
perspective,
but
I'm
putting
anything.
I
need
to
spend
more
more
cycles
on
it,
but
I
could
find
out
where,
where
in
k,
webplates
and
the
stars
we're
at.
D
So
they
actually
reach
o'reilly,
actually
reach
out
so
sig
docs.
We
went
into
looking
at
alternatives
to
catacota,
like
with
killer
coda,
play
with
kubernetes
and
and
the
the
creator
played
with
kubernetes
went
on
the
sig
dogs
meeting
as
well
killer,
dot,
sh
and
another
alternative
as
well,
and
then
a
product
manager
from
o'reilly
which
reached
out
about
a
little
bit
over
a
week
ago.
D
Very
very
recent,
so
we
were,
I
still
would
like
to
if
you
know,
when
I
do
have
cycles
to
poc
some
alternatives
and
what
that
what
that
possible
migration
looks
like
and
also,
if
there's
a
cost
to
that
as
well
and
and
also
see
just
in
case,
because
we
are
dependent
on
catacota
now
to
maintain
the
infrared
behind
these
scenarios.
So
that's.
D
F
F
B
D
The
the
creative
killer
coder
reached
out
with
the
migration
doc
also
so,
okay,
we
have
a
doc
and
how
to
migrate
from
catacombs.
E
F
F
A
A
B
That
many
things
that
are
useful,
okay,
good,
mostly
k
website,
makes
sense.
There
is
the
only
thing
that
we
like
us
under
a
contributor
catacota.
We
should
actually
let
and
then
in
k,
test
infra.
B
B
A
A
You
know
all
right,
I'm
gonna
move
on
to
the
next
item,
which
is
annual
report,
which
is
also
a
big
item.
I
had
something
I
was
supposed
to
do
on
this
and
british
here
today.
No,
so
it's
just
me
and
avinash
and
avinash
is
more
likely
to
have
actually
done
things
today
is
the
the
day
of
avinesh.
A
Yeah
so
but.
E
Yeah,
but
no
what
I
am
and
avinash
thank
you
for
the
for
the
reference
and,
very
briefly
what
I
did
was
I
I
I
went
to
the
annual
report
summary
and
instead
of
making
my
emax
org
file
for
my
own
consumption,
I
just
added
it
all
on
the
xmd
file,
oh
lovely.
G
E
And
I
shared
it
in
the
current
c
contract
slack
channel,
with
some
thoughts
on
what
I
thought
could
be
interesting,
tweetable
stuff
from
the
annual
reports,
with
some
examples
of
possible,
tweets
and
and
well
it's
it's
not
ever
and
it's
not
filled
in
in
its
in
entirety.
But
it's
it's
a
structure
with
a
couple
of
ideas
and
that
that
is
what
the
the
the
the
sum
of
what
I
did.
A
D
A
Welcome
to
the
contributor
comms
meeting,
we
are
very,
very
serious
here
anyway,
I
put
the
link
to
frederico's
hackmd
into
the
chat
and
I'll
put
that
into
the
notes
as
well.
E
E
E
It
yes,
so
what
I've
done
was
to
immediately
create
some
tweets
for
those
that
I
thought
were
were
obvious
and
and
and-
and
my
main
doubt
is
if
we
should,
for
example,
in
the
features
in
the
new
features
stuff
like
that
go
into
one
to
one
tweet
by
feature
or
just
say
something
more
general
saying
there
was
a
lot
of
new
enhancements
and
great
improvements
in
the
last
year
check
them
out
all
in
the
annual
report.
E
H
I
feel
for
the
kids
contributors.
We
should
basically
focus
first
on
the
health
wanted
things,
because
that
must
go
out
first
and
then,
basically,
the
announcement
part
and
all
those
things
that
usually
get
tweeted
by
communities.
I
o
twitter,
like
recently,
you
must
have
seen
the
feature
blogs.
All
of
the
features
blog
that
get
released,
get
something
as.
F
H
Yes-
and
we
usually
focus
on
the
upstream
thing,
so
I
I
feel
the
help
wanted
sections
to
go
first
and
as
soon
as
possible,
because
help
is
really
needed,
because
I
see
on
the
review
side,
also
there's
a
lot
of
places
where
we
need
help
right.
That's
very
critical
at
some
part
of
the
project.
We
are
like
lacking
reviews
and
all
those
things.
A
H
And
it
is
the
same
way
you
do
it
like.
Frederico
has
added
that
it's
the
same.
You
have
the
sig
names.
Just
in
the
hell
pointed
section.
There
is
part
of
the
things
if
you
just
put
it
as
to
it.
Under
this
hacking
file
and
get
appear
started,
I
get
I
used
to
start
it
according
to
tweets
by
magic.
E
A
E
That
is,
that
is
actually
the
question
that
I
have
in
the
l
point
and
initiatives.
Do
we
want
the
one-on-one
or
not?
I
I
I.
I
made
a
couple
of
two
tweets
suggestions
in
the
beginning,
which
are
quite
broad
so
that
that
would
cover
everything,
but
if
we
want
to
go
on
one
on
one,
then
yes,
these
are
the
the
ones
that
are
mentioned
in
the
in
the
annual
report.
A
Yep,
so
I
went
ahead
and
went
into
our
campaigns
in
progress
section
of
our
notes
from
today's
meeting,
and
so
you
can
see
there
the
list
per
frederico's
document
of
which
sigs
have
help
wanted
in
the
annual
report
so
which
sigs
we
need
to
tweet
about.
A
H
I
think
last
time
what
we
did
is,
I
have
the
document
the
google
docs,
where
we
just
you
know,
went
on
put.
F
H
Who
was
free
out
of
the
day
could
just
put
up
the
issues,
because
the
issue
thing
is
just:
you
need
to
copy
paste,
the
material
that's
present
in
the
docs
or
the
hack
empty
file.
Now
we
are
creating
so
I'll
try
to
find
that
dock.
I
don't
know
where
that
dock
went,
but
I'll
pause
there
as
a
reference
yeah,
but
it
it
gets
done
very
fast,
like
it
usually
takes
a
week
or
two
to
get
it
done.
A
Sounds
good:
let's
do
something
like
that.
We
only
have
five
minutes
left
in
this
meeting
of
course,
so
we
won't
do
it
right
this
second,
but
we'll.
Let
everyone
know
on
slack
about
that
and
we'll
sync
up
on
it
again
next
week
that
sound
like
a
good
plan,
yeah
cool,
we'll
sync
on
this
next
week,.
A
And
then
the
only
other
two
items
in
our
table,
one
is
ray
working
on
reviewing
the
apac
meet
our
contributors,
blog,
which
he
already
updated
us
on.
Is
there
an
update
on
that
from
someone
else?
Okay,
he
already
updated
us
on
that.
That's
in
updates
and
big
wins.
A
I
guess
that's
done
and
I
can
go
ahead
and
remove
that
line
from
the
table.
I
put
a
thing
on
my
list
to
update
this
table
after
we're
done
with
this
meeting
so
I'll
leave
that
for
a
second
and
then
the
new
slack
channel
creation
thing.
F
A
We
discussed
it
last
time.
I
think
they
must
have
put
the
notes
about
that
into
the
the
notes
of
the
day.
Instead
of
into
the
thing
so.
A
F
A
A
A
H
So
I
have
added
the
talks
in
the
document
as
a
reference.
If
you
want
to
check
in
today's
meeting.
A
Four
different
pr's,
which
talks.
H
It's
it's
like
in
the
under
the
annual
report,
help
wanted
section.
I
wanted
a
reference
talk
for
the
last
time.
A
D
F
Fun
when
that
happens
and
like
having
all
four
of
these
somehow
magically
happen,
all
at
once
never
gonna
happen.
So
we're
gonna
have
some
funky
state
at
some
point
where
things
aren't
working,
but
then
they
will
eventually
kind
of
think.