►
Description
[SIG ContribEx] Contributor Comms Weekly Meeting for 20230616
A
Hello
and
welcome
to
the
Friday
June
16th
edition
of
the
contributor
comms
team
meeting,
how's
it
June.
As
a
reminder,
we
do
operate
under
a
code
of
conduct
which
essentially
says
to
be
respectful
of
your
fellow
speakers
and
attendees
and
generally
be
excellent
to
each
other,
and
why
is
my
desk
doing
that.
A
A
A
I
think
everyone's
been
on
at
least
once
before,
so
hello
and
welcome
back,
if
you
ever
do,
want
to
introduce
yourself
or
reintroduce
yourself
to
the
group
Feel
Free
at
any
time,
all
right,
let's
dive
in
I,
was
doing
other
stuff
before
this
meeting
and
didn't
actually
update
the
notes
before
this
meeting
before
this
meeting.
Does
anyone
have
any
updates
big
wins
that
they
want
to
share
I've
been
out
what
last
week
or
two
weeks
just
one
week,
I
hope?
B
A
A
B
B
A
B
B
C
I
do
have
an
update
for
the
spotlight
Vlog
in
the
six
release,
so
we
created
that
group
with
the
coaches
and
the
leads,
and
the
best
thing
is
that
the
team
is
working
on
the
drafting.
The
questions.
Oh
sorry,
drafting
the
answers
for
the
question
that
I
have
shared,
and
hopefully
I
have
got
this
confirmation
that
I'll
be
receiving
the
answers
from
the
team
by
the
end
of
the
next
week.
A
A
B
E
E
E
A
Thank
you
good
context
to
have
really
I
haven't
reviewed
these
questions
very
thoroughly,
I
think,
there's
probably
stuff
that
we
could
add
them
to,
but
since
I
hopefully
can
focus
a
little
bit
more
now,
I
only
have
one
more
trip
in
June
I'm
hoping
to
get
through
those
and
actually
answer
them
this
week.
So
let's
hold
me
accountable
on
that:
let's
ping
each
other
every
day.
A
A
A
B
Yeah
like
this
is
you
know
the
the
work
for
Enrico
and
Arno,
and
everyone
did
like
that
is
a
good
kind
of
case
study
for
contributor
comms
to
highlight
like
hey
look.
This
is
a
quote
customer
kind
of
thing
coming
to
us
and
asking
for
help
and
here's
how
it
went
and
here's
you
know
the
whole
process
and
boom
out.
It
went
and
you
know
fairly,
smooth
right
versus
like
coming
to
us
last
minute
kind
of
thing.
You
know
I.
B
D
F
A
A
B
A
B
A
B
B
A
D
A
A
A
B
No
there'll
be
another
system
that
needs
like
we'll
need.
Basically,
if
we're
going
to
do
anything
through
GitHub
like
we
need
a
system
that
says
hey
once
this
hits
approved,
zapier
can
get
involved
and
then
put
it
in
buffer
kind
of
thing,
but
there's
a
lot
of
steps
in
between
here
and
there.
So
some.
A
But
if
GitHub
becomes
this
thing
where
maybe
sometimes
someone
will
put
something
on
it
and
we
don't
actually
have
all
the
automation
to
like
make
it
go
out
at
the
time
that
they
wanted
to
go
out
and
stuff
like
that.
So
we're
gonna
have
to
like
keep
a
close
eye
on
that
repo
that
almost
no
one
ever
uses
we're
never
going
to
notice.
And
it's
going
to
be
another
situation
like
the
one
I
just
described,
where
someone
put
something
in
there
and
we're
like.
A
A
B
B
A
B
A
A
A
A
B
B
A
D
D
A
B
D
D
A
A
D
F
Yes,
so
book
reading
club
I've
reached
out
to
Carlos
Santana
for
arranging
things.
I
did
it
yesterday
or
two
days
ago,
so
no
no
updates.
Yet
what
I
asked
was
around
the
the
formats
that
we
want
to
to
use?
Why
am
I
saying
this
because
we've
been
having
these
discussions
around
Twitter
spaces
and
YouTube
and
stuff
like
that,
some
people
that
have
been
contacting
for
interviews
they
seem
to
somewhat
prefer
something
more
live
than
the
Google
Docs.
F
F
So
hopefully
we
should
be
near
completion
soon.
If
not,
maybe
we
can
go
with
the
ones
that
we
have,
because
we
already
have
quite
a
bit
of
content.
Right
I
mean
three:
each
one
of
them
will
like
six
questions.
There's
it's
it's
quite
a
bit
of
content
right,
I
I
would
prefer
to
have
everything
and,
and
then
I
make
a
series,
but
we
can
we
can
analyze
that
that's
when
we,
when
we
have
a
status
template
from
everyone
and
I,
think
that's
it
for
me,.
F
No,
that's
true,
that's
what
I
said.
Actually
that's
it's
verb
is
what
I've
said
to
Carlos
yeah
I
was
thinking
and
that's
that
that's
another
topic,
but
we
could
do
like
this
half
blog
half
events,
kind
of
thing
in
which
we
would
do
a
written
interview,
much
like
when
you
you.
May
you
have
an
interview
with
the
author
of
a
book
right
that
there
are
two
different
things.
One
is
the
written
words.
F
The
other
is
like
using,
for
example,
Twitter
spaces
to
go
after
it
as
a
follow-up
to
the
written
interview
right
so
I
mean
this
is
just
an
idea.
Instead
of
saying
things
as
one
or
the
other
I
think
it
could
be
useful
to
make
one
as
a
natural
natural
follow-up
of
of
the
other.
We
would
have
an
inter
interview
out
there.
F
A
F
Seeing
this
as
a
follow-up,
so
I'm
not
saying
that
pizza
should
only
be
used
by
that,
but
in
terms
of
the
interviews,
I'm
I'm
thinking
of
this,
we
will
do
an
interview
normal
one,
Google,
Docs,
Etc
blog
posts
out
there,
and
when
the
blog
post
was
published,
we
could
arrange
for
a
Twitter
space
live
thing
that
would
be
based
on
the
the
like.
We,
we
have
the
person
a
which
does
X,
and
we
have
this
interview.
If
you're
interested
in
learning
more
join
us
and
we'll
go
through
it,
we
could.
F
So
it's
more
of
an
additional
like
add
something
on
top
of
the
interview,
instead
of
replacing
it
in
this
case,
although
I
can
also
see
it
being
used
when
there's
no
interview
there,
but
when
we
make
an
interview
and
if
people
are
are
up
for
it
and
I've
got
a
couple
of
people
that
have
asked
me
about.
If
we
do
video
interviews,
maybe
this
is
an
an
interesting
approach.
We
would
do
the
we
would
have
the
best
of
both
worlds.
F
D
D
F
A
A
Yeah
we
could
do
both
if
folks
wanted
to
do
it.
It's
just
that
folks
have
to
be
willing
to
do
that,
but
maybe
start
with
the
Twitter
spaces,
but
I
just
wanted
to
mention
that
so
that
someday,
if
someday,
when
we're
doing
all
these
big
spotlights
and
we're
doing
Twitter
spaces
for
each
one
and
we're
like
this
is
easy.
We
could
add
more
on
to
this.
Then
we
can
do
YouTube
too.
E
A
A
F
A
F
A
A
A
D
A
B
I
think
I
was
using
a
few
on
the
track,
but
we
finally
settled
on
this
one,
but
basically
the
update
with
zapier
is
Nigel
thinks
everything
like
at
face:
value,
look
good,
he's,
gonna,
dive,
a
little
deeper,
make
sure
everything's
working
right
and
then
I
think
that'll
be
done,
but
he
said
he
was
going
to
do
it
a
little
later
this
week.
So
I
was
gonna
ping
him
next
week.
B
Into
the
group
one,
so
he
has
access
to
all
the
things
like
I,
don't
have
access
to
the
G
Drive
YouTube
directory,
for
example,
to
make
sure
that
the
zapier
is
actually
doing
the
right
thing
right.
You
know
so
you've
got
to
verify
all
that
basically
or
I
gotta
get
access
somehow,
which
I
don't
know
how
to
do.
A
B
When
you
look
at
the
original
ass
might
be
a
good
opportunity
to
work
on
this,
while
we're
working
on
the
fastly,
comms,
yeah
I
think
this
falls
under
the
case
study
now
more
than
the
like
generate
guidelines.
Kind
of
thing,
like
the
case
study,
will
probably
generate
guidelines
as
an
artifact.
At
this
point,.
B
D
A
C
A
A
F
Yeah
still,
the
readme
file
is
still
not
there
up
there.
Yeah
I
could
put
that
as
my
next
task
cool
yeah
add
info
about.
Yes,
yes,
I'll
I'll
put
that
on
my
radar
I,
it
was
off
I,
didn't
I
I
thought
that
I
had
done
the
what
was
needed
there,
but
there
were
still
some
additional
stuff
that
we
discussed.
That
could
be
useful,
so
I
I'll
be
on
it
cool.
A
B
A
C
A
A
D
D
A
D
A
B
A
F
A
A
A
A
D
A
Cool
all
right,
so
that's
kind
of
it
for
the
in
progress
items.
Let's
talk
about
to
do
items,
there's
a
safe,
Spotlight,
available
recommendation
there.
If
anyone
wanted
one
I,
don't
think
anybody
wants
to
take
on
a
new
item
today.
Do
they
does
anybody
want
to
take
on
a
Sig
Spotlight
that
doesn't
have
one
yet.
A
Doesn't
sound
like
it?
Do
you
ever
want
to
take
on
a
Sig,
Spotlight
and
write
a
blog
post?
You're
always
welcome
just
let
us
know
promote
new
contributor
Workshop
content,
we're
still
waiting
on
the
GitHub
workspaces
thing
comes
guidelines
versus
sensitive
security
topics,
great
idea,
never
gonna
happen
retrospective
on
registry
comms,
honestly
I
think
that's
not
really
gonna
happen
either,
but
that'll
be
a
Chris
thing
and
he's
talking
on
the
phone
notify
columns
team
when
a
new
issue
is
created,
maybe
someday,
we'll
figure
that
out
slackbot
is
still
broken.
A
A
Great
idea,
though,
contributor
Summit
work
should
be
starting
in
the
next
week
or
two
I
know:
FICA
you're
interested
in
working
with
the
contributor
Summit,
so
I'll
make
sure
to
keep
everyone
informed
when
that
starts
update
the
GitHub
team,
that's
something
that
we
still
need
to
do
case.
Study
based
on
the
CDN
article
I'm
gonna,
move
that
to
in
progress
to
say
we're
going
to
do
it.
A
A
A
B
D
B
A
A
A
A
B
A
B
B
A
B
D
A
D
A
B
A
Yeah
because,
like
we
want
to
be
notified
about
issues
that
come
into
the
like
the
whole
Sig,
contribex
slack
or
not
GitHub,
but
we
only
want
to
be
notified
about
some
of
them.
Because,
like
our
issue
process
is
we
have
a
template
within
Sig
contribex
that
folks
can
request
stuff
from
us.
So
we
want
to
know
when
people
use
our
template
basically
to
create
issues,
so
that
makes
it
a
little
bit
tricky.