►
From YouTube: Keynote: Technical Oversight Committee Q&A
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
Keynote: Technical Oversight Committee Q&A - Cameron Motevasselani, Armory; Praseeda Sathaye, AWS; Gopinath Rebala, OpsMX; Dadisi Sanyika, Apple & Moderated by Kelsey Hightower, Google
A
B
Oh
hi
I'm
a
principal
Solutions
specialist
solution,
architect
at
AWS
I
work
with
the
AWS
customer
strategy,
customers
to
help
them
with
the
containerization
and
application
modernization.
So
my
role
in
Spinnaker
over
here
is
like
I've
written
a
couple
of
blogs
on
Spinnaker
operator
with
eks,
and
we
have
a
team
over
here
also
who
contributes
to
Spinnaker
and
we
help
our
customers,
who
actually
use
Spinnaker
as
the
delivery
mechanism.
C
Right
on
yeah,
hey
everyone,
I'm
Cameron,
Moda
vaselani,
just
a
quick
note.
This
is
not
the
entire
technical
oversight
committee
here,
where
about
half
of
the
half
of
the
group,
so
just
wanted
to
put
that
out.
There
I'm
an
engineering
manager
over
at
Armory
I've,
worked
on
a
bunch
of
different
projects
on
the
Spinnaker
in
the
Spinnaker
community
and
we're
Armory
is
a
commercial
provider
of
of
Spinnaker.
D
A
C
A
C
I'm
happy
to
talk
to
you
know:
what's
the
purpose
of
the
governing
board,
we
need
to
come
up
with
a
plan
and
a
vision
for
Spinnaker
and
for
the
future,
not
just
coming
up
with
a
plan
and
a
vision
and
then
and
then
telling
the
community
to
to
do
it.
We
need
to
staff
and
help
make
this
Vision
a
reality,
so
that
that's
what
we're
here
to
do
and
that's
what
I
hope
that
we're
going
to
be
talking
a
bit
more
about
today.
C
So
what
was
my
motivation
for
joining
the
community
really
revitalizing
the
community,
as
you
can
see
here,
we've
we're
in
we're
acting
on
that
plan
right
now.
So
it's
pretty
it's
pretty
exciting.
We
want
to
reduce
the
technical
debt
as
well
and
really
lower
the
barrier
of
Entry
to
develop
on
Spinnaker,
that
is
to
say,
contribute
to
the
Spinnaker
code
base
and
increase
contributions
and.
A
D
You
know,
Spinnaker
is
a
wonderful
product,
it's
a
really
Dynamic
community
and
it
was
doing
great
things
and
we
want
to
just
contribute
to
that.
We
have
been
contributing
to
Spinnaker
for
quite
some
time,
and
we
just
really
want
to
extend
our
involvement
in
the
community,
help
lower
that
bar
to
entry,
and
you
know,
keep
it
growing
and
keep
it
moving
forward.
A
The
question
is
about
the
oversight.
Community,
you
work
at
a
very
large
cloud
provider.
You
have
your
own
tools
as
well,
and
you
mentioned
earlier
that
you
have
customers
that
use
Spinnaker
and
again
you
could
just
easily
support
those
customers.
What
kind
of
puts
you
to
join?
What
influence
you
to
join
the
community
and
serve.
B
On
this
community
as
well
yeah,
sorry
about
that
I,
didn't
hear
the
question
so
as
being
a
solution,
architect
and
specialist
I'm
being
approached
by
not
only
you
know,
strategic
customers,
but
also
the
other
customers
who
are
interested
in
trying
Spinnaker,
and
the
first
thing
is
like
how
can
I
get
started
with
that
very
easily
right?
So
I
was
thinking
that
we
have
this
new
eks
blueprint,
which
we
are
going
to
announce
in
the
reinvent.
B
E
All
right,
it
is
option
X,
we
work
with
lots
of
customers
who
are
using
Spinnaker,
and
we
see
some
of
these
common
themes
recurring
in
terms
of
Spinnaker
extensions
or
increasing
the
scalability,
and
things
like
that,
so
the
community
is
already
contributing
to
those
and
we
are
also
actively
contributing
is
so
to
bring
in
a
Prosperity
with
multiple
people.
We
were
talking
about
the
users
and
contributors
and
leaders,
so
we
also
want
to
bring
that
perspective
in
bring
more
users
in
have
them
contribute
to
the
system.
So
we
want
to
take
that
leadership.
A
A
What
plans
do
you
have?
What
are
you
governing?
What
plans
do
you
have
and
then
what
influences
those
plans?
Do
you
all
go
off
into
like
your
own
private
slack
Channel
and
make
this
stuff
up
like
what
influences
things
that
go
into
the
plans
that
you
have?
So
what
are
the
plans
and
what
influences
those
plans?
Whoever
wants
to
start.
C
So
that
that's
a
great
question:
what's
what's
the
plan
and
how
did
we
come
up
with
the
plan?
So
we
when
we,
when
we
created
the
technical
oversight
committee,
we
we
did
a
couple
things.
We
we
took
a
look
at
the
existing
landscape
with
our
governance
structure
and
said:
hey
this
isn't
working.
Let's,
let's
combine
the
steering
committee
and
the
technical
oversight
committee
together.
So
we
can
be
a
bit
more
agile
in
making
decisions
and
then
making
it
happen
so
coming
up
with
the
plan.
C
What
what
do
we
want
to
do
and
make
happen?
That's
kind
of
like
the
starting
point,
so
we
took
a
poll
amongst
all
of
ourselves.
Why
did
we
join
the
community
and
why
did
we
want
to
see
happen
in
the
community
and
we
took
those
answers
and
that
really
is
driving
our
roadmap
in
our
future,
so
I
think
we're
going
to
keep
hearing
those
same
kind
of
themes
of
developer
experience,
lowering
the
barrier
of
entry
and
then
making
Spinnaker
a
bit
more
robust
and
scalable
a
true
multi-cloud
solution.
A
C
Yeah,
there's
no
more
steering
committee,
it's
just
the
technical
oversight
committee
and
what
we
had
seen
was
the
the
participation,
especially
over
the
pandemic,
the
participation
from
those
those
groups
and
those
committees
just
kind
of
fell
off.
So
we
really
want
active,
engaged
members
who
again
are
contributing
to
the
code,
and
that's
that's
actually
how
we
came
up
with
this
committee
is
we
took
a
look
at
who
are
some
top
contributors,
who's
interested
in
the
community
and
participating
and
from
there.
F
One
of
the
things
that
I've
seen
not
just
in
Spinnaker
but
like
any
Cloud
native
tool,
is
like
a
road
map
and
that
usually
gives
us
confidence
as
to
when
we're
building
on
this
platform
that
it's
going
to
be
supported
for
a
while.
It
is
there
a
thought
about
revisiting
like
a
public
roadmap,
because
you
know
it's,
it
seems
like
to
link
off
to
somewhere
and
it
references
old
dates.
I
think
for
that
that'll
really
kind
of
give
confidence.
C
A
Totally
I'm
going
to
summarize
that
question
just
in
case
they
didn't
get
it.
You
know,
there's
a
road
map,
you
know
these
open
source
committees
and
if
you
look
at
the
current
roadmap,
there
are
things
like
dates
that
are
definitely
past
due.
It
probably
needs
to
be
revamped.
It
needs
to
be
refreshed.
What
are
your
thoughts
about
that
roadmap
and
actually
it's
one
of
our
questions?
A
E
There
are
things
happening
in
the
community
and
through
new
developments,
new
plugins-
that
is
also
scalability
improvements
that
are
happening,
but
the
documentation
site
itself
is
not
being
kept
up
up
to
what
is
being
released.
So
recently
we
made
releases
with
128
129.
There
were
features
that
were
released
in
those
releases,
but
they're
not
documented.
So
that's
definitely
one
of
the
issues
where
we
will
address
document
what's
coming
as
well
as
what
has
already
been
released.
B
Yeah
I
totally
agree
on
that
and
that's
the
first
thing
documentation,
because
when
myself
I
started
with
the
Spinnaker,
that
was
a
challenge
for
me
and
I.
Definitely
think.
As
a
committee,
we
have
the
responsibility
to
improve
on
that
and
plus,
like
our
customers,
who
come
to
ask
us
like
hey.
Can
you
make
the
workflow
of
integration
with
this
plugin
easy
like
Lambda,
plugin
and
other
plugins
yeah?
We
don't
have
anything
to
point
them
like
this
is
how
what
the
process
is.
B
D
The
documentation
Sig
is
meeting
tomorrow.
I
just
want
to
point
that
out.
So
absolutely
this
is
about
making
the
the
barrier
to
entry
lower.
First,
that's
top
priority
fixing
the
things
like
the
documentation,
finding
ways
to
make
Spinnaker
accessible
to
everyone.
So
you
can
begin
to
contribute
beyond
that.
It's
dealing
with
the
other
side
of
that
issue
like
scalability,
and
things
like
that
and.
A
A
Documentation
also
kind
of
signifies
consensus
when
I
see
a
public
roadmap
with
up-to-date
dates
and
commitments
and
names
by
those
commitments,
I
think
people
get
this
feeling
like
okay,
this
is
what's
coming,
I
have
an
opportunity
to
debate
and
discuss
those
things
and
then,
when
there
is
healthy
documentation,
it
feels
like
hey
you're,
communicating
that
these
things
should
actually
be
used
versus
some
back-end
thing
that
may
apply
to
a
small
set
of
people
I'm
going
to
keep
going
with
this.
Anyone
do
you
want
to
add
anything
else
to
that
yeah.
C
Yeah
I
do
so
part
of
you
know.
Revitalizing
the
community
and
coming
up
with
a
plan
is
to
get
consensus
and
we're
we're
in
that
process
right
now.
So
one
of
the
things
to
answer
your
your
question
earlier,
one
of
the
things
we
want
to
do
is
revive
the
six,
so
Sig
participation
has
been
a
little
bit
lower
than
we'd
like.
So
we
want
to
come
up
with
the
plan
of
action
and
then
start
Staffing,
those
six.
C
A
Yeah
I
think
it's
a
good
place
to
step
up,
for
you
know,
users
of
the
particular
product.
If
you
really
want
to
see
these
documentations
get
written,
you
might
have
to
write
them
right.
That's
a
that's
the
thing
that
I
think.
Sometimes
we
Overlook
I'm
gonna,
go
to
the
next
question
here
and
we're
going
to
get
a
little
deeper
and
this
medical
release.
Cadence
has
slowed
last
year
and
a
lot
of
times
when
you
know,
if
you
use
any
popular
open
source
project,
we
look
at
those
GitHub
Stars.
C
So
I
did
take
a
whack
at
trying
to
just
fix
what
was
currently
there
and
update
it.
It
turned
out
to
be
a
very
huge
problem.
A
really
big
project,
I
I,
was
actually
going
through
some
old
Google
Docs
that
predated
my
time
on
the
Spinnaker
project
and
I
saw
the
previous
developers
and
leaders
saying
in
comments.
Oh,
this
is
going
to
be
a
big
project
right.
C
It
was
very
much
something
that
hey
it's
not
broken,
so
why
fix
it?
It
accomplishes
our
needs
and
we
can
make
releases.
Bintry
went
down
and
our
release
process
essentially
shut
down
the
automated
release
process.
I'll
say
so
thanks,
huge
thanks
to
Salesforce
David,
Byron
and
Carl
Skuse,
I,
hope,
I'm,
saying
his
last
name
right.
C
They
basically
came
in
and
totally
revamped
our
release
process,
so
we
have
been
making
releases
a
lot
more
often
regularly
now
so
that
that's
been
going
well,
there
is
still
room
for
improvement,
so
we
have
a
changelog
that
has
new
features
and
breaking
changes
and
all
of
that
good
information
on
the
website.
We
want
to
start
promoting
that.
The
fact
that
hey
there's
a
new
Spinnaker
release
take
a
look,
so
we
want
to
start
doing
blog
posts,
videos,
Etc.
We
also
want
to
improve
the
testing
for
open
source
right
now.
C
E
David
and
Carl
to
bringing
this
up
to
date,
it
definitely
improved
a
lot
in
the
last
few
months
we
did
make
128,
129
and
130
is
coming
soon.
So
that's
a
big
Improvement
in
and
the
testing
is
another
piece.
One
of
the
reasons
why
we're
not
able
to
bring
in
more
things
into
it
faster
is
being
able
to
have
that
integration
test
cleanly
done
with
all
the
new
plugins
and
extensions.
We
want
to
give
that
Community
a
chance
to
test
their
own
extensions
as
well.
E
So
that's
a
big
on
priority
for
sure
and
so
we'll
make
that
happen,
and
we
should
expect
better
review
process
as
well.
All
the
contributions
that
are
coming
in
go
back
into
the
open
source
and
gets
released,
not
just
major
releases.
We
may
even
look
at
patches
if
something
breaks
in
between
Community
fines.
We
want
to
be
able
to
respond
faster
and
make
patch
leaders.
A
Yeah
I
mean
I
think
a
lot
of
times.
People
underestimate
the
responsibility
now
of
a
popular
open
source
project.
You
know
when
I
got
into
open
source
years
ago,
putting
something
on
GitHub
or
anywhere
just
making
it
available
was
like
the
bar.
Now
you
got
to
have
a
logo
release
Cadence
videos
user
conference.
So
a
lot
has
changed
since
then,
which
kind
of
moves
me
to
my.
A
Lots
changes
in
these
communities
communities
borrow
ideas
from
each
other
as
we
should,
but
then
new
projects
come
up,
especially
in
the
CD
space,
and
a
lot
has
evolved
since
Spinnaker
first
came
out.
So
how
does
spinner
interact
with
the
other
tools
in
the
space
right?
We've
seen
a
big
movement
towards
declarative
tools
as
new
platforms,
deployment
targets
come
out
like
kubernetes,
you
see,
tools
come
out
that
are
hyper
focused.
We
saw
that
in
a
previous
talk.
So
how
do
you
all
think
about
that
in
general?
A
B
So
we
can
start
as
I
mentioned
before,
so
we
are
looking
towards
I
have
another
session
at
three
o'clock
or
one
o'clock,
I
guess
with
Spinnaker
operator
and
using
the
customize
how
we
can
deploy
this
financial
service
in
eks.
So,
as
I
mentioned,
like
probably,
that
will
be
the
best
start
from
our
site,
like
from
AWS
side,
to
contribute
towards
that
via
the
eks
blueprint
and
I.
B
Think
like
giving
more
information
and
insight
to
what
we
have
developed
so
far,
like
my
colleagues
have
developed
a
key
along
with
the
customer.
So
that
is
one
area
where
I
see
that
we
could
do
more
like
a
marketing
or
visibility
as
part
of
this
Toc,
so
that
they
can
get
some
information
on
those
plugins.
So.
C
Yeah
one
of
the
key
key
value
propositions
of
Spinnaker
is
how
interoperable
it
is
with
different
pieces
of
technology.
So
we
saw
the
Argo
integration
earlier
and
I
think
that's
becoming
a
more
and
more
common
thing
that
we'll
see
Spinnaker
and
Argo
I
definitely
believe.
Spinnaker
is
an
and
product
because
it
does
integrate.
So
well
with
other
best-in-class
tools.
C
C
They
used
to
be
you
know,
hardware
and
then
virtual
machines,
and
now
kubernetes
and
I
mean
what's
next
right.
Does
the
existing
tooling
support
moving
from
one
platform
to
another,
Spinnaker
does
and
that's
kind
of
one
of
the
the
the
great
things
about
it?
Is
it
solves
your
issues
today
and
it
can
help
support
your
issues
tomorrow
as
well.
E
Strengths,
it's
a
fairly
good
way
of
constructing
the
workflows
and
it
has
pretty
strong
deployment
credentials
with
the
cloud
environments
like
AWS
and
even
with
kubernetes
I.
Think
the
Home
Depot
originally
tried
to
implement
a
scalable
but
limited
feature
set
that
allows
the
ease
of
use
of
in
terms
of
resources,
and
we
added
few
things
to
it.
We
also
implemented
something
like
hey.
You
can
separate
out
your
Cloud
environments
and
run
individual
Cloud
instances
for
AWS
and
kubernetes
all
within
the
same
Spinnaker.
E
So
there
are
a
bunch
of
strengths
that
Spinnaker
has
and
it
brings
to
the
table
for
multi-cloud
environments,
but
there
are
things
like
the
declarative
things
that
are
improving
and
also
the
interoperability
that
other
tools
that
are
coming
in
in
the
ecosystem.
When
you
look
at
large
Enterprises
there's
interactions
that
needs
to
happen
with
those
we
can
do
it
as
an
extensions,
but
we
also
can
look
into
standards
like
that
cloud.
Events
that
the
DC
was
also
mentioning
and
see
how
we
can
make
it
a
better
tool.
E
So
what
we
look
for
is
use
the
strength
of
the
Spinnaker
and
there
is
a
big
Community,
there's
deployed
at
a
very
large
scale
going
forward.
Can
we
make
it
easy
to
integrate
with
new
systems
that
are
coming
in
or
existing
systems
with
interoperable
standards?
So
that's
a
what
would
be
one
of
the
focus
that
we
will
have.
A
Yeah
I
think
one
big
thing
that
the
community
wants
typically
is
to
pay
attention
to
in
general,
is:
can
you
scale
down
right,
I?
Think
a
lot
of
systems
evolve,
maybe
towards
the
Enterprise
use
case,
so
much
so
that
you
have
the
potential
to
leave
the
common
use
case
of
the
simpler
use
cases
behind
to
be
able
to
solve
some
of
these
Enterprise
things
as
this
technical
committee.
Do
you
all
think
about
that
at
all?
If
anyone
wants
to
weigh
in
on
that,
I
think
that's
important,
because
I
do
think.
D
A
G
C
Yeah
so
far,
the
the
meetings
that
we've
had
have
been
at
roughly
a
monthly
Cadence.
We
do
want
to
make
that
more
of
a
monthly
Cadence,
let's
say
but
yeah.
We
do
want
to
start
publishing
like
to
Joel's
Point
earlier
the
roadmap
and
the
vision,
I
guess
what
I
would
say
is
we're
still
kind
of
nailing
that
down
and
once
we
do
it's
going
to
be
part
of
the
the
push
is
to
get
that
out
there
and
promote
that
I.
C
A
C
Totally,
yes,
yeah!
That's
a
that's
a
great
question!
So
there's
a
mailing
list,
a
Toc
at
Spinnaker,
dot,
IO!
We
are
also
in
slack.
We
don't
have
a
public.
Well,
we
have
a
governance
Channel.
Actually,
that's
where
I
would
I
would
recommend
folks
to
to
join
in
and
and
leave
some
comments.
If
you
have
questions
comments,
concerns,
let
us
know.
A
C
A
I'll
tell
you
I've
been
a
part
of
a
lot
of
big
communities.
Big
and
small
and
transparency
goes
a
really
long
long
way,
especially
for
the
fact
of
just
being
knowing
that
these
meetings
are
occurring.
Knowing
that
important
things
are
being
talked
about,
and
actually
you
might
actually
inspire
someone
to
raise
their
hand
to
possibly
want
to
join
the
committee
at
some
point
in
the
future
or
being
able
to
relay
information
that
you
all
cover
in
a
more
real-time
basis
to
their
other
communities
right.
A
My
guess
is
you
all
can't
reach
the
entire
world
so
having
the
rest
of
the
community
be
able
to
relay
those
messages
from
you
know,
somewhat
of
an
authoritative
Source
can
go
a
long
way.
That's
a
fantastic
question
by
the
way,
thanks
for
asking
that,
if
you
do
have
a
question,
raise
your
hand
we'll
bring
the
mic
to
you,
we
have
about
10
more
minutes.
So
oh
we're
going
to
take
another
one,
fantastic,
introduce
yourself
and
ask
your
question.
Hi.
H
Definitely
like
some
IP
or
some
ways
of
doing
things
that
folks
kind
of
kind
of
hold,
close
and
I'm
wondering
if
there's
any
way
that
the
technical
oversight
Community
can
kind
of
coax
some
of
that
stuff.
Out
of
some
of
these
organizations
like
Netflix
that
that
you
know
when
they
have
these,
like
really
Advanced
kind
of
patterns
that
they're
they're
stumbling
across
the
same
things,
but
they're,
maybe
a
year
or
two
in
front
of
us.
Why
should
we
go
through
those
pains
if
they've
already
kind
of
solved
this
stuff
and
I
get
it
like?
H
A
E
Yeah,
so
what
what
I
heard
was
did
all
certain
patterns
that
most
of
the
organizations
are
going
through?
We
saw
this
Pinnacle
adopting
it
scale.
It
Clause
a
bunch
of
these
large
organizations
and
the
Spinnaker
users.
Now
they
are
hitting
that
some
of
those
limits
and
they're
looking
at
the
same
kind
of
problems.
So
these
are
some
of
them
are
features
that
are
going
to
the
open
source.
Some
of
them
are
patterns,
best
practices
and
things
like
that,
for
example,
if
you
want
to
take
a
multi-region
kind
of
deployment,
so
it's
Pinnacle.
E
E
For
the
last
one
year
the
there
has
been
a
little
slowness
because
of
the
pandemic
and
other
things
now,
with
the
steering
committee
and
Technical
oversight,
committee,
merging
and
also
revitalization,
of
special
interest
groups.
Usually
most
of
the
discussions
in
sigs
are
public.
Anyone
can
attend.
The
notes
are
all
public.
E
We
have
slack
channels
I,
think
we
start
going
through
that
motions
of
getting
the
participation
back
in
again,
so
that
will
also
bring
in
all
the
changes
that
are
happening,
making
it
easy
for
people
to
contribute
and
that
will
bring
back
the
discussions
and
slack.
Also,
we
can
have
a
much
more
lively
discussions
and
exchange
of
ideas
untruly
for
that.
C
Yeah
yeah
definitely
so
there's
there's
a
few
ways.
I
think
we're
tackling
that
so
plugins
are
are
a
huge
part
of
that,
but
they're
not
at
the
moment
perfect.
Let's
say
so:
we
we
adopted
a
framework
called
pfrj
and
it
relies
on
these
things
extension
points,
but
we're
kind
of
not
we're
kind
of
moving
away
from
the
extension
points
and
and
focusing
on
these
API
contracts.
So
we've
moved
a
lot
of
the
cloud
driver
contracts
to
the
cloud
driver,
API
package,
very
lightweight
package.
C
You
can
just
like
pull
it
into
your
plugins
and-
and
you
have
these
apis-
that
you
can.
You
can
use
and
rely
on
now
a
lot
of
those
apis
take
in
maps
of
maps.
So
it's
like
it's
as
a
developer.
I,
don't
know
what
I
need
to
put
in
there.
It
can
break
things,
so
we
really
need
to
start
adding
more
schemas
and
better
better
ways
of
communicating
between
a
bit
better
to
find
contracts.
C
Essentially,
I
know
that
there's
going
to
be
some
more
plug-in
updates
coming,
I,
know,
I,
believe,
there's
a
talk
later
about
plugins,
so
I'm,
looking
forward
to
seeing
more
of
those
updates.
Come
back
to
the
community,
I
I
definitely
have
seen
you
know,
people
will
make
updates
for
their
own
organization
and
then
they
need
to
contribute
it
back
to
Spinnaker,
and
it's
not
always
it's
not
always
trivial,
but
having
relying
making
public
and
explicit
what
those
API
contracts
are
and
then
hooking
in
to
them
yourself
and
allowing
others
to
then
build
on
it
too.
C
A
Can
imagine
it
being
a
nightmare
to
refactor
the
code
base,
cut
new
releases
and
being
worried
about
breaking
all
of
these
plugins
that
are
relying
on?
Who
knows
what
configuration
objects
being
passed
around?
Are
there
any
more
audience
questions
you're
right?
If
you
have
a
question
at
any
point,
raise
your
hand.
Maria
will
bring
the
microphone
over
to
you
I'm
going
to
get
to
the
last
question
that
we
have
schedule,
which
is
what
advice
do
you
have
from
contributors
that
want
to
get
more
involved
in
the
community
right?
A
D
Suggest
you
started,
of
course,
vinegar
IO
in
the
documentation.
We
have
some
information
about
the
guidelines
to
commit
and
also
the
slack
Channel
definitely
join
the
slack
Channel
It's,
a
Wonderful
Community
they're.
Very
welcoming-
and
you
know
just
just
talk
to
us
and
and
we
will
help
you
through
it
and
as
we
lower
the
bar
to
entry.
It's
good
to
know.
You
know
the
information
that
we
need
to
be
sure,
that's
in
the
documentation
and
make
sure
that's
available
for
you,
yeah.
C
D
C
As
the
DC
said,
slack
is
also
a
a
big
area.
There's
a
weekly
Spinnaker
office
hours,
every
Tuesday.
So
if
you
want
help
with
Spinnaker
getting
started,
trying
to
figure
out,
how
can
I
contribute?
That's
also
a
great
great
place
to
start
well,
it's
not
quite
confirmed
I
would
like
to
do
another.
We
did
a
Spinnaker
gardening
phase
in
the
past
and
I'd
really
want
to
do
that
again
next
spring,
so
April,
May,
I'm,
really
hoping
that
we
we
throw
another.
One
of
these
gardening
days
is
what
we
called
it.
C
It
was
basically
a
week-long
event
where
anyone
in
the
world-
and
we
did
have
worldwide
participation
in
it-
could
join
a
team.
You
might
not
know
other
people
who
work
on
Spinnaker
or
want
to
work
on
Spinnaker
hackathon,
so
you
you
get
placed
with
the
team,
and
then
we
provided
the
community
provided
mentors
to
help
out
teams
getting
started.
C
B
Have
anything
vinegar,
any
plugins
or
any
ideas?
Please
please
feel
free
to
share
to
this
team,
and
maybe
we
can
come
up
with
I
was
thinking
of
whatever
blogs
you
have.
We
could
share
it.
We
could
make
it
visible
as
part
of
this
community
and
maybe
adopt
it
as
best
practices.
So
those
are
some
options.
What
we
have.
E
A
Yeah
one
thing,
I
think
I've
seen
the
tragedy
in
a
lot
of
these
communities,
we're
all
using
this
stuff.
We're
all
learning
this
stuff,
but
very
few
people
actually
share
the
nuanced
details
right.
Maybe
you
only
share
the
success
stories.
Maybe
only
show
the
areas
where
it
absolutely
work
with
no
problems
but
I.
Think
if
you
have
the
time
or
the
ability
share
everything
you
can
like
how
you
install
it
that
little
puppet,
Chef
or
ansible
script
that
you
use
to
upgrade
it
and
make
sure
things
don't
break.
A
Maybe
you
have
a
different
set
of
design
patterns
for
dealing
with
plugins
and
having
them
yourself.
I.
Think
those
things
are
super
critical
because
if
you
think
about
it,
there's
only
so
many
Technical
Community
oversight
committee
members,
but
there
are
so
many
more
people
that
are
just
out
in
the
community
doing
this
stuff
in
production.
A
I,
don't
know
if
you
like
me
once
you
get
past
day,
zero
day,
two
and
three
all
about
production,
but
the
things
that
they
don't
tell
you
on
the
website,
nothing
against
the
website,
but
no
one
ever
puts
in
there
how
much
memory
you
really
really
need
in
production
and
when
it
falls
over
what
to
do
y'all
have
that
experience
so
share
it
in
any
form
that
you
find
comfortable
I'm
going
to
give
one
more
last
call
for
questions.
You
have
a
subset
of
your
technical
oversight
Community
here.
A
If
you
have
any
questions
this
is
your
opportunity
or
I'm
going
to
wrap
it
from
here.
It
doesn't
look
like
we
have
any
more
questions.
This
is
a
huge
responsibility:
you're,
not
just
managing
an
open
source
project,
you're,
also
managing
some
people's
livelihoods,
their
whole
profession.
So
no
pressure,
but
thank
you
for
your
service.
Let's
give
them
a
big
round
of
applause.