►
From YouTube: GitOps Principles Committee Weekly Meeting 20210811
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
Hi
everyone
welcome
to
the
august
11th
2021
get
ups
working
group
principals
committee
meeting.
I
am
scott
rigby,
I'm
your
host
for
other
guests
anyway,
we're
we're
going
to
be
covering
a
little
bit
about
the
last
working
group
chairs
meeting
in
this
and
pass
the
proposal.
Your
way,
I
know
leo
planned
to
to
do
this,
but
I
think
I'm
guessing
maybe
who
knows
something
may
have
happened.
Power
might
have
gotten
cut.
A
lot
has
been
going
on
today.
A
One
second,
I'm
gonna
paste
into
the
chat
for
those
listening
later.
If
there
is
anyone
listening
later,
you
can
find
this
linked
from
there's
a
google
meetings.
Google
doc
linked
from
the
get
up
working
groups,
github
repos
meetings
document
and
from
the
readme
you'll
you'll,
get
there
pretty
quickly
just
get
to
the
principal's
committee
section
so
yeah.
A
C
A
That's
awesome
leo,
I
just
so
we're
recording
and
do
you
want
to
go
ahead
and
present
what
you
were
going
to
and
I'll
put
an
agenda
item
on
that
I
was
going
to
do
it
in
your
absence.
But
if
you
want
to
well.
C
Actually,
I'm
not
sure
exactly
how
we're
going
to
proceed
now,
because
I
saw
the
message
that
we
had
posted
on
the
principal's
channel
that
we
went
to
cancel
this
one.
Oh
did:
did
you
see
that
there
was.
C
D
E
F
That
no
it
wasn't
this
is.
This
is
confusing.
I
thought
it
was
not
because
of
because
of
the
sea
of
peace.
A
It
does
we
can
certainly
stop
this,
but
if
you,
if
you
want,
we
should
we
just
give
a
high
level
overview
leo,
just
real,
quick
and
then
and
then
make
cut
the
short
and
then
and
then
do
it
next
week.
I
can.
I
can
do
that
if
you
want.
A
Just
might
be
nice
to
give
a
little
bit
of
a
heads
up.
That's
all
like
we
we've
got
some
some
things
to
pass
everyone's
way,
basically
to
all
the
maintainers
and
to
to
this
event,
sorry
principal's
working
group
and
maintainers.
Essentially,
I
think,
we've
all
agreed,
even
though
nick
you're
just
joining
this,
but
we've
we've
been
meeting
about
the
principles
for
months
and
we're
now
in
a
state
of
diminishing
returns
for
the
value
of
each
meeting,
not
that
we
don't
need
to
still
resolve
it.
A
We
do
but
that
this
might
not
be
the
way
to
continue
formatting
it
based
on
you
know,
just
like.
I
think,
we've
noted
it
before
and
I
think
in
past
meetings
over
half
the
group
was
saying:
hey.
Can
we
just
start
doing
this
asynchronously,
and
I
think
I
was
the
one
saying
well
until
it's
resolved.
I
would
rather
keep
meeting
with
anyone
who's
interested,
and
I
think
maybe
that
was
just
me
not
getting
the
hint.
So
there's
that
and
also
we've
received
a
lot
of.
A
We
have
all
collectively
gotten
a
lot
of
given
and
received
a
lot
of
feedback
on
this
so
far
and
and
all
of
our
feedback
hasn't
even
always
made
its
way
into
each
week's
contribution
to
the
principal's
draft
to
the
pr,
because,
because
we
kind
of
keep
getting
sort
of
only
part
way
through
the
agenda,
we
never
really
get
to
the
meat
of
it
or
we
get
to
parts
of
the
meat
of
it.
We're
not
able
to
really
make
it
through
all
of
the
country
all
of
the
feedback.
A
So
the
idea
was
that
we're
gonna
now
bump
this
next
draft
over
to
the
chairs,
to
put
together
a
proposal
that
that
that
we
think
incorporates
all
the
feedback
send
it
to
the
maintainers,
for
you
know,
make
sure
that
that
sounds
correct
and
then
and
then
was
there
anything
missing.
It
then.
C
What
we
want
to
do
is
we
think
at
this
point,
what
might
be
a
good
approach
to
move
forward
is
basically
put
together
a
release
candidate,
given
all
the
information
that
we
have
received
at
this
point,
because
basically,
every
every
principles,
meaning
we're
kind
of
like
almost
recycling,
a
lot
of
the
same
conversations
that
we've
had
over
and
over
right
so
basically
put
together
a
release
candidate,
get
it
in
front
of
the
maintainers
and
make
sure
that
the
maintainers
can
also
using
all
the
recollected
community
feedback
that
we've
received
from
community
input
right.
C
Using
all
that
evaluate
the
release.
Candidates
against
that
have
a
release
candidate
reviewed
by
the
open,
get
ups
maintainers
and
then
open
that
release
candidate
to
basically
a
final
round
of
open
community,
and
actually
one
thing
that
we've
been
discussing
as
of
chairs
is:
there
is
a
there
is
a
listing
of
interested
parties
that
have
not
quite
been
directly
involved
in
any
of
the
principles
calls
and
their
feedback
should
be
considered
as
well,
so
actually
reach
out
to
those
interested
parties
in
the
open,
githubs
project
and
say
hey.
C
You
know
what
this
is.
This
is
a
release
candidate
that
looks
to
integrate
all
the
feedback
and
all
the
knowledge
that
we've
gathered
over
the
past
months
from
everybody
that
participated
and
looked
to
accelerate
the
coming
reaching
this
state
of
consensus
on
top
of
a
release
candidate.
That
would
actually
be
the
the
foundation
of
a
version
1.0.
C
So
it's
kind
of
just
of
what
we've
been
talking
about
looking
to
get
out
of
this
kind
of
like
cycle
of
diminishing
returns.
So
that's
basically
kind
of
elaborating
on
what
scott
mentioned,
so
I'm
gonna
yield
and
christian
your
hands
up
so
go
ahead.
B
Yeah
so
I'll
you
actually
answered
my
question
while
you
were
talking,
but
I'll
still
take.
The
time
I
was
I
was
actually
going
to
ask
was:
is
this
a
risk
candidate
for
v1
or
vo2,
because
I
know
we
were
working
on
o2
for
a
while
are
is?
Is
the
proposal
to
incorporate
what
we've
been
working
on
o2
into
the
release
candidate.
A
Yeah,
so
that
so
here's
the
so
this
this
is,
thank,
you,
hope,
remind
me
later,
okay,
yeah,
so
here's
the
link
to
the
to
the
milestones
that
we
have
in
that
discussion
item
that
we
we
added
as
milestones
this.
A
This
will
essentially
be
to
update
these
milestones
to
be
rc1
rc2,
you
know
like
so,
ultimately,
it
would
be
if
it's
an
rc,
it's
an
rc
towards
the
very
first
full
release
that
we
have,
so
it
would
be
v1,
so
it'd
be
a
bit
basically
like
since
we've
decided
to
follow
symbol,
it'd
be
1.0.0,
dash,
rc.1,
rc.2,
rc.3,
etc.
A
You
know
what
I
mean
and
then
once
we
feel
that
we're
oops,
you
know
what
I'm
saying
once
we
feel
that
we've
we've,
like
all
of
all
the
bases
are
covered
and
we've
covered
everything
that
we
have
in
our
milestones
and
we
don't
have
any.
You
know
extraordinarily
major
showstoppers
as
a
as
a
committee,
then
then
we
can
go
ahead
and
say
all
right:
let's
do
the
b1,
because
until
then
everything
so
far
is
it's
not
even
a
full
release.
We've.
A
We
have
a
lot
of
work
that
that
still
can't
really
be
fully
updated,
yet
we're
still
using
the
version
that
we
had
since
last
november,
which
is
not
bad
it's
just
we
we
we've
identified
that
we
want
to
update
it
somewhat.
C
Of
what
I
at
least
personally,
I've
been
very
much
looking
to
accomplish
this.
I
think
the
principles
are
just
the
beginning.
I
think
once
once
we
have
the
principles,
there
is
a
lot
of
conversation
as
to
how
do
these
principles
actually
apply
in
all
these
different
scenarios
and
use
cases
we've
talked
talked
about.
How
does
security
apply?
How
does
incident
management
apply?
C
How
and
it
seems
to
me
that
we,
the
principles,
will
actually
be
transformed
by
that
process
right,
but
until
we
get
to
a
point
of
actually
having
something
established
as
a
foundation
to
move
forward
into
this
further
level
of
conversation,
we'll
never
get
to
that
point
of
adoration
right.
So
what
I'm
really
kind
of
trying
to
to
drive
us
towards
is
getting
to
a
point
where
the
principles
are
laid
as
a
foundation,
or
we
can
continue
the
conversation
right
and
not
not
keep
this
ongoing
iteration
of
like
finding.
A
Wheels
constantly
yeah
yeah,
I
just
want
to
you,
know
just
real
quick.
I
wanna
I
just
wanna
be
fair
to
like
you
know
like
this,
is
there
has
been
a
lot
of
progress
made
and
I
don't
think
you're
not
saying
that
I
I
think
I
don't
think
you're
saying
the
opposite
of
that.
I
think
you
know
I
mean
because
there's
been
like
many
many
many
meetings
like
this,
they
haven't
all
been
wheel.
Spinning
some
of
them
have
felt
that
way,
and
some
of
them
are.
A
You
know,
I'm
just
trying
to
qualify
this
a
little
bit
from
my
own
perspective.
I
think
everyone
not
only
on
this
call
but
on
the
past,
calls
definitely
wants
to
do
what
you're
saying
and
that
has
been
a
goal,
and
it's
been
stated
a
number
of
times.
We
know
that
this
is
that
these
principles
are
foundational
for
doing
these
other
things
we
have
that
written
in
the
charter,
and
I
definitely
really
appreciate
you
working
like
as
one
of
the
chairs
too
and
trying
to
help
move
this
forward.
A
I
think
the
main
the
main
thing
that
you're,
I
think
that
leo
is
talking
about
that's
different
and
correct
me.
If
I'm
wrong
leo
at
least
than
we've
said
before,
is
that,
instead
of
doing
like
a
continuing
to
have
milestones
that
are
pre
like
major
version
zeros,
let's
go
ahead
and
start
bumping
rc's
and
how.
C
And
how
I'm
also
talking
about
a
little
bit
about
process
right,
I
think
there
is
there,
is,
I
think,
with
the
process
that
we
followed
is
not
that
it
has
not
resolved
resulted
in
a
lot
of
value.
C
C
That
is,
I'm
looking
for
the
right
word
to
kind
of
frame
it
to
reach
consensus
in
a
way
that
everybody's
opinion
is
heard,
as
we've
been
done,
been
doing,
that
everybody's
opinion
is
integrated,
but
that
we
can
get
to
a
point
of
of
progress
right
and
that's
the
reason.
I'm
thinking
this
basically
coming
up
with
a
release
candidate
and
a
series
of
women's
candidates
that
are
basically.
C
What's
the
word
I'm
looking
for
that
are
basically
approved
and
reviewed
by
the
maintainers
and
that
are
open
for
interested
parties,
parties,
commentary,
they're,
open
for
community
commentary
and
that.
But
the
point
is
that
there
is
a
way
to
incorporate
that
into
the
israelis
candidates
and
I
think
that's
what
the
maintainers
are
there
for
right.
The
maintainers
are
there
to
take
the
community
feedback
and
the
community
input
and
coalesce
and
make
it
coherent
right.
C
So
basically,
that's
what
I'm
looking
for,
I'm
looking
for
for
getting
this
in
front
of
all
the
maintainers,
making
sure
that
the
maintainers
agree
making
sure
that
there
is
a
voice
that
is
allowed
that
allows
the
group
that
allows
us
to
consolidate
this
many
many
voices
into
something.
Because
right
now
I
think
we
we
are
very
there's
just
too
many
voices
fragmented
with
the
process
right
and
I
think,
going
through
multiple
rc's,
driven
or
or
guided
by
the
maintainers
listening
and
opening
up
for
the
whole
community.
A
A
Oh
so,
instead
of
oh
geez
well,
so,
instead
of
continuing
on
the
this
process,
we
have
changed
the
process
up
several
times,
but
instead
of
continuing
on
the
process
that
we're
doing
right
now.
Where
we're
having
this
this,
this
weekly
meeting,
where
we
continue
to
chip
away
but
not
necessarily
get
through
through
through
very
far
infection.
A
We
we
moved
to
the
maintainers
to
to
write
a
draft
just
sorry
to
draft
the
next
rc
so
that
rca
can
be,
can
be,
kicked
back
to
this
group
and
other
interested
parties
for
feedback
and
and
changes,
and
we
move
through
the
rc
process,
as
opposed
to
just
like
the
one
hour
weekly
meeting
process,
and
we
try
to
make
that
as
async
as
we
can.
B
B
G
G
Over
and
over
again-
or
you
know,
we
diverge
from
something
and
and
we're
living
in
a
virtual
world
where
everything
is
virtual,
and
I
don't
mind
doing
you
know
these
recurrent
meetings
like
this,
just
not
on
a
weekly
cadence,
because
at
a
certain
point
I
stopped
working
at
four
and
then
I
said
in
these
things,
and
then
I
go
to
bed.
G
You
know
so
you
know
breaking
them
up,
doing
more
work
before
the
meeting
having
the
discussions
and
then
for
someone
to
take
it
on
themselves
to
just
kind
of
just
you
know,
gather
all
the
various
inputs
and
then
we
can
discuss
that
would
make
it
a
lot
easier
to
go
forward.
G
I
think
so
having
a
release,
candidates-
and,
I
said,
like
a
concept
that
sounds
great.
At
the
same
time,
I
would
like
to
have
something
you
know
to
hold
on
to
so,
if,
like
the
meetings
or
if
there
was
like
a
certain
schedule
for
the
releases,
so
you
have
something
to
actually,
you
can
have
in
your
calendar
and
not
get
quadruple
booked
or
something
yeah
which
happens
all
the
time.
G
A
Let
me
share
my
screen
real
quick
just
so
we
can
look
at
the
milestones
because
that's
what
we're
talking
about
now.
Oh
sorry,
christian,
your
hands
raised.
B
No,
I
just
wanted
to
echo
kind
of
what
robert
was
saying
is
that
if
I
would
like
to
keep
the
meetings,
but
if
we
have
a
very
specific
agenda
for
them
like
before
we
before
the
approval
of
a
release
candidate,
you
know
kind
of,
like
I
don't
know
similar
to
like
a
burn
down
call
or
I
I
don't
know
something
like
that.
So
just
echoing
what
robert
was
saying
so
anyways,
I
think
that's
what
you're
about
to
show.
A
A
Just
so
happens
that
right
now,
there's
only
one
issue
tied
to
each
one,
so
I
think
we've
all
agreed
now
that,
like
really
what
that
the
purpose
of
the
these
meetings
can
be
shifted,
essentially
a
triage
while
we
right
well,
so
we
can
prepare
things
like
if
we,
if
we,
if
points
have
been
raised
but
they're
not
written
down
anywhere,
someone
can
be.
A
Someone
can
take
an
action
item.
To
do
that,
these
milestones,
I
was
going
to
say
that
we
can
actually
we
don't
have
to
necessarily
well,
let's,
let's
say
this:
you
know,
for
example,
the
next
milestone
was
going
to
be
today
and,
and
that
was
going
to
be
simplifying
the
principles.
Titles,
that's
not
going
to
happen
today
right,
so
we
were
going
to
do.
We
were
going
to
do
that
and
then
and
the
next
one
was
going
to
be
resolving
the
notes.
A
The
next
one
is
going
to
be
entering
the
accessibility
language
and
then,
hopefully,
at
some
point
sometime
before
kubecon,
we
do
the
full
lease
right.
So
I
think
what
we're
gonna
do
is
change
this
now
and
did
we
have
a
date
for
the
rc
me.
C
Yeah,
sorry
leo,
no,
that's
kind
of
one
of
the
reasons
that
I
I
didn't
quite
feel
prepared
to
go
over
this
all
kind
of
today
was
because
I
think,
there's
that
type
of
nuance
that
we
have
to
figure
out.
C
One
of
the
things
that
we
also
want
to
address
is
kind
of
reach
out
to
the
maintainers
and
kind
of
get
the
maintenance
sense
as
to
what
is
their
availability
right.
You
know
what
I'm
saying:
what
is
a
reasonable
time
frame
for
us
to
expect
feedback,
that
there
is
a
governance
in
place,
that
we
would
look
for
a
simple
majority
for
a
lot
of
these
like
review
processes
right
where
the
maintainers
are
actually
saying
all
right.
C
Yes,
we've
looked
at
the
full
set
of
feedback
from
the
community,
and-
and
we
can
all
agree-
this
is
a
this-
is
our
interpretation
or
an
attempt
to
interpret
what
the
truth
is
telling
us
right
and
now
we
want
to
kind
of
bring
that
back,
because
we
need
to
make
sure
that
we
heard
right.
We
want
to
make
sure
that
there
is
that
there
is
time
and
availability
from
from
them.
C
Another
thing
that
we
were
talking
amongst
us
kind
of
within
the
chairs
is:
what
is
a
good
time
for
us
to
think
about
targeting
an
actual
version.
One
release
right.
We
have
github
comments,
so
would
it
be
that
we
should
be
working
towards
being
able
to
announce
version
1.0
during
github's
con,
which
would
be
great?
If
that's
the
case,
we
would
have
to
walk
work
backwards
from
that
to
see
what
kind
of
type
of
timeframes
we
would
be
looking
at.
So
at
this
point
I
think
it
would
be.
C
A
That
I
just
mentioned:
does
that
make
sense
yep?
So
so
I'm
right,
I'm
basically
so
data
is
optional
for
milestone.
I
won't
add
it,
but
we
agree
that
we're
going
to
do
an
rc,
we're
going
to
have
an
rc1
milestone.
I
just
said:
does
this
sound
right?
First
release
candidate
drafted
by
the
github
working
group,
slash
open,
get
up
to
containers
incorporating
all
discussion
and
feedback
thus
far.
The
goal
is
to
pass
this
back
to
the
principles
committee
for
async
feedback.
C
A
You
know
what
we
we
have
email
for
some
of
the
people,
that's
right
in
the
original.
This
is
what
I
was
thinking.
The
original
google
lock.
This
was
from
okay
linked,
but
then
I
think
folks
just
copy
the
link
style,
and
so
a
lot
of
them
are
linked.
In
any
case,
we'll
say,
I
think
we
don't
need
to
list
that
here.
That
can
just
be
part
of
our
plan
but,
like
we'll
say,
milestone
date
pending.
C
While
you
do
this,
robert
and
jesse
have
your
hands
up,
so
maybe
we
can
robert.
Why
don't
you
go
first?
I
think
you
were
first
of
all
jesse
because
it
might
be
whatever
it
is.
G
Yeah,
I
was
just
well,
let's
see
sorry
adhd
and
my
medicine
is
kicking
off
or
going
away.
G
Yeah
so
due
dates
and
time
boxing
and
everything
like
that,
I
it's
been
brought
up
in
principle
meetings
before
and
some
people
were
strongly
against
setting
dates,
and
things
like
that.
I
think
it's
very
important
to
do
that.
To
have
some
sort
of
deadline.
It
can
be
a
soft
deadline
but
at
least
have
something
to
work
towards.
G
Obviously,
for
for
a
you
know,
milestone
right
now
we
don't
need
to
set
that
you
know
straight
away,
but
we
should
at
least
think
when
we
want
this
done.
So
we
have
something
to
work
against,
and
the
other
thing
I
was
thinking
about
is
the
the
interested
parties
list,
which
I
don't
think
is
totally
complete.
G
It's
probably
gathered
at
the
start
when
everything
started
happening
and
then
just
you
know,
kind
of
crayon
is
not
honest,
but
but
you
know
I've
been
part
of
this
thing
for
many
months
now,
so
you
know
it's
it's
not
totally
updated.
G
B
A
G
C
The
communication
like
process
release
because
we
will
want
to
communicate
this
out
to
the
community.
It
is
the
inner
interesting
part
of
his
scale.
We
don't
have
contact
information,
so
basically,
this
needs
to
be
communicated.
C
Everybody
and
I
think,
a
point
to
make
robert
about
time.
Lines
is
important
right
too,
if
we
reach
out
kind
of
to
communicate
a
sense
of
urgency.
This
is
important.
This
is
happening,
and
you
want
to
add
yourself
now
to
that
right.
Make
sure
that
we
that
we
get
up
people
up
to
date.
The
communication
and
the
slack
channel,
I
think,
is
also
pretty
much
stale
like.
C
I
don't
think
anybody
that
interested
parties
or
a
good
person
with
them
are
not
active
there
so
basically
make
sure
that
this
this
is
effectively
communicated
to
the
entire
community
that
this
communicated
to
the
open,
beta
computers
and
all
the
interesting
parties,
including
soft
dates
or
dates
for
whatever
it's
worth
right
yeah.
So
that's
just
a
quick
response.
Go
ahead,
jason.
D
No,
I
just
it's
sort
of
a
shift.
It's
it's
an
observation
based
on
where,
where
we're
at
in
this
meeting
is
this,
this
is
the
first
time
it's
really
happening.
So
I
pinged
nick
on
the
side
and
said
this
is
an
interesting
first
meeting
to
join.
So
this
does
look
back
to
some
observations
that
I
made
earlier,
so
I'm
just
going
to
reiterate
them.
D
I
think
that
this
as
a
you
know,
we
have
a
working
group
we're
working
on
open
get-ops.
We
have
committee
work,
that's
happening.
I
think
we
all
agree
that
it's
time
to
sort
of
set
some
dates
draw
some
lines
in
the
sand,
deliver
something
back
to
the
overall
working
group.
I
think
that
the
goal
should
be
then
moving
back
to
a
working
group
that
continues
to
work
on
communications.
D
We
improve
the
website.
We
start
working
on
what
the
requirements
are
around
tutorials.
We
make
decisions
around
whether
or
not
we're
looking
at
things
like
I
mean
I
think,
we've
already
made
the
decision,
how
we're
going
to
approach
compliance,
how
we
might
do
that
with
principles
and
no
spec.
All
of
that
needs
to
happen.
I
think,
and
I
I
believe
that
that
should
happen
at
the
working
group
level.
D
I
think
that
the
idea
of
a
working
group
meeting
once
a
month
and
being
primarily
driven
by
a
couple
of
parties
is
probably
needs
to
change
that
might
need
to
become
a
weekly
working
group
meeting
and
based
on
experience
that
I've
had
in
other
working
groups
whether
it
was
way
back
in
the
day
with
with
sas
or
pci
express
or
infiniband
or
more
recently
and
like
open
containers
initiative
that
is
typically
how
this
work
gets
done
is
gonna,
be
it's
a
working
group.
It's
weekly,
you
show
up,
you
do
the
work.
D
If
you
don't
show
up
that's
okay,
too,
we
still
value
your
input
and
your
opinion.
We
will
communicate
the
best
we
can,
but
the
work
has
to
move
forward
and
I
think
the
thrust
of
what
I'm
saying
is
based
on
what
you
know
kind
of
leo
your
observations
and
that
we,
I
think,
we're
beyond
the
you
know.
D
Everyone
has
an
equal
voice,
no
matter
how
much
they
show
up
how
infrequently
they
show
up,
because
that
has
really
started
to
slow
us
down,
and
I
think
we
need
to
start
looking
at
sort
of
quorum
and
boots
on
the
ground.
At
a
particular
meeting
making
decisions
merging
prs
moving
forward,
it's
open
source,
I
mean,
if
somebody's
super
passionate,
they
can
file
a
pull
request
right,
that's
cool!
It's
not
like
we're
writing
things
in
you
know
spray
paint
on
a
brick
wall
and
then
gonna
veneer
it
it
just.
We
need
to
move
forward.
D
I
think
the
better
off
we're
going
to
be
and-
and
I
think
we
I
love
the
idea
of
like
making
sure
all
voices
are
heard,
but
I
think
that
we
have
struggled
with
the
difference
between
you
know,
group,
consensus
and
all
voices
being
heard,
and
I
think
that
is
it's.
I
think
it's
time
for
us
to
move
on
from
that.
C
G
B
Yeah
just
saying
I
completely
agree
with
with
jesse
and
I
think
we've
we've
I
heretofore
completed
the
two
completed
consensus
versus
every
voice
is
heard
right
and
I
think
that's
helped
us
right.
Everybody
started
up
until
this
point
and
now
it
does
seem
like
we're.
It's
now
working
against
us
and
I
I
would
like
to
see
you
know
some
sort
of
consensus
policy.
B
I
guess
for
lack
of
a
better
word
or,
but
how
we
reach
consensus,
whether
it
be
through
like
lazy
consensus
or
I
know
I've
asked
this
in
the
past
and
scott
you,
I
think,
you've
you've
answered
that
that
that
the
chairs
have
been
working
on
it,
but
just
how
consensus
is
reached,
and
you
know
what
what
that
process
is.
You
know,
I
think
I
think
if
we
move
closer
to
that
there
we
go.
Thank
you
for
posting
that
link
yeah.
B
A
Cool
thanks
question
all
right.
Well
with
that
in
mind,
let's,
let's
move
on
right
there's,
it
sounds
like
we're
back
to
the
back
to
the
the
proposal
that
we
agreed
to
do,
but
just
we
didn't,
we
didn't
want
to
pull
the
trigger
just
yet
it
sounds
like
we're
sounds
like
we're
saying:
let's
pull
the
trigger
right,
where
we
have
one
meeting,
that's
weekly,
we
move
from.
A
Two
weekly
meetings
and
one
monthly
meeting
to
just
one
weekly
meeting
where
we
cover
all
the
all
bases
sounds
sounds
good.
I
don't
think
we
so
far.
Everyone
has
agreed
to
this,
so
I
don't
think
we
are
going
to
need
to
have
some
prolonged
process
and.
G
Yeah,
I'm
not
trying
to
word
this
but
but
like,
like
I
mentioned
weekly,
sounds
like
a
lot,
especially
if
there's
no
agenda
before,
like
the
10
minutes
before
things
are
happening,
and
you
know
the
normal
thing
that
kind
of
happens
in
these
things.
G
A
We
discussed
both.
It
was
by
the
way,
and
everybody
said
that
both
of
those
generally
so
for
me,
I
actually
am
not
even
getting
to
that
level
of
detail
like
that's.
That
sounds
fortnightly
sounds
fine
to
me
personally.
Let's
just
do
it
and
if
anybody
has
a
problem
with
it,
we'll
talk
about
it.
D
Can
I
reply
to
that
quick,
oh
yeah,
yeah.
That's
the
only
reason
for
my
hand,
so
yeah
the
week.
The
weekly
is
me
just
drawing
a
line
in
the
sand.
We
can
rub
it
out,
put
it
somewhere
else,
every
two
weeks,
it's
fine.
I
will
say
from
my
previous
observation,
something
like
the
the
oci
runtime
spec
was
very
detailed
and
we
had
a
lot
to
do.
We
met
weekly,
sometimes
more
than
that
for
months.
A
Jesse,
I
love
that.
Would
someone
be
good
enough
to
take
notes
if
they
haven't
already
on
this,
because
this
is
pretty
important
anyway,
I'm
just
going
to
hope.
The
answer
is
yes
from
someone
and
because
my
mind
is
only
able
to
do
one
task
at
a
time
right
now,
cool.
Thank
you
and
we'll
figure
out
the
details
right
we'll
like
get
back
with
the
details,
we
don't
just
waste
time
doing
that
stuff
right
now,
hey
jesse,
you
know,
oci
didn't
take
very
long.
Did
it.
A
Any
case,
let
me
share
my
screen
real
quick,
so
because
we're
talking
right
now,
just
about
like
you
know,
a
basic
triage
thing
right.
So
the
link
that
I
sent
before
is
the
gov.
Is
the
decision
making
we're
not
gonna
go
over
it
all
right
now.
I
just
wanted
to
make
it
clear
that
we
have
inside
of
inside
of
the
governance
dock
and
so
the
working
group
that
is
soon
to
be
moved
to
to
the
open
gate.
Ups
project
lee
and
I
are
working
on
that.
A
Whatever,
maybe
it's
in
the
maybe
it's
in
the
open
gaps
project
anyway,
we
have
an
issue
to
move
files
over
the
appropriate
files
over
so,
for
example,
you'll
see
this
simplify
a
little
bit
so
that
the
the
opengaps
project
is
a
sandbox
project.
The
adopts
working
group
is
a
limited
time.
A
Working
group
under
cncf
delivery,
app
delivery
tag,
so
will
the
working
group
will
have
the
charter
like
a
normal
working
group,
does
and
other
things
that
are
important
for
working
group
related
information
stuff,
that's
important
for
the
opengetops
project
will
move
one
file
at
a
time
through
pull
requests,
as
as
we
have
been
so
far
into
the
openg
ups
project,
we'll
continue
doing
that,
including
this
governance
doc.
A
So
for
now,
and
until
then,
sorry
until
then,
and
even
after
that,
once
it
moves
the
decision,
making
section
stands
the
milestones.
Now
that
we
are
like
doing
this,
these
were
cool
milestones.
Right
like
we
want
to
simplify
the
titles
we
want
to
resolve
the
notes
we
want
to
ensure
the
accessibility
of
all
language.
I
think,
given
that
we
just
talked
about
this,
I
think
I
want
to
suggest
that
we
add
that.
Does
anyone
have
an
objection
to
adding
that
as
part
of
the
the
goals
here
for
this.
G
I
I
think,
that's
fine
and
at
the
same
time,
the
the
simplified
principle,
titles
and
and
these
discussions
they
they
are
taking
a
while.
G
So
if
they
kind
of
get
mostly
done
through
through
you
know,
discussions
or
whatever,
and
then
someone
actually
you
know,
takes
that
and
and
makes
that
something
that
we
can
look
through
and
actually
say
yes
or
no,
but
but
again
this
kind
of
just
and
it's
it's
it's
I
say
this
and
then
I
don't
really
have
any
power
to
do
a
help
or
anything
like
that.
G
It's
it's
kind
of
it's
kind
of
you
know
so
it's
kind
of
hard
for
me
to
say
people
should
do
this,
but
then
I
would
just
consume
it,
but
but
that
would
make
sense
to
me
if
someone
actually
went
through
what's
going
on
in
discussions
and
and
understand,
what's
going
on
there
to
create
something
that
we
actually
can
take
at
this
just
take
a
stand
on
not
just
you
know,
a
bunch
of
the
things
that
are
happening
in
discussions.
If
that
makes.
C
G
To
answer
that
really
quickly,
while
still
holding
it
on
in
my
scatter
brain
the
reason
why
I
say
this
is
because
there's
a
lot
of
things
to
do
in
the
open,
get
out
projects.
So
you
know,
there's
there's,
there's
articles
to
write
or
you
know
best
practice
patterns
whatever
you
want
to
call
it.
There's
documents
to
create
if
everyone
is
really
involved
it's
hard.
G
But
if
someone
for
like,
for
instance,
for
the
principles,
the
decisions
there
and
the
release
candidates
kind
of
like
gather
everything
and
can
explain
to
people,
they
can
just
show
up
and
actually
just
understand
or
read
the
agenda
and
and
make
a
decision
based
on
that
because
being
a
part
of
a
working
group
that
has
so
many
things
happening
is
going
to
be
hard
for
a
lot
of
people,
because
most
people
have
a
job
and.
A
That
makes
sense.
I'm
now
doing
the
thing
where
we
we
move.
We
move
these
to
the
correct
milestones,
so
we're
essentially
closing
since
we're
talking
about
like
mainly
like
planning
and
pr
stuff,
and
not
just
debating
concepts
synchronously
right
where
this
is
for
the
planning,
primarily
now
okay.
So
so
I
just
closed
the
basically
the
the
0.2.0
milestone.
A
A
Okay,
great
so
just
in
terms
of
housekeeping
super
fast,
I'm
gonna
just
go
through
I'm
just
gonna
reattach
these
milestones
and
so
I'll.
Just
do
the
same
thing
so
version
three.
A
And
then
this
milestone
could
be.
C
A
A
A
F
A
A
Is
the
way
to
go
and
under
and
in
our
communication
section
oops
sorry
in
our
communication
section
in
the
get
ups
working
group
how
to
get
involved,
one
of
them
is.
A
A
Yeah,
no,
no
worries,
I
don't
think
it's
like
no
one's
going
to
be
struck
down
smitten
anyway,.
A
Smoke,
I
think
it
is
okay,
so
like
just
to
wrap
up
the
milestones
thing
we
have
two
and
and
and
the
one
we
say
we
at
least
know
we
want
a
version
one
before
get
ops
con.
That's
why
I
marked
it
as
october
12.,
not
that
we
want
to
wait
that
long.
Hopefully
we
do
that
sooner
than
this,
and
this
one
is
pending
the
miles.
The
date
is
pending
maintainer
availability
in
the
coming
weeks
and
we'll
find
that
out-
and
I
think
we're
done
done
with
milestones.
So
I'm
going
to
stop
sharing
my
screen.
A
So
dan
and
I
had
an
action,
write
the
next
blog
post
and
I
think
we
got
pulled
into
other
things.
So,
let's
just
fold
this
in.
If
anyone
wants
to
get
like
you
know
me,
I'm
all
about
collaboration,
let's
just
anybody
who
wants
to
chip
in
on
it.
Let's
do
it
as
long
as
it
doesn't
stop
it
from
happening.
G
B
A
All
right,
awesome,
yeah,
the
the
standing
to
do
that
we
have
is
number
one
make
a
blog
post.
It's
just
like
welcome
to
this
blog.
You
know,
but
instead
of
being
very
generic,
it's
just
like
literally
welcome
to
the
vlog
here's
how
here's
what
it's
for
this
is.
This
is
what
we're
doing
with
like.
A
Right
exactly
so,
not
that
but
like
essentially,
if
we
don't
want
to
be
cheeky,
we
don't
have
to
say
that
we
can
call
it
whatever
we
want,
but
essentially
that
we're
we're
moving
to
the
open,
get
ups
project.
It's
sort
of
announcing,
open,
get-ups,
right
and
and
then.
D
A
Cool
and
it's
all
by
pr
now,
because
so
we
have,
we
don't
have
the
website
fully
automated.
Yet,
interestingly,
the
build
is
not
automated,
but
we
will
get
that
that's
what
to
do
in
the
website,
but.
A
G
A
G
Long
enough,
I
think
yeah
and
as.
G
A
Just
submit
a
pr
you
should
be
able
to
oh
in
the
text.
You
should
be
able
to
you're
right.
We
don't
have
prow
or
anything
set
up,
but
where
is
the
where's
your
pr?
Do
you
mind
sending
that
to
me?
A
A
Yeah
point
of
order
top
of
the
hour
thanks
robert
I'll,
see
you
on
slack
and
see
you
all
on
slack
and
before
our
next
meeting
we'll
have
a
doodle
yeah.
I.