►
From YouTube: CDF TOC Meeting - 2021-08-17
Description
What's the Technical Oversight Committee TOC? https://cd.foundation/about/toc/
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
All
right
well
we're
four
minutes
in,
and
people
are
here
so
we
can
get
started.
The
very
first
agenda
item
is
the
results
of
the
talk
chair
election
and
so
I'd
like
to
announce
and
congratulate
oleg
as
the
next
cdf
talk
chair.
B
I
made
a
statement
in
during
the
elections.
It
remains
basically
in
the
same
in
terms
of
my
intent
to
focus
on
interoperability
and
helping
with
all
projects
with
whatever
governance
and
collaboration
part.
I
guess,
as
a
cdf2
cga
doesn't
really
change
so
focus
even
more
on
collaboration
and
on
empowering
anyone.
I've
been
in
the
cdf
and
yeah.
Whatever
happens,
I
don't
consider
the
guy
myself
as
a
kind
of
big
boss.
So
basically
yeah
tomorrow
wants
to
lead
the
meetings
drive.
The
agenda
topics
drive
initiatives.
Please
do
so
any
contributions.
B
A
All
right
so
with
that
I
guess
I'll
hand
the
rest
of
the
agenda
over
to
you
for
today.
We've
got
a
couple
topics
here,
but
you're
the
chair
now
so
congrats
and
good
luck.
B
B
Yeah,
probably
a
ton
of
slug,
just
in
keys.
D
B
B
So
on
the
top
we
have
a
jinky
separator
proposal,
so
we
have
a
pull
request
and
the
proposal
in
the
mailing
list
is
submitted
by
the
visa
show
up.
Well,
basically,
this
company
is
main
contributor
behind
the
junk
separator
for
kubernetes.
B
We
don't
have
any
representatives
from
them
on
the
today's
call.
Am
I
right,
but
maybe
tracy
could
summarize
the
discussions
between
the
continuous
delivery
foundation
and
mr
slab
about
this
particular
project,
because
I
know
that
there
were
some
discussions,
but
I'm
not
sure
what's
the
state
and
what
are
the
current
commitments
from
this
year.
D
Yeah
no
commitments,
I
think
we
should
get
bartek
in.
I
don't
know
if
he
was
invited,
but
there's
lots
of
work
happening
on
jenkins
operator
and
I
think
it's
progressing
well.
It
recently
became
a
sub
project
of
jenkins
as
kind
of
official,
but
I
think
in
practice,
jenkins
sub
project
doesn't
really
have
any
like
it's
it's
a
label,
but
it
doesn't
particularly
dictate
the
governance
or
how
the
project
should
operate.
D
So
I
think
they
were
interested
in
considering
whether
it
could
be
a
top
level
jenkins,
sorry,
cdf
project,
and
you
know
again
looking
for
just
ways
to
help
grow.
The
project
grow
the
community
and
also
have
some
good
governance
around
it
yeah.
I
I
think
I
pointed
out
the
the
roots
for
getting
involved
and
I
think
there's
some
things.
D
Certainly,
on
cdf
side,
we
can
help
with
the
promotion
and
growth
of
that
and
involvement
with
our
conferences
and
things
but
yeah,
as
mentioned
for
becoming
a
a
project.
That's
up
to
the
toc.
C
So
I'll
sort
of
summarize
what
I
said
in
the
slack
I
I
have,
I
am
just
curious
what
the
what
the
status
of
this
is,
because
I'm
I'm
unsure
why
it
should
be
a
new
top
level
project
instead
of
just
continuing
to
be
under
the
jenkins
project
and
and
if
they
need
some
support,
either
from
cdf
or
visibility
or
community
engagement
or
governance
like
we,
we
can
give
them
that
or
jenkins
can
give
them
that
in
their
current
position.
C
So
I
I'm
mainly
curious
what
they,
what
we
think
or
what
they
think
they
hope
to
get
from
being
a
new
top
level
project
that
they're
not
getting
now
or
that
that
they
can't
get
now.
C
This
would
be
a
great
a
great
time
for
bartek
to
be
here
to
answer
that
question.
But
if
anybody
has
insights
or
or.
B
B
Me
I
can
briefly
comment
on
the
jinky
side
because
yeah
I
second
jason's
question,
but
yeah
first
thing
in
this
particular
topic.
I
would
like
to
abstain,
firstly
because
of
my
church
and
state
conflict.
B
B
We
have
governance
model
for
the
jenkins
project
as
well
for
the
jenkins
core
for
other
companies,
but
yeah
whatever
sub
project,
whatever
just
plugin
community,
they
can
define
their
own
governance,
their
own
collaboration
model.
To
some
extent,
we
have
freedom
of
choice
with
regards
to
licenses
with
regards
to
role
on
boarding
processes.
B
Yes,
the
jinx
community
will
reserve
some
rights.
For
example,
jenkins
governance
meeting
may
enforce
particular
actions
like,
for
example,
code
of
conduct
for
any
sub
project,
but
ultimately,
jenkins
community
is
not
like
a
vertical
of
power.
B
We
started
discussions
with
virtuslab
one
year
ago
and
with
red
hat
about
a
potential
open
governance
for
this
for
kubernetes
operator.
These
discussions
didn't
go
that
well,
but
it's
rather
amount
of
company
contributors
agreement.
It's
not
a
problem
of
the
jinx
20.
C
Thanks,
I
guess
I
might
be
liking
some
of
the
context
from
red
hat's
involvement.
With
that
I
can
reach
out
to
some
folks
and
see
yeah.
I
can
forward.
B
Some
messages
to
the
team
if
needed,
because
there
is
a
public
discussion
and
the
results
have
private
discussion
with
the
jenkins
governance
board.
If
there
is
permission
from
participants,
I
can
share
some
insights
with
tlc
but
yeah,
ultimately
long
story
short
the
jinx
separator
at
some
point.
They
went
to
dark
in
open
source
because
they
started
their
private
project
and
the
maintainer
was
not
available.
B
Unfortunately,
due
to
personal
reasons
and
finally,
red
hat
was
unable
to
contribute
to
this
component,
even
though
it
was
under
the
umbrella
of
jenkins,
and
here
we
had
a
clash.
Because
again
we
provide
full
power
to
maintainers
and
if
maintainers
explicitly
decide
to
not
accept
contributions
to
not
accept
particular
visions
in
their
project,
they
totally
can.
B
So
we
try
to
litigate
that
and
our
main
problem
was
that
wasn't
very
responsive
until
they
returned
back
to
life,
with
a
renewed
commitment
to
jinx
kubernetes
operator
and
with
a
product
built
on
the
top
of
it.
So
after
that
they
returned
back
to
open
source
coming
in
to
start
contributing.
B
But
at
the
moment,
when
we
were
able
to
introduce
open
governance
together,
wizard
heart
was
lost
because
retract
basically
decided
to
create
a
hard
fork
and
to
start
evolving
hard
fork
which
they
abandoned.
Maybe
two
or
three
weeks
ago.
There
is
announcement
and
junkies
developer
man
at
least,
but
finally,
it
was
not
that
the
great
situation
community-wise,
because
we
had
a
split
yeah,
obviously
like
it
happens
in
open
source
whomever
contributes
wins
so
that
what
happened
yeah.
We
will
be
working
on
reintegrating
forks
somehow
but
yeah.
B
We
haven't
really
introduced
the
open
governance
model,
though
there
was
proposal
in
august
created
by
red
hat
and
the
jinx
governance
board,
and
then
we
proceeded
with
the
same
proposal
in
january
that
they
have
divisive
slab.
So
this
topic
is
somewhere
there,
but
none
of
the
parties
are
actually
able
to
complete
that.
E
So
if,
if
I
may
kind
of
thinking
about
sort
of
going
back
a
year
and
two
years,
something
like
that,
whenever
we
we
kick
this
off,
I'm
concerned
that
one
we're
basically
shifting
drama
from
one
level
to
another
level.
This
is
what
that's
sort
of
my
first
reaction.
The
second
thing
is-
and
this
is
speaking
as
someone
who
no
longer
is
a
voting
member
of
the
toc.
So
you
know
take
this
as
you
will.
E
The
other
thing
is
that
we
had
a
lot
of
conversations
about
branding
spread,
so
we
think
about
the
landscape.
It's
like,
oh
well,
you
know,
is
something
a
product
or
something
a
product
feature
that
is
being
created
in
order
to
create
more
real
estate.
For
you
know,
discoverability
and
honestly,
like
I,
I
feel
I
would
feel
uncomfortable
taking
a
piece
of
an
ecosystem
that
by
itself
isn't
really
relevant
as
a
standalone
and
saying
that
this
is
a
top
level
project.
E
That
said,
you
know
it
would
need
at
the
very
first-
and
you
know,
steve.
I
went
through
this
with
with
steve
and
tracy,
like
you
need
a
a
toc
sponsor
to
kind
of
walk
through
that,
and
if,
if
no
one
is
willing
to
sponsor
it's
dead
right
there,
but
you
know
my
feedback
to
this
project
would
be.
This
doesn't
really
make
sense,
as
as
far
as
what
the
goals
of
the
cdf
are.
You
need
to
figure
your
out
within
the
jenkins
community.
B
Oh,
it's
not
a
genius
plugin,
I
would
say
to
some
extent
its
repackaging
of
jenkins
or
not
the
distribution
of
jenkins.
So
basically,
separator
is
just
a
api
extension
for
kubernetes,
which
manages
jenkins
in
a
better
way.
But
yes,
it's
designed
to
manage
only
jenkins.
So,
for
example,
spinach
supports
multiple
engines.
F
I
think
that's
a
misnomer
that
we
have
with
creating
projects
in
the
cdf
that
all
of
a
sudden,
you
create
a
project,
and
you
have
all
these
people
that
want
to
contribute.
It's
really
a
grassroots
pro
effort
that
needs
to
happen,
and
I
need
for
me
I'd
like
to
see
that
happen
prior
to
them.
Getting
their
proposal
in
place.
B
There
are
definitely
individual
contributors,
hoping
in
helping
out
like
in
other
projects,
but
again,
even
in
the
jinx
community
is
something
we
would
like
to
help
them
miss.
So
we
want
to
support
all
our
sub
projects
as
well.
It's
just
a
question
of
how
many
resources
we
have
and
yeah
on
this
level.
It
would
be
perfect
to
collaborate
with
the
continuous
delivery
foundation.
D
So
I
think
that
might
be
key
to
it
or
saying
you
know:
how
can
we
enable
jenkins
operator
to
achieve
what
it
wants
from
within
the
umbrella
of
the
jenkins
project
and-
and
I
think
cdf
can
help
play
that
role
if,
if
what
we
want
to
do
is
bring
people
together
and
unite
them
around
technology
and
see
how
that
fits
into
a
wider
jenkins
road
map,
then
that
may
be
a
role
we
can
play
in
helping
the
the
jenkins
governance
make
that
happen.
B
Yeah
we
were
working
with
the
team
we
organized
online
meetups
to
promote
it.
We
published
blog
posts,
we
added
operator
to
our
photographers
and
other
programs.
We
also
have
a
google
summer
of
code
project
this
year,
so
from
the
community
site.
We
definitely
try
to
help
and
yeah.
I
can
also
say
thanks
to
the
team
working
on
kubernetes
separator,
so
this
is
basically
a
vegeta
show
up
one.
This
is
a
red
hot
one,
so.
B
C
C
C
B
We
take
it
offline.
Maybe
jason
could
gather
some
insights
from
the
red
hat
side
because
I
can
provide
a
list
of
contacts
who
you
could
contact
to
get
the
information
yeah
and
then
we
can
convince
somewhere
offline.
Maybe.
E
Okay,
but
I
I
would,
I
would
say
that
it's
not
jason's
response
or
anybody's
responsibility
on
the
toc
to
go
digging
that
up
it's
responsibility
of
the
project
to
provide
a
compelling
case
right.
I
I
think
that
that's
a
really
important
thing,
if
like,
where
are
they?
Why
are
they
not
here?
They
need
to
be
here
representing.
E
G
G
B
So,
okay,
here
we
can
basically
communicate
it
back
to
bartek,
who
requested
it
and
yeah.
Maybe
we
would
be
able
to
build
it
because
well,
regardless
of
whether
it's
a
jenkins
sub
project
or
cdf
project,
there
are
some
clear
action
items
which
are
needed
to
facilitate
contributions
and
many
things
actionable
will
be
discussed
a
few
times.
So
we
could
focus
on
that
and,
while
others
could
export
the
keys
more.
B
B
So
moving
on
then
october
first
so
now
we
have
only
one
month
and
a
half
left
before
oktoberfest
starts
and
actually,
if
you
want
to
organize
any
events,
events
should
be
planned
in
the
beginning
of
september,
because
there
is
some
coordination,
schwab,
logistics
and
other
things,
but
yeah
it's
coming.
F
Artelias
will
we
did
it
last
year
and
we'll
do
it
again.
This
year
we
reached
out
on
our
we
followed
the
guidelines
that
were
set
forward
and
didn't
need
that
much
help
from
the
cdf,
but
any
overarching
you
know,
marketing
or
whatever
that
the
cdf
is
going
to
do
will
participate
in.
D
Yeah-
and
I
was
going
to
add
that
the
the
link
I
put
is
the
page
we
had
set
up
last
year
and
the
plan
was
just
to
do
an
equivalent
for
this
year
and
roxanne
was
going
to
set
that
up
and
reach
out
to
projects
to
find
kind
of
the
best
link
and
then
also
do
the
corresponding
promotion
and
social
media
so
help
direct
people
to
the
to
our
particip
participating
projects
and
their
landing
pages
for
it.
B
G
We
can
put
something
up
for
screwdriver.
I
think
we
did
last
time
we'll
wait
for
communications.
B
And
everyone
will
tell
us
and
yeah
one
note
that
it's
actually
the
participation,
because
they,
in
fact
you
can
also
participate
in
passive
way,
just
put
some
github
topics
and
done,
and
you
can
promote
to
work
on
social
media,
create
onboard
link
events
for
contributors
and
they
will
try
to
do
that.
B
So
yeah
and
also
another
thing
which
is
related
is
cdf
tabs,
because
in
jenkins
we
did
a
few
events
for
oktoberfest,
including
grant
openings
presentations
like
contributing
to
jenkins,
and
they
have
been
quite
useful
in
terms
of
attracting
interest
and
attracting
contributions.
B
So
if
anyone
is
willing
to
organize
local
online
meetups,
we
can
currently
need.
So
maybe
it's
also
a
good
topic
to
discuss
with
roxanne
and
jaclyn,
because
yeah
all
such
meetups
are
useful.
They
can
brand
it
as
particular
project
meetups
or
cdf
meetups,
if
needed,
and
for
example,
for
switzerland.
I
plan
to
do
a
cdf
meetup
this
year,
instead
of
just
a
genius
one.
H
B
I
I
included
that
topic
here,
so
this
is
just
some
kind
of
announcement,
so
all
of
you
probably
know
that
internal
ability
seek
is
about
one
and
a
half
years
old
and
we
released
the
first
version
of
our
roadmap
july
2020.
So
it's
a
year
old
and
lots
of
things
happened
since
we
created
roadmap,
for
example,
events
for
the
work
stream
under
sig
interval,
it
became
top
level
seek
and
also
we
have
been
doing
some
information
sharing
knowledge
sharing
and
identifying
some
areas
to
focus
on
now.
I
We
believe
that
it
is
time
to
go
and
look
at
our
roadmap
to
see
what
we
achieved,
what
we
haven't
been
able
to
achieve
and
what
else
we
want
to
work
on.
What
is
just
a
call
for
action
if
anyone
is
impressed
to
contribute
to
our
roadmap
with
new
topics
and
so
on,
welcome
to
join
our
meeting
this
thursday
at
3
pm
utc,
we'll
start
refreshing
our
roadmap
and
that's
all
if
any
questions.
If
anyone
has
any
questions,
we
can
take
them
not,
then
we
talk
on
thursday
before
anyone
joins
the
meeting.
B
That's
great:
do
you
plan
to
keep
the
roadmap
in
a
similar
format.
I
Yeah,
I
think
this
tracy
miranda
who
helps
us
with
the
structure
of
the
roadmap,
so
it
makes
a
lot
of
sense
because
we
no,
we
can't
put
exact
pace,
but
we
can
plan
like
what
can
we
do
now
and
what
can
we
do
in
long
term,
short
term
and
so
on?
So
if
people
have
different
ideas,
we
can
do
that
as
well,
but
I
think
everyone
likes
the
format.
The
currently.
B
Thanks
for
the
update
thanks,
okay,
so
the
next
one
seek
events
looking
to
become
a
project.
F
Yeah,
so
just
a
a
heads
up
on
that
the
sig
events
and
the
sig
events
vocabulary.
They
are
looking
to
become
a
project
down
the
road.
What
they're
realizing
is
that
two
things
they
want
to
publish
a
standard
for
the
events
and,
secondly,
they
are
because
they're
they're
creating
you
know
code
to
make
it
all
happen.
F
So
they
have
a
little
bit
of
ways
to
go,
but
it
looks
like
they.
It
should
be
a
good
fit
down
the
road
for
becoming
a
project,
in
my
view,
so
just
want
to
give
everybody
a
heads
up
that
that's
being
worked
on
things
that
they're
doing
internally
is
is
like
getting
get
repos
organized
getting
documentation.
B
Yeah,
maybe
one
question
in
cncf:
there
are
two
types
of
memberships.
First,
one
is
project.
Second,
one
is
standard
and
standard
actually
presumes
that
there
are
reference,
implementations,
etc.
So
it
doesn't
exclude
the
code
part.
B
E
I
think
this
might
be
the
chance
to
explore
that
discussion,
because
we
haven't
had
this
circumstance
before.
F
They
are
publishing
the
you
know
like
the
communication,
events
and
kind
of
trying
to
come
up
with
a
standard,
so
the
event
payload
and
you
know
the
fields
in
the
event-
and
things
like
that
are
standardized,
so
you
can
have
seamless
integration
between
different
projects
and
products
so
that
that's
kind
of
one
of
the
things,
but
also
at
the
same
time,
they're
writing
code
to
make
some
of
it
happen.
So
you
know
the
event
listeners.
F
Those
type
of
things
are
being
written
as
well.
So
I
don't
have
the
exact
details
from
on
the
coding
perspective
what's
happening,
but
I
think
it's
going
to
be
both
that
are
going
to
be
a
product
of
the
events.
C
F
E
Really
really
cool
speaking
of
someone
who
actually
supports
teams
who
do
this
sort
of
work
be
really
awesome
if
a
key
part
would
be
the
conformance
test,
infrastructure
and
similar
types
of
things
to
make
that
super
easy
and
provide
us
a
certain
level
of
attestation,
interoperability
with
cloud
events,
I
think
that
could
be
a
very
powerful
framework
contributor
framework.
F
And
that's
and
that's
where
I
have
a
feeling,
the
the
coding
part
that
they're
doing
right
now
is
gonna,
be
the
groundwork
for
that
framework
as
part
of
that
process.
So,
besides
the
events,
I
think
you're
going
to
have
extra
stuff,
that's
going
to
be
needed
to
make
it
all
happen,
but,
like
I
said,
I
just
want
to
give
everybody
a
heads
up
of
that.
It's
coming
down
the
pipeline.
B
That's
for
sure,
and
I
guess
that
this
new
standard
will
be
aligned
with
cloud
events,
so
we
will
be
able
to
at
least
have
some
adapters
today.
Is
it
correct.
F
It's
mostly
based
on
cloud
events,
so
95
around
cloud
events
right
now.
There
are
some
things
that
they
are
recognizing
that
are
going
to
be
issues
like
that
they're
still
trying
to
figure
out.
So,
for
example,
if
you
publish
push
a
doctor
image
to
a
registry,
all
the
registries
are
not
consistent
on.
When
that
push
has
been
completed.
F
Some
of
them
do
web
hooks.
Some
of
them
do
grcp.
You
know
so,
there's
a
bunch
of
different
scenarios
when
you
start
talking
to
interacting
with
a
repository
and
registries
how
those
events
come
out
of
there.
So
that's
one
of
the
things
that
they're
going
to
be
tackling
it's
hard
to
analyze.
When
you
have
a
bunch
of
different
implementations,.
D
Steve,
I
can
help
connect
you
with
folks
from
the
linux
foundation
or
cncf.
If,
when
folks
are
ready
to
have
the
conversations
around
the
standards,
I've
been
just
learning
a
bit
more
and
there's
just
yeah.
There's
lots
of
options
for
how
standard
light
versus.
D
F
Into
those
meetings
perfect:
well,
I
we're
not
quite
there
yet
you
know
they
have.
Their
proof
of
concept
has
been
completed
so
they're
moving
to
the
next
step,
and
there
there's
still
a
bunch
of
work
to
do
before
we
get
to
this
point
of
trying
to
become
a
project
and
actually
publish
standards,
but
it's
moving,
which
is
good.
D
B
B
E
I
started
the
sorry
unmuted
okay,
I
saw
the
the
jenkins
traffic.
I
hadn't
seen
anybody
from
seen
any
comments
from
the
armory
folks.
I
was
going
to
reach
out
and
poke
cameron
and
those
guys
not
sure
if
cara
or
oleg,
if
you
had
had
conversations
with
them,.
B
I
asked
them
a
few
times,
including
so
we
had
a
demo
by
spinnaker
at
the
phase.
One
evaluation.
Yes,
I
pinned
them
last
time
two
weeks
ago
asked
whether
everything
is
fine.
It's
fine,
but
yeah.
F
B
E
I
think
they're
more
more
email
based
I
I
can
follow
up
with
those
guys.
K
Yes,
all
the
projects
are
on
track,
so
the
most
important
thing
is
most
certainly
going
to
go.
Well,
it
should,
and
we
are
now
planning
the
final
demos
and
presentations
and
if
you
go
into
the
gsoc,
if
this
is
of
interest,
if
you
go
into
the
gsoc
channel
for
the
cdf
slack,
there's,
actually
a
poll
going
right
now
on
when
those
presentations
should
be
held
when
would
be
best
for
people,
so
please
feel
free
to
participate
in
that
poll.
It
will
be
very
similar
to
the
midterm
demos.
K
The
students,
the
gsoc
student
participants,
seem
very
excited
about
it.
So
that's
great
we're
also
encouraging
them
to
write
final
blog
posts
linking
to
their
demos
linking
to
their
work
and
we'll
certainly
be
publishing
that
within
the
jenkins
blog,
but
it
would
be
really
nice
actually,
especially,
if
should
the
spinnaker
gsoc
student
write
a
post
as
well,
if
they,
if
we
did
something
within
the
cdf
to
promote
all
these
blog
posts
and
the
final
demos,
we
did
some
sort
of
wrap
up
right
up.
That
would
be
really
nice.
K
Swag
has
been
organized,
but
it's
been
organized
flabby's
is
sponsoring
swag,
which
is
very,
very
good
of
them.
It
has
been
organized
to
be
a
jenkins
t-shirt
and
I
have
pained
the
spinnaker
folks
that
they
are
more
than
welcome
to
have
the
to
participate
in
that
swag
and
they're
they're
invited
to
have
it,
but
that
they
may
wish
to
do
something
for
their
student.
In
addition,
since
it's
a
slightly
off
brand
for
them-
and
I
think
that
is
all
the
updates.
So
it's
a
lot
of
lo.
K
B
Yeah,
maybe
one
related
questions
about
the
blog
post,
so
as
it
was
communicated
by
roxanne
in
september.
You
will
have
a
newsletter
by
the
stf
about
jenkins
in
the
cloud
and
we
definitely
have
a
few
pending
blog
posts
that
are
related.
For
example,
cloud
events,
plugin
for
jenkins
phase,
one.
B
Whether
we
could
learn
that
also
g
unit,
external
storage
is
also
within
the
scope
of
cloud
native
seek
of
jenkins.
K
As
far
as
the
cloud
events
plug-in
shuji
is
writing
a
blog
post
for
the
cdf,
and
I
I
assume
she'll,
be
writing
about
the
entire
work
she's
been
doing
over
g-stock
and
will
build
on
what
she
did
during
phase
one
for
the
others.
I
have
put
it
within
the
channel
and
promoted
that
they
would
write
posts
for
the
cdf
newsletter
if
it
fits
the
topic
and
that
they
should
certainly
submit
them.
B
I
talked
to
my
student
akihiro,
he's
aware
about
the
opportunity,
but
yeah.
It's
also
a
question
about
the
bandwidth,
because
here
we
had
some
mentor
capacity
issues
in
the
project
and
other
things,
but
well
the
project
itself
is
going
well,
but
I
can't
commit
there
will
be
a
blog
post
for
cdf
newsletters,
because
the
deadline
is
just
in
three
days.
B
He
might
follow
up
with
roxanne
tomorrow.
B
Yeah,
by
the
way
there
will
be
devops
world
conference
in
late
september
september,
28th
to
30th
all
jsoc
students,
spinnaker
and
jenkins.
They
were
invited
to
record
liking
talks
for
this
conference
and
I
know
for
sure
that
some
students
recorded
them
and
yeah.
They
will
be
also
represented
there,
so
I'm
not
100
sure
about
the
spin
and
care
team.
So
maybe
it's
a
topic
for
you:
tara
to
check,
while
you're
engaged
with
them,
but
yeah.
If,
yes,
the
slot
was
reserved.
B
E
E
L
Also
dan
lawrence
is
heading
our
keynote
on
security
and
scalability,
so
yeah
about
that.
B
Yeah
and
we
will
likely
have
a
jinx
contributor
summit
on
october,
2nd
right
after
the
conference
legend
is
to
be
defined.
We
got
quite
good
experience
with
the
event.
In
june,
we
processed
some
feedback
to
make
it
even
more
funny
and
interesting
to
participants,
but
yeah.
There
will
be
an
event
there.
B
Last
time
I've
heard
a
conversation
between
mark
and
alice.
It
was
october
2nd,
which
is
saturday,
okay,
but
let's
say
I
have
something
to
ask
tomorrow
once
I'm
back
from
vacation,
because
it's
not
clear
to
me
what
is
the
final
day
and
we
are
doing
it
in
a
packed
amazon.
It
seems
so
we
it
improves
our
outreach,
but
it's
also
not
aligned
with
devops
vault,
which
has
additional
changes.
B
Okay,
then
next
painting,
I
guess
we
meet
as
usual
on
31st
of
august,
unless
there
are
blockers
for
that,
but
I'm
not
aware
of
any
and
yeah.
There
are
a
few
topics
in
the
mailing
list,
which
I
consider
bringing
up
including
sandbox
projects
and
another
one
is
about
inclusive
naming
initiative
for
membership,
but
yeah.
None
of
them
are
time
critical,
but
if
there
is
time
there
at
the
next
meeting,
I
would
like
to
bring
them
up
and
the
responses
to
the
mailing
list
would
be
appreciated.
B
Okay,
I
guess
not
so
thanks
everyone
and
yeah.
If
you
have
any
feedback,
any
ideas,
how
we
are
gonna
answer
the
meetings
to
make
them
more
efficient.
Please
just
comment
in
sdfslock
and
also
if
anyone
wants
to
drive
these
meetings,
please
step
up,
because
how
we
do
it
in
jenkins.
We
try
to
rotate
the
horse
and
we
also
try
to
have
a
note
keeper
roll
also
on
rotation,
so
that
one
person
basically
hosts
another
person
makes
notes
and
it
allows
everyone
to
participate
in
the
discussion.