►
Description
[SIG ContribEx] Weekly Contributor Comms Meeting for 20230922
A
A
This,
what
is
this
I'm
gonna
check
this
thing
from
the
chat?
First.
A
A
All
right
looks
like
that's
good
to
go,
though
it
should
send
soon,
once
the
health
checks
complete,
we'll
keep
an
eye
on
that
and
check
it
again
here
in
a
bit.
Probably
so,
let's
start
with
our
first
item
so
earlier
this
week,
arpit
and
I
meant
to
actually
update
the
social
media.
Lead
handbook.
Imagine
that
yay.
A
Thank
you
very
much.
Our
pit
for
working
with
me
through
that
process
and
arpit
had
several
really
good
ideas
that
I
wanted
to
share
in
the
meeting
that
I
wanted
us
to
discuss.
While
we
were
looking
through
the
social
media
handbook,
one
of
them
was
we
were
talking
about
if
we
should
have
documents
around
a
process
for
how
we
adopt
new
social
media
channels
and
things
like
that
which
is
in
new
items.
So
we
can
talk
about
more
about
that
in
a
minute.
A
But
coming
from
that,
we
were
talking
about
LinkedIn,
since
we're
investigating
that
there's
that
existing
LinkedIn
thing,
but
arpit
pointed
out
that
generally
we're
Kate's
contributors
across
social
media.
So
should
we,
instead
of
using
the
existing
one,
actually
be
creating
a
new
one
with
our
usual
name.
B
B
A
Cool
how's
that
going
by
the
way
did
anyone
ever
respond.
No.
B
A
A
Can
ignore
that
yeah
just
move
forward
with
Kate's
contributors
that
sound
like
the
plan,
yeah
yeah?
Why
not
sure.
C
B
B
D
A
Ago
now,
just
maybe
why
we
need
Docs,
so
I'm
gonna
go
ahead
and
Skip
to
this
top
new
item,
since
it's
related,
so
we
were
looking
through
the
social
media
handbook
and
we
were
talking
about
the
responsibilities
of
a
social
media
lead
and
how
a
social
media
lead
should
probably
theoretically
lead
the
charge
if
we're
gonna,
adopt
something
new
and
like
what
all
would
be
involved
with
that.
How
do
we
test
it?
A
How
do
we
decide
whether
or
not
that's
a
good
platform
for
us
initiate
the
process
to
request
more
funding
in
buffer
if
we're
gonna
need
that
make
sure
that
it
follows
existing
social
media
guidelines
right.
A
So
we
considered
putting
a
bunch
of
stuff
about
that
in
the
handbook,
but
the
handbooks
are
pretty
consistent.
That
they're,
like
here's,
a
brief
overview
of
the
role,
here's
brief
overview
of
the
responsibilities
of
the
role
and
here's
a
brief
overview
of
the
Shadow.
So
there's
no
real
place
there
for
details
on
here's.
How
we
do
a
specific
thing
that
this
role
owns
so
I
think
that
should
be
its
own
separate
dock
I.
B
Agree
with
that
yeah
totally
yeah
the
evaluation
process,
I
think
it's
it's
pretty
simple
right
like
where
are
our
contributors
and
then
you
know,
maybe
we
need
to
just
get
some
stats
from
cncf
to
kind
of
just
prove
that
out
and
be
done
with
it
yeah.
You
know
like
I,.
A
Don't
know,
as
I
started,
to
explore
what
I
would
write
about
it.
I
was
like
there's
a
good
chunk
of
stuff
here
enough
to
necessitate
a
doc
I
think,
and
we
could
also
add
in
like
details
about
buffer
in
there,
because
another
thing
I
did
with
the
social
media
handbook.
While
we
were
going
through,
it
was
remove
all
references
to
the
word
tweet
make
them
all
posts
and
remove
all
references
to
the
contributor
tweets
repo.
A
Cool,
thank
you
very
much
for
that.
So
we'll
move
on
to
the
next
updates.
Big
Win
wins
item,
which
is
also
something
that
our
pit
found
our
pit.
Do
you
want
to
talk
about
it.
E
Yep,
so
basically
what
I
found
when
I
am
writing
some
tweets
in
the
buffer,
like
if
you
wrote
a
tweet
India,
you
make
a
draft
on
it
on
the
buffer
and,
if
you
like,
if
you
want
to
reiterate
it,
it
is
okay.
But
if
you.
D
E
The
draft
you
cannot
actually
draft
the
same
tweet
again
like
buffer.
E
Oh
yeah,
I
am
actually
I
found
it
a
long
time
ago,
so
I
have
for
what
it
is
for
a
week
or
for
24
hours.
B
Like
this
happens
to
me
frequently
when,
like
the
API,
doesn't
fully
disconnect
cleanly
I
feel
like
because
I'll
have
like.
Oh,
this
thing
didn't
go
out,
try
again
and
it
fails.
So
it's
like
wait.
A
minute
and
I
go
look
and
it
actually
went
out.
It
just
didn't,
remove
it
from
the
queue
so
I.
D
A
D
A
A
A
A
Thank
you,
I'm
sure,
we'll
see,
I,
know,
I,
put
the
role
handbook
issue
in
the
board,
so
we'll
see
that
stuff
come
up
when
we
get
to
the
the
board
as
well,
sometimes
I'm
tempted
to
call
the
board
the
table.
A
For
reference
for
anyone
who
missed
that
I
don't
know
if
we
have
anyone
new
enough
to
have
missed
that,
but
we
used
to
have
a
big
table
at
the
top
of
the
dock
that
we
would
use
for
the
same
thing.
We
use
the
board
for
now.
So
that's
pretty
funny
anyways
anyway
and
yeah.
Then
I
have
a
note
to
go
through
Frederico
stuff.
Let's
go
ahead
and
hop
too.
C
F
Us
about
it
and
yeah,
so
it's
this
was
open,
but
now
it's
I.
It's
not
no
longer
a
work
in
progress
in
the
sense
that
I've
already
reviewed,
reviewed
it
so
I'm.
It's
there
just
waiting
for
editorial
comments
by
the
docs
team,
Etc
and
anyone
I've
shared
the
links
in
our
in
our
Channel
as
well,
and
the
tentative
publication
date
is
for
next
Thursday
I
think
so,
if
there's
nothing
that
needs
to
be
done.
That
leads
us
to
extent
past
that
date.
It
will
be.
F
It
will
be
done
on
on
next
Thursday.
So
then
that's
pretty
much
it
for
the
for
the
conformance
pr,
the
first
one.
That's
in
there,
it's
the
no,
it's
not
the
first
one.
It's
the
production,
Readiness,
it's
the
third,
the
fourth
one.
F
This
is
the
issue,
so
I
open
an
issue
for
it.
I've
shared
the
hack,
MD
link
with
the
the
author,
so
he
is
reviewing.
It
told
me
that
he
would
be
reviewing
next
week,
and
this
is
the
immediate
one
in
the
pipeline.
After
them,
the
conformance
one,
and
so
that's
that's
already
on
XMD,
so
it
should
be
the
next
PR
opened,
and
this
is
in
terms
of
blogs,
pretty
much.
It's
the
rest.
F
I
know
that
the
the
third
one
that
will
be
published-
okay,
one
second
I-
had
some
issues
with
my
Google
Drive
being
100,
so
some
people,
just
when
people
were
starting
to
add
stuff
they
they
couldn't,
but.
F
Yeah
yeah,
when
I
open
when
I
open
a
Google
doc,
it
just
300
CPU
usage
and
there
we
go
interesting.
So
it
was
the
enhancement
project.
That's
the
one!
That's
also
done
on
the
on
the
Google
Doc
and
that's
that
one
that
will
go
out.
I
I'm
still
insisting
with
the
other
two
with
the
good
organization
and
the
API
which
are
are
essentially
in
the
same
status
as
they
were
last
week.
The
same
can
be
said
about
the
book
club
one,
but
that's
planned.
F
So
it's
still
one
week
we're
still
one
week
ahead
of
the
revised
scheduled
and
the
kubecon
one,
which
there's
also
no
updates.
F
But
it's
a
lot
of
waiting,
so
it's
like
the
CPU
that
just
context
switches
without
major
problems.
I
think
that
the
Sig
architecture
wants,
fortunately,
are
the
ones
that
now
are
actually
give
me
giving
me
some
work
right.
Reviewing
Etc
the
rest
is,
is
just
pinging
people
and
and
and
hopefully
waiting
that
I
have
some
more
content
to
to
add
yeah.
A
Fussing
reminders
so
much
of
the
work
of
creating
these
blogs
yeah
all
right
sounds
good,
so
nothing
needed
right
this
moment,
but
I
guess
we'll.
F
Yeah,
that's
those
ones
yes
and
blog
wise,
there's,
there's
the
first
one
there
it's
it's
from
nitish,
so
yeah
I
think
it's
it's
pretty
ready
for
publication
as
well.
I
think
there
are
some
review
spending,
but
I
think
nitish
can
can
provide
that
feedback.
F
Which
I
can't
perfectly
relate
I
can
give
the
the
a
quick
update
on
on
this
from
the
perspective
of
being
their
reviewing,
so
the
bulk
of
the
the
of
of
it
is
is
done
there
are.
There
were
a
lot
of
comments
that
were
already
integrated
small
fixes,
we're
talking
about
the
to
the
typical
stuff
that
goes
on
around
this.
This
kind
of
this,
this
kind
of
of
Spotlight
articles.
F
That
being
said,
there
are
a
couple
which
are
still
not
reflected
there
and
while
that
is
the
case,
well,
it's
not
ready
for
publication
and
we
will
have
to
update
the
publication
date
as
well
and
as
and
also
when
this
is
done,
update
the
website,
one,
which
is
I,
mean
the
simplest.
The
simple
thing
there
are
I
would
say
two
to
three
pending
reviews
that
need
to
be
addressed
in
some
way:
either
integrated
or
Alternatives
suggested.
So
that's
the
the
the
point
of
it.
A
Sounds
good,
you
can
also
type
nitish
if
there's
anything
in
particular,
you
want
to
call
out
about
this.
One
looks
like
you
all
are
working
through
it.
Sometimes
that's
how
it
is.
A
Cool
are
there
any
other
blog
updates
that
you
particularly
want
to
be
here
for
Frederica
or
other
updates.
F
F
A
A
Thank
you
very
much.
Frederico
and
the
Tish
all
right.
A
Let's
see
what
else
we've
got,
we
already
talked
about
the
contribbeck
spotlight
blog
update,
which,
let's
check
on
that
again:
Spotlight
blog
for
sick
release,
sick
performance,
contribex.
A
A
All
right,
we
should
archive
the
contributor
tweets
repo.
We
should
we
said
that
we
should
reach
out
to
the
GitHub
folks
about
that
right.
B
C
A
B
A
Cool
appreciate
that
avnish
we'll
check
in
on
that
again
next
week
by
the
way
I've
got
next
week
and
then
the
week
after
I've
got
two
more
of
these
meetings.
I
believe
before
I
am
out
so
I
have
one.
D
B
B
A
A
I
should
probably
not
do
that
anyway.
Questions
comments
and
concerns
about
that
are
welcome,
but
you
should
all
be
fine
and
you've
got
this.
Thank
you.
Frederica
we'll
see
you
around
on
slime
and
next
week.
A
So
in
the
new
items
we
already
went
over
the
top
thing
there,
which
was
creating
social
media
channel
process
stuff.
So
our
pit,
you
and
I
should
work
together
more
on
that
you
should
ping
me
on
slack
now
to
be
like
hey.
We
need
to
work
on
that,
because
everything
from
this
meeting
is
removed
from
my
brain
after
this
meeting
ends.
E
A
A
B
D
B
B
A
Me
too,
it
makes
the
tweets
much
better
as
well.
I
think.
D
A
We'll
see
how
that
works
out
anyway,
it's
underpant,
you
had
an
item
in
here.
Would
you
like
to
talk
about
it.
D
A
Yes,
absolutely
that's
a
good
point.
I,
don't
know
where
we
are
with
the
annual
report
right
now
also
signed
upon
you
sound
like
a
robot,
but
I
can
still
understand
you.
So
it's
not
a
huge
issue.
I
think.
A
Anyway,
yes,
that
is
something
that
we
should
do
every
year,
that
was
always
one
of
our
biggest
requests
from
the
rest
of
the
Sig
kind
of
from
the
rest
of
the
project
is:
please
help
us
get
contributors
to
meet
The,
Help
Wanted
stuff
from
the
annual
report
yeah.
So
does
anyone
know
where
the
annual
report
is
right
now,
Jesus.
B
A
A
All
right-
and
this
was
published
four
months
ago-
I-
don't
know
that
we
ever
actually
did
anything
with
that
oops.
A
A
G
A
I'm
glad
that
we
have
folks
from
that
group
in
our
team,
I
don't
think
there
was
any
specific
process
for
this.
Was
there
Sunday
pun
like
there's
not
like
a
sheet
like
we
did
for
kubecon
tweets?
Maybe
we
should
do
something
like
that.
Yeah.
F
G
Think
we
did
once
and
I
remember
when
Deva
Dida
when
he
was
there
here
in
the
group
we
used
to
do
this,
like
he
created
Rasheed.
A
E
A
Okay
Avenue.
She
had
something
to
say.
G
A
Yes,
we
often
integrate
the
contributor
Summit
tweets
into
the
kubecon
tweets
document
like
the
sheet
that
we
use
here.
A
So
we
wanted
to
check
with
you
if
you
wanted
to
do
things
that
way,
if
there
are
any
specific
contributor,
Summit
tweets
that
you
would
like
to
put
in
here,
Beyond,
what's
already
in
here,
you're-
welcome
to
use
this
DOC.
For
that.
A
Sounds
good
also,
if
you
have
any
volunteers
or
Shadows
working
with
you
on
the
contributor
Summit
comms,
you
might
want
to
point
them
to
the
stock
and
ask
them
to
help
out
with
it
by.
D
A
Anyway
sounds
good
also,
while
we're
here
in
the
kubecon
tweets.
Thank
you
very
much
Vishal
for
doing
a
couple
of
tweets.
Already
we
haven't
posted
this
in
Sig,
contourbacks,
yet
or
anywhere
else.
Really
yeah
I
have
to
recognize
people
by
voice
I'm
not
great
at
that,
but
if
we
should
go
ahead
and
start
posting,
this
places.
A
D
A
B
E
B
A
So
I
was
saying:
would
you
DM
me
and
let's
work
out
a
message
to
send
the
Sig
contribex
Channel.
A
The
contributor
the
kubecon
tweets
asking
for
help
writing
the
the
posts
which
is
not
tweets
anymore.
It's
posts,
I,
guess
I-
should
change
the
name
of
this.
A
And
everyone
Help
Wanted,
please
share
with
your
channels
anyone
you
know
who
would
like
to
do
a
little
bit
of
work
in
the
community.
We
would
appreciate
their
contributions
to
the
tweets
if
they
share
their
name
or
handle.
We
will
do
a
tweet
or
post
at
the
beginning
of
the
kubecon
coverage
to
thank
them
for
their
work,
so
be
publicly
recognized.
E
A
So
we
should
probably
come
up
with
a
buffer
post
about
this
as
well
saying
hey,
this
project
is
starting
up.
We
need
some
help.
It's
super
easy
to
contribute
to.
Let
us
know
in
the
contribex.com
slack,
if
you
want
some
help,
if
you
want
to
help.
A
A
Something
along
the
lines
of
the
contributor
comms
team
is
doing
their
biannual
kubecon
posts
project
and
they
could
use
help
writing
posts
about
stuff
happening
at
kubecon.
It's
super
easy
to
get
started
with
ping
Us
in
control,
bikes
comms.
If
you
would
like
to
help
if
it's
in
the
kubernetes
slack
I
think
honestly,
it
would
also
be
okay
to
even
Point
them
directly
to
this
sheet,
because
it's
got
instructions
at
the
front.
A
A
A
Excellent,
so
we
are
through
the
notes:
we've
got
less
than
15
minutes
left,
so
we
should
probably
do
the
board
there's
a
lot
of
stuff
on
the
board
right
now,
anyway,
I
think
we
talked
about
a
good
amount
of
it
anyway,
so
ready
for
review.
We
talked
about
the
Sig
architecture,
ones,
natish.
Was
there
anything
you
wanted
to
add
about
Sig
release,
you
think
Frederico
pretty
much
covered
it.
I
I
think
yeah
Frederico
pretty
much
has
covered
all
the
aspects.
What
I
wanted
to
share
is
that,
like
for
this
week,
the
mid
semester
exams
are
going
on
and
I
did
not
look
at
the
pr
that
has
been
raised.
I
know,
Fredrico
has
suggested
a
lot
of
changes,
but
as
soon
as
I'm
done
with
exams,
which
is
tomorrow
itself
right,
I'll
be
raising
the
changes
very
soon.
B
A
B
C
Yeah,
it's
just
needed.
If
you
want
this
issue
templates,
so
we
decided
that
we'll
be
taking
updates
from
all
the
sigs
or
any
other
updates
across
kubernetes
and
people
can
give
their
updates
to
an
issue.
And
that
is
the
suggestion
that
we
got
so
we
will
be
having
an
issue
template
based
on
which
will
it
will
be
easier
for
them
to
submit
to
us
what
they
want
to
be
updated
for
the
next
weeks
and
wkb
newsletter.
C
B
A
D
B
A
C
C
A
B
A
C
Sounds
good
continuous,
like
like
the
name
of
the
issue
you
can
create
future
and
feature
and
update
for
lwq
videos.
That
sounds
good
to
something
else,
and
that
is
the
description.
A
I
think
that
makes
sense
you
could
also
do
feature
and
update
in
lwkd
I
think
either
way
works.
Though
yeah
we
only
have
nine
minutes
left.
C
Yeah
I'll
just
think,
though,
com
comment
that
gives
you
information.
A
That's
right
so
we'll
move
on
from
this
for
now
and
move
it
to
Slack
all
right
and
the
next
one
is
update.
Social
media
lead
handbook
which
says
that
it's
still
like
a
thing,
but
it's
actually
merged
I,
don't
know
why
it's
not
updated
on
the
board.
B
A
So
I
guess
I'll
delete
my
branch,
which
is
good
nice.
A
A
I
do
love
moving
stuff
on
the
board,
though
it's
pretty
satisfying
all
right.
Eight
minutes
left,
let's
see
if
we
can
get
through
the
in
progress
items.
Stick
architecture
Spotlight
article
any
updates
on
that
I
guess
that's
also
Frederico
actually
never
mind.
We
already
talked
about
those
Sig
testing
Spotlight
article
from
Sunday
punt,
any
updates
there.
A
C
B
A
A
E
So
basically
the
thing
is,
we
are
doing
the
Vlog,
like
from
the
angle
of
said
so
I
am
like
modifying
the
presence
regarding
that
and
also
we
are
filling
up
the
dock
in
the
WG
meetings
of
the
signal
which
the
first
one
is
on
next
Tuesday,
so
yeah.
E
Yep
like
if
I
like
prepare
the
questions
that
are
satisfying
like
I,
will
send
questions
doc
on
the
Channel.
Once
I
am
ready
with
it
to
get
reviewed
like.
D
G
E
A
G
B
E
So
like
we
can
cover
the
whole
signal
generally
also,
and
we
can
also
do
like
the
main
content
of
the
blog
will
be
focused
on
the
side,
and
we
can
also
cover
the
whole
Sig.
Apart
from
that.
A
A
A
I
think
enhancement.
Freeze
is
coming
very
soon
right.
A
So
it'll
be
harder
to
get
stuff
from
sigs
as
that
gets
closer.
So
it's
good
that
a
lot
of
these
are
moving
along
right
now,
but
if
you
encounter
any
issues
where
they
can't
respond
for
a
little
bit,
that
could
be
why
just
so
you
know
foreign.
A
We
already
talked
about
the
Sig
release,
spotlights
well
Spotlight,
the
one
that's
in
progress,
I,
wouldn't
imagine
you
have
any
updates
on
the
other
Sig
release,
Spotlight
right,
natish,.
I
Yeah
correct:
there's,
no
updates,
because
the
people
that
I
would
like
to
reach
out
they're
pretty
much
busy
with
the
VISA
issues
for
the
coupon
and
other
stuff
as
well.
So
no.
A
Updates
for
this
week
much
appreciated
a
tech
lead
Shadow
requirements,
so
Jay
you're
on
today.
At
some
point
you
should
go
over
the
tech
rule
book
and
see
what
you
want
to
update
about
it.
A
And
then
the
ask
that
we've
been
making
to
all
of
the
leads
is
to
also
add
a
section
in
there
saying
explicitly
the
requirements
if
you
want
to
become
a
shadow,
so
Chris
and
I
had
a
meeting
about
it
for
the
sub
Project
Lead.
One
Frederico
did
it
on
his
own
because
he's
a
boss
like
that
yeah.
A
I
mean
our
pit
met
last
week.
To
do
the
social
media
lead
one.
It
might
be
a
good
idea
for
you
to
work
with
one
of
us,
probably
Chris.
We
would
probably
be
better
at
it
yeah,
so
you
might
want
to
try
to
set
up
a
meeting
to
do
those
updates.
B
I'm
happy
to
wake
up
a
little
early
to
meet
with
y'all.
Don't
worry
so
yeah
throughout
some.
D
A
H
Some
question
I
have
some
question
regarding
that,
like
in
the
dock,
you
just
mentioned
that
he
or
she
needs
to
be
familiar
with.
You
will
yeah
I,
think
I
think
we
can
change
that
requirement
a
bit.
D
A
A
Yeah,
that
is
true,
so
I
think
you
should
leave
it
in
as
a
as
a
requirement,
but
you'll
see
in
some
of
the
other
role
handbooks.
If
you
look
like
in
the
social
media
handbook,
I
think
we
have
at
least
one
requirement
that
has
in
brackets
at
the
beginning,
optional
yeah.
It's.
D
B
A
Okay,
thanks
also
as
our
pit
and
I,
and
also
we're
at
time
a
minute
Beyond
time.
So
if
you
have
to
go
no
worries
but
I'll
just
say
one
quick
thing
here,
as
our
pit
and
I
were
going
through,
the
social
media
lead
requirements.
A
I
remember
that
we
had
written
them
in
such
a
way
that
it's
not
limited
to
one
social
media
lead,
there's,
no,
nothing
anywhere
in
our
readme's.
That
says
that
we
have
to
only
have
one
of
each
lead.
A
A
Okay,
yeah
cool,
and
we
are
a
minute
over
time.
I'm
gonna
keep
going
here
for
just
another
couple
of
minutes:
election
comms.
Thank
you
so
much
our
pit
for
all
the
work
that
you've
done
on
that.
We
are
past
the
point
where
you
need
to
do
things
there.
We
have
just
a
few
more
Communications
for
that
remaining
and
they
are
more
sensitive
because
they're,
like
the
results
of
the
election,
so
I'm
planning
to
handle
those
myself.
A
This
was
kind
of
the
first
time
that
we
had
someone
in
the
election
officers
who's
assigned
as
the
comms
lead
and
comms
liaison,
so
I
kind
of,
even
though
I'm.
Obviously,
here
I
tried
to
make
use
of
that
and
had
our
pit
work
on
it
with
me.
So
in
the
future,
that
might
be
a
process
that
we
follow.
I
hope
if
I'm,
not
an
election
officer,
someone
else
will
be
and
someone
else
that
someone
else
will
probably
work
with
our
team
Maybe
to
ask
for
help
with
the
elections
comms.
A
So
thank
you
very
much,
our
pit
for
helping
me
test
out
that
process,
Bob
Sean.
Thank
you
for
joining
and
kubecon
tweets.
We
mostly
went
over
that
again.
Thank
you,
bashal,
as
you're
dropping
off
for
your
work
on
that,
and
we
need
to
share
that
around
share
it
on
your
social
media.
Share
it
on
slack
any
new
folks
to
the
project.
It
can
be
a
great
way
for
them
to
contribute.
So
we
hope
that
more
folks
will
join
in
and
we'll
talk
about
that
more
next
time.
Bye.
A
And
to
do
there's
a
couple
of
spotlights
that
are
available,
let
us
know
if
you
want
to
take
those
on
guidelines,
maybe
we'll
get
to
that
someday
a
new
contributor
Workshop.
Maybe
that
will
get
done
someday
and
notify
comm's
team
when
a
new
issue
is
created
more
for
sujay,
to
look
into
yeah.
A
B
One,
no
one
in
the
project
is
currently
doing
that,
so
there's
no
mechanism
to
really
do
it
and
apps
yeah,
like
there's
not
apps
in
our
kubernetes
slack,
for
various
reasons,
Integrations
with
GitHub
and
zapier,
and
all
these
other
things
that
need
to
happen
might
not
even
be
possible,
but
there's
a
way
to
set
up
apps
without
actually
using
like
the
slack
app
or
the
zapier
app
for
slack
whatever
you
want
to
call
it,
but
yeah.
That's
kind
of
gnarly
and
okay.
B
D
F
A
H
One
thing
can
we
do
it
like
if
we
create
a
app
slack
app
like
the
one
announcement
bottle
or
something.