►
From YouTube: 2022-04-25 Maintainership Working Group
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
It's
not
okay
welcome
everyone.
This
is
our
second
maintainership
working
group
meeting,
and
so
I
think
there
will
still
be
more
people
who
join
along
the
way,
but
for
now
we're
just
getting
started.
It's
april
25th
today
and
jerome's
got
the
first
item.
This
is
read-only,
hey.
B
So
max
and
emmanage
is
that
correct?
So
I
just
want
to
say
I'm
super
excited
that,
like
we
literally
threw
this
together
on
a
thursday
and
I'm
actually
seeing
some
engineers
actually
in
this
discussion.
So
I
just
want
to
acknowledge
that,
like
I
really
appreciate
whoever
ever
talked
to
people
and
like
socialized
and
like
they're,
actually
showing
up
so
like
that,
I
think
we
need
to
celebrate
that
a
little
bit.
So
thank
you
for
attending
really
appreciate
it.
B
A
A
A
B
Yeah
yeah,
so
the
thing
I
was
just
going
to
point
out
is,
I
think,
that's
exactly
what
you
were
saying,
which
is
specialized,
repos
and
or
other
considerations
we
have
and
then
right
now
we
don't
have
any
any
anything
that
is
part
of
products.
Everybody
has
to
follow
the
same
definition
of
done,
so
I
want
to
make
sure
that
that's
consistent
or
stays
consistent.
So
as
long
as
we're
good
there,
I
think
that
that's
the
main
things
at
this
point:
okay,
cool.
E
A
Okay
yeah,
so
so,
let's
just
wait
and
get
to
that,
and
maybe
in
the
future
we
might
consider
like
a
dri
for
those
and
so
that
we
don't
have
a
representative
for
all
the
repos
so
anyway
changes
since
last
time.
This
is
very
quick
and
then
we
can
get
into
the
discussion
topics
but
number
one.
I
have
an
apac
friendly
day
every
tuesday,
and
so,
as
we
have
more
people
in
apac
join.
Currently
we
don't
have
any
I'll
set
up
an
apac
time
for
every
other
tuesday.
A
A
The
next
one
I've
created
an
issue
board
and
epic
to
track
progress
of
the
initiative.
The
epic
makes
a
little
more
sense
because
we
can
have
sub
sub
epics
for
each
exit
criteria,
but
the
issue
board,
I'm
not
sure.
Yet
what
issues
will
show
up
here
and
what
labels
we
should
be
tracking
for
progress
darva.
Do
you
have
an
idea.
E
Yeah,
just
just
some
thoughts.
First
of
all,
I
like
this
sub
epic
idea.
That's
really
good.
I've
noticed
a
lot
of
times.
Engineers
tend
to
default
to
the
workflow
labels,
but
I
think
we
could
use
those.
Maybe
the
main
ones
I
could
see
is
using
are
ended,
which
means
it's
in
progress
blocked,
which
means
it's
blocked
by
something
and
that
might
trigger
someone
to
document
what
it's
blocked
by
in
review.
A
Exit
criteria-
number
one-
is
one
percent
done,
so
this
is
the
intent
really
behind
this
section,
as
we
should
be
updating
what
the
status
is
each
week,
but
there
really
isn't
a
status.
So
here's
a
good
example.
A
A
A
A
We
also
need
to
make
sure
that
we're
covering
all
of
the
repos
at
the
end
of
the
day
increase
the
number
of
maintainers
or
have
a
plan
to
get
there
reviewing
the
duties
and
requirements
reviewing
the
current
roles,
reviewing
the
trainee
process.
Of
course,
all
of
these
come
with
changes
associated
with
them.
Reviewing
the
training,
mentorship
pilot
communications
plan,
and
then
this
one
will
define
along
the
way
but
handbook
cleanup,
and
so
before
we
really
flail
a
little
bit
too
much.
C
Criterias
happy
because
I
know
we
discussed
it
previously
when
dennis
did
anyway
to
take
on
number
two
there's
already
quite
a
lot
of
work
done.
I
I
think
lucas
in
create
already
has
sort
of
like
a
front-end
ability
to
see
real-time
status
of
maintainer
availability.
The
thing
we're
missing
is
historical
status
and
seeing
trends
over
time.
So
yeah,
I'm
more
than
happy
to
take
that
on.
For.
A
G
I
just
had
a
question:
are
there
are
those
generally
in
in
order
of
priority
like?
Are
there
any
that?
We
think
that
we
should
find
dris
for
sooner.
A
No
to
the
first
one
they're,
not
in
order
of
priority,
for
example,
the
communications
plan
most
likely
that's
last
or
along
the
way
for
each
thing
that
we
do
and
for
the
second
one
I
think
we
might
talk
about
a
little
bit
in
terms
of
what
should
we
be
focusing
on
now
midterm
late
term?
On
christopher's
point:
does
that
help
answer
the
question.
G
Yeah,
I
think
so.
I
just
want
to
make
sure
that
yeah
there
weren't
any
in
mind
that
we're
specifically
looking
for
for
dris
on
at
the
moment,
but
sounds
like
all.
B
I
mean
what
we
could
do
is
we
could,
I
want
to
say
temp
dri,
like
sometimes
when
we
say
dri
people
think
okay,
I'm
in
here
for
the
long
haul.
What
we
could
do
is
is
we
just
have
a
single
sentence.
Description
is,
is
actually
have
somebody
try
to
go
draft.
What
the
issue
consists
of
that,
maybe
it's
more
expensive
just
to
be
iterative
on
it.
B
That
might
be
more
palatable
yeah
for
first
sign
up,
I'm
not
sure
whether,
like
I
don't
know
how
people
think
about
that,
where,
whether
we
say
the
dri
or
we
just
ask
people
to
sign
up
to
basically
go
expand
on
an
area
and
try
to
write
up
something
associated
with
it
of
what
which
what
should
be
done
in
this
or
what's
people's
feedback
on
that
thought.
E
I
kind
of
think
my
first
reaction
is
if
we
could
create
just.
I
think
this
is
what
you're
saying,
I'm
not
sure
our
creative
summary
epic
for
each
sub,
epic,
just
what
we
think
it
is.
What
the
effort
is
and
then
socialize
that
with
everyone
and
ask
them
if
they
want
to
sign
up
for
the
sub
epic.
Is
that
what
you
were
saying
for
us
to
summarize,
or
were
you
looking
for
volunteers
to
create
the
sub
epics.
B
E
So
michelle
I
can
help
draft
out
this
sub
epics.
You
want
to
help
with
all
of
the
sub
ethics
just
drafting
them
out.
I
can
drag.
B
G
Darva
to
lighten
the
load,
if
that
would
help
sure.
D
Yeah,
I
think
that
helps
as
well,
because
I'm
I'm
a
non-maintainer,
so
I
don't
have
contacts
into
the
process,
but
I
have
thoughts
from
outside
maintainership.
But
if
you
can
flush
out
in
you
know
in
a
proper
manner,
I
would
be
able
to.
You
know.
B
B
A
I'm
sorry
about
my
headphones.
I
don't
know,
I
don't
know,
what's
happening
christopher,
you
want
to
take
the
next
one.
B
Yeah,
so
you
know,
if
anybody's
familiar
with
the
air
water
food
exercise,
here
you
can
here
you
have
to
breathe
every
five
seconds.
I
need
water
every
five
days
and
food.
I
think
it's
like
every
30
days
or
something
like
that,
so
the
idea
is
is
like.
B
What's
the
things
that
you
need
most
urgently
versus
things
that
could
potentially
be
delayed,
and
I
was
trying
to
think
about
things
and
in
particular,
like
you
know,
the
one
that
comes
to
mind,
is
somebody
going
through
the
trainees
and
trying
to
push
on
getting
you
know
like
we
have
an
okay,
our
goal
to
increase
our
maintainership.
That's
not
necessarily
a
goal,
this
working
group,
but
as
part
of
that
we
do
need
to
look
at
our
current
trainees
and
and
try
to
understand.
B
Okay,
like
who's
been
in
there
for
over
a
year
as
an
example
as
a
trainee
and
different
aspects.
So
I'm
looking
I'm
looking
for
potentially
somebody
to
to
take
that
on
in
the
short
term,
which
is
kind
of
going
and
doing
an
audit
of
that
and
kind
of
pushing
various
managers
on
it.
So
so
it's
probably
a
manager
that
I
would
ask
to
kind
of
take
this
one
on.
H
B
E
All
right
so
I'll
jump
in
real
quick.
I
believe
this
is
an
okr
becoming
a
maintainer
for
the
next
quarter
and
I
think
that
I
see
it
almost
like,
dare
I
say
it
in
engineering
allocation,
but
I
won't
say
that,
but
I
think
we
need
to
work
with
product
to
reserve
capacity,
for
people
to
be
able
to
finish
this
work,
some
of
the
feedback
I'm
getting
is
you
know
I'm
too
busy.
I
have
too
many
deliverables.
E
My
throughput
is
going
to
suffer.
If
I
focus
on
this
and
it's
a
temporary
type
of
thing,
this
isn't
permanent.
We
just
need
whoever
is
like
working
on
their
trainee
maintainers
issues
to
have
a
capacity
to
finish
them
up.
B
Okay,
now
I
think
I
get
it
so
what
you're
saying
is
somebody
who's
currently
working
who's,
less
efficient
because
they're
learning
so
consequently,
we
need
to
make
sure
that
they
have
the
appropriate
capacity
with
products
on
an
individual
by
individual
basis.
So
how
do
we?
How
do
we
make
sure
products
engaged
on
that?
How
do
you
make
sure
we're
communicating
that
effectively
and
how
do
we
make
sure
we're
adjusting
appropriately
okay.
E
Yeah,
because
the
the
message
that
you
constantly
get
about
maintainers
is
it's
too
much
work
for
me
to
review.
I
have
to
go
in
red
because
it's
just
overwhelming,
so
the
idea
of
finishing
your
trainee
maintainer
issue
you're
going
to
get
the
same
feedback,
so
we
have
to
alleviate,
give
like
alleviate
some
pressure
somewhere
for
them.
A
E
F
Part
of
it
is
because
the
trainees
are
assigned
at
a
much
higher
rate
than
a
typical
reviewer.
So
when
they
take
the
red
circle
off,
they
get
pounded
with
reviews
pretty
quickly
depending
on
the
specialty.
But
like
I
had
a,
I
had
a
reviewer
on
my
team
who
took
his
red
circle
off
and
he
got
like
eight
reviews
assigned
to
him
kind
of
all
at
once,
and
then
he
was
like
oh
crud
and
put
the
red
circle
back
up
because
he
had
other
stuff.
E
B
Are
reviewers
are
reviewers
the
only
one
I
mean.
Is
it
because
the
bots
is
auto
assigning
them
or
is
it
because
people
are
signing
them
or
both
or
do
we
know.
F
The
bot
picks
them
and
the
people
assign
them.
Typically,
it's
what
happens.
B
F
For
reviewers,
not
necessarily
it's
so
the
bot
picks
for
viewers
at
three
are
picks
trainees
at
three
times
the
rate
of
a
regular
reviewer,
I
think,
is
I
yeah.
That's
right.
E
A
E
B
Can
I
can
take
an
action
to
talk
to
david
about
it?
He
knows
about
the
okr
because
he's
been
in
okay,
our
discussions,
but
I'll
take
an
action
to
talk
to
david
about
so
we'll
start
at
the
top.
A
I'll
create
the
issue
for
the
the
trainee
maintainer
getting.
D
Yeah,
so
my
input
was
around
whether
we
can
have
something
like
a
local
maintainer
instead
of
a
global
maintainer,
because
if
you
see
you
have
a
like,
you
can
have
a
shorter
cycle,
training
somebody
to
be
a
local
maintainer
of
a
specific
group
or
a
specific
domain,
rather
than
going
through
the
whole
tedious
process
of
becoming
a
global
maintainer
and
many
people
across
gitlab
work
in
the
same
area
of
the
code
base
for
a
very
long
period
of
time.
D
So
they
become
comfortable
in
that
area,
so
they
might
have
a
shorter
cycle
on
becoming
a
maintainer
for
that
specific
domain.
So
that
is
also
something
that
we
could
think
about.
If
you
want
to
have
more
people
come
in
as
maintainers,
and
if
you
have
local
maintenance
in
different
parts
of
the
app,
then
you
reduce
workload
of
global
maintainers.
F
So
we
actually
proposed
this
as
a
as
a
strain
relief
for
some
of
the
database
maintainership
stuff,
and
we
have
a
proposal
in
an
issue
that
we
actually
had
talked
about
trying
to
work
on
in
15,
and
the
idea
was
to
do
it
for
maintainers
and
reviewers,
but
not
for
trainees.
That
would
give
them
in
order
to
give
them
kind
of
a
global
view
of
all
of
the
things
that
are
out
there.
I
don't
know
if
that
makes
sense
at
all,
but
something
we
were
gonna
try
at
least.
D
Well,
I
you
also
want
to
add
one
point
that
I've
not
written,
because
I
I
see
this
trend
of
if
you
become
a
global
maintainer
from
a
specific
domain.
There
is
also
this
trend
of.
They
are
picked
into
more
reviews
of
that
domain
itself
and
plus
they
have
reviews
in
other
domains.
For
example,
imran
authentication
and
authorization
is
mostly
assigned
to
stuff
within
authentication
and
authorization
as
maintainer,
because
he's
the
only
maintenance
from
our
group,
I'm
sure
max-
is
also
pulled
into
more
reviews
of
compliance
than
other
groups.
D
So
if
you
have
a
local
maintainer
say
in
the
group,
then
embrace
for
cloud
automatically
reduces
and
yes
like
time
to
get
into
other
reviews.
B
So
I'm
definitely
not
opposed
to
this.
I
think
this
is
the
question
we
have.
We
already
have
this
with
repose,
where
it's
like.
As
an
example,
the
gilly
team
has,
I
think,
maintainers
maintainers
for
all
of
all
all
the
getaway
members
or
maintainers,
except
for
new
hires,
who
are
basically
on
boarding.
So
I
think
I
think
a
little
local
maintainership
within
the
the
common
project
totally
can
make
sense
and
work.
B
We
need
to
make
sure
that's
supported
as
well
and
doesn't
doesn't
doesn't
get
lost,
because
I
think
we're
always
going
to
have
parts
of
the
code
base
that
don't
map
well
or
that
we
have
to
kind
of
figure
out
here,
and
you
know
our
choices
are,
as
is,
everybody
goes
local,
which
I
think
is
going
to
be
super
hard
to
do
to
be
honest,
unless
we
go
to
managers
being
responsible
for
that
which
I
could
do,
but
I'm
not
I'm
not.
I
haven't
seen
that
work
well.
B
In
the
past,
in
a
past
life,
so
so
kind
of
my
thinking
is,
is
we
still
need
general
maintainership
and
we
need
to
make
sure
that,
however,
we
roll
this
out
it's
in
a
way
that
still
people
are
encouraged
to
go
for
general
maintainership
in
particular,
if
you're
looking
to
influence
the
code
base
across
the
entire
product.
I
think
that's
the
case
where,
like
having
that
understanding
of
the
code
base
is
super
important.
You
know
whether
that
be
in
frameworks
or
other
aspects.
So
that's
kind
of
my
thought.
High-Level
thought
process.
G
See,
I
think,
maybe
manoj
you
had
a
point
before
mine
or
or
was
that
already
expressed
yeah
yeah
yeah
got
it
yeah.
I
was
just
wondering
if
we
should
explicitly
add
this
as
an
exit
criteria.
It
has
come
up
quite
a
bit
and
it
could
be
to
evaluate
local
maintainership
and
and
perhaps
kick
off
an
experiment
as
part
of
the
exit
criteria.
G
Cool
yeah,
I
can
add
an
mr
for
that.
E
A
So
I
actually
noticed
that
too,
and
the
reason
that
I
decided
to
push
christopher
to
merge.
The
mr
ahead
of
cleanup
is
because
I
really
feel
like,
for
example,
what
nicki
minaj
just
mentioned.
I
I
do
think
it
ties
back
to
number
five.
I
really
feel
like
once
we
get
into
those
sub
epics,
where
we
have
freedom
to
be
more
specific,
that
those
things
will
start
cleaning
up.
G
I
think
that's
what
michelle
was
suggesting
earlier
seems
like
number
five
comment
but
yeah.
I
agree
thanks
for
for
pointing
me
to
that
agreed
that
it
would
be
good
to
not
add
too
many
more
exit
criteria.
B
And
to
be
just
to
be
somewhat
explicit,
like
that,
was
just
christopher's
brain
dump
at
the
time
and
people
added
things
as
well
so
like
like.
B
If
you
ask
me
at
a
high
level,
what
I'm
looking
for
is
is
I'm
looking
for
increase
in
maintainership
and
a
system
in
place
that
I
have
confidence
that
we
will
be
able
to
support
maintainership
through,
let's
say
the
next
five
years
under
understanding
of
growth
and
potential
of
both
the
product,
as
well
as
as
potentially
the
growth
of
the
organization
in
the
business,
so
that
that
was
kind
of
my
high
level
kind
of
two
high-level
exit
criteria
but
like
if
you
put
those
at
the
top,
it's
too
abstract
for
people
to
to
really
get
get
grappling
on
it
and
kind
of
get
experience.
A
Okay,
we
have
five
minutes
left,
I'm
not
sure
if
we
can
get
to
this
last
one.
So
just
in
case
we
don't.
I
have
four
action
items
at
the
bottom
of
this
agenda,
but
I'm
going
to
go
ahead
and
try
to
do
this
last
one.
So
there
are
a
lot
of
specialty
repos
and
I've
called
out
workhorse
and
database
as
two
of
those
because
they
frequently
ask
for
volunteers.
I
know
each
of
them
have
asked
at
least
three
times
to
just
like.
Please
help
us,
but
the
pattern
is.
A
B
She
she
probably
took
a
break
break
so
yeah.
She
said:
should
we
identify
all
the
special
repos
and
enough
idea
our
eyes
and
asked
to
focus
on
greasy
maintainership
for
the
specialty,
repos
and
then
goes
on
to
say
we
will
need
to
set
specific
goals
for
the
minimum
number
of
maintainers.
We
need
for
these
repos
and
whenever
we
go
below
that
number,
maybe
a
notification
should
be
triggered.
We
should
be
looking
automating
when
possible.
So,
like
we
already
recognized
some.
B
The
question
is
that
you
do
the
audit
first
or
you
get
started
on
the
three
that
are
the
two
or
three
that
we've
already
recognized.
A
E
Thoughts,
I'm
sorry,
I
missed
what
was
said,
but
one
of
my
concerns
was.
I
don't
have
a
clear
picture
of
how
many
of
these
we
have.
So
we
need
like
a
list
of
them
and
then
maybe
we
can
go
from
there,
but
that
was
one
of
my
concerns
or
questions.
B
Yeah,
so
I
know
where
it
gets
merged,
so
I
have
to
go
back
and
look,
but
is
part
of
pragma
in
theory,
is
the
repos
that
I'm
mostly
concerned
about
at
this
point?
Everything
that's
in
is
part
of
product.
That's
what
mra
count
gets
counted
against,
so
people
are
very
motivated
to
add
it
to
that
list.
B
B
It's
it's
it's
a
good
question,
like
the
other
way
to
solve
that
problem.
Is
you
turn
everybody
into
their
own
repos
right
and
then
you
blow
out
the
repos
as
an
example.
So,
but
it's
an
open
question-
and
I
agree
with
you
like
we've-
got
to
work
it
to
figure
out
whether
it's
a
different
process.
B
F
F
Yeah,
I
can
do
that
post
it
in
the
slack
channel,
maybe
or
yeah.