►
From YouTube: Cloud Native Live: TAG Contributor Strategy Livestream
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone
welcome
to
cloud
native
live
where
we
dive
into
the
code
and
community
behind
cloud
native.
I'm
taylor
dolezal,
head
of
ecosystem
at
the
cncf,
where
I
work
closely
with
teams
as
they
navigate
their
cloud
native
journeys.
Every
week
we
bring
a
new
set
of
presenters
to
showcase
how
to
work
with
cloud
native
technologies.
A
They
will
build
things,
they
will
break
things
and
they
will
answer
your
questions
in
today's
session.
We
have
quite
the
cloud
native
crowd,
as
you
can
see.
Catherine
dawn,
carolyn
and
josh
have
joined
us
to
talk
about
tag.
Contributor
strategy
now
tag,
that's
a
fun
game
to
play,
but
that's
not
what
we're
talking
about
here
today.
Tag
stands
for
technical
action
group
so
folks
that
get
involved
and
kind
of
work
on
different
aspects
throughout
the
cloud
native
community.
A
This
is
an
official
live
stream
of
the
cncf
and,
as
such
is
subject
to
the
cncf
code
of
conduct.
So
please
don't
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct.
Basically,
please
be
respectful
to
all
of
your
fellow
participants
and
presenters
be
excellent
to
one
another
with
that.
I
would
love
to
hand
it
off
to
the
team
to
kick
off
today's
presentation
and
discussion
team
with
that.
Please
take
it
away.
Welcome.
B
Awesome
well
thanks
so
much
for
the
intro
taylor,
and
so
we
are
very,
very
excited
to
be
able
to
spread
the
word
about
the
tech
contributor
strategy
today
and
I
am
joined
by
a
group
of
people
who
are
really
doing
amazing
work,
and
we
really
really
feel
that
more
maintainers
should
know
about
this.
So
that's
why
today
we're
going
to
discuss
why
there
is
a
tag
contributor
strategy.
If
you
need
one
hint,
we
do
think
you
do
and
how
you
can
participate
so
yeah.
B
There
is
a
lot
that
goes
into
successfully
maintaining
a
project
and
it
all
goes
way
beyond
code
and
docs,
you
have
mentoring,
cultivating
and
promoting
leaders,
marketing
your
project,
contributor
recruitment,
deciding
on
governance.
There
is
a
lot
of
things
right
and
most
of
these
things
are
not
necessarily
things
that
maintainers
are
have
previous
experience
with,
so
it
can
really
feel
overwhelming.
B
But
you
cannot
neglect
any
of
these
aspects,
because
that
will
negatively
impact
your
project.
So
how
do
you
handle
all
that
right?
You
are
a
developer,
you
you!
You
are
really
good
at
coding
and
docs
right,
but
the
good
news
is
you
really
don't
have
to
figure
it
out
by
yourself
right?
There
are
lots
of
projects
that
have
been
there
before.
Just
look
at
the
cloud
native
landscape.
How
many
open
source
projects
there
are
like
right,
so
no
need
to
reinvent
the
wheel.
B
Besides
we
live
and
breathe,
open
source
and
open
source
is
about
community
right,
so
not
only
within
your
project,
but
also
across
projects,
and
the
cncf
is
basically
the
home
for
all
our
projects,
and
it
provides
this
amazing
platform
for
us
to
connect
to
exchange
ideas,
learn
from
one
another
and
basically
to
build
a
thriving
ecosystem
of
successful
open
source
projects,
and
that
is
really
what
the
tech
contributor
strategy
is
about.
B
So
we
are
all
from
a
variety
of
cncf
projects
and
we're
committed
to
helping
your
project
succeed
right
and
basically,
what
the
tag
does
is
define
strategies
to
build
scale
and
retain
contributed
communities,
so
those
are
really
important
things.
So
our
ask
to
you
today
is:
please,
please,
please
don't
try
to
figure
it
out
on
your
own,
let's
connect
and
figure
it
out
together,
because
that
way
anyone
can
really
benefit.
B
So
I'm
going
to
share
my
screen
because
I
want
to
share,
show
you
our
website
here.
You'll
see
two
options
right
like
contribute:
it's
the
url
is
contribute
dot.
Cncf
here,
you'll
see
two
options:
we're
gonna
see
montes
today's
sessions
is
on
maintainers
and
I'm
gonna
show
you
a
little
bit
about
commun
the
community
section.
Here
you
will
see
some
guides
high
level
guides.
You
will
see
one
these
three.
Let's
start
with
a
community
crm
run
book
a
lot.
B
A
lot
of
people
don't
really
know
that
there
are
cr
community
crms.
You
may
know
it
from
sales,
but
these
can
be
really
really
helpful
to
manage
your
project.
So
here
you
learn
a
little
bit
about
what
community
crms
are
a
little
bit
like
some
tips
on
how
to
use
tags
and
like
some
recommendations
on
a
daily,
weekly
and
monthly
activity.
So.
B
Based
on
what
are
other,
if
you're
adopting
a
crm,
you
don't
have
to
start
from
scratch.
Right,
like
just
have
a
look
here,
see
what
has
worked
for
others
and
then
adapt
it
for
yourself
right
same
thing
with
project
health
measuring
your
project.
Health
are
important,
so
here
you
learn
all
about
that
and
specifically
how
to
make
sense
of
death
stats.
We
see
a
lot
of
people
who
kind
of
struggle
with
that.
B
So
here
you
will
learn
a
little
bit
what
to
look
at
right
and
then
you
have
things
about
responsiveness:
how
that
impacts,
health,
how
to
interpret
contributor
activity
and
lots
more
information,
so
really
really
good
place
to
start.
If
you're
interested
in
that
area,
then
there
is
the
contributor
growth
framework,
which
is
a
high-level
guide
on
yeah
that
provides
a
high-level
overview
of
how
to
how
to
grow
and
your
community
a
community
and
how
to
engage
more
with
them.
B
This
is
based
on
interviews
with
a
bunch
of
people
and
you
will
learn
about
how
to
motivate
users.
The
importance
of
honest
and
clear
communication
documentation
super
important.
Why
it's
important
and
the
human
factor
yeah
a
lot
of
these
things
will
sound
very,
very
common
sense
and
you
were
probably
you
had
a
gut
feeling
about
it
too,
but
it's
really
important
to
see
like
see
it
first
written
out,
because
it's
really
important.
B
It
sounds
very
it's
very
fluffy,
but
it's
very
important
because
that's
why
people
come
people
come
because
they
are
connecting
with
people
right
and
it's.
So
it's
good
to
see
it.
It's
good
to
see
that
what
other
projects
emphasize
and
so
on
then
you'll
hear
about
like
you,
you
can
read
a
little
bit
about
prs
like
how
to
manage
expectations
and
oops.
Then
engagement,
I'm
not
going
to
go
through
all
these,
but
incentivizing.
Contributions
like
the
contributor
ladder
is
very
important.
B
It's
very
important
for
people
as
they
join
a
whether
decide
to
which
project
to
contribute
to
kind
of
see
like
what.
If
I
start
contributing
where,
where
will
it
lead
me
right,
like
that's
like
having
that
visibility
is
really
motivating
right
and
then
not
no
code
contribution.
Non-Code
contribution
super
important:
you
don't
want
only
people
contributing
code,
that's
important
too,
but
you
need
people
to
help
on
slack
right
to
help
tell
the
story.
Those
are
really
really
important
too
and
then
long-term
contributions.
B
Gonna,
stop
sharing
and
basically
what
I
have
done
like
so
I
worked
on
the
crm
and
contributed
growth
guide,
and
it
really
was
what
it
really
was.
A
great
experience.
B
I
had
just
joined
the
linker
d
team
and
had
lots
and
lots
of
questions
right.
I
needed
guidance
on
how
to
grow
my
community,
our
community,
how
to
engage
with
them
and
there
wasn't
actually
something
ready
to
go
right.
But
what
the
tag
allowed
me
to
do
is
pick
people's
name,
that
I
would
have
otherwise
not
been
able
to
do
to
pick
right,
because
because
so
I
decided
to
create
a
guide
for
me
right
like
so.
B
It
was
basically
for
me
that
I
created,
but
also
it
would
be
available
for
anyone
who
needed
it,
but
my
main
motivation
was
for
our
project
right,
but
because
the
end
result
would
benefit.
The
community.
Maintainers
were
very,
very
happy
to
talk
to
me
and
they
were
very
generous
with
their
time
and
all
those
conversations
were
incredibly
valuable
and
I
got
a
lot
more
out
of
it
than
anyone
who
was
just
going
to
read
the
guide.
B
So
if
you
need
a
resource
that
is
not
available,
there
really
is
an
entire
community
to
help
you
build
it
and
because
chances
are,
if
you
need
it,
another
project
needs
it
too.
So
we
should
probably
build
it
and
make
it
available
for
any
anyone,
and
the
whole
process
for
me
was
a
huge
learning
curve
and
I
really
recommend
anyone
who
needs
something
to
kind
of
do
it
in
kind
of
the
tag
context.
B
Yes,
you
are
probably
wondering
it
will
take
some
time,
but
it's
it
honestly.
It
wasn't
a
crazy
amount
of
time
and
you
also
have
to
consider
that
it
will
probably
save
you
lots
of
time
down
the
line
because
you
gathered
so
much
information
that
has
been
validated
by
other
people
that
you're
not
flying
blind
anymore.
So
it
is
really
worthwhile.
So
you
put
a
little
effort
or
something
a
little
more
effort
at
the
beginning,
but
it
will
really
help
you
save
time
down
the
line.
B
So,
even
from
a
purely
egoistic
point
of
view,
it's
really
worthwhile
doing
it's
good
for
your
deck,
it's
good
for
the
community
and
it's
a
great
way
to
become
an
active
member
of
our
cross
project
community,
which
is
the
cncf.
B
So
I
hope
that
kind
of
got
like
provided
a
sense
of
what
the
tag
contributor
strategy
is
and
why
we
think
that
you
should
get
it
off
for
some
described
and
links
to
that
point
to
how
to
connect
and
so
on.
I'm
gonna
share
a
blog,
post
and
yeah.
I
know
anything
that
I
missed
dawn,
carolyn.
C
Josh,
well,
I
was
going
to
say
we're
going
to
continue
going
through
the
projects
of
the
tag
here,
but
if
you
have
any
questions
about
things
in
the
tag
about
recruiting
contributors
and
governance
and
running
your
project
and
connecting
with
other
maintainers
etc,
please
ask
them
in
chat
and,
and
we
will
field
them,
we
will
work
them
in
and
field
them
as
we
see
them.
E
Yeah,
that's
really
the
first
way
that
I
think
most
people
get
involved
with
the
tag
is
you
know
you
have
a
question
you're
like
I've,
gotten
to
the
point
where
I'm
supposed
to
have
a
diverse
group
of
maintainers,
and
I
have
no
idea
how
to
get
there
like
that's
one
of
the
big
ones.
To
be
honest,
then
understanding
how
to
set
up
governance
and
what
we
welcome
people
to
do
and
what
what
people
have
been
doing
so
far
is
just
coming
to
our
meetings.
We
meet
every
thursday.
E
You
can
see
it
on
the
cncf
calendar.
If
you
look
for
contributor
strategy
and
just
drop
in
and
chat,
it's
it's
pretty
much
office
hours
every
week.
In
addition
to
just
like
a
standard
agenda,
we
run
so
it's
never
an
imposition.
You
can
always
just
drop
in
ask
questions,
just
lurk
and
kind
of,
listen
and
see.
What's
going
on
and
oftentimes,
that's
a
great
way
to
just
realize
we're
asking
questions
about
something
that
you
may
know
and
that's
how
a
lot
of
people
eventually
become
contributors.
E
They
didn't
like
show
up
one
day
and
they're.
Like
look,
I
wrote
this
wonderful
thing
here.
You
go
usually
it's
in
reaction
to
seeing
the
types
of
questions
that
projects
are
bringing
or
the
things
they're
struggling
with,
and
realizing.
You've
already
thought
about
this
a
bit
and
have
some
suggestions.
A
A
A
Try
it
demo
it
and
then
kind
of
step
up
your
involvement
in
terms
of
as
time
goes
on,
like
has
have
folks
found
that
helpful,
or
are
there
any
other
tips
or
tricks
that
you
might
be
able
to
give
to
folks
kind
of
looking
to
get
more
involved
or
those
that
are
curious?
I
know
that
getting
involved
in
open
source
and
things
like
that,
it's
not
like
you
have
to
jump
in
and
immediately
rewrite
the
orchestrator
for
kubernetes.
There
are
many
other
ways
to
help.
E
Source
project
is
going
to
be
really
important:
okay,
great
okay.
So
if
you've,
if
you're
a
maintainer
or
an
active
contributor
or
you've
tried
to
you've
you've
participated
in
running
a
project
most
likely,
you
already
have
the
experience
needed
to
say
this
is
what
I've
done.
This
is
what's
worked.
This
is
what's
gone
horribly
and
maybe
also
just
point
out
gaps.
We're
like
I
don't
have
an
answer,
but
this
seems
like
a
common
problem
that
multiple.
E
Projects
have
it's
less
about
okay,
first,
I'm
gonna
run
kubernetes
before
I
try
to
contribute
to
kubernetes.
It's
not
quite
the
same
thing
with
with
the
tag.
Another
difference
is
that
oftentimes,
it's
really
easy
to
not
make
a
commitment
to
being
a
contributor
every
week
or
all
the
time,
but
to
drop
in
share
your
experience
and
that's
valuable
to
us,
and
it's
not
considered
like
a
one-off
low-value
contribution.
E
Oh
that's,
useful
or
maybe
you've
come
up
with
an
amazing
way
to
like
curate
good
first
issues
for
your
project,
and
you
want
to
share
that.
Just
dropping
that
in
chatting
with
us
and
getting
that
content
even
bootstrapped
and
started
is
a
useful
contribution,
even
if
you
don't
have
the
time
to
come
back
week
after
week,
and
that's
not
really
expected,
though.
Obviously
you
know
we
love
it.
If
people
have
fun
and
want
to
keep
contributing.
A
Awesome,
thank
you
so
much
for
that
distinction.
I
think
it's.
It's
really
helpful
to
know
that
and
and
definitely
want
people
to
to
feel
that
that
sense
of
welcome
to
it
with
getting
involved
and
kind
of
knowing
like
it's.
Okay,
if
you
miss
a
meeting
or
two
life
happens,
but
we
still,
we
still
value
having
those
conversations
cool.
Thank
you.
Thank
you.
Yeah.
B
I
think
starts
just
with
as
little
as
just
having
a
question
and
sharing
it
there
and
then
to
like
building
a
guide
or
whatever
right
like
anything
and
anything
in
between.
So
I
I
don't
know
I
feel
like,
sometimes
especially
with
smaller
projects.
You
probably
feel
alone
with
certain
things.
It's
like
it's
good,
just
like
also
like.
I
think
it
just
feels
good
to
just
connect
with
other
people.
B
You
know
and
exchange
ideas
like
with
anything
else
right
like
so
there
is
that
value
right
and-
and
if
and
I
really
like,
the
idea
of
that
cross
project
community
right
because,
like
we
talk
all
about
community
and
open
source,
but
it's
like,
like
a
lot
of
people,
keep
in
their
own.
It's
like
we
can
learn
from
so
much
from
one
another
right
and
like
creating
that
that
internally,
I
think
that's
incredibly
valuable,
and
I
think
I
so
that's
why.
B
E
So
I
would
like
to
talk
about
concrete
ways
that
we
need
help
right
now,
so
you're
like
I'd
love,
to
contribute
honestly,
like
this
sounds
a
little
vague.
Let's,
like
get
specific
here,
I
have
a
slide
that
kind
of
calls
out
where
we're
looking
for
help.
E
We
just
started
a
new
initiative
called
community
infrastructure,
and
the
idea
is
that,
let's
say,
for
example,
that
you
want
to
keep
a
list
of
contributors
up
to
date
on
your
readme
or
on
a
separate
page
in
your
repo
and
really
call
out
and
thank
everyone,
who's
helped
your
project
out.
If
you've
ever
looked
into
this,
you
know,
there's
probably
like
16
different
solutions.
Four
of
them
are
unmaintained.
Each
one
has
different
quirks.
E
These
are
the
types
of
things
that
we'd
like
to
look
at
and
go,
which
ones
have
been
working
well
for
people
and
maybe
have
a
project.
Five
projects
say:
we've
all
been
using
this
github
action
or
we've
been
using
this
workflow.
This
is
why
it
works
for
us,
because
we're
a
big
project
or
a
small
project,
and
you
kind
of
call
out
what's
unique
about
us
and
how
this
solution
works.
Well
for
us,
and
so
we're
looking
for
maintainers
to
share
what
they're
using
to
support
their
community.
E
Now
I
know
the
the
acronym
there
is
ci,
but
we're
definitely
not
talking
about
ci
cd
or
build
pipelines
or
anything
like
that.
We're
looking
for
your
experiences
and
tips,
running
an
open
source
project
and
supporting
the
project
itself,
all
the
meta
stuff.
That
kind
of
just
needs
to
happen
all
the
invisible
work
that
goes
into
running
your
project,
so,
for
example,
kubernetes
huge.
E
Obviously
they
have
lots
of
resources,
lots
of
people
to
be
able
to
help
run
the
community
one
of
the
things
that
they
have
is
pro
and
if
you've
ever
looked
into
like
wow,
I
want
to
be
like
kubernetes.
Kubernetes
has
a
great
way
for
people
who
don't
have
right
access
to
the
repository
to
be
able
to
do
things
like
help
label
things,
triage
issues,
review,
pull,
requests,
just
coordinate
and
figure
out
who
are
the
three
to
five
people
who
should
be
reviewing
the
pr,
and
I
mean
gosh,
just
a
million
other
things
right.
E
Prow
is
definitely
like
a
kitchen
sink,
but
as
a
smaller
project,
when
you
think
about
well,
how
do
how
do
I
have
something
like
that?
I
can't
run
like
prowl
on
a
cluster
all
by
myself
somewhere,
so
we're
looking
at.
E
Can
we
take
the
functionality
of
prow
and
put
it
in
a
github
action,
which
is
a
lot
easier
and
more
practical
for
one
to
two
maintainer
projects
to
be
able
to
run
themselves
and
get
some
of
the
benefits
of
workflows
and
processes
that
things
like
kubernetes
has
figured
out
but
scaled
down
for
little
projects,
so
we're
looking
for
you
know,
advice
processes,
actual
github
repos
that
are
out
there
like.
E
I
found
one
that
already
existed,
that
does
prowl
in
a
github
action,
and
so
I've
been
contributing
to
it
and
trying
to
help
get
it
to
the
point
where
it's
a
little
closer
to
what
what
prow
really
does
and
so
we're
looking
for.
Do
you
have
a
pet
project
like
that?
Are
you
using
one
of
these
with
your
with
your
project?
E
So
even
if
you
don't
actually
have
solutions,
maybe
you
just
have.
This
is
a
problem
for
me
and
I
don't
know
how
to
fix
it
and
hear
all
the
weird
janky
things
I
do,
but
it
sucks
and
it's
horrible,
that's
great
feedback,
because
if
we
hear
that
from
two
or
three
projects
we
could
go,
maybe
we
should
be
looking
for
solutions
in
this
area
and
then
sharing
that
information
back
to
the
wider
cncf
community.
E
We
don't
have
like
good
first
issues
and
things.
What
would
be
the
best
way
to
start
is
coming
to
the
contributor
growth
working
group.
I
think
we'll
be
able
to
post
links,
I
think,
to
our
calendar
that
would
I'll
come
over
the
link
and
put
it
in
chat
here
and
so
contributor
growth
we're
the
ones
who
are
kind
of
working
on
this
initiative
and
we're
still
like
the
brainstorming
phase
of
going.
E
What
projects
should
we
be
talking
about?
What
projects
are
people
using
we're
still
trying
to
just
like
aggregate
all
that
information
and
then
pick
out
one
or
two
places
where
we
can
focus?
I
can
provide
a
link
to
the
prow
github
action
in
chat
here.
That's
something
I've
been
contributing
to
on
and
off
for
a
couple
months,
but
I
think
it
has
a
has
a
lot
of
promise
and
that's
somewhere
where
we're
going
to
be
focusing
very
soon.
But
I
don't.
A
I
just
posted
the
cncf
community
calendar.
Thank
you
so
much
catherine
for
for
sourcing
that
I
know
that
I'll
post
to
well
students
to
a
couple
different
platforms.
I
think
linkedin
might
not
get
these.
I
know
twitch
and
youtube
will
also
for
those
of
you
watching
on
linkedin,
recommend,
checking
out
cncf.io,
calendar
or,
or
you
know,
feel
free
to
reach
out
or
drop
questions.
If
there's
anything
you
want
specifically
and
I'll
try
to
help
out
on
that
front,
but
keep
the
questions
coming,
keep
the
conversations
going.
This
is
all
fantastic.
E
Yeah,
so
I
think
dawn
did
you
want
to
talk
about
templates?
Next,
we
have
some
resources
that
kind
of
help
people
get
started
with
making
governance
docs
contributing
guides.
Things
like
that.
D
Yes,
I
would
love
to
share
some
templates,
so
catherine
earlier
went
over
some
of
the
the
resources
that
we
have
around
community
and
we
also
have
some
similar
resources
around
governance.
So
you
know
how
do
you,
how
do
you
come
up
with
a
governance
model
to
select
leadership?
How
do
you
build
things
like
mission,
scope
and
values
into
your
governance
model,
and
so
we
have.
We
have
these
resources
along
with
the
ones
that
that
katherine
mentioned
and
the
templates
really
are
kind
of
an
artifact
out
of
the
resources
that
we've
been
building.
D
D
What
I
wanted
to
start
with
just
kind
of
you
know
running
lists.
There
are
some
that
are
really
really
pretty
important,
so
like
the
the
contributing
template,
for
example,
and
we
actually
have
a
whole
resource
written
around
around
how
to
make
a
contributing
guide.
So
we
have
a
template
that
goes
along
with
this,
but
this
document
itself
explains
exactly
how
to
fill
out
the
template.
D
How
what
to
put
in
your
you
know
in
in
your
document.
It
gives
you
some
ideas
for
ways
that
people
can
can
contribute.
It
talks
about
meetings,
finding
an
issue
asking
for
help.
You
know
pull
request
lifecycle,
so
it
gives
you
a
lot
of
options
for
your
contributing.md
template,
because
this
is
something
that,
let's
face
it
like
no,
no
two
projects
are
going
to
have
the
exact
same
structure
for
a
contributing
guide.
So
this
will
help
you
all
of
the
things
that
you
really
need
to
put
into
your
contributing
md5.
D
Setup,
this
is
something
that
I
see
missing
from
way
too
many
contributing
files,
and
it's
super
important,
because
if
people
want
to
contribute
to
your
project,
they
probably
need
to
set
up
their
development
environment
and
then
other
kind
of
logistical
things
like
signing
your
commits
pull,
request
checklist
and
we
also
have
at
the
bottom
of
this
file
several
really
good
examples
that
you
can
look
at.
So,
if
you're
a
little
more
driven
towards
the
the
examples.
That's
that's
a
good
place
to
start.
E
E
The
people
who
worked
on
this
document
went
through
and
looked
at
existing
cncf
projects
and
just
open
source
projects
in
general
and
said
who
do,
we
think,
is
a
good
model
for
this
type
of
thing,
who
has
a
really
great
contributing
guide
that
that's
that's
effective,
that's
helping
people
when
they
first
come
onto
the
project
and
enables
them
to
just
immediately
start
contributing,
and
we
would
compare
and
contrast
a
whole
bunch
and
go
what's
different.
What's
unique,
what
are
the
gaps
and
that's
kind
of
what
this
is?
E
Is
a
huge
smoosh
or
like
amalgamation
of
a
bunch
of
different
contributing
guides
from
different
projects,
but
there's
a
lot
there.
There
are
a
lot
of
cncf
projects
and
we
may
not
know
of
all
of
them.
You
know
you
can
see.
Some
of
these
were
pretty
popular
like
helm
was
maybe
a
gimme
kubernetes,
obviously,
but
there
may
be
smaller
ones
where
maintainers
have
innovated
and
come
up
with
new
things,
or
maybe
you
think
your
project
is
doing
something
different
that
you
don't
see
represented
here.
E
D
Yeah,
absolutely,
I
think
that
that's
really
important.
There
are
loads
of
different
ways
to
contribute
to
these
guides
and
we
we
also
really.
We
really
do
love
to
see,
see
examples
and
we
have
a
there's
a
project
template
repo
under
the
cncf
org
and
you
can
see
so
for
the
governance.
We
have
several
different
governance
options,
so
we've
broken
those
down
into
three
different
templates
because
they're
all
very,
very
different.
D
So
we
have
the
maintainer
template,
which
is
what
we
would
consider
sort
of
the
standard
governance
practices
that
most
projects
should
start
with,
but
we
do
have
other
templates.
So
if
you
look
at
the
elections,
template
for
example,
that
is
one
for
gigantic
projects
like
kubernetes,
who
needs
to
have.
You
know,
steering
committee
elections
and
you
know
technical
oversight
committees.
D
So
you
can
see
what
that
looks
like
and
right
now
we
do
have
you,
you
kind
of
have
to
view
it
in
view
the
raw
version
of
it,
because
we
have
comments
and
instructions
embedded
here
in
in
the
documents.
D
So
we
recommend
that
when
you
actually
look
at
it
for
your
project,
that
you
view
the
raw
one
but
we're
in
the
process
of
actually
taking
those
comments
and
augmenting
them
and
moving
them
to
a
how-to
document
like
I
showed
you
earlier
for
the
contributor
template.
So
that's
something
that
carolyn
started
doing
and
we
think
it's
a
fantastic
idea,
so
we've
been
working
on
that
for
some
of
the
other
other
templates
as
well.
So
that's
another
thing.
That's
coming
soon.
It's
also
another
thing
that
people
could
help
out
with,
but
emotionally.
C
If
you
yeah,
I
was
gonna,
say
if
you've
used
one
of
these
templates,
I
mean
the
thing
is
that
a
lot
of
these
templates
were
kind
of
you
know
first
or
second
drafts.
So
if
you
use
one
of
these
templates,
we
could
really
use
you
jumping
in
a
to
help
us,
you
know
documenting
the
template
for
for
what
people
need
to
know,
based
on
your
own
experience
with
it
and
also
helping
us
improve
the
template.
D
Yeah
for
sure,
that's
that's
a
great
way
to
contribute
and
and
help
us
help
us
make
the
resources
that
we
have,
even
even
better.
So
all
of
the
templates
have
a
value
section.
We've
got
some
examples,
but
you
need
to
replace
these
with
your
actual
values.
For
your
for
your
project,
we
have
a
section
on
on
maintainers.
D
It
talks
about
how
to
become
a
maintainer
meetings,
cncf
resources,
codes
of
conduct,
how
you
do
voting
so
how
you
make
decisions
in
the
project
and
all
of
this
can
be
found
in
in
the
template,
and
it's
really
designed
to
be
used
along
with
the
contributor
ladder
which
we
mentioned
earlier,
but
we
also
have
a
contributor
ladder
template.
So,
as
catherine
mentioned,
this
is
a
really
fantastic
way
for
contributors
to
be
able
to
see
how
they
might
move
up
into
a
project.
D
So
the
contributor
ladder
is
really
designed
to
go
along
right
with
and
all
of
the
governance
templates.
So
we
recommend
that
you
pair
the
governance
template
with
a
with
the
contributor
ladder
template
as
well,
and
it
talks
about
all
the
different
levels
in
your
project
and
what
it
takes
you
to
move
to
the
next
level,
which
is
really
important-
and
you
know
I
think,
we've
kind
of
talked
about
this
earlier.
D
But
you
know
one
of
the
best
ways
to
learn
about
something
is
to
to
help
teach
others
and
we're
always
looking
for
help
and
improvements
for
the
templates
and
the
how-to
guides.
So
if
you
have
a
passion
for
governance,
contributor
growth,
any
of
the
areas
that
we're
working
in
we
we
encourage
you
to
come
out
and
join
us.
E
Yeah,
I
think
sometimes
it's
easy
to
see
a
template
like
this
and
think
it's
done,
but
that's
definitely
not
the
case
for
basically
anything
that
our
group
produces.
You
know
the
cncf
isn't
static.
None
of
the
projects
that
we
work
on
is
like
all
right.
This
is
the
way
to
do
it.
This
is
our
governance
structure
from
here
on
out,
never
change
it.
You
know,
essentially,
all
of
our
projects
evolve
and
change
every
day,
so
the
guidance
that
the
tag
should
be
providing
needs
to
change
all
the
time.
E
So
if
you
see
something
and
you're
like
this
is
really
cool
but
for
a
project
like
mine,
half
of
this
isn't
applicable,
we
want
to
know.
Maybe
we
should
make
a
separate
template
that
looks
a
little
different
for
the
different
type
of
projects
that
we
have
in
the
cncf,
but
yeah
just
don't
look
at
it
and
think,
oh
well,
I
would
have
contributed
to
the
contribution
ladder,
but
it's
already
done.
That's
definitely
not
the
case.
We
can
always
keep
improving
and
involving
these
documents.
C
Even
just
suggestions
of
things
to
put
in
because,
like
the
way
that
we
ended
up
with
the
values
section
in
all,
the
government
templates
was
that
aiva,
I
think,
came
by
and
and
said.
Basically,
this
needs
a
value
section
right.
We
need
to
communicate
values
of
the
project
in
the
governance
like
yeah
you're
right,
it
does
need
one
and
then,
but
we
didn't
know
what
to
put
there
and
then
somebody
from
another
project
had
a
very
nice
sort
of
generic
value
section
for
their
project
that
we
borrowed.
B
Yeah,
I
think
these
should
be
seen
really
as
living
documents
right,
like
they're
they're,
never
going
to
stay
that
way,
because
it's
like
like,
even
if
they're
just
new,
for
instance,
with
a
crm
run
book
right
like
that,
is
like
the
feedback
or
like
the
input
of
a
few
people,
people
who
did
it,
but
it's
probably
missing
a
lot
of
other
things
right.
So
it's
like
it's
a
first
start.
We
put
it
there.
B
We
only
got
feedback
from
certain
people,
but
there
may
be
lots
of
ways
how
you
can
use
us
here
at
community
crm
that
are
valuable.
That
are
not
there
right,
and
that
applies
to
everything.
So
it's
like
and
that's
another
thing
it
like
whenever
we
contribute
something
to
the
tag,
it
doesn't
have
to
be
this
full
thing.
It's
like
okay.
B
This
is,
to
my
best
knowledge
right,
like
what
I
like,
what
I've
learned
and
what
other
people
have
told
me
put
it
out
there
and
then
like,
ideally
as
people
use
it
because
there's
a
everywhere
there's
like
a
at
like
a
contribute
or
edit
or
you
know
like
button,
so
to
make
it
really
easy.
So
it's
like,
if
you
see
something
you
know
like,
and
even
if
it's
just
like
an
issue
because
you
don't
want
to
do
the
whole
pr.
B
It's
like
making
a
comment
like:
oh
we've
done
this
and
this
so
it
should
be
con.
Ideally,
as
more
people
use
it,
it
will
improve
over
time
right,
so
it
should
improve
like
there
are
none
of
these
like
perfect.
Probably
so
any
little
feedback
or
whatever
is
highly
appreciated
and
is
also
a
valuable
contribution.
D
And
I
think
the
crm
runbook
in
particular
is
a
really
good
example,
because
it's
it's
not
something
that
we
talk
about
in
a
lot
of
open
source
projects.
So
I
I
saw
this
as
a
really
innovative
addition
to
the
the
tag
and
it's
something
that
you
know.
Catherine,
was
really
really
passionate
about
and
and
brought
to
us,
and
so
you
know,
I
would
say
you
know,
look
look
through
the
resources
and
if
there's
something
that
you're
doing,
that's,
maybe
maybe
innovative
that
you
think
other
people
can
learn
from.
D
That's
that's
a
really
good,
a
really
good
way,
I
think,
to
to
contribute
new
material
to
to
the
tag
you
know
we
talked
about
kind
of
you
know,
sharing,
sharing
ideas
and,
and
one
way
that
you
know
being
a
maintainer
is
hard
right.
So
we
need
we
need
support.
You
know
maintainer
to
maintainer,
so
I
think
next
josh
is
up
he's
going
to
talk
a
little
bit
about
the
maintainer
circle.
C
Yeah,
so
I
you
know
honestly,
one
of
the
things
we
talked
about
was
like
guidance
and
that
sort
of
thing
and
different
people
sharing
advice
and
resources,
but
honestly
there
when
you're
a
project
maintainer
there
are
problems
that
you
deal
with,
that
there
aren't
any
like
a
document
can't
help
you
resolve
those
or
maybe
they're,
honestly,
not
resolvable
at
all.
Maybe
you
just
want
to
talk
to
other
maintainers
who
have
the
same
kind
of
problems
that
you
have.
I
maybe
just
to
commiserate.
C
So
I
want
to
highlight
that
yeah
and
that's
actually
why
we
have
maintainer
circle,
so
maintainer
circle
is
periodic
a
few
times
a
year,
either
online
or
in
person.
At
kubecon
cloud
native
con,
we
get
together
a
group
of
maintainers
to
talk
about
things.
C
The
this
is
a
picture
from
the
last
one
in
valencia,
and
this
was
a
conversation
about
reviewers
reviewing
how
to
do
good,
reviewing
how
to
mentor
new
reviewers,
how
to
deal
with
problems
that
come
up
in
reviewing
other
people's
submissions,
and
we
got
together
for
about
two
hours
in
valencia
for
a
lot
of
people
to
talk
about
this.
C
Handling
security
issues,
all
kinds
of
the
other
things
that
are
really
honestly
very
part
of
what
makes
being
a
maintainer
of
a
project
really
difficult.
So
the
so,
if
you
are
a
maintainer
of
the
project,
I'm
saying
and
you
don't
have
to
be
an
accredited
cncf
maintainer
on
the
cncf
maintainer
list.
Honestly,
you
just
have
to
consider
yourself
a
maintainer
right.
Are
you
responsible?
If
you
go
away?
Does
something
bad
happen
to
the
project?
If
the
answer
to
that
is,
yes,
then
you're
a
maintainer.
C
And
the
and
we
would
be
really
interested
in
having
you
join
us
and
by
joining
us
I
would
say
you
can
either
the
main
communication
happens
on
the
maintainer
circle,
slack
channel
and
cncf
slack.
The
and
the.
C
The
and
or
you
can
just
join,
we
have
the
tag
contributor
strategy
mailing
list.
We
mainly
use
the
mailing
list
only
for
announcements.
So
if
you
just
want
to
keep
track
of
what
we're
doing,
including
announcements
of
new
maintainer
circles,
you
can
join
that
it
is
it's
not
a
discussion
list.
We
do
most
of
our
discussion
on
slack,
so
you
don't
have
to
worry
about
getting
too
many
posts
from
that
now
for
maintainer
circle.
C
You
know
please
show
up
and
participate
particularly
interesting
if
you
are
a
maintainer
not
on
kubernetes
overwhelmingly
the
people
who've
been
turning
out
for
maintainer
circles
are
kubernetes
maintainers
because
there's
a
lot
of
them,
but
we
really
really
want
to
reach
the
other
cncf
projects
for
one
thing,
because
I
think
you
guys
are
going
to
have
more
different
perspectives,
but
you
would
probably
particularly
if
you're,
one
of
only
three
maintainers
on
a
project.
You
could
probably
use
the
peer
support
even
more
than
your
kubernetes
peers.
C
So
please
join
us
and
participate
make
use
of
that
resource.
And
importantly,
if
you
have
either
an
an
idea,
an
area
of
expertise
or
a
problem
right,
you
know
so
either
something
that
you
figure
out
how
to
do
and
you
want
to
share
with
other
maintainers
or
something
you
haven't
figured
out
how
to
do,
and
you
want
to
talk
to
other
maintainers
about
how
you
resolve
this.
Please
come
to
us
suggested
as
a
topic.
C
E
I
was
gonna
say
my
favorite
part
about
participating
in
maintainer
circle.
Is
that,
as
you
said,
a
lot
of
these
they're
awkward,
they
don't
always
have
clear
solutions
or
they're,
not
easy
to
discuss
in
public
without
having
to
be
very
careful
what
you
say
and
how
you
explain
the
situation
and
all
that
a
lot
of
it's
a
little
sensitive
right
and
what
I
really
liked
about
is
we
had
small
breakouts,
where
I'd
be
with
three
other
maintainers
and
whatever
we
said
amongst
each
other.
E
We
all
understood
because
we're
dealing
with
similar
things
and
there
it
was.
It
was
explicit
understanding
that
we
weren't
sharing,
who
said
what
or
you
know,
spilling
the
tea
or
anything
like
it.
Just
stayed
in
the
group
which
made
it
feel
very
comfortable
like
I
could
just
open
up
and
say
yeah
it's
hard
when
things
are
like
this,
I
can't
talk
about
it
publicly
because
it
just
doesn't
sound
great,
but
it's
still
a
thing.
E
I
have
to
figure
out
how
to
respond
to,
and
people
were
really
great
at
giving
suggestions
for
how
to
deal
with
situations
like
that.
For
example,
conduct
situations,
for
example,.
D
C
Okay,
I'm
going
to
talk
about
one
other
thing
that
we're
actually
going
on
now
and
another
sort
of
newish
initiative,
which
is
the
mentoring
working
group.
C
C
So
the
so
this
is
a
new
working
group.
You
can
actually
find
the
information
in
the
tag
constructor
strategy,
repo,
with
links
off
a
lot
of
them
into
the
mentoring
repo
which
has
existed
for
a
while.
This
is
an
e
easy
place
for
you
to
get
involved
from
either
of
two
sides.
One
is
if
you
are
a
project
maintainer
reviewer,
sub
project
owner
a
regular
contributor
anywhere
else,
obviously
we're
looking
for
mentor,
mentors
and
project
ideas.
C
One
thing
that's
particularly
going
on
right
now
that
the
mentoring
working
group
folks
wanted
me
to
call
out
is
that
for
the
lfx
mentorship
program,
which
is
the
one
run
by
the
linux
foundation,
project
idea.
Mentee
applications
are
due
well
project.
Verbals
will
do
this
friday
and
then
minty
applications
open
the
following
week.
C
C
The
stop
sharing
here
I
as
an
example
of
what
that
went
through
is,
for
example,
a
year
ago.
We
decided
that
we
actually
needed
better
election
software
for
kubernetes
and
for
a
couple
of
other
cloud
native
projects,
and
so
we
created
an
lfx
project
and
recruited
a
terrific
mentee
who
helped
put
together
the
scaffold
of
that
election
system
in
flask,
which
has
continued
developing
as
the
electoral
project
for
github
driven
elections
for
projects
the.
C
So
you
can
think
outside
of
obviously
recruitmenties,
for
you
know
hacking
on
the
mean
things
for
your
project
for
your
project
code,
but
also
think
about
things
that
you
need
around
your
project
that
you're
never
going
to
get
to
yourself,
but
you
could
motivate
yourself
to
mentor
somebody
to
do
them.
C
One
of
the
things
I've
really
found
is
that
yes,
could
I
written
the
code
myself
I
could
have,
but
would
I
have
is
another
question
entirely:
whereas
if
you're
doing
a
mentorship-
and
you
have
a
schedule
and
deadlines-
and
you
have
to
meet
with
your
mentee
twice
a
week,
then
that
actually
makes
sure
that
things
happen
now.
The
other
side
of
that
is,
if
you
are
a
new
contributor,
you
know
and
not
a
project
owner
of
any
kind.
C
C
There
are
always
mentorship
opportunities,
all
the
time
and
the,
and
particularly
I'm
going
to
say
for
new
contributors
who
are
non-male.
C
We
try
to
promote
diversity
through
these
programs
and
we
don't
actually
get
as
many
non-male
candidates
as
we
would
like.
So,
if
that's
you,
please
look
at
the
internship
opportunities
that
are
available.
E
Dash,
I
had
a
question
for
you
about
this.
If
I'm
a
product
and
I'm
trying
to
think
what
could
people
work
on?
What's
the
experience
and
kind
of
skill
level
that
I
should
be
anticipating
from
most
of
the
mentees.
C
So
so,
if,
if
all
it
requires,
is
a
freshman
college,
knowledge
of
python
or
java,
then
then
you're
going
to
get
lots
of
applicants,
but
that
shouldn't
restrict
you,
because
the
truth
is,
you
only
need
one
qualified,
mentee
right
and
honestly,
sometimes
people
enter
into
this
kind
of
knowing
who
the
mentee
already
is
right,
because
you
have
somebody
who's,
a
student
who's
involved
in
your
project
or
somebody
who
otherwise
qualifies
for
these
programs,
because
lfx
and
outreach
don't
strictly
need
to
be
students
the
and
effectively
using
the
mentorship
to
get
them
the
time
to
work
on
the
project
which
they
otherwise
wouldn't
have,
because
maybe
they
need
to
look
for
a
job
the
but
go
ahead
and
also
file
the
things
that
require
specialized
skills
right,
because
I've
seen
grad
students
in
the
application
pool
and
if
somebody's
a
grad
student,
then,
following
that
project
about
hey
now,
that
kubernetes
supports
full
dual
stack.
C
We
need
to
actually
support
dual
stack
in
our
security
monitoring
tool
is
not
out
of
the
question
for
a
mentorship
program
for
a
mentorship
thing.
The
main
thing
about
it
is:
you
need
to
look
for
tasks
that
are
completable
in
a
three
to
four
month
period
and
the
most
important
thing
is:
you
need
to
look
for
tasks
that
you
have
a
mentor
for
right.
C
F
C
They
may
teach
you
how
to
put
your
own
stuff
on
github,
but
they
don't
teach
you
how
to
participate
in
a
public
open
source
project
that
already
has
rules
and
a
lot
of
our
projects.
A
lot
of
the
cloud
native
projects
actually
have
very
specific
rules.
So
that's
often
like
your
first
week
right.
This
is
how
you
do
a
pull
request
against
this
project.
C
The
you
know
this
is
where
the
docs
are
this,
is
you
know
you
need
to
have
your
docs
tied
to
your
pull,
request,
submission
et
cetera,
et
cetera,
the
I
would
say,
do
plan
to
have
regular
meetings
with
your
mentee.
C
You
know,
since
we're
talking
about
like
an
eight-week
period,
for
a
lot
of
these
mentoring
programs.
Think
about
even
more
than
once
a
week.
C
F
C
A
Like,
like
you
said,
I
I
can't
agree
more,
there
is
something
I
was
reading
just
the
other
day
talking
specifically
about
education
and
and
students
and
student
teacher
and
family
relationships,
and
it
was
shown
like
repeatedly
that
the
more
interactions
happen,
the
daily
the
weekly,
the
monthly
recaps
of,
what's
going
on
the
better
the
students
actually
did
in
school.
So,
like
you
said,
if
it's
an
eight-week
program
and
you
meet
once
every
eight
weeks,
that's
that's
not
gonna
work
out,
yeah.
C
Now
now,
there's
some
other
things,
so
one
of
the
other
things
that
we're
trying
to
get
out
of
this-
and
this
is
again
maintainers
helping
other
maintainers
and
mentees
helping
other
mentees
is
that
the
mentoring
working
group
is
going
to
create
some
forums
channels,
whatever
they
need
to
actually
figure
out
the
format
for
this,
both
for
mentors
across
all
cloud
native
projects
and
for
mentees
across
all
cloud
native
projects,
because,
particularly
again,
we
have
projects
of
all
different
sizes
right
and
you
know.
C
Yes,
we
have
these
big
pools
of
people
and
say
kubernetes,
but
not
necessarily
in
cortex,
to
take
an
example
and
so
being
able
to
have
your
mentors
share.
Notes
with
mentors
from
other
cloud
native
projects
can
really
help.
You
end
up
having
to
deal
with
a
lot
of
people
issues
if
you're
a
mentor.
C
You
know,
because
you
know
you're
talking
about
students,
other
people
who
are
new
to
the
project
and
being
able
to
lean
bounce
ideas
off
other
mentors
for
advice,
particularly
if
you're,
the
only
mentor
for
your
project
is
super
helpful,
same
thing
with
mentees
who
are
looking
for
and
potential
mentees
who
are
looking
to
sort
of
break
into
contributing
to
cloud
native.
C
It
can
be
really
useful
to
collaborate
with
other
mentees
and
share
notes
and
on
top
of
which,
to
get
sort
of
all
this
in
there
keep
an
eye
on
cncf
announcements
and
twitter,
etc,
because
we're
going
to
have
a
survey
of
people
who
have
mentored
for
cncf
projects
across
these,
these
various
formal
programs.
C
I
because
we
want
to
start
building
a
body
of
advice
and
shared
knowledge.
That's
public
for
for
mentors.
E
E
This
is
actually
content
that
I
produce
for
my
project
porter
and
it's
been
wildly
successful
and
I
have
a
to
do,
but
if
anyone
would
like
to
help
is
to
promote
this
concept
at
the
tag
level
as
a
general
thing
that
projects
can
do
oops,
sorry,
yeah,
let
me
I'm
going
to
send
a
link
of
just
what
we've
done
in
a
porter
here,
but
we've
created
a
tutorial
page
that
walks
you
through
everything
you
need
so
say
it's
friday,
night
and
you're
super
inspired
and
you're,
like
I'm
gonna
work
on
this
project
and
to
be
honest,
no
one's
probably
around
on
slack
to
chat
or
like
help
you
out
or
give
feedback
or
anything.
E
So
this
tutorial,
the
concept
is
regardless
of
the
project.
It
should
give
you
enough
information
so
that
you
can
get
started
and
get
familiar
with
working
on
the
project.
So,
for
example,
mine
here
walks
you
through
how
to
clone
the
repository,
how
to
get
any
necessary
tools
that
you
need
to
have
a
working
development
environment.
Helps
you
navigate
through
the
code
a
little
bit
understand.
E
What
are
some
common
commands
you're
going
to
run
with
the
build
scripts
like
what
are
the
make
commands
like
make
build,
make
tests?
What
should
I
be
doing,
and
then
it
walks
them
through
making
a
common
type
of
change
to
the
code
base.
So
even
if
there's
no
good
first
issue
at
the
moment,
they
have
something
that
they
can
try
and
practice
going
through.
Okay,
I'm
going
to
add
a
new
command
to
the
cli
or
a
new
endpoint
to
this
api
figure
out
how
to
test
it,
build
the
code.
E
E
All
this
down
is
great
because
otherwise
you're
trying
to
like
brain
dump
it
haphazardly
for
each
person
who
asks
which
is
hard
and
then
it's
it's
timely
right,
because
they're
going
to
be
asking
you
for
help
for
a
lot
of
us
off
hours,
and
this
is
really
great
with
which
time
zone.
So
I
can
have
someone
who's
13
hours
off
for
me,
benefit
and
be
able
to
contribute
without
kind
of
being
at
a
disadvantage
because
we're
not
able
to
talk
synchronously.
E
C
Okay
with
all
that
we're
we're
almost
the
end
of
our
time.
So
let
me
go
ahead
and
share
how
to
keep
in
touch
with
us
for
all
of
these
initiatives
and
more
the.
C
So
there
we
go
so
slack
channel,
obviously,
first
landing
spot
tag.
C
Contributor
strategy,
slack
channel
on
the
cncf
slack,
is
a
good
way
to
find
us
there's
a
mailing
list
and,
like
I
said,
we
use
that
almost
entirely
for
announcements
of
upcoming
activities,
also
for
announcements
of
things
like
new
guides
new
documents,
new
templates
that
we
put
up
there's
a
talkify
link
that
filters
all
of
our
meetings
are
on
the
cncf
public
calendar,
but
there's
a
talk
of
my
link
that
actually
filters
it
to
the
specific
contributor
strategy,
links
and
again.
C
Somebody
said
this
earlier,
but
for
most
of
our
meetings
we
tend
to
leave
20
to
30
minutes
at
the
end
of
every
meeting
for
people
who
work
on
projects
to
just
drop
by
and
ask
questions
right.
So
if
you
have
a
governance,
if
you're
overhauling
the
governance
on
your
project
feel
free
to
drop
by
the
monthly
governance
meeting
and
just
put
yourself
on
the
agenda,
also
the
maintainer
circle
slack
there
and
again
you
can
find
all
of
these
links
off
of
the
dedicated
link
blog
post.
C
A
Awesome,
thank
you
so
much.
I
shared
that
to
the
respective
chats,
so
please
be
sure
to
check
that
out.
I
think
we
might
have
time
for
just
one
more
question
if
anyone
wants
to
raise
up
anything
in
particular,
otherwise
really
do
want
to.
Thank
you
all
for
stopping
on
by.
I
know
it
was
a
long
drive
to
get
here,
but
really
appreciate
everyone
was
able
to
make
it.
A
Absolutely
no
always
fantastic
to
chat
with
y'all.
I
really
appreciate
you
making
the
time.
Thank
you,
everybody
for
joining
the
latest
episode
of
cloud
native
live.
It
was
wonderful
to
learn
from
the
tag
contributor
strategy
team.
I
hope
that
you
are
able
to
take
some
of
these
lessons
and
apply
them
to
your
own
lives
teams,
jobs,
etc,
and
we
hope
to
see
you
around
the
cloud
native
water
cooler,
so
to
speak.
The
questions
and
interactions
from
everyone
was
fantastic
today.
Thank
you
so
much
for
joining
us.
A
We
hope
to
see
you
again
soon
and
yeah
keep
your
head
in
the
clouds
thanks.
Everybody
have
a
good
one.
Thanks.