►
From YouTube: GitOps Principles Committee Weekly Meeting 20210519
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
Brilliant,
so
in
the
absence
of
scott,
does
anybody
want
to
volunteer
as
moderator.
A
I
guess
I
opened
my
mouth
first,
so
that's
I
have
volunteered
by
default.
Didn't
I
okay,
yeah
no
worries
so
so
I
think
the
agenda
for
today
is
so
firstly
for
those
of
you
who
are
watching
this
in
the
future.
Welcome
to
the
we
the
get
offs
principles
committee
meeting
on
the
wednesday
19th
of
may
2021.
A
Today
the
agenda
is
to
review
the
status
of
the
pr
for
the
principles,
the
initial
principles
document
and
is
there
any
other
agenda
from
a
topic
from
the
people
here.
A
B
A
Right
so
scott
opened
this
a
week
ago,
just
before
the
previous,
the
previous
meeting,
I
I
took
a
look
at
this
earlier
and
couldn't
approve
it.
I
don't
think
I
don't
know
why,
but
I
wasn't
able
to
prove
that,
but
I
think
some
of
us
have
approved
it.
If
I'm
not
mistaken,.
A
But
there's
been
fairly
active
discussion
yeah
so
on
the
pr
does
anybody
want
to
get
us
started
about
discussing
this.
B
B
No,
I
I
mean
the
the
the
principles
documents,
the
principles
that
the
the
of
this
and
moshe
did,
I
think,
is
everything
resolved
now
right.
B
Sorry,
please
yeah,
I
I
I
just
mean,
like
everything
that's
been
opened
on
this
pull
request
have
been
resolved
right.
There's
nothing
left
to
to
take
any
decisions
in
regards
of
I'm
I'm
redecorating.
So
I'm
really
tired.
C
There's
it
doesn't.
C
C
A
B
E
I'm
blowing
up
formality
here.
Forgive
me
just
for
the
folks
that
weren't
on
last
week's
meeting.
E
E
B
A
Yeah,
I
think
it
just
needs
to
be
merged
with
somebody
with
right
access
to
the
repository.
I
I
can
take
an
action
to
chase
this
up
outside
of
outside
of
this
meeting,
to
try
and
get
it
merged
before
the
next
one.
A
Okay,
so
if
we
have
a
mergeable
pr,
I
can
we
can
chase
getting
that
merged
in
until
between
this
meeting
and
the
next
any
other
topic.
Anybody
else
would
like
to
add
to
the
agenda
today.
C
Yeah,
I
don't
have
a,
I
don't,
have
the
link
for
it
hold
on
in
order
to
add
it,
but
my
meeting
agenda
there-
it
is
sorry,
I'm
looking
at
the
calendar.
Invite
one
thing
I
do
want
to
discuss
is
like
now
that
we
have
this
merged.
What
what
are
the
next
steps?
I
guess
like?
Where
do
we
go
from
from
here
now?
I
guess
would
be
the
next
topic
of
discussion.
C
It
would
be
nice
to
at
least
have
the
discussion
right
like
where,
because
I
know
merging
it
it
we
open
it
up
now
to
to
everyone
else
for
feedback.
When
do
we
like?
What's
the
next
steps
right,
how
what's
the?
What's?
What
do
we
envision
so
action
topics?
Thank
you,
breese
I'll
see
you.
A
Writing
that
down
so
I
mean
a
question,
was
what
the?
A
What
are
we
doing
about
explanatory
notes?
So
I
believe
that
last
time,
a
couple
of
weeks
ago,
we
were
talking
about
additional
notes.
I
took
an
action
away
to
write
some
of
those
I've
not
managed
to
complete
that
yet,
but
that
is
still
on
my
to-do
list
and
I
still
intend
to
get
round
to
that.
Do
we
have
any
more
people
who
would
like
to
provide
an
additional
note?
A
I
believe
that
moshe
had
another
a
note
to
provide
on
kind
of
details
about
reconciliation,
loops
and,
in
particular,
open
and
closed
systems
open
and
closed
loops
when
it
comes
to
state
reconciliation,
and
I
thought
that
that
would
be
a
good
addition
do
we
have
any
additional
notes
that
we
want
to
go
through
any
additions
to
these
principles
that
we
want
to.
D
Yeah,
so
I
I
agree,
I
think
that
people
have
you
know,
remember
that
the
get
ups
working
group
is
about
education
and
about
helping
people
kind
of
embrace
and
adopt,
and
so
I
absolutely
feel
like
writing
down.
The
principles
is
only
step
one
and
there
we
now
have
to
help
people
understand
them
and
people,
and
that's
going
to
come
through
a
number
of
different.
It's
going
to
come
through
repetition.
It's
going
to
come
through
examples.
It's
going
to
come
through
a
whole
bunch
of
things,
so
I
think
posters.
D
D
And
so
then
it
also
led
me
to
think
okay
well,
what's
up
with
the
with
the
website
team,
so
some
of
these
assets
that
we're
talking
about
building
we
have
to
have
a
place
to
put
them.
I
don't
want
to
just
think
I'm
going
to
get
repository,
we're
talking
about
a
bit
of
a
marketing
exercise
around
this.
C
Yeah,
I
absolutely
agree-
and
I
think
that's
an
excellent
point
cornelia-
is
that,
like
okay,
now
that
now
that
we
have
them
having
them
in
a
git
repo,
you
know
that
that's
the
it's!
You
use
an
interesting
word
like
sticking
them
in
it.
It's
it's
almost
like
you're
sticking
in
a
drawer
and
forgetting
about
them.
C
B
Could
we
could
we
possibly
have
a
type
of
slide
deck
like
done
presentation,
or
or
at
least
something
just
start
off
with
I'm
probably
going
to
do
a
get
ups
talk
internally
at
crayon
very
soon
and
having
those
kind
of
things
ready
to
go,
so
I
can
just
talk
about
it
not
having
to
prepare
a
lot.
That
would
be
great.
D
A
I
I
I
believe
that's
been
set
up
as
part
of
the
project.
I
I
don't
have
the
details,
so
scott
and
yourself,
I
think,
had
access
to
the
cncf
org
around
this.
But
in
the
meantime,
if,
if
there's
a
a
simple
way
of
sharing
things,
any
any
kind
of
publicly
hosted
documents,
I
think
would
work.
D
D
I
don't
know
if
they've
posted
all
of
the
kubecon
talks
yet,
but
we
can,
you
know,
certainly
link
to
the
the
presentation,
but
then
for
for
people
like
you,
robert
who
want
to
do
a
presentation,
you
may
not
want
to
use
exactly
those
slides
it
has
cncf
branding
on
it,
etc,
etc.
A
I've
got
to
say
I
really
like
the
idea
of
a
github's
media
kit.
That's
yeah,
make
sure
everything
is
on
brand,
make
sure
the
the
principles
and
the
practices
are
represented
accurately,
and,
and
I
mean
we
have
a
logo,
so
some
some
guidelines
around
how
to
use
the
logo
when
to
use
it
and
when
it's
not
appropriate
to
use.
It
sounds
quite
sensible
as
an
overall
thing.
A
Do
we
have
so
what
what
do
we
think
are
the
best
next
steps
then
to
to
make
this
happen?
Should
somebody
take
an
action
away?
Should
we
schedule
pairing
sessions
to
kind
of
do
some
of
these
actions?
What
would
be
the
best
way
of
of
making
those
things
happen?.
E
I
could
take
an
ai
on
connecting
with
the
website
team
because
I
think
I'm
on
it,
so
I
can
just
ping
dan.
I
think
he
might
have
been
waiting
for
some
things
to
settle
here
so
might
be
time
to
to
ping
them.
So
I
can
do
that
one
thing
not
to
rewind,
but
I
sorry
I
got
a
little
distracted
here
with
something
so
another
next
step
outside
of
this
but
kind
of
up.
E
So
I
think
scott-
and
I
were
talking
about
maybe
getting
together
and
just
trying
to
put
a
narrative
together
to
accompany
the
principles
which
is
based
on
a
lot
of
what
you
had
written,
brees
and
others
that
was
from
last
week.
So
that's
an
ai
that
we
can
carry
forward
as
well.
A
So
would
you
could
you
give
me
more
details
about
what
that
would
what
that
would
be,
so
this
would
be
writing
the
explanatory
note
or
adding
context
adding
a
history
section.
E
No
more
context
and
and
narrative
support
of
the
of
the
principles.
Okay
and
probably
in
its
own
markdown,.
E
A
What
I
would
say
is
that
there
is
a
soon
to
be
a
podcast
where
some
of
us
are
going
to
be
talking
about
this.
Exactly
for
some
reason,
I
can't
type
anymore,
but
one
thing
that
could
work
quite
well
would
be
to
use
the
recording
and
have
that
transcribed
and
then
use
that
at
the
basis
for
the
materials,
because
I
think
we're
going
to
talk
about
the
context
in
the
story.
That's
already
something
we've
planned
on
talking
about
during
the
time.
What
what's
the
opinion
on
that?
A
I
think
that
might
be
you
know
we
can
send
that
off
to
be
transcribed
very
quickly
and
that
can
form
the
basis
of
a
document
that
we
can
use
as
an
initial
draft.
A
A
So
I
I
I
can
do
that
after
our
podcast
cornelia,
you're
hosting.
Is
there
anything
else
that
might
be
worth
mentioning
about
that.
A
A
A
Githubs
and
for
the
sake
of
the
recording
and
for
people
who
might
not
be
familiar,
this
is
the
idea
that,
under
what
condition,
what
emergency
conditions
can
we
not
act
in
accordance
to
the
principles
and
and
what
are
kind
of
the
best
practices
around
that
there
was
a
mention
of
immediacy
and
distributed
system.
C
Right,
like
you,
have
like
the
principles
and
then
like
when
I
guess
I
don't,
like
the
word
exceptions,
so
I
do
like
break
the
glass
like
when
to
break
the
glass.
Maybe
keep
that
keep
that
verbiage,
but
it's
almost
like
you're
you're
writing
those
like
when,
when
don't
I
get
ops
in
a
get
ups
workflow.
A
Yeah
and
a
really
clear
one
is
the
bootstrapping
process.
So
it's
it's.
You
can't
create
a
github
system
without
having
some
software
operating
already
and
obviously
that's
a
system
that
software
can't
be
installed
via
githubs,
because
you
don't
have
a
github
system
yet
so
the
question
becomes,
you
know
how
do
you
bootstrap
a
github
system
and
what's
the
lowest
level,
so
I
think
we
had.
A
E
We
want
to
talk
about
adoption,
planning
and
the
maturity
models,
or
do
we
want
to
defer
you?
Yes,.
A
Yes,
okay,
good,
so
I
think
adoption
path
and
maturity
model
for
githubs
are
both
things
that
are
going
to
be
very
useful,
especially
for
communicating
get
ups
and
and
getting
githubs
adopted.
So
I
I
think
those
are
fairly
big
things,
so
the
some
of
the
other
ones
are
just
quite
quick
notes,
maybe
a
few
paragraphs,
but
I
think
an
adoption
path
and
a
maturity
model
are
slightly
more
complex.
But,
yes,
I
think
those
are
absolutely
worthwhile.
I
would
second
that.
A
Okay,
so
we
we
have
clear
so
some
some
kind
of
additional
notes
to
write.
We
have
a
set
of
things
to
do
around
the
media
kit.
I
think
this
is
essentially.
This
will
be
captured
by
getting
the
recording
transcribed.
A
But
we
don't
really
have,
and
there
are
some
outstanding
action
items
around
the
additional
notes.
So
is
there
anything
else
that
we
want
to
take
away
and
do
and
before
the
next
meeting?
A
D
So
I
I
want
to
come
back
to,
and
I
know
that
somebody
took
the
action
night
of
jesse.
You
took
the
action
item
to
talk
to
dan
about
website,
so
I'm
kind
of
thinking
like
the
website
should
have
a
blog.
D
And
so
all
of
these
assets
that
we're
talking
about
feel
like
just
like
a
regular
cadence
of
blog
posts
and
then
it
feels
like
as
the
industry.
As
you
know,
we
have
these
various
events
and
people
ask
these
questions
about.
How
should
I
structure
my
repositories?
Should
I
have
multiple
repositories,
et
cetera,
et
cetera?
That's
where
we
can
continue
so
there's,
there's
always
this
tension
of?
Are
these
blog
posts
or
these
assets
that
we
put
in
a
github
repository,
and
I
guess
it
depends.
D
It
depends
on
if
it's
just
if
it's
a
narrative
or
if
it's
a
narrative
that
comes
with
sample
code
or
something
like
that.
But
I'm
feeling
like
a
lot
of
these
topics
are
like
blog
topics
like
open,
github's,
blog
topics.
A
A
E
I
don't
I
don't
know
if
they've
been
meeting
or
not
the
the
slack,
the
slack
channel
doesn't
have
any
traffic
really.
So
I
I
just
ping
dan.
So
I
can.
I
can
take
that.
I
can
talk
about
the
blog
there
too,
and
just
see
if
see
if
we
can
get
things
spun
up
or
get
an
idea
of
if
they
already
spun
up.
A
Yeah,
I
mean
by
by
default
a
really
cheap
and
easy
way
of
doing.
That
would
be
to
set
up
a
repository
under
the
open,
githubs
organization
and
then
go
ahead
and
create
a
github
github
pages.
I
believe
we
we
can
set
up
custom
domains
so
that
that's
a
next
level
up
discussion,
but
there's
a
question
about
which
having
the
open
githubs
domain.
So
if
we
could
point
the
open,
githubs
domain
to
github
pages
and
we
can
get
the
s
tls
certificate
set
up,
that
would
probably
be
good
enough
to
start
with.
A
I
feel-
and
we
we
already
had
some
quite
awesome-
design
input
for
logo,
design
and
stuff,
so
I'm
sure
we'd
get
community
contribution
to
make
the
website
very
attractive
and
effective.
So
if
we
got
that
started,
I
think
we
could
iterate
on
that
quite
well,
but
I
defer
to
the
website
team
on
that.
Obviously,.
A
So
I
I
think,
writing
those
topics,
whether
we
end
up
as
blog
or
documents
in
github.
That's
that's.
I
think
that's
that
can
get
started.
What
about
the
poster
and
infographics?
Is
that
something
we
want
to
start
taking
a
look
at
and
is?
Does
anybody
want
to?
Actually
I
mean
you
mentioned
cornelia
that
you
you'd
be
making
your.
A
Yeah
you're
making
your
presentation
available
to
the
github
working
group.
Anything
else
that
we
want
to
take
on
for
the
poster
and
the
infographics.
D
So
the
other
thing
that
I'll
I'll
offer
up-
and
I
don't
you
can't-
please
forgive
me
if
I've
told
you
all
this
already,
but
I
don't
think
all
of
you
have
heard
this.
So
one
of
the
communities
that
I'm
super
involved
in
is
the
devops
enterprise
community.
D
So
this
is
gene
kim's
community
and
we
had
an
event
about
a
month
ago,
which
happens
once
a
year
where
a
whole
bunch
of
devops
peeps
get
together
about
50
of
us
get
together
and
for
three
days
of
sharing
and
working
and
we
build
white
papers.
And
this
year
I
brought
a
topic
which
is
I
provocatively
titled.
It
does
get
up
to
replace
devops
knowing
full
well.
D
The
answer
is
no,
but
we
had
a
team
of
about
four
of
us
who
worked
on
that
topic
for
two
days
and
we
are
publishing
a
a
white
paper
on
that
it'll
be
an
I.t
red
white
paper
and
we
did
a
on
the
last
day.
We
do
a
readout
of
you
know
what
we've
done
so
far
and
the
goal
is
teach
everyone
something,
and
so
we
did
like
a
10
minute.
D
You
know
blurb
on
what
is
get
offs
and
it's
it's
not
exactly
the
way
that
we've
crafted
the
principles
here,
but
it's
it's
something
that
we
could
use
as
an
as
a
starting
point.
The
other
thing
that
I'll
mention
is
that
the
the
team,
the
devops
community,
liked
the
presentation
so
much.
D
They
all
recommended
that
we
not
wait
for
the
white
paper
to
be
published,
and
so
we
have
created
a
blog
post
and
itrev
is
going
to
be
publishing
that
blog
post
next
week
and
so
there's
a
few
assets
there
that
we
can
bring
in.
D
D
F
E
I'll
see
if
I
can
find
somebody
I've
seen
some
pretty
cool
stuff.
D
A
So
is
there
anything
else
we
want
to
cover
today,
so
we
have
quite
a
few
actions
to
take,
take
away
we'll
get
some
assets
generated
from
the
upcoming
podcast
or
which
would
be
pretty
kind
of
a
low
low
effort
requirement
from
us
to
kind
of
start
generating
some
some
initial
assets,
any
other
topics
or
anything
else.
We
want
to
talk
about
for
these
two
for
the
additional
notes
on
the
poster.
F
So
I
what
I
understood
from
from
your
comment,
price
breaking
the
glass
is
when
you
intentionally
go
out
of
githubs
in
order
to
achieve
githubs.
A
So
I
think
so
the
the
way
it's
been
used
in
previous
discussion
is:
how
do
you
deal
with
situations
where
you
have
a
strict
requirement?
A
That
would
mean
that
you,
you
break
one
of
the
guitars
principle
and
that
could
be
legislative
requirements
that
could
be,
for
example,
one
one
great
example
is,
if
you
end
up
with
personally
identifiable
information
in
your
state,
store
right,
and
you
have
a
request
to
delete
that
information.
How
do
you
deal
with
it
right?
The
github
principle
states
that
that
should
be
immutable,
and
yet
you
have
a
legal
requirement
to
remove
it.
A
So
so
I
think
in
in
that
case,
most
people
would
pragmatically
say
well,
let's
just
remove
it
manually,
let's,
let's
have
an
exception
to
the
standard
process,
but
there
are
kind
of
other
situations
where
that
might
be
the
case.
One
of
them
is
responding
to
an
incident.
F
Okay,
then,
then,
I
propose
we'll
have
an
an
additional
point
to
additional
nodes,
which
is
out
of
scope,
because
to
me
the
principles
define
like
the
gist
of
what
githubs
is,
and
this
defines
what
is
in
scope
and
to
better
describe
what
is
in
scope
out
of
scope,
often
helps
with
examples.
For
example,.
A
Yeah
so
the
initial,
the
initial
work
scott
and
I
ended
up
doing-
I
had
a
quite
lengthy
section
about
the
scope
of
githubs
and
what
it
should
and
shouldn't
be
applied
to,
but
that
we
kind
of
distilled
that
out
when
we
got
to
the
four
principles.
F
A
Okay,
any
any
other
topic
then,
before
we
close,
I
think
we've
exhausted
those
two
topics
and
we've
got
clear
actions
to
take,
and
hopefully,
by
the
time
we
come
back
to
the
next
meeting,
we'll
have
quite
a
few
documents
to
to
review
together
as
a
group
and
hopefully
a
clear
idea
of
whether
we
can
start
contributing
to
an
open,
github's
blog
and
if
not,
and
maybe
the
the
website
team
needs
a
little
bit
of
help.
A
Any
other
topic
before
we
move
on
to
planning
the
next
meeting.
A
Okay,
that
seems
like
a
no,
so,
in
which
case
we
have
a
a
regular
meeting,
so
the
next,
the
next
time
we
meet
should
be
the
26,
and
I
believe,
26th
of
may.
A
And
anything
we
want
to
explicitly
address
for
the
agenda
for
the
next
meeting.
I
think
so.
A
So
maybe
simply
take
a
look
at
the
website
status
and
review
the
documents
that
have
been
generated
in
the
interval.
C
Yeah,
and
also
if,
if
there's
been,
if
there's
gonna,
be
prs
to
the
notes
right,
we're
gonna
have
to
review
that
pr.
The
pr
right
for
the
notes
I
mean
we
can
do
that
asynchronously
as
well,
but
we
can
talk
about.
There
would
be
a
point
of
discussion.
C
A
Okay,
it
feels
like
we've
got
concrete
things
to
do
now
that
the
principles
are
kind
of
the
draft.
One
of
the
principles
does
this.
Does
this
seem
to
everybody
that
this
is
the
correct
next
step,
or
are
we
missing
something?
Are
we
going
in
the
right
direction.
E
I
think
this
is
all
good
stuff
right.
The
only
feeling
I
have
is
that
not
all
of
this
feels
like
principles,
committee
scoped
stuff,
but
I
think
that's,
okay.
I
think
we
can
initiate
this
nah
and
get
it
rolling.
I
don't
think
we
have
to
be
over.
We
don't
have
to
over
rotate,
but
I
think
that's
just
my
only
observation
and
for
folks
maybe
watching
the
video
later
they
might
be
thinking
the
same.
So.
D
D
Yeah
I
mean,
I
don't
think
all
of
the
work
in
the
get-offs
working
group
has
to
come
in.
A
committee
has
to
come
in
a
formal
committee
and
or
maybe
just
using
this
committee
to
continue
to
advance
the
education
around
the
principles
seems
fair
enough,
but
otherwise
we
could
just
dissolve
this
committee
for
now
and
say:
okay
when
we
get
a
pr,
then
we'll
come
back
together
and
talk,
but
I
think
the
first
thing
to
do
is
to
say
we're
not
done.
You
know
it's
kind
of.
D
Yeah
yeah,
and
so
I
think
that
the
most
urgent
principles
work
is
to
start
to
get
the
word
out,
and
you
know
another
thing
that
it
dawns
on
me
is
like:
where
are
are
all
the
places
that
we
can
start
to
get
the
word
out?
So
there's
the
blog,
but
then
are
there
other
conferences
that
we
want
to
submit
papers
to.
D
You
know,
talks
to
to
to
talk
about
what
we're
doing
and
open
get-offs
and
and
what
the
principles
are
and
the
value
of
them
and
just
keep
evangelizing
them.
It's
really,
I
feel
like
we're
getting
into
an
evangelism
phase
for
a
bit.
A
Yeah-
and
I
mean
there's,
there's
going
to
be
quite
a
few
conferences
coming
up
for
the
rest
of
the
year.
That
would
be
really
highly
suitable
for
this,
both
from
the
cncf,
the
linux
foundation
and
other
organizations.
That
would,
I
think,
benefit
from
from
us
taking
a
look
at
them.
A
So
maybe
what
we
can
do
is
is
have
a
list
next,
next
time
we
meet
have
a
list
of
potential
conferences
and
take
a
look
at
doing
something
as
open,
git
ups
to
to
evangelize
the
principles,
to
kind
of
submit,
an
application
to
upcoming
conferences
as
the
open
githubs
group,
rather
than
as
individuals,
and
try
and
represent
kind
of
the
work
we've
done
to
those
various
kind
of
channels.
E
E
D
Oh,
that
is
a
great
idea.
Yeah.
D
F
D
A
Okay,
so
yeah
jesse,
if
you
could
grab,
grab
some
people
on
slack
and
start
thinking.
Look
that
sounds
excellent.
A
Okay,
any
any
last
topic,
then
I
think
I
think
we
we
we've
got
quite
a
few
things
any
anything
else
we
want
to
go
through
today,
or
should
we
call
this
meeting
to
a
close.
A
All
right,
brilliant,
so
thank
you
all
for
attending
and
to
whoever's
watching
in
the
future.
Thank
you
for
watching
us
talk
about
githubs,
and
hopefully
we
can
see
you
at
the
next.
The
next
get
ups
working
group
principles.
Committee
meeting.
That's
a
that's
a
mouthful
where
we'll
carry
on
and
pick
some
of
those
items
up.
So
thank
you
all
for
coming
today
and
see
you
next
time.