►
From YouTube: CI/CD UX Meeting 2020-10-07
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
So
welcome
everyone
to
the
cicd
ux
meeting
yeah
we're
having
almost
a
full
team
just
nowadays
on
pto,
probably
hopefully
enjoying
some
good
weather.
I
think
she's
in
spain,
somewhere
traveling,
so
yeah
we
have
quite
some
fyi's
as
a
read.
Only
to
start
from,
there
are
quite
some
vacations
coming
coming
up
and
also
we
have
a
feminine
friends
days,
of
course.
So
hopefully
everyone
has
some
good
plans
to
spend
and
to
enjoy.
A
Maybe
the
last
I
don't
know
summary
they're,
not
that
summery
days
anymore,
cool,
yeah
and
then
to
the
discussion
items.
So
the
first
thing,
of
course,
just
wanted
to
again
congratulate
hayana
with
promotion
to
the
staff.
That's
amazing
well
deserved
congrats.
On
that
super
happy.
You
know
to
see
those
things
happening
on
the
team
and
yeah
a
little
bit.
That
was
a
bit
of
a
positive
start.
Then,
of
course
a
little
bit
of
a
sad
news.
A
So,
oh
god,
let's
just
go
through
that,
so
juan's
just
has
started
his
countdown
for
the
final
seven
days.
Sorry
juan
for
saying
it.
This
way
just
wanted
to
make
an
official
kind
of
like
announcement
just
to
make
sure
that
we
are
all
aligned
on
the
same
page.
So
we
are
refilling
those
roles,
of
course,
so
we
will
be
searching
for
a
new
product
designer
there.
We
are
meeting
up
with
rupert
to
discuss
exact
plans
there.
A
I
just
want
to
specifically
highlight
the
fact
that
we
will
not
be
having
any
official
backup
for
juan's
stage
groups
in
the
meantime,
but
I
was
encouraging
james
and
will
be
encouraging
darren
to
submit
any
urgent
screams
for
help
for
the
ux,
as
well
as
research
work
to
our
channel.
So,
as
I
said,
please
be
kind
to
them,
offer
some
help.
If
you
will
feel
like
you
have
a
capacity
or
bad
fees.
A
I
don't
think
this
will
happen
a
lot
or
will
happen
at
all,
because
actually
juan
left
really
a
solid
issue
for
the
transition,
but
still
you
know
just
kind
of
like
saying
it
out
loud
there
hyanna
do
you
want
to
vocalize
your
next
point.
B
Yes
and
wait,
who
wants
departure?
B
We
have
an
open
spot
for
the
training,
design,
maintainer,
and
then
I
mentioned
here
that,
if
you're
interested,
please
reach
out
to
me
and
videga
was
faster
than
a
bullet,
if
you
already
raise
her
hand,
but
in
any
case,
if
you're
interested
in
becoming
a
ux
maintainer
there's
a
process
in
the
handbook-
and
you
can
open
an
issue
for
that.
B
I
know
that
right
now
we
don't
have
enough
capacity
to
go
over
for
more
training
maintainers,
because
there's
only
three
actual
maintainers
for
that,
but
you
can
always
just
start
the
process
anyways
and
or
something
in
your
backlog
and
review
things.
But
anyway
that
was
my
announcement
and
then
back
to
you
nadya
just.
C
Yes,
I
was
not
as
fast
as
the
guys,
so
I
will
open
up
that.
C
No
worries
at
all
once
a
spot
opens
up
I'll
I'll,
be
in
a
position
to
take
it.
B
Yeah
and,
like
I
said,
there's
also,
you
don't
really
need
to
go
over
the
process
to
become
a
maintainer.
So
if
you
also
look
at
the
handbook
page,
we
made
recently
some
updates
talking
about.
You
know
how
anyone
that
is
an
expert
on
pajamas
or
a
design
system,
etc.
Some
specific
areas
can
become
a
maintainer
or
a
knowledge
expert
in
pajamas.
B
So
please
have
a
look
and
yeah
just
let
us
know
how
how
we
can
help
you
navigate
this
process,
even
though
we
cannot
accommodate
more
maintainers
than
what
we
have
today.
A
Okay
and
then
to
another-
I
hate
saying
this,
but,
as
you
all
probably
seen
with
my
message
yesterday
same
as
as
news
on
about
juan,
unfortunately,
it's
kind
of
like
got
into
the
same
timing.
I
promise
you.
This
is
a
coincidence
and
yeah.
My
last
day
at
gitlab
will
be
on
31st
of
october.
A
I
have
accepted
a
really
nice
opportunity
outside
with
a
lot
of
salt
on
my
heart,
to
be
honest
because,
as
I
was
sharing
with
some
of
you
already,
I
feel
like
I
learned
it
was
only
a
year.
It
was
really
it's
probably
the
shortest
experience
funny
enough
in
my
career,
but
I
feel
like
this
was
one
of
the
most
knowledgeable
and
the
people
are
so
senior
you
guys
everyone
on
youtube
seriously
on
this
team
are
so
serious.
I
was
a
senior.
A
I
was
saying
that
it
almost
feels
like
you,
don't
need
anyone.
You
know
to
help.
You,
like
everyone,
is
figuring
out
things
on
themselves,
I'm
just
so
proud.
However,
things
are
as
they
are,
so
31st
of
october
is
going
to
be.
My
last
day
I
proposed
to
hayana
to
backfill
me
until
we're
gonna
find
a
proper
well,
how
do
you
say
feel
for
the
role
yeah,
so
the
role
will
be
opened
inside
and
outside
of
gitlab.
A
So
actually
any
one
of
you
can
apply
and
a
couple
of
people
on
this
team
are
definitely
should
be
doing
that.
If
you
have
any
questions
around
that
process
feel
free
to
reach
out
to
me,
we
still
have
quite
some
weeks
while
I'm
here,
I
would
be
happy
to
support
each
and
every
one
of
you
but
yeah.
A
I
actually
personally
really
like
seeing
a
bit
more
product
design
managers
who
are
coming
internally
from
gitlab,
because
you
kind
of
like
know
the
all
of
the
insides
out
of
the
process,
and
I
personally
within
this
role.
I
think
this
is
something
that's
going
to
be
very,
very
helpful
to
the
teams
that
you're
going
to
be
managing
so
yeah,
if
any
questions
feel
free
to
jump
in
right
now
or
reach
out
to
me
after
the
call
or
whatever
okay
enough
of
this
sadness.
A
E
Up
to
your
point
yeah,
so
this
was
actually
a
message
that
I
shared
with
nadia
and
we
are
also
discussing
it
here
today.
E
I
was
looking
at
the
document,
an
async
design,
critique
document
which
was
circulating
from
the
source
code
team,
where
they
have
put
examples
of
all
the
merge
requests,
widget
and
from
various
different
areas
within
gitlab
and
how
they
are
taking
inputs
from
the
designers
from
the
pms,
and
I
mean
it's
a
very
vast
exercise,
so
it
was
done
in
a
span
of
maybe
a
month,
I
would
say,
and
pedro
is
still
in
the
process
of
analyzing
it,
but
how
it
was
done.
E
It
sounded
pretty
interesting
to
me,
so
it
just
occurred
to
me
that
maybe
we
could
leverage
one
such
technique
to
do
something
for
the
ci
cd
area
as
well
and
like
from
the
top
of
my
mind,
I
had
a
few
thoughts
as
well,
so
I
mean
recently
I've
been
looking
at
more
issues
which
are
not
related
to
pipeline
authoring
for
a
change
like
not
graph
related,
but
everything
else,
and
that's
how
I
discovered
that
there's
a
lot
of
discrepancy
and
inconsistency
in
the
language,
especially
on
the
cicd
settings,
page
like
the
tone
of
voice
for
various
different
sections.
E
It's
not
consistent,
then
other
areas
in
the
past
three
months
I
mean
that's
what
I
know
maybe
before
that.
Also
there
was
a
lot
of
work
done
in
the
mr
widget
area
for
pipelines,
and
I
mean
we
are
coming
up
with
new
solutions,
and
I
myself
don't
remember
like
taking
into
account
all
the
previous
designs
that
have
been
done
and
whether
or
not
we
are
consistent
with
what
other
messages
users
are
seeing
in
similar
areas.
So
I
mean
that's
another.
E
One
then
comes
something
that's
very
familiar
with
everyone,
which
is
the
alerts
that
we
are
surfacing
in
linter
and
previously
also
on
the
pipeline
view
page
not
now
not
not
anymore
and
yeah,
I
mean
how
we
are
framing
those
messages
and
what
format
we
are
following.
A
Better,
I
actually
really
like
that
proposal,
because
we
have
been
slightly
touching
upon
that
with
marcel
and
he
was
sharing
that
this
process
has
led
to
some
really
cool
outcomes.
So
you
know
I'm
thinking
a
little
proposal
here,
maybe
like
which,
if
you
have
a
like
a
start,
a
starting
proposal.
Maybe
it
would
be
worse
just
to
put
it
in
an
issue
and
like
tag
the
whole
city
ux.
We
have
this
little
tag
called
ux
acid,
or
something
like
that.
A
So
we
could
like
reflect
on
your
proposal
and
I
think
like
when
things
are
in
writing.
It
would
be
much
easier
to
grasp
and
also
putting
the
figma
file
there
as
an
example.
So
people
can
view-
and
you
know
kind
of
give
some
time
to
create
some
thoughts.
B
What
do
you
all
think
yeah?
I
just
kind
of
want
to
add
here
that
it's
so
nice
that
I'm
looking
at
the
comments
in
this
file
and
it's
so
nice
that
there's
like
research,
researchers
there's
a
tory
pedro.
There
are
so
many
people
from
different
roles,
leaving
their
feedback
on
the
file
itself.
B
So
it's
a
nice
way
to
to
combine.
I
think,
especially
when
we
do
like
the
think
big
sessions,
or
we
have
some
prototypes
to
discuss.
I
could
definitely
see
the
value
not
only
between
ourselves
as
the
ux
people,
but
also
yeah,
to
bring
this
to
the
to
the
developers.
I'll
definitely
use
something
like
this.
E
Yeah,
so
source
code
team
had
two
versions
of
this
file.
One
was
shared
just
for
the
designers,
the
other
one
was
for
product
managers.
This
one
is
with
the
designs.
Do
you
know
why.
B
Elder
out
of
office
now
I
can
check
with
with
myself
maybe.
E
A
Cool
thanks
for
bringing
that
outfit
for
sure.
I
think
that
could
lead
to
some
nice
new
ritual
here
as
well,
also
make
please
for
free
to
create
an
issue,
so
we
could
like
look
into
something
more
next
point
is
also
yours.
So
back
to
you.
B
This
one
wait
because
it's
yeah,
no,
I
just
wanted
kind
of
like
a
shout
out,
but
also
a
heads
up
that
nadine
made
some
updates
to
the
ux
coverage
process
in
the
handbook,
the
pto
planning
based
on
the
recent
usage
by
dimitri,
and
I
so
yeah.
I
think
it's
actually
super
cool
that
we
had.
B
You
know
data
to
feedback
into
this
process,
so
yeah
thanks
nadia,
but
also
if
you're
planning
your
pto,
have
a
look
and
see
how
how
this
this
issue
template
could
work
for
you,
that's
kind
of
it
neither
doing
vocalize
anything
or
I
can
just
jump
to
my
next
one.
Thanks.
A
For
bringing
that
up,
you
know
I
feel
like
yeah,
that's
good,
that's
definitely
a
new
process
and
I
felt,
like
you
know,
maybe
even
within
the
future
usages
of
that
I
will
have
some
great
feedback.
So
let's
make
sure
we
iterate
on
this
and
add
the
updates
to
that.
I
forgot
actually
to
mention
this
edition.
So
thanks
for
bringing
it
up
hannah.
B
Cool
and
jumping
to
cross
stage.
My
first
point
is
about
the
dora
forum
metrics
in
gitlab.
I
always
think
about
dorado
explorer
when
every
time
I
google
it,
I
just
get
images
of
door
the
explorer
yeah.
So
we
are
splitting
some
of
the
functionalities,
some
of
the
features
between
progressive
delivery
and
release
management.
B
There
was
a
call
I
think,
a
week
ago,
dmitry
were
you
in
the
call.
I
think
you
were
still
out
of
office
right.
B
B
B
We're
gonna
add
this
new
section
at
a
group
level
and
a
new
navigation
menu
and
everything
to
display,
like
some
four
widgets.
For
now
that
would
display
some
of
the
metrics
and
then
progress
delivery
would
take.
Two
metrics
and
release
management
will
take
another
two:
we're
not
gonna
redesign
anything
or
really
create
any
new
dashboard
experience.
B
So
this
is
going
to
be
an
opportunity
for
us
to
cross-collaborate
with
analytics
a
little
bit
outside
of
our
release,
comfort
zone.
G
When
kenny
kenny
mentioned
this
to
me
randomly
in
a
meeting
somewhere-
and
he
mentioned
at
the
time
that
tori
he
thought
so
at
the
time
he
he
he
envisioned
it
as
much
more
less
divided
less
like
here's
for
two
metrics,
here's
two
metrics!
G
So
that's
fine,
but
I
was
wondering
if
ultimately,
where
we're
going
with
this
is
a
much
more
deeper
understanding
of
all
of
the
different
personas
who
might
be
leveraging
the
information
on
the
page
and
needing
to
go
deeper
from
a
design
standpoint
around
that
so
not
just
surfacing
what
we
have
right
now,
really
trying
to
understand
how
those
different
personas
would
use
the
information
and
figure
out.
Does
that
mean
it
changes
how
it's
presented
or
used
or
interacted
with?
B
B
G
B
Buyer
group,
you
know
manager,
persona,
so
yeah
release
managers
kind
of,
but
the
focus
is
in
the
people
that
want
to
get
upgrade
their
gitlab
tire
and
leverage
of
more
of
these
metrics.
For
now,
that's
what
I
understood.
G
B
A
Actually,
lori,
that's
a
good
point.
I
remember
yeah.
I
have
been
starting
to
discuss
that
with
orit
and
with
kenny
that
he
planned
like
to
have
a
person
from
the
ux
department
who
would
help
like
kind
of
like
to
uni,
unify
this
whole
activity
around
dora
for
metrics
among
cicd,
and
I
remember
also
he
was
mentioning
tori,
so
I
I
don't
know
maybe
hayan.
A
I
don't
know
just
to
see
that
we
are
trying
to
build
this
from
the
really
cross
stage
way
of
thinking.
B
Yeah,
I
think
that's
a
future
plan
nadia
like
okay,
expand
and
then
do
really
the
linking
between
the
stages.
For
now
it's
bringing
the
data
we
have
in
the
back
end
and
showing
the
analytics
page
we're
not
even
like
designing
anything,
we're
just
reusing.
You
know
the
funky
ui
that
we
have
in
analytics
and
in
this
epic
that
are
linked
here.
B
There
is
a
list
of
issues
about
the
next
steps
right
about
creating
not
only
new
features,
but
also
adding
like
the
necessary
features,
for
example,
for
the
ultimate
tire,
which
will
mean
that
we
need
to
connect
this
with
configure
and
with
other
stage
groups.
So
I
think
the
investigation
right
now
an
investigation
of
that
the
direction
is
it's
really
minimal,
but
this
information
is
there.
I
also
still
need
to
to
consume
everything.
A
B
And
next
yeah,
just
a
heads
up,
dimitri
and
I
are
wrapping
up
the
three-year
release,
vision
box.
We
work
on
this
before
my
pto
or
dimitra's
video,
some
videos,
so
there's
a
figma
file
here.
If
you
want
to
review
and
next
week
we
are
showcasing
these
two
pms,
because
the
intention
is
that
they
can
use
the
clickable
figma
prototype
to
record
some
sort
of
showcase
that
they
can
share
with
the
sales
people,
but
also
add
to
the
vision
page
to
the
handbook
page.
B
E
Oh
because
you
had
put
the
link
there,
so
I
thought
that
maybe
I
should
I
want
to
oblige
to
do
that,
so
so.
This
exploration
for
which
the
link
I've
just
I've
posted.
It
only
has
like
very
initial
level,
explorations
it
kind
of
chalks
out
the
features
that
we're
planning
to
put
in
there.
But
this
kind
of
touches
upon
my
next
point,
which
again
ties
back
to
your
conversation
about
cicd
dashboard
that
I
would
be
talking
after
a
couple
of
points
down
this
agenda.
A
A
I
know
that
pretty
much
everyone
is
busy
with
the
three-year
visions,
so
we
just
discussed
with
with
ian
today
that
he
and
team
are
also
doing
some
awesome
stuff.
I
know
that
ron
and
james
were
doing
some
amazing
things
so
yeah.
If
anyone
wants
to
share
any
experiences
between
each
other
feel
free
to
reach
out.
There's
a
lot
of
cool
stuff
happening
there,
cool
all
right
over
to
user
research.
Laurie.
Your
first
point,
which
we
kind
of
like
discussed
here
but.
G
Yeah
so
nadia
you
were
going
to
do
the
pipeline
research
for
or
eat
so
she's
been
out
of
office
for
various
reasons
until
about
the
10th
of
october.
But
since
you're
leaving
and
you're
going
to
be
gone
for
about
a
week
between
now
and
when
you're
gone
gone,
I
just
wasn't
sure.
G
I
know
the
reason
that
you
wanted
to
take
it
over
for
a
because
it
was
because
she
didn't
have
a
lot
of
time
and
I'm
not
sure
how
much
time
she
will
have
when
she
does
come
back,
and
I
know
dimitri's,
focusing
on
the
a
b
testing
and
some
other
activities.
So
I
can't
take
it
on
unless
we
want
to
move
it
out
to
november,
but
yeah.
A
Yeah,
you
know
good
point
very
good
point.
I
was
already
thinking
about
that.
I
was
kind
of
hoping
that
we
can
start
with
the
sessions
in
october,
but
I
understand
that
it's
a
bit
of
like
unrealistic
timeline,
also
taking
into
account
my
weak
pto
yeah.
Let's
bring
this
up
next
week
with
reid,
but
also
what
do
you?
A
Maybe
this
is
a
question
that
also
will
be
useful
for
everyone
else
if
we
like,
if
the
pm
and
the
product
designer
do
not
have
a
capacity
to
take
on
the
research,
and
we
have
the
researcher
on
the
stage
busy
do
you
think
we
should
be
addressing
that
to
adam
or
like
to
anybody?
Just
kind
of
like
to
hey
reflects
that?
Yes,.
G
I
don't
know
who
to
complain
to
I
don't
everybody
all
I
can
say.
Is
everybody
sid?
I
I
don't
know
who
will
who
will
hear
it
enough
to
grant
christy
the
head
count
that
we
need
nothing
set
in
stone
right
now.
I
know
we'll.
We
still
have
a
long
negotiation
for
head
count,
but
she's,
hoping
that
we
can
get
two
more
researchers
for
ops
and
another
recruiter
to
help
emily
since
rupert's
gone
back
to
his
daytime
job
of
being
a
person
recruiter,
but
that's
not
set
in
stone.
G
So
that
could
mean
that
we
could
get
more
people,
but
it
could
also
mean
that
we
don't
get
anybody.
So
I
know
kenny
has
requested
two
additional
researchers
for
ops,
rightfully
so,
but
so
I
don't
know,
I
don't
know
where
the
money
has
to
come
from.
That's
why
I'm
like
who
to
ask.
I
don't
know
like
that's
where
we
have
to
find
out
who
holds
the
pin
in
the
checkbook
to
say.
G
A
I
see
I
will
try
to
well
reach
out
to
adam
valerie
christie,
just
to
make
sure
that
hey
you
know
this
is.
G
And
let
can
you
know
too,
because
kenny
kenny
knows,
but
any
more
that
we
can
tell
kenny,
and
I
don't
know
eric-
I
mean
I'm
not
sure
who
else
to
to
let
them
know,
because
this
is
a
problem
and
I've.
I've
voiced
it
with
adam
before
it's
like
I'm,
I
am
but
one
person
and
there's
lots
and
lots
and
lots
to
do
in
ops
and
if
I'm
busy,
I
can't
help
like
james
wants
help
with
somebody
taking
notes
for
his
session.
G
I
can't
I
don't
even
know
if
I
can
help,
but
at
least
if
he
invites
me,
I
have
a
choice
to
attend,
but
with
stuff
that
tao
and
vithika
are
doing
I'm
committed
to
this
21
person,
usability
test
and
I've
cut
it
run
and
finish
with
andre
by
the
end
of
the
month.
So
I
can't
help
with
that
stuff.
Andre
is
doing
I
can't
or
dmitry's
doing.
I
can't
help
him
with
anything.
So
it's
it's
just
kind
of
catch
22.
A
A
Bad
yeah,
like
you,
your
ex
researchers,
are
such
a
useful
power.
Yeah
I'll
try
to
address
it
from
my
side
as
well,
not
promising
that
you
know
that
it's
gonna
have
immediate
impact,
but
yeah
thanks
and
let's
discuss
this
particular
topic
next
week.
I'll
put
it
to
our
reaction
agenda,
we
say
or
eat
and
don't
end.
G
G
So
we're
going
to
go
back
a
couple
of
steps
and
do
a
usability
test
on
the
process
of
creating
a
green
pipeline
with
the
hopefully
four
four
users
of
four
competitors,
so
travis
circle,
ci,
github
and
jenkins,
and
what
the
concept
will
be
is
that
they
will
have
code
from
their
platform.
They
use
to
do
a
pipeline
of
some
sort
of
test.
I
don't
know
whatever
the
coders
decide
developers
decide
and
they
will
need
to
recreate
that
code
in
gitlab.
G
This
was
determined
that
it
was
a
very
off
of
used
scenario
and
they
will
have
free
reign
in
the
sandbox
of
get
lab
to
look
at
docs
google
things
if
they
need
to
whatever
they
need
to
do
in
order
to
make
it
a
successfully
run
pipeline.
So
we're
going
to
give
them
an
hour,
and
hopefully
it'll
be
a
pretty
simple,
like
test
pipeline
that
they
have
to
redo.
So
we'll
see
how
that
goes,
but
we've
never
actually
tested
the
entire
the
entire
process
of
doing
that.
G
So
that's
what
we're
going
to
be
doing,
hopefully
starting
the
14th
or
the
21st,
but
I
have
nobody
to
recruit
for
my
two
I'm
doing
circle
and
travis
and
there's
nobody
on
respondent
who
qualifies
so.
I
think
I
think
andre
has
like
nine
or
ten
to
choose
from.
So
I
think
he'll
be
fine,
but
my
part
may
take
a
little
bit
longer.
G
A
G
H
Yeah,
I
was
you
were
saying:
there
was
no
research
on
pipeline
creation.
There
has
been
some
in
the
past,
but
I
don't
know
if
that
has
been
considered.
G
Not
any
holistically,
I
think
so
part
of
the
cms
is
that
it's
not
a
usability
test
right,
so
you
should
have
at
least
done
a
scorecard
or
something
from
a
holistic
standpoint,
and
we
hadn't
done
that
yet
so
we
went
ahead
and
decided
to
do
that.
Especially
to
your
point.
It's
been
a
while
things
may
have
changed.
Let's
just
go
ahead
and
get
a
new
baseline
and
see
see
what
we
can
find
out
yeah.
G
So
that's
going
to
take
a
lot
of
my
time,
at
least
as
soon
as
my
things
get
scheduled
and
viticus
is
kind
enough
to
see
if
she
can
set
up
a
environment
for
us
and
dove
and
nadia's
have
been
also
helping
to
identify
people
who
can
help
us
internally
code,
those
pipelines
for
the
four
different
competitors.
So
I'm
managing
all
of
that
as
well.
A
Busy
times
crazy
thanks
vitica
for
offering
support
there
same
tonight,
I.
G
A
E
E
You
yeah,
so
this
is
again
the
point
where
I
mean
in
our
previous
research
meeting
for
a
ci
cicd.
Is
it
cn
with
a
like
tom?
I
mentioned
that
you
would
be
con
conducting
a
problem,
validation,
research,
around
dashboards,
and
I
expected
that
to
happen
because
there's
been
a
lot
of
ask
around
it
and
in
the
three
years
vision
the
concepts
that
I
came
up
with.
E
That's
a
part
of
it
and
she
agreed
that
it
would
solve
like
it's
good,
it's
very
useful
to
have,
but
I
mean
in
terms
of
metrics
and
aligning
with
what
hayana
and
jackie
had
already
done.
I'm
not
sure
how
much
we
are
in
sync
with
that
and
invite
after
that
meeting
I
have.
E
I
don't,
have
any
update
further
about
what's
happening
on
that
front,
so
I'll
make
it
a
point
to
remind
tao
to
open
an
issue
yeah,
but
I
I
was
really
curious
that
what
all
should
we
keep
in
mind
like
what
previous
research
that
hannah
and
jackie
would
have
done
or
lori
is
aware
of
that.
We
should
keep
in
mind
before
we
venture
into
creating
a
whole
new.
I
mean
conducting
a
whole
new
problem,
validation,
research.
B
Yeah,
can
you
give
us
a
little
bit
of
context
of
ithaca
of
what
this
dashboard
will
look
like,
because
you
know
it
sounds
like
just
a
name.
It
sounds
like
the
same
thing
as
as
we
are
beauty
for
release
management.
So
if
you
can
clarify.
E
Right,
so
if
you
click
on
that
figma
link
that
I
have
posted
for
three
year
version,
you
would
see
that
I'm
proposing
that
on
the
pipeline
new
page,
instead
of
like
putting
scantily
the
content
on
the
upper
half
of
the
page,
we
can
use
that
for
dashboard
as
well
like
showing
a
few
information
such
as
the
usage,
the
storage
consumption
or
the
job
execution,
duration
or
whatever,
is
very
critical
for
users
to
look
at
around
that
time.
But
that's
my
limited
understanding
of
what
is
expected
from
the
dashboard.
Of
course.
E
Yeah
I
mean
tower
did
mention
that
she
does
want
to
sync
with
jackie
on
this,
but
I'm
very
sure
that
hasn't
happened
yet
yeah.
But
I
was
just
curious
like
if
you
can
point
us
to
something.
B
Yeah
I
adhere
to
the
to
the
agenda
some
of
the
the
links
so
the
cic
director
dashboard
dashboard,
which
was
our
main
issue
and
then
jackie,
did
a
whole
opportunity.
Canvas
which
is
the
problem
validation,
phase
on
it
and
the
the
background
context
context
is
really
around
deployments.
B
So
I
think
in
a
sense,
you
might
want
to
connect
that
to
the
findings
that
we
already
have
and
also
we
have
customer
interviews,
we
did
solution,
validation.
I
did
prototyping
and
there's
a
dovetail
project
about
that.
B
I
would
highly
recommend
tao
and
jackie
to
sync
up,
because
the
decision
made
for
the
director
level
or
the
cicd
group
dashboard
is
that
we
just
want
to,
as
I
said,
before,
leverage
of
existing
dashboards
existing
metrics
rather
than
creating
a
new
one,
because
that
was
the
main
feedback
from
our
users
or
customers
that
they
don't
want
to
go
anywhere
else
and
trying
to
figure
out.
You
know
more
metrics
on
whatever
project
level.
They
want
to
have
this
overview
and
a
single
entry
point
for
everything
around
the
project.
B
So,
for
example,
if
now
ci
and
the
pipeline
is
something
that
would
also
be
part
of
the
cicd
dashboard
vision,
I
think
that
it
would
be
nice
for
them
to
have
a
conversation
and
see
where
this
can
yeah
they
can.
They
can
live
in
harmony
rather
than
you
know,
in
a
different
area.
E
All
right,
so
I
would
share
all
of
these
information
with
jar
when
she's
back.
E
And
yeah
thanks
laurie
for
making
me
aware
of
the
timelines
I'll
make
sure
we
added
that.
G
Yeah
it's
it's
kind
of
hard.
If
you
don't
have,
if
you're
not
doing
internal
people
or
you
don't
have
like
customers
all
lined
up,
we
just
need
some
time.
So
I
worry
when
I
see
in
the
next
milestone,
because
that's
only
like
four
weeks,
so
I
just
want
to
make
sure
you
have
enough
time
to
to
recruit
right.
A
A
Sounds
like
a
bit
of
quietness
and
then
yeah
just
to
raise
this
quickly,
for
maybe
next
five
minutes
or
whatever,
who
has
more.
We
haven't
like
been
discussing
any
kind
of
like
retrospective
stuff
in
quite
some
time,
just
wanted
to
give
this
opportunity
for
us
to
talk.
Let's,
let's
go
over
these
three
points
like
well,
a
bt
yeah
sure
drop
hyanna.
I
you
mentioned
that
just
wanted
to
say.
E
I
have
something
I
mean
after
a
couple
of
milestones.
I
had
a
very
well
managed
milestone
and
they're
really
less
and
in
the
beginning
I
was
like
so
confused
what
to
do
with
my
free
time.
E
A
What
what
did
what
helped
you
vitica,
what
like?
What
did
you
do
to
achieve
this?
This
point
in
your
world.
E
A
I
I
think
we
we
had
some
like
good
some
good
syntax
sessions
regarding
the
like
three-year
vision
thing.
You
know,
at
least
that
was
pretty
helpful
for
me
and.
I
There's
still
kind
of
like
one
thing
that
never
was
clear
to
me,
which
is
like
like
if
we're
ever
gonna
like
integrate
all
these
bishop
marks
into
just
like
one
vision.
I
I
see
it
seems
that
everyone
right
now
is
working
on
silos
in
each
niche
tool
in
each
of
the
features
and
the
under
group
stages,
but
yeah.
I
think
like
at
least
the
the
initial
scene
cup.
I
I
learned
a
lot
from
from
from
that,
so
maybe
those
should
become
something
like
like
something
that
has
like
a
cadence.
You
know,
because
you
learn
a
lot
from
that
and
I
think
we
think
from
for
doing
that.
You
were
you,
you
actually
were
the
one
who
did
those
meetings
and
everything.
E
I
think
I
can
comment
on
that
one.
I
have
a
little
sense
of
what
direction
this
is
going
in
so
for
now,
what
I
know
is
like
tom
and
I
we
are
working
on
the
ci
part,
then
dove
and
I
nadia
they
are
looking
for
the
pipeline
authoring
part.
But
what
we
are
doing
is
in
the
figma
file.
We
are
working
on
the
holistic
flow
and
we
are
marking
the
features
which
would
be
taken
care
of
by
the
other
team
and
that
we
are
going
to
discuss
in
our
specific
meeting.
E
I
think
jason
is
organizing
something
mid
mid
october
after
nadia
is
back
from
our
vacation.
I
But
no
like
in
like
joke
sites,
I
think,
like.
I
think
that
that's
a
pretty
cool
thing
to
keep
doing
somehow.
You
know
like
just
checking
that
everyone
is
like.
What's
her
vision,
how
is
it
changing
and
how
are
we
aligning
towards
that
and
like
are
we?
I
You
know,
I
think
the
greatest
value
that
I
got
out
of
that
was
like
understanding
where
everyone
like
what
problems
is
everyone
trying
to
fix
and
like
how
how
my
group
can
like
contribute
to
that
you
know
or
tie
back
to
that
you
know,
so
I
think
they
should
be.
They
should
be
on
something
regular
just
for
the
sake
of
just
because
they
are
so
so
valuable
for
that
forgetting
context.
A
It
was
a
good
question
juan
about
you
know,
merging
those
and-
and
I
see
how
holistically
dimity
and
hannah
work
in
the
release
as
well,
and
actually
I
would
be
even
curious
if
we
would
want
to
be
aligning
in
the
ci
cd.
Maybe
that's
the
question
that
I
should
address
to
kenny
as
well
like?
What's
the
what's
the
vision
there
because
yeah
that
those
things
should
not
exist
like
any
separate,
separate
vacuums
but
yeah
good
one
to
address.
I
Yeah,
especially
because
they
have
like,
like
I
have
been
working
on
dashboards,
you
know
and
there's
like
a.
I
have
a
big
mission
for
dash
person.
There's
likely
many
other
things
that
are
gonna,
be
dashboards
in
other
parts
of
the
stage.
So
how
how
would
like?
I
I
think,
I'm
aware
of
that,
but
I
don't
know
how
we're
gonna
like
end
up
merging
everything
into
like
maybe
like
this
is
there's
gonna,
be
just
like
a
dashboard
view
or
something,
and
then
you
know,
I
feel
until
there's
a
little
bit
of
lack
of
contextualization,
of
how
we
end
up
making
everything
meet
together.
You
know.
E
Yeah,
that's
a
very
valid
point.
I
mean
at
some
point
I
would
love
to
sync
with
dmitry
and
here
and
if
possible,
at
some
time
with
the
larger
team
in
gitlab.
But
that's.
A
Yeah,
well,
I
think
it's
nice
also
to
be
leveraging
your
actual
cases
for
showing
your
three-year
vision
work.
You
know,
like
that's
a
nice
idea
for
the
presentations
for
the
future,
so
feel
free
to
share
that
and
yeah.
I
I
still,
I
think,
that's
a
great
question
to
address
your
product,
because
that
I
think
the
thinking
also
could
be
coming
from
like
that
level
as
well
cool.
I
know
we
don't
have
much
time,
but
still
just
wanted
to
address.
A
At
least
you
know
that
this
portion
of
the
kind
of
like
a
retro,
we
talked
about
the
good
things.
Maybe
somebody
faced
any
challenges.
You
know
like
yeah
any
help
or
any
support,
that's
needed
anything
at
all
in
your
stage
group
in
in
in
overall
in
our
team,
whatever.
E
E
So
it
was
very
difficult
to
keep
a
track
of
the
issues
that
we're
working
on
and
it
led
to
a
lot
of
confusion.
So
at
one
point
I
had
no
idea
it
felt
like
everything
that
I
was
working
on
that
was
in
process.
I
wasn't
supposed
to
touch
them
at
the
first
place
and
it's
good
that
all
the
confusion
got
cleared
out
and
I
hope
it's
there
in
the
documentation
as
well
I'll
check
that
again,
but
yeah
that
was
kind
of
confusing.
A
E
A
Well,
lori,
we
heard
from
you
that
we
need
more
ux
researchers.
This
is
something
that
I
still
I
promise
to
address.
So
I
will
add
that.
B
B
A
Seems
like
there
is,
or
nothing
else
or
there
is
nothing
more
to
share
people
just
don't
want,
and
I
will
take
that
as
well.
It's
time
to
wrap
this
up
thanks
a
lot
for
attendance.
It
was
really
really
nice
collecting
everyone
again
together.
Great
conversations
thanks
for
bringing
things
up
and
yeah
I'll
share
the
recording
later
or
those
who
have
not
been
here
thanks
a
lot
have
a
good
rest
of
the
day.
We
chat
soon.