►
From YouTube: TOC Meeting - Apr 25, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
A
And
for
you
to
sign
you
something,
but
today's
April
26th
welcome
everyone.
You
still
needs
a
few
of
us.
A
D
A
All
right,
yeah
welcome
everyone,
so
start
to
start
action
item
from
last
meeting.
I
only
had
one
action
item
30
for
you
to
document
start
starting
a
draft
and
about
the
documentation
for
chair
election.
We
have
some
discussion
last
time
about
what
happens
with
a
chair.
If
the
chair
is
not
part
of
the
TOC
anymore
and
so
forth,.
F
Yeah
I'm
working
on
that
and
I
will
sometimes
any
issue
perhaps
or
sharing
Google
book
yeah
I
can
create
an
issue
I
shared
Google
Docs
under
that
issue,
so
everyone
can
see
that
the
reason
it
hasn't
happened
yet
because
we
are
still
you
know,
working
with
getting
up
the
charter
update
version
of
Charter
to
be
approved
by
the
board.
That
might
you
know,
have
impacts
on
chair
and
Deputy
chair
election
policy,
so
it
might
be
better
to
have
that
together.
So
we
can
have
one
policy
discussing
both
positions.
A
F
A
Sense,
thanks
fatty
since
you're
talking
do
you
want
to
discuss
the
TRC
20
yeah
three
elections.
F
So
this
year
we
have
six
out
of
nine
seats
up
for
elections
in
Tech,
North
Side
committee.
So
two
and
user
representatives
are
no
their
terms
for
one
year,
Emily
and
Justin,
and
the
terms
I
think
terms
expire,
April
30th
this
weekend
and
currently
the
Voting
is
happening
and
in
the
selection
only
the
end
user
members,
the
camera.
So
we
have
six
voters
because
we
have
six
end
user
members,
hopefully
being
off
next
week.
F
We
should
know
the
results
and
we
will
announce
that
on
Main
lists
and
slack
who
will
be
the
end
of
the
representatives
within
Toc.
The
second
election
is
about
project
Representatives,
which
is
what
we
discussed
during
previous
meeting
as
well.
So
while
we
were
working
on
documenting
the
process,
we
identified
few
things
there.
The
last
time
when
the
project
representatives
were
elected,
a
certain
process
was
followed,
but
I
don't
remember
that
process
being
discussed
within
TRC.
It
may
have
been,
but
I
it's
been
two
years
now.
F
So,
instead
of
the
copying
dot
Pro
that
process
and
following
that,
we
want
to
get
to
see
to
look
at
what
that
process
was,
and
you
know
by
just
any
changes
and
the
three
questions
we
asked
Dave
since
these
are
projects
representative
elections.
The
last
time
only
people
with
10
or
more
comments
were
considered
as
eligible
Waters
within
project
representative
elections.
As
we
all
know,
people
can
contribute
our
projects
in
different
ways.
F
So
that
is
first
question.
Second
question
is
about
term
current
project.
Representatives
have
two
years
term.
We
just
want
to
mention
like
if
Chelsea
wants
to
keep
two
years
terms
for
the
projects,
and
the
last
question
is
about
term
limits.
We
don't
have
any
limits
currently
for
individuals,
like
individuals
can
serve
on
the
TRC
two
terms
on
or
something
like
that,
and
the
question
is
like
what
you
also
want
to
introduce
some
kind
of
term
limits
as
well.
F
All
these
questions
are
on
that
issue
I
linked
there
and
if
anyone
wants
to
you
know,
have
a
camera,
please
go
and
comment
it.
There,
like
I,
put
the
links
there
and
then
based
on
what
comes
up
from
this
discussion,
then
we
can
document
that
process.
If
no
one
responds
by
I
think
we
should
start
the
process
mid-may
or
something.
Then
we
followed
last
year's
or
2021
election
process,
as
is
no
changes
to
your
terms.
No
term
limits,
and
only
the
people
with
Comics
are
eligible
to
vote.
C
F
F
In
addition
to
that
to
make
sure
like
we
don't
miss
Waters,
there
will
be
a
water
registration
form
as
well
like,
because
inside
this
might
have
issues,
people
can
state
that
they
should,
because
there's
Waters
because
of
whatever
reasons,
and
then
that
will
be
revealed
by
the
election
officers.
So,
yes,
we
will
be
using
in
size
again
yeah.
F
I
can
actually
send
that's
a
good
point
or
like
be
onboarded
all
the
projects
to
LFX
in
size
end
of
last
year
and
based
on
the
organization's
GitHub
organizations,
we
know
I
can
add
those
organizations
we
registered
on
insights.
To
that
issue
actually
and
say
please,
project
Representatives
check
is
this
is
correct
if
we
are
missing
any
org
or
repo.
Just
let
us
know
so
we
get
the
list
corrected.
Maybe,
and
if
you
can
action
me
yeah
and
also
last
point,
we
will
only
consider
last
year's
contributions.
F
C
Basically,
you
expect
10
commits
within
one
year
or.
C
Criteria,
if
this
is
what
I
didn't
grasp
from
your
pull
request,
because
I
understood
that
10
commits
from
the
beginning
of
times
of
the
project.
A
C
Yeah
because
yeah
I
will
I
think
we
will
need
to
do
something
because
yeah
definitely
know
about
active
contributors
who
just
do
not
commit
code
in
our
project.
Yeah
right
now,.
G
D
G
H
F
F
H
Consuming
like
riding.
C
White
papers
and
even
needs
you
expect
that
individual
LF
profiles
are
configured
correctly
because
many
contributors
do
commits
using
the
corporate
emails
and
unless
somebody
Associates
this
email,
it
won't
be
counted
properly.
On
all
of
X
insights.
F
C
F
That
form
that
form
actually
what
registration
form
could
actually
cover
like
what
Tracy
you
said
like
we
have
lots
of
people
helping
with
arteries,
they
should
be
considered
as
Waters,
then
you
can
submit
those
names
via
form
for
mortalism,
for
example,
and
same
with
other
things
like
pull,
request,
reviews
and
so
on.
So
we
make
sure
like
we
actually
recognize
people's
other
types
of
contributions.
F
But
then
what
we
can
do
we
can
document
the
process
based
on
like
what
we
discussed.
We
just
take
commission.
Then
we
explicit
State
any
other
contributions.
They
are
also
valuable
and
this
water
registration
form
should
be
used,
for
you
know
bringing
those
community
members
as
voters,
because
we
need
to
start
this
process
pretty
soon.
So
people
can
start
talking.
D
F
C
Soon
as
possible,
yeah,
the
real
project
leads
have
access
to
the
list
of
Voters.
We.
F
F
Ask
like
yeah,
I,
think
last
year's
like
2021
Waters,
the
time
they
contained
GitHub
handles.
We
can
do
the
same
for
this
year's
election.
F
F
F
H
F
Yeah
I
think,
if
you
can
get
this
pull
request
merged,
then
we
cannot
pay
that
file
and
introduce
the
projects
represented
to
Alexa,
and
then
we
should
have
that
election
was
Associated
by
next
to
your
stimulate,
and
then
we
kick
off
the
Empire
process.
F
H
Yeah
I,
don't
I,
don't
think
Steve.
Do
you
see
anything
from
ortillas
standpoint
that
there's
issue
with
this
and
I
I?
Don't
I
mean
the
question
around
term
limits,
I
I,
don't
think
we
should
have
term
limits.
Well,
I!
Think
we
yes
I,
think
there
should
be
a
you
should
have
to
get
reelected
every
two
years.
Let's
just
put
it
that
way,
but
you
should
be
able
to
be
re-elected
as
many
times
as
the
community
wants
to
elect
you.
E
Yeah
I
looked
at
the
I,
looked
at
our
insights
in
the
artillius
project
in
the
repos,
look
pretty
accurate.
So
that
looks
good
on
that
front.
But,
like
you
said,
we
just
need
to
make
sure
that
in
the
pull
request
we
have
the
references
to
the
alternative
way
to
handle.
A
Yeah
about
about
the
term
limits,
I
think
it
I
agree
with
you
Tracy
that
it's
hard
to
find
volunteers
on,
on
the
other
side,
having
some
limits,
or
at
least
some
recommendations
might
kind
of
help
us
to
to
work
on
on
like
preparing
the
the
next
volunteer.
The
next
leaders
in
this
group,
if
it
makes
sense,
I'm
just
worried
that
if
we
don't
set
any
limits
at
all,
then
it's
just
easy
to
continue.
A
At
least
I
know
for
myself:
I
tend
to
maybe
like
I.
Don't
have
a
limit,
I
say:
okay,
well,
I'll
just
continue
to
do
this,
but
I
don't
know,
or
we
could
have
a
recommendation
if
you're
not
comfortable
with
limits
say.
Maybe
we
recommend
that
we
have
a
two
two
terms,
but
we
leave
it
up
to
the
TOC
too
make
a
final
decision
so
that
we
don't
constrain
ourselves
into
a
situation
where
we
don't
have
another
candidate.
H
And
that
would
be
another
way
to
do.
This
is
to
and
I
don't
know
if
the
projects
themselves
have
tocs
I
know
artillius
we're
going
to
run
elections
for
tocs
this
year.
If
the
projects
have
their
own
Toc,
then
the
TOC
could
nominate
somebody
from
the
project
POC
to
be
a
project
representative,
and
we
wouldn't
have
to
have
elections.
A
D
H
That's
ortelius
has
a
governing
board,
but
we're
considering
putting
together
a
small
I
would
call
it
a
maybe
like
an
architecture,
Review
Committee
or
something
that
just
as
technical
topics.
H
F
Well,
that's
pull
requests
if
you
can
get
that
like
full
requests,
I'm,
not
saying
we
should
manage.
If
there's
an
issue
we
should
update,
but
that's
the
current
thing
how
we
are
running
these
elections
for
end
users.
So
what
we
want
to
do
is
like
we
want
to
write
same
kind
of
document
for
project
Representatives
as
well.
F
Yeah,
we
can
quickly
go
through
the
document.
If
you
have
time
I
see,
Cameron
is
waiting
for
sprinkle
project
update,
so
I
don't
want
to
take
the
time
from
his
presentation.
That's
pretty
simple
document
like
it
talks
about
what
Toc
member
being
Qs
member
means.
What
is
the
timeline
when
the
election
starts
when
the
ballots
are
distributed,
candidate
criteria,
water
criteria
and
so
on?
Let's
create
a
standard
document,
but
I
just
want
to
make
sure
we
all
see
what
is
there
and
find
out.
D
A
Maybe
we
could
I
suggest
we
Cameron
presentation
and
we
go
for
the
agenda
and
if
we
still
have
time
we
we
can
do
the
review
online.
Otherwise
we
do
it
offline.
It
makes
sense.
G
A
A
Okay
sounds
good,
so
thanks
Cameron
for
preparing
your
project
update
for
today,
I
will
stop
sharing
so
that
you
can
get
started.
I
Well,
we'll
just
do
it
like
this
awesome
here
we
go.
That's
not
it
either
cool
all
right!
So,
hey
everyone!
Welcome
to
the
Spinnaker
project,
update
I
just
wanted
to
go
over
a
quick
project,
history
and
then
talk
about
some
of
the
governance
changes.
We've
done
and
then
talk
about
our
roadmap.
It's
next
here!
So
let's
go
into
it
and
please
at
any
point,
feel
free
to
unmute
and
ask
some
questions.
So
Spinnaker
was
born
back
in
2015.
It
was
pretty
out
of
Netflix.
I
Netflix
was
a
pretty
heavy
user
of
aws's
vm's
strategy
at
that.
At
that
point
there
was
not
much
of
a
UI
on
top
of
AWS
and
Netflix
wanted
to
improve
the
developer
experience
for
their
developers,
so
they
created
Netflix
grid
Spinnaker
back
in
2015..
I
It
was
open
source
to
you
A
year
later
after
Google
joined
the
project
and
as
it
was
being
open,
source
Armory
and
Ops
Max
basically
came
into
existence
as
vendors
for
the
the
Spinnaker
open
source
community.
I
So
we
started
growing
a
bunch.
We
participated
in
the
Google
summer
of
code
for
a
few
years
and
we
hosted
week-long
Community
hackathons.
This
was
a
really
cool
new
type
of
a
hack.
Upon
that
we
we
did.
It
was
worldwide
hackathon
where
I
was
24
7
for
about
a
week,
and
we
did
have
people
taking
shifts
essentially
as
a
mentors
for
the
the
teams
that
we
created.
So
the
idea
was,
you,
don't
have
to
have
a
team
or
a
project
idea
to
participate
in
the
hackathon.
I
It
was
really
to
start
really
to
help
improve
our
contributors
so
get
new
folks
into
the
Spinnaker
project.
For
those
who
don't
know,
Spinnaker
is
a
pretty
I
guess
I
would
say
like
heavyweight
deployment
tool,
so
it
it's
not
the
simplest
to
run
and
manage.
I
However,
it
scales
very
well
for
large
Enterprise
organizations
because
of
that
the
the
community
members
are
made
up
of
mostly
large
Enterprises
and
the
developers
come
from
those
organizations
again
because
of
that,
we
wanted
to
start
and
bring
people
outside
the
community
in
as
new
members,
so
that
we
could
keep
the
project
going
and
be
successful
and
then
copid
hit,
and
that
was
very
sad.
I
So
some
major
contributors
and
Community
leaders
left
the
project.
Both
Netflix
and
Google
have
stepped
back
from
the
project.
In
pretty
major
ways
we
saw
contributions,
go
down.
I
think
this
was
a
pretty
common
thing.
We
saw
across
different
open
source
organizations
during
this
time,
so
the
steering
committee
wasn't
really
engaged
and
the
typical
oversight
committee
wasn't
really
engaged
either
there
was
one
or
two
active
members
as
part
of
the
open,
the
technical
oversight
committee
during
this
time
as
well,
the
release
process
broke.
I
There
was
a
lot
of
hard-coded
dependencies
on
third-party
services
that
ended
up
shutting
down
and
that
that
took
us
quite
a
bit
of
time
to
fix
that.
I
During
this
time,
though,
it
wasn't,
all
bad
Salesforce
were
in
the
community
as
a
contributor
and
has
really
come
in
as
a
really
great
Community
leader,
so
very
thankful
for
Salesforce
joining
joining
the
community.
All
right,
let's
build
it
next
time.
So
as
as
we
were
in
as
we
were,
leaving
the
the
major
covid
days,
let's
say
we
were
discussing
internally
at
Armory
about
trying
to
revive
the
community.
Like
hey
Spinnaker's,
this
cool
thing.
We
know
many
people
are
using
it.
It's
not
that's,
not
a
question
to
us.
We
have.
I
I
We
met
many
community
members
here,
especially
at
from
the
CDF
in
CD,
at
cdcon,
in
Austin
in
2022.,
so
I
met
a
lot
of
people
in
the
community,
I
hadn't
met
before,
and
that
was
really
great
just
talking
with
people
and
getting
an
idea
of
what
people
wanted
out
of
Spinnaker
and
out
of
the
community,
it's
a
very,
very
broad
topic,
but
that
was
kind
of
the
intent.
Is
that
hey?
What
are
you
guys
here
for
you
came
to
cdcon
you're
coming
to
the
Spinnaker
Summit
talks?
I
Why?
Who
are
you?
What
are
you
interested
in
so
I
took
that
opportunity
to
start
to
recruit
new
technical
oversight
committee
numbers,
so
we
we
were
really
intentional
about
sorry
about
that.
I
We
were
really
intentional
about
who
and
how
we
went
about
forming
this
this
this
new
committee,
so
we
wanted
to
get
contributors,
vendors
and
large
users,
so
it
wasn't
all
stacked
in
one
in
one
area
we
ended
up
going
with
nine
members
total
that
wasn't
we
we
wanted
either
seven
or
nine
members,
so
it
was
kind
of
a
who's,
all
Well's
interested
and
and
let's
see
who's
racing
their
hand
there
oops.
I
So
we
worked
with
the
previous
technical
oversight
committee
and
steering
committee
from
the
Spinnaker
side
and
the
CDF
on
updating
the
governance
structure.
So
in
fact
he
was
a
huge
huge
help
in
all
that
we
did.
While
the
technical
oversight
committee
on
the
steering
committee
weren't
active,
we
knew
those
people,
they
were
part
of
the
community.
So
we
just
reached
out
and
said:
hey:
do
we
have
your
blessing
on
on
changing
up
the
leadership
structure
and
updating
the
the
governance?
I
So
what
we
did
is
we
combined
the
technical
oversight
committee
and
the
steering
committee
into
one
group
so
that
we
could
be
more
agile
in
terms
of
our
decision
making?
It
is
comprised
of
both
Technical
and
non-technical
folks.
So
we
we
do
a
lot
of
discussions,
both
technical
as
well
as
like
event,
planning
and
hey
who's,
going
to
be
talking
on
this
panel.
Can
we
Recruit
new
members
for
working
on
this
project,
so
on
so
forth
and
again,
the
other
intent
was
faster
decision
making
and
affection.
I
So,
as
I
said,
we
had
a
lot
of
intent
with
creating
this
committee,
so
we
we
gathered
motivations
for
joining
the
technical
oversight
committee
and
then
we
used
those
motivations
and
saying
hey.
We
all
came
in
with
something
we
want
out
of
the
community
and
we
all
came
in
with
the
expectation
we're
going
to
be
helping
out
with
the
community
as
well.
Helping
out
in
this
case
means
attending
technical
oversight.
Committee
meetings
publicly
speaking
about
Spinnaker
at
least
once
a
year
and
having
members
from
your
organization
contribute
code
to
the
project.
D
Let's
continue
on.
I
I
guess
I'll
I'll
quickly
go
over.
Our
governance
are
particular
oversight.
Committee
members-
let's
see.
I
Here
in
GitHub,
so
if
we
take
a
look
at
the
governance
information.
I
The
the
current
members
of
our
technical
oversight
committee-
it's
Amy
Smith
from
Netflix
myself,
I'm,
the
chair
of
the
memory
we've
got
Cole
at
Autodesk,
the
DC
from
Apple
who's.
Somebody
I
believe
in
that
David
Byron
over
at
Salesforce,
but
not
optimax,
James
from
Home
Depot
mattcoberly
at
jpmc
in
Christina
from
AWS.
So
we
did
want
to
try
to
get
some
some
Cloud
providers
joining
the
the
technical
oversight
committee
to
show
their
in
intentions
of
voting.
The
production.
I
All
right
and
then
the
the
project
roadmap
so
for
2022.
Most
of
what
we
were
doing
was
folks
fixing
the
release
process
getting
getting
ourselves
unblocked.
I
There's
gonna
be
more
improvements
to
come,
so
we
have
we've
set
up,
we've
updated
all
the
automation,
not
all
the
automation,
there's
always
more
more
things
to
automate,
so
we're
still
working
on
the
release
process
and
shifting
left
on
our
our
test
name.
So
right
now,
testing
happens
very
late
in
the
process
and
we
want
it
to
happen
as
part
of
our
our
main
development
sector.
I
In
addition,
we're
starting
to
set
up
a
release
manager
rotation
so
as
we
fixed
and
improved
the
release
process
that
that
knowledge
about
how
it
works
is
Consolidated
with
a
few
folks.
So
we're
setting
up
a
release,
manager,
rotation
and
getting
more
more
folks
prop
to
speed
thanks
nice
talking
I
like
so.
We
also
restarted
the
RFC
process
and
we
we
started
doing
this
by
showing
hey
these
are
the
projects
we
want
to
do.
I
Let's
get
community
input
on
them
and
let's
start
discussions
in
public
again,
so
we
restarted
the
RFC
process
as
part
of
2022.
and
then
going
into
2023.
We,
our
our
main
objectives,
are
to
improve
contributions
to
Spinnaker,
so
we're
currently
working
on
modernizing
spinning
we're
bringing
we're
upgrading
spring
Java
and
Gradle,
and
this
is
helping
improve
security.
A
lot
graduating
from
CDF
is
on
our
roadmap
at
some
point,
so
we're
working
to
to
get
towards
that
towards
that
goal.
I
We
do
want
to
reduce
the
barrier
of
entry
for
getting
started
so
we're
working
on
improving
our
install
methods
for
getting
excuse
me
like
a
day.
One
use
just
get
it
set
up
and
going
so
that
you
can
get
your
hands
on.
I
Then
we
also
are
setting
up
a
mono
repos.
This
is
really
going
to
drastically
simplify
development
and
release.
Spinnaker
is
comprised
of
12
microservices
and
it's
it's
quite
a
lot
to
develop
by
having
a
a
mono
repo.
It's
really
going
to
help
our
our
testing
and
our
reliability
product
we've
been
very
interested
in
CD
events,
integration
that
came
out
as
part
of
our
one
of
our
rfcs
from
Erickson.
So
we're
really
looking
forward
to
integrating
CD
events
into
the
project.
I
I
Lastly,
we
want
we
want
to
focus
on
performance
improvements,
so,
like
I
said,
Spinnaker
is
used
by
very
large
Enterprises
throughout
throughout
the
throughout
the
world
and
the
performance
these
these
Enterprises
are
hitting
these
stealing
issues.
So
it's
really
cool
to
see
it's.
It's
also
a
challenge
that
Spinnaker
has
is:
how
do
we
improve
performance
for
very,
very
large
setups
as
I'm
sure?
I
Most
of
you
know,
every
company
has
their
own
unique
way
of
deploying
and
managing
their
their
software
life
cycle,
and
because
of
that,
it's
challenging
to
identify
common
areas
of
of
improvement
for
scale
all
right
and.
I
We
did
so
we
had
a
steering
committee
and
we
had
a
technical
oversight
committee
and
the
steering
committee
was
largely
that
they
were
technical,
technical
folks,
but
that
wasn't
their
day-to-day
operations.
It
was
more
directors
leaders
within
the
company
of
and
business
units
right
and
then
we
had
a
technical
oversight
committee
and
then
we
also
have
six
as
well.
So
now
it's
it's
technical
oversight
committee
and
then
siggs,
and
then
we
meet
on
a
bi-weekly
every
other
week
basis.
H
Thank
you,
we're
artillius
is
going
through
the
are
we
or
are
we
not
going
to
do
a
Toc,
but
I
think
it
will
be
I
think
it's
an
important
part
to
pull
some
of
our
architecture
Sig
folks
over
and
give
them
a
Toc
role,
and
you
think
that
kind
that
helps
solidify
some
of
your
contributors.
Then.
I
There
was
a
little
bit
of
a
lack
of
communication
between
the
two
organizations,
and
so
it
was
like
the
the
folks
who
were
helping
throw
events
weren't
necessarily
talking
to
the
the
contributors
as
as
much
and
the
project
road
map
started
to
get
unclear
and
things
started
to
seem
to
to
fall
apart.
So
the
decision
making
seemed
to
go
very
slow
and
there
wasn't
too
much
action
being
taken.
I
It
is
that's
one
of
the
reasons
we
included
joining
the
the
meetings
on
a
regular
basis
as
an
expectation
if
you're
not
participating,
you're,
not
you're,
not
participating
and
you're,
not
being
active
and
you're,
not
you're,
not
contributing
to
the
community,
and
then
it
just
goes
back
to
the
expectations
on
well
we're
all
here
to
participate
and
help
move
this
forward,
and
if
we're
not
doing
that,
let's
find
a
way
to
to
do
that
better.
We.
I
We
did
update
our
our
governance
structure,
but
it
was
more
I
would
say.
Let
me
let
me
take
a
look,
though.
H
H
Just
sit,
I'll
show
you
my
email
and
if
you
have
one,
if
there's
my
email,
it's
just
Tracy
at
the
PlayHub,
so
you
do
have
it
and
I
would
love
to
get
together
with
you
if
anybody's
at
cdcon
or
really
talk
about
adoption,
because
that's
one
of
our
challenges
as
well.
I
Important,
it's
something
that
we
we
constantly
struggle
with.
It's
not
a
it's,
not
a
simple
thing:
it's
not
I
one,
one
of
the
hardest
parts
for
us
as
as
it's
I,
don't
know
if
it's
silly
or
not,
but
we
have
so
many
microservices
and
we
have
a
shared
library
and
when
you
update
that
shared
Library,
all
the
services
get
updated
and
testing.
H
We,
if
we
get
together
at
cdcon-
and
you
can
tell
us
about
making
just
simplifying
the
on-ramp,
we
will
show
you
how
we
figure
out
how
those
microservices
map
together
and
how
you
figure
out
what
you
have
to
deploy.
I
Ment
yeah
appreciate
it
and
I'll
share
the
slides
after
this
meeting.
E
And
I
have
a
quick
question
with
your
when
you
added
the
criteria
around,
you
know
what
people
are
on
the
like.
The
TOC
need
to
be
doing,
and
things
like
that.
Did
you
look
at
any
gamification
around
that.
I
Let
me
think
the
the
only
time
we've
used,
gamification
I
think
it's
meant
for
the
hackathon
is
to
entice
contributors
and
and
give
give
prizes
there.
But
though
we
haven't,
we
haven't
considered
that.
H
I
So
we
will
have
to
come
up
with
some
cool
swagger.
Badges
are
free.
H
A
A
Good
something
happened
with
my
headphones:
I
hope
it's
not
too
bad.
I
was
saying
thanks
a
lot
Cameron
for
for
the
great
presentation
and
yeah.
If
you
have
any
more
questions
to
Cameron,
I
guess
Cameron
you're,
quite
often
for
participant
of
this
meeting
so.
H
And
Cameron
did
you
guys,
did
Spinnaker
sign
up
for
a
Spinnaker
project,
Summit
AT
cdcon.
H
I
Oh
I'll
have
to
let.
H
Me
share
that
with
you,
because
if
you
did,
then
that
would
be
a
good
place
for
some
of
the
artillius
folks
to
chat
with
your
team.
I
A
A
G
H
I
9Th
okay
I'll
reach
out
to
Fernando
to
to
have
him
choose
one.
I
I
A
J
Yes,
go
through
those
quite
quickly,
I
guess
so
we
have
been
reaching
out
I
guess
from
the
TOC
to
get
new
sponsors
in
the
different
six
which
currently
lack
sponsors
and
Tracy
has
volunteer
there.
J
Thank
you,
Tracy
for
volunteering
and
I
just
wanted
to
to
state
it
here,
modest,
I,
guess
the
the
thing
is
it's
very
much
okay
with
having
Trace
as
a
sponsor,
so
we
welcome
you
there
I
I,
don't
know
I
mean
the
process
doesn't
really
say
on
how
if
there
is
no
sponsor
anymore
for
a
sake,
how
should
a
new
sponsor
be
elected
or
acquainted
or
so
is
it
to
be
done
by
the
TOC
I
mean
when
a
new
project,
a
new
Sig
is
created
and
obviously
the
the
TLC
will
approve
the
the
new
suit
coming
in?
J
J
A
A
What
happens
if
there
is
no
volunteer,
so
that's,
maybe
something
we
we
should.
We
should
do
I
don't
know.
Is
that
something
I
know?
Maybe
you
you
would
like
to
to
draft
a
possible
approach.
We
could
document
for
that
and
we
could
then
review
it
in
the
next
meeting.
J
Yeah
I
can
try
to
think
about
something.
There
I
know
that
there
are
several
things
now
in
that
APS
open
the
list
on
the
six
there's,
no
stop
it's
not
just
the
advantage
that
lacks
and
a
sponsor.
So
maybe
we
should
then
assume
the
other
ones
are
actually
done,
not
able
to
elect
a
new
sponsor
or
a
point
on.
So
we
have
a
short
case
there
right.
G
Yeah
I
think
the
request
to
get
volunteers
for
sponsors
recently
came
out
because
we
discovered
this
as
well.
There's
a
number
of
cigs
that
aren't,
you
know,
don't
have
an
updated
or
current
sponsor,
so
we
kind
of
put
it
out
there.
Andrea
asked
for
folks
to
volunteer
on
the
TOC,
but
we
didn't
follow
through
with
you
know,
future
processes
I'm
dealing
with
that.
J
And
I
think
we
we
should
I
mean
we
don't
have
another
steering
body
yet
for
the
the
students
project.
But
still
the
state
is
still
the
the
steering
committee
so
today
for
the
the
syrians
project
so
on
until
we
have
a
formal
leader
or
board
for
the
citizens
project
I
think
we
should
keep
to
say
at
least.
A
Yeah
so
so
far,
indeed,
we
have
been
like
having
like
discussions
that
are
not
specifically
not
necessarily
specific
to
see
the
events
but
more
in
general
to
events
and
architecture
in
the
Sig
events
group
or
more
related
to
Administration
and
governance
there
and
the
more
technical
discussions
in
the
city
event
working
group,
but
yeah.
We
could
consider
merging
the
two.
H
And
I
have
not
attended
an
interoperability
Sig
meeting
in
quite
some
time,
I'm
assuming
they're,
still
meeting
correct.
G
H
Okay,
because
I
feel
like
sometimes
at
that
interoperability,
Sig
and
the
events
CD
events
project,
maybe
should
be
a
little
more
closely
engaged.
G
Yeah
recently,
we
just
started
well
getting
ready
to
start
another
topic
that
I'm
not
sure
is
as
close
to
events
as
in
the
past.
A
A
Sorry,
I
think
we
still
need
to
one
thing
that
we
we
should
probably
decide
is
what
what
to
do
for
groups
where
we
don't
have
a
sponsor
anymore,
I,
guess
the
the
idea
of
the
sponsor
is
mainly
to
to
someone
that
make
sure
we
have
updates
from
the
sigs,
and
we
we
have
a
kind
of
roadmap
or
in
a
visibility
on
what
the
the
C
mission
is
and
what
is
achieving
is
the
the
sake
still
needed
is
still
actual.
Do
we
need
to
have
like
the
six
that
we
have
today?
E
I
would
I
would
say
that
we,
like
Emil,
said
we
get
through
the
two
governance
documents
that
we
have
in
Flight
right
now
around
the
elections
and
stuff,
and
then
just
keep
looking
for
volunteers
for
go
the
volunteer
route
for
a
little
bit
and
then
once
we
get
those
pull
requests
done
for
the
election
stuff
and
those
other
docs
that
we
come
back
around.
That
would
probably
be
like
two
to
four
weeks
that
we
can
then
take
a
look
at
what
we
do
for
the
sponsors
and
the
the
documenting.
H
E
E
Yeah
yeah,
so
I
could
have
like
Sasha
Wharton
from
ortilius
who's,
not
on
the
TOC,
be
involved
with
the
the
Spinnaker
as
a
you
know,
a
way
to
do
another
way,
another
way
to
get
an
outside
view
into
what
the
the
Project's
doing
and
then
Sasha
would
then
report.
What's
going
on
through
a
Toc
representative,
just
just
a
thought.
A
J
No,
no,
not
really
I
mean
I
would
not
be
in
silicone
myself.
So
I
will
be
able
to
to
join
that
meeting.
But
I
guess
you
as
the
chair
will
not
be
there.
I
I
think
it
is
it
at
8
00
a.m.
Local
time
Pacific!
Yes,.
A
B
A
Yeah,
that's
a
very
good
point
in
mark
any
other
comment.
A
A
Okay,
so
we'll
send
then
a
cancellation
email
for
the
meeting,
and
if
there
is
anything
we
need
to
discuss,
we
can
set
up
something
adult
or
do
it
asynchronously
for
the
mailing
list,
all
right,
yeah,
thanks
everyone.
A
We
are
over
time
now
so
but
see
some
of
you
in
person
there
in
Silicon
and
looking
forward
to
meet
everyone
either
virtually
or
in
person.
In
our
next
meeting.