►
From YouTube: monthly contributor-docs subproject mtg
Description
monthly contributor-docs subproject mtg
A
Right,
hello,
everyone,
my
name
is
Paris
today's
January
22nd.
We
are
running
the
sub-project
meeting
for
contributor
experience,
contributor
experiences,
contributor
documentation,
which
is
a
key
area
for
the
project.
What
we
usually
do
during
this
meeting
is
go
through
a
project
form
that
has
some
issues
that
are
labeled
with
contributor
documentation,
kind,
documentation,
kind
of
cleanup,
etc
from
the
community
repo
make
sure
that
things
are
being
addressed
or
her.
Someone
has
a
cycle
or
we
tell
the
triage
team
to
to
either
like
cycle
frozen
it
or
something
along
those
lines.
A
We
do
have
new
folks
with
us.
I
know
Bart.
This
might
be
your
first
meeting,
but
at
this
group
and
then
some
real
draw
I
think
this
might
be
your
first
meeting
of
this
group
as
well.
So,
instead
of
doing
the
project
work
first,
do
you
either?
If
you
have
any
questions,
concerns
or
comments
that
you
wanted
to
to
bring
to
the
group
to
the
crew
today
or
actually.
B
A
Wow
I
wonder
why
you
looted
me:
I
was
just
a
fool
all
right:
let's
go
right
into
the
project
board
then,
because
this
is
where
we'll
see
kind
of
what
we're
working
with
right.
Now
we
keep
a
pretty
basic
project
board.
If
you
want
to
help
out
with
that,
that's
awesome.
We
do
have
a
triage
team
now
and
contributor
experience.
They
live
in
slack.
A
It's
like
a
safe
control
box,
triage
they're,
trying
hard
to
figure
out
how
to
like
box
them
up
and
make
a
service
out
of
triage,
but
that's
a
that's
a
separate
story,
so
what
we
have
in
the
to
do
column
in
the
progress
column.
Most
of
these
issues
right
now
in
the
in
progress
column,
are
our
outreach,
intern
Misha.
This
shows
awesome.
She's
been
plowing
through
a
lot
of
the
developer
guide,
related
issues.
A
The
contributor
site
is
also
a
part
of
this
contributor
documentation
project
as
well
that
lives
in
a
different
repo,
and
we
have
a
different
project
board
for
that.
We
should
probably
get
an
umbrella
issue
in
here
that
talks
about
the
contributor
guide,
with
maybe
some
of
like
the
features
that
are
going
to
go
first,
so
either
I'll
take
an
action
for
that
Bob.
Can
you
make
a
note
for
me
to
keep?
Do
me
a
favor
and
take
notes
really
quick,
while
I'm
sharing
my
screen
I
apologize,
that's.
A
D
A
A
I
need
to
take
an
AI
to
create
an
umbrella
issue
that
just
briefly
talks
about
the
contributor
site,
and
just
you
know,
because
there
are
different,
there
are
different
repos
and
then
just
lists
and
very
high-level.
Some
of
the
issues
that
are
features
that
are
gonna
roll
first,
so
we
can
I
can
do
that
today,
all
right
so
outside
of
develop
for
guide
stuff,
though
we've
got
we
of
the
cap
in
here
the
contributor
site
discussion,
but
it
would
be
cool
to
have
like
a
feature,
a
feature
issue
as
well:
Oh,
Marilla
issue
for
reviews.
A
This
has
been
sitting
for
a
while
and
I
novitiate
has
been
doing
some
wonderful
issue.
She's
been
doing
some
work
with
looking
at
videos
like
Tim's
videos
that
he
does
about
how
to
be
a
good
code
reviewer
and
making
a
documentation
on
like
what
it
means
to
actually
review
PRS
with
kubernetes,
obviously
different
strokes
for
different
folks
in
different
areas.
But
this
is
a
guide
that
fish
has
been
working
on,
but
it's
a
very
big
guide.
A
So
if
you
wanted
to
either
help
her
or
jump
in
I
doubt
she
would
I
doubt
she
would
mind,
and
then,
let's
see
some
other
things
that
I
just
wanted
to
highlight
in
the
in
progress
section
that
are
already
assigned
and
the
test
grid
analysis.
I,
don't
believe,
she's
worked
on
that.
Yet
this
is
something
that
we
do.
You
think
as
a
priority
based
off
of
what
we've
already
seen
the
survey
results
come
back,
I
mean
we've
only
done
it.
D
Or
do
actually
something-
and
that
might
be
good,
determine
on
the
issue
with-
is
the
presentation
from
the
contributor
summit
this
past
year
from
Michelle's
test
grid
and
essentially
just
documenting
that,
because
test
code
itself,
a
lot
of
the
points
I've
actually
been
automated
away.
If
you
have
a
job
and
can
just
point
it
towards
the
job
name,
the
other
thing
that's
come
up
is
the
job
documentation
itself.
It
might
something
long-term
worth
surfacing
on
the
contributor
site
and
just
like
you
know
how
to
write
a
proud
job,
all
right,
cool.
A
A
C
A
A
All
right,
so
that's
pretty
much
it
that's
what
we
have
labeled
as
in
progress
right
now,
but
I
know
that
a
lot
of
all
there
are
some
of
the
entities
that
need
to
go
over
as
well,
but
let's
start
with
some
of
the
ones
I
clearly
don't
have
they
clearly
don't
have
anybody
assigned
to
them.
So
we've
got
this
one.
This
is
a
been
a-been
rant
from
slack
that
we
hadn't
put
in
slack
just
because
it
has
a
lot
of
good
issues.
This
issue.
A
Okay,
all
right,
so
this
was
what
Ben
had
said
to
us
and
slack
one
day,
and
we
said
this
is
all
really
great
info.
Actually
we
should
put
this
in
an
issue.
The
thing
is:
it's
not
really
an
issue,
it's
more
of
a
rant,
so
we
need
this
broken
down
into
multiple
issues,
and
then
we
can
get
some
people
assigned
to
that
and
more
clear
guidance.
There
I
think
most
people
look
at
this
issue
and
get
scared
and
run
away
because
it's
got
a
lot
of
in
the
u.s.
A
things
and,
like
you
know,
if
you,
if
you
know
the
project
kind
of
things
in
it,
so
it
makes
it
hard
for
a
Help
Wanted.
But
there
are
a
lot
of
things
in
here
in
my
opinion
that
we
could
probably
break
down
and
to
help
on
it
issues.
So
if
that's
something
that
calls
to
you
too,
we
definitely
could
use
help
as
well,
because
you
know
we
do
have
contributors.
Sometimes
they
will
file
issues
about
their
experience
and
not
necessarily
about
something.
That's
specifically
broken.
D
A
A
This
one's
from
2017
this
one
says
that
the
docker
md
file,
it
basically
says,
run
mini,
run
hypercube
with
these
grams
and
even
after
an
update.
It's
mostly
don't
do
this
anymore
use
many
human
stead,
yeah
I,
think
that
one
could
just
be
closed.
Is
that
still
say
that
what
it
looks
like
yeah?
That's,
not
even
there
I'm
just
can
I
just
Chloe
close
this.
Just
close
it
doc
doesn't
even
exist
anymore.
A
Just
the
rest
of
them
have
folks
now
I'm
looking
to
see
how
they're
doing
this
one
is
one
that
is
one
of
the
documents
that
we
have
it's
kind
of
like
the
API
convention.
So
it's
the
development
environment,
one
that
is
constantly
changing
and
it
constantly
needs
updates
like
development,
firemen's
and
peep,
and
how
people
are
opinionated
on
it.
People
are
constantly
telling
us
that
the
install
guide
is
not
accurate.
A
But
there
this
is
not
a
prayer,
I
know
for
a
fact:
it's
not
a
priority
for
them,
so
this
is
only
I
mean
long
vigil
claimed
at
December,
21,
so
I
know,
I
mean
her
prior.
Her
priorities
right
now
are
getting
the
getting
the
features
up
for
the
contributor
site,
but
also
priorities
for
her
right
now.
So
this
is
like,
like
I
said
this
always
is
a
living
doc.
A
We
need
to
figure
out
a
way
to
identify
the
living
docs
that
always
change
and
make
sure
that,
like
I,
don't
know,
maybe
every
contributor
experience
meeting
now
that
it's
bi-weekly
we
check
those
Doc's,
make
sure
they're
good,
and
you
know
if
new
contributors
show
up
on
the
line.
Have
them
take.
Take
those
you
know
key
documents
and
make
changes
to
them
or
something.
E
D
D
D
A
A
D
A
A
Exactly
why
we
did
it
so
and
that's
why
I'm
trying
to
like
think
about
telling
folks
on
the
contributor
summit
team
that
they
should
not
necessarily
think
about
like
what
people
are
gonna
enjoy
that
day,
but
also
what
we
could
use
as
videos
go
forward.
So,
like
saying,
should
present
on
topics
like
walkthroughs
and
stuff
like
that,
knowing
that
they're
gonna
get
recorded
and
that
we
can
use
this
for
documentation
in
the
future,
all
right
yeah,
then
the
boxed
up
workshop.
That's
something
that,
like
everybody,
knows,
needs
to
happen.
A
A
A
A
A
What
do
you
think
about
this
right
here
as
a
developer
on
the
project
like
how
to
me
like
this?
Is
someone
calling
for
documentation
or
creating
new
API
server,
but
it's
from
2016,
so
obviously
old?
That's
for
call
ID
involved
like
what
I
feel
like
we
already
have
this
right
conventions
and
are
also
just
very
routinely
scrubbed
and
maintained.
Do
we
have
this
and
do
we
have
this.
B
A
A
Yeah
so
I
think
maybe
I'll
just
keep
this
open
until
I,
think
Paul
and
then
I'm
gonna
ping-pong,
because
the
thing
is
this
is
definitely
not
going
to
be
a
priority.
This
right
here,
like
fish,
are
getting
assigned
to
it.
So
it's
why
I
wanted
to
stop
I'm
gonna
start
cleaning
up
her
plate
because
she's
got
waiting
anything
signed
to
her
right
now,
so.
A
So,
in
my
opinion,
it
looks
like
the
issue
is
still
open,
whether
or
not
it's
a
priority.
There's
another
story
and
figuring
out
what
the
priority
is
on,
that
I
might
pain,
maybe
Jordan
off
the
side
and
see
what
Jordan
says
about
it.
But
we
have
anybody
really
paying
about
those
kinds
of
things
since
so,
I
don't
know
if
either
the
API
sock
is
doing
it
bowler
one.
D
A
If
anybody
wants,
if
anybody
wants
a
good
PR,
you
can
take
this
one
right
here,
because
this
isn't
Scott
about
taking
out
some
words
like
just
and
simple
and
things
along
those
lines,
and
we
had
a
ton
of
folks
that
were
without
a
doubt
like
in
agreement
with
it.
So
next
step
would
be
implementation.
So
if
anybody
on
the
line
wants
to
take
this,
we
can
work.
You
can
partner
with
Maria
on
it,
but
Maria
also
hasn't
assigned
it.
She
said
she
would
partner,
but
not
necessarily
do
the
from
the
scripts
or
anything
like
that.
A
A
C
A
A
See
like
here's,
the
just
two
comments.
We
do
have
a
code
of
conduct
committee.
They
should
review
your
work
they're
not
going
to
necessarily
like
I
doubt
that
they're
gonna,
you
know
talk
about
the
technical
specifics
but
they'll.
You
know
they
may
ask
to
tweak
some
things
or
something
in
regards
to
the
the
link
itself
or
point
the
link
somewhere
else.
You
know
something
like
that.
So
you're
John
after
you're
done
no
and
I'll
I'll
ping,
the
code
of
conduct
committee,
so
that
they
can
review
it.
So
this.
D
A
D
D
This
I
would
just
close
out:
don't
worry
about
the
the
caps
thing
it's
it
hasn't
been
updated
in
since
October
30th,
2019,
so
I
think
it's
safe
to
close,
but
as
far
as
like,
because
we're
also
getting
other
PRS
of
people
updating
stuff
for
the
design
proposals.
Ideally,
they
should
be
moved
into
the
can
hands.
What's
repo,
there
is
an
open
issue
for
that.
F
A
A
C
A
Don't
have
a
timeline
we
should
100%
I,
think
so
I
mean,
and
that's
one
of
the
things
that
the
triage
team
is
also
trying
to
really
think
about,
as
well
is
like
what
the
SLA
is
are.
Should
we
close
this
issue?
If
it's
been
for
years
like?
Should
we
just
open
up
a
new
one,
fresh
one
like
that
kind
of
thing?
C
C
Yeah
yeah
I
mean
yeah,
it's
it's
I
know,
but
I
do
not
see
timelines
kind
of
thinking
anywhere
in
any
sector,
anything
it's
being
open,
and
that
is
being
what's
like.
If
a
person
is
assigned,
we
don't
know
mine,
they
freaking
ship
to
any
other
person
or
so
because
I
see
around
a
lot
of
things.
That's
being
us
in
for
a
lot
of
days
with
you.
A
Should
in
that
case
you
just
ask
and
I
can't,
because
that
I
mean
it's
like
you
can
see,
some
people
are
assigned
to
hundreds
of
issues.
So
in
that
case,
I
would
just
say,
hey
I
know,
I
can
solve
this
issue.
Are
you
close?
Do
you
need
some
help,
that
kind
of
thing
and
if
they
don't
reach
out
to
you
within
like
three
days?
Maybe
if
you
want
to
get
validated,
you
can
ask
the
sing
in
there
slack
channel
or
just
do
it.
Cuz
code
is
king.
A
A
A
A
A
A
Excuse
me
this
show
like
I
mentioned
earlier,
is
one
of
the
main
folks
that
are
that
is
working
on
it
right
now,
here
are
some
of
the
issues.
Most
of
the
issues
are
I'm
not
going
to
lie
to
you.
Research
focus
groups
and
things
that
aren't
standard
issues.
So
the
one
of
the
main
things
that
we're
trying
to
do
now
is
break
these
down
so
that
they
are
issues
so
that
you
can
have
punch
cards.
A
That's
not
the
case
right
now,
so,
as
you
can
see
just
some
of
the
features
that
we're
going
to
get
out
the
door
to
begin
with
are
the
code
of
conduct
so
obviously
we're
gonna
display
that
I'll
read
me
in
a
code
of
readme
that
will
have
a
code
of
conduct.
Section
looks
like
she's
working
on
some
kind
of
Hugo,
versioning
thing,
I,
think
Bob.
She
might
have
been
waiting
on
you
for
something
along
those
lines
and
then
also
she's
working
on
an
event,
an
events
page.
So
that's
pretty
much.
The
stuff
I
actually
know.
A
That's
done.
I
apologize
Bob!
So
that's
the
stuff
that
that
is
done,
and
then
this
is
the
stuff.
That's
in
progress,
if
you
will
so,
for
instance,
there's
going
to
be
an
events.
Page,
that's
just
gonna,
be
the
calendar
to
jump.
We're
gonna
have
an
extensive
events
page.
You
know
down
the
road,
but
this
is
just
a
calendar.
A
homepage.
D
D
A
There's
gonna
be
a
contributor
guide
section
as
well.
The
problem
with
the
the
how
it
is
currently
is
that
it's
too
verbose
and
lengthy
so
we're
trying
to
trying
to
figure
out
how
to
be
better
web
writers
and
probably
do
a
custom
page
that
hot
links
like
tape
from
like
a
table
of
contents
perspective
to
github,
canonical
sources.
D
D
A
D
D
A
A
I
have
it
on
a
custom,
page
she's
working
on
a
custom
page
that
will
pretty
much
link
to
key
elements
here.
So
it's
gonna
link
to
before
you
get
started
your
first
contribution
contributing
kubernetes,
contributor,
playground,
community
advanced
topics,
that's
gonna,
be
the
the
custom
page
instead
of
scrolling
through
this
and.
D
Know
but
like
if
they're
read
me
and
the
contributor
guys
update
it
to
be
what
you
said
you
wanted
to
be,
but
the
content
is
still
like
resource
from
the
community
repo.
It
will
then
exist
on
the
contributor
site
so
that
we
could
go
to
you
know
Kate's
dev,
slash
CLA
and
have
that
be
that
documentation
on
the
CLA.
D
A
D
A
I
want
this
left
hand,
column
so
I
told
her.
So,
for
instance,
this
is
what
I
said.
I
said
see
the
contributor
guide
at
the
top.
Keep
that,
but
instead
of
adding
release
notes,
it
should
be
welcome
and
then
bounty
program
should
be
before
you
get
started,
and
then
coding
convention
should
be
your
first
contribution
and
then
the
collaborative
development
should
be
contributing
like
that's
what
the
left
panel
should
read,
because
right
now
the
left
panel
is
literally
a
bunch
of
where.
A
A
Get
involved
right
here.
This
is
perfect,
like
there's,
this
site
is
beautiful,
because
it's
just
like
here's,
where
we
talk,
here's
where
we
learn
and
then
here
look
at
the
contribution
guide.
This
is
it
and
then
every
one
of
them
has
hot
that
has
links
in
here
so
like
asking
for
help,
reporting
an
issue
and
then
here's
code
contributions.
Here's
look
if
you'd
like
to
fix
bugs
or
add
a
new
feature.
Please
make
sure
you
do
the
contribution
guidelines
and
then
look
boom
right
to
their
github.
A
A
D
C
Think
Bob
homepage
right
so
the
like
that
the
home
page
and
the
Cuban
it
is
contributed
guide.
It
has
all
the
sub
links
right.
It's
just
a
tab,
a
different
tab
for
the
home,
and
this
so
is
it
like
a
palace.
You
were
asking
about
the
tabs
like
for
a
different
page,
bringing
it
up
and
then
making
it
a
different
tab.
Yeah.
A
A
A
If
it's
just
like
us
like
doing
three
Parra's
and
then
shipping
the
site
and
like
let's
just
do
that,
but
cuz
like
I,
just
feel
like
there's
too
too
much
work.
People
don't
want
to
do
the
work
clearly
right
like
that's.
Why
I'm
a
fan
of
the
way
nodejs?
Does
it
because
it's
the
only
thing
that
their
contributors
do
is
update
did
hub
and
they
have
one
or
two
or
three
section
heading
links
on
their
website.
Yeah.
D
The
other
thing
like
nodejs-
and
it's
also
predominately
just
their
public
website
like
we
I-
think
we
have
a
careers
I,
especially
contributing
it's
like
that
there
no
deicide
is
not
meant
for
developers
is
meant
for
you
know.
Essentially,
oh
I
should
say
contributors.
It's
it's
meant
for
people
to
discover
the
project
itself.
What.