►
From YouTube: Your Team’s Open Source Contributions, in One Dashboard | Alex Courouble | CHAOSSConEU2019
Description
CHAOSSconEU2019 Session: "Your Team’s Open Source Contributions, in One Dashboard"
By Alex Courouble, Open Source Engineer, VMware
Slides: https://chaoss.github.io/website/CHAOSScon/2019EU/slides/Your-Teams-OSS-Contributions-in-one-Dashboard.pdf
With the rise of Open Source Program Offices in the industry, we are observing a rise in teams dedicated to upstream open source contributions. As this often represents the result of a large investment from a company, it is important to be able to quantify and monitor the team’s contributions over time. To answer this, we created a tool that tracks the open source contributions from a list of users. The tool uses Perceval and the GitHub API to track pull requests, issues, comments, reviews, commits authored, and commits merged. The dashboard then displays a summary of the team’s contributions, any user’s contributions as well as a series of charts.
A
A
A
How
many
companies
I
feel
have
a
program
office
at
the
can
open
source
program
office
and
I
found
this
great
blog
post,
and
it
said
that
70%
of
tech
companies
with
more
than
10,000
employees
will
have
I
got,
will
have
like
75
77
percent
likely
to
have
a
normal
store
program
office,
and
we
fall
in
that
category
and
now,
among
those
77
percent,
I
think
it
was
45
44
%
that
also
contributed
code
upstream
right.
So
it's
not
only
about
consuming
the
open
source.
A
It's
about
also
good
tuning
back
to
the
communities,
so
the
SCC
at
VMware
I
get
that
from
from
the
website.
So
our
mission
statement.
So
essentially
we
want
to
make
the
communities
better
and
we
want
to
contribute
more.
This
nandi
code
also
just
knowledge
and
reviews
and
everything
to
communities,
are
really
important
to
us.
So
we
have
five
areas
of
expertise
in
app
kubernetes
orchestration
containers
turn
which
is
donated
to
CN
CF.
A
So
we
have
like
one
guy
who
commutes
a
lot
to
kubernetes
and
he's
emails.
Every
week
swear
like
that.
So
he
took
him
a
good
amount
of
time
right
and
with
24
engineers
on
the
team
doing
that
it's
obviously
like
a
huge
loss
of
time
and
in
addition
to
that,
our
director
would
have
to
go
through
every
single
email
and
kind
of
copy.
Everything
and
read
his
report
right,
so
I
get
with
em
the
guy
we
met
and
we
kind
of
talk
about
how
we
can
automate
that
and
how
to
meet
all
the
old
process.
A
So
in
those
emails
we
talked
about
also
the
classic
stuff
pull
request,
reviewed,
submitted
and
merged
issued
open
comments,
but
also
you
know
stuff,
that's
less
quantifiable.
So
community
involvement
talks
things
like
that.
So
what
I
did
what
we
needed
is
essentially
the
dashboard
and
some
kind
of
reporting
tour
to,
because
it's
very
automated
all
right
so
to
like
just
displays
everything
specifically
to
github
and
to
get
data.
So
I
started
with
just
github
the
graph
QL
API
super
easy
to
use.
A
Looked
at
reviews.
The
sorry
issues
opened
issues
commented
on
issues
close
PRS,
Murs,
submit
it
and
the
any
comments
on
PRS
so
I
have
a
cron
job
that
just
queries
that
for
the
whole
team,
so
for
every
single
user
on
engineer
on
our
team
and
then
I
have
a
small
flask
API
that
serves
that
to
front-end
and
later,
like
the
people
that
contribute
to
Linux.
A
What
kind
of
jealous
that
they're
they're
very
the
commits
were
not
on
a
tool
right
or
like
well,
we
also
want
to
have
a
or
a
work
like
being
recognized,
so
I'm
I,
looked
at
personal,
which
is
really
useful.
I
have
a
list
of
repositories
that
I'm
forcing
every
day
just
to
get
the
reason
the
commits,
and
they
also
helped
us
getting
more
informations
through
the
three
to
github.
Api
I
wasn't
very
able
to
get
who
would
actually
merge
it
commit.
A
So
you
easy
to
find
who
wrote
it
coming
right,
but
to
find
who
merger
commit
to
github.
Api
wasn't
really
really
clear
with
that.
So
I
just
used
first
of
all
and
look
at
the
commit
commit
er,
that's
supposed
to
Green
author,
and
that
gave
us
a
sense
of
who
are
the
people
who
actually
gonna
review
the
commits
and
merge
them.
A
So
right
now
the
tool
is
it's
not
open
source?
Yet
it's
like
I'm
only
spending
5%
of
my
time
on
it.
It's
kind
of
hacked
it
together
since
last
August,
and
we
have
a
couple
views.
I
have
a
lot
of
work
ahead
of
me,
but
might
be
a
little
small,
but
listen
it's
a
summary
for
the
whole
team.
You
can
change,
you
can
change
the
you
can
choose
a
time
range,
you
see
all
the
/
projects
and
then
for
each
project.
A
You
see
the
poor
request,
commands,
pull
requests,
merged
issues,
open
issues,
comments
and
from
a
director.
It's
super
easy
to
just
go
and
go
in
there
copy
and
paste
into
it
report
and
then
for
any
engineers.
We
don't
have
to
spend
right
to
two
hours
like
three
hours
that
they
come
to
on
Friday
when
you
want
to
go
home
just
to
put
their
report
together.
A
So
also
we
saw
abstract
created
that
he
wanted.
He
wanted
more
granularity
when
it's
more
and
more
details,
so
I
could
you
to
pay,
for
you
can
choose
a
specific
project
or
choose
an
organization,
for
example
the
hey
directed
open
ad
organization
and
it
just
aggregates
all
the
projects
together
and
get
all
that
data
to
again.
You
can
choose
a
time
range.
You
can
go
back
as
soon
as
as
far
as
the
the
engineers
were
hired
and
also
wanted
to
include
something.
A
They
also
wanted
to
include
some
charts,
because
we
want
to
know
how
the
the
investment
that
the
my
made
to
them
our
team
is
paying
out.
So
those
are
the
charts
starting
at
the
beginning
of
the
of
our
our
team.
You
can
see
it's
growing,
it's
growing.
It's
a.
There
was
some
issue
here
with
a
the
issues
open.
One
of
my
colleagues
had
imported
projects
and
his
crepe
kind
of
failed
and
import
a
bunch
of
issues
on
the
same
date.
A
A
Maybe
I
know.
Starting
head
is
probably
the
best
the
best
use
case
for
this,
but
a
better
way
to
manage
our
enemies
to
know
when
someone's
going
when
they
left
and
things
like
that.
What
team
they're
on
so
that's
right
now,
I'm,
just
I
just
have
a
config
file
that
I
have
to
like
hard-code
myself,
like
mentoring
myself,
then
the
graph
right
now
only
have
grass
for
the
entire
team
and
for
the
entire
length
of
the
our
team
of
our
of
my
team.
A
So
we
want
to
be
able
to
have
those
grass
for
a
specific
person
for
a
project
for
the
whole
team
for
pretty
much
any
entity.
That's
on
the
that's
in
the
my
database
and
obviously
I
would
like
to
eventually
either
open
source.
The
whole
thing.
If
there
is
enough
interest-
or
maybe
some
parts
of
the
implementation,
I
was
just
talking
with
the
personal
people
about
potentially
doing
some
work
with
graph
QL,
because
right
now,
first
of
all,
our
new
supports
the
the
old
github
API,
so
I'm.
Hopefully
we
can
work
together,
something
like
that.
A
And
obviously
the
graph
QL
API
stability
billing
bill,
so
it's
still
a
sell
work
work
to
be
done
from
get
out
there.
So
let
me
I'm
about
halfway
done.
Let
me
show
you
the
to
a
little
bit
more
hands-on,
so
it's
running
like
in
a
small
VM
in
California
right
now,
so
it's
not
the
fastest
so
how
to
run
it
locally.
A
A
We
worked
along
with
my
director
to
kind
of
get
them
like
a
good
format
for
him
to
copy
and
paste
into
an
email
that
he
will
like
eventually
submitted
upwards,
so
the
things
that
the
team
gets
so
big
if
it's
edge,
one
that
we
start
having
some
of
the
data
right,
so
you
can't
just
go
fill
all
of
that.
This
is
too
much
so
we'd
go
through
a
specific
user.
You
can
just
look
up
someone
here.
Here's
a
lot
of
PRS
because
he
his
work
here
every
link
will
lead
the
to
the
link
on
github.
A
A
A
So
here
all
our
communities
project
we
that
we
contribute
to
have
are
just
aggregated
in
one
view,
so,
for
example,
for
the
for
the
team
lead
for
the
service
for
the
Lark
Association
team
go
in
here
and
I
can
look
at
the
his
all
of
his
employees
a
little
bit
engineers.
The
charts,
like
I,
said
pretty
straightforward.
I
was
gonna
hike.
This
together
like
it's,
it
could
be
improved,
obviously,
ideally
like
to
have
like
to
be
able
to
input
the
time
periods
the
nice
per
month.
A
We
wanted
to
see
my
quarter
because
we
work
of
no
facial
quarters
and
obviously
I
also
want
to
aggravate
those
those
those
charts
per
specific
engineer.
So
someone
one
person,
you
want
to
see
how
much,
how
Devin
evolving
and
everything
flow
created
a
Status
page
that
a
little
of
issues
at
first
with
my
services
that
were
not
or
crashing
you
know
we're
not
operating
properly
and
yeah.
So
that's
the
tool,
obviously
still
a
lot
of
a
lot
of
work
in
progress.
Let
me
go
back
to
the
presentation.
A
We
have
a
lot
of
teams
now
that
said
of
the
open
source
technology
center
that
contribute
more
and
more
to
open
source,
so
they
might
be
interested
in
it
and
we
yeah
so
I
was
kind
of
want
to
give
you
interest
and
see
what
part
people
are
interested
in
and
that's
about
it
so
and
one
has
any
question:
I
think
we
have
a
lot
and
I
favor
any
more
time.
Yes,
I
know
we
have
free
limits.
If
anyone
has
any
question
otherwise,
yeah.
A
B
A
A
B
C
B
C
C
A
I
can't
I
can't
really
talk
for
my
boss.
My
big
big
boss,
right
I,
think,
is
just
a
forward
for
them
a
way
to
track
how
the
team
is
doing
and
I
got.
What
first
of
all
were
to
contributing
like
what
impacted
making
on
those
communities
this
project
and-
and
it
was
a
big
investment
for
VMware.
So
they
want
to
make
sure
that
things
are.
C
A
And
that's
why
I?
Actually,
let
me
go
back
to
to
the
tool,
but
that's
why
so
in
a
summary
version,
which
is
the
part
that
here
actually
copies
and
pastes
I
made
a
summary,
especially
for
the
comments,
because
you
know
like
on
long
PRS
and
issues.
If
you
people
get
a
lot
of
comments
and
you
would
get
a
huge
list,
so
that's
why
I
respect
summarize
one
comment
on
one
poor
request
but,
for
example,
for
the
actual
pro
request:
that's
pretty
important
stuff
right
so,
like
I
actually
list
the
individual
be
ours.
B
So
my
question
was
around:
are
it
sounds
like
you're,
using
this
purely
for
like
internal
performance
tracking
and
seeing
for
the
student?
What
you
thought
about
using
this
tool
like
see
where
you
are,
relatively
speaking
with
the
larger
projects
in
which
you're
working
I
mean
so
like
kubernetes,
there's
a
lot
of
smell
bad
yeah.