►
From YouTube: [SIG ContribEx] Weekly Meeting for 20220316
Description
[SIG ContribEx] Weekly Meeting for 20220316
A
Hi
everyone
and
welcome
to
the
thursday
17th
of
march
installment
of
the
sig
contributor
experience
meeting.
I
am
your
host
allison,
you
know
it's
been,
it's
been
a
while,
since
you
know
some
of
y'all
folks
have
been
on
the
call,
I
think
would
be
good
to
do
like
a
round
of
introductions
because
we've
got
some.
We've
got
some
new
faces.
Some
familiar
faces.
A
B
C
D
I
I
do
various
things,
including
sometimes
running
events,
sometimes
mentorship
surveys
particularly
calms
a
few
of
the
things.
Nigel.
Do
you
go
ready.
E
I'm
gone
yet
I
can
go.
My
name
is
nigel.
I'm
a
community
manager
over
at
vmware,
relatively
new
to
a
contributor
experience,
been
helping
out
with
some
youtube
stuff
and
with
hosting
the
last
community
meeting
and
yeah,
looking
forward
to
being
more
helpful
to
contribute
experience
I'll
pass
it
over
to
eric.
F
Howdy,
I
hope
my
audio
is
okay
today,
but
my
name's
eric
I've
been
on
sig
contribex
for
two
years.
I
think
and
have
mostly
been
working
on,
writing
and
updating
the
developer
guide
and
contributor
guide.
So
I
guess
I
will
pass
it
over
to
debobrata.
G
Basically,
I
work
with
marketing
team.
Sometimes
I
read
blog
posts
and
I
have
been
in
contracts
for
last
five
six
months,
so
you
could
find
me
in
the
contracts
with
my
name
and
that's
it
about
me.
I
will
pass
it
to
puja.
I
guess
if
I
name
it,
sorry,
if
I
pronounce
it
wrong.
H
That's:
okay!
It's
it's
weird
german
spelling!
I'm
puya!
I've,
oh
okay,
for
sure,
I'm
not
sure
if
I've
ever
been
official
part
of
counterbacks,
but
I've
organized
or
helped
organize
a
lot
of
contributor
summits,
starting
with
china
and
yeah.
I'm
looking
forward
to
to
being
part
of
this
again
passing
the
ball
to
laura.
I
Hello,
I'm
assuming
we're
on
introduction
time.
My
name
is
laura
santamaria,
I'm
a
developer
advocate
at
palumi
and
I
am
the
person
who
is
coordinating
the
monthly
community
meeting.
So
that's
why
I'm
here
and
I
literally
came
on
now
because
I'm
late,
so
if
you
haven't
gone,
can
you
raise
your
hand
or
like
leave
an
emoji
or
something
so
I
know
who
to
eddie.
Okay,
I'm
told
to
pick
eddie
so
eddie.
It's
your
turn.
J
K
K
K
L
L
I've
been
here
for
around
one
one
and
a
half
years
and
like
it's
nice,
to
attend
one
of
these
meetings.
Again,
it's
been
a
while,
since
I've
been
here
so
excited
to
be
here
again,
you
want
to
go
next.
M
Hello,
everyone
I'm
harshada
from
india,
like
I
have
been
selected
as
lfx
19
like
one
week
ago,
so
hello,
everyone,
it's
my
first
week.
N
My
guess
I
haven't
gone
yet
so
hi
everyone,
I'm
shri,
karan
I've
been
a
part
of
this
community
for
about
eight
months
or
so
now,
and
due
to
a
lot
of
work,
issues
and
stuff,
like
that,
I
dropped
out
of
contributions
for
the
last
month
or
so
so,
yeah
happy
to
be
back
and
happy
to
see
some
familiar
faces.
A
And
with
introductions,
I
forgot
to
say
the
one
line
before
introductions,
which
is
we
abide
by
a
code
of
conduct
which,
in
short
means
it
be
excellent
to
each
other,
and
with
that
I
think
being
mindful
of
time,
especially
you
know,
we'll
start
off
with
contributor
comms.
You
know
with
marketing,
so
yeah
take
us,
take
it
away
castle
and
chris
and
deva
brother.
G
Yeah,
so
basically,
we
had
a
lot
of
comms
update
this
week
with
the
community's
release
cycle
survey
coming
up
like
we
thanks
to
josh
for
changing
it
and
updating
the
survey,
and
then
we
had
accounts
regarding
it.
Also.
G
Last
yesterday
we
had
comms
regarding
the
officers
and
today
I
guess
we
will
be
tweeting
about
the
monthly
community
meeting
that's
happening
tomorrow
and
yes,
the
new
contributors
like
meet
our
contributors,
blog
post
for
the
second
part
focusing
on
australia
and
residential
region,
is
out
now
both
on
k,
dev
and
kids,
dot,
io.
A
Cool
beans
and
any
any
questions
from
anyone
else
on
the
team
for
contributor
comms.
E
Yeah,
so
for
the
blog
for
last
community
meeting,
y'all,
don't
need
that
anymore?
C
E
E
E
I
C
E
Okay,
so
yeah,
if
y'all
want
to
take
a
look-
and
let
me
know
if
I
need
to
add
more
stuff
to
it
or
like
change
stuff.
Let
you
know.
A
All
righty
now
we
will
jump
up
over
to
events
so
office
hours.
Do
we
have
anyone
from
the
office
hours
team
on
the
line?
I
no
no.
H
A
Yeah
david
okay
action
item
here
is
making
sure
that
I
sync
up
with
the
office
hours
team.
I
think
it's
one
thing:
I'm
trying
to
work
on
a
bit.
More
is
syncing
with
each
of
the
individual
groups
like
and
being
like,
hey
yeah,
so
didn't
it
just.
O
C
D
J
I
think
the
time
zone
shifts
messed
people
up
too,
because
we
are
kind
of
light
on
participants.
I
Yep
that's
this
thursday.
I
only
have
one
or
two
topics,
because
I
got
delayed
in
putting
the
call
out
to
ask
for
topics
right
now:
I'm
exploring
using
labels
on
issues
as
a
way
to
flag
topics
during
the
meeting
continuously
we're
we're
looking
into
having
a
little
flag
and
trying
to
encourage
people
to
add
them
to
caps
and
things
like
that.
I
But
this
round
we're
just
really
going
to
be
talking
about
the
reliability
discussion,
the
reliability
bar
discussion
from
last
one,
since
it
was
such
a
popular
topic
and
what
was
the
other
one
josh.
D
Yeah,
so
what
I
have
is-
and
it
was
all
in
the
agenda,
so
we
have
three
things:
one
is
kind
of
a
retrospective
on
it's
been
a
year
since
we
changed
the
release,
cadence.
D
A
second
thing
on
the
fact
that
we
are
moving
from
beta
apis
being
turned
on
by
default.
The
beta
api
is
being
turned
off
by
default
and-
and
I
don't
think,
that's
a
change
that
most
people
are
aware
of,
because
certainly
I
just
noticed
it
when
one
of
the
follow-up
prs
went
in
and
not
when
the
original
pr
went
in.
So
that
seems
worth
discussing,
there's
some
good
reasons
for
it,
but
people
need
to
know
about
it
and
then,
finally,
the
you
know
ongoing
reliability.
D
Discussion,
one
of
the
the
the
minor
items
that
we
have
on
the
agenda
is,
I
wanted
to
update
people
on
the
contributor
summit.
D
Okay,
so
it's
there,
but
one
of
the
things
it's
brought
home
to
me
more
is
that
we
need
a
method
of.
D
We
need
to
be
getting
content
for
the
community
meeting
sort
of
continuously
and
it
needs
to
not
be
dependent
on
whoever
is
going
to
be
the
next
meeting
host,
because
if
we
do
that
we
get
into
the
cycle
where
we're
looking
for
a
next
meeting
host,
we
don't
get
them
until
10
days
out,
which
means
they
don't
even
start.
Looking
for
content
for
the
meeting
until
10
days
out.
D
And
the
only
reason
why
this
one
is
kind
of
working
out
is
because
it's
me,
but
if
we'd
actually
succeeded
in
recruiting
like
a
person,
who's
relatively
new
to
contrib
x
for
hosting
it,
they
would
have
been
kind
of
lost.
So
texan
issues
is
good,
but
we're
we're
looking
for
other
ideas
on
how
can
we
grab
stuff
from
the
community
that
should
be
discussed
in
the
community
meeting
or
get
people
to
suggest
stuff
to
us
from
across
the
community
on
a
sort
of
continuous
basis.
I
Right
and
just
just
as
a
note,
we
have
tried
forms
there
is
a
google
form,
that's
been
attached
to
the
calendar.
I've
been
posting
it
in
various
channels.
No
one
wants
to
fill
it
out.
I
know
we
talked
before
about
having
a
github
form
if
they're
not
going
to
use
the
labels,
I
don't
know
that
they'd
use
a
git
home
form
either
and
also
it
does
still
require
people
to
be
comfortable
enough
in
github.
I
So
I
mean
there's
been
a
few
different
attempts
at
trying
to
fix
this
problem
so
still
suggest
ideas,
but
this
has
been
a
long-running
issue.
I
think,
especially
now
that
we're
no
longer
doing
it
based
on
each
sig
is
required
to
show
up
at
some
point
now
that
it's
actually
based
on
just
topic
of
topics
of
discussion.
So
just
a
note
on
that,
one.
A
Yeah,
just
like
thinking
of
the
top
of
my
head,
like
kind
of
some
ideas
and
things
like
so
we've
got
kind
of
like.
A
Maybe
we
need
to
define
some
kind
of
roles
around
the
community
me
I'm,
I'm
kind
of
I
feel
like
I'm
a
little
bit
out
of
touch,
which
is
on
me.
I
should
kind
of
say
what's
going
on,
but
maybe
so
from
my
understanding.
We
have
a
host
and
is
that
correct,
laura.
I
I
So
that's
the
three
roles
around
the
meeting
itself
traditionally
before
when
we
had
the
sigs,
the
host
was
the
one
who
reached
out
to
the
six
make
sure
they
were
ready.
Things
like
that
that
was
on
the
host
for
each
month,
but
it
at
least
they
knew
what
topics
they
were
going
at
and
the
chairs
should
have
known
that
we
were
coming
to
talk
to
them.
I
We've
been
trying
to
figure
out
a
better
way
to
make
it
so
that
the
hosts
aren't
necessarily
the
one
having
to
come
up
with
the
topic
of
discussion,
especially
since,
in
the
past,
all
of
the
hosts
have
been
new
to
the
project
new
to
a
sig
new
to
everything,
and
so
they
don't
have
the
connections
into
various
cigs
to
ask
for
help.
So
over
the
past
few
times,
we've
tried
to
do
it.
Paris
has
been
really
helpful
in
helping
me
find
people
just
because
you
know
I've
been
posting
in
the
various
channels.
I
Things
like
that
and
various
people
say.
Oh,
I
know
so,
and
so
I
can
reach
out
to
them,
but
crowdsourcing
it
over
time
from
all
of
us
saying,
like
I'll
help.
The
host
with
this
person
I'll
help
the
host
with
this
person
isn't
necessarily
going
to
get
us
a
good
process.
In
the
end.
A
Yeah,
I
think
there
might
be
room
for
defining
a
role
around
this
where
it's
kind
of
you
know.
Curation
of
like
topics
like
so
then
host
kind
of
is
rotating,
and
it
can
be
like
someone
who's
new
to
the
community,
and
you
know,
then
we
have
like
a
curator
role
who,
like
you,
know,
could
potentially
be
like
shattered
by
like
the
host
and
all
that
so
like
this
role
of
this
curator
would
be
like
to
go.
A
So
that,
like
you
know,
they
can
understand
that
and
then
next
meeting
that
host,
that
was
for
that
meeting.
They
like
know
some
people
and
can
potentially
curate
the
next
one.
So
that's
that's
just
something
from
the
top
of
my
head
kind
of
based
on
a
lot
of
like
the
comments
like
paris
has
been
giving
like.
Really
good
assistance
with
helping
out,
like
you
know,
with
a
lot
of
kind
of
things
on
the
similar
lines
around
this
thing,
so
yeah.
What
are
other
people's
thoughts
on
the
topic.
E
Yeah,
I
I
think
that
you
know
if
we're
expanding
the
house
responsibilities
to
include,
like
you
know,
kind
of
helping
gather
some
interest
for
the
next
meeting
or
next
topics.
I
think
that
can
work.
I
I
am
wary,
like
laura
mentioned,
of
adding
another
form
sheet
issue
thing
that's
there,
but
if
we
have
people
who
are
particularly
active
in
monitoring
slack
and
seeing
threads
or
like
conversations
that
kind
of
run
long,
it
might
be
good
to
be
plugging
like
hey.
E
This
is
a
good
issue
to
bring
up
or
like
if
we
had
a
designated
space,
maybe
not
creating
a
new
channel
but,
like
maybe
some
other
way
to
annotate
like
oh
hey.
This
would
make
a
really
good,
like
community
meeting
topic
in
the
slack,
because
that
seems
like
where
most
of
the
communication
is
taking
place.
Anyways.
E
D
And
I
think
slack
is
probably
I
think,
nigel's
right
slack
is
probably
the
way
to
go
here
rather
than
the
form
and
stuff
that
we
have.
D
I
think
part
of
where
we
need
to
get
to
is
that
you
know
sig
leads
contributors
etc
need
to
feel
that
if
they
need
to
re
a
large
portion,
you
know
the
community
outside
of
their
city,
that
putting
something
on
the
agenda
in
the
community
meeting
is
the
way
to
go
so
that
it's
not
a
matter
of
contributing
searching
for
topics,
but
a
matter
of
people
send
sending
us
saying
hey.
I
want
to
talk
about
this
at
the
community
meeting.
Sure.
E
I
I
think
both
is
great,
but
I
think
just
like,
as
as
a
kickstart,
you
know,
then
people
kind
of
get
used
to
oh
hey.
This
is
getting.
You
know
like
certainly
letting
the
sig
leads
know
are
the
people
who
are
doing
stuff
for
each
like
place,
like
I'm
sure
they
already
do
know,
but
reminding
them,
because
you
know
people
forget
like
hey,
we
need.
We
need
topics.
So
like
a
call
for
a
call
for
topics,
I
guess
to
sign
off,
like
you
know,
any
of
the
communications
that
we're
having
with
with
sig
leads.
I
I
Trying
to
get
them
to
hand
raise
is
going
to
be
a
long
uphill
battle.
I
think
so.
The
more
we
can
get
just
the
community
saying.
I
want
to
talk
about
this
at
the
community
meeting.
I
think
that's
where
it
would
be
really
helpful,
and
I
do
agree
that
getting
that
on
slack
is
probably
the
best
spot,
since
everybody
is
talking
there
so
like.
I
If
someone
is
in
a
channel
for
another
sig
and
notices,
something
that
they
think
would
be
a
great
cross-cutting
discussion,
bringing
it
up
and
trying
to
get
the
the
sig
itself
to
be
interested
in
talking
about
it,
because
the
expert
doesn't
have
to
be
the
lead,
it
doesn't
have
to
be
the
chair,
and
I
think
a
lot
of
people
seem
to
think
that.
So
maybe
we
just
need
better
messaging
around.
E
I
think
just
like,
as
we
have
more
of
these
regular
community
meetings
and
like
examples
of
like
oh
that
could
be
me
talking
about
this
thing
that
perhaps
other
folks
like
when
they
start
to
see
themselves
like
in
the
meetings
it'll
feel
less
of,
like
a
I'm,
not
important
enough
to
kubernetes
to
talk
in
a
community
meeting.
You
know.
E
I
think
that
part
of
it
is
just
like
some
of
the
groundwork
that
we're
doing
now
and
then
like,
if
we're
able
to
get
folks
like
to
kind
of
grass
root
it
from
like
the
folks
that
are
here
to
say,
hey
like
bring,
can
you
bring
it
up
in
a
community
meeting.
D
Yeah
the
I
mean
really
where
I'd
like
to
get
to
is
things
like
I
mean
take,
for
example,
this
you
know
beta
off
by
default.
D
Pr
right
is
what
we'd
like
to
get
to
is
the
point
where,
when
somebody
is,
writing
that
pr
they
say:
oh
hey,
this
should
probably
come
up
in
the
community
meetings
and
they
send
a
note
to
someone
yeah,
the
you
know,
and
you
know,
and
not
because
the
problem
is
that,
if,
if
whether
it's
us
or
whether
it's
sig
leads
or
whatever,
if
we're
asking
people
to
collect
ideas
after
the
fact,
then
they
have
trouble
thinking
of
them
the.
If
we're
going
to
do
this
on
slack,
is
there
a
way?
D
A
Could
we
have
a
I
mean
like
an
handle
like?
I
think
this
is
some
something
could
look
into
on
like
this
like
automation,
side?
Is
it
like
a
bot
that
could
exist
where
you
go
slash
potential
community
meeting
topic
or
something
in
a
reply
or
something
or
I
think
yeah?
A
I
There's
there's
a
long
running
one
for
rethinking
the
community
meeting.
I
think
it's
still
actually
open,
so
I
can
probably
add
to
that
or
I
can
make
a
new
one.
I
guess
the
one
thing
I
do
want
to
remind
everybody
is
you
know
this
is
still
we've
been
trying
to
reboot
this
now
for
a
year
we're
finally
getting
a
little
bit
of
traction.
I
So
I'm
not
surprised
that
we're
not
completely
getting
that
traction
that
we're
hoping
for
so
the
one
thing
I'd
I'd
be
careful
of
is
not
flailing
too
much
and
trying
this
trying
that
trying
the
other
people
need
to
get
used
to
having
it
there.
So
just
something
to
keep
in
mind
if
we
can
add
two,
I
think
that
makes
more
sense
versus
taking
away
and
trying
something
else.
So,
just
as.
I
But
I
see,
you've
got
your
hand
up.
L
So
what
I
was
about
to
say
aligns
with
what
allison
just
mentioned
around
like
it
could
be
something
that
we
could
add
on
to
slack
automation.
It
would
work
similarly
to
how
like
at
anders,
are
synced
today
or
you
know,
like
okay
to
test
labels
are
applied
today.
Something
like
that,
because
I've
seen
this
elsewhere
as
well,
where
you
react
to
a
message
with
a
particular.
L
I
don't
know
what
it's
called
like:
the
slack
reaction
thingy
that
just
goes
ahead
and
puts
it
somewhere
and
it's
better
to
filter
it
down
it's
better
to
have
a
bunch
of
people
who
are
actively
involved
in
the
community
meeting
filter
those
topics
down
at
a
later
point,
because
now
we
all
have
topics
not
just
after
the
fact,
but
also
since,
as
and
when
they're
happening
as
well.
L
L
If
someone
could,
let
me
know-
because
I
I'd
be
more
than
happy
to
help
out,
because
I
usually
have
like
a
close
watch
on
these
type
of
like
controversial
changes
so
like
this
is
one
thing
I'm
happy
to
like
add
more
detail
in
like
in
an
issue,
but
this
is
something
we
could
do
like
yeah.
A
All
righty,
so
let's
we've
moved
on
to
the
next
topic,
just
because
we're
at
30
minute
mark
and
we've
got
a
bit
to
come
through,
but
we
can
come
back
to
discussion
on
the
community
meeting.
If
there's
more
ideas
on
the
line,
so
contributor
summit,
we
are
starting
to
put
things
together
and
puya
is
going
to
be
stepping
up
as
co-lead
on
the
contributor
summit
side
of
eu.
A
There
are
meeting
notes
working
on
putting
together
the
agenda,
feel
free
to
add
and
like
if
you,
if
you've
got
time
to
add
the
template
in
and
add
you
know
what
things
need
to
be
raised
going
back
through
the
events
documentation
too
as
well.
I
think
it's
been
a
while,
since
we've,
you
know,
run
a
contributor
summit
and
it's
definitely
kind
of
you
know.
This
is
the
second
one
that
we've
run
after
not
really
running
any
summits
for
two
years.
So
it's
just
kind
of
continual
improvement.
A
Yeah
is
what
I'd
like
to
say
on
on
those
lines.
Is
there
any
questions
from
anyone
on
the
line
around
a
contributor
summit.
D
H
Yeah,
I
listened
I
talked
this
morning
and
we
also
thought
it
would
be
nice
to
make
it
more
unconference
style
and
have
maybe
just
one
kind
of
kick-off
session
in
the
morning
that
that,
like
wakes
people
up
the
keynote
style
thing
and
then
ended
with
a
panel
of
contributors,
you
know
so
like
frame
the
the
unconference
there's
like
a
keynote
and
a
panel.
H
And
do
like
single
track
plus
hallway
track
to
keep
it
keep
it
lean.
For
I
don't
know
how
many
people
will
be
there
yeah
sure.
D
Well,
that's
that
is,
that
is
the
indefinite
thing,
yeah
right!
So
far,
it's
looking
like
it's
going
to
be
a
lot
like
l.a
was
in
in
terms
of
in-person
attendance,
because
I
will
tell
you
that
several
large
corporate
sponsors
of
kubernetes
have
not
yet
given
their
staff
permission
to
go
the
so
and-
and
that
includes
me,
I
I
have
not
been
allowed
to
buy
a
plane
ticket
yet
so
the.
D
A
Yeah,
there's
a
there's,
a
lot
of
discussion
that
can
be
actually
kind
of
had
now,
like
you
know
on
that
point
like
especially
when
we're
trying
to
grow
this
event
again,
I
think
yeah,
especially
like
I've
been
thinking
a
bit
about.
Can
we
actually
bring
back
the
like?
Would
there
be
some
value
in
bringing
back
the
contributor
workshop
in
like
a
sh
in
us,
in
a
different
style
or
just
kind
of
that's
something
that
we
can
explore
later
on?
A
This
call
because
it's
under
it's
under
mentoring
but
yeah
any
any
other.
Any
other
comments,
questions
queries
on
the
line
for
kuya
and
contributor
summit.
A
D
No
not
yet
I've
been
kind
of
overwhelmed
with
other
things,
the
I
need
to
actually
submit
the
pr
for
an
election
subproject
charter
and
because
of
some
technical
I'll
considerations
to
actually
move
the
elections
directory
at
the
same
time
that
we
upgrade
electo
the
because
it's
gonna
require
some
coordination
with
our
infra
team,
the
so,
and
and
currently
I'm
actually
supervising
an
intern
who
is
working
on
improving
the
security
of
alecto.
D
So
the
but
yeah,
but
I
mean
next
step,
is
to
submit
a
pr
that
actually
kind
of
creates
it
as
a
sub
project.
Does
some
projects
need
to
get
approved
by
the
steering
committee?
I've
forgotten.
D
D
Yeah,
I
I
did
ping
the
list
of
of
election
officers.
D
D
D
Our
deadline
for
this
is
really
july.
I
guess
because
that's
when
we
have
to
have
everything
in
place
for
first
starting
the
election
process.
D
It's
gonna
be
low,
so
selection
committee
would
basically
be
doing
two
things.
One
is
the
election
committee
would
be
recommending
election
officers
to
the
steering
committee
every
year,
and
the
second
thing
the
election
committee
would
be
doing
is
basically
sort
of
supervising
or
github
managing
on
demand
elections
for
anybody
who
wants
to
run
a
smaller
election
since
we'll
have
the
ability
to
provide
that
the,
but
somebody
has
to
approve
the
pr.
D
You
know
the
I
I
guess,
sort
of
the
bigger
potential
time
commitment
would
be
looking
at
improvements
in
the
election
process
itself.
For
one
thing,
we
have
an
awful
lot
of
unfinished
documentation
around
around
the
election
and
around
the
steering
committee
election.
So
because,
like
currently
the
the
process
documentation
of
how
you
run
the
steering
committee
election
is
both
incomplete,
which
it
always
was
and
is
now
is
still
largely
based
on
sieves.
D
So
it
needs
to
be
updated
and
completed
and
made
more
clear
and
followable
and
a
bunch
of
other
things.
So
that
would
be
the
biggest
part
of
the
time.
Commitment
for
this
would
be
would
be
helping
complete
that
documentation.
D
The
the
rest
would
be
pretty
minor,
the
rest
would
be.
You
know,
you're
looking
at,
I
don't
know,
probably
five
hours
of
of
argument
of
discussion
on
slack
in
in
july
to
pick
election
officers
to
recommend
election
officers,
and
you
know
a
couple
hours
a
month,
the
rest
of
the
year
to
approve
people's.
I
want
to
run
an
election
for
x.
A
All
righty
which
moves
us
over
to
mentoring,
meet
our
contributors.
Paris
has
left
notes
here
and
that
will
be
moving
meet
our
contributors
into
office
hours
and
that
we
might
sunset
the
documentation,
we're
looking
also
for
so
around
playground,
g-stock,
outreachy,
lfx,
mentorship
program,
we're
looking
for
a
group,
mentoring
coordinator
and
that's
paris
over
paris
has
left
a
note
here
and
we
we've
linked
the
issues
there.
Sorry
so
next
yeah
so
check
out
that
issue.
A
Where
we've
got
the
group
mentoring,
coordinator,
new
role
for
that
and
yeah
any
questions
about
what
we've
got
so
far.
Any
discussion
points
around
those.
I
know
I
just
kind
of
jumped
from
one
thing
into
another.
There.
A
Which
leads
us
to
contribute
a
workshop.
Now
I've
been
thinking
about
the
the
contributor
workshop
a
bit.
A
I
think
it's
been
a
long-standing
project
where
tried
to
do
a
lot
of
things
with
it,
and
we've
tried
to
make
it
like
virtual
we've
tried
to
do
things
in
the
middle
of
a
pandemic
when
everyone's
like
got
less
bandwidth,
and
you
know,
I
think
we
need
to
kind
of
start
with
it
again,
some
form
or
some
shape
around
the
contributor
summit,
but
in
a
smaller
kind
of
scope,
and
this
wouldn't
be
happening
at
it,
wouldn't
be
happening
at
eu.
A
C
I
mean
bandwidth
problems
aside.
That's
like
the
key
hang
up
in
doing
it
right
like
we
have
to
figure
out
a
low
bandwidth
way
for
folks
to
do
this.
C
A
Yeah,
I
just
thinking,
like
you
know,
that's
one
thing
like
with
the
contributor
summit
scaling
down
from
san
diego
there's
kind
of
you
know
less
new
folks
in
that
room
and
having
in
north
america,
we
had
in
2021
sick,
meet
and
greet
during
the
main
conference,
and
then
I
felt
kind
of
you
know.
During
that
time
there
was
a
lot
of
like
clashes
between
you
know.
A
A
There
is
kind
of
a
challenge
where,
if
you
bring
new
contributors
to
the
summit
there
there
might
be
too
many
people
and
if
you
do
it
during
the
main
conference
yeah.
So
I
think
I
don't
want
to
make.
I
we're
running
a
little
bit
short
on
time,
so
we've
got
17
minutes
left
here
and
I
want
to
make
sure
there's
enough
time
for
other
areas.
C
A
So
yeah,
I
will
actually
yeah
future
of
contributor
summit
income
yeah
action
item
to
kind
of
maybe
look
into
that
in
a
time
that
we
can
plan
that
any
other
kind
of
questions
around
you
know.
Actually,
I
think
that
was
the
only
discussion
to
be
honest,
but
any
other
thoughts
or
questions
online
yeah.
A
So
next
week,
community
management,
we
need
to
get
the
lead
moderator
going
like
going
again
right,
so
we
need
to
get
lead
moderator
happening.
There's
an
issue
in
github.
A
I
will,
after
this
meeting,
go
grab
that
and
link
that
in
here,
so
any
of
any
folks
here
from
community
management
on
the
line
who
can
chime
in
on
anything
happening.
On
that
end,.
A
I
so
last
but
not
least,
we
have
contributor
documentation
eric
eric's
on
the
line.
F
I'm
here
I
kind
of
slacked
off
after
the
last
meeting
I
was
supposed
to.
I
have
a
bunch
of
pull
requests
that
need
additional
reviewing.
I
think
most
of
them
just
need
like
one
more
person
to
look
at
it,
so
I
will
I'm
just
gonna
spam.
The
contributes
channel
with
like
three
or
four
pull
requests
that
just
need
somebody
to
look
at
them.
So
I'll
do
that
later
this
morning,.
F
A
All
righty
contributor
site,
so
there
is
that
issue
that
we
had
open
for
moving
some
of
the
documentation
to
capes
dot
dev
and
does
anyone
in
the
anyone
in
the
call
have
a
quick
link
to
that,
because
I
tried
to
find
a
link
to.
I
could
not
find
that.
A
A
We've
just
briefly
gone
over
contributor
documentation,
eric's
going
to
be
putting
some
pull
requests
into
the
contributor
experience
slack
channel
later
on
today,
and
we're
now
on
to
the
contributor
site,
where
there
was
that
kind
of
discussion
from
the
last
meeting
where
we
wanted
to
migrate,
kate
stop
well,
we
wanted
to
migrate
content
into
kate.
Stop.
A
Dev
josh
has
proposed
that
we
expose
here
that
content
by
the
community
site
and
I
think,
general
consensus
on
that
has
been
yes,
we
should
do
that,
and
now
kind
of
you
know
if
that's
the
as
general
kind
of
five.
This.
D
Yeah
I
mean
there's
two
steps
to
it.
One
is
just
wholesale
right
now.
D
The
so
you
know,
and
does
that
mean
that
that
stuff
stays
in
the
community
opponent
gets
imported?
Somehow?
Does
that
mean
that
we
copy
stuff
over?
Does
it
mean
that
the
contributor
site
repo
ceases
to
exist,
and
actually
we
have
one
repo
that
is
both
community
and
the
contributor
site?
D
F
Who's,
who
is
those
people
who
are
those
people.
A
Think
this,
I
remember,
like
bob,
wrote
the
script
that
did
the
copying
of
things
across
and
I
think
you
know
that's
that's
something
that
sig
chair
as
well.
I
need
to
have
more
oversight
on
this,
because
that
is
one
of
our
areas.
It's
in
the
charter,
you
know
so
yeah,
follow
up
item
to
you
know
fear
for
like
getting
a
bit
more
visibility
in
there
yeah.
I
will.
A
So
contributor
site.
A
But
actually,
though,
is
there
anyone
here
on
local
who's,
worked
on
the
contributors
site.
H
M
P
M
P
Familiar
with
the
code
base,
the
yoga
template
language
and
stuff
yeah,
which
which
actual
content
is
in
the
website
on
the
website
and
which
content
is
on
the
other
website,
other
repositories
like
conte,
kubernetes
website
so
yeah.
I
know
that
mainly
the
blogs
are
on
the
this
contributors
website.
A
So
I
think,
with
the
contributor
side
we
could
in
one
way
like
we
could
have
another
script,
that
kind
of
syncs
whatever's
happening
in
the
community
repo
or
we
could
move
the
content
itself.
I've.
A
F
A
So
yeah,
I
think
we've
got
about
seven
minutes
left
where
we've
got
a
github
management,
it's
usually
bob
nikita
and
kristoff.
I
haven't
had
the
opportunity
to
sync
up
with
them
about
what's
happening
on
that
and
so
we'll
skip
over
that
and
which
leads
us
last
but
not
least,
to
open
mic
and
discussion.
So
is
there
anything
on
anything
else?
Folks
would
like
to
cover
anything
that
we
haven't
gotten
the
agenda
of
the
school.
A
So
we've
got
swag
ideas
for
owners
just
linked
down
here.
So
right
here,
we've
got.
You
know,
one
of
the
one
of
the
things
like
that's
been
kind
of,
discussed.
Paris
got
this
issue
here,
where
you
know
we
want
to
be
able
to
give
swag
away
to
people
who
raise
their
hand,
and
they
say
they
want
to
own
part
of
like
they
want
to
be
in
an
owner's
file
right
so
yeah
who,
what
kind
of
pieces
of
swag
could
we
have.
C
C
A
We've
got
in
the
chat,
we've
got
face
tattoos,
but
I'm
not
sure
that's
fake,
face
tattoos
or
fake
tattoos,
fake
tattoos,
kubernetes
stuck
on
tattoos.
You
know,
I
don't
know.
I
actually
had.
C
Now
the
the
okd
tattoos
didn't
go
over
well
what
they
need.
Yeah.
D
C
The
if
you
have
enough
of
them
it
could
be
if.
A
Do
any
laundry
that's
good
right?
Could
we
have
like
a
kubernetes
like
like
a
ring?
You
know
you
could
like,
like
I'm,
I'm
I
own,
I'm
an
owner
like
gonna.
I
don't
know.
Oh.
D
On
a
kind
of
silly
pragmatic
way,
although
this
is
probably
would
be
too
much
budget,
a
pragmatic
thing
honestly
would
be
to
get
branded
yubi
keys.
D
A
I
I
remember
seeing
some
initiative
a
while
ago
around
ubiki's
in
kubernetes,
so
I
think
it
was
like
with
sick
leads
or
something
or
I
need
to
kind
of
chime
up
on
that.
Maybe
there
might
be
some
newbie
keys
around.
Is
that
the
discount
code
that
people
are
talking
about,
I'm
I'm
not
sure
yeah.
D
H
D
A
I
think,
if
we
kind
of
tandem
this
into
like
an
initiative
around
kind
of
security
and
stuff,
I
think
there
is
there
is
probably
like
you
know
something
we
should
do,
and
we
should
at
least
kind
of
try
get
some
of
that
budget.
I
mean
how
many
owners
do
we
have.
Can
we
can
we
scope
that.
D
We
also
have
to
determine
is,
is
how
are
we
defining
owner
here
right
because
there's
an
awful
if
you
include
everybody
who
is
the
owner
on
one
directory,
that
that
may
only
have
two
files
in
it?
That's
a
lot
of
people
the
so
it
would.
You
know
if
we're
doing
anything.
D
D
We
need
some
new
way
to
compare
it
with.
We
need
to
decide
it's
a
criterion
for
a
significant
owner.
A
A
So
we
could,
I
think,
yeah
that
there's
been
there's
going
to
be
like
updates
or
there's
updates
in
the
next
couple
weeks.
I
don't
kind
of
want
to
like
start
kind
of
getting
into
that
weird
judgy
idea
of
judgey
area
of
like
how
much
of
an
owner
are
you
kind
of
thing
well.
D
But
but
I
mean
to
give
you
an
example:
we're
going
to
find
that
we've
got
a
couple
hundred
people
who
are
well.
I
think
we
will
right.
I'd
want
to
actually
see
this
number,
but
I
I
have
the
sense
that
there
are
a
lot
of
people
who
are,
for
example,
they're
listed
as
an
owner
in
say,
an
event
directory
for
one
event.
D
That
happened
three
years
ago,
so
the
you
know,
or
they're
an
owner
file
for
sort
of
one
web
dock
for
a
single
document-
the,
although
not
with
maine
kubernetes
stocks,
because
it
doesn't
work
like
that.
The
so
we
just
kind
of
want
to
do
a
spot
check
on
that
and
see
what
the
numbers
are,
because
if
there's
like
150
people
who
do
fall
under
that
category
of
they
are
an
owner
file
of
one
directory
that
has
no
subdirectories,
then
we
might
want
to
reevaluate.
A
Yeah,
which
kind
of
we're
at
time
at
the
moment,
but
it
was
it's
lovely,
seeing
y'all
you
know.
Thank
you
very
much.
Everyone
for
like
coming
along
to
the
call
really
appreciate
it.
I
really
appreciate
all
the
work
that
y'all
have
been
doing
to
help
out.
Like
you
know,
it's
it's
it's
a
lot
so
like.
Thank
you
laura
for,
like
continuing
on
with
like
running
the
community
meetings.
I
really
appreciate
it.
Thank
you
like
chris,
and
just
everyone
like
yeah.