►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230203
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230203
A
Hello
and
welcome
everyone
to
the
Friday
February
3rd
2023
edition
of
the
contributor
comms
team
meeting
as
usual,
a
reminder
that
we
do
have
a
code
of
conduct
that
we
operate
under.
It
basically
says
to
be
respectful
of
your
fellow
participants
and
speakers
and
generally
be
excellent
to
each
other
and
for
today,
I
have
shared
our
note
stock.
If
you
have
access
to
edit,
please
do
add
yourself
in
if
somebody
wants
to
kind
of
play,
notetaker
and
add
anyone
who
isn't
able
to
add
themselves
I
would
appreciate
it.
I
also
haven't
added
myself.
A
You
are
welcome
to
do
that.
Whoever
wants
to
and
before
we
get
started
today,
I
think
there
are
a
number
of
newer
folks
on
the
call
we
try
to
remember
to
offer
an
opportunity
at
the
beginning
of
the
session
for
anyone,
who's
new
to
say,
hello,
tell
us
a
little
bit
about
who
you
are
and
what
you're
looking
to
get
out
of
being
here
today,
totally
optional.
If
you
would
like
to
unmute
and
say
hello,
you're
welcome
to
do
that.
You're
also
welcome
to
use
the
chat.
A
All
righty,
then,
if
you'd
like
to
say
hello
later
on,
you
are
welcome
to
jump
in
at
any
time
all
right.
Let's
start
off
with
updates
and
big
wins,
and
there
is
one
major
update
in
the
slack.
Thank
goodness.
I
checked
that
as
I
was
getting
things
set
up
here,
Bob.
A
A
We
have
been
kind
of
starting
to
look
into
Mastodon,
but
one
of
the
things
in
the
early
discussions
on
that
was
like
which
server
do
you
get
on
of
course,
so
we
were
kind
of
waiting
to
see
if
the
cncf
would
maybe
create
one
for
their
projects
and
I
haven't
updated.
I
haven't,
haven't
gotten
an
up
to
date
on
the
status
on
that
so
I'll
try
to
check
in
on
that.
C
C
A
C
C
A
A
D
E
You
know
with
the
more
we
use
it
the
more
we
can
refine
it,
because
there
are
things
that
certainly
are
not
completely
adjusted.
So
it's
a
loop
of
improvement,
so
your
feedback
on
the
on
missing
information
Etc,
is
also
a
welcome.
I
think
that
we
have
most
of
the
things
in
the
blogging
guidelines,
but.
C
B
E
C
Kind
of
yeah.
E
Yeah,
but
that
yeah,
but
the
reason
why
I
think
that
I-
that's
not
there
is
because
it's
the
it's
needed,
but
in
general
there
will.
There
will
always
be
quite
a
few
suggestions
in
terms
of
the
revision.
I
never
saw
a
Blog
article,
just
it's
done
in.
E
Will
have
the
kind
of
feedback
that
you
that
you
had
and
it's
not
limited
to
head
data
generally.
It
goes
to
the
text
so
and
amidst
everything
else,
I
think
that's,
that's
something.
That's
not
a
major
problem,
but
you're
right,
maybe
even
linking
to
it.
I
was
thinking
like
linking
to
previous
examples
to
the
markdown
file
of
previous
examples,
even
probably
even
better,
because
people
then
just
was
just
copy
paste
and.
C
Really
helped
me
so
it
was
kind
of
like
it
was
fast
I
I'm
a
little
bit
caught
delayed
because
I
took
some
time
to
work
on
my
comments,
but
it
was
relatively
fast,
so
it
was
I.
Think
we
improved
I
would
say
as
well.
A
Our
Charter
as
a
group
is
to
help
with
Communications,
both
internally
within
the
contributor
community
and
externally,
facing
making
sure
that
the
the
user
Community
the
and
the
external
Community
kind
of
understand
some
of
the
awesome
work
that
contributors
do
so.
We
always
have
this
project
of
creating
Sig
Spotlight
blogs,
where
a
member
of
our
group
interviews
the
Sig
chairs
and
then
writes
a
blog
post.
A
As
you
can
see
in
this
wonderful
example,
oh
by
the
way
we
need
to
update
the
we
actually
have
a
list
of
the
Sig
spotlights
of
the
past
in
our
repo
now.
So
we
probably
need
to
update.
C
C
F
F
Question
do
is
there
like
a
if
there
were
to
be
like
a
podcast
of
like
someone
interviewing
like
the
major
contributors
and
talking
to
them
about
like
what
it
is
that
they
do
and
and
why
it's
important,
is
that,
like
does
that
fall
within
the
purview
of
this
team?.
A
Never
had
something
like
that
in
the
past,
I,
don't
know
any
reason
that
we
wouldn't
I
think
the.
E
Closest
was
perhaps
in
terms
of
some
Spotlight
I.
Remember
that
I
think
it
was
rare
someone
if
you're
not
mistaken,
it
did
make
it
so
something
the
interview.
Instead
of
being
just
a
Blog
article,
was
actually
a
YouTube
video
right.
D
B
A
F
Is
that
something
that,
because
I
know
that,
like
people
like
I'm,
a
huge
podcast
person
like
I
love
like
anything
technical,
especially
if
it's
something
that
like
I'm,
somewhat
familiar
with
and
I,
don't
need
to
like
stare
at
a
screen
in
order
to
like
understand
like
what's
happening?
Technically,
I,
don't
know.
Maybe
we
could
start
that
and
I
would
I
would
like
to
to
lead
that
if
we
have
some
people
who
have
already
kind
of
done
something
like
that
it.
B
F
D
D
A
D
A
F
A
I
bet,
you
probably
have
seen
some
of
his
work
around.
He
was
really
wonderful
at
running
it,
but
moved
on,
and
so
okay.
F
A
Perfect
awesome
and
guess:
yeah
I
think
that's
a
pretty
cool
idea.
We
can
start
floating
the
idea
around
and
if
you
want
to
pursue
it,
we
do
have
the
opportunity
to
request
some
funding
from
the
cncf
for
projects
that
require
it.
F
E
D
E
Content
there
not
not
a
transcription
but
making
people
aware
right.
D
A
F
A
F
I'm
already
in
it
I
just
in.
F
D
A
Bring
that
up
in
future
meetings
as
well,
I
guess
I'll,
add
it
to
the
bottom
of
the
table
granted.
How
often
do
we
get
to
the
bottom
of
the
table
before
we
stop
for
the
day,
I
accidentally
inserted
that
row
above
but
I
think
that's
fine,
I'll,
probably
move
this
at
some
point
and
Trigger.
A
Give
me
yes
for
ideas
like
this.
That
is
probably
the
case
yeah
so
reach
out
to
me
in
Paris,
we'll
discuss
more
and
we'll
discuss
more
on
this
meeting.
If
you
join
next
week,.
A
We
are
within
the
kubernetes
contributor
experience.
Okay,
so
we.
D
A
I
was
just
recording
interviews
for
the
podcast,
while
I
was
at
Cloud
native
security
con
by
the
way
I
was
at
Cloud
native
security
con.
The
last
couple
of
days
I've
been
live.
A
D
A
A
E
A
You
continued
to
use
the
existing
articles
board.
Is
that
what
you
ended
up
doing.
E
E
F
It's
like
a
note-taking
app,
it's
weird
because
it's
like
oh
great
another
note-taking,
app
slash
to-do
list,
but
it's
really
powerful.
It's
more
like
a.
What
it
was
described
to
me
was
a
very
flexible
database
with
a
good
UI.
F
F
In
things
of
like,
oh,
this
is
just
you
know,
words
on
a
page.
You
can
like
create
really
good,
like
connections
and
stuff,
like
that,
all
over
the
place.
E
D
B
E
I
I
I
I
use
that
at
work
for
myself
at
least
it's
good
because
of
the
revision
process,
but
for
this
I
don't
think
it
makes
sense
it's
more
of
an
interactive
kind
of
thing
right
at
the
same
time.
So
it's
fine.
E
No
well
I've
mentioned
to
tools.
One
is
Arc
mode,
which
is
using
Amex,
which
is
also
an
editor
in
terms
of
notes,
more
related
with
notion
in
that
regard,
but
living
inside
emx
for
those
that
use
MX,
which
also
has
marked
on
like
syntax
to
it,
and
it
has
a
lot
of
plugins
calendars
and
stuff
like
that.
So,
but
if
you
live
inside
emx,
it's
great,
if
you
don't
live
inside
Air
Max,
it
could
drive
you
to
start,
but
it
depends
on
your
degree
of
lunacy.
E
I
would
say
that
the
other
one
is
the
directly
committing
stuff
to
the
to
GitHub
using
markdown
I
found
that
it's
actually
useful
when
for
for
for
seeing
diffs
and
stuff
like
that
who
who
added
what,
when
it's
actually
very
useful,
but
not
so
much
when
we
need
something
interactive
like
we
are
doing
here
right
all
at
the
same
time,
editing
I
think
this
is
for
meeting
minutes.
It's
it's
it's
out.
A
The
other
thing
I
added
to
updates
here
was
that
I
was
thinking
about
you
kind
of
you
tweets,
which
I
need
to
get
to
work
on.
I
know
the
contributor
Summit
folks
are
already
working
on
tweets
for
that,
so
we
probably
need
to
get
started.
We
usually
do
we
like
pre-prepare
tweets
about
the
maintainer
track,
so
should
probably
get
started
on
those
and
Federico
has
added
the
board.
E
E
Which
I
could
give
you,
but
no
no,
no
needs
no
need
so
I
think
that
the
the
only
thing
that
I
so
I
I
sort
of
shared
this
last
time.
But
let
me
start
by
the
easy
stuff.
So
one
good
thing
in
this
project
boards
thing
approach
is
that
the
current
version,
the
last
version-
was
more
free
form,
so
you
ended
up
adding
notes
more
than
anything
which
were
unrelated
with
actual
things
that
were
happening
in
the
repository.
This
one
is
much
more
tied
with
the
issues
and
and
and
push
requests
right,
so
it.
A
Was
also
tied
to
some
things,
but
at
the
time
we
were
using
Umbrella
issues
more,
and
so
we
had
to
track
individual
items
through
those
separate
notes
and
then
yeah
the
whole
umbrella
issues
thing.
We
stopped.
E
But
but
I
I
I've
heard
that
people
that
used
the
previous
version
saying
that
this
one
is
much
more
operational
in
in
a
way.
So
if.
A
E
Can
let
me
start
I'm
by
showing
the
two
main
view,
so
this
is
the
kanban
view
which
in
which
this,
so
we
select
one
of
the
fields
as
a
line
right
and
a
column,
and
we
can
move
things
around
there,
but
I
think
it's
interesting
to
if
you,
if
you
go
into
the
block,
PRS
tab,
yes
drop
down,
yep
table.
E
I
think
this
makes
things
even
easier,
because
a
lot
of
the
information
that
you
you
have
here
is
is
automatically
pulled
from
the
from
the
from
the
issue
and
pull
request.
So
I
I
have
manually
added
the
the
stuff.
That's
been
there
for
the
last
last
six
months.
Obviously,
as
we
mentioned
last
time,
there
are
ways
to
automate
this
by
running
a
job
that
looks
into
labels
Etc,
which
is
what
we're
doing
in
the
kubernetes
release
team.
E
So
every
time
that
you
see
that
little
merged
icon
there,
this
actually
links,
and
if
you
click
on,
for
example,
that's
that
first
one
stick
instrumentation.
If
you
click
on
the
actual.
A
D
E
Recent
one
okay,
so
you
can
see
that
the
reviewers
link
Etc
one
thing
that
I've
found
missing
is
that
it
doesn't
really
show
the
person
who
actually
opened
the
push
request,
which
is
I
I,
find
I
found
interesting,
we'll
have.
D
A
E
Exactly
so,
and
then
you
have
the
status
fields,
which
was
added,
so
we
can
add
whatever
fields
we
will
want.
Actually
I
can,
we
can
add
a
a
owner
or
author
column
there
and
which
are
like
GitHub,
usernames
and
manually
say
this
is
from
imram.
This
is
from
whomever
that
information
is
kept
as
metadata
here,
but
it
isn't
just.
E
Present
in
the
in
the
in
the
in
the
source
PR,
so
just
by
changing
things
here.
Does
that
mean
that
you
will
affect
the
actual
PR?
You
can
obviously
also
immediately
this
select
the
The
Columns
that
you
want
to
be
shown.
The
labels
Etc
yeah
there
you
can
add
and
select,
and
you
can
see
that
hidden
Fields
select
labels,
for
example.
E
Thank
you
so
this
these
are
the
labels
of
the
or
source
push
request.
So
we
can
play
with
that
a
little
bit
and
then
you
have
that
status,
one
which
is
the
one.
That's
it's
the
custom
field
with
a
series
of
fixed
values
which,
when
you
click
on
the
when
you
shift
to
table
View.
E
Corresponds
with
this
right,
it's
when
yeah
and
when
you
move
things
from
one
to
the
other,
the
status
is
updated
on
the
list
field.
It's
not
nothing.
Major,
adding
things
is
relatively
straightforward.
You
just
start
typing
in
the
table
view,
for
example,
if
you
select
a
repository,
which
means
that
we
can
add
stuff
that
is
come
going
into
the
contribute
site
repository
into
the
Sig
repository
or
into
the
kubernetes
website
repository
if
needed,
because
we
do
have
situations
in
which
we
don't
have
one
single
repository
with
everything.
E
Gate.Dev
sites
one
and
we
can
add
inside
the
kubernetes
organization,
we
can
add
whatever
pull,
requests
or
issue
that
we
want.
So
you
have
these
drafts
there,
which
actually
they
only
live.
E
These
ones
are
the
ones
that
have
no
existence
outside
of
the
boards
right,
but
you
can
convert
to
issue
okay,
so
if
you
want
you
can
edit
it
and
then
you
can
convert
to
issue
or
not
convert
to
issue
and
leave
it
like
that.
I've
I've
created
this
once
for
the
not
yet
started
stuff
that
has
come
to
mind.
Obviously,
as
I
mentioned
last
time,
one
possibility
of
going
around
the
entire
process
is
basing
this
on
a
more
structured
will
create
an
issue
saying
six.
We
want
to
do
a
Sig
architecture
Spotlight.
E
This
is
an
issue
right
and
then,
when
it's
done,
there's
a
pull
request
with
the
article
which
closes
the
issue
it's
merged
and
automatically
it
gets
done.
Otherwise
we
will
skip
the
issue
entirely
and
just
work
with
the
notes
there
and
the
push
request.
So
everything
is
fine.
Also
in
terms
of
the
status
we
can,
we
can
add
stuff.
E
Like
I,
don't
know
fmd
file
done
waiting
for
review
so,
depending
on
the
scope
that
we
want
to
give
this,
we
we
can't
play
that's
a
bit
I've
just
made
four,
which
for
me
are
like
bare
minimum
right
to
do
in
progress,
ready
for
review
and
then-
and
you
can
see
the
done
one
already
there
in
terms
of
the
seek
instrumentation
and
also
the
all
the
other
ones
that
are.
A
There,
as
the
blogging
lead,
you
have
ownership
to
do
with
it.
As
you
will
one
question
for
you,
we.
E
E
A
E
E
E
That's
essentially
defines
to
why
how
has
a
series
of
fixed
Fields
like
graduation
criteria,
production,
ready,
review,
testing
Etc,
so
any
enhancement
that
wants
to
to
advance
needs
to
have
a
cap
and
there's
a
cap
Reading
Club,
yes,
which
is
part
of
Stig
architecture,
I
attended
a
couple
of
times
and
it's
interesting
because
essentially
it
picks
up
some
caps
and
it's
a
joint
effort
in
in
taking
a
a
reads
which
is
very
useful
for
people
who
never
saw
a
cat
before.
F
Can
give
you
early
access
all
right?
We
know
who
our
first
interview
is
gonna,
be.
E
Now
they
they
choose
caps
from
all
over.
No
there's
no
and
that's
one
of
the
questions
yeah.
What
is
the
the
the
the
the
choice
process?
Etc
so
and
it's
I
think
it's
interesting
because
the
cap
is
such
a
fundamental
part
of
the
kubernetes
release
process
that
it's
interesting
in
a
way
to
make
contributors
aware
of
what
it
is
and
then
discuss
did
I
understand
this
correctly.
What
is
this
aiming
at
going
into
the?
E
Why
is
this
enhancement
actually
even
needed
in
terms
of
kubernetes
I
find
I
found
it
interesting,
so
I've
added
it
there
and
the
rest
are
your
usual
suspects
in
terms
of
the
six
there's.
F
E
Another
one
that
I
want
to
add
yeah
that
that's
there,
the
book
reading
club,
which
is
from
Carlos
Santana
and
that's
another
one
which
I
I
think
it's
interesting
to
to
confirm,
not
specifically,
but
certainly
something
related
with
contributions.
A
I
knew
that
the
book
reading
club
existed,
but
it
never
occurred
to
me
that
we
should
probably
be
doing
things
to
help
promote
these
groups.
So
I'm
excited
that
you're.
Looking
into
these,
we
should
probably
also
try
to
work
with
them
to
like
do
regular,
tweets
or
whatever
tweets
end
up
being
yeah
about
about
their
meetings
and
things
like
that.
A
A
E
E
It
is
I
think
it's
either
was
twice
a
per
month
or
bi-weekly,
or
something
like
that.
I.
D
C
E
That
is
documented
as
well,
but
it's
very
much
related
with
the
cap
Parts,
but
then
the
Sig
leads
decides
if
they
want
there
and
then
people
that
are
part
of
the
release
team
typically
enhancements.
You
know
enhancement
team
go
into
which
one
that
the
real
the
six
set,
that
they
want
to
be
there
and
check
if
they,
if
they
comply
with
the
formal
requirements
which
one
of
them
is
do
they
have
a
cap,
is
the
cap.
D
A
E
Yeah
and
I
don't
know
how
many
people
can
actually
interact
with
it
right
now,
because
I
just
created
very
directly,
but
anyway,
it's
perfectly
possible
to
change
the
settings
in
the
yaml
file
and
and
add
more
editors
and
people
to
change
it.
So
that's
the
next
step
also
see
who
needs
who
needs
and
when
to
do
it
and
when
and
just
try
to
define
a
bit
of
a
I.
A
Am
approach
to
it,
yeah
sounds
like
good
progress
with
that
I
think
we
should
probably
move
into
our
table
since
we
have
20
minutes
left.
Does
that
sound
good
to
folks?
Any
other
new
items
updates
big
wins
that
folks
want
to
go
over
before
we
drive
into
the
table?
A
A
So,
let's
see
if
we
can
quickly
run
through
these,
it's
rather
long,
so
it
can
be
kind
of
challenging.
The
first
item
is
some
work
that
we
were
doing
to
try
to
make
sure
that
we
are
aware
of
GitHub
issues
and
PRS
that
we
should
be
aware
of.
We
had
updated
our
template
to
at
our
team
on
GitHub,
but
we
were
looking
into
more
that
we
could
do
there.
Imran
I
think
you're.
The
only
one
here
who
has
any
stake
in
that
yeah.
C
C
D
A
A
Checking
on
again
some
other
time
next
item
Frederico,
you
wanted
to
make
some
updates
to
the
blogging
process.
It
sounds
like
that'll
kind
of
go
hand
in
hand
as
you're
developing
the
board,
all
right
cool
and
the
board
is
restarted.
Granted.
B
A
A
A
A
I
usually
use
the
color
coding
to
indicate
days
which
they
don't
seem
to
have
maintained
here
or
probably
didn't
know
about.
So
I'll
probably
reorganize
that
a
little
bit
later
anyway,
so
hopefully
in
a
future
meeting,
we'll
talk
more
and
hopefully
in
the
slack,
we'll
talk
more
about
getting
all
that
stuff
to
date.
A
B
A
A
This
is
the
the
portion
of
that
that
is
our
GitHub
team,
so
this
is
what
we're
trying
to
notify
when
there
are
issues
in
PR's
that
should
have
our
attention,
aside
from
the
reviewers
and
approvers
stuff,
that
we've
been
updating
in
the
owner's
files,
so
we've
been
updating
who
has
approver
permissions
on
various
repos
and
who
should
get
pinged
directly
to
review
things.
A
This
is
more
of
like
a.
We
want
folks
to
have
an
FYI
of
this
thing
exists.
D
D
A
C
So
priorities
to
fix
the
zapier
stuff,
so
that's
the
I
think
it's
happier
I
think
we
have
it
in
the
update
somewhere
in
the
last
week.
So
yeah.
A
D
C
Also
good
idea,
so
this
I
desire
to
wait
until
zappy,
Sappy's
stuff
is
finalized.
So
that,
because
was
doing
something
till
last
week
and
I
was
helping
him
with
the
taking
the
old
source
code
and
looking
at
the
features,
what
it
actually
does
and
I
wrote
some
more
user
requirements,
let's
say
or
how
to.
E
C
C
C
D
C
D
C
C
C
C
A
Cool
so
we'll
move
on
past.
That
item
we'll
probably
encounter
the
zapier
thing
later.
If
you
want
to
talk
more
about
it,
update
repo
with
role,
descriptions,
Chris
and
I
did
add
in
the
sub
Project
Lead
one,
and
then
we
were
doing
other
things
and
I.
A
Okay,
we
did
get
that
merged,
so
I
think
we
can
pretty
much
remove
this
one
for
now
and
just
I
think
I
might
put
it
at
the
bottom
of
the
table
as
a
every
now
and
then,
if
we
get
to
that
a
reminder
that
we
should
recheck
what
roles
we
have
in
our
group
and
update
them
as
needed.
D
A
D
C
I
think
this
again,
this
I
mean
even
though
I
mean
I
mean
direct
contribution
from
us
is
little
because
there
has
been
a
PR
which
has
been
deploys,
the
app
so
yeah.
So
if
anyone
within
us
like
newcomers,
can
have
a
look
as
well
within
this
yeah
new
contributor
Workshop
stuff,
so
if
anything
everything
is
clear
to
them,
then
it's
also
a
good
review.
So
main
part
is
like
they
review
them.
Then
you
give
provide
a
feedback,
how
it's
going
so
I
think
from.
A
A
A
A
E
Were
you
saying
no
exactly
so,
because
these
are
ideas
they
are
not.
There
are
plenty
of
more
possibilities:
I
haven't
added.
All
cigs
that
were
not
subject
was
Spotlight,
but
I
I,
I
added
some
just
to
get
the
ball
rolling,
so
I
would
say
that
anyone
wants
to
pick
up
one
of
them
or
another
one,
essentially
the
processes
to
about.
They
cannot
always
talk
to
me
and
we
can
see
how
how
to
proceed,
but
otherwise
it
would
be
like
going
there
creating
a
draft
and
assigning
I.
E
Don't
think
this
will
work
right
now
because
of
the
permissions,
but
talk
with
me
and
it
will
get
done.
Yeah.
F
For
the
well
I'll
talk
to
to
Kaz
and
first
with,
like
with
regard
to
like
podcast
stuff
I,
don't
know
if
we
want
to
like.
D
D
C
A
A
All
right
so
we'll
move
on
from
that.
That
sounds
good.
Next
item
we've
been
just
kind
of
trying
to
keep
an
eye
on
the
migration
from
katakota
to
GitHub
code
spaces.
I
know
that
became
more
urgent
recently,
because
they're
gonna
they
had
like
a
special
instance
for
us
to
keep
the
kubernetes
stuff
up
and
running
in
katakota,
but
they're
gonna
spin
that
down
faster
than
we
thought
they
were
going
to.
So
this
migration
is
continuing
to
occur.
Is
the
last
update
I
have
on
it.
A
Anybody
else
have
newer
stuff
on
katakata
to
GitHub
code
spaces,
no
cool,
so
we'll
just
keep
an
eye
on
that.
We're
trying
to
make
sure
that
we
know
so
that
we
can
update
the
contributor
Community
when
it's
there
next
item
we've
got
nine
minutes,
see
what
we
can
do
the
validate
command.
This
is
prioritized
yeah.
It
already
says
this
is
not
prioritized
right
now.
C
Issue
covering
all
these
issues
and
yeah
then
yeah
this
yeah
redundant
one.
So
we.
A
Definitely
do
need
an
updated
tracking
method
for
our
tasks.
When
we
were
a
small
group
that
was
growing,
it
made
a
lot
of
sense
to
track
them
just
like
in
our
daily
meeting
notes
and
have
them
somewhere
consistent
where
we
could
see
them
every
time.
But
now
we
have
actual
prioritization
of
things.
C
A
F
Can
we,
since
we're
using
the
GitHub
boards
with
that,
be
a
good
place
to
kind
of
quite.
A
B
B
I
would
say
that
although
I
called
it,
the
blogging
one
yeah
I
would
perhaps
even
prefer.
E
If
we
kept
the
status
and
the
rest
of
things
generally,
that
can
be
applicable
to
most
tasks
that
we
do,
because
I
I
do
think
that
it
it's
likely
for
the
amount
of
things
that
we
we
have.
It
doesn't
really
make
sense
to
split
things
into
three
different
project
boards.
If
we
could
have
one,
not
necessarily
with
20
different
specific
Fields,
but
just
with
three
or
four
covering
pretty
much
every
aspect
of
our
work,
I
think
it
would.
B
Be
better
because
I
would
like
to
in
at
a
glimpse,
have.
E
A
look
into
what
the
technical
part
is
doing,
but
they
will
see
the
blogging
Etc
I
think
this
builds
common
knowledge
and
context
in
a
better
way.
A
A
Github
has
been
making
some
improvements
on
their
boards.
We
were
talking
about
so
maybe
it's
time
all
right
back
to
whatever
we
were
doing
before
here
we
are,
there
was
a
Blog
that
debba
asked
us
to
help
push
through
like
a
year
ago,
and
it's
still
open.
D
A
A
Next
item
keep
track
of
Sig
Doc's
blog
sub
project
process
changes.
Anybody
here
from
Sig
Docs,
don't
think
so
today,
right
yeah,
so
sigdox
was
also
updating.
Their
blog
sub
project
process
changes
and
they
were
gonna
base
them
off
of
frederico's,
because
Frederico
is
awesome
at
defining
how
blogs
should
work
like
actually
Rey
usually
joins
us
every
now
and
then
and
he's
part
of
Sig
doc.
So
this
was
kind
of
an
update
with
him.
Federico
did
you
have
something
you
wanted
to
say
no.
E
A
Fair
point:
I
think
that
counts
as
great
though
in
this
case
much
better
than
what
we
had
before
well
I
mean
clearly
the
blog
project
thinks
so
so
they
would
be
the
ones
too
determine
that,
but
anyway,
and
now
we're
getting
into
the
items.
The
bottom
ones
are
kind
of
things
that
are
like
on
hold
indefinitely
I.
Think
mostly,
we
don't
always
have
to
organize
that
way,
but
we
try
to
so
security
comms
guidelines
someday.
A
We
would
like
to
write
a
guide
like
for
our
repo
with
more
strict
security
or
more
strict
guidelines
for
communications
about
security
issues,
so
we
need
to
work
with
Sig
Security
on
that
it
was
an
idea
that
I
threw
by
them
one
point
like
over
a
year
ago
and
they're
like
yeah.
That
sounds
like
a
great
idea:
let's
do
it,
and
here
we
are
it's
not
happen,
but
someday
maybe
it'll
happen
scheduling,
tweets
for
non-contributor
comms
members.
This
is
basically
actually
the
priority
right
now.
A
A
Probably
not
cool
all
right
talked
about
that
a
good
amount
Chris
had
some
notes
about
Administration
tasks
that
he
wanted
to
move.
I
think
he
did
move
that
I'll
check
with
him
on
that.
A
Let
me
write
that
down
before
I
forget
check
with
Chris
Chris
I
shouldn't
do
that
today,
though,
we'll
just
do
it
next
week,
of
course,
has
other
stuff
going
on
today:
contributor
podcast,
love
that
idea,
contributor,
comms,
gold
stars
for
achievements.
This
was
a
pie
in
the
sky
idea
that
maybe
we'll
do
someday
and
let's
deprecate
the
table,
love
it
and
we're
done
two
minutes
early.
A
A
If
not,
then
I'll
go
ahead
and
end.
The
recording
folks
can
hang
out
for
another
minute
or
two
to
just
chat
off
the
Record
if
they
want
to
but
see
y'all
on
YouTube
next
time,
bye.