►
From YouTube: CI/CD UX Team - 2021-11-03
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
Awesome
so
this
is
the
cicd
ux
meeting
for
november
3rd.
So
I
want
to
start
talking
about
the
talent
assessment
you
might
have
seen.
I
shared
with
you
some
spreadsheets
that
are
going
to
be
used
for
this
quarters
round
of
performance
reviews,
performance
evaluations.
A
B
I'm
trying
to
understand
if
I
have
any
questions
about
it
or
not,
because
there's
been
lots
of
kind
of
new
things
coming
up
around
the
talent
assessment
and
a
bunch
of
training.
So
for
for
this
particular
thing,
we
basically
just
need
to
read
some
materials
and
then
fill
out
the
performance,
worksheet
kind
of
like
our
own
input
or
like
understanding
of
how
we're
doing
and
then
be
ready
to
discuss
it
with
you
in
a
one-on-one.
Is
that
correct.
A
That's
right,
I'm
asking
everyone
to
read
the
handbook
pages
because
we
changed
the
process
again
so
last
year.
If
you
remember,
we
did
use
the
spreadsheets
right
and
you
fill
in
for
some
examples
of
how
you're
performing
in
specific
responsibility
and
you
grade
it
yourself
right.
It's
the
same
exercise,
it's
the
same
dynamic
this
time,
but
now
we
introduce
the
growth.
A
So
it's
not
just
about
performance.
So
what
I
need
from
you
is
that
you
understand
growth
right
and
you
understand
how
you're
going
to
be
in
a
sense
evaluated,
but
also
for
performance,
and
let
me
open
the
handbook
page
here
where
we
say
is
performing,
is
growing
performing
and
exceeding,
if
I'm
not
mistaken.
A
So
let
me
click
here,
yeah
developing
performing
exceeding
so
pretty
much.
You
need
to
understand
what
those
are
so
that
you
can
grade
yourself.
You
can
assess
yourself
and
we're
going
to
have
that
discussion
synchronously
next
week,
so
that
we
can
move
forward
with
the
process,
but
the
dynamic
itself
isn't
different,
but
how
we
are
labeling
performance
and
growth.
It's
it's
important
to
understand
is
that
clarifying
yeah.
B
Yeah
makes
sense,
and
one
more
thing
that
I
wanted
to
clarify.
Yesterday
we
had
a
meeting
with
valerie
and
the
topic
of
talent
assessments
came
up
and
she
mentioned
that
she
doesn't
expect
us
to
come
up
with
a
lot
of
examples
for
every
category
that,
unlike
last
year
now,
we've
recently
gone
through
360
reviews
and
so
on.
So
it
would
be
sufficient
to
kind
of
lightly
touch
upon
those,
and
I
don't
know,
maybe
like
add
one
example.
What
are
your
expectations
here?
Yeah.
A
So
that's
correct
right.
We
went
through
that
process
recently
and
I
also
put
together
a
document
for
each
of
you
for
the
360
feedback
with
yeah
the
highlights
and
the
areas
for
growth
etc.
So
we're
gonna
use
that,
but
if,
for
some
reason
something
happened
and
you
have
a
new
example
since
one
day
we
finished
that
we
finished
that
in
september
that
you
want
to
highlight
right
feel
free
to
put
that
in
the
sheet.
I
think
it's
important
for
us
to
when
looking
at
the
document
asynchronously
and
when
coming
together.
A
What
I
want
to
discuss
is
that,
if
you
put
for
example
yourself,
you
should
assess
yourself
as
developing
or
I
don't
know
if
yourself
is
exceeding-
and
I
do
developing,
then
what
are
the
examples
that
we're
looking
at
right
so
that
we
can
have
a
starting
point
for
that
discussion.
A
I
think
that
would
that
would
facilitate,
but
indeed
don't
need
to
go
into
a
lot
of
detail,
but,
on
the
other
hand,
gina
and
kaiden
are
here,
but
they're
going
to
do
that
for
the
first
time
and
they
were
not
part
of
the
360
feedback.
So
for
them
it's
important
that
yeah
they
bring
examples.
So
I
think
we
need
to
balance
that
out,
based
on
the
context
that
we
have
shared.
C
A
I
shared
with
you.
Let
me
share
it
again
on
drive,
so
I
think
the
one
that
is
in
the
handbook
is
not
the
one
that
we
are
using,
adding
I
create
a
copy
for
that
and
share.
Let's
see.
Oh
it's
already
everything
I'm
gonna
copy
here.
The
link
I'm
just
going
to
drop
here
in
the
in
the
agenda.
A
The
files
are
here
are
private
right.
They
are
catered
to
you,
so
we
are
the
only
ones
that
have
access
to
it.
What's
going
to
happen
is
that
maybe
valerie
explained
that
yesterday
I
wasn't
there
that
managers
are
going
to
come
together
and
going
to
do
right,
a
calibration
session
and
yeah
we're
going
to
use
the
same
template
that
rose
already
created
that
I
don't
think
you
have
access
to.
A
I
don't
think
you
will
have
access
to
industry,
for
managers
to
do
the
calibration
and
to
see
where
people
are
and
discuss
growth
and
performance.
A
But
the
last
part
I
want
to
highlight
is
that
something
different
we're
going
to
do
right.
It's
in
here
in
the
issue,
description,
add
the
highlights
large
in
the
dock
right,
two
three
strains
accomplishments,
two,
three
improvement
areas,
anything
else
noteworthy
so
in
case
we
already
had
that
documented
based
on
the
360
feedback,
just
copy
paste
that
or
just
bring
some
topics
to
this
question,
because
these
these
three
questions
right,
these
three
areas,
the
strengths,
improvements
and
anything
that
impacted
you.
For
example,
you
were
recently
promoted.
You
have
a
covey
impact,
etc.
A
It's
what's
going
to
be
brought
to
this
question
during
the
calibration
session,
but
you
can
go
into
detail
on
that
and
you
can
write
that
or
polish
that
together.
A
Then
I
also
want
to
review
together
the
q4
okrs
for
cicd.
So
here
link,
I
haven't
checked
the
agenda
for
yesterday's
ux
fall,
but
I
assume
that
christy
did
she
talk
about
it
yesterday,
let's
see
yes,
she
did
so
any
outstanding
questions.
Anything
that
you
would
like
to
discuss
as
a
group
as
well
than
its
verification.
B
That's
all
I
want
to
say,
but
it's
also
exciting,
very,
very
exciting,
I'm
very
happy
to
see
the
focus
on
usability
and
all
of
the
discussions
around
ui
polish.
A
So
it
does
look
like
a
lot.
A
lot
of
the
things
are
follow-ups
from
last
quarter,
so
psychological
training,
you're
gonna,
have
to
do
that.
Right.
We
are
gonna
have
to,
for
example,
keep
reviewing
emergency
quests,
keep
addressing
ux
app,
that's
something
that
we
are
doing
in
a
way
organically
and
for
our
team
in
particular,
we're
going
to
be
tracking
that
right
as
part
of
that's
a
kpi.
A
For
the
the
maturity
category,
which
is
the
the
job
to
be
done,
and
also
the
the
heuristic
evaluation,
I
try
to
work
with
design
managers
to
balance
it
out.
So,
for
example,
let's
quarter,
I
think
nadia
and
katie
hadn't
done
a
specific
ar.
So
we
swapped
that
so
that
vitica
and
dalio
and
gina
didn't
have
to
do
again
this
quarter
and
which
is
the
evaluating
experience
of
making
recommendations
and
the
merchandise
we
did
is
going
to
be
a
carryover
in
particular
for
gina.
A
B
A
Yeah,
that's
right,
so
we
need
that
exercise
right
of
assigning
severity
to
these
issues
and
well
for
verify.
In
particular,
we
picked
sure
kr
how
much?
How
much
did
we
commit
to
25
of
all
that
10
percent
capacity,
but
with
the
share
kr
is.
Let
me
open
here
is
around
kelly
25
yeah,
I'm
gonna
link
here
you
can
find
all
of
this
information
in
live
by
the
way.
A
A
That
doesn't
mean
that
runner
is
not
going
to
be
tackling.
What's
that,
it
means
that
the
front-end
engineers
back
engineers
are
going
to
be
working
and
pm
will
be
assigning
that
workload
across
the
team,
so
that
verify
as
a
whole
can
deliver
25
of
the
issues
across
the
stage,
but
for
release
and
for
package.
That's
a
conversation
with
daniel.
We
need
to
keep
influencing
the
the
the
planning
and
the
milestones
so
that
yeah
we
can
close
those
issues
and
address.
A
So
indeed,
it's
a
conversation
with
pms
and
try
to
inform
that's
what
we
can
do
right.
It's
to
prepare
the
issues
make
sure
that
they
are
ready
for
development
and
work
with
pms
to
help
prioritize
those.
B
A
And
things,
let
me
know
if
you
need
any
help
there
for
verify
in
particular
nadia.
This
is
part
of
the
product,
krs
right,
so
yeah,
it's
a
commitment.
So
if
this
is
not
being
planned
or
prioritized,
yeah
voice
that
concern
and
just
work
with
love
to
have
at
least
one
that
wants
for
car
recommendation
based
on
the
severity
of
these
items,.
D
E
Is
my
mic
working
now
all
right,
yeah
but
yeah?
I
think
the
I
agree
with
maggie's
issues
like
a
lot
and
yeah
just
voicing
something
that
that
hyuna
had
raised
before
like
collaborating
with
product
to
make
this
part
of
the
milestone.
Instead
of
extra
work.
We
have
to
do
on
the
side
as
us
designers,
because
otherwise
it
just
became
stuff
of
the
work
and
gets
possible.
A
Yeah-
and
I
agree
it
can't
look
a
lot
right,
but
nothing
that
we
are
putting
here
on
the
designer's
plate
is
extra
work,
so
we're
talking
about
maturity
of
your
categories,
we're
talking
about
we're,
losing
the
jobs
to
be
done,
we're
talking
about
prioritizing
this
usability
issues,
but
also
the
scorecard
recommendations
from
all
the
scorecards
that
you
have
done
in
the
last
couple
of
months.
So
it's
getting
everything
that
is,
it's
ready
to
be
served.
Let's
put
it
like
that
and
put
it
on
the
table
right.
A
So
you
don't
want
all
this
effort,
especially
when
it
comes
to
research
or
what
we
discover
insights,
that
we
discovered
that
impacted
his
ability
to
go
into
the
backlog.
We
want
to
have
design
informing
the
priorities,
help
inform
them
and
have
a
you
know,
an
organic
flow
right
now.
Things
are
in
the
same
way
influenced
by
through
the
krs,
but
what
you
want
to
do
to
have
is
just
a
regular
organic
flow
for
these
activities
in
the
future.
A
But
if
you
have
any
thoughts
any
concerning
questions,
please
comment
in
the
issues
and
ping
me
and
then
we'll
continue.
The
discussion
there,
ac
with
the
valerie
and
the
other
dries.
A
I'm
gonna
power
through
here
through
gina's
point
the
next
question
she's
asking
about
which
one
is
this
she's
asking
about
the
oh?
Yes,
the
issue
tracker
for
ux
that
and
the
due
date
right,
if
the
due
date
that
I
added
there
is
when
we
need
to
fill
in
the
issue
put
in
the
issue,
description
or
issue
should
be
completed.
A
I
couldn't
create
an
epic
to
track
that,
because
pms
and
teams
have
their
own
tracking
issues
and
also
the
boards
things
change
and
it's
difficult
for
me
to
see
what's
being
planned
or
what's
completed
because
teams
they
they
have
different
dynamics.
So
what
I'm
asking
from
you
here
is
that,
as
you
start
working
on
a
ux
one
of
these
issues,
right
or
you
know,
that's
going
to
be
delivering
a
given
milestone.
That
has
a
a
due
date
in
a
way
put
that
in
one
of
the
tables.
A
So
this
is
for
you
and
I'll
be
keeping
track
of
this
we're
going
to
be
discussing
during
your
one-on-ones
and
the
due
date.
Is
there
I
put
the
end
of
q4,
so
I
want
to
see
by
you
for
what
progress
did
we
make
right?
What
were
the
issues
that
we're
committing
to
and
let's
say
something
was
not
completed
or
was
moved
out
of
a
milestone?
What
happened?
So
it's
a
way
to
keep
track
of
that.
A
So,
if
there's
anything
that
needs
to
be
improved
in
each
description
or
how
this
process
is
being
made,
let
me
know
so:
we
adjust
it's
the
first
time
we're
doing
that
for
everyone
in
ci
cd,
so
trying
to
experiment
it
a
little
bit
daniel.
A
Yes,
I'm
working
with
ux
management
to
have
a
board
in
in
periscope,
so
not
here
per
se,
but
then
have
that
data
and
pulling
everything
from
the
labels
and
also
the
the
group
labels.
But
while
we
don't
have
that,
we
can
start
just
adding
things
here
manually
and
then
we'll
see
in
the
the
next
milestone,
for
example,
if
you
can
still
use
this,
if
it's
tiny,
but
that's
that's.
C
So
this
is
just
an
fyi
that
I
added
the
resources
that
we
were
discussing
about
in
the
cicd
skills
matrix
discussion
issue
through
this,
mr,
which
is
here,
and
you
can
find
the
merged
the
resulting
page
on
the
link,
the
handbook
page
link
if
there
is
anything
that
I've
missed
or
something
that
is
probably
in
the
wrong
section.
Please
make
that
change
through
an
mr.
A
Please
do
so
take
care
of
yourself
and
don't
worry,
but
thanks
for
the
making
this
change,
it's
really
awesome
and
by
the
way
for
the
skew
matrix
discussion,
I
presented
it.
It's
not
sure
if
you've
seen
the
recording
in
the
ux
leadership
hall,
it
was
really
nice,
seeing
the
teams
and
how
you
know
folks
are
assessing
themselves
quantitative
research.
A
Every
team
was
like
like
skewed
like
this
and
people
really
being
critical
of
themselves,
but
also
do
we
want
to
invest
that's
much
in
quantitative
and
I
think
you
can
see
later
on
the
results,
not
sure
if
this
was
already
shared,
but
I'm
going
to
follow
up
and
continue
the
next
steps
for
our
team,
hopefully
next
week.
So
I'm
going
to
use
these
merger
quests
as
an
inspiration.
So
thank
you.
B
Yeah
so
kind
of
along
the
same
lines
of
constantly
improving
ourselves
and
our
skills.
We
also
currently
have
an
issue
open
around
a
ux
milestone,
planning
and
we've
had
some
really
interesting
discussions
there
sharing
how
we
do
milestone
planning,
what
challenges
we're
experiencing,
what
are
some
opportunities
for
us
to
improve
and
so
on,
and
it
was
very
interesting
to
see
how
our
process
varies
and
I
think
there
were
lots
of
good
tips
that
came
out
of
those
discussions
as
well.
B
So
this
week
we
will
still
keep
the
issue
open,
so
you
can
still
weigh
in
if
you
have
any
suggestions
or
thoughts,
and
at
the
end
of
this
week
we
will
identify
action
items
and
probably
propose
a
handbook
update
as
well
with
some
tips
and
resources,
not
sure
yet
what
it
will
look
like,
but
we
will
find
a
good
place
where
it
can
be
helpful
not
only
to
our
team
but
also
to
those
outside
of
cicdux.
E
I
just
wanted
to
say
thank
you
for
opening
this
discussion
now
yeah,
I'm
always
happy
to
see
you
opening
discussions
about
process
and
and
designing
how
we
work,
you're,
really
good
at
this.
Basically
doing
it
and
yeah
I'll
leave
my
comments
before
the
end
of
my
week.
So
so
they
can
be
integrated
as
well.
C
Thanks,
I
appreciate
it.
Danielle
yeah
I've
not
been
able
to
get
to
this
as
well,
but
I
definitely
had
some
ideas
like
I.
I
have
some
thoughts
to
put
down
there.
So
I've
noticed
that
with
while
I'm
transitioning
to
a
different
pm,
I'm
again
having
to
revisit
a
few
things,
so
it
everything
cannot
be
set
in
stone.
C
B
E
Yeah
absolutely
so,
I'm
not
aware
with
all
of
the
points
here,
but
the
first
is
reviewing
research
final
discussion
for
an
issue
in
dependency.
Proxy
ui
katie
left
a
comment
here.
So
let's
get
to
the
next
one,
because
that's
what
I
know
the
most
so
will
is
working
with
calvi
to
identify
customers
to
interview
to
understand
the
reasons
why
customers
are
not
using
gitlab
to
deploy
right,
so
specific
customers
that
use
gitlab
up
until
verify
or
c
high
and
then
not
for
deployment.
E
So
we
have
a
few
conversations
on
that,
but
it's
been
hard
to
to
get
really
good
customers
to
interview
on
this.
So
they
put
out
a
survey.
So
we
didn't
get
good
results.
So
now
they
are
collaborating
with
assays
and
cams,
which
I
forgot
exactly
what
it
means,
but
it's
essentially
the
customer
facing
teams
that
interact
with
our
customers
directly
to
from
them
get
at
least
of
these
customers
to
then
interview.
A
Maybe
the
recent
conversations
that
product
managers
had
in
different
stage
group
with
similar
customers,
so
I'm
not
sure
how
how
will
and
kevin
are
working
looking
at
the
existing
data,
but
would
be
worse
looking
at
the
names
and
some
of
the
people
that
were
already
interviewed,
for
example,
by
jackie
or
by
dove,
and
just
some
some
potential
customers
as
well,
I
think,
would
be
a
good
place
to
start
just
that's
my
initial
thought.
Anyone
else.
B
That's
a
really
great
point:
dove,
always
interviews
a
lot
of
customers
and
while
we
mostly
focus
on
pipeline
authoring,
workflows
and
usership
templates,
I'm
sure
release
comes
up.
So
you
I
will
share
some
dovetail
videos
with
you
recordings,
so
you
can
have
a
look
if
there
are
any
insights
there
for
you.
B
C
I
I
have
a
project
that
I'm
linking
here,
which
is
dovetail
so
it's
it's.
It's
a
it's
an
effort
that
many
people
are
participating
in
right
now.
It's
to
understand
the
cross-stated
option
for
small
and
medium
businesses,
and
there
are
many
different
kind
of
organizations
that
we
have
spoken
to
so
far.
So
it's
a
very
it's
a
goldmine
of
all
kinds
of
information.
E
Yes,
thanks
for
sharing
that
I'll
I'll
tag
will
in
in
a
comment
here
to
make
sure
he
sees
it.
The
the
customer
that's
listed
in
in
the
issue
already
is
based
on
an
interview
by
vitica
and
jackie.
So
it's
already
like
the
first
first
data
point
from
this,
so
they
might
reach
out
again
to
that
customer.
Just
talk
specifically
about
this
topic,
but
yeah
I'll
ask
bill
to
go
over
the
other
interviews
as
well
to
see
if
there
are
more
valid
customers
for
this.
E
All
right
looks
like
our
next.
I
have
a
make
a
comment
here.
I
was
gonna
suggest
a
while
back
that
we
shuffled
the
order
of
these
entries
every
now
and
then
because
I
realize
I
have
a
lot
of
time
in
the
beginning
and
then,
if
the
meeting
drags
on
for
too
long,
vitica
or
whoever's
at
the
end
has
usually
less
time
that
you
have
to
wrap
up
so
shuffling
sometimes
can
be
good.
Also
I'll
get
some
questions
for
being
the
first
ones.
E
So
there's
that
yeah
my
two
points
for
today,
a
small
update
on
the
new
designs
for
the
environment
page
I'm
happy
to
have
it
finally,
wrapped
up
with
all
the
feedbacks
that
we
had
along
the
way
and
also
towards
the
end
from
jeremy
and
hayanna.
I
had
to
spend
some
extra
time
incorporating
incorporating
these
feedbacks
and
make
sure
they
were
broken
down
downstream
into
the
issues
from
the
epic.
E
I
would
definitely
try
to
write
down
some
of
my
learnings
on
this,
because
my
process
has
been
designing,
figma
and
then
exporting
my
proposals
from
the
artboards
into
design
management,
which
I
think
works
well
for
small
and
medium
issues,
but
then
for
larger
issues
and
especially
issues
where
you
have
multiple
iterations
of
the
same
design.
You
can
get
really
tricky
to
to
manage
the
versions
of
your
design
and
and
where
the
feedback
goes
in,
these
versions
right.
So
one
thing
that
happened,
for
example,
was
me
moving
from
one
layout
to
a
radically
different
one.
E
Instead
of
duplicating
and
creating
a
new
iteration
in
design
management,
I
just
overrode
the
previous
one.
So
a
lot
of
the
comments
lost
lost,
meaning
because
the
anchors
in
the
ui,
where
they
were
pointing
to
were
gone.
So
that's
one
thing
that
that
needs
to
improve
and,
on
a
broader
scale,
the
fact
that
this
was
a
large
issue
that
then
was
promoted
to
an
epic
meant
that
everything
from
the
issue
was
escalated
to
the
epic,
except
for
design
management,
which
I
think
is
not
available
in
ethics.
E
E
So
what
I
did
was
I
finished
incorporating
the
feedbacks
reopened,
the
original
issue
for
that
and
then
now
that
I'm
done,
I
close
it
again.
Close
every
single
comment
thread
on
the
original
design,
management,
markups
and
and
moved
the
designs
to
the
specific
issue.
So
any
new
discussion,
especially
towards
implementation,
will
happen
on
the
specific
issues
rather
than
the
big
one
that
doesn't
make
sense
anymore.
E
A
And
I'm
not
just
sharing
your
thoughts
anymore.
I
think
this
is
a
good
vlog.
This
is
dog
foodie
right,
so
it's
a
good
opportunity
for
you
to
bring
this
up
when
if
it's
an
issue,
whatever
type
of
whatever
deliverable
it
share
those
insights
so
that
we
can
improve
the
ux
design
management
to
our
own
workflows.
That's
the
whole
goal
of
having
that
feature,
but
thanks
for
sharing.
E
So
that
doesn't
fall
true
yeah.
The
other
point
in
this
is
that
this
issue
ended
up
being
very
large
due
to
the
nature
of
it,
where
it
made
sense
to
redo
the
entire
page.
For
this
specific
issue,
I
don't
think
it
could
have
been
tackled
as
a
smaller
nvc,
because
it's
also
paired
with
every
factor
of
the
code
in
the
page,
but
this
was
exhausting.
E
E
You
know
interaction
and
usability
points
were
covered,
so
I
definitely
don't
want
to
work
on
an
issue
as
large
as
this
next
milestone
and
just
try
really
hard
to
break
down
into
smaller
parts,
because,
even
though
it
might,
we
might
be
able
to
design
larger
things
all
of
the
administration
and
feedback
and
process
it
has
to
go
around.
It
makes
so
much
work
that
it's
not
necessarily
worth
it
and
it's
it's
better
to
follow
the
mvc
approach
and
really
design
on
a
smaller
scale
over
time.
E
My
next
point
is
on
deployment
approvals.
More
of
something
I
wanted
to
share
with
the
team.
Xenia
has
created
a
technical
proposal
for
how
the
back
end
should
work
for
deployment
approvals.
E
It
was
super
interesting
to
see
him
making
this
document
and
also
he
also
made
a
tech
demo
that
I
can
share
later,
because
it
shows
how
the
technical
structure
for
a
new
feature
is
born,
and
it's
a
new
feature,
because
the
funding
approvals
today
are
based
on
a
workaround
that
involves
manual
jobs
and
protected
environments,
but
it's
not
actually
a
deployment
approval.
It's
just
running
a
ci
job
right,
so
there
is
no
representation
in
our
back
end
that
a
deployment
was
approved.
E
There
are
no
apis
like
there's
not
that
much
documentation
around
it.
So
the
idea
here
is
to
make
deployment
approval
the
first
class
citizen
that,
like
you,
can
query
from
the
api
you
can.
You
can
actually
go
into
the
database
and
see
which
deployments
were
approved,
which
ones
were
rejected,
have
an
auditing
around
that
etc,
and
one
of
the
outcomes
for
that
that
will
create
a
new
ci
job
status,
which
is
waiting
for
approval.
That
will
replace
the
skipped
status
that
manual
jobs
receive
when
they
haven't
been
officially
rejected
right.
E
So
if
I
make
a
change
that
will
be
deployed
to
a
protected
environment
today,
if
I
go
to
the
pipelines
page,
it
shows
that
job
has
skipped
in
the
future.
With
this
implemented,
we
will
show
waiting
particular,
so
it
will
help
us
also
build
out
the
wise
in
a
more
intentional
way.
So
users
know
that
it's
not
someone
has
to
approve
or
reject
this.
B
This
is
really
great
to
hear
thanks
daniel
for
working
on
this.
It
makes
so
much
more
sense
than
the
current
experience
and
makes
it
much
more
intuitive
to
understand
like
how
your
pipeline
works
in
just
like
human
terms.
B
So
I
one
thing
I
wanted
to
clarify
this
status
waiting
for
approval.
Will
it
only
be
used
in
the
situation
instead
of
skipped,
or
will
you
also
show
it
when
it's
spending,
for
example?
So
when
the
manual
job
has
been
created
and
it's
it's
ready
to
be
run,
or
I
guess
I'm
trying
to
understand?
Is
it
like?
A
one-to-one
relationship
between
the
manual
job
has
been
created
and
it's
ready
to
run.
B
There's
now
like
this
play
button
action
that
you
can
run
at
any
time
or
is
waiting
for
approval
tied
to
like
a
specific
point
in
the
pipeline,
like
certain
jobs
need
to
run,
and
then
it
will
go
into
waiting
for
approval
or
yeah.
I
don't
know
does
that
my
question
makes
sense.
Can
a
job
be
go
into
waiting
for
approval
when
it's
like
pending.
E
So
I
I'm
not
exactly
sure.
I
think
this
would
be
a
great
question
to
ask
in
the
comments
of
that
issue
a
link,
but
from
what
I
understood
so
far.
I
think
it
would
replace
the
job
status
when
it
gets
to
skipped
right
now.
So
as
soon.
C
I
can
take
a
quick
stab
at
this.
I
might
not
be
hundred
percent
right,
but
so
pending
is
when
the
job
fails
to
get
picked
by
a
runner.
So
let's
call
it
manual
so
when
that
manual
icon
appears,
that
means
when
the
job
manual
job
is
created.
So
maybe
what
it
is
trying
to
do
is
it's
trying
to
deploy
to
a
branch
to
which
not
everybody
has
access
to
approve
actions
on,
and
that's
when
this
appears
so
I
mean
I'm
not
able
we
can.
C
We
consider
the
skip
situation
when
I
think
it
is
allowed
for
that
to
be
skipped
for
the
manual
job,
but
otherwise
it's
for
the
manual
job.
You
are
right
about
that.
Nadia
like
when
the
manual
job
gets
created,
yeah
because.
B
That's
where
my
confusion
comes
from,
because
to
me
skipped
it's
already
kind
of
like
the
final
status,
like
we
moved
on
from
that
job
to
me,
doesn't
map
directly
to
the
waiting
for
approval
status?
For
me,
just
the
manual
job
state
indicates
to
me
it's
waiting
for
approval.
E
D
E
That's
something
we
have
to
align
better
on
as
well,
because
from
this
technical
proposal
it
will
reflect
it's
made
to
reflect
on
on
the
environments
page
and
the
whole
approval
workflow.
But
since
we're
especially
because
we
are
introducing
a
new
state,
it
also
has
to
reflect
on
on
the
pipeline
graph
and
the
pipelines
page.
So
we
have
to
understand
how
that
will
be
represented
and
where
it
fits
in
the
workflow.
B
Yeah,
I
will
add
a
I
will
let
a
comment
to
this
issue
and
ping
xin
yin
you
just
to
clarify
and
vitika
will
also
bring
you
there,
because
I
guess
it
relates
to
pipeline
execution
as
well.
I
would
love
to
get
some
clarity
there.
Yeah.
A
I'm
gonna
power
through
the
read-only
items
for
fake
package
package
and
katie
for
katie
and
gina,
so
katie
shared
here.
The
three
problem:
validation
issues
that
she's
prioritizing
with
her
pm.
The
next
upcoming
milestones,
which
is
awesome,
katie,
saw
a
need
for
package
an
opportunity
to
work
on
more
generative
and
problem
validation,
research.
A
So
please
have
a
look
and
her
second
point
is
about
also
research
she's
working
on
finding
a
way
to
document
all
the
past
research
for
package
and
she
created
a
video
that
helps
answer
the
workflows
and
motivation
questions.
So
please
have
a
look,
leave
any
feedback.
If
you
have
here
async
so
that
kd,
you
can
have
a
look
in
the
agenda
and
nadia
over
to
you.
B
B
You
can
you
hear
me
yeah.
So
first
thing
we're
planning
to
make
the
pipeline
page
layout
fluid
by
default,
which
means
the
pipeline
page
will
take
up
your
whole
screen
for
100
width
of
your
screen
and
the
reasoning
for
that
is.
We
want
to
show
more
of
the
pipeline
graph.
The
whole
point
of
the
pipeline
graph,
like
one
of
the
main
benefits
that
it
provides,
is
this
overview
of
your
whole
pipeline
architecture.
B
B
So
we
want
to
give
them
the
ability
to
see
the
full
name,
because,
right
now
it
can
be
difficult
to
tell
the
jobs
apart.
Sometimes
because
we
show
such
a
small
portion
of
the
name,
sometimes
the
names
are
dynamically
generated,
so
the
first
part
of
the
name
can
be
the
same.
That
makes
it
impossible
to
tell
the
jobs
apart,
so
yeah
feel
free
to
comment
on
the
issue.
B
If
you
have
any
any
any
thoughts
or
comments,
and
the
other
issue
is
the
file
tree
mvc
for
the
pipeline
editor,
and
I
will
just
go
ahead
and
take
30
seconds
to
show
you
the
prototype,
because
I
think
it's
quite
straightforward.
There's
not
that
much
to
talk
about
here,
but
we're
making
pipeline
editor
full
width
as
well.
So
I'm
I'm
personally
super
excited
about
these
full
width
layouts.
B
It
just
makes
sense
for
the
kind
of
work
that
our
users
are
doing
using
using
these
tools,
so
we
will
be
adding
an
mvc
of
a
file
tree
in
the
pipeline
editor,
where
you
will
be
able
to
access
all
of
your
pipeline
files
that,
like
you,
you
can
include
in
your
pipeline
or
downstream
pipelines,
multiproject
pipelines,
things
like
that
and
as
an
mvc,
you
would
be
able
to
open
these
in
a
new
tab
in
the
file
view.
B
Eventually,
though,
you
would
be
able
to,
you
will
see
like
a
file
tree
hierarchy
here,
and
you
would
be
able
to
open
them
inside
the
pipeline
editor
and
the
section
would
be
collapsible
and
the
pattern
that
we're
using
is
the
same
pattern.
We
have
in
the
merge
requests
in
their
file
tree,
so
yeah.
A
B
C
C
Okay,
so
should
I
move
on
to
my
atoms
all
right,
so
the
couple
of
issues
that
I
worked
on
the
previous
week,
one
is
for
it's
a
very
it's
from
a
very
recent
conversation,
a
discussion
over
an
mr
that
nadia
and
I
participated
on
which
was
around
not
surfacing
the
complete
job
blogs
when
the
logs
exceed
0.5
mb.
C
So
we
are
adding
a
button
on
the
job
logs
page
now,
so
that
users
can
progressively
load
like
on
click
the
previous
500
kbs
of
in
off
logs
and
the
it's
just
a
button
that
we
are
adding
and
in
in
the
process.
I
figured
that
we
were
providing
multiple
triggers
for
showing
complete
raw
file,
so
this
was
also
a
good
opportunity
to
get
rid
of
that,
and
this
is
a
pretty
simple
one.
C
So
so
far
what
we
have
been
showing
through
the
usage
quota
page
was
just
the
ci
minutes
and
ci
minutes
is
like
how
it
is
calculated
is
we
multiply
the
duration
by
the
cost
factor,
that's
associated
with
the
runners
that
you're
using
so
for
mac
runners,
it's
a
little
high
for
regular
rulers,
it's
slow,
but
what
is
happening
is
since
we
do
not
charge
the
free
and
public
projects
for
like
we
provide
them
a
lot
of
free
minutes.
C
So
there
was
no
traceability
like
there
was
no
way
for
them
to
know
like
for
how
long
are
my
pipelines
running,
and
that
was
creating
a
problem
I
mean
for
us
a
whole,
a
lot
of
me
meaning,
but
for
them
to
maybe
optimize
their
pipelines,
it's
very
important
for
them
to
at
least
have
some
access
to
some
kind
of
information
there.
So
going
ahead
now,
we'll
also
show
like
how
what's
the
pipeline
duration,
the.
C
I
would
call
it
the
raw
pipeline
duration,
because
it
doesn't
have
any
cost
factor
associated
to
users
like
to
name
spaces
and
for
groups,
so
we
cannot
break
it
further
down
into
subgroups
and
projects.
That's
like
that.
Would
be
a
lot
of
work
to
do,
but
for
an
mvc,
it's
just
for
groups
and
name
spaces
and
again
the
issue
link.
Is
there
I'd
be
happy
to
see
some
feedbacks
if
there
are
any?
C
Lastly,
there's
a
form,
input,
add-on
issue
that
was
being
worked
on
it
drizzled
further
down
from
a
couple
of
other
efforts
that
jeremy
was
working
on
and
I
participated
in
this
and
it
looks
like
like
we
have
made
a
very
good
progress
there
and
the
new
variants
for
the
input
form
field.
They
would
be
new
variants
for
the
add-ons,
for
the
input
field
would
be
available
pretty
soon
and
in
the
meanwhile.
C
I
have
also
documented
the
current
mvc
approach
that
we
take
like
manually,
adding
that
icon
and
what
icon
should
be
added
for,
show
and
hide.
This
is
just
documentation
for
that
in
this,
mr
here,
which
is
yet
to
be
merged
and
yeah.
That's
that.
A
Okay,
thank
you
for
sharing.
Anyone
has
any
thoughts
or
comments
before
I
move
to
gina's
read-only
items
all
right,
okay,
so
gina
first
topic
is
for
testing,
so
they're,
adding
a
new
project,
quality,
summary
they'll.
Let
a
team
see
like
an
overview
of,
of
course,
project
quality
and
bring
more
attention
to
the
testing
features.
So
tina
has
a
bunch
of
questions
here
in
terms
of
feedback.
So
please
have
a
read
and
leave
the
comments
here,
a
sync
or
leave
comments
in
her
issue
right.
A
So
it's
about
the
empty
states
and
understand
a
little
bit
more.
How
do
we
link
documentation
gina
if
you're
watching
this,
I'm
going
to
also
write
down
check
the
pajamas
and
guidelines
and
also,
if
you
have
any
questions,
let
me
focus
in
the
in
the
slack
channels
and
you
can
well
you
can
ping
jeremy
for
any
any
questions,
and
she
also
has
a
read-on
item
which
is
actually
super
awesome.
A
So
I'm
gonna
read
that
it's
about
the
runner
vision,
so
she
created
a
video
but
also
has
an
epic
that
talks
about
the
runner,
configuration
details
and
work
actually
for
scorecards
and
also
how
to
improve
messaging.
After
deleting
the
runners,
this
is
a
really
a
great
result
right
and
I
think
the
first
time-
maybe
I
don't
know
in
a
year
that
we
see
like
such
a
big
movement
or
big
changes
going
on
for
runner.
A
Now
that
we
have
more
stability
in
gina,
it's
a
stable
counterpart,
so
I'm
really
excited
to
see
the
results
there
and
see
gina
working
on
moving
runner
forward
when
we're
enterprise
management.
So
that's
pretty
awesome,
have
a
read:
have
a
look
and
leave
your
feedback
here
as.
D
C
There's
just
and
like
an
fyi
at
the
end
in
the
cool
stuff
section
that,
since
I'm
going
through
this
coaching
for
privatization
and
capacity
management,
there's
a
timesheet
tracker
that
I've
created
for
myself
and
I
created
a
template,
so
others
in
the
team
can
also
use
it.
It's
a
very
so
why?
Why,
when
to
use
this,
is
to
understand,
if
there's
any
gap
between
what
you're,
assuming
your
priorities
to
be
and
what
it
is
in
reality.
C
So
you
can
just
keep
a
track
like
of
the
things
that
you're
doing
keep
on
checking
the
box
at
what
time
you're
doing
what
you
can
also
change
the
strategies
at
the
top
that
do
whatever
suits
your
own
role
and
your
goals
and
yeah.
I
mean
it's
easier
to
it
made
it
very
easy
for
me
to
understand.
Like
what
have
I
been
telling
everyone
that
I
am
focusing
on
and
what
is
it
that
I'm
focusing
on
in
reality.
A
Thank
you
for
trying
me.
I
just
added
a
question
here.
It's
really
interesting
and
also
here
see
how.
How
are
you
going
to
use
that
and
if
there
will
be
any
learning,
but
just
a
heads
up
for
everyone
as
a
result,
it's
not
ours
right.
So
there's.
D
A
No
expectation
that
anyone
needs
to
know,
or
anyone
is
tracking
your
work
hours
so
also
be
mindful
of
that,
but
I'm
curious
to
see
how
how
are
you
gonna
use
it?
Okay,.
B
Oh
before
we
we
leave
just
very
quickly.
I
forgot
to
share
that.
I
will
be
having
some
time
off
starting
in
november,
7th
7th,
I
think
or
11th,
but
it's
going
to
be
the
week
after
next.
So
I
was
wondering
if
any
of
you
could
cover
for
me
I'll,
be
creating
coverage
issue
so
yeah,
let
me
know
if
any
of
you
will
be
available.
B
A
There'll
be
a
lot
of
time
off,
I
mean
from
all
of
us
in
the
future.
So
I
think
it's
it's
a
good
heads
up
thanks
man,
if
I
remind
me
of
that,
if
you're
planning,
like
any
time
off
by
the
end
of
the
year
christmas
holidays,
create
those
placeholder
issues,
because
the
weekend
coordinates
also
be
off
in
in
december
and
in
november.
A
So
let's
try
to
have
that
coordinated
so
that
one
person
that
stays
is
not
covering
for
everything.
I
think
that
you
need
some
complaining
ahead
right
cool.
Then
let
you
go.
Thank
you
so
much
for
joining
and
for
sharing
and
then
yeah
see
you
around
see
you
later
and
daniel
I'll
see
you
in
one
second
nadia
we
are
together.
I
don't
think
you've
seen
that
danielle
was
here
next
to
me.