►
From YouTube: GraphQL.js Working Group - 2021-01-05
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
So
we
wait
for
a
couple
minutes,
maybe
like
somebody
join
at
least
like
at
least
two
people,
yeah
martial
wars
and
rope
added
themselves.
Yeah
yeah.
One
thing
we
can
do
is
to
to
move
it
one
one
hour
late,
because
what
happened
with
this
time
is
like
a
graphical
working
group.
So
we
just
copy
paste
it
manually
do
manually,
do
time,
saving
so
come
on
now
it's
so
it's
maybe
like
confusing.
Actually
we
can
switch
to
from
utc
to
something
gym.
Gmt
anytime
works.
B
I
guess
yeah
yeah
like
like,
like
udc,
but
with
time
saving
daylight
saving.
Oh
okay,
yeah
all
the
countries,
I
think
like
most
of
the
countries
who
do
time,
saving
it
just
with
oh
hi,
rob
hi.
B
By
the
way,
do
you
do
you
want
to
discuss
something
about
streaming?
D4,
because
it's
not
an
agenda,
we
can,
you
can
add
it.
C
B
B
C
I
might
have
to
jump
off
a
little
bit
too,
so
I'm
just
gonna,
listen
in.
B
A
B
B
So,
let's
start
from
agenda
items
and
yeah
like
first
thing,
like
everybody
should
sign
specification,
membership
and
agreement
code
of
contract
and
participation
guide.
We
actually
like
graphql
foundation,
started
to
unroll
a
club
board
so
like
you
need
to
sign
it
anyway
to
contribute
your
code.
So
if
somebody
forget
it's
like
very
easy
and
you
can
sign
it
this
individual,
no,
you
don't
need
to
sign
this
company.
You
can
sign
this
into
your
contributor
yeah
and
second
thing
is
introduction
of
attendees.
B
C
B
D
Hi,
my
name
is
marcelo,
I'm
an
individual
individual
contributor
and
I
look
specific.
I
work
specifically
with
subscriptions
on
graphql.
B
The
terminal
volunteers
for
not
taken
so
if,
if
somebody
wants
to
take
notes,
actually
we
have
like
recording,
but
it
always
good
to
have
like,
because
it's
searchable
to
have
notes.
B
B
B
More
so
you
on
the
call,
because
there
is
agenda
items
about
you,
I
will
post
action
item
you
post
it
on
a
chat,
so
it
was
about
giving
you
trash
permission
rule.
So
do
you
have
it
right
now?
I
think
I
actually
added
you
to
to
graphql
js
repo.
B
Okay,
so
we
can
close
this
one
so
yeah
about
yeah.
I
need
to
work
on
some
other
one
about
cleaning
one
about
cleanup
maintenance
list
on
github.
It's
we
decided
that
should
be
handle
by
graphql
foundation.
I
forget
somebody
work
on
it
in
graphql
foundation
because
it's
like
general
issue
not
only
for
graphql
js
but
for
repositories.
B
A
B
A
Like
on
the
agenda
like,
if
you
open,
like
any
older
agenda
item
like
you,
can
see,
there's
like
a
view
calendar
or
subscribe
to
google
calendar
link
the
uh-huh
yeah.
I
see
it
yeah
like
when
you
click
that
you
subscribe
to
graphql
graphical
working
group
instead
of
graphql
js,
so
it's
kind
of
confusing
when
you
do
it
the
first
time,
so
maybe
those
should
be
fixed.
B
Okay,
so
yeah
I
will,
I
don't
know
how
to
add
like
or
if.
Even
if
I
have
access
to
graphql
foundation
calendar,
I
will
check
with
them.
So
it's
action
item.
For
me,
I
will
write
to
somebody
like
from
foundation
and
figure
out
how
to
add,
how
to
add,
graphql
js
working
group
into
calendar
and
to
have
correct
link
yeah,
and
I
think
we
also
have
the
link
the
same
link
in
readme.
A
B
B
We
target
the
same
date
so
last
wednesday
of
a
month
because
it
doesn't
interact
with
any
other
working
groups
and
it's
like
empty
sort.
B
How
how
we
end
up
with
current
time
is
that
we
copy
paste
time
from
graphql
working
group,
but
graphql
working
group
shifted
one
hour
to
adjust
for
day
day
by
saving
time.
What's
so
like
right
now,
it's
kind
of
surprising
because
it's
like
stayed
in
utc,
but
workout
time
in
all,
almost
all
countries
are
moved
to
one
hour
forward.
B
So
I
suggest
to
do
the
same
because
like
for
me,
it's
always
a
confusion
should
should
it
be
like
for
me
it's
like
6
p.m,
or
workout
time
or
7
p.m
of
workout
time,
because,
like
graphql
working
groups
is
on
seventh
year,
so
I
suggest
to
move
it
one
hour.
If
anybody
have
like
okay,
it
works.
Oh
yeah,
no.
Okay,
maybe
like
even
worth
to
look
like
some
time
zone
which
include
daylight
saving,
so
we
can
say
like
gmt
or
something.
B
So
we
can
say
it's
like
fixed
time,
but
in
time
zones
that
include
daylight
sailing,
yeah,
okay,
so
next
agenda
item
yeah,
actually
one
thing:
it
would
be
like
confusion,
because
we
would
have
two
january
2021
calls,
but
I
think
we
can
have
like
january
2021
number
one
and
number
two.
B
So
so
next
discuss
six
zero,
zero
to
two
items
yeah,
so
I
can
share
my
screen
and
we
can
yeah.
Okay,
let's
actually
look
at
the
steps
and
basically
we
I'm
I'm
like.
Currently
we
stuck
with
step
now,
even
step
number
one
to
clarify:
what's
happened
like
I
accidentally
discovered
cve
for
graphql
js,
nothing
serious
like
it's
mostly
denial
of
service
attack,
so
it's
like
just
server,
can
run
out
of
memory
and
basically
to
reboot
itself.
B
So
it's
not
like
remote
execution
or
something
I
worked
on
the
fix
and
I
have
fix,
but
I
want
to
apply
it
before
we
branch
out
so
and
that's
why
it's
like
took
some
time
and
afterwards
I
had
like
problems
on
my
main
job.
So
that's
why
it's
stuck
one
thing
I
suggest
to
to
make
it.
B
B
A
B
Let's
make
it
like
monday,
I
will
do
it
tomorrow.
Seven
fifth
is
it
is
christmas
in
ukraine
and
I
will
have
friday
and
to
like
finish
from
what
we
can.
So
we
can
put
dead
wine
for
11th
of
january.
B
B
Yeah,
so
after
that,
we
will
see
how
much
work
left,
but
basically
until
next
call,
we
should
move
to
to
number
six
and
start
working
on
number.
Seven
is
like
everybody:
okay,
with
with
dates.
A
B
Everything
else
scope
is
the
same
like
from
updates.
There
is
like
one
thing
I
want
to
fix.
It's
related
to
to
bug.
B
B
So
I
will
update
14th
and
15th
version
to
have
non-braking
fix,
like
that
fix
like
symptom,
not
a
problem
and
foxy
six
and
zero
zero.
I
will
add
to
a
proper
fix.
Rest
of
the
scope
is
the
same
and,
like
I
already
have
code
ready
both
for
1600
and
1500.
B
B
B
B
One
thing
that
we
discussed
previously-
and
I
want
to
do
it's
like
quiz
release-
include
two
kind
of
breaking
change
like
typescript
related
and
breaking
changes
not
related
to
typescript
conversion.
So
idea
is
to
at
least
try
to
put
most
of
like
non-typescript
related
stuff
into
stuff
that
we
planned
like
some
of
them.
We
plant
like
years
ago,
like
removing
deprecated
stuff,
to
put
it
into
alpha
release
and,
after
after
we
release
it,
and
I
think
I
targeted
on
it
on
monday,
so
after
we
make
this
release,
we
can
switch,
we
can
basically
match.
B
We
can
basically
merge
the
heat
pr
into
into
main
yeah.
I
I
quickly
reviewed
because
I
like
you
might
do
exchange
28
days
ago.
I
reviewed
that
like,
and
there
is
like
some
some
things.
B
I'm
some
some
like
things
that
I
want
to
change
before
merging
because
otherwise
we
will
add
like
additional,
commits
and
make
commit
history
unnecessary
big.
So
I
left
couple
comments
my
suggestion
to
improve
the
process
and
make
it
faster-
let's,
let's
agree
some
fixed
time
and
do
online
review
online
code
review
so
yeah.
So
so
we
both
will
use
like
a
zoom
or
something
here
and
and
because,
like
I
have
a
question
about
some
stuff
and
some
some
stuff,
it's
like
easier
to
to
do
in
cochairing
when
to
write
any
attacks.
B
B
Okay
yeah,
so
I
will
contact
you
yeah
yeah,
and
what
do
I
need
for
for.
B
B
B
B
We
have
code
dump
from
2015
of
16.
I
forgot
what
was
the
first
commit
and
after
was-
and
we
don't
have
like
anybody
to
ask
basically
so
idea-
is
to
at
least
preserve
like
commit
history
for
past
four
years,
because
some
of
the
changes
it's
like
very
easy
to
track
and
see
that
change
is
motivated
by
some
issue
of
pr.
B
So
anybody
who
wants
to
ask
some
something
about
that
with
like
pr
or
with
a
gender
item
or.
C
So,
just
after
16
is
released.
That's
when
we'll
do
the
17
experimental
branch.
B
I
don't
have
like
really
one
example
in
javascript
world,
but
previously
I
work
like
from
better
development,
and
I
work
with
linux
kernel
and
linux.
Kernel
previously
had
like
a
model
with
two
wines:
kind
of
experimental
wine
and
official
wine
stable
wine.
So
idea
is
to
do
the
same
because
right
now,
right
now
like
we
have
two
responsibilities:
we
have
responsibilities
for
production,
javascript
servers
and
production
servers,
yeah
not
to
break
stuff
and
not
to
to
experiment
with
the
people,
because
it's
like
stable
library
and
bunch
of
stuff
depend
on
it.
B
And
second
thing
is
responsibility
for
other
to
be
referral
supplementation.
So
if
we
add
something
we
need
people
actually
duplicate
it
so
like
python,
implementation
of
graphql
is
line-by-line
replication
of
javascript,
so
we're
not
only
experimenting
with
javascript
community.
We're
actually
experimenting
with
the
python
community
at
the
same
time.
B
B
B
B
What's
what's
agree
if
everything
goes
well
and
we
can
release
1600
this
month,
we
just
release
it
and
release
next
release
in
like
three
months.
If,
if
it's
like
take
longer,
we
just
like
squash
it
into
one
release,
because
it
doesn't
make
sense
to
do
break
and
release
and
another
breaking
release
in
like
two
months.
It's
like
too
short
period
for
breaking
for,
like
a
number
increase.
But
what's
let's
start
get
this
month
and.
B
B
Yeah,
let's
discuss
it
on
the
next
call,
when
we
will
have
actual
update
on
on
what
happened,
and
next
call
is
on
last
wednesday,
wednesday.
It's
on
27th,
so
it's
22
days
so
bunch
of
time
to
to
finish
typescript
migration.
If,
if
we
stay
on
the
schedule.
C
B
It's
yeah
it's
interesting
question,
so
we
should
not
maintain
full
time
from
migration
because
migration,
it
will
make
migration
way
way
harder
and
for
a
long
time
it's
like
a
question
should
we
add
four
types
based
on
like
premigration
code
after
migration,
so
technically
immigration
should
not
change
anything
beyond
an
actual
code
beyond
types.
So
we
should
not.
B
B
Should
we
do
that?
It's
like
a
big
question,
because
that's
why
I
think
like
mike
created
this
issue,
I
will
check,
I
think,
like
mike,
opened.
B
B
So
it's
like,
I
think
it's
a
question
of.
Is
it
worth
to
to
come
to
pay
maintenance
price?
So
one
of
the
reasons
we
actually
do,
typescript
migration
is
that
people
are
wanting
wanting
to
contribute,
but
they
four
types
is
major
pain
point,
so
they
need
to
learn
for
and
they
don't
use
for
at
work
or
they
don't
use
for
like
at
all
and
to
learn
for
specifically
to
contribute
like
one
time
per
or
one
feature
is
to
too
much
to
ask.
B
B
B
D
B
Yes,
there
is
one,
so
it
was
suggested
by
by
somebody
from
a
guild.
I
forget
his
name
cto,
for
you.
B
I
remember
so
totally
months
ago
and
problem
with
it
is
that
we
have
like
pretty
complex
four
times
most
of
them
like
90
percent.
It's
like
pretty
simple,
but
five
or
ten
percent
like
for
example,
for
visit
function
is,
is
non-trivial,
so
we
we
can
try
to
convert
like
another
question.
Is
it
worth
it
don't
know
or
not?
B
What
what
I
know
that
my
major
use
case
for
graphql
js
was
away
and
revi
right
now,
switching
to
rust
so
like
we
basically
need
to
ask
them
if
they're
switching
to
rust
anyway,
like
do
they
need,
like
four
types,
really
need
four
types
and
meantime
all
they
are
happy
to
to
stick
on
fifteen
zero.
Zero,
current
stable
line
until
like
they
switch
to
rust
so
or
maybe
like
facebook
have
other,
like
think
about,
relates
public
publicly.
B
I
think
it's
like
biggest
client
of
kraftke,
js,
apollo
and
the
way,
but
apollo
use
typescript.
They
don't
use
flow
and
biggest
like
open
source
ripples
that
use
graphqs
and
fall.
It's
it's
right
away.
I
am
aware
of
like
graphql
compose,
but
graphql
composer
spoke
with
after,
and
he
thought
that
he
don't
convert
his
own
code
into
typescript
because
he
wanted
graphqs
to
convert
first.
B
B
B
A
Finish
a
pr2863
on
graph,
ljs
cool.
I
think
we
should
get
that
merged.
Then
it's
like
it's
fixing
the
all
the
workflows,
so
it
runs.
B
Yeah
whisper
so
problem
with
it
that
we
have
branches.
We
have
like
fourteen
zero,
zero
branch
and
photon
xx,
branch
and
fifteen
xx
branch,
and
we
need
to
to
run
it.
If
I
remove
correctly,
it's
like
this
pair
from
god
right
yeah
from
goggle,
so
like
yeah,
I
need
to
yeah
because
it's
mentioned
master,
so
it's
like
well,
it's
run
testing
only
on
master
and
yeah,
but
it
will
run
on.
A
B
A
B
B
Yeah,
but
I
already
released
a
version,
so
let
me
think
about
it
so
like
ideally,
we
we
don't
need
to
restrict
it
only
with
master
like
push
only
this
master
like
let's.
I
will
keep
this
issue
open,
so
I
find
it
and
I
will
yeah
actually,
I
promise
goggle
to
figure
out
another
issue
why
linton
is
failing,
so
I
will
do
both
and
I
will
write
the
user.
B
C
B
B
Yeah,
so
yes,
we
didn't
have
a
lot
of
energetic
items,
a
lot
of
items,
but
all
them
are
major,
so,
like
basically
like
typescript
conversion
is
modulated
with
working
group.
In
the
first
place
we
would.
B
B
A
lot
of
progress
we
just
need
to
stay
on
the
schedule,
so
it
would
so
what
we
target
for
next
working
group
is
to
have
the
heat
as
a
hip.
They
are
matched
and
we
would
discuss,
like
consequence,
consequence
questions
about
like
phone
typing
and
other
things
and
by
the
way,
if
you
have
idea
for
gender
items
like
even
meta,
gender
items
are
not
only
about
like
actual
code
changes,
but
about
processes
or
about,
like
maintenance,
feel
free
to
add
them
into
agenda
for
next
next
working
group,
and
also
it's
like
open
group.
B
So
you
can
invite
other
people
to
join
us.
If
you
know
that
they're
interested
in
discussion,
especially
like
about
four
types,
if
you
know
somebody
who
who
heavily
dependent
on
graffiti
json
for
please
advise
them
to
next
next
working
group,
when
we
discuss
it
there,
yeah
yeah
other
than
that,
that
was
very
productive.
B
So
we
will
see
on
each
other
on
27th
of
january.
One
hour
later,
bye,
bye,.