►
From YouTube: CDF TOC Meeting, Feb 28, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
So
we
have
a
few
things
on
the
agenda
for
today,
but
as
you
wanted
to
start
with
action
item
from
last
meeting,
so
we
have
some
discussion
list
a
couple
of
weeks
ago
about
TSC,
chair,
Deputy,
chair
and
I.
Guess
we
can
cooperate
that
in
a
minute
seek
security.
Archival
was
done
so
thanks
a
lot
about
that
and
there's
still
work
in
progress
for
the
Chinese,
Sikh,
Chinese
language
or
Kabul.
A
I
have
to
do
that.
We
had
a
question
about
presentation
to
be
added
to
the
calendar.
A
I
checked
that
it's
possible
to
read
extra
text
to
individual
events,
so
I
started
adding
Christie's
presentation
about
diagram
for
March
the
14th
and
we'll
continue
to
do
so
for
upcoming
presentation.
As
soon
as
we
got
the
exact
date
and
I'm
still
waiting
for
shipwright
project
representative
to
be
chosen
by
the
project.
So
no
updates
on
that
for
the
next
topic
fatty.
You
would
like
to
introduce.
B
That,
yes
yeah,
as
you
all
know,
we
have
the
us.
We
have
Awards
process
kit
a
few
weeks
ago
and
we
have
been
getting
some
nominations
and
this
Friday
is
the
last
day
for
nominations
and
we
can
go
and
donate
some
other
community
members
who
have
been
doing
good
job
for
the
CDF.
So
you
have
a
few
more
days
nominate
someone,
and
if
you
click
that
link,
you
will
get
all
the
issues
Roxanne
created
on
GitHub
Foundation
report.
So
please
go
and
nominate.
B
In
addition
to
that,
we
also
have
a
fifth
award
category
and
user
organization.
I
should
all
have
received
a
Google
form
to
nominate
an
unusual
organization.
You
think
who
is
doing
a
good
job
within
CDF
or
within
contractor
ecosystem.
So
we
very
much
look
forward
to
your
nominations
there
and
once
we
are
done
with
nomination
period
Then,
the
voting
for
all
these
hours
will
be
done
and
you
will
be
asked
to
vote
for
all
the
award
categories.
B
Five
of
them,
so
please
check
your
mailboxes
with
their
an
email
from
Michelle
asking
for
any
user
company
nominations,
nominates
company
and
user
Organization
for
that
award.
So,
in
addition
to
that,
yeah.
B
The
voting
will
happen
via
Google
form,
so
you'll
receive
a
link
to
Google
phone
with
the
nominated
people
or
organizations,
and
then
you'll
go
and
vote
on
them.
Okay,
so
you
will
get
single
Google
form
with
all
the
nominees
for
five
PDF
Awards
got.
B
And
no
problem
and
based
on
the
feedback,
actually
we
received
from
the
community
based
on
last
year's
Awards
process.
We
made
some
updates
to
the
program
and
we
published
the
guidelines
they
weren't
available
there.
So
one
of
the
big
changes
we
made
to
the
awards
process
was
to
make
sure
that
more
people
could
be
recognized
for
their
airports
effort.
So
what
we
did.
There
is
a
person
if
a
person
won
an
award
on
certain
category
that
person
can't
be
nominated
again
for
that
category,
because
there
may
be
other
people
who
may
be
doing
good
job.
B
So
that
is
one
of
the
changes
that
well
done
and
the
other
changes
the
next
bullet
point.
We
also
want
to
make
sure
that
we
have
some
community
members
monitoring
to
nomination
and
elect
voting
process
in
case.
If
someone
raised
a
concern
about
a
horse
process
and
thanks
Tracy
for
volunteering
to
serve
as
an
award
officer
and
only
Hoffman
also
volunteered
to
serve
so.
B
C
B
C
It
be
possible,
maybe
at
cdcon,
to
allow
the
projects
to
have.
You
know
announcements
as
well
at
cdcon
for
the
individual
projects
or
is.
C
B
Thanks
a
lot
for
that
students,
I
I,
forgotten
to
mention
so
last
year,
all
the
project
servers
were
you
know
the
nominations
were
done
under
CDF.
That
is
the
other
change
we
have
done
so
the
projects
award
process
is
done
by
the
project.
Stem
cells,
like
nominations
and
winners,
and
the
winners
for
the
project.
Awards
will
also
be
announced
at
cdcon
like
the
last
years.
So
please
make
sure
that
you
don't
disclose
the
winners
within
your
projects.
B
A
Yeah,
thank
you,
fatigue,
I
think.
The
next
topic
is
also.
B
Yours,
yes,
so
thanks
to
Tracy
I
think
we
took
Tracy's
update
from
GitHub
issue
as
is
and
shared
it
with
legal
I
think
it
is
the
same
wording
as
the
one
you
create
Tracy
and
this
says
pass
the
board
now.
So
once
the
CDF
board
updates
or
approves
the
updates
to
the
Charter,
then
the
deputy
chair
will
be
in
place
like
in
the
charter
and
then
the
chiosi
can
decide
the
way
forward
about
that.
B
A
Okay,
if
there
are
no
questions
on
these,
let's
move
to
the
next
topic.
A
Okay,
just
some
updates
from
the
last
latest
governing
board
meeting
I
presented
the
work
that
we're
doing
here
on
the
doc
and
one
question
that
came
up
was:
how
can
we
assess
the
the
help
or
CDF
projects?
And
how
do
we
do
that
and
a
couple
of
ideas
were
discussed
and
specifically
project
Community
metrics?
A
That
means
like
number
of
contributors
over
time
contributions
and
so
forth,
but
those
kind
of
metrics
we
have
devsta
today,
but
it's
only
used
by
a
few
of
the
CDF
projects,
and
so
the
tool
that
can
be
used
for
all
project
would
be
LFX,
but
the
data
is
private
for
the
direct
protection
regulation
today
and
we
discussed
with
Michelle
I
think
that
it
will
be
good
to
build
some
anonymized
reports.
A
C
Like
the
LFX
insights
and
some
of
the
tools
were
going
away
on,
the
the
Linux
Foundation
side
is:
is
that
true,
or
is
that
are?
Are
those
still
staying
around.
E
F
B
What
Robert
said
so
dive
stats,
which
was
developed
by
cncf,
that
is
going
away
that
will
be
retired
and
LFX
has
its
own
insized
version
2
and
as
it
overstays
it
effects
will
be
around
well
I.
Think
some
people
within
the
links
Foundation
they
are
working
on
bringing
additional
dashboards,
live
I
believe
so
yeah.
G
So
I
I
have
a
suggestion
for
us.
Then,
if
Halifax
is
sticking
around
I
think
we,
it
might
be
wise
for
us
to
pull
together
some
of
the
kind
of
the
leaders
on
some
of
the
open
source
projects
and
get
a
list
of
of
issues
and
requirements
that
we'd
like
to
see
improved
on.
So,
for
example,
we
I
don't
know
if
we
may
be
alone
in
this.
G
There
have
been
two
areas
where,
where
LFX
did
not
serve
us
well,
one
of
the
first
ones
is
we
have
we
gamify
our
like
Ambassador
programs
and
our
or
what
we
call
our
Champions.
So
every
six
months
we
have
to
go
through
and
do
this
massive
manual
count
of
how
many
times
people
showed
up
for
a
meeting
how
many
times
how
many
pull
requests
they
did
but
blogs
they
submitted
to
determine
their
involvement.
G
Secondly,
we
had
issues
with,
as
all
of
you
know,
because
it
was
discussed
here,
getting
a
bounty
program
set
up,
we
got
a
grant
and
we
had
no
way
of
paying
our
our
committers
through
LFX
tools.
Even
though
we
have
LFX
has
a
crowdfunding.
We
they
there
is
nothing
that
they
could
do
for
us.
G
We
had
to
pull
all
the
money
out
of
it
and
switch
it
over
to
GitHub
to
make
it
work,
which
was
kind
of
a
pain
in
the
butt
to
be
quite
honest
and
I'm,
guessing
that
other
open
source
communities
have
had
other
areas
where
LFX
tools
could
have
better
served
them.
So
it
would
be
I
think
you
know,
even
if
we
did
two
created
a
LFX
working
group
and
invited
some
of
the
open
source
leaders
or
anybody
on
the
open
source
teams
to
start
looking
at
LFX.
G
E
No
doubt
Tracy
that
gamification,
the
the
we
call
it
our
liquid-based
Legends.
It's
it's
huge
for
open
source
people
love
to
be
a
part
of
that
they
they
love
working,
moving
up
that
ladder
and
you
know
getting
swag
and
those
sorts
of
things.
It
absolutely
needs
to
be
part
of
LFX,
I,
I
I,
that's
a
no-brainer
and
and
just
the
fact
that
you're
not
able
to
manage
grants
within
LFX.
G
G
G
E
G
And
even
two
mistakes,
even
from
the
CDF
Ambassador
perspective,
you
know
that
we
have
an
ambassador
program.
I
think
garima
did
a
good
job
of
trying
to
identify
people
who
should
be
a
part
of
the
ambassador
program
and.
H
G
E
Ambassador
not
influencer,
we're
not
like
yeah
for
sure
I
mean
like
these
are
just
standard.
How
in
2023,
open
source
projects
are
managed
and,
and
it's
I
think
Linux
Foundation
has
an
opportunity
to
be
a
real
leader
here
and,
and
it
just
pains
me
that,
there's
in
a
commercial
stuff
out
there
that
that's
nibbling
around
us
like
we
should
be
the
leader
on
this
I.
C
C
I
I
So
so
I
guess
I
need
to
be
aware,
as
that
thing
evolves,
because
we're
using
Dev
stats
in
the
Jenkins
project
quite
heavily
to
to
decide
how
are
we
doing
for
engagement
and
how
is
the
community
health-wise
and
and
we
we
saw
very
dangerous
signs
in
December
and
have
taken
actions
in
January
now
trying
to
trying
to
correct
that
and
have
seen
positive
results
again
in
the
dev
stats
metric.
So
so
I'm
I'm
very
interested
in
that
I.
Pr
I
solemnly
promise
to
attend
more
frequently
to
be
sure
that
I'm
involved
yeah.
B
I
can
maybe
share
some
light
on
that.
Actually,
if
you
look
at
this,
that's
currently
only
four
of
our
projects
are
listed
there.
The
founding
four
is
exciting:
Jenkins
technon,
Jenkins,
X
and
spinker,
and
when
we
noticed
this
around
September
October
last
year,
we
went
and
attempt
to
include
our
other
projects.
We
now
have
nine
projects
and
response
we
got
was
their
stats
will
be
phased
out,
retired,
put
your
efforts
on
LFX
in
size,
V2
and
that's
what
we
did
actually
all
our
projects.
All
nine
projects
are
currently
on
LFX
inside
Suite,
2.
B
I
can't
see
them,
but
the
problem,
you
can't
see
them.
So
that's
that's
the
issue
that
was
brought
up
during
the
board
meeting
last
week
and
we
are
currently
collecting
what
kind
of
information
we
should
be.
You
know
making
available
to
our
committees,
which
is
like
without
invading
privacy
and
so
on.
So
we
are
looking
to.
B
You
know
make
sure
that,
even
if
there's
goals,
we
should
have
something
as
an
alternative
before
that
happens
before
we
lose
their
stuff,
and
that
is
how
this
conversation
started
and
maybe
once
that
document
is
viewed
by
the
board,
we
are
working
on
a
document
to
collect
type
of
the
metrics
we
want
to
collect.
I
B
Others
exactly
and
just
to
highlight
that
inside
Suite
tool
has
subset
of
what
is
available
on
their
stats.
So
not
everything
is
on
insights,
LFX,
but
yeah.
Based
on
the
conversations
we
are
having
I'm
sure
we
can
bring
this
topic
back
to
LFX
development
organization
within
Williams
Law,
as
Tracy
mentioned
like
apart
from
metrics.
What
else
is
missing
like
security
and
FX
security
is
not
good
enough.
Perhaps
we
should
collect
that
type
of
feedback
as
well
and
bring
them
to
LFX.
I
Great.
Thank
you
thanks
fatty,
that
that
excuse
my
backtracking
back
to
the
meeting
agenda.
A
No
I
think
that
was
sorry
Tracy.
You
were
going
to.
G
So
I,
you
know
I'm
not
sure
if
we,
if
there's
an
absent
item,
but
I
would
like
to
motion
that
week
that
we
create
and
I
don't
know
how
we
do
this
a
working
group
to
review
requirements
for
the
for
LFX.
G
A
A
Suggest
the
same
so
I
mean
since
you,
Tracy
and
Robert
will
brought
this
out
quite
enthusiastically.
Would
you
like
to
oh.
F
E
I
G
E
J
G
Do
it
do
we
have
a
full?
Do
we
have
Quorum
today.
A
C
F
A
To
the
proposal,
sorry,
the
proposal
is
to
form
a
working
group
to
discuss
about
LFX
tools
and
Community
metrics.
Is
that
right,
Tracy.
G
That
should
work
I
I
would
almost
add
to
that
motion
to
review
require
future
requirements
of
LFX
tools.
J
I
do
see
that
From
skoda
perspective
I'm,
able
to
log
in
view
certain
basic
metrics,
but
if
I
want
to
dig
anything
deeper
into
LFX,
it
says
you
don't
have
permission,
ask
for
where
I
admin,
which
is
expose
that
data.
Something
like
that.
So
yeah
a
working
group
look
into
what
we
can
see
and
what
are
the
things
we
are
supposed
to
see.
That
will
be
good.
A
Yeah,
only
in
favor
all
right
great,
so
we're
going
to
form
the
working
group
I
think
we
have
guidelines
for
working
group
on
the
TOC
website.
So
it
would
be
good
to
just
maybe
create
a
readme
with
participants
and
the
mission
of
the
working
group
and.
F
G
If
any
kind
of
like
or
a
process
that
we're
supposed
to
go
through
for
a
proper
working
group
like
do,
we
have
to
create
a
charter,
do
we
have
to
do
anything
outside
of
just
saying
we
want
to
start
a
working
group.
B
I
think
working
groups
like
based
on
the
things
I
remember
from
years
ago:
it's
they
are
pretty
similar
to
six,
so
they
need
to
be
proposed
on
GitHub
and
I
put
by
the
TOC.
Now
you
voted
when
it's
already
Maybe
a
charter
could
be
created
and
the
meeting
list
could
be
linked
there,
stating
that
this
working
group
was
discussed
and
approaching
to
see
meeting
and
it
gets
created
that
way.
B
C
E
G
And
if
you,
if
you
get
it,
create
it
out
there
and
give
me
access
to
it,
I'll
be
happy
to
add
a
charter.
A
So
there
is
a
mailing
list,
information
I
guess
we
should
be
able
to
set
the
creative
wglfx
requirement
mailing
list-
I,
don't
know
if
I
have
admin
tool
for
that.
Is
that
something
you
could
do
as
well?
Party
yeah.
F
A
Yeah
so
I
think
this
was
very
useful.
So
thanks
for
that,
so
going
back
to
did
you
be
meeting?
The
other
aspect
that
was
mentioned
to
you
know,
learn
more
about
the
help
of
our
project
was
in
terms
of
adoption,
so
project
user
usage,
metrics,
and
so
what
we
found
out
is
that
there
is
a
policy
already
from
the
Linux
Foundation
about
Telemetry
data,
collectioning
usage
policy
and,
if
I
understand
correctly
the
general,
so
the
the
default
is
that
should
not
collect
the
telemetry.
F
A
But
yeah
I'm
not
sure
any
I
would
like
to
maybe
dig
a
bit
deeper
in
this
I'm,
not
sure
whether
this
is
referring
only
to
like
installation
of
software.
All
this
is
referred
also
to
other
Telemetry
data
like
downloads,
and
things
like
that.
I
Yeah,
the
Jenkins
project
will
need
to
review
that
because
we
certainly
do
collect
Telemetry
data
about
installed
versions,
and
we
use
that
Telemetry
data
to
guide
our
choices
for
technical
implementations,
so
that
I
assume
that
we
have.
We
have
at
least
some
coverage
that
we've
been
collecting
that
data
for
10
plus
years
and
it's
intentionally
anonymized
it's
intentionally
safeguarded.
It's
never
to
you,
know
no,
no
exposure
of
users
and
and
a
very
careful
policy
about
what
we
allow
ourselves
to
do.
I
Additional
Telemetry
on
is
that
one
Andrea
that
I
need
to
worry
about,
assuring
we're
compliant
or
is
it
safe
for
me
for
the
moment
to
not
worry
about
it
and
put
it
on
my
backlist.
A
B
Yeah,
maybe
I
can
give
some
context
so
Mark,
like
some
other
project
Representatives,
they
came
asked
us
like
okay,
we
want
to
know
how
our
users
are
using
our
project,
which
compounds
they
are
using,
how
many
times
they
are
you
not
I
download.
It
is
downloaded,
which
versions
like
similar
to
how
we
have
been
doing
and
I
when
I
Googled
things
and
I
found
Jenkins,
Telemetry
I
think
it's
opt-in.
B
If
I'm
not
missing,
you
have
to
explicitly
check
and
make
sure
that
the
data
is
shared
So
based
on
that
feedback,
I
told
them
like
Jenkins
has
been
doing
this,
but
we
need
to
check
this
with
the
legal
as
part
of
this
board
discussion.
One
part
of
it
is
like
Community
Health
and
growth,
the
metrics
and
the
other
part
is
telemetry.
Well.
B
If
we,
if
you
can
help
me
with
what
kind
of
data
you
are
collecting
like
Chinese
Community,
is
collecting,
then
we
can
make
that
part
of
the
document
we
are
currently
working
on
and
then
we
can
ask
legal
like
this
is
one
our
projects
want
to
collect
by
the
way.
Jenkins
has
been
doing
this
for
quite
some
time.
Like
since
it's
been
around,
and
then
we
come
back
to
you
saying,
okay,
this
is
all
okay
or
you
need
to
fix
this,
and
so
you
get
this
clarified
as
well.
I
Great
so
for
precision,
Jenkins
Telemetry
is
actually
not
opt-in.
We
actively
connect
collect
Telemetry
unless
they
have
opted.
If
I
recall
correctly,
it's
opt
out
so
so
we
gather
their
data
in
terms
of
which
plug-in
version
they're,
they're
they're
installing
and
which
Jenkins
controller
version
they're
installing
and
of
course,
we
track
the
download
Counts
from
our
download
sites
as
well
so
but
happy
to
provide
those
kind
of
things.
We
thought
that
you
and
I
can
just
chat
separately
or
do
a
separate
conversation
about
it.
Great
yeah,
yeah.
B
So
please
look
at
the
police
attack,
because
that
policy
is
kind
of
yeah,
pretty
limiting
yeah
everyone
like
all
the
project
Representatives,
if
you
have
ideas
or
feedback
from
the
community
like
you
want
to
collect
this
type
of
information,
read
that
policy
and
the
conversation
is
already
happening
just
take
part
in
the
conversation
incoming
meetings.
A
Thank
you
anything
else
from
the
GB
meeting.
I
may
have
missed
that.
You
think
you
should
be
wrote
here,
30
by
any
chance.
B
I
think
this
and
the
other
thing
project
CDF
calls
for
2003,
so
we
should
have
them
pretty
soon.
We
have
been
discussing
those
things
and
they
are
pretty
similar
to
last
year's
course,
but
we
had
some
additions
to
the
goals
based
on
the
community.
B
G
A
Thanks
fatty
sorry,
but
you
understand
all
right
any
more
questions
about
project
health
or
other
C,
GP
updates.
A
Okay,
looking
forward
to
the
new
working
group,
thanks
for
that
again
so
next
topic
I
have
on
the
agenda
is
the
okr.
A
So
unfortunately,
Oleg
is
not
here
today,
but
I
can
present
what
we
did
the
work
we
met
with
Oleg
and
started,
creating
a
document
with
a
list
of
objectives
that
we
think
could
be
interesting.
Okrs
for
for
the
TOC,
so
I
wanted
to
just
go
through
this,
at
least
at
a
high
level.
Today
gather
some
feedback
and
also
ask
a
books
on
the
on
the
TOC.
Please
do
to
comment
offline.
A
Just
as
an
introduction,
based
on
what
we
discussed
previously,
so
we
want
to
adopt
okrs
to
because
the
CDF
adopts
okr
as
well.
So
we
want
to
to
double
cars
for
the
doc
and
match
with
the
work
that
is
done
at
CDF
level.
A
So
we
identified
like
five
main
areas
with
Oleg
and
we
also
had
some
extra
ideas.
So
the
objective
number
one
would
be
project
engagement
with
a
CDF
technical.
F
A
A
Okay,
so
the
second
objective,
this
project,
interoperability-
and
this
is
direct
their
directory
connected
to
one
of
the
objectives
that
you
see,
and
so
here
results
one
to
have
a
project
vocabulary
published
for
all
the
CDF
hosted
project
and
the
second
one
would
be
to
have
two
tools
to
adopt
CD
events
and
to
have
two
blog
posts
about
interoperability
through
CD
events,
and
also,
we
included
here
to
have
a
reference
architecture
presented
to
the
DLC
twice
a
year
and
gains
feedback
from
the
TOC
that
we
have
two
presentation
on
the
progress
of
the
reference
architecture
to
the
EOC.
A
Third,
and
we
thought
a
important
objective
would
be
the
project
pipeline
and
the
key
result.
Num
number
one
here
is
to
maintain
a
pipeline
at
least
two
project
at
any
point
in
time
through
the
year
and
as
well
as
as
key
results.
Number
two
to
add
two
new
project
into
the
CDF
in
2023
key
results:
free
to
establish
a
clear
roadmap
for
graduation
for
two
of
the
CDF
projects
which
are
currently
incubating,
and,
finally,
the
work
that
we
already
started
about.
Updating
the
project
member
benefits
webpage
and
to
create
a
PDF.
A
So
number
four
in
terms
of
folk
leadership:
they
wanted
to
bring
back
possibly
update
from
the
seek
working
group
towards
the
TOC,
and
this
is
something
that
we
started
already
to
have
a
yearly
published
report
of
secret
activities
and
results.
So
the
idea
here
is
to
to
take
all
the
updates
from
the
different
working
groups
and
sakes
and
create
a
Consolidated
View
at
the
end
of
the
year,
so
that
we
have
a
good
view
at
the
end
of
the
year.
What
we
achieved
there.
A
And
key
result:
three:
this
is
going
back
and
forth.
These
are
going
back
to
the
presentation
from
last
week
from
the
open
ssf
about
diagrams
and
visualizing
the
the
foundation.
So
we
want
to
have
one
hierarchical
diagram
with
the
CDF
community
structure
and
one
diagram
of
the
different
groups
and
project
Associated
or
linked
within
kind
of
overlaid
on
a
reference
architecture,
so
that
we
can
understand
which
project
and
which
group
is
working
in
which
area
and
finally,
objective
5
Toc
sustainability
key
results,
one
at
four
new
Toc
contributors.
A
So
there
is
this
concept
of
Toc
contributors
and
to
have
more
joining
us
for
more
key
results
to
execute
elections
according.
A
And
key
results
free,
reduce
the
leave
of
absence
policy.
A
And
so
these
are
the
the
five
I.
Don't
know
it's,
maybe
a
lot
of
them
quite
a
few
of
them.
We
are
already
working
on
them,
so
it
felt
like
something
that
we
could
have,
even
if
it's
aspirational
as
a
list
of
objective
work
for
this
group
for
this
year.
A
Other
ideas,
things
that
we
could
work
on
and
we
could
include
in
the
okr
things
like
technical
initiatives,
so
I
have
more
technical
initiatives,
started
driven
by
the
TOC,
perhaps
anonymity,
initiatives
with
other
groups
and
Foundations.
So
we
already
have
something
going
on
with
the
psmi,
the
value
stream
management
and
another
area.
A
We
could
consider
working
on
cicd,
cost
efficiency
and-
and
finally,
some
questions
we
had
was
about
evaluation
of
these
okrs,
whether
we
should
do
quarterly
evaluation
and
keep
track
of
the
progress
on
these
in
terms
of
technical
implementation
of
these
okrs.
Currently,
it's
a
markdown
price,
so
we
could
just
add
this
markdown
in
a
repo
or
we
could
do
something
more
fancy.
I,
don't
know,
use
a
GitHub
project
or
something
like
that.
F
C
You
know
something
like
like
a
progress
bar
or
Gantt
chart
that
would
allow
us
to
say
that
we're
50
here
with
objective
one
kpi,
two
just
an
idea.
A
Yeah
I
mean
if
we
transfer
this
to
into
a
GitHub
project.
There
might
be
some
tooling
that
allow
allows
us
to
do
that,
but
I
can
investigate
further
in
this
yeah.
A
Thanks
Steve
anymore,.
G
Think
it's
a
lot
but
I
think
it's
good
to
get
them
all
down.
I
feel,
like
you
know,
I,
think
I'm,
assuming
the
objectives
are
in
order
of
what
are
they
in
order
of
achievement,
or
just
you
know,
is
this
a
list
like
what
do
we
want
to
get
done?
First,.
A
Right,
that's
a
very
good
question.
No,
we
didn't
discuss
priority
or
order
in
this
list
yet,
but
it's
probably
something
we
should
do.
I,
don't
know
if
it's
possible
to
put
some
kind
of
weight
or
priority.
Maybe
if
we
transfer
this
into
GitHub
issues,
we
could
then
associate
a
priority.
G
Well,
maybe
we
get
a
little
credit
if
we
can
get
some
of
the
on
objective
number
one.
If
we
can
get
some
of
the
Toc
or
the
open
source
kind
of
project
leadership
working
together
on
an
LFX
effort,
maybe
we
can
get
that
to
transition
over
to
more
getting
them
to
come
to
the
TOC
meetings.
G
G
I
know:
I've
tried,
I,
don't
I'm
bad
at
continuing
continuing
to
follow
up
to
see
where
those
projects
are,
but
there
are
projects
out
there
that
we
should
be
maybe
giving
some
attention
to
and
I'm
not
sure
how
we
go
about
doing
that.
You
know
it's
just
hard
to
keep
track
of
some
of
the
stuff
when
it's
we're
not
meeting
on
a
you
know
us
on
a
daily
effort
for
us,
but
two
new
projects
and
having
two
in
the
pipeline
I
think
is
a
really
good,
I.
Think
objective.
Three
is
probably
important.
F
Thanks
yeah
all.
A
Right
I
hope
I
shared
the
link.
Yes,
so
the
link
is
in
the
meeting
notes
so
feel
free
to
to
add
more
commentary
for
this.
J
A
It's
also
something
I
mean
for
each
of
these
areas,
it
very
applicable.
It
could
be
the
case
that
we,
we
could
form
a
working
group
to
drive
that
effort.
Specifically,
the
downside
of
having
too
many
working
groups
might
be.
That
then
at
the
end
is
still
saying
the
group
of
us
and
if
we
don't
manage
to
get
more
people
involved,
we're
kind
of
dividing
our
bandwidth
or
work
across
doing
working
groups,
so
yeah
I'm
not
sure
what
the
best
balance
he
here
is.
G
On
that
topic,
did
we
ever
hear
back
from
Willamette
directive.
B
A
Sorry
I'm
not
sure
but
spelling
I,
think
project
mode.
Is
it
okay,
I'll
find
out
that
good
sense.
A
Okay,
any
more
comments
on
the
okrs.
F
B
F
B
Your
care,
like
Port,
we
can
inform
the
board,
but
you'll
see,
is
independent
technical
party
within
the
going
to
so
what
is
important,
at
least
from
the
overall
strategy
discussion
perspective
if
it
could
map
these
back
to
board
a
strategical
somehow
and
that
will
that
can
be
perhaps
done
once
the
goals
are
approved
by
the
board.
But,
yes,
monsters
thought
we
should
present
this
Andrea.
A
Okay,
so
what
I
can
start
doing,
then,
is.
A
H
Yeah
I
just
wanted
to
to
bring
up
the
question
there
about
graduated
projects
or
non-graduated
projects.
Should
there
be
some
difference
when
it
comes
to
the
first
two
objectives
there?
If
the
project
is
graduated
or
not,
do
you
think
we
need
would
put
higher
requirements
on
projects
which
are
graduated
and
compared
to
the
ones
which
are
not.
A
So,
do
you
mean
it's
something
like
graduated
projects
are
expected
to
be
interrupt
to
implement
interoperability,
features
or
things
like
that.
A
H
I
guess
when
it
comes
to
transparency
and
showing
what
happens
in
the
product,
that's
probably
not
no
difference,
but
maybe
when
it
comes
to
like
guidance
on
what
should
be
provided
by
the
projects
when
it
comes
to
well
to
say,
interoperability
and
those
things.
Maybe
that's
a
hard
requirement
on
the
graduated
projects,
but
not
for
the
others.
F
A
I
mean
I
think
for
sure
I
mean
it
would
be
good
for,
like
a
more
mature
project
to
to
lead
the
way-
and
you
know
demonstrate
like
interoperability
features
for
other
projects.
Also
to
follow
I
mean
we
could
consider
extending.
F
G
A
Yeah
yeah
absolutely
I
mean
indeed
like
we
have
two
tools
to
adopt
City
events
as
part
of
the
objective
too
yeah
and,
of
course,
I
mean
this
could
be
like
two
graduated
tools
and
in
fact
I
mean
there
is
work
going
on
already
started
to
you
know:
work
on
a
chill
event,
see
the
events
plugin
for
for
Jenkins
yeah.
G
That
that's
the
big
winner,
you
know
if,
if
the
Jenkins
Community
Embraces
it
it
will
change
the
course
for
CD
events,
I
think,
because
so
so
many
people
depend
on
Jenkins
of
Jenkins
is
starting
to
use
events.
It
would
make
a
huge
difference.
Yes,.
E
What
what's
what's
going
to
drive?
This?
Is
a
user
and
right
now,
Ben
Ben
Powell
right
has
been
working
with
CD
events
and
he's
engaged
with
the
Spinnaker
team.
They've
got
a
something
really
cool
going
for
that,
but
it's
not
just
enough
to
I
agree
with
you
Jenkins
doing
it
Spinnaker
doing
it.
That's
cool
but
having
a
customer,
a
user.
E
Sorry
a
user
talking
about
this
at
a
conference
and
why
it's
so
cool,
because
I
think
that
that
creates
momentum
for
other
CD
providers
to
add
that
My
Hope
Is
that
the
commercial
ones
do
this
My
Hope
Is!
That
CDF
is
first
and
then
commercial
providers,
like
harness
octopus
deployed.
They
include
CD
events,
I'm,
not
sure,
I,
understand
well
Siri.
You
need
to
work
to
understand
sorry,
but
yeah
you're,
absolutely
right
getting
Jenkins
on
board
getting
Spinnaker
and
that's
in
work.
E
G
Yeah
and
I
think
we'll
get
those
end
users
from
Jenkins
as
what
I
I
believe.
B
One
time
one
thing
I
want
to
make
sure
like
graduation
criteria
like
yeah
interpretability
could
be
discussed
within
the
graduation
criteria,
but
I
am
afraid,
like
matching
another
project
or
putting
another
project
as
a
criteria
may
not
be
good
I'm
sure
you
don't
mean
that,
but
just
on
Twilight
you
can
say
interoperable
Solutions
and
so
on.
But
adopting
cd-run
says
graduation
criteria
may
not
be
the
right
thing
to
do.
H
F
A
I
I
met
with
with
Jared
from
Fidelity
this
morning,
so
they
have
resources
are
located
to
to
work
on
the
Jenkins
City
events
plugin.
A
So
this
work
is
starting
now
and
if
I
don't
know,
if
you
seen
the
the
first
user
story
that
was
published
by
CDF
from
Fidelity,
so
both
Jenkins
and
City
events
are
mentioned
there,
and
that
is
a
part
one
and
the
plan
is
to
have
more
parts
coming
and
I
assume
following
implementation.
So
let's
that's
something
that
I
think
it's
goes
very
well
along
this.
This
lines
you
were
mentioning
Robert
I
mean
of
course
ideally
would
be.
We
will
see
other
type
of
end
users
as
well.