►
From YouTube: CI/CD UX meeting 2023-04-26
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
Hey
everyone
today
is
the
26th
of
April
and
we
are
meeting
for
the
cicd
ux
meeting
and
today,
I'm
filling
in
for
Hannah
and
let's
start
with
those
stunning
topics
and
fyis.
So
I'll,
just
like.
A
I'll
mention
like
the
important
items
so
first
just
hand
is
going
to
be
back
next
week
on
Monday
and
next
week
on
Thursday.
We
have
our
very
first
design
review
meeting.
So
that's
great,
and
anybody
who
wants
to
want
you
to
share
a
problem
with
the
team
for
design
feedback.
Please
add
it
to
the
agenda
in
advance.
A
The
agenda
can
be
found
in
the
calendar
invite.
So
it's
probably
not
the
same
one.
It's
a
different
one,
then
the
next
and
one
is
vocalize.
That.
B
Yeah
but
it's
more
like
a
FYI
or
read
only
item
but
I
thought
this
information
from
the
cicd
catalog
project
that,
like
we
redefined
this
name
because
I'm
working
on
the
experiment,
phase
of
the
feature,
so
probably
it
might
affects
to
other,
maybe
AI
projects
or
your
new
feature.
So
I
think
it's
just
good
to
know,
because
if
we
name
it
using
the
experiment
patch,
because
I
was
using
the
alpha
before,
but
I
had
to
change
the
experiment.
B
A
A
He
I
think
is
not
on
the
call
so
I'll
quickly
verbalize.
He
has
thanked
everyone
for
the
reviews
on
the
minimal,
onboarding
design
flow
and
is
working
on
incorporating
all
the
changes
and
I
can
totally
understand
like
there
are
so
many
comments,
so
it's
definitely
going
to
take
some
time.
A
A
Oh
okay,
okay,
Ali
I
was
just
mentioning
that
I
was
kind
of
covering
your
items
for
you.
Do
you
want
to
take
it
up
and
vocalize.
A
D
Problem
that
far
already
yeah
wanted
to
say
thank
you
for
everyone,
for
the
reviews
and
feedback
working.
D
And
yeah,
currently
working
on
improvements.
A
Yeah
just
wanted
to
mention
like
great
work
there
and
we
understand
like
how
many
feedback
there
are
on
the
issues
now
and
the
time
it's
going
to
take
you
to
incorporate
those
moving
on
to
Gina.
She
is
out
of
office
today
and
they'll
still
be
holding
sessions
for
the
solution,
validation
for
Runner,
Fleet,
dashboard.
A
Does
anyone
have
any
comments,
although
I
don't
know
Fleet
dashboard
validation?
If
not,
then
I'll
pass
it
on
to
Emily.
E
Oh
so
my
main
focus
this
past
week
has
been
planning
for
a
design
Sprint
within
environments.
So
we
want
to
kind
of
rethink
environments
as
like
a
deployment
tool.
So
just
I
don't
know
if
all
of
you
know,
but
I
used
to
run
design
Sprints
and
teach
how
to
do
design
Sprints
at
my
previous
company,
so
I'm
taking
the
time
while
planning
for
this
to
help
fix
up
some
of
our
templates.
E
Get
everything
organized
so
might
have
wait,
waited
this
a
little
low
given
kind
of
some
of
the
stuff
we're
having
to
do
but
hoping
to
have
that
complete
before
I
guess.
This
will
be.
My
next
tip
is
I'll,
be
out
of
office
for
two
weeks,
starting
May
12th.
So
my
covered
issue
is
there
but
yeah?
Oh
see.
There's
Utica
has
a
question
yeah.
A
When
you
mentioned
about
like
really
looking
at
this
whole
experience
of
environments,
environments
and
deployment,
it
kind
of
reminded
me
about
the
secrets
manager,
like
native
solution
for
Secrets
management
and
I'm,
just
curious
that
how
you
and
your
team
have
talked
about
it
that,
while
you
are
looking
at
this
bigger
effort,
that's
definitely
going
to
take
some
time
in
that.
Meanwhile,
how
do
you
plan
to
look
at
the
smaller
improvements
to
this
area?
A
E
So
that's
a
really
good
question:
we're
hoping
that
actually,
the
the
design
Sprint
like
day
one
will
really
help
our
focus
and
what
we're
going
to
be
kind
of
going
into,
and
some
of
the
takeaways
of
this
will
actually
be
to
have
I.
Think
it's
like
three
or
four
I'd
have
to
double
check,
but
issues
that
are
ready
for
development
to
take
on.
So
while
we
are
looking
at
kind
of
reimagining,
the
whole
experience
we're
also
looking
at
getting
out
smaller
issues
to
kind
of
work.
A
E
Yeah
and
I'll
be
recording
all
the
sessions
for
this
too,
so
I'll
be
able
to
share
those
out.
I
think
we're
looking
at
hosting
this,
like
the
first
or
second
week
of
June
and
having
it
run
for
a
week
and
a
half
with
split
async
and
sync
period,
so
still
trying
to
figure
out
how
everything
works
together,
but
hopefully
we'll
be
able
to
share
it.
The
process-
and
maybe
it's
something
other
designers
can
kind
of
take
on
as
well.
F
I
would
just
I
would
like
to
be
included
in
those
design.
Sprints,
that's
note,
and
then
the
other
thing
is
just
I
had
created
that
deck.
That
highlighted
the
trouble
with
variables
and
environments.
F
Okay,
well,
I
had
created
that
deck
for
y'all
and
I
will
link
it
here.
It's
just
that
we
have
not
been
like
listening
intentionally
for,
but
have
kept
hearing
about
this
pain,
Point
related
to
variables
and
environments,
and
so
when
that
happens,
that's
an
indicator
that
that's
something
that's
particularly
painful,
so
I
just
wanted
to
be
a
part
of
that
design,
Sprint,
but
also
to
like
Elevate
that
deck
again,
which
I
will
link
as
soon
as
I
can
find
it
well.
A
F
A
Thanks
all
right,
so
the
next
item
is
I
wanted
to
share
like
the
progress
that
we
are
making
on
the
beautifying
UI
16.1,
which
is
going
to
start
in
the
next
Milestone,
so
Payton
and
I.
A
We
met
to
do
a
small,
prioritizing
prioritization
exercise,
because
if
you
look
at
the
issue,
there
are
a
lot
of
issues
shared
with
us
many
epics,
so
we
just
like,
went
through
the
list
and
picked
up
items
that
we
can
work
on
with
the
time
limitation
and
which
also
makes
sense
to
work
on
with
all
the
current
priorities.
A
We
like
put
aside
a
bunch
of
issues,
then
we
plotted
a
chart
of
like
what's
going
to
be
impactful
and
visible,
because
it's
purifying
UI
literally,
and
then
we
plotted
that
against
how
much
time
it's
going
to
take
and
how
much
time
we
have
and
you'll
see
like
in
the
description,
I've
updated.
The
table
of
the
things
we
are
working
on
most
are
like
small
but
impactful
improvements,
but
there
are
two
that
would
require
some
design
work,
which
is
the
last
two
in
the
table.
A
One
is
unboxing
pipeline
detail,
page
which
is
kind
of
ambitious,
but
we'll
still
like
give
it
a
try
and
the
other
one
is
rearranging
the
tabular
layout
on
the
jobs
list
view
to
match
the
pipeline
list
view.
If
you
like,
compare
the
two
today,
there
is
a
difference
in
style
and
there's
also
difference
in
how
we
are
organizing
data.
The
jobs
view
has
like
so
many
columns,
which
just
makes
it
difficult
to
when
we
like
change
the
viewport
size
it.
It
doesn't
look
very
elegant.
A
The
kind
of
shifts
that
happen
there,
that's
one
and
everything
else
is
just
like
regular
Street
group
work.
So
I'll
talk
about
that
in
some
other
meeting.
If
nobody
has
a
question
or
comment,
I'll
like
pass
it
on
to
sunjunk.
F
I
have
one
comment:
I'm
trying
to
find
I'm
distracted
by
trying
to
find
the
link.
I
did
this
analysis
of
the
stuff
verbatim
for
the
last
two
quarters,
which
will
come
out
at
the
end
of
this
week.
The
report,
but
part
of
that
was
identifying
paper
cuts.
Some
of
you
got
pulled
into
the
issue.
F
Yeah
and
so
I
created
an
issue,
and
the
idea
was
just
to
get
verification
from
the
team
about
whether
or
not
it
was
a
paper
cut
but
bless
them
if
they
didn't
just
start
thinking
about
how
to
fix
those
things.
F
But
I
wanted
to
call
it
out,
because
some
of
them
are
small
things
that
relate
specifically
to
pipelines
and
those
pipeline
views
so
visika
as
soon
as
I
could
find
the
issue.
It
might
be
worth
like
just
kind
of
scanning
to
see
if,
when
you
and
Peyton
do
that,
work,
if
there's
any
other
little
things
you
can
support,
and
maybe
that
team
would
pick
them
up
or
or
you
can
get
a
little
help.
A
That
yeah
definitely
so
we
were
a
little
conservative
with
our
planning,
because
yeah
I
mean
we
just
did
not
want
to
over
promise.
But
I
have
this
hunch
that
we
would
in
fact
have
some
time
to
spare
and
we
can
definitely
squeeze
in
some
small
Mrs.
Then.
A
A
B
Yep
thanks
betika,
so
there
is
one
excited
moment
for
me
and
for
the
team
was
the
detailed
page
of
the
catalog
has
been
shipped
and
is
being
reviewed
and
I
believe
we
are
ready
to
break
things
down
for
the
implementation.
So
the
front
end
team
is
working
on
like
how
can
we
break
things
down,
starting
to
communicate
it
with
the
back
end
teams,
just
the
usual
development
flow,
so
I
think
we're
good.
B
If
you
check
the
issue
like
we
got
a
lot
of
feedback,
it
was
really
exciting
and
also
the
design
is
done
so
I
think
the
team
is
ready
to
work
on
this
on
16.1
until
16.2.
So
that's
exciting
and
the
other
piece
that
I
like
to
share
with
you
is
like
myself,
with
our
amazing
Tech
writer
is
working
on
the
very
initial
onboarding
flow.
B
Let's
say
for
Less
experienced
user
who
haven't
create
any
pipeline
so
far
and
then,
if
you
check
this
example,
review
app
like
this
is
targeted
for
those
audience
and
then
like
I,
just
try
this
out
by
myself
like
it
was
so
nice
and
it
was
so
helpful,
like
he
put
all
the
like
comments.
Just
next
to
each
yamu
syntax,
what
does
this
means
and
then
you'd
expect
to
see
some
failure
tax
tests
after
running
this?
Because
of
this
reason?
B
B
Have
really
cute
dinosaur
icons,
so
that
was
exciting
when
I
successfully
build
the
pages
on.
My
namespace,
like
this
is
cute,
like
really
big
dinosaurs
were
on
the
pace,
so
I
think
it's
a
good
example
and
FYI
I'm
out
for
two
weeks
and
coming
back
on
May
15
I
edit
my
coverage
issue
and
yeah.
That's
it
for
me.
B
So
Ayana
is
not
here.
So
maybe
you
can
verbalize
your
comments
if
you
don't
have
any
other
questions.
Sorry.
A
So
if
we
are
being
paint
in
the
community
contributions
for
package,
we
need
to
assign
that
to
Pedro,
because
he's
I
think
covering
first
day
trips
that
don't
have
a
designer,
and
here
are
the
like
changes
that
were
made
to
the
magicus
review
in
relation
to
that
all
right
with
that,
we
are
kind
of
through
with
the
product
design
items
and
now
a
second
passing
it
on
to
Will
and
Erica.
A
F
C
So,
starting
to
wrap
up
and
hand
off
projects
to
others
before
my
leave
starts
in
a
couple
weeks,
so
I've
added
my
parental
leave
issue
above
and
also
to
the
template,
since
it
will
go
on
for
a
period
of
time
and
then
I'm
also
going
to
be
making
a
Q2
research
prioritization
issue,
a
lot
of
it
is
going
to
be
carried
over
from
what
hasn't
been
completed
in
q1,
because
teams
have
been
pretty
proactive
about
letting
me
know
what
research
needs
they
have
so
I'll.
C
You
know
ping,
you
know
Emily
and
Ollie,
and
many
others
that
I
work
with
with
that
gets
created
also
wanted
to
shout
out
Erica,
for
you
know,
supporting
Emily
with
recruiting
for
her
solution.
Validation,
study
I
just
want
to
thank
you,
for
you
know
joining
in
on
on
that
comment,
thread
and
really
helping
support
her
with
with
recruiting.
F
A
F
And
I
think
with
our
big
success.
This
quarter
will
be
that
you
guys
can
sort
of
drive
that
and
be
more
self-serving,
or
that
sounds
funny,
but
yes
be
able
to
get
access
to
those
participants.
So
neither
give
you
one
of
if
you
anticipate
like
in
two
weeks,
starting
to
need
that
participant
pool.
We
should
be
asking
Caitlyn
for
a
push
now
and
then
that
way
you
guys
aren't
like
in
a
spot
where
you're
like
no
I
need
this
participant.
No,
you
need
this
participant.
B
D
C
And
then
my
last
comment
is
that
I
reviewed
all
these
minimal,
onboarding
design,
I
think
maybe
sometime
last
week
and
gave
some
feedback
I
really
appreciate.
You
know
you
putting
those
screens
together.
C
I
think
Vita
had
spoken
to
this
before,
but
you
know:
there's
no
prior
designs
to
just
clearly
leverage,
so
that's
incredibly
difficult
to
just
try
to
create
something
from
scratch
and
I
think
it
was
smart
to
you
know
open
it
up
to
feedback
from
the
whole
ux
team
and
also
bring
it
into
the
ux
Showcase
to
get
some
additional
feedback
and
comments.
C
C
F
Like
anyway,
but
I
I
want
to
talk
about,
I
am
doing
meetings
with
everyone,
because
we
kind
of
like
had
that
Benchmark
stuff,
and
so
there
wasn't
any
way
to
juggle
in
new
research
topics,
because
that
took
up
a
lot
of
time.
F
F
So
just
a
note
that
that
hasn't
been
finalized
and
then
what
I
was
out.
But
I
saw
that
there's
a
thread
talking
about
naming
for
the
catalog
components,
and
we
did
have
an
issue
for
that,
but
it's
silver,
and
so
that
means
that
Dove
drives
it.
F
So
I
did
collect
like
a
little
bit
of
data
for
him
that
he
can
use,
but
it
was
very
narrowly
focused
on
like
how
we
name
the
the
group
of
components
and
so
and-
and
that's
already
been
done
for
him
yeah
so
I
did
that
for
him,
but
I
don't
have
the
agility
to
like.
Do
it
again
in
an
easy
way,
and
it's
also
a
silver
project,
so
he
should
drive
it.
F
F
So
anyway,
I
just
wanted
to
note
that
I'm
not
driving
that
project
and
I
did
like
as
like.
That's
what
I
always
am
trying
to
help,
so
I
did
try
to
help
by
getting
a
little
bit
of
feedback
just
on
those
two
like
how
do
we
name
a
group
of
components,
but
if
we
wanted
to
do
other
research
that
needs
to
be
like
blown
up
and
reprioritized
and
going
through
that
process,
so
I
just
thought.
F
F
And
then
another
thing
that
we're
doing
is
we're
working
on
the
CI
components,
Alpha,
which,
which
we
can't
even
call
it
that,
because
we've
now
like
changed
what
that
means.
So
it's
now
like
we're
pre-experimentation,
but
we
have
people
coming
in
and
they're
using
a
sample
project
to
use
a
CI
component
and
we
looked
at
their
satisfaction
with
the
CIA
templates
and
then
across
assignments,
and
so
they
were
more
satisfied.
F
So
it's
really
good,
like
I,
was
a
little
nervous
like
what,
if
they're,
not
satisfied,
then
we
have
to
do
all
this
other
work,
but
they're
looking
like
they're
satisfied.
So
we
now
know
that
there's
we're
ready
to
take
the
next
steps,
but
so
I
knew
we
did
like
scaffold
their
approach
in
the
in
that
assignment
where
they
used
a
sample
project.
So
then,
what
we
need
to
do
is
then
like
break
out
how
we
scaffolded
that
and
then
make
sure
that's
happening
in
the
in
the
catalog
view
when
we're
ready,
yeah.
A
Okay,
is
there
any
like
for
these
sessions
that
are
happening
where
users
are
coming
in
and
testing
the
say
components?
Is
it
a
video
we
can
watch
like
of
them.
F
F
Have
one
one
video
where
they
made
a
video
themselves
and
shared
it,
but
we
kind
of
are
just
getting
more
of
their
self-reports
and
then
we're
doing
follow-up.
So
it's
not
as
neat
as
being
able
to
watch
them
use
it.
A
F
Yeah,
oh
by
having
them
use
it
yeah
yeah,
it's
a
good
idea.
Yeah.
F
So
it
was
pretty
easy,
so
I
think,
but
but
it
delivers
on
the
concept
of
being
able
to
use,
include
to
kind
of
get
the
component
like
get
the
components
in
your
pipeline
right,
but
I,
don't
think
it
would
be
like
white
worth
it,
but
that's
a
really
good
idea
to
keep
in
mind
like
as
we
go
as
we
move
forward
and
include
more
participants.
Yeah.
A
F
A
A
All
right
does
anyone
have
anything
else
to
mention.