►
From YouTube: OCI Weekly Discussion - 2022-02-03
C
B
F
G
Starting
out
early
here,
yeah,
I
mean
sign
up
on
the
list.
G
I
I
I
I
think
it's
pretty
packed
now,
but
yeah
put
your
name
in
and
sign
up.
I
think
they're
looking
for
people
who
live
there,
but
you
know,
if
you
want
a
link
I
can.
I
can
go,
find
the
link.
G
D
E
D
They
probably
are
just
insufficient
policies,
so
I
have
no.
I
have
no
complaints
with
documenting
things
and
I
think
either
the
charter
or
the
tob
repo
itself
would
be
fine
places
to
iron
out
stuff.
Like
that,
I
know
that
at
some
point
rose
had,
you
know
wanted
to
see
particular
information
around.
How
do
people
become
maintainers,
and
this
kind
of
thing.
D
D
So
if
it's
something
like
that,
then
I'm
all
for
it.
I
just
you
and
I
hadn't-
I
hadn't
done
it
myself
so
like
if
there's
anything
particular
that's,
that's
missing,
yeah,
absolutely
open
issues
and
take
a
first
stab
at
it.
H
Another
ubi
repo
sounds
fine.
I
don't
think
we
have
a
particular
place
in
it,
yet
I
would
say
that
probably
my
opinion
is
that
unless
it's
actually
a
change
to
the
rules
in
the
charter,
policies
can
be
separate,
and
the
reason
for
that
is
that
the
charter
has
specific
requirements
for
amending
it,
and
if
we
don't
really
need
to
amend
the
charter,
we
can
avoid
having
to
go
through
that
whole
voting
process
for
everything.
D
Yeah,
my
only
addition
to
that
is
yeah
it
definitely
as
we
found
out
last
year,
it's
not
fun
or
easy
to
like
do
stuff
with
the
charter.
My
my
only
thought
there
is
of
if
someone
did
have
the
same
passion
and
initial
you
know
drive
that
alexa
did
you
know
he
he
kind
of
reorganized
a
ton
of
the
charter.
I
I
think
those
pr's
are
still
there.
D
D
I
can't
even
think
of
the
term
the
the
collection
of
maintainers
of
the
specs
tdc
yeah
tdc,
so
like
there's
a
bunch
of
like
outdated
ideas
and
language
that
it
also
would
be
nice-
and
I
guess
maybe
it's
separate
from
what
you're
talking
about
nisha,
but
I
feel
bad
that,
like
kind
of
alexa's
stuff,
has
kind
of
fallen
by
the
wayside
and
again
it's
not
like
there's
any
one
person
at
fault
it's,
but
I
feel
like
that.
D
Some
of
the
things
he
was
trying
to
clarify
would
help
understand
where
the
t.o.b
even
should,
or
has
kind
of
commitments
to
the
projects
versus
the
projects
defining
and
organizing
their
own,
like
the
specs,
at
least
under
the
current
charter.
It
seems
like
the
this
idea
of
a
tdc
is
where
most
like
technical
authority
resided.
Unless
there
were
just
total
blocked.
You
know
discussions
or
issues,
and
that's
really
the
tob.
I
I
guess
what
I'm
coming
to
is
the
tob
and
the
current
charter
has
a
fairly
small
role
in
the
oci
and
so
yeah.
D
E
Okay
in,
let
me
just
take
a
look
real,
quick
at
any,
like
pull
requests
that
are
open
to
this.
So
there
are
three
pull
requests
and
then
two
of
them
are
submitted
by
alexa.
E
E
I
know
if
I,
if
I
wanted,
to
merge
this,
what
is
the
procedure
for
it.
H
D
E
To
me
that
we
also
need
some
kind
of
operations.
Documentation
is
that
also
policy,
or
is
that
just
like
how
how
the
dob
operates.
D
Yeah,
I
would
agree
with
with
vbats
that
like
if
we're
just
talking
about
things,
to
help
guide,
how
we
operate
like
that's
outside
the
charter,
and
I
think
we
can.
I
mean
there's
nothing
in
this
repo
and
maybe
that's
step
one
as
to
how
things
are
things
outside
the
charter
are
approved
and
merged
in
this
particular
repo.
D
E
That
sounds
that
sounds
like
a
plan
start
of
next
steps
and
is
to
submit
like
a
skeleton
of
what
the
operations
would
look
like
and
then
start
filling
in
every
time.
We
come
across
a
question
that
says:
how
do
we
operate
on
when,
when
something
hap,
when
something
when
an
issue
comes
up,
how
do
we
resolve
an
issue
or
like
how
do
we
manage
a
particular
task?
So,
for
example,
once
a
charter
amendment
has
been
voted
on,
how
do
we?
E
H
I
think
it's
worth
writing
that
down
in
practice.
It's
been
chris
and
amy
who've
been
facilitating
that
so
it
just
sort
of
informally
when
there
is
something
that
needs
to
change
in
the
charter.
Chris
and
amy
have
been
helping
with
it,
but
that's
certainly
something
that
we
can
write
down.
D
Anisha,
just
just
in
case
you
haven't
seen
this
like
this
is
the
last
time.
Well,
maybe
the
only
time
in
the
last
several
years
that
we've
changed
the
charter
a
bit,
and
so
this
submitter
is
a
lawyer
with
the
linux
foundation,
and
so
he
took
like
what
elec
what
we
had
started
and
and
made
his
own
pr.
E
Yeah,
I
I
I
recognize
this
speaking
of
documentation.
What
do
you
all
think
about
note-taking
and
you
know
calling
calling
for
note
takers
whenever
we
have
these
meetings.
E
Can
we
have
a
consensus
concession
about
that,
saying
that
we
we
get
a
note
taker
every
time
we
ask
for
a
note
taker
or
have
call
out
for
a
note
taker
every
time
we
have
these
meetings.
E
Oh,
these
are
both,
I
think,.
H
E
F
F
They
also
try
to
assign
someone
to
triage
issues
which
people
seem
to
duck
out
of.
Everyone
should
kind
of
just
be
doing
that,
but
it's
helpful
to
have
some
like
responsibilities
here.
E
Okay,
so
just
I'm,
I'm
also
notetaking
right
now.
That's
why
I'm
asking
that's.
Why
I'm
rather
that's
why
I'm
being
quiet
in
the
middle
but
yeah
brandon,
that
sounds
like
a
plan
is
add
a
note
taker
feel
field
and
have
a
have
a
triage
triage
call
whenever
it's
needed.
D
B
Yeah
it's
it's
kind
of
like
last
week
we
agreed
on
getting
the
pr
111,
merged
and
kind
of
making
additions
like
type
of
mistakes,
or
anything
like
that.
On
top
of
that,
is
there
anything
pending
the
blocking
of
the
merge
at
this
point
or.
D
Sorry,
I'm
here
I
have
no
idea.
I
addressed
a
lot
of
people's
concerns
when
brandon,
I
think
you
had,
or
somebody
asked
about
clarification
on
what
the
list
of
endpoints
would
look
like.
You
probably
just
need
some
examples,
but
I
think
it's
otherwise
that's
getting
into
nitpick
territory.
So.
D
D
Oh
yeah,
I'm
not
personally
elated
about
having
a
an
array
of
endpoints,
but
I
don't
know
if
I
said
it
in
the
dock
or
in
the
commit.
I
think
I
said
in
the
dock,
but
if,
since
any
extension,
could
have
optional
and
you
know,
could
not
implement
an
optional
endpoint,
then
there's
no
other
way.
Even
if
you
see
that
it
has
the
oci
endpoint
or
the
oci
extension
or
whatever
it
is
that
you
wouldn't
know
it
has
certain
endpoints
implemented
until
you
try
it
and
get
a
404
or
503
or
whatever.
D
A
D
D
Is
it
really
needed
to
have
a
a
framework
for
adding
you
know
new
things
to
the
api
which
is
effectively
heading
any
other
pr
for
something
that
changes
the
changes
or
updates
or
ads
to
the
api
and
at
all,
it
doesn't
have
to
happen
in
an
extensions
framework,
but
the
it's
basically
giving
a
name
space
so
that
if
you
come
to
a
registry-
and
you
see
you
know
an
aws
and
oraz
or
whatever
you
know,
gcp
and
endpoint
extension
that
you
could
at
least
see
like.
D
A
D
Like
for
at
least
until
something
gets
added
else
in
oci,
then
you'd
actually
see
like
oci
slash
extension
discover
like
that
string
there,
so
the
whole
string
okay
effectively
what
the
extension
endpoint
would
be.
So,
whatever
the
prefix
is
up
to
that
point
effectively
v2
then.
F
D
A
E
F
Yeah,
I
can
take
a
look
too.
I
I
I
just
don't.
I
don't
have
a
use
case
for
this
and
if
I
don't
see
any
issues
with
it,
I
just
I'll
take
a
look
before.
D
D
Yeah,
no,
please
please
do
that.
I'm
been
trying
to
dial
in
you
know
just
yeah,
that's
all
on
the
wall,
so
go
ahead.
Yeah.
A
I
think
all
the
credit
on
this
one
goes
in.
I
think
this
nicholas
document
originally
and
we
commandeered
it
and
took
it
over
and
started
throwing
all
kinds
of
stuff
into
it.
So
they
went
through
the
description.
What
everything
is,
and
so
last
this
past
meeting,
we
were
starting
to
go
through
a
bunch
of
the
user
stories
of
all
the
various
requirements
and
starting
to
chug
through
those.
A
E
I
I
think
it
would
be
useful
to
show
josh's
categorizing.
E
F
F
Particularly,
there
are
a
few
things
that
steve
had.
I
had
at
the
bottom
that
were
more
about
the
customer
like
assurances
for
the
customer
and
then
nisha
had
a
bunch
of
stuff
about
copying
or
grafting
things
from
one
registry
to
another,
which
I
I
guess.
I
don't
maybe
sure
if
you
want
to
talk
about
how
that
is
in
relation
to
references,
but
I
do
think
it's
like
either
storing
or
querying
and.
E
So
the
the
idea
is
to
link
a
bunch
of
objects
together,
so
in
the
event
of
copying
from
one
registry
to
another,
the
objects
do
not
get
lost.
E
The
links
between
these
objects
need
to
be
broken
or
rearranged.
Then
that
should
be
allowed.
Now.
I
feel
like
the
second
one
is
not
really
something
that
a
registry
should
do,
because
it
is
like
a
directed
acyclical
graph
thing,
but
to
get
around
the
rearranging
one.
Can
one
can
copy
those
objects
over
to
another
registry
or
another
repo
like
basically
copy
the
objects
and
redo
the
links,
so
you
create
a
new
permutation
of
the
linkage.
Among
those
objects,
does
that
make
sense,
josh
or
anyone
else.
F
It
sort
of
makes
sense-
I
I
guess
my
goal
right
now
is
just
to
make
sure
we
can
list
these
requirements,
and
so
that's
what
the
groupings
were
for
and
I'm
just
trying
to
figure
out.
If
there's
a
way,
we
can
group
these
better
who
who's
sharing
brandon.
Can
you
scroll
up
to
the
three
yeah
so
there's
this
last
one?
I
want
the
ability
to
automate,
maybe
nisha
this
can
switch
to.
F
F
F
Yeah
one
thing
that
occurred
to
me
too
is
that
we're
kind
of
these
all
sort
of
the
categories
when
we
did
the
conformance
stuff,
we
broke
down
into
categories
and
maybe
those
four
it
was
push-pull
discovery
and
management.
I
think
I
think
perhaps
everything
could
fall
into
those,
because,
if
they're
going
to
end
up
in
distribution
spec,
if
changes
will
end
up
in
distribution
spec
either
way,
they
will
fall
into
those
categories.
F
So
maybe
that
maybe
that's
a
good
idea,
but
I
don't
know
if
this
is
getting
off
topic
from
a
status
update
or
it's
just
a
continuation
of
the
working
group
so
I'll,
let
brandon
nicole.
E
A
That
haven't
been
thinking
of
how
they
would
want
to
use
reference
types
until
now
to
chime
in
if
they
have
some
ideas
that
are
maybe
non-traditional
might
help
us
think
about
how
how
people
would
use
these
that
weren't.
Originally
thinking
of
a
signature
and
s
balm,
like
we've,
been
using
in
every
one
of
our
other
examples.