►
From YouTube: GitOps Working Group Meeting - 20210513
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
I'll
paste
in
the
the
link
to
the
meeting
notes.
A
The
direct
link
for
today
is
and
zoom
for
anyone
watching
this
later.
The
link
is
also
in
the
meetings
markdown
document
inside
of
the
github
working
group.
Excuse
me,
the
kit,
ops
working
group
get
repository.
A
So
I'm
a
little
low
energy
today,
but
that's
fine.
I
don't
really
need
to
speak
too
much.
We
have
an
agenda
and
if
folks
wouldn't
mind
just
adding
your
names
or
if
someone
could
add
the
names
of
attendees,
that
would
be
great.
We
have
oh,
I'm
so
sorry,
I
pasted
the
wrong
link.
A
Thanks
and
let's
please
add
topics
below-
I
see
one
topic
by
christian
if
just
as
a
point
of
order,
I
don't
really
see
people
talking
over
one
another
at
this
point,
but
but
if
we
can
do
hand
raising
that
would
be
great
and
then
I'll
just
do
basic
moderation.
A
B
Sure
sure,
if
you,
if
you
don't
mind
I'll,
I
feel
free,
I
I
can
speak
for
hours
as
you
know,
so,
just
kind
of
an
update
on
the
on
the
get
up.
So,
as
a
lot
of
you
know,
we
had
our
first
get
ups
con
right
as
a
day,
zero
event
day
negative
one
event
I
guess
for
for
kubecon
we
we
actually
did
have
a
slack
channel
for
that.
B
We
kind
of
sort
of
mini
discussed
it
on
the
slack
channel,
but
we
kind
of
came
to
the
decisions
like
well.
Let's
just
have
a
general
get
ups
working
group
events
channel
right
so,
instead
of
creating
a
slack
channel
for
every
event,
we're
gonna
have
we'll
just
use
that
one
slack
channel
to
coordinate
that,
and
then
I
came
up
with
the
the
idea
of
or
someone
did
and
I
agreed
with
it
is
we.
We
should
just
have
a
general
events
committee
instead
of
a
committee
for
each
event.
B
So
so
I
think
that's
a
great
idea.
I
think
I'm
gonna
move
forward
with
that.
Unless
there's
like
any
objections
from
the
from
the
broader
group
to
have
a
general
events
committee,
it's
an
open
committee
right,
just
like
every
every
other
committee
here
feel
free
to
join.
Our
meetings
will
probably
be
ad
hoc
only
because
it
it
at
least
for
the
beginning
only
because
we
don't
know
what
events
we're
going
to
do
just
yet
right.
This
is
still
new.
B
B
B
B
Foreign
I'll
actually
paste
that
information.
You
know
the
documents
I'll
follow
the
doc
link.
What
do
you
call
it
a
slack
channel
once
we
have
it?
I
guess
I
guess
we're
gonna
scott.
I
don't
know
if
we're
gonna,
rename
it
or
if
we're
gonna,
create
a
new
one
and
archive
that
one.
I
don't
care
either
way.
I
don't
know
if
I
have
permissions
to
rename
it
so
we'll
figure
that
out
as
soon
as
we
come
so.
B
So
I
think
that's
that's
it
in
terms
of
the
events
committee,
so.
A
Yeah,
that's
I
just
wanted
to
raise
a
hand
for
a
second
in
response,
christian
yeah,
that
sounds.
That
sounds
good
to
me
too.
Personally,
would
you
mind
making
the
github.
A
Just
for
some
transparency-
and
we
can
also
point
a
a
cncf
slack
admin
to
that
issue.
A
Well,
so
I'm
also
doing
notes,
you
know
why
you're
what
why
you're.
A
Speaking
into
yeah,
not
very
well
together
and
wanting
to
put
some
agenda
items,
so
if
anyone
has
anything
else,
you
had
a
question
about
or
something
that
you
wanted
for
an
agenda
item.
You
could.
A
It
is
not
get
ups,
not
at
this.
Not
at
this
point
get
upstairs
was
a
much
older
event
that
predated
the
working
group
and
also
predated
yeah,
and
it's
it's
managed
by
weaveworks,
and
it
has
been
for
all
this
time.
A
A
A
A
The
the
short
the
short
update
for
the
principals
committee
is
for
anyone
who's
been
following
it.
It's
been,
there
have
been
weekly
meetings
for
quite
a
while,
after
after
there
was
a
pr
a
pull
request
that
was
open
for
quite
a
while.
It's
it
was
a.
It
was
a
a
suggestion
that
I
made
to
to
try
to
do
weekly,
in-person
sync
sessions
for
anyone
who
wants
to
show
up,
and
those
have
worked
out
very
well.
A
The
primary
focus
of
those
is
all
of
you
probably
have
read
the
the
the
current
getups
principles
on
the
gaps
working
group
readme.
They
are.
A
They
were
basically
from
the
initial
principles
that
were
laid
out
by
weave
works
years
ago.
Everyone
agrees
that
they
need
to
be
updated
a
bit
and
they
have
been
updated.
A
A
There
are
a
few
other
points
that
need
to
be
made
just
a
few
notes
that
for
now
they're
working
notes
that
are
added
and
there's
a
and
there's
a
a
glossary.
A
All
of
that
was
moved
to
to
a
pull
request
in
the
open,
get
ops,
github
repository
and
for
the
moment
it's
open
dash,
git
ops,
because
it
appears,
as
we
were,
closing
in
on
the
name
of
the
sandbox,
the
cncf
sandbox
project.
There
was
the
open,
good
ops.
All
one
word
was
created
or
regis
created
by
someone
who
currently
we
don't
know
who.
So
if,
if
it's
somebody
in
our
community,
that's
awesome,
please
just
be
like
hey
yeah.
That
was
me.
I
was
hoping
to.
A
You
know,
transfer
that
at
some
point
and
just
forgot
to
say
something:
if
not,
we
will
likely
move
ahead
with
with
making
a
request
to
have
that
formally
transferred,
because
it's
just
really
name
squatting
at
this
point
an
empty,
an
empty
thing,
any
case,
that's
where
it
is
now,
so
you
can
go
to
get
ups.
Sorry
open,
dash,
get
ops
in
the
github
repo
you'll
see
that
there
is
a
documents
repository
and
the
the
pull
request.
A
Is
there
there's
explanation
at
the
top
of
the
pull
request
about
where
the
commits
are?
So,
if
you
just
look
at
the
files,
change,
you'll
see
not
a
whole
lot
there.
That's
literally
just
what
we
were
focusing
on
for
broad
consensus
for
the
first
pre-release
of
pre-release,
of
the
revised
git
ops
principles
as
defined
by
or
you
know,
as
defined
by
the
cncf,
get
ops
working
group.
A
So
if
you
look
at
the
readme
for
the
the
the
working
group,
read
me,
there's
a
clarification
point
now
that
the
that
that
the
working
group
is
actually
a
working,
a
working
group
under
cncf,
apps,
app,
sig
delivery,
sorry
sig,
app
delivery
and
the
sandbox
project,
which
was
initially
also
of
the
same
name,
has
been
renamed
to
opengetops.
A
To
avoid
wanting
to
avoid
confusion
and
two,
because
that
is
a
project
that
is
intended
to
to
have
a
to
be
a
long-lived
project,
whereas
working
groups
generally
are
short-lived,
I
mean
it
could
be,
could
be
quite
a
while
that
the
working
group
is
still
here.
But
but
the
goal
of
the
working
group
is
to
help
steer
the
direction
of
of
the
documents,
programs
and
any
any
possible
code
for
interoperability
that
might
come
about,
and
that
would
that
would
then
live
in
the
open
gaps
project.
A
So
those
are
the
those
are
the
two
things
I
wanted
to
mention
because
in
order
to
talk
about
where
the
principles
are
and
how
you
can
see
that
I
had
to
mention
the
open
githubs
project.
So
I
hope
that
helps
a
little
bit
and
I
you
know,
there's
more
details,
but
that's
that's
the
summary,
so
I
am
going
to
now
yield.
I
see
one
hand
raised
christian.
B
Yeah,
so
my
question
is
so
I'm
actually
filling
out
the
github
issue,
but
now
you're
starting
talking
about
transitioning
over
and
I'm
pretty
sure,
there's
going
to
be
a
list
of
things
to
do
for
the
transition
over.
B
So
I
guess
my
question
is:
is:
should
I
be
asking
for
a
different
name
when
renaming
the
psych
channel
or
our
should
we
is
that
independent
and
should
we
are
we
just
gonna,
do
all
that
as
a
as
one
big
project,
like
that's
gonna,
be
an
undertaking
from
all
of
us
as
one
project
to
like
renaming
things
and
start
moving
things
over.
So
my
question
is
more
of
about
when
you
know
when
the
rubber
hits
the
road.
How
are
we
going
to
track
all
of
this.
A
Yeah,
so
so,
right
now,
everything's
been
done
with
as
full
transparency
as
possible.
If
you
go
to
the
get
ops
working
group,
get
ups
dash
working
dash
group
get
get
there's
a
pull
request
looks
like
organization.
A
A
Cool
and-
and
there
may
be
things
that
may
be
slightly
out
of
date,
but
I
think
it's
pretty
it's
pretty
up
to
date.
It's
been
some
things
have
been
a
little
fast
moving,
but
I
believe
everything's
up
to
date,
transparently
there
and
just
to
be
clear,
we're
not
in
a
process
of
transitioning
the
working
group
to
opengetups.
But
the
idea
is
that
the
the
working
group
is
a
working
group
that
will
last
for
as
long
as
it
needs
to
last
could
be
could
be
years.
A
I
don't
know
it
could
be
a
year,
I'm
not
really
sure,
but
the
goal
is
to
set
up
the
the
to
help,
define
officially
define
the
meaning
of
getups
the
principles
of
getups
various
things
related
to
this
area.
A
That's
what
the
working
group
is
really
for
and
to
oversee
the
the
persistent
I
don't
want
to
say
forever,
but
the
persistent
project
called
now
called
open
get
ops,
so
the
working
group
will
still
govern
open,
get
ops
for
as
long
as
it
needs
to
be
here
until
it's
something
that's
completely
self-running,
and
at
that
point
we
very
likely
won't
need
to
have
a
working
group
we'll
actually
get
functioning
a
fully
functioning
project.
B
A
Exactly
exactly
and
the
people-
and
you
know,
the
working
group
will
still
have
the
committees
just
so
that
we
can
be
efficient.
That's
it.
I
think
nothing,
nothing
different!
It's
just
that!
There's
now
a
place
for
those
an
actual
project
for
those
artifacts.
If
you
think
of
you,
know
the
cncf
conformance
project,
it's
very
similar
to
that.
It's
at
the
moment,
there's
no
code,
but
there
may
very
well
be
code
for
interoperability
between
github's,
tooling,
so.
C
A
Does
anyone
have
questions
about
either
of
the
two
agenda
items
that
we
just
talked
over,
or
rather
three?
I
guess
the
events
committee,
the
principles
committee,
update
and
and
the
question
about
open,
good
ops,
I'm
sorry
and
the
question
about
getupstays.
A
Okay,
does
anyone
have
anything
else
to
to
talk
about?
We
could
also
just
cut
the
meeting
short
or
would
would
you
like
to
it
doesn't
have
to
be
that
formal?
Does
anyone
have
any
you
know?
I
don't
want
to
overrun
anything
that
people
have
on
their
minds
or
haven't
quite
said
yet
so
definitely
pipe
up.
If,
if
there's
something
that
you've
been
mulling
over
in
the
back
of
your
mind
and
just
haven't
said
it,
but
we
could,
we
could
have
a
discussion
about
how
get
up
scott
went.
B
Well,
one
one
quick
thing
before
that:
I
think
it's
worth
bringing
up
the
you've
had
some
ideas
of
forming
different
committees
for
different
things
like
you
had
like,
there's
a
need
for
like
a
social.
B
You
know,
committee
me
a
team,
a
need
for
there's,
there's
a
need
for
like
a
few
open
roles,
I
guess
or
or
open.
If
someone
wants
to
take
a
leadership
role
on
some
of
these
things,
I
don't
know
scott.
If
you
want
to
talk
about
some
of
these
things,
I
know
there's
there's,
there's
some
github
issues
around
it.
Maybe
you
know
pertinent
to
bring
those
up
to
light
in
case
someone
is
interested.
E
A
I'm
just
actually
writing
notes
and
then
that's
not
so
yes,
so
actually
you
can
see
because
you're
on
sharing
screen
so
there's
also
the
communications
team
or
committee.
I
guess
I
don't
know,
I
guess
it's
really
a
team,
here's!
Here's!
What
here's,
what
where
we
are
at
right
now
so
currently.
A
Yeah
to
what
to
what
leonardo
just
said
first,
I
guess
there's
a
I
believe,
a
discussion
about
a
rather
maybe
an
issue.
A
So
there
have
been
a
couple:
people
that
have
stepped
up
dan
garfield
also
is
is,
is
helping
to
moderate
right
now.
The
current
moderators
of
reddit
of
the
subreddit
get
ops.
A
I
don't
know
all
of
them.
There
are
a
few.
Let's
see
here,
give
me
just
a
second
for
that
to
load.
I
guess.
D
A
Yeah,
so
I'm
a
moderator
dan
garf
dan
garfield
is
today
was
awesome,
just
like
it's
getting
a
username
and
it
looks
like
robert
offered
to
help
with
that
too,
to
help
with
a
ban
hammer,
I
guess,
if
needed,.
A
A
A
So
I
just
posted
that
oops,
I'm
sorry
I
accidentally
posted
leonardo
here
is
the
issue
for
everyone.
There
we
go.
A
Yeah,
okay,
so
that's
one,
the
other!
The
other
is.
A
The
other
is
the
communications
team,
and
currently
this
is
where
it
is,
if
you're
not
on
github
teams
are
only
visible
to
other
members
of
the
of
the
github
work.
So,
but
I
can
show
you
the
team
role,
the
teams
real
quick.
This
is
full
transparency.
A
Some
of
this
needs
to
be
reorganized
slightly,
but
not
too
much.
For
example,
there
are
bootstrapping
admins
who
are,
who
don't
right
now
have
a
any
specific
role
in
the
organization
in
the
working
group,
so
the
idea
would
be
to
add
those
to
talk
with
those
people
about
taking
on
an
official
role
or
remove
them
from
the
admin
group.
A
I
believe
that
was
announced
the
last
time
I
I'm
honestly
not
sure
if
it
wasn't
that
vote
went
through,
it
was
on
the
it
was
on
the
apps
or
the
sig
app
delivery
mailing
list,
so
every
it
should
be
clear,
but
if
not
that's
cool,
I
just
said
it
now
and
there
is
a
there
is
a
a
pull
request
to
to
update
the
governance,
which
has
information
about
chairs,
reintroducing
the
charter
and
and
just
updating
the
the
initial
wording
of
the
governance
which
which
there
was
a
proposal
to
simplify
the
governance
initially,
so
it
was
primarily
for
bootstrapping
purposes.
A
A
Governance,
pr
in
progress
that
there
is
a
there's,
a
goal
I
think
to
I
know-
to
have
that
reviewed
this
this
week,
so
keep
up
to
date
with
that.
So
what
I
was
getting
to
with
the
teams
is,
there's
a
communications
team
and
there
have
been
several.
There
have
been
several
people
who
who
have
not
really
been
voluntold,
but
I
suppose
volunteered
to
like
truly
volunteer
to
to
help
with
this
and
currently
currently
it's
you
know
me
chris
short,
who's,
really
a
youtube
ninja.
A
If
you
know
all
of
the
other
things
chris
does
dan
garfield
as
well,
and
sonya
schweigert,
who
was
helping
with
communications
for
get
ups
kind
of
other
things.
Sonya
is
working
on
the
basically
helping
with
the
twitter
handle
and,
if
you
don't
know
twitter
is.
A
A
Saying
initially
is
that
there
there
are
open
positions,
please
get
involved.
You
know,
there's
no
requirement
for
membership
in
the
get
ops
working
group.
It's
really
it's.
It's
essentially
a
duocracy
with
a
bit
of
governance.
A
So
if
you're
interested
in
that
kind
of
thing,
let's
talk
we'll
open
a
github
issue
for
transparency
and
we
can
discuss
it.
So,
please
get
in
touch
in
the
in
the
cncf
wg
dash,
git,
ops,
slack
channel.
A
We
can
go
ahead,
for
example
christian
and
once
I
don't
know,
I
I
believe,
there's
no
contention
about
renaming
the
vietnam
eu
working
group
too.
Excuse
me
two
events,
but
we'll
just
keep
it
simple.
B
A
B
A
You
can
put
that
in
the
issue
if
you
want
like,
because
we
still
need
to
do
other,
like
you
can
make
it
a
check
box.
That's
checked
that
piece,
but
then
we
still
need
to
update
the
yeah
update.
The
pardon
me
yeah,
the
slack
channel
and
I'll
probably
send
a
send
an
email
to,
or
I
don't
know
if
it's
if
we
need
to
send
an
email
to
the
mailing
list
for
this,
it's
probably
not
that
high
priority
for
anyone.
This.
A
Scenes
thing,
but,
as
you
asked
you
know
yes,
this
is
a
place
where
folks
can
get
involved
too.
So
so
sorry,
back
to
the
teams,
the
other
team
are
maintainers
of
the
get
ops
working
group
and
opening
gouge
project.
A
They
are
people
who
helped
to
bootstrap
the
project
with
a
few
folks
that
swapped
roles
from
the
different
companies
that
they're
at
there's
a
there's
a
get
up.
There's
a
an
issue
in
in
the
get
ups
working
group
about
that.
So
it
is.
A
A
Okay
and
and
give,
and
and
and
that
as
well
the
governance
pull
request
that
I
linked
to
before
gives
you
an
idea
of
how
a
slightly
better
idea
than
the
current
governance
governance
doc
about
how
that
works
and
how
people
can
continue
to
be
more
involved
on
that
on
levels
like
that
too.
A
So,
and
and
that's
it,
we
did
have
a
working
group
team
with
just
everyone
involved
or
everyone
who
has
some
role
in
the
working
group,
so
that
someone
can
at
this
team
it
can
add
each
other
as
needed.
That's
that's
not
yet
clear
exactly
how
that
works.
We
do
have
an
open
issue
for
that,
and
I
believe
that
leonardo,
you
and
dan-
and
I
can
get
to
that
in
the
next
chairs
meeting.
We
can
also
talk
about
it
here.
A
If,
if
there's
not
some
other
higher
priority
thing,
let's
look
and
see
if
there's
yeah,
no
other
agenda
topics,
yet
I
don't
see
any
raised
hands.
So
after
discussing
this
item
we
could
we
could.
We
could
look
at
the
proposal
for
oh,
let's
see
here.
A
A
B
No,
no,
just
just
that,
it's
it's!
It's
a
open,
invite
to
any
committee,
so
not
just
the
ones
that
we
need
help
in,
but
just
in
just
in
general
right.
If
you
want
to
do
the
principles
committee
as
well
and
other
other
committees
where
just
we
have
a
general
slack
on
the
cncf
slack.
So
just
at
one
of
us
and
we'll
point
you
the
right
people
to
get
involved
so
and.
E
A
Well,
let's
take
one
quick
look
at
the
at
the
the
project-
governance
pr
and
see
if
this
kind
of
fits
the
bill
for
you.
A
Okay,
so
inside,
let's
just
just
look
at
this
file
in
a
way,
that's
a
little
bit
more
viewable.
A
So
currently,
let
me
blow
this
up
a
little.
I
don't
know.
If
can
folks
read
this?
Yes,
okay,
so
in
the
current
governance
pull
request,
there
is
a
roles
section,
and
that
is
there's
basically
several
sections.
There's
roles,
elections
and
decision
making
and
those
are
the
three
main
sections
underneath
roles.
A
There's
all
members
and
there's
a
description
about
how
this
is
an
open
public
working
group,
that's
welcoming
to
everyone
who
would
like
to
join
and
be
and
be
involved
and
and
that
there's
no
special
requirements
apart
from
responsibilities
listed
below-
and
this
is
already
this
part
is
already
written
in
in
in
some
form
in
the
current
governance.
So
this
is
not
big
news,
but
just
follow
the
code
of
conduct
the
cncf
code
of
contact.
That's
that's!
A
The
only
real
requirement,
aside
from
what
one
can't
do
is
that
members
of
the
good
ops
working
group
cannot
must
not
or
may
not
create
the
impression
that
they
have
any
authority
or
formal
responsibilities
within
the
get
ups
working
grip.
Apart
from
any
explicitly
assigned
roles
that
are
below
so,
I
think
that's,
I
hope
that's
very
clear,
and
I'm
pretty
sure
everyone
in
this
call
understands
that.
That's
just
the
caveat
to
being
a
completely
open
group.
B
Yeah
so
there's
there's
a
there's:
an
implicit
follow,
cncf
and
a
explicit
responsibility
clause.
Essentially.
E
Don't
you
think,
scott
that
we
might
want
to
move
the
committees
out
of
the
government
governance
stocks
explicitly
because
of
two
reasons?
I
I
don't
think
there's
going
to
be
a
lot
of
contention
or
or
need
to
agree
as
much
as
governance
and
committees
are
going
to
be
you're
going
to
change
much
more
often,
governance
is
going
to
stick
around
but
like
the
get
up,
sconce
committee
likely
can
already
be
kind
of
eliminated
right.
E
A
No
thanks
and
by
the
way,
so
I'm
a
little
low
energy
today,
but
just
so
you
all
know,
I
am
super
amped
about
how
everything
is
going
with
the
gaps
working
group
and
the
open,
get
ups
project
and
the
cncf
onboarding
and
how
github's
con
went
and
everything
I'm
just
like
really
and
really
excited
about
the
near
future
too.
So
I'm
just
that's
not
being
conveyed
in
my
voice
today,
but
trust
me
just
listen
to
some
of
the
past
recordings,
even
like
a
minute
or
two
of
them
and
you'll
you'll
see
the
difference.
A
Nothing!
Nothing
really
depressing
with
the
get-offs
working
group
has
happened.
I'm
just
very
under
the
web,
so
just
wanted
to
say
that
okay,
but
thanks
leonardo,
yes,
that's
great
and.
E
A
That
sounds
great.
There
is
an
open
pull
request
by
by
alison
doughny
about
having
a
contributing
document,
and
it's
just
that
we
really,
I
think,
have
to
connect
all
together
and
collaborate
on
that
a
bit
more
because
it
needs
a
bit
of
work.
But
you
know
allison
is
a
you
know,
cncf
ambassador
very
involved
in
the
in
the
the
this.
Excuse
me
the
cncf
country
sink.
Oh,
my
gosh
sig
contrib
x.
D
A
Contribution
guidelines
and
ladders,
if
you
want
to
call
them
that
or
or
whatever
so
so.
What
I
was
thinking
initially
leonardo
is
that
I
just
kept
some
of
the
stuff
smashed
into
the
governance,
with
the
idea
that
the
the
the
parts
that
relate
to
contributing
specifically
and
how
you
get
there
would
be
move
to
a
contributing
doc.
But
maybe
it
should
be
part
of
the
same
pr,
I'm
not
sure
so
yeah.
Thank
you.
E
I
think,
as
long
as
we
move,
because
I
think
right
now,
we
probably
want
to
encourage
the
community
to
take
an
active
role
and
since
governance
is
going
to
be
a
more
elaborate
process,
as
as
long
as
we
can
kind
of
provide
this
ability
into
two
things
which
committees
are
available
and
what
is
like.
One
bullet
as
to
this
is
how
you
can
volunteer
for
a
committee
like
open
up
an
issue
or
whatever
it
is.
That
already
clears
the
path
to
others
that
want
to
support,
and
that's
just
going
to
increase
our
throughput.
A
A
In
fact,
what
leonardo
is
doing
right
now
is
is
very
or
saying
to
christian's.
Point
earlier
is
very
in
line
with
with
response
with
the
current
idea
of
responsibilities
for
the
chairs,
which
is
to
ensure
the
promotion
of
continued
open
involvement
for
the
working
group.
So
thank
you
thank
you
and
both
of
you
for
that
yeah
and
then
like
how
decisions
are
made.
So
if
anyone
has
any
any
thoughts
about
this
or
any
objections,
nothing
should
be
out
of
line
with
standards
of
other
other
cncf
projects.
A
But
please
have
a
look.
That's
a
way
to
get
involved.
A
A
So
if
you
want
to
see
that
real,
quick,
the
getups
working
group
logo
is
here,
pretty
cool
the.
In
fact,
let's
go
to
cncf
artwork
real
quick.
A
Yeah
and
then
under
the
inc
under
the
sandbox
project,
there's
a
lot
of
open
things.
Open,
git
ops
is
one
of
them
right,
so
that
is
there
and
then
other
cncf
logos.
There
is
the
get
ups
working
group
because
it's
not
a
project.
It's
for
a
working
group,
most
working
groups,
don't
have
logos,
but
we
do
which
is
very
cool,
and
here
they
are
so
so
I'll
paste
the
link
in
for
all
of
you,
but
essentially,
if
you
want
to
check
out
you
know
any
of
these,
the
horizontal
stacks.
A
A
C
A
Anyway,
so
that's
so
that's
that
one
and
then
the
and
then
the
excuse
me
and
then
the
git
ups
working
group
you
saw,
but
just
so
you
can
see
all
of
the
different
variations
for
horizontal
stacked,
just
icon,
etc.
Here
so
I'll
paste
these
in.
A
A
A
Well,
there's
a
few
there's
a
few
things
like
just
behind
the
scenes,
or
you
know,
housekeeping
stuff,
like
deb
stats
for
projects
that
has
to
be
sorted
out.
Some
of
the
other
files
need
to
be
moved
just
or
copied
into
the
opengd
ops
project
and
at
the
very
very
least
there
are
there's
a
licenses,
pr
that
needs
to
be
merged
or
it
needs
to
be
approved
and
then
merged.
There
is
a
the
the
same.
Maintainers
need
to
be
added
so
that
they
can
do
that.
A
Programmatically,
there's
a
few
things
like
that,
but
all
all
of
all
of
that
housekeeping,
I
think,
is
in
the
on
the
project
board
for
open
getup
setup
that
I
was
showing
you
where
the
project
boards
were
earlier.
So
that's
that's
my
updates.
I
don't
really
aside
from
that.
Getupscon
was
awesome.
A
I
don't
know
if
anyone
here
didn't
go
to
that
or
maybe
there
are
people
listening
to
the
video
later,
who
haven't?
Who
didn't
go
to
that,
but
all
of
the
videos
are
have
been
up
on
the
get-offs
working
group
youtube
channel.
A
So
here
we
go.
Let
me
pass
that
channel
to
you
all
check
out
the
playlists
all
of
the
get
opticon
stuff
for
getupscon
eu
2021.
I
guess
we
need
to
put
eu
in.
There
is
here
and
yeah.
B
I
gotta
say
I
gotta
say
it
was
a
great
event,
just
like
a
big
recorded
and
public.
Thank
you
to
everyone
who
was
involved,
scott
leo
robert.
You
know
people
not
on
right
aubry
sonia
chris
short
like
it.
We
had
an
opportunity
to
put
this
on
and
it
was.
It
was
really
short
notice
and
it
everything
that
went
down
and
everything
that
happened.
B
It
went
short
notice.
We
did
it
like
with
really
really
short
short
notice
and
also
public.
Thank
you
to
the
all
the
presenters
and
everyone
who
recorded,
because
we
essentially
asked
them
to
record
and
upload
like
within
a
week
of
their
and
like
we
got
everyone's
recording
and
it
was.
B
It
turned
out
really
well,
so
we
we
hope
to
get
a
a
better
event
now
that
we
have
more
time
right
now
that,
like
okay
yeah,
we
can
do
this
for
for
for
kubecon,
north
america
and
so
yeah,
so
just
kind
of
just
public.
Thank
you
to
everyone.
It
was
kind
of
nerve-wracking
there
for
a
little
bit
because
of
the
short
timelines,
but
we
ended
up
doing
it
and
we
couldn't
have
done
it
with
all
the
the
volunteer
help.
B
So
again,
this
is
another
call
for
volunteers
like
it.
It
is.
It
is
very
helpful,
especially
when
you're
doing
things
in
in
short,
short
timelines,
so
it
was,
if
you
haven't
checked
it
out,
is
the
youtube
play.
This
is
there
as
scott
was
pointing
out,
it
was
really
great.
A
Yeah
and
that's
coming
together,
that's
going
to
be
the
organizing
of
that
is
going
to
be
starting
very
soon,
so
don't
wait
till
kubecon
n
a
to
to
to
volunteer
if
you
want
to
be
involved
in
any
way
in
helping
there's
different
things
that
people
do,
they
don't
have
to
organize
every
every
part
of
it.
B
So
I
do,
I
do
have
a
question.
I
don't
know
who's
who
here
we
can
ask
that
is
like
a
cncf
ambassador
or
anything.
I
haven't
heard
anything
in
terms
of
north
because
I
think
n
a
is
scheduled
to
be
here
in
the
los
angeles
convention
center.
Actually
I
live
nearby
here
so,
but
I
don't
know
if
it's
going
to
be
like
a
hybrid
event
in
terms
like
hybrid
live
hybrid,
you
know
virtual.
B
So
you
know
in
in
terms
of
trying
to
plan
for
the
next
get
ops
con.
It's
gonna,
I
guess
you're
gonna
depend
heavily
on
what
the
cncf
is.
Gonna
do
in
terms
of
like
a
live
event
versus
a
virtual
event,
so.
F
No,
I
have
that
it
might
very
well
be
hybrid,
so
I
think
the
best
option
is
to
just
prepare
for
both
kind
of
delivery
in
person
and
and
and
online
also
makes
for
more
inclusive
event,
because
then,
no
matter,
if
you
can
attend
or
can
do
it
from
from
your
own,
you
you
you
can
have
similar
experiences.
You
know,
I
think,
that's
that's
the
old
point
of
going
hybrid
for
for
kubecon
and
the
satellite
events.
A
Is
there
does
anyone
have
any
other
questions
or
anything
any
or
just
want
to
chat
at
all?
If
not
you're,
not
a
captive
audience,
we
can
give
you
back
eight
extra
minutes
of
your
life,
but
the
floor
is
open.
If
you
want
to
say
something,
please
raise
your
hand
or
speak
up.
Give
it
a
minute.
F
Just
a
minor
thing:
do
we
collect
talks
about
githubs?
I
just
recorded
one
for
devops
connect,
which
is
part
of
the
lsa
conference
next
week.
So
do
we
as
members
or.
A
F
Yeah
yeah
sure
I
I
was
just
looking.
There
is
a
really
awesome.
Guitars
list.
Could
everybody
works,
so
we
can
have
just
just
a
list
maintained
by
us
of
talks,
presentations
about
githubs,
not
not
per
se,
done
only
by
members,
but
in
general,
like
what
we
see
we
see
around.
A
That
makes
a
lot
of
sense
and
and
and
one
one
thing
I
we
know
that
is
in
the
works
that
that
dan
is
leading.
Currently
is
the
website
committee
it
didn't.
We
didn't
have
that
on
our
github
teams,
yet
that
needs
to
be
formalized,
but
it's
it's
it's
getting
started
and.
A
In
what
ways
should
or
could
or
is
it?
You
know,
within
the
scope
of
the
good
ops
working
group
to
amplify
all
of
the
other
things
in
the
world
that
are
happening
that
relate
to
get
ops?
It
does
seem
to
me
very
clearly
within
scope,
but
but
that's
not
an
official
word.
We
would
have
to
really
just
communicate
on
the
github
discussion
and
try
to
reach
basic
consensus
on
on
that,
because
not
only
one
thing
I
want
to
notice.
A
Not
only
would
someone
have
to
maintain
that,
but
we
want
to
be
clear
that,
if
we're
going
to
include
that
in
the
scope
of
the
group
that
we
do
a
good
job
at
it,
so
I
think
personally,
I
think
it
would
require
a
few
more
volunteers
for
people
who
are
on
the
lookout
for
things
like
that
and
some
processes
for
how
to
raise
these
events
or
how
people
can
list
these
events
or
ask
the
get
office
working
group
to
amplify
those
events.
You
know
what
I
mean
yeah,
that's.
A
Yeah,
perfect
yeah.
I
love
that
too.
I
would
love.
I
think
that
was
part
of
the
initial
vision
of
the
working
group.
That's
just
not
something
that
we've
done
too
much
of
right.
Now
I
will
say
there
have
been
a
few
notes
that
we
have
a
few
points
that
we've
made
to
specifically
try
to
amplify.
Other
other
excuse
me
other
events
in
the
community.
A
In
fact,
we
should
probably
mention
those
at
the
very
end
here,
because
there
are
a
couple
coming
up
that
are
big
ones.
One
was
mentioned
earlier,
get
off
stays,
I
think,
that's
june,
9th
and
10th.
I
hope
I'm
not
wrong
about
that.
A
Yeah
get
upstairs.com
yeah
june,
9th
and
10th.
Please
get
it
yeah.
I
guess
I'll
just
add
this
in
the
notes.
Announcements
at
the
end.
A
A
Cdcon
yeah,
that
was
what
I
was
really
struggling
for
here,
okay,
so
the
getup
summit
and
several
people
from
the
cd
foundation
spoke
during
the
get
ops
con
that
the
getups
working
group
organized.
So
we're
really
definitely
in
good
in
pretty
good
communication
across
the
foundations,
so
really
just
trying
to
make
sure
that
there
is,
you
know
no
one
really
has
control
over
what
other
people
do.
You
know
outside
of
any
outside
of
agreements
right
and
licenses
and
so
on,
but
it's
it's
not
about
that.
A
It's
more
about
just
working
together
to
build
bridges
and
and
help
really
build
this
community,
as
git
ops
is
seems
to
be
at
least
I
I
would
say
quickly
becoming
a
new
standard
for
for
for
it
and
applications.
A
Okay,
so
I'll
paste
that
here.
Thank
you
thank
you.
Do
we
have
any
other
announcements
while
we're
at
it
before
we
round
off.
A
Okay
cool!
Well
then,
you
know
thanks
everybody
for
coming,
I'm
looking
forward
to
the
next
month's
meeting
and
please
check
out.
I
just
want
to
show
you
one
other
thing,
since
I'm
sharing
my
screen
right
now,
please
open
up
the
the
the
outline
in
the
google
in
the
meetings,
google
doc.
A
It
lists
the
all
of
the
notes
and
agenda
for
each
of
the
meetings
and
and
and
meetings
that
are
specifically
like
this
is
for
our
monthly
meeting
right
and
then
the
principals
committee
has
had
their
own
meetings
and
so
has
the
get
opticon
committee
committee.
I
suppose
we
can
also
christianity
suppose
we
can
also
rename
that.
A
Yeah,
both
here
and
in
the
events
markdown
file
inside
of
the.
C
A
Yeah
right
now,
it's
excuse
me
right
now.
I
think
this
is
probably
just
the
last
note.
Is
that
please
everyone
note
that
we
do
have
a
meetings.
I
said
events,
but
we
have
a
meetings
markdown
file
which
which,
which
has
basic
links
to
all
of
those
same
places.
It's
got
links
to
the
youtube
recording
the
text
chat
for
each
which
is
stored
in
in
the
github
repo
and
a
link
to
the
notes
section
for
each
of
those
committees
in
the
monthly
meeting.