►
From YouTube: OSPO panel discussion - Universe 2022
Description
In this panel session, OSPO experts working at F5, Google, Spotify, Fannie Mae, and the CHAOSS project will share insights about the value that data brings to the success of OSPOs. The OSPO experts will also discuss the role data plays in their decision making today, and how data could be used to better inform their thinking in the future.
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
A
Open
source
program,
offices
or
auspos
are
kind
of
a
really
interesting
new
thing
that
businesses
and
organizations
of
all
sizes
are
starting.
They
do
lots
of
different
things,
manage
legal
security
and
best
practices
around
open
source.
Some
of
them
are
responsible
for
improving
engineering,
best
practices
at
their
organizations.
A
Others
are
really
invested
in
these
deep
open
source
strategies
for
their
businesses,
and
so
today,
we've
got
some
folks
with
us
who
are
going
to
tell
us
about
their
their
I
suppose
that
their
organizations
and
what
they're
focused
on
so
just
so.
We
can
calibrate
a
little
bit
with
the
room
just
to
show
hands.
Who
knows
what
a
nozpo
is.
A
Okay,
that's
good
who
has
won
at
their
organization?
Okay,
that's
also
good
who's.
Who
here
is
running
it
at
their
organization:
okay,
okay
and
who's.
Thinking
about
starting
one,
maybe
but
doesn't
have
one:
are
there
anyone
any
folks
who
are
sort
of
Oz
po
interested,
but
not
sure,
yeah,
okay,
good,
okay,
all
right
great!
So
we
have
yeah.
We
have
four
great
panelists
today
who
are
going
to
share
their
experience
with
us.
So
why
don't
you
take
it
away
and
introduce
yourself
so
Christine
as.
B
D
E
Hello:
everyone,
Sophia
Vargas
I'm
in
Google's,
open
source
programs
office
as
a
program
manager,
but
I
like
to
refer
to
my
role
as
a
general
purpose:
analyst
supporting
our
various
teams
across
ospo
and
outside
of
ospo
with
data
related
work,
I'm.
Also
an
active
member
of
the
chaos
Community,
where
I
work
with
external
members
on
how
to
define
project
project
metrics
for
things
like
health
and
sustainability.
A
Cool
well
welcome,
and
just
so
you
know
we're
going
to
save
about
five
minutes
for
the
questions
from
you
all
at
the
end.
So
if
you
have
questions
you
want
to
ask
this
group
there'll
be
time
for
that
and
we'll
probably
just
hang
around
outside
afterwards,
so
maybe
Sophia.
Maybe
you
can
start
us
off
I'm
curious,
like
what
kind
of
decisions
do
you
help
Google
with
in
the
auspo
at
Google,
like
what.
E
Car
yeah
so
I
mean,
first
and
foremost,
our
organization
is
essentially
responsible
for
how
we
engage
in
open
source
communities,
both
setting
policies
around
how
we
consume
and
release
open
source
code,
providing
the
central
point
of
authority
on
license
compliance
use
process
and
offering
tooling
and
support
in
terms
of
what
I
support
as
an
analyst
I'm
generally
looking
for
feedback
metrics,
how
well
are
things
being
adopted
used?
How
are
things
changing
and
try
to
provide
input
on
how
we
need
to
adjust
our
programs.
A
E
And
so
I
guess
it
would
be
operations.
Team
has
a
lot
of
metrics
for
feedback
in
terms
of
how
programs
are
going.
Are
we
doing
well?
Are
things
changing?
Are
people
using
our
processes
or
are
they
doing
something
else?
I
think
from
my
work,
particularly
I
focus
more
on
better
understanding,
engagement
levels
within
open
source
across
all
of
alphabet.
So
understanding
is
this
growing
changing?
Are
our
processes
accessible?
Are
people
complying?
Are
they
sharing
with
us?
What
they're
doing
and
whether
or
not
we
can
identify
areas
that
need
to
be
adjusted
say?
E
A
C
Okay,
so
decisions
so
we're
a
relatively
newer,
open
source
program
office.
So
what
we're
doing
right
now
is
we're
getting
ready
to
launch
external
contributions
to
open
source
projects
from
our
engineers
and
our
technologists
to
go
out
from
a
financial
services
company.
So
we
are
in
the
process
of
becoming
like
better
corporate
citizens,
because
we
care
about
the
software
that
we
consume
and
we
care
about
the
maintainers.
So
it's
pretty
exciting
time
right
now,.
D
So
we've
been
doing
open
source
for
10
years.
We
have
a
quite
large
portfolio
of
various
projects
in
various
States,
so
a
lot
of
the
data
we
collect
is
to
look
at
what
is
the
health
of
different
projects?
Are
we
doing
enough
here?
Is
this
actually
something
we're
not
really
caring
about
anymore
and
should
just
archive
should
be
responsible
about
what
we
try
to
distribute?
B
So
we're
also
pretty
much
new
open
source
program
office.
So
some
of
the
things
that
we're
trying
to
think
around
is
a
strategy
and
open
source
is
basically
also
using
and
releasing
publishing
or
also
contributing
back.
So
some
of
the
more
interesting
things
that
could
be
around
data
is
what
are
some
of
the
open
source
projects
of
the
key
open
source
projects
that
you're
consuming.
And
how
do
you
become,
as
you
said,
a
good
open
source
Citizen
and
contribute
back
to
the
ones
that
you
strategically
care
about.
B
So
some
of
the
data
that
could
be
useful
is
like
what
is
actually
being
consumed,
and
then,
alongside
that,
maybe
with
some
of
the
outside
metrics,
some
of
the
more
interesting
things
could
be.
What
are
some
of
those
projects
that
are
being
that
need
help
that
maybe
maybe
not
the
most
popular
but
ones
that
not
only
you
care
about,
but
in
the
industry
as
a
whole,
cares
about
as
well
right.
A
So
you're
sort
of
hinting
towards
I
think
what
per
said
before
like
Health
right.
This
is
one
of
these
things
that
I
think
we
talk
a
lot
about
in
in
in
the
sort
of
auspo
world
which
is
like
we
want
projects
that
we
are
building
and
maintaining
to
be
healthy
or
the
ones
that
we're
dependent
upon
to
be
healthy
and
like
who
wants
to
take
a
stab
at
like
defining
what
that
means.
Maybe
the
chaos
person
at
the
end
could
ever.
E
Go
I
would
I'm
always
answer
it
with
the
awful
answer
of.
It
depends
right,
so
I
look
both
at
a
macro
portfolio
level,
as
well
as
in
working
with
individual
project
teams,
on
understanding
what
their
goals
are,
because
you
can't
really
define
success
if
you
don't
know
what
you're
working
toward
so,
it
could
be
as
simple
as
increasing
engagement
in
the
community
or
ensuring
that
our
external
contributors
have
the
same
experience
as
our
internal
contributors
without
the
same
experience
or
resources
available
to
them.
E
So
looking
for
signals
that
might
say
how
quickly
are
we
responding
to
pull
requests
from
non-googlers
or
how
many
of
those
pull
requests
are
getting
merged
into
the
central
project
as
an
indicator
of
whether
or
not
we
need
to
improve
or
fine-tune
our
documentation
templates
guidance
training
in
the
external
community?
So
that's
just
one
example
of
ways
that
we
are
looking
at
what
what
health
means
in
that
context
and
then
trying
to
set
metrics
against
those
goals.
D
Or
no
so
I
think
we
try
to
go
in
the
complete
opposite
direction,
not
because
this
is
not.
This
is
great.
This
is
valuable
and
you're
going
so
much
into
depth
of
this
and
you're
so
much
more.
An
expert
about
this
than
I
am
so,
but
we
try
to
collect
four
smaller
metrics
that
is
actionable
for
our
teams,
and
this
is
like
these
are
the
four
things
you
need
to
care
about.
We
can
always
make
it
more
advanced,
but
just
starting
small
and
say
this
is
like
your
activity.
D
You
have
the
last
three
months.
This
is
the
number
of
contributors
you
have
internally
externally.
Do
you
have
any
security
vulnerabilities?
Do
you
have
anything
like
stale
like
issues
or
pull
requests
that
you
haven't
reacted
to,
and
we
boil
that
down
to
like
a
score?
That's
like
red
or
green.
Basically,
okay,.
A
So
more
like
a
school
card
just
for
them,
yeah,
nice,
okay,
that's
interesting,
so
Christine
I
know:
you've
got
some
thoughts
on
the
sort
of
relationship
between
metrics
that,
for
us,
posts
can
track
and
security.
Do
you
do
you?
What
what
would
you
want
this
room
to
know
about
the
kind
of
work
that
you
you
all
do
in
that
space
yeah.
B
For
obviously,
open
source
is
heavily
used
and
consumed
and
popular
and
security
is
it's
a
big
attack
surface?
So
what
is
what
is
metrics
play
a
role
in
it,
and
so
some
of
the
things
that
you
would
possibly
be
interested
in
alongside
the
vulnerabilities
that
a
project
has
you
also
want
to
be
thinking
about.
We
talked
about
like
the
health,
because
in
a
sense,
if
the
community
is
around
it
and
is
big
and
growing,
it's
kind
of
an
indicator
of
good
in
the
sense
that
it's
being
fixed
as
fast
as
they
come.
B
So
there's
like
an
aspect
of
security
project
s
other
things
again
like
how
many
vulnerabilities
are
out
there
in
a
particular
software,
and
there
are
like
a
lot
of
different
people
who
are
thinking
about
it.
For
example,
depths.dev
is
a
website,
though
you
can
go
and
actually
look
at
a
lot
of
different
metrics.
There's
like
open
source
security.
Foundation
has
a
project
called
scorecards
right
where
you
can
look
at.
How
does
a
project
kind
of
have
all
these
like
metrics
around
scoring
like
what
is
the
best
practices
that
it's
following?
Do
they
have
things
like?
B
Branch
protection
turned
on
and
all
of
these
different
things
that
you
can
actually
score
a
project
on.
So
these
are
some
of
the
things
that
you
want
to
kind
of
like
any
open
source
project
that
you're
consuming.
You
want
to
have
some
measure
of
like
what
are
the
metrics
around
what
you
term
security
and
again
it
could
depend
on
what
it
is
that
you're
you're
looking
for
and
one
awesome,
might
think
about
security
or
look
at
all
of
the
data
and
wait
it
separately.
B
B
Yeah,
yes
back
to
that
kind
of
thing,
so,
there's
like
that
is
there
only
one
maintainer
and
some
some
ecosystems,
like
a
lot
of
JavaScript
projects,
may
only
typically
have
like
one
maintainer.
There
are
all
of
these
research
reports
that
say
that
some
of
the
more
popular
packages
out
there
are
maintained
by
only
a
handful
of
people,
but
you
have
to
be
like
mindful.
B
If
it's
just
one
maintainer,
if
you're
an
Oscar,
can
you
actually
help
them
with
more,
maybe
more
than
just
donations
by
your
time
as
well,
and
in
addition
to
that,
there's
the
bus
factor
and
then,
if
you
have
an
open
source
project,
what
is
like
that
diversity
of
like?
Are
there
big?
How
many
companies
are
actually
contributing
to
that
project
is
also
kind
of
like
key
to
that
interesting.
C
So
I
always
think
because
there
is
so
there
are
so
many
projects
with
single
maintainers.
We
try
to
cultivate
a
culture
where
there
are
multiple
maintainers
on
the
project,
because
anybody
could
leave
the
company.
Anybody
could
abandon
their
project
and
then
what
we
would
do
is
we
would
go
and
archive
it
and
make
it
read
only.
But
if
we
have
multiple
maintainers
on
the
project,
we
cultivate
that
culture
of
support,
then
that's
a
really
strong
way
to
start
open
source
projects.
C
D
Yeah
we
have
the
same
kind
of
approach
as
well.
We
we've
had
a
long
history
of
of
Engineers
being
enabled
to
do
what
they
feel
is
the
right
thing
to
do
through
autonomy
and
being
driven
by
Passion,
but
I.
Think
for
us,
a
more
stable
ownership
of
a
project
is
to
boil
it
down
so
that
there's
a
team
that
owns
it.
D
So
it's
a
team
decision
also
because
then
it
comes
down
to
saying
the
team
also
has
to
make
a
call
saying:
okay,
we
we
own
this
thing
and
we
do
need
to
invest
ours
into
this
project,
to
probably
maintain
it
and
that's
going
to
go
away
from
the
other
team
responsibilities
that
you
do
so
you
kind
of
have
to
budget
for
that
time
as
well.
So
that's
the
metric.
We
look
at
we
look
at.
D
Is
there
a
team
actually
taking
ownership
of
this,
and
then
we
also
look
at
the
activity
that
happens
in
the
proteins
area,
what
a
percentage
of
that
activity
actually
happens
during
working
hours,
so
looking
at
like
call
working
hours
and
weekends,
and
if
you
have
a
project,
that's
maintained
primarily
in
weekends
and
evenings
and
nights.
It's
a
fairly
good
indicator
that
this
is
actually
not
something
that
might
be
a
Core
Business
thing
to
actually
care
about.
Yeah
we
might
say.
Maybe
you
should
just
have
this
as
a
private
thing
and
that's
totally
fine
as
well.
D
C
And
then
to
also
to
add
on
top
of
that
as
as
well
so
there's
so
many
different
paths
that
one
can
get
into
within
open
source,
you
don't
necessarily
have
to
be
a
classically
trained
engineer.
So
another
great
thing
for
open
source
projects
is
Community
Management,
so
as
a
maintainer
you're,
always
sometimes
you
do
feel
like
a
lone
wolf.
But
if
you
have
somebody
in
your
team
like
on
your
side
as
your
community
person,
they
can
help
manage
the
intake
and
the
consumption
as
well
right.
So
yeah,
it's
a
good
track.
A
E
It's
a
markdown
file,
it's
it
might
have
some
get
history
around
it,
but
those
initial
conversations
and
discussions
are
happening
in
Zoom
meetings,
and
so
instead
we'll
have
a
record
in
that
document.
That
says
who
worked
on
it,
and,
and
so
we
have
a
we
try
to
create
our
own
ways
of
recording
other
styles
of
contribution
that
are
not
just
based
on
Version
Control,
Systems
right.
A
Yeah,
okay,
I
think
some
folks
in
this
room
probably
are
thinking
about
starting
in
Oz,
Pope
and
I.
Think
this
is
a
not
an
obvious
like
there's,
not
an
obvious
Playbook
I
think
it
depends
on
the
organization.
I
was
going
to
say.
Maybe
Britney
could
use.
Does
stuff.
Tell
us
a
bit
about
your
experiences
of
starting
I.
Suppose
like
what
what
you
know,
what
sort
of
organizations
might
want
to
do
this?
How
would
you
recommend
somebody
get
started?
It's
a
hoot
I'll.
C
Tell
you
so
one
of
the
biggest
things
I
would
think
when
starting
an
open
source
program
office
or
trying
to
cultivate
that
concept
of
good
corporate
citizenship
is
internal
culture.
We
have
to
really
educate
our
folks
inside
of
our
company
to
really
understand
the
the
gravitas
and
the
magnitude
of
how
much
open
source
software
is
being
consumed
and
the
importance
of
it.
C
And
so,
when
you
start
sharing
that
sort
of
vision
and
that
story,
you
get
lots
of
folks
on
board
and
you
get
more
folks
excited
about
giving
back
into
the
open,
because
many
times
when
you're
starting
up
an
open
source
program
office,
there's
possibly
just
maybe
a
third
of
your
core
engineering
team-
gives
back
and
understands
what
they're
doing.
But
if
you
share
that
concept
of
community
it,
it
really
grows.
B
One
of
the
key
things
is,
as
you
said,
is
that
you
want
to
take
a
look
at
the
company
as
you
jump
in
and
see.
Where
is
open
source
either
being
used
or
consumed?
What
are
the
bottlenecks,
so
it
might
stop
with
just
going
around
and
just
talking
to
a
whole
bunch
of
people.
What
are
their
thoughts
about
open
source?
Where
do
they
see
the
blockers?
B
Other
policies
that
the
company
has
favorable
or
are
they
do
they
kind
of,
like
prawn,
against
open
source
or
just
basically
taking
a
temperature
check
on
what
is
like
the
appetite
for
open
source
in
the
company
is
pretty
important
and
then,
after
that,
it's
a
matter
of
like
where
does
the
company
want
to
go
and
where
does
open
source
fit
strategically
into
its
business
model?
Some
companies
that
do
open
source,
it's
not
like
open
source
open
source,
might
be
something
that
they're
doing.
B
E
E
A
That's
right:
it's
not
the
best
price
you
want
to
be.
That
makes
sense.
So
there's
a
if
I
can
just
play
that
back
you're,
saying:
there's
a
sort
of
risk
that
the
remit
of
an
auspo
can
be
so
incredibly
Broad
you,
it's
generally
a
small
team
and
you
can
just
get
overwhelmed
and
actually
become
ineffective.
If.
D
You
look
at
any
tech
company
you
can
see.
Open
source
is
probably
part
of
most
of
what
they
actually
do
right
down
to
like
the
dependencies
with
infrastructure
and
so
on
also
what
the
engineers
want
to
do.
So,
if
you
feel
the
ospush
would
be
part
of
every
conversation
about
open
source,
you
have
to
kind
of
be
everywhere
and
that
doesn't
work
right.
So
you
have
to
kind
of
find
where
it
makes
sense
for
you
to
be
yeah,
yeah
and.
C
B
A
lot
of
it
is
also
around
like
automation
when
you're
talking
about
where,
where
as
per
sale,
is
fail.
It's
just
a
there's
like
the
aspect
of
likeness
of
people
and
like
there's
an
automation
part
of
it.
So
the
people
aspect
where
things
can
get
a
little
really
tricky
is
that
the
internal
relationships
that
you
need
to
work
with,
because
open
source
works
with
so
many
like
product
teams,
the
legal
teams,
engineering
teams
like
there's
so
many
hats
that
sometimes
you
need
to
wear.
A
A
You
know,
roughly
speaking
in
the
sources
like
work
like
an
open
source
Community,
but
within
you
know,
behind
the
firewall
of
your
organization,
so
adopt
some
of
the
same
practices
for
collaboration
and
sharing
and
reuse
Christine.
What's
what's
your
sort
of
experience
of
inner
source
of
companies
and
and
how
it's
the
same
as
open
source
and
the
work
of
an
OS,
Pro
or
and
how
it's
different,
I?
Guess
what
what.
B
I
I
joined
F5
about
a
year
ago
and
a
lot
of
the
engineering
teams,
just
the
nature
of
acquisition
and
all
are
very
siled
and
some
of
the
coach
codes
not
shared,
which
is
not
what
my
experience
was
so
inner
sources.
It's
actually
sometimes
like
a
stepping
stone
to
getting
people
thinking
with
an
open
source
mindset,
so
the
ability
to
share
code
internally
just
give
and
then
on
the
using
all
of
the
best
practices
around
open
source
can
allow
people
to
share
code
and
develop
products,
so
they
can
reuse
use
across.
B
So
that's
kind
of
like
where
I
see
inner
Source
can
have
break
down
silos.
It
can
help
like
build
community
and
it
can
help
basically
just
get
people
into
the
habit
of
like
what
does
open
source
look
like,
so
that,
if
you
actually
then
move
into
open
source.
Well,
that's
not
like
really
foreign
yeah.
A
B
We
inherited
like
the
inner
Source
work
as
well,
but
so
there's
some
things
that
are
very
similar,
like
there's
metrics
parts
of
it,
where
you
can
be
looking
at
the
same
thing.
What's
the
adoption
of
my
particular
component
within
the
entire
company?
Are
you
also
so
there's
some
things
that
you're
thinking
about
that
are
similar?
You
may
not
be
thinking
as
much
in
the
legal
aspects
and
then
a
lot
of
projects
might
go
through
like
the
pipeline
from
it
becomes
inner
source
and
it
eventually
becomes
open
source.
A
I'm,
just
paying
attention
to
time
we're
going
to
save
the
last
five
minutes
for
questions
so
I
just
want
to
skip
ahead
to
kind
couple
of
future.
Looking
topics:
I
guess,
open
question
to
you
all
like:
what's
the
thing
that
you're
most
excited
about
that's
happening
in
the
sort
of
auspo
world
right
now,
whether
it's
sort
of
research
that's
happening
in
Academia,
that's
helping
us
better,
understand,
Community,
Health,
new
tools
and
Technologies
or
auspose.
We
heard
about
Oz
po
at
the
World
Health
Organization
and
the
last
keynote,
which
was
super
cool
to
learn
about.
A
D
Something
for
me
personally,
I,
think
I
think
the
conversation
about
sustainability
and
viability
and
maintainers
and
their
maintain
a
burnout
I
think
that's
a
good
conversation
to
have.
What
kind
of
worries
me
a
little
bit
is
that
we
also
keep
steering
it
back
to.
How
can
companies
reduce
the
risk
without
actually
solving
the
problem,
but
I
think
it's
good
that
the
conversation
is
happening
as
well
as
the
the
funding
announcement.
D
A
E
B
C
You
know
the
pardon
me
yeah,
so
the
United
States
government
is
going
to
thoroughly
start
putting
open
source
program
offices
into
every
particular
sector,
which
is
exciting.
There
are
amazing
things
that
are
happening
in
Europe
and
there's
open
source
program
offices
that
are
popping
up
everywhere
and
Community
is
huge.
So
that's
what
I'm
really
excited
about
they're,
like
multi-sector.
A
F
So
I
have
a
question
about
inner
sourcing.
I
know
Google
might
be
doing
a
lot
of
inner
sourcing
and
do
you
face
any
challenges
in
in
respect
to
the
release
management
of
those
products,
because
a
lot
of
internal
teams
might
be
contributing
to
that,
and
also
do
you
see
a
challenge
opening
up
that
inner
source
project
to
the
outside
Community
as
open
source
project
from
the
licensing
or
IP
perspective,
because
you
have
to
go
through
a
big
process
to
make
it
an
open
source
project.
Yeah.
E
What
we've
been
thinking
more
about
is
how
to
create
better
Bridges
between
internal
systems
and
external
systems,
knowing
that
we
have
our
own
Version
Control
Systems
and
we
use
GitHub
for
a
lot
of
our
external
project
or
external
work.
And
so,
if
we
know
something
is
going
to
eventually
become
something
public,
then
we
advise
a
different
set
of
tooling
difference
in
the
infrastructure,
so
that
that
transition
is
simpler
versus
having
to
copy
everything
over
adopt
a
new
issue.
Tracker
adopt
a
new
mechanism
adopt
a
new
process,
create
new
documentation.
E
E
Even
if
it's
not
open
source
yet
so
that
that
transition
is
smoother,
because
it's
really
easy
to
use
a
bunch
of
internal
tooling
that
it
just
suddenly
becomes
unavailable
and
so
I
think
that
it's
it's
kind
of
a
tricky
model
to
balance,
because
I
think
some
things
might
never
leave
our
company
and
so
like
it's
not
as
necessary,
and
we
have
so
many
resources
internally.
That's
much
easier
to
use
all
those
things
so
I
think
it's.
E
It
can
be
very
much
Case
by
case,
but
as
osbo
we're
trying
to
make
more
consistent
infrastructure
and
tooling
available
for
these
external
first
models,
as
well
as
a
bridge
between
the
internal
external
systems,
to
allow
that,
because
sometimes
even
when
you
externalize
something
you're
still
using
those
internal
tools.
So
how
are
you
copying
between
it?
E
How
are
you
maintaining
a
single
poison
point
of
truth,
especially
for
something
like
issue
tracking,
which
gets
really
complex
and
you're
getting
issues
coming
in
from
the
actual
community,
and
you
have
to
replicate
those
internally
and
prioritize
triage
them
and
then
still
communicate
back
externally?
What
happened?
E
C
Thank
you
so,
like
add,
on
top
of
that,
really
quick
too
the
concept
of
building
open
source.
First
many
companies-
you
have
a
particular
set
of
licenses
you
you
need
to
think
in
that
sense.
If
you
think
this
inner
source
project
is
going
to
be
viable,
your
novel
code
could
be
patentable,
but
if
you're
building
with
multiple
different
libraries
think
about
the
licenses
and
think
about
that,
so.
G
B
H
C
B
So
I
would
definitely
do
interact
with
devrel
and
some
of
the
folks,
like
sometimes
each
little
project,
maybe
have
its
own
like
Community
engineering,
it's
all
like
sort
of
devrel
and
even
supporting
Advocates
that
look
over
it,
and
so
we
are
just
like
interacting
with
them
to
make
sure
if
there's
anything,
they
need
any
tooling
Etc.
That's
something
that
we
would
be
helping
build
because
we're
setting
a
level
up
and
doing
it
at
scale.
D
So
if
we
are
a
consumer
facing
company,
so
I
would
ever
assume
is
mostly
concerned
with
the
apis
and
Zone
we
make
available
to
develops
in
that
sense,
but
specifically
of
Spotify.
We
have
something
as
exotic
as
a
platform
marketing
team,
which
is
basically
ins
put
in
there
to
kind
of
Market
our
platform
things
we
do,
and
that
also
include
open
source.
So
that's
that's
inspiring
part
of
me.