►
From YouTube: SIG Contributor Experience: Weekly Update 20200729
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
Well,
we
buy
by
the
cncf
code
of
conduct,
which
can
essentially
boil
down
to
please
be
excellent
to
each
other,
and
these
meetings
are
recorded
and
will
be
posted
to
youtube
now
with
that
we're
actually
going
to
sort
of
not
follow
our
standard
schedule
today,
where
we
normally
go
through
stand
up,
but
actually
kick
it
over
to
chris
to
talk
about
orbit.love
beta.
That
looks
pretty
interesting.
A
Yep
one
sec:
I
will.
B
B
Cool
you
see
my
screen.
B
Yep
looks
good
cool
awesome,
so
I
I
so
I
don't
know
how
many
people
here
are
familiar
with
a
project
called
orbit.
They
essentially
have
been
trying
to
codify
a
model
of
how
to
look
at
your
community.
B
You
know
they
kind
of
have.
I
don't
want
to
say
it's
similar
to
the
kubernetes
contributor
ladder,
but
like
similar
in
spirit,
at
least
where
they
kind
of
have
a
notion
of
different
levels:
ambassadors,
fans,
users
and
observers
and
they've
been
essentially
trying
to
build
tooling
to
bucket
people
in
these
categories,
based
on
their
participation,
your
community,
whether
it's
through
avenues
like
slack,
github
and
and
so
on,
and
some
of
our
projects
have
been
piloting
orbit
out
and
have
been
having
some
success.
B
For
example,
I
worked
with
the
spiffy
team
recently
and
kind
of
you
know
they
showcase
kind
of
what
they
have
done
with
spiffy,
where
you
kind
of
you
know
see
who's
new
to
the
community,
what
have
they
added
and
so
on,
and
they
kind
of
have
it
connected
through
a
variety
of
data
sources.
You
know
we
have
a
variety
of
tools
in
cncf
like
dev
stats
that
tend
to
be
very
developer
focused
but
they're
not
as
friendly.
I
think
for
let's
call
them.
B
You
know
like
normal
people
or
people
that
aren't
used
to
looking
at
you
know,
grafana
dashboards
up
to
you,
know,
bazoo,
and
you
know
we're
about
to
consider
entering
a
contract
with
orbit
to
look
at
the
kubernetes
community,
for
example,
and
I
would
think
contributor
experience
would
be
a
great
place
to
kind
of
help
pilot
this
tool
and
give
feedback.
The
orbit
folks
also
want
to
have
an
opportunity
to
kind
of
give
feedback
based
on
their
discoveries
using
their
tools
for
the
kubernetes
community.
B
A
B
Yeah,
so
I
mean
it
off
it
off.
You
know
by
default,
uses
github
for
authentication,
but
it
has
a
notion
of
essentially
data
sources
where
it
could
pull
from
a
github
org,
but
it
could
also
connect
to
say
a
slack
to
a
mailing
list
system.
It
could
also
help
if
you
have
a
system
that
does
like
developer
affiliations,
for
example.
It
could
also
tie
into
that,
so
I
still
consider
them
kind
of
beta,
but
you
know
projects
and
a
couple.
Companies
in
our
ecosystem
have
been
using
it
and
they've.
B
You
know
found
it
useful,
basically
to
identify
folks
that
they
may
want
to
approach
to.
You
know
have
a
more
formal
role
in
the
organization
whether
it's
like
becoming
a
maintainer
or
I
don't
know
their
company
and
like
oh,
we
would
love
to
hire
this
person,
but
essentially
it's
giving
another
avenue
of
for
you
to
look
at
people
within
your
community
that
generally
doesn't
come
up
easily
in
depth.
Stats
is
kind
of
the
way
I
look.
B
Yeah,
so
these
are
some
basic
ones.
These
are
just
members.
You
know,
I
think
the
reporting
is
interesting
and
probably
not
as
detailed
as
you
would
have
in
dev
stats,
but
the
notion
is:
they
have
a
different
way
of
of
looking
at
contributors
versus
like
raw
github
information,
they're,
also
looking
at
other
inputs,
mailing
lists,
slacks
and
so
on,
and
then
they
try
to
bucket
people
into
base
their
their.
B
Their
kind
of
you
know
orbit
orbit
model
which
they're
more
interested
in
learning
from
the
kubernetes
community
of
kind
of
how
we
bucket
people
in
our
you
know,
contributor
ladder
right
and
they're
trying
to
see.
If
there's
lessons
they
could
take
to
kind
of
evolve
their
model.
So
in
in
my
idea
at
least,
we
potentially
could
end
up
in
a
situation
where
we
kind
of
have
a
good
idea
of
identifying
potential.
B
You
know
new
contributors
or
promising
folks
that
may
we
may
want
to
like
loop
in
you
know
to
our
community,
because
right
now
I
think
people
just
kind
of
just
show
up
and
you
know,
find
contrabex
or
find
you
know
someone
community
that
kind
of
kindly
takes
them
through
the
process.
C
B
Yeah
I
mean
we're
not
mandating
anything,
we're
it's
more
of
just
we're,
trialing
it
out
and
looking
to
kind
of
both
learn
from
each
other
they've
taken
a
different
perspective
on
things,
and
I
think
it's
just
useful
to
kind
of
get
a
another
set
of
eyes
on
how
to
look
at
community
and
if
the
end
of
the
day,
we
have
a
cool
tool
out
of
it
that
we
could
potentially
use
awesome.
If
it's,
you
know
a
bit
of
a
failed
experiment,
it's
a
failed
experiment.
We
take
our
our
lessons
so.
A
Yeah,
if
you
could
just
toss
your
name
under
the
in
the
notes
on
that
section
just
so
you
sort
of
have
a
little
group
of
people.
B
And,
and
just
to
give
you
an
idea
that
time
commitment,
essentially,
I
think
we're
gonna-
do
a
two-month
kind
of
pilot
with
them.
I
think
it
would
just
be
like
a
30-minute
meeting
every
week,
while
they
kind
of
learn
from
us
and
do
it.
The
output
of
the
pilot
would
be.
They
would
also
write
like
a
bit
of
a
paper
of
recommendations
based
on
their
perspective,
and
you
know,
at
the
end
of
the
day,
we
may
have
a
useful
tool
for
us
for
for
the
community,
but
we'll
see
how
it
works.
B
I
think
in
two
we
we're
trying
to
schedule
a
post
kubecon,
because
some
of
us
are,
you
know,
kind
of
stuck
in
cube,
kubecon
bonanza
right
now,
but
most
likely
will
happen.
Probably
after
kubecon
the
first
week
after
kubecon
we
we
may
try
to
do
like
just
a
formal,
hey
who
we
are
meeting
in
a
couple
of
weeks
before
kubecon,
but
I
don't.
I
don't
feel
like
serious
work
will
happen
until
after
after
the
conference.
B
A
Cool
and
anything
that
we
discover
on
our
side,
we
will
definitely
forward
on
to
the.
B
List
cole,
yeah
I'll
look
at
trying
to
create
yeah
with
the
people.
That's
signed
up
I'll,
go
look
at
the
notes
and
and
kind
of
reach
out,
and
maybe
we'll
have
like
a
a
github
issue
or
some
other
public
forum
where
we
could
kind
of
track
and
all
this
stuff
so
kind
of.
If
anyone
wants
to
jump
in
and
participate,
they
can
okay
that'd
be
awesome.
Thank
you,
chris
cool.
All
right.
Thanks
for
the
time
yep.
A
A
Oh
now,
with
that,
we
can
sort
of
go
back
to
our
regularly
scheduled
program
and
kick
off
with
events.
A
Actually,
I
don't
see,
I
don't
see,
george
and
or
anyone
else
that
might
know
about
office
hours
or
the
community
meeting.
So
I'll.
A
Just
kick
off
the
little
thing
about
our
contributor
summit
right
now,
we're
still
sort
of
tbd
josh
and
I
were
sort
of
like
brainstorming
the
other
day
about
potential
things
we
could
do,
but
it
still
will
probably
boil
down
to
sending
a
survey
out
to
the
kubernetes
dev
mailing
list
to
see
if
people
want
to
like
you
know,
record
sessions
or
try
and
meet,
or
do
something
of
that
nature.
A
I
don't
have
any
updates
on
steering
election
about
kristoff.
Is
there
anything
on
that
side
from
you.
D
Yes,
the
steering
approved
criteria
for
for
membership
at
our
private
meeting
on
monday,
but
I
haven't
sent
an
email
about
it,
which
is
on
my
list
that
I
used
to
tell
me
I'll,
be
I'll
I'll,
be
sending
that
over
to
the
the
election
officers
and
and
seeing
if
there's
any
feedback
or
we're.
If
we're
good,
with
with
the
criteria
that
steering
approved.
A
Awesome
actually
josh
do
you
know,
did
the
election
email
get
switched
out
yet.
A
So
there
there's
we
have
and
it's
like
election
at
kubernetes
dot,
io
email
address
for
the
election
officers,
that's
managed
in
the
case.io
repo.
A
Okay,
then,
then
yeah,
I
probably
haven't.
A
Oh,
it's
it's
pr!
It's
just!
There's!
There's
you'll
you'll
get
invited
to
it
right
after
it's
updated.
A
Okay,
okay,
are
there
any
other
potential?
Steering
updates
are
staying
election
updates.
G
No
we've
been
waiting
for
to
find
out
what
the
steering
approved
criteria
were.
A
A
What's
that,
are
there
any
other
events
related
things
people
want
to
discuss,
or
should
we
kick
over
to
the
next
section.
E
I
don't
really
have
an
update
next
wednesday
is
a
cluster
api
addiction
edition,
but
that's
it.
A
Cool
are.
E
A
Unfortunately,
I
think
all
our
three
main
streamers
are
not
on
the
call
at
the
moment,
but
can
can
follow
up
with
them
in
slack.
A
More
streamers,
yeah
we've
been,
we've
been
doing
callouts
for
it,
but
finding
people
that
have
both
the
time
and
equipment
to
do
it
has
been
an
issue.
A
Problems
see,
were
there
any
other
things
for
meet
our
contributors.
A
Okay,
let's
see
is
e
on
the
line
by
chance.
G
A
Read
off
his
updates,
so
the
google
summer
of
code
is
in
the
second
phase
of
evaluations
and
is
in
progress
this
week.
Community
bridge
also
appears
to
be
in
the
same
thing
with
second
valuations
going.
Our
second
evaluations
are
due
this
week
as
well,
and
this
is
the
final
evaluation
set
for
the
current
cycle.
A
I
don't
have
any
other
information
beyond
that:
okay,
what
that
is
any
other
discussions
for
mentoring
at
this
point
in
time.
A
Actually
there
there
is
one
thing
I
do
want
to
toss
out,
and
this
is
also
in
yesterday's
mentoring
call.
We
might
see
about
adjusting
the
times
on
the
meeting,
because
attendance
has
been
a
little
bit
of
an
issue,
but
that
probably
won't
hit
go
to
the
list
to
change
until
probably
at
least
two
weeks
from
now,
we
will
see
about
we'll
see.
G
It's
every
other
monday
at
4,
00
p.m,
pacific.
The
time
we
picked
because
we
discovered
that
all
of
the
currently
active
contributors
were
either
west
coast
or
in
apec
yeah.
E
I
would
love
to
to
sunset
that
monday
night
meeting
then
officially.
A
Yeah
we
we
talked
about
it
and
I
think
it
was
just
going
to
either
send
a
message
to
the
list
was
the
last
action
item
from
that
or
confirm
with
some
of
the
current
mentoring
owners
sub
project
owners.
A
E
A
Okay,
now
with
that,
was
there
anything
else
for
mentoring
before
we
move
on
to
community.
F
So
we
are
at
the
second
revelation
of
who
is
google
form
of
code,
that
is
in
progress
this
week
and
we
are
at
the
second
and
the
final
relation
with
community
bridge
this
week
as
well.
Okay,
so
next
week
I
will
have
our
final
results.
We'll
start
having
our
financials
with
community
bridge
mentoring
and
we'll
have
some
intermediate
results
with
the
good
summer
code
as
well.
H
G
Okay,
okay,
so
we
had
a
mentoring
meeting
yesterday,
which
we
realized
was
actually
an
inconvenient
time
for
all
the
people
who
actually
were
attending
and
that
the
people
for
whom
that
time
was
convenient
were
no
longer
attending
the
meeting
so
expect
soon
on
the
mailing
list
and
email
about
changing
yeah.
The
time
of
the
mentoring
meeting.
E
A
F
D
F
As
far
as
I
know,
so
we
had
a
single
single
mentoring
meeting
before
splitting.
Today
we
have
two
meetings
and
one
of
them
is
focused
on
apec
and
other
ones.
F
And
the
issues
we
have
was
the
me.
F
A
We
we
we
have
a
new
meeting
for
the
new
contributor
workshop
already
scheduled
at
seven.
I
think
it's
at
7
00
pm
that
seems
to
be
working
out
for
the
people
from
apac.
We
will
send
something
to
the
list
regarding
updating
the
other
meeting
time.
You.
F
F
Another
option
is
to
eliminate
immediate
the
immediate
plus
plus
an
a
meeting
at
all
and
probably
having
like
a
small
10-minute
session
at
the
regular
contributor
experience
meeting
once
once
a
month
or
once
in
two
weeks
you
know,
probably
it
will
be
more
convenient
to
have
everybody
in
the
same
world
just
to
discuss
some
entry
and
stuff.
A
No
well,
you
know
at
this
point
we
will.
We
will
sort
that
one
out
later.
I
don't
want
to
spend
too
much
more
time.
Talking
about
you
know,
trying
to
schedule
a
meeting,
so
the
next
community
management
on
the
need
to
know
chairs
email,
there's
a
couple
items
the
note
regarding
working
groups
that
one
is
currently
on
there.
Oh
actually,
both
those
items
are
currently
slated
to
go
out
probably
later
today.
So
this
is
regarding
the
working
group
annual
reports
and
the
unconscious
bias
training
for
leads.
A
Okay,
let's
see
there,
it
doesn't
there's
an
apac
coordinator
update
and
I'm
assuming
that's
a
parasite.
Don't
forget,
shout
outs,
we'll
include
that
one
in
there.
A
Okay,
github
management.
The
big
thing
is
that
we
did
our
first
round
of
the
org
cleanup
and
that
went
well.
No
real,
immediate
follow-up
items
at
this
point
in
time.
Gwen
is
actually
going
to
be
like
I
had
a
little
bash
script
that
automatically
did
the
like
did
all
the
commits
and
everything
for
removing
people.
Gwen
is
actually
going
to
be
rewriting
that
in
something
more
sustainable,
go
and
they'll,
probably
that
will
probably
start
happening
soon-ish
next,
we
are
very,
very
close
to
deprecating
incubator.
A
In
fact,
it
might
actually
happen
by
the
end
of
the
week.
It's
only
been
an
open
issue,
since
I
think
2018
try
like
as
a
high
priority
issue,
but
but
but
we're
getting
there.
I
got
the
word
from
external
storage,
that's
good
and
it
cute.
Yes,
it's
being
spun
out.
You
might
have
seen
the
thing
going
to
the
list.
A
Okay,
that
takes
us
to
dev
stats.
I
laurie,
I
know
couldn't
make
it.
I
don't
think,
there's
any
update
on
that
one
at
this
point
in
time.
G
So
we
had
a
meeting
on
monday
and
the
one
of
the
things
that
came
out
of
that
is
we're
going
to
be
working
on
identifying
which,
which
existing
graphs
and
charts
with
parameters
are
the
most
useful
to
the
personas
that
we
care
about,
starting
with
sig
leads
and
using
those
to
compose
custom
dashboards
for
the
contributor
site.
G
A
Cool,
have
you
sorry
excuse
me
talking
to
lucas
yet.
A
G
The
we
might
end
up
doing
some
things
with
specific
charts
to
make
it
easier
to
embed
them,
because,
ideally,
what
we
want
is
people
to
be
able
to
go
to
pages
and
contributor
site,
see
the
charts
without
having
to
jump
out
to
dev
stats.
G
Yeah
the
and
I
think,
there's
a
few
where
there's
like
multiple
different
charts
on
one
page
that
might
be
harder
to
embed,
in
which
case
we
might
end
up
working
with
lucas
on
that.
A
Okay,
is
there
anything
that
you
any
other
anything
you
need
from
the
group
at
large,
or
you
know
if
you're
interested
in
this
just
go
to
the
meetings.
G
Yeah
go
to
the
meetings
and,
to
the
extent
that
anybody
you
work
with
within
the
project
says
something
about
dev
stats
or
things.
They
would
like
to
know
about
the
contributors
that
they
work
with.
Then,
please
forward
it
to
us.
I
mean
our
biggest
challenge
in
dev.
Stats
remains
getting
concrete
feedback
on
what
information
people
actually
need.
G
A
Oh
thank
you,
for
that.
Are
there
any
other
questions
for
devstats
and
discussion
for
destats.
A
So
we'll
we'll
move
it
over
to
contributor
documentation,
contributor
guide,
no
real,
updates
there
developer
guide.
How
are
things
going
for
you
eric.
I
Pretty
good
I've
been
I've,
been
pretty
deep
in
the
developer
guide
and
I've
got
like
one
section
left
to
rewrite
and
should
have
a
pretty
big
pr
on
friday.
I
think.
I
A
I
I
love
this
kind
of
work,
it's
fun
for
me.
It's
like
easier
than
coding,
but
and
way
easier
than
you
know,
writing
marketing
copy.
A
A
Okay,
so
that
takes
us
to
open
discussion.
Let's
see,
don't
see
any
new
contribution
line,
so
I
can
pass
that
we
talked
about
orbit
earlier.
The
one
thing
I
want
to
bring
put
on
people's
radar
is
the
issue
triage
cap.
A
This
is
mostly
for,
I
think
the
the
contributions
leads
to
get
into
a
good
state,
but
we're
now
at
a
point.
This.
A
Over
some
of
the
labels
that
we
use
like
in
kubernetes,
kubernetes
and
adding
a
label
like
needs
triage
to
all
the
incoming
issues
and
we're
sort
of
now
in
in
the
point
in
between
releases,
where
it'd
be
a
great
time
to
push
forward
with
it,
we'll
we'll
see
if
we're
able
to
make
it
happen.
But
I
know
people
are
interested
in
it.
A
If
you
have
any
questions
or
comments
about
that,
please
feel
free
to
or
please
check
out
the
cap,
and
we
will
need
to
follow
it
up
eventually,
with
both
updates
to
our
documentation
and
likely
plenty
of
comms
to
things
like
kdev,
twitter
and
all
that
other
fun
fun
stuff.
Regarding
the
potential
workflow.
A
A
A
Okay,
we
actually
blitzed
through
that
pretty
quick
this
week
with
that,
I
can
give
you
a
half
an
hour
of
your
day
back.