►
From YouTube: TOC Meeting - March 28, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
C
A
E
Pray,
hopefully
better
weather
than
we
have.
Although
it's
getting
it's
it's
starting.
D
A
E
A
B
So
we
have
here
today
Steve
from
the
vsmi,
so
we'll
discuss
about
it
in
in
a
moment
and
introduce
the
the
project,
but
first
I
wanted
to
cover
a
couple
of
items
for
for
the
agenda
before
we
get
there,
but
yeah
so
welcome.
Everyone
today
is
March.
The
28th
TSC
meeting
as
usual
feel
free
to
sign
yourself
in
share
a
TSC
member
or
project
representative
by
highlighting
your
name
or
you
can
add
your
name
into
the
other
art
in
this
list.
B
And
yeah,
so
just
a
couple
of
notes:
action
item
from
last
meeting
we
discussed
last
meeting
about
toc's
sponsor
for
special
interest
groups.
So
I
sent
an
message
to
the
mailing
list
about
that.
B
B
So
last
time
we
had
the
brilliant
presentation
by
Christy
and
David
about
tecton
and
it's
very
nice
to
see.
We
have
quite
a
few
presentation
scheduled
for
the
future
sessions,
so
thanks
Mark
for
scheduling
one
for
next
meeting,
April
the
11th
about
Jenkins.
So
looking
forward
to
that,
and
also
we
will
have
one
the
following
meeting
about
Spinnaker
project
update
from
Cameron
and
also
in
may.
We
have
a
session
scheduled
by
jithm
for
a
screwdriver.
So
that's
great
thanks.
Everyone
for
setting
up
this
presentations
later
in
the
year.
B
B
Yeah
next
up,
you
know
the
agenda
just
to
to
link
back
to
what
we
discussed
last
time
about
project
metrics
and
health
status
of
devstat
I,
don't
know
party.
If
you
wanted
to
discuss
about
this.
G
Yeah
exactly,
as
you
said,
Andrea
and
based
on
camera
light,
and
we
had
during
LFX
requirements
working
group
session
last
week.
I
had
a
chat
with
cncf
folks
and
convinced
them
that
we
need
this
information
available.
We
can't
create
like
V3
in
size,
V3
and
so
on,
and
they
thankfully
brought
up
all
the
CDF
projects
to
Dev
stats.
G
So
the
this
is
now
fully
working
except
affiliations.
So
the
tool
is
doing
some
processing
in
the
background
to
correctly
identify
the
affiliations
and
it
will
take
a
couple
of
days
once
the
calculations
are
update
but
except
affiliations
or
other
information
should
be
pretty
relevant
and
correct
because
it
fetches
information
from
GitHub
organizations.
G
As
I
note
on
the
slack
channel,
LFX
requirements
work
reflect
Channel,
I
used
what
we
know
about
the
GitHub
organizations
and
some
of
our
projects
like
Jenkins,
might
have
multiple
GitHub
organizations.
So
if
you
have
more
than
just
what
one
GitHub
organization
just
reach
out
to
me,
and
we
asked
ask
cncf
folks
link
to
those
additional
GitHub
organizations
to
include
in
the
statistics
and
that's
online,
any
feedback,
just
you
can
send
them
to
me.
B
Okay,
so
next
topic
is
vsmi
and
CDF
interpret
with
the
joint
working
group.
B
B
And
on
our
side
we
care
very
much
and
the
CDF
about
the
interoperability.
We
have
our
intervalability
special
interest
group
and
it
seems
it
looks
that
we
have
quite
a
good
overlap
in
terms
of
mission
of
things
that
we
won't
achieve.
So
we
had
an
initial
meeting
to
discuss
to
discuss
if
we
could
work
together
and
now
we
could
work
together
and
we
have
a
proposed
Charter
that
was
prepared,
so
we
invited
Steve
to
to
join
our
meeting
today
so
that
yeah.
B
We
could
present
this
this
idea
to
this
audience
as
well
and
see
who
would
be
interested
in
participating?
What
ideas
and
comments
we
can
have
about
it
so
Steve.
Would
you
like
to
do
some
introduction
present
yourself
and
the
work
of
vsmi.
E
Am
you
yeah
so
yeah?
So
thanks
for
that,
and
and
thanks
for
giving
giving
us
some
time
here,
I
think
that
there's
a
lot
in
common
between
the
value
stream
world
and
the
continuous
delivery
World.
E
We
in
the
value
stream
management
world
struggle
with
access
to
high
quality
data
in
order
to
visualize
and
measure
an
entire
value
stream,
and
that
I'm
sure
is
a
challenge.
That's
shared
inside
of
the
continuous
delivery
world.
Although
the
scope
is
much
broader
in
the
value
stream
world,
you
know
we're
working
all
the
way
from
product
portfolio
initiation
to
Value,
realization
for
customers,
and
so
that
involves
a
number
of
systems
that
are
not
code
native
are
not
digitally
native,
not.
E
So
this
means
that
you
know
folks
who
are
really
interested
in
that
end-to-end
flow
of
work,
resulting
in
customer
value,
delivery
really
struggling
to
connect
all
the
different
pieces
and
establish
a
a
reliable
or
trustworthy
through
line
of
work
items
all
the
way
from
initiation
to
Value
delivery.
E
But
we've
got
a
lot
of
similar,
let's
say
metrics
that
are
valuable
in
that
context.
We've
got
a
lot
of
similar
tooling
and
you
folks
have
been
at
this
for
quite
some
time,
so
there
should
be
a
great
opportunity
to
kind
of
Leverage
that
work
and
momentum
and
experience
in
tackling
this
challenge
of
extending
the
scope
and
maybe
looking
at
slightly
different
entities
and
use
cases
in
the
Valley
Stream
world.
E
But
we
see
this
as
a
yes
and
opportunity
with
a
lot
of
alignment
between
between
the
two
Scopes
and
and
use
cases.
So
the
proposed
Charter
kind
of
goes
into
I.
Don't
know
we
could
I
could
share
that
or
we
could
just
go
go
through
it.
I
don't
know
if
folks
are
interested
in
looking
at
a
slide
deck,
there's
very
little
in
terms
of
visualization.
E
Here,
aside
from
illustrating
kind
of
the
scope
that
we're
considering-
and
you
know
the
range
of
where
we
start
looking
at
data
to
where
we
stop
and
how
we
sort
of
connect
all
the
dots
together.
E
But
you
could
see
in
this
document
in
the
working
Charter
that
we're
primarily
focused
on
work
items.
As
the
you
know,
the
unit
of
measurement
and
the
performance
of
those
work
items
so
where
they
are
delayed,
where
they
pile
up
in
cues,
where
they're
blocked,
where
they're
returned
in
terms
of
rework
to
Prior
stages
in
a
value
stream
and
understanding.
Really.
What
is
the
value
streams
performance
for.
E
B
Just
a
comment
I
mean
you
mentioned
some
slides
I
mean
if
you
have
some
slides
that
you
would
like
to
present
Steve.
That's
that's
I
think
would
be
interesting.
For
me
at
least
I.
Don't
know
what
other
folks
thank.
H
You
for
me,
or
one
question
before
we
switch
to
the
slides.
So
if
you
talk
about
new
architecture
for
video
stream
management,
how
would
it
align
to
use
continuous
delivery
system
architecture
which
we
already
have
on
the
roadmap?
Would
it
be
two
separate
reference
architectures,
or
would
you
expect
them
to
be
integrated
into
the
single
one.
E
E
There
is
a
lot
of
commonality,
of
course,
but
I
think
separate.
Perhaps
separate
customers
perhaps
separate
use
cases
and
so
I
think,
depending
on
you
know,
I
think
of
everything,
as
customer
outcome
backwards
right.
So
customers
of
continuous
delivery,
reference
architecture
and
and
interoperability.
E
E
You
know
like
there's
the
the
scope
of
the
metrics
that
we
care
about
in
the
Valley
Stream
world
is,
you
know,
kind
of
starts
at
the
door
metrics,
but
with
different
goal
posts
and
then
goes
upstream
and
downstream,
and
ideally
deeper
into
quality
and
aspects
like
value
added
time,
which
is
would
be
like
a
distant
goal
for
something
like
this.
E
But
when
you
talk
about
value
stream,
metrics
I
think
we're
talking
about
extending
goal
posts,
but
also
looking
at
different
different
definitions
than
what
we've
seen
so
far
with
Dora
and
space
metrics
and
then
ideally
talking
about
realization.
So
what
is
the
customer
outcome
of
all
that
activity?
H
D
Yeah
so
so
my
mine
actually
was
I'm
fascinated
by
the
non-digitally
directly
available
kind
of
things
that
you're
interested
in.
So
that's,
that's
not
that's
unrelated
to
any
products
my
company
offers,
but
more
of
fascinated
by
the
The
Human
Side
of
what
you're,
what
you're
concerned
with
there
just
I'll,
be
listening
carefully
cool.
E
But
I
think
you
know
to
speak
directly
to
the
Human
Side
one
one
call
out
from.
E
The
the
charter
and
what
we
know
about
the
use
cases
and
the
and
the
the
customers
that
we'd
be
catering
to
primarily
interoperability,
is
the
challenge
of
the
implementer
right.
The
person,
the
person
who's
tasked
with
getting
the
system
connected
and
and
showing
that
the
data
is
telling
a
story
that
is
coherent
and
valuable
right.
E
That
right
now
is
is
really
challenging,
because
folks
have
very
messy
data.
As
you
know,
they
don't
track
things
like
work
profile
or
what
you
might
know
is
flow
distribution.
They
don't
separate
the
things
that
they're
doing
into
constructive
categories
that
allow
us
to
separate
each
of
these.
Each
of
these
things
and
and
measure
them
separately
and
and
look
at
things
like
distribution
to
see
what
kind
of
work
is
being
done
and
I
think
that's
different
from
something
like
CD
events.
Right
I
mean
we're.
E
We
care
a
little
bit
more
about
what
is
the
type
of
work,
that's
moving
through
the
system
and
the
friction.
That's
that
that
work
is
encountering
over
time.
The
delay
that's
that's
encountering,
so,
instead
of
firing
events,
you
know
this
happened
at
this
time
and
this
happened
at
a
time
period
in
the
future.
Beyond
that,
we
care
about
sort
of
like
that
plus.
What
is
the
the
shape
of
each
of
those
things?
That's
going
through
the
workflow
so
that
we
can
understand.
Okay,
well,
there's
a
lot
of
technical
debt
being
done.
E
That
should
have
an
impact
on
well,
let's
say:
there's
a
lot
of
technical
debt
being
addressed
that
should
have
an
impact
on
quality
that
we
can
see
in
the
future.
There's
a
lot
of
investment
in
features
that
could
have
a
negative
impact
on
technical
debt
as
a
byproduct,
but
it
should
be
showing
results
in
terms
of
customer
value.
E
So
that's
kind
of
the
vision
for
something
like
this,
which
I
think
is
a
level
almost
like
a
a
business
level
above
something
like
CD
events
like
what
is
the
the
actual
realized
outcome
of
all
the
things
that
are
happening
in
the
value
stream,
but
to
get
back
to
the
customer.
So
primarily,
the
challenge
is
the
folks
who
have
to
wire
all
that
up
and
either
they're
trying
to
pull
it
from
a
data.
Lake.
E
That's
extracted
data
from
all
these
systems
and
kind
of
put
it
in
one
place
or
ideally
directly
from
the
tooling
right
I
think
we
want
to
move
in
a
direction
where
all
of
these
tools
we
can
give
this
to
servicenow,
and
we
can
give
this
to
Salesforce.
We
can
give
this
to.
E
You
know
jira
line
and
maybe
via
plug-in
Maybe,
not
maybe
just
by
clear
guidance
say
if
you
structure
your
data
this
way
and
you
publish
to
this
web
hook,
it's
going
to
come
in
and
it's
going
to
be
clearly
attributable
through
the
whole
stream
right.
So
we're
not
very
opinionated
about
implementation
yet,
but
our
primary
customer
is
the
people
who
are
struggling
to
wire
all
these
systems
up
and
get
this
data
connected
and
visible.
And
then
you
know
the
the
I
guess
the
paying
customer
is
the
value
stream
leader.
E
The
folks
who
are
in,
like
maybe
the
the
BP
engineering
Who's
involved
in
kind
of
continuous
delivery
performance
and
the
vendors
themselves
struggle
with
this
idea
of
you
know
they
want
to
provide
value
and
if
they
don't
have
data
from
outside
of
their
ecosystem,
they
can't
really
tell
a
story
of
implementing
or
supporting
a
value
stream
analysis.
C
E
I,
don't
know
about
non-digital
data
I,
don't
think
we're
targeting
any
non-digital
data.
At
the
moment
the
scope
would
be
anything
that
is
capturing
workflow,
metrics
Within,
the
value
stream
we're
across
the
Valley
Stream.
E
So
you
know
we
talk
about
product
portfolio
planning,
that's
that
would
be
present
in
something
like
jira
line
it
could,
it
could
be,
you
know,
an
event,
that's
fired
from
slack.
That
says
you
know
we've
or
you
know
a
new
channel
in
slack.
That
represents
a
new
initiative.
E
E
But
it
is
early
and
we
don't
have
a
lot
of
strong
opinions.
Yet
that's
why
we're
kind
of
coming
to
you
folks.
First,
we
don't
want
to
reinvent
the
wheel
and
we
don't
want
to
to
duplicate
efforts,
or
you
know
obviously,
step
on
any
toes,
there's,
obviously
a
lot
of
a
lot
of
value
here
that
we
could
hopefully
augment.
C
And
who
do
you
foresee,
let's
say,
there's
something
coming
from
a
slack
that
you
want
to
capture?
Are
you
in
a
position
to
make
that
information
available
as
a
cloud
event.
E
That
entirely
depends
on
well
I
I.
Imagine
yes,
I
mean
slack.
Has
everything
from
like
native
app
implementations
to
webhook
integration,
so
I?
Imagine
you
could
fire
off
any
kind
of
event
that
you
wanted,
but
I
I
also
imagine
that
that
slack
is
in
the
scope
of
the
current
CD
workflow,
so
I'm
not
sure
that
that's
something
that
we
would
add.
But
if
it's
you
know
if
it's
a
missing
piece
that
seems
valuable,
then
we'll
we'll
we'll
certainly
investigate
it.
C
Yeah,
so
what
I'm
trying
to
get
at
is
if,
if
you're
going
to
be
doing
capturing
or
listening
for
this
data
to
be
updated,
like
you
said
like
interior
line,
it
would
be
great
if
that
was
publicized
using
an
event
versus
plug-ins
and
API
type
of
implementation,
because
that
way
with
the
CD
events
project,
we
could
be
able
to
categorize
those
and
make
them
available
to
everybody
in
the
pipeline.
E
Yeah
and
I
think
that
you
know
that's
a
perfectly
reasonable
goal
in
the
context
of
this
effort.
I,
don't
know
what
sort
of
things
we
would
we
would
start
with
and
and
capture,
but
you
know
that
is
one
of
the
things
that,
like
slack,
is
one
of
those
things
that
can
Bridge
gaps
in
a
lot
of
tooling.
That
doesn't
do
what
you
want
it
to
do.
Right
I
mean
you:
could
you
can
have
people
kind
of
fill
in
the
gaps
or
or
Bots
fill
in
the
gaps?
E
E
We
have
to
do
a
little
bit
of
a
deep
dive
into
CD
events
to
to
understand
how
much
of
that
seems
to
be
a
fit,
but
I
am
interested
in
hearing
from
your
perspective,
whether
you
think
this
is
an
extension
on
CD
events
if
it
fits
somewhere
else,
if
it's
a
a
level
above
I
I'm,
not
sure
and
I,
don't
have
strong
opinions
about
that.
I
So
as
someone
who's
worked
on
early
worked
on
the
events
team,
anything
that
we
do
in
the
future
in
terms
of
interoperability,
I
personally
think
it
should
be
done
through
events,
I
I
mean
we've
looked
at
plugins
for
a
long
time
and
we
know
the
challenges
of
them
and
we
have
to
get
to
a
better
place,
so
I
would
be
pushing
for
if
there's
a
working
if
you're
gonna,
if
we're
going
to
have
a
value
stream,
working
group
I
feel
like
that.
I
Working
group
should
be
under
the
CD
events
and
be
building
events
as
opposed
to
under
interoperability
and
and
I.
Think
from
a
Toc
perspective.
We
need
to
really
look
at
interoperability
and
CD
events
and
see
if
they're,
one
team,
because
they're.
I
Similar
thing,
one
is
doing
it
in
a
very
specific
way
and
building
vocabulary
around
the
events,
but
but
anyway,
if
we're
going
to
do
this,
if
we're
going
to
move
forward
with
it,
I'd
be
pushing
for
it
to
be
under
the
event
and
under
the
guidance
of
Andrea
and
Emil.
E
F
What's
the
best
way
to
get
involved
in
this
working
group.
E
Well,
we
have
so
it's
currently
running
through
Oasis
I,
don't
know
if
any
folks
in
CDF
are
also
Oasis
members,
I'm
sure
they're
I'm
sure
there
are
I
know
that
through
a
couple
of
vendors,
they
have
membership
on
other
technical
committees,
but
we're
a
technical
committee
under
Oasis
right
now.
So
we
have
a
regular
meeting.
E
Cadence
it'd
be
great
to
hear
from
folks
who
are
interested
in
attending
our
meetings
and
I
can
make
sure
that
you
you
get
invited
and
or
you
know,
that
materials
and
meeting
notes
and
video
or
whatever,
is
valuable
as
shared
back
and
forth
and
I'm
happy
to
come,
I'm
happy
to
come
here,
I'm
happy
to
be
it
go
between
or
whatever
is
helpful.
B
Yeah
I
think
what
we
were
considering
was
to
set
up
kind
of
a
new
joint
working
group,
so
we
could
have
like
meeting
dedicated
to
people
interested
in,
in
both
words
yeah.
The
only
risk
is
that,
of
course,
might
be
that
we
dispersed
kind
of
attendance
because
it's
an
extra
meeting
on
people's
calendar.
B
So,
but
what?
What
are
people
thoughts
about
this.
B
C
Would
initially
start
with
just
having
Steve
join
and
his
group
just
attend
a
couple
meetings
on
the
CD
events,
and
just
so
they
get
a
kind
of
a
feel
for
what's
going
on
there
and
then
down
the
road
make
a
decision
on
if
an
additional
meeting
is
needed.
J
Yeah
and
I
agree
as
well.
I
think
we
we
have
the
the
Sig
events
meetings
every
second
Monday.
Then
we
have.
We
have
dedicated
CD
events
meetings
where
we
actually
discussed
the
protocol
and
details
about
that.
But
maybe
this
is
more
for
the
the
Sig
itself,
but
at
this
stage
at
least
the
the
stethoscope
of,
where
is
our
event,
efforts
going
and
well
obviously
the
name.
Cd
events
doesn't
match
very
well,
maybe
with
the
broader
scope
of
the
obsm
at
the
moment.
J
But
that's
maybe
a
detailed
question,
but
I
think
we
would
have
a
room
in
our
agenda
on
the
signetings
for
for
sure
to
talk
about
the
the
BSM
aspects
of
the
end-to-end
pipeline
or
what
we
should
call
it
as
well,
of
course,
so
that
makes
sense
and
well
I
think
that's,
maybe
a
better
option,
yes
to
say
Chase
it
to
begin
with.
Instead
of
adding
another
meeting
in
our
in
our
calendars,
I'm,
not
exactly
sure
what
we
would
but
topics
we
should
like
start
on.
There.
I
mean
reference.
J
Architecture
is
not
something
we
have
been
discussing
a
lot
in
that
group,
yet
so
I'm
a
bit
hesitant
to
like
drive
that
work.
But,
of
course,
as
a
joint
effort
we
can.
We
can
help
out.
C
Well,
that's
why
I
was
saying
to
start
out
with
the
meet
and
greet
and
kind
of
get
a
feel
for
the
lay
of
the
land
and
then
kind
of
work
from
there.
G
C
B
B
Currently
runs,
is
it
it's
every
other
Monday,
it's
a
ml
I
believe
it's
4,
P.M,
UTC,
sorry,
4,
P.M,.
J
B
J
B
Like,
like,
you
said
ml,
so
in
the
City
events
meeting
we
discuss
specific
details
about
the
city
event
project
itself
in
terms
of
specification
sdks
and
things
like
that
quality
events.
Meeting
it's
meant
to
be
more
like
overarching
type
of
discussion
and
yeah
I
guess
it
would
be
interesting
really
to
start
discussing
from
my
perspective
would
be
interesting
to
start
discussing
some
yeah
from
an
architecture
point
of
view.
How
do
we
see
events
sitting
in
the
in
the
cicd
space?
B
E
K
B
Are
other
folks
from
from
the
TOC
here
today
would
be
that
are
interested
in
joining
in
this
conversation?.
A
B
A
F
Yeah
I
think
it's
the
same
time
just
just
next
week,
so
that
should
work
thanks.
J
Just
one
one
more
comment
from
either
the
next
meeting
is
planned
out
for
two
weeks
from
now,
but
Monday
that
is
a
holiday
in
Sweden,
so
I
won't
be
working
then.
So,
if
if
we
should
meet,
then
I
won't
be
there,
but
I
will
be
there
two
weeks
later,
but
I'm
not
sure.
If
that's
that's,
not
a
holiday
in
all
countries
Andrea
will
you
be
there
in
on
April
11th.
A
H
Well,
it's
basically
Easter
for
many
countries.
Switzerland
well
in
Switzerland
is
a
bit
complicated
because
in
my
Canton
I'm
supposed
to
work,
but
at
the
same
time
the
child
care
doesn't
work.
So
I
guess
the
same.
For
me.
B
All
right
so
I
mean
we
could
either
try
and
postpone
that
meeting
or
the
following
meeting.
That
would
be
on
April
the
24th.
J
F
J
B
B
B
E
G
B
A
B
A
B
So
that's
great,
so
we
we
have
a
plan
for
the
next
step.
Unless
we
on
the
charter,
we
had
some
some
questions.
B
E
Do
you
folks
have
any
current
joint
efforts
like
this?
We
could
use
as
a
reference.
A
B
B
G
G
Yeah
cd1
start
as
a
work
stream
on
this
special
interest.
Group
interoperability,
so
maybe
like
a
similar
approach,
could
be
taken
for
this
as
well
within
City
events
like
if
it
makes
sense.
A
G
B
E
No
I
think
the
24th
gives
us
enough
time
to
do
all
the
exploration
we
need
on
on
RN
to
bring.
You
know,
I
think
that
there's
some
value
from
the
other
resources
we're
considering
leveraging
and
so
I'm
still
synthesizing,
that
I'm
going
to
bring
all
that
together
and
present
everything
on
the
24th.
That
means
we
should
be
well
informed
and
ready
to
make
some
good
decisions
about
moving
forward.
E
I've
added
myself
to
the
slack
too
so
I'll
be
around
and
I'll
catch
up
with
everything
that's
been
going
on.
I
am
curious
about
I
mean
right
now.
The
proposed
Charter
is
in
the
context
of
interoperability.
So
I
was
wondering
if
it's
valuable
to
also
add
the
same
context
from
CD
events
as
I'm,
not
sure
it
doesn't
sound
like
it's
clear
whether
or
not
we
should
focus
entirely
on
events
and
not
interoperability,
or
if
there's
you
know,
there's
a
path
leveraging
both
or
something
else.
K
I
would
agree
with
Tracy
what
she
said
earlier
that
it
seems
like
this
is
a
better
fit
for
CD
events.
At
least
initially
I
mean
unless
we
have
some
other
type
of
implementation
that
we
think
of
it
just
seems
like
that's
the
best
scope
for
this
at
the
moment,
so
I
would
I
would
say
yes,
City
events
for
sure.
F
I
I
did
leave
a
question
in
chat,
asking
the
difference
between
the
different
types
of
CD
events.
Meetings
I
see
three
different
meetings
on
the
on
the
calendar,
all
relating
to
CD
events,
just
curious,
which
one
is
the
one
to
to
join
for
the
for
this.
B
Yes,
thanks
glamor,
that's
a
very
good
question
so
and
I
think
we're
aware
it's
maybe
a
bit
confusing
and
so
on
the
on
every
other
Monday
yeah
pre,
PM
UTC,
which
is
yeah
this
afternoon.
For
me,
we
have
a
meeting
called
CDF
seek
events,
and
this
is
the
one
that
we
are
targeting
for
for
this
topic,
the
other
two
meetings
you
see
there
are
City
events
working
group,
so
there's
a
specific
to
the
City
events
project
as
opposed
to
the
Sig
events
group
and
those
two
meetings.
B
B
The
one
that
we
are
targeting
for
this
is
the
Monday
3
P.M
UDC,
so
the
one
I
put
a
link
in
the
in
the
notes.
Awesome
thank.
A
B
Pay
connection
to
do
do
ads
on
the
current
Charter.
The
CDF
seek
events
as
well.
J
E
I've
got
the
I've
got
the
event
for
the
24th
in
my
calendar,
but
I'm
happy
to
be
invited.
I
can
send
my
email
address
here.
J
J
E
B
B
Joining
us
today,
Steve.
B
I
lost
my
okay.
Sorry
I
lost
my
part
of
my
zoom
window.
Okay,
we
we
have
a
few
minutes
left.
We
can
use
them
to
go
through
the
roadmap.
That's
okay
for
books!.
B
Unless
there
is
anything
else,
more
pressing
that
people
would
like
to
to
discuss
in
the
last
few
minutes,.
I
I'd
just
like
to
give
a
update
on
our
LFX
working
group,
we
did
have
our
first
meeting.
I
We
have
a
there's
a
get
repo
out
there
for
discussion,
so
if
anybody
would
like
to
add
issues
or
complaints
or
things
that
they
love
about
LFX,
that
we
would
like
to
see
the
Linux
Foundation
keep
in
the
product.
That
would
be
a
good
place
to
express
it.
So
we
will
meet
again
next
month.
I
I
think
we
have
another
two
or
three
weeks
and
the
goal
is
to
get
as
many
of
those
kind
of
discussion
points
together
and
then
we
will
work
on
a
shared
dock
that
we
can
pass
off
to
the
Linux
Foundation.
That
says
these
are
the
things
we
think
could
make
this
product
better.
These
are
the
things
we
love
and
this
is
what
it's
missing.
I
I
B
A
A
I
I
I
think
Steve
has
a
few
that
he
has
to
add
I.
Think
Mark
has
a
few
Mark's
favorites.
We
have
to
have
a
discussion
on
Mark's
favorites.
I
So
we'll
be
getting
that
together
in
the
next
six
weeks-
and
this
is
a
working
group,
meaning
it's
not
intended
to
last
forever.
Hopefully,
it'll
be
a
disbanded
working
group
by
no
later
than
June.
B
Sorry
go
ahead,
Steve.
E
I
was
just
wondering
so
I
just
checked
my
email,
I
applied
for
CDF
or
Linux
Foundation
membership
or
CD
Foundation
membership.
I
can't
remember,
I,
always
CDF
membership
in
February
and
I
haven't
had
a
response.
So
I
don't
know
if
I
should.
Oh,
if
anybody
on.
G
That
I
actually
thanked
an
email
just
today,
Steve
two
hours
ago,
no.
A
G
Yeah
I
think
you
you
applied
for
both
because
you
need
to
be
a
left
member
in
order
to
join
the
CDF
as
a
member
so
yeah,
we
can
follow
it
up
on
the
mail.
We
need
some
documentation
from
your
site.
Oh
I,.
A
B
All
right,
we
only
have
three
minutes
left,
so
maybe
we
can
close
the
meeting
short
for
three
minutes
unless
anyone
has
any
other
remarks.
B
Okay.
Well,
thanks
a
lot
for
the
great
discussion
good
to
see
everyone
today
and
have
a
great
rest
of
your
day.