►
From YouTube: [SIG ContribEx] Bi-Weekly Meeting for 20201028
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
We
abide
by
the
cncf
code
of
conduct,
which
essentially
boils
down
to
please
be
excellent
to
each
other,
and
with
that
we
can
kick
right
off
into
our
recurring
business.
Actually
I
don't
see
anyone
new
on
the
line,
so
we
yeah
yeah.
I
think
we
can.
We
can
go
right
into
our
recurring
business
and
events.
There
isn't
really
any
updates
here
for
office
hours
or
the
community
meeting.
The
community
meeting
is,
of
course,
on
hold
now
to
2021
for
the
contributor
summit.
A
If
anyone
is
interested,
we
now
have
a
tracking
issue
where
people
are
volunteering
on
that
thread.
The
sort
of
big
question
right
now
is:
when
do
we
actually
want
to
host
it?
A
My
personal
thought
was
to
host
one
since,
like
the
the
focus
of
it
is
going
to
be
social
and
not
really
work
related.
I
was
thinking
of
actually
like
doing
it
after
the
120
release,
because
that
should
be,
you
know
end
of
the
year.
The
major
deliverables
are
done
and
people
can
relax
and
chill.
A
Cool,
if
you
don't
mind
following
up,
but
just
like,
plus
wanting
that
on
the
thread
just
so
we
have
some
other,
you
know
I
don't.
I
don't
want
to
say
accountability,
but
just
other
like
support
of
it
outside
of
the
you
know.
The
call.
A
A
Okay,
that
takes
us
to
the
steering
election.
I
think
the
only
big
thing
is
the
retro
next
monday
josh.
Is
there
anything
else.
A
A
Okay,
we'll
kick
it
off
into
mentoring.
I
don't
see
personal
line,
so
I
think
we'll
just
skip
the
meet
our
contributors
and
ihor
is
also
out.
I
don't
know
if
folks
saw,
but
he
unfortunately
got
coved
and
will
probably
out
be
up
for
a
bit
well.
E
Yeah,
although
I
can
report
so
we're
skipping
this
term
on
gsoc
well,
gsoc
hasn't
started
yet
we're
skipping
this
term
on
outreachy.
If
people
are
thinking
of
projects,
we
should
be
aware
that
we
have
one
credit
without
richie
that
expires
after
the
spring
term.
E
So
if
we
don't
use
it
for
the
spring
term,
then
then
it
just
expires.
We
need
to
raise
more
money,
the
and
we're
doing
one
project
for
community
bridge
right
now
we
have
money
in
community
bridge
to
actually
do
two
or
three
other
projects,
something
we
should
also
talk
about
in
the
spring.
E
A
Okay,
next
do
we
have
any
updates
on
the
new
contributor
workshop,
I
wasn't
able
to
make
the
last
meeting.
D
The
updates
for
new
contributor
workshop
was
so
the
videos
are
currently
in
the
progress
of
being
recorded
and
stuff,
like
that.
The
video
recording
guides
like
pretty
much
almost
like
it's
gonna,
be
there
in
github
really
soon
we
were
it's.
It's
kind
of
at
the
moment,
a
bit
difficult,
we're
recording
videos
because
there's
a
lot
of
stuff
around
kubecon,
being
extra
demanding
saying:
oh
yeah,
we
want
the
videos
yet
now
thing
so
yeah.
I
think
that's!
D
A
Cool
the
next
general
thing
is
like
we've
been,
we
went
back
to
one
sort
of
mentoring
session
for
a
while,
and
that
was
essentially
taking
over
the
old
contributor
summit
session
and
that
has
now
sort
of
become
the
you
know:
apac
friendly
mentoring
in
general,
and
then
we
were
looking
to
schedule
a
naeu
friendly
one,
and
I
think
we
now
have
that
the
the
date
and
time
selected
markie.
Do
you
remember.
B
F
B
Yeah,
I
think
it
was
11
00
to
12
p.m
or
sorry,
11
a.m
to
12
p.m.
Pst.
A
Two
sorry
cool:
it's
all
good.
Do
you
want
to
send
something
onto
the
list
and
get
a
pr
into
the
like?
A
Actually,
I
need
to
generate
a
new
zoom
meeting
for
it,
so
I
will
do
that
and
get
that
to
you
and
then
do
you
want
to
follow
up
with
a
pr
into
six
dot
yaml
to
update
the
meetings
you
got.
It.
B
A
Cool
the
other
sort
of
big
thing
is
that
there
is
a
open
pr
out,
adding
you
know,
bumping
marquee
to
an
approver
in
the
mentoring
directory,
and
I
think
that
we
will
probably
be
following
that
soon,
with
adding
a
few
more
reviewers,
like
the
getting
more
people
actively
involved
in
mentoring.
Honestly,
this
is
this
is
just
sort
of
rectifying
the
people
that
have
been
active
in
it,
just
not
actually
in
the
like
orders,
file
of
the
actual
directory.
F
A
Okay,
that
will
take
us
over
to
community
management.
I
don't
have
anything
for
the
need
to
know
yet.
Does
anyone
else
have
any
suggestions
for
it.
A
Okay
and
then
do
we
have
anyone
that
could
potentially
give
an
apac
update.
A
Okay,
dev
stats.
I
don't
think
laurie's
on
the
line
and
then
I
I
do
remember
seeing
that
there
was
a
small
update
in
slack.
A
C
Yeah,
the
big
thing
we
took
last
week
off
mostly
focus
on
we
got
a
kubecon
or
kubecon
maintainer
talk
in
that
will
really
outline
a
lot
more
of
what
we've
been
up
to
and
some
of
the
successes.
So
the
leads
caslin
myself
and
rajula
have
been
focused
on
that.
Only
other
thing:
that's
floating
around
is
an
approval
for
a
subproject
that
got
a
ton
of
plus
ones
on
the
mailing
list.
Thanks
all
we'll
need
to
move
forward
on
that,
but
kubecon
comes
first
for
the
time
being.
A
Cool
yeah,
the
update
to
actual
subproject
isn't
too
hard.
It's
essentially
just
a
update
to
sigs.yaml,
oh
awesome
and
then
that
that
becomes
an
official
subproject,
easy
more
yeah.
All
in
my
life
I
like
it,
it
is
kubernetes
and
like
yamls
everywhere.
A
Marketing,
okay,
contributor
documentation,
I
don't
have
any
updates
for
the
guide
or
the
the
contributor
guide.
I'm
sorry
on
the
developer
guide.
The
one
little
comment
about
about
this
really
quick
is
that
we
are
actually
getting
a
lot
of
people
going
with
the
audit,
which
is
honestly
surprising
and
good
that
that
will
stem
for
more
work
later
on
and
with
that
I'll,
kick
it
over
to
you.
You
know.
G
Y'all
I
haven't
gone
through
all
the
other
comments
on
the
on
the
audit.
Yet
but
yeah,
it's
like
it
looks
like
six
out
of
the
11
issues
have
had
some
kind
of
activity
on
him,
which
is
pretty
pretty
astounding,
but
rhiann
started
a
started.
Some
work
on
the
sig
testing
stuff
in
the
developer
guide-
and
I
feel,
like
I
haven't,
had
enough
t
this
morning
to
totally
talk
about
what
we're
doing,
but
he
basically
is
working
on
updating
the
end-to-end
testing
guide.
G
I
had
gone
through
and
sort
of
updated
the
end
end
testing
guide
to
reflect
cube
test
2,
but
but
apparently
cube
test.
Two
isn't
ready
enough
yet
to
be
included
in
like
the
official
end
and
testing
guides,
so
so
the
one
that
was
already
there
also
needs
to
have
some
stuff
done
so
rian
started
working
on
it
and
I'm
gonna
be
helping
him
with
that.
I
don't
know
if
he
has
anything
to
to
say
about
that
particular
thing.
But
now
is.
H
You
totally
should
yeah.
There
was
some
comments
from
aaron,
it's
actually
the
original
issue
update
comes
from.
I
think
2018.,
oh
and
aaron
recently
made
some
comments
about
things
to
add.
So
I
looked
around
for
information
around
specifically
his
comments
and
I
added
things
about
brow
et
cetera,
so
I've
fed
eric
with
that
and
then
I
will
help
him
when
he
needs
gaps
for
writing.
I'm
not
the
writing
master,
but
I
can
develop
the
information.
G
Yeah,
so
I'm
gonna
need
to
probably
find
some
more
sig
testing
people
to
talk
to
to
learn
more
about
that
stuff
because
I've
looked
at
it,
but
I
can't
say
that
I
totally
grok
it
yet.
A
Okay,
have
you
talked
to
jorge
other
george
there's
another
one.
A
A
Release
so
yeah,
so
that's
under
sig
release,
but
the
this
specifically
like
it
bleeds
a
lot
over
into
testing,
but
he
might
be
another
good
resource.
I
can
pass
you
as
like
slack
and
github
handle
after
the
meeting,
okay
I'll
ping,
you
on
slack
to
to
get
that
info.
Okay,
all
right,
one
other
yeah!
There
we
go
marky
put
in
there.
A
The
other
thing,
if
you
don't
mind,
if
you
have
some
of
the
issues,
the
the
testing
issues
that
do
cover
what
is
missing
and
what
should
be
added,
if
you
can
post
those
in
the
developer
guide
audit
thread
just
so,
we
have
like
a
you
know
it
can
go
to
there
and
then,
even
if
it's
just
following
like
links
out
to
what's
missing
right.
That's.
G
A
good
idea:
okay
I'll
get
that
particular
thread
to
riyan,
so
he
can
put
his
stuff
on
there.
I
will
do
that
right
now.
Okay,
thank
you.
That's
a
good
point.
Awesome.
A
G
H
Okay,
I'm
actually
taking
the
end-to-end
testing
as
part
of
the
local
building
test
as
part
of
the
new
controversy
workshop,
and
once
we're
done
with
that,
that
would
also
properly
that
video
resource
would
probably
be
because
I
I'm
honestly
not
the
technical
expert,
but
I'm
part
of
the
team
on
project
management.
So
that
should
be
once
we
got
all
those
videos
out
there
underneath.
A
A
Okay
for
the
contributor
site,
not
too
many
updates
there,
one
sort
of
like
big
thing
that
did
change
is
we
switched
over
from
the
built-in
git
or
the
built-in,
like
javascript,
search
to
google
search.
That
was
actually,
I
believe
that
was
adam's
first
pr.
B
Yeah
yeah,
it
was
did
I
get
approved.
I
think
I
saw
it
yep.
A
It
it
all
got
merged.
In
yesterday
I
did
have
one
one
little
follow-up
little
thing
to
fix
another
like
separate
little
bug,
but
it
like
wasn't
in
the
reference
documentation
or
anything
like
that.
But
okay,.
A
A
Okay,
so
the
big
thing
really,
the
only
thing
in
here
right
now
is
we've
been
participating
in
the
github
recognition
beta.
This
essentially
allows
you
to
do
like
slash
shout
out
to
someone
in
github
only
in
specific
repos
for
now,
and
it
will
then,
like
you
know,
pop
up
in
the
github
timeline.
If
you
click
on
the
test
issue
in
the
notes,
I
can
link
it
in
chat.
A
A
The
when
it
gets
the
profile
stage
you'll
be
able
to
approve
it.
Github
is
very
aware
of
the
potential
like
trolling
and
moderation.
Type
capabilities
are
needed,
this
sort
of
thing,
but
if
you
want
to
try
it
out,
please
go
ahead
and
use
that
test
issue.
For
now
we
will
probably
roll
it
out
to
yes
on
the
announcement
out
for
general
usage
next
week,.
A
Again:
okay,
any
questions
about
that
or
other
github
management
type
things.
A
Okay,
one
small
slackin
for
update
is
we
have
this
issue?
I
don't
remember
the
deadline
for
it.
I
think
it's
actually
in
in
the
issue
itself.
No,
it's
not,
but
we
need
to.
A
A
I
A
So
at
this
point
we
get
the
plus
ones
essentially
for
the
using
one
password
need
to
sync
with
steering
at
this
point.
Steering
sc
one
two
and
three
which
are
named
accounts
will
own
the
we'll
own,
the
one
sort
of
password
accounts.
This
is
like
mostly
just
for
a
break
glass
scenario
where
they
might
have
to
get
in
and
do
something.
Otherwise
it
will
essentially
be
delegated
to
contrabex
to
manage
it
and
just
need
to
get
those
like
confirmed
with
steering
and
get
that
stuff
out.
A
A
Sorry,
I
just
also
realized,
and
I
sort
of
skipped
sergey-
do
you
think,
were
you
referencing
jenny's
update
in
slack.
I
H
A
Something
that's
not
in
here,
but
an
update
from
jenny.
The
oh
there's
no
update
on
the
sick,
weekly
progress,
reporting.
I
Template
yeah,
so
we
finished
the
document
and
yeah
big
shout
out
to
everybody
contributed
right
now,
I'm
I
actually
used
it
very
well.
When
I
was
sick
for
a
week
and
then
I
returned
back
and
looked
at
the
weekly
stats
and
like
it's
really
helpful,
like
you
can
review
what
happened
and
you
kind
of
like
don't
have
this
form
of
being
out
for
a
while.
I
I
think
we
need
to
have
many
improvements
to
the
sick,
weekly
thingy,
but
we
may
need
to
start
with
some
feedback
from
other
people
like
how
are
the
people
using
it?
So
I'm
looking
for
active
contributors
who
want
to
be
who
want
to
know
the
status
of
a
week
and
if
you
can
use
this
list
of
prs,
completed
and
active
and
suggest
other
ideas
what
you
want
to
track
to
be
really
nice.
A
And
what
what
might
be
a
good
follow-up
excuse
me,
is
we
actually
bring
it
up
in
the
chairs
and
tls
slack
slash
like
monthly
meeting,
because
that's
going
to
be
okay,
that's
where
we'll
probably
be
able
to
get
the
most
feedback
on
people
that
are
sort
of
running
these
things.
A
I
will
say
that
attends
has
been
fairly
light
but,
like
you
know,
covered
and
people
have
been
busy.
What
is
this
meeting?
Oh
it
it
it's
technically,
not
on
any
of
the
calendars.
I
can
get
you
invite,
though.
Essentially
it's
it
just
goes
to
the
leads.
It's
not
public,
but
yeah
I
can.
I
can
get
you
information
on
that.
Thank
you.