►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230224
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230224
A
Hello
and
welcome
everyone
to
the
Friday
February
24th
edition
of
the
contributor
comms
sub-project
of
Saint
contribex,
a
reminder
to
everyone.
We
do
operate
under
a
code
of
conduct
which
basically
says
to
be
respectful
of
your
fellow
speakers
and
fellow
attendees
and
generally
be
excellent
to
each
other.
A
So
I've
got
our
note
stock
up
here.
It
should
be
in
the
chat
as
well.
A
If
you
have
any
updates
or
big
wins,
go
ahead
and
add
those
in
I
see
one
item
so
far
we
can
come
back
to
updates
and
big
wins.
So,
first
item
someone
asked:
do
we
have
any
issue
templates?
B
So
basically,
I
asked,
maybe
I'll
add
a
little
bit
more
context
to
it.
So
yes,
I
mean
since
yeah
it's
also
the
task
regarding
zapier
and
so
on.
There
are
so
many
issues
like
stroll
across
all
the
yeah
six
I
closed
couple
of
them,
but
I
just
want
to
write
a
proper
issue.
We
have
some
discussions,
I
added
in
the
comments,
but
I
want
to
properly
write
a
like
a
yeah,
proper
issue.
Having
you
know
what
are
the
things
to
be
done
so
that
it
follows
a
certain
guideline
yeah.
A
Yeah,
let
me
actually
get
signed
into
GitHub
here
and
then
I'll
actually
be
able
to
show
you
basically
in
the
community
repo.
We
I
know
that
we
do
have
an
issue
template
some
of
the
work
that
Hina
was
doing
in
that
first
item
in
our
table
was
updating
the
issue
template
to
make
sure
that
it
notified
us
when
an
issue
was
made
for
us
I'm,
not
sure
exactly
where
those
live,
contributor,
comms
request.
B
Yeah,
actually
so
that's
that's
the
variety
so
I
I
can
yeah.
So
the
request,
a
slack
request.
So
there
are
a
couple
of
like
eight
options:
I
can
choose,
so
that's
what
these
templates
are.
So
what
I
am
really
interested
is,
like
so
I
mean
classical
way.
When
we
do
an
issue
or
like
a
story,
we
have
a
like
acceptance
criteria.
What
needs
to
be
delivered,
and
so
that's
so
detailed
information.
We
like
pack
it
in
a
like
issues
or
such
such
a
kind
of
template.
B
Do
we
have
because
most
of
the
issues
are,
let's
say
a
user
specific.
It's
not
a
very
general
way,
so
just
want
to
know
if
we
have,
if
kubernetes
follows
a
particular
issue,
format
that
it
needs
to
have
this,
and
this-
and
these
are
the
things-
needs
to
be
I.
Don't
know
what
part
of
acceptance
criteria
whatever
way
it
is
and
so
on,
because
I
I
know
the
general
way
of
adding
what
are
the
problems
I
have,
but
this
one
have
in
that
specific
issue.
B
B
B
D
B
E
B
Deliverable,
okay
and
it
needs
to
cover
some
cases
like
like.
Let's
say
we
create
an
issue,
let's
say
the
workflow
is
it's
creating,
so
zapper
should
accept
a
GitHub
issue,
that's
one
one
of
the
thing
and
then
it
should
trigger
once
it
accepts
an
issue.
It
verifies
the
Tweet
length,
that's
another
criteria,
it
should
satisfy
and
so
on
and
so
forth.
Let's
say
what
are
the
things
it
needs
to.
Let's
say
I
mean
classical
with
this
acceptance
criteria:
stuff.
B
What
are
the
things
it
needs
to
go
through
so
that
the
issue
can
be
resolved.
So
there
is
a
concrete
way
of
waiting
the
issue
so
that,
okay,
if
these
fonts
are
accepted,
the
issues
can
be
closed
because
normally
we
write
an
issue.
There
are
so
many
problems
we
write
and
I,
don't
know
which
are
the
real
solution
which
tries
to
solve
so
I
just
want
to
write
exact
points
because
I
I
looked
at
the
old
existing
workflow
existing
mechanism,
where
we
use
that
using
the
Twitter
bot
and
so
on,
I
just.
A
Yep
I
think,
as
you
can
see
from
these
there's,
not
really
anything
in
particular
that
we
put
in
that.
D
B
A
Pretty
much
it
seems
to
be
the
one
in
k
Community
and
are
one
in
the
tweets
repo.
C
B
A
The
the
file
that
defines
yeah
what
the.
C
C
D
D
B
Yeah
exactly
yeah
I
mean
I
I,
don't
know
what
to
say
about
anything
about
automation.
This
is
not
what
I
meant
is
like
whenever
we
create
an
issue
to
work
on
like
we
are
working
on
zappl
solution,
so
I
want
to.
So.
If
you
go
to
the
issue,
there
is
only
one
issue.
So
if
you
just
click
on
that,
maybe
maybe
you'll
have.
C
B
B
A
C
A
The
place
like
we
had
an
issue
for
the
the
Sig
spotlights,
but
the
issue
with
that
is
that
they
stick
around
forever
and.
A
C
B
A
B
A
Yeah
I,
don't
think,
there's
a
whole
lot
of
guidance
on
that.
It
might
be
a
good
idea
to
ask
in
in
Sig
contribex
about.
B
A
F
We
usually
but
I
I
would
be
wary
of
depending
on
templates,
because
templates
are
the
suggestion,
so
anyone
so
when
I
get
the
templates,
often
I
just
feel
the
things
that
I
think
are
applicable
because
otherwise,
generally
templates
can
be
quite
General,
so
I
I
generally
there's
a
lot
of
stuff
that
goes
not
applicable,
not
applicable,
not
applicable.
So
if
you're,
depending
on
a
template
for
having
some
little
automation
there,
you
would
have
so
it's
it's
important
to
to
know
that
it
could
be
that
the
person
using
the
template
deleted
it.
B
A
A
D
F
Yeah
this
is
related
to
this,
but
also
to
other
things.
So
as
a
follow-up
to
our
conversation
on
boards,
I,
I
and-
and
this
is
linked
with
the
idea
of
umbrella
issues
I've-
and
this
is
merely
an
experiment
because
for
State
architecture
specifically,
for
example,
I
know
what
didn't
work
right
so
and
now
I've
I've
contacted
the
leads
and
said
well
I'm,
going
to
open
an
issue
on
this,
so
that
we
could
just
see
if
this
got
any
additional
traction.
So
I
did
open
an
issue
for
it.
F
Although
I
opened
it-
and
this
is
I-
think
it's
an
important
topic
to
discuss.
I
opened
it
on
the
contributor
side
repository.
Maybe
this
so
maybe
even
if
one
uses
umbrella
issues,
I
think
we
wish.
We
should
have
a
joint
decision
on
where
to
open
them,
because
maybe
I
should
have
opened
it
on
the
on
the
contributor
on
the
community
site
or
sorry
repository
or
because
you
actually
can
close
issues
across
repositories
nowadays.
So
this
is
just
I'm
thinking
loud.
F
If
we
end
up
using
issues,
it
could
be
that
we
so
we
will.
We
will
need
to
determine
if
we
want
to
open
every
single
one
of
them
in
our
own
repository
or,
if
some
specifically,
the
ones
that
end
up
with
with
being
published
and
specifically
for
the
blogging
Parts.
Maybe
this
maybe
this
is
specific
for
the
blogging.
Those
are
very
linked
with
the
contributor
side
right.
So
that's
why
I
opened
it
there,
but
just
something
to
bear
in
mind.
C
F
Yeah
right
but
the
issue-
maybe,
for
example,
the
people
on
I
opened
it
at
the
contributor
side.
Maybe
I
will
get
an
angry
email
today
from
someone
saying
that
they
don't
like
that
kind
of
issues
to
which
I
will
reply
with
no
problem
or
not.
So
we
could
have
the
issues
on
our
own
site
for
our
own
tracking
and
then
have
the
PRS
close
them
across
repositories
and.
F
F
C
F
Scenario,
I
close
it
and
I
think
I
did
it
in
order
to
measure
how
helpful
it
is
and
what
problems
currently
without
with
the
current
tools
and
the
current
community
that
we
have
what
advantages
and
disadvantages
it
brings
to
the
table,
I
think
after
one
month
of
this,
maybe
we
will
have
a
better
we'll
be.
We
will
be
at
a
better,
better
place
to
to
answer
some
of
this.
Should
we
put
it
here
or
there?
Is
it
useful?
It
isn't
useful.
So
it's
more
of
an
experiment
than
anything
else.
B
Just
a
question
before
we
move
on
so
just
I
forgot
it
right.
So
we
can.
We
can
I
mean
I.
Myself
can
also
add
the
issues.
I
mean
yeah.
Add
it
to
the
tracking
board
right
yeah.
F
Well,
I
I've
actually
added
a
comment
in
our
slack
Channel
about
that.
I
would
like
you
to
at
least
to
try
or
to
add
it
or
something,
because
I
I'm
I
am
not
sure
on
the
permissions.
F
If
you
can't,
you
should
be,
and
if
you
find
a
problem,
please
tell
me
in
the
channel
and
we
can
work
through
it,
okay,
because
the
idea
is
exactly
that.
This
is
not
to
be
a
bottleneck.
Ideally,
we
would
have
automatical
automatic
visibility
of
stuff
because
we
would
have
some
kind
of
label
that
would
be
specific
to
sick
contracts
comps.
That
would
be
the
ideal
ideal
scenario
close
enough
for
me,
because
I
think
that
sometimes
automation
is
useful
when
you
have
a
lot
of
stuff.
F
But
if
you
you
shouldn't
be
like
this
main
goal,
we
can
use
it
with
a
manual
step,
which
is
we
search
for
it
and
edit
it.
This
allows
to
search
across
repositories
within
the
kubernetes
organization,
so
we
can
in
the
in
the
in
the
project
board.
If
you
go
at
the
current
state
of
it,
it
I've
added
the
sick
architecture
Spotlight,
which
is,
is
living
on
a
different
repository,
and
we
have
things
there
from
from
different
repositories.
C
A
A
I
bet
we
could
find
the
big
the
like
umbrella
issue.
I
was
talking
about
for
the
six
spotlights
yeah,
that's
tracked
in
here
somewhere.
F
F
Obviously,
here
it's
just:
this
is
a
tool
when
you
end
up
either
using
it
or
using
something
else,
depending
on
the
advantages
that
it
brings
to
the
table.
Even
individual
preferences
play
a
role
here,
because
some
people
like
to
have
this
view.
Others
prefer
to
have
something
else,
but
it's
there's
no
there's.
No,
actually
time
lost
in
actually
trying.
So
why
not
right.
A
Yeah
and
as
you
were
mentioning
the.
D
A
F
Yeah
yeah,
it's
a
it's
a
draft,
you
just
end
there
and
you
it
lives
only
within
the
project
board
itself.
It's
like
almost
like
metadata,
although
you
can,
with
a
click,
convert
it
into
an
issue,
but
that's
that's
good
because
it
doesn't
doesn't
limit
us
to
things
that
live
in
GitHub
we
can,
and
if
you
go
into
the
current
stage
of
the
board,
you
will
see
that
a
lot
of
the
the
six
Spotlight
ideas
are
are
not
issues.
F
A
simple
workflow
could
be
actually
I,
don't
think.
That's
the
new
one.
B
A
D
F
Yes,
so
everything
that
you
see
as
a
draft
there
is
lives
is
exists
only
within
the
board,
so
it's
not
tied
to
any
issue.
Although
you
can,
you
can
automatically
create
an
issue
from
it.
So
I
I
can
see
a
workflow
around
having
ideas
which
are
not
even
signed
yet
as
drafts.
Then
someone
moves
forward
and
says:
well,
I
will
do
it.
F
We
could
create
an
issue
out
of
it
automatically
and
assign
that
person
to
it,
and
then
it
would
be
closed
when
whatever
it's
done
is
done
or
you
can
just
keep
the
draft
and
use
it
as
a
a
note
throughout
the
entire
life
cycle,
because
there's
no
actual
benefit
of
creating
anything
more
substantial
in
terms
of
of
an
actual
issue
object
in
GitHub,
that's
the
old
one
again
right,
yeah.
A
A
That
there
are
actually
two
old
boards,
so
there's.
A
F
Realizing
this
is
like
the
Matrix.
We
are
on
the
third
interaction
of
the
of
the
simulation
right,
so
yeah,
but
but
again
we
don't
need
to.
We
I
have
no
expectations
that
this
one
will
work
as
long
as
it
moves
during
the
process.
If
we
can
get
more
work
done
with
it,
just
because
we're
exploring
it
I
think
it
will
it's
fine,
even
if
we
end
up
dropping
it
at
the
end.
F
For
now
you
see
that
the
Sig
architecture,
one
Spotlight
one-
is
actually
an
issue
on
the
contributor
sites,
which
is
there
and
and
and
well,
and
and
that's
it
any
other
work
that
we're
doing
could
be
also
in
here,
obviously
the
status
names
to
do
in
progress
ready
for
review.
We
can
add
stuff
there
or
change
things
that
are
that
exist,
I've
kept
it
as
as
per
our
previous
discussion,
I've
Captain
General.
F
In
order
to
avoid
making
this
a
blogging
only
scope,
because
this
can
the
idea
is
to
use
this
for
other
tasks
as
well
for
everything,
ideally
so
the
more
generic
we
are
with
the
status,
the
more
accommodating
we
are
for
all
purposes.
A
Cool
other
questions
comments
discussion
around
the
tracking
board.
One
of
our
tasks
from
last
time
was
to
for
the
leads
to
outside
of
the
meeting,
go
ahead
and
start
populating
the
board
with
their
items.
So
I
know
that
I
didn't
do
work
on
that.
I
need
to
put
something
in
there.
I
need
to
put
the
coupon
Tweets
in
there,
but
maybe
we
should
try
that
right
now.
Should
we
try
it
live
and
see
what
happens.
Yeah
sure
just
try
adding
in
item,
because
I
don't
think
I
need
an
issue
to
track
that.
A
Okay
chain,
three
tweet
planning
I,
want
to
grab
the
link
for
that.
A
Yeah
so
I've
got
that
draft
there
and
we'll
work
on
that
more
later.
It
should
be
in
progress,
but
it's
not
in
progress.
So
it's
in
the
correct
place.
F
F
And
and
if
there's
any
issue
with
it
just
add,
I
can
create
a
threads
in
the
in
our
slack
Channel,
just
to
tackle
permission
and
stuff
like
that.
A
Yeah
that'd
be
good
so
that
folks
have
a
good
place
to
share
their
issues,
yeah
cool.
So
then
we
should
probably
go
over
stuff
on
the
board.
But
before
we
do
that,
there's
one
more
item
in
new
items:
Avinash
yeah.
D
So
last
week,
or
maybe
before,
coms
team
was
tagged
in
a
thread
where
yeah,
but
they
needed
some
help
with
editing
in
the
blog.
So
it's
like
as
I'm
seeing
it.
This
document
is
for
newbies
and
they
can
you
know
it's
a
good
document,
so
maybe
comps
can
help
with
the
editing
thing
you
have
a
Blog
Federico
can
take
it
or
maybe
anybody
can
take
it.
So
I
just
wanted
to
point
it
out.
A
F
Should
probably
add
it
to
the
board?
I
was
exchanging
devices
because
I
need.
B
A
Yeah
that
you've
probably
seen
yeah
yeah,
so
it
is
in
your
realm
to
delegate
how
we
get
that
editing
done.
If
you
would
like
no
perfect,
okay.
F
Yeah
yeah,
no,
absolutely
so
it's
it's
already
in
in
a
DOC
format.
So
who
is
the
the
author?
Is
I
missed
that
part.
D
F
Perfect,
so
what
what
is-
and
you
have
have
you
already
reviewed
it
or.
F
Okay-
okay,
perfect,
okay,
so
yeah!
First
of
all,
does
anyone
want
to
do
your
wife
finish?
Do
you
want
to
continue
with
the
process,
for
example,
of
reviewing
Etc
because
otherwise
I
well?
For
me,
the
process
is
like
this:
we
will
look
into
it,
make
an
initial
set
of
comments
around
the
the
content
that
we
do
have
over
there.
Then
we
either
pass
it
through
XMD
or
just
to
mark
down
and
and
create
an
issue
with
the
cool
altered.
F
Stuff
I
can
create
the
issue
and
ads
the
author
esque
water,
because
that
counts,
and
this
is
aligned
with
the
stuff
that
we
have
decided
before,
and
then
we
will
get
the
second
round
of
comments
which
is
more
around
them.
F
The
formatting
and
stuff
like
that,
so
I
will
even
before
that
I
think
that's
I
I
will
give
a
heads
up
to
to
Tim
and
others
on
the
on
the
cdocs
review
because
they
generally
want
to
have
their
their
their
review
there
as
well
and
the
sooner
they
they
do
it.
The
better.
D
So
there
is
a
thread
going
on
and
Tim
and
Josh
have
been
in
talk
with
her.
So
I'll
just
tag
you
that.
So
if
you
have
some
comments.
D
Yeah,
so
Josh
has
said
that
it
is
a
good
if
we
can
have
it
as
a
Moc
data
contributor,
blog.
F
That's
sad,
it's
just
following
that
that
that
bullet
list
that
we
made
a
couple
of
weeks
ago
right
so
it's
fine
I,
will
pick
it
up
and
I'll
keep
everyone
informed
in
the
slack
channel
so
that
anyone
can
drop
in
at
any
time
and
review.
Also
Etc.
F
True,
but
that's
why
I
asked
if
someone
has
any
direct
interest
in
it,
because
otherwise
I
feel
like
there
would
be
tattling
people
with
things
that
they
don't
want
to
do,
and
yeah.
F
So
but
thank
you
for
that
I
finished,
I'll,
I'll,
I
I
was
completely
unaware
of
this
and
I
think
this
is
I
need
to
do
to
to
have
a
look.
F
A
Sounds
good
all
right,
so
that's
all
that
we
have
right
now
in
the
notes
for
new
items
and
updates.
Big
wins
granted
Frederico
is
changing
devices,
but
is
there
anything
that
folks
want
to
talk
about
in
the
board
which
we
should
start
shifting
to
instead
of
the
table?
Theoretically,
though,
we
can
still
use
both
it's
whatever
works
for
folks,
that's
what
we're
all
about
here.
A
Cool,
so
in
the
board
we
had
some
six
spotlights
that
are
to
Do's
I
added
the
Tweet
planning.
We've
got
a
couple
of
spotlights
or
Yeah
couple
spotlights
in
progress.
One
of
these
does
have
an
issue
with
it.
The
sync
architecture,
one
it
looks
like
I,
don't
know
that
is
just
yeah.
It
has
an
issue
with
it
and
if
you
click
it,
it
brings
it
up
very
cool.
A
So
Frederico
was
mentioning
this
one.
It's
a
signed.
Labels
cannot
be
as
supported
app
because
it's
in
contributor
site
cool.
So
this
is
what
Frederico
was
talking
about.
He
opened
this
issue
in
the
contributor
site
to
track
that
one
issue
and.
A
There
is
also
this
draft
blog
post,
which
we
keep
trying
to
push
on
I.
Think
yes,
so
we
might
as
well
look
at
that
now,
since
it
is
in
here
and
not
just
in
the
table.
A
Updated
two
weeks
ago
that
she
was
gonna
work
on
it
and
I
haven't
seen
anything
since
so
I'm
just
gonna
leave
that
be
for
today
and
Imran
looks
like
you
added
one
on
the
zapier
automation
so
far.
C
A
A
Up
to
the
top,
so
the
first
item
here
automatically
add
a
comment:
tagging
GitHub
coms
team.
Whenever
a
label
is
applied,
this
is
de-prioritized
but
yeah.
Some
more
information
about
issue
templates
and
stuff
in
that
work,
which
has
four
links
on
it
already
so.
D
I
I
would
think
for
that.
I
believe
this.
This
problem
now
doesn't
require
a
template
or
something
like
that,
because
I
think
we
can
solve
this
by
zapper
automation
itself
like
we.
For
now
we
are
thinking
of
doing
something
similar
but
more
advanced
in
case
of
tweet
tweets.
So
we
can
just
have
a
very
basic
check
of
labels
if
it
is
contributor,
comms
and
then
based
on
that,
we
can
ask
the
what
to
tag
the
team
or
something
like
that.
A
Yeah,
we
do
still
need
to
do
that
work
and
also
like
for
our
issue
template
in
the
Community
repo,
like
people
can
theoretically
not
that
they
do.
But
theoretically
people
can
make
requests
of
our
team
there.
A
And
if
someone
did
actually
use
that
workflow,
we
would
want
to
know
about
it,
especially
because
no
one
ever
uses
that
workflow.
So
we
would
probably
miss
it.
So
even
beyond
the
zapier
considerations,
when
there
is
an
issue
that
we
should
know
about
in
GitHub,
we
want
to
keep
thinking
about
making
sure
that
we'll
know
what's
going
on.
But
that
is
a
good
point
that
the
zapier
stuff
will
have
its
own
automation
integrated
with
it,
which
should
reduce
the
need
for
this
to
some
degree.
F
A
Cool,
so,
let's
move
on
in
the
table.
Blogging
process
updates.
We've
already
talked
quite
a
bit
about
restarting
the
kanban
board
anytime
folks
want
to
discuss
that.
Please
bring
it
up.
We've
gotta
talk
about
it
a
lot
in
order
to
make
it
work
like
a
fine
wine.
We
need
to
Mush
the
grapes
and
ferment
them
or
whatever
I,
don't
know
how
to
make
wine
moving
on
updating
the
owner's
files.
This
is
almost
done,
except
for
that
one
that
I
still
need
to
update.
A
It
was
on
my
list
to
do
yesterday
and
I
just
didn't
get
around
to
it,
not
that
it's
particularly
complicated.
It's
the
old
one.
A
It's
not
particularly
complicated
for
me
to
update
the
pr
that
I
have,
but
it
just
takes
mental
effort
to
go
in
there
and
find
it
and
decide
how
I
want
to
recreate
it.
I
just
want
to
I
think
I'm,
probably
just
gonna,
delete
it
and
like
recreate
the
pr,
because
I
don't
feel
like
dealing
with
additional
commits
and
squash,
and
all
of
that,
so
that's
something
I
still
need
to
do,
which
I
don't
need
to
spend
that
much
time
on.
Six.Yaml
needs
a
Upstream
marketing
text,
update
sujay
I.
A
C
A
A
A
A
So
many
little
misspellings
in
here
and
that's
the
one
that
we
cared
about.
A
Another
one
right
there
excellent.
Thank
you
so
much
for
doing
this.
Clearly
it
was
very
needed,
and
that
was
just
two
days
ago
that
nabaroon
mentioned
it
so
probably
good
that
we
waited
this
long.
I'm
gonna,
try,
slapping
and
approve
on
here.
What
what
thing
is
this
in
this
is
in
community.
Do
I
have
permission
to
do
that,
I,
don't
know
we're
gonna
find
out
right
now.
A
Cool
and
that
takes
a
little
bit
for
it
to
pick
up
so
I'm
gonna,
leave
that
and
we'll
come
back
to
it
awesome.
Thank
you,
CJ
for
putting
up
that.
Pr,
like
I,
said
clearly
very
needed
next
item.
Unless
welcome
to
opinion
about
anything.
There
update
Upstream
marketing
contributor
there
I
go
update
the
Upstream
contributor,
comms
GitHub
team
Upstream.
Why
is
that?
Why
do
I
have
that
word?
There
I'm
just
ruining
things
for
myself.
A
Yes,
so
we
still
need
to
update
the
contributor
comms
team.
We
haven't
actually
done
that.
Yet
apologies
about
that,
not
that
we
use
the
GitHub
team
very
much
anyway,
so
I
don't
think
it's
generally
a
big
deal.
The
owner's
files
were
the
bigger
deal
which
we
mostly
have
fixed.
We
still
need
to
fix
it
on
the
contributor
tweets
thing,
which
is
probably
pretty
important
for
you
right
now:
I
guess
you're
still
exploring
the
zapier
stuff,
but
you
will
need
that
imminently.
A
So
I
need
to
make
sure
to
get
that
done
today,
which
I
was
going
to
fix
yesterday,
but
I
will
do
it
today.
Next
item
slack
Bob's
still
broken.
This
is
de-prioritized,
so
we'll
skip
update
repo
with
role
descriptions,
we're
all
good
there
if
folks
want
to
create
a
new
role
or
update
a
role.
Just
let
us
know
anytime,
contributor
sites.
This
is
prioritized
below
zapier,
but
there
is
a
new
contributor
workshop
on
the
contributor
site.
Now
so
that's
exciting.
A
They
said
that
they
didn't
want
it
to
be
promoted
just
yet,
for
some
reason
that
I
don't
remember.
This
was
in
the
Sig
control
X
meeting
we
were
talking
about
it.
B
A
No,
so
we've
stopped
doing
the
new
contributor
workshop
at
in
person
at
kubecons
or.
A
At
kubecons,
because
we
weren't
seeing
very
good.
B
A
A
That
is,
that
is
the
right
one:
okay
good!
So
this
does
exist
now,
but
we're
waiting
for
something
that
I
don't
remember
to
actually
talk
about
it.
So
there
is
not
imminent
work
needed
right
this
second,
but
FYI
that
we
will
need
to
promote
that
soon.
A
D
B
C
A
They
want
to
integrate
GitHub
code
spaces
into
the
curriculum.
Make
sure
that
folks,
who
are
going
through
the
curriculum
can
use
GitHub
code
spaces
to
perform
the
activities
that
are
mentioned
in
it.
A
C
Yeah
so
I
have
an
update
on
that.
I
talked
with
the
cheers
of
switch
networking
and
that
and
there
we
have
two
new
chairs
I
mean
the
new
chairs
are
probably
Shane
and
Michael
and
I
I
am.
C
Is
not
official
yet
but
yeah,
so
okay
I
have
prepared
a
dog
and
will
share
it.
Maybe
today
or
tomorrow,
yeah.
C
A
Probably
has
its
benefits,
cool
and
then
the
cap
reading
club
one
do
you
have
any
updates
on
that
Frederico
if
you're
still
around
he's
offline
right
now
cool,
we
already
talked
through
the
board
and
everything,
though
so
so
I
think
we
should
move
Sig
networking
to
in
progress.
A
C
A
Yeah:
here's
a
limitation
of
the
board,
so
I
moved
that
to
in
progress.
B
A
Think
I
could
do
that.
What
is
your
GitHub
name
sujay.
C
A
Are
the
Caps
important?
No,
oh,
this
is
this
status
or
is
this.
A
Yeah,
maybe
it
is
yeah.
Okay,
I
think
we
did
talk
about
that
you're
right
all
right.
We
need
to
work
on
that.
Do
you
have
your
issue
open
for
that
yet
or
you're
waiting
for
the
other
one
to
go
in
you
don't
have
to
have
them.
The
issues
like
completed
to
file
for
org
membership
I,
don't
think
most.
A
I,
don't
know
that
you
need
to
wait
for
it
to
be
merged,
but.
A
C
A
Soon,
though,
I
wonder
if
I
can
add
that
as
a
note,
though,
on
that
keep
losing
it
if
I
click
on
this
aha.
C
D
You
are
adding
that
is
the
cap
grading
Club
one
assigned
to
someone
is
Frederico
working
on
that.
Yes,.
A
A
Cool,
so
we
I
don't
have
any
notes
about
that
right
now:
added
Sig
networking.
A
To
the
board
cool,
thank
you
so
Jay
for
giving
us
that
opportunity
to
test
out
the
board.
A
E
May
I!
Yes,
please
so
I
have
completed
working
on
the
questions.
Part
of
the
six
CLI
Spotlight
I
just
need
to
I
just
need
to
talk
to
JS
about
that.
A
E
A
Yeah
as
long
as
it's
in
there
that'll
help
us
track
it,
and
you
said
that
was
on
CLI
I.
Don't
see
that
in
here
right
now,
so
it's
in
progress
right.
You
said
you
created
the
the
interviewer.
Did
you
send
the
interview.
E
A
E
Talked
about
it,
I
haven't
decided
that
yet
maybe
I
should
asked
the
chair
about
his
preference.
A
A
A
A
E
E
D
A
A
But
yeah,
so
let's
keep
an
eye
on
that
when
you
feel
comfortable
going
for
org
membership.
If
you
feel
like
you
need
more
PR's,
let
us
know
we'll
find
some
little
things
for
you
to
fix
up.
A
A
There
are
just
let
us
know:
I'm
gonna
quickly
run
through
these
last
ones.
I,
don't
think,
there's
anything
that
needs
major
work,
GitHub
code
spaces.
As
we
said,
we
need
to
keep
an
eye
on
that
for
the
course
content
anyway,
GitHub
tweets
that
is
kind
of
the
main
priority,
but
in
this
happier
sense
this
blog,
we
already
looked
at
that
keep
track
of
sigdoc's
blog
sub
project
process
changes
nothing
in
particular
there
probably
security
comms
guidelines,
maybe
someday
we'll
do
that.
A
A
Funny
Chris
had
some
notes
about
administration
of
the
sub-project
that
he
wanted
to
make
sure
that
we
added
into
the
sub-project
lead
role
or
something
somewhere,
so
those
exist
Mark
wanted
to
look
into
the
idea
of
creating
a
contributor
podcast,
that's
going
to
be
a
slow
burn,
trying
to
figure
out
if
that's
a
good
idea
and
if
so
how
we
would
implement
it.
This
is
a
cool
idea,
but
we'll
probably
never
do
it
realistically,
but
let's
keep
it
in
mind
and
deprecating.
A
A
Of
made
it
through
yeah,
it's
basically
on
time
cool
if
folks
can
stick
around
for
another
minute,
any
last
minute
items
before
I
stop
the
recording.