►
Description
The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD, Kubernetes, and related CNCF projects. The OKD Working Group includes the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group produces supporting materials and best practices for end-users and provides guidance and coordination for CNCF projects working within the SIG's scope.
https://okd.io
A
All
right,
let's
go
ahead
and
get
started
anything
to
the
agenda.
Anything
any
modifications,
I'm
just
peeking
right
now,
hang
on.
B
Yeah
good
on
the
new
business
stuff
that
looks
good
sandro
thanks
for
calling
that
out.
How
do
we
want
to
phrase
jamie
the
conversation
about
moving
the
location
of
dot
docs.okd.io,
the
actual
content
to
an
alternative
location
is
that
in
the
issues
repo
now
as
as
to
individual.
B
Yeah
yeah
yeah,
if
you
could
put
that
in
the
issues
section
and
when
michael
comes
because
there's
a
little
bit
more
to
it
than
that,
I
just
want
to
make
sure
it
doesn't
impact
our
access
to
the
re,
documentation,
teams,
resources
for
building
that
that
it
doesn't
break
their
build
chain
or
whatever
to
hello.
A
All
right,
let's
bicycle
on,
so
let's
see,
let
me
put
in
I'll
put
it
in
current
projects,
the
we'll
put
repo
transition
and
the
issue
there
all
right.
Welcome
to
the
documentation,
okd
documentation,
subgroup
meeting
for
november
30th
of
2021.
A
Please
make
sure
you
put
your
name
in
the
attendance
section,
so
we
know
who
was
here
and
in
case
anyone
that
needs
to
get
information
wasn't
here.
We
know
to
get
it
to
them
in
terms
of
the
agenda.
There's
no
updates
on
in
terms
of
current
projects
on
the
agenda.
There's
no
update
to
the
charter
update
and
placements
I've
sort
of
been
plucking
away
at
it
and
haven't
really
had
time
to
complete
that
yet
name
and
scope
of
the
install
and
readme.
A
A
Predisposed
of
the
past
couple
weeks,
so
once
he
frees
up
some
time,
then
we
can
run
by
run
some
of
the
ideas
that
we
have
by
him
and
then
move
forward
code
of
conduct.
Michael
any
updates
on
changing
any
references
in
the
code
of
conduct
to
make
it
appropriate
for
okd.
C
B
I
don't
see
3t
and
I
would
like
to
I'd
like
to
also
have
jamie
and
I
have
access
to
the
username
password
for
the
twitter
so
that
we
can
announce
the
releases
so
because
tritie
is
on,
I
think,
bangalore
time
or
someplace
there.
So
that
there's
and
I
I
started
the
process,
but
I
didn't
get
it
all
the
way
through
with
her
to
share
that.
B
So
my
ask
of
dritty,
if
you're
watching
this
afterwards,
is
to
sure
if
we
can
figure
out
a
way
to
share
the
username
password
for
the
okd
repo,
with
both
jamie
and
myself,
then
like
when
vadim
pushes
out
the
4.9
release.
I'd
like
that
to
go
out
on.
A
All
right,
but
there
was
discussion
on
the
survey
at
the
main
meeting
folks,
are
pretty
much
happy
with.
It
sounds
like
the
question
list
is
pretty
much
solidified
at
this
point,
so
she's
going
to
go
back
and
rework
all
of
that
stuff
and
get
back
to
us
when
it
is
solidified
repo
transition
go
ahead.
Diane
take
it
away.
If
you
have
any
news
for
me.
B
All
right:
well,
the
legal
has
been
eating
turkey
last
week
too,
so
I
didn't
get
anything
out
of
legal
yet,
but
I
asked
I
was
going
to
ask
michael
burke,
because
one
of
the
conversations
we
had
at
the
last
working
group
meeting
was
about
transitioning,
the
location
of
the
content
for
docs.okd.io,
not
changing
the
url
or
anything
like
that.
But
if
we
move
where
that
content
is
into
a
new
repo,
whether
it's
openshift
cs,
slash
okd.
B
If
that
has
an
impact
on
the
build
process
for
documentation,
I
don't
want
to
mess
up
our
relationship
to
the
docs
team
because
we
like
having
our
docs
auto-generated
off
of
the
upstream
content,
but
I
wanted
to
make
sure
that
our
request
to
move
the
repo
for
okd
content,
not
okd
code,
but
the
content,
whether
it's
guides
or
website
or
documentation,
would
impact
how
you
build
the
docs
for
us.
B
A
Yeah,
so
so
the
is
it
the
files
are
generated
and
then
committed
to
the
docs
repo
from
from
another
location
or
they're
written
directly
to
the
docs
repo.
How
does
that
work.
F
Okay,
so
can
I
just
can
I
just
ask:
are
we
actually
planning
on
transitioning
the
docs,
because
at
the
minute
that's
actually
managed
by
a
different
process,
and
it's
served
with
a
different
repository.
It's
served
from
a
different
mechanism
that
the
okd.io
we
just
have
a
link
to
the
docs
dot.
It
has
its
own
identity
outside
of
okd
or
io.
It's
a
separate
web
serving
process.
It's
a
separate
documentation,
creation
process.
F
B
That's
that's
what
I'm
I'm
getting
to
the
bottom
of
here
because,
like
there
was
an
ask
to
move
the
docs.okd.io
content
into
the
reap,
the
repo
that
we
end
up
in,
you
know
where
we
move
it
to,
and
I
want
and
that
set
off
a
few
alarms
in
the
back
of
my
head
about
process
and
builds,
and
things
like
that.
So
that's
why
I
asked
michael
to
come.
C
A
Well,
that's
an
interesting
question,
so
those
let
me
ask
you
this:
the
new
stuff.
That's
the
new
there's,
the
new
document
format
right
that
just
came
out
that
you're
using
is
that
rendered
to
html
or
is
it
in
in
like?
Is
it
rendered
to
a
middle
product
and
then
rendered
to
html
or
is
it?
A
A
A
B
There
was
a
part
two
to
the
request
that
I
heard
at
the
the
last
meeting,
and
forgive
me
if
I
paraphrase
this
wrong
correct
me.
If
I
do,
the
other
part
of
the
ask
was,
can
we
add
into
the
docs.okd.io
links
back
to
the
guides
that
are
on
in
our
there?
So
you
have
your
regular
menu
system
for
docs.okd
dot
io,
which
is
goes
to
all
the
sections
in
the
actual
docs.okd.io
and
then
at
the
maybe
in
that
menu
system.
F
A
Was
getting
at
so,
in
other
words,
michael,
it
would
be
the
the
stuff
that
we
create.
Would
it
be
possible
to
create,
as
you
call
them
before,
books?
I
don't
know
what
they're
called
in
the
new
language
of
the
new
system
but
create
links
to
our
external
stuff
within
the
okd
generated
docs.
C
A
B
I'm
yeah
that
that
might
be
sufficient
yeah,
so
I
wanted
to.
I
was
trying
to
do
this
in
two
parts.
It's
like
one,
clear,
the
air
that
we
can't
really
move
the
docks.
We
have
to
keep
that
dock
structure
there,
but
the
other
one
was
to
embed
somehow
link
back
out
to
the
okay
dot
io
sites
guides
from
the
docs.okd.io,
and
if
you
can
create
a
sample
book
in
that
where
we
put
those
things,
how
do
we
maintain
that
book?
B
C
You
can
just
generate
a
pr
okay,
okay,.
B
All
right
cool
because
I
think
that's
yeah,
that's
what
I
was
trying
to
tease
out
here
in
this
conversation
was
the
better
way
to
go,
then
try
and
ask
them
to
break
their
build
process
or
whatever.
A
C
A
F
Yep,
it
is
on
the
website
how
you
raise
a
an
issue
or
a
pr
against
the
the
doctors,
the
official
docs
yeah.
F
A
Let's
move
that
using
forward
to
make
things
as
as
clear
as
possible
as
to
which
documentation
we're
talking
about
okay,
so
task
for
us
is
for
the
for
this
group,
maybe
at
our
next
meeting,
which
won't
be
until
next
year
to
come
up
with
a
list
of
links.
We
will
file
a
pr
or
an
issue
with
the
docs
repo
with
those
and
then
michael
can
then
get
those
incorporated
into
the
okd
documentation
as
a
book,
as
is
that
actually
the
correct
terminology
still
with
the
name,
I
think
so.
A
Okay,
let
us
know
if
you
leave
that's
what
we
call
it:
okay,
cool
all
right
so
now,
moving
on
to
the
survey
repo
transition,
are
there
any
issues
in
the
repo
or
well?
It
looks
like
I
kind
of
broke
this
up,
but
I
don't
see
any
issues
with
the
docs
that
came
in.
Oh
actually,
there
is
low
contrast
for
text
and
background
sandra.
Do
you
want
to
talk
about
that?
A
little
bit
about
what
you
put
in.
G
Yeah,
I'm
not
sure
if
it's
just
my
monitor
but
the
the
contrast
between
the
text
and
the
background.
It's
really
really
narrow.
G
A
With
I
think
these
are
equalities
yeah,
I
think
that's
great
now
do
this.
Did
you
try
it
with
both
theme
settings
because
there's
that
little
switch
at
the
top.
G
Yeah
I
tried
it
with
the
dark
mode
and
with
the
light
mode,
and
they
have
low
contrast
in
different
places.
I
say:
cool
okay
depends
on
where
you're
looking
at.
F
Yeah
yeah,
I
mean
it's
easy
to
change
colors.
I
I'm
not
a
web
designer,
so.
D
F
I
I
put
the
caveat
there
that
I'm
happy
that
if
anybody
wants
to
come
up
with
core
themes-
font
sizes-
I
can
add
them
in
very
easily-
but
I'm
somebody
with
more
of
a
ux
experience-
should
probably
do
that.
B
I
could
ask
brandon
johnson
who's.
The
contractor
I
have
on
on
demand
to
take
a
look
at
it
and
give
a
few,
maybe
examples
in
the
draft
over
the
holidays,
and
then
we
could
come
back
and
look
at
it.
It's
a
good
thing.
People
with
disabilities
are
visual
impairments,
often
say
the
same
thing,
so
not
be
a
bad
thing
to
do.
There
might
even
be
a
resource
inside
of
red
hat.
F
A
Yeah
well,
and
I
meant
more
along
the
lines
of
so.
If
you
find
someone
or
we
find
someone,
you
can
just
direct
them
what
to
do
sort
of
yeah.
So
what
I'd
like
to
do,
ideally,
is
brian:
have
you
sort
of
take
point
on
website
stuff,
not
necessarily
doing
the
work,
but
in
terms
of
getting
people
to
the
place
where
they
can
do
the
work
like
and
helping
us
find
volunteers
and
stuff
like
that,
so
consider
yourself,
a
web
manager?
How
does
that
sound.
F
A
And
I'm
I'm
writing
up
something
to
to
for
us
to
post.
I
haven't
finished
it
yet.
Obviously,
turkey
day
or
day
of
giving,
thanks
as
it
is
more
for
me,
took
a
big
chunk
out
of
my
time,
but
I
plan
on
having
that
done
before
the
end
of
the
year.
We
will
have
something
up
to
address
the
security
stuff.
A
F
Okay
and
then
the
last
one
we
we
deferred
the
decision
on
inclusive
language,
because
diane
wasn't
here
last
time
just
to
run
that
that
by
you
and
so
everything
that
we've
we've
done
everything
we
can
for
inclusive
language.
But
there
are
still
quite
a
few
uses
of
the
word
master
and
they
really
relate
to
the
product
because
we
control
the
control
plane,
nodes,
the
master
nodes.
F
So
I
think
we've
done
everything
that
we
can
from
our
documentation
point
of
view,
but
it
was
just
that
there
are
still
things
reported
in
the
tool,
but
we
can't
really
do
anything
about
it
and
the
other
area
was
external
gate
repos
that
we
link
to
still
have
the
default
branch
called
master
branch,
but
again
they're
out
of
our
control
or
their
other
repos.
Like
m
vadim's,
install
repo,
and
I
think
the
okd
repo,
the
openshift,
slash.
F
Okay,
the
epo
is
still
master
but
from
a
documentation
point
of
view
where
we're
sort
of
clean
in
terms
of
things
that
we
control.
So
are
we
happy
with
that?
Or
do
we
want
to
take
further
action?
Was
the
decision
we're.
B
Never
happy
with
that,
but
I
think
that
is
you've
pointed
out.
It
is
on
the
product
side
of
the
house,
and
I
know
there
is
an
initiative
to
change
that.
I
don't
know,
michael
if
you're
aware
of
that
at
all,
but
I
think
it
takes
a
little
bit
of
time
and
probably
more
time
than
we'd
like
so
I
will
see
if
I
can
get
an
answer
from
the
engineering
team
on
when
that
what
that
timeline
is
and
bring
it
back
to
the
group
yeah.
B
F
Yeah,
so
if
you
go
into,
if
you
actually
go
into
that,
so
two
or
three,
if
you
go
into
that
issue,
you'll
see
that
the
scan
returned
66
cases
and
I've
highlighted
all
the
places
where
so
I
mean
I
think
we
could
put
something
in
our
main
meeting,
because
I
mean,
if
you
look
three
of
those
repos
are
okay
d,
repos
or
community
repos.
F
So
they
are
probably
things
that
we
can
influence
or
two
of
them
are
obviously
we've
got
the
library,
we've
got
the
ocp
and
then
we've
got
our
installer.
So.
A
B
D
And
I
think
that's
done,
and
it
really
is
a
never-ending
thing.
Like
the
the
wildfly
project.
Has
you
know,
master
branch,
etc?
I
think
that's
a
red
hat
thing.
You
know
every
single
docs.okdio
dock
for
every
version
and
every
on
so
on.
Like
you
know,
I
would
say:
push
it
to
those
people
and
let
them
clean
up
their
things.
A
But
I
think
I
think,
opening
an
issue
with
those
respective
repos
does
that
right,
yeah
saying
hey,
dude
change,
this
he's
going
to
change
it.
Likewise,
if
we
open
one
up
with
the
openshift
repo
or
the
okd
repo
christian
or
someone
can
bring
it
up,
push
it
upstream
and
try
to
get
into
trust.
D
B
That
that
was
it
three
that
are
are
in
our
control,
like
that
vedim
could
fix
or
that
christian
could
push
forward.
We
could
we
could
put
issues
there
and
tag
christian
and
tag
vadim
and
ask
them,
assign
it
to
them.
I'm
rich
bowen,
who
is
in
he's
a
red
hat
or
who's
one
of
who's,
the
person
who's
doing
the
inclusive
language
stuff
has
a
master
plan.
I
mean
has
been
working
with
the
engineering
teams
to
get
this
worked
out.
I
just
haven't
seen
a
timeline
for
when
it's
getting
done.
B
I
would
suspect
that
there
is
out
there
somewhere
already
an
issue
logged
against
the
ocp
product
repos
to
fix
this,
but
I
haven't
seen
it
and
I
haven't
found
it
yet
that
we
could
add
a
comment
on
to
rather
than
create
open
a
new
comment.
So
I
think
that
might
be
the
thing.
B
There
we
go
yeah
and
then
find
find
that
needle
in
the
haystack
find
the
one
for
the
overall
product
and
I'll
see.
If
I
can
dig
that
up
and
go
fishing
for
that,
and
I
know
that
there
was
an
overall
scheme,
but
that
was
probably
six
months
ago
when
we
brought
this
topic
up
the
first
time.
I
don't
know
what
the
date
is
on
that
issue,
but
it's
it's
an
old
one,
so
I
hadn't
thought
about
it
in
a
little
while.
B
F
Okay,
so
I'll
raise
the
issues
against
the
install
the
community
and
the
okd
main
repo
and
then
I'll
close
that
issue
for
us
and
then
the
last
thing:
it's
not
an
issue,
but
it's
a
pull
request
and
we
talked
I
think
two
meetings
ago
about
that
we
do
the
reviews
as
to
whether
to
accept
pull
requests
at
this
meeting.
So
I
don't
know
whether
we
want
to
get
into
that
now
or
we
just
want
to
accept
this.
This
is
one
of
sandro
to
put
the
the
content
about.
F
A
B
A
I
think
you
know,
let's
look
at
the,
let's
actually
bring
it
up
and
just
know
what
we're
dealing
with
here.
So.
F
A
I
would
say:
let's
do
this
asynchronously
as
opposed
to
this
meeting,
because
it
looks
like
it's
actively
being
discussed
as
we
speak,
like
literally
vadeem,
just
looked
at
it
four
minutes
ago.
So
let's
do
this
asynchronously,
but
let's
get
it
done
before
the
end
of
the
week.
Once
everyone
has
signed
off
on
it,
then
yeah
I'd
say:
let's
go
ahead
and
incorporate
it.
F
F
A
A
F
A
As
well
I
mean
you
know
because
moving
forward,
it
won't
always
be
you
so
sandra.
Let's
go
ahead
and
add
you
that
way.
We've
got
one
other
person
to
help
with
that
and
you're
sandra
you're,
very
good
with
like
documentation
and
and
prodding
us
to
get
stuff
in.
So
I
think
it'll
be
good
to
have
you
as
an
approver.
G
I
I
don't
know
honestly,
but
I
I
don't
think
that
should
be
a
threshold
for
someone
from
community
to
be
added
there
as
long
as.
F
G
D
A
All
right
cool,
let's
move
on
now
to
we've,
got
a
bunch
of
new
business
that
basically
relates
to
the
same
thing.
So
my
recollection
was
that
basically
we
were
going
to
work
on
4.9
stuff
and
at
the
beginning
of
the
year,
actually
get
it
posted
because
we
were
going
to
have
to
write
that
stuff
out
so
sandra.
We
we
had
a
plan
to
do
it,
it's
just
not
as
quick
as
what
we
would
ideally
want,
because
this
is
our
first
time
actually
syncing
up.
A
Well,
that's
not
true,
I
think
4.4
or
whatever.
I
think
there
was
a
big
push
to
have
things
synced
in
terms
of
announcements
via
okdu
resources
and
stuff
like
that.
But
since
then
there
hasn't
been
so
this
would
be
our
first
time
actually
like
announcing,
and
so
the
discussion
at
the
last
docs
meeting
I
think
was
like
okay.
We
need
a
list
of
features
and
things
that
we
can.
A
We
can
forward
the
open
shift
stuff,
but
also
write
up
some
okd
specific
stuff.
So
that's
where
that
is
at
for
all
of
those
and
I'm
volunteering
to
write
some
stuff,
and
I
don't
know
that
anyone
else
has
volunteered
yet
to
help
write
some
stuff
for
this.
H
Yep
so
dan
and
I
I
think,
are
planning
on
doing
the
openstack
deployment
stuff
because
we've
beaten
our
heads
into
the
ground
on
it
enough
times.
Now
that
we
we
kind
of
have
a
good
grip
on
what
you
need
to
do,
for
it.
E
Yeah
so
I
gathered,
I
gathered
a
list
in
the
other
in
the
other
meetings
notes
about
just
everybody
who
said
they
could
they
could
do
a
thing,
so
the
next
steps
are.
A
They're
not
so
I
responded
to
you
a
little
bit
in
your
in
chat
when
you
asked
me.
Basically,
we
don't
have
a
centralized
like
volunteer
contact
list,
so
it's
basically
the
working
group,
google
group
and
slack
right
now,
and
if
we
want
to
maintain
a
working
group
participant
list,
then
we
could
do
that
and
we
talked
about
this
before
it's
just.
I
haven't
had
the
time
to
set
up
such
a
thing
where,
basically,
we
list
everyone
who's
actively
involved
with
the
working
group
and
what
their
areas
of
participation
are.
E
Okay,
I
yeah-
I
just
didn't
know
if
if
such
a
thing
existed
so
I
had
asked
in
the
openshift
commons
okd4
group:
could
we
have
an
okd
guides
channel
made,
please
that
seems
like
a
reasonable
place
to
coordinate
that
work.
B
Sorry,
okd
dash
guides
or
guidance
which
would
you
prefer.
A
To
organize
it,
I
would
say
that
would
be.
The
best
thing
is
to
start
a
discussion
there
and
then
people.
H
If
we're
using
github
discussions,
we
might
also
want
to
set
up
if
we
know
who
the
people
are
or
doing
different
things
we
might
want
to
set
up.
I
think
they're
called
teams
in
github
of
like
representing
the
individual
sub
groups
in
the
working
group,
doing
different
things
as
well
as
a
catch-all
group
to
to
hit
everyone.
F
But,
but
also
as
we
make
decisions
documented
in
in
the
okay
dot
documentation
under
the
subgroups,
so
that's
where
people
should
go
and
look
for
what
the
state
of
a
working
group
is.
What
the
projects
are,
that
that's
what
it's
there
for?
That's
why
we
change
it
to
a
dynamic
content,
so
people
can
easily
make
updates.
A
Right
and
ideally,
what
would
happen
is
that
each
subgroup,
their
respective
notes
and
decisions,
then
get
presented
at
the
main
meeting
as
a
bullet
item.
So
basically,
everyone's
sort
of
checking
in
each
subgroup
sort
of
checking
in
with
where
they're
at.
G
A
Yeah,
so
let's
remember
who
wants
to
who
I
I
I
will
volunteer
to
archive
those
somewhere
cool
and
we
will
archive
those
and
remove
them,
and
let's
just
get
this
done
with.
Yes,
they
are
in
the
okd
dot,
io
repo.
A
B
A
For
folks
that
weren't
at
the
main
meeting,
we
did
register
on
github
okd
dash
project.
I
think
it
is
timothy
did
from
the
f
cost
group
for
us
and
then
added
myself
as
and
brian,
and
I
think
a
handful
of
other
people,
diane
and
vadim,
as
as
owners
on
it.
Yeah.
B
And
I
reached
out
to
the
owner
of
the
github.com
okd
repo
that
is
completely
empty
and
been
dead
for
a
long
time
and
heard
nothing
back.
So
I'm
also
there's
a
process
in
github
to
ask
for
that
back.
Okay,
we'll
see
if
we
can
initiate
that
I'll,
give
them
another
couple
of
days
and
hit
him
up
again
and
if
he
doesn't
respond
or
she
doesn't
respond
or
they
don't
respond,
we'll
see
if
we
can
get
github
to
give
it
to
us
too.
An
okd
project
is
fine
as
well.
I
just
like
short.
A
Okay,
all
right
so
yeah.
So
let's
try
to
direct
subgroup
stuff
to
for
documentation
the
okd
dot
io
in
cs
right
now
and
then
at
the
main
meeting.
We'll
have
everybody
so
daniel
at
the
next
main
meeting.
If
you
could
update
us
on
where
you're
at
with
things
and
then
moving
on
we'll
do
that
for
all
of
the
subgroups
and
sandro
et
cetera.
So
eventually,
we'll
have
like
four
or
five
subgroup
updates
in
the
main
meeting.
A
G
A
That's
actually
everything
that
we
have
on
the
list.
Does
anyone
have
anything
else
they
would
like
to
bring
up.
D
D
A
A
A
B
B
So
I
would
say
that
one
of
the
discussions
we
should
add
maybe
to
the
the
repo
is
you
know
what
is
the
new
release
announcement
process
rather
than
call
it
release
process,
because
that
might
scare
the
bejesus
out
of
video
but
announcing
a
new
release,
so
we
put
out
a
blog.
We
do
this
and
do
that.
You
know
how
we
do
that
and
I
think
that's
we'll
use
4.9
to
to
figure
out
that
process
or
what
we.
B
F
B
I
think,
and
I
I
hesitate
to
even
say
this-
I
think
that
that's
actually
what
I
was
thinking
in
the
release
process
for
each
new
release,
because
it's
a
sub
release
for
the
night
like
fortnightly,
I
almost
think
there's
a
way
to
automatically
kick
off
a
a
twitter
announcement
to
when
the
release
is
built
that
we
could
add
into
the
build
process.
I've
seen
it
done
that.
I
E
So
there
are
two
hooks
here:
one
is
the
build
process.
The
other
is
the
okd
clusters
have
an
have,
a
mechanism
of
checking
for
updates
right.
We
can
hook
into
that.
I
don't
actually
exactly
know
what
that
mechanism
is
like.
Is
it?
Is
it
an
rss,
feed
or
or
is
it
just
they
they
paying
an
api
that
we
can.
A
E
E
B
We
could
talk
chat
with
them,
vedim
and
slack
and
somewhere
and
see
if
that's
humanly
possible,
I've
just
seen
it
done
for
other.
I
can't
even
think
of
one
off
the
top
of
the
other
other
release
processes
that
it
just
automatically
pushes
out
to
twitter,
but
that's
getting
ahead
of
ourselves.
I
think
if
we
just
document
what
we
want
and
then
we
can
figure
out
how
to
get
it,
make
sure
things
get
in
and
they'll
get
missed
and
don't
rely
heavily
on
vedim
or
whoever
is
in
that
role.
B
I
think
you
have
privs
to
do
so.
Let
me
check
and
see
if
you
can
figure
out
how
to
do
it.
If
not,
let
me
know
and
then
I'll
figure
out
how
to.
A
Yeah
I'll
take
a
look
after
this
meeting.
Okay,
do.
A
Else
on
the
meeting,
no
all
right,
all
right
I'll,
try.