►
From YouTube: ContribEx Bi-Weekly Update 20191023
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
Let's
get
rolling
then
hello,
everybody
and
welcome
to
the
October
23rd
edition
of
contributor
experience.
My
name
is
Elfie
Phillips
and
I
will
be
moderating.
The
call
today
I'd
like
to
welcome
any
new
contributors
new
visitors
to
this
call
if
we
have
any
and
invite
them
to
introduce
themselves
if
they
are
interested.
B
D
E
D
A
C
Was
awesome,
the
traffic
is
still
growing,
even
though
it's
not
growing
like
geometrically.
So
that's
good.
We
had
about
150
live
people.
This
time,
I
haven't
looked
at
the
tail-end
numbers
recently,
we
are
on
break
for
this
month
because
of
Q
Khan
and
one
person
Chris
McCarty,
who
joined
the
project
via
office
hours
is
speaking
at
Q
Khan.
So
that
makes
me
happy
that
people
are
are
nice
doing
other
stuff
once
they
do
office
hours?
C
C
We
could
do
it
now
whatever,
so
we
had
like
nine
people
this
week
and
it
was
kind
of
like
at
some
point
I
was
like.
Are
we
wasting
other
people's
time?
Now
we
had
one
sig
once
it
showed
up,
one
sig
said
they
were
gonna,
show
up
and
didn't
show
up,
and
then
the
third
signera
responded
to
any
of
the
hosts
queries.
C
So
Josh
had
opened
an
issue
on
this
and
github,
because
the
kind
of
viewership
had
been
declining
over
time
and
the
issue
is
like
do
we
want
to
do
anything
about
it?
I
had
I
had
mentioned
it
in
in
Psych
and
I
think
Parris
you'd
mentioned,
maybe
bringing
it
back
to
like
bi-weekly
or
maybe
once
a
month.
C
C
Yeah
cuz,
we
asked
the
release
manager
to
come
and
that's
like
an
important
bit
for
them
so
like
we
want
to
make
it
useful
for
people.
So
I
was
thinking,
maybe
monthly,
starting
in
January.
That
gives
us
cig
when
you're
host
you'll
know
a
month
in
advance.
That
gives
you
a
whole
month
to
bother
a
cig.
They
can't
like
make
any
excuses.
What
point.
D
C
So
I
haven't
looked
at
that,
yet
so
I
think
what
we
do.
If
you
look
at
the
numbers
once
we
do
that,
we
might
consider,
because
that
means
I
think
we'd
have
to
have
like
six
updates
per
meeting
yeah.
So
what
I
was
thinking
is
this.
We
don't
really
have
been
using
the
demo
slots
effectively.
You
could
go
to
at
least
for
a
month
and
then
maybe
what
we
do
is
rotate
through
the
SIG's
first
issue,
because
they
have
they
have
like
the
governance
requirement
and
a
working
group
is
technically
supported
by
two
sig.
C
D
C
I'm,
hesitant
to
add
demos
back
unless
they're,
like
Core
related
I,
feel
like
giving
their
ten
minutes
for
everyone
to
do,
even
though
it's
open
source
like
an
open
source
product
page,
that's
fine
but,
like
you
know,
asking
the
release.
Manager
sig
leads
to
come.
I
think
we
should
just
like
keep
it
to
business,
I
guess
unless
people
think
that
they're
fun
and
they
break
up
the
monotony
of
a
meeting
and
they
love
them
as
anybody
like
absolutely
crazy
about
the
demos
and
loves
them.
Are
you
just
like
the.
F
D
C
C
D
Yes,
that
is
where
I'm
spending
the
majority
of
my
time
you'll
hear
in
future
updates
when
I
say
no
time,
we
are
live
with
contributor
summit,
we
are
streaming
live
or
so
live
we're
already,
starting
on
the
note
before
you
go
in
faux
meaning
for
attendees
and
staff
and
everybody
that's
involved,
we're
already
starting
to
get
that
together.
The
schedules
live
check
that
out
I'm
in
the
middle,
putting
links
in
the
agenda
right
now
so
schedule.
Also
Sunday
night
has
also
started
to
shape
up,
which
is
cool.
D
We've
signed
some
contracts
with
karaoke,
so
we'll
have
cig
late
night
present
on
Sunday
night,
which
will
be
super
cool.
What
else
did
I
want
to
say
about
it?
We
have
roughly
a
220
current
contributors
signed
up
right
now
we
still
have
room
for
another
hundred,
so
if
anybody
is
going
to
any
cig
meetings
this
week,
please
put
that
on
agendas.
If
you
don't
see
it
on
agendas
already
and
that's
about
it,
stuff
is
shaping
up.
So
we're
super
pumped
and
I.
Think
countdown
is
like
20
days
or
something
so
yet
minutes.
A
D
D
For
chairs
for
need
to
know
this
week,
I
have
contributor
summit.
Of
course,
they're
gonna
get
that
info
until
forever,
because
we
run
three
contributor
summits:
a
year,
uh-huh
contributor
summit,
building
a
triage
team
which
I'm
gonna
also
table
for
later
to
talk
about.
Why
I
have
that
on
there
and
then
also
a
couple
of
different
conformance
things
went
out
this
week
for
chairs
that
they
need
to
be
aware
of
that
were
high
level
and
very
important
in
the
conformance
world.
I
D
And
they're
going
in
there,
I'm
gonna
link
to
ours
and
I'm
also
going
to
link
to
the
cluster
lifecycle,
rooming
document.
Oh
we
can.
We
can
talk
about
it
now
if
you
want
or
we
can
table
it
open
mic,
but
there's
an
open
issue
right
now
with
Tim
Sinclair
talking
about
PRS
and
things
like
that,
though,
we
need
to
get
some
attention
too,
but
the
reason
why
I'm
putting
build
triage
team
there
is
to
address
a
lot
of
those
concerns
right
now
that
the
community
is
having
with
large
issues
and
large
PRS.
That's
it
stale.
D
So
that's
the
that's
kind
of
what's
going
on
there
and
what
I'm
trying
to
do
as
well
on
the
contributor
experience
side
is
build
out.
Our
triage
team
get
their
role,
books
done
and
then
what
they
and
then
what
other
six
could
do
is
essentially
take
that
as
a
template
and
then,
like
the
cluster
life
cycle
group,
has
a
grooming
dock
that
we're
gonna
fork
as
well.
D
D
So
I
don't
know
Jonas
if
you
have
any
cycles
or
if
anybody
on
the
call
right
now
has
cycles
to
work
on
this
lengthy
issue,
specifically
in
here
the
one
that
sit
that
I
just
referenced
about
Tim
and
the
PRS,
so
there's
kind
of
a
couple
of
different
things
that
need
to
happen.
One
is
the
PRS
that
are
old
need
to
be
addressed
now
and
then
two
at
a
meta
level.
How
can
we
have
this?
D
J
Pasted
it
in
there
too,
but
I
actually
get
I'm
happy
to
work
with
whoever's
interested
about
that
thing.
With
him
setting
up
an
unconference
at
the
summit,
I
think
it
could
be
a
really
good
way
for
people
who
are
interested
in
getting
involved
with
the
project,
but
not
sure
where
to
start
or
how
to
contribute.
If
there's
someone
a
point
of
contact,
I
could
get
in
touch
with
to
secure
space
for
it
and
someone
I
could
talk
to
about
getting
it
on
the
contributor
site
schedule.
D
Know
we
just
have
to
the
thing
with
the
unconference.
Is
that
folks
vote
on
it?
So
yes,
I
definitely
want
to
see
this
as
and
that's
kind
of
what
I
said
to
Tim
is
I'd
like
to
see
this
go
out
for
a
vote
and
this
being
like
PR
hygiene
in
general,
because
that's
a
little
different
than
issue
hygiene,
just
a
tad
I,
think
not
too
much
but
I.
Guess
when
you're
talking
about
like
provable
rights
and
things
like
that,
it
is
different
and
merge
rights
so
know.
D
Josh
asked
in
chat,
I
thought
we
already
had
a
triage
project
know
we
have
triage
project
for
contributor
experience,
but
not
for
other
things.
Don't
necessarily
have
that
and
then
contributor
summit
yeah,
let's
so
I'd
like
for
you
to
propose
that
at
the
contributor
summit
and
I,
don't
think
mark
he's
on
the
line
now
Marquis
running
the
on
conference,
so
I'll
give
marki
ahead
South
that
we
probably
already
have
one
comment
or
one
suggestion:
that's
going
to
come
down
the
pipeline
and
then
yeah.
D
K
So
real,
quick
Python
as
far
as
triage
team
is
concerned
for
contributed
experience,
something
we
already
have
a
list
four
or
five
active
members
there
right.
So
that's
pretty
much
the
team
I
guess
anybody
can
still
be
part
of
it
and
you
know
I
just
put
the
slack
channel
that
we
created
just
for
triage,
so
I
know.
Anybody
would
like
to
join
those
discussions.
K
F
F
A
Well,
that
is
so
awesome.
Thank
you,
Bob
for
working
on
that
and
for
that
update.
Does
anybody
have
any
questions
for
him
about
that.
F
D
Have
a
meeting
today
so,
if
anybody's
interested
in
contributor
documentation
holler,
but
this
is
an
area
that
is
definitely
I,
feel
like
getting
some
real
of
from
Markey
and
a
future
outreach
intern
from
the
dev
guide
perspective.
D
We
do
have
a
ton
of
issues
right
now
within
Kay
community
that
our
deaf
guy
related
it
needs
extra
extra
love.
If
anybody
on
the
call
has
extra
cycles
this
week
and
wants
to
do
some
or
triage
and
content
creation
for
dub
guide
stuff,
it's
there
for
you
happy
to
review
and
I'm
sure
others
on
the
call
would
as
well
and
that's
pretty
much
it
as
far
as
what
I
have
I
know.
Other
owners
are
on
the
line
as
well.
Does
anybody
have
any
other
updates
for
contributor
documentation
for
what
y'all
are
working
on.
F
C
A
H
D
Should
use
some
of
the
brute
mentorian
tactics
that
we've
been
using,
which
is
set
them
up
with
another
slack
channel
if
they
want
they
can
be
private
and
the
reason
why
it's
private?
It's,
because
people
feel
that
they
can
ask
dumb
questions
and
I.
Don't
say
that
forum
enables
perspective
I'm,
just
saying
that
from
other
quotes,
and
that
seems
to
happy
working
and
then
have
everybody
start
on
the
same
level
and
then
give
them
the
community
membership,
MD
doc
and
say
hey
if
you
want
to
get
to
reviewer
status.
H
E
D
H
D
Think
there's
like
a
lesson
learned
here
is
that,
like
when
you're
explicit
and
you
ask
for
contributors,
you
usually
get
them
and,
like
I,
see
it
on
the
mailing
lists
all
the
time
to
like,
with
my
belt
often
and
with
six
storage
and
with
cluster
lifecycle
like
when
they
just
go
out
to
their
mailing
lists
and
say:
hey
I
need
X,
Y,
&,
Z
and
I'm
gonna
do
XY
and
Z
for
you.
Then
they
usually
get
what
they
want.
Like
we
talked
about
this
in
staring
at
a
meta-level
the
other
day
where
it's
like.
D
How
can
we
get
all
SIG's
to
kind
of
do
that?
But
that's
also
asking
a
lot
because
tasking
out
work
and
in
itself
is
extremely
hard,
so
any
n,
so
I
don't
know
if
anybody
has
ideas
and
wants
to
work
around
this
kind
of
a
thing,
but
it's
it's
definitely
an
open-ended
topic
that
needs
to
get
worked
on.
It's
not
even
a
technical
barrier.
L
F
L
D
Didn't
want
to
get
a
better
resolution
to
this,
because
it
is
like
it's
the
large
triage
issue
that
I
talked
about.
We
were
talking
about
and
like
building
a
teeth,
building
teams
and
things
like
that.
But
I
didn't
hear
anybody
on
the
line
that
is
interested
in
kind
of
working
on
this
stuff
or
if
you
have
any
extra
cycles
now
or
if
you're
interested
but
like
post
cube
con
I
wanted
to
see
if
we
could
try
to
get
this.
D
C
D
D
Well
I'll,
maybe
maybe
you
can
help
out
with
the
front
end
of
like
figuring
out
what
SIG's
some
of
these
issues
below
and
like
treat
we'll.
We
can
treat
triage
together
the
some
of
the
like
the
super
super
old
ones,
just
to
get
some
attention,
and
then
we
can
work
on
the
meta
issue
later
post
cube
con,
so
I'll
pin.
F
D
All
right,
groovy,
one
more
thing:
no,
oh,
my
god,
literally
it's
the
contributor
survey.
I
am
logging.
The
questions
into
Survey
Monkey
today
on
there
pretty
much
just
locked,
as
is
based
off
of
that
issue.
I've
worked
through
all
of
the
comments
on
the
actual
subject
matters
and
then
I
will
send
a
link
to
the
slack
Channel.
They
get
some
beta
testers
and
some
people
to
look
at
the
actual
grammar
and
things.
Hopefully
we
can
go
live
next
week
with
the
survey.
That's
it
great.