►
From YouTube: CI PM/UX Weekly on 2020-07-21
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).
B
Any
agenda
item
to
to
showcase
that
I
have
closed
the
issue
where
we
had
the
where
we
have
been
discussing
the
UX
technician
of
done
for
CI,
quite
some
good
feedback
there
and
and
a
good
amount
of
that
so
also
started
reflecting
that
in
the
handbook
in
the
in
the
verified.
You
have
section
for
now
to
indicate
that
we
are
running
that
as
a
pilot
in
the
in
one
of
the
teams
for
now
so
not
like,
adding
that
widely.
Yet
to
the
handbook.
B
We
just
wanted
it
to
be
there
to
be
more
visual,
physical
and
visual.
The
Reis
points
of
discussion
happening
right
now
in
the
merge
request.
So
can
he
has
some
interesting
proposals
and
good
feedback
so
working
around
that
and
yeah
and
assigned
I
assigned
Whitaker
as
the
DRI
to
merge
after
the
discussions
will
be
done
so
yeah
before
I'm
gonna.
Merge
that
please
jump
in
into
the
Mar
and
leave
any
thoughts
and
inputs.
If
you
still
have
any
feedback
to
add.
A
B
The
little
disclaimer
this
is
something
that
the
release
management
is
doing
really
successfully.
For
now,
the
goal
of
the
UX
definition
of
done
is
to
how
must
Oh
prepare
the
the
work
before
it
goes
into.
The
UX
means,
like
you
know,
like
working
on
defining
the
problem
a
little
bit
better,
but
also
to
work
to
improve
the
output
of
the
UX,
also
in
terms
of
thinking
about
the
iterative
approach
to
the
design,
thinking
about
better
alignment
with
the
engineering
as
we
go.
B
This
is
a
pilot
as
I
said,
this
is
experimentation,
so
it's
aimed
for
us
to
try
this
out,
and
we
discussed
this
with
Whitaker
on
Monday,
where
we
said
hey,
like
I'm
personally
open,
if
I'm
expecting
some
adjustments
to
this
as
we
go
or
I'm,
also
like
I'm,
open
to
see
if
we
will
come
to
a
conclusion
after
two
milestones,
as
we
agreed
before
review
this
and
that
hey
this
is
doesn't
work.
This
is
flowing
us
down,
or
this
is
useless.
I,
don't
really
open
to
see
what
we're
gonna
learn.
B
A
A
A
A
B
B
Next
item
is
also
mine,
and
this
is
another
one
where
an
interesting
discussion
is
happening
right
now.
So
in
this
issue,
so
we
had
a
discussion
with
Darby
few
weeks
ago,
where
he
was
asking
me
a
question
like
in
CI.
We
have
quite
some
issues
where,
where
we
are
working
on
a
bit
more
technical
experiences
that
are
focused
around
the
developer
persona,
for
example,
or
our
technical
personas,
and
where
we
are
talking
about
the
like,
for
example,
or
like
experience
working
with
the
issue,
let
me
choose
llamo
template
as
an
example.
So
it's
not
like.
B
B
So
there
is
user
experience
work
to
that,
but
we
are
not
involving
any
product
designers
into
these
types
of
issues
or
features
because
well
most
often
we
tend
to
think
that
user
experience
is
equal
to
the
user
interface
changes
and
therefore
we
thought-
okay,
maybe
like
labeling
or
like
marking
this
issue
with
some
type
of
sign
hey.
This
is
a
technical
feature,
but
that
still
needs
some
new
acts
involved
with
the
product.
Designer
involvement
we've
been
thinking.
B
Maybe
that
would
be
helpful,
so
I
actually
acted
quickly
and
I
just
went
and
create
their
label
and
got
some
nice
questions
and
feedback
from
Jace
and
then
from
penny.
So
there
is
a
discussion
happening
right
now
in
the
issue.
We
also
just
discussed
the
creation
of
this
label
with
progressive
delivery,
so
there
was
also
like
some
IJ,
some
very
similar
questions
that
you
have
raised
like
it
seems
like
very
do
negative
to
them.
You
acts,
label
and
yeah.
B
However,
people
like
the
idea
of
separating
those
two,
but
there
were
questions
why
we
exactly
need
those
so
I'm
thinking.
Maybe
I
just
need
to
move
this
discussion
into
a
separate
issue
and
first
like
talk
to
people
and
see
if
we
wanna
get
that
highlight
that
that
type
of
involvement
from
the
you
acts
and
then
we
can
move
on
I,
don't
know
if
anybody
has
any
thoughts.
It's.
D
Maybe
we
just
need
like
see
our
UX
:
:,
yeah,
mall,
UX,
:,
:,
a
numerate,
all
the
technical
ones,
and
that
bestie
was
totally
great
I'm
totally
on
board
with
having
the
designer
be
part
of
you
know,
working
on
all
issues,
we've
talked
about
it
before
and
I
think
that
that's
and
be
touka.
You
know:
we've
already
started
working
on
some
things
that
are
like
technical
issues
that
don't
have
a
front
end,
so
yeah
I
think
labeling.
Those
things
is
nice
and
could
help
with
searches
and
sorting
and
different
things
like
that.
D
C
B
I,
don't
want
people
to
think
that
this
is
the
idea
or
that's
the
ball,
so
we
have
to
I
need
to
think
how
we
need
to
totally
avoid
that
to
not
create
that
impression
for
people
but
yeah.
It
sounds
like
this
conversation
is
Sparkle.
They
stop
it
because
particles.
A
lot
of
conversations
we
had
like
spend
like
50
minutes
in
the
previous
meeting,
so
yeah
thanks
for
all
of
your
feedback
and
all
the
thoughts
oh
I'll
check.
B
D
A
Hey
nonny
I
would
be
confused
by
using
just
doing
a
DX
label
because
our
products
are
for
developers
and
so
for
them.
For
me,
they
are
all
of
the
users
of
our
features,
but
I
threw
in
the
labels
there
that
I
found
from
the
issue,
like
you
know,
UX
the
scoping
laid
for
UX
:
:
yeah
more.
You
ask
uncle
an
API
that
makes
sense.
B
C
Just
sorry,
I
was
saying
that
I
have
updated
this
epoch.
That's
a
CI,
UX
feeds
and
I
have
transferred
all
the
issues
that
for
this
milestone,
that
needs
UX
work
and
I've
also
kind
of
assigned
a
size
to
them.
Depending
on
my
understanding
of
how
elaborate
those
design
work
is
going
to
be
one
thing
that
I
noticed,
which
I
think
was
an
oversight
from
my
side
as
well,
is
I.
Think
at
some
point
we
decided
we
would
create
an
issue
too
for
Doug
improvement.
A
Yeah
by
the
way,
so
there
were
two
that
you
and
I
talked
about,
and
one
of
them
you
had
said
they
improved
the
empty
state.
You
said
that
we
think
we
already
have
an
issue
for
it.
So
I
did
go
find
that
issue
on
the
mural
board.
You
probably
see
it
I.
Just
if
you
move
your
cursor
to
the
right,
I
see
you
out
there
on
the
board
with
me
as
well.
It's
the
one
that
it
wasn't
sure
no
I'm
high.
A
Do
you
see
my
cursor
I'm,
highlighting
the
one
right
now,
I
wasn't
sure
if,
since
we
were
only
gonna
do
one,
if
we
wanted
to
stick
with
this
one,
that
I
don't
think
is
done.
Let
me
see,
let
me
go
at
the
time
when
I
looked
at
this
issue,
it
wasn't
done.
The
other
thing
is
we
I
put.
So
oh
wait
is
closed.
Interesting,
okay,
so
oops
can.
A
C
D
A
Ways
so
when
V
Takei
and
I
were
looking
at
this,
we
are
graphing
out
the
feedback
on
the
public,
dag
beta
feedback
issue,
and
so
we
pulled
out
a
few
of
the
proposals.
Is
not
everything
from
the
insights
that
a
few
and
put
it
on
these
this
graph,
and
then
we
thought
maybe
the
ones
on
the
furthest
right
quadrant.
Here
both
the
improves
the
content,
one
and
the
one
that
maybe
just
hovering
on
improve
the
empty
state.
A
We
would
take
at
least
one
into
13.3,
because
all
the
other
ones,
a
lot
of
them-
require
some
design
work
from
Vedika.
We
didn't
want
to
try
to
do
design
and
implementation
in
the
same
milestone,
so
I
went
out
and
I
found
the
I
found
this.
So
it's
already
done
in
13.2,
but
then
I
took
a
pause
b.
Touka
and
I
realized
dag
falls
under
Jason
now,
13:03.
D
D
D
A
D
C
Think
if
you're
talking
about
the
mural
board
does
another
update
that
I
wanted
to
give
that
which
I
thought
I
would
be
giving
in
the
research
meeting.
But
I
spoke
with
Lori
and
I
asked
her
like.
How
do
we
follow
up
with
the
participants
who
are
very
interested
in
giving
feedback?
They
probably
wrote
a
lot
on
the
feedback
issue
and
how
to
get
in
touch
with
them
to
probably
investigate
further
and
I
have
already
started
to
schedule.
B
A
A
A
A
A
D
A
D
Have
conflicts
with
so
many
of
the
CIA
safety
meetings.
I,
don't
know
like
that.
I
think
that
one
is
what
I'm
not
able
to
attend:
I'm,
also
not
able
to
attend
15
meeting
and
DAGs
mine
I,
don't
mind
you
representing,
of
course
you're
more
than
capable,
but
if
there's
anything
that
you
need
from
me,
I
guess.
Let
me
know
and
be
happy
to
support,
I'm
sure
it'll
be
fine,
but
I'm,
just
thinking
more
in
terms
of
how
I
can
be
there
to
help,
rather
than
like
me
trying
to
make
sure
everything's.
Okay.
A
A
D
Other
thing
that
you
can
do
that
often
helps
is
just
try
and
knock
things
out.
That
could
be
done
async.
So
don't
let
things
that
could
be
just
a
quick
flag
message
build
up
on
the
agenda
just
just
like
handle
them
as
you
go,
and
that
really
helps
a
lot
to
you.
I
did
notice.
There
are.
It
seems
like
quite
a
lot
of
think
meetings
for
CI
I
was
invited
to
like
eight
or
nine
different
meetings
at
different
times,
and
it
seems
like
a
lot
but
I
don't
know.
A
It
is
a
lot
we've
gotten
the
habit
of
discussing
things
on
slack
sooner
than
later,
and
I
was
just
inspired,
because
at
last
week's
CEO
group
conversation
he
had
a
slide
on
there.
He
always
has
one
that's
things
that
are
on
his
mind,
and
one
of
it
was
his
concern
with
the
Pearl
of
proliferation
of
meetings
and
to
try
to
keep
in
mind
our
default
to
to
work
async
and
so
I've
gone
and
I
like
I've,
been
able
to
reduce,
eliminate
or
reduce
recurring
meetings
on
my
calendar,
and
so
this
was
the
next
one.
D
E
Reason
that
we
look
out
the
UX
research
one
was
that
we
were
finding
that
we
didn't
have
enough
time
to
get
to
talking
strategically
about
research,
so
it
wasn't
tactical
conversations
it's
supposed
to
be
looking
forward.
So
if
we
find
we
have
time
to
do
it
here,
I'm
fine
with
it.
But
that
was
the
reason
we
broke
it
out
because
we
didn't
have
time
to
get
to
that
here.
E
D
A
Like
if
I
look
at
the
agenda
from
the
last
I
mean
the
last
meeting
was
really
short,
it
was.
We
only
had
one
discussion
items
on
that
one,
but
it
was
the
one
before
we
did
run
out
of
time
and
one
before
I
saw
that
time
happened
before
the
last
two
items.
So
it
varies.
Let's
keep
it
for
now
and
then,
like
I,
said,
if
we
think
that
it
makes
sense
to
combine
them,
we
can
later
yeah.
D
Mine
will
be
async
anyway
yeah
a
year,
but
it's
a
good
good
for
everybody.
If
we
can
combine
meetings,
we
can
reduce
think
meetings
and
it's
always
generally
a
good
thing
unless
they're
serving
a
specific
purpose.
But
if
we've
got
a
bunch
of
sequence,
for
example
that
are
consistently
ending
early
and
nobody's
really
going
to
you
then
yeah.
A
D
D
For
example,
oh
and
there's
another
project
that
I
want
to
kick
off,
that
the
release
team
just
did
they're
looking
at
their
Direction
page,
so
the
verified
direction.
I'm.
Sorry
they're,
really
it's
in
our
case
Direction
page
and
they're,
coming
up
with
mock-ups
of
what
their
features
will
look
like
in
three
years,
and
it's
a
really
interesting
effort
where
it
challenges
the
product
managers
to
think
about
what
the
priorities
are
over
a
very
long
time
period.
D
It
helps
us
think
about
the
product
in
terms
of
you
know
like
how
would
we
actually
design
something
that
looks
like
that
and
it
helps
with
sales
and
marketing
and
things
like
that
in
the
board
as
well,
and
so
that's
something
that
we'll
be
sending
out
soon.
That
is
essentially
I,
think
a
research
effort,
but
I've
been
talking
for
units
all
posterity.
A
D
D
Exactly
based
on
some
kind
of
like
I'm
like
it
would
be
great
to
grab
some
customers
and
and
like
talk
to
them
about
it
and
validate
it
rather
than
just
me.
We
could
sit
here
and
come
up
with
something
together
and
probably
pretty
cool,
but
it
would
be
more
compelling
when
we're
telling
the
story
if
we're
like
and
talk
to
these
customers
and
they
had
gave
us
these
quotes
about
it.
D
C
They're
couple
of
things
that
I
updated
Tao
about
in
our
one-on-one
yesterday,
one
was
that
we
would
start
for
CI.
We
would
start
maintaining
good
jobs
to
be
done
red
sheet
and
I
think
that's
going
to
come
in
very
handy,
so
that
would
be
like
a
single
source
of
truth
for
all
the
jobs
to
be
done
listed
at
one
single
place.
Maybe
later
we'll
move
it
to
the
handbook
so
that
we
can
refer
it
in
our
issues
when
we
create
any
and
another
one
was
like.
The
other
update
I
wanted
to
talk
about
was.
C
D
C
D
I
would
prioritize
Jenkins
importer
now
the
events
that
over
any
literally
anything
else
because
it
came
in
as
an
emergency
project
from
the
CEO
it
was
like
sales-
is
telling
us
that
we've
got.
We've
got
customers
blocked
and
nobody
is
nobody's
able
to
buy
gitlab
because
of
this
one
missing
feature,
so
we
scrambled
something
together.
We
gather
requirements,
we
built
it
and
then
sales
couldn't
find
anybody
who
wanted
it,
and
so
the
idea
for
awhile
was
like.
Oh,
you
know,
everybody
disappeared
and
once
you
know
stop
working
because
of
copán
and
everything.
D
Now,
and
so
some
research
too
deeply
and
sincerely
try
to
understand
what
that
gap
is,
is
probably
the
most
absolutely
important
thing
that
we
can
work
on,
because
we
either
need
to
we're
wrong
in
some
ways.
Right,
like
someone
was
wrong
somewhere,
I,
don't
know
exactly
where,
but
it's
easy
to
guess,
but
we
need
actual
data
to
back
up
whatever
we
do
next,
which
could
be
canceling
it
because
nobody
turns
out
was
interested,
but
we
at
the
moment
we
can't
explain
why,
and
we
need
to
be
able
to
explain
why.
E
D
A
A
Yeah
I
agree:
do
you
Lori,
do
you
and
so
I
had
if
I'm
looking
at
the
UX
research
agenda
now
I
had
a
topic
on
the
rules?
Epic,
do
you
want
me
to
leave
it
there?
Do
you
want
me
to
move
it
to
this
meeting
discussion
since
Jason
brought
up
in
number
six?
Let
me
let
me
paste
in
what
I
what
I
had
from
the
other
agenda
I
see.