►
From YouTube: 20210805 SIG Arch Enhancements
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
Yes,
okay
cool,
so
today
is
august
5th
2021,
and
this
is
the
sig
art
enhancement,
sub
project
meeting,
I'm
kirsten,
I'm
an
owner
and
we
are.
We
have
two
items
on
our
agenda
which,
for
whatever
reason
I
cannot
find
right
now.
I
don't
know.
If
there's
only
three
of
us,
I
don't
really
think
we
need
to
share
our
screens,
but
we
have
two
items
on
our
agenda
and
the
first
item
is
improvements
to
cap
cdl
by
xander
and
I'm
gonna.
A
Let
him
take
it
away
and
just
give
us
a
little
bit
of
information
about
what
he's
been
working
on
and
maybe
show
us
what
he's
been
working
on
and
kind
of
explain.
You
know
what's
going
on
with
that,
so
take
it
away.
Xander.
B
Sounds
good
looks
like
you
might
need
to
enable
screen
sharing
and
then
I
can
get
that
going.
A
B
C
A
B
Perfect
so
I
started,
I
just
had
some
free
time
on
my
hands
and
I
started
playing
around
with
kept
ctl
and
I
it
kind
of
started
as
me
thinking
about
some
things.
That
would
be
useful,
as
I'm
going
to
take
on
the
enhancements
lead
role
for
the
next
release.
B
Makes
sharing
really
an
adventure?
Okay,
so.
B
C
B
Okay,
perfect,
so
this
is
just
like
my
own
little
kind
of
fork
of
the
project
just
to
like
test
out
some
features
and
then
solicit
some
feedback
before
I
actually
try
to
implement
this
in
the
actual
cuddle
code
base
in
in
the
enhancements
repo.
B
So
the
first
thing
I
added
was
a
gets
call
that's
list
just
to
try
getting
an
individual
cap
rather
than
using
the
the
filter
functionality,
that's
in
the
existing
one,
and
then
this
actually
has
a
flag
dash
o,
which
will
kick
it
straight
to
a
web
browser
and
open
that
enhancement
or
that's
that
cap
issue.
B
So
that's
one
call
and
then
the
the
list
that
I
have
here
is
pretty
similar
to
the
existing
filter
functionality.
You
can
just
do
list
and
filter
by
like
dash
m,
which
is
milestone
for
1.23
and
it'll
fetch.
This
one
takes
a
little
time
to
fetch
those,
and
then
we've
got
like
clickable
links
here
to
open
those
and
then
the
one
main
quality
of
life
thing
that
I
tried
out,
which
I'm
pretty
happy
with.
Is
this
login
functionality?
B
So
if
we
do
kept
ctl
login,
what
it's
going
to
do
is
pop
open
this,
this
github
auth
window
and
spit
out
a
code,
and
we
can
do
3,
7,
c6,
f5,
b3
and
then
authorize
and
then
so
now,
at
the
cli
level.
Here
I
am
authenticated
to
github
with
my
user
and
so
as
like
an
enhancements
maintainer
from
the
cli.
I
could
change
milestones
and
do
that
kind
of
stuff,
and
this
avoids
having
to
do
the
like.
You
know
at
the
end.
B
The
token
generation
and
environment
variable
saving
and
all
that
kind
of
stuff
that
uses
github's
oauth
device
flow.
A
Yeah
so
you'd
be
able
to
like
use
your
spreadsheet
or
whatever
you're
going
to
use
and
then
just
kind
of
that's
dope.
That's
actually
like
super
dope.
I
like
this
because
it's
it's
like
just
also
immediately
useful,
like
for
people
who
would
have
a
really
who'd
be
like
hey.
I
actually
want
this.
I
wouldn't.
B
Much
what
I've
been
up
to
with
it,
I
think
I
talked
about.
I.
A
B
That
seems
that's
been
super
useful.
I
discovered
the
like
p
term,
go
library
with
this,
which
is
just
a
super
cool
package
that
I
hadn't
used
before.
Yes,
that's
pretty
much
it.
I
jeremy
was
really
excited
about
the
login
functionality
too,
so
like
if
there
is
appetite
for
it.
I
can
certainly
work
on
implementing
that
in
the
actual
code
base,
yeah.
A
I
mean
the
thing
is:
is
that
the
one
of
the
problems
with
some
of
the
work
or
some
of
the
older
kept
ctl
work?
We
felt
like
it
was
introducing
some
friction
into
sort
of
like
the
cap
process
for
people
sure
the
cool
part
about
this?
Is
I
actually
think
it
takes
away?
Some
friction.
You
know,
so
it's
like
it's
like
kind
of
judging
it
off
a
little
bit.
A
A
B
I
we
like
it
was.
I
was
kind
of
using
my
own
persona
as
I
was
working
on
it
as,
like
a
team
member
essentially
like
what
what
would
I
find
useful
in
terms
of
like
just
like
interfacing,
with
caps
like?
How
can
I
make
that
easier,
yeah
and
like
yeah?
I
don't
wanna
at
this
point
like
change
any
of
the
like
underlying
process,
yeah.
B
A
A
B
A
A
Yeah
cool,
no,
I
mean,
I
think,
if
you
want
to
like
demo
it
maybe
for
for
jeremy
or
the
other
pet
people
or
kfctl
people
as
well
or
just
kind
of
open
it
up
and
see
what
they
think.
I
I
I
personally
wait.
Why
did
I
personally
think
that
it's
pretty
awesome,
so
it's
just
like
I
can
see
like
immediate
utility
to
it,
which
is
kind
of
it.
Doesn't.
C
C
A
D
A
I
thought
it
would
be
cool
to
like
think
more
about
like
how
do
we
want
to
go
into
2022
like
what
are
some
new
things
that
we
could
kind
of
do
for
2022
to
start
the
year
off,
and
one
of
the
things
that
I
was
thinking
would
be
good
is
to
work
on
the
process
cap
template
because
a
lot
of
people
have
been
asking
for
it
and
also
like
the
whole
kerfuffle
with
the
cadence
cap
and
whether
or
not
that
was
done
correctly
and
how
we
could
sort
of
better
improve
that,
I
think,
would
have
like
immediate
value
to
the
community.
A
But
it's
also
not
something
that
I
think
would
take
a
lot
of
effort,
since
it's
kind
of
like
what
you're
doing
or
it's
like,
hey
like
people
are
already
using
like
the
old
template
format
and
it's
kind
of
a
drag
here.
We
can
offer
them
something
else
to
use
and
also
encourage
people
to
start
thinking
about
sort
of
memorializing
their
process
kept
in
this
other
way.
It's
something
that
we've
talked
about,
but
I
think
that,
like
the
sort
of
immediacy
of
it
is
a
little
bit
higher
now.
A
So
that
was
something
that
I
wanted
to
explore
and
also
get
sort
of
like
a
draft
template
up
and
then
get
some
feedback.
And
then
maybe
it's
a
little
bit
of
meta,
though
right,
because
using
a
process
cap
would
be
a
process,
change
and
then
you're
like
well.
Would
I
use
the
process
cap
for
the
process
for
the
for
the
process
yep
or
would
I
do
it
in
some
other
way
and
I
kind
of
fell
into
a
rabbit
hole
thinking
about
like?
B
D
B
A
Yeah-
and
I
was
I
was
thinking
about
like
a
lot
of
the
the
thing
about
process
changes
is
about
sort
of
it's
not
just
about
what
are
you
changing?
It's
really
about
letting
people
know
and
having
that
sort
of
community
feedback,
and
also
potentially
saying
hey,
we're
not
going
to
do
it
next
time.
A
We're
telling
you
what
what
we're
going
to
do
like
one
of
the
sort
of
canonical
process
caps
for
me
is
the
api
defecation
stuff,
like
the
no
perma
betas,
where
that
was
announced
like
a
year
plus
ago,
and
that's
always
been
steps
and
something
that
I
think
was
done
really
well,
and
you
don't
necessarily
need
that
long,
but
just
sort
of
thinking
about
how
much
time
do
you
need
and
how
should
you
for
especially
like
if
it's
just
affecting
your
stay,
you
know
things
can
do
whatever
they
want
when
they
want
to.
A
A
Because
something
that
affects
everybody
would
need
more
time
than
something
that
just
affects
one
sig,
and
I
just
thought
that
that
would
be
something
that
would
kind
of
you
know
reduce
a
little
bit
of
friction
for
the
new
year
and
it
probably
I
don't
know
that
it
would
be
required,
because
I
don't
think
that
that
goes
in,
like
the
spirit
of
a
process
kept.
But
it's
something
that
could
be
available
to
people
in
the
new
year
and
then
we
could
also
like
refine
it.
A
You
know
for
the
next
for
the
for
the
next
release,
probably
the
spring
summer,
release
after
that
and
have
like
this
working
template,
which
I
think
would
be
pretty
cool.
Another
thing
that
I
wanted
to
do
was
make
sure
that
the
repo
permissions
were
good,
because
I
don't
know
if
you've
noticed
the
standard
or
you'll
probably
notice
this
soon
and
the
enhancements
repo
milestone.
Maintainers
can
edit
things
because
they
need
to
be
able
to
edit
the
descriptions
of
issues.
B
A
That
also
means
that
they
can
manually
merge,
which
is
fine.
I
mean
it's,
not
fine,
but
it's
it's
okay
for
caps
right,
because
the
fig
is
the
last
word
on
the
cast
anyway.
So,
regardless
of
what
you
merge
like,
if
the
sig
looks
at
it,
it's
like.
No,
you
did
something
wrong
like
fix
it,
that
you
have
that
backstop,
but
for
things
like
the
kept
template
and
kept
cto,
I'm
a
little
bit
like.
We
should
make
sure
that
you
can't
like
manually,
merge
into
those
repos
just
because
you
know
only
like
an
enhancement.
C
A
And
we
shouldn't
have
people
accidentally
or
just
being
able
to
come
along
and
manually,
merge
just
because
they're
a
milestone
maintainer.
So
just
thinking
about
the
sort
of
security
of
those
repos,
those
like
sort
of
more
sub
project
repos,
as
opposed
to
like
cap
repos
and
then.
A
And
that's
that
seems
like
a
pretty
easy
to
do,
but
it's
just
been
something
that's
like
you
know
for
once
and
for
all
like.
What
do
we
want
to
do
with
this
and
then
the
other
thing
that
I
was
thinking
about
and
as
a
newer
person
to
the
enhancements
repo?
This
is
also
something
for
feedback
would
be.
A
You
have
your
forum
and
it
has
like
a
brief
instruction,
but
then
you
can
go
to
like
the
bigger
the
bigger
booklet
that
gives
you
all
of
the
details
for
each
of
the
fields
and
kind
of
trying
to
answer
questions
that
way
or
maybe
showing
some
really
great
forms
of
kept
as
well,
because
I
do
think
that
that's
like
a
sense
of
a
point
of
friction
where
the
instructions
aren't
necessarily
clear.
I'm
not
talking
about
like
the
fields
of
the
cat,
but
just
the
instructions
like
what
we
ask
for
is
it.
A
Super
clear
and
also
the
format,
makes
it
a
little
hard
to
read
like
in
the
template,
because
you're
trying
to
keep
it
brief,
because
it's
the
template,
but
there
might
be
a
little
bit
more
information
that
you
could
give.
So
that
was
just
like
three
of
the
things
I
was
thinking
about.
A
That
seemed
like
really
like
bite-sized
enough
to
be
able
to
tackle
before
2022
and
also
nice
sort
of
ergonomic
improvements
to
to
start
2022
us,
because
it's
still
a
weird
a
weird
year
and
not
like
fighting
off
before
then
you
can,
as
you
know
so,.
B
Yeah,
I
think,
having
examples
directory
specifically
would
be
fantastic.
You
know
that's
if
I'm
looking
at
like
it's
different
but
like
if
I'm
looking
at
implement
or
using
a
library
that
I'm
unfamiliar
with
like
the
first
place,
I
usually
stop
is
the
examples
directory
yeah.
So,
in
addition
to
like
having
the
template,
if
we
just
had
a
top
level
folder
in
the
enhancements
repo,
that
was
examples.
C
B
Picked
like
four
cups
that
we
think
were
really
well
done
using
the
most
current
format.
That
might
be
especially
helpful.
A
Yeah
like
something
like
that
and
like
it
could
be
potentially
like
annotated
or
something,
but
it's
also
like,
as
the
kept
template
gets
bigger.
It's
almost
harder
to
like
it's
almost
harder
to
see
what's
in
the
template,
but
then
it's
also
harder
to
like
really
get
an
idea
of
what
you're
supposed
to
put
in,
because
it's
just
like
this,
especially
with
the
instructions
it
becomes
really
long,
and
I
think
some
of
the
instructions
also
haven't
really
been
like
audited
in
a
while.
A
You
know
so
it's
like,
I
know
what
they
mean
like
you
might
know
what
they
mean.
If
you
look
at
a
lot
of,
if
you
look
at
a
lot
of
cats,
but.
A
That
it's
really
like
explicit
like,
and
I
think
that
maybe
auditing
those
instructions
also
could
be
like
really
helpful,
because
I
know
like
for
the.
I
think
it's
for
tests.
I
want
to
say,
for
the
graduation
criteria
like
we
pretty
much
want
graduation
criteria
for
alpha
beta
and
ga.
That's
what
we
want,
but
the
thing
is
kind
of
written
with,
like
the
arrows.
A
So
it
looks
like
you
only
need
graduation
criteria
if
you're
going
from
like
alpha
to
beta,
where
you're
going
from
like
made
it
to
d.a,
and
that's
like
a
little
piece
of
friction
that
I
think
that
people
don't
really
like
everybody
knows
it,
but
nobody
ever
fixes
it,
and
I
think
that
that
would
be
like
really
helpful
for
people,
but
also
just
clarify
like
what's
expected
so
yeah
that
those
were
those
are
like
the
three
things
that
I
was
just
thinking
about
like
going
into
2022
as
like
things
that
could
have
a
good
like
impact
on
like
just
the
ergonomics
of
doing
a
calf
and
make
it
just
a
little
bit
easier
to
do
a
cap.
A
B
Yeah,
I
think
that
sounds
good.
I'm
I'm
happy
to
collaborate
if
you
want
to
get
a
draft
going
in
the
yeah
channel
on
slack.
C
B
On
the
process
kept
specifically
yeah,
yeah
cool.
A
And
I
I
was
just
thinking
of
it
like
because
I
think
sometimes
it's
like
we
think
about
all
this
is
like
worth
being
release
based,
but
then
you
get
kind
of
caught
up
in
the
release,
and
that
was
why,
at
least
when
I
was
thinking
about
it,
reframing
it
as
like.
Hey
like
what
are
some
things
that
we
could
bring
into
2022.
A
That
would
be
like
kind
of
wind
and
also
easy
to
sort
of
articulate
to
people,
because
you
also
don't
want
too
much
churn
in
the
cap
and
the
enhancements,
like
you,
know,
folder
and
then
the
template
and
things.
So
I'm
also
trying
to
think
about
like
grouping
changes
together
so
that
we
can
kind
of
easily
articulate
it
to
the
community
as
opposed
to
like
little
changes
all
the
time
that
can
kind
of
like
people,
don't
necessarily
notice
or
or
hear
about
so.
B
Yeah
that
was
like
a
a
friction
point
with
the
last
release,
where
we
would
try
to
tell
people
like.
Oh
your,
your
cap
doesn't
follow
the
latest
template
and
you
know
we
would
get
the
response
back
like
well.
A
Yeah
that
that
then
the
last
meeting
I
actually
brought
up
like
a
staging
directory
or
like
the
idea
of
versioning
the
templates
and
then
just
having
like
a
versioning
policy.
Yeah.
C
A
Of
the
things
that
I
don't
like
is
that
I
don't,
I
think,
that
it's
going
to
be
stable
and
actually
like,
since
I'm
not
doing
the
release
team,
I'm
definitely
paying
more
attention
to
the
template.
Changes
there
haven't
been
any,
but
I'm
paying
more
attention
to
it,
because
I
don't
think
that
I
don't
think
that
that
template
should
change
a
lot,
and
I.
A
The
size,
it's
not
the
size
of
the
change,
you
know,
and
I
don't
think
that
we
have
a
great
way
to
articulate
that.
So
that
was
something
I
brought
up
in
the
last
meeting
as
well,
like
whether
you
know
we're
formally
versioning
it
or
just
informally,
saying
like
no
like
we're
just
holding
changes
for
x
period
of
time
and
merging
them.
You
know
together,
like
just
like
low
lo-fi
style.
A
C
A
Yeah
I
mean
that
was
what
I
was
thinking
when
I
was
talking
about
it.
I
think,
like
a
month
or
so
ago,
was
like
what
we
don't
have,
because
I
mean
this
is
this
is
me
like,
and
I
kind
of
go
back
to
tax
forms
a
little
bit
because,
like
you
have
like
it's
a
wrong
form,
it's
boring
and
it's
really
hard
to
figure
out
what
is
where
especially.
A
C
A
Yeah
I
mean
it's
like
you're:
gonna
have
to
rely
probably
on
the
ci
like
for
the
minutia,
but
I
do
think
it
would
be
nice
when
I
say
to
somebody:
hey
xander,
like
you're,
using
a
cap
from
2020,
can
you
update
to
a
modern
one
for
for
xander
to
be
able
to
go
and
be
like?
Well,
what
are
the
like?
Why?
Why
do.
C
A
What
are
the
major
changes
here
like?
What
are
the
major
changes
that
I
need
to
think
about,
because
sometimes
you
have
to
actually
think
about
some
of
the
changes?
It's
not
just
like
trivial,
and
I
also
think
that
if
we
minimize
the
merges
into
the
cap,
then
it's
also
kind
of
easier
to
tell
people
hey.
The
cap
has
changed
like.
A
Can
you
come
take
a
look
at
the
new
template,
so
I
think
just
like
tightening
that
that
whole
process
up
is
going
to
be,
I
think,
beneficial
to
people,
because
I
I
worked
on
the
release
team
and
I
always
felt
that
tension
too
of,
like
like
it
was
obvious
when
someone
used
a
really
old
template
right,
like
new
templates,
mad
old,
like
okay,
fine,
like
update
it
and
that's
like
so
obvious,
but
then
there's
the
line
of
like
wait
like
there
are
some
small
changes,
but
is
that
enough
to
ask
somebody
to
update
absolutely
or.
C
C
The
oldest
remaining
issue
in
kubernetes
I
picked
up
so
it
was.
It
started
out
as
an
issue
literally
in
kkk
and
the
tracking
was
all
over
the
place,
and
I
thought
that
was
good
enough
and
then
they
said
no.
You
have
to
open
up
an
issue
and
you
know
and
the
enhancements
thing.
So
I
did
that
and
then
you
know
no,
you
need
to
count.
I
see
that
makes
sense
and
then
two
years
go
by
right,
yeah,
oh,
you
have
to
redo
it
all
again.
C
Wait
a
minute
just
like
it
sort
of
feels
like.
A
The
other
thing
that
we
could
improve
and
this
kind
of
comes
back
to
you,
one
of
the
things
I
thought
would
be
nice
to
work
on,
and
I
don't
know
if
I
said
it
earlier
is
that
like
making
the
readme
just
a
little
bit
more
helpful
so
like
if
the
template
has
changed
profoundly
right,
because
there
was
a
big
change.
I
would
say
like
a
year
ago
that
could
have
been
like
in
a
red
banner
in
the
read
me
like:
hey
guess
what
everyone.
A
But
that
would
be
like
when
you
go
to
the
directory.
That
would
be
like
a
huge
visual
cue
for
you,
even
if
you're
not
touching
that
kept
this.
This
release
in
your
mind,
now
you're
like
hey,
okay,
like
something
changed,
and
that
that
would
be
great
for
an
email
as
well,
but
emails
get
lost
and
I
think,
having
that
sort
of
like
sticky
reminder
or
sticky
piece
of
information
hey
now
now
there
are
pr
reviews
that
you
need,
or.
C
C
That
would
be
nice,
you
didn't
get
the
notices
because
right
right
now,
what
you
get
is,
you
know
it
goes.
It
goes
idle
and
nothing
happens,
and
then
somebody
somebody
you
finally
get
agreement
for
this
to
be
looked
at
and
then
a
couple
of
weeks
later
you
get
a
notice
that
says:
oh
you've
got
to
redo
your
format.
Yeah.
A
A
Like
what's
new
or
like
even
like,
what's
new
or
like,
like
hey,
alert,
now
he's
now
performing.
A
A
D
C
C
C
B
B
A
A
To
my
ideas
too,
like
I,
I
came
up
with
some
of
them
recently
and
it's
just
good
to
have
like
some
immediate
sort
of
like
feedback
of
like
oh
wow,
like
that,
I
think
you're
on
the
right
track.
Just
because
there
are
things
that's
been
bothering
me,
but
I've
never
really
had
the
time
because
of
like
doing
other
like
release
stuff
to
like
just
go
and
like
actually
do
it.
So
because
they're
not.
A
A
B
Yeah
I
can
yeah,
I
can
show
you
real,
quick,
actually
just.
C
B
Essentially,
what
it
is
is
added
a
login
command
to
kept
ctl
to
get
around
the
having
to
set
like
an
environment
variable
and
like
generate
a
github
token,
and
all
that.
So
you
just
do
kept
ctl
login
and
it
spits
out
a
device
code
and
opens
up
a
github
window.
And
you
enter
the
device
code.
And
then
you
are
off
in
kept
ctl
as
your
github
identity
and
have
all
of
the
same
permissions
to
interface
with
the
enhancements
repo
that
you
would
on
github
from
the
cli
level,
which
allows
us
to
like.