►
From YouTube: CTA | How to Get involved + Project Update - What's Next - Dan Garfield, Scott Rigby & Chris Short
Description
CTA | How to Get involved + Project Update - What's Next- Dan Garfield, Codefresh; Scott Rigby, Weaveworks & Chris Short, AWS
A
So
my
job
was
to
tell
you
how
to
get
involved
and
we
need
your
help.
All
these
problems
that
we're
talking
about
today
aren't
necessarily
solved
easily.
There's
some
quotes
that
have
come
out
of
today.
Already
right,
like
choose
your
tech
debt,
you
know,
choose
it
wisely,
you're,
not
choosing
a
tool,
you're,
choosing
your
technical
debt
and
then
the
ubiquitous
conway's
law
always
applies.
A
So
how
do
you
get
involved
in
helping
us?
Well
first,
thank
you
to
all
the
volunteers
that
made
this
possible
today.
That's
a
lot
of
people,
yeah
christian
aubrey,
from
red
hat
yeah.
You
know,
scott
from
weave
works,
a
bunch
of
people
there,
a
few
people
from
aws
yeah,
it's
a
lot
of
volunteers.
It's
a
lot
of
speakers
too,
when
you
put
them
all
on
one
page.
A
So
thank
you
to
all
the
speakers.
This
would
not
have
been
as
awesome
of
a
day
without
them.
So
how
do
we
get
involved?
Showing
up
is
actually
80
of
the
work.
Scott
I've
heard
that
I've
heard
that
yes,
so
what
is
in
front
of
you?
Well,
it's
the
cncf
that
io
slash
calendar
and
if
you
search
for
get
ops,
you
will
find
our
working
group
meetings,
which
you
can
then
add
to
your
calendar.
It's
awesome!
B
B
Okay,
but
there
are,
there
are
different
groups
of
people
working
on
different
work,
products
that
are
part
of
the
good
ops
working
group
and
for
the
open,
getups
project
and,
and
one
of
the
things
that
we
do
with
that
meeting.
Is
those
people
report
back?
I
guess
you
could
say
or
try
to
you
know
just
just
integrate
so
that
everybody
has
an
idea
of
what's
going
on.
B
A
B
A
B
A
A
If
you
have
an
issue
like
with
a
term,
that's
missing
from
the
glossary,
for
example,
feel
free
to
open
an
issue
and
create
a
pr
and
it'll
get
added,
trust
me
and
then
slack.
I
created
a
shorter
link
because
that
url
no
one's
going
to
remember
please
join
us
on
slack.
That's
a
great
way
to
get
your
stuff
into
our
meetings
into
our
field
of
view.
A
B
I
know
at
some
point
it
was
noted.
You
know
that's
where
documents
live,
but
but
basically
that
is
a
cncf
sandbox
project.
It
is
not
the
same
as
the
getups
working
group.
Just
like
most
projects
aren't
the
same
as
working
groups.
Working
groups
are
meant
to
be
short-term.
They
last
as
long
as
they
last
they're,
either
underneath
technical
advisory
groups,
which
the
github
working
group
is
it's
underneath
the
app
delivery
sig.
How
are
we
doing.
B
And
other
working
groups
are
just
directly
under
cncf.
Excuse
me,
so
in
any
case,
where
was
I?
Where
was
I
going
with
that?
Oh
yeah,
so
the
so
the
get
ops
working
group
it
it
doesn't
seem
to
be
going
need
to
go
away
right
this
moment
or
anything
like
that.
I
mean
it
will
last
as
long
as
it's
needed,
but
once
the
once
the
open
get
ops
project
is
really
running
solidly
on
its
own
and
it
doesn't
feel
like
it
needs
a
separate
group.
B
That
group
may
not
be
necessary
anymore,
because
you'll
actually
be
able
to
group
together
with
folks
in
the
opengetapps
project.
That's
already
getting
started,
so
the
github
teams
that
I
mentioned
that
where
people
are
joining
to
to
do
certain
types
of
tasks
together,
explore
certain
ideas
together.
You
know
I
mentioned
earlier
during
the
opening
the
the
get
up
impact
on
environmental
sustainability.
B
Hey
if
that's
one
of
the
topics
that
interests
you
awesome,
please
connect
with
with
us
and
other
folks
who
are
a
part
of
that
group,
and
if
you,
if
you
have
an
ability
to
commit
to
that,
then
we
can
add
you
to
that
team.
Yeah,
another
cool
thing
about
being
added
to
a
github
team
is
that
you
can
choose
to
show
that
badge
on
your
github
profile.
You
know
so
it's
you.
You
can
do
that.
You
can
do
that
too,
and
we
try
to
also
make
it
clear
that
volunteers
can
have.
A
B
Yes,
so
in
terms
of
slack,
I
got
a
little
off
topic
there,
but
in
terms
of
slack
we
have
both
channels
and
you
can
use
both,
but
we've
been
migrating
as
much
as
possible
to
open
get
ups.
If
there
are
things
that
are
specific
just
to
the
working
group
that
aren't
really
relevant
to
git,
so
we
might
still
do
it
on
the
working
group,
but
but
hopefully
that
helps
you
there.
There.
A
The
word
right,
like
tell
your
friends
like,
do
tell
your
friends
how
to
do
devnops
through
a
pull
request
right,
like
that's
the
start
of
it
that
started
that
conversation
internally
tell
us
what
you're
up
to
right
like
we
want
to
know
the
companies
and
the
people
that
are
using
git
ops,
so
it
you
know,
obviously,
there's
a
lot
of
people
doing
get
ops
it'd
be
great
to
know
who
they
are,
so
we
could
learn
from
them
and
hopefully
learn
from
their
mistakes
so
that
we
can
pass
those
on.
You
know
through
guidance
or
documentation,.
B
Right,
that's
a
good
point.
If
you
need
to
be
anonymous
with
your
employer
about
some
genopsa
horrors
that
you've
had
that
can
be
respected.
You
know
we
don't
think
we
have
an
nda
process,
but
you
can
also
just
tell
us
without
telling
us
who
you
are.
You
know
right
yeah.
Also,
there
is
an
adopt
to
what
chris
said.
There's
now
an
adopters
yes
page
within
the
the
opengetops
project,
repo.
I
think
anyway,
it's
one
of
it's
one
of
the
repos
there
isn't.
B
There
is
a
page
where
you
can
list
yourself
as
an
adopter
of
git
ops
and
there's
a
template
showing
you
how
to
do
it.
So
please
do
that.
Give
like
a
one
sentence:
hey!
This
is
how
I'm
using
githubs
and
even
like.
Oh
here's,
a
link
to
our
blog
post,
showing
you
more
in
depth
on
how
we're
using
git
ups
or
even
how
we're
in
the
middle
of
using
git,
ops
or
whatever
you
want
to
say.
A
And
then
you
know,
I
made
this
short
and
sweet
like
thank
you
all
for
coming.
Thank
you,
scott.
Thank
you
dan.
Thank
you,
christian.
Wherever
you
are,
I
don't
know
where
you
went
but
really
happy
to
have
you
all
here
today
hope
you
had
a
great
day.
I
hope
you
have
a
greater
kubecon
and
we
look
forward
to
seeing
you
in
detroit.