►
From YouTube: Empowering the End Users Priyanka Sharma(CNCF)Todd Moore(IBM) OpenShift Commons Gathering KubeCon NA
Description
Empowering the End Users
Diane Mueller(Red Hat), Priyanka Sharma (CNCF), Todd Moore (IBM)
OpenShift Commons Gathering KubeCon NA
November 17, 2020
Today, end users are not just “using” open source software. They are active and valuable participants, helping to drive innovation into upstream projects and launching new projects into the open from behind the firewall. Empowering more companies to navigate the cloud native ecosystem and participate in open source is essential to all our success. Join Priyanka Sharma (CNCF), Todd Moore (IBM) and Diane Mueller (Red Hat) in a conversation on best practices for supporting end users
466765 Empowering End Users
A
Well,
hello,
everybody
and
welcome,
I
hope,
you're
enjoying
today
the
openshift
commons
gathering
here
we're
really
thrilled
that
you've
decided
to
join
us
for
the
day
and
participate
in
this
event,
and
I'm
really
pleased
today
to
bring
this
next
panel
together.
More
of
a
conversation
than
a
panel,
hopefully
we'll
have
today,
we've
invited
priyanka,
sharma
and
todd
moore
priyanka
is
the
general
manager
at
cncf.
A
So
I'm
really
pleased
because
priyanka
coming
from
the
foundation
point
of
view,
todd
having
a
really
extensive
background
in
open
source
program
office
and
open
source
advocacy,
bring
a
whole
ton
of
experience
to
this
conversation
and
insight.
So
I'm
really
thrilled
and
pleased
to
have
them
there.
And
if
you
don't
know
me,
I'm
diane
mueller,
I
am
the
director
of
community
development
and
the
organizer
and
founder
and
person
behind
the
scenes
at
openshift
commons
and
working
through
the
okd
working
group
as
well
to
do
that
open
source
project.
A
B
Yes,
absolutely
thank
you
so
much
for
having
me
diane,
hi,
everybody,
I'm
priyanka
sharma,
and
I
am
the
general
manager
for
the
cloud
native
computing
foundation
which
hosts
critical
infrastructure
technology
projects
such
as
kubernetes,
prometheus,
envoy,
etc.
Today
we
are
70
plus
projects
and
the
end
users
in
our
ecosystem
are
a
key
to
our
growth.
We
actually
enjoy
the
largest
end
user
community
of
any
software
foundation
and
we're
very
proud
of
that.
So
that's
a
little
bit
about
me.
If
you
want
to
learn
more
about
cncf,
I
want
to
reach
out
anytime.
B
C
Yeah,
thank
you,
diane
and
thank
you
for
having
me
as
well.
I've
worked
in
open
source
for
ibm
on
and
off
over
the
last
20.
Some
odd
years
spent
quite
a
bit
of
time,
setting
up
organizations
such
as
the
cncf.
I
was
chair
of
the
board
there
at
one
point
and
have
you
know,
watched
organizations
grow,
especially
those
organizations
who
have
embraced
end
users
and
bringing
them
in
each
of
the
organizations
that
I've
participated
in
I've
always
been
a
strong
advocate
for
end
users.
A
So
I'm
going
to
cue
up
a
slide
here
and
I'm
going
to
also
give
a
great
shout
out
priyanka
one
of
the
impetuses
for
this
conversation
was
the
talk,
the
keynote
that
you
gave
back
at
kubecon
eu
and
you
talked
about
something
called
the
virtuous
end-user
cycle,
and
I
don't
know
whether
you
coined
that
phrase
or
whatever,
but
you
certainly
put
a
spotlight
on
it.
So
I
was
gonna
share.
B
As
all
that
happened
in
the
first
few
years,
we
were
very
focused
on
education,
because
the
delta
between
the
folks
who
came
up
with
the
modern
technology
stack
and
the
larger
like
fortune
5000
out
there
was
quite
big.
The
fortune.
5000
was
much
more
focused
and,
of
course,
there's
amazing
examples
out
there
that
were
much
ahead
of
their
time,
but
I'm
speaking
generally
folks
were
they
want
they
needed
to
learn
the
basics.
You
know
cloud
native
101
and
over
time.
B
B
So
number
one
in
this
virtuous
cycle
of
empowering
the
end
user
is
that
when
you
give
end
users
a
formal
seat
at
the
table,
when
you
really
may
empower
them
to
be
part
of
the
conversation
they're
guiding
the
projects,
they're
t
sharing.
What
should
what
they
would
like
to
see
in
the
road
map
or
giving
feedback
on
what
they
tried
and
didn't
work?
That's
one
level
then
the
second
is
sometimes
they
may
identify
a
gap
large
or
complex
enough
that
they
may
create
a
project
and
contribute
it
to
open
source.
There's
plenty
examples
like
that.
B
I
mean
envoy
from
lyft
and
jager
from
uber
are
graduated
projects
in
the
cncf
that
came
from
these
end
user
companies
and
then
are
now
values
by
a
lot
of
people
are
like
established
as
very
looked
up
to
open
source
projects.
So
that's
the
second
piece
right
and
then,
when
these
projects
exist,
there
are
folks
who
may
build
enhancements
on
top
of
that
and
have
value-add
services
on
top,
and
so
when
you
involve
the
end
user.
B
A
A
If
I
go
back
eight
or
nine
years,
often
on
an
enterprise
or
an
enterprise
organization,
end
user
would
get
the
vendor
red
hat,
maybe
ibm
to
put
in
the
bug,
fix
for
them
or
put
the
bugzilla
note
in
and
obviously
it
was
actually
them
using
the
open
source.
So
there's
this
whole
arc
that
has
happened
over
the
past.
A
Giver
to
actually
working
with
us
side
by
side
in
most
of
these
projects,
so,
as
you
pointed
out,
jager
and
lager
from
uber
or
lyft,
donation
and
boy
or
this
morning
I
did
a
or
a
while
when
we
were
recording
this.
Probably
when
I
I
did
a
talk
with
erickson
who's,
doing
a
lot
of
work
around
middle
cube,
and
so
you
see
this
huge
amount
of
effort
from
enterprises
going
into
these
projects
now
and
we're
side
by
side.
A
So
it
kind
of
changes
the
nature
a
little
bit
of
how
vendor
relations
are
with
end
users,
and
I
think
it's
a
good
thing.
I
think
it's,
but
it's
also
it's
we're
watching
the
dynamics,
change
a
lot
and
I
think
some
of
the
things
that
you've
done
with
the
cncf
from
the
toc
adding
end
users
onto
the
toc
and
representation
into
the
board,
have
really
helped
things
immensely,
empowering
them
to
have
the
voice
and
give
away
that
podium.
C
Very,
very
good-
and
you
know
the
it's
it's
it's
something
that
we
started
a
very
very
long
time
ago
in
ibm.
So
we've
got
you
know
a
20
plus
year
history
of
having
an
open
source
project
office
because,
as
we
got
going
in
linux,
we
found
that
you
know
we
wanted
to
be
able
to
manage
our
contributions.
But
then,
as
we
got
more
and
more
into
other
open
source
projects,
it
became.
C
C
You
know
at
some
point
or
another
adopted
the
same
sort
of
thing
and
structure
within
their
companies,
but
but
the
change
now
that's
come
about
is
that
general
businesses,
people
who
are
our
partners
in
things,
people
who
are
our
clients-
have
have
latched
on
to
open
source
and
have
become
great
consumers
of
it.
But
then
they
really
found
that
if
they
started
contributing
and
could.
C
They
could
gain
velocity
versus
their
competition
and,
as
a
result
of
that,
they
were
being
much
more
disruptive
in
their
industries.
They
were
gaining
market
share,
they
they
were
able
to
be
on
that
leading
edge
and
it
have
some
sense
of
control
and
and
therefore
they
also
needed
to
monitor
what
they
were
doing,
what
they
were
contributing
licenses,
etc.
Right.
C
So
so
developers
got
very
engaged
and
the
project
offices
you
know
started
to
to
spring
up
and
what
we
found
is
that
every
large
fortune,
500
at
some
point
or
another
now
is-
is
on
this
path
at
some
place,
they've
either
been
consumers
or
they're
out
contributing
in
some
small
ways,
maybe
or
maybe
just
coming
up
with.
You
know
a
comment
or
an
issue,
and
then
some
of
them
are
full-fledged
in
there
going
in
and
contributing
code.
C
C
A
It's
not
just
writing
it.
It's
like,
if
you're
watching
this
video
and
you're
in
this
openshift
commons
event.
You
are
a
part
of
this
community
you're
hearing
this.
You
know
this
talk,
you're,
getting
this
feedback,
we're
going
to
ask
you
for
feedback
on
it
and
someday
we're
going
to
make
you
talk
on
one
of
these
podiums
as
well.
A
So
I
think
what
one
of
the
things
around
empowering
end
users
that
that
I'd
like
to
tease
out
too,
is
how
we're
changing
the
definition
of
who's
in
the
community
as
well
and
and
coach,
and
how
to
coach
people.
And
I
think
this
is
what
I've
used.
Ospo
and
open
source
initiatives
like
everybody,
from
intersource
commons
to
chaos
and
other
groups
how
to
coach
enterprises
to
enable
and
who
allow
their
end
user
to
participate,
because,
historically,
that
hasn't
been
an
easy
thing
for
people,
and
it's
still
for
a
number
of
folks.
C
Brought
in
some
of
the
ibm
folks
who
wrote
some
of
the
licenses,
like
the
apache
version,
2
license
to
go
talk
to
lawyers
within
organizations
so
that
they
could
understand
the
implications
of
what
was
going
on
there,
because
that
tends
to
be
the
first
stumbling
block.
There's
other
stumbling
blocks
like
security
and
other
things
that
people
start
to
get
concerned
about.
But
I've
always
found
that
the
legal
team
seems
to
be
the
first
ones
that
you've
got
to
kind
of
get
around
and
convince
as
you
go
through
this.
B
Well,
so
I
would
say
there
are
two
aspects
right
that
are
very
important
when
you're
trying
to
encourage
contribution
and
as
as
tata,
there's
there's
always
going
to
be
stumbling
blocks.
When
it
comes
to
you
know,
people
whose
job
it
is
to
make
sure
everything's.
Okay,
with
like
lawyers,
compliance
teams,
risk
teams
etc.
B
The
two
things
I
think
is
one
as,
as
you
said,
dan
every
contribution
matters.
I
think
that
has
always
been
true,
but
it's
only
now
being
recognized.
So
when
we
talked
about
documentation,
documentation
is
critical.
We
and
cncf
help
all
our
projects
as
much
as
we
can
with
docs
writers,
with
connecting
them
with
other
enhancers
who
can
help
them?
It's
a
it's
like
an
active
part
of
the
job,
but
that's
actually
like,
if
you
think
about
it,
the
folks
who
are
setting
up
this
event,
the
events
organizer
they're,
doing
a
pretty
massive
service.
B
When
you
think
about
the
people
listening,
they
are
spending
the
time
trying
to
understand
so
they're
everyone's
becoming
part
of
the
larger
community
and
the
more
they
see
themselves.
As
somebody
who
can
step
in
and
be
like
hey,
I
have
a
suggestion
for
how
to
do
this
event,
or
I
have
a
suggestion
for
how
that
you
know.
Maybe
we
revert
this
documentation
or
here's
a
typo
or
here's
an
issue,
etc.
B
B
They
have
end
user
representatives
and
that's
required,
like
you,
need
to
have
x
number
of
end
users
same
for
the
governing
board
same
for
various
other
avenues,
and
what
that
does
it
creates
that
awesome,
energy
of
top
level
engagement,
as
well
as
the
groundswell
that
we
just
talked
about
that
comes
from
every
contribution
matters,
so
with
the
combination
of
that
it
becomes
that
much
easier
to
convince
legal
teams
and
anyone
in
compliance
and
risk
that
look.
This
is
a
industry-wide
thing.
That's
happening.
This
is
not
just
like.
B
Priyanka
is
really
excited
about
doing
something
that
she
does
for
fun
and
getting
paid
for
it
right
it
just
like
changes.
The
dynamic-
and
I
think,
thinking
about
that,
like
structure
the
open
source,
end
user
in
and
value
everything
they
bring
in
is
what
really
make
moves
the
needle
forward.
I
think.
A
So
there's
steps
in
the
progress
so
making
that
really
clear
has
been
a
huge
help,
and
so
that's
one
of
the
the
best
practices
I
could
shout
out
to
every
project
you
know
and
and
some
of
the
ones
that
I
work
on,
aren't
the
best
at
documenting
that.
But
I
think
that's
something
that
clearly
the
contributors.
C
C
You
have
to
have
that
that
equal
playing
field
that
ability
that
well-defined
path
in
order
for
people
to
really
want
to
be
out
there
and
contributing,
but
you
know
a
lot
of
the
stumbling
blocks
initially
that
I
see
with
people
first
trying
to
get
out
there
is
it's
kind
of
daunting
right,
you're,
putting
yourself
on
the
line.
There's
this
you
know.
First,
you
know
first
pull
request
that
you
know
gee.
Am
I
doing
it
right
and
you
know
so.
C
People
get
nervous
and
oftentimes.
What
we
do
is
especially
internally
here,
even
within
the
company
for
for
folks
who
haven't
been
engaged
in
open
sources.
We
run
a
process
where
we
call
it
a
dojo
and
and
we
help
them
and
and
we
get
them
to
get
their
first
pull
request
in
and
then
we
mentor
them
for
a
period
of
time
to
help
them.
A
C
A
C
C
So
just
get
involved,
you
know
and
work
with
your
company
and
if
you
have
issue
getting
going
in
open
source
because
you
have
roadblocks
in
the
company
there's
so
many
of
us
that
have
gone
down
that
path,
just
ask
for
help.
We'll
help
you
you
know
with
the
arguments.
You
need
to
convince
people
to
get
engaged.
B
Yeah
I
hundred
percent
agree
and
particularly
what
you
said.
Sorry,
particularly
what
you
said
todd
about.
You
know
like
it's
work
with
people.
If
there
is
someone
who
is
trying
to
get
something
done
like
support
them
and
that
will
like
your
journey
becomes
further
so
open
source.
Just
like
any
other
place,
it's
all
about
the
people.
The
difference
is
yes,
you
can
reach
out
to
them
online
and
they
will
reply
to
you.
They
don't
need
to
meet
you
two
three
times
to
do
like
work
with
you.
B
It's
very
open
anyone
open
open
source.
Anyone
can
like
knock
on
any
door
and
get
entry,
and
I
think
that's
the
beauty
of
it,
and
I
hope
people
see
that
over
time
that
more
and
more
people
see
that
that
this
is
actually
the
one
place
where
you
want
to
make
an
effort.
There
are
lots
of
people
who
could
take
that
effort
and
guide
your
journey
along
the
way,
it's
all
about
people,
but
you
can
build
a
relationship
with
anyone
that
you
want
to
so.
A
A
What
we
see
is
especially
like
in
the
cncf
is
all
these
interdependent
projects
that
have
multiple
complexities,
and
so
I
think
one
of
the
really
daunting
things
for
newbies
coming
into
the
cncf,
and
even
people
who
are
trying
to
you
know
find
out
when
the
next
release
is,
for
you
know
prometheus
and
how
grafana
interfaces
with
that
and
then
oh
I'm,
using
something
and
I'm
using
something
in
telemetry.
But
the
alignment
of
all
of
those
rubik's,
cube
and
three-dimensional
chess
games
is
really
very
daunting
for
folks
and
so
well.
C
I
think
the
the
obviously
I
always
advocate
start
simple
again
things
like
documentation,
finding
the
the
niche
where
there's
a
place
where
you
feel
comfortable
contributing,
but
then
there's
a
need
in
it
as
well
too.
So
many
of
the
projects
are
really
dying
to
have
people
come
and
join
them,
and
and
good
competent
developers
will
be
embraced
and
handed
the
keys
to
the
kingdom
that
to
help
them
in
their
journey
promoting
their
code
and
moving
it
forward.
C
So
you
know
I
always
always
find
an
area
that
I'm
I'm
interested
in
most
and
go
dig
into
that,
because
I'll
be
happy
doing
it
and-
and
you
know,
look
for
a
community-
that's
vibrant
right,
one
that
really
has
good,
solid
level
contributors.
Has
that
clear
path
to
how
you
become
a
maintainer
is
is
running
an
open
governance
so
that
you,
you
know,
there's
no
single
vendor
in
control
of
it
and
you
know,
works
completely
out
in
the
open.
It's
the
transparency
that
makes
this
work.
C
C
You
know
one
of
the
things
you
see
in
projects
is
they
gain
so
much
velocity,
sometimes
that
the
original
folks,
who
were
the
contributors
of
the
base
code,
don't
even
recognize
what's
there
as
they
go
away
for
three
or
four
months,
because
it's
all
just
changed
right
and,
and
so
it's
staying
up
with
that,
it's
tough,
so
it
there
are.
There
are
tons
of
dependencies
and
you've
got
to
trust
and
work
with
those
dependencies
and
if
you've
got
a
problem,
get
a
hold
of
the
folks
who
are
working
in
that
you
know.
C
B
Yeah,
so
when
I
would
say,
go
for
it,
you'll
go
for
it.
Oh
may
I
so,
first
of
all,
100
agree
with
todd
and,
second
of
all,
something
I've
seen
work
quite
effectively
for
people
is,
if
you're
an
engineer,
or
you
know,
a
engineer
or
technical
person
of
any
sort,
right,
docs
writer,
product
manager,
etc.
B
Anyway,
you
are
probably
consuming
or
utilizing
an
open
source
library
project,
many
of
those
you're
probably
consuming
and
utilizing
like
a
lot
of
them,
and
so
you
are
very
close
to
some
of
their
in
your
daily
work
and
they
can
be
a
really
great
place
to
start
because
there
you're
the
end
user.
So
you
know
how
that
particular
project
is
performing
for
you.
You
know
what
the
issues
are.
B
You
know
what
you
would
like
to
see
change,
so
you
start
with
a
knowledge
advantage,
and
so
that
can
be
those
projects
can
be
a
really
good
place
to
just
start.
Getting
your
feet
wet
in
terms
of
you
know
like
checking
out
docs
commenting,
maybe
eventually
having
a
pull
request
and
at
that
point
you've
become
pretty
conversant
in.
How
does
this
whole
open
source
thing
work
and
at
in
that
moment,
then
you
can
kind
of
decide.
Hey.
B
Do
I
like
this
here
or
am
I
interested
in
this
other
adjacent
technology
or
I'm
looking
for
a
project
that
does
contributions
differently
and
has
a
different
vibe?
You
know
because
it's
a
community
at
the
end
of
the
day,
so
that
can
also
be
a
good
way
to
kind
of
get
started,
is
like
pick
something
that
you're
really
familiar
with
and
you
use
in
your
daily
work
and
that
can
take
you
quite
far.
A
So
I'm
go
we're
almost
to
the
end
of
our
time,
but
I'm
gonna
ask
one
more
question:
I'm
gonna
ask
you:
are
we
at
a
tipping
point
where
we're
going
to
see
more
of
these
projects
driven
by
the
end
users
than
they
are
vendor
driven?
So
how
about
closing
on
that
note?
Have
we
hit
that
tipping
point,
or
are
we
still
in
the
stage
of
having
to
enter?
You
know
en
engage
and
nurture
new
end
users
to
come
on
board.
C
I'll
go
first,
I
think
momentum
is
building.
I
believe
that
we're
seeing
the
start
of
of
the
real
ramp,
I
think
it's
going
to
be
an
exponential
ram.
I
think
the
tipping
point
is
still
a
few
years
away,
so
you
know,
I
think,
we're
we're
there
in
terms
of
buy-in
that
open
source
can
be
much
better
quality
code,
much
better
security
in
a
lot
of
ways,
and
now
they
can
find
people
who
will
engage
and
do
a
good
job
within
their
their
companies,
and
I
think
that
you'll
see
the
end.
C
B
You're
right
nothing
wrong
with
that,
and
I
would
say
that
yeah
we're
not
at
the
tipping
point
by
any
means.
This
is
just
the
beginning.
This,
like,
while
we
enjoy
the
largest
end
user
community
for
any
open
source
foundation,
it's
only
140
plus
people
there's
a
fortune
5000
over
there
and
that's
just
the
top
5
000
companies
right.
So
there's
a
lot
of
ground
to
cover
that's
number.
One
second
is
I
do
think
that
it
won't
ever
be
that
oh,
the
end
users
took
over
and
like
the
vendors
are,
like.
B
I
don't
know
off
doing
something
else
somewhere.
I
I
think
that
the
definitions
of
what's
an
end
user,
what's
up
enhancer
or
vendor.
What's
a
part
project
contributor,
open
source
project,
everything's
going
to
get
more
blurry,
which
is
also
a
good
thing,
because
if
you're
an
end
user-
and
you
start
using
a
project-
that's
open
source
and
then
you
start
commenting
on
it
and
you
slowly
start
doing
more
contributions,
then
you're
in
the
contributor
bucket.
B
C
A
I
I
think
it's
I
think
you
both
hit
the
nail
on
the
head.
I
told
I
we're
going
to
keep
saying
we
100
agree
with
each
other.
I
think
there's,
I
think,
closer
to
the
tipping
point
and
I
think
for
from
my
perspective,
from
the
openshift
commons,
what
we're
really
trying
to
do
is
empower
the
end
users
to
be
part
of
this
greater
peer-to-peer
network
so
that
they're
sharing
best
practices
and
lessons
learned
and
they're
hearing
it
from
each
other,
as
opposed
to
from
you
know,
vendors
and
foundation.
A
Folks
and
the
more
we
can
do
to
nurturing
and
engage
those
relationships
across
industries
and
between
end
users
with
different
and
shared
workloads.
The
more
we're
going
to
get
you
know
much
better
innovation
driven
back
into
these
projects,
and
I'm
really
looking.
I
don't
think
we'll
ever
hit
a
tipping
point
where,
as
you
put
it,
it's
all
end
user,
driven
or
all
you
know
or
some
other
variation.
I
think
people's
it's
gonna
get
blurry.
A
We're
going
to
have
an
amazing
future
for
open
source.
So
with
that,
I
want
to
thank
both
of
you
for
everything
that
you
do
to
make
the
cncf
an
awesome
space
to
work
in
as
well
as
people
to
to
collaborate
with.
So
thank
you
very
much
today
for
your
participation
here
and
going
to
let
you
go
back
to
your
day,
jobs
and
we'll
hear
you
in
chat,
hopefully
sometime
during
kubecon.
So
thanks
again
guys.