►
From YouTube: [SIG ContribEx] Weekly Meeting for 20220622
Description
[SIG ContribEx] Weekly Meeting for 20220622
A
Well,
I
can
talk
later
yep,
okay,
hey
everyone!
Welcome
to
the
contributor
experience
bi-weekly
meeting
of
june
22nd.
A
A
A
A
Okay,
so
with
that,
let's
get
started
here,
put
your
name
in
the
attendees.
If
you
haven't
already,
I
think
everybody
has
so
muhammad.
Have
you
dialed
into
one
of
these
before.
A
Okay,
well,
we
don't
need
to
do
interest.
Did
you
do?
Okay
events?
We
don't
necessarily
have
everybody
here
for
the
events,
so,
let's
just
run
through
them
really
quickly
and
office
hours.
Do
we
have
anybody
from
involved
with
office
hours
here
right
now,.
A
Okay,
skip
over
community
meeting.
Laura
is
not
joining
us
right
now,
and
so
I
don't
necessarily
know
what's
going
on
with
july's.
E
A
A
lot
of
folks
are
there
yep,
but
contributor
summit.
D
So,
for
this
we'll
be
ramping
things
back
up
in
july
after
the
holiday,
you
can
expect
a
flurry
of
comms
and
things
like
that,
calling
for
volunteers
and
probably
early
july.
At
this
point,
okay,
I
don't
think
there's
we
don't
have
any
immediate
deadlines
or
anything
like
that
associated
with
it
right
now,.
A
A
Yeah
we
had
a
retro
from
the
eu
meeting
with
some
lessons,
learned,
etc.
A
A
A
The
okay
steering
election
discussed
below
because
it's
more
complicated
than
that
other
events.
A
I
don't
think
it's
really
anything
else.
One
other
thing
is
in-person
kubernetes
community
day
type.
Events
are
starting
to
happen
again.
A
Do
we
want
to
reach
out
to
the
organizers
of
those
events
and
find
out
if
they
need
anything,
contributor-wise
and,
and
the
corollary
to
that
question
would
be
do
we
have
any
anybody
in
the
sig
who
would
be
interested
in
being
in
charge
of
of
that
sort
of
outreach,
because
some
of
these
kcds
in
the
past,
like
the
reason
why
we
have
the
current
portable
version
of
the
new
contributor
workshop,
is
because
they
started
using
it
at
kcds
in
asia?
D
A
Yeah,
the
yep,
so
that's
the
question
is
so.
A
A
Okay,
anything
else
in
our
events.
A
Okay,
mentoring
meet
our
contributors.
I
know
that
the
blog
stuff
has
been
ongoing
because
I've
been
approving
the
blog
posts,
and
these
are
the
mostly
the
blogs
from
asia.
F
Is
the
recent
one
marched
like?
I
think
there
was
a
pr
open
recently
regarding
the
china
blog
post
and
there
was
some
date,
confusion
regarding
a
saturday
release
date
or
something
done.
F
Okay,
I
guess
let
me
just
check
it.
F
Oh
all
right
I'll
reach
out
to
yes
regarding
the
changes
and,
yes,
we
can
see.
E
A
Fix
the
stuff
that
I
can
fix
without
knowing
more
but
there's
stuff
that
I
can't
fix
and
and
the
problem
is
that
we
keep
going
in
the
cycle
where
I
say
this
still
needs
to
be
fixed.
And
then
we.
A
A
A
A
Okay,
the
yeah
one
of
the.
By
the
way,
I
started
a
discussion
in
docs
about
changing
the
process
by
which
we
edit
these
blog
posts,
because
editing
by
github
comment
is
incredibly
inefficient
and
it's
painful
for
both
the
editor
and
the
writer.
A
D
I
know
in
the
past
like
it
depends
on
the
author,
but
we've
like
done
a
first
draft
and
first
round
of
reviews
in
like
hack,
md
or
google
docs
and
then
drop
it
in
there.
A
A
Yeah,
the
okay
yeah,
so
the
the
talk
is
about
officially
switching
to
a
process
where
the
first
stage
of
drafting
is
some
form
of
editable
doc,
such
as
a
google
doc
or
hack
md.
A
Instead
of
moving
straight
to
a
pr
and
that,
in
fact,
we
don't
move
to
a
pr
until
the
blog
post
is
actually
scheduled
to
be
published,
because
one
of
the
other
really
painful
things
about
the
current
process
of.
Oh
we're,
not
publishing
this
on
tuesday.
Can
you
update
the
date.
A
D
E
A
A
A
Okay,
so,
okay,
so
the
the
view
on
actual
video
mock
is
that
if
we
were
to
start
it
up
again,
we
would
want
to
do
something
to
change
the
format
in
an
effort
to
get
in
an
effort
to
make
it
more
interesting
to
potential
contributors,
basically
yeah,
and
in
which
case
my
my
first
thought
not
that
I
have
the
bandwidth
to
organize.
A
Okay,
community
management,
nigel.
E
Yeah
yeah,
so
I
got
creds,
so
I
was
able
to
make
some
progress
so
right
now
doing
it
in
pieces
was
zapier.
I
can
reliably
so
I
made
a
separate
account
on
the
zoom
that
I'm
trying
all
this
out
on,
so
it
won't
affect
anything
that
anybody
else
is
doing.
It's
only
enabled
for
my
my
channel
on
zoom,
but
what
I
have
reliably
working
is
making
a
recording
in
zoom
and
seeing
that
show
up
in
google
drive
now.
E
What
I
haven't
yet
tested
is
like
doing
it
with
naming
and
like
making
a
bunch
of
recordings,
but
I
did
do
one
where
yeah
I
did
do
two
where
they
came
through
just
fine
and
I
want
to
try
as
well.
E
I
know
part
of
the
problem
has
been
if
we
pause
a
recording
two
videos
get
created
and
if
that's
gonna
be
an
issue,
it'd
be
great
to
identify
that
now
we
can
problem
solve
around
it,
but
yeah
for
now
things
are
happening
with
able
to
get
zoomed
to
google
drive
and
then
we'll
do
the
second
piece
after
some
more
testing.
E
Yeah
hope
so
chris
sent
me
this
other
tool
that
I
have
to
check
out
but
yeah.
I
will
report
back
once.
I
evaluate
that
as
well.
A
A
A
I,
however,
something
has
come
up
now,
where
we
might
need
kind
of
a
separate
policy
which
is
academic
surveys,
so
that
is,
surveys
attached
to
an
actual
sort
of
accredited
university
where
there
has
been
some
communication
with
the
community
on
the
content
and
purpose
of
the
survey,
how
we
want
to
treat
those
in
terms
of
policy
like,
for
example,
should
an
accredited
academic
survey
be
allowed
to
advertise
the
survey
on
kubernetes
users,
which
is
an
area
where
we've
banned
commercial
surveys,
mostly
because,
honestly,
the
week
before
we
did
that
fully
one-third
of
the
traffic
on
kubernetes
users
was
commercial
surveys,
so
the
whether
or
not
we
want
to
offer
them
any
kind
of
comms
resources.
A
Whether
or
not
any
other
communication
channel
should
be
available
to
them.
I,
I
would
say
it:
it
takes
a
guarantee
that
they
need
to
meet
certain
minimum
requirements,
things
that
I
call
the
quasi-gdpr
requirements,
which
is
that
the
survey
has
to
have
a
header
announcing
who
is
taking
the
survey.
Why
they're
taking
the
survey
where
and
how
the
data
will
be
handled
and
also
how
to
get
your
data
excluded?
A
D
A
You're
right
so.
A
I
can
see
why
you
would
want
to
answer.
Ask
the
question,
but
I
can't
see
why
anyone
would
want
to
answer
it
the
or
be
able
to
answer
it
for
that
matter.
A
The
and
the
so
so
speaking
of
of
so
my
thought
would
be
that
they're
allowed
to
send
to
kubernetes
users
or
other
appropriate
channels,
depending
on
the
nature
of
the
survey
like.
If
it's
a
survey
on
networking
it
might
go
to
sig
network
if
they
meet
those
requirements.
D
A
D
One
other
thing,
at
least
with
the
surveys
and
determining
comms
and
all
that
is
that
the
blog
sub
project
needs
to
know
that
people
can
open
prs
to
publish
like
to
advertise
their
surveys
and
let
directly
at
least
third-party
ones,
because
that
was
an
issue
last
time
as
well.
D
With
the
original
survey
in
its
pre-revised
form
had
a
blog
post
that
was
to
be
published
on
the
kubernetes
blog
asking.
For
you
know,
people
said
to
you.
A
D
A
D
D
The
yeah,
the
the
big
thing
is
that
the
at
least
the
original
blog
reviewers
did
not
see
an
issue
with
some
of
those
posts.
A
Okay,
so
I
need
to
talk
to
the
blog
post,
about
the
difference
between
project
surveys
and
third-party
stuff.
The
I
mean
my
general
attitude
and
I'll
need
to
talk
to
the
blog
folks
about
this.
Is
we
just
shouldn't
be
publishing
third-party
stuff
on
the
kubernetes
blog
period?
A
If,
if
companies
need
to
publish
it,
that's
what
the
cncf
blog
is
for
and
like
I
said,
I
can
imagine
doing
it
for
a
really
big
survey
right
if
the
university
of
matric
in
combination
with
mit,
wanted
to
do
this
huge
survey
of
open
source
development
et
cetera
that
was
going
to
take
multiple
years
and
involve
you
know,
hundreds
of
recipients
that
I
could
see.
I
know.
A
A
Okay,
does
somebody
else
want
to
carry
that
or
do
I
need
to
carry
that,
because
somebody
needs
to
actually
bring
it
up
on
the
blog
stuff.
A
A
Good
to
know
that
exists
yep
the
it's
the
survey
slack
channel.
Anybody
can
post
any
survey
on
there
at
any
time.
The
kubernetes
project
in
the
header
specifically
makes
no
guarantee
that
the
surveys
are
appropriate
or
even
safe,
nice,
so
the-
and
that
was
the
other
reason
to
take
them
off
of
kubernetes
users,
because
since
our
own
users
did
not
know
the
difference,
they
could
actually
be
entrapped
in
to
answering
some
sort
of
you
know:
spammer
pir
visting
thing
thinking
it
was
coming
from
the
project
so.
A
The
okay,
if
that's
all
anything
else
in
community
management,.
A
Okay,
I
called
that
elections
as
its
own
item
because
planning
some
major
developments
there,
I'm
currently
working
on
launching
the
election
subproject
as
as
discussed
and
approved
several
months
ago.
It's
been
waiting
because
it's
got
a
bunch
of
complicated
moving
parts,
including
upgrading
our
election
software
in
the
same
sort
of
process.
A
I
in
the
meantime,
I
actually
put
out
a
call
in
slack
for
who's
interested
in
participating
in
this,
for
clarity
for
the
soundtrack.
The
difference
here
is
the
election.
Subproject
is
a
separate
but
overlapping
group
with
the
election
officers,
so
the
election
officers
are
three
people
who
are
specifically
appointed
to
run
the
annual
steering
election
and
their
rotates
every
year.
A
The
election
subproject
is
going
to
be
more
in
charge
of
ongoing
election
stuff,
so
making
sure
that
the
documentation
gets
improved
and
updated,
which
it
desperately
needs
right
now,
because
there's
an
awful
lot
of
the
documentation
specifically
about
civs.
Still,
for
example,
I
helping
support
the
election
software
and
our
deployment
of
it
together
with
kate's
infra,
and
one
of
the
other
things
is
now
that
we
have
the
election
software
any
say.
A
Workgroup
team,
whatever
within
kubernetes,
can
actually
launch
their
own
preference
selection
at
any
time,
and
so
we
just
need
to
approve
that
and
help
them
with
the
data
formats.
For
how
do
I
generate
an
election?
A
The
the
oh
and
the
other
thing
is
that
the
new
election
subproject
will
be
recommending
election
officers
for
steering
to
approve
so
taking
away
the
let's
search
for
election
officers
from
whatever
random
steering
member
gets
assigned
to
it
every
year
and
instead
offering
them
a
slate
of
people
that
they
could
approve,
from
speaking
of
which
I
I
don't
know
who
put
dims
in
there.
But
I
am
thrilled
if
dims
is
available.
D
Yep
dims,
because
dims
cannot
run
again.
He
volunteered
to
be
a
steering
a
former
or
you
know,
former
steering
member
on
the
election
committee.
Okay,.
A
A
And
and
honestly,
the
main
job
for
the
election
officers
is
a
lot
of
reminding
people
that
they
need
to
vote
and
fixing
people's
candidate
profiles
because
yaml
formatting,
the
those
are
the
two
big
tasks
honestly
from
a
time
perspective.
A
A
I
don't
see
any
good
reason
why
it
needs
to
have
its
own
repo.
Well,
I
do
see
some
reasons
why
it'd
be
good
for
it
to
have
its
own
repo,
but
they
don't
feel
compelling
because
we
already
basically
have
all
the
documents
in
the
community
repo.
I
can
just
move
them
to
a
new
folder.
A
C
A
Because
it's
still
up,
I'm
gonna
we're
gonna
have
to
take
it
down
as
part
of
moving
stuff
around,
because
I'm
going
to
be
changing
the
folder
structure
for
the
elections
and
I
electo
identifies
which
election
is
which
by
its
file
location.
So
that
needs
to
not
happen
while
it
goes
running.
A
Okay,
the
that's
on
electo's
to-do
list,
but
but
one
of
the
problems
with
get
ops
is
how
else
do
you
identify
things
if
not
by
their
file
location,
the
so
okay?
So
in
that
case,
I'm
currently
working
on
a
pr.
All
of
that
will
be
going
into
an
elections
folder
which
will
be
directly
under
the
root
of
kubernetes
communities.
So
the
parts
of
elections
that
are
under
events
will
be
coming
out
of
there.
A
First
stage
will
be
to
just
move
that
all
under
that
folder
second
stage
will
be
to
extract
the
docs
from
the
individual
annual
election
folders
and
put
them
into
an
election
docs
folder,
which
I'll
do
as
a
separate
pr,
and
so
just
look
out
for
that,
and
then
that
will
have
to
be
coordinated
because
I'll
need
to
work
with
kate's
infra
to
shut
down
the
election.
A
Software,
while
we're
doing
that
moving
around
also
somebody
asked
us
in
slack,
electo
has
been
updated
to
deal
with
the
issue
that
we
had
last
year
around
being
able
to
re
recast
your
ballot,
and
so
that
is
fixed
and,
and
we
enhanced
a
couple
of
other
security
potential
security
problems
identified
by
that
enhance
them.
We
patched
a
couple
of
other
potential
security
problems
identified
by
the
security
team,
very
hopefully
in
the.
B
Okey
dokey,
so
we
didn't
have
our
meeting
last
week
because
I
got
messed
up
by
travel.
Tell
me
so
the
current
things
we
have
in
progress,
though,
are
renaming
of
our
stuff
generally
to
contribute
comms
rather
than
marketing,
which
chris
started
off
this
process.
I
don't
know
who
put
these
questions
in
there.
That
was
chris.
A
Bob
because
I've
got,
I
have
some
pr's
against
contributor
site
to
change
the
references.
Okay,
but
obviously
you
want
those
to
go
in
on
pretty
much
the
same
day
that
the
folders
are
actually
changed
awesome.
B
E
B
In
the
process
of
stepping
away
from
the
group,
so
he
can
focus
on
some
other
priorities
of
his,
so
we're
kind
of
doing
the
handoff,
while
we're
finishing
off
this
like
last
thing
of
this,
so
we'll
have
to
figure
that
out.
So
I
guess
I
should
talk
with
you
josh
as
I
look
over
all
of
that
and
figure.
E
A
Okay,
the
so,
presumably
you
are
also
on
a
recruitment
drive
for
the
coms
team,
yeah.
B
Always
we
have
a
lot
of
really
wonderful
members
who
have
been
coming
for
a
while
now.
So
a
major
part
of
this
is
that
we've
been
working
on
new
role:
definitions
for
the
groups
for
the
group,
so
we're
working
on
figuring
out
what
members
we
have
right
now
and
what
they
want
to
do
and
what
that
ends
up.
B
Looking
like
for
the
team
at
large,
if
that
makes
sense,
so
we're
working
on
making
sure
that
we
have
roles
to
shadow
so
that
people
can
kind
of
move
up
within
the
group
and
take
on
new
responsibilities,
and
things
like
that.
So
chris,
let
us
know
months
ago
that
he
was
planning
on
stepping
away
from
the
group
more
this
year.
B
A
B
We
have
a
new
slack
channel,
which
is
also
something
started
off
by
chris.
That
has
now
finished
up.
We
have
the
slack
channel,
so
you
can
always
find
us
there.
If
you
need
to
message
us,
you
can
use
our
at
or
you
can
message
us
in
the
slack
channel,
which
was
really
helpful.
This
week,
when
I
missed
the
meeting
and
we
were
able
to
sync
up
asynchronously.
B
A
I
my
suggestion
for
for
kind
of
opening
it
to
the
stakes
as
a
way
to
drop
stuff
in
is
just
that.
Historically,
if
somebody
tags,
the
comms
group
in
the
main
contrib
x
channel
and
their
timing
happens
to
be
bad
with
people's
time
zones
and
travel,
they
sometimes.
A
And
and
hopefully,
if
we
can
get
the
team
name
renamed,
we
won't
have
as
much
of
a
problem
with
github
notifications,
yeah.
B
We're
also
working
on
getting.
We
have
a
team
in
github
now
that
can
actually
be
like
addressed
in
issues
we're
also
working
on
updating
the
issue
template
in
the
community
repo.
I
guess
it
is
to
make
sure
that
it
will
actually
alert
the
comms
contributor
commons.
C
A
B
D
B
Next
thing
I
have
on
here
is:
I
also
wanted
to
call
out
that
several
of
our
members
are
working
on
sig,
spotlight,
blog
posts
now
for
a
lot
of
them.
This
is
the
first
time
that
they'll
be
writing
a
blog,
so
they'll
be
going
through
the
process
like
we
discussed
earlier,
where
they'll
do
a
hackmd
or
a
google
doc
first
and
the
contributor
comms
team
will
review
that
before
creating
a
pr.
A
Okay,
yeah,
and
so
my
suggestion
for
the
process
of
that
is
share
the
google
doc
or
hack
md
with
me
and
sf
tim
for
copy
editing
before
you
submit
the
pr.
A
B
I
think
we're
good,
but
I
also
wanted
to
call
out,
since
we
were
mentioning
the
blog
thing.
Rashid
had
a
suggestion
in
the
comments
which
was
basically
what
we
were
saying.
An
author
creates
the
draft
in
google
docs
and.
B
A
Because,
ultimately,
the
one
that
works
best
for
editing
is
that
the
editor
is
actually
the
one
who
submits
the
pr
because
they're
submitting
it
with
the
scheduled
publication
date
and
the
problem
with
that
is.
How
do
we
make
sure
that
the
author
gets
contribution?
Credit
for
it.
A
Okay:
okay,
I'm
gonna
tag
you
rashid
on
this,
except
that,
of
course,
I
don't
know
your
email.
G
Would
so
when,
in
an
interview,
there's
the
the
original
author,
which
is
the
inter
interviewer
in
comms,
but
there's
also
a
someone
that
gets
interviewed
in
my
specific
case.
It
was
in
for
xin
yang
from
six
storage.
Would
it
make
sense
if
to
get
the
interviewee?
G
D
One
thing
just
looking
at
time,
we're
at
like
15
minutes
left.
A
Okay,
so
let's
finish
off
rasheed,
if
you
can
drop
your
email
address
in
the
comments,
I
actually
want
to
tag
you
on
the
co
committer
thing,
because
that's
not
something
that
anybody
in
the
blog
team
knows
how
to
do
and
we
could
use
your
technical
information.
A
The
so
okay
or
or
a
link
to
yourself
in
the
notes.
I
just
wanted
to
assign
you
that
so
that
we
follow
up
with
you
and
how
do
we
do
that?
A
Okay,
so
yeah,
but
you're
right?
We
need
to
outline
the
interviewee
step
also
in
the
the
approval
workflow.
So
okay,
so
we
have
other
things
contributor,
documentation
bob.
Are
there
any
updates.
D
D
D
There
will
be
a
new
section
carved
out
for
it:
okay,
it'll
it'll
be
under
the
contributor
docs
portion
instead
of
like
a
top
level
item,
but
like
yeah
they're,
looking
at
the
various
libraries
and
things
like
that
to
you
sort
of
what
will
give
it
the
best
experience,
especially
as
you
cannot
rely
on
catacota
and
other
things
like
that
anymore.
A
Okay,
which
is
a
shame
because
we
got
this
whole
catacota
repo,
but
the
we
knew
eventually,
when
o'reilly
acquired
them.
They're
gonna
get
a
lot
more
expensive.
The
okay
github
management.
D
We
will
have
a
we
are
like
expanding
our
new
member
coordinators
role
expect
a
call
to
go
out
to
the
various
mailing
lists
to
recruit
new
member
coordinators.
For
that
probably
the
later
this
week
or
early
next
week,.
G
D
A
Yep,
okay,
the
okay
and
then
open
items.
Muhammad.
C
Okay
yeah,
so
I
am
working
on
something
for
six
release.
So
basically
they
have
this
interesting
problem
where
every
release
they
have
a
ton
of
repos
that
need
alias
updates
of
the
for
managing
owners
of
the
folders
and
repositories.
C
So
some
poor
person
goes
every
month
and
every
release
and
makes
a
ton
of
changes
in
a
lot
of
replays
which
they,
which
can
be
automated.
So
I
put
together
something
that
we
use
in
canadian,
where
only
users
are
auto,
updated,
so
yeah,
that's
what
the
pr
does.
I
had
a
number
of
conversations
with
a
lot
of
people
that
were
like.
C
Oh,
this
is
not
something
we
do
automatically,
but
I've
reworked
the
pull
requests
so
that
it's
an
opt-in
feature
and,
more
importantly,
the
repositories
that
we're
going
to
use
all
the
members,
all
the
laces
that
we
care
about
are
going
to
be.
You
know,
teams
anyway,
so
so
bob
looked
at
it.
He
had
some
comments.
I
s
addressed
most
of
them
or
all
of
them.
C
D
And
nikita
and
arnold
also
chimed
in
at
this
point
like
I
only
see
this
being
useful
for
sig
release.
I
do
not
think
it
belongs
in
the
k-org
repo,
like
it,
probably
in
sig
release's
own
tooling,
just
you
know
if
they
want
to
map
and
manage
their
their
sinking
of
things.
That's
fine!
That's
on
them,
but
if
it,
if
it
lives
in
the
chaork
repo,
it
essentially
puts
on
the
github
admins
to
be
the
long-term
maintainers
of
it.
C
D
If
it's,
if
it's
outside
the
the
kr
repo
and
say
like
it,
aligns
with
sick
releases
workflows,
it's
all
good,
it's
it's
just
not
something!
You
know
the
myself
with
other
github
admins
are
comfortable
with
like
living
as
part
of
of
korg.
Just
because,
like
it's,
it's
a
workflow,
that's
printed!
Just
for
that
that
one
sig
and
not
everyone
at
large.
F
D
The
like
99
of
the
repos
do
not
sync
with
github
teams
have
their
own
separate
owners
and
owners
aliases
that
do
not
map
to
any
specific
group.
The
only
place
that
like
I
can
guarantee
owners
are
like
essentially
sig
leads,
is
the
k
enhancements,
repo
and
the
root
of
cake
of
kubernetes
community.
C
All
those
can
be
integrated.
C
D
D
The
like,
where
we
we
copy
the
sig,
leads
list
overs
to
like
k,
enhancements,
okay
and
in
k.
Org
that,
like
there
really
isn't
any
other
place
where
they
are
commonly
duplicated.
C
D
Yes,
sorry,
like
I,
the
I
know
you
you,
you
put
a
lot
of
work
into
doing
this
like
initially
and
all
that,
but
like
anything
that
touches
some
of
these
things
and
we
we
start
have
to
considering
it
for,
like
everyone
and
who's,
going
to
be
like
the
eventually
responsible
for
owning
all
the
code
related
to
that.
That's
where
it's
just
like
not
super
cool
with
it
at
it.
In
the
the
k,
org
repo
yeah.
C
I
get
it
now
so,
like
I
mean
I'm
new
to
the
project,
so
kind
of
learning
talk.
First,
then
start
shipping
things
right
in
other
places,
they're
a
little
bit
more
forgiving
on
shipping
first
and
I'm
talking
later.
D
Know
so
I
apologize.
I
also
didn't
respond
to
you
like
sooner
on
on
that.
Pr,
like
honestly,
like
github
notifications,
are
kind
of
a
tire
fire
for
me.
So
like
it's
it's
hard
for
me
to
to
like
check
back
in
on
on.
C
C
A
Okay,
I
was
going
to
check
on
on
what
we
were
waiting
for
on
the
the
chair
thing.
But
and
apparently
the
answer
is
nothing
because
that
just
merged
and
and
then
over
the
next
couple
weeks,
I'll
be
finding
out
all
of
the
additional
things
that
I
need
to
change.
D
The
actually
need
to
create,
like
an
issue
template
of
the
onboarding
off-boarding
checklist
for
chairs
and
deals
yep.
D
C
A
D
D
I
will
also
ping
people
again
as
a
reminder
to
please
you
know,
plus
one
after
that,
a
steering
member
will
basically
open
up
the
funding
request
for
the
cncf
to
do
it.
Cool.
E
G
Nothing
major
just
one
small
doubt.
Should
I
reshare
my
akmd
six
storage
spotlights
document
in
the
countrybacks
channel,
because
I
think
I
did
it
on
the
contrabax
comms
one.
So
maybe
it's
it's
useful
to
to
share
it
on
the
on
the
other
one.
B
We
should
go
through
a
round
of
reviews
with
the
contrib
xcoms
folks
and
then
okay.
So
let
let
me
first
as
is,
and
then
we
can.
A
A
The
I'll
write
it
up
in
the
repose
workflow
is
that
basically,
except
for
stuff,
that's
specifically
sick
in
tribex
tim,
and
I
are
basically
there
to
be
copy
editors
which,
honestly
most
blog
post
drafts,
need
the
so
that's
kind
of
a
second
stage.
After
the
content
is,
is
done.
Then
we
get
the
punctuation
and
grammar
et
cetera,
correct,
different
formatting.