►
From YouTube: API Vision working group | 10/31/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).
B
Well,
just
hopping
from
one
meeting
to
the
next
this
morning,.
A
Today
we
don't
have
that
much
to
discuss
it's
okay,
it
is
not
in
the
call,
so
I
think
that
she
is
updating
about.
You
know
the
documentation
of
the
rest
API,
especially
on
the
world,
that
we
are
doing
related
to
the
to
the
open
API.
Very
soon,
too,
that's
data
was
creating
different
issues
for
different
teams.
A
A
We
reviewed
existing
content
and
now
the
next
thing
is
I
want
to
review
a
training
resources,
other
ideas
by
other
different
companies.
So
maybe
we
can
get
some
ideas
about.
You
know
what
are
the
learning
paths
or
different
things
that
they
are
doing
and
boyan
is
going
to
join
me
in
order
to
help
me
with
this
exit
criteria.
A
So
this
week
this
week,
the
only
Advance
here
is
the
outline
of
the
next
steps,
but
for
the
next
two
weeks,
I
think
that
maybe
taking
a
look
to
the
you
know
different
companies,
what
they
are
doing,
I
think
is
going
to
be
good
progress
for
us
here.
C
B
I'll
move
to
my
points
and
I'll.
Add
some
links.
I
don't
have
the
links
in
there
just
yet,
but
I'll
come
back
around
and
add
links.
I
think
I
shared
this
last
last
working
group
meeting,
but
our
internal
API
survey
is
still
out
and
open.
I
need
to
do
some
follow-ups,
myself
and
various
channels,
but
could
still
use
help
just
getting
the
word
out
and
getting
more
feedback.
I
think
we
have
roughly
30
or
so
responses
now
I
feel
like
we
could
do
a
lot
better
than
that.
B
So
yeah
I
think.
If
you
know
anyone
who
you
could
reach
out
to
on
different
teams,
just
maybe
asking
them
if
they
would
mind,
sharing
some
feedback.
That
would
be
helpful.
A
Maybe
you
can
post
this
again
on
the
engineering
week
in
review
in
the
document,
because
that
document
every
week
you
know
the
whole
engineering
Department
review.
That
document
so
I
think
that
that
could
be
another
idea.
You
know
to
post
again
even
that
they
know
there
is
a
also
it's
like
channel.
That
is
engineering
for
your
information,
so
you
can
post
it
there
in
there
as
well.
B
And
one
thing
that
could
help
is:
if
someone
else
want
to
try
sharing
this
just
a
different,
a
different
angle,
a
different
name
behind
it.
Maybe
people
don't
know
me
as
well.
B
So
if
yeah
I
know
Arturo
has
some
star
power.
So
if
you,
if
you
wouldn't
mind
sharing
it,
might
it
might
help
coming
from
someone
different
and
like
I,
want
to
keep
pushing
the
message
out
too,
but
just
looking
for
ways
to
kind
of
get
get
exposure
to
it.
B
My
next
bullets
I've
put
together
a
uxr
issue.
I
know:
we've
got
an
open
issue
in
the
working
group
under
the
working
group
label
around
API
personas,
but
I'm
trying
to
work
on
actioning
that
taking
into
ux
research
and
try
to
start
working
against
that
in
Q4.
B
So
that's
something
that's
been
on
my
my
plate
and
then
the
last
item
I
had
is
just
one
to
share
out
and
I.
Think
I
haven't
looked
back
to
slack
to
see
if
there's
any
discussion
on
this
yet
but
I
met
with
maintainer
of
go,
get
lab
last
week
this.
You
know
this
came
up
a
while
back,
probably
six
months
ago,
there's
interest
in
in
gitlab,
taking
more
of
a
role
in
go,
get
lab,
I!
B
Think
it's
been
for
us
a
matter
of
kind
of
timing
and
capacity,
but
I
think
it
may
be
more
of
an
opportunity
now
to
start
reconsidering
this
so
I
think
we
have
a
couple
issues
out
there
that
are
related
to
this
topic
and
there's
a
discussion
in
slack.
B
B
A
Yeah
I
know
that
I'm
not
sure
if
this
is
relevant
to
the
API
working
group
for
more
to
the
encourations
group.
You
know.
B
Yeah,
it's
a
good
question.
I,
don't
know
it
could
be
a
bit
of
both
I
think
yeah,
I!
Think
of
our
apis
I.
Think
the
the
user
experience
developer
experience
around
using
our
apis
is
relevant
when
we're
talking
about
sdks
and
other.
You
know
libraries
for
using
RPS,
so
I
think
I
think
there's
some
relevancy
there,
but
it
could
also
be
something
that
that
may
be
more
appropriate
for
us
to
look
at
for
the
Integrations
team
standpoint.
B
So
I'd
like
I'd
like
to
consider
it
on
both
threads
and
see
see
what
feedback
we
can
we
can
get
around
this
and
how
we
want
to
action
in.
C
I
I
definitely
remember
that
you're
saying
that
talking,
let's
talk
about
this
in
the
past
and
I
could
see
the
relevance.
That's
to
talk
about
apis
sure
it's
a
good
question
of
whether
efforts
is,
but
it
doesn't
seem
irrelevant
to
me
at
least
at
least
especially
this
early
investigation
stage.
B
Right
yeah
good
deal
so
yeah
I
think
yeah.
If
there's
anything
that
anyone
would
like
to
share
on
this
here,
I'm
happy
to
open
up
some
discussion
and,
of
course
we
have
slack
and
a
couple
of
issues
that
I've
highlighted
there
and
I'll
pull
I'll,
pull
all
the
links
into
the
dock.
Here
too,
as
I
get
a
moment,
yeah
happy
to
kind
of
start
talking
about
this
I
know
when
it
first
came
up
it
was.
It
didn't
feel
like
the
right
timing
for
this
today.
A
Yeah
I
think
that's
a
having
an
issue
is
going
to
be
helpful,
especially
because
I
I
just
want
to
discuss
not
just
the
goal
GitHub
you
know,
but
in
general
how
to
deal
with
these
projects.
You
know
because
in
the
past
we
have,
and
actually
we
fully
take
ownership
of
any
prayer
or
not.
But
this
has
been
other
conversations.
You
know
about
other
libraries
and
things
to
interact
with
good
luck
and
and
I.
Don't
remember
exactly
the
discussions,
but
there
are
problems
about.
You
know
the
capacity
that
we
have
to
take
ownership
about.
A
B
Yeah
I
I,
agree,
I,
think
that's
a
good
point
that
we
I
think
that
we
can't
necessarily
set
a
precedent
that
we
can
do
this
in
every
case,
and
we
have
to
be
thoughtful
about
about
this
particular
case
as
well.
B
I
think
I
think
the
best
example
of
something
like
this
in
git
lab
is
the
terraform
provider
which
the
mine
are
seeing
right
now
the
model
I'm
going
to
talk
to
Victor
next
week
and
ask
some
more
questions
on
this.
But
my
understanding
of
the
model
is
that
we
are
maintainers
of
the
terraform
provider
yeah,
but
it's
the
the
main
effort
involved
is
really
in
reviewing
the
requests
and
making
decisions
and
guiding
you
know
kind
of
guiding
the
process
there.
B
So
if
you
know,
if
there
are
big
feature
requests,
we
can
still
say
we
don't
have
capacity,
but
if
there
are
opportunities
to
add
some,
some
features
functions
that
support
a
new
API
that
we've
added,
that
there
could
be
some
some
benefit
and
a
low
level
of
effort
to
handle
these
types
of
things
and
that's
I've.
Also.
B
You
know
that
took
some
some
of
the
feedback
in
my
discussion
with
this
maintainer
to
understand
what
the
effort
has
looked
like
on
their
end
and
I,
put
that
into
into
interview
notes
that
you
guys
can
access
and
review
as
well.
So
that
should
give
you
a
little
more
context
as
to
what
we
might
be
looking
at,
but
you
know
ultimately
I
think
it
needs
a
home
where,
wherever
that
is
or
we
need,
we
need
to
look
at
how
to
support
get
more
support
in
terms
of
maintainership.
B
A
All
right
anything
notice
from
anyone.