►
From YouTube: OCI Weekly Discussion - 2022-01-27
Description
agenda/notes: https://hackmd.io/El8Dd2xrTlCaCG59ns5cwg?view#January-27-2022
A
B
D
D
I
haven't,
I
haven't,
had
a
slackware
install
in
some
years,
but
no
I've
I've
been
on
debian
for
quite
a
while
now,
so
this
this
machine
is
the
I'm
actually
on
my
personal
machine
right
now
and
it's
debbie
and
sid.
I
like
rolling
releases.
C
D
Okay
forecast
and
it's
pretty
light
agenda
today,.
E
D
C
A
D
D
Particular
you
want
to
say
about
this
right
now,
because
mostly
it
just
needs
updating
for
like
the
last
discussions,
and
it
looks
like
some-
I
I've
had
a
window
of
time
this
morning,
which
is
very
procrastinating
or
otherwise,
but
so
I
did
just
push
before
this
meeting
some
updates,
which
I
don't
expect
anybody
to
have
read
through,
but
it's
it's
really
just
trying
to
like
start
tidying
it
up
based
on
the
last
discussions,
there's
still
lots
of
like
to
do's
and
things
that
if
people
go
through
this
and
have
like
you
know,
you
only
want
to
use
the
github
suggestions
feature.
D
That's
that's
fine
and
good.
I
would
welcome
that.
B
B
E
D
One
thing
that
and
not
in
in
the
changes
that
I'm
going
through
and
you
know
like
where
you
had
the
extension
name
and
component
module
or
whatever
I'm
not
keen
on
using
the
word
namespace
unless
it's
like
used
just
as
a
describing
word,
but
not
as
a
define,
you
know,
defining
placeholder
name
so
like
in
some
places.
I've
allowed
it
to
be
like
the
extensions
namespace
name.
You
know
like
referring
to
like
how
it's
described,
but
not
to
abuse
or
overload
the
word
namespace
anymore.
D
B
B
B
Yeah,
I'm
fine
with
that.
If
you
go
down
to
the
yeah,
so
this
this
is
the
one
I
just
wanted
to
be
sure
on
so
based
on
all
of
the
feedback
and
and
everything.
This
is
the
proposed
thing
we're
arriving
on.
So
this
has
the
module
change.
We
talked
about
a
few
weeks
ago
and
then
extension
as
opposed
to
namespace,
based
on
vincent's
feedback.
D
D
D
E
D
D
Okay,
with.
D
For
the
sake
of
everybody's
excitement
and
entertainment,
was
there
other
particular
things
in
this
sage
that
you
wanted
to
go
point
on
or
just
to
to
rightfully.
F
Push
it
push
it
forward.
I
I
think
we've
steve
she's
comment
is
probably
steven's
comment
is
probably
the
captures
everything
and
your
edits
to
me
looks
good.
I
don't
have
any
concern.
Namespace
or
extension
sounds
okay,
because
the
end
like
flick.
F
And
mike
we
had
agreed
that
these
things
would
probably
change
over
time.
So
this
is
like
an
iterative
approach
right.
We
want
to
see
how
it
is
or
and
evaluate
before
we
take
it
to
maybe
spec
version
2
and
so
we'll
have
enough
fake
time.
B
B
The
character
set
of
namespace
component
and
or
sorry
extension
component
and
module
need
to
be
restricted
to
the
same
character,
set
that
we
use
for
regular
paths.
E
B
Well,
there's
a
there's
stylistic
and
security
concerns,
so
the
first,
so
the
security
concern
is
like.
Let's
say
I
have
an
extension,
that's
uppercase
steven
and
then
lowercase
steven,
but
they're
different
yeah.
Basically,
this
is
the
this
this
right
here,
this
component
name,
although
this
has
slashes
in
it.
So
there's
just
one
part
of
that.
It's
like
this
first
part
of
the
red
deck
where
it
lets
basically
lowercase
kabob.
B
B
D
B
Not
starting
with
yeah
there's
because
but.
B
D
E
E
A
D
D
But
then
it's
got
this
comment
here,
which
came
in
from
cemetasia's
edits
of
of
doing
the
versions
in
the
media
type.
F
I
I
think
we
have
an
option
of
maybe
taking
that
out
if
needed.
So
a
couple
of
options
that
came
up
during
the
discussion
was
we
leave
the
versioning
to
the
extension
right.
It
could
be
through
an
argument
or
it
could
be
through
media
type,
so
the
extension
is
free
to
do
whatever
versioning
it
wants,
specifically
for
auras.
What
I
recommended
was
if,
if
and
when
we
do
come
across
through
versioning,
we
can
make
it
a
parameter,
but
right
now
there
is
no
requirement
for
versioning
and
the
other
thing
was
response.
F
Types
have
version
in
their
on
the
header.
The
same
way
for
like
distribution
does
so
it
keeps
it
consistent.
We
don't
have
to
invent
a
new
versioning.
Those
were
some
of
the
options
we
were
thinking.
So
if
we
don't
want
to
do
the
voicing
recommendation,
we
can
take
it
out.
D
I
did
want
to
you
know
at
least
mention
something
about
versioning,
but
it
probably
is
in
the
way
of,
if
there's
a
drastic
enough
change,
that
your
your
endpoint
is
fundamentally
different.
F
D
It's
just
that
you're
returning
different
different
json,
you
know
expecting
different
json
types
or
otherwise.
Then
you
should
use
that
through
except
accept
or
content
type
headers
right.
F
So
that's
why
we
went
with
a
header
rather
than
using
it
in
the
parameter
and
all
that
and
the
response
type.
The
client
can
pass
the
header
and
decide
what
it
wants
to
do
with
that.
But
if
it's
totally
breaking
then
I
don't
think
we
should
call
it
the
same
operation
name.
It
should
be
a
different
operation
and
we
have
options
at
that
point
in
time.
Sure.
D
Okay,
okay,
so
now
I
just
I
was
about
to
rework
that
one
thing
and
I
was
curious
if
you
were
already
using
it
or
something.
So
that's
that's
good
I'll
redo.
The
versioning.
D
It
was
my
plan
to
actually
finish
this
before
this
meeting,
but
that
that
ship
has
sailed.
I've
got.
D
D
B
D
D
B
Yeah,
are
you
okay
yeah,
I
mean
either
way
I
went
with.
I
still
did
make
the
government
workshop
the
so
I
I
prefer
not
abbreviations,
because
it
makes
it
hard
to
look
up
a
word.
If
you
don't
know
the
word
yep.
That's
the
reasoning
behind
that.
D
F
Yeah,
that
was
just
a
conversation
or,
if
that's
actually
legit,
no,
that's
that
has
to
change
I'll,
just
paste
in
I'll.
Just
give
you
give
you
how
how
the
current
specification
is.
D
A
B
D
G
D
B
B
What's
in
repository.go,
real
quick
is
that
just
regular
expressions
right
below
it,
just
the
sibling
to
ext.
D
E
B
D
That's
and
that's
what
I
kind
of
wanted
to
avoid.
You
know
having
some
dot
that
could
be
pointed
to,
even
if
this,
even
if,
like
the
underscore
aws,
is
just
saying
these
docs
are
defined
over
there,
so
you
could
figure
out.
You
know
canonically.
Yes,
we
reserve
that
you
know
underscore
aws
and
that
project
is
owning
the
definition
of
it
or
something
like
that.
G
C
Hey
vincent
just
backseat
driving
here
line,
33
close
another
quote
after
extensions
before
the
period
on
on
line
33.
C
C
C
C
This
is:
we've
got
a
back
seat.
Drivers
we're
all
here
watching
yeah,
I'm
learning
australian,
too
phil.
C
I
don't
know
exactly
what
that
means.
That's
when
you
popped
your
flip-flop
man,
I
know,
but
you
gotta
have
a
double
double
double
plugger,
so
you
can
blow
one
plug
and
have
some
redundancy.
E
D
Yeah,
I
think
this
was
something
that
came
out
of
a
prior
brainstorm
of
like
different
extensions
names.
Components,
but
even
like.
D
D
D
B
B
D
Do
we
need
to
detail
out
the
whole
path,
because
at
that
point
all
right?
You
know
if
you
just
see
that
it
yeah.
I
guess
in
some
extent
you
you
might
just
because
somebody
has
an
underscore
oci
endpoint
might
not
mean,
or
you
unders
or
whatever,
whatever
it
is,
do
they
have
to
implement
the
entirety
of
that
namespace.
D
C
Just
vincent
sir,
tell
me
when
you're
interruptable.
B
And
then
some
more
conjugation
in
there.
D
D
H
Yeah,
that's
what
I
was
just
saying:
I'll
I'll
go
ahead
and
I'll
leave.
H
I
I'm
I'm
a
okay
with
that.
I'm
willing
to
start
a
subsequent
pr
to
do
some
grammar
cleanup
for
it.
D
Is
that
is
that
any
different,
better
lucky?
Obviously
the
other
one
was.
G
D
F
Do
you
do
so
for
versioning,
that's
the
one
you
were
asking
about
right,
yes,
sir,
how
do
you
want
to
go
about
it
because
I
think
each
extension
will
have
its
own
probably
opinion
on
how
to
do
versioning?
Do
we
leave
it
to
the
extension,
or
do
you
want
to
give
some
guidance
here.
D
It's
probably
worth
I
I
feel
like
it's
worth.
I
don't
know
historically,
there's
lots
that
we
don't
comment
on
that
kind
of
like
leave
it
as
an
exercise
for
for
people,
even
if
there's
already
a
pattern
of
how
folks
do
it.
D
D
Maybe
I'll
just
type
it
up,
I
I'd
I'd,
prefer
to
at
least
have
something
giving
a
little
bit
of
guidance,
obviously
not
dictating
how
anybody
would
would
go
about
doing
it.
Just
it
was
like
pointing
them
in
the
right
direction
so
that
anything,
any
of
these
things
start
looking
and
smelling
similar
enough.
A
A
A
D
D
B
B
B
B
All
right
so
now
we
just
need
to
work
in
nft
and
word
hole
and
I
think
we'll
be
good.