►
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
A
A
A
A
Nick
veenhof
(director
contr.
success):.
Is
it
clear
what
this
team
does??
Is
it
clear
what
our
goals
are?
and
maybe
open
up
some
room
for
questions
or
even
discussions.?
There
is
a
document
that
I
think
was
linked
in
the
meet
up
events.,
I'm
not
sure
if
everyone
has
access
to
that.,
if
you'd
like
to
join,
or
is
that
open
for
all
it
should
be??
I
control.
I'll
just
drop
the
drop.,
the
link
in
the
the
zoom
chat
in
case
anyone
hasn't
got
it.
A
A
A
B
Lee
tickett
(contributor
success):
yeah.,
let
let
let's
let's
dive
in
with
with
the
imi.
yeah,
and
and
give
people
an
opportunity..
I
I
guess
you
want
to
summarize
a
little
bit
what
the
team
does.
nick,
for
those
that,
although
we
we
we've
got
very
familiar
crowd..
I
guess
the
the
recording
could
be
view
by
anyone..
So
you
might
wanna
do
a
quick
intro.
A
A
A
Nick
veenhof
(director
contr.
success):
currently,
we're
4,
people.,
nick
veenhof,
(director,
contr.
success):
and
we're
working
with
the
wider
community
and
on
a
couple
of
items,,
we
follow
the
open
source
growth
strategy,,
which
I
think
is
very
interesting
for
those
that
are
curious
to
understand,,
like
how
good
lab
does
open
source
and
why
we
do
open
source
and
what
we
believe
that
I
am
committing
to
open
source
and
driving.
These
contributions
actually
also
helps
the
company
move
forward.,
and
so
there
is
this.
A
A
Nick
veenhof
(director
contr.
success):
that
on
a
company
strategy
it.
it
means
that
if
there
is
more
contributions,
there's
more
features,,
there's
more
users,
and
there's
more
revenue.
and
then,
like
it's
like
it.
Is,
do
a
flywheel..
So
that's
like
a
very
high
level
of
view
on
like.
why,.
We
also
really
believe
that
it's
important
for
the
company
itself.
A
Nick
veenhof
(director
contr.
success):
the
growth
strategy.
and
I'll
I'll
try
to
be
quick
so
that
there's
enough
room
for
questions
and
discussions.
it
has
like
4
pillars
like
one,
is
that
we
want
to
improve
the
contribution
velocity,,
which
means
that
if
people
submit
something,
they
should
not
wait
for
like
6
months
to
get
feedback
ideally.
these.
These,
like
feedback
loops,,
are
quick.
A
A
A
Nick
veenhof,
(director
contr.
success):
reasons
why
they
would
contribute..
So
if
you
look
at
it
from
2
ways
as
intrinsic
values
and
extrinsic.
yeah,
values
from
why
someone
would
do
that,
intrinsic
means
is
because
you
believe
you're
adding
something
for
the
greater
good..
And
it's
because
you
really
believe
that
it's
doing
something
good
extrinsic.
for
example,
as
a
hackathon,
people
will
contribute
because
they
get
a
gift.
A
Nick
veenhof
(director
contr.
success):.
This
goes
quite
in
depth,
and
there's
like
multiple
things
that
we
could
do
there.
both
is
from
developer,
badges
and
certifications
to
recognition,
like
the
heroes,
program,,
mvps
and
and
other
programs
to
figuring
out
like,.
How
could
someone
even
advance
in
their
career?
because
they
contribute
to
gidlam.?
They
are
maybe
more
likely
to
get
hired
in
a
higher
paying
role.
ultimately.,
but
that's
a
bit
harder
to
to
prove.
A
A
Nick
veenhof
(director
contr.
success)::
this
is
the
events
going
to
office
hours..
You
can
see.
This
was
part
of
the
strategy,,
but
only
since
lee
got
really
frustrated
and
says
we
have
to
do
this,,
he
actually
took
action,
vice
for
action.
and
we're
having
his
office
hours
now,,
even
though
I
think
this
was
on
this
page
already,
for
like
a
year,
or
even
2
years..
So
I
think
that's
that's
great-
that
we're
we're
doing
this
right.
Now.
A
A
A
A
Nick
veenhof
(director
contr.
success):,
you
want
to
motivate
the
person
to
come
back
to
make
a
feeling
of
a
belonging
to
make
a
feeling
of
the
community,
so
that
there
is,
is
returning
and
frequent
contributors,,
so
that
also
the
efforts
spent
in
attracting
the
person
and
making
sure
that
first
contribution
is
successful
is
also
resulting
in
more
later
on,
so
that
you
can
scale
up
as
in
like
that,,
it's
like
a
cumulative
effect..
So
that's
that's
a
bit.
What
I
believe
is
really
important.
There.
A
Nick
veenhof
(director
contr.
success):,
all
the
other
items,
are
also
important.
for
example,
governance
model,
making
sure
that
we
follow
the
code
of
conduct.,
making
sure
that
it's
a
safe,
environment,,
inclusive,
environment.
like,
without
any
of
that,.
You
will
probably
also
not
attract
people.
as
so,
there's
it's
an
end
and
story.
A
A
A
A
C
C
Missy:
but
didn't
really
know
specifically
what
the
the
things
folks
are
looking
at
in
the
projects
that
people
are
working
on.,
but
I'd
be
curious
to
know
how
many
contributors
are
just
people
who
are
doing
it
because
of
their
own
volition.
and
how
many
people
are
actually
part
of
an
organization
or
work
for
a
company
that
are
contributing
upstream
in
their
daily
work..
A
Nick
veenhof
(director
contr.
success):,
it's
an
amazing
question.,
and
the
question
itself
is
something
that
we're
trying
to
answer..
It
is
hard
because
we
don't
require
people
to
explain
why
they're
contributing,
or
if
you
you
look
at
it
like,
if
they're
actually
being
paid
to
contribute
by
an
organization,
or
if
they're
doing
it
from
an
individual
perspective.
A
A
A
A
Nick
veenhof
(director
contr.
success):
able
to
make
it
change
in
the
product
itself
so
that
you
can
identify
yourself
and
saying,,
like
my
organization,,
asked
me
to
do
this.
and
I'm
doing
this
on
the
paying
cadence
or
paying
time,,
or
I'm
doing
this
on
a
volunteering
time
with
the
same
profile
or
you
same
good
luck,
profile.
A
A
A
A
A
C
Missy:
no.
you
help
shed
some
light
on
the
difficulties
of
actually
categorizing
people.,
but
a
follow
up
question.
I
would
have
to,
that
is,
or
is,
from
a
github
perspective..
Are
you
looking
to?,
so
you
are
looking
to
attract
more
companies
and
people
who
contribute
as
part
of
their
job?
or
is
the
monthly
goal
of
unique
contributors,,
also
aiming
to
get
individual
people
who
just
do
it
for
the
other,,
like
reasons
you
listed
like
for
your
advancement
or
learning,,
etc.
A
Nick
veenhof
(director
contr.
success):.
I
think
the
the
main
goal
is
to
grow
the
community
in
both
ways..
But
I
believe,-
and
this
is
my
personal
believe,-
that
if
it's
more
sustainable,,
if
these
are
people
that
are
being
paid
to
country.,
because,
like
the
the
other
flip
side
of
attracting
a
lot
of
individuals.,.
A
Nick
veenhof
(director
contr.
success):.
What
can
you
ask
from
these
people??
What
can
you
expect??
You
push
a
lot
for
the
returning
contributors?.
You
may
be
pushing
these
people?.
They
most
likely
have
very
high
intrinsic
values,
as
in
like,,
you
really
want
to
do
good..
You
really
want
to
go
above
and
beyond.
A
Nick
veenhof
(director
contr.
success):,
but
there
is
a
very
high
risk
of
burnout
with
these
people
that
take
up
different
responsibilities.
for
example,
the
core
team
of
good
lab..
I
think
most
of
them
are
individuals
in
in
their
free
time.,
I'm
making
an
assumption
here.,
but
I
I
believe,
that's
today..
Still
the
case.
A
D
Daniel
murphy
fullstack
engineer,
contributor,
success:
yeah,.
I
just
want
to
jump
in
there
and
just
say,,
even
though
we
don't
have
all
the
exact
data
on
on
that
question.
we
see,
I
think,
anecdotally,.
We
can
say
that
there
is
a
number
of
top
contributors
and
regulars
returners
who
are
doing
this
of
their
own
volition
and
are
doing
this
because
they
want
to
contribute,
or
they
want
to
be
a
part
of
the
community.
and
that's
been
very
valuable
to
get
lab
as
a
whole,
to
have
that
sort
of
drive
from
someone
that
just
wants
to
contribute.
D
D
C
A
A
Nick
veenhof
(director
contr.
success):
contributors
that
got
something
merged.
and
it's
important
to
give
that
nuance
right?.
So
the
the
the
thing
that
today
we
count
and
and
I'll
I'll
explain
a
bit
more
about
what
that
is.
people
that
open
a
merch
request
to
not
necessarily
even
like
add
something
to
an
existing
merch
request,
and
then
get
that
merged
in
that
month,.
And
that's
like
a
hundred
10
last
month,
the
month
before
the
3
months
before
there
were
100
to
13..
If,
if
I
recall
correctly.
A
Nick
veenhof
(director
contr.
success):,
I
mean,.
If
you
look
at
how
many
people
interact
with
merge
requests
itself,,
I
think
we're..
I
need
to
take
a
look
at
the
numbers,,
but
it's
it's
higher.
and
if
you
look
at
how
many
people
interact
with
issues
and
merge
requests
like
all
together.
and
that's
about
like
3,000.
A
A
A
A
A
A
A
A
Nick
veenhof
(director
contr.
success):,
if
someone
interacts
with
an
issue
and
the
issue
gets
closed,
and
the
issue
is
linked
to
merge,
request
that
got
merged..
That's
probably
more
valuable
than
an
issue
that
gets
close,
and
there's
no
link
to
a
merchant
press.,
like
all
of
that
stuff,
is,
is
something
that
we
as
a
team,
are
trying
to
figure
out
like
how
to
add
value
to
something
that
got
added..
That
is
not
necessarily
a
code.
A
D
Daniel
murphy,
fullstack,
engineer,,
contributor,
success:
and
just
to
to
add
on
that
to,
I
think
part
of
it
is-
is
showing
the
value
of
community
contributions
as
a
whole
across
the
organization..
So
sometimes
other
teams,,
you
know,.
They
want
to
know
what
we're
doing.
why,
we're
doing
it.,
and
we
want
to
be
able
to
show
that
value,
that
not
only
are
the
code
contributions
important
to
get
lab
as
a
product.
D
Daniel
murphy,
fullstack
engineer,
contributor
success:,
but
that
contributions
to
say
the
unification
program
that
we're
working
on
right,
now,
or
contributions
to
the
handbook
pages
and
values,
contributions
to
issues,
comments,,
things
like
that
are
still
contributing
to
gitlab
as
a
product,
too.,
and
this
does
just
have
to
be
code
contributions.,
so
being
able
to
showcase.
Why.
A
A
A
A
A
B
Lee
tickett
(contributor
success):
drivers
was
the
I.
I
know
the
state
of
our
issues
isn't
great.,
and
I
know
that
if
you
were
to
to
kind
of
spin,
the
will
grab
a
random
issue..
The
chances
are
that
you
wouldn't
be
able
to
work
on
it,
you'd,
look
at
it,
and
you
wouldn't
understand
what
the
problem
was,
or
what
was
being
asked,
or
how
to
get
started,.
Or
I.
I
just
knew
that
the
quality
of
issues
wasn't
very
good.
B
B
Lee
tickett
(contributor,
success):,
here,,
right?
or
triage.
some
issues
so
go
through
and
make
sure
that
they
are
nice
and
accurate.
That
label
correctly.
they've
got
good
implementation
plans
and
then
probably
dig
in
and
actually
start
coding,
and
it
wasn't
till
last
week
when
we
had
this
one.,
we
had
a
week
without
a
session,,
but
so
we
had
about
8
or
9
back
to
back
sessions..
But
then
we
had
this
gap,
and
nick
said,
well,.
Why
don't.
B
Lee
tickett
(contributor
success):,
but
I
I
thought
you
know
oh,.
I
should
do
the
same
thing,
and
I
had
to
look,
and
we
actually,,
interestingly,
only
have
one
quick
quin
in
our
backlog
at
the
moment,,
and
I
think
I
have
too
many
windows
open..
Now
I
I
am
a
bit
scared
of
sharing
my
screen,,
so
I
only
got
one
at
the
moment.
but
I'll
drop
the
the
link
in
the
chat,
and
if
someone
ever
wants
to
share
it,
or
just
have
a
look
yourselves.
B
B
Lee
tickett
(contributor
success):
get
better
ourselves
as
well.,
because
we
know
full
well
that
we've
got
a
huge
backlog.
We've
got
hundreds
of
issues,
and
we
just
haven't
got
capacity
to
pick
it
all
up..
So
nick
did
a
really
good
job
at
the
beginning..
This
sort
of
explaining
that
we're
just
trying
to
pick
up
a
few
little
bits
that
we
think
are
a
are
going
to
be
like
efficient
uses
of
our
time
and
have
an
impact.
B
Lee
tickett
(contributor
success):,
but
for
a
lot
of
this
other
stuff.
we
would
be
really
good
opportunity,.
I
think,
for
us
as
a
team,
to
go
through
a
backlog
and
try
and
identify
some
of
those
quick
wins
and
try
and
flesh
some
of
them
out
a
little
bit..
So
if
anyone
from
the
community
does
want
to
chip
in.
B
Lee
tickett
(contributor
success):,
I
was
interested.
after
contributing
for
a
certain
amount
of
time
in
helping
other
people
who
are
trying
to
contribute.
and
that's
very
much
what
our
team
does..
So
you
know
you,
marco
nicholas,
many
others
are
really
interested
in
already
helping
us
by
kind
of
moving
things
forward
on
the
triageops
project,
from
an
automation
point
of
view.
getting
involved
with
discussions
for
decision
making
and
and
kind
of
community.
B
Lee
tickett
(contributor
success):,
I'm
gonna
have
a
quick
look
nick,.
Your
your
screen
was
prepared
for
sharing..
Do
you
mind
to
share
in
your
screen
with
that
issue,
and
I
think
what
I
would
like
as
well.,
but
I'm
not
sure
if
it's
possible.
is,,
if
you
could
give
like,
some
of
a
summary
of
this
whole
discussion
with
labels
that
we
have
before
we
dive
into,.
Maybe
a
more
practical
update
on
that.
A
B
Lee
tickett
(contributor
success):,
so
I'll
I'll
I'll
rewind,.
As
far
as
I
can
remember.,
but
nick,
100%
that
so
much
conversation
is
taking
place.
That
is
hard
to
remember
exactly
what.
why,,
the
main
thing
that
I
remember
is,.
We
had
a
label
accepting
merge
requests,,
and
this
used
to
be
one
of
our
primary
sort
of
labels
that
we
would
suggest.
community
contribute
to
search
for.
B
B
Lee
tickett
(contributor
success):,
but
that
wasn't
the
case.,
the
the
label
was
just
assigned
fairly,
randomly
to
issues.,
so
they
were
probably
tens
of
thousands
of
issues
with
that
label
on
maybe
even
something
like
50
of
all
issues.,
so
it
it,
it
become
fairly
meaningless..
So
I
think
that
that
was
the
first
goal
was
to
just
get
rid
of
that
label
because
it
really
wasn't
adding
any
value.
B
B
B
Lee
tickett
(contributor
success):,
which
again
is
a
I
don't
know
if
it's
a
british
or
american,
or
but
it's
a
a
sort
of
cultural
phrase,
which
might
not
mean
anything
to
some
people.
and
yeah,
especially,.
You've
got
to
translate
from
this
emoji
to
the
phrase,
and
then
you've
got
to
understand
what
the
phrase
means.
so
the
clear
path
forward.
There
was
just
to
use
something
which
is
a
a
lot
lot
more
sort
of
understandable
interpretable..
So
we
change
that
to
quick
win.
B
A
B
Lee
tickett
(contributor
success):,
but
then
we
at
some
point
introduced
seeking
community
contributions.
again..
I
don't
remember
the
background
as
to
when
and
why
and
how?,
but
with
this
it's
a
bit
stricter
than
the
accepting
merge
request
to
label.
When
you
add
seeking
community
contributions,
I'll
bot
will
actually
say.
B
B
B
B
Lee
tickett
(contributor
success):
we're
happy,
reasonably
happy
with
keeping
quick
win
personally,.
I
would
like
to
get
rid
of
it
and
use
the
white
the
issue
weights.,
but
it..
I
believe
that
some
of
the
engineering
teams.
the
product
teams
use
that
in
specific
ways..
So
we
we.
We
can't
do
that
at
the
moment,,
some
reasonably
happy
that
we
use
quickly.,
but
there's
a
bit
of
an
expectation
that.
B
Lee
tickett
(contributor
success):,
a
quick
win
should
probably
be
ready.
For
development.-
that's
a
a
workflow
label.,
so
we
might
want
to
kind
of
create
an
automation
or
something
to
say..
If
isn't,,
let's
prompt
the
offer,
or
the
the
person
who
added
the
quick
win
label..
Something
like
that
to
say
is
this
ready
for
development?
and
if
it
isn't,,
is
it
really
a
quick
win??
It
might
be
that
we
have
an
issue.
B
B
B
Lee
tickett
(contributor
success):.
The
suggestion
is
that
something
that
I
can't
see
the
label
in
front
of
me,,
but
I
think
it
is
workflow
ready
for
design
and
already
for
design..
So
if
you're
a
designer,,
then
you're
probably
gonna
go
for
stuff,
that's
ready
for
design,
or
it
might
be
planning
breakdown
or
something
like
that..
That's
fine.!
You
can
go
for
that.
if
you're.
B
Lee
tickett
(contributor
success):
more
of
a
a
a
developer
and
engineer..
I
don't
know
the
perfect
terminology
front,
end
back
end.
that
you
probably
going
to
want
something..
That's
what
I
ready
for
development.
and
there's
an
expectation
there.
if
something
is
ready
for
development,,
then
it
should
have
an
implementation
plan
on
there.
B
B
Lee
tickett
(contributor
success):
probe
the
the
person
who
added
that
label.
he
changed
it
to
that.,
they
would
say,
hey,
like.
I
can't
see
an
implementational
plan
on
that..
Could
you
please
app
one,
or
maybe
the
other
way,
around.
you've
added
an
implementation
plan.?
Do
you
want
to
set
this
to
ready
for
development?,
so.
B
D
D
Daniel
murphy,
fullstack
engineer,,
contributor
success:
and
the
contributor
success
team
one,
you
know,.
One
of
our
roles
here
is
to
try
to
move
things
forward
and
to
find
some
compromises
and
another
one
of
github's
values
is
disagree.,
commit,
disagree?,
so
we've
had
some
teams
say
that
they
want
to
use
some
of
these
old
labels.
we're
trying
to
get
rid
of.
D
Daniel
murphy
fullstack
engineer,
contributor
success:,
some
teams
want
the
idea
of
of
something
specifically
labeled
for
the
community
and
things..
Not
other
teams
want
to
get
rid
of
that..
So
there's
a
lot
of
varying
opinions
in
this
whole
issue.
That's
been
going
on
for
over
a
year.,
and
so
one
of
the
things
we
decide
was
that
we
just
have
to
kind
of
move
this
forward
a
little
bit.,
because
it's
it's
gone
on
long
enough..
We
new
need
to
take
some
action
here,
and
we
can't
satisfy
everybody,
but
we
can
try
to.
D
A
Nick
veenhof
(director
contr.
success):,
you
know,
with
the
goal
that
if
someone
comes
to
the
github
project
and
and
wants
to
be
part
of
the
gilla
community,
that
they're
quickly
able
to
find
their
way
in
this
50
k
issues
that
we
have..
So
I
think
that's
the
main
goal.
there's
many
other
opportunities
for
us
to
improve
both.
What
nico
is
doing
in
in
cool
summer
of
code.,
some
user
study
that
daniel
is
leading.,
and
it
is
one
of
these.
These
items?.
A
C
Missy:,
I
have
a
thought.
I
haven't
read
through
this
whole
thread,
obviously.,
but
just
from
what
we've
discussed
so
far,.
That
was
certainly
something
that
I
had
questions
about
is
after
working
through
all
the
seeking
community
contributions
or
quick
wins
for
a
team.,
then
what
next?
like,?
What
can
a
community
member
work
on??
And
it
wasn't
until
you
said
that
you
can
work
on
any
issue,,
that
I
realized
that,
because
I
thought
it
really
was
just
scoped
to
whatever
was
labeled
those
things.
and
it
does
seem
to
vary
from
team
to
team
a
bit,
but.
C
Missy:,
I
think
highlighting
that
would
be
nice
for
community
members..
Let
them
know.
actually,
they're
part
of
the
community,,
contribute
to
anything.
You
want,
just
check
and
communicate
with
people.,
but
it
doesn't
have
to
necessarily
be
scoped
only
to
the
quick
winds,
or
only
to
the
seeking
community
contributions.
C
A
Nick
veenhof
(director
contr.
success):.
It
might
be
really
interesting
to
understand
marco's
perspective,
because
I'm
pretty
sure
marco
no
longer
does
quick
wins
or
maybe
in
the
past,.
When
we
was
not
a
good
left
team
member
on,
on
how
you
approach
that
you
mean
you've
not
seen
the
the
what's,
the
opposite
of
quick?,
the
slow
wins
label
so
hard
and
impossible..
Maybe
you
could
add
a
label
like
that.
B
E
E
E
E
E
E
Mediastudio
marco
zille:,
our
finding
issues.,
because
mediastudio
marco
zille:,
when
I
did
try
to
find
issues.
and
when
somebody
asked
how
to
find
issues
to
work
on,,
I
relied
on
what's
on
the
handbook,,
basically
on
what
it
was
on
the
handbook
so
good
for
any
contributions
seeking
community
contributions
and
the
usual
stuff.
E
E
A
Nick
veenhof
(director
contr.
success):.
It's
it's
interesting
that
you,
you
mentioned..
You
have
your
a
little
bit
of
your
own
agenda..
If
we
talk
to
customers
like,,
the
the
thing
that
we
try
to
cover
is
like,.
What
is
itching?
and
I
or
the
phrases
then
like,
scratch
your
own
age?,
it's
the
same
as
having
your
own
agenda,,
but
I
I
feel,
there's
some
political
vibe
to
that.
You
don't
have
with
scratching
your
own
age.
A
A
Nick
veenhof
(director
contr.
success):.
I
think
this
goes
back
to
if
we
we
want.
Is
this
large
community
where
people
are
here
because
they
they
believe
this
is
like
for
them,
the
right
place
to
be
and
and
like
the
intrinsic,
why?.
Why
are
you
here
is
because
you're
actually
able
to
make
a
change
that
benefits
yourself
in
a
way
and
also
others,,
because
you
believe
that
you
want
to
share..
Otherwise
you
just
make
glue
code
or
you
make
workarounds
and
like
you're,
not
sharing,,
and
you
keep
it
to
yourself.
A
nick
veenhof,
(director
contr.
success):,
I
think
we.
the
the
difficulty
is
like
how
to
I
explain
to
others
that
maybe
the
age
that
they
have
is.
This
is
how
you
search
for
something
similar,,
and
this
is
where
you
can
collaborate
with
others
that
have
that
same
age,
and
then
find
this
is
common
ground.
A
A
A
Nick
veenhof
(director
contr.
success):
experience
in
going
through
an
issue
to
then
go
through
a
merge
request..
So
for
me,.
This
is
like
an
unsolved
problem.
in
a
way,
I'm
not
under
sure
even
how
to
solve
it.
In
the
the
world
I
came
from,,
which
is
the
the
triple
world..
There
was
no
such
thing
as
a
separation
between
a
code
change
and
an
issue..
It
was
just
like
a
single
thing.,
and
all
of
this
questions
happened
in
that
single
thing.
A
A
A
A
Nick
veenhof
(director
contr.
success):
and
within
good
luck
we
prefer
merch
request,,
because
most
of
the
attention
goes
to
merchants,,
including
discussions
and
all
that?.
So
I
think
that's
one
of
the
challenges
that
we,
as
a
contributor
to
success:
team,
have.
and,
in
extension,
the
wider
community
like,.
How
can
we
make
that
more
like
a
unified
process?.
A
B
Lee
tickett
(contributor
success):.
I
I
added
a
quick
note
in
the
doc
as
well,
that
when
I
was
fairly
early
on
contributing,,
I
used
to
quite
like
browsing
the
issue
list
and
sorting
it
by
by
age..
So
looking
at
the
really,
really
old,
issues,
there,,
there's
issues
in
the
issue:
tracker
that
probably
6
or
more
years
old.
and
obviously
something
that's
been
open.
That
long,
I
think.
B
Lee
tickett
(contributor
success):
is
bound
to
to
have
a
little
bit
of
a
following,
and
it'll
be,.
You
know,
make
a
few
people
happy
if
it's
fixed
or
closed
or
delivered.
similarly,,
there's,
there's
issues.
and
I'd
sort
by
a
popularity.,
so
again,,
seeing
anything
that's
got
like
a
hundred
or
more
votes,.
You
know.
that's
going
to
be
something
that.
B
Lee
tickett
(contributor
success):,
you
know,.
It
would
definitely
make
you
feel
good
and
make
a
a
lot
of
it.
other
people
happy
if
you're
able
to
to
solve
or
deliver
on
it
or
even
just
pulling
together
the
right
people
or
closing
something,
count,,
because
you
know
what
this
is
actually
already
being
delivered.,
but
the
issues
still
open,
or
this
bugs
being
fixed,
or
this
feature
no
longer
even
exist..
So
that
really
kind
of
goes
full
circle
background.
B
B
B
Lee
tickett
(contributor
success):,
you
know.
get
lab
users
that
that
could
kind
of
weren't
necessarily
developers.
coders,
that
that
wanted
to
just
kind
of
troll
for
issues
and
find
stuff
and
be
like,.
I'm
gonna
try
this
and
see
if
this
is
still
broken,
or
search
the
docs
and
see
if
this
is
now
possible.
well.
B
Lee
tickett,
(contributor,
success):
or
or
even
just
pull
in
the
right.,
so
products
engineers
or
product
managers
and
say,
hey,
like,
is
this
something
you
want
to
do,
like?
how
could?
so
people
can
start
designing
things
and
planning
things.
and
you
know,
putting
things
together,,
even
if
they
can't
build
them.
A
Nick
veenhof
(director,
contr.,
success):
and
and
also
there's
like,,
there's
2
ways
of
attracting
these
kind
of
individuals
or
or
you
know,
people
that
want
to
do
this.
One
is
because
these
people
believe
that
this
is
very
valuable,
or
to
is,
if
we
kind
of
like
a
attach
value
to
it,
right?,
and
so
that
kind
of
like
brings
us
into
c
as
well.
A
A
A
A
D
Daniel
murphy
fullstack
engineer,
contributor
success:.
I
want
to
pose
a
question
just
to
to
miss
you
and
nick
you,,
because
I
know
you've
both
been
recently
finding
issues
to
work
on
and
starting
mrs..
So
do
you..
If
you
have
any
feedback
on
how
you
found
the
issues
that
you've
been
working
on.,
that's
something
we're
always
trying
to
figure
out,
not
just
as
a
team
telling
the
community
how
to
do
it.
but
learning
from
the
community
how
they
approach
finding
issues
so
that
we
can
try
to
make
that
a
better
experience..
D
B
C
Missy:
I've
missy:
been
finding
issues
by
using
the
filters
I
found
out
about
the
quick
wins
one
like
a
week
or
2
ago,
extremely
recently,.
I
was
just
using
the
contributor
look
seeking
community
contributions.
and
then
there
was
another
one,,
a
good
first
issue,,
which
I
think
is
like
a
super
old
one.
At
this
point.
C
C
Missy:
github
and
the
code
base
as
well
that
way.,
it's
not
so
overwhelming,
dealing
with
the
entire
code
base
and
then
I
did
have
the
chance
of
running
into
something
in
an
issue
that
I
was
working
on,
that
turned
into
a
bigger
thing.
actually,.
What
lee,
you
and
I-
and
I
mark
them
up-
was
probably
there
when
we
look
at
the
converting
the
mr.
list
to
view,
and
I'm
working
up
to
work
on
that
first.
first,.
I
need
to
learn
view..
So
I'm
doing
that
graphql
issue
to
get.
C
Lee
tickett
(contributor
success):
to
do
the
view
component
of
that
one
piece.
and
then
eventually,,
I'm
hoping
to
to
do
that.
so
that
wasn't
something
that
was
like
originally
created
or
scoped
as
an
issue..
But
in
doing
other
stuff
that
kind
of.
I
walked
into
it,
and
no
one
else
was
working
on
it.,
so
I'm
like,
oh,.
I
think
I
could
take
that
well,.
I
I'm
sure
I
know
you've
been
following
along
and
joining
the
sessions.,
but
obviously,
mark,
I's
working
on.
B
Lee
tickett
(contributor
success):
converting
the
the
folk
button
from
hamil
to
view.
andrew
mentioned
today
that
he's
working
on
converting
the
star
button.,
I
think,
from
from
hamilton
view..
Now
that
I
imagine
a
lot
simpler
than
converting
the
entire
merge
request
app
to
to
view..
But
I
definitely
be
like,.
If,
if
you
want
to
sort
of
join
them.,
I'm
sure
marco
and
andrew,
but
be
happy
to.
E
C
A
A
A
C
Missy:,
I
would
be
curious
to
know
if
teams
have
time
on
a
regular
basis
to
scope
out
quick
wins,
cause.
It
seems
like
sometimes
every
time
there's
a
hackathon.
It
seems
like
things,
get
carried
a
bit
more,
and
there's
a
few
things..
But
then,
there's
been
a
number
of
times
that
I
open
a
quick
win,
and
it
has
no
implementation
plan.
and
then
it
there's
a
threat
of
comment,
saying,.
Can
you
please
add
a
an
implementation
plan?,
but
it's
not
added
yet.
C
B
Lee
tickett
(contributor
success):.
The
answer
is
essentially,.
Now
that
everyone
knows
that
community
is
like
a
a
an
essential
part
of
of
getlab,
but
I
I
I
don't
think,-
or
I
think
very
few-
have
got
something
scheduled
into
that
calendars
to
to
kind
of
revisit
that
issues
list
and
and
kind
of
do
housekeeping
on
it..
There's
reports
that
come
out.
B
Lee
tickett
(contributor
success):,
so
we've
got
a
bot
that
that
uses
some
level
of
machine
learning
and
artificial
intelligence
to
try
and
label
new
issues.
With
the
correct
group.-
and
then
that
group,,
the
engineering
manager.,
maybe
the
product
manager
of
that
group
thing,,
has
visibility
and
tries
to
kind
of
do
the
initial
triage
in.
B
B
Lee
tickett
(contributor
success):
to
to
find
a
way
that
we
can
really
kind
of
emphasize,
and,
and
it
become
more
of
a
a
kind
of
kpr
or
a
like..
We
have
chos
like
key
results,
or
something
that
you
know,.
All
teams
should
always
have
a
certain
number
of
quick
questions
or
issues
with
clear
implementation
plans
or
something,,
and
the
idea
is
to
to
try
and
make
it.
B
B
Lee
tickett
(contributor
success):,
but
the
the
the
kind
of
flip
side
is
that
if
they
want
people
to
contribute-
and
they
won't.
community
contribute
wider
community
contributors
to
do
that,
work
for
them.,
then
they
they
should
do
this.
and
you
know,
hopefully,
your
kind
of
case
in
point
where
you've
picked.
Some
issues
picked
to
team
that
have
got
a
really
nice
curated
list
of
quick
wins.
B
Lee
tickett
(contributor
success):
and
you're
kind
of
working
your
way
through
them.,
so
you
know
that
they
might
want
to
keep
quiet
about
that,
because
they
might
want
to
just
keep
curating
their
own
issues.
but
hopefully,.
If
they
can
celebrate
that,,
then
you
know,,
the
other
teams,
will
kind
of
realize
the
value,
and
and
that
actually,
you
know,
an
hour,,
a
week,
or
whatever
it
might
take
for
them
to
invest
and
spend
some
time
on
some,.
Some
issue.
housekeeping
would
be
really
really
well
spent..
B
Nick
veenhof
(director
contr.
success):,
I'm
I'm
also
curious.
If
even
the
implementation
plan
like
could
be
done
by
community
members.
right?.
So
in
in
a
way,
you
don't.
or
we
need
to
figure
out
how
to
unlock
basically
ourselves
from
like
some
of
these
teams,.
Some
might
need
an
approval
for
sure
to
even
proceed..
That
doesn't
mean
that
we
cannot
cultivate
or
get
a
culture
of
suggesting
implementation
plans
or
figuring
out
how
to
unblock.
A
Nick
veenhof
(director
contr.
success):
community
members
themselves.,
and
this
is
somewhat
of
a
tricky
problem.,
because
the
the
nature
of
the
open
source
project
or
of
kid
lab
itself
is
indeed
the
open
core..
As
so,
there
is
always
some
part
of
that
friction
happening
there.,
but
finding
that
balance
without,
like
being
too
much
blocked
on
these
teams,,
have
to
create
all
of
these
issues.
A
A
B
Lee
tickett
(contributor
success):,
but
I
also
mentioned
that
we
would
have
some
contributors
that
would
be
for
focusing
on
what
flow,,
planning,,
breakdown,
or
workflow
ready
for
design
where
they
would
be
the
ones
that
could
potentially
help
to
put
the
implementation
plan
or
those
designs.
Together.
A
A
Nick
veenhof
(director
contr.
success):
like
cheer
for
a
team
right
exactly.,
then
that
adds
more
complexity
to
to
nick's
algorithm.
Where
he's
got
to
find
a
way
that
to
to
reward
the
person
that
puts
the
implementation
plan,
together
with
a
bonus
points
as
well.
we'll
be
able
to
give
an
overview
of
that
plan
in
5
min.,
but
maybe
for
those
that
are
just
to
like,.
Read
that
on
our.
A
A
A
Nick
veenhof
(director
contr.
success):,
that's
true.!
If
you
could
do
it
all
yourself.,
but
I
think
if
you're
looking
to
collaborate
or
maybe
get
feedback
on.
is
this
the
right
approach??
Then
it
probably
makes
perfect
sense
to
like,
get
some
feedback
on
that
implementation,
plan,
and
in
effect,
just
have
it
out
there
and
then
for
others
to
pick
up..
It
could
be
a
great
help
as
well.,
so
it
it
depends.
like,
if
it's
an
age
that
you
have,
and
you
urgently
have
to
scratch.
It.
sure,
go
ahead
and
fix
it
like
there
is.
A
Nick
veenhof
(director
contr.
success):,
if
you
could
help
someone
else
by
doing
this
and
get
recognized
for
it,
and
you're,
not
in
an
urgent
pressure..
For
some
reason,
I
think
it
would
make
total
sense
to
write
it
down..
I
I
think,
that's
it,
and
it's
a
bit
more
reactive
at
the
moment.
right?
someone
comes
to
to
discord
and
asks,.
You
know
they
need
help.
B
Lee
tickett
(contributor
success):
solving
an
issue.
and
nicholas
yourself,
or
marco,
or
me,
or
daniel
raymond,,
or
someone
will
will
often
jump
on
and
and
help
try
and
look
at
the
issue..
I
understand
it
and
break
it
down
and
add
an
implementation
plan
perfect.
for
example,.
I
think
it
was
a
session
last
week..
Maybe
we
stumbled
on
one
that
had.
it
was
marked
for
quick
when
and
it
was
a
follow
up
issue,
potentially
from
a
merge
request
that
mark
I
raised
months,,
maybe
a
year
ago,
whatever.
B
Lee
tickett
(contributor
success):
and
you
know
I
I
asked
marco
kindly.
any..
I
did
an
implementation
plan.,
but
you
know,.
If,
if
you
think
about
yes,,
I
know
a
lot
of
effort
and
work
in
time
does
go
into
kind
of
figuring
out
who
and
what
and
where,
and
putting
these
together.,
but
at
the
same
time,.
I
I
think
you
probably
could.
you
know,
easily
do
maybe
5
times
as
many,.
If
not
10
times
as
many
implementation
plans.,
then
you
could
actually
have
capacity
of
delivering,
going
through
the
review
process
back
and
forward,,
etc.
so.
B
Lee
tickett
(contributor
success):
they
they
does
come
a
point.
Where?
yeah,,
maybe
you
juggling
too
many
merge
requests.
and
you
just
want
to
step
back
from
from
coding
and
jump
in
from
projects,
projects
and
and
just
kind
of
sit
and
yeah,
put
some
implementations
together
and
help
help
some
people.
E
E
A
A
E
E
Mediastudio,
marco
zille:
and
the
that
that
issue
that
I
looked
at
the
other
week
was
another
perfect
example,
because
I
was
sure
all
the
changes,,
all
all
the
the
the
quick
action,
the
invitations,
and
the
rest.
api..
They
are
all
calling
the
update
service..
So
we
could
just
make
a
change
on
the
update
service.,
but
that's
not
really
the
case.,
but
I
only
found
that.
A
E
Lee
tickett
(contributor
success):
no,-
maybe
that's
okay
for
this
kind
of.!
So
so
I
I
I
can
say
like
a
bit
of
a
cheat
and
the
the
half
hour
that
we
might
have
wanted
to
to
spend
code
in..
You
can
watch
the
pairing
from
this
morning,
which
you
see,.
I
know
you
were
there
anyway.,
but
we
were
working
half
of
the
time
on
creating
a
new
web
hook.
B
B
Lee
tickett
(contributor,
success):
yeah.
and
our
feedback
is
a
great
example,,
but
also
for
this
kind
of
pointy
score.
Any
sort
of
system
which
I
I
I
know,
is
a
sort
of
interesting
topic.
and
it's
not
the
answer
to
all
our
problems.,
but
you
know,.
If,
if
we
can
start
seeing,
like
all
issues.
hot
merge,
requests.-
and
you
know
someone's
activity.
it
it,
it
can
be
really
helpful
to
to
kind
of.
B
Lee
tickett
(contributor
success):
get
behavior.
and
yeah,
they.
Definitely
we
set
out
here
that
we
want
to
start
picking.,
I'm
gonna
call
them
contributor
of
the
month
as
opposed
to
mvp.
or
but
but
you
know,
people
that
are
exhibiting
that
the
the
right
behavior.,
if
that
makes
sense,
it's
not
necessarily
someone.
That's
delivering
the
most.