►
From YouTube: OCI Weekly Discussion - 2022-02-10
A
B
B
I
have
a
actually
a
tob
question.
I
how
how
does
the
t.o.b
vote
on
chair
chairs
that
are
running
right
now?
I
just
saw
the
email
yeah.
D
A
B
Okay,
so
I
just
have
a
couple
of
like
governance
questions.
The
first
one
is:
how
do
how
do
folks
in
the
community
and
in
the
technical
developer
community
reach
out
to
the
technical
oversight
board?
Is
it
through?
Well,
let
me
put
it
this
way.
There
seems
to
be
from
my
perspective,
three
modes
of
communication.
B
One
is
email,
second,
is
github
issues
and
third
is
in
this
meeting:
is
there
a
priority
or
a
preference
that
folks
reach
out?
I
mean
I,
I
guess
you
know
there
is
the
there
is
the
either
or
thing
folks
can
reach
out
in
all
three
forums,
but
I
I
feel
like
there
needs
to
be
some
central
point
where.
B
Discussions
about
the
set
topic
are
consolidated,
so
there's
one
place
for
everyone
to
go.
Look
at.
Would
that
be
the
meeting
on
how.
D
F
Well,
you're,
more
of
an
authority
so,
but
I
actually
talked
to
sam
about
this
a
while
back
when
there
was
issues-
and
I
think
the
answer
was
for
things
that
are
like
requiring
action.
It
must
go
through
the
mailing
list,
but
go
ahead.
D
Yeah,
so
I
guess
I
saw
your
issue
the
other
day
and
was
trying
to
think
of
a
response,
and
I
guess
I
got
stuck
thinking
about
like,
and
maybe
it's
to
josh's
point
like
reaching
out
to
the
tob
is
kind
of
a
generic
statement.
D
So
if
someone
just
has
a
one-off
question-
and
there
happen
to
be
tob
members
in
this
meeting
and
it's
not
a
formal
request
or
you
know
needing
action,
then
I
guess
whatever
makes
most
sense
at
the
time,
but
things
that
you
know
anything
that
is
going
to
generate
a
discussion
and
obviously
I
think
github
issues
makes
the
most
sense.
Because
then
there's
a
log
of
public
discussion
on
the
topic.
That's
you
know
freely
kind
of
available
to
anybody
who
wants
to
see
what
happened
during
the
discussion.
D
So
you
know
when
we've
called
meetings
of
the
tob,
we
use
the
mailing
list
to
announce
them
so
that
everyone,
you
know
it's
a
public
record
of
our
intent
to
meet
so
yeah
yeah.
I
don't
want
to
ramble
any
more
than
that.
I
guess
maybe
maybe
if
we
restate
what
the
reach
out
is,
it
might
have
different
answers
based
on
what
someone's
asking
of
the
tob.
C
Sam
yeah,
I
would
say
that
the
the
language
in
the
charter
basically
explicitly
enshrines
the
mailing
list
as
the
preferred
method
for
the
tob
to
operate.
I
would
generally
say
that
any
written
form
of
communication
is
something
that
I
personally
find
completely
reasonable
and
acceptable.
I
don't
really
think
meetings
like
this
are.
C
Are
the
best
place
to
raise
issues,
because
there
isn't
there
isn't
a
guarantee
that
everyone
from
the
tob
is
going
to
be
here
and
that
we're
all
going
to
be
able
to
act
as
a
unified
body,
so
a
written
form
of
communication,
something
that's
on
the
mailing
list.
Something
that's
in
a
github
issue
sounds
like
it's.
It's
better
for
us
being
able
to
actually
actually
accomplish
something.
B
If
so,
as
far
as
initiating
a
discussion
on
a
particular
topic,
would
a
github
issue
or
a
mailing
list
be
the
place
to
do
that.
C
I
think,
if
you're
looking
for
an
answer,
the
answer-
that's
in
the
charter,
is
the
mailing
list,
but
if
you're
looking
for
preferences
from
people,
I
think
that
I
mean
I
just
told
you
what
mine
is.
I
think
that
it's
a
pretty
reasonable
answer,
anything
that's
a
written
form
of
communication,
either
mailing
list
or
the
github
issues.
B
Well,
the
chatter
doesn't
say
you
know
preferably
mailing
lists.
It
says
any
discussions
and
mailing
lists,
so
it's
it's
kind
of
vague
in
that
regard,
just
because
it
says
mailing
list,
like
the
word
mailing
list
is
in
that
sentence.
B
I
think
the
spirit
of
it
is
operating
transparently,
which
we
have
you
know
three
different
forums
to
operate
transparently.
This
meeting
is
a
as
an
open
meeting.
Anyone
can
join
the
github
issues
are
public,
anyone
can
post.
The
mailing
list
is
public.
B
D
I
my
guess,
you
know
I
mean
kind
of
like
what
sam
said
it.
If
we're
going
to
be
writing,
you
know
if
it's
something
that
needs
kind
of
permanency
of
of
record
like
then
having
it
written
down
in
either
form
is
fine.
D
I
think
if
someone
said
something
to
the
mailing
list-
and
it
looks
like
something
that
could
generate
a
lot
of
commentary
over
time
and
maybe
end
up
with
like
lgtms
like
affirming
something
that
then
we
can
simply
ask
someone
in
a
response
to
that
mailing
list
post
to
please
open
an
issue
with
their
request
and
kind
of
redirect
as
necessary.
I
guess
is
what
I'm.
B
Saying,
okay,
so
in
summary,
it's
like
the
community
members
can
reach
out
in
any
kind
of
format,
but
the
tob
is
the
t,
o
b
is
required
to
direct
them
to
a
format
that
to
a
forum
that
would
be
most
appropriate
for
the
for
the
subject
matter.
Does
that
sound
good.
C
I
just
want
to
point
out
here
right
now:
we've
only
got
four
tob
members
on
this
call,
so
we
can't
we
don't
even
have
a
quorum
to
be
able
to
vote
on
things
right
now.
So
I
like
we
can
talk
informally
about
whether
we
have
consensus,
but
this
isn't
like
this
isn't
really
a
tob
meeting.
This
isn't
a
place
where
we
make
decisions
that
are
part
of
the
tob
right
now.
B
C
B
But
I'm
still
going
through
it,
so
these
are.
This
is
good
discussion
for
me
to
start
writing
governance
document,
so
I
thought
I
thought
I'd
just
seed.
D
Yeah
yeah,
so
I
think,
there's
def,
there's
definitely
some
content
in
the
charter
and
some
of
it's
referenced
in
the
read
me
like
the
sections
where
how
votes
can
be
held
but
yeah
I
mean,
like
sam,
said
we
we,
I
mean
I've
been
in
and
around
the
oci
since,
since
the
day
was
founded
the
the
tob,
because
it's
meant
to
be
a
hands-off
organization.
As
far
as
the
technical
work
of
the
oci
projects,
it's
really
only
met
on
an
as-needed
basis
like
there's
no
monthly
quarterly.
D
So
when
we
do
have
a
call
to
meet
as
a
tob,
we
tend
to
find
a
time
that
you
know
works
across
pacific
eastern
australia,
time
zones
so
yeah
that
that's
kind
of
and
again
maybe
good.
As
someone
like
yourself
comes
in
new
and
and
and
I'm
sort
of
expressing
some
some
historic
activities
that
aren't
necessarily
written
down
they're,
just
that's
the
way
things
have
operated
for
six
years.
D
You
know,
maybe
it
would
be
good
to
kind
of
revisit
some
of
that.
Would
it
be
better
to
have
more
in
this
read
me
or
written
down
in
some
in
some
way
so
yeah,
it's
happy
to.
B
B
So
my
goal
over
here
is
just
to
document
what
the
governance
is
like.
Currently,
I
don't
think
we
can
change
much
unless
we
document
how
things
operate
currently,
once
things
you
know,
once
we
find
that
okay,
we
actually
do
not
have
processes
to
take
care
of
certain
scenarios.
B
I
I
yield
the
floor.
I
think
my
discussion
topics
have
worn
out
for
now
so
I'll
I'll
come
back
with
questions,
but
it
seems
to
me
that
questions
about
tob
operations
need
to
go
to
the
mailing
list
rather
than
brought
up
in
this
meeting.
D
But
also
feel
free,
you
know
if
you
want
to
kind
of
start
a
shared
doc
and
send
it
to
the
tob
you
know.
Maybe
some
of
these
things
can
just
like
kind
of
source
v,
bats
myself,
others
who've
been
around.
You
know
just
we
can
type.
If
you
have
a
list
of
questions,
we
can
just
fill
in
answers
where
we
have
them
or
say
that
that's
not
something
that
we've
thought
about.
You
know,
or
there
hasn't
been
a
process
or.
B
So
I
guess
my
action
here
is
to
send
all
my
questions
to
the
mailing
list.
B
G
B
Well,
so
so,
this
is
why
I
brought
up
the
question
about:
what's
the
best
way
to
do
it
in
practice,
it
seems
to
me
the
best
way
to
do
it
is
to
come
to
these
meetings,
even
though
these
meetings
are
not
supposed
to
be
like
this.
This
meeting
is
not
for
tob
business.
It
seems
to
be
the
place
where
people
come
to.
B
You
know
catch
the
tob's
attention,
so
I
guess
this
is
why
I'm
asking
you
know
what
is
the
preference,
then
that
does
not
interfere
with
the
purpose
of
this
meeting
in
particular.
B
B
Vincent,
do
you
have
any
thoughts.
G
No,
there
was,
it
was
a
huge
and
it's
kind
of
shifted
and
shaped
over
time,
but,
like
the
group,
was
very
meaningless
based
since
the
beginning
and
even
as
slack
came
on,
and
otherwise
it
kind
of
like
teetered
to
where,
like
certain
conversations
happened
in
slack,
but
it
had
been
written
into
the
charter
of
like
things
were
discussed
in
the
mailing
list,
even
down
to
like
the
voting
for
releases
and
stuff.
Like
that,
that's
why
I
say
like
not
to
feel
like
a
black
hole
because
historically.
G
There
is
not
a
whether
by
disorganization
or
just
the
nature
of
the
kinds
of
questions
and
conversations.
There
is
not
a
conclusive
single
place
for
conversations
to
be
absolutely
raised
in
that
context
and
absolutely
brought
to
conclusion
in
that
same
context.
So
sometimes
it's
just
using
the
tools
that
we
have
to
get
done
with
it,
but
the
feeling
has
been
that
sometimes
it
feels
like
something
will
go
to
a
mailing
list
and
then
not
give
me
traction
and
then
have
to
be
raised
back
in
this
call.
D
I
I
think
the
only
thing
I
would
add
to
that
is
that
I
mean
it's
kind
of
good
to
remember
that
the
initial
work
of
the
oci
was
a
pretty
small
group
of
people
who
were
basically
trying
to
get
run
c
out
the
door
and
the
first
spec
and
all
these
definitions
I
mean
there
was
a
tob.
D
There
was
this
idea
of
a
tdc
in
the
project
maintainers,
but
you
know
over
time,
and
I
think
some
of
alexa's
sort
of
prs
that
are
out
there
kind
of
aging
aging
on
the
vine
and
not
really
moving
forward,
was
to
try
and
and
refresh
the
charter,
to
recognize
that
the
oci
operates
in
quite
a
different
manner
today
than
it
did.
Six
years
ago
we
have
met,
you
know
a
few
more
specs.
D
We
have
many
more
kind
of
projects,
and
really
you
know
the
one
thing
I
I
wanted
to
kind
of
clarify
with
something
you
said.
Nisha
is
like
people
come
here
to
get
the
tod's
attention.
I
that
that
may
be
true
in
a
few
instances,
but
I
hope
people
mostly
come
here
to
get
maintainers
attention
of
a
specific
project
of
a
specific
spec
or
activity,
that's
happening,
which
is
not
the
purview
of
the
tob.
D
So
yeah
you
know
I
this.
I
think
we
used
to
call
this.
The
weekly
developers,
discussion
like
it
was
just
anyone
working
on
oci
stuff,
come
here
if
you're
stuck,
if
you
need
help
the.
I
think
the
problem
with
the
last
few
years
is
that-
and
we
talked
about
this-
probably
too
much
last
year,
but
you
know
there's
this
sort
of
first
horizon
of
participants
who
kind
of
like
moved
on
and
now
there's
a
second
horizon
of
like
participants
who
are
more.
D
You
know,
we've
got
people
from
registries
here.
Cloud
providers
like
those
people
didn't
exist
in
this
community
when
we
were
working
on
red
sea
because
it
was
a
totally
different
project,
a
totally
different
focus.
So
anyway,
all
that
to
say
like
this
is
really
meant
to
be
kind
of
the
the
working
meeting
of
developers
who
are
hacking
on
the
latest
thing
that
oci
is
working
on.
D
D
Yeah
absolutely,
but
I
guess
I'm
trying
to
de-focus
like
the
tob's
efforts
should
be
fairly
minimal
when
things
are
working
properly
in
all
the
projects
and
specs
like
we
should,
we
should
help
where
we
can.
We
should
answer
questions,
but
our
actual
concrete
work
to
do
should
be
near
zero.
Most
of
the
time
as
a
official
t.o.b
body
making
actions.
B
So
I
did,
I
did
look
at
like
the
the
open
container
statistics
on
each
of
the
projects.
Ransi
is
definitely
the
most
active.
B
I
would
think
that,
because
it
is
the
most
active,
it
is
the
most
influential,
and
that
means
that
you
know
they.
They
have
some
processes
that
maybe
we
could
probably
you
know,
take
a
page
out
of
like,
for
example,
they
have
a
maintainers
guide
where
they
talk
about
what
the
maintainers
responsibilities
are
and
how
they
should
communicate,
how
they
should
vote.
B
I
think
we
can
follow
this
their
same
working
model
because
they
are
an
active
community.
This
is
an
active
community
and
there
are
many
concerns
that
come
here
that
don't
have
anything
to
do
with
technical
details.
They
have
to
do
with
governance.
B
So
I
I
mean
I'm
I'm
fine
with
the
the
emailing
to
the
mailing
list
as
long
as
the
maintainers
as
long
as
the
tob
members
know
that
it
is
their
responsibility
to
look
at
the
mailing
list
and
answer
things
from
the
mailing
list,
and
my
fear
is
that
if
it's
not
documented
that
that
is
their
responsibility,
they
will
shirk
it.
B
So
I'm
not
saying
that
you
know
no
mailing
list
communication,
I'm
just
saying
that
there
needs
to
be
some
follow-up
from
that
mailing
list
communication,
meaning
that
whatever
is
decided
in
the
mailing
list
gets
documented
somewhere.
That
is
easy
for
other
projects
to
look
up.
B
I
will
I
will
yield
here
because
I
think
it
seems
to
me
that
governance
discussion,
this
isn't
the
forum
for
governance
discussions,
so
this
is
probably
the
last
time
I
will
bring
that
up
here
and
we'll
start
moving
those
conversations
to
the
mailing
list.
Instead.
G
G
B
G
C
Oh
yeah,
you
have
to
just
report
those
that's
true.
I
think
that's
just
the
linux
foundation,
that
does
that.
That's
not
a
tob
responsibility.
H
B
On
that
note,
I
think
josh
has
a
topic
on
distribution.
Spec
I'd
be
interested
in
following
along.
F
F
Can't
figure
out
the
word
here
as
it
relates
to
the
working
group,
the
reference
types
working
group
and
I'm
wondering
last
week
right
after
the
call
we
got
the
extend
vince's
extensions
thing
merged
and
I'm
wondering
if
that's
enough
for
us
to
put
out
a
1.1,
do
we
does.
Anyone
have
concerns
around
doing
that,
because
we
don't
really
have
something
to
point
to
as
it's
unreleased.
F
And
there
is
a
milestone,
and
one
thing
I
put
on
there
was
off
and
I
think
we're
gonna
have
to
totally
pull
that
out.
Unless
we
want
to
wait
another
six
months.
I
I've
got
thoughts
on
things,
I'd
like
to
add
to
compliance
checks.
At
some
point,
I
don't
know
if
I'll
be
able
to
get
those
done
before
you're
ready
to
do
a
1.1,
and
I
wonder
how
much
that
falls
into
including
off
in
there
somehow,
just
because
compliance
does
do
implicitly
doesn't
auth
in
there.
So
there's
something
that
happens
even
though
it's
not
part
of
the
spec.
F
I
think
actually
related
to
the
conformance
vince,
or
maybe
I
ought
to
read
through
that.
Like
would
a
for
a
registry
to
be
1.1
compliance,
it
doesn't
even
need
to
accept
those
endpoints
right.
I
F
On
off
switch
okay,
we
can
talk
more
in
github.
F
I
F
I
F
No
I'm
I'm
done.
I
just
think,
as
people
start
writing
against
extensions
if
it's
unreleased
that
has
the
risk
of
someone
changing
extensions
out
from
underneath.
I
know
like
for
sure
I
mean
a
few
months
ago.
G
G
They
just
reference
main
rather
than
tagged
releases
of
extensions
that
get
added
over
time,
because
if,
if
any
given
thing
in
the
world
like
or
as
or
whatever
you
know,
gets
gets
their
extension
documented
and
pointed
to,
I
don't
I
don't
that
hooked
the
document.
I
hope
that
the
documents
there
allow
for
us
to
not
have
to
like
rev
a
version
of
the
spec
every
time,
some
something
like
that
gets
added.
I
Would
it
make
sense
to
have
a
list
of
extensions
that
are
passed
in
that
people
want
to
have
tested
against
and
then
we'd
have
to
make
tests
for
each
one
of
those
tensions
which
gets
complicated?
But
at
least
then
is
people
explicitly
saying
please
test?
This
extension
is
really
there
and
enabled
and
working
on
my
registry.
F
F
I
I
guess,
if
we,
if
we
have
official
like
extensions
extensions,
I
do
think
that's
a
feature
and
maybe
we
ought
to
increase
our
cadence
for
releasing.
Instead
of
I
don't
know,
we've
been
pretty
pretty
slow
on
that
and
I
think
for
for
extensions.
It's
not
such
a
big
deal
since
they're
always
optional.
I
I
If
I
see
something
that
conformance
doesn't
test
with
a
1.0.0
or
you
know,
whatever
the
version
is
we're
not
going
to
go
back
and
re-tag
that
to
update
the
conformance
test,
I'm
assuming
and
so
does
that
just
mean
that
we
release
without
a
good
conformance
test,
and
hopefully
he
picks
up.
The
next
version
is
that
kind
of
best
practice
we're
going
to
follow.
F
I
I'm
not
sure
that's
a
great
idea
just
because
we
we
have
the
whole
conformance
page
now,
so
I
don't
know.
I
think
I
shot
myself
in
the
foot
with
this.
F
I
All
right
circling
back
to
we're
talking
about
the
the
extensions
listing,
basically
the
discovery
mechanism
of
that
one.
I
To
not
have
a
automatic
discovery
out
there.
Basically
there'll
be
some
registry
provider
out.
There
might
think
that
security
from
a
security
is
a
good
practice,
and
so
they
just
don't
want
to
advertise.
They've
got
these
things
out.
There.