►
From YouTube: GitLab 16.5 Kickoff - Verify:Pipeline Authoring
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
This
is
a
new
tab
that
we
are
adding
and
in
this
tab
we
have
it
we'll
have
a
table
and
also
this
table
will
be
created
automatically,
which
will
list
the
inputs
parameters
that
each
template
needs
to
have
and
more
information
like
is
it?
What
is
the
default
value
and
if
it's
a
mandatory
or
not-
and
we
also
have
some
sort
of
a
some
sort
of
a
graph
to
allow
user
to
navigate
easily
and
see
the
information
about
each
individual
component?
A
That
is
part
of
the
repository
and
with
it
with
with
this
Improvement
user
could
easily
understand
how
to
use
the
the
template
or
the
components
you
know,
what
are
the
inputs
parameter,
how
to
use
it
and
more
and
yeah
and
I
think
once
we'll
complete
this
epic
we'll
be
able
to
move
components
from
experimental
to
better
and
the
second.
The
third
priority
is
continue
to
work
on
the
input
enhancement,
reminder
inputs
are
the
preferred
way
to
pass
parameters
to
to
a
component
and
would
like
to
enhance
the
their
capability.
A
Furthermore,
and
you
can
see,
we
have
a-
we
have
a
full-blown
epic
inputs
by
the
way
are
any
better.
We
still
have
like
one
more
issue
to
complete
once
we
completed,
hopefully
in
this
Milestone
and
we'll
be
able
to
to
move
inputs
or
form
better
to
GA,
and
as
always,
if
you
want
to
see
the
full
scope
of
of
this
Milestone,
you
can
install
and
look
at
the
table
with
that
I'm
going
to
hand
it
over
to
Saint,
John
and
Saint
John
is
going
to
talk
about
the
scope
of
work
for
ux.
B
Yeah
thanks,
though
so
I'm
going
to
share
my
screen
thing.
Is
this
one
okay?
So
this
is
the
right
window,
so,
first
of
all,
I'm
going
to
finalize
the
journey
map
that
I
share
with
you,
also
in
the
last
kickoff
meeting,
so
I
just
shared
the
Journey
map
here
quickly,
I'm
not
going
through
the
details
for
now
but
like
this
is
the
journey
map
and
then
the
quick
competitor
evaluation
that
I
did
before
and
then
and
then
there
are
some
ideation
that
came
out
from
this
journey
map
exercise.
B
So
we
can
kind
of
walk
through
that
with
the
whole
team
and
if
we
can
review
and
see
what's
the
next
items
for
US
based
on
this
design
activity,
so
that
will
be
finalized
in
16.5
and
the
other
things
that
was
part
was
another
Journey
map
that
is
just
focusing
on
the
release
flow.
So
we
we
now
currently
have
a
releasing
flow
that
led
users
to
go
into
their
project
settings
and
I
like
to
revisit.
B
If
this
ux
is
okay
to
go
or
not,
so
you
can
expect
another
Journey
map
which
is
already
in
progress,
so
you
can
so
check
building.
What's
happening
there
and
the
other
piece
that
I
want
to
do
is
so
this
POC
came
out
a
while
ago
and
seems
like
we're
we're
ready
to
implement
from
the
technical
perspective,
so
I
need
to
kind
of
finalize
for
the
spec,
for
the
design
and
I
can
do
a
quick
user
validation
within
16.5
dope.
Do
you
want
to
add
anything
else
lyrics
perspective.
B
Yep
thanks:
that's
it
from
my
side
and
then
we
have
also
another
teamwise,
so
section
wise,
active
ux
research
efforts
going
on.
So
you
can
also
check
the
link
here
below
and
check
what's
happening
there.
That's
all
from
me:
I'll
stop
sharing.