►
From YouTube: API Vision working group #13
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
It
was
good,
we'll
see,
we
went,
I
actually
met
up
with
a
a
get
live
team
member,
a
friend
of
mine,
Hannah,
Suiter
who's,
another
pm
on
our
team
and
we
walked
around
the
boulder
Fall
Festival.
So
I
did
that
and
then
we
went
down
to
Manitou,
Springs
Colorado
and
just
checked
out.
It's
like
a
little
like
mountain
town,
near
Pike's,
Peak
and
near
Colorado.
Springs,
which
is
I,
don't
know
kind
of
a
destination.
Just
something
to
do
just
wanted
to
go
check
it
out.
A
B
Great
well
I
think
we
have
critical
mass.
It
might
be
a
little
bit
lighter
today.
I
know
we
have
a
few
outs
in
at
least
in
the
Europe
area,
with
the
the
queen
so
Arturo's
out
so
yeah.
Maybe
we
can
go
ahead
and
get
started
and
if
anyone
else
jumps
in
we
can
we
can
catch
up
all
right.
So
I'll
start
on
the
point,
so
Arturo
brought
a
couple
and
I'll
just
voice
over
those.
So
the
first
one
is.
B
We
were
discussing
the
timing
and
Cadence
of
this
meeting,
so
I
thought
it'd
be
good
to
kind
of
get
feedback
on
how
this
time
works,
how
the
day
works
just
the
general,
the
general
Cadence
and
I'll
point
to
this
later,
but
I
was
working
on
kind
of
just
a
survey
to
share
within
this
group.
So
I
added
that
question
there
as
well,
but
I
thought
I'd
get
thoughts
from
those
on
the
call.
A
Yeah
sounds
like
a
good
idea
to
me,
like
yeah
I,
think
we
sometimes
or
often
see
see
a
common
in
Friends,
Day
or
public
holidays
on
Monday,
so
right
makes
sense
to
move
to
meeting
and
yeah.
So
Friday
is
is
probably
the
same
problem,
but
any
other
day
would
work.
For
me,
too.
D
B
Yeah
I
think
yeah
I.
Think
mostly
for
this.
The
sync
meeting,
the
Monday
Mondays,
seem
to
be
a
challenge.
I
think
it
may
be
different
if
yeah
we're
not
you
know,
trying
to
organize
like
we
are,
but
yeah
so
Tuesday,
Wednesday
Thursday
seems
to
be
I
should
recommended
twice
seems
to
be
the
choice,
all
right,
any
other
thoughts
or
feedback
on
this.
What
about
the
the
bi-weekly
Cadence?
Is
that
working
well?
Is
it
enough
or
is
it
too
much.
C
A
Yeah
same
here,
I
think
every
week
would
be
too
much
and
but
two
weeks
seems
to
work
well.
We
almost
always
have
points
on
the
agenda
and
we
almost
always
use
all
of
the
time.
I
think
that's
a
good
yeah,
a
good
indicator
for
for
a
good,
yeah
schedule.
If
we,
if
we
are
too
often
over
time,
this
probably
means
we
should
maybe
meet
more
often
or
do
more
things
async,
but
I
think
we
have
a
very
good
balance
at
the
moment.
D
B
Cool
and
if
you
would
like
to
also
share
you
know
feedback
on
that
survey
on
this
point
we
can.
We
can
get
feedback
more
broadly.
Welcome
to
the
call
sheridi
am
I,
saying
that
right.
B
Thanks
for
joining,
we
were
just
talking
about
the
Cadence
of
our
calls.
I
know
you're,
maybe
new
to
joining
so
but
yeah.
You
can
feel
free
to
share
your
feedback
as
far
as
like
what
you
think
would
be
good
on
bi-weekly
Cadence
Mondays
as
a
regular
sync
timing
and
we're
considering
actually
moving
it
to
Tuesday,
Wednesday
or
Thursday.
E
Okay,
it
works
for
me:
I
don't
have
a
problem.
Tuesday
Wednesday
Thursdays
are
also
okay,
so
yeah.
This
is
the
first
time
attending
this
call,
so
I
think
I
will
just
I'm
not
very
much
familiar
with
how
how
the
discussion
in
this
call
goes
goes
on
and
so
on.
Sure
yeah
I'll
be
okay,
I'm,
okay,
with
the
Tuesday
Thursday,
then
other
days
also
the
same
time
works
for
any
day
in
the
week.
B
Okay,
that's
a
good
point
about
the
timing
too.
Maybe
yeah
I'll
have
to
look
at
that
all
right.
Well,
thanks
for
your
feedback,
I'll
move
on
to
point
number
two
also
Serenity
are
you?
Do
you
have
the
doc
as
well
have
access
to
the
doc?
Oh
you
you're
in
there.
Okay,
I
just
want
to
make
sure
you're
aware
of
that.
Okay
number:
two
note
for
dris:
can
you
please
update
the
progress
for
each
of
the
exit
criteria?
So
you
know
this.
B
Mr
is
open
and
we've
added
exit
criteria
to
our
our
working
group
page
and
we're
hoping
that
we
can
all
identify
the
dris
and
and
then
start
to
share
some
type
of
progress
which
may
be
you
know,
maybe
a
challenge
in
some
cases,
but
we
want
to
start
somewhere
just
get
a
sense
of
where
we
are
so
any
questions
comments
on
that
one
or
we
can
move
on
to
the
next.
B
Okay,
number
three
Arturo
was
throwing
out
a
recommendation
as
well
he's
suggesting
that
for
async
updates
on
each
of
the
things
that
that
we're
covering
from
a
dri
perspective,
that
we
could
use
this
doc
to
share
more
progress,
async
progress
updates
and
you'd
like
to
do
that
for
the
next
two
weeks.
B
I
think
I
think
too
at
least
Buena.
Do
you
have
any
items
as
dri
I
think.
A
No,
but
what
what
that
says
this
mean?
Does
it
mean
we
have
like
a
every
every
two
weeks?
We
have
something
on
our
dock,
to
where
everyone
gives
and
gives
an
update
on
on
the
status.
B
Yeah,
that's
that's.
My
understanding
here
is
just
that
we
have
a
status
check
and
that
we're
we're
doing
that
kind
of
preemptively
so
that
we
we
can
kind
of
keep
track
of
each
of
these
items
over
time.
So
you
know
I,
guess
on
on
some
of
these
calls.
We
don't
always
touch
on
every
item.
So
if
we
can,
you
know
add
that
to
the
dock
ahead
of
time
we
can
at
least
async
kind
of
keep
up
with
where
things
are,
and
you
know,
everything's
blocking
or
moving
slowly.
A
Think
I
know
let's
have
a
another
DIY
for
an
item,
but
I
think
this
sounds
like
it
makes
sense
and
we
could
just
try
it
like.
We
can
just
yeah
have
like
a
template
for
for
each
meeting
agenda
and
then
yeah.
C
B
B
Cool
okay,
any
other
topics
or
points
or
comments
on
that
on
number
three.
B
Yeah
I
think
this
would
be
a
responsibility
for
the
dris
as
identified
in
the
exit
criteria,
but
I
think
I
want
to
say
that
there's
still
a
few
items
that
don't
have
dris
so
there
may
be.
You
know
something
to
explore
there.
D
B
B
Okay,
I'll
move
to
point
four
R2
is
asking:
how
can
we
engage
the
rest
of
the
members
of
the
working
group
so
for
each
epic
exit
criteria?
We
have
we
identify
the
next
issue.
Maybe
we
can
try
to
assign
or
delegate
some
of
these
so
yeah.
We
have
dris,
we
have
epics
associated
with
each
of
the
topics
and
we
have
issues
within
those.
So
obviously
the
dri
is
meant
to
help.
B
You
know
share
the
progress
updates,
help
move
things
forward,
but
they
may
not
be
Hands-On
doing
the
work
on
every
item,
so
we
might
have
issues
that
we
need
to
delegate
so
yeah.
So
definitely
I
agree
with
this
I
think
trying
to
think
about
how
we
can
engage.
B
You
know
more
of
of
those
who
signed
up
or
or
others
that
are
interested
in
being
a
part
of
the
group
and
picking
up
issues
and
participating.
I
think
would
be
great
any
thoughts
on
this.
D
I
would
like
add
the
ad.
Maybe
since
we
we
have
owners,
but
also
other
members
are
going
to
participate
here,
so
maybe
they
could
be
like
some
synchronous
communication
between
them,
so
they
can
like
give
updates
to
their
owners
or
just
like
to
be
like
having
track
in
between
and
so
owners
can
use
this
page
to
give
like
this
by
week.
Update
does
that
sounds
reasonable.
B
And
I
think
maybe
I'll
try
to
clarify
that.
So
we'll
have
a
dri
like
say
on
the
dri.
Sorry
I
just
need
to.
B
Build
you
know,
let's
say:
I'm
the
dri
and
I'm
working
with
Andy
on
an
issue
you're
talking
about
the
discussion
between
myself
and
Andy.
In
that
case,
can
you
clarify,
like
you,
would
like
to
see
some
of
that
conversation
being
serviced
asynchronously.
D
B
Yeah
I
don't
want
to
get
too
deep
with
the
dris,
but
something
like
that
yeah
I,
think
that
makes
sense
absolutely
yeah,
but
you
know.
I
would
hope,
though,
that
the
dri
of
of
the
topic
is
is
staying
a
prize
on
what's
going
on
with
those
issues,
but
I
agree,
there's
going
to
be
cases
where
we
want
others
to
kind
of
communicate
those
issues.
A
B
Now,
moving
on
to
number
five,
so
I
mentioned
earlier,
I
put
together
a
quick
just
Google
survey,
so
it's
very
sparse
just
wanted
to
kind
of
get
a
pulse
on
where
we
are
with
with
the
working
group
how
everyone
is
feeling
about
the
progress
and
and
what
we're
working
on
so
yeah
feel
free
to
jump
in
there
and
and
I'll
drop
this
as
well
in
the
in
the
slack
Channel
as
I
share
yeah
share
the
meeting
notes
from
today.
B
And
last
point
I
had
here
is
number
six
I've
been
working
on
this
for
a
little
while
this
has
been
I.
Guess
one
of
my
dri
items,
the
internal
API
user
survey.
This
is
like
the
next
iteration
of
the
Gap
analysis.
We
started
with
kind
of
a
more
manual
process,
trying
to
understand
identify
what
apis
exist
in
each
of
the
each
of
the
areas
like
within
our
stages
and
groups
and
are
they
you
know
graphql
rest?
How
do
we
like?
What
would
it
look
like
to
get
parity?
B
You
know,
do
we
you
know,
do
we
have
feature?
Are
we
are
we
covering
all
of
our
features
in
terms
of
API
endpoints?
So
this
is
going
to
kind
of
take
this
a
little
bit
more
broader.
It
was
such
a
manual
process
that
we're
hoping
that
the
survey
could
get
us
some
pretty
good
input
from
the
teams
across
gitlab
about
how
we're
approaching
our
apis
and
yeah
I've
been
working
on
this
getting
some
feedback
in
the
issue.
B
I
have
taken
it
into
now,
a
formal
qualtric
survey,
format
and
I'm
working
on
getting
this
shared.
Hopefully,
this
week
so
I've
been
asking
for
feedback,
but
you
know
it's
it's
still
possible
to
share
feedback
now.
So
if
you
want
to
take
a
look,
go
through
the
survey,
give
it
a
try,
there's
some
things
functionally
within
the
survey.
I
think
I'll
still
need
to
tweak
so
yeah.
Just
let
me
know
if
you're
running
into
issues
but
yeah
happy
to
hear
your
thoughts
on
that
which
we
can
do.
B
D
Sorry
I
don't
have
access
to
this
link.
Is
this
like
preview,
locked
temporarily
or
I
need
an
account
dude.
B
B
B
I,
don't
know,
usually
you
don't
have
problems
with
these
okay.
Let
me
Circle
back
and
I'll
share
this
in
the
slack
Channel
as
well.
B
B
Cool
and
since
you're
new
to
the
call
3D
I
thought
I'd
just
check
in
and
see
you
know
what
you're
you're
hoping
to
get
out
of
the
call.
If
there's
anything,
we
can
answer
for
you
or
point
to
interested
in
your
your
thoughts
on
what
we're
working
on.
E
Yeah
hi,
so
actually
I
have
joined,
I
joined,
get
lips
I'm
three
months
back
and
since
then,
I've
been
mainly
working
on
the
tasks
which
are
related
to
the
API,
like
I,
have
a
fixed
few
of
the
apis
I
develop
new
apis
for
my
for
the
authorization
group
and
what
I
observed
while,
while
doing
all
this,
while,
while
developing
apis
on
working
on
API
kind
of
requirements,
I
felt
there
is
some
lack
in
the
way
we
document
API
currently
and
the
way
we
take
the
requirements
from
the
users
when,
when
it
comes
to
API,
we
should
be
having
a
well
at
least
some
sort
of
well-documented
what
you
call
requirement
where
we
know
that
what
would
be
the
exact
URL?
E
What
will
be
the
parameters?
What
will
be
the
types
like
the
way
we
could
generate
it
using
swagger
and
so
like
in
generally,
in
the
way
in
we
specify
using,
opens
open,
API
specs.
E
If
we
could
just
get
that
in
place,
then
the
there
were
some
last
minute
confusions
on
one
of
my
implementations
where,
where
how
I
implemented
that
API
requirement
the
data
type
that
I
used
to
the
data
type
that
I
use
to
accept
the
parameter
from
the
user,
it
was
not
correct
or
it
was
not
up
to
the
it
was
not
as
expected
by
the
user
by
the
end
user.
It
was
correct
the
world,
it
was
working
in
everything,
but
it
was
not
as
per
what
was
expected.
E
So
it
was
a
very
last
minute
change.
No
one
noticed
it,
but
it
was
a
very
last
minute
change
and
we
had
to
fix
it.
So
I
thought
that
if
if
this
could
have
been
documented,
that
this
is
what
the
this
is,
how
the
API
specs
will
look
like,
then
the
that
last
minute
issue
would
not
have
happened.
So
that's
the
reason.
I
thought
that
probably
we
can
maintain
it
using
swagger
or
some
other
open,
API
aspect
tool,
and
so
I
just
erased
this
point
in
one
of
the
retrospectives
in
that
team.
E
So
Hana
put
me
in
touch
with
this
group,
so
I,
that's
how
I
just
thought
I
will
just
get
into
the
meeting
and
see
what's
going
on.
E
B
A
Yeah
yeah
I
was
supposed
about
to
say
that
yeah
I
just
looked
into
how
we
can
generate
an
open,
API
documentation
and
yes,
I
can
share
an
issue.
A
I'll
put
it
in
the
agenda
yeah.
So
this
is
basically
basically
the
issue
about
Auto
generating
this
document,
and
we
just
started
working
on
this
okay
and
yeah.
The
idea
is
to
I
think
we
want
to
build
something
in
this
Milestone
to
to
generate
to
at.
A
To
go
to
open,
API
documentation,
I'm,
not
sure
how
far
we
get
with
annotating.
All
the
endpoints,
like
you
know,
probably
have
to
yeah,
add
some
examples
and
stuff
like
this.
There's
there's
a
lot
to
do,
but
yeah
feel
free
to
to
check
the
issue,
and
if
you
want
to
help,
there's
probably
something
yeah,
something
you
can
add
to
it.
E
B
I'm
I'm
kind
of
curious
to
use
sweetie
what
what
was
the
exact
data
type
that
you
know
the
user
is
confusing.
If
you
can
recall
no
pressure,
but.
E
E
Okay,
so
this
excess
level
there
was
one
I
will
just
send
to
the
Mr.
Also
if
you
want
so
there
was
this
attribute
named
access
level
which
we
were
accepting
as
the
string,
but
the
same
API
I
mean
the
same
attribute
at
in
other
apis.
What
we
was
being
accepted
as
integer.
E
So
that's
the
word.
So
we
have
access
levels
in
in
our
in
git,
lab
right,
maintain
a
reporter
and
developers
like
that.
So
I
was
accepting
in
my
API
it
as
string,
but
in
other
EPA
implementations.
We
are
accepting
it
as
integer,
so
it
had
to
be
like
it
had
to
be
in
sync
with
other
implementation,
so
I
had
to
make
this
stage
last
one.
B
I
understand
yeah,
that's
a
really
good
example:
yeah
that
yeah
I
think
yeah
the
term
here
too
Beyond
open,
API
documentation
is
standards
so
like
having
some
kind
of
standard
set
across
how
we
implement
our
apis.
So
yeah,
that's
that's
good
feedback
that
you
know
we're
seeing
internally
and
I.
I
know
that
there
are
a
lot
of
cases
of
this,
so
yeah
I'm,
hoping
that
this
is
a
really
good
starting
point
that
Andy's
working
on
with
automating
the
documentation
cool.
E
Not
as
a
friend
that
I
noticed
immediately,
but
yeah
I'm
not
very
curious
to
go
through
all
the
go
through
the
vision
in
detail
and
just
look
at
the
issues
which
are
related
to
it
not
answer
this
was
my
immediate
feedback
was.
B
B
All
right,
well,
I,
don't
see
any
other
points,
so
I'll
just
leave
it
open
for
another
minute
here.
If
there's
anything
to
share
I,
don't
know
anything
from
here
in
Katie.
B
Yeah
and
I
I
think
that's
I'll,
try
to
coordinate
with
Arturo
as
he's
back
in
the
office
and
and
work
on
the
async
structure
like
how
can
we
get
some
progress
updates
because
there
are
some
things
I'd
be
interested
in
hearing
if
we
had
the
right
people
on
the
on
the
call,
but
I
know
we're
working
on
the
the
rest
of
our
graphql
rapper,
so
I'm,
not
sure
where
that
is
I
was
kind
of
curious
and
want
to
check
in
on
the
status
of
that
myself,
but
yeah
I
know
we're
talking
Andy
about
through
some
of
the
questions
you
had
on
how
to
scope
this
for
this
Milestone.
B
I
know
we
have
some
other
related
technical
docs
tasks
out.
There
I
think
that
Katie
you've
been
working
on,
so
maybe
we
can
just
work
on
getting
the
table
structure.
I
know
we're
about
at
time
already
for
today
and
then
work
on
doing
this
async
between
now
and
the
next
call
I
think
that
would
be
pretty
pretty
valuable.