►
From YouTube: [SIG ContribEx] Bi-Weekly Meeting for 20210330
Description
[SIG ContribEx] Bi-Weekly Meeting for 20210330
A
Hello,
everyone
welcome
and
welcome
to
this
week's
contributor
experience
weekly
meeting
zoom
edition,
I'm
I'll,
be
your
host
allison
and
just
a
general
housekeeping
here.
We
we
abide
by
the
cncf
code
of
conduct
so
just
in
short,
be
excellent
to
each
other
and
I
think
ev
everyone
on
the
line's
familiar.
A
A
D
A
A
A
D
A
E
Yeah
no
major
updates,
lfx
mentoring
is
is
running,
so
no
main
genius
will
have
a
next
round
of
evaluations
in
the
next
few
weeks,
so
everything
is
moved
there
what's
good
concern
of
code
with
during
the
period
when
students
have
to
apply
so
if
there
are
any
potential
students
at
this
meeting
who
want
to
participate
in
google's
room
of
code
this
year.
So
it's
your
time.
E
A
C
I
don't
know
when
we've
last
updated,
this
meeting
we're
switching
to
more
of
a
focus
on
written
content
and
bob
has
set
up
a
new
spot
in
the
contributor
website
for
that,
because
we
think
written
content
has
a
better
chance
of
getting
done
and
being
more
maintainable
the
and
are
busy
trying
to
reassign
the
individual
chapters
within
that
based
on
on
who
can
produce
that,
I
have
not
been
able
to
sync
up
with
the
new
zealand
folks
anytime
lately.
So
I
don't
know.
What's
going
on
with
build
and
test.
A
All
right
moving
on
so
another
note
here
is
we're
looking
for
folks
to
help
with
code,
2040
and
other
partnerships
that
will
help
us
with
diversity,
specifically
that
back
up
our
black
lives
matter
statements
and
our
values.
So
that's
from
paris,
ideally
training
on
kubernetes.
It's
important
that
fault.
Oh
wait
was
that
the
same
note,
ideally
yeah
kubernetes.
B
I
I
can
comment.
This
is
actually
like.
Whatever
we
do
decide
to
do
with
the
new
contributor
workshop,
you
know
make
more
written
content.
This
sort
of
goes
back
to
making
it
into
a
course
that
people
can
take.
So
it
can
still
be
something
people
can
do
in
that
sort
of
environment
in
a
workshop
style
thing,
but
that
is
a
secondary
priority
to
her
to
us.
Just
getting
you
know
the
content
down
and
getting
it
there.
B
A
A
B
I
don't
think
there's
any
big
updates
there.
Yet
we
only
have
one
item
on
there
and
that's
the
we
all
have
access
to
the
zoom
live
construct.
The
live
transcribe,
although
it's
kind
of
janky
to
turn
it
on
and
the
live.
Transcribe
is
essentially
closed.
Captioning
live
closed,
captioning,
so
anyone
that
is
potentially
it's
an
accessibility
ad.
A
It's
heads
down
and
your
reports
slightly-
I
guess
so
I
guess
that
covers
us
for
the
need
to
know
chairs
and
team
leads
aipac
coordinator.
We
don't
need
to
worry
about
that.
I
believe
the
the
meeting
has
been
removed
from
the
calendar
and
the
initiatives
syncing
up
with
them
asynchronously
from
now
on.
I'm
not
sure
on
that.
B
B
One
of
the
big
problems
in
the
past
has
been
repo
groups,
like
don't
map
well
to
a
lot
of
our
cigs
that
work
primarily
out
of
so
reaper
groups,
group,
multiple
repos
together
as
one
unit,
but
we
have
a
bunch
of
sigs
that
literally
work
just
collectively
out
of
kubernetes
kubernetes
and
so
there's
no
way
for
them
to
sort
of
measure
or
see
what
their
work
is
when
just
using
repo
groups.
So
this
breakdown
should
help
them
as
well
as
sub
project
owners
that
do
actually
just
look
at
specific
repos
for
things.
B
C
C
B
F
B
If
we're
looking
at
things
like
kk,
but
we
like,
I
much
prefer
the
pr
repo
breakdown
and
just
by
by
label,
and
we
we
can
embed
those
specific
dashboards
and
things
like
the
contributor
website.
So
we
can.
Basically,
you
know,
tell
our
you
know
our
groups
how
to
interpret
the
data
there
without
having
to
have
it
just
be
on.
D
D
D
No,
that's
all
right.
I
I
wasn't
planning
to
report
since
matt's,
not
here,
but
there's
a
few
blogs
moving
forward
and
the
survey
was
kind
of
the
big
focus
for
a
while
and
we
were
able
to
get
a
pretty
good
number
of
responses
to
that.
So,
probably
that's
going
to
be.
I
would
predict
that
that's
going
to
be
more
focused
than
that's
working
on
right
now,.
C
B
B
C
B
A
B
B
D
E
B
D
B
F
E
A
A
B
B
So
hopefully,
here
soon
we
will
have
a
more
complete
list
of
the
things
that
do
actually
need
to
be
updated
and
some
of
them
have
just
gone
ahead
and
just
like,
oh,
we
can
take
care
of
this
and
they've.
You
know
at
least
pr
in
the
the
important
changes,
but
the
the
big
thing
is
like
we,
we
have
a
good
set
of
like
most
of
the
things
are
now
dude.
Are
you
know
at
least
on
it
and
keeping
it
up
to
date
or
trying
to.
D
Just
really
quick
on
that,
my
name
and
eric's
name
are
still
on
that.
I
don't
have
a
mechanism
of
tracking
that
project
bob.
Do
you
have
a
recommendation
of
how
we
can
how
I
can
just
keep
my
finger
on
the
pulse
of
that
part
of
the
reason
I'm
asking
is
that
this
meeting
so
frequently
is
allison
asking
you
questions
bob
asking
everybody
asking
bob
questions.
So
if
there's
a
way
that
I
can
be
a
little
bit
more
informed
and
answer
questions
instead
of
you,
I
don't
know,
save
a
few
vocal
cards
for
you.
A
A
B
A
B
B
A
A
A
G
E
G
A
B
Okay,
so
we
sent
out
the
our
the
signature
box
annual
report,
and
this
is
the
last
day
to
get
comments
well,
trying
to
this
to
be
the
last
day
to
get
comments
in
on
it.
It's
already
been
set
up
the
list.
If
you
can,
please
take
a
look
at
it.
I
think
everything
is
accurate
there,
if
not
just
toss
a
comment
and
I'll
try
and
get
it
addressed
by
the
end
of
the
day.
B
Okay,
so
the
next
one
is
something
that
we've
discussed
a
little
bit
in
steering
and
we
have
previously
made
our
leads.
Take
the
unconscious
bias
training.
It's
actually
like
the
inclusive
speaker,
training
that
the
lf
offers
as
a
mandatory
requirement
to
become
a
lead
at
this
point,
we're
thinking
you
know
if
we
want
to
try
and
begin
to
address
some
of
the
other,
let's
say
systemic
issues,
but
like
at
a
community-wide
level.
Would
this
be
good
to
actually
make
it
an
org
member
requirement,
which
means
before
you
can
join
one
of
the
kubernetes
orgs?
B
B
C
You
have
to
think
you
have
to
think
about
people
who
are
contributing
in
their
spare
time,
which
is
a
lot
of
them,
numerically
speaking,
the,
and
you
know
why.
Why
do
we
need
to
make
the
move
to
immediately
saying
you
know
hey
this
is
required
and
we're
going
to
suspend
your
membership.
If
you
don't
take
it,
why
not
just
first
start
out
by
simply
throwing
it
open
to
all
org
members
and
saying
hey.
B
C
E
B
A
A
I
I'm
not
sure,
though,
like
the
benefits
like
are
really
there,
because
I
I
don't
think
if
we
I'm
not
sure
if
we've
had
any
issues
where,
like
you
know,
someone's
become
a
member
and
then
they've
just
actively
been
doing
harmful
stuff.
That's
where
I
could
see
like
having
this
skating
on
a
unconscious
bias,
thing
being
a
whole
check.
This
person
aligns
with
our
community
values
once
again
thing,
but
maybe
it's
a
potentially
a
better
idea.
Further
down
the
line,
like
anything,
that's
more
than
a
member.
B
C
C
G
Is
it
possible
to
just
make
it
available
to
every
new
every?
I
don't
want
to
say
every
person,
but
every
org
member,
not
as
a
mandatory
and
then
revisit
it
and
say
three
or
six
months
to
see
how
many
people
have
actually
taken
it
and
then
then
you
have
a
better
foundation
to
work
from
to
say
then.
Well
we
want
to
do
you
know,
membership
level
enforcement.
I
don't
want
to
use
the
word
enforcement,
but
then
you
have
something
to
say
to
say:
okay.
Well,
we
did
this
and
we
just
let
it
be
out
there.
G
C
We'll
start
to
look
at
what
the
goal
is
here
right.
The
goal
is
that
we
want
an
atmosphere
where
people's
prs
don't
get
reviewed
or
not
reviewed
on
the
basis
of
their
ethnicity
or
background
right
that
they
get
reviewed
or
not
reviewed,
based
on
the
content
of
the
pr
and
and
and
not
biased
right,
and
in
order
for
that
to
happen,
we
don't
need
every
single
person
to
be
aware
of
their
unconscious
bias.