►
From YouTube: Drupal Contribution Recognition Upstreaming Conversation
Description
This conversation is between Drupal and GitLab's Christos and Nuritzi, from the Community Relations team, about upstreaming Drupal's contribution recognition features.
During this video chat, Tim Lehnen, Drupal's CTO, shows what the contribution recognition features look like and answers questions about it.
A
B
Yeah,
no,
no
problem,
so
you
know,
as
I
was
saying
in
2016,
we
decided
we
wanted
to
understand
the
contribution
ecosystem
around
drupal
and
where
the
actual
contributions
were
coming
from,
whether
they
were
done
by
the
nights
and
weekends
sort
of
open
source
volunteer
that
people
imagine
in
their
heads
or
whether
they
were
done
by
people
whose
time
was
sponsored
by
their
employers
or
you
know.
If
it
was
part
of
client
work,
they
were
contributing
back
so
to
track
this.
B
B
I'm
doing
this
on
behalf
of
the
organization
I
work
for
or
on
behalf
of
the
customer
or
client
that
I'm
working
for
and
you
can
do
sort
of
any
combination
and
permutation
of
these
things,
because
we
certainly
have
contributors
who,
when
we
first
launched
this,
we're
like
well
hey.
Sometimes
I
I'm
doing
something
for
my
day
job.
But
then
I
work
nights
and
weekends
on
it
too,
and
I
want
that
recognition
as
a
volunteer,
as
well
as
doing
it
for
my
employer.
B
So
the
ui
that
we
built
in
our
issue
queue
looks
something
like
this,
where,
as
you're
adding
a
comment
to
the
issue
queue,
you
also
have
the
ability
to
adjust
the
attribution
or
you
just
you
know,
ignore
this
entirely.
Leave
it
at
the
default
you
set.
You
know
when
you,
when
you
set
up
sort
of
the
standard
on
your
profile
for
for
what
it
means
for
your
work
and
that
data
goes
in
there.
B
So
we
the
I,
as
I
said
before,
what
we're
really
started
out
trying
to
do,
is
just
measure
and
understand
where
all
these
contributions
are
coming
from.
So
since
2016,
when
we
did
this,
we
take
that
data
and
dries
puts
out
an
annual
blog
post
with
a
report
about
contribution
in
the
drupal
ecosystem,
and
so
it
includes
you
know
how
much
contribution
we
get
in
general.
B
It
talks
briefly
about
what
these
things
are:
the
kinds
of
things
that
we're
working
on
like
which
which
projects,
because
drupal
has
core
and
almost
40
000
modules,
themes
and
distributions,
and
also
like
how
many
of
these
issues
are
even
non-code,
related
they're
about
governance,
they're
about
community
events,
they're
about
all
sorts
of
things.
So
we
get
this
sort
of
data
and
in
particular
we
we
start
to
get
these
okay.
B
We
also
know
roughly
how
many
of
those
contributors
are
actually
doing
sort
of
most
of
the
work.
Roughly
half
of
them
only
got
one
credit
in
that
year.
The
top
30
have
20
of
the
total
right,
and
then
you
know
we
can
get
some
more
data
about
this
and
get
the
ratio
of
purely
sponsored
and
sponsored
and
volunteer.
So
we
put
that
data
together
and
so
more
or
less.
B
What
we
discovered
in
drupal,
for
example,
is
that
close
to
65,
something
like
that
of
of
drupal
contribution
is
actually
happening
on
an
employer's
time
with
an
organizational
sponsor,
so
the
the
individual
contributor
is
doing
it
as
part
of
their
day,
job
or
their
client
said,
they're
allowed
to
contribute
that
work
back
in
some
form
and
we
track
who
those
organizations
are
so
measuring.
This
was
sort
of
the
the
first
step,
but
we
went
from
there
to
okay.
B
Well,
how
do
we
leverage
that
data
to
improve
the
contribution
health
of
the
community
and
for
us
what
that
meant
was
providing
recognition
to
again
those
individuals
who
contribute?
We
try
not
to
rank
individuals,
that's
not
kind
of
the
sort
of
ethos
that
we
want,
but
we
want
to
recognize
hey.
Some
of
these
people
were
really
important,
but
then,
on
the
organizational
side
we
want
to
say
hey.
B
These
are
the
service
providers
who
you
should
work
with
because
they
contribute
the
most
to
the
drupal
project,
or
these
are
the
best
employers,
because
they
let
their
employees
contribute
all
those
sorts
of
things.
And
so
we
started
using
contribution
data
to
govern
the
marketplaces
of
services
that
we
provide
on
drupal.org.
So
all
of
these
service
providers
that
are
in
the
drupal
ecosystem
are
ranked
by
their
contribution
credits
and-
and
we
take
it's
a
little
bit
more
complex
than
just
this
data.
B
B
A
C
B
Yeah
not
attributed
you
can
see,
is
less
than
20
of
the
issues,
so
it's
actually
pretty
highly
used.
It's
something
that
became
as
soon
as
we
made
it
available.
This
notion
that
people
could
say:
oh
gosh,
I
can
actually
explain
why
I'm
able
to
do
this
work.
People
found
it
really
compelling
and
really
important.
So
so
the
take-up
has
been
very,
very
strong.
Also,
the
fact
that
we
let
you
sort
of
set
a
default
and
sort
of
not
worry
about
it
after
you've
said
it.
C
B
Yeah
well
exactly
they
don't
really
like.
They
don't
really
make
a
big,
a
big
difference.
Now
there
are
actually
some.
There
are
actually
some
signals
that
we
also
kind
of
report.
So,
for
example,
you
know
on
a
on
a
user
profile,
we
have
a
list
of
all
the
places
where
they,
where
a
person's
been
credited.
So
these
are
closed,
fixed
issues
where
the
maintainer
sort
of
agreed.
B
Yes,
you
were
one
of
the
contributors,
one
of
the
nice
things
about
this-
is
it's
again,
not
just
a
commit
history,
so
someone
who
goes
in
as
a
reviewer
or
an
accessibility,
maintainer
or
usability
expert,
or
something
like
that
or
just
a
commenter
who
provides
something
useful,
can
still
get
a
form
of
credit.
That's
not
based
on
having
a
commit
authorship
or
something
like
that
added
there's
other
ways
to
handle
that,
but
that's
one
of
the
the
things
we've
done
in
this
project
and
similarly
you
might
ask
okay.
B
Well,
you
know:
does
everybody
who
just
go
in
there
automatically
sort
of
wind
up
being
credited,
but
the
way
this
works?
So
we
have
a.
We
have
a
drupal
core
issue
here,
for
example,
and
you
can
kind
of
see
there's
just
a
little
hover
that
tells
us
for
each
contributor
kind
of
what
their
attribution
is
and
yeah.
B
That's
awesome,
yeah,
it's
pretty
cool,
and
now
you
know
when
I
think
about
this
and
what
we
want
to
do
next
and
and
think
about
with
kind
of
working
working
with
gitlab
on
this
is
I
realize
what
we've
built
is
fairly
custom,
of
course,
to
our
workflow
and
the
drupal
project,
but
I
think
there
are
some
underlying
principles
that
could
be
useful
kind
of
a
cross
open
source.
So
that's
kind
of
where
I
want
to
pick
your
brain
and
think
about
what
the
right
next
steps
are.
So
let
me
pause
again.
A
B
Yeah,
so
at
the
moment
we
don't
we
don't
worry
about
getting
too
much
more
granular
on
an
individual
like
issue
basis
right.
So
at
the
end
we
don't
kind
of
separately
calculate
out.
You
know,
50
of
this
issue
was
volunteer
and
50
was
by
the
organization.
We
just
say
hey
for
this
issue.
There
was,
even
if
it
was
the
same
person,
there
was
one
person
who
was
doing
it
as
a
volunteer
and
there
was
these
organizations
involved,
so
we
just
kind
of
add
them
together.
B
B
A
B
They
were
contracting
with
us
and
they
put
our
name
on
it
and
that's
cool,
but
we
actually
didn't
go
through
legal
to
do
that.
So
could
you
edit
and
take
that
off,
and
so
we
do
have
just
as
an
administrative
ability
we've
gone
through
and
been
able
to
remove
those,
and,
of
course
they
could.
We
we
let
the
whoever
sets
the
attribution,
even
after
the
issues
close,
they
can
go
back
and
change
this
and
be
like
whoops
site.
B
I
had
the
wrong
organization
or
they've
since
reached
out
to
me,
and
I
I
want
to
take
that
off.
It
hasn't
been
a
very
common
issue,
like
I
said,
I
think
it
happened.
One
case
with
a
pharmaceutical
company.
That's
very
sensitive
to
their
brand.
Slash
may
have
recently
developed
one
of
the
current
vaccines,
but
yeah.
That's
that's
the
one
that
I
can
okay,
cool,
yeah,
so
sort
of
taking
it
from
here.
B
You
know
the
reason
I
went
to
naritsi
to
talk
about
this
is
so
we're
at
a
place
where
we'd
like
to
accelerate
our
adoption
of
gitlab
features.
So,
like
I
said,
we
use
git
lab,
merge,
requests,
we
use
the
code
viewing
and
web
ide
and
we're
starting
to
use
ci
and
pipelines.
The
biggest
thing
we're
missing
is
that
we're
still
using
our
own
issues
and
there's
there
were
sort
of
two
reasons
for
that
one
was
we
have
a
bunch
of
custom
metadata
we
can
handle
that
with
scoped
labels.
B
Now
the
other
was
this
credit
system.
We
didn't
want
to
just
sort
of
throw
it
away.
So
there's
a
there's,
a
few
possibilities
you
know
for
us.
One
thing
we
can
do
is
we
could
continue
to
maintain
a
sort
of
separate
sort
of
custom
code
base,
use
an
api
to
get
the
comment.
History
associate
that
with
a
drupal.org
profile
that
has
attribution
data
and
sort
of
retroactively,
build
a
credit
history
based
on
gitlab
issues,
but
you
can
sort
of
see
how
that's
a
little
bit
hacky
and
janky.
B
The
other
question
is:
is
there
the
capacity
within
what
git
lab
sort
of
offers
on
a
self-hosted
instance
to
build
to
build
a
plug-in
for
this,
but
you
know:
would
that
potentially
break
in
get
lab
upgrades,
or
could
we
upstream
it?
Is
there
a
version
of
this,
even
if
it's
not
exactly
what
we
do
now?
That
would
be
valuable
kind
of
across
get
labs
customers,
particularly
the
open
source
projects.
So
yeah,
that's
kind
of.
C
Thank
you
I'll,
take
the
part
of
upstreaming,
I
guess
and
rich.
You
can
take
the
other
part
about
whether
it
can
be
a
custom
solution
or
not.
I
guess
sure
I
don't
know
so.
My
my
original
thought
is
like
I
love
it.
We
not
really.
I
do.
We
have
similar
situations,
I
mean
if
I
can
quickly
start
my
screen
right
now.
We
use
viteria.
C
C
It's
not
a
cross
gitlab
over,
so
in
any
case.
So
what
I'm
trying
to
say
here
is
that
this
feature
that
you
just
saw
to
me
showed
to
us
sorry,
it's
it
solves
sort
of
a
lot
of
our
problems.
I
mean
some
of
the
things
that
you
report
already.
We
can
report
them
through
bitters
analytics
because
we
can
have
reports
about
organizations
about
time
zones.
B
C
C
I'm
really
interested
in
apps
in
finding
a
way
to
see
whether
that
worth
upstreaming
it
explore
it
with
engineers
and
be
able
to
see
you
know.
For
me,
it
makes
a
lot
of
sense,
combining
both
you
know,
having
the
ability
to
do
self
report
and
associate
give
credits
to
people
or
provide
more
information
about
the
kind
of
contribution
that
you're
making
because
understanding
understanding
the
multiple
contributions,
the
intention
for
contributing
and
what
keeps
people
around.
C
C
As
norissa
said,
it's
been
only
four
months
that
I'm
here
so
I'm
still,
you
know
looking
around
not
looking
around.
You
know
it's
gonna
be
great
success.
For
me
to
understand
how
we
can
we
can
we
can
do
that
so
yeah,
I'm
really
interested
in
that,
but
I
know
for
a
fact.
I
know
that
upstreaming
is
gonna.
Take
a
lot
of
time
for.
B
A
But
I
just
wanted
to
also
mention
that
I've
heard
sid
specifically
ask.
I
think
this
was
christos
before
you
were
here,
how
we
keep
track
of
contributions
that
are
non-code
based
necessarily
so,
like
people
commenting
and
suggesting
things,
and
so
this,
I
think,
really
addresses
that
so
and
it's
a
gap.
I
think
that
we
currently
have
so
I
I
think
that
it
would
be
well
received
and
just
like
seeing
how
it
all
works
is
really
helpful.
B
At
all,
please,
please
go
ahead,
yeah!
Nothing!
Nothing
is
proprietary
in
this
kind
of
stuff,
so
please
do
and
yeah.
You
know,
I
think,
that's
that
was
that
was
kind
of
the
the
sort
of
secondary
discovery
after
we
started
by
just
trying
to
measure
who
was
involved.
You
know
originally
we
were
like
well.
Could
we
make
a
special
syntax
for
commit
messages
that
used?
B
You
know
special
characters
before
organization
names
or
whatever,
and
then
we'd
parse
it
all,
and
then
we're
like
well
a
that
relies
on
people
typing
something
right
which
is
never
good
and
b.
You
know,
there's
all
these
non-code
contributors
or
even
sort
of
code
contributors,
but
they're
not
submitting
a
commit
or
a
merge
request
directly
themselves,
and
this
this
proved
to
be
a
really
valuable
part
of
that.
So
yeah.
A
Yeah
and
again
like
we
had,
I
know
we're
almost
at
time
that
just
you
talked
about
some
of
this
being
special
snowflake,
but
I
don't
think
that
that's
really
the
case.
I
think
that
this
could
be
valuable
for
so
many
different
open
source
organizations
that
really
do
want
to
understand
where
their
contributions
are
coming
from,
which
companies
are
participating
all
that
kind
of
stuff.
So
I
think
that
as
an
ecosystem
like
provider,
we
have
this
unique
ability
to
help
with
that.
B
B
Yeah,
so
we've
talked
with
chaos
about
how
our
system
works
before,
because
they've
been
sort
of
thinking
about
the
same
problem
space.
Although
to
my
knowledge,
they
haven't
sort
of
proposed
a
specification
for
sort
of
a
standardized
solution
that
could
be
used
and
then,
similarly,
the
university
of
vermont,
I
guess,
has
talked
about
they're,
doing
a
study
about
how
open
source
communities
sort
of
as
they
say,
the
mission
of
ocean
is
to
study
how
open
source
communities
come
together
to
solve
complex
problems,
et
cetera,
et
cetera,
et
cetera.