►
From YouTube: [SIG Docs] Bi-Weekly Community Meeting for 20230822
Description
[SIG Docs] Bi-Weekly Community Meeting for 20230822
A
A
You
are
here
at
the
bi-weekly
secret
docs
community
meeting
big
thanks
for
everyone
who's
in
attendance
today
and
for
joining
I'm,
just
going
to
very
quickly
grab
the
agenda
and
pop
that
in
the
chat
here
for
folks
who,
who
have
yet
to
see
it,
I've
already
put
a
few
things
in
there,
but
for
folks
who,
if
you
have,
if
you
are
a
member
of
the
seed
docs
mailing
list,
you
should
be
able
to
have
access
to
our
agenda
and
thus
be
able
to
jump
in
and
edit
and
add
things
as
you
wish.
A
If
you
don't
have
that
access
you
can
join
the
Google
group
and
one
of
us,
tech
leads
or
chairs
are
happy
to
make
sure
that
you
get
that
access
ASAP.
A
With
the
with
today's
meeting,
we
are
likely
going
to
have
a
shorter
one
noted
your
your
timing,
Nate
that
you
need
to
jump
off
of,
and
so
with.
That
being
said,
I
wanted
to
welcome
everyone
and
to
let
you
all
know
that,
given
that
this
is
a
kubernetes
meeting,
we
do
abide
by
the
kubernetes
code
of
conduct.
That
does
mean
that
we
want
everyone
to
be
respectful
and
kind
to
one
another.
A
We
want
to
make
sure
that
that
is
happening
not
only
here
in
this
meeting,
but
via
slack
via
issues
and
and
GitHub
PRS,
in
any
way
that
we
work
together
and
collaborate.
We
expect
folks
to
be
kind
and
respectful.
However,
we
know
that
doesn't
always
happen,
and
so,
if
you
do
have
an
issue
that
comes
up
that
requires
code
of
conduct,
committee,
guidance
and
information
I
do
want
to.
A
Kubernetes.Io
feel
free
to
send
through
your
requests
anything
anytime,
any
email
that
you
send
there
doesn't
automatically
mean
that
you've
kind
of
filed
the
report
you're
just
reaching
out
to
the
community
to
talk
to
have
a
chat
and
get
guidance
and
we'll
go
from
there.
So
as
someone
who
has
absolutely
used
it
before,
they
are
a
great
Community
they've
just
had
some
new
members
come
on
board,
so
definitely
reach
out
to
those
folks.
A
If
you
feel
that
you
need
to
okay
with
that
being
said
again,
big
hi
to
everyone
I
want
to
check.
If
there's
anyone
new
on
the
call
today
that
would
like
to
introduce
themselves
and
to
say
hi
to
the
community.
B
Hi
I'm
not
really
new,
but
I
just
wanted
to
reintroduce
myself.
I
was
the
documentation
lead
for
1.25
the
1.25
release
and
I.
Just
am
I'm
interested
in
getting
involved
again
with
Sig
docs.
So
just
wanted
to
say
hello
again
and
I
am
looking
forward
to
working
with
everyone.
A
Amazing
welcome
back
Kristen,
it's
it's
great
to
great
to
have
you.
It's
also
I
want
to
actually
just
kind
of
point
out
if
you
don't
mind
and
highlight
the
fact
that
it's
you're
a
great
example
of
folks
who
you
know
understand
what
their
you
know.
Load
needs
to
be
and
can
kind
of
step
back
if
needed
and
then
come
back
when
you
know
that
you've
got
the
capacity
which
is
great,
really
really
healthy
way
to
kind
of
approach.
A
How
they
understand,
if
folks,
don't
want
to
on
the
on
the
call
itself,
you
can
absolutely
if
you
wish
to
jump
into
the
agenda
and
just
add
in
your
name
under
new
contributors
or
new,
with
an
asterisk
for
folks
who
are
returning
or
you
can
also
add
anything
in
the
chat
throughout
any
time,
at
the
specific,
throughout
the
specific
meeting,
as
well
all
right,
giving
folks
another
small
chance,
nope,
okay,
we're
going
to
move
on
to
the
next
part
of
our
agenda,
thanks
Kristen
great
to
great
to
have
you
back
and
what
I
would
like
to
do
now
is
just
go
through
a
couple
of
the
updates
and
reminders
that
we
have
four
Sig
docs,
that,
as
it
happens,
for
those
who
are
new
or
returning
a
need,
a
reminder.
A
You
may
know
that
in
docs
we
do
have
a
specific
program
that
we
call
PR
wrangling
and
what
that
means
is
that
every
week
we
have
one
of
our
approvers
who
is
kind
of
on
shift
to
push
our
PR
and
PR's
and
contributions
forward
to
get
that
kind
of
machine
running
in
terms
of
contributions
coming
in
and
out.
Sometimes
that
means
which
is
often
the
case
when
I'm
on
closing
a
lot
of
PRS
at
a
stale
and
just
no
one's
being
no
one's
working
on
them.
A
That's
also
part
of
that
too,
but
this
week's
PR
WR
engl
right
now,
thanks
so
much
Nate
and
we've
got
Anna
Young
on
for
next
week
and
then
the
week
after
we
have
Ray
lohano
one
of
our
other
docs
coaches
for
those
who
are
approvers
on
the
call,
please
make
sure
you
jump
in
and
look
at
the
pr
Wrangler
shift
so
that
you
know
when
yours
are
and
and
for
those
who
approvers
who
don't
have
capacity
or
you
need
a
shift
kind
of
replaced
just
reach
out
to
one
of
us
docs
chairs
as
well,
and
we
can
absolutely
help
you
with
that
too.
A
Okay,
our
agenda
is
kind
of
semi-light.
Today,
I'm
going
to
do
as
little
talking
as
I
can,
but
I
do
have
a
bit
of
an
update
around
a
release.
A
One
two
nine
for
folks
who
may
or
may
not
know
we
did
just
do
a
release
for
kubernetes
1.28
has
just
kind
of
is
just
now
recently
live
and
for
folks
who,
in
the
community
call
a
couple
weeks
back,
you
may
be,
would
have
seen
that
we
did
have
a
couple
of
interesting
challenges
in
docsum
and
quite
a
few
things
needing
to
be
merged
and
worked
on
a
little
bit
later.
And
so
we
did
have
a
red
status
update.
A
A
Some
of
those
challenges
and
I
want
to
kind
of
be
very
transparent
about
that
with
the
community
here
and
then,
hopefully,
then,
report
back
the
results
or
should
I,
say
the
discussions
and
possible
outcomes
of
that
chat
with
the
community
here
for
this,
and
so
with
in
that
vein
of
of
trying
to
generally
kind
of
just
improve
communication
and
status
and
updates
and
help
with
the
release
I've
put
in
information
about
the
upcoming
release
Here
for
everyone
to
see
so.
A
Firstly,
Shadow
applications
are
open
for
1.29,
but
anyone
in
the
community
that's
interested
in
being
a
shadow
either
in
docs
or
comms,
which
we
care
about
very,
very,
very
much
so
here
in
cdocs,
but
in
any
other
part
of
the
of
the
release
team.
It's
also
welcome,
feel
free
to
jump
in
into
you
can
see.
Xander's
Postman
seek
released,
which
I've
linked
to
in
the
in
the
agenda
and
then
I've
also
linked
to
the
issue
which
I'll
quickly
copy
and
paste
here
into
our
chat.
A
The
issue
where
a
lot
of
the
leads
are
being
nominated
as
well,
which
is
just
here
so
and
to
that
end
we
do
have
our
docs
and
comms
leads
nominated
as
well.
So
I
want
to
know,
firstly
that
Priyanka
sagu
is
the
1.29
release
team
lead
with
Xander,
whose
Sonoma
can
never
pronounce
I'm
sorry
Xander.
A
If
you're
listening
to
this
with
Xander
being
this
releases,
Emeritus
advisor
and
then
cat
Cosgrove,
who
was
a
shadow
for
1.28
docs
cat,
will
be
the
1.29
docs
lead
with
Carol
Valencia,
a
former
docs
lead
going
to
be
the
1.29
comms
lead
as
well,
and
so,
as
a
note,
you
may
be
seeing
both
cat
and
Carol
in
our
upcoming
meetings
quite
often
very
soon,
because
us
and
docs
were
going
to
request
that
those
comms
and
docs
leads
for
release
come
to
our
meetings
as
a
requirement
of
their
role
going
forward,
so
that
we
can
try
and
make
sure
that
communication
and
help
and
and
kind
of
issues
that
might
come
up
with
certain
kind
of
things
that
are
blocked
with
docs
or
comms,
that
we
can
help
resolve
them
in
this
meeting
with
the
community
together.
A
So
I
want
to
kind
of
put
that
out
there
that
those
are
names
we
are
hopefully
going
to
expect
to
then
be
here
in
the
coms
in
the
docs
meetings
going
forward
for
this
release
and
if
you've
got
any
questions
about
any
of
that
feel
free
to
reach
out
to
myself
or
Divya
already,
as
as
your
co-chairs,
but
hopefully
more
to
come
in
terms
of
what
happens
from
the
Retro
for
1.28
and
what
else
we'll
be
reporting
on
for
the
next
release.
A
Nope,
okay,
all
right
we're
going
to
move
on
then
thanks.
So
much
for
bearing
with
me
folks
and
we're
going
to
move
on
to
I
want
to
move
on
to
the
first
kind
of
issue
in
PR.
That's
been
popped
in
here.
A
I
will
do
so
specifically
copy
and
paste
here
into
the
chat
by
Tim,
who
I,
don't
think
is
on
the
call
today,
unfortunately,
but
if
anyone
does
have
an
idea
of
of
information
that
they
want
to
share
from
Tim
of
having
shared
this
or
jump
in
with
any
idea
feel
free
to
do
so.
This
is
I'm,
unfortunately
back-to-back
meetings
today,
and
this
is
the
first
I'm
seeing
of
this
specific
PR
that
Tim
has
added
in.
A
So
it
looks
like
what
we'll
need
to
do
is
further
review
and
there's
a
couple
of
discussions
here.
A
Right,
so
what
I
think
we?
What
I
believe
Tim
is
wanting,
is
the
community
to
generally
discuss
whether
this
is
something
that,
if
we
want
to
make
this
change,
given
that
the
one
two
eight
releases
out
and
we're
in
that
kind
of
Middle
Ground
period
between
releases
kind
of
beginning
with
129
now
would
be
the
time
to
jump
in
what
I
would
request.
Maybe
Nate,
given
your
this
week's
PR
Wrangler.
A
C
This
is
the
I
I
haven't
I,
haven't
read
through
this
just
yet
so
I
I'd
be
hesitant
to
give
my
thoughts
right
this
moment,
but
I
would
be
happy
to
I'd
be
happy
to
take
a
look
at
it.
I've
done
some
versioning
stuff
on
other
sites
as
well.
So
this
could
be
this.
This
could
be
in
my
in
my
wheelhouse,
so
I
will
take
a
look
at
it.
I've
subscribed
to
the
I've,
subscribed
to
the
pr
just
to
remind
myself
to
take
a
look
at
it
as
well.
So
yeah.
A
Perfect
great
so
I'm
just
going
to
pop
in
the
notes
here.
Just
so
Tim
knows
that
we've
kind
of
had
a
chat
here
that
you're
going
to
jump
in
and
have
a
look
at
that
and
give
some
more.
Let's
say,
specific
opinions
and
Views
once
you've
been
able
to
kind
of
dive
in
and
have
a
look
at
the
at
the
pr
itself,
which
is
great
thanks.
So
much.
A
I
will
write
better
notes
once
I'm
no
longer
kind
of
hosting
the
meeting,
but
just
to
just
as
a
quick
reminder
for
me
to
just
expand
on
that
in
the
in
the
notes.
There.
Okay
is
there,
given
that
that
was
the
only
issue,
slash
PR
kind
of
listed
in
today's
agenda.
Is
there
any
other
issue
or
PR
that
folks,
here
on
the
call
wanted
to
bring
up
or
address
before
we
moved
on
to
the
discussion
points
we've
got
listed.
A
Going
once
going
twice:
okay,
thanks
folks,
I
do
now
want
to
jump
over
to
the
discussion.
Points
and
I
do
know
that
Abby
has
popped
one
in
as
the
first
point
to
discuss.
Looking
for
specific
ideas
around
our
doc
Sprint
for
kubecon,
the
contributor
Summit
in
North,
America
Abby.
Take
it
away.
D
Yes,
hopefully
my
internet
holds
I'm
in
a
different
location
than
normal,
so
hopefully
I
can
get
through
this.
So
we're
looking
to
hold
a
doc
Sprint
at
the
upcoming
contributor
Summit.
So
a
doc
Sprint
will
be
an
in-person
event
where
we
all
sort
of
sit
down
and
work
on
an
issue
or
some
sort
of
task
within
the
repo.
So
it's
we're
looking
for
ideas
for
this
and
it's
an
ideal
eye.
D
An
ideal
idea
for
this
will
be
something
that
we
can
use,
have
a
lot
of
people
working
on
and
contributing
to
so
something
that
could
be
kind
of
broken
up
into
a
smaller
pieces
or
in
the
past.
We've
done
something
that
affects
a
lot
of
pages,
so
people
could
take
a
section
and
make
a
contribution
in
the
past.
I
think
we've
maybe
done
seeing
some
bug
hunts
or
your
general
issue
management
stuff.
D
So
I
just
wanted
to
first
update
the
folks
on
the
call
here
and
in
the
community
that
we
will
be
doing
a
talk
Sprint
at
the
upcoming
contributor
Summit.
So,
if
you're
able
to
attend
in
person,
please
look
out
for
that
on
the
agenda
and
then
we're
also
looking
for
ideas
of
what
things
to
do
and
work
on
where
we
can
all
get
together
in
person
and
hack
away
at
the
site.
So
let
me
know
here:
if
you
have
any
ideas
and
I'll
also
Post
in
the
in
the
flat
Channel
and.
A
A
Great
thanks,
Abby
I,
do
want
to
know
for
folks
on
the
call
Abby
actually
organized
our
last
doc
Sprint.
That
was
a
huge
success
where
we
looked
at
the
page
weights,
specifically
that
we
that
we
had
across
the
site,
which
was
really
great,
having
attended
I,
it
was
I,
was
blown
away
and
I
think
I'm
so
excited
for
Abby
to
kind
of
be.
A
You
know,
holding
the
reins
for
the
next
stock
Sprint,
so
ideas
welcome
something
that
it
doesn't
have
to
be
a
huge,
huge
mini
project,
but
something
that
a
few
folks
in
a
room
together
can
hack
on
and
work
on
together,
so
that
we
can
kind
of
solve
a
manageable.
Let's
say,
challenge,
maybe
or
like
interesting
thing,
Improvement
that
we
want
to
make
across
docs,
or
maybe
it's
only
for
a
localization
area
as
well.
That's
okay,
too
little
thing.
Every
idea.
C
A
Again
same
yes,
we
will
be.
This
will
be
in
Chicago
for
folks
who
are
unaware,
the
North
American
will
be
in
Chicago
for
2023
in
early
November,
and
so
the
doc
Sprint
is
unfortunately
still
going
to
be
something
that
is
mostly
efficient
in
person
we've
still
yet
to
kind
of
unlock.
A
How
we
can
do
something
virtually
that
that
is
successful,
but
that
could
be
something
that
is
also
worthwhile
us
kind
of
discussing
at
this
doc
Sprint
to
figure
out
how
we
can
do
something
virtual
and
a
bit
more
inclusive.
That
way:
cool
thanks,
Abby,
thanks!
So
much
for
that.
A
The
next
discussion
point
is
technically
mine,
but
I
know
Robert
is
on
the
call
too
I
wanted
to
kind
of
put
down
and
remind
everyone
to
add
thoughts
to
the
generative
AI
GitHub
discussion
that
we
have
and
Robert
if
you're,
if
you'd
like
to
kind
of
jump
in
and
just
give
folks
a
reminder
of
why
we
are
having
that
discussion
in
the
first
place.
Happy
happy
to
give
you
the
floor.
Oh.
E
Thank
you
we're
doing
it
now.
Yeah,
okay,
I
just
want
to
make
sure
Hey.
So
again,
just
a
reminder:
we
we've
in
the
past
few
weeks
we've
been
discussing.
How
can
we
use
generative
AI
to
help
us
in
documentation
in
that
discussion,
lots
of
great
ideas
and
so
to
kind
of
help
move
the
discussion
along
I
did
a
PR
talked
to
Jeffrey
and
Nate,
and
the
the
idea
was
okay.
E
Well,
let's
look
at
blog
posts
that
we
don't
have
translation
for
and
see
if
we
can
do
that,
I'm,
a
big
fan
of
doing
things
manually
before
automating,
and
so
it's
an
example
in
the
pr
and
I
will
put
that
right
here
in
the
chat
nope.
E
That's
the
other
one
hold
please
I'm.
Getting
there.
Okay
I
got
it
there.
We
go
so
what
this
a
couple
of
files,
one
of
them
that
it's
not
going
to
show
up
on
the
netlify
preview,
because
it's
the
dates
in
the
future,
but
I
went
through
and
got
a
one
in
the
past,
translated
that
using
gbt4.
This
is
manual.
Translation
had
some
challenges
around
markdown
formatting,
but
just
kind
of
a
you
know.
Just
this.
E
This
is
an
idea
right
here,
not
saying
that
this
is
the
end-all
be-all,
but
just
showing
kind
of
what
we're
thinking
from
the
LF
perspective
on
okay.
How
can
we
jump
in
and
help?
Can
we
provide
access
to
tooling
workflow
those
sorts
of
things
that
the
team
wants
to
use?
E
We're
gonna
have
a
really
tough
time,
finding
a
partner
out
there
a
vendor
to
provide
exactly
what
the
Sig
docs
is
going
to
really
want,
but
I
I
think
it's
worthwhile
to
just
try
a
little
bit
and
to
see
what
happens
see
if
there's
some
value
there
good
feedback
on
hey,
we
don't
want
to
crush
maintainers
somebody
from
the
Spanish
localization
site
of
the
house.
Chined
in
that
was
great
feedback.
Tim
came
in
examples
of
like
well.
E
This
is
how
we're
doing
it
with
other
languages
right
now
putting
in
you
know
the
English.
It
was
originally
translated
from
okay,
valuable,
but
just
wanted
to
just
put
something
out
there
to
to
look
at
fully
expect
it
to
be
shot
down,
but
just
as
an
idea
of
like
okay.
We
could
do
this
sometimes
when
you
really
want
to.
What's
that's.
What's
that
one
of
our
many
laws
on
the
internet,
if
you
want
an
answer
to
a
question,
you
got
to
post
the
wrong
answer
and
have
people
reply
with
the
correct
one.
A
So
I
think
my
first
comment:
Robert,
is
that
this
PR
is
a
surprise
to
me.
Given
our
earlier
discussions,
where
I
think
there
was
a
few
folks
who
were
very
concerned
about
using
it
using
any
generative
AI
for
translations
and
now
the
first
kind
of
let's
say
kind
of
show
PR
of
what
we
could
possibly
do
as
a
translation,
one,
so
I'm
a
little
confused
as
to
why
that
was
the
first
possible
kind
of
use
case.
A
Given
that
there
was
some
discussions
around,
is
there
a
way
to
look
at
some
low-hanging
fruit
of
small,
true
edits,
PRS
that
come
in
that
could
actually
get
flagged
by
this
kind
of
tooling.
As
yes,
this
spelling
doesn't
match
the
dictionary,
and
yet
the
one
PR
that
has
been
submitted
to
change
this
does
so
we
can
automatically
kind
of
pop
that
in
and
approve
and
whatever,
so
that.
That
is
that.
A
D
F
A
C
A
I
guess
I
guess
I
guess
my
one
question
we
that
what's
what's
the
difference
between
let's
say
that
scenario
in
this
one
now.
E
Which
you
know
when,
when
Jiffy
and
I
chatted
at
Nate,
the
three
of
us
were
chatting
absolutely
like
man.
If
we
could
just
have
this
run
through
grammarly,
you
know
and
just
tell
us
what
was
wrong
well,
the
problem
is,
is
that
grammarly
doesn't
have
an
exposed
API.
There
are
some
ways
of
tying
into
it,
and
but
they're
all
hacks
and
they're
violating
terms
of
service,
and-
and
so
this
was
the
one
like
okay,
this
seemed
doable
the
the
thing
that
you
were
laying
out.
E
B
E
That
did
that,
so
you
happy
to
take
feedback
and
just
like
no,
no,
no
use
this
service
over
there,
something
a
little
bit
more
finer
granular
detail,
I'm
like
no!
No!
This
is
the
service.
We
want
to
use.
Oh
okay,
great
yeah,
so.
A
I
think
so,
I
think
the
the
Crux
of
this,
of
what
like,
Tim
and
and
aspenish
team
are
kind
of
like
looking
at
here
is
that
you
will
load
that
something
like
this
would
create.
Where
so,
firstly,
seek.
Docs
are
also
the
whole
kubernetes
project,
but
specifically
sick
docks.
A
We
have
a
small
amount
of
reviewers
and
approvers
right
now,
I
keep
a
load
on
them,
and
so
with
that
new
PRS
that
are
coming
in
that
need
to
be
reviewed
despite
their
size,
the
just
the
amount
that
could
come
in
from
let's
say
a
process
like
this
would
create
a
lot
of
review,
alert
and
eventual
burnout,
and
so
my
Wonder
would
be.
Is
that
using
something
like
this
that
doesn't
actually
post
a
PR
but
posters
posts,
something
that
a
localization
team
can
eventually
themselves
create
as
a
PR?
B
A
It's
something
else
that
actually
doesn't
create
something
to
review
in
the
pile
of
PR
that
we're
doing
but
helps
to
help
helps
to
kind
of
accelerate
some
of
that
work,
but
still
has
a
human
being.
The
reviewer
before
a
PR
is
is
kind
of
made.
That
could
be
an
option,
but
I
feel
like
the
like.
Tim
is
suggesting
that
the
problem
of
its
scaling
is
is
is,
is
the
current
issue
right
now,
and
so,
oh
absolutely,.
E
The
last
thing
we
want
to
do
is
say:
look
we're
helping
and
doing
the
other
thing,
yeah
very
sensitive
to
that.
The
the
purpose
here
was
just
to
show
like
okay.
This
is
what
it
could
look
like
and
we're
having
the
conversation
now
on.
Oh
okay!
Well,
how
are
we
going
to
implement
and
that's
that's
kind
of
a
good
thing
where
we're
actually
kind
of
working
through
because,
previous
to
this,
this
kind
of
draft,
PR
and
and
I
do
not
expect
this
to
get
so.
E
A
A
Right
yeah
so
really
appreciate
the
work
work
on
that
I
would
say,
unfortunately
not
a
fit
for
the
work
workflow
right
now.
A
There
needs
to
definitely
no
doubt
for
sure
and
I
would
also
my
I
I
understand
the
idea
of
what
what
is
it
that
we
can
show
I
think
it
might
be
worthwhile
and
I
wonder
if,
if
you're
getting
in
the
in
the
room
with
with
with
with
Nate
with
Jiffy
with
other
folks
at
the
at
the
cncf
I
know,
Tim
pepperon
specifically,
was
also
part
of
the
discussion
and
Ray
as
well
of
folks
who
could
possibly
help
you
architect,
something
that
is
more
along
the
lines
of
let's
say
helping
out
on
the
contributor
experience
side,
where
it's
catching
small
tribute
edits.
A
That
can
kind
of
go
into
a
certain
pile
of
what
new
contributors
can
easily
review
and
jump
in
and
help
out
with
versus,
let's
say
a
larger
translation
file
than
venues
kind
of
like
piled
onto
like
a
small
amount
of
people
who
already
had
a
lot
of
work.
To
do
things
like
this
in
order
to
be
able
to
like
present
something
to
show,
as
you've
mentioned,
I'm
on
the
translation
side
of
things,
I'm
just
a
little
concerned
that
constantly
focusing
on
that
is
a
possible
solution.
A
Great
any
that
that
was
me
me
and
you
talking
about
Robert
I,
want
to
open
the
floor
and
make
sure
if
anyone
else
has
any
kind
of
suggestions
or
comments.
I
can
see
Keegan
you've
you've
jumped
in
here
I'll
I'll.
Happily
read
that
out.
If
you
like,
yeah,
go.
C
A
Okay,
cool,
so
PR
trigger
is
called
a
private
instance.
Apple
from
Siri
is
optionally
used
by
the
people,
so
syntax,
formatting,
style,
trained
and
change
could
be
a
good
Target.
I
agree,
but
Providence
is
limited
to
our
dock
scope
tune
for
syntax
in
our
requirements.
It
can
be
done
with
Azure
open
air.
That's
true!
The
challenge
is
to
get
the
data
assembled
and
the
cost
of
the
private
instance.
Another
important
note
from
lately
AI
generated
content
cannot
be
copyrighted
for
recent
court.
Really,
can
you
that
Court
ruling?
A
Can
you
tell
me
what
country
place
that's
in
because
we
are
Global
right.
A
Sure,
thank
you.
You're
right,
I
would
say.
You've
brought
up
a
really
really
good
point,
Keegan
about
cost
of
possibly
running
something
and
I.
Guess
Robert
I'd
like
to
kind
of
throw
that
to
you.
What
is
their
budget
for
us
doing
something
that
Keegan
is
suggesting
where
we
can
possibly
have
a
private
instance
that
trains
only
on
our
data,
for
example,.
E
Yes,
what
I
can
do
is
go
and
get
it
for
free,
so
I
like
that
budget.
So
what
I
can
do
is
you
know
leading
strategic
Partnerships
at
LF
when
you
know
Sig
doc
says:
oh,
we
want
to
do
this.
We
want
to
use
this.
We've
tried
it
great
and
I
can
have
a
conversation
with
Microsoft
on
donating
this.
E
A
I
think
what
we
would
need
to
do
is
pro
like
a
that
decision
is,
is
largely
not
just
up
to
docs,
probably
up
to
like
overall
k8s,
but
at
the
same
time
having
a
playground
so
that
we
can
make
a
decision.
I
think
is
actually
important
too.
So
even
something
small
that
we
could
possibly
test
the
viability
of
something
like
this
is
that
something
that
you
can
also
possibly
get
for
free
or
or
how
would
that
work.
E
Well,
who
who
approves
that
the
budget?
How
does
that
work
with
cncf
and
kubernetes,
so.
A
That
would
be
through
the
steering
committee,
I
believe
and
and
that's
something
that
we
docs
would
approach
them
to
say:
hey
we
we're
in
talks
with
with
LF
around
you
know,
possibly
using
a
generative,
Ai
and
possibly
playing
around
with
something
there.
A
At
the
same
time,
we
can't
make
decisions
about
what
we
want
to
use
or
do
without
testing
and-
and
you
know,
working
on
something
as
a
maybe
that
might
require
you
know
some
kind
of
either
funding
or
okay
on
the
budget
side,
and
we
would
take
that
to
the
steering
community.
So
I
think
we
don't
with
that.
A
We
would
need
to
kind
of
go
to
steering
together
you're
on
the
LF
side,
us
the
cdocs,
I
guess
Nate
I
would
love
for
you
to
kind
of
give
your
opinion
here
like
do
you
think
that
would
be
a
violence?
Do
you
also
think
it
would
be
viable,
as
also
someone
who's
been
kind
of
involved?
In
these
conversations.
C
Absolutely
they're
the
right
place,
you
know,
and
it's
a
matter
of
again
sort
of
showing
the
the
value
so
again
with
these
experiments
that
we're
doing
trying
things
hey.
This
is
going
to
be
something
that's
potentially
worthwhile
I
think
that's
sort
of
not.
A
Right,
I'm
just
sorry
doing
note,
taking
at
the
same
time,
because.
E
This
means
a
lot
more
when
it
comes
from
the
Sig
to
the
steering
committee.
I
I,
don't
want
the
perception
of
internal
LF
telling
other
folks
what
to
do.
So.
If,
if
this
team
decides
hey,
this
sig
wants
to
go
and
explore
something,
and
the
steering
committee
says
okay
sounds
good.
E
A
Okay,
I
think.
The
one
thing
that
I
would
want
to
kind
of
specifically
call
out
is
that
we
want
to
kind
we
we're
doing
this
from
the
basis
of
being
able
to
explore
and
make
a
decision
about
what
the
Sig
wants
with
this
tooling
and
I.
Think
I
want
to
also
highlight
in
the
discussion
that
we
do
want
to
kind
of
highlight
the
fact
that
you
know
on
the
translation
front.
C
E
Well,
is
we've
got
a
Microsoft
representative
on
the
steering
committee
right,
I'd
have
I
am
actually
so.
That
would
be
an
easy
ask.
A
So
I
would
have
to
say
it
wouldn't
because
it
they
may
not
be
the
person
in
Microsoft
to
ask
about
you,
know
getting
access
and
getting
info
well.
E
I
I
could
I
could
well
when
I
get
the
green
light,
and
you
all
want
to
you
know.
Steering
committee
says:
okay,
I
I
can
figure
out
how
to
make
it
work.
I'm.
A
Okay
sure
everyone's
sick.
C
C
Pass
at
doing
another
demo
or
how
what
what
do
we
feel
like
our
next
step,.
E
Well,
my
hope
is
to
be
honest
with
you
that
somebody
in
in
in
in
this
space,
you
know,
is
going
to
look
at
this
and
say
well
Reeves.
This
is
terrible.
This
is
the
worst
PR
I've
ever
seen.
It
needs
to
be
this
way,
and-
and
so
you
know
in
my
experience,
doing
a
thing
that
is
pretty
bad-
normally
encourages
folks
to
do
it
the
right
way
and
I'm
kind
of
hoping
that
somebody
else
would
jump
in
and
say
no.
This
is
the
way
it
should
be
done.
A
Just
to
make
sure
I'm
understanding
correctly,
you
mean
the
pr
that
you've
already
raised
with
the
translation.
Well,.
E
I'm
hoping
like,
instead
of
going
back
and
saying
well,
if
is
this
the
thing
is
this
this
the
thing
you
know
to
really
you
know
kind
of
have
some
other
folks
that
have
a
lot
more
experience
with
documentation
than
I
do
say
like
well.
No,
we
should
do
this.
Let's
try
this
is.
Is
there
it'd
be
really
cool?
If,
like
somebody
else
that
it's
just
not
me
doing
it,
because
I'm
afraid
that
we're
gonna
get
more
of
the
same,
which
is
substandard.
A
Gotcha
and
when
you
say,
and
when
you
say
doing
it,
you
mean
like
you're,
looking
from
the
community
to
have
actual
tangible
demo
or
examples
of
of
what
the
tooling
could
possibly
achieve.
For
the
sake
is
that
correct,
yeah.
E
A
I
totally
understand
and
I
think
I.
What
I
want
to
say
is
that
I
think
the
elephant
in
the
room
here
is
that
you
definitely
need
help
in
figuring
out
how
to
make
this
possible
tooling
as
successful
as
possible.
For
this
thing,
on
our
end,
we
are
so
busy
and
overwhelmed
with
the
work
we
are
already
doing
for
us
to
already
put
in
extra
for
possibly
figuring
out
how
to
use
this
tooling.
So
I
think
what
could
be
a
next
step
to
to
answer
your
question.
A
Nate
is
putting
a
call
out
in
the
discussion
to
say:
okay,
does
anyone
have
ideas,
a
of
something
that
we
could
build?
That
would
actually
be
beneficial
and
also
has
the
time
to
actually
build
something
out
and
show
that
specific
idea
out
there,
because,
unfortunately,
Robert
I
think
what
we're
running
into
is
that
yeah
there's
a
lot
of
great
momentum
and
drive,
and
you
know
interest
in
doing
this,
but
no
one
has
time
or
capacity
yeah
well
said.
Thank.
A
Yeah
so
I
think
if
we
ask
so
what
I'll
I'll
put
this
in
the
in
the
in
the
notes
in
a
moment,
but
I've
noted
your
specific
feedback,
rough
and
and
and
Keegan
in
our
in
our
Notes
too,
but
that
basically
and
Keegan
I
might
have
a
call
out.
If
you
don't
mind,
jumping
into
the
discussion
to
put
in
the
idea
of
hey
what.
If
we
had
a
private
instance,
you
know
to
be
able
to
train
the
the
llm
on
our
specific.
A
You
know,
style
guide
to
be
able
to.
You
know,
pull
up
certain
kind
of
peers
that
require
changes
that
or
something
like
this.
If
you
want
to
jump
into
the
discussion
to
put
that
there,
maybe
that
could
be
something
that
we
could
tack
on
of.
Is
anyone
interested
in
trying
to
possibly
build
something
like
this?
A
Isn't
something
that
seek
docs
can
can
go
with
at
the
moment,
okay
of
the
scale
and
the
issue,
the
scale
of
that
on
our
current
reviewer
and
reviewers
and
approvers
right
now
we
just
don't
have
enough,
but
it
doesn't
mean
that
it
can't
be
a
future
thing
that
we
look
into
once.
We
have
a
lot
more
robust
group
of
people
being
able
to
dedicate
time
and
work
valid,
yeah
cool
anyone
else
want
to
jump
in
with
ideas
or
additions
to
some
of
the
discussion
that
we've
got
going
on
now.
A
A
Up
of
that,
I
want
to.
Let
folks
know
that
the
action
item
from
this
is
that
we
want
folks
to
jump
into
the
GitHub
discussion
feel
free
to
even
tag
Robert
in
there,
if
you
wish,
so
that
he
so
that
he's
getting
the
pings
on
that
too.
Thanks
Keegan
that
you'll
add
that
as
well.
I
believe
that
the
discussion
was
linked
up
earlier,
but
I'll
just
quickly
grab
it
again
for
you.
A
A
Put
your
hand
up
in
that
discussion
and
tag
Robert,
and
that
could
be
something
that
we
could
kind
of
try
and
work
on
for
the
in
the
for
the
end
of
being
able
to
possibly
get,
maybe,
let's
say
some
kind
of
approval
on
the
steering
Community
side
to
have
a
budget
or
an
okay
to
have
some
kind
of
training
area
or
private
instance,
or
something
where
we
could
actually
work
on.
A
On
on
something,
in
a
way,
that's
that
produces
some
kind
of
results
for
us
that
we
can
see
what
tooling
could
be
made
and
useful
all
right
thanks,
Robert,
thanks
again
for
persevering
with
this
beauty
of
open
sources
of
people,
but
we
also
the
beauty
of
open
sources,
people
that
don't
have
a
lot
of
time,
so
I
I
work
at
LF
I
know.
Thank
you
great
great
thanks.
So
much
I
will
a
note
for
everyone.
A
Following
the
note
taking
in
the
agenda,
I'm
going
to
jump
in
afterwards
and
add
it
on
all
these
comments,
but
anyone
else
that
is
at
the
end
of
our
agenda.
Anyone
else
have
anything
to
add
to
this
or
any
other
topics
they'd
like
to
bring
up
today.
F
I
just
gave
a
presentation
on
using
generate
API
at
Red
Hat,
the
bottom
line.
If
I
gave
you
a
tlcr,
it
would
be
simply
AI
General
AI,
authored
content
is
not
copyrightable.
F
F
It's
a
so
it's
a
problematic
thing.
The
the!
If
you
have
no
tolerance
for
legal
risk,
then
the
the
takeaway
is
don't
use
genitive
AI
at
all.
If
you're
like
me
and
you
think
that
there's
a
middle
ground,
the
solution
is
to
author,
your
content,
use
generative
AI
to
modify
or
improve
your
content
and
then
thoroughly
revise
and
edit
it
at
the
end
and
keep
keep
notes
demonstrating
that
process.
C
Was
I
was
just
going
to
drop
and
then
that's
such
an
interesting
couple
of
points
that
I'm
going
to
be
late
for
my
next
thing,
do
we
know
the
interaction
between
Ai
and
CC
by
four,
because
I
I
don't
like,
because
because
we
yeah
we
do
have
a
copyright,
and
there
are
certain
lately,
like
things
like
marketing
or
rather
trademark
stuff,
is,
is
sort
of
managed
by
the
seats.
C
F
So
I'm
I'm,
not
a
legal
expert
but
but
when
I
was
looking
at
that
a
similar
question
in
the
red
hat
documentation,
which
is
both
copywritten
sorry
copyrighted
and
licensed
under
Apache
2.0
for
others
to
reuse,
it's
very
similar
to
CC
by
four
and
the
two
are
not
exclusive.
Basically,
the
permissive
licensing
that
you've
just
mentioned.
F
Is
you
granting
permission
to
others
to
use
your
copyrighted
content
and
that
it
granting
permission
is
an
essential
part
of
the
copyright
process?
What's
what's
not
allowed
under
copyright
is
unpermissioned
use
and
when
you
encounter
that
you
have
to
defend
your
copyright,
otherwise
you
erode
the
strength
of
your
claim
to
that
content.
F
C
Interesting,
that's
actually
we
do
have
a
couple
of
I
may
run
that
past,
just
as
a
hypothetical
sort
of,
maybe
not
so
hypothetical
but
as
an
interesting
question,
I
may
or
may
not
be
able
to
report
back
just
yet,
because
I
know
that
we
are
working
on
I
believe
we
are
working
on
a
sort
of
a
tntf
wide
opinion
on
on
AI
and
things
like
that.
C
But
we've
got
that
out
just
yet
so
I
can't
I
can't
say
this
is
the
cncf
opinion,
but
I'm
I'm
curious
to
hear
what
other
folks
have
been
hearing
and
researching
and
then
whatnot
in
this
phase.
So
thank
you
for
that.
Yeah
I
know.
I
really
do
need
to
go.
Let's
continue.
A
Great,
thank
you
thanks.
Phil
I
think
I
am
also
equally
interested
and
I.
Think
the
question
of
copyright
is
is
important
because
a
it's
in
generally
generally
important
for
the
project
across
its
different
markets
and
different
places
that
it's
accessed,
but
also
in
the
interest
of
Open
Source
to
you
know
and
and
how
we're
licensed
and
how
that
works
legally
as
well.
So
that's
super
important
thank
you
for
sharing.
Hopefully,
I've
done.
Some
of
your
points
Justice
feel
free
to
jump
into
the
agenda
later
on.
F
A
Awesome,
thank
you,
I
think
also
I've
added
in
some
of
the
links
that
yourself
and
Keegan
have
also
added
in
around
copyright.
There
too,
and
the
US
court
case
info
around
content
for
AI.
That
cannot
be
copyright,
copyrighted
and
I've.
Also
I
just
want
to
kind
of
repeat
here,
whatever
written,
which
is
basically
possible
solution,
is
we
author
content
have
ai
help
improve
it?
Humans
come
in
at
the
end
and
do
the
polishing
and
that,
as
a
process
is
documented
as
to
how
we
actually.
F
A
It
was
that
so
yeah
it
no
there's,
no
longer
a
a
separation
between
what's
copyright
and
what's
AI
right,
yes,
yeah.
F
A
A
Jump
in
and
log
when
third-party
information
and
content
is
actually
in
our
docs
too.
So
if
we
can
find
a
very
similar
way
to
describe
that
in
like
a
document
that
for
our
contributors
in
a
way
that
they
already
know
about
in
terms
of
our
third
party
content,
that
could
be
also
a
useful
way
to
help
explain
to
the
world
as
well.
F
A
Awesome
we
are
almost
at
time-
and
it's
very
it's
very
rare-
that
our
meetings
go
an
hour
long,
but
lately
they
have
been,
and
so
I
just
want
to
make
sure
that
anyone
who
wants
to
jump
in
and
give
another
comment
on.
The
specific
topic
has
the
has
the
means
to
do
so
feel
free
to
speak
up
now.
D
So
I
don't
know
if
this
would
logistically
work
and
it
might
not
fit
into
when
people
want
to
work
on
it.
But
is
this
something
that
we
could
do
with
like
a
little
hackathon
or
something
at
the
doc
Sprint
to
talk
to
have
people
work
on
some
of
these
Concepts
or
ideas
we
have
for
AI
and
how
it
could
look
in
the
in
a
within
the
community
and
for
the
docs?
D
Maybe
it's
something
to
think
about
doing
like
a
little
hackathon
or
I?
Don't
I,
don't
I,
don't
really
know
how
it
would
look
out.
Logistically
I
just
thought
that
might
be
some
dedicated
time
that
we
can
get
community
folks
together
to
talk
about
this
and
work
on
different
concepts
to
get
some
PRS
up
or
or
whatever
yeah.
A
A
A
For
sure,
because
that
way,
I
would
want
to
say
that
folks
will
then
start
thinking
about
an
idea
that
possibly
can
have
demo
quality
or
some
kind
of
realization
in
The
Conch,
in
the
constraints
of
rather
doc
Sprint
for
four
hours.
What
can
we
produce
or
show
that
this
that
how
this
talk
would
be
helpful
for
us
and
that's
a
really
good
way
for
folks
to
kind
of
really
kind
of
contextualize,
an
idea
that
could
you
know
and
and
have
a
and
have
like
a
healthy
constraint
as
well.
B
A
You
One
Last
Call
out
for
any
more
comments
on
this
topic.
A
Okay,
I'm
gonna.
Take
that
as
a
no
a
big
thank
you
to
everyone.
Who's
come
in
and
participated
today
really
grateful
for
your
ideas
and
participation
and
energy.
However,
that
form
comes
up
for
you
and
feel
free
to
for
those
of
folks
who's
who
I
was
taking
notes
on
behalf.
A
If
you
want
to
jump
into
the
agenda
and
and
some
of
those
that's
completely
okay,
a
big
call
out
just
once
again
to
jump
back
into
the
GitHub
discussion
for
further
ideas
that
you
may
have
that
you
also
maybe
have
capacity
to
possibly
work
on
and
possibly
work
on
at
the
doc
Sprint,
that's
going
to
be
happening
at
contrib
Summit.
That's
a
great
idea
out
of
coming
out
of
Abby.
That
would
be
great
Robert.
A
That
also
gives
you
a
decent
time
frame
of
do
we
we
might
have
something
to
show
by
November,
let's
say
and
and
and
so
and
so
on.
So
that
could
be
something
that
we
could
work
on
and
we
know
the
steering
Community
is
going
to
be
there
at
kubecon.
So
we
can
kind
of
get
a
lot
of
those
conversations
happening
in
parallel
I'll,
be
there
awesome?
Okay,
big
thanks.