►
From YouTube: API Vision working group | 12/12/2022
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
B
A
A
bathroom
is
still
not
not
complete,
but
it
will
be,
hopefully
complete
next
complete
next
week
and
yeah,
we're
also
preparing
to
move
sorry
to
pack
some
boxes
and
yeah.
Let's
hope
it
will
be.
Let's
hope
the
bathroom
will
be
finished
next
week,
because
otherwise,
we'll
be
left
with
a
non-functional
bathroom
for
like
two
weeks
or
so.
A
A
Yeah
yeah
I
just
said
I'm.
We
started
to
pack
some
boxes
and
planning
to
to
start
moving
on
this
weekend
and
yeah
seems
like
we
can
move
in
before
Christmas,
which
oh.
A
A
Yeah
yeah
I'm
super
happy
about
it.
It's
very
nice
there's
there
I
think,
there's
yeah,
there's
a
couple
of
things
probably
left
to
be
to
be
done
when
we
moved
in
but
yeah
we
figured
it's
nicer
to
move
it
now
and
and
finish
some
things
when
we're
already
in
instead
of
like
waiting
waiting
here
and
now,
and
then
we
also
have
enough
time
to
prepare
our
croon's
home
for
for
the
new
tenants,
so
that
also
takes
probably
I
think
we
have
to
paint
the
walls
white
again
yeah.
A
A
A
Yeah
we
do
so.
We
have.
A
We
still
have
to
get
a
Christmas
tree,
but
yeah
so
enough
time
to
make
one.
A
C
Yeah,
so
it's
just
getting
getting
into
the
notes.
Here
I
see
the
Arts
hero
left
an
item
async,
so
he
mentioned
that
he's
been
working
on,
create
learning
paths
and
content
to
distribute
or
contribute
to
the
API.
I
think
boyan
you've
been
helping
on
that
too,
and
he
says
that
he's
outlined
a
new
API
docs
structure
and
he's
going
to
be
creating
merge
requests
for
that.
So
I
haven't
looked
at
these
notes,
yet
so
I'm
not
sure
what
he's
talking
about
there.
C
But
let's
see
Doc's
summary
of
API
improvements,
yeah,
so
maybe
just
re
reordering
how
we,
how
we
have
the
API
documentation,
yeah.
B
C
Awesome,
okay,
gotcha
great
I,
was
going
to
add
here
adding
an
item
so
I've
been
working
on
the
internal
API
survey,
so
we
reached
out
to
Engineers
within
gitlab
and
we're
exploring
essentially
how
we
approach
API
development
about
opinions
or
processes
around
rest
versus
graphql
challenges
that
we
may
have,
and
so
I
have
uploaded
a
video
and
shared
that
out
to
our
working
group,
Channel
and
Integrations
group
Channel
as
well.
So
we
can
probably
keep
sharing
that
a
little
bit
broader,
yeah
I'll.
C
Add
some
links
here
to
that
yeah,
looking
forward
to
hearing
people's
thoughts
from
the
survey.
If
there
are
some
additional
next
steps,
I
think
we
have
I
think
44.
Respondents
total,
and
you
know
it
was
our
first
kind
of
pass
at
this
this
type
of
survey.
So
there
could
be
a
lot
of
different
actions
we
could
take
from
that.
But
mostly
this
is
in
response
to
our
Gap
analysis.
So
we
we
were
trying
to
understand
what
gas
we
had
in
arrests
versus
graphql
apis.
C
We
worked
with
a
few
groups
previously,
you
know
like
a
spreadsheet
audit,
but
it
was
just
a
handful
of
groups
that
were
participating
there
and
rather
than
going
more
broad
with
that
approach
because
it
was
kind
of
Hands-On,
we
thought
we
would
use
this
survey
and
try
to
understand
what
gaps
and
challenges
we
were
having
so
so
yeah.
This
will
close
out
that
issue.
C
The
next
thing
I'm,
seeing
us
on
doing
on
the
research
side
is
probably
the
last
thing
that
we're
planning
on
doing
is
the
API
Persona,
research
and
I'll
have
to
add
links
in
here
for
these.
But
let
me
add
the
note
here
so
yeah
we'll
be
working
on
that
in
the
next
I.
C
Guess
the
rest
of
this
quarter
we'll
try
to
get
that
up
and
running
and
we'll
be
investigating
if
there
are
additions
to
our
existing
personas
or
clarifications
or
if
we
need
to
create
new
personas
to
kind
of
capture
users
of
our
apis.
So
I've
got
a
research
issue
open
for
that
and
then
we'll
be
getting
that
up
and
going
next,
so
yeah
I'll.
Let
me
find
some
links
to
add
here
and
if
you
guys
have
other
items
to
add,
maybe
you
can
work
on
that
here.
C
Oh
gotcha,
thank
you,
and
so
this
so
this
was
for
the
when
I
was
sharing
out.
The
API
survey
results.
B
C
C
Yeah
internal
API
survey,
so
we've
done
we've
done
an
external
user
research
or
API
user
research
survey.
We
just
did
the
internal
API
survey
and
then
there's
one
third
very
focused
research
issue
on
the
API
Persona
itself.
So
the
the
first,
the
very
first
survey
we
did
was
more
broadly
reaching
out
to
external
users
to
understand
what
their
pain
points
and
challenges
were
around
our
apis.
So
it
wasn't
really
focused
on
defining
personas.
So
we're
going
to
do
a
little
bit
more
research
on
that
topic.
C
Okay,
all
right
I
was
gonna.
Ask
I
was
thinking
about
this
warning
to
our
recent
work
on
API
docs
generation.
So
I
was
wondering
Andy.
If,
if
there's
any
follow-up
from
that,
if
anything
is
there
an
opportunity
to
maybe
share
that
a
little
more
broadly
to
to
users
to
to
kind
of
get
a
sense
of
what
they
can,
what
they
can
do
now
with
in
terms
of
open
API,
spec.
A
Not
yet
so
I
think
I've
been
pretty
busy
with
the
jira
stuff,
so
I've
didn't
look
into
the
open
API
that
much
in
the
past
couple
of
weeks,
but
I
think
the
next
step
is
to
Seattle,
so
the
documentation
that
you
that
we
generate
right
now.
It's
not
really
that's
user
friendly,
so
I
think
the
next
step
is
to
be
able
to
have
people
to
have
an
easy
way
to
generate
the
documentation
and
then
I
want
to
add
I.
A
Think
I
have
an
issue
for
that
and
try
to
find
it
to
add
a
guide
to
the
documentation
on
how
to
how
to
contribute
to
the
open,
API
documentation.
So
it's
easy
for
for
everyone
to
see
how
it
works
and
yeah
how
to
add
more
more
stuff
to
it.
C
Okay,
perfect
yeah.
If
you
can
find
that
issue
that
was
just
making
sure
that
we're
not
missing
an
opportunity
to
share
out
the
work
that
we've
done
so
far,
but
I
know
that
for
the
federal
kind
of
use
case
you
know
we
were
yeah
I
assume
we're
leveraging
that
today,
but
I
guess:
there's
still
some
work
to
be
done
to
expose
this
to
users.
A
Right
exactly
so
yeah.
Accordingly,
the
focus
was
just
petram,
but
I
think
this
is.
This
is
the
the
great
thing
about
this
if
it's
actually
usable
for
for
real
users?
So
that's
why
we're.
C
All
right:
well,
that's
what
we
had
on
the
agenda
today.
If
I
can
clear
my
throat
so
I
think
that's
you
know.
One
thing
that
we
are
lacking
is
is
more
of
the
status
updates.
I,
don't
know
if
there's
anything
else
that
everyone
here
is
tracking
or
working
to
progress,
even
if
we
can
just
share
updates
if
nothing's
happened,
that's
fine
but
yeah
for
anyone
else.
That's
not
on
the
call
updates
on
dri
items.
C
Would
be
great
to
hear
from
everyone?
Is
there
anything
I'm
missing
on
right,
I
think
I
think
Andy.
You
know
that
automated
docs
effort
was
the
main
one
that
you
were
working
on
and
boy
on
your
help
in
Arturo
with
that
first
item,
so
I
think
we've
kind
of
reported
everything
that
we're
working
on
on
this
call.
C
B
C
You're
good
all
right!
Well,
thanks
for
hopping
on
the
call
today,
I,
don't
know
if
there's
anything
else
before
we
wrap
up
on
your
end,
all
right
hope
you
all
have
a
good
week.