►
From YouTube: CDF Outreach Committee - Dec. 8, 2020
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
I'm
doing
well,
how
are
you
oh,
pretty
good,
ready
for
christmas,
yeah
yep,
I
own
two
yeah
I
haven't
decorated.
I
haven't
done
anything,
but
I'm
ready
for
christmas.
You
are
you
close
enough
to
family
or
people
that
you
can
feel
comfortable,
seeing
over
holidays
yeah
I'll,
be
probably
just
my
mom.
I
don't
know.
I
don't
know
what
my
sister's
gonna
do
with
the
kids
but
yeah.
B
We
we
didn't,
spend
thanksgiving
with
them
because,
like
my
mom's
got
a
few
underlying
conditions
and
my
sister
is
going
to
the
gym,
so
my
mom
was
a
little
freaked
out.
Yeah
we'll
see.
A
A
B
Yeah
that
works,
because
I
figured
we'd,
probably
like,
depending
on
the
committee's
availability-
that's
probably
going
to
change.
I
just
I
just
thought
I'll,
just
put
something
on
the
books
to
to
just
kick
it
off.
Yeah
sounds
good.
A
I'm
glad
we
have
so
many
learnings
on
virtual
events,
so
oh
thank
you
alyssa
and
help
out
yeah.
I
should
look
at
this
press
release.
Well,
we'll
look
at
it
during
the
meeting,
so
I'll
save
the
I'll
save
the
excitement
for
that.
B
Yeah
folks
have
additional
oops
come
on.
Did
I
not
do
that?
I'm
posting
the
wrong
thing.
If
folks
have
additional
stuff
for
the
agenda,
I've
gotten
entered
a
few
things.
A
A
Yeah,
if,
if
we
can
get
some
of
the
people
who
sometimes
come
like
berlin
and
other
folks
from
like
the
folks
from
jfrog
and
stuff,
that
would
be
really
great,
but
we
may
need
to.
I
may
need
to
like
email
them
and
be
like
hey
we're
doing
something
special.
So.
A
Work
out
for
today
we'll
we'll
well
and
when's
our
so
let
me
when's
our
next
meeting.
Do
we
have
another
meeting
before
the.
B
A
The
agenda
decision
on
next
because
I
know
the
toc
cancel
theirs,
so
yeah
I
mean
it.
I
think
I
might
my
opinion.
Just
off
the
cuff,
I
would
say,
like:
let's
cancel
it
and
plan
on
meeting
on
the
fifth,
I'm
gonna,
plus
one
of
that
yeah:
okay,
okay!
Well,
we
have
two
votes
already
then
so.
A
A
And
tracy
we
were
saying
for
the
personas
conversation.
If
we
don't
get
the
turnout
for
this
meeting
that
we're
hoping
then
we
may
need
to
like.
I
may
need
to
email
people
and
let
them
know
that
we
have
something
special,
that
we
want
their
input
on
and
then
like
expect
people
to
come
on
january
5th
and
give
us
do
you
think
that
would
be
a
challenge
for
anything
that
you're
trying
to
do
with
this
this
year
or
what
or
would
having
people's
feedback
by
the
5th
of
january
be
like
acceptable.
E
Yeah,
I
think
just
progressing
it.
Okay,
this
continuously
is
good.
A
Okay,
cool
very
excited
about
this
press
release,
so
oh
hi,
tracy
hi,
put
some
more
names
on.
F
A
F
Is
a
big
lift?
It's
gonna
make
it
busier,
but
it'll
shift
right
yeah
the
whole
opens.
The
the
community
has
been
pretty
excited
about
this,
so
they've
been,
you
know,
really
pulling
together
to
see
it
happen.
Nice
welcome,
melissa,
hey.
A
Well,
things
have
been
cra
and
right
because
comply
was
released,
but
I'm
not
sure
if
you
have
to
do
anything
on
that,
because
I
know
you're
very
relay
oriented.
G
I
am
very
relay
oriented.
Well,
we
we
are
doing
some
things
with
that,
because
well
we
have
the
pe
and
relay
integration.
So
as
far
as
like
yeah,
as
far
as
like
observability
stuff
is
concerned,
we
want
to
also
do
like
get
ops
using
relay
and
comply.
A
G
G
A
Yeah
yeah,
if
you
want
to
stick
a
link
in
the
chat
or
something
I
can
put
it
in
the
doc,
because
I
would
love
to
read
it
and
I'm
making
it.
I
think
we
can
go
ahead
and
get
started.
We
don't
want
to
wait
much
longer.
So
the
news
that
we
were
also
talking
about
melissa
is
that
we've
had
a
new
project
that
was
added
to
the
cdf
as
an
incubating
project
right
nice.
And
so,
let's
take
a
look
at
this
press
release
here.
A
Most
people
on
the
call
have
probably
seen
this
so
we'll
not.
We
don't
have
to
talk
about
it
at
great
length,
but,
let's
see
so
ateliers
is
an
open
source,
microservices
management
platform
that
simplifies
the
organization
sharing
and
release
of
microservices
and
other
reusable
components,
so
so
tracy
just
to
be
tracy
reagan.
Just
to
be
clear
like
this
is,
is
this
part
of?
Are
you
using
this
product
as
part
of
your
solution
or
using
this
tool
as
part
of
your
solution?
Or
is
it
this
core.
A
F
Hub
mapping
and
versioning
part
yeah,
it's
the
catalog
and
the
versioning
and
the
the
back
end
engine
to
do
all
of
that.
Nice.
A
So
and
that's
been
the
case
for
for
a
while,
so
you've
already
been
like
kind
of
working
with
this
community
and
then
now
it's
just
now,
they're.
A
Yeah
cool
well
really
excited
about
it
and
I
missed
the
toc
announcement,
but
I'm
very
happy
to
see
see
this
and
I
have
some
homework
to
do
about
it.
I
think
simplifies
it.
F
F
I'm
trying
to
bring
isaac
in
with
potentially
somebody
from
the
argo
cd
as
well
yeah,
I'm
going
to
standardize
on
what
that
is
going
to
be.
So,
I
think
we'll
it'll
be
an
interesting
experience
and
you
know
doing
the
automated
configuration
management
around
all
these
cd
tools.
A
Yeah
yeah,
it's
super
exciting
and
I
love
how
like
everything
old
is
new
again
right.
It's
such
a
it's
so
important
for
us
to
have
this
like
cyclical,
rising
of
all
these
different,
like
kind
of
concepts
that
we
keep
stringing
together
in
new
ways
with
new
technologies.
So
it's
it's
great
to
see
like
configuration
well.
F
F
You
know
we
have
not
that
all
of
the
projects
are
alike
but,
for
example,
jenkins
and
screwdriver
are
pretty
close
and
take
down
and
spinnaker
are
pretty
close.
So
we're
not
we're
not
that,
and
hopefully
we'll
have
some
other
projects
that
will
want
to
come
in
that
are
around
potentially
open
source
security,
scanning
or
testing
tools
or
other
other
parts
of
the
cd
pipeline
that
we
should
be
able
to.
You
know
build
out
in
open
source
projects.
A
F
A
So
so
I'm
I'm
kind
of
changing
my
role
at
armory
from
being
the
spinnaker
community
manager
and
I'll
be
working.
Some
well
quite
a
lot
on,
like
our
new
venue,
some
new
products,
stuff
that
we're
working
on
some
more
r
d,
stuff
and
working
with
isaac
on
that
and
that's
part
of
what
the
argo
story
is
about,
and
I
was
thinking
we
met
last
week
with
what's
his
name
joe,
I
think
his
name
is
joe.
Oh,
no
ed,
edly
right
from
the
argo
team
and
we
had
a
really
great
conversation
with
him.
A
E
And
I'll
just
add
to
those
who
missed
the
talk
meeting
today,
tara
hernandez
was
definitely
getting
excited
and
getting
ahead
to
to
imagining
like
a
shareable
microservices
marketplace
that
could
be
owned
at
cdf
and
kind
of
just
drive
that
which
would
be
yeah
very,
very
exciting.
F
F
I
haven't
we've:
just
I've
just
started
working
with
the
events
working
group.
So
no
I
haven't.
I
I
think
it's
an
important
discussion
to
have
that
ev.
That's
one
of
my
favorites,
my
favorites,
you
know
kind
of
groups
to
talk
to
yeah,
but
we
will.
I
will
bring
that
up
to
him
and
I
can
bring
it
up
to
the
techton
team
as
well
yep.
That
sounds
good.
A
Let's
see
we
had
someone
else
join
the
oh
is
that
biology,
bibology,
hey
guys,
you
look
familiar
hi
yeah,
so
that's
great
to
have
you
here,
because
we
have
a
couple
folks,
anything
else
on
ortilius
any
questions
for
tracy
or
other
follow-up
items
for
us
to
talk
about
another
time.
E
Now
just
ask
everyone
to
help
share
the
news
so
share
on
linkedin
or
retweet.
I
think
jackie's
put
the
links
in
so
yeah.
Let's
just
spread
the
word
and.
F
We
had
him,
we
had
a
beer
and
donuts
party
too
that
as
soon
as
I
get
off
of
this
call,
I'm
gonna
I'm
gonna,
publish
and
I'll
put
it
out
on
the
cd
foundation.
Nice.
H
F
E
F
Well
I'll
make
sure
and
publish
it
and
get
it
out
there,
nice.
Well,
congratulations
so
so
exciting!
Thank
you.
It's
been
a
it's
been
hard
work
and
I'm
so
excited
that
we've
got
it
to
this
point
and
yeah.
I
want
to
thank
everybody
here.
Who's
been,
you
know
in
my
front
row.
It
helps
a
lot
to
have
few
friends
in
your
front
row.
F
A
Yeah
it's
well
and
you're
you
you
do
the
same
for
all
of
us,
so
it's
great
to
be
a
via
community
and
I
think,
like,
as
you
say,
it's
exciting,
to
see
us
thinking
about
this
more
as
a
community
and
less
as
competitors
and
like
this
is
what
it
takes
to
do
that
so
yay.
A
On
that
note,
let's,
let's
move
on
to
talking
about
personas
and
talking
about
what
are
the
personas
that
we
all
care
about
when
we
are
not
only
just
marketing
our
products
or
working
with
doing
outreach
to
our
open
source
communities,
but
for
broadly
for
cdf
outreach
who
are
the
personas
who
care
about
our
services.
So
we
have
a
draft
document
here
of
some
persona
profiles
that
we
put
together,
and
I
wanted
to
share
this
and
really.
A
I
think
this
is
mostly
for
not
to
say
that
anybody
else's
feedback
on
the
call
isn't
valuable,
because
everyone's
feedback
is
valuable,
but
I
think
particularly
melissa
and
biology,
I'm
not
sure
if
you've
seen
these
personas
and
actually
alyssa.
I
don't
know
if
you
have
worked
on
this
either,
but
no
I
have
not.
A
I
definitely
want
to
get
the
feedback
of
all
these
fresh
eyes
on
these
on
these
personas,
and
what
can
we
do
to
to
augment
them,
and
one
of
the
things
that
we
talked
about
is
like
these
seem
like
really
good
high
level
and
tracy
miranda
may
want
to
say
more
in
a
moment,
but
I
I
think
we've
agreed
that
these
are
pretty
good
high
level
categories
or
buckets.
A
Although
feedback
on
all
feedback
is
welcome,
but
a
next
step
that
we're
thinking
about
is
dividing
these
personas
into
into
more
specific
or
or
you
know
what
what
type
of
application
developer
are
you
there's
different
different,
different
specializations
right,
so
talking
a
little
bit
more
about.
That
is
something
we'd
love
to
do,
but
also
just
kind
of
kind
of
want
to
validate
the
work
so
far.
Tracy.
Do
you
have
anything
else
that
what
do
we
need
from
this
team
on
this?
What
are
you
hoping
for.
E
Yes,
so
this
is
the
document
rosalind
put
together.
We've
been
discussing
it
at
the
strategy,
calls
under
the
governing
board
and
I
think,
besides
general
feedback,
we
wanted
to
capture
sort
of
the
pain
points
for
each
group
right.
A
E
Then
also
start
to
dig
into
some
of
the
categories
like
appdev
and
just
capture
the
different
variants.
So,
as
we
get
more
sophisticated
about
how
we
think
about
our
conferences,
our
website,
our
programs,
we
always
know
who
we're
targeting.
A
A
Yeah,
that's
that's
helpful.
It's
in
the!
If
you
go
into
the
outreach
meeting,
invite
you
should
be
able
to
get
to
the
meeting
notes
and
it's
under
the
personas
target
personas
for
cdf
outreach,
but
I
will
also
just
share
the
link
in
the
chat
so
that
you
can
get
quick.
E
G
I
sent
a
request
for
access,
but
I
I'm
happy
to
get
feedback.
Okay,.
A
Let
me
get
the
I've
got
you
all
help.
Let
me
pause
my
screenshare
in
case
there's
something
weird
in
my
email.
Let's
see.
F
And
we've
been
doing,
the
ortillius
community
has
been
doing
some
work
on
this
as
well.
So
I
will
as
soon
as
you
share
that
I'll
add
I'll,
just
cut
I'll
just
copy
onto
the
bottom.
The
work
we've
done
on
the
different
individuals
that
we
perceive
to
be
users
of
continuous
delivery.
A
Thank
you,
jackie.
Thank
you
all
right
cool.
So
let's
do
let's
do
a
quick
review
of
like
what's
on
here
and
then
that
way
you
can
see
maybe
easiest
to
see
what
the
holes
are,
but
we've
got
that
application
developer
and
we
have
a
description
here.
A
A
Then
we
have
a
more
of
a
director
level
persona
the
delivery
director-
and,
let's
see
so
that's
really-
that
person
is
really
focusing
on
focusing
on
roi
and
focusing
on
the
big
picture,
as
is
the
technology
executive.
A
We
have
described
here
and
we
have
this
other
role
that
we
thought
of
as
like
a
solutions
explorer,
and
some
of
these
people
are
more
like
devrel
types,
but
there's
a
range
and
I'm
interested
to
know
like
if
there
are
other,
like
maybe,
as
we
said,
subsets
of
this
or
other
titles
that
are
associated
with
this
kind
of
behavior.
A
As
far
as
researching
these
are
the
people
who
get
hands-on
with
the
tooling
but
they're.
It's
like
more
of
an
inch
deep
mile
wide
thing
than
using
it
to
do
us
to
like
create
a
solution,
and
I
think
that's
an
important
distinction
from
folks
who
are
folks
who
are
trying
to
solve
a
problem
versus
maybe
trying
to
evangelize
the
technology.
Even
if
that
is
internally
within
their
team
or
something.
G
Yeah
go
ahead
so
okay,
so
I
guess
something
like
where
would
someone
who's
say?
A
cloud
engineer
run
in
here
so
like
if
somebody
is
like
auditing,
their
aws
infrastructure,
or
you
know
looking
for
underutilized
instances
and
then
wanting
to
get
like
reports.
G
A
Yeah,
I
think
that
person
falls
under
devops
champion,
but
I
think
this
this
bucket
more
than
any
of
the
others,
maybe
would
would.
It
would
be
incredibly
useful
to
break
this
out
a
little
bit
and
try
to
so.
I
just
added
cloud
engineer
to
the
list
and
we
have
cloud
architect
on
here
which
is
like
kind
of
similar,
but
I
think
that,
even
like
the
use
case
that
you
just
mentioned,
that's
pretty
specific
right.
G
So
the
reason
I
I
kind
of
think
that
one
maybe
should
be
broken.
Half
then
is
like
so
a
cloud
champion
could
be
someone
who's
focused
entirely
on
like
ci
and
cd
and
like
all
their
use,
cases
like
they
might
not
even
ever
know
about
tekton
or
touch
tecton,
because
they're
not
really
working
in
like
a
hybrid
cloud
environment,
and
so
a
lot
of
them
would
just
be
looking
at
on-premise
stuff.
G
G
Like
often,
people
are
just
looking
at
being
like
a
linux,
administrator
or
windows
administrator,
and
so
they
basically
their
day-to-day,
is
like
basically
not
necessarily
super
involved
in
like
cloud
services
or
cloud
infrastructure
and
they're
more
like
on-premise,
meaning
they're,
using
like
more
like
an
os.
That's
like
a
virtual
os,
maybe
but
they're
not.
H
C
G
B
G
Yeah
yeah,
so
I
I
just
meant
like
that
might
be
broken
out
into
two
sections,
so
one
would
be
devops
champion.
Another
one
would
just
be
like
cloud
cloudy
type
of
person
because
even
like
an
sre,
I
think
would
think
I
would
consider
them
to
be
kind
of
a
cloud
engineer
because
they're
all
about
site
reliability
they're
using
like
they
might
actually
be
more
of
a
techton
target
because
they
would
be
looking
at
they
might
use
tekton
with
other
tools
which
give
them
like
notifications
of
things.
That
might
have
changed
condition.
G
F
I've
added
a
ton
of
which
you
know
we
worked
on
breaking
this
stuff
apart,
so
we
did
it
based
on
their
role,
the
skill,
their
goals,
their
motivations,
their
frustrations,
and
we
try
to
try
to
control.
They
try
to
create
personas
like
we
have
devops
or
release
engineer
jake,
and
we
have
sam
and
we
have
okay.
So
we
did
try
to
imagine
those.
So
maybe
we
can
just
build
on
some
of
those
roles
or
maybe
you
guys
should
take
a
look
at
it
and
yeah
see
if
it
makes
sense
or
not
well,.
A
Sorry,
I'm
just
going
to
tag
you
here
and
ask
you
if
you
don't
mind,
taking
a
look,
because
I
don't
we
can
look
at
these,
but
we
won't
be
able
to
be
as
thorough
as
you
can
be.
So
if
you
have
time
to
like
provide
feedback
on
this
and
say
if
they
had
anybody
who
had
or
or
say,
this
doesn't
look
quite
like
from
my
perspective,
this
is
a
little
too
specific
because
I
I
do
think
it's
important
for
us
to
like
when
we're
talking
about
cloud
versus
on-prem.
A
It's
it's.
Definitely
not
a
black
and
white
thing
right.
It's
a
continuum
and
different
organizations
are
managing
these
resources
in
pretty
heterogeneous
ways.
So
we
don't
want
to
be
like
exclusive
to
people
who
are
still
like
doing
mainframe
stuff.
I
mean
that
makes
a
lot
of
sense,
that
they
don't
understand
the
cloud,
but
many
of
what
some
of
them
don't
and
like
that's,
okay,
so
we
just
kind
of
have
to
pay
attention
that
continuum.
I
think
it's
really
important.
So
thank
you
for
bringing
that
up.
G
Yeah
that
would
make
a
lot
of
sense,
so
I'll
have
to
think
about
that,
but
yeah.
So
another
thing
I
was
thinking
of
when
I'm
looking
through
this
document
would
be
like.
I
don't
see,
and
I
don't
know
if
this
is
even
a
target
like
I
don't
specifically
see
someone
who
would
be
considered
like
low
code
or
no
code.
I
mean
I
guess
that
could
be
sprinkled
into
any
of
these.
A
Yeah
so
well,
I
think
I
guess
tell
me
more
because
I
think
that
it
depends
on
what
the
task
is
so
like
low
code,
doing
what
low
code
or
no
code.
So
is
this
like
a
delivery
director
who's,
maybe
doing
a
low
code,
making
a
dashboard
with
a
low
code
solution?
G
What
I
mean
consumer
I'm
talking
about
more
from
a
consumer
perspective,
because
there's
also
the
possibility
that
people
like
at
least
in
the
case
of
like
what
we
do.
There
are
instances
where
folks
are
not
going
to
really
want
to
like
use
emel.
G
C
A
D
Yeah,
I've
added
a
few
titles
that
that
hopefully
makes
sense
and
and
yeah
I
haven't,
looked
at
the
pain
points,
but
I
can.
I
can
chuck
something
on
some
legs.
B
Act
for
the
devops
champion.
I
think
that
maybe
we
might
just
need
to
rename
it
instead.
B
Champion,
I
think
the
champion
part
was
tripping
me
up
earlier,
because
it
makes
it
sound
like
an
evangelist,
and
these
roles
aren't
necessarily
evangelists,
and
I
wonder
if,
by
renaming
it
as
well,
we
might
be
able
to
cover
the
additional
roles
that
melissa
and
bolaji
have
brought
up.
A
A
I
think
for
me
the
top
pain
point
that
comes
to
mind
when
I'm
thinking
about
app
dads
is
context.
Switching,
that's
one
that
we
think
about
a
lot
and
in
these
times
of
tool,
soup
context,
switching
is
a
very
has
a
high
cost
and
is
also
frustrating
for
app
devs.
What
else
for
app
devs
pain
points,
or
we
can?
We
can
go
on
to
this
devops
blah
category
2.
D
I
would
say
you
know
they
are
worried
about
or
not
they
want
to
know
where
their
code
is,
I
mean,
did
the
code
get
to
the
production
or
not
right?
I
think
that
level
of
visibility
or
whatever
you
want
to
call
it
right.
Essentially
they
could
change,
but
it
may
be
stuck
somewhere
or
it
did
actually
make
it
to
production.
What
happened?
Did
it
roll
back
some
sort
of
visibility
around
their
court
checking,
I
guess
connector,
for
example.
Has
this
thing
you
pipeline
that
they
can
see?
D
You
know
where,
where
that
pipeline
is,
in
that
sense,
right.
A
That
kind
of
capture
it
observability
of
status
and
processes
after
code
check-in.
A
G
D
A
Oh
okay,
yeah
and-
and
I
think
they
definitely
care
about
how-to
content.
So
that's
a
good
one
to
have
on
there,
but
yeah
for
low
code,
no
code,
maybe
we
just
say
difficulty
or
lack
of
interest
or
ability
in
using
yaml
or
other
declarative
languages.
G
Well,
yaml
in
particular,
is
like
a
whole
sea
of
just
confusion,
so,
like
also
like
within
the
tecton
sphere,
things
are
very
low,
like
not
low
code,
sorry,
but
they're,
very
like
low
level.
So
when
you
are
using
gamble,
it's
very
it's
very
low
level
yaml
so,
like
the
end
user
might
end
up
with,
like
various
different
triggers
and
various
different
events
that
they
can
do
so,
like
the
reason
why
a
product
that's
built
on
top
of
tekton
has
done
like
they've
even
bothered
like
investing
in.
G
That
is
because
there
is
like
a
low
code
and
no
code
type
user
who
just
wants
to
use
like
a
gui.
They
can
see
the
workflows.
They
want
to
basically
have
some
interaction
with
it,
but
they
don't
necessarily.
They
don't
necessarily
know
enough
yaml
to
just
like
dive
into
tecton,
because
tecton
is
very
complex.
Yeah.
A
A
Is
very
very
low
level,
and
so
and
the
like,
it's
complex,
the
way
that
the
yaml
files
are
linked
or
integrated
into
the
service
right.
G
Yeah
there's
that
aspect
of
it
I
mean
any
open
source
project
can
be
like
that.
But
then
I
think
it's
primarily
that
it's
really
like
tekton
is
really
low
level
yaml.
So
anything
that's
built
on
top
of
it
is
meant
to,
or
at
least
like
built
using.
It
is
meant
to
like
make
that
a
little
bit
easier
for
the
end
user,
because
at
the
end
of
the
day,
they're
not
they're,
not
like
full-on
experts
with
cloud
native
resources
and
tooling.
E
G
I
think
for
both
of
them,
because
I
mean
there
could
be
an
app
developer,
who
isn't
isn't
like
super
super
familiar
with
yaml
but
they're
working
on
something
like
which
uses
cloud-native
resources
or
tooling.
And
then
you
have
someone
who's
focused
entirely
on,
like
let's
say
just
operations
and
that's
like,
I
feel
like
a
different.
They
have
a
different
scope,
but
they
have
the
same
problem.
A
Sounds
good
scopes
focus
on
similar
problems,
lots
of
really
good
notes
here
that
will
help
us
refine
this.
Thank
you
so
much.
Let's,
let's
talk
a
little
bit
about
pain
points.
If
we
have
time
time
check,
let's
see
we're
at
10
30,
and
we
have
a
few
more
things
to
talk
about.
I
think
we
have
a
few
more
minutes
since,
since
you
both
are
great
feedback
givers,
so
keep
it
up.
Pain
points
for
this
category.
A
That's
a
little
nebulous
right
now,
but
I
think
the
title
should
give
you
give
it
away
like.
This
is
a
whole
class
of
people
who
are
thinking
about
infrastructure
and
the
way
that
things
are
securely
and
reliably
architected,
either
in
the
cloud
or
on-prem
or
both
so
and
and
paying
attention
to
empowering
teams
and
keeping
teams
within
the
business
requirements.
E
I
had
a
pain
point
for
the
updates.
Sorry,
oh.
A
A
I
found
this
a
lot
when
talking
to
these
folks
what
else
it's
painful
for
this
persona
biology.
This
is
our.
This
is
a
bread
and
butter
for
spinnaker.
So
I
know
you
have
yeah.
I
mean
well.
D
I
think
reduction
in
time.
I
guess
right,
I
mean
amount
of
time.
It
takes
the
court
to
go
to
production.
How
do
we
reduce
the
time
to
reduce
to
production.
D
I
would
say
how
do
I
support,
I
guess,
various
applications
or
workload
types
or
targets
like
cloud
versus
on-prem,
blah
blah
blah.
A
Yeah,
that's
a
good
one,
so
kind
of
just
the
heterogeneity
right.
D
I
think
the
other
thing
that
these
people
sort
of
run
into
is
you
know,
I
mean
I'm
not
sure
it's.
They
definitely
are
in
the
mix
of
selecting
the
this,
this
tooling
right
for
the
for
the
organization.
So
there's
a
lot,
there's
there's
an
open
source
versus
you
know
other
things
out
there,
so
they
definitely
struggle
with
selecting
the
right
tooling
for
it
and
integrations
you
could
talk
about
integrations.
You
know
like
and
integrate
multiple
things,
because
they
have
other
things
already
there.
D
A
D
A
So
I
heard
almost
another
pain
point
there
that
I've
heard
from
this
group
is
like
application
develop.
Let's
just
say
like
folks
who
consume
this:
the
tooling
that
this
this
persona
cares
about
are
set
in
their
ways
and
they're,
not
it's
hard
to
get
them
to
switch
right.
I
mean
I
find
that
that's
a
pain.
Does
everybody?
Can
they
do
you
think?
That's
a
pain
point.
D
Getting
adoption
any
new
tooling
is
a
challenge
right
and
because
of
legacy
and
some
cost,
and
no
don't
want
to
touch
something.
That's
working
yeah.
That
kind
of
a
thing
I
mean
educating
and
onboarding
new
applications.
Users
is
a
big
challenge
for
them:
yeah,
just
because
they
put
something
in
there
doesn't
mean
that
everybody's
gonna
adopt
them
right.
So
yeah.
A
That's
good
and
some
of
these
might
end
up
getting
combined,
but
I
think
it's
good
anything
else
to
add
alyssa.
I
know
you're
really
like
in
touch
with
us.
C
Yeah,
I
don't
have
anything
specific
to
add
to
this
document
right
now,
I'll
have
to
review
it
after
the
meeting,
but
I
think
I
think
it's
it's
a
great
document,
but
I
was
wondering
so
in
addition
to
this,
would
it
be
worthwhile
for
us
to
do
like
a
survey
throwing
it
out
to
the
community
and
get
their
feedback.
A
Maybe
once
we
have
something
a
little
bit
like
once,
we
like
you,
take
a
pass
out
at
alyssa
and
we
get
some
more
comments.
Maybe
we
can
figure
out
how
to
turn
that
into
some
questions,
or
maybe
we'll
have
questions
that
come
up.
So
maybe
action
item
is
like
as
we
go
through.
This
create
a
list
of
questions
for
clarification
that
come
up
and
that
can
see
the
survey.
A
Some
of
these
already
will
already
be
in
comments.
We
can
aggregate
those-
maybe
we
add
a
section
of
questions
to
the
docs,
so
we
can
use
it
later.
Good
idea,
all
right
time
check
again.
We
got
we're
coming
up
to
the
end
of
the
time
pain
points.
Can
we
quickly
talk
about
pain
points
for
these
other
personas,
for,
like
the
for
the
executives
and
the
directors
comes,
what
comes
up?
A
And
are
these
more,
I
think,
probably
both
of
these
personas
care
about
both
of
these
things,
yeah
yeah,
yeah,
probably.
D
D
And
you
know
kind
of
you
know
how
many
engineers
they
have
to
allocate
right.
You
know,
do
I
just
get
a
sas
product
and
be
done
with
it
yeah
or
do
I
do
I
do
a
self
d
do
do
it
to
myself
and
then
have
two
engineers
allocated
for
rest
of
their
lives
right.
Sometimes
I.
D
E
A
Yes,
and
that's
that's
specifically
more
for
the
director-
I
think
that
maybe
just
thinking
about,
like
so
reducing
context,
switching
because
the
director
cares
a
lot
about
productivity
of
their
teams.
So
I've
found
that
this
kind
of
comes
up.
A
And
maybe
who?
Who
cares
about
legacy
workloads,
like,
I
think
in
a
lot
like,
especially
we
talk
a
lot
about
fintech
like
in
fintech.
I
think
is
it
these
folks
who
are
tasked
with,
like
you
know,
like
we
have
all
this
cool
new
tech
that,
yes,
we
need
to
use,
but
by
the
way,
like
that
legacy
workload
that
has
been
working
and
has
been
secure
and
reliable
for
10
years,
like
you're,
not
changing
that.
It's
like
these
people
kind
of
have
to
deal
with
the
upstream
impact
of
that
like.
A
D
That
they
care,
I
mean,
I
think,
that's
what
seems
to
be
everybody's
their
day.
Job
is.
A
A
Okay,
anything
specific
for
the
executive-
that's
not
already
in
here
really
what
do
we
have
for
the
executive?
I
think
it's
probably.
A
Yeah
so
like
maybe
it's
more
about
like
telling
this
telling
the
story
of
digital
trans,
I
mean,
maybe
it's
not
digital
transformation
but
yeah
being
able
to
justify
or
like
show
so
showing
progress
in
digital
trans
formation
and
maybe
like
other
way
other
reason.
Other
things
that
go
into
pleasing
the
board
is
like
adhering
to
what's
budgeted.
G
Yeah,
I
mean
not
not
only
adhering
to
what's
budgeted
but
also
like,
I
feel
like
and
like
a
cio
or
whatever
well
or
cto
will
also
have
to
like
consider
selling
ideas,
probably
to
like
a
board
or
selling.
If
there
is
going
to
be
something
new
or
something
different,
balancing
that
I
guess
the
new
or
different
stuff
with
whatever
the
you
know,
primary
motivator
primary
money
maker
is
within
the
company.
A
Yeah,
this
is
good.
I
think
we
should
wrap
this
up
to
make
sure
that
we
have
time
to
talk
about
the
other
items
on
the
agenda
unless
yeah,
but
how
about?
Let's?
We
still.
I
would
love
to
talk
a
little
bit
more
about
the
solutions
explorer
and,
of
course,
asynchronously.
Oh
thanks,
so
I
see
you
folks
are
already
like
kind
of
swarming
on
this
dock.
A
Keep
doing
that
and
then
we'll
talk
about
this
more
at
our
january
5th
meeting
and
we'll
see
if
we
can
get
more
folks
from
the
wider,
our
wider
community
to
join
and
talk
to
us
more
about
these
pain
points,
but
we'll
have
the
document
a
little
bit
more
buttoned
up
before
that.
Thank
you
so
much
for
your
feedback.
It's
awesome.
E
All
right,
and
just
one
thing
to
add
to
that
just
for
2021-
I
think
what
we're
seeing
from
the
board
is.
You
know
acknowledgement.
We've
we've
focused
a
lot
on
the
the
ops
type
role
and
shifting
left
to
the
app
dev,
but
in
2021
we
want
to
consciously
target
the
leadership
roles,
so
the
delivery
director,
the
c-suite
and
we'll
be
trying
to
figure
out
how
to
do
that
through
cdcon
and
and
other
channels.
So
any
ideas
and
thoughts
please
bring
those
to
the
the
january
5th
meeting.
E
A
All
right,
podcast
wrap
up
jackie,
I'm
gonna
some
links
here
or
do
you
yeah.
B
It's
a
it's
a
link
to
to
a
a
blog
that
we
wrote
just
giving
some
stats
of
who
participated
in
the
podcast.
How
many
downloads
we've
had
how
many
speakers
and
then
how
many
episodes
we're
wrapping
up
the
year
publishing.
B
So
I
thought
that
was
something
really
good
to
highlight
to
this
community.
It's
an
easy
like
way
to
collaborate
with
the
cdf
we
had.
Actually
quite
a
few
members
participate
this
year
we
wrapped
up
the
year
with
25
recorded
episodes,
and
we
are
publishing
them
one
each
week
for
the
remainder
of
the
year
and
then
I've
also
highlighted
our
top
five
episodes
so
yeah.
B
I
think
this
is
an
easy
way
for
the
community
to
get
involved
with
the
cdf
and
it's
an
easy
way
to
get
your
brand
awareness
out
there
as
well,
and
if
you
scroll
down
to
I
thought
that
was
kind
of
like
a
cool
little
map
of
like
where
our
listeners
are
from,
for
example,
so
yeah.
So
that's
that's
some
more
stats
into
who's.
Listening
to
us
and
who's
tuning
in
so
that's.
I
thought
that
was
another
good
key
point
for
folks.
B
If
you're
trying
to
expand
your
audience,
yeah
take
a
look
at
that
we
we
could
definitely
use
your
help
and-
and
you
know
it
benefits
both
of
us.
The
other
thing,
too,
is
I'm
starting
planning
for
the
webinars.
B
I'm
also
thinking
about
changing
the
name
webinar
to
webcast.
Since
I
know
some
folks
have
given
feedback
on
that,
but
yes,
so
this
is
also
a
really
great
member
benefit.
We
are:
we've
updated
our
webinar
guidelines,
so
I
encourage
folks
to
definitely
take
a
look
at
those.
B
B
Yeah
and
then
the
next
one,
you
know
that
we're
working
on
still
is
the
annual
report,
so
I've
included
also
the
link
to
the
working
deck,
as
well
as
the
work
back
calendar
and
that
outlines
all
of
the
sections
that
are
going
into
the
annual
report
and
it
highlights
you
know,
milestones
and
due
dates
and
owners,
so
yeah
we're
we're
slowly
working
through
through
that.
The
other
thing
I
wanted
to
chat
about
really
quick
is
and
just
again,
if
folks
are
participating.
B
If
community
projects
are
participating
in
gsoc
2021,
please
let
us
know
so
that
we
can
also
take
account
into
how
many
projects
per
community
projects
are
being
submitted,
because
I
think
we
will
need
to
go
to
google
and
and
see
what
we
can
do
there
to
negotiate
some
more
spots.
B
So
everybody
hopefully
can
can
participate,
and
we
won't
have
to
pick
and
choose
then
the
other
one
that
I
wanted
to
highlight
as
well.
If
you're
interested
in
participating
in
the
planning
committee
for
cdcon
2021,
our
kickoff
meeting
is
december
14th
at
8
a.m:
pacific
standard
time
this
probably
might
change
depending
on
the
community
the
planning
committee's
availability
to
meet,
but
I
just
thought
I'd
include
the
google
invite
and
then
also
the
zoom
link
for
this
first
one.
B
E
Cool
all
right,
oh
wait.
Actually,
there's
one
more
thing:
looking
for
feedback,
I'll
drop
this
in
the
group
chat,
but
roxanne
and
jackie,
and
I
have
been
working
on
a
updated
cdf
join
member
page
and
a
deck.
So
this
is
not
live
yet.
So
well,
it's
it's
there,
but
it's
not
linked
off
the
main
website,
but
we're
looking
at
making
it
more
compelling
as
to
why
people
should
join.
E
So
it's
still
a
work
in
progress,
but
any
feedback
would
be
appreciated
and
we'll
be
linking
in
a
full
kind
of
member
benefit
stack
at
that
kind
of
orange
call
to
action
button
but
yeah.
If
anyone
has
any
feedback
or
things
aren't
clear
or
we
could
make
it
nicer,
I
think
we'll
be
looking
to
do
a
big
push
for
new
members
next
year
and
bringing
that
value
so
yeah
this.
This
highlights
it
and
also
to
make
sure
existing
members
are
taking
advantage
of
all
the
things
we
have
to
offer.
A
Yeah
definitely,
this
is
a.
This
is
a
great
resource.
I
really
like
the
icons.
That's
definitely
eye-catching
a
good
way
to
organize
the
page,
okay
cool
I
can
give
when
you
get
the
fees
right
on
here
too,
you
can
get
some
feedback
see
this.
E
Yeah,
no,
that's
it!
Okay,
if
there's
any
feedback,
let
us
know
yeah.
A
A
little
a
little
description
here
would
be
good
yeah,
like
maybe
just
maybe
tell
them
what
they're
getting,
and
even,
if
that
links
to
another
place
on
the
page
that
tells
them
what
they're
getting
like,
then
you're
keeping
them
engaged
in
the
page.
Maybe
it
looks
like
it
looks
like
something
forgotten
seeking
feedback
for
new
member
joining
page.
A
Cool
any,
when
do
you
need
that
feedback
bye.
E
A
I
A
Like
we
should
be
thinking
about
that
when
it
comes
to
scheduling
for
cdcon
right
because
maybe
that's
like
a
whole
untapped,
not
untapped,
but
we
know
that
they
care
about
our
content.
So
anyway,
next
next
meeting
should
we
meet
on
january
5th,
or
should
we
try
to
meet
again
on
the
22nd?
A
All
right,
let's
go
for
the
fifth
and
we
will
try
to
get
a
good
showing
at
the
meeting
so
that
we
can
get
more
feedback
and
and
talk
about
our
plans
for
2021.
As
far
as
how
we
can
engage
more
leadership
roles-
and
I
just
wanted
to
remind
everybody
one
more
time
to
share
this
ortilius
press
release.
I'm
going
to
do
that
right
now,
after
this
meeting
share
it
on
linkedin
or
twitter.
A
F
A
E
B
Agreed
we're
done
when
it's
december
15th
from
at
9
00
a.m,
pacific
standard
time.
A
Did
it
okay,
the
day
after
yeah,
so
and
has
the
invite
already
gone
out
yeah.
B
It
all
it's
gone
out
to
the
all
of
the
lists,
so
it
it's
probably
just
sitting
in
the
inbox,
but
I
can
I
can
send
you.
One
roth,
no
worries
I'll
find
it.
A
I'm
just
gonna
all
right,
thanks
everybody
for
your
time
today
and
looking
forward
to
partying
with
you
next
week.
Thank.