►
From YouTube: API Vision working group | 01/09/2023
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
A
Yeah
good
good
I'm
going
to
comment.
I
can't
go
I
can't
start
commenting
because
he's
Skating
here,
but
I
created
a
mail
request,
moving
a
lot
of
things
for
the
rest,
API
and
then
Katie
say
hey.
We
cannot
go
this
way
so
I
mean
it
was
kind
of
adira
from
me,
but
it's
going
to
be
much
more
work
than
than
I
expect,
but.
A
Yeah
but
basically
for
the
docs
API
I
outline
the
new
structure
that
is
going
to
be
similar
to
what
we
have
with
graphql
and
yeah.
The
idea
is
to
move
every
single
page
that
we
have
for
the
rest,
documentation
under
the
rest
directory
and
but
but
yeah.
So
let's
see
how
how
it
goes
during
the
this
week.
B
Well,
will
that
align
with
the
work
we're
doing
around
automated
documentation
as
well.
A
Hey
no
because
I
mean
it
could
be
helpful
because
it's
on
the
open
API,
but
this
party
is
basically
the
documentation
that
we
we
already
have
in
place
and
not
also.
For
example,
we
have
a
samples
for
graphql
that
we
don't
we
don't
have.
We
have
getting
get
it
getting
started
page
on
graphql
that
we
don't
have
on
rest.
So
at
the
end
is
try
to
match
both
things
and
and
have
the
basically
the
the
same
structure
and
something
that
we
like,
but
yeah,
I.
A
Think
it's
going
to
take
a
lot
of
iterations
here,
but
at
least
for
me
we
know
the
elections
that
we
are
taking,
which
is
good
and
Technical
writers,
azraf
or
Katie.
They
are
like
also
happy
and
aligned
with
this
with
with
this
direction,
which
is
very
good.
C
I
was
just
gonna
say
to
me:
I
think
the
most
valuable
part
of
what
you
were
trying
to
do
there
Arturo
is
is
aligning
the
graphql
and
the
rest
API
doc
structure,
because
at
the
moment
it's
a
little
bit
all
over
the
place,
especially
the
introductory
stuff.
We
mix
and
match
and
merge
the
two,
and
we
really
want
to
try
and
create
a
clearer
separation
and
a
clearer
path
for
what
you
want
to
use
and
when
so
yeah
moving.
B
Awesome
yeah,
that's
exciting,
now
cool
well,
I
think:
we've
we've
waited
a
good
while
now
so
I'll
jump
in
to
any
other
issues.
I
know
arterial,
you
kind
of
started
that
one
off
yeah
I
was
just
gonna,
say:
Happy
New
Year
to
everyone.
I
know,
I've
kind
of
said
said
that
to
a
lot
of
our
team,
but
for
the
API
working
group.
B
My
first
item
is
before
the
break.
We
were
discussing
the
go,
gitlab,
library
and
exploring
you
know
if
there's
an
opportunity
for
team
members
to
get
involved
and
provide
some
level
of
support,
not
necessarily
taking
over
full
ownership,
but
getting
familiar
with
with
the
library,
with
the
issues
and
and
helping
guide
things
along
or
you
know,
propose
changes
or
support
changes
here
and
there.
B
So
I
created
an
issue
last
time
and
we
had
several
team
members
raise
their
hands,
so
you
can
kind
of
look
in
there
and
and
take
a
look
and
and
I've
proposed
kind
of
next
steps
in
that
issue,
to
try
to
move
move
that
along
and
and
see.
If
we
can
provide
some
level
of
support
here
and
Arturo
I
see
your
question,
there
is
this
related
to
the
working
group.
B
Yeah
I
can
go
back
and
look
at
the
exit
criteria.
I
think
this
was
just
something
that
was
relevant
to
this
group.
What
we're
trying
to
accomplish.
So
how
do
we
support
customers
using
our
apis
or
users
internally,
partners
yeah?
So
this
is
something
that
I
think
I
think
it's
definitely
relevant
to
to
the
team
here.
B
I,
don't
know
if
it
lines
up
with
any
single
criteria
and
yeah
I,
don't
think
the
intention
is
for
us
to
to
be
fully
responsible,
but
I
think
that
it's
it's
definitely
pertinent
to
to
those
involved
in
this
group.
So
that's
where
we
I
think
we
discussed.
Essentially,
you
know,
maybe
that's
not
something
that
the
Integrations
team
would
take
on
or
the
working
group
would
take
on
explicitly,
but
that
we
we
would
see
who
in
in
gitlab,
is
interested
in
participating,
so
I
think
I.
Think
everyone
here
is
is
relevant
to
that
discussion.
B
All
right,
well,
I
started
a
section
for
dri
updates
and
the
main
one
that
I'm
working
on
right
now
is
around
prioritizing
refreshing,
our
API
personas.
B
So
the
the
two
items
or
two
actions
that
I'll
be
working
on
is
reviewing
our
customer
interviews
that
we've
we've
had
over
the
the
past
months
and
kind
of
summarize
feedback
from
that,
and
then
we
also
have
this
ux
research
research
issue
around
API
personas.
So
we
haven't
really
gotten
into
that
I
think
we
were
getting
into
the
holidays
as
I
was
kind
of
starting
to
pick
this
one
up
so
I
think
we'll
really
get
into
this
one
over
the
next
month
or
so.
B
And
my
last
update
is
I
think
there
were
some
missing
recordings:
I
haven't
hadn't
uploaded,
yet
so
I'm
going
to
go
and
backfill
those
apologies
on
that
I
was
starting
to
list.
The
dates.
I
need
to
go
back
and
see
how
many
were
missing,
but
we'll
work
on
on
filling
those
back
in.
B
Anyone
else
have
dri
updates
to
report
on
or
exocriteria.
C
B
D
Yeah,
so
I
was
hoping
to
talk
with
a
tour
about
prioritizing
the
graphical
of
arrest,
performance
testing
so
profiling
and
to
make
sure
that
we
can
get
that
to
the
next
step
in
that
process.
So
that
report
requires
some
low-level
stuff,
so
we
need
to
just
block
out
some
points
in
the
milestones
for
that
perfect.
B
B
C
No
I
haven't
really
prioritized
or
looked
at
anything
for
the
next
couple
of
weeks.
Okay,.