►
From YouTube: CI PM/UX Weekly on 2020-07-28
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
our
cipmux
weekly
check-in,
we'll
just
start
right
away.
So
first
agenda
item
I
wanted
to
let
you
know
that
in
the
past
I've
been
adding
a
link
under
each
I'm
going
back
after
the
meeting
and
added
a
link
to
the
the
recording.
But
I'm
going
to
stop
doing
that
because
I
created
a
playlist
for
us
that
you
could
just
go
there
and
see
all
of
them.
For
example,
if
you
go
to
the
top
of
the
agenda,
it'll
say:
recording
c
playlist
when
you
go
to
that
playlist.
A
What
I
did
was
I
double
labeled
our
videos,
each
one
I
mean
double
labeled
them
to
two
playlists
to
the
ci
group
playlist,
which
is
the
general
one
with
all
ci
team,
related
videos
and
then
a
separate
one
that
this
one
so
that
you
don't
have
to
search
through
the
other
one,
because
the
other
one
has
everything
from
deep
dive
discussions,
but
whereas
this
one's
specific
to
our
session.
So
just
a
call
out
to
that.
So
you
won't
see
me
adding
a
individual
link
under
each
agenda.
A
For
that,
I
thought
right
away
just
to
make
sure
we
have
time
for
the
discussion.
I
moved
to
agenda
item
2
and
something
that
just
came
in
on
our
slack
channel
this
morning
from
fur
khan
that
we
could
look
at
those
two
issues
to
make
sure
what
work
there
is
either
for
victica
or
vitico
and
myself.
A
So
looking
at
the
first
issue,
he
mentioned
merge
immediately
possible
in
invalid
scenarios
with
pipeline
for
merger
request.
A
B
So
I
did
look
at
this
and
I
can,
I
think
summarize
what
they're
trying
to
say.
Okay,
so
even
when
the
option
for
pipeline
must
succeed
is
selected.
C
B
Also
in
situations
where
just.
B
Also
in
situations
where
the
master
is
like
a
few
comments
ahead
of
the
current
branch
and
the
pipeline
hasn't
run
again,
we
do
provide
the
users
with
an
option
to
merge
immediately
and
what
can
what
that
can
do?
Is
that
might
end
up
breaking
the
master
and
that's
the
concern
that
they're
expressing
here
so
fur
khan
mentioned
that
in
his
knowledge,
why?
The
reason
that
we
had
put
merge
immediately
was
to
override
merge
trains.
B
But
I
think,
even
though
we
want
to
override
merge
trains,
but
that's
only
for
use
cases
when
there
is
an
urgency
or
if
something
is
of
a
very
high
priority.
I
mean
the
master
is
commits
ahead
and
there's
a
chance
for
breaking
the
build.
Okay.
D
In
in
when
there
was
a
broken
master
is,
is
kind
of
it's
funny,
because
it
has
it
had
the
opposite
effect
that
it's
like.
Oh
no,
we've
got
a
broken
master.
Do
we
want
a
one
hour
pipeline
to
run
before
we
can
merge
and
fix
master?
So
they
wanted
a
button
where
you
could.
Click
merge
immediately
fix
master
and
get
merged
trains
running
green
again,
but
then
it
has
the
inverse
effect
where
you
could
immediately
break
master
if
you
use
it
in
the
wrong
way
as
well
by
skipping
the
pipeline.
So
there
was
yeah
yeah.
D
A
I
wonder
if
there's
a
way
to
make
the
logic,
so
I
it
sounds
like
okay,
so
under
the
possible
fixes,
is
check
to
make
sure
the
pipeline,
like
succeeds
against
matters
they're
still
valid
before
presenting
the
merge
master
has
advanced.
Could
they
say
why
merge
is
not
possible
that
works,
because
in
the
possible
fix
this
proposal
there
it
does
account
for
that
scenario
marcel
to
not
let
the
mr
get
blocked
if
to
allow
the
merge
immediately
in
the
cases
where
master
is
broken,
you
don't
want
to
wait.
B
I
do
have
another
concern
here
that
I
mean,
if
we
really
want
to
do
this
like
check
to
make
sure
that
pipeline
that
succeeded
against
master
is
still
valid,
shouldn't
that
be
happening
for
both
the
merge
train,
as
well
as
merge
immediately.
B
B
Okay,
so
in
the
possible
fixes,
if
you
read
in
the
description,
they
say
that
check
to
make
sure
that
the
pipeline
that
succeeded
against
master
is
still
valid
before
presenting
merge
immediately.
B
But
if
we
are
doing
that
shouldn't
we
be
doing
that
for
both
starting
the
merge
train,
as
well
as
merge
immediately
like
checking
the
validity.
Once
again,
if
the
master
is
advanced.
B
Because
I'm
curious
like
what,
how
does
starting
a
merge
request
resolve
the
problem
here,
starting
the
moisture
and
resolve
the
problem
here?
Does
it
do
things
well.
D
If
you,
if
you,
if
you're
running
a
merge,
request
or
merge
results
pipeline,
but
basically
like,
if
you
run,
if
you
add
something
to
the
merge
train,
it's
going
to
run
a
whole
pipeline
anyway.
So
it
doesn't
matter
like
how
far
ahead
master
is.
A
Yeah,
I'm
I'm
a
little
confused
and
I
didn't
realize
that
there's
some
comments
within
the
last
hour
that
I
need
to
catch
up
on.
Let's,
let's
come
back
to
this
and
we'll
have
we'll
we'll
I'll
start
our
thread
async
in
our
team
channel,
because
I
have
some
questions
for
the
engineer
like
one
is
what
marcel
pointed
out,
I
was
like
how
could
a
how
could
anything
ever
get
ahead
of
master,
because
master
is
always
supposed
to
be
ahead
of
anything
in
merge
string
so
and
maybe
there's
a
scenario
I'm
not
familiar
with.
D
A
And
if,
if
that's
the
case,
maybe
what
we
need
here
is
at
least
a
a
warning:
do
you
really
want
to
be
doing
this
because
it
kind
of
takes
things
out
of
order?
I.
B
B
That
foregone
put
a
screenshot
of
the
warning,
so
if
we,
I
think
the
use
case
is
pretty
well
taken
care
of
okay,
we
need
to
understand
if
we
need
to
change
this
at
all.
A
Okay,
if
we,
by
the
way,
I
did
see
the
comment
that
if
we
do
move
ahead
with
this
with
any
changes,
it's
not
going
to
be
a
bug.
It
is
a
a
change
to
the
feature
that
I'll
I'll
change
the
labeling
and
remove
bug
all
right
yeah.
I
want
to
analyze
that
one
a
little
more
and
then
we'll
start
a
thread
async
in
our
team
channel
on
the
second
issue
method
to
clean
up
old
artifacts
in
bulk,
oh
crap.
I
didn't
add
the
proposal
on
here.
A
I
have
to
change
this
to
the
feature
proposal
template,
but
basically
I
know
that
users
have
a
way
to
delete
artifacts
through
the
api.
I
don't
does
ferkan
say
in
here
what
he
needs
from
ux.
I
have
a
couple
questions.
A
A
I
could
work
with
vitica.
You
can
come
up
with
whatever
ui
change
you
would
want
to
make
and
then
do
that
implementation
in
13.4.
Okay!
Does
that
sound,
fair,
okay,
yeah
and
I
like
the
idea
of
just
introducing
the
api
at
first
number,
one
the
ui
will
to
consume
it
and
also
it
lets
us
deliver
something
without
trying
to
design
in
a
hurry.
D
All
right,
I
think
there
is
like
not
that
it
it
I
mean
just
if
you're
cursed.
I
think
there
is
like
a
documented
way
to
delete
artifacts
in
bulk,
so
like
not
not
with
like
with
a
rake
task
or
a
script,
or
something
like
that.
You
can
go
so
it's
a
troubleshooting
dock,
where
support
is
trying
to
find
out
why
you
know
you've
got
so
much
space
with
you
or
something
like
that
and
they're
able
to
actually
I'd
have
to
look
look
it
up,
but
there
there's.
D
A
I
I
hope,
you're
right
when
I
first
glanced
at
this.
I
went
to
the
api
docs
and
I
went
to
resources
and
I
just
looked
up.
I
just
did
a
keyword
search
on
art.
Was
it
artifacts?
I
can't
remember
what
I
searched
on
and
I
saw
a
way
to
call
out
a
specific
artifact,
but
not
a
way
to
do
it
in
bulk.
But
I
didn't
look
at
what
you
said.
The
rake
method.
C
C
D
Issues
and
and
it
used
to
be
internal,
but
we
thought
why
not
just
make
them
transparent.
Why
not
just
let
other
people
see
them
so
the
docs
are
there,
but
it's
not
like
it's
really
promoted
for
people
to
use.
We
just
we
just
made
them
public
so
that
people
could
self
troubleshoot
and
sometimes
fix
things
without
needing
to
call
support,
so
there
there
is
a
way
to
do
it.
I
didn't
read
through
in
detail,
I
just
remember
seeing
the
the
header
basically
and
knowing
that
there
was
a
process
for
it.
A
A
D
A
Yeah
and
I'm
I
would,
let
me
add,
ask
for
conant,
I
think,
he's
the
one
who
worked
on
whichever
engineer
worked
on
the
the
the
issue
we
had
for
the
feature
to
keep
the
latest
artifact,
if
this
would
prevent
anything
that
had
the
lock
setting
to
prevent
that
from
getting
deleted,
because
because
we
obviously
wouldn't
want
them,
I
wouldn't
want
to
suggest
this
as
a
workaround
and
have
it
delete
something
they
need.
Like
you
mentioned
yourself,
okay,
oh
thank
you
for
sharing
that
I
hadn't,
I
didn't
know
we
had
this
out.
A
There
is,
I
guess,
since
this
is
something
that
our
support
team
uses
informally,
even
though
we
have
it
in
our
docs,
we
should
not
link
to
it
from.
D
A
Okay,
so
I
still
it's
a
support
process.
I
still
want
to
move
forward
with
this
issue
as
far
as
delivering
an
api
to
bulk
delete,
but.
D
A
Yeah
yeah
and
it
would
really
help
them
if
they
want
to
reduce
their
usage
before
consumption
for
yeah.
Sorry.
A
So
all
right,
I
think
we
have
a
plan
for
for
that
issue.
I'll,
add
the
comments
back
to
our
agenda.
A
Number
three:
I
kind
of
wanted
to
do.
Well,
let's
go
to
that
one.
This
is
the
ux
review,
epic.
It's
a
it's
a
standing
agenda
item
that
nadia
proposed
for
each
time
we
get
together
in
this
meeting.
Let
me
scroll
down
to
what
we
have
for
design
work
in
13,
hey
vitica.
Last
time
we
talked
about
this,
we
were
going
to
check
with
dimitri
if
we
can
remove
the
ones
that
were
assigned
to
him,
I'm
assuming
they're
still
there,
because
it's
still
in
progress.
B
Or
yeah,
so
I
closed
the
ones
that
were
closed
at
that
point,
but
I'll
check
with
him
for
the
rest
of
them.
A
Okay,
I'll
and
then
for
the
13.31
again,
I'm
looking
under
the
table
that
says
design
work.
I'm
assuming
we
don't
that's
past
milestone.
We
don't
need
to
talk
about
those.
Let
me
look
real
quick
on
the.
A
Okay,
so
I
can't
remember
what
we
do
with
this
table.
I
don't
want
you
to
have
to
update
the
table.
So,
let's,
let's
agree
that
wherever
the
state
of
these
are
I'll,
just
click
through
the
individual
issues
to
see
where
we're
at
and
then,
when
they're
completely
done,
we'll
remove
it
from
the
table.
That's
great
okay!
A
B
Okay,
I
can
give
a
quick
glimpse
like
there's.
Just
one
that
was
changed
today,
which
is
merge.
Widget
gives
ambiguous
ui
instructions.
C
B
The
rest
of
them,
I
still
I'm
the
assignee
for
all
of
them
and
they're
in
progress.
Okay,
so
today
I
replaced,
if
you
remember
yesterday,
I
had
a
discussion
with
you
about
this
new
message
that
I
the
format
that
I
proposed.
B
So
I
spoke
with
designers
from
verify,
and
I
I
was
actually
confused
if
the
color
of
the
button
in
the
merge
request
widgets,
they
also
kind
of
change
with
the
status
of
the
pipeline,
because
in
the
previous
design
it
was
blue
but
turns
out
it
doesn't
it
just
if
it's
ready
to
merge
it's
green
and
then
there
is
this
other
state.
B
So
I
think
this
would
go,
but
still
I
have
tagged
designers
from
the
create
team
devops
create
so
that
they
can
verify
if
this
is
a
valid
approach
and
I've
changed
the
message
as
we
discussed
and
instead
of
the
loading
state,
sarah
and
fred,
they
suggested
that
pipeline
running
would
make
more
sense
because
there
is
actually
a
pipeline
running
at
that
moment.
A
A
Okay
and
then
the
comment
that
I
had
yesterday
was
the
the
sentence:
that's
below
the
button.
This
request,
we
thought
maybe
change
that
to
this
action.
B
A
Yeah,
okay,
awesome
all
right!
So
you,
if
you
upload
another
one,
does
it
do?
Does
it
it?
You
have
to
re-add
all
your
comments
right.
B
I
will
have
to
yeah
that
that's
something
that's
a
little
weird
and
also,
if
I
don't
name
my
iterations
in
a
certain
way,
it's
very
different.
It's
very
difficult
to
follow
up
like
what's
the
chronology.
A
Let
me
see
that's
one
of
the
things
that
I
think
is
the
the
team
that
the
create
team
that
owns
this
design
widget
is
going
to
change
that
you
can
reorder
things,
but
I
don't
know
if,
if
that
is
in
their
current
milestone,
that's
coming,
though.
Okay.
B
A
C
This
doesn't
give
me
a
way.
Okay,
all
right!
That
looks
great.
Thank
you.
Oh
you
added
the
comments.
Okay,
perfect.
Thank
you.
B
And
for
this
third
one,
I
had
picked
cheryl
in
the
channel
yesterday
to
point
me
towards
the
engineer
who
would
who
can
tell
me
more
about
deleting
bills
that
issue
on
allowing
instances
add
me
to
delete
bills,
so
she
has
suggested
that
I
should
get
in
touch
with
fabio.
B
A
Okay,
great,
I
saw
that
for
for
ux
research,
thanks
for
adding
that
comment
in
the
replacing
jenkins
slack
channel.
If
I
don't
see
any
responses
on
there
I'll
also
there's
a
if
you
look
through
the
jenkins
rapper
issues,
because
jenkins
rapper
became
a
mini
epic.
There
are
comments
from
some
other
folks
that
you
could
also
ping
but
I'll
find
their
names
in
ping
them
as
well.
B
I
took
the
names
from
the
same
issue,
which
was
jenkins,
rapper
private,
beta
feedback
and
discussion.
Yes,
I
also
tagged
them
in
the
comment
that
I
had
put
in
the
channel.
They
were
not
there
in
that
channel,
but
they
would
still
get
notified
about
it
yeah,
but
yeah,
since
there
isn't
any
response
yet.
So
I
was
wondering
like,
should
I
put
a
comment
in
the
issue
itself:
tagging
them.
A
Well,
I
noticed
that
the
folks
that
you
tagged
are
from
that
private
private
feedback
issue,
but
in
the
jenkins
rapper
epic
itself,
there's
comments
from
like
chris
timberlake
and
a
couple
other
folks
that
we
can.
We
can
mention.
B
Would
you
lead
me
to
the
epic
yeah
yeah?
Let
me.
C
A
A
A
There
was
a
person
from
the
sales
team
I'll
find
that
in
and
ping
them,
for
example.
Let
me
go
to
your
at
chris,
so
there's
chris.
I
just
added
him
to
your
thread
on
that
replacing
jenkins
channel
gosh.
I
can.
I
could
see
his
face
this
other
person
I'm
thinking
of
but
like
he
has
a
beard
and
he
wears
sunglasses
in
his
profile
pic,
but
I
can't
think
of
his
name
I'll,
find
it
later.
A
B
I'm
not
really
okay,
there
is
some
update
about
the
research,
but
I'd
rather
talk
about
it
in
our
yeah.
A
Our
research
that
sounds
good,
hey,
so
agenda,
item
form
for
for
this
meeting.
I
I
remember
that
nadia
had
mentioned
that
vitica,
you
would
start
adding
the
ux
definition,
I've
done
to
ux
issues
and
current
milestone.
Oh
yeah,
I
wanted
to
see
what
that
looks
like.
B
Is
there
a
link
if
you
look
at
all
the
issues
that
I'm
tagged
in,
I
have
at
the
bottom?
I
have
added
that
section:
okay,.
C
A
Bottom
of
the
description,
the
issue
description,
yeah,
the
description,
okay,
I'll-
do
that.
I
just
wanted
to
have
you
point
me
to
one,
but
since
all
of
them
have
it
I'll
go?
Look
there?
Thank
you
all
right.
So
my
number
five,
when
I
tried
to
use
dovetail
for
a
meeting
that
I
was
prepping
for
last
week
with
a
customer,
I
couldn't
figure
out
how
to
do
the
recording.
So
thank
you
lori
for
telling
me
it
doesn't
record
so
we
so
I
was
like.
A
E
Yeah,
so
you
just
record
it
like
normal.
I
tend
to
record
mine
on
my
computer
and
then
drop
it
into
the
dovetail.
E
To
find
the
file,
and
then
it
will
upload
it,
and
then
you
can
do
a
transcription
of
the
meeting
bye
marcel
I'm
coming
soon
too,
but
I
wouldn't
trust
it
because
in
my
merge
request
research
it
was
it
didn't
know.
What
mr
was
didn't
like
it
was
like
myrrh
mermaid
creates.
E
A
A
Thanks
bye,
lori
vitica,
we'll
have
to
pick
up
your
other
one
that
I
have
to
run
to
a
meeting
as
well.