►
From YouTube: CI & PA PM/UX Sync on 2020-09-23
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
Okay,
welcome
everyone
to
rci
and
pipeline
pmux
check-in,
hey
nadia,
so
we'll
start
with
the
first
agenda
item
there.
Let's
go!
Look
at
that!
Yes,
do
you
know
at
some
point,
do
you
want
to
have
a
separate
issue
for
pipeline
authoring?
Ux
needs
dove
and
nadia.
B
I
we
we
haven't,
really
used
issues
to
track
our
work
like
this,
I'm
not
sure
if
it's
necessary.
I
guess,
if
there's
a
need,
we
can
start
one.
But
at
this
point
I
I
don't
know.
A
Okay,
and
actually
this
one-
I
usually
dialogue
with
back
and
forth
with
vitica
on
this,
but
since
she's
out,
let
me
scroll
through
to
see
if
anything
has
changed,
that
I
want
to
call
out
not
really
and
she
and
I
touched
base
end
of
last
week.
So
we
can.
We
can
skip
this
agenda
item
and
come
back
to
it
and
I
don't
have
any
questions
for
I'll
ping
vitica
separately.
If
I
do
agenda
item
two,
it's
yours,
n
s,
are
we
doing
initials.
B
B
So
I
noticed
that
we
have
a
lot
of
issues
currently
around
improving
the
warnings
and
errors
in
ci,
so
the
configuration
warnings
and
errors
that
you
see
in
the
pipeline
page
in
run
the
pipeline
run
the
pipeline
page
and
also
the
linter,
and
there
is
no
like
cohesive
vision
for
what
this
experience
should
look
like
and
feel
like,
and
how
it
should
work
to
optimize
air
resolution
in
ci
and
air
resolution
is
an
extremely
important
part
of
the
ci
user
journey.
B
Every
user
at
one
point
or
another
will
encounter
errors
and
it's
a
very
frustrating
experience.
So
we
want
to
improve
it.
So
I
I
dug
around
the
issue
boards
and
I
tried
to
collect
the
epics
and
issues
into
like
a
parent,
epic
that
focuses
on
improving
the
air
resolution
in
gitlab
ci.
One
of
their
sub
epics
is
focusing
specifically
on
warnings
and
errors
in
the
linter.
B
However,
since
our
vision
is
to
have
embedded
linting
within
the
editor,
we
will
have
to
kind
of
look
at
those
issues
and
see
what
is
relevant
and
how
we're
gonna
maybe
reward
those
issues
we
need
to
groom
them
to
to
be
relevant
for
the
editor
experience
and
generally,
I
just
want
to
look
into
the
experience
of
air
resolution.
How
can
we
make
it
as
loose
as
possible
even
going
beyond
the
alerts
and
like
looking
at
things
like
documentation
or
maybe
some
help
within
the
ui
so
from
everyone?
B
I
would
love
some
help
to
just
find
whatever
issues
they
are
missing
in
that
epic,
because
I
I
think
there
are
many
more
and
I
tried
looking
for
like
errors
and
alerts
and
warnings,
but
maybe
you
know
of
some
issues
that
you've
seen
in
the
past
that
are
relevant
and
even
if
they're
closed,
already
feel
free
to.
B
A
D
A
Okay,
any
other
discussion
on
that
topic.
All
right,
so
number
three
is
read-only
and
it
was
something
good
that
I
think
will
benefit
vitica.
She
can
she-
and
I
will
benefit
from
that
number
four.
A
So
I
just
want
to
make
sure
that
there
weren't
any
questions
on
how
we
use
the
candidate
labels,
because
I
know
that
apm
team
was
not
using
that
and
I
I
don't
know
that,
there's
one
other
team,
that's
using
it,
because
I
see
that
label
being
used
at
the
project
level.
The
ones
we
created
are
at
the
group
level
for
our
gitlab
group.
It
came
up
with
actually
in
my
one-on-one
with
cheryl,
and
she
was
saying
that
sam
beckham
hadn't
used
it
before
and
he
found
it
confusing.
B
A
Yeah
so
I'll
give
you
the
context
of
why
we
use
them
and
then
and
then
how
we
use
them
for
ci,
because
there's
so
many
things
happening.
It's
one
of
the
more
mature
product
area
that
we're
constantly.
A
Potentially
changing
our
priority
of
things
we
had
previously
planned
for
the
next
milestone
and
then
prior
to
us
using
candidate
labels.
That
meant
changing
the
milestones
on
a
group
of
issues
that
the
wider
community
or
users
might
have
been
internally
and
externally
been
monitoring,
and
it
we
ended
up
getting
a
lot
of
comments
about
how
frustrating
and
confusing
it
is
for
someone
to
expect
that
an
issue
is
has
a
milestone.
A
A
Assigning
issues
to
a
specific
milestone:
instead,
we
invented
the
candidate
label,
for
whatever
reason,
users
seeing
that
candidate
label
on
an
issue
doesn't
interpret
that
as
a
commitment
in
the
way
they
did.
If
we
put
the
same
milestone
for
like
if
something
had
a
candidate
13.7,
and
we
also
put
a
milestone
13.7,
that
was
more
definitive
commitment
than
the
label,
so
the
label
became
a
way
for
us
to
plan
group
some
issues
together
that
we
want
to
target
for
a
milestone
but
haven't
finished
planning
and
committing
it.
A
So
the
way
we
use
it
is
instead
of
so
two
things
is
the
pm
will
put
a
candidate
label
on
a
milestone
and
I've
created
them
far
into
the
future,
and
you
see
their
scoping
labels.
So
no
issue
can
have
more
than
one
candidate
label.
A
A
pm
will
put
some
candidate
label
on
a
group
of
issues
that
we
think
we
want
to
target
for
a
specific
milestone.
It
also
lets
the
allows
us
to
get
a
filtered
list
of
those
candidate
issues
so
that
we
can
identify
which
ones
need
design
work
to
be
done,
and
then
I
make
sure
there's
either
a
ux
label
on
it,
and
then
I
meet
with
my
designer
and
say
of
these
20
issues
for
candidate
for
13.7.
Let's
say
of
these
27
of
these
actually
need
truly
a
design.
A
Five
of
them
only
need
some
input
on
the
copy
from
a
ux
perspective
and
that's
how
we
work
with
them
now,
if
an
issue
later
during
planning,
so
right
now
we're
planning
for
13.6.
If
we
at
the
end
of
planning,
we
commit
that
15
out
of
the
20
issues
will
be
committed
for
13.6.
Those
15
will
get
a
milestone,
13.6
applied
to
it,
and
then
the
remaining
five
will
have
their
candidate
label
change
from
candidate
13.6
to
13.7
or
it'll
be
removed
altogether,
because
we
decide
we
don't
want
to
move
forward
with
those
does.
A
Yeah
one
problem
we
have
with
this
is
our
it's
hard
for
us
to
dog
food.
Our
epic
feature,
because
that
epic
feature
I
mean
it's
our
roadmap
feature
because
it's
driven
off
of
epics
and
it
shows
in
the
roadmap
all
the
epics
filtered
on,
let's
say
on
group
or
on
category,
but
it
doesn't
expand
the
duration
of
the
epic.
A
If
you
don't
have
pre-assigned
milestones
on
the
issue,
because
the
epic,
the
duration
is
driven
by
the
the
far
into
the
future,
is
driven
by
the
furthest
future
milestone
on
an
issue
under
that
epic.
And
if
we're
not
assigning
milestones,
it
doesn't
work.
So
I
have
to
what
we
might
do
is
do
better
from
the
pm
perspective.
Do
better
planning
to
try
to
guess
how
long
it
would
take
to
deliver
all
the
issues
for
a
particular
effort
and
maybe
have
a
place
over
issue
that
has
a
milestone
far
into
the
future.
A
A
A
A
When
I
was
looking
at
these
issues
under
in
our
backlog,
that
has
anything
to
do
with
cicd
metrics
jason,
and
I
noticed
these
three
are
about
group
level:
pipeline
dashboards.
The
third
one
is
not
necessarily
a
group
level,
but
it
gave
me
some
ideas
that
I'm
gonna
try
to
figure
out.
What
are
the
common
themes
in
these
three
issues
and
start
some
problem
validation
put
work
on
it
that
will
lead
into
some
working
with
ithaca.
A
We
may
come
up
with
also
some
preliminary
designs
and
then,
and
then,
if
we,
if
we
decide
at
the
conclusion
of
problem
validation
that
we
want
to
move
forward
with
some
of
our
hypothesis,
then
we'll
go
into
some
design,
work
and
solution.
Validation
for
that,
but
this
is
one
of
the
three
areas
that
I
called
out
as
a
focus
area
for
priority
for
ci
team
during
our
team,
ci
team
split
ama
and
I
want
to
move
forward
with
it
in
13.5.
E
Just
let
me
know
if
you
need
any
help
with
anything
and
as
you
create
the
research
issue,
if
you
put
me
on
it,
if
you
assign
me
to
it
too,
then
I
can
watch
it.
Okay,.
A
E
A
A
F
Other
than
that
point
as
well
just
wanted
to
vocalize
my
comments
that
I
know
that
jackie
and
the
hayana
had
they
have
been
doing
some
well
research
and
testing
some
of
the
prototypes
for
the
cicd
dashboard.
D
F
A
Management
yeah,
I'm
vaguely
aware-
and
I
would
appreciate
if
you
link
some
of
that,
so
I
vaguely
became
aware
of
it
when
jackie
and
I
and
matt
gonzalez
from
the
compliance
team
were
in
a
session
together
and
he
was
talking
about
having
dashboards
for
compliance
purposes,
and
she
was
jackie
was
talking
through
that
through
her
team
doing
some
problem
validation.
A
They
found
some
things
that
was
in
interviewing
users
was
not
going
to
be
useful
at
all
yeah.
Well,
I'm
going
to
to
yeah
I'm
going
to
make
sure
that
I
know
those
lessons
learned
so
that
I
don't
pursue
something
that
we
already
know.
There's
not
a
there's,
not
a
demand
for
yeah.
F
A
E
Number
six
yep,
so
sorry,
andre
and
I
are
going
to
conduct
a
category
maturity
scorecard
on
the
job
to
be
done
needing
to
create
a
green
pipeline,
so
others
of
my
team
or
my
company
can
leverage
ci
to
increase
efficiency
of
their
tasks.
E
E
How
is
our
current
process,
so
we
thought
what
better
way
to
understand
it
than
putting
together
a
baseline,
summative
evaluation
of
creating
a
green
pipeline,
so
we're
in
the
process
of
creating
that
testing
plan
and
getting
screeners
and
stuff
ready.
So
recruiting
can
start
just
more
of
an
fyi
for
everybody
to
know
about,
and
then
once
we
have,
the
data
we'll
share
it
in
dovetail
and
it'll
also
be
linked
to
that
issue.
B
Can
you
also,
if
you're
gonna,
have
any
meetings
around
this
or
like
interviews?
Can
you
please
invite
me
as
an
optional
participant,
because
setting
up
getting
to
a
green
pipeline
is
the
primary
metric
that
we're
monitoring
in
pipeline
authoring,
so
yeah?
I'm
super
excited
about
this
and
it's
right.
It's
like
perfect.
If
you
weren't
doing
this,
I
would
raise
my
hand
and
ask
if
we
can
do
this
now,
so
awesome.
Keep
me
in
the
loop
please.
I.
B
E
Yeah
I'll
yeah,
you
can
hop
on
the
issue
and
then
once
we
get
people
scheduled
I'll
put
it
in
the
ux
research
calendar.
So
you,
you
can
see
all
the
events
there
and
then
you
can
just
come
to
the
ones
that
you
can
attend.
That's
fine!
So
the
cms,
though,
won't
be
too
much
talking,
but
it
will
be
hopefully
informative,
because
we
need
to
capture
like
success.
Failure
and
things
like
that.
So
we'll
be
working
with
jason.
E
B
E
Yeah
so
dove
we're
just
going
to
put
them
all
on
the
ux
research
calendar.
It's
a
shared
google
calendar.
So
if
you
add
that
to
your
I'm
sure
long
list
of
google
calendars
just
like
I
have
it-
should
show
up
there
once
we
have
people
scheduled,
so
you
can
drop
into
any
session.
E
That's
on
the
calendar,
so
I'll
make
sure
the
title
is
self-explanatory.
So
you
know
which
sessions
are
the
ones
that
you
should
pay
attention
to
and
then
I'll
also
post.
Once
we
have
the
dovetail
project
up
and
going
I'll
post
a
link
to
that
in
the
issue
as
well,
which
is
where
all
the
recordings
and
stuff
will
be
in
case
you
miss
any.
E
A
I
I
linked
in
item
c.
There
succeed
the
for
your
awareness.
If
anyone
doesn't
already
know,
there's
an
issue
from
the
pm
perspective
to
actually
create
the
metric
for
tracking
first
green
pipeline.
A
Yeah,
I
think
they
dove
and
jason
will
be
working
on
that
one,
but
it
may
give
you
an
idea
of
you
may
want
to
help
them
refine
that
too,
if
you
decide
in
what
you
find
is,
is
if
they're
not
there's
a
better
way
for
them
to
track
that.
A
That's
okay,
anything
else
on
number,
six,
okay,
so
number,
seven,
I'm
just
a
quick
heads-up!
A
I
haven't
done
much
with
this
yet,
but
I'm
thinking
I'm
doing
a
ux
research
project
on
merge
trains,
adoption
and
I'll
create
a
I'll,
create
a
ux
research
issue
for
that
for
discussion
at
our
next
ux
research
meeting
I'll
put
as
much
as
I
know
that
I
want
to
do
with
that
and
then
either
laura
you
can
chime
in
async
in
the
issue
and
give
you
some
help
or
if,
if
you
don't
have
a
chance
before,
then
we
can
have
it,
I'm
going
to
throw
it
as
an
agenda
item
for
our
next
ux
meeting
as
well.
E
A
A
I
was
more
focused
during
that
handoff
on
what
was
next,
that
I
needed
to
plan
for
and
prioritize
and
not
so
much
some
of
the
things
that
she
was
aware
of
from
feedback
from
users.
So
I
need
to
go
back
and
gather
that
and
then
see
if
she
has
anything
else
she
wants
to
add
to
it
yeah,
so
so
on
that
one
as
well
lori
I'll
I'll
assign
you
to
it
so
you're
aware.
So
it's
on
your
board.
Yeah,
perfect.
A
A
Okay,
I
think
we're
going
to
finish
early
yay
anything
else.
Folks,
all
right,
I
guess
that's
it
for
today
give
you
seven
minutes
back.
Everyone
thanks.