►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe in Amsterdam, The Netherlands from April 17-21, 2023. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
A
Well,
I'm
just
gonna
because
we're
five
minutes
in
already
just
want
to
get
started,
but
it
was
nice
to
talk
to
everyone
in
the
new
year
so
welcome
to
Welcome
to
our
glossary
meeting.
Let
me
just
share
our
very
first
off
this
year.
A
Let
me
share
on
the
screen.
Oh,
let
me
add
the
link
again
for
those
who
should
joined
later.
Add
your
names
please
and
as
usual.
As
you
know,
this
is
a
cncf
meeting.
So
please
attach
a
code
of
content
and
basically
just
be
respectful
and
kind
very
easy.
Okay,
let's
start
with
the
glossary
updates,
so
the
Portuguese
blog
will
go,
live
on
January,
12th,
very
exciting,
took
a
little
while,
but
I
think
it
turned
out
really
well
and
looking
forward
to
seeing
it
live.
A
You
may
or
may
not
have
seen
it,
but
we've
updated
tags
and
deprecated
some
definitions
there's
a
link
to
a
sheet
which
might
make
it
easier
where
you
can
see
the
whole
I,
don't
know
I
just
put
it
there
may
or
not,
may
may
or
may
not
be
easier,
and
you
will
also
see
like
updates
in
the
style
guide.
So
oh
no!
This
is
not
supposed
to
be
this
one:
oh
I
had
I,
okay,
well
anyways
and
the
style
guide.
There
is
a.
A
Let
me
just
do
this
real,
quick
in
the
style
guide.
There's
like
an
update
where
you
can
see
what
tags
we're
using
so
we're
trying
to
be
we're.
We
have
very
specific
tags,
and
here
you
see
like
how
we
use
them.
We
are
trying
to
be
to
minimize
them,
so
it's
not
like.
So
it's
it's
meaningful.
These
are
the
ones
that
we
have.
A
If
anyone
at
some
point
feels
that
there
should
be
a
new
one,
don't
just
add
a
new
one,
please
reach
out
to
maintainers
and
make
sure
that
it
is
attack
that
we
should
be
using
and
then
also
kind
of
a
little
mention
because
we
talked
about
this
before
but
like
a
little
bit
of
our
approach,
the
minimal,
viable
definition,
which
kind
of
means
helps
for
people
who
are
contributing
with
new
terms.
Basically,
we
really
are
trying
to
provide
a
high
level
overview
just
enough,
so
people
can
dig
deeper
right.
A
We
don't
want
to
over
complicate
things.
The
goal
is
really
to
make
it
accessible
to
anyone
and
the
basis
to
then
kind
of
go
on
and
learn
more
about
Cloud
native.
So
those
two
sections
are
new
and.
A
B
Yeah
I
guess
that
was
the
discussion
about
when
to
wrap
a
line.
That
was
that
one
PR
where
I
said
where
I
made
some
suggestions
to
wrap
the
longer
lines
to
smaller
ones,
and
then
the
discussion
went
off
and
yeah.
B
Yeah
yeah
yeah,
it's
it's
knocked
on,
but
I
guess
it's
just
about
what
do
we?
What
what
do
we
understand
or
what
do
we
consider
semantic
line
breaks?
B
Do
we
really
break
only
at
the
exclamation
mark
or
do
we
break
even
when
there's
no
sign
at
all,
or
what
do
we
do?
I?
Guess,
that's!
Basically
the
question
we
should
answer.
A
I
think
for
editing
purposes
because,
like
when
you
edit
the
beginning
of
a
sentence,
often
that
the
end
changes
too
right.
So
it's
like
if
things
move
around
because
it's
not
like.
Sometimes
it's
just
like.
If
it's
just
like
a
a
letter
missing
or
so
no
but
like
if
you're
editing
a
sentence,
then
it
impacts
the
entire
sentence
from
the
beginning.
Until
so,
that's
why
I
was
thinking.
I
know
that
sometimes
they're
very
long,
but
at
least
for
editing,
purposing
I,
find
it
easier
to
have
than
complete.
B
Yeah
I
guess
that's
just
a
matter
of
of
what
you
are
used
to
or
or
what
yeah
I
mean
for
me.
It's
exactly
the
other
way
around.
So
I
I
like
it
if
it's
smaller,
send
smaller
things
to
edit
but
yeah
I'm.
As
I
said
in
the
progress
time,
open
I
have
no
strong
opinion
to
it.
B
As
far
the
important
things
that
we
have
a
conclusion.
A
Yeah
I'm,
just
thinking
like
when,
when
you
do
a
suggestion
you
know
like
when
there
is
a
suggestion
and
then
like
you
can
do
the
whole
sentence,
and
otherwise
you
would
have
to
have
half
a
sentence
here
and
the
other
half
a
sentence
there
and
then
like
a
little
bit
there.
But
you
could
also
do
a
suggestion
for
the
first
part
of
the
sentence
put
the
full
sentence
there
and
then
the
other
suggestions
just
stroke
it
out
and
then
like
break
it
down
above
or
something
yeah.
B
A
Yeah,
okay,
I
think
I,
don't
know
other
than
that.
It's
pretty
much
ready
right
to
merch
and
then
for
do.
We
have
anything
specific
before
we
go
more
into
these
kind
of
things.
That
is
more
for
the
localized
team,
Soco
stuff
that
you
make
that's
more
interesting
before
we
go
more
in
maintainer,
specific
stuff.
D
There
are
many
changes
in
main
branch,
so
I
think
all
localization
branches
need.
E
D
And
there
are
duplicated
terms
and
we
apply
the
new
workflow
for
labeling
Auto
labeling,
so
those
should
be
applied
to
a
development
Branch
azure
for
localization
and,
for
instance,
if
you
you
put
localization
team,
does
not
check
the
duplicated
status
term
and
they
can
possibly
they
possibly
translate
or
localized
duplicate
or
will
remove
the
tongues.
D
It
is
used
to
this
effort,
so
I'd
like
to
recommend
to
update
or
development
branches,
so
I
think
our
localization
teams
know
how
to
replace
their
development
Branch
with
May.
D
You
can
check
the
example,
the
second
bullet
and
this
time,
I
maintained
I,
need
to
check
all
localization
teams
applied,
updated
development
Branch
according
to
the
latest
main
branch.
This
time
so
I'm
going
to
create
a
project
item
to
check,
all
branches
are
updated,
so
I
will
share
it
when
I
create
a
project
in
our
repository.
I
will
share
it
to
selectioner,
so
that
team
maintain
a
certain
join
that
project,
but
recently
Wes
updated
according
updated.
Their
development
range.
D
D
Okay,
I
guess:
there's
no
other
question
yeah
anyway.
Our
render
Henry
other
maintenance
maintainers
don't
need
to
worry
about,
and
second
one,
the
last
one.
The
last
item
is
about.
The
our
glossary
project
will
have
post
to
URL
is
directly
redirection
case.
D
D
So
maybe
we
also
face
similar
case,
so
we
need
to
have
some
policy
to
add
redirection
or
not.
So
it
is
just
ensuring.
B
Yeah,
just
just
a
comment
on
that.
The
question
is
this:
this
just
happened
because
we
renamed
the
term
right
and
also
the
file
name
and
I
I
would
I
would
think
that
this
is
not
something
that
happens
really
often
and
then
I'm
thinking
about.
Okay,
what's
the
alternative,
the
alternative
would
be
to
to
change
manually
yeah,
but
that's
not
it
that's
not
possible
to
change
everything
by
hand.
B
Now
what
I'm
thinking
about
was:
what's
the
alternative
to
to
go
in
all
places
and
and
edit
the
the
reference
but
yeah,
it's
too
too
many
places.
A
Yeah
and
also
it's
not
about
how
we
link
to
it,
it
is
this
is
a
public
resource
and
yeah.
The
goal
is
for
people
to
use
it
and
link
to
it
right
like
so.
If
we're
doing
our
job
well
and
are
successful
at
some
point,
a
lot
of
people
like
you
know
like
we'll
start,
so
we
should
never
ever
kind
of
change
a
link
without
a
redirect,
because
then
we're
breaking
links
and
yeah.
B
A
D
Also,
it
is
really
been
related
when
we
reply
when
we
duplicate
comes,
those
terms
are
also
still
have,
will
have
the
URL
link.
D
So
if
someone
keep
the
typical
URL
link
to
duplicate
the
term.
C
D
For
one
day
we
need
to
show
the
status
of
documented
document
or
which
term
so
that
duplicate
duplication
status
can
be
notified
by
other
people
who
already
LED
or
who
already
have
compared
the
previous
links.
D
So
yeah,
if
Catherine
and
Noah
said
this
case
is
not
open
often
so
maybe
we
can
discuss
it
later
once
we
place
more
complicated
to
the
situation,
but
this
time
she
already
just
sharing
the
status
is
okay
for
me
today.
Is
there
any
question
or
comments
regarding
on
this
issue.
D
Okay,
I
think
this.
There
is
none
and
okay,
guys
are
in
there's
just
two
items
that
I
listed.
That's
all.
A
Yeah
so
maybe
going
to
the
localization
teams
that
are
here
anything
any
up
to
anything
you
want
to
to
tell
us
about,
or
questions
or
whatever
I'm
just
gonna
go
around.
Edson
is
the
first
one
on
my
screen.
F
Okay,
let
me
open
here
related
to
the
labeler
workflow
Coco
that
you're
talking
about
this
is
already
working.
I,
I,
updated,
I.
Think
yesterday
the
Portuguese
Branch
so
right
now
we
do.
We
do
not
need
to
do
this
manually
right
or
we
need
to
do
something.
D
Yeah
actually
I
I
disabled
the
workflow
manually.
Currently,
so,
even
though
you
updated
your
development
branch
that
will
not
work
yet,
once
every
localization
teams
update
their
development
branch,
then
I
will
activate
the
workflow.
The
reason
why
I
disabled
the
workflow
is
that
if
any
development
Branch
does
not
have
have
some
setting
Parts
regarding
the.
D
Label
or
workflow,
then
they
they
face.
We
Face
check
failure
in
every
pH.
So
that's
the
reason.
Okay.
F
Got
it?
Thank
you
just
one
more
question:
Catherine.
There
is
a
list
with
the
deprecated
tags
and
definitions,
but
I
can
access
when
I
click
I
need
to
request
access.
F
No
Arts,
thank
you.
That's
all
I
think
for
my
from
my
side,
just
just
one
more
thing
today,
with
help
of
sioko,
we
merged
some
terms
that
was
done,
but
this
week
I
will
review
all
of
the
updates.
There
are
a
lot
of
change,
so
I
need
to
I
will
open
some
issues
for
the
Portuguese
team,
because
we
need
to
update
tags
to
check
the
deprecated
definitions
and
yeah.
So
there
are
a
lot
of
work
to
do
besides
just
localization
terms,
yeah,
that's
all.
A
Anything
from
on
your
site
that
you
would
like
to
share
or.
E
Yeah
and
thank
you
okay,
so
as
I
mentioned
actually
so,
I
also
don't
have
the
access
to
those
links
actually
so
I
try.
They
have
all
the
tags
and
other
ones
so
I
like
that,
and
also
we
had
10
terms
already
actually
local
us
or
already
done
actually,
but
right
now
we
have
almost
24
done
so
I'm,
hoping
to
actually
make
it
kind
of
upload
to
the
main
branch.
E
So
no
just
I
was
asking
the
question
because
is
there
any
other
kind
of
I
think
I
had
to
go
through?
Because
the
as
seoko
was
mentioning
about
some
changes
they
need
to
rebasing
or
something
like
that.
So
I
was
waiting
for
that.
So
that
was
my
question
or
should
I
go
for
a
revising
or
I
have
to
wait
for
some
changes
and
then
go
for
the
peer
or
I
can
create
a
PR
right
now.
D
Yeah
I
think
you're
the
better
to
replace
your
developments.
Your
teams,
people
want
to
Branch.
First,
okay,.
E
D
If
you
debase
the
development
Branch,
you
will
see
some
changes
from
English
document,
English
terms.
If
you
your
team,
already
translated
or
localized
the
English
terms,
then
you
developed
to
check
the
original
English
document
has
been
changed.
If
changed,
you
can
apply
to
those
24
times
and
then
you
you
can
open
the
new
PR
towards
your
development
Branch
to
membranes.
D
G
To
share
hi
everyone
from
Pakistan
working
on
their
viewers,
Branch
development
for
Urdu
and
I'm.
Actually,
finally,
a
student-
my
I
have
done
my
intro
last
I.
Think
last
month,
I
missed
the
glossary
meeting
last
month
due
to
illness
and
voluntable
to
attend.
So
this
is
my
intro.
Basically,
I
am
from
Pakistan
working
working
as
an
student
goal
line
developer,
also
the
Kroger
grocery
localization
approver,
so
yeah
working
on
actually
working
on
some
stuff
in
vocabulary
for
Urdu
technical
vocabulary.
G
Basically,
the
technical
vocabulary
was
missing
because
of
some
word
like
scalability
and
some
like
API
Gateway
was
missing
and
also
so.
We
are
currently
working
on
that
and
we'll
update
soon
this
month.
Also,
you
know
she
had
exams
this
month,
so
couldn't
be
able
to
work
on
more
terms,
but
we'll
we'll
be
able
to
inshallah
this
this
month
and
yeah
hope
for
good
awesome.
G
Exactly
but
but
it's
actually
our
last
semester,
so
we
are
free,
almost
free
cool
well.
A
Welcome
for
sure
and
yeah
we're
all
very
excited
to
see
the
New
Order
effort,
Giant
and
last
but
not
least,
Victor
anything
on
your
end.
H
H
I'm
still
just
going
around
and
find
what
I,
where
I
can
contribute
for
the
localization.
My
new
tips
ton
is
Mandarin
Chinese,
so
I
I'm
actually
started
to
offer
to
help
the
planning
skill
DB
there
have
a
Chinese
documentation,
I'm
helping
there,
so
I
probably
cannot
spend
I.
Probably
it
cannot
spend
that
much
time
also
probably
not
qualified
to
do
the
the
localization.
Just
so
is
there
any
like
just
random
help
him
there?
That's
I,
see
helper
there's
a
role
called
helper.
I!
A
So
you
you
are
looking
to
contribute
like
for
the
regular
glossary.
You
mean,
like
the
English.
H
Yeah,
basically
just
in
the
community,
any
any
project
or
that
needs
like
localizations
help
yeah,
so
so
some
just
like
short-term
some
user
review
or
or
translate
something
and
yeah.
So
what
what
type
of
road
is
that?
Is
there
such
a
role
in
the
community?
That's
needed.
A
Well,
for
a
localization
team,
they're
kind
of
every
team
Works
has
their
own
little
flow,
so
I'm
not
sure
if
there
is
like
anything
there
but
like
for,
like
on
the
English
glossary
I
mean
there
are
a
lot
of
issues
that
are
open
it.
Generally.
It's
like
working
on
issues
like.
H
A
On
terms
or
and
yeah
like,
if
there
are
any
questions
on
slack,
it's
always
great
to
see
the
community
kind
of
help
and
and
answer
those
as
well
but
they're,
not
to
be
honest,
I
mean
if
you
are
in
the
slack.
It's
not
like
they're
like
tons
of
questions
so.
B
Yeah
no
I
was
just
asking
myself:
where
did
you
see
this
helper
role
and
respectively?
Did
you
did
you
read
the
contributor
letter,
for
example,
or
the
I
mean
that
you
can
pretty
much
see
how
how
how
you
would
enter
the
the
different
paths?
I
mean
yeah.
So
if
you
want
to
become
a
contributor,
it's
pretty
pretty
much
stated
there.
What
what
is
expected
and
how
you
how
you
can
climb
up
the
ladder
if
you
want
so
yeah,
that's
my
comment
on
this.
H
Okay,
yeah
yeah
for
now
I'm
just
helping
a
particular
project
with
that
translation,
so
I
guess
I'll
just
keep
on
doing
that
and
that
question
is
there's
one
term
I
like
for.
Is
it
just
a
like
software
service?
I
know
the
translation
was
not
quite
right.
However,
it's
already
been
translated
a
long
time
ago,
so
it's
already
kind
of
established,
so
so
for
a
situation
like
that,
the
the
actual
translation
can
have
a
better
choice.
It's
not
that
Community!
H
It's
just
you
know
it's
totally
translate
a
long
time
ago
by
some
somewhere
else
for
a
situation
like
that.
Does
the
cncf
terminology,
that
is
there
like
a
need
to
change
that,
so
basically
the
software
as
service
translated
into
Chinese
that
actually
software
is
service.
That's
the
current
translation,
so
but
it's
already
kind
of
established
as
the
the
term
to
be
used
for
that
for
that
English
term.
So
how
long
did
I
make
that
clear?.
A
H
It
should
be
different.
The
the
current
way
to
translate
is
is
translated
before
probably
the
cnci
product
even
exists
that
that
term
can
be
can't
have
a
better
translation
so
for
citizen
station
like
that,
should
we
for
cnci
perspective,
should
we
make
Corrections?
So
it's
to.
A
A
H
I'm,
usually
as
an
example,
it's
just
it's
it
yeah
for
cncs,
that's
probably
a
new
term,
but
for
that
that
term
itself
has
been
there
for
forever
right,
so
that
was
translated
in
a
way.
That
was
not
quite.
It
means.
H
It
is
a
service,
not
you.
B
Know,
okay
and
your
question
is
if,
if
we
should,
if
we
should
Define
this
term
in
Chinese
language,
to
kind
of
correct
this
yeah.
H
A
Okay,
right
localization
is
not
translation,
so,
like
translation
would
be
literally
taking
the
words
and
then
translating
them
into
your
language.
But
if
there
is
already
a
standard
like
a
term
established
term
in
Chinese
you're,
not
gonna,
make
up,
you
shouldn't
be
making
up
a
new
term
right,
so
it
may
be
that
at
some
point
someone
didn't
know
that
established
term
and
simply
translated
it
just
because
they
weren't
familiar
with
it
and
then
yes,
we
should
definitely
keep
established
terms
because
yeah
we
don't
want
to
introduce
new
different
variations
of
it.
A
We
should
definitely
stick
to
what
the
industry
is.
Yeah
is
referring
to
that
term.
B
I
just
wanted
to
say
that
I
agree
on
that,
but
I
guess.
That
is
something
that
that
you
could
discuss
in
the
Chinese
localization
team,
so
yeah.
A
C
H
A
I
would
start
with
raising
that
discussion
there
and
say
like
yeah,
it's
just
the
actual
term.
Is
this
it's
established.
Maybe
you
can
show
some
links
where
it's
like
you
know
like
and
then
and
then
update
it.
H
Yeah
I
already
brought
it
up,
yeah
I
think
you're
right.
You
probably
should
stick
to
the
established
term.
Even
if
it's
not
the
perfect
translation.
A
A
Because
if
not
I
think
there
are
like
a
few
things
that
we
wanted
to
discuss
that
we're
more
like
within
the
men
well
kind
of
questions
that
we
as
maintainers
had
that
we're
going
to
discuss
now
may
or
may
not
be
super
relevant
to
you,
so
you're
welcomed
to
stick
around
or
just
like,
I
know
it's
late
for
some
of
you,
so
yeah
we'll
just
continue
with
that
and
yeah.
A
So,
okay,
so
we
just
discussed
the
markdown
thing
and
then
like
data
center,
so
I
just
noticed.
Why?
A
Well,
first
of
all,
like
typical
problem,
people
always
do
that
the
problem
addresses
and
people
start
talking
about
the
solution
like
we
did
it
so
many
times
and
then
I
Pro
got
it
here
to
again,
like
people
start
talking
about
the
solution,
so
we
need
to
change
that
and
then
of
course
that
was
a
little
bit
in
the
how
IT
addresses
how
how
it
helps
sorry
and
one
thing,
but
I
realized
that
it
was
very
much
focused
on
the
cloud
and
yet
clouds
are
data
centers.
A
But
what
is
the
problem
that
a
data
center
actually
addresses?
It's
not
necessarily
not
having
that
infrastructure,
because
if
you
have
your
own
infrastructure
as
a
company,
you
still
own
it,
you
still
have
the
whole.
That's
that
that's
the
benefit
of
the
cloud
right,
so
is
it
that
you
can
connect
them
into
a
distributed
system.
You
know,
like
you
have
all
of
them.
You
have.
You
can
do
like
basically
like
a
super
computer.
A
No,
no,
it's
just
data
center,
so
it
has
nothing.
It
can
be
a
cloud.
You
know
it
can
be
a
cloud
data
center
or
it
can
be
like
the
one
on
a
company
and
the
definition
itself
was
very
much
focused
on
cloud
but
like
we
have
a
definition
for
cloud
and
the
data
center
is
not
equal
Cloud.
D
Data
center
in
general,
I
think
program.
The
data
center
address
is
just
a
centralized
management
of
computing
infrastructure.
D
C
B
Yeah
I
was
asking
myself
okay.
If,
if
we
ask
the
question
okay,
what
problem
solves?
What
problem
does
the
data
center
solve,
then
I
I
would
have
to
think
of
what
has
been
before
data
centers
and
I.
Don't
have
an
answer
to
this
I
mean
it's
like
localized
computing
power
right,
everyone
works
on
his
own
machine
or
what
I.
A
A
That
then,
it
would
be
what
I
was
like
thinking
right
like
you
have
several
computers,
you
all
you
connect
them
all,
and
then
you
basically
have
a
super
like
you
have
a
much
bigger
capacity
because
they're
all
connected
instead
of
having
your
own,
you
have
a
lot
more
power.
You
can
connect
your
individual
personal
computers
so
that
like
and
then
you
suddenly
like
you-
can
do
things
that
are
much
more
powerful
right.
Yeah.
A
Because,
like
I
think
what
was
before
was
probably
like
what
like
what
the
problem
IT
addresses,
I
like
to
think
about
like
okay.
What
did
a
world
look
like
before?
There
was
that
right
and,
as
you
mentioned,
that's
pretty
old
right.
So
probably
it
was
people
with
their
personal
computers
right,
like
you,
had
like
different
stations
with
their
own
computers
that
were
not
connected,
so
the
maximum
like
yeah.
So
that's
the
maximum
you
could
do
with
was
the
power
of
that
person
that
individual
computer
and
that's
very
limited.
A
C
A
A
Okay
and
then
Microsoft
so
for
everyone
who's
else
here,
so
we're
changing
microservices
to
microservices
architecture
and
the
services
definition
will
become
like,
like
the
Microsoft
like
where
we
have
to
update
that
as
well,
and
so
I
did
send
something
in
slack
Soko.
So
it
is
microservices
architecture
which
is
kind
of
weird,
but
microservices
is
generally
kind
of
used
in
as
a
plural.
So
if
you.
A
D
C
B
A
D
A
A
And
then
the
last
thing
I
know
this
is
not
super
important,
oh,
but
didn't
don't
we
have
now
draft
is
true
that
kind
of
thing
now
I
saw
Chris
Abraham
doing
because,
like
the
feedback
appreciated
is
I,
don't
know,
I
think
that's
kind
of
odd.
It's
very
like
draft,
and
public
like
that
is
like
much
better,
but
is.
Is
there
a
way
to
kind
of
bulk
change
these
things?
A
And
the
question
is:
do
we
need
that
if
we
have
the
the
other
part,
the
new
section
when
it
says
like
draft
true
and
not
I,
don't
remember
what
that
was
about
yeah.
B
Yeah,
can
we
not
just
have
an
or
conjunction
to
say
either
feedback
appreciated
or
draft?
B
Yeah
yeah
I
meant
there's
some
there's
some
place
in
the
Hugo
thing
in
order
to
show
it
or
not,
but
it
checks
it
just
checks
checks
for
completed
right,
so
only
those
who
are
completed
are
shown
in
the
Hugo
and
the
templating
stuff.
B
A
Yeah
I
I
think
if
it
is
shown
or
not
now
is
differently.
It's
not
completed
anymore.
It
is
if
it
does
not
have
the
draft.
True
thing:
that's
a
new
thing.
Okay,
I
think.
If.
D
The
true
header,
if
the
category
of
text.
D
The
category
tag
category
count
duplicative
terms
as
well.
So
that's
the
reason
why
Chris
added
more
drip
to
True
tag
so
that
those
State
those
terms
which
she
does
not
in
competitive
status,.
A
Okay,
so
is
our
terms
published
based
on
that
draft,
not
true
not
being
true
now
and
not
the
completed
or
is
it
looking
at
both.
D
I
I
think
recently
or
or
tongues
which
she
has.
A
A
D
Yes,
we
didn't
apply
the
teleport
header
to
all
accounts.
We
only
applied
to
chapter
2
to
duplicate
our
PDP
appreciative
terms,.
D
No,
the
trip
to
here
is
used
only
for
counting
number
of
tags
for
category
okay-
okay,
yes,
hey
not
for
the
closer
return
status,
so
yeah.
Actually
it
should
be
automatically
not
specifying
both
things.
I.
A
D
D
Through
option,
if
it
was
invited
by
Chris-
but
maybe
it
is
very
initial
effort
to
quickly
remove
I-
mean
quickly
apply
the
counting
Texas
issue.
C
A
Like
it's
more
intuitive
and
terms
for
people
like
yeah,
just
one
total,
like
the
feedback,
appreciated
and
completed,
is
not
really
the
way
these
things
are
expressed.
A
Okay,
let's
see
what
he
says
and
if
he
put
it
on
his
to-do
list
that,
like
somewhere
in
the
future,
that's
fine
anything
else.
Anyone.
F
F
A
So
it's
a
little
bit
of
yeah,
so
the
glossary
started
and
people
starting
kind
of
to
to
so.
What's
it
called
contribute
terms,
and
we
didn't
have
like
a
real
process
to
evaluated
and
then
start.
We
started
getting
all
these
terms,
they're,
not
really
cloud
native
terms.
So
we
feel
very
sorry
because
that
people
put
effort
in
it.
You
put
effort
in
it,
localizing
it
right,
but
someone
input,
and
so
it
is
like
we.
A
A
Yeah
yeah
and
just
FYI,
so
we
do
have
terms
that
are
not
necessarily
Cloud
native
so
like
we
have
the
foundational
tag
and
terms
that
we
believe
are
necessary
to
understand
Cloud
native
terms
like
data
center
right.
If
you
talk
about
a
cloud,
if
someone
is
learned
that
is
kind
of
the
basis
to
understand
what
a
cloud
is,
so
those
we
do
keep
and
they
only
have
a
foundation
foundational
tag.
A
But
if
they're,
like
debugging,
for
instance,
is
like
there
is
no
need
to
know,
understand,
debugging,
to
understand
cognitive
terms,
and
it
has
nothing,
it's
nothing
specific
to
content.
So
just
for
you
to
kind
of
understand
our
logic
and
yes,
it
was
a
hard
decision
and
we
really
feel
sorry
for
you
guys
that
actually
put
all
the
effort
as
well
in
localizing
them,
but
yeah.
F
Because
I
saw
Here
For
example
managed
Services,
we
have
the
status
deprecated,
so
this
will
be
the
process
to
deprecate
to
deprecate
some
of
these
teams
right,
because
I
will
open
a
PR
to
update
the
tags
and
see
the
deprecated
terms,
so
yeah.
A
I
think
like
right
now,
I
don't
know
if
probably
I,
don't
know
how
it
will
affect
our
because
if
we
have
like
the
draft
true
or
false
and
not
status
anymore,
well,
stat
yeah,
I,
don't
know
we
have
to
figure
that
out,
but
right
now,
I
think.
If
we
put
deprecated
it's
not
going
to
show
in
the
glossary.
So
then
it's
gone
I.
F
H
D
Maybe
maintenance,
you
should
mix
status
of
Toms
property
for
our
oral
major
array.
D
Yeah
we
sometimes
we
change
status
or
terms
status
like
I
mean
like
completed
to
duplicated
or
something
else
could
be
appreciated
status.
D
But
if
that
term
already
translate
localized,
then
the
localization
team
may
not
quickly
follow
the
status
of
term
in
English
duplicated
term.
So
maybe
maintainers
need
to
find
a
way
to
make
status,
changes.
D
A
Think
something
that
we
can
do
is
like,
and
we
should
probably
do
I
mean
in
the
list
with
the
tags.
We
have
also
list
the
ones
that
are
deprecated
but
generally
kind
of
say,
like
hey,
we
deprecated
this
term
like
put
it
in
the
glossary
in
this
meeting
and
then
kind
of
have
like
a
you.
Just
just
communicate
a
bit
better.
D
Yeah
yeah
also
sometimes
are
status,
pretty
big
appreciated,
but
those
people
appreciate
we
are
maybe
contributors
harder
to
find
which
terms
are
in
feedback
appreciative
status
so
that
they
can
try
to
contribute.
So
it
is
better
related
with
other
status
information
in
public
issue.
A
Well,
I
know
that
at
some
point
a
lot
of
people
were
localizing
terms
that
were
still
feedback
appreciated.
So
that's
that's
what
you
mean
right
like
that's,
not
a
deal
because
they're
not
they're
not
regarded
as
ready.
D
A
A
Yeah
I,
don't
know
I,
don't
know
how
to
I
think
did
we
add
that
in
I
think
somewhere
and
contributor
guides
at
some
point
but
I.
A
A
Okay,
well,
let's
think
how
we
can
do
that
anything
else.
A
Okay:
okay,
good,
then
Noah,
let's
try
to
close
policies
as
code
data
center
microservices
I,
and
then
we
can
move
forward
with
the
next
things
on
the
to-do
list,
but
I
think
we
should
be
good.