►
From YouTube: ContribEx Weekly Update 20191204
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).
D
B
D
Workstation
we're
doing
some
fun
stuff.
There
I've
met
a
lot
of
you
folks
at
the
contributor
summit
at
kook
on
the
other
week,
I
work
with
Jonas
a
little
bit
and
I
also
support
I
work
on
project,
often
so
I'm
just
looking
to
do
more
in
the
community
and
seem
like
a
really
great
opportunity
to
pitch
in.
E
F
F
B
B
H
I'm
here,
but
I'm
not
sure
I
have
an
update,
dad
I
made
playbooks
for
my
part
of
the
event:
George
merged
them
yesterday,
despite
having
typos
and
things
so
I'm
gonna,
I'm
gonna
go
and
probably
iterate
on
that
in
the
next
like
autumn
after
the
releases
out
or
something
I,
don't
know
yes,
there's
there's
this
person
in
charge
of
the
release
and
she's
super
mean
and
won't.
Let
me
sleep
and
stuff.
It's
like
it's
terrible,
yeah.
G
H
It's
it's
super
crying
I
with
some
of
these
things
with
him
like,
let's,
let's,
let's
not
what's
that
called
anyway,
yeah
cool.
C
That's
my
update
things
like
that.
The
other
bit
of
the
events
update
is
that
we
had
the
retro
for
the
contributor
summit
at
the
last
to
well.
It
took
us
two
meetings
to
get
there
at,
but
we
got
there
out
there
I'm
a
whole
bunch
of
action
items,
so
people
can
see
the
notes
for
details.
The
other
update
I
think
is
that
G
fees,
the
lead
for
the
contributor
summit
for
Amsterdam
and
he's
in
the
process
of
putting
together
the
team
now.
B
G
Is
there
a
specific
part,
I
mean
like
I,
guess
we
could
do
the
notes,
and/or
the
meetings
and
stuff
so
community
meeting
is
set
for
this
week
and
next
week
next
week
is
gonna,
be
the
retro,
so
we're
pushing
those
things
out
so
marki
sent
the
emails
to
the
right
people.
I
do
need
to
send
an
email
that
I'm
planning
on
sending
on
Monday
to
kind
of
remind
everybody
hey
for
2020
we're
gonna
change
the
cadence
down
to
once
a
month
and
kind
of
get
people
going
with
that
meter.
Contributors
was
awesome.
G
This
morning
we
had
about
46
concurrent
people
about
a
hundred
and
fifty
uniques.
This
morning
we
had
Kelsey
and
Taylor
on,
and
that
was
those
pretty
fun
thanks.
Those
of
you
that
participated
and
office
hours
is
next
week,
and
that
is
gonna
close
this
up
for
2019
and
I.
Think
that's
pretty
much
it
for
community
management,
Gwen.
H
G
H
B
G
G
So
this
is
something
I
did
wanted
to
bring
up
to
the
other
group
kind
of
just
like
a
heads
up
to
tell
people.
It
will
be
very
benefit
of
moderators
for
slack
for
a
while
now
and
especially
in
Europe
and
Asia.
It
would
be
really
useful
to
get
more
folks
on
board
and
ask
maybe
people
who
have
been
doing
it
for
a
year
to
cycle
out
and
then
come
back
in
a
year.
G
I'm
really
trying
to
avoid
having
you
know,
contribute
is
always
responsible
for
this,
this
this
and
this
all
of
us
all
the
time.
So
if
we
do
like
three
people,
I
could
rotate
out
this
year
for
six
months
or
whatever
it
works.
So
if
you've
got
co-workers
or
something
that
are
looking
to
contribute
to
something,
but
don't
really
have
time
but
have
to
sit
on
slack
for
work
anyway,
it
will
be
really
useful,
especially
in
Asia
Pacific.
G
G
They
could
just
ping
me:
I
have
a
whole
page,
I
love
a
page
in
the
community
repo
on
how
to
be
a
moderator,
and
things
like
that.
We
just
did
moderator
training
and
all
that
stuff,
so
we'll
have
to
sort
we'll
have
to
sort
how
we're
gonna
do
code
of
conduct,
training
and
all
that
stuff
to
onboard
new
people,
but
I
think
I'm,
not
sure
I.
G
B
G
I
think
this
is
me
and
Gwen:
I
went
through
I
went
through
a
bunch
of
github
stuff
last
night
and
found
some
I'm
gonna
need
help
with
a
translation
to
him
be
for
the
contributor
cheat
sheet.
I,
don't
have
it
in
front
of
me,
but
I
just
basically
pinged
them
asking
them
for
it.
G
But
the
biggest
thing
we've
added
recently
that
I
remember,
is
that
Jeff
and
another
new
person-
I'm
sorry
I
forgot
their
name
has
been
working
on.
This
is
adding
how
to
add,
release
notes
to
PRS
when
doing
like
the
case,
the
contributor
workflow.
So
that's
definitely
one
of
those
is
landed.
I
think
the
second
one
is
still
being
PR.
I
need
to
look.
We.
H
Don't
have
an
update,
but
I
have
an
opinion
go
for
it.
So
when
Lachlan
and
I
did
a
talk
at
coop
con
about
the
release
team
shadow
program,
I
had
sort
of
started,
realizing
that
that
is
how
mentoring
needs
to
look,
or
that
is
one
of
the
ways
in
which
we
need
to
implement
it.
And,
of
course
it
doesn't
look
the
same
as
it
would
on
the
release
team,
but
I
think
what
we
can
do
as
a
cig
is
to
encourage
other
SIG's
to
push
more
towards
you
interactions
and
I.
H
My
tentative
plan
is
once
I
drop
the
release
to
like
vanish
a
bid
from
seek
release
because
I
think
stake
release
is
doing
an
amazing
job
at
onboarding.
People
like
completely
amazing,
there's
like
a
paved
path
for
everyone
and
I'm
going
to,
but
obviously
I
was
just
gonna
join
another
cig
and
see
what
I
can
do
there,
because
it'll
have
to
look
different
in
them
like
more
technical
stick,
but
here's
the
thing
release
engineering
also
has
a
shadow
process,
so
it
works
for
them.
It
seems
silly
anyway
and
I
know.
H
I
The
the
big
challenge
there
and
I
talked
to
some
other
people
about
this.
He
is
coming
up
with
narrowly
scoped
tasks
for
cig
work
right.
The
nice
thing
about
release
and
about
events,
and
that
sort
of
thing
is.
We
have
all
of
these
jobs
that
have
a
specific
length
of
time
and
a
specific
set
of
duties
and
coming
up
with
that
force.
A
signet
working
is
a
lot
harder.
I
am.
H
Thinking,
one
of
the
things
to
do
is
I
one
of
the
things
that
really
that
this
won't
work
for
everyone,
but
the
more
ways
we
have
for
people
to
get
involved
the
better
right,
because
it's
not
going
to
work
for
every
personality
type.
But
what
I
was
thinking
is.
We
could
encourage
six
to
maybe
group
review.
Pull
requests
have
new
folks,
look
at
like
pull
requests,
but
do
it
together
and
then
have
the
overall
reviewer
who
actually
has
more
context
kind
of
be
available
for
questions
little
Alison
hi.
Sorry,.
F
Okay,
I
actually
have
a
document.
We
used
to
do
something
called
zoom
code
reviews
resume
reviews.
It
was
required
for
every
review.
I
have
I,
have
the
document
that
explains
how
to
do
it.
If
you
want
I
had
to
ask
the
guy
to
make
sure
he's,
okay
with
it,
but
he's
a
big
open
source,
proponent,
so
I'll
just
say:
hey
Jay,
you
mind
if
I
borrow
this
for
kubernetes.
J
F
G
F
G
F
Can't
see
why
he
would
say
no,
but
it's
it
was
really
helpful
and
it
really
reduced
a
lot
of
bugs
at
the
same
time.
But
it
was
a
really
good
way
to
onboard
junior
developers
onto
the
team
that
we
were
working
on.
So
I
will
find
it
for
you,
yeah.
H
Yeah,
that's
that's
like
one
idea
that
I've
had
for
that.
So
I'm
glad
I'm,
not
the
first
one
with
this
idea,
so
that
probably
means
that
we
can
more
easily
convince
others
to
be
on
board
yeah.
So
I
am
yeah
I'm.
It's
just
that.
I
have
looked
at
like
how
far
I've
come
in
the
last
two
years
since
becoming
a
contributor,
and
what
made
the
difference
for
me
between
me
and
some
of
the
folks
that
I
see
at
the
new
contributor
workshop
and
the
difference
is
mentoring.
H
I've,
gotten,
amazing,
mentors
and
part
of
that
is
because
I
just
asked
for
it
and
because
I
show
up
and
make
mistakes
and
people
are
like
no.
This
is
how
we
do
things
and
that's
again,
not
everyone's
style,
but
the
more
we
can
do
that
for
more
people
right.
Not
everyone
feels
comfortable
speaking
up.
Not
everyone
is
like
lucky
enough
to
feel
safe
about
speaking
up
so
and
that's
not
how
mentorship
is
supposed
to
work
right.
You
shouldn't
have
to
manage
upwards.
H
B
B
H
Cichlids
aren't
reading
their
emails
at
all,
like
I,
will
post
a
screenshot
in
channel
to
see
what
the
last?
What
like
there
is.
Not
even
that
many
posts-
and
there
is
the
yeah
sig
leads,
aren't
reading
it.
I
have
visual
evidence
of
the
read
receipts
on
that
list
and
I'm
going
to
post
it
publicly
and
second
term
X,
channel
and
I
think
the
next
step
is
publicly
shaming.
H
The
sig
leaf
part
of
every
six
Charter,
as
I
learned
earlier
I,
was,
like
literally
I,
was
sending
out
a
reminder
for
poor
Chris
who's,
doing
release,
notes
and
can't
get
an
answer
from
SIG's,
which
is
super
uncool
and
I'm
like
okay.
So
is
this
even
the
way
that
sig
leads
communicate?
I
wasn't
sure.
I
was
like
this
looks
really
dead
in
here.
Is
this
still
the
official
way
and
so
either
you
know
or
it's
it's
possible
that
the
read
receipts
are
wrong.
H
C
G
H
H
G
H
A
G
Have
been
conversations,
that's
theory
has
been.
Having
is
how
to
carrot-and-stick.
Sig
co-chairs
all
SIG's
need
API
reviews
right,
usually
mostly
so
like
if
you're
not
meeting
your
transparency
requirements.
You
know,
maybe
that's
a
that's
a
valve
that
gets
squeezed
a
little
bit,
but
I
don't
think
it
ever
went
past
discussion
stage.
I
think
that
it
is
a
problem.
I
mean
Paris,
isn't
here,
but
you
know
she's
written
newsletters.
We've
continually
had
people,
you
know
even
a
contributor
summit
who
bob
has
to
chase
down
hey
you're
a
co-chair
you're
supposed
to
register
mutsig.
G
I
G
H
G
And
more
noise
doesn't
exactly
help
either
right,
like
they
have
their
own
slack
channel
right,
there's
a
leads,
it
is
chairs
and
tech
leads,
and
if
you
read
them
a
lot
of
it
is
the
same
stuff
that
you'll
see
posted
on
the
development
mailing
list
as
well.
K
J
C
H
E
B
H
X,
including
like
I,
don't
know,
I
released
me,
my
not
my
big
stick
is
a
big
fat,
or
else
you
know
it's,
but
at
the
same
time
you
know,
maybe
the
consequence
should
be
well.
H
G
H
The
thing
about
a
mailing
list
is
it's
easy
for
me
to
use
when
I'm
hunting
down
people
for
an
issue,
I
have
to
like
look
at
their
github
handle
and
I
have
to
find
their
name
on
slack
like
their
smile
and
I'll,
send
them
a
DM
fine
which
sig
they
belong
to.
It's
this
whole
like
20
minute
process.
It
takes
a
long
time
sending
out
a
post.
Sending
out
a
blast
to
the
mailing
list
is
easy
by
comparison.
E
H
If
you
have
like
the
entire
relief
release
team,
which
is
like
roughly
30
people
and
you
invite
and
you
would
invite
all
of
them
individually
with
their
primary
and
secondary
email
to
a
calendar
even
or
you
have
a
mailing
list
and
it
just
works,
so
it
it
just
anyway,
I
I,
think
I,
think
I
think
we
just
don't
have
any
consequences
and
people
are
just
like
well,
it's
fine
I
mean
I
experienced
this
with
another
situation
and
we're
releases
kept
slipping
because
scalability
wasn't
responsive
mm-hmm
and
it
turned
out
with
that.
H
G
So,
let's,
let's
think
about
some
solutions
here,
because
so
obviously
I
think
we're
gonna
need
to
surface
this
in
the
release,
retro
right
as
a
problem
and
then
like.
How
do
we
approach
the
leads
for
this?
Do
we
need
it?
Do
we
need
to
send
the
uncomfortable
email
to
the
developer
list
like
because
I
feel
if
it
was
just
contributor
experience,
saying
hey
no
one's
responding
to
our
thing?
They're
gonna
say
you
know
what
they
just
want
me
to
show
the
community
meeting.
G
That's
not
important
for
me,
but
if
we
release
were
to
say
well,
look
if
we
don't
start
getting
responses
for
people,
we're
just
gonna
start
necky
knacking
your
merges
are
something
like
is
there?
Is
there
like
a
carrot
that
you
could
say
because
I
mean
this
kind
of
stuff,
I
feel
kind
of
lands
in
our
purview
right,
I,
don't.
F
E
G
It
just
to
be
in
the
org.
You
have
to
be
subscribed
to
the
developer
mailing
list
and
I
know
for
a
fact,
a
lot
of
times
when
people
we
send
messages
and
stuff
like
that,
like
Bob,
is,
went
and
looked
and
seen
that
the
list
of
people
who
register
for
contributor
summit,
a
lot
of
who
are
supposed
to
be,
or
you
know,
a
lot
of
our
missiles
for
your
grammars
and
stuff
like
we
find
out,
aren't
subscribed
to
developer
list
and
they
might
be
a
co-chair
or
things
like
that.
So
I.