►
From YouTube: CNCF TOC Meeting 2020-06-16
Description
CNCF TOC Meeting 2020-06-16
C
E
E
Some
of
you
know
me,
some
of
you
don't
I
am
Priyanka
and
I
have
been
part
of
the
CFCF
ecosystem
for
a
while
in
in
the
early
days
of
the
cloud
Native
community
I
joined,
I
joined
with
the
open
tracing
project,
which
some
of
you
may
remember,
which
is
now
merged,
with
open
census
to
be
open,
telemetry,
and
there
was
those
were
the
early
days
because,
like
we
were
the
third
project,
there
was
a
lot
of
excitement.
I,
remember,
meeting
Chris
at
a
co-working
space
in
San,
Francisco
and
being
so
impressed
by
this
cool
idea.
E
I
stayed
involved
as
a
contributor
as
someone
who's
educating
the
ecosystem
about
what
is
tracing.
What
is
the
word,
observability
think
very
basics
at
that
time
and
have
seen
it
grow
in
that
first
wave
too,
where
we
were
explaining
what
our
distributed
systems
effectively
to
now
to
the
second
stage,
which
was
when
I
joined
gitlab
as
director
of
cloud
native
alliances.
E
At
that
time,
I
was
elected
to
the
Governing
Board
of
the
CN
CF
and
got
to
see
how
the
magic
is
made
by
the
execs,
Dan
and
Chris,
and
then
eventually
I
had
this
opportunity
to
join
the
Foundation
as
its
new
GM.
You
may
wonder
what
is
a
GM
when
Dan
was
IDI,
it
is
same
difference.
It's
the
same
thing.
E
Anyone
who's
interested,
please
swing
ping
me
on
slack
or
email,
whatever
you
want
to
do
to
a
book
a
time
where
we
can
discuss
what
your
experience
in
cloud
native
is.
How
can
I
help
in
any
way?
So
that's
what
I'm
doing
mainly
right
now.
Interestingly,
while
doing
that,
there's
always
a
lot
of
work
to
be
done
to
which,
like
you
know,
you
can't
wait
for
the
listening
tour
to
be
over
to
start
doing.
So,
that's
also
occupying
my
days
quite
significantly.
E
Overall,
my
objective
with
the
foundation
is
to
to
keep
building
upon
the
awesome
experience
that
I've
had
here
and
that
I
know
a
lot
of
other
folks
have
had,
and
we
want
to
do
that
by
growing
and
nurturing
the
end
user
community
who
all
of
you
want
to
engage
with
and
work
with
for
your
projects
for
your
technologies.
If
you
want
to
support
the
ecosystem
in
general
during
this
very
unique
time
and
finally,
I
think
there
is
an
opportunity
for
us
to
go
second
wave
with
a
deeper
developer
engagement.
E
You
folks
are
the
people
who
approve
and
manage
the
projects
that
enter
since.
Yes,
liz
has
done
an
amazing
job
being
the
chair,
in
my
opinion
and
I,
think
everyone
works
so
hard
here
with
all
the
awesome
technology
coming
in.
We
needs
to
be
able
to
support
the
wider
ecosystem
with
how
can
they
leverage
this
I
know
that
fairly
well,
because
I
remember
the
open
tracing
days,
I
was
just
focused
on
one
project
right
and
it
takes
a
significant
amount
of
work,
in
my
opinion,
to
educate
I'll.
E
You
know
the
larger
developer
or
DevOps
community
on
the
benefits,
the
reasons
why
people
should
think
about
their
tech
and
text,
a
canvas
in
a
certain
way,
so
I
think
there's
a
lot.
We
can
do
there
and
I'm
very
excited
to
partner
with
you
all
and
continue
this
journey.
Thank
you.
I
would
be
happy
to
take
questions
if
Liz
allows.
B
B
D
D
D
C
D
Indeed,
if
that
process
works
well,
it's
a
trial,
we'll
see
I
think
there
have
been
some
questions
from
some
sick
chairs
about
whether
or
not
we
still
wanted
any
kind
of
ongoing
reviews
and
presentations
to
happen,
and
so
at
this
point,
assuming
that
the
new
process
is
successful,
they
won't
be
required.
But
we
do
encourage
this
kind
of
interaction
between
SIG's
and
projects.
Anyway,
it
could
be
really
worthwhile
for
projects
to
familiarize
the
six
with
what
they're
doing
and
to
build
relationships.
D
B
D
Great
and
Katie
have
posted
the
link
to
the
spreadsheet,
for
anybody
who
doesn't
woody
I
have
the
slides,
okay,
wonderful,
I!
Think
we've
got
a
couple
of
slides
to
remind
toc
folks
that
we
have
worked
to
do
so.
Some
of
these
votes
that
they're
for
votes,
outstanding,
I,
think
some
of
them
are
pretty
close
to
being
passed.
D
D
We
have
some
annual
reviews
for
sandbox
projects,
so
these
still
need
three
sponsors
to
basically
say
yeah
I
support
the
ongoing
sandbox
nature
of
this
project
and
so
against.
If
you're,
a
toc
person
on
this
call,
do
you
go
in
doesn't
require
all
of
us
to
look
at
all
of
them
that
you
know
if
everybody
goes
and
looks
at
one
or
two
of
them,
we
should
have
them.
You
know
we
will.
F
D
So
if
anyone,
if
a
TOC
memory
is
particularly
keen
to
lead
the
DD
for
any
of
these
projects,
either
shouting
now
or
adding
yourself
onto
the
PR
or
mailing
or
whatever
slack,
it
would
be
great
to
start
identifying
who's
gonna
do
what
because
I
can
see
this
is
going
to
be
yeah.
There's
a
chunk
of
work
coming
up
folks,
so
let's
try
and
line
up
who
can
do
what.
G
We
already
have
a
sick
presentation
and
the
recording
there
and
the
and
the
due
diligence
is
doc
that
they've
prepared.
This
is
really
pretty
comprehensive
as
a
result,
so
happy
to
work
with
whoever
on
the
talk,
is
going
to
sort
of
complete
that
due
diligence,
but
that
that
one
in
particular
is
fairly
advanced,
they're,
fantastic.
D
Know
I
think
I
was
looking
at
this
this
morning.
The
process
that
we
currently
have
to
say.
You
know
we
should
get
the
relevant
seek
to
do
their
review
and
then
the
TOC
member
dreyes,
due
diligence
and
I,
have
noticed
that
some
of
the
projects
are
quite
quite
rightly
they're-
sort
of
writing
their
own
due
diligence
document
to
help
kick
start
that
process
I.
Think
that's
a
completely
valid
thing
to
do.
D
I
am
slightly
concerned
that
we're
going
to
end
up
with
projects
that
have
been
through
like
three
sick
reviews,
because
they're
spread
across
different
SIG's
and
you
know,
there's
a
lot
of
work
on
into
it
and
then
maybe
the
TOC.
If
we
haven't
identified
who
the
TEC
person
is
they
they
might
have
other
questions,
it
might
feel
like
we're
going
back
to
the
beginning
again
so
I'm
kind
of
hoping
we
can
start
trying
to
get
these
due
diligence.
D
Things
happening
a
bit
more
in
parallel,
but
also
thinking
that
the
TOC
folks
can
work
with
the
SIG's
and
ask
for
help
and
say
please.
Could
you
dig
into
this
particular
area?
I
have
questions
you
know
either
directly
with
the
project
but
or
maybe
help
asking
the
sig
for
their
opinion
as
well.
I
can
see
some
folks
volunteering
for
a
few
projects.
So
that's
wonderful,
Thank,
You,
Michele,
Thank,
You,
Justin,
Thank,
You,
Katie.
D
H
A
D
All
right,
so
lots
of
work
ahead
of
us
I
am
I,
guess
I'm
also
going
to
say
you
know
for
the
projects.
If
anyone
is
representing
those
projects
on
the
core,
we'll
do
our
best,
you
can
see
the
workload
we
have
here
so
yeah
all
right.
Any
other
questions
about
the
kind
of
project
side
of
things
before
we
move
on
to
the
technology
radar.
I
Awesome,
thank
you
so
for
those
who
haven't
met
me
before
I'm
Cheryl
I'm,
the
director
of
ecosystem
at
CNCs
and
I,
focused
primarily
on
end-users
and
I'm,
very
excited
to
announce
this
new
initiative,
which
comes
from
the
CNCs
end
user
community,
and
this
really
came
about
because
of
some
discussions
that
I
had
with
in
the
end
user
community
and
with
Liz,
with
Elena
and
Katie
and
Jeff,
the
TOC
and
user
reps,
and
the
thinking
was.
How
do
we
make
sure
that
we
have
the
actual
reality?
I
What
is
the
real-world
usage
of
cloud
native,
and
how
can
we
use
that
to
drive
the
CNC
F
technical
strategy
so
that,
for
instance,
if
projects
are
in
sandbox
for
a
year,
then
we
have
a.
We
have
a
process
where
you
could
say
like
these
are
things
that
we're
actively
looking
for
actively
interested
in.
I
So
next
slide,
please
and
who
is
in
the
end
user
community.
So
this
is
a
group
of
about
145
companies.
You
see
they
range
some
tiny
startups
building
greenfield
applications,
some
huge
household
names,
some
have
lots
of
legacy
and
enterprise
and
some
have
to
deal
with
regulatory
compliance.
So
there's
a
really
wide
range
of
really
wide
diversity
of
companies
within
this
end-user
community
and
most
of
what
the
end
user
community
does
is,
is
closed.
I
It's
not
publicly
recorded
or
shared,
and
the
reason
for
that
is
that
these
companies
often
don't
have
the
legal
or
PR
approval
to
say
what
they're
doing
publicly.
So
they
can
talk
about
it
within
a
closed
group,
but
they
can't
talk
about
it
publicly.
So,
over
the
last
couple
of
years,
I've
heard
a
lot
of
really
really
intense
amazing
discussions
within
these
companies
and
I
wanted
to
share
some
of
those
discussions
in
an
aggregated,
an
anonymized
way
out
to
the
general
public
and
the
end
users
and
vendors
who
are
looking
at
cloud
native
next
slide.
I
Please,
oh,
do
feel
free
to
put
some
questions
in
the
chat
as
you
go
along.
If
there's
anything
that
you
want
to
ask,
so
technology
radar
is
an
opinionated
guide
to
a
set
of
emerging
technologies
and
I.
Think
I
should
have
added
here
as
well
at
a
specific
point
in
time,
so
this
format
originated
from
a
consultancy
called
thought
works,
and
this
is
what
their
latest
radar
looks
like.
I
We
think
that
this
is
promising
and
then
the
outermost
one
is
hold
hold,
meaning
we
just.
We
think
that
there
are
better
ways
to
do
this,
so
we
no
longer
recommend
these
features
these
projects,
and
you
can
see
that
the
thought
works
radars
divided
into
quadrants.
So
it's
not
just
technologies,
it
includes
techniques,
platforms,
tools
and
languages.
I
I
So
this
is
a
clearer
definition
of
what
these
four
levels
means
so
again
adopts
trial,
assess
and
hold
so
from
most
most
mature
and
widely
used
to
least
okay,
let's
go
to
the
next
one.
So
I
wanted
to
take
this
format
and
tweak
it
a
little
bit
to
make
this
useful
for
the
broader
community
and
I'm
glad
to
see
that
josh
has
also
never
heard
of
it.
It's
new
to
me,
so
the
most
important
one
is
the
first
one
that
this
is
community
driven.
So
it's
not
the
opinion
of
a
single
company.
I
We
wanted
to
simplify
it
a
little
bit,
so
we
want
to
focus
on
the
future
adoption,
so
we
just
keep
assess
trial
and
adopt
and
then
on
the
on
the
last
slide,
the
thought
works.
Radar
is
a
hundred
items
published
once
a
year,
but
at
least
within
the
cloud
native
I
think
we
can
all
agree
once
a
year
is
kind
of
slow
for
our
community.
So,
instead
we're
going
to
do
10
to
20
items
once
per
quarter
on
a
specific
use
case.
I
So
following
good
for
these
practices,
so
small
and
often
or
frequent
and
often-
and
so
the
first
use
case
that
I
focused
on
was
continuous
delivery.
So
the
next
few
slides
I'm
going
to
talk
about
how
actually
the
methodology
behind
building
it
and
creating
a
tech
radar,
I,
wouldn't
I,
wouldn't
be
showing
this
in
the
future
future
ones,
but
I
think
it's
important
to
understand
how
it
was
created.
So
I
created
this
Google
spreadsheet,
it's
open!
Well,
it's
not
open.
I
I
Next
step,
step:
nice,
yes,
so
this
was
the
result
of
that
spreadsheet.
So
you
can
see
this
is
actually
a
super-wide
spreadsheet,
so
this
goes
across
the
top
and
then
keeps
wrapping
down
to
the
to
the
one
on
the
bottom
and
I
blacked
out
the
names
of
the
country,
but
33
companies
submitted
177
data
points
and
you
can
see
it's
color-coded,
so
green
for
adopts
blue
for
trial,
yellow
for
assess
and
red
for
hold.
I
So
the
next
stage
in
this
was
looking
at
looking
horizontally,
looking
across
the
rows
at
the
individual
projects
and
then
putting
those
into
the
rough
categories
of
adopts
trial
and
assess,
and
this
is
where
I
want
to
make
it
very
clear
that
it's
subjective
it's
a
opinionated
guide.
So
you
could
certainly
argue
that
some
of
these
could
be
in
different
levels.
I
Just
depends
on
where
he
wanted
to
put
the
cutoff
point
and
when
I
was
building,
this
I
decided
the
first
one
like
flux
and
helm
seem
to
have
enough
positive
consensus
to
go
in
an
adult
circle.
Ci
get
lab
and
customized
had
mostly
positive
recommendations,
but
perhaps
not
as
many
responses
and
then
assess
was
just
a
really
wide
mix.
You
know
some
of
them.
I
There
wasn't
enough
data
to
say
conclusively
one
way
or
another
Jenkins,
which
is
obviously
the
longest
one
had
lots
of
positives,
but
also
lots
of
negative
ones,
so
assess
is
the
most
varied
out
of
these
three
and
then
the
next
step
after
that
step
three
and
was
to
look
at
some
of
the
patterns
or
themes.
I
see
the
question
from
this:
do
you
think
we
should
public,
publish,
eyes.the,
yeah,
publish
eyes?
Should
we
publish
the
anonymized
step
to
data
as
well
as
the
final
radar
I
think
we
could
probably
do
that?
I
It
depends
entirely
on
whether
it
would
just
be
in
the
editors
opinion
whether
this
we
might
have
to
strip
out
comments.
For
instance,
if
the
comments
you
know
with
the
Oh
the
identity
of
the
company,
of
course,
a
lot
of
the
companies
are
absolutely
fine,
with
sharing
their
data
as
well.
So
I
think
this
is
yeah
I
think
we
could
probably
do
that
cool
and
then
for
the
last
step
of
this
was
analyzing
I'm.
Sorry
go
back
one
analyzing
the
the
themes.
So
again,
this
is
an
editor's
subjective
view
of
what
is
interesting
or
surprising.
I
I
So
I
would
read
this
radar
as
flux
and
helm
showed
the
most
bored
positive
consensus
circle,
see
I,
customized
and
gitlab
are
seen,
as
has
some
positive
responses,
but
maybe
not
as
much
consensus
as
those
in
adopt
and
then
everything
else
in
assess
can
be
there
for
different
reasons.
So
some
things
are
too
new.
Some
things
like
Jenkins.
I
You
know
the
the
difficulty
I
had
with
this
my
first
reaction
when
I
saw
this
was,
but
why
is
Jenkins
in
SS,
because
everybody
knows
Jenkins
and
and
lots
of
people
use
it.
So
the
the
point
about
showing
you
this
specially
was
to
say
would
it
have
been
by,
in
my
opinion,
as
the
editor
to
put
Jenkins
within
the
same
lead
in
a
circle,
see
I
customize
and
get
that
if
you
could
actually
pop
back
to
that
spreadsheet
for
a
moment
Nene.
Thank
you
next
one
one
after
this
sorry
for
words.
I
I
Well
yeah
Jenkins
is
is
pretty
old,
so
this
is
exactly
what
I'm
saying
like
I
wanted
to
not
make
this
judgment
on.
You
know
because
everybody
knows
Jenkins,
so
we
should
move
it
higher.
The
point
is
to
look
at
what
these
actual
companies
recommend
and
try
and
be
at
least
somewhat
fair
about
about
it.
I
I
Sort
of
difficulties
with
this
because
it
could
be
well,
it
almost
certainly
is
a
biased
group
right.
This
is
the
same
thing
that
alex
is
saying
about
getting
the
the
surveys
size
and
sorry,
the
verticals
and
some
ideas
about
the
respondents
and
because
the
projects
were
suggested
by
the
end-user
community,
we've
were
explicitly
not
adding
in
extra
things
that
it's
not
the
opinion
of
CN
CF.
It's
not
the
opinion
of
the
TOC.
I
So
again,
we
definitely
couldn't
release
the
real
names,
possibly
the
industry
sectors
and
I
have
a
I
have
a
link
at
the
end
of
this
couple
of
slides,
where,
if
you
I
know
I'm
going
to
forget
some
of
these
answers,
so
if
you
pop
them
in
there,
that
would
be
pop.
These
suggestions.
There
that
would
be
great,
but
I
think
that
we
can
just
be
careful
about
as
long
as
we're
careful
about
how
much
information
we
release
yeah,
certainly
possible,
certainly
doable.
I
What's
the
criteria
for
including
the
items
in
the
technology
list,
the
criterias
it
came
from
the
end
users,
that's
100%
it,
so
we
didn't
suggest
anything.
We
didn't
take
anything
else,
it's
just
what
the
end
users
themselves
suggested
and
yeah
I
do
think.
This
is
super
useful
to
show
at
least
what
a
group
of
weil
end
users
is
doing
so
awesome
I
also
think
it's
actually
really
interesting
data.
Just
even
the
anonymized
version
is
really
interesting.
I
Will
there
be
a
centralized
portal
to
access
the
radars?
Will
it
be
linked
to
the
CN
CF
landscape
again,
like
I,
think
we
could
build
this
out.
I
need
to
I
need
to
scope
that
out
as
a
project
and
build
it,
but
it
sounds
like
people
find
it
useful
enough.
So
at
some
point
we'll
definitely
live
on
the
CN
CF
website
as
a
resource
that
you
can
explore
and
look
around
for
sure.
I
Would
it
be
linked
to
CN
CF
landscape.
Similar.
It's
great
includes
lots
of
the
vendors
which
kind
of
give
good
assessment
in
terms
of
how
much
end
users
use
vendors
versus
open
source.
So,
yes
agreed
like
that's.
Why
I
said
I
think
it's
very
important
that
this
is
reality
and
we're
not
just
talking
CN
CF
projects.
Only
I
think
this
is
crucial
to
recognize
that
this
is
the
actual
experience
of
the
end
users.
So.
I
Allen
I
think
this
is
so
similar
someone
yeah,
so
I
again
are
not
saying
this
I
present
this
as
a
resource
to
be
taken.
With
the
caveat
said
it
is
opinionated
I
thought
I,
don't
in
my
opinion,
as
a
as
the
editor
of
this
particular
radar,
I
would
not
have
felt
it
was
the
right
thing
to
do
to
move
Jenkins
of
the
basis
of
its
adopted
in
lots
of
places.
So
again
you
could
certainly
argue
one
way
or
another.
It
is
definitely
subjective,
but
the
point
of
this
is
to
spark
discussion
right.
It's
not.
I
It
can
never
clearly
never
be
purely
objective.
It
is
the
opinion
of
33
companies
and,
as
Moschino
says
it
does,
shell
hold.
There
were
quite
a
few
holds
in
that,
and
therefore
that
was
my
my
my
judgment
for
what
I
said
and
I'm
willing
to
stand
by
my
own
judgment,
but
certainly
happy
to
have
you
to
discuss
this.
I
The
official
version
leaves
that
hold
data
most
likely
for
political
reasons.
Can
you
say
some
words
regarding
this
or
what
our
other
opinions
so
there
I
suppose
you
could
call
it
a
little
bit
political,
but
I
also
feel
that
this
is
a
matter
of
choice
and
I.
Wanted
this
to
be
a
bit
more
positive
and
forward
forward-looking.
Rather
than
saying
don't
do
this
I.
I
Felt
that
it
would
be
better
to
just
keep
the
three
that
were
more
like.
Yes,
you
should
try
it
or
suggest
it.
If
there
were
strong
opinions
and
people
really
feel
like
they
want
to
see
what
things
were
in
hold,
then
again
we
can
look
at
it.
This
is
the
very
first
one
that
we've
run.
So
all
of
this
can
change
right.
Everything
here
is
is
flexible.
We
can
absolutely
change
this
format.
I
The
the
main
thing
for
me
is
that
this
is
valuable
to
the
community
and
it's
useful
information
and
useful
data
presented
in
a
kind
of
easy
to
consume
way
and
trying
to
reflect
some
level
of
reality.
But
again,
I'm
I
said
there
is
a
there
is
a
link
and
please
feel
free
to
add
a
comment
there,
so
that
I
can
track
it
after
this
school,
because
I
am
very,
very
keen
to
make
sure
this
is
a
useful
resource.
I
I
So
one
that
surprised
me
was
that
most
of
the
end
users
had
tried
a
lot
of
different
options
and
adopted
more
than
one
so
I
guess
I
expected
most
to
just
end
up
adopting
a
single
solution,
but
many
had
combined
multiple
solutions
and
then
also
open
source,
their
components
of
their
own
continuous
delivery
framework.
So
Luna
way
have
released
manager,
cue,
papaya
from
box,
static,
controller
phones
and
land
owned.
I
It
also
surprised
me
that
I
didn't
see
any
of
the
public
cloud
managed
solutions
which
could
be
a
bias
in
the
group,
or
it
could
be
that
there
is
actually
a
preference
for
one
in
continuous
delivery
on
parental
Enclave
within
your
own
cluster
and
or
it
just
might
be
the
maturity
in
the
features
that
were
available
a
few
years
ago.
When
the
end
users
were
making
their
decisions.
I
Number
two
helm
is
more
than
packaging
applications.
So
I
was
very
surprised
to
see
that
helm.
Somebody
suggested
helm
in
this
chart
because
I
don't
think
of
it
as
a
continuous
delivery
tour.
But
it
turns
out
that
it's
a
widely
used
component
of
lots
of
different
companies
as
part
of
CD
and
then
the
third
one
was
Jenkins
again.
I
I
thought
that
this
would
have
the
most
discussion
around
it,
so
Jenkins
is
definitely
widely
used
and
why
they
evaluated,
but
compared
to
almost
all
the
other
options,
had
the
largest
number
of
companies
who
said
they
put
it
on
hold
for
new
applications.
So
that's
not
to
say
that
Jenkins
is
bad
or
Jenkins
is
not
used.
I
And
then
I
think
we
are
think
this
is
the
last
one
of
my
slides
so
again,
I'm
trying
to
I
really
want
to
make
this
a
useful
resource,
and
so
each
one
of
these
that
we're
going
to
publish
each
quarter
will
focus
on
a
different
use
case.
So
I
picked
out
a
few
categories
from
the
CN
CF
landscape.
Maybe
you
want
to
find
out
what
end
users
are
doing
around
security?
I
You
know,
lots
of
people
are
asking
for
this,
so
I'm
I
think
that
we
can
find
some
way
to
at
least
released
release
the
anonymize
data
without
any
of
the
comments
and
yeah
we'll
see
we'll
see
what
we
can
do.
First
of
all,
another
interesting
point
that
flux
is
in
adopt.
What
other
is
an
assess
can't
draw
a
conclusion
about
not
having
cloud
platforms
present
if
they
in
the
technology
list.
So,
as
I
mentioned
before,
the
projects
that
were
listed
here
were
suggested
by
the
end
users.
I
I
Another
alternative
approach
would
be
to
seed
the
technology
list
of
all
the
solutions
from
an
aerial
of
the
existing
landscape,
but
I
like
that.
The
current
approach
doesn't
put
words
in
the
mouth
of
the
respondents
so
yeah.
This
was
exactly
my
thought.
I
didn't
want
to
give
the
impression
that
there
were,
you,
know
ten
options,
and
that
was
it.
If
you
don't,
if
you
use
anything
other
than
these
ten
options,
then
you
know
you
don't
have
an
opinion
on
CD
I.
I
Don't
think
that
could
be
correct
and
and
also
there
are
lots
of
projects
which
are
not
going
to
be
on
the
CNC
F
landscape
I
mean
amazing
to
think
that
there
can
be
the
CNCs
landscape
is
not
all-encompassing,
but
they're
always
going
to
be
products
that
are
not
available
on
there.
So
I
do
think
it's
important
to
say
this
set
of
Tours
the
the
answers.
The
options
also
come
from
the
end
users.
There's
a
lot
of
Bosch
well,
fair
enough.
I
F
Had
a
quick
question,
Liz
Cheryl
thinks
this
is
really
interesting
and
I.
Think
from
a
storage
thing
perspective,
we
had
been
looking
at
different
use
cases
and
trying
to
avoid
king-making,
and
perhaps
this
is
a
way
for
us
to
evaluate
that.
But
one
thing
that
you
said
and
maybe
I
misheard
was
is
this
data?
Did
you
say
it
was
years
old
or
I
mean?
How
do
we
gauge
the
relevance
today
of
those
I'm
assuming
I.
I
Make
sure
the
what
I
said
was
Jenkins
is
a
few
years
old,
so
this
data
was
collected
in
May
so
last
month
and
the
idea
is
that
it
would
be
newly
refreshed
every
month.
Oh
and
also
the
idea
is
that,
since
this
was
the
first
time,
I
ran
it
as
the
editor
I
collected
the
data
and
I.
These
are
my
opinions
on
it,
but
in
the
future,
we're
going
to
pull
five
companies
from
the
end-user
community
to
be
the
judge
of
what
projects.
I
I
Exactly
yeah
exactly
so
continuous
delivery,
probably
won't
come
up
again
for
a
little
while,
but
and
the
the
actual
topic
of
it
would
be
decided
by
that
editorial
panel.
You
know
what
they
want,
but
I'm
I
want
to
invite
votes
and
opinions
from
the
wider
community
about
what
you
would
find
interesting
and
then
let
the
editorial
panel
decide
what
the
topic
is
and
what
the
final
results
are.
I
But
yeah
I
foresee
this
being,
hopefully
an
interesting
resource
that
at
least
once
a
quarter.
We
can
use
to
make
sure
that
we're
all
aware
of
what
the
reality
is
as
end-users
are
facing
it
now.
Oh
and
yes,
uh-huh
I,
keep
forgetting
things.
I
should
add
so
in
the
future
I'm
looking
to
remove
myself
from
this
process
as
much
as
possible.
So
in
the
future
one
of
Jeff
Elena
Katie,
will
do
the
presentation
of
this
radar.
I
G
G
We
were
kind
of
debating
how
not
to
be
kingmakers,
and
it
sort
of
occurs
to
me
that
the
SIG's
could
use
the
tech
radar
as
a
as
a
way
of
taking
kind
of
a
semi
objective
view
of
what
the
end
users
are
actually
using
to
kind
of
prioritize
into
shape.
That's
that
documentation.
So
so
so
perhaps
this
is
a
an
easy
way
to
to
unbias
the
date.
G
I
D
Absolutely
I
think,
some
time
ago,
we'd
been
saying
you
know,
it'd
be
great
to
get
more.
You
know
some
way
of
the
TOC
being
on
to
understand
what
end
users
really
want
a
need,
and
what
do
they
see
as
gaps
in
the
landscape
and
I
think
this
is
a
fantastic
initiative
to
help
supply
that
information
to
the
TOC
and
the
cigs,
and
you
know
the
whole
TOC
community.
I
I
see
the
comment
about,
except
that
the
tech
radars
retrospective
and
the
cigs
are
supposed
to
be
looking
to
the
future.
Absolutely
agree.
This
is
its
advisory
right.
It's
extra
information
that
the
six
could
use
to
make
their
judgments.
It's
not
a
suggestion
that
or
requirement
that
you
necessarily
take
any
action,
it's
just
another
data
point
and
similarly
for
covering
close
source.
It's
like
yes,
this
is
purely
advisory
to
for
the
six.
J
Can
I
ask
one
questions
and
so
here's
Bartok
from
sick
observability?
Is
there
any
way
we
can
help
with
this?
Rather,
if
it
touches
like,
let's
say
our
area,
because
we
did
like
similar
surveys
to
be
honest,
so
we
would
have
some.
We
would
love
to
have
some
input
into
into
potential
I
know
questions
or
or
things.
I
I
know,
I
really
appreciate
the
offer
to
help
and
I'm
glad
that
you
think
this
will
be
useful
enough
that
you
want
to
help
with
it
and
I
think
this
should
be
driven
by
the
end
user
community.
So
I
keep
saying
this,
but
I
don't
want
to
give
the
impression
that
you
know
you
can
Lobby
and
say
I
want
to
have
this
project
on
this
radar,
so
that
would
be
my
only
like
caveat
or
or
thought
about
it.
I
Otherwise,
like
I,
think
if
this
means
that,
for
instance,
the
cigs
and
the
end
users
can
come
together
and
like,
for
instance,
if
we
did
do
one
on
observability
and
after
a
tech
raid
I
was
published,
a
cig
said:
hey.
We
really
want
to
talk
to
this
particular
company
because
they
seem
to
be
doing
something
unexpected
or
they
they
seem
to
be
quite
forward-looking.
Like
can
you
help
connect
us
with
with
this
like?
We
could
definitely
do
that.
G
Hey
Cheryl,
quick
one:
do
we
think
we
could
maybe
extended
to
include
technologies
other
than
as
other
than
just
projects?
So
so,
for
example,
you
know
whether
it's
runtime
or
storage
or
whatever
right
there
there
are.
There
are
lots
of
different
focuses,
and
it
might
also
be
useful
to
to
gain
some
feedback
as
to
sort
of
what
classes
of
technology
as
opposed
to
just
specific
projects
are,
are
grabbing
the
attention
of
the
end
users.
There.
G
I
I
Those
are
said,
the
actual.
So
if
this,
some,
the
a
tricked
decision
of
that
would
be
made
by
that
editorial
panel.
So
if
they
wanted
to
talk
about,
you
know
what
are
people
doing
for
you
know,
objects,
door,
blocks
or
file
or
whatever
like
it
would
be
up
to
them
to
decide
what's
interesting
to
the
end
users,
so
that
makes
sense.
G
D
So
unless
it's
just
saying
that
you
know
you're
kind
of
soliciting
votes
for
topics
for
future
technology
radar,
so
and
I've
clicked
on
the
link
and
it
links
to
a
an
issue.
So
presumably
we
could
use
that
to
maybe
suggest
some
ideas.
Maybe
this
Alex's
idea
of
sort
of
technologies,
yeah
potentially
be
a
candidate.
I
Follow
the
chats,
though,
I
think
the
way
does
a
time
slice
which
also
shows
things
which
are
established
or
coming
ie,
both
directions
and
yeah.
It's
very
much
fixed
to
this
point
in
time,
so
that
could
reflect
what's
coming
up
as
well
as
what
things
are
starting
to
people
moving
away
from
just
one
point
from
our
standpoint,
I
think
the
sig
is
also
representing
end-users,
a
little
bit
anyways.
Some
way
of
hope
we
can
give
is
that
we
would
love
to
help
within
companies.
We
know
to
take
part
of
these
surveys.
I
Data
points,
yes,
absolutely
absolutely
agreed.
If
you
want
to,
you,
can
always
put
them
in
touch
with
me.
If
you
want
to
get
end-users
that
you
know
to
contribute
towards
this,
and
it
is
part
of
the
CNCs
end
user
community,
so
there's
a
little
process
for
how
they
join
that
in
user
community.
But
then
within
that,
like
I,
would
absolutely
love
to
have
the
basics,
try
and
get
there
and
the
project
maintainence
get
their
viewpoints
expressed
on
this
as
well,
and
thank
you
Katie
for
linking
the
issue.