►
From YouTube: ContribEx Bi-Weekly Update 20191009
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
Hi
everyone
welcome
to
October
ninth
edition
of
contributor
experience
thanks
for
giggling
with
me
for
the
first
five
minutes.
Today
we
have
a
regular
agenda
meeting.
If
you
are
on
the
call
right
now.
Please
put
your
name
on
the
agenda.
I
will
lazy
link
the
agenda
in
chat
right
now,
one
second,
all
right.
As
always,
we
have
a
code
of
conduct.
Please
be
excellent
to
each
other,
since
there
are
so
many
of
us
on
a
call
make
sure
you
try
to
either
raise
your
hand
or
say
in
chat
that
you
have
something
to
add.
A
So
we
can
get
to
you
I,
don't
believe,
there's
any
new
contributors
on
the
call
right
now,
nope
I,
don't
see
any,
which
means
we
have
our
regular
show
hello,
regular,
show
and
then
to
get
any
two-hour
stand-ups.
First
we
do
events.
Then
we
go
to
a
mentorian
community
management,
github
management,
if
any
of
those
sub
project
owners
or
anybody
in
any
of
those
sub
projects-
is
on
the
line
right
now
and
has
updates
in
those
sections.
A
C
D
Don't
judge
all
right
so
real
quick,
we
didn't
meet
our
contributors
last
week.
I
just
wanted
to
mention
that
we
switch
over
to
the
event
thing.
That's
more
workflow.
Most
of
you
don't
care
for
office
hours
is
going
to
be
our
last
office
hours
until
keep
car
next
week,
so
we're
gonna
really
push
it
heavily
and
market
it.
D
D
So
Jonas
said
last
week:
mark
Marky
is
doing
this
week.
We
need
someone
for
next
week
and
then
Markie
signed
up
for
two.
If
we
could
get
some
more
different
people
than
the
usual
suspects,
I
think
it'd
be
great.
Also
if
you
can
help
us
reach
out
to
maybe
people
who
don't
do
this
effectively
I'm
kind
of
doing
the
work
for
them
in
the
background
anyway.
D
So
if
there's
someone
who's
too
busy,
but
might
be
a
good
personality
or
something
like
that,
if
you
have
any
co-workers
or
anything
like
that
that
want
to
get
in
there,
we
I
basically
kind
of
set
up
the
work
for
them.
They
just
kind
of
have
to
read
through
it.
So
if
you
could
think
people
that
are
kind
of
too
scared
of
the
commitment
or
whatever
like
feel
free
to
tell
them
well,
George
will
do
the
work
for
you
anyway.
D
A
So
contributor
summit
updates,
there's
a
blog
post.
That's
gonna
go
live
today.
If
I
can
get
my
images
get
skills
together
and
then
that's
also
going
to
go
with
several
outlets,
whether
it's
ke
dev
mailing
list,
whether
it's
Twitter
it's
gonna,
be
a
lot
going
on
there.
Best
thing
for
people
to
do
on
this
call
right
now
is
to
help
us
spread
the
word.
The
main
action
with
all
of
the
communications
today
is
to
check
the
schedule
and
register,
because
we
have
I
think
it's
less
than
100
tickets
left.
A
So
we
want
to
start
making
sure
that
we
have
some
of
our
major
maintainer
z'
there,
and
things
like
that,
so
that,
when
there's
on
conference
sessions
going
that
they
can
really
speak
to
the
subjects.
So
again,
everybody
on
this
call
once
that,
once
that
stuff
goes
out,
please
do
me
a
favor
and
get
that
out
to
your
networks,
especially
if
you
sit
in
other
SIG's
and
send
another
Sigma
teens.
A
The
easiest
thing
to
do
is
just
pop
that
on
their
agenda
and
say
hey,
you
don't
even
need
to
read
it
out
loud,
just
put
it
on
the
agenda,
and
that
would
be
awesome.
That's
it
for
contributor
summit
steering
committee
election
is
now
over,
so
we
do
not
have
to
record
on
that
anymore,
Bob
or
George.
Do
you
want
to
talk
about
anything
that
relates
to
like?
Is
there
the
retro
or
anything
to
wrap
it
up?
You.
D
D
Something
I
would
like
to
get
to
do.
I,
don't
know
if
Brian
grant
or
E
or
I
can't
speak
to
them
are
interested
in
doing
this
next
year,
but
I
definitely
want
to
get
new
people
in
from
contributor
experience,
learning
how
to
run
elections.
So
I
am
happy
I've
been
in
every
election
and
that's
fine
and
I'm
happy
to
shadow
and
help
someone,
but
I
think
it
really
helps
when
we
get
new
people
in
so
I
mean
I
just
want
to
start
the
conversation.
D
Now,
if
you're
interested
in
doing
the
election
stuff,
it's
really
rewarding,
it's
really
fun.
You
know,
I
can
help
talk
you
through
it
and
all
this
stuff.
But
I
would
like
to
get
someone
other
than
me
in
there
sometimes,
so
we
can
get
like
a
rotation
going
other
than
that.
Most
of
the
fixes
that
we
have
have
been
pretty
straightforward
and
they're
in
the
retro
I
mean
we
needed
a
new
email
address.
I
believe
that
in
the
future,
SIVs
won't
work
for
us.
D
One
of
the
things
I
want
to
talked
about
github
is:
is
there
a
way
that
we
could
just
have
like
a
little
github
app
that
connects
to
the
kubernetes
org
figures
out?
Who
all
the
members
are?
And
then
we
pick
a
you
know,
pick
a
threshold
instead
of
having
our
own
spreadsheet
with
emails
and
then
sending
people,
email
ballots
are
still
a
problem.
D
Like
in
their
three
date
like
I
suspected,
there
was
like
a
postfix
cue
that
someone
forgot
the
flood,
whatever
old
UNIX
crap,
like
you,
can
think
of
so
I,
just
like
to
move
us
away
from
email,
something
that
is
directly
tied
to
you,
know,
github
and
stuff.
So
I
think
it's
also
an
opportunity
for
someone
who
might
not
know
anything
about
kubernetes
but
knows
how
to
write
a
web
app
or
whatever.
D
B
D
D
E
Just
a
question
regarding
the
contributor
summits:
so
we
have
the
issue
of
building
the
Amsterdam
contributor
summit
team.
We've
gotten
a
bunch
of
comments
on
there.
People
singing
up
so
just
wondering
when
we're
gonna
move
forward
with
this,
because
there
is
no
date
set
or
anything
like
that.
So
just
a
general
question
I
think.
A
Jeff
is
gonna
move
forward
within
the
next
couple
of
days.
So
just
look
out
for
that
I
think
he
said
he
wants
to
get
a
small
core
team
together
and
then
proceed
with
the
strategic
planning,
but
I
can't
I.
Don't
want
to
speak
for
deaf
but
yeah
I'm
just
going
to
assume
in
the
next
week
or
so
for
sure.
Okay.
E
A
All
right
up.
Next
mentoring
meet
our
contributors.
We
did
indeed
have
it.
Last
week
we
had
a
large
crew
that
was
fun
next
month
is
November,
so,
yes,
we
will
do
it
for,
like
we'll,
do
a
pre
cubed
con
special.
If
anybody
on
the
line
right
now
is
interested,
I
think
I
have
Paul
Maury
and
about
three
other
people
that
are
coming
on
for
November,
but
again,
please
feel
free
to
come
on
anyone
and
then
also
in
regards
to
mentoring.
We
are
live
without
Ricci
now,
I
think
we
have
three
physicians.
A
Not
us
necessarily
contributes
contrib
ex
has
one
but
kubernetes
as
a
whole.
Has
three
projects.
Please
hang
out
with
us
and
outreach.
He
apps
that's
a
slack
channel.
That's
where,
for
those
who
aren't
familiar
with
outreach
Eva's,
the
potential
interns
need
to
make
a
first-time
contribution
as
a
part
of
their
application
process.
A
So
it's
kind
of
like
we're
doing
issue
triage
for
new
contributors
right
now
in
that
slack
Channel
and
would
love
help.
It's
pretty
much
standard
fare
as
far
as
giving
links
to
contributor
guide
and
telling
people
that
they
can
contribute
in
certain
places
when
they're
unsure
so
super
pumped
about
outreach.
He
is
well.
This
will
be
our
largest,
our
largest
class
to
date.
So
sorry,
yeah
no
go
ahead.
Mom
one.
A
For
sure
we've
had
that
around,
while
other
pqube
guns
as
well
so
yeah,
no
cool
any
questions
about
outreach
e
or
meet
our
contributors
and
then
a
quick
shout
out
to
mark
e2
who's
in
helping
with
some
mentorian
issue,
triage
I'm,
helping
us
to
break
down
some
issues,
because
we
have
some
just
floored
super
large
issues
in
there
that
need
to
be
broken
down
to
get
more
task
oriented
so
appreciate
that
Marky.
Thank
you.
A
They
are
still
discussing
about
organizing
a
webinar
targeting
8
APEC
time
zones
for
contra,
for
both
contributing
topics
and
consumer
base
topics.
If
you
are
interested
in
on
the
line
with
helping
that
crew
out
I'm
sure
they
would
love
it,
they
need
I
think
it's
actually
tonight
at
11:00
p.m.
Pacific.
A
If
you
are
of
that
late,
I,
don't
have
anything
right
now,
with
the
exception
of
contributor
summit
for
the
need-to-know
chairs,
email
and
tech
lead.
So
if
anybody
has
anything
else
outside
of
contributor
summit,
let
me
know
I'd
like
to
get
that
out
either
today
or
tomorrow.
If
so,
if
not
it'll
be
punted
until
next
Monday,
anybody
have
anything.
Maybe.
B
A
B
Essentially,
something
mail
out
earlier
this
week
about
cleaning
up
inactive
owners
from
KK
over
the
game's,
essentially
like
a
week
of
time
to
respond
and
there'll
be
like
nineteen
PDR
is
foot
touching,
fifty-five
owners
files
going
out
this
weekend
for
hopefully
get
it
emerged
by
the
end
of
the
week.
Some
will
actually
less
PRS
just
because
there's
been
a
couple
people
taking
care
of
it.
B
A
A
All
right
and
anybody
have
anything
for
the
get
Badman
team
questions
concerning
comments,
and
if
you
didn't
hear
one
more
time,
github
is
going
to
be
at
the
contributor
summit
they're
going
to
have
a
booth
and
they're
also
going
to
teach
a
session
on
navigating
conflict
and
github
code
reviews,
and
things
like
that.
So
that
should
be
a
decent.
That
should
be
a
pretty
good
fashion.
B
F
A
C
G
G
C
A
If
we
get
the
outreach
in
turn,
then
we'll
have
someone
to
help
with
content
creation
as
well.
So
that's
an
impossibly
evenly
release
team
stuff
that
was
brought
up
in
the
retro,
so
cheers
to
that
anybody
have
anything
else.
Oh
ferry,
they're,
working
on
that's
contributor,
guide,
our
contributor
documentation
related
or
have
any
blockers
or
discussions
with
anything
contribute
or
documentation
related.
A
B
That's
mostly
just
fixing
stuff.
So
that
way
it
renders
right
and
you
go
so
he
go
use
the
different
mark
done
renderer
than
github,
and
so
there's
some
things
that
you
know
it's
a
github
is
a
little
bit
more
forgiving
and
I.
Think
it's
Black
Friday
one
is
is
less
so
so
it's
just
fixing
some
things
like
spacing,
and
all
that
and
then
getting
in
the
automation
to
pull
stuff
in
from
external
locations
and
the
site.
B
A
I,
look
at
the
calendar
I
feel
like
we
might
have
a
meeting
put
on
contributor
documentation.
What
is
that
next
week,
maybe
horse
out
on
the
23rd?
Oh
yeah?
No,
that's
the
23rd.
Okay.
We
should
get
a
mailing
list
that
out,
then
that's
two
weeks.
So
what
we
should
do
next
is
either
chat
and
slack
or
a
mailing
list
about
the
next
steps
for
what
we
need
to
do.
A
A
H
D
H
D
Hey
so
I
was
only
on
the
kubernetes
podcast
from
Google
and
they
like
ambushed
me
and
they're.
Like
talk
contributor
experience
and
the
next
thing
you
know
like
the
next
day,
they
invited
me,
but
I
really
talked
a
lot
about
you
all
and
all
that
stuff.
So
you
got
a
chance
to
listen
to
it
and
give
me
feedback
on
what
I
could
do
better.
I
was
kind
of
like
talking
off
the
top.
D
My
head
and
like
I
might
have
missed
something,
or
you
know
said
something
with
the
wrong
level
of
detail
that
you
want,
but
I
would
appreciate
any
feedback
there.
You
know
I
figured
the
opportunity
to
talk
about
the
programs
that
we're
talking
about
and
how
people
can
get
involved.
Stuff
was
really
awesome.
So
if
you
ever
get
a
chance
to
get
on
there,
it
seems
that
they
cycle
around
to
contribute
experience
like
every
six
months
or
something
I.
Don't
remember
the
last
time
you're
on
Paris,
but
reach
out.
D
I
D
So
I
happen
to
have
a
call
with
Tim
about
this
during
our
one-on-one
on
Monday
and
it
feels
like
he
just
woke
up.
He
did
a
few
github
queries
and
he
was
like
really
sad
that
some
of
these
PRS
are
over
a
year
old,
some
of
them.
So
he
was
like
what
what
what
we
need
to
have
is
like
a
lifecycle
document
of
like
what
a
PR
goes
into.
D
So
you
know
someone
does
a
PR,
a
bot
says
you
know,
have
you
signed
the
CLA
or
whatever,
and
then
we
do
all
these
steps,
but
then
there's
nothing.
There's
nothing
in
there
that
really
says.
Okay.
This
PR
has
been
open
60
days.
Should
we
maybe
cast
wider
the
amount
of
reviewers
or
when
old,
fade
about
whatever
we
call
the
bot.
Now
you
know
it
tells
you
this
PR
hasn't
been
touched
in
30
days.
Do
life
cycle
stale?
Maybe
we
should
consider
something
like
this
is
just
ideas:
I
have
like
hey?
D
No
one
has
touched
us
for
30
days.
Have
you
considered
going
in
hash,
PR
reviews,
or
you
know,
going
to
a
cig
me
or
you
know,
maybe
adding
more
like
little
tips
and
the
life
cycle?
You
know
that
we
can
automate
in
a
way
that
at
least
lets
the
user
know
that
they
just
don't
have
to
sit
there
and
wait.
You
know
what
I
mean
be.
I
B
I
Requests
because,
like
like
it's
fine
for
us
like
I,
know
people
that
I
can
I
can
bug
to
get
in
lgt
em
on
something,
but
if
you're,
a
newer
contributor
or
if
you're
contributing
in
an
area
that
you're
not
as
familiar
with
the
people,
it's
it's
really
hard
and
they
do
just
sit
there.
I
mean
I've
got
a
I've,
got
a
pull
request.
That
is
literally
two
lines
and
is
completely
trivial.
That's
been
sitting
there
for
like
nine
days,
just
because
I
can't
get
the
big
lead.
Yeah.
D
Or
it's
been
30
days
and
then
it
like
goes
up
a
directory
and
then
pings
notice
owners,
but
then
in
my
head,
I
was
like.
Oh,
that
sounds
like
a
nightmare.
Everyone
at
the
top
level
of
the
tree
he's
just
gonna
get
crushed
so
like
I
was
thinking
about
just
drafting
a
like
a
little
Google
document.
That's
like
a
workflow
of
like
you
know,
user
does
PR,
which
should
happen
and
then
maybe
kind
of
skeleton
hang
out.
D
You
know,
okay,
what
should
happen
after
you
know
a
day
a
week,
30
days,
60
days,
90
days
or
because
right
now
it
just
says
you
know
it's
been
30
days
type
of
slash
command
to
not
get
bothered
again.
That's
what
I
feel
like
I
do
when
I
get
the
bot
right.
It's
like
just
leave
me
alone.
You
know
like
even
if
all
it
said
was
like.
D
A
Think
test
and
crook
has
like
a
sit
on
workflow.
That's
similar
to
that,
but
definitely
not
like
that.
But
I'm
saying
that
just
because
it
might
be
something
that
you
can
work
off
of
and
then
you
don't
have
to
build
it
from
scratch.
But
yeah
I
know
I
would
ask
in
their
chat
in
theirs
in
their
slack
because
they
might
have
something.
I
A
The
problem
with
triaging
pull
requests
is,
if
you're,
not
in
the
folder,
then
all
you're
doing
is
just
I,
guess
shepherding
and
like
nagging
people.
So
right
now,
no
they're
only
focused
on
issues.
I
mean
that's
something
that
we
can
actually
are
meeting
right
now,
that's
something
that
we
can
have
them
look
into,
but
you
know
they're
just
trying
to
get
it
together
for
issues
right
now.
Yeah.
D
D
So
I'm
gonna
start
drafting.
So
this
is
something
that's
gonna.
Take
a
lot
of
discussion,
a
lot
of
feedback.
I
know
you
know
Aaron
and
Christoph
and
Akita
wyeth
comments
and
stuff,
but
I
think
I'm.
Just
gonna
start
with
a
skeleton.
You
know
just
kind
of
you
know,
for
my
own
purposes,
to
figure
out
how
a
PR
workflow
works,
and
then
we
could
start
to
convert
I
figured
just
starting.
The
conversation
would
be
fine
because
he's
right,
some
of
those
old
PRS
are
just
outright
embarrassing
and
like
I,
don't
want
to
I.
D
A
D
B
A
D
A
A
Dox
is
doing
the
same
as
well,
so
we've
got
there's
a
couple
SIG's
that
are
like
trying
to
figure
this
out,
but
if
we
could
figure
this
out
of
a
wide
scale,
that
would
be
super
dope.
This
is
the
type
of
stuff
that
I
wish.
We
would
talk
about
a
contributor
summit,
so
I'm,
hoping
that,
like
some
of
those
on
conference
tickets,
get
taken
up
with
some
of
these
topics,
cuz.
That
would
be
great.
A
H
D
Yeah,
what
one
minor
thing
yeah,
if
you're
going
to
contributor
summit
I
realized,
we
don't
have
like
a
group,
slash
team
picture.
So
if
we
have
an
opportunity,
if
there's
like
a
five
minute
break
or
something
in
contributor
summit,
if
we
can
really
try
to
get
an
effort
to
get
everybody
in
and
if
one
didn't
make,
it
will
Photoshop
them
in
or
something
but
like
working
on
a
talk
and
I
really
wanted
to
talk
about
how
great
this
is
and
realized.
We
don't
have
a
picture
well.