►
From YouTube: GraphQL Working Group (Secondary, APAC) - 2022-11-09
Description
GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools. Get Started Here: https://graphql.org/
D
D
Cool
I
guess
we'll
get
started
in
a
minute
or
two.
C
B
Yeah
we
have
a
person
on
the
team
who
his
pandemic
hobby
was
balloon
twisting
and
he
got
to
like
Pro
level
at
it.
B
B
He's
the
favorite
dad
at
every
birthday
party
and
he
can
do
distances
and
really
elaborate
ones.
So
I
I
challenged
him
to
make
the
girl
okay,
I.
B
We
had
a
team
catch
up
and
the
surprise
at
the
end
was
he
taught
us
all
how
to
make
balloon.
Animals
yeah
amazing.
D
That's
awesome:
now
you
can
make
your
own
graphql,
bullying,
art,
exactly
love,
it
all
right,
crew
ready
to
get
started!
Yeah,
Benji,
I,
don't
see
you
in
the
agenda
file
yet
but
I
assume
you're
fixing
that
I'll.
D
Cool
well,
as
per
usual
bias
all
showing
up.
We
agree
to
spec
membership
agreement
participation,
guidelines
contribution
guides
code
of
conduct,
a
bunch
of
links
out
to
all
the
docs
there.
If
you
ever
feel
like
some
good
evening
readings,
but
otherwise
I
think
it'd
be
helpful
to
go
around
just
do
a
quick
set
of
intros,
even
though
we
got
a
tight
group
and
I'll
go
in
alphabetical
order,
with
the
exception
myself
since
I'm
already
talking
get
myself
out
of
the
way
so
hello
everybody,
my
name
is
Lee.
B
Hey
everyone,
I'm
Donna,
I
work
with
Andy
at
atlassian
as
well,
and
I
also
help
out
with
graphql
Java.
Do.
B
A
Hey
I'm
Philip
as
last
time,
I'll
I'll,
just
listen
in
I
work
on
the
caucus
team
at
Reddit
and
I've
built
the
cut
off,
kill
integration,
that's
built
on
top
of
Andy's
awesome,
graphql
travel.
C
C
D
There
was
a
Tech
conference
that
I
ended
up
not
getting
to
do
at
the
last
moment,
so
I've
still
not
been
to
Australia.
D
It's
on
my
my
list
to
come
visit
at
some
point,
but
the
thesis
of
the
conference
was
that
you
would
get
on
like
a
cruise
boat,
I
think
and
literally
stop
in
those
three
cities
to
do
the
same
conference
in
Brisbane
and
then
the
exact
same
conference
in
Sydney
and
then
in
Melbourne,
in
whichever
order
would
make
the
most
sense-
and
it's
just
like
three
runs
of
the
same
one,
because
why?
If
you
lived
in
one
city,
why
would
you
ever
travel
to
the
universities?
I
guess
is
the
thesis,
but.
D
D
Yeah,
it's
on
my
list
all
right
well
glad
to
have
this
focused
crew.
We
don't
have
a
super
deep
agenda.
Actually
the
other
part
of
your
agenda
is
yakovs
and
I.
Don't
actually
see
him
here,
so
we
may
punt
on
this
until
the
next
session.
Surely,
okay,
in
which
case
we
can
just
get
it
into
business,
talking
about
graphql,
scalers,.
A
C
C
A
C
B
Yeah
there's
a
that
would
be
welcome,
there's
an
architect
here
who
loves
shell
scripting
and
he
automated
his
whole
upload
process
from
Zoom,
including
screaming
the
start
like
he
would
detect
when
people
started
talking
and
it
wasn't
just
Chit
Chat
and
he
had
a
script
to
trim.
Maybe.
D
B
Somebody
who's
very
easily
nerd
sniped,
so
I'll.
Let
them
know.
B
C
D
Yeah,
so
the
primary
meeting,
let
me
drop
a
link,
especially
if
you
haven't
had
a
chance
to
go,
look
at
notes
from
that
one.
Then
it
might
be
worthwhile
just
to
do
like
a
quick
overview
just
to
make
sure
if
there
is
something.
Excuse
me
that
you
wanted
to
dig
into.
We
can
have
a
moment
to
do
that.
D
I.
Think
the
primary
thing
that
we
will
do
as
a
shift
going
forward
is
having
more
of
these,
like
cross-meeting
check-ins,
making
sure
that
there's
a
decent
amount
of
overlap
between
them,
but
not
everybody
is
in
all
of
them,
of
course,
and
So
speaking
to
what
happened
in
the
previous
ones.
Doing
a
little
bit
of
a
recap:
it's
like
standing
agenda.
It's
probably
a
good
thing
for
us
to
do.
D
I
think
there
was
something
else
that
was
talked
about
meeting
Cadence
I,
don't
remember
if
that
was
the
case
anyway,
that
one
I
remember
for
sure
the
other
one
is
the
community
Grant.
This
was
one
I'm
excited
about.
This
is
both
a
of
course.
D
If
any
of
you
all
are
interested
in
applying
to
the
community
Grant,
you
absolutely
should,
but
also
one
of
the
things
that
it
might
be
too
late
to
do
for
this
time
around,
but
something
I
think
we
should
start
doing
is
collecting
proposed
Focus
areas
for
these
kinds
of
Grants.
So,
for
example,
our
website
needs
a
healthy
amount
of
work.
D
Graphql
documentation
could
be
a
lot
better.
There's
definite
like
projects
in
there
it'd
be
really
interesting
to
kind
of
think
about
these
Community
grants
kind
of
like
the
summer
of
code,
where
a
lot
of
Summer
of
code
participants
will
pitch
projects
and
have
people
apply
to
take
on
those
projects.
D
D
Thanks
otherwise
I
think
probably
the
biggest
news
was
the
Benji
I.
Think
you
flagged
this.
That
Express
Scrap
ql
has
been
a
little
bit
in
disrepair
for
the
last
couple
of
years.
D
It
hasn't
had
a
primary
maintainer,
it's
version
skewed
away
from
graphql
JS
and
it's
caused
some
maintenance
pain
and
we
had
a
conversation
about
whether
that
was
even
the
right
project
to
be
representative
of
the
graphql
over
HTTP
work,
and
we
came
to
the
consensus
that
it
probably
was
not
that
actually
most
of
the
work
was
going
into
the
graphql
HTTP
project,
and
then
we
decided
to
move
that
under
the
foundation's
umbrella.
D
D
And
then
otherwise,
we
were
talking
about
expanding
deprecations
to
the
ability
to
deprecate
objects,
which
is
I.
Think
we
understood
that
there's
a
real
problem
to
be
solved,
but
I
think
more
problems
than
answers
came
out
of
it
at
present,
so
that
got
stage
one
and
then
more
in
the
Weeds
on
deferring
stream.
D
Actually,
do
we
even
get
time
to
talk
about
different
stream,
yeah
I
think
we
did
specifically.
There
was
the
overlap
between
deferred
stream
and
subscriptions.
What
does
it
mean
to
use
different
stream
within
a
subscription
and
there's
just
like
an
entire
domain
of
stuff
that
we've
not
thought
hard
enough
about
around?
Do
you
Multiplex
or
not?
D
What
happens
if
one
thing
fails,
while
it's
in
the
middle
of
a
multiplex
there's
just
like
a
bunch
of
complicated
behavior
that
we're
not
really
confident
we
have
the
right
answers
to
and
Rob
had
pitched
essentially
blocking
the
use
of
deferred
stream
from
within
a
subscription
to
make
it
easier
for
us
to
launch
this
for
queries
and
mutations.
D
D
D
Here
we
go
so
this
is
the
actual
technical
project
we
moved,
underneath
the
graphql
umbrella
and
Dennis
is
the
main
maintainer
of
this
project.
So
Dennis
has
been
working
on
this
for
about
half
a
year
at
this
point,
I
think
maybe
a
little
bit
longer
than
that
in
a
very
like
focused
way
and
has
been
part
of
the
set
of
folks
who've
been
working
on
the
graphql
over
HTTP
spec.
D
That
is
this
one
they're
confusingly
very
similarly
named
the
repos
which
we'll
have
to
see
if
we
have
to
that
that
ever
causes
confusion,
we
have
to
fix
that,
but
the
second
one
is
the
actual
specification
dock.
The
first
one
is
a
javascript-based
project.
B
Done
quite
a
bit
of
work
since
we
last
spoke
and
looking
to
put
the
finishing
touches
on
it
really.
So
we're
done
with
all
of
the
writing
and
template
and
put
in
a
string
based
template
as
well,
so
that
two
outstanding
items
we
see
now
is
getting
the
right
licensing
want
to
make
sure
that
that's
consistent
with
everything
else,
graphql
and
also
I'm
hooking
up
the
domain
so
that
it's
on
a
proper
Foundation.
C
C
D
C
It's
really
it's
the
same
good
or
bad
process,
as
in
the
spec,
some
chat
scripting
producing
some
HTML,
deploying
it
via
GitHub
Pages,
using
like
some
GitHub
actions
as
initial
trigger
that
that's
basically
the
setup.
It's
successfully
deployed
already
on
the
GitHub
action
page,
sorry,
GitHub
pages
URL
for
this
report,
but
yeah
like
you,
find
a
separately.
We
need
to
have
like
a
domain
entry
for
scalars.draftpll.org
to
hook
it
up
correctly,
that
that's
that's
really.
What
is
missing,
I
think
I'm.
D
C
You
give
me
access,
that's
possible,
otherwise,
I'm
happy
who,
but
that's
actually
an
interesting
question.
The
domain
is
a
legally
owned
by
the
foundation.
These
days,
I
I
would
hope.
So,
yes,.
D
The
Linux
Foundation
actually
has
the
tools
that
they
use
for
managing
DNS,
which
okay
I'll
ask
at
least
our
our
PM.
If
there's
an
easy
way
for
me
to
access
that
directly,
otherwise,
I'll
just
bring
that
up
the
next
time.
The
two
of
us
meet,
okay
or
maybe
I-
could
just
get
her
help
with
it
sooner
rather
than
later.
C
Yeah
yeah,
so
that
that's
I
think
in
the
actual
we
are
looking
really
at
the
same
setup
as
a
graphical
spec,
so
she
asks
what
we
need
is
really
the
same
entries
as
aspect
of
dog
the
yeah.
The
other
thing
is
that
I
mentioned
it's
a
little
bit
just
legal
fine-tuning.
I
would
say
that
we
we
don't
want
to
embed
new
licensing
or
anything
so
I
would
expect
that
the
same
license
we
use
for
the
spec
is
also
applied
to
the
scale
aspect,
because
it's
also
text.
C
You
know
it's
not
software.
So
it's
it's
really!
It's
it's
really.
In
my
simplified
legal
World,
it
should
be
the
same
yeah.
D
I
think
that
makes
sense
to
me
I
think.
The
one
question
here
is:
are
these
specs
that
are
sort
of
like
licensed
and
owned
by
the
graphql
project
like
when
you
submit
one
of
these?
Are
you
can?
Are
you
basically
like
giving
it
to
the
project?
That's
probably
the
easiest
way,
especially
if
you
want
to
have
like
multiple
people
contributing
to
them
once
they
land.
Yes,
so.
C
B
C
C
Yeah
and
I
I
think
it's.
It
also
matches
the
intent
of
the
author
of
respect
if
I,
if
I,
contribute
to
spec
I
want
to
have
it
shared
and
publicly
available
as
much
as
possible.
You
know
it's
not
really
a
it's.
It's
something
for
the
public
and
for
the
community.
I
want
to
be
consumed.
So
I.
Don't
think
that
there
will
be
anybody
who's
who's,
worried
about
that
yeah.
D
Maybe
what
would
be
most
helpful
is
to
have
one
license
doc
because
of
course,
the
spec
at
the
graphql
spec
there's
like
one
file,
and
it
makes
sense
that
you
would
include
all
the
licensing
information
within
that
file.
But
if
the
idea
of
this
is
that
you're
going
to
have
a
whole
bunch
of
scalar
specs,
ideally,
then
you
wouldn't
want
them
all
copying
and
pasting
or
like
having
to
have
like
a
big
chunk
of
legal
text
in
your
otherwise
very
small
template.
D
C
C
C
If
you
can
do
it
yourself,
lead
it
that's
great.
If
we
need
to
invoke
another
person
yeah,
we
should
paint
this
other
person.
D
Yeah,
maybe
what
you
can
do
first
is
just
get
an
empty
file
in
place,
like
literally
just
have
a
license
file,
that's
just
empty,
or
that
says
you
know
the
license
will
be
put
here
before
the
project
launches
or
something
like
that,
and
then
that
way
you
can
get
all
the
linking
mechanics
and
make
sure
that
it
renders
the
way
that
you
want
it
to
render
and
everything
like
that,
and
then
I
can
take
the
action
to
follow
up
and
get
the
appropriate
licensing
text
in
place.
B
Should
we
start
with
copying
and
pasting
the
graphql
spec
license,
or
is
there
something
there?
That's
particular
to
that
project.
D
I,
don't
there
shouldn't
be
anything
that
is
particular
I,
think
there's
some
stuff
that
might
be
linked
in
a
way
that
breaks
in
non-obvious
ways,
but
probably
that
was
going
to
be.
My
plan
was
like
start
by
copying
and
pasting
and
then
editing
it
down
to
make
sure
that
it
was
very
clear
that
it
applied
to
the
scale
respects
I.
Think
like
in
particular
like
there's
a
copyright
notice
section
for
the
spec.
That's
just
would
not
be
quite
the
right
thing,
yeah
for
the
for
the
scalar
submissions.
D
C
Yeah,
okay,
that
sounds
also
great.
Like
I
said,
these
are
the
two
things
we're
kind
of
blocked
on,
or
we
need
a
little
bit
help
in
general.
Just
to
reiterate,
we
like
the
planners
that
we
will
review
new
product
requests
manually,
that
comes
in
yeah
and
two.
It
doesn't
scale
anymore
but
I
doubt
if
we're
not
scared,
because
we
are
not
expecting
hundreds
of
thousands
and
so
yeah
it
really.
The
overall
goal
is
to
get
this
out
and
get
this
moving
and
have
the
infrastructure
in
place
that
works.
B
C
Then
we
can
refine
things
and
wordings
as
we
go
and
get
feedback
and
other
people
want
to
contribute
but
having
this
infrastructure
in
place,
including
license
and
domain
really.
C
That
brings
us
to
very
good
point
already:
go
yeah
happy
to
discuss
any
other
details
or
questions
if
some
things
are
up,
but
otherwise
I
think
that's
the
main
issues
from
us
understand
something
else.
D
C
That
sounds
awesome
no
from
not
for
me.
D
Cool
we'll
call
it
a
wrap,
we'll
have
a
good
short
meeting.
Yeah
nice
work
on
the
progress,
Donna
and
Andy.
The
I'm
excited
for
this
to
launch
yeah
it'll
be
very
exciting.
C
One
one
thing
around
this
Maybelline
to
two
things:
I
think
it
would
be
great
if
we
write
a
short
blog
post
or
something
once
we
launch
it
to
advertise
it
a
little
bit
and
also
if
we
can
leverage
like
again,
the
Twitter
account
to
tweet
something
out
with
the
blog
post
linger
so
that
that
would
be
my
rough
idea
to
promote
this
a
little
bit
more
in
general.
C
I
think
our
blog
post
is
a
little
bit
underutilized
and
we
could
do
more
to
reflect
the
work
we're
doing
and
the
progress
we're
doing.
For
example,
Express
craft
very
deprecated
should
be
probably
announced
clearly
or
we
could
announce
it
clearly
or
like
the
new
spec
compliant
or
future
spec
compliant
project
included
again
in
the
into
the
foundation.
Stuff
like
this
is
probably
worth
blogging
about,
just
as
a
general
idea.
D
I
totally
agree
to
be
frank:
I
just
haven't
had
the
time
to
write
those
things,
but
certainly
Andy.
If
you
would
like
to
see
this
appear
on
the
log
write,
it
send
invisible
request
and
we
will
get
emerged
and
you'll.
Oh.
D
I
can
go
dig
it
up.
It
is
one
of
those
domain
or
repo
names
where
GitHub
forces
you
to
name
it
in
a
weird
way
to
make
the
default
website
work.
C
Didn't
know
that
it's
just
a
pull
request.
I
I
had
a
more
complicated
process
in
mind,
but
if
it's
a
pull
request,
we
definitely
can
I
will
try
to
utilize
it
more
and
and
bring
up
some
publicness.
D
Yeah
I
know
you
didn't
intend
that
just
wanted
to
make
sure
it
was
clear.
D
Yeah
yeah
and
no
one's
ever
able
to
find
it
because,
of
course,
it's
called
something
weird,
because
that's
how
GitHub
Pages
work
and
I'm
also
realizing
that
we've
refactored
all
this
to
use
Gatsby,
which
is
very
cool
but
I'm,
not
a
a
Gatsby
user.
D
C
Okay,
that's
great
I,
actually
I
either
never
knew
or
forgot
about
it.
So
thanks
a
lot
for
pointing
this
up
yeah,
but
that's
for
myself.
D
It's
a
good
reminder,
though.
I
think
we
we
don't
spend
enough
time
thinking
about
sharing
the
results
of
the
work
that
we're
doing
and
I
might
bring
a
reminder
to
the
whole
group
that,
like
especially
as
we
make
significant
decisions,
we
ought
to
make
note
of
them
here.