►
From YouTube: CDF TOC Meeting - Aug 2, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
So
hello,
hello,
welcome
to
the
cdf
dvc
meeting
today
is
august
2nd
and
we
have
a
few
topics
in
our
agenda.
So,
first
of
all
gifts,
a
proposal
with
an
tcg
election
cdf
reference,
section,
continuation
review
of
community
guidelines
and
some
bits
of
upcoming
events.
A
If
you
have
any
other
topics,
you
would
like
to
add
to
the
agenda.
Please
just
do
so,
and
here
the
first
topic
is
about
peer
sam.
So
there
was
the
line
to
vote
on
29th
of
june
july.
So
by
the
deadline
we
got.
Seven
binary
quotes
no
negative
feedback
and
I
press
it
is
concluding
the
work
board.
So
now
pc
is
officially
accepted
to
the
foundation
I
created
a
ticket.
For
that.
It's
him.
A
B
C
You
did
that
pr
get
merged,
then.
A
Yes,
I
mentioned
the
proposal
request.
So
if
something
needed
you
can
still
do
updates
postfactom,
but
yeah,
it's
meshed.
By
now.
A
Actually,
I've
matched
all
of
two
simple
requests,
except
the
most
recent
one
submitted
by
fatih
about
the
documentation.
D
A
A
E
C
Let's
go
ahead
and
merge
that
leg
and
then
as
the
hinder
and
I
and
the
other
folks
at
persia
are
doing
the
onboarding
process.
If
we
find
anything,
that's
a
little
weird,
we'll
open
an
issue.
F
Yeah,
I
have
a
question
about
persia
now
the
steps
you
need
to
follow
they,
I
think
there
are
like
two
three
high
level
items
like
one
of
them
is
legal
review
like
license
scan
and,
like
you
know,
if
the
name
has
any
copyright
issues
and
so
on,
so
we
need
to
open
it
to
lf
legal.
F
They
will
do
that
and
then
transfer
of
domain
and
such
things
we
need
to
open
another
ticket
for
that
and
the
announcements-
and
I
already
started
a
thread
with
lori
and
the
cdf
stuff
to
plan
this
or
the
coordinate
announcement
and
so
on.
So
those
are
the
three
high-level
items,
but
they
will
come
with
more
detailed
steps
under
the
issue
like
open
up
foundation
repo.
So
who
should
we
be
working
with
sudhindra
and
steve?
You
too
yeah
yeah,
yeah
and
glory
for
the
announcement.
G
Yeah,
I
want
to
kind
of
be
a
part
of
all
of
them,
because
we
have
to
have
a
full,
concerted
effort
going
with
all
the
team
and
part
of
what
I
need
to
do
is
document
what
we're
doing
so
for
for
everything.
So
if
I
could
be
a
part
of
the
conversations
with
stephen
cedinger
that'd
be
great
so
that
I
can
fill
up
the
chain.
F
Yeah
then,
I
will
start
at
threads
and
I
will
put
all
those
items
under
the
foundation.
The
issue
olek
was
showing,
so
it
is
like
everyone
can
see.
What
are
the
items
we
need
to
deal
with
and
then
we
follow
them
one
by
one
and
then
we
keep
you
updated
with
the
progress
on
legal
side
and
elsewhere.
D
D
C
Yeah
and
the
in
the
proposal
we
had
a
list
all
the
licenses
that
persia
was
consuming.
So
all
that
work
has
been
done
and
it's
in
the
proposal.
F
B
B
That
I
can
check
out,
but
that
was
built
by
jfrog,
so
we
can
I
I'll
work
with
our
team
to
figure
out
what
lies.
What
is
the
license?
We
need.
Let
me
know.
G
Yeah
I
was
talking
with
steven
yesterday
and
basically,
a
new
task
was
added
to
my
list,
which
is
trying
to
get
all
of
the
onboarding
stuff
put
together
from
the
admin
side
in
terms
of
like
username
passwords.
All
of
that
stuff,
I'm
going
over
the
the
doc
that
oleg
had
up
there
and
making
sure.
B
G
C
Great,
oh,
that
brings
up
one
thing.
I
don't
think
that's
in
the
documentation
because
it
came
later,
there
was
a
request
for
the
a
certain
user
id
from
the
lfx
side
to
be
added
to
the
get
repo
at
the
org
level
and
yeah.
C
A
Okay
yeah,
I
just
added
a
few
items
but
yeah.
I
will
glance
through
this
checklist
and
I
added
open
source
license
kanink
as
fatty
mentioned,
though.
If
I
understand
correctly,
there
is
one
issue
with
that.
Some
from
what
I
heard
the
effect
security
is
still
unavailable.
F
I
think
this
license
scan
is
actually
while
the
project
is
going
through
legal
review
like
not
continuous
scan,
if
I
understood
correctly
from
the
document
I've
seen
so
what
you
are
saying
is,
I
think,
the
topic
we
discussed
some
months
ago
to
enable
this
old
project.
I
think
that
is
separate
than
this.
I
haven't
checked
that,
but
I
can
check
it
so
project
license.
C
Yeah
and
the
one
that
we
ran
against
persia
was
a
rust
because
all
the
codes
in
rust
that
we
ran
a
rust-based
license
scanner
to
pull
out
all
the
package
dependencies
and
the
licenses.
C
D
C
Thing
that
we
may
have
missed
is
the
website
is
runs
under
a
react
framework,
so
there
may
be
a
node
scan
that
needs
to
be
done
for
the
licenses
on
that
front.
But
that's
basically
the
docusaurus
code
base.
A
Okay
yeah,
so
speaking
of
this
list,
the
results
have
a
bunch
of
follow-ups
which
were
created
like
patent
transfer
requirements,
etc.
So
fatty,
if
you're
going
to
speak
with
legal,
maybe
it
makes
sense
to
bring
up
these
topics
so
for
some
requests
here.
So
here
we
got
the
response.
D
A
Okay,
that's
even
easier,
then.
F
But
I
will
go
through
the
onboarding
document
again,
as
well
as
the
open
issues
for
onboarding
related
issues,
and
I
highlight
them
to
legal.
If
we
haven't
got
any
response
for
them.
F
And
there
are
some
other
logistics
stuff,
like
slack
or
what
I
don't
know,
what
sergio
is
using
for
asynchronous
communication
or
mainly
stack
of
stuff.
So
they
will
all
be
part
of
this
onboarding,
like
maybe
you
already.
G
B
C
So
there's
this
slack
go
through
lfx
iit,
or
is
that
something
you
do
fatty.
B
B
And
for
the
most
part
we
have
kept
everything
under
you
know
an
independent
control,
so
persia
has
its
own
google
group
and
everything.
So
it's
easy
to
manage.
Yeah.
A
And
I
believe
well,
we
can
grant
access
to
all
tucson
members
if
needed.
F
Okay,
that
is
part
of
one
of
the
documents
we
have
up
there
for
review
of.
I
think
what
we
are
planning
to
do
is
we
plan
to
give
access
to
commander
for
ship
code
shares,
port
numbers
and
project
leads
or,
however,
you
call
them.
So
you
don't
go
through
us,
you
can
go
and
manage
your
prison.
Cdf
calendar,
your
stuff.
A
F
Baby
is
a
bit
we
can
discuss
this
separately.
You
please
don't
go.
D
D
B
A
Okay,
so
yeah
touristy,
chair
election,
just
a
reminder:
the
deadline
is
tomorrow.
I
guess
tomorrow
anywhere
on
the
earth
or
something
like
that,
but
yeah.
If
anyone
wants
to
run
for
the
toc
chair
position,
please
just
put
your
nomination
here
after
some
consideration
I
put
in
my
nomination
but
yeah.
So,
first
of
all,
even
if
I
continue
for
this
term,
I
won't
continue
for
the
next
term,
I'm
huge
supporter
of
changing
public
roles
in
the
community.
E
If
you
considered,
we
considered
a
vice
chairperson,
because
if
oleg,
if
you're
saying
hey
man
next
time,
if
you
get
it
you're
not
coming
back
for
it,
I
think
it
would
be
a
good
move
for
somebody
else
to
say
all
right.
Let's
see
what
this
is
all
about
and
at
least
share
some
of
the
responsibilities.
A
Yeah,
it's
perfectly
fine,
so
this
is
basically
what
I
mentioned
in
terms
of
if
you're
interested
in
the
future.
Why
not?
If
you
want
to
formalize
this
position,
I'm
also
perfectly
fine.
E
We
should
have
done
this
before
the
persia,
bringing
that
in
and
merging
that.
So
we
could,
you
know,
make
it
conditional
for
the
persea
team
that
they
have
to
be
vice
chairperson,
you
know
give
to
get.
G
E
Absolutely
well
look
oleg.
I
I
do
think
that
thank
you
for
nominating
yourself,
but
but
look
I'm
new
guy.
I
I'm
certainly
not
talking
about
myself,
but
I
do
think
somebody
with
more
experience
should
be
a
vice
chairperson
and
and
just
start.
You
know,
first
of
all
to
help
you
out
ola
because
I
know
you're
doing
a
lot,
but
also
to
get
ready
for
the
next
turn.
I
mean
we
want
to
continue
this
right.
G
G
A
Yeah,
so
if
anyone
is
interested
just
to
dm
me-
or
I
will
probably
name
a
few
people-
let's
see
but
yeah,
I
agree
that
some
continuity
in
this
role
is
important.
A
D
A
Thanks
and
yeah
so
toc,
basically,
there
is
contributors
in
the
e
which
leads
us
to
contributors.
A
Okay,
so
we
probably
should
then
explore
tracy
from
here
because
she's
now
do
you
see
member
but
yeah,
otherwise,
just
again
itself.
F
Oh,
it
is
probably
where
michelle
is
located.
I
I
will
go
and
confirm
this
with
michelle.
Sorry,
we
missed
that
the
time
of
the
day.
D
F
So
I
have
the
link
to
deck
there.
I
think
let
me
share
my
screen
if
it
is
okay
with
you,
so
I
can
quickly
highlight.
Where
is
the?
F
Yeah,
okay,
so
we
added
six
more
slides
here
that
three
first
like
10
to
12
is
the
feedback
from
the
gardening
boards
today
session,
which
took
place
on
thursday
last
week,
and
we
simply
like,
I
simply
went
there
and
added
the
questions
and
comments
about
the
proposal.
Reference
architecture
proposal
there
and,
if,
like
I'm,
not
going
to
read
all
these
bullet
points
individual,
but
at
least
I
felt
like
we
need
to
come
up
with
more
concrete
actionable
items
to
present
this
idea.
What
this
reference
architecture
actually
means?
F
Who
is
the
audience
for
this
initiative?
And
what
is
the
target
for
this
initiative?
So
that
is
like
one
of
the
like
two
of
the
main
feedback
we
received
apart
from
that
like
what
are
the
ways
we
could
help?
The
organizations
who
are
on
their
way
to
embrace
countries
that
are
in
education
was
highlighted
as
one
of
the
key
things
this
initiative
could
help
others
with
and
finally
it
more
work
is
needed
to.
F
F
I
think
all
like
you
word
one
suggesting
to
have
this
work
starting
or
details
under
special
telescope
best
practices
and
the
other
three
slides
are
about
like
proposed
next
steps,
and
yesterday
tracy
reagan
sent
an
email
to
tlc
mail
list
and
she
proposed
to
have
this
work
done
under
a
new
work
group.
So
we
simply
put
the
two
proposals
in
front
of
us
like
under
sick
based
purposes
or
any
work
group.
F
So
these
are
the
proposals
out
there
and
but
this
regardless
of
where
this
work
is
done,
the
conversation
should
take
place
around
like
scope
of
the
work
interactions
with
other
groups,
like
other
sikhs,
ambassador
group
outreach
and
so
on.
What
are
the
inputs
and
what
are
the
outputs?
This
type
of
information
should
be
made
available
because
it
is
difficult
to
grasp
what
this
work.
Actually,
what
this
initiative
actually
means-
and
few
of
you
were
in
the
meeting,
so
I
want
to
stop
talking
now-
maybe
oleg
terry
steve
lori.
Any
of
you
want
to
add
christ.
H
The
work
that
we
need
to
do
is
is
is
actually
quite
straightforward.
I
I
don't
think
this
is
massively
complicated
at
this
stage
and
really
what
what
needs
to
come.
Next
is
just
an
extension
on,
what's
already
been
started
within
best
practices,
so
the
the
big
gap
that
we
have
right
now
from
a
from
a
customer
perspective
is
that
we're
we're
not
explaining
how
to
think
about
continuous
delivery
as
a
as
a
methodology
as
a
set
of
tools
for
solving
particular
problems.
H
H
We've
got
some
brilliant
projects
implementing
that,
but
we're
we're
failing
to
properly
communicate
how
this
needs
to
fit
in
an
organizational
level
and
we're
not
getting
the
message
across
to
the
decision
makers,
and
I
think
the
best
way
to
understand
that
problem
is
that
you
know
with
with
a
typical
open
source
project,
it's
usually
driven
by
developers
scratching
their
own
itches,
so
it's
people
solving
their
own
problems
and
as
a
byproduct,
creating
a
tool
that
they're
releasing
for
other
people
to
use,
but
within
continuous
delivery.
H
So
so
the
piece
of
work
that
we
need
to
be
focusing
on
next
is
just
clarifying
and
documenting
how
you
get
from
that
high
level
methodology
to
understanding
what
that
means
for
each
stakeholder
in
an
organization
and
to
to
put
it
bluntly.
This
is
the
what's
in
it
for
you
piece
which
needs
to
be
focused
on
each
stakeholder
in
an
organization
who
will
have
a
say
in
whether
or
not
that's
the
way
of
working.
That
organization
wants
to
move
ahead
with
so.
G
During
your
presentation
that
was
like,
there
was
just
like
a
key
point
that
you
were
talking
about
like
how
this
is
going
to
save
the
enterprise
company
time
and
money
and
proficiency,
and
I
think,
when
you're
talking
about
hitting
all
of
the
the
proper
like
pain
points.
Those
are
always
pain
points,
regardless
of
what
level
that
you're
at
right.
H
Yeah,
so
so
we
we
already
have
the
starting
point
for
for
that,
in
that
there's
a
section
in
best
practices
which
already
flags
a
different
classes
of
stakeholder
and
and
puts
a
very
high
level
requirement.
You
know
what
what
is
that
stakeholder
interested
in
so
so.
The
the
first
piece
of
work
to
be
done
is
to
make
sure
that
we've
captured
all
of
the
classes
of
customer
that
we
expect
to
be
involved
in
these
types
of
decisions,
so
who's
interested.
H
And
then
we
just
need
to
expand
on
each
of
those
roles
to
to
document
what
their
viewpoint
is
and
what
they're
actually
motivated
by
what?
What
are
the
drivers
for
their
piece
of
work?
What
what
are
the
challenges
that
they
face?
What
are
the
blockers
that
that
they're
encountering
and
then
an
arc?
H
H
H
H
As
you
move
through
the
process
of
implementing
continuous
delivery
as
a
methodology
and
at
some
point
we'll
get
down
to
the
level
of
detail
where
we're
talking
about
the
stuff
that
sits
within
the
mlops
roadmap,
within
cd
events
and
within
interoperability.
H
And
then
we
pull
all
all
of
that
content
in
and
show
how
it
fits
into
the
bigger
picture,
and
then
the
at
the
bottom
end
of
this
you've
then
got
the
opportunity
for
individual
project
teams
to
say:
okay.
Well,
this
is
how
our
project
aligns
to
that
architectural
view.
So
this
is
how
our
tool
maps
into
cd
events
and
where
we
fit
in
in
in
in
the
overall
architecture
of
of
this
piece.
You
know
we
we
provide
a
capability
within
this
space
within
the
bigger
problem.
E
You
know
there's
plenty
of
other
reference
architectures
out
there
for
this
stuff,
but
all
of
them
are
vendor
driven.
I
can't
think
of
a
single
one.
That's
independent
of
it,
I
is.
Is
there
another
like
where's,
my
it's
like
it's
like
it
seems
like
this
is
the
only
offering
that
that
or
inc
you
know
little
hint
of
one
coming
from
somebody
without
an
axe
to
grind.
C
And,
and
that's
one
of
the
things
that
we
have
to
make
sure
we
do,
is
we
don't
when
we
describe
the
reference
architecture,
we
don't
lock
in
or
name
particular
vendors
as.
C
We're
gonna-
and
I
think
we
can-
we
can
kind
of
do
that
if
we
have
the
approaches
from
two
ends.
Kind
of
like
what
tracy
suggested
in
her
email
is.
One
end
is
coming
from
the
vocabulary
side,
so
we
have
a
standardized
vocabulary
and
then
we
have
the
use
cases
coming
from
the
the
reference
architecture
side
and
we
bring
them
together
through
the
landscape
and
the
landscape
gets
flushed
out,
even
more
so
than
it
has
in
the
past
year.
C
E
H
Yes,
so
so
you're
absolutely
right.
This
is
part
of
the
driving
reason
for
why
we
wanted
to
do.
This
is
because,
right
now,
the
the
biggest
challenge
is
that
you
know
the
foundation
has
really
almost
saturated
its
currently
accessible
market,
because
you
know
we're
already
talking
to
all
the
people
who
already
understand
this
stuff.
H
So
so
we
have
to
do
more
to
connect
all
these
pieces
together,
so
that
someone
is
coming
into
this
relatively
new
is
getting
the
right
information
about
what
all
these
pictures
mean,
because
those
landscapes
are
great.
If
you
already
understand
all
the
conceptual
stuff,
but
they're
actually
just
really
confusing.
If,
if
you
don't
already
intimately
know
what
all
of
those
projects
do
and
how
they
relate
to
each.
G
H
Then
you're
you're
not
recommending
an
individual
tool,
you're
not
applying
any
bias,
but
you
are
allowing
people
to
consume
the
architecture
and
then
show
how
what
they're
doing
aligns
to
some
or
all
of
that
architecture,
and
I
think
that's
that's
the
approach
that
we
took
with
best
practices.
Originally,
you
know
we,
we
allow
individual
projects
to
publish
white
papers
showing
how
they're
aligning
to
best
practice
with
with
their
tooling,
and
I
think
that
is
the
that's
the
key
piece
of
information
that
we
actually
really
need
to
communicate.
H
Is
you
know,
we've
got
these
tools
and
we've
got
this
practice,
but
how
do
you
understand
how
all
this
fits
together?
So
we
need?
We
need
to
tell
that
story
in
a
way
that
makes
it
easy
for
people
to
pick
up
and
understand.
E
I'm
also
seeing
value
in
getting
other
companies
to
join.
This
is
where
you
fit
in
company.
This
is
where
you
can
come
in
and
provide
value
to
cdf,
so
I'm
not
only
looking
at
it
from
from
the
perspective
of
getting
newer
folks
expanding
the
tent,
which
I'm
a
huge
fan
of,
but
also
of
getting
more
organizations
in
and
explaining
them.
This
is
why
it's
valuable
valuable
to
you.
This
is
where
you
fit
come,
join
us!
E
H
So
the
I
think
the
the
big
first
step
is
going
to
be
getting
the
right
group
of
people
in
involved
on
on
documenting
these
these
pieces,
because
it's
it's
not
so
easy,
finding
those
sorts
of
product
management
skills
and
getting
those
people
involved
in
in
source
work.
H
So
hopefully
we
can
reach
out
to
all
the
members
and
ask
for
you
know,
nominations
or
volunteers
for
people
to
come
and
get
involved
in
in
this
bit
of
the
process
from
a
less
technical
and
more
product
focused
perspective.
C
And
I
think
one
of
the
other
things
when
we
go
and
do
this
effort,
that
we
need
to
make
sure
that
all
this
information
is
not
hidden
away
in
a
git
repo
and
actually
published
on
our
website
for
people
to
find
easy.
Because
if
it's
in
a
if
we
have
just
markdowns
and
doc,
you
know
and
repos
we're
not
going
to
be
able
to
to
get
the
information
out
to
the
folks
that
need
it
with
easily
yeah.
H
You're
absolutely
right,
yeah,
and
I
mean
the
assumption
is
that
we
will
we'll
we'll
extend
it
into
the
best
practices
site
so
that
it
becomes
a
another
top
level
section
under
best
practices.
And-
and
so
you
can
guess,
go
straight
from
the
methodology
into
the
architecture
from
a
a
basic
website.
D
So
I'm
sorry
to
interject:
just
did
we
decide
where
we're
going
to
do
this
work?
Should
we
do
it
under
best
practices?
Do
we
want
to
start
gathering
people
under
there
to
start
working
on
this.
A
I
think
it
would
be
the
best
because
all
six
need
topics
to
stay
active
and
here's
the
tvc.
I
think
that
we
should
try
to
offer
topics
to
seeks,
as
often
as
possible
and
encourage
people
to
participate
in
the
special
interest
groups,
and
until
you
see
if
the
topic
is
interesting
to
us,
we
should
also
go
there
and
ask
for
regular
updates
from
sick
representatives.
H
And
I
think
a
lot
of
this
work
is
just
going
to
be
integration
of
the
things
that
we
already
have
from
from
the
other
six.
So
my
expectation
is
that
you
know
we'll
continue
to
mature
things
within
cd
events
and
and
feed
that
information
in
into
the
reference
architecture.
H
This
is
this
is
about
making
sure
that
we're
doing
the
communication
work
to
make
all
of
this
value
that
we've
already
created
fully
available
to
to
a
an
audience
that
is
not
yet
comfortable
with
working
in
the
way
that
we've
been
working
at
the
engineering
level.
H
F
G
I
think
it's
sorry
put
my
screen
on.
I
I
think
before
we
talk
about
this
specifically,
perhaps
sort
of
a
teaser,
a
couple
of
blog
posts
might
be
good
like
where
you
say
like
where
it's
under
a
theme
right
like
so
how
does
an
enterprise
scale
up
and
how
does
the
cdf
address
those
issues?
And
then
you
can
kind
of
talk
to
some
of
the
projects
in
one
post
and
then
in
the
next
post.
G
You
can
really
just
kind
of
pose
the
question
okay,
so
we
have
all
of
these
projects
and
we
have
all
of
these
different
best
practices.
But
what
is
actually
needed
to
help
the
company
scale?
And
then
we
start
talking
about
what.
If
there
was
a
reference
architecture
that
really
helped
companies
look
at
their
project
from
point
a
to
point
b
to
point
c
and
used
all
the
tools
we
mentioned
in
blog
post,
one
and
blog
post
tool,
but
put
it
into
an
actionable
item
plan
for
people
to
actually
move
forward.
G
And
then
it
addresses
all
of
those
things
that
terry
already
outlined
the
pain
points
for
each
component
of
the
of
the
devops.
You
know
process
of
the
cd
process
and
things
like
that,
so
I
think
it's
easier
to
do
it
in
like
those
sort
of
bite-sized
pieces
and
surely
you
could
write
one
large
blog
post
and
then
just
chop
it
up
so
you're
not
doing
like
three
times
the
work
you're
just
doing
one
where
you
address
first
like
what
is
this?
G
D
G
I
think
that's
something
that
is
really
good,
because,
when
I
think
about
other
projects
and
sig
working
groups
and
needing
contributors
and
needing
to
get
eyes
on
those
things
as
well,
this
is
really
kind
of
a
nice
umbrella
way
to
highlight
them.
While
we
focus
on
something
that
you
know
isn't
exactly
what
they're
doing,
but
using
what
they're
doing
to
help
solve
the
issue.
D
G
And
just
like
just
saying
for
something
like
this,
we
could
definitely
use
linux
foundation
in
terms
of
getting
like
some
art
direction
and
actually
creating
a
campaign
using
the
what
is
his
name:
derek
right,
using
their
graphics,
team
and
and
creative
teams,
so
that
this
isn't
just
like
another
blog
post.
G
Yeah,
I
don't
know
if
a
white
paper,
but
maybe
if
you
like,
start
with
some
like
blog
posts
and
then
if
it
gets
to
the
point
where
we
have
enough
information,
then
yeah
put
it
into
a
white
paper
moving
forward,
but
I
think
gaining
the
traction
of
the
community
would
be
probably
the
first
step
and
then
getting
to
robert's
point
some
companies
to
fall
in
line
and
say
like
yes,
these
are
things
that
we're
looking
for
these
are
you
know,
issues
we're
trying
to
solve.
G
You
know,
then,
maybe
making
it
larger
scale
into
like
a
white
paper
or
moving
the
whole
idea
and
creating
that
sig
or
that
group.
That
project
can
be
more
of
a
reality,
but
I
think
it's
gonna
you've
got
the
framework
there,
like
the
architecture
framework.
You've
got
the
you
got
the
we
got
the
foundation
working
it's
now,
it's
time
to
like
build
it
up,
so
that
you
can
blast
it
out.
H
And
also,
I
think,
it's
important
to
to
understand
that
now
that
we've
got
the
best
practices
site
in
place,
we
can
start
to
deliver
this
stuff
iteratively
and
incrementally,
rather
than
having
to
spend
another
18
months
going
away
quietly
working
on
it
before
publishing.
This
is
information
that
we
can.
H
We
can
release
as
we
complete
it
and
build
up
a
picture
over
time,
so
we're
we're
we're
again
doing
this
in
a
customer-focused
way,
so
we're
doing
our
experimentation
in
the
real
world
with
genuine
users,
rather
than
just
doing
it
from
a
single
viewpoint
and
not
getting
any
feedback
on.
G
It-
and
I
think
that
too
also
leads
to
other
avenues
in
terms
of
obviously,
a
marketing
outreach,
chair
and
other
avenues
in
terms
of
like
press
and
getting
industry
involved,
because
the
way
that
we're
looking
at
things
is
completely
different
and
all
of
these
things
are
attractive.
So
getting
all
of
that
lined
out.
There's
multiple
storylines.
We
can
take
and
push
so
that
again,
we're
highlighting
all
of
the
projects,
we're
highlighting
the
best
practices
and
we're
highlighting
the
need
for
scaling
up
and
the
need
for
reference
architecture
in
general.
H
G
G
G
A
Okay,
so
we
have
nine
minutes
left.
I
suggest
that
we
quickly
gloss
through
the
two
remaining
topics
and
yep,
so
maybe
we
could
continue
the
reference
architecture
discussion
at
the
next
sig
meeting
or
maybe
dedicate
them
there
to
submit
into
that.
So
as
you
prefer,
okay,
so
there
is
an
item
about
community
guidelines.
Is
it
from
ufc.
F
Yeah
we
already
talked
about
talk
onboarding,
so
thanks
everyone
for
doing
that
documentary,
we
can
always
add
missing
stuff
there,
and
the
other
document
I
want
to
highlight
is
the
user
stories
simply
like
case
study
guidelines.
We
are
restarting
that
as
well
and
we
sent
the
guideline
for
community
review
as
pull
request,
which
is
linked
in
the
con
talk
agenda
document.
F
So
please
take
a
look
at
it
and
provide
your
comments
and
we
have
two
three
committee
members
lined
up
for
state
their
interest
to
contribute
case
studies,
so
we
will
slowly
start
getting
this
moving.
G
F
F
Oh
so
we
discussed
the
webinars
and
podcasts
and
we
will
probably
work
with
webinars.
First
and
lori
has
an
idea,
but
I'm
not
going
to
say
what
that
idea
is.
So
you
will
probably
hear
more
about
that
from
lori
when
the
time
is
right,
so
I'm
not
going
to
spoil
that.
Podcast
needs
to
wait
a
bit,
because
we
need
to
find
out
how
we
can
restart
that.
F
Just
to
add
to
that,
our
ambassador
group
is
actually
working
on
having
some
kind
of
timeline
for
podcasts,
so
that
could
be
an
option
as
well.
A
Yeah
well,
if
you
could
just
reuse
the
platform
so
that
you
saw
the
following
on
the
platform,
I
think
even.
D
A
Scope
changes:
it's
not
a
problem
at
all:
it's
better
to
have
a
live,
podcast,
a
new
podcast
and
another
one
which
is
not
active
anymore.
F
Yeah
spinnaker
summits
were
kicked
off
and
the
cfp
for
that
closes
tomorrow.
So
if
you
are
interested
to
propose
a
talk
for
spinnaker
summits,
please
do
that.
I
think
the
link
is
on
the
agenda
and
that
will
happen
before
cubecon
monday
and
sorry,
sunday
and
monday,
20,
3rd
and
24th
of
october
in
detroit
and
then
the
other
event.
This
second,
just
friday,
last
friday
we
got
in
a
heads-up
from
lf
events
team
saying
that
we
can
get
half
day
during
open
source
summit
europe.
We
quickly
started
a
google
phone
to
collect
proposals.
F
E
D
E
D
E
A
So
if
you
want
something
else,
drinks
contributor
summit
will
take
place
in
orlando
florida.
A
So
there
is
announcement
on
our
discourse
channel
with
all
the
details
and
okay,
if
you're
interested
check
it
out.
So
there
will
be
a
bunch
of
presentations,
usually
stories
a
lot
of
things
about
jake's
roadmap,
so
business
as
usual.
A
A
Okay,
then,
thanks
to
everyone
and
see
you
in
two
weeks,
so
it
will
be
august
16th,
I
guess
business
as
usual.
So
regarding
that
toodle
poll
about
the
meeting
time,
there
was
no
consensus
about
the
new
meeting
time
there.
So
I
think
that
we
just
keep
this
meeting
and
even
there
is
a
new
toc
chair.
They
are
welcome
to
run
the
poll
again,
but
for
now
somebody
has
strong
demand
to
move
the
meeting.
We
keep
it
as
this,
and
actually
the
participation
is
quite
good.