►
From YouTube: OKD Community Development Meeting 03 21 2023
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
B
Let's
go
ahead
and
get
started
with
the
okd
working
group,
Community
Development
meeting
for
March
21st
of
2023,
and
we
have
a
a
sort
of
mandate,
I
think
to
go
through
the
project
planning
board
and
really
start
to
use
that
as
our
area
of
focus
in
terms
of
planning
for
Community,
Development
and
whatnot.
B
D
B
E
I
don't
mind
either
way,
it's
probably
easier
if
you
drive
if
you're
sharing.
If
you
want
to
share
well.
E
B
All
right,
it's
all
good,
okay,
so
here's
the
project
board
and
again
the
idea
is
for
us
to
get
back
into
using.
We
started
to
set
it
up
and
then
we
sort
of
drifted
away.
I,
don't
recall
the
reasons
for
it,
but
the
idea
is
to
use
this
for
our
planning
moving
forward
into
into
really
shape
the
meeting
around
it
so
that
we
can
make
sure
that
we
get
things
done.
B
So,
let's
look
at
in
progress
and
we'll
we'll
move
our
we'll
move
basically
from
right
to
left.
I
think
that
that's
a
good
way
to
try
to
get
rid
of
stuff-
that's
maybe
been
completed,
but
we
don't
know
or
what.
E
So
so
what
I
did
is
I
moved
a
lot
of
the
stuff
that
was
in
progress
into
radio
backlog,
okay,
just
to
just
so,
we
start
off
with
a
little
bit
clearer.
So
these
are
the
two
things
that
we
talked
about
last
week
where
the
rest
of
the
stuff
I
think
quite
a
lot
of
it
is
stale
yeah
well.
A
Yes,
Brian
merged
that
today,
so
thank
you.
Brian,
okay,
fantastic.
D
B
Yeah
good
one,
okay,
so
documentation,
marking
three
one
is
end
of
life.
B
B
So,
what's
the
general
consensus-
and
forgive
me
folks,
I
wasn't
here
two
weeks
ago,
so
I'll
have
to
catch
up
a
little
bit,
sir.
We
we
basically
good
to
go
and
we're
gonna
pull
it
from.
E
So
the
the
consensus
was,
we
don't
want
to
remove
it
because
we
still
have
people
in
the
community
that
are
using
the
311
documents.
I
mean
we
know
over
two
or
three,
but
still
are
out
there
that
haven't
yet
gone
to
four,
so
we
didn't
want
to
move
it,
but
I
think
the
idea
was
that
we
put
a
banner
across
the
top.
E
F
Yeah
Brian
we
haven't
released
that
blog
post
that's
going
to
have
the
end
of
build
in
it.
Yet,
okay.
E
Because
because
Michael
was
asking
for
the
wording,
if
you
just
go
further
down,
so
we
were
just
going
to
copy
the
wording
from
the
Centos
and
Community
some
once
we
have
that
I
think
Michael's
just
going
to
put
a
banner
on
the
top
of
the
documentation,
just
to
say
that
it's
it's!
No,
it's
not
under
active
maintenance
at
the
end
of
life
or
whatever
the
wording
we
decide
and
I
think
he
was
coming
back
and
said.
What
is
the
wording?
Okay,.
B
E
Well,
I
mean
in
reality
everything
but
412
is
is
out
of
Maintenance.
We
don't
retrofit
anything
back
beyond
the
current
version.
Do
we
so
do
we
need
do
we
want
to
put
that
on
everything,
not
interactive
maintenance
or
not
no
longer
being
maintained
on
everything,
but
the
latest?
Or
do
you
want
to
make
311
a
a
sort
of
a
different
message?
Sort
of
this?
Isn't
the
current
design
or
release
or
anything
yeah.
G
E
But
I
think
we
also
need
to
be
clear
that
we
are
different
from
ocp,
because
I
think
there's
a
lot
of
confusion,
that
a
lot
of
people
associate
okb
and
assume
there's
a
similar
pattern
as
ocp.
So
I
think
we
do
need
something
that
says
that
would
different
from
us
from
ocp.
We
don't
have
the
long-term
support
versions:
We
Never,
Back
Port
any
fix
to
any
previous
version.
E
G
So,
just
as
a
reference,
if
I
go
to
The
openshift
Container
platform,
4.3
documentation,
it
says
there
with
a
big
red
banner
on
the
top.
You
are
viewing
documentation
for
a
release
that
is
no
longer
maintained.
Right
and
I'm
actually
surprised
that
that
doesn't
show
up
for
our
documentation.
Since
it's
just
a
copy
paste
thing.
B
Well,
they
have,
or
at
least
they
used
to,
they
have
like
basically
flags
that
flip
sections
on
and
off
I.
B
G
B
Yeah
well,
and
we
also
want
to
look
at
what
we
put
on
the
okd.io
site.
So
one
thing
I,
don't
think
we
have
anywhere
is
just
a
blurb
about
our
release
cycle
because
we
sort
of
copied
and
pasted
everything
from
what
Vadim
had
on
the
readme
at
the
repo.
Maybe
we
create
a
task
to
just
write
a
paragraph
about
the
release
cycle
and
how
that's
to
answer
Brian's
pointed
to
to
write
something
that
basically
identifies
what
the
release
cycle
is
and
how
it's
different
from
ocp.
B
A
I
just
wanted
to
add
a
comment
in
here:
I
think
like
we
should
definitely
make
it
like
a
page
that
describes
our
support
policy
or
our
like.
Whatever
we're
calling
this,
you
know
like
our
really
our
whatever
we
cover
but
I,
think
I
think
we
could.
We
should
actually
go
further
than
the
ocp
docs
I
think
we
should
have
that
Banner
on
every
version,
even
the
current
version.
That
just
says,
and
instead
of
saying
this
version
isn't
supported
or
something
like
that.
A
I
think
we
should
call
out
the
fact
that
you
know
tell
the
user
okd's
support
and
maintenance
life
cycle
is
different
than
ocp.
You
should
look
at
this
page
because
for
a
new
user,
if
they
don't
see
anything
there,
they
might
expect
the
diversion
they're
getting
into
has
long-term
support
or
something
and
I
think
we
should
make
it
explicit
to
everyone.
Even
someone
who's
just
starting,
say,
hey!
A
Look
if
you're
on
4.x,
you
know
you
should
know
that
once
we
go
to
4.x
plus
1,
the
okd
working
group
is
not
going
to
like
you
know,
we're
not
going
to
continue
support
for
this
right
and
we're
not
going
to
backboard
for
that.
So
I
think.
Even
as
someone
making
an
initial
decision,
that's
an
important
thing.
They
need
to
think
about.
E
I
mean
I've
just
gotten
the
documentation.
There
is
something
we've
got
to
fix.
If
you
just
go
to
this
page,
I'll
put
it
in
the
chat.
E
There
is
a
section
called
support
in
the
okd
documentation
which
says
get
support,
visit
the
red
hat
customer
portal
and
review
knowledge
base
article
submit
a
support
case
and
review
additional
product,
documentation
and
resources.
All.
B
B
I'm,
creating
a
separate
I
want
creative
yep
separate
items
because
one
would
go
to
Michael
Burke
and
then
one
is
for
us
to
do
on
the
website.
So.
B
B
How
do
folks
feel
like
this
brings
up
an
interesting
question
of?
Do?
Is
this
information
we
would
want
to
have
just
in
the
docs
or
also
on
the
website.
F
G
Because
I
mean
it's
also
not
really
true,
that
we
don't
support
all
the
versions
in
a
way.
I
mean
we're
not
offering
commercial
support.
But
if
someone
comes
up
with
a
question,
let's
say
for
4,
11
or
410.
Now
in
our
issue
tracker
at
least
probably
some
people
are
gonna
chime
in
and
and
have
some
comments,
but
of
course,
you're
not
getting
commercial
support,
but
you
also,
as
Jamie
mentioned
earlier,
you're,
also
not
getting
that
for
the
latest
version.
B
B
Was
this?
Let
me
just
finish
this
one
thought
one
of
the
things
that
maybe
newer
folks
who
aren't
in
the
meeting
aren't
aware
of
is
that
early
on
there
was
a
very
vehement
discussion
where
Vadim
Christian
at
all
from
Red
Hat
were
very
adamant
not
to
use
the
word
support
in
any
way,
because
it
could
lead
people
to
think
that
at
some
level
there
was
a
commitment,
I'm.
C
E
E
B
So
someone
was
I
inadvertently
cut
someone
off.
Does
that
person
want
to
chime
in
again
sorry
about
that
yeah.
F
It's
okay:
what
about
saying
Community
Assistance
for
support!
So
there's
the
expectation
this
is
coming
from
the
community,
not
from
Red,
Hat
and
or
anyone
else,
and
it's
assistance.
F
So
you
know,
and
you
can
even
put
a
you
know
the
a
qualifier
you
know
if
you
ask
for
support,
you
know
if
you
have
a
question
this
is
coming
from
members
of
the
community.
Please
understand
this
is
not
their
full-time
job;
they
will
get
to
it
when
they
get
to
it.
If
they
can
get
to
it
right,
no,
so
give
them
some
level
of
EX
expectation
as
well.
B
Yeah,
the
way
that
it
works
briefly
is
there's
a
a
series
of
scripts
that
they
run,
that
where
there's
flags
that
say
include
or
exclude
the
books
as
they're
called
in
the
documentation
and
that's
how
the
okd
documentation
gets
constructed
generated
and
we
reach
out
to
Michael
Burke
and
let
him
know
please
remove
this,
and
then
he
puts
tags
around
a
section
that
will
remove
it
next
time
the
the
generating
script
runs,
but
we've
not
yet
actually
added
a
book
as
they've
recalled.
B
G
B
B
So
do
we
want
a
page
that
outlines
I
created
this
because
I
we
we
originally
were
talking
about
the
release
cycle
on
letting
people
know
about
the
release
cycle,
I
think
at
least
having
something
on
the
website
describing
the
release
cycle
is
a
good
idea,
because
we
do
get
a
lot
of
questions
about
well.
When
is
you
know
the
ocp-412
came
out
like?
Does
that
mean
okd412
is
out,
you
know.
Does
that
mean
you
know
stuff
like
that?
So.
A
I
mean
having
it
on
the
website
is
nice
because
you
know
it's
I
think
as
Amy
suggested,
like
it's
really
easy
for
us
to
change
that,
and
then
we
could
always
if
we
put
a
ban,
if
we
end
up
putting
a
banner
in
the
docs,
we
can
always
have
a
link
from
that
Banner
to
the
support
page
on
the
website.
So
that
makes
it
easy
too.
B
All
right
I
will
assign
this
task
to
myself
I'm
happy
to
to
come
up
with
some
language
yeah
right,
Amanda.
B
And
that's
going
to
be
a
separate
ticket,
so
that'll
be
remove
d
support
page
there's.
B
D
Are
we
able
to
make
changes
to
the
landing
page
of
the
docs
site?
If
you
just
go
to
docs.okd
dot,
IO
it?
It
doesn't
even
mention
anything
about
it.
Being
a
community
lens
distribution
basically
says
it's
a
distribution
of
kubernetes
optimized
for
applications
and
is
used
to
build
openshift
online
and
openshift
container
platform.
B
B
E
E
B
B
B
E
E
C
C
C
Yes,
I
I,
look
you
tell
me
because
I've
got
the
so
I've
got
a
draft
there,
installing
a
single
node
okd
cluster,
the
real
Hardware
so
should
I
just
move
it
to
in
review
and
then,
if
you
guys,
are
happy,
we
can
then
look
at
including
it
somewhere
in
the
in
the
as
a.
A
C
A
blog
or
in
the
okd
documentation,
I,
don't
know
you
tell
me.
E
E
I
don't
know
personally
I
think
it
should
be
in
the
the
docs,
because
that's
where
all
the
rest
are
being
stored,
content
is.
D
C
C
The
the
the
the
Luigi,
the
one
on
top
is
my
private
GitHub
and
the
LM
is
the
red
hat.
One
yeah
use
the
red
hat
one
yeah.
B
B
Progress
yeah
all
right
all
right
now,
let's
go
to
ready,
investigate
the
available
tutorials
for
setting
up
okd
to
determine,
and
we
did
a
lot
of
work
on
that
we're,
and
then
someone
actually
started
asking
questions
on
the
thread
itself
and
then
I
think
that's
where
we
sort
of
where
we
left
it.
So
we've
got
this
great
list
and
I
think
we
wanted
to
sort
of
cuddle
this,
for
what
we
think
is
the
best
right,
something
that
we
can
highlight.
B
So
what
I
I
think
what
we
want
to
do
is
have
folks
contribute
on
this
thread
to
which
ones
you
think
are
worthy
of
highlighting
on
the
website.
For
folks
to
you
know
utilize,
but
so
much
of
it
is
is
really
old.
I
do
appreciate,
Dwayne
that
you
put
the
the
age
of
these
things
in
here.
B
So
yeah
I
would
say
moving
forward,
we'll
check
up
on
this
in
two
weeks.
But
if
folks
could
comment
on
what
ones
you
think
are
worthy
of
making
it
to
the
website,
that
would
be
helpful
and
then
that
way
we
can
sort
of
have
a
curated
list
of
stuff
that
at
least
we're
highlighting
examples
of
documentation
that
we
haven't
been
able
to
fill,
or
we
don't
have
the
people
power
to
maintain.
B
So
definitely
something
that's
that's
ready
to
be
tackled
is
for
folks
to
select
good
examples
of
documentation
that
we
can
direct
people
to
Define
a
getting
started
page
for
beginners.
B
And
this
sort
of
Diane
was
going
to
do
it
and
obviously
she
had
you
know,
has
stepped
away
in
the
bigger
picture.
So
does
anyone
want
to
take
this
on?
Well.
H
B
E
G
E
B
E
E
So
I
I
think
that
was
what
what
kicked
this
one
off
it
was.
Is
there
anything
we
can
do
to
sort
of
hand
hold
somebody
in
terms
of
just
getting
them
active?
Because
if
you
look
at
a
lot
of
Open
Source
sites,
they
have
a
getting
started,
which
is
a
Hello
World,
10-15
minute
exercise,
and
then
we
put
them
into
the
real
docs
I.
Think
it
was
that
idea,
even
though
okd
isn't
a
10-15
minutes
getting
started
reality
because
it's
kubernetes
and
it's
it's
a
full
blown
install
of
it.
So.
B
B
E
If
I
do
a
six
node
I
mean
yes,
maybe
once
we
have
the
assistant
installer
Sno,
but
even
then
you've
got
to
set
up
the
image
for
the
assisted
in
Solo
run
through
that
wizard
download
the
iso
then
upload
it.
And
then
it's
not
a
here's.
Three
steps
to
get
you
going.
B
E
B
E
B
B
I,
does
it
make
sense
for
us
to
have
a
basic
and
we've
done
many
in
the
past,
but
they've
been
kind
of
opinionated
in
terms
of
platform,
but
a
basic
video
of
of
installation
and
destroying
on
AWS
just
so
that
people
can
watch,
because
we
don't
if
we,
if
people
go
to
the
website,
there's
nothing.
That
really
shows
you.
What
the
cluster
looks
like
in
terms
of
the
console
or
the
CLI,
there's
really
nothing
that
that
grabs.
B
F
B
Is
but
it's
all
very,
do
it
on
UPI
on
vsphere,
do
it
in
AWS
with
IPI?
Do
it
there's
nothing,
that's
generalized,
because
there's
so
many.
G
C
F
E
F
E
And
then
we
come
down
to
well,
why
wouldn't
you
just
use
openshift
local
CRC
or
whatever
it's
called,
which
does
have
an
okd
flavor
to
it.
B
C
The
the
CRC
the
CRC
is,
is
really
texting
on
on
on
a
laptop
I
mean
you
need
at
least
32
gig
of
of
RAM
and
a
couple
of
CPUs
available,
and
then,
if
you
you're
doing
your
development,
like
some
people,
use
I,
don't
know
Visual,
Studio
or
jet
Brands
IDE,
and
then,
by
the
time
you've
developed
your
first
application.
Your
machine
is
halted
so.
G
I
want
to
come
back
to
the
suggestion
from
Jamie
I.
Think
a
video
is
a
really
excellent
idea,
because
it
allows
us
to
kind
of
take
that
cost
once
of
spinning
up
whatever
six
null
cluster
and
then
also
showing
some
of
the
powers
like
okay.
Maybe
let's
do
an
upgrade
now
or
what
what
happens
if
I
delete
one
of
the
machines
or
if
one
of
the
machines
is
sick,
and
then
you
just
see
that
okd
takes
care
of
everything
in
the
video,
and
maybe
this
can
be
covered.
F
E
H
E
Than
fixing
it
now,
let's
assign
the
task
to
somebody:
I
mean
I,
don't
know
whether
you
fancy
this
one
Jack
or
to
actually
drive
this
one
along,
but
let
somebody
Define
this
or
we
can
use
a
discussion
thread
to
actually
say
what
should
the
experience
be,
and
then
we
can
look
at
craving
it.
B
F
B
E
B
F
Spots
s-p-o-t-z,
if
it
requires
two-factor,
put
another
Z
on
there,
if
not
that'll,
work.
B
Are
you
popping
up
here?
Will
you
I'm.
B
Are
you
part
of
this
of
the
okd?
Have
you
been
added
overall
to
okay?
Okay,
then
we'll,
let's
I'll
come
back
to
this,
but
yeah
we'll
assign
that
to
you
we'll
add
you
to
that
and
then
we'll
do
that.
Okay,
okay,
we've
got
18
minutes,
let's
see
if
we
can
fly
through
review
guide,
section,
docs,
yeah,
actually
someone
someone
mentioned
something
in
the
channel.
B
I
think
was
like
two
weeks
ago
about
an
outdated
Doc
and
I
asked
him
to
put
in
a
ticket
I,
don't
know
that
they
did
or
not,
but
we
probably
should
actually
cycle
through
the
guides
again,
because
now
they're,
probably
once
again
outdated
or
even
more
outdated.
Well,.
B
They
will
be
once
we
get,
but
we've
we're
I
I
feel
like
we
need
to
get
something
happening
to
clean
these
up,
instead
of
just
letting
them
sit.
So
do
we
pull
them
down
in
general
and
just
wait
for
the
other
effort
to
come
up
because
people
are
getting
misdirected
I
guess
is,
is
my
concern,
because
the
thing
from
the
comment
from
a
user
two
weeks
ago
was
there
was
misinformation.
Basically
that
wasn't
valid
anymore
in
one
of
the
guides.
How.
B
I,
don't
know
what
do
folks
think
take
them
down
in
their
entirety,
or
do
we
review
them
real,
quick,
maybe
at
the
next
meeting
and
and
see
if
they
make
the
cut
to
stay
or
not,
and
this
is
the
guides
that
are
right
here
these.
F
B
Yeah
I
mean
it's
kind
of
yeah.
This
is
this
is
charo's.
E
G
B
E
Mean
I
I
also
think
that
even
in
store
config
has
changed
since
then.
So,
if
you
use
the
scripts
from
here
or
the
git
repos,
they
won't
work
because
they
they
change.
The
I
forget
what
what
they've
changed
a
couple
of
the
fields
that
are
now
mandatory
or
default
within
the
installed
config
file,
for
example,.
B
B
For
example,
this
one
this
is
the
one
that
I
wrote,
I
I,
think
it's
helpful,
but
I
think
you're
right
as
blog
posts,
and
we
were
going
to
reach
out
to
the
authors,
but
I
don't
think
we
got
contact
info
for
every
single
one
of
these.
So
prerequisites
who
was?
Does
anyone
remember
who
wrote
prerequisites?
We
know
this
is
me
whose
prerequisites
UPI
anyone
remember.
We.
B
B
B
E
B
Exactly
it
was,
it
was
now
they
use
before
they
used
to
use
M4,
and
now
they
use
m6i.
Is
that
right,
I
think
so?
Yeah.
B
G
B
G
Would
convert
them
as
is
and
add
an
appropriate
base
tag,
okay
or
maybe
also
a
disclaimer,
yes,
I
mean
as
a
as
a
citizen
of
the
internet,
I
think
it's
common
to
come
across
outdated
blog
posts,
but
you
just
need
to
have
a
look
from
when
it
is.
And
if
you
see
that
something
is
from
five
years
ago,
then
maybe
the
information
can
be
useful,
but
maybe
also
not.
D
G
B
We
did
do
a
survey
which,
actually
we
probably
at
this
point,
could
redo
the
survey.
We
did
do
a
survey
last
spring.
B
Across
the
board,
the
results
were
across
the
board.
Okay,
let
me
okay,
let's,
but
let
me
actually
that's
a
good
point.
Let
me
synthesize.
The
survey
results
that
we
have
into
a
document
I'll
create
a
ticket
for
that
who
wants
to
do
move
guides
to
blog
posts.
Anyone
want
to
at
least
take
a
stab
at
that.
Basically,
all
you
need
to
do
is
copy
the
content
into
new
pages
in
the
repo
that
holds
the
the
blog
posts.
E
I
can
do
that:
okay,
I've
posted
a
link
to
the
actual
event,
the
blog
about
the
event
and
most
of
the
owners
and
okay
as
I
are
listed
there
anyway.
B
Okay,
this
is
the
size
survey
results
from
2022.,
and
you
know
we
could
do
a
survey
every
year
right
and
have
it
be
sort
of
like
Fedora
and
and
other
projects
that
basically
like
regularly.
B
You
know,
conduct
a
survey
of
users
to
try
to
get
a
sense
of
direction
moving
forward.
We
know
that
the
biggest
thing
was
operators
right
myself
to
this.
D
B
B
Okay,
oh,
that
was
the
other
thing
is,
is
we
don't
have.
B
Like
a
process
document
for
actually
using
the
projects
in
GitHub
like
like
how
how
do
we
manage
the
board,
how
do
we
actually
Define
giving
people
access
and
whatnot
I
think
this
one's
ready?
We
just
need
to
to
sit
down
and
actually
spend
a
meeting
or
two
like
really
focused
on
this,
like
what
is
that
process
nomiko
has
contributed
to
this
discussion
before
is
like
okay.
B
What's
the
process
for
people
graduating
to
different
levels
of
participation,
so
maybe
at
the
next
meeting,
we'll
spend
some
time
on
that
one
redesigned
the
okd.io
homepage
Brian
do
we
know
if
their
name
is
escaping
me
right
now
the
person
Brendan
right
Brendan.
E
He
came
back
and
said
that
he
was
not
a
designer
he.
He
was
a
a
a
developer.
Who
can't
really
have
the
design
skills
got.
B
C
E
H
E
Very,
very
quick
Port
from
a
different
technology
which
has
meant
to
be
a
placeholder.
While
we
actually
did
the
proper
templates
and
design
in
NK
docs
yeah
and
it
sort
of
lived
there
for
like
two
and
a
half
years
now,
and
that
really
adds
the
the
the
the
the
the
bottom
section
I
mean.
We
do
have
that
just
as
a
sort
of
a
number
one.
E
G
Yeah
so,
first
personally,
I'm
I'm,
quite
fine
with
the.
If
with
the
home
page
itself
like
I,
mean
I'm
sure
if
you
want
to
improve
it,
go
ahead
but
I,
don't
necessarily
think
it's
a
it's
a
bad
like
it
looks
bad
or
anything,
I
mean
it's
very
functional
but
I.
Think
that's!
Okay
for
an
open
source
project.
E
I
think
the
the
comment
was,
it
doesn't
grab
people,
it
doesn't
sort
of
say
this
is
something
that
I'm
I'm
interested
in
or
it
doesn't
help
things
like
standout
and
that
latest
Banner
is
just
using
a
feature
that
was
already
there.
It
doesn't
really
sort
of
standouts
and
sort
of
shout
or
attention
or
anything.
E
G
B
E
F
G
E
G
C
G
B
E
Comes
back
to
our
initial
question
is:
if
someone
arrived
there
does
it
say
why
they
should
want
to
get
involved
in
this
project
or
why
they
would
want
to
use
it
what
it
is
actually
in
in
sort
of
real
terms
rather
than
buzzwords.
So
it's
all
around
this
getting
started,
bringing
people
into
the
community
it's
to
try
and
grab
them,
be
more
useful,
less
marketing,
fluff,
more
sort
of
concrete.
E
So
that's
what
all
this
was
about,
so
I
mean.
Maybe
we
should
just
roll
all
of
these
into
one
activity.
E
B
E
B
Okay,
yeah:
let's
set
up
something
at
the
next
meeting,
let's
discuss
when
we
would
want
to
do
that
because
we're
a
little
short
on
time
right
now,
but
let's
set
up
a
separate
session,
that's
going
through
the
website
and
just
saying:
okay:
this
is
something
we
should
change.
This
is
something
let's
copy
this
from
here
and
it
doesn't
have
to
be
super
detailed,
like
we
don't
have
to
actually
do
the
process
of
copying
and
pasting
and
everything
and
writing,
but
at
least
if
we
have
a
basic
set
of
bullet
points.
B
E
E
Are
we
going
to
have
a
standard
license
that
we
all
agree
to?
Do
we
want
to
make
sure
that
we
have
a
standard
layout
or
should
we
want
template
set
up
within
the
Gateway
Pro?
All
of
these
things
that
you
normally
get
by
being
part
of
an
organization,
so
that
was
that
what
that
tag
was
back
in
August
of
2022.
yeah.
B
B
E
Yeah,
this
is
governance,
because
I
think
it
also
around
that
I
think
there's
another
ticket.
That
says
we
need
a
process
for
say
who
can
who
can
approve,
pull
request
and
should
we
actually
lock
out
certain
branches
and
then
this
then
comes
into
the
operated
discussion
about
if
we
do
create
a
catalog?
How
do
we
govern
that
catalog?
Who
has
rights
to
change
it?
How
do
we
stop
somebody,
a
spurious
person
going
in
and
breaking
everybody's
okay
D
cluster,
by
putting
a
a
rogue
update
on
something,
for
example,
and
I
I?
E
All
of
that's
now
built
from
our
repos?
How
are
we
managing
that?
How
are
we
stopping
Rogue
Agents
from
being
able
to
damage
them
or,
of
course,
Havoc
yeah.
B
And
we
need
to.
We
need
both
sides
of
the
house
in
this
discussion
right
so
yep,
Christian,
Vadim
Luigi,
and
then
you
know
the
the
sort
of
Community
Development
folks
coming
to
an
understanding
of
of
how
to
process
people
who
want
to
start
participating
and
then
how
to
make
sure
that
they
have
access
to
what
they
need
and
everything
like
that.
Okay,
all.
E
B
Yeah
yeah
all
right.
Well,
we
we
made
some
Headway.
We
got
about
a
third
of
of
the
way
through
everything.
That's
that's
happening.
We've
got
some
places
to
start
any
last
minute.
Thoughts
before
I
end
the
meeting
foreign.
B
Thank
you
for
every
every
contribution.
Every
comment
was
very
helpful
to
to
get
things
going
and
I'll
see
you
all
in
two
weeks,
cool
or
next
week
for
the
technology
cheers.