►
From YouTube: K8s SIG Docs Localization Subproject Meeting: 2023-07-03
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Yeah:
okay:
this
thing
meeting
is
for
localization
self-productivity
thing
and
we
discuss
important
items
written
in
this
meeting
notes
and
if.
A
If
everyone
can
see
this
meeting
notes
or
view
on
any
link
for
this.
A
B
Yeah
hi,
hello,
hey
yeah,
I'm,
sorry-
and
this
is
my
first
time
in
the
talks
localization
meeting
previously
I've
been
like
I've,
been
joining
a
couple
of
the
last
sick
dogs
meetings.
A
Thank
you
Syria
in
my
pronunciation,
your
name
correctly,
yeah
that.
A
Nice
to
meet
you
and
I'm
Taco
I'm
reading
this
kubernetes
localization
soft
project
and
and
Corridor
this
sub
project.
Is
there
any
new
posts
who
Wanna
introduce
yourself?
How
about
you
Robert.
C
Oh
hi,
thank
you.
I'm
Robert,
Reeves,
I,
oversee
strategic
Partnerships
over
at
the
Linux
foundation,
and
one
of
the
things
that
we
would
like
to
help
with
is
see
if
we
can
assist
the
Sig
docs
team
with
generative
AI.
C
Are
there
tools
that
the
team
would
like
to
use
that
Linux
Foundation
can
help
procure
underwrite
support
y'all
in
the
good
work
that
you
do
so
I'm
here
to
listen
and
to
offer
assistance
to
do
what
we
do
at
Linux
foundations,
Foundation,
which
is
to
be
the
janitors
of
Open
Source.
So
just
here
to
help.
A
C
Of
course
that's
thank
you
for
having
me,
but
I
I
don't
want
to
derail
the
the
conversation
if
we
have
time
to
discuss
it
afterwards.
But
you
know
Hallmark
of
of
Open
Source
is
joining
a
meeting
expressing
your
intention
and
and
to
see
if
that's
something
you
would
like
to
help
with,
but
again
I
don't
want
to
derail
the
conversation
or
the
agenda.
A
Okay,
I
guess
other
approach
are
not
new,
so
let's
start
go
through
the
agenda.
Part
first
item
is
about
pronouncement,
which
is
me
is
now
officially
one
of
the
localization
sub-productive
lead.
As
you
know,
our
RP.
A
She
are
learning
she.
She
has
been
running.
The
software
lead,
but
I
joined,
escorted
of
this
sub
project
and
many
products
are
no
me
as
Korean
localization
team
team,
lead
and
I
contributed
to
signals
related
in
localization,
maybe
four
or
five
years
so
I'm
very
happy
to
be
to
read
my
role
that
I
can
have
other
localization
pins,
azure.
A
D
I'm
sure
so
we
recently
had
the
deprecation
of
the
catacola
tutorials,
and
what
happened
is
that
the
tutorials
got
removed
from
the
English
website,
but
cascading.
Those
changes
down
to
the
localizations
took
some
time,
I
think
about
two
months.
D
One
of
the
reasons
at
least
I
can
speak
only
for
my
localization,
but
one
of
the
reasons
why
the
Portuguese
localization
didn't
take
it
earlier
is
because
we
we
didn't.
We
weren't
really
aware
that
this
removal
will
happen
in
the
English
website.
D
D
A
Oh
thanks,
Maureen
sure
I
definitely
agree
with
you
and
in
case
of
Korean
localization,
and
we
are
so
very
struggled
with
checking
updates
the
content.
I
have
one
tip
regarding
the
song
we
have
Labor
repector
is
labor.
It
is
a
way
to
check
the
big
changes
were
major
critical
changes
in
figures
documents
for
English
document.
So
if
you
see
this
reflector
labor.
A
A
So
in
case
of
Korean
localization
team,
we
try
to
check
this
lip
picture.
They
will
be
here
when
we
update
our
content
or
contention,
but
yeah
sure
it
is
very
hard
to
check
the
outdated
content,
and
these
days
we
create
some
ombre
like
issues
to
or
to
handle
this
kind
of
situation.
A
But
it
is
very
manure
if
we
notice,
then
we
create,
but
we
don't
notice
and
we
don't
create
and
many
localization
teams
cannot
trace
and
even
worse
thing
is
some
localization
contributors
are
not
kind
of
there's
no
team
for
them
and
who
are
going
to
take
care
if
my
actual
concern
this
one.
A
So
this
discussion
may
be
related
with
how
do
we
Trace
localization,
and
whether
the
localized
contents
are
up
to
date
for
each
language
and
who
are
actually
maintaining
that
content?
It
is
a
very
critically
for
us.
A
But
step
by
step,
you
can
maybe
update
the
kind
of
document
localization
card
so
that
products
can
create
umbrella
issue
according
to
the
right
document.
And
then
maybe
we
should
find
out
a
way
to
trace
status
of
localized
content,
localization
15
and
who
are
going
to
maintain
this
one.
Not
the
or
perverse.
D
Yeah,
that
makes
a
lot
of
sense
to
me.
I
wasn't
really
aware
of
the
labor
refactor.
That's
really
good
information.
Thank
you
for
that.
I
will
take
a
look
on
this
like
how
we
can
track.
Perhaps
I
don't
know
if
it's
really
easy
to
create
an
automated
process,
but
I'll
I'll
take
a
look.
If
there
is
something
that
we
could
do,
perhaps
in
in
the
towards
like
making
some
all
the
automation
for
alerting
people,
perhaps
I,
don't
know
something
like
a
dashboard
may
be
useful.
E
Right
I
could
just
make
a
suggestion.
I
wonder
if
the
owners
file,
which
has
owners
for
specific
localization
branches,
might
be
useful
in
that
effort.
A
Hi
Robert
you
mean
we
can
trace,
I
mean
we
can
check
foreign
maintaining
of
each
particular
localization.
E
Yeah
I
I
believe
that
the
responsibility
should
rest
on
the
localization
teams
to
maintain
current
information
about
who
the
owners
are
for
the
localization
branch.
That
way,
this
information
can
be
used
to
communicate
information
to
those
groups,
critical
information
to
those
groups
either
manually
or
through
some
automated
process.
A
Sure
thank
you
and
prolonged
that
code
owners
or
operas
I.
Think
since
inside
a
purpose
list,
there
are
many
localization
of
robots
for
each
team,
so
maybe.
A
Sometimes
we
are
harder
to
find
unapproval
who
can
who
are
traits
expressing
this
updating
issues
in
case
of
Korean
localization
team?
We
are
teamed
up
and
we
have
a
World
War
II
contributors
for
keep
checking
this
kind
of
reflector
level,
as
well
as
the
tracing
outdates.
The
contents
but
I
know
most
of
localization
team
members.
Don't
have
a
kind
of
law
or
a
contributor
who
have
the
kind
of
role.
D
E
D
Mentioned
about
owners
for
localization
branches,
so
my
localization,
for
instance,
we
don't
have
a
specific
localization
branch.
D
E
Probably
this
would
be
a
good
good
follow-up
topic,
maybe
not
to
to
go
into
it
right
now,
but
I
did
misspeak
a
little
bit,
I
believe
the
the
owner's
file
or
the
approvers
might
be
keyed
off
of
the
subdirectory
in
the
localization
folder,
so
yeah
we
can.
We
can
look
at
that
a
bit
later,
if
you'd
like
parking
lot
so.
A
As
a
localization
soft
project
call
it
yeah
I
agree
with
the
roar
about
using
a
probabilist
for
maintaining
the
localizations
and
but
sometimes
those
Brokers
are
not
active
reasons.
We
frequently
remove
some
inactive
approvals
recently,
but
they
should
be
reactive,
so
maybe
to
check
the
history
status
of
localization
of
purpose.
Maybe
I
can
frequently
leave
a
message
to
them
whether
they
are
active
or
not.
Maybe
bi-monthly
for
checking
one
of
them
are
in
our
sub
project,
this
month's
limiting,
so
that
we
maybe
we
should.
A
D
Yes,
yes,
that's
good,
I'm,
also
taking
kind
of
an
action
item
for
myself
to
think
some
processes,
or
perhaps
some
automation
that
we
could
use
to
have
those
changes
surface
somehow.
D
Sorry
yeah
I
just
mentioned
that
I'm
gonna
do
some
reflection
to
see
to
think
processes
that
we
could
use
and
then
bring
those
back
to
the
group.
A
A
E
E
A
A
A
Here,
I
created
on
umbrella
issue,
to
check
out
the
Korean
content
in
one
of
our
development,
branching
Korean
localization-
and
we
say
it
is
about-
and
we
report
this
outage
the
parts.
Actually
it
is
worth
200
Parts
you'd
be
multiplied,
see
it
is
from
the
English
we
we
catch.
A
It
changes
in
English
document
like
this
and
based
on
this
reference,
we
keep
updates
or
Korean
Korean
document,
and
we
I
created
this
report
based
on
a
script
very
simple
python
script
here
this
one
and
it
is
in
our
Repository
okay,
this
kind
of
a
very
simple
term
for
localization
on
Earth.
A
Here
we
have
some
states
in
this
lipo
here
there
are
developments
escaped
for
kubernetes
documentation
and
the
scripture
that
correct
localization
use.
Is
this
one,
but
we
created
this,
it's
okay,
universally
can
be,
can
be
this
one
can
be
used
universally
to
other
localization
teams.
Input
localization
team
is
using
this
kind
of
similar
bison
sterility.
A
Like
this.
Comparing
to
this
development
branch,
we
check
English
changes
during
our
development
based
on
checking
the
two
development
branch
here,
then
this
one
generated
the
difference
and
okay.
The
document
we
need
to
update.
D
This
is
really
interesting,
I
think
I'm
I'm
gonna
talk
to
you,
the
docs
maintainers
about
maybe
having
branches
for
localization
as
well,
because
we
can
only
leverage
that
we
have
branches,
so
I'm,
I'm
gonna
take
a
look
at
this
and
see
what
we
can
do
for
the
Portuguese
localization.
Thanks
for
sharing
this,
it's
really
useful
thanks.
A
And
actually
Korean
localization
team
also
have
in
a
situation
typical
qualification
or,
as
you
see,
Korean
localization
team
localized
to
many
English
documents,
maybe
more
than
600.
A
It
covers
type
of
English
documents
and,
as
you
can
see,
whenever
we
trace
this
outdate,
the
content
there
is
listed
too
long
to
200
updates
is
not
this
one.
Maybe
one
of
that
documentation
document
totally
rewriting.
Then
we
have
to
keep
your
local
life.
We
have
to
localize
again
so
well,
we
don't
like
the
detector
label.
Actually
that
means
last
level
or
for
us
anyway.
We
had
to
we
have
to
do
this
job,
but
it
is
not
automated.
A
So
maybe
we
have
to
find
automated
way
or
data
workflow
so
that
to
to
reduce
our
effort
to
update
this
kind
of
outdated
context.
A
Young
and
let
me
put
our
reference
so
that
Lauren
and
other
folks
can
face.
A
Okay,
Maureen,
you
can
reference
this
links
and
if
you
need
any
help
any
question
then
just
let
me
know
absolutely.
D
D
A
A
A
So
this
umbrella
issue
is
about
replacing
a
short
code
in
main
branch
and
the
action
item
to
all
localization
contributors
to
update
their
localized
content
to
duplicate,
remove
those
shortcode
and
love
actually
helped
us
to
update
localization
localize
the
content
to
remove
that
kind
of
charge,
code
and
I
hope
to
check
the
status
so
like.
Could
you
share
the
status.
A
E
E
E
E
Branch
to
take
care
of
that,
and
then
we
just
move
my
second
search
first
thing:
oh
yes
and
so
I
just
have
some
changes
to
make
for
the
Japanese
branch.
I
can
take
care
of
those
later
today
and
then
I
believe
this
will
be
imposed
once
the
Indonesian
Branch
merges.
Then
I
believe
you
can
also
close
the
umbrella
issue.
A
Thanks
a
lot
for
taking
care
of
this
umbrella
issue
and
there
is
actually
really
nice
job
and
it
is
very
helpful
for
us
and
yeah
I
I
saw
we
can
update
like
we
are
going
to
update
this
one,
and
since
there
are
several
Japanese
reviewers
in
there,
and
so
when
they
world.
E
A
Here
and
yeah
I
I
see
there's
no.
A
Reaction
from
Indonesian
reviewers
here,
maybe
more
than
one
months
right
so
yeah
I'm,
going
to
watch
this
CR
and
try
to
see
status
over
Indonesian
perks,.
A
Thank
you
and
yeah.
Maybe
you
can
clear
this
issue
no
later
than
tomorrow
or
two
days
later,
right.
A
Recently,
we
removed
all
contents
related.
A
In
from
the
English
main
branch
so
all
applies,
the
content
should
be
updated
in
sense
of
the
katakoda
remover
since
at
katakoda,
if
not
active.
A
So
we
have
text
equally
and
we
have
depends
here,
but
we
still
waiting
for
progress
and
assignment
from
the
localization
post
and
several
localization
approach
already
working
on
this
issue,
but
maybe
some
of
them
are
not
responsible
or
they
are
not
notifications,
so
yeah
I,
I,
hope
to
core
all
of
localization
of
robots
based
on
code
owners.
I
mean
honor
various
as
their
life
suggests
suggested,
so
that
they
can
be
assigned
to
updating
their
each
localized
contents
for
December
relationship.
A
So
first,
if
you
are
here-
and
you
are
interested
updating
each
localized-
the
content
with
people
to
assign
yourself
to
work
on
this-
but
maybe
you
need
to
have
some
kind
of
languages
tested
understanding
for
this.
One.
A
Parents
go
to
the
next
item
and
next
item
brought
from
the
team
system
suggestion.
It
is
one
of
state
of
technically
and
hope
to
hope
to
this
hope.
This
soft
productivity
thing
discuss
following
item
and
let
me
open
decision
directly.
A
Okay,
as
we
keep
discussing
the
outdated
content
relatively
discussions
here,
actually
it
is
quite
difficult
issue
to
handle
for
all
localized
localization
teams.
So
one
suggestion
is
this:
one.
A
Providing
a
purpose
outage:
duplication
for
localized
content
so
that
folks,
in
working
on
localization,
they
can
easily
find
out
which
content
is
outdated
and
maybe
read
or
some
readers
can
report.
That
document
is
outdated
and
not
to
blame
localization
contributors.
A
So,
based
on
this,
this
suggestion
I'm
not
sure
name
of
this
support
this
contributor,
but
considered
from
Japan,
provided
a
nice
PR
of
providing
a
per
page
outdated
notification
for
localized
content,
so
this
appear
basically
check
some
differences
between
English
document
and
localized
document.
So,
if
local,
if,
when
based
on
the
timestamp
of
English
English
content,
you
can
check
when
English
version
has
been
updated,
but
if
localized
content
is
not
updated
along
with
it
timestamp,
then
this.
A
Secretes
provided
or
short
code
to
show
on
on
notification.
This
document
has
been
maybe
outdated,
so
I
guess
it
is
very
nice
suggestion
like
this
information,
this
documentation,
maybe
I'll,
take
out
of
date,
so
I
I
actually
didn't
see
the
details,
but
yeah,
surely
except
to
report
US
here
this
is
the
show
called
message.
A
A
And
this
on
employment,
the
notification
part
here
so
I
think
team
already
provides
almost
as
a
team,
so
I
guess
technically
it
is
okay
status.
A
So
yeah,
please
share
your
idea
whether
this
PR
of
September
to
you
and
you
know
if
there
is
any
enhancement
point
for
this
year.
E
If
they
make
a
a
change,
that's
unrelated,
it
will
change
the
modified
date
and
the
the
warning
will
disappear,
but
that's
there's
no
guarantee
that
the
downstream
the
localized
page
is
up
to
date
with
the
Upstream
page.
Do
you
see
what
I
mean.
A
Sure
that's
actually
nice
concern
I
I
cared
similar
way
and
yeah.
Maybe
if
we
do
this
kind
of
equally
Import
in
like
this
kind
of
alternation,
then
maybe
we
skipper
are
tended
to
believe
what
automation
suggests.
E
D
I
had
the
same
concern
and
one
thing
that
occurred
to
me
that
I
think
it
might
be
undesirable
like
for
the
brother's
sake,
but
it
would
be
a
way
of
addressing.
This
is
adding
some
information
to
the
front
matter
that
tells
which
we
could
like
some
create
some
versioning
system
of
sorts,
where
you
could
add
a
tag
to
the
front
matter
telling
that
the
documentation
is
in
a
certain
version
and
then
have
that
compared
because
that
would
be
slightly
more
reliable
than
just
comparing
dates.
A
Sure
nice
commenting
yeah,
I
I
think
for
the
first
people,
John
I
think
it
is
acceptable
for
us
but
yeah.
We
need
to
update
and
find
out
some
some
points
that
are
not
a
desired
desirable,
so
life
and
modern.
Could
you
put
your
idea
on
that
here
so
that
we
can
or
share?
We
can
share
our
ideas.
A
My
idea
in
there
and,
of
course
the
discussions
I
mean
this
kind
of
concern
has
been
related
raised
in
our
meeting,
and
you
can
put
your
ideas
and
yeah.
That's
my
suggestion.
Is
it
okay
to
you.
B
A
A
And
robot
yeah,
we,
as
you
see,
we
are
facing
some
difficulties
to
updating
and
tracing
outage
the
contents.
We
have
some
script
and
some
automations
and
also
notifications,
but
it
is
not
perfect,
so
yeah,
sometimes
some
perks
bring
some
tourists
of
Tears
for
localization
framework,
so
yeah
maybe
put
there's
some
kind
of
help
related
with
the
kind
of
tools
and
yeah.
Let
me,
let
me
call
you
to
get
some
help.
A
C
It
okay,
absolutely
what
we're
looking
for
look
last
thing:
Linux
Foundation,
wants
to
do
is
tell
developers
what
tool
to
use.
What
we're
looking
for
is
understanding
the
tooling
that
you're
using
today
and
tooling
that
you
want
to
use
in
the
future,
and
we
very
much
want
to
learn
from
Sig
docs
here.
Our
thoughts
are
if
the
kubernetes
Sig
docs
team
is
having
success
with
generative
AI.
C
Let's
one
make
sure
that
we
can
help
you
either
getting
good
discounts
underwriting
the
cost
whatever,
and
we
want
to
share
that
success
with
other
projects
in
the
foundation,
not
just
cncf,
but
openjs
CDF,
you
name
it,
and
so
we're
really
looking
at
kubernetes
sick
docs
as
the
the
lighthouse,
the
the
folks
that
are
Paving
the
path.
C
We
think
that
this
team
is
the
most
advanced
team
when
it
comes
to
tooling
and
frankly,
the
the
amount
that
you're
producing
is
far
greater
than
other
teams,
and
so,
if
you're
having
success,
we
want
to
help
you
with
that.
We
also
want
to
see
if
we
can
replicate
that
success
with
other
projects
and
other
foundations
if
this
winds
up
being
a
best
practice.
Sharing
that
with
the
other
teams,
obviously,
if
there
is
a
tool
that
you
like
to
use,
we
would
like
to
help
you
get
that
tool.
C
Get
a
very
steep
discount
and
in
return,
I
would
work
with
that
company
for
a
case
study,
those
sorts
of
things.
So
this
is,
you
know
it's
very
early
in
this
conversation,
but
what
would
help
me
is-
and
we
don't
have
to
do
this
now,
we
we
can
long
running
process,
but
help
me
understand
the
tools
that
you're
using
I
can
work
with
the
individuals
that
are
using
those
tools
to
better
understand
the
value
and
then
work
with
the
tool
provider
to
get
a
really
good
discount.
C
A
Sure,
thank
you,
and
you
know
this
meeting
is
statistic
for
the
localization
interests,
so
first
that
signals
or
think
of
the
stocks
using
our
also
a
little
bit
different.
Maybe
it's
different.
We.
A
In
single
docs,
so
foreign
has
also
regular
meetings.
So
maybe
you
do
maybe
it
is
great
if
you
participate
other
signals
meetings
so
that
you
can
coming.
A
C
Course,
of
course,
thanks
for
having
me
I
do
see
a
hand.
That's
raised
Robert.
E
Hi
I
I
work
at
Red,
Hat
I,
just
I'm
helping
to
create
a
working
group
on
exactly
this
subject.
I
also
have
a
presentation
coming
up
to
the.
D
E
Services
Group
on
using
generative
AI
in
documentation.
As
you
know,
it's
all
fast
moving.
There
are
important
considerations,
many
different
ways
of
using
the
tools,
but
I'd
be
glad
to
share
this
with
you.
Is
there
some
way
that
I
can
reach
you
or
forward
information
to.
C
You
well,
there
is
my
email,
okay,
great.
C
C
C
So
I'm
looking
to
learn,
I'm,
looking
to
understand
what
you
hope
for
what
you
would
like
to
see
and
and
I
am
here
simply
to
make
your
dreams
reality,
that
is
it
so
dude
yeah,
I
I.
You
know
I'm
relatively
new
to
Linux
foundation
and
when
the
team
was
starting
to
talk
to
me
and
say
hey,
could
you
join
Linux,
Foundation
I
said
I'm,
not
smart
enough
to
do
that.
I,
I'm,
I
I
can't
do
that.
C
I
I
know
sales,
I,
know,
marketing,
I,
know
Partnerships,
and
they
were
like
yes,
that
that's
why
we
would
like
some
help
with
so
you
know
for,
for
where
I
see
this
working
out.
You
know
Ralph,
you,
you
know
team,
you
tell
me
what
is
working.
What
you
would
like
to
explore
and
I
will
get
those
companies
froth
up
and
excited
to
work
with
you
and
bending
over
backwards
to
get
you
what
you
need.
A
Thank
you
and
right
I'm,
also
interested
in
most
of
localization
posts,
also
interested
with
your
activities.
So
for
sure,
please
share
your
link
in
or
link
to
your
activity
to
our
Channel
as
well,
maybe
to
robot
too
sure
I.
C
Mean
frankly,
the
like
I
am
a
recovering
release
manager
devops.
We
used
to
call
this
software
configuration
management,
that's
where
I
started
my
career,
so
I'm,
always
all
about
getting
the
software
out
to
where
it
can
provide
the
most
value
and
huge
fan
of
GitHub
actions.
Love
it
and
I
see
no
reason
why
we
should
not
in
sick
docks.
New
documentation
goes
up
originally
starts
out
in
English
great,
and
it
needs
to
be
localized.
C
Why
can't
we
have
GitHub
actions
that
passes
us
through
generative
AI
does
a
translation,
and
somebody
that
is
you
know,
a
native
speaker
or
an
expert
speaker
in
that
language
can
do
the
things
that
a
a
robot
cannot
do,
provide
a
human
voice
to
it.
You
know.
Maybe
there
is
a
idiom
that
does
not
translate
well.
Okay,
well,
great,
that
native
speaker,
that
expert
speaker
will
be
able
to
do
a
PR
on
that
PR
and
I.
I
really
believe
that
this
should
be.
C
You
know
the
role
of
humans
in
in
this
when
we're
talking
about
generative
AI
is
to
validate
the
change
is
to
validate
what
is
created.
You
all
will
always
need
a
human
to
make
sure
that
it
works
for
other
humans.
C
I,
don't
think
Google
has
gotten
that
yet,
but
they'll
come
around,
you
know,
but
I
think
it
it's.
You
know
there
are
things
that
we
can
do
to
help.
This
team
be
more
productive
to
avoid
burnout,
because
we
always
know
that
that
you
know
documentation
is
absolutely
necessary
and
one
of
the
last
things
we
think
of
when
we're
talking
about
projects
and
we're
hoping
at
Linux
Foundation
that
with
generative
AI,
we
can
make
this
a
tier
one
citizen.
C
A
Thanks
Robert
to
your
perio,
Clemente
and
yeah
I
actually
presented
or
talk
in
kubernetes
Community
Based
patient
in
Korea,
I
I
organized
to
this
event,
and
there
are
more
than
1
000
participants
for
this
event
and
wonderful
I
share
the
similar
either
with
you
and
how
we
Act
how
localization
contributed
I
should
act
with
AI
generation,
so
I
shared
some,
not
a
proper
version.
Translation
like
this,
and
so
someone
have
to
debut.
A
Even
though
the
content
is
from
the
AI
generative
translation.
A
Is
purely
before
that
it
was
machine
generated
documents,
yeah
I
I
also
shared
this
kind
of
talk
to
proof
in
Korea.
C
A
C
Is
I'm
very
happy
that
we're
all
thinking
about
this
and
my
hope
is
to
take
the
learnings
from
this
team?
C
Get
you
the
tooling
that
you
need
to
be
successful,
help
set
up
best
practices
and
then
use
it
as
a
positive
example
for
other
projects
in
all
of
our
disparate
foundations,
we
should
be
the
ones
Linux,
Foundation,
cncf,
openjs,
CDF,
all
the
other
foundations.
Frankly,
we
should
be
the
ones
leading
the
charge
here.
We
should
be
telling
other
companies
other
software
developers.
This
is
the
best
way.
C
I,
don't
think
we
should
listen
to
the
generative
AI
vendors
I
think
we
should
listen
to
our
developers
and
and
who
has
the
best
developers
in
the
world
so
Linux
Foundation.
So
let's
listen
to
them
and
see
what
works
and-
and
that
is
my
hope.
A
E
Thank
you.
So,
as
you
know,
there
are
machine
translation
websites
platforms
as
a
service
out
there,
but
do
a
lot
of
automation.
They
look
up
previous
translations
for
specific
string
and
they
suggest
those.
E
Many
of
those
now
are
adding
AI
to
their
portfolio,
of
course,
and,
as
you
said,
it
has
to
the
whether
it's
coming
from
machine
translation
or
AI.
They
have
a
a
system,
a
workflow
that
puts
the
suggested
changes
in
front
of
a
human
to
validate,
and
you
know
you
can
look
at
that.
E
You
can
say
yes,
this
is
good
or
no,
it
needs
to
be
changed,
and
then
you
click
a
button
and,
depending
on
how
it's
configured,
then
that
change
gets
published
or
it
goes
to
other
human
validators
for
additional
checks,
and
but
eventually
it
goes
up
in
the
translation.
E
E
C
I,
don't
think
this
is
a
pipe
dream.
I
think
we
should
work
towards
it
and
I'm
right
there
with
you.
If
we
can't
find
a
partner
that
wants
to
benefit
from
this.
You
know
this.
This
relationship,
then
we'll
do
it
on
our
own.
It's
not
like.
We
haven't
built
software
before
we
know
what
we're
doing,
and
so
you
know
if
we
can
find
a
partner,
that's
going
to
carry
the
heavy
lifting
and
they
benefit
by
making
a
profit
with
other
companies.
Great
awesome.
C
If
we
have
to
do
this
ourselves,
no
problem,
you
know
we've
built
LFX,
we
we
know
what
we're
doing,
and
so,
ideally
that
feedback
loop
would
be
by
having
public
PRS
with
requests
for
change,
suggestions
that
the
the
model
could
go
back
and
say:
oh
I,
see
that
we
got
it
wrong,
because
somebody
made
a
suggestion
on
this
PR
that
feeds
into
the
llm,
whatever
it
is,
and
okay
and
and
if,
if
another
company
doesn't
want
to
benefit
from
that,
then
we'll
we'll
build
it
ourselves.
C
C
Yeah
again,
you'll
see
me
on
the
next
one,
but
but
Ralph.
If
would
love,
you
know
any
pointers,
things
that
you're
working
on,
but
what
I'm
really
interested
in
is
understanding
a
workflow.
C
Is
there
an
individual,
that's
leveraging
AI,
maybe
they're
taking
oh
I,
need
to
update
the
stock
I'm
going
to
cut
and
paste
copy
and
paste
this
into
generative
AI
it's
going
to
translate,
I
massage
it
and
then
get
it
back
into
a
PR.
Well,
if
there's
things
that
we
can
do
using
an
API
like
I,
said
I'm
pretty
good
at
GitHub
actions,
and
so
would
love
to
do
a
PR.
If
there
is
an
example,
happy
to
carry
water
happy
to
chop
wood
alongside
you.
C
Yeah,
absolutely,
and
if
this
winds
up
being
powerful
for
LF
and
kubernetes
sick
Docs,
you
know
if
Red
Hat
wants
to
leverage
this
and
start
using
this
internally.
For
you
know,
Red
Hat
Fedora,
whatever
openstack
you
know
it.
It's
no
I'm!
Sorry,
not
openstack!.
C
Then
even
better,
you
know
if
Red
Hat
wants
to
have
this
API
if
Red
Hat
wants
to
run
with
that,
maybe
certainly
you
know,
there's
a
there
there's
a
again
another
idiom,
there's
plenty
of
chicken
on
this
phone,
so
you
know
we.
We
can
there's
a
lot
of
opportunities
to
be
successful.
We
don't
have
to
be
the
ones
in
charge
at
Linux,
Foundation
we're
more
than
happy
for
another
organization
to
take
the
lead
just
as
long
as
our
developers
benefit
and
and
whatever
it
takes
to
get
there
we'll.
E
Great,
thank
you.
Just
a
quick
note,
I
I,
believe
red
hat
is
approaching
this
very
much
the
same
way.
We
want
to
focus
on
our
core
competencies,
which
is
creating
these
Cloud
platforms.
We,
the
my
sense
from
this
is
not
official,
of
course,
but
my
sense
is
that
the
documentation
or
the
content
creation
community
doesn't
want
to
get
into
inventing
new
tools
they
want
to
use.
What's
out
there.
Yes,.
C
E
C
C
Ralph,
let's
take
this:
let's
continue
this
conversation
over
email
happy
to
chat
with
whoever
you
think
is.
You
know
it
would
be
valuable
to
at
Red
Hat,
maybe
there's
another
foundation
in
the
works.
Who
knows-
and
you
know,
multiple
hands
make
for
light
work.
Yes,.
A
Yeah
I
I
think
we
can
close
our
meeting
and
yeah
thanks
perks,
lots
of
discussions
and
resorbing
our
meeting
items,
and
maybe
it
is
the
last
call
if
you
have
any
question
or
suggestions,
and
that
needs
to
be
shared
in
this
meeting.
Please
share
now.