►
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).
B
A
I
saw
some
teams
kind
of
made
an
update,
so
hopefully
they
will
join
as
well
later
on.
A
Cool
so
let's
get
started
so
we
have
the
tags
somehow
half
implemented,
so
we
did
something
we
wanted
to
iterate
and
then
the
issue
is
kind
of
like
stuck
in
the
pipeline,
so
I
think
the
recommendation
would
be
for
localization
steam
to
not
implement
it
yet
because
then
you
have
to
do
it
all
over
again.
So
it's
like.
I
thought
it
would
be
quick
positive,
like
okay.
A
Let's
do
this
really
quickly
and
then
and
then
do
the
other
change
so
yeah,
I'm
always
kind
of
mindful
or
try
to,
because
I
feel
bad
when
people
do
double
work
right
like
so.
I
would
maybe
just
not
touch
it,
and
also
we
wanted
to
provide
some
guidance
as
to
how
to
handle
tags
in
the
documentation,
but
we
wanted
the
updates
to
be
live
yet
because
we've
seen
that
and
some
in
two
or
three,
maybe
or
two
I
don't
know
terms
there
were
like
several
tags
and
it's
like
yeah.
A
Sometimes
you
can
add
like
lots
of
tags
because
it
fits
into
from
a
broad
perspective.
It
fits
into
their
various
things.
But
then
the
tags
are
not
useful
anymore,
because
they're
not
really
telling
you,
so
you
wanted
to
to
be
very
deliberate
and
thoughtful
about
how
we
use
them.
So
they
can
be
useful
for
the
user
when
they're,
looking
for
terms
and
understanding
how
this
fits
in
versus,
like
putting
all
lots
of
tags.
That
suddenly
just
are
lots
of
noise
and
don't
really
tell
you
anything
about
it,
because
everything
is
technology
related.
A
So
we
also
started
the
in
the
discussions.
The
we
started
a
discussion
in
github
for
how
to
handle
updates,
so
edson
already
provided
feedback.
So
basically,
there
is
no
right
approach
right
now
here
and
we
just
want
everyone
to
maybe
share
their
own
approaches
and
then
kind
of
figure
out
what
the
best
approaches
and
when
we
found
something
that
the
most
and
again
like
everyone
can
handle
it.
The
way
they
want
every
team
can
handle
it.
A
The
way
they
want
to,
but
we
wanted
to
kind
of
first
gather
some
ideas
and
have
a
conversation
there
before
we
kind
of
say
like
this
is
like
the
recommended
approach,
so
team
portuguese
has
one.
If
anyone
else
has
one,
it
would
be
great
to
share
it
here
or
comment
or
just
like
engage
in
a
conversation,
because
it
is
kind
of
oops,
not
this
one.
A
A
It's
generally,
like
people
come
to
see
the
lightning
talk,
so
it's
not
necessarily
people
that
come.
Oh.
I
want
to
hear
that
particular
talk,
so
you
have
a
much
broader
audience
right.
It's
a
much
bigger
audience.
They
come
to
see
lightning
talks.
They
come
to
see
a
lot
of
things,
so
you
are
touching
you're
getting
to
you.
You
reach
people
that
not
necessarily
pick
you
or
are
not
necessarily
you.
They
didn't
see
your
talk
or
whatever
on
the
list.
So
it's
great
for
awareness.
A
The
goal
of
the
lightning
talk
is
saying
like
this
is
the
glossary.
This
is
why
it
matters.
This
is
why
you
should
use
it
if
you
want
to
contribute.
This
is
why
you
should
contribute
we're
also
localizing
want
to
localize.
This
is
what
so,
it's
like,
really
kind
of
like
really
quick
short
explanation.
What
it
is
it's
purely
awareness,
and
so
people
know
that
it
is
there
and
that
they
can
participate
and
and
yeah
and
contribute
as
well
in
the
localized
effort.
A
The
panel
discussion
unfortunately
well,
another
first
nation
said
because
waitlisted
means
that
it
was
because
like
getting
a
talk
in
kubecon
is
very
hard
right.
There's
a
ton
like
we've
gotten
lots
of
rejections
this
year,
it's
very
very
hard,
so
waitlisted
means
that
it
was
good
enough
right
like
it
was
really
good.
It
passed
that
bar,
but
they
didn't
have
enough
spots,
so
they
do.
Sometimes
speakers
cannot
come
or
something
happens,
and
then
it
opens
up.
So
there's
still
a
chance.
A
The
panel
discussion
again
for
those
who
don't
know
it,
we
invited
several
people
from
the
localized
team.
It
was
very
localized
focused
and
then
like
why
everyone
thinks
it's
important
to
have
a
localized
version
of
the
talk
and
so
on
so
yeah.
We
wanted
that
to
be
like
an
opportunities,
particularly
for
some
of.
We
cannot
invite
everyone,
of
course,
but
some
of
the
team
leads
of
the
different
localization
efforts
to
give
them
a
chance
as
well
to
talk
to
a
bigger
audience.
A
Then
we
also
want
to
empower
you
to.
We
would
love
like
and
that's
like
if
people
are
interested,
you
know
like
what
we're.
Of
course
we
want
to
do
this
on
a
larger
scale,
for
the
glossary
in
general,
like
localization
in
general,
but
I
think,
like
we
just
started
this
effort.
Localization
the
localized
glossaries
are
still
not
complete.
It's
still
work
in
progress,
so
probably
not
a
lot
of
people
in
your
region
know
that
there
is
a
glossary
available
in
korean
in
german.
A
You
know
like
they
don't
know
that
right
so
and
they
don't
know
that
it
exists
and
they
don't
know
that
they
can
contribute
like.
So
both
things
are
important
right
like
having
them,
knowing
that
it
exists
and
using
it
and
and
contributing
is
another
thing,
but
I
think
like
getting
the
word
out
there
for
people
to
use
it
is,
is
the
first
kind
of
step,
so
we
would
love
for
you
to.
You
know:
go
talk
at
meetups,
kcds,
national
conferences.
A
Why,
like
you,
are
part
of
cncf
project?
Why
it's
important
yeah?
So
I
think
that
would
be
great
if
you
could
do
that
in
your
it's
a
little
bit
good
for
the
teams
as
well,
because
you
can
then
become
really
the
face
of
that
project
in
your
respective
regions,
and
so
we
created
the
stack
here.
Let
me
just
go
real
quick
over
it.
A
So,
basically
just
like
quick
explanation
what
it
is,
but
it
walks
you
through:
okay,
first,
like
cloud
native
definitions
in
general,
right
like,
for
instance,
right
now,
they're,
really
like
really
driven
by
vendors.
Why
it's
not
ideal
and
why
why
we
need
kind
of
a
very
easily
accessible
one.
So
this
is
like
in
general
why
we
need
cognitive
definitions
or
the
issue
with
or
the
problem
statement
with
the
current
state
without
the
clock
in
the
glossary,
then
we
talk
about
the
cloud
native
glossary
right.
A
It's
trusted
vendor
neutral
community,
driven,
that's
really
important
right
for
all
these
things,
and
people
can
keep
it
up
to
date.
Right
like
if
you
have
a
vendor
definition,
the
vendor
definition
is
going
to
be
outdated
because
it's
not
their
priority.
Very
often
it's
a
marketing
tactic.
I
know
it
because
I'm
in
marketing
so
there's
like
an
seo
the
search
engine,
optimization
you're
trying,
so
you
do
it
once
and
then
you
don't
update
it.
A
I
think
it's
really
important
right
and
then
our
goal,
then
how
people
can
help
right
they
get
the.
This
is
not
necessarily
for
the
people
who
want
to
contribute
first,
like
just
use
it.
You
know
like
when
people
are
want
to
learn
about.
B
A
Link
back
to
definition
and
so
on
and
then
help
as
well
improve
it
as
you
use
it,
and
then
we
want
to
talk
in
general
a
little
bit
about
contributing
in
general.
So
this
is.
This
is
like
from
a
lot
of
this
came
from
rael
and
victor
they've
been
talking
about
this.
They
also
did
a
cube,
can't
talk
about
contributing
to
docs
and
but
like
more
towards
geared
towards
technology
technology.
A
Coupon,
sorry-
and
so
here
are
a
lot
of
inspiration
from
there
like,
first
of
all
like
what?
How
can
you,
what
are
the
different
ways
of
contributing
right?
It's
not
just
docs!
It's
not
just
code
right
like
there
are
all
these
different
things
right
and
we're
gonna
talk
about
this
so
where
that
fits
in,
why
localization
matters?
A
This
is
like
really
important
for
localization
teams
right
and
then
why
you
should
do
it
like
how
how
you
can
kind
of
the
the
contributor
ladder
then
like
about
your
team
and
how
to
get
started?
Okay,
like
if
people
are
interested,
what
should
they
do
and
then
I
think,
like
it's
basically
kind
of
that's
like
resources
and
so
on
so
and
again
the
wrong
one.
A
So
now
I'm
always,
I
have
too
many
tabs.
So
basically-
and
I
don't
know
like-
maybe
someone
has
ideas
to
improve
it
too,
you
know
what
message
do
you
think
might
resonate
again.
We
want
to
make
sure
that
we
are
a
team
like
all
localized
people
as
well
like
work
together,
like
if
people
start
using
this
and
talking
at
conferences
and
see
something
resonates,
particularly
like
just
put
in
a
mess
like
something.
You
know,
let's
improve
the
deck,
so
everyone
can
improve
it.
A
So,
let's
make
this
not
like
something:
oh
I
use
it
and
then
I
figure
it
out
the
best
practices
and
don't
report
back
right,
like
the
idea
is
kind
of
helping
each
other
and
so
yeah.
If
anyone
is
interested,
let
us
know
I
mean
we
would
love
to
help.
You
like
you
know
like
that,
like
whatever
help
you
need,
I
don't
know
and
then
also
like.
A
If
anyone
has
any
other
ideas
about
what
we
can
do
to
get
the
word
out
specifically
and
the
countries
or
I
don't
know,
doesn't
he
I
want
to
have
an
idea?
I
know
it's.
A
very
kind
of
my
only
idea
was
like
talking
at
conferences
but,
like
I'm
sure
there
are
other
things
that
we
could
do.
C
I
I
have
a
a
question
more
organizational
one:
where
does
the
the
slides
live
so
is?
Is
there
a
folder
or
something
that
we
can
share
there.
A
C
A
Yes,
because.
A
C
I
was
thinking
of
maybe
we
can
have
one
place
where
the
template
lives
and
also
the
localized
ones,
with
their
adjustments,
maybe
so
that
we
have
on
yeah
everything
on
one
place.
D
C
And,
and
also
also,
people
have
the
the
chance
to
to
yeah
see
what
maybe,
the
other
teams
adjusted
in
their
slides,
yeah.
A
A
That's
a
good
idea,
I
think
yeah
and
probably
I
think
we
can
share
make
it
because
I
created
a
folder
promo
cloud
native
promo
or
something
I
called
it
in
that
folder.
So
we
can
probably
share
that
folder
and
maybe
link
to
it
in
the
glossary
glossary
channel.
On
top
you
know,
and
then,
if
anyone
has
ideas
as
well,
like
whatever
whatever
like.
I
think
this
is
a
team
effort
right,
like
whatever
we
can
find
to
improve
it.
E
It's
more
of
a
question,
that's
better
than
a
an
idea,
but
do
you
have
a
some
meetups
per
country?
You
a
list
of
meetups,
you
you,
you
know
we
we
already
involved.
The
cncf
is
already
involved,
I'm
not
really
a
meetup
guy.
So
it's
not
something.
I
I'm
really
used
to.
C
A
A
But
now
the
cnc
and
cncf
kind
of
moved
like
a
year
and
a
half
ago
or
something
they
moved.
So
here
we
have
canada
and
yeah
just
go
here
and
see
they're
all
cncf,
so
they
should
be
all
relevant.
A
lot
of
them
are
still
doing
stuff
virtually.
A
B
A
So
some
yeah
on
both
sides.
It
doesn't
have
to
be
a
cncf
affiliated
one.
You
know
it
could
be
a
devops
one.
It
could
be
it
doesn't
matter.
Anyone
who
is
using
cloud
native.
It's
not
we're
not
saying
it's.
Just
the
cncf
community
right
so
yeah
and
like
virtual,
is
always
easy
because
you
can
do
it
right.
So
it's
worth
checking
maybe
a
little
further.
A
I
think
most
are
kind
of
going
back
to
in
person
just
because
it's
so
much
nicer
and
people
are
sick
of
doing
stuff
virtually,
but
I
think
some
are
still
doing
virtually
so
yeah
or
maybe
the
other
thing
is
like.
Whenever
you're
have
a
trip,
a
work
trip
or
whatever
you
know,
like
keeping
that
in
mind,
you
have
to
go
travel.
I
don't
know
where
you
know
and
then
see
ahead
of
time.
If
there's
a
meet
up
there
and
then
say
like
oh,
you
know
like.
A
B
A
Yeah,
okay
and
so
the
bengali
teams
blog
is
live,
go
check
that
out
very
cool.
I
mean
it's.
I
love
working
on
them
because
I
kind
of
learned
so
much
about
the
different
languages,
specifically
the
ones
I
didn't
know
about,
and
there's
a
bengali
like
a
whole
little
story,
backstory,
which
was
interesting.
The
spanish
team
is
going
to
go,
live
on
the
19th.
Oh
I
I
do
have
the
korean
one.
A
I
haven't
looked
at
it
yet,
but
that
is
on
my
to-do
list
and
then
team
portuguese
is
tbd
and
okay.
I
think
this
is
celco
oj1.
B
B
B
But
handling
this
skill
for
new
commits
are
very
easy
for
us,
which
we
need
to
guide
to
new
contributors.
B
Sign
ups,
yet
so
folks,
who
are
managing
your
table
development
branch,
leave
aware
of
this
situation.
Maybe
we
need
to
disable
manually
that
issue
for
those
peers
to
hope
a
pair
that
wants
to
merge
how
much
in
operand
to
another
branch.
A
B
E
B
Mean
when
we
make
a
commit
using
github
gui,
it
provides
the
sign
of
option
defaultly.
So
it
is
automated,
but
people
people-
maybe
many
people-
does
not
use
wgi
when
they
make
a
new
commit.
They
need
to
provide
an
option
additional
option
to
provide
economy,
I'm
not
coming
to.
B
B
A
C
A
A
If
we
could
like
skip
it
but
the
cmc,
so
it's
it's
it's
it's
something
that
they
need
and
it's
global
so
well,
we'll
yeah
we'll
have
to
add
it
somewhere.
B
B
B
B
Yes,
so
I
think
just
one
use
is
about
french,
but
since
there
are
many
other
words
from
french,
so
I.
A
E
Yes,
so
with
the
french
localization
team,
we
made
the
initial
pier,
thank
you
circo
for
review
it
so
quickly,
so
the
pier
is
ready,
but
I
wait
for
my
two,
the
two
other
maintainers
to
review
this
one.
It's
quite
complicated
right
now,
because
one
of
them
is
in
vacation
for
like
a
long
time
and
the
other
one
is
just
doing
this
or
I
think
in
the
few
days
or
coming,
and
it
will
be
pretty
ready.
E
E
Just
one
just
one
one
question:
sorry:
we,
the
the
dev
affair
branch,
is
behind
master
branch
from
like
eight
or
ten
comments.
I
think,
should
we
rebase
this
one
before
after
after
we
merge
the
init,
the
initial
peer?
So
how
does
this
work
for
generally
for
your
for
your
team?
So
if
I.
B
B
So
if
you
you,
you
are
going
to
translate
and
localize
your
localize,
the
source,
english
document.
B
E
C
Okay,
well,
then,
I
think
I
go
next
so
team.
Germany
is
also
making
super
slow
progress,
but
the
problem
is
there,
so
we
have
six
terms
ready
that
this
one
more
than
the
last
time,
and
we
have
three
terms
in
progress.
C
So
I'm
a
little
bit
disappointed
because
I
I
made
a
linkedin
post
and
it
gained
some
attention
and
people
were
super
enthusiastic.
But
then,
unfortunately,
nothing
really
happened.
So
there
were
there
were
no
additional
contributions
from
them.
C
So
what
I
did
is
I
I
looked
to
the
kubernetes
localization
efforts
and
I
plan
to
maybe
join
join
the
kubernetes
localization
meetings
to
see
if
I
can
can
somehow
get
folks
from
there
in,
but
so
my
my
first
impression
was
that
that
I
think
also
with
the
companies
localization
team
team.
Germany
is
not
really
active
there
as
well,
but
I
will
have
to
check
that
again.
C
So
that's
that's
my
plan
yeah,
and
I
hope
that
that
there
will
be
a
little
bit
more
more
folks
joining.
A
I'm
just
thinking
that,
actually
I
know
the
linkedin
post
got
attention,
but
at
the
end
didn't
translate,
but
maybe
like
for
our
promo
kit
for
the
teams.
We
could
also
create,
like
some
social
media
post
ideas,
that
the
teams
could.
Oh.
B
A
As
inspiration
or
whatever,
and
maybe
we
could
create
also
like
little
cards,
social
media
cards
with
you
know,
yeah
something
that
people
can
so
so
people
yeah
just
to
give
them
tools.
So
I
think
that's
another
idea,
so
we
have
talks
social
media
posts
there's
another
idea.
So
if
there
are
any
other
ideas,
so
you
did
have
an
idea
in
a
while,
but
you
didn't
think
about
mentioning
it
because
because
I
think
it's
actually
a
good
idea,
it's
just
it
just
didn't
yeah,
it's
just
a
difficult
yeah.
C
Sometimes
I
I
don't
know
I
don't
know
what's
so
I
have
the
impression
that
the
german
folks
are
not
are
not
that
that
active
in
the
in
the
community.
That's
one
thing.
The
other
thing
is
that
you,
you
told
in
the
slack
channel-
and
it's
like
chat
that
maybe
all
the
german
folks
are
using
the
english
terminology,
so
they
don't
really
use
the
german
localized
ones.
I
don't
know
could
be
yeah.
A
Have
teams
international
teams
and
they
speak
even
in
germany,
they
speak
english
at
work.
So
that's
the
reality.
Is
that
that
like?
Why
would
you
people.
A
A
A
Case-
I
guess
I
don't
see
anything
for
hindi
here,
but
I
see
that
kunal
is
there,
so
I'm
just
gonna
put
him
on
the
spot.
D
Yeah
hi
everyone.
I
think
it's
been
long
that
I
have
like
attended
this
particular
meeting.
So,
to
be
honest,
like
I
wasn't
in
sync
with
the
hindi
team
for
a
while,
but
I
have
been
like
reviewing
the
chat
and
like
total
15
terms
have
been
localized
till
now
and
four
or
five
of
them
are.
You
know
we
are
working
on
that,
so
I
wasn't
in
sync
with
the
team,
so
I'm
not
able
to
like
fully
update
on
that
part.
A
I
don't
think
anyone
see
someone
from
the
italian
team.
I
don't
think
so.
Yes,
so
italian
team.
I
think
there's
also
like
a
little
summer
kind
of
hole
because
they
were
very
active
and
at
some
point
they
said,
that's
going
a
little
slower,
but
they
have
50
new
terms
and
death
branch
ready
to
merge
and
six
new
terms,
currently
in
review
and
more
coming
soon.
So
and
hopefully,
next
time
someone
can
join
this
meeting
as
well
would
be
awesome.
Korean.
B
D
B
Do
you
want
me,
okay,
let
me
introduce
korean
progress
in
case
of
korean
actually
yung
gong
yung
kong
kim,
who
is
one
of
both
of
roberts
in
korean
localization
team.
B
B
A
B
A
Okay
and
then
team
portuguese,
so
a
new
approver
reviewer
is
coming
soon
and
then
they're
working
on
a
guide
or
checklist
for
approval,
and
that's
a
really
good
idea
to
have
like
how
I
wish
like
now,
maybe
a
little
hint.
A
Maybe
they
could
do
that
in
english,
too
so
and
then
two
terms
are
ready
but
need
to
rebase
the
main
branch
first
and
blog
post
version.
One
is
done
so
I
guess
we
should
see
that
very
soon
and
if
we
have
that
like
with
korean
and
portuguese,
we
would
have
all
blog
posts
for
every
single
language
that
is
live
now.
So
so
that's
that's
cool.
A
Another
thing
that's
new.
I
forgot
to
mention,
so
we
are
finally
able
to
record
this
meeting.
So
it's
going
to
go
on
a
youtube
channel,
so
other
people
can
see
that
on
their
own
time,
specifically
with
people
in
on
the
other
side
of
the
world,
as
ko
and
jihoon
can
say,
it's
tough
to
make
it
to
the
meeting.
So
it's
good
that
we
have
that
and
whenever
team
members
also
share
their
knowledge,
it's
not
like
it's
there
and
captured,
and
people
can
see
it
later.
On
anything
else,.
A
A
No
okay,
I
think
we're
in
a
really
good
shape.
I'm
excited
to
see
localization
efforts
moving
forward
and
I
really
really
really
hope
that
we
can
do
the
little
promo
things
localized.
So
I
think
I'm
excited
about
that
and
I
I
hope
that
the
different
teams
are
excited
about
that
as
well.
To
be
able
to,
you
know,
talk
about
it
and
and
and
and
in
different
meetups
again
again,
like
please
reach
out
happy
to
help.
However,
we
can.
A
This
is
good
for
the
project,
it's
good
for
the
team,
so
if
you
have,
if
there
is
something
we
didn't
think
about,
and
also
if
you
have
other
ideas
right
like
we
have
the
talks,
we
have
social
media
posts
like
if
you
have
any
other
ideas
that
would
make
it
easy
for
people
and
we're
creating
this
promo
kit.
Basically
right,
it's
like
okay,
you
want
to
promote
it.
Here
are
the
things.
So
what
else
should
be
that
promo
kit?
Please
let
us
know
okay,
but
I
think.
F
I
had
a
quick
question
actually
that
that
brought
me
here
today.
The
landscape
graph
project
has
been
kind
of
quietly
bubbling
along
in
a
good
way.
F
Over
the
last
month,
a
month
and
a
half,
some
things
took
a
little
longer,
but
we've
consolidated
down
to
a
serious
design
that
is
scalable
and
and
have
started
documenting
some
things
and
have
figured
out
how
to
do
graph
composition
right
so
different
domain
experts
from
different
tags
and
different
groups
can
contribute
in
a
way
that
they
don't
collide,
and
then
we
can
have
ci
and
cd.
F
So
one
of
my
questions
about
the
tags
that
are
being
defined,
not
technical
advisory
groups,
but
the
attributes
that
are
part
of
the
glossary
are
those
localized
like
I'm
to
the
point
where
I
can
start
to
bring
in
categories
and
tags
in
this
new
well-formed
model
that
uses
graphql
as
an
interface
definition,
language
and
a
way
to
standardize
on
something
that
is
an
actual
standard
graphql
as
being
the
api
surface
in
and
out
of
the
graph,
and
so
now
I'm
starting
to
actually
do
some
specific
data,
modeling
and
so
yeah.
F
B
Has
implemented
things
right?
Yes,
currently
we
implemented
the
text
but
not
fully
implemented.
So
we
didn't
guide
each
localization
teams
to
add
I
mean
their
own
tags
or
localized
eggs
yet,
but
some
of
some
teams
are
working
on
translating
and
localizing
tech
itself,
so
some
some
localization
teams
have,
for
instance,
a
korean
localization
team
also
try
to
translate
text,
but
currently
it
is
in
their
our
own
development
branch.
B
F
Okay,
cool.
Well
then
I
will.
I
will
plan
accordingly
so
that
I
can
accept
localized
tags.
Do
you
know,
and
I
I
was
planning
to
implement
it
such
that
you
know
whatever
is
there
will
bring
in?
But
if
some
languages,
if
some,
if
some
tags
don't
have
translations
or
localization
in
some
languages,
that's
okay!
I
won't
make
it
break
if
they're
not
there,
but
if
they
are
there,
I
can
display
them
and
I
assume
we're
using
you
know
unicode
and
all
of
that,
so
it
should
be.
F
Should
it
should
just
work
but
it'll
be
the
first
kind
of
actual
localization
testing
or
or
non
yeah.
So
I
might
find
out
that
somewhere
along
the
linkage
in
the
data
model,
you
know
we're
not
correctly
handling,
internationalized
or
localized
strings,
but
I'm
pretty
sure
everything
is
full
unicode
throughout.
So
it
should
be
fine.
B
Okay,
I
I
think
if
we
have
some
mature
localized
text-
and
I
will
share
it
through
a
link
so
that
you
can
check
the
localized
text
but
not
not
very
many
tags,
we
in
case
of
a
glossary
project,
glossary
repository,
we
don't,
we
didn't
define
not
too
many.
I
mean
pure
pure
text.
Actually,
maybe
we
have
six
take
seven
takes
currently
not
too
many.
So
please.
A
F
No,
that's
that's
perfect.
I
just
want
to
make
sure
I
was
correctly
set.
A
What
we
like
the
way
we
envision
it
in
the
english
version
either
so
we're
kind
of
actually
asking
or
like
recommending
not
to
work
on
the
text
for
now
until
that
is
implemented.
So
there's
no
double
work,
so
it
is
a
little
bit
on
hold,
but
I
know
that
your
person.
F
F
So
I'll
have
to
watch
the
recording
when
it
posts
I
put
in
the
chat
sort
of
the
current
state
of
the
graph
with
the
graphql
stuff.
I
mentioned
that's
more
of
a
just
a
bunch
of
links,
but
it's
sort
of
a
summary
of
the
various
pieces
of
technology
that
we're
bringing
to
bear
in
the
actual
implementation
of
the
graph.
So.
A
A
And
see
you
hopefully
all
next
month.