►
From YouTube: CI & PA PM/UX Sync on 2020-09-09
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
cipm
ux
weekly
check-in.
I
just
realized
it's
called
ci
and
it's
excluding
our
name
of
our
new
group.
For
those
who
don't
know
there
is
a
splitting
off
from
ci
group
is
group
pipeline
authoring.
Did
you
know
that
lori?
I
think
you
might
be
the
only
one
who
didn't
know
that.
A
Oh,
oh,
what
do
you
mean
at
the
our
ux
at
the
same
time
this
time
last
week.
A
That's
right,
that's
right!
I
completely
forgot,
so
it's
not
much
on
our
agenda
because
I'm
in
the
middle
of
prepping
stuff
for
13.
A
Right
when
we
started
talking
about
how
to
distinguish
our
two
nadias
I
can.
I
was
going
to
write
a
thought
on
the
agenda.
Now
I
completely
forgot.
What
was
it
about?
This
is
going
to
be
a
really
short
sink.
Let
me
think
it
was
about
15
13.5,
oh
yeah,
okay,
so
let
me
go
see
if
I
can
find
the
issue.
So
I
jason-
and
I
have
already
submitted
our
list
of
candidate
issues
for
13.5
and
darby.
A
The
the
ems
darby
and
sam
are
are
darby's
filling
in
for
cheryl,
while
she's
out
this
week,
they're
assigning
that
out
for
engineers
to
weight
those
issues
and
then,
when
that's
done
by
end
of
this
week,
I
think
jason
and
I
are
going
to
oh.
I
just
remember
what
my
thought
was
and
then
jason.
A
A
Communication
has
gone
out
about
the
change,
the
reduced
ci
minutes
for
free
plans
from
2000
minutes
down
to
400
minutes,
and
there
were
comments
both
in
on
social
media
and
also
in
I
think,
issues
that
users
aren't
able
to
see
the
historical
usage
from
past
month,
because
the
usage
quota
page
currently
in
the
ui,
gets
when
the
ci
minutes
get
reset
each
month.
All
of
that
data
also
gets
wiped
from
that
past
month
and
there's
no
place
for
them
to
go.
A
There's
a
date.
In
october,
it
wasn't
october
1st
there's
going
to
be
a
huge
demand
for
being
able
to
see
their
historical
usage,
because
it
gives
them
a
chance
to
know
if
they
have
to
buy
minutes
in
advance
to
see
how
much
they
use
in
the
past.
So
I
created
an
issue
for
it
yesterday,
I'm
thinking
of
putting
it
in
13.5
as
a
candidate,
but
it
requires
some
fast
designing
on
viticus
part
in
order
to
put
it
in
as
a
candidate,
because
we
need
to
figure
out
how
we
want
to
display
this.
A
I
I
proposed
in
the
issue
that
we
put
it
in
the
analytics
section.
If
you
in
the
in
the
right
in
the
navigation
on
the
left,
you
can
go
to
analytics
and
there's
one
for
ci
right
now.
It
shows
data
about
pipeline
graphs,
but
we
could
also
show
data
about
pass
usage
there.
But
this
depends
on
what
you
know
product
designer
wants
to
do.
My
question
is:
how
do
we
want
to
do
it
when
something
comes
up?
That's
urgent!
A
D
So
going
forward,
though
I
had
a
proposal,
I
shared
it
with
nadia
as
well
that
looking
at
all
the
things
that
I
worked
in
13.5
that
I
worked,
I
would
pick
a
set
of
issues
and
try
to
estimate
them
like
how
much
time
I
spent
on
them
and
what's
the
size
and
all
of
that
and
come
up
with
a
number
that
I
could
handle
this
number
with
ease
going
ahead.
But
I
would
also
keep
some
bandwidth
free
for
ux
team,
related
work
and
anything
extra
that
comes
in.
A
Okay,
oh
so,
in
that
in
that
process,
would
you
be
putting
a
ux
size
effort
on
the
candidate
13.6
issues,
and
where
would
I
see
those
right?
I
think
we
have
to.
D
Nadia
shared
an
excel
sheet
that
I
think
dove
and
nadia
are
also
working
with
for
estimation.
So
I
want
to
give
that
a
try
and
see
how
it
works
out.
F
Yeah,
it's
actually
it's
funny
that
it
goes
into
that.
The
item
that
I
added
so
here
I'm
I
am,
I
added
as
a
final
point
in
the
agenda
like
a
link
to
the
issue
and
in
that
issue
the
the
planning,
the
xls
file
that
which
you
guys
talking
about
is
there.
F
A
Okay:
okay,
oh
okay!
So
I'm
glad
that
that's
something
we
can
maybe
adopt
all
right.
So
in
this
case
let
me
I'm
trying
to
find
the
issue.
I
think
I
parked
it
in
canada
13.6.
Let
me
look
at
it.
A
I
created
an
issue
all
right
in
the
thank
you
so
much
nadia
for
always
taking
such
great
notes
in
the
and
by
the
way,
I'm
going
to
switch
all
of
this
to
numbering.
So
I
can
refer
to
it.
In
the
agenda
item
3a,
I
made
the
I
linked
to
the
issue
there.
A
A
Right
now
to
be
conservative,
I
parked
it
in
candid
13.6,
but
we
probably,
if
at
all
possible,
if
we
can
get
the
design
in
in
time,
we
might
want
to
consider
moving
this
to
13.5.
Can
you
prioritize
this
vitka
and
what
I'll
do?
Okay
and
what
I'll
do
is
I'll
leave
whatever
is
already
in
13.5
that
the
engineers
are
waiting,
but
I'm
going
to
take
something
out
from
my
issue
label
from
ci
interactions
and
put
this
in
instead,
if
we
can
get
the
design
in
time.
D
A
Oh
perfect,
yeah
I'll,
confirm
async
with
you
in
slack
that
I
make
sure
I
move
out
the
right
issue.
Oh,
I
think
it's
the
one
where
I
put
it's
a
nice
to
have
or
something
like
that.
So
that's
the
one
that
I'll
d
scope
or
I'll
move
that
to
13.6.
A
Okay,
then
I'll,
swap
these
two
and
put
this
one
in
and
on
this
issue
for
allowing
a
view
of
ci
usage,
historical
data
under
proposal,
I'm
I'm
not
a
hundred
percent
sure
that
is
the
proposal
we
have
to
stick
with
as
far
as
where
we
would
have
this
page
live,
but
I
couldn't
find
a
better
place
for
it,
but
I
would
leave
it
also.
That's
also.
One
thing
that
I
need
input
from
designer
about
vitica
is:
is
that
the
logical.
C
C
A
A
The
group
admin
would
have
a
group
admin
view
of
usage
across
all
projects,
so
they
would
see
the
warning
and
then
also
they
would
get
an
error
on
an
individual.
Mr,
I
believe
I
have
to.
I
have
to
verify
that,
but
I
they
get
some
kind
of
message
that
this
pipeline
can't
run
because
you
you
need
to
go.
Here's
a
link
to
go,
buy
additional
ci
minutes,
and
these
are
only
for
projects
that
are
using
shared
runners,
right,
yeah,
yeah.
A
So
there's
a
couple
of
ways
that
that
gets
communicated
and
it
was
there's
a
faq
page
that
was
emailed
out.
That
also
gives
all
of
the
links
to
where
that
that
answers
all
those
questions.
Where
did
it
go?
Let
me
find
it
and
put
it
in
our
agenda.
It
was
customer
faq
who,
it
is
I'll,
add
it
to
okay.
A
A
Okay,
so
I'll
link
it
there
in
the
agenda.
Oops
whoa
is
that
the
right
link
that
had
a
really
weird,
let
me
click
on
it
to
make
sure
yeah.
A
A
I'll
find
it
and
add
it
to
the
german
dove
okay,
so
that
really
answered
a
question
that
came
up
for
me
yesterday
about
what
to
do
with
this
new
issue.
I
created
I'm
thinking
that
also
when
this
change
goes
live.
A
I
was
wrong.
I'm
looking
at
the
email
that
went
out
to
customers,
it
did
say
effective
october
1st.
So
even
if
we
got
this
into
milestone
13.5,
it
won't
be
available
for
self-hosted
until
october
22nd,
but
the
moment
it's
deployed
to
production.
A
A
A
Yeah
yeah,
I'm
gonna,
I'm
actually
gonna
add
that
to
the
agenda
for
the
ci
engineering
weekly
meeting
just
for
their
awareness.
A
This
is
kind
of
slipping
in
to
is
being
added
to
the
list
that
we
already
submitted
for
13.5
candidates,
and
so
when,
when
vittiga
has
the
design
uploaded
I'll
pass
it
to
the
em
to
have
an
engineer
both
weight
the
issue
and
probably
make
it
the
priority
to
just
get
started
on
it
next
week.
Is
it
next
week
that
the
next
milestone
development
starts?
I
lost
track
it's
next
week
next
week.
A
Well
next
week
is
the
last
week
of
development
for
the
current
milestone
the
well
friday.
The
18th
is
the
start
of
the
new
milestone.
A
F
Yeah,
I
think
we
kind
of
like
touched
that
already.
So,
just
like
additional
awareness,
I
attacked
pretty
much
everyone
who
is
in
this
meeting,
but
a
short
announcement
that,
since
we
have
two
stage
groups
right
now
well
in
ci,
so
I
hope
that
we're
gonna
have
a
little
bit
of
a
better
planning
for
the
ux
capacity
work.
F
I
think,
like
we
have
time
to
dedicate
to
the
actual,
like
planning
a
little
bit
more
right
now,
to
make
it
easier
for
vitica
and
idea
to
plan
the
capacity
and
to
know
how
many
issues
from
the
ux
we
can
take
in
order
to
be
effective
there.
So
the
proposal
is
in
the
issue
and
I
know
nadia
and
dawg
have
been
practicing
this
process
in
the
past
in
ibm.
I
know
we
have
been
proposing
similar
stuff
in
cicd
earlier.
F
I'm
not
sure
how
you
were
already
on
board
or
not,
but
anyway
go
please
go
to
the
issue
and
make
yourself
familiar
and
leave
concerns
or
feedback.
If
you
have
any.
A
Okay,
so
number
five-
I
just
added
there
when,
when
dove
was
asking
about
the
ci
minute
changes
on
number
six
later.
D
Yeah,
so
I
just
wanted
to
confirm
that,
are
we
still
prioritizing
the
same
epic
that
we
thought
is
important
to
work
on
for
the
previous
milestone,
which
is
get
up
and
running
quickly
with
gitlab
ci?
D
In
that
case,
we
can
pick
up
some
issues
from
there
as
well,
for
13.6.
A
Yes,
that
was
my
original
plan,
but
as
of
yesterday,
I'm
thinking
I'm
I'm
thinking.
I
might
need
to
prioritize
anything
around
usage
because
of
the
ci
minutes.
The
the
clearest
case
is
the
one,
the
issue
that
I
mentioned
today,
but
I
was
looking
through.
A
I
was
trying
to
think
from
our
users
perspective
when
this
change
is
effective
october,
1st,
all
the
other
things
that
they're
going
to
need
to
effectively
adjust,
and
I
want
to
pull
some
things
potentially
out
of.
Let
me
find
it
out
of
the
list
of
issues
that
have
the
ci
usage
label.
D
Okay-
so
I
just
wanted
to
ask
like,
is
that?
Is
there
any
communication
that
has
been
rolled
out
to
the
users
that
I
could
also
look
at
just
to
understand
how
they're
going
to
get
affected
by
this.
A
A
No,
it
was
there,
we
have
a
blog
post
that
mentions
it
and
that
email
that
went
out
to
all
of
the
registered
users.
I
think
there
I
think,
the
there's
another
team
that
managed
some
of
the
announcements
on
social.
Let
me
find
the
channel
is
this:
the
channel.
A
Yeah,
so
this,
why
doesn't
that?
Let
me
copy
the
channel.
G
D
Yeah
I
found
it
yes,
so
there's
a
there
is
a
blog
post
that
was
from
the
first
of
september
that
got
upcoming
changes
to
ci
cd
minutes
for
free
to
users
on
gitlab.com.
A
A
I
think
there
was
a
fourth
one,
but
I
can't
think
of
it
yeah.
Oh,
I
have
something
exciting.
Actually
I
wanted
to
to
tell
you
all,
starting
this
month
after
the
13.4
release,
there
is
going
to
be
regular
meetings
at
the
stage
level
between
product
and
the
the
sales
team
for
having
a
regular
feedback
loop
between
what
our
sales
team
and
our
customer
success.
Teams
are
hearing
with
customers
and
prospects
to
sync
with
with
product
managers
and
the
product
managers,
also
to
use
that
as
a
way
to
recruit
participation
from
customers.
A
When
we
from
we
have
a
design
that
we
want
about
a
solution,
validation
or
problem,
validation,
exercise
and
my
question
for,
let
me
I
don't
think
other
stages
are
adding
their
designers
and
I
I
the
the
one
the
first
one
I
schedule
is
september:
24th,
it's
a
thursday.
So
we're
asked
to
do
these
right
after
the
release
of
a
current
milestone
within
five
days
of
the
22nd,
and
I
think.
B
A
A
couple
things
both
both
both
of
that
so
here's
the
agenda.
For
that,
let
me
copy
the
agenda.
I
think.
B
Because
if
it's
to
get
thoughts
on
designs,
that's
not
how
you
should
ever
do
that,
because
that's
basically
a
focus
group
and
you're
not
actually
going
to
get
good
enough
feedback
from
them
to
get
the
solution.
Validation.
It
really
has
to
be
usability
test,
which
is
task
based
and
individual,
so
that
that's
my
word
of
caution
around
anything
that
you
do
around
getting
feedback
on
designs
and
calling
it
solution
validation.
B
A
Yeah
sorry
lori,
I
I
wasn't
really
understanding
your
question.
We
wouldn't
do
it
in
this
session.
It
would
be
a
place
for
us
to
get
participants
from
the
folks
that
are
working
that
are
working
directly
with
customers
and
and
prospects.
So
you'll
see
this
this
agenda
that
I
started
for
that
meeting.
The
the
the
purpose
so
there's
a
guide
there
that
I
link
to,
but
then
I
also
put
in
there
there's
a
there's
gonna,
be
an
issue
board
for
this
meeting
that
drives
a
meeting.
A
But
the
two
points
under
there
is
for
pre-sales
deals
that
need
pm
support,
but
also
when
we
have
features
requiring
feedback
and
we
need
their
support
to
connect
us
to
prospects
and
customers
to
talk
to
and
so
perfect
yeah.
And
so
you
know-
and
I
you
know
I
don't
know
if
designers
are
interested
in
attending
it
or
you
tell
me
hey,
I
need
the
type
of
prospect
or
customer
that
can
speak
to
what
they
want
to
see
in
a
pipeline
graph
or
the
type
of
customers.
A
Recruit
and
and
so
that
both
sides
get
value
both
cs,
both
customer
success
and
product.
F
Yeah,
I
think
it's
a
great
idea
to
try
involving
the
product
designers
and
see
how
like
how
useful
they
find
that
because,
for
example,
in
my
previous
organization,
we
have
been
directly
like
reaching
out
to
the
customer
success
of
the
sales
people,
and
I
was
always
finding
them
as
a
really
important
counterparts.
F
So
it
would
be
nice
if
you
would
set
up
like
a
nice
connection,
nice
relationship
with
those
people
we
like
in
the
past-
we've
been
using
them
as
a
first
testers,
also
for
some
of
the
things
because
well
sometimes
they
might
be
very,
very
close
to
the
customers,
but
in
any
way,
I
think,
that's
like
it's
a
nice
opportunity,
I'm
not
sure
what
what
vidiq
and
nadia
think
but
sounds
like
a.
F
D
A
So
knowing
that
don't
be
concerned
that
the
first
one
that
I
just
added,
vitica
you
and
nadia
s
to
it,
I
need
to
I
need
to
adjust
the
time
for
that,
because
it's
like
not
at
a
time
that
you
can
attend,
but
at
the
time
I
was
not
thinking
to
inc
to
schedule
when
it
would
work.
So
I
think
that
first
meeting
is
a
one-off.
I
don't
know
that
it's
a
recurring
but
I'll
fix
the
later
ones.
A
A
What
another
thing
I
wanted
to
point
out?
That's
interesting!
I'm
sorry
did
I
interrupt
someone.
Oh.
B
I
just
wanted
to
ask
how
you
might
want
to
reach
out
to
emily
and
rupert,
and
let
them
know
that
we're
you're
doing
this,
because
they
may
be
interested
in
the
fact
that
you're
going
to
recruit
users
this
way,
because
they
might
suggest
the
same
to
other
people.
And
then
we
might
also
want
to
get
these
customers
to
to
join.
First
look
as
well,
if
they
aren't
already
in
our
panel.
A
B
B
And
rupert
is
also
a
recruiter,
but
since
we're
not
hiring
right
now
too
much
he's
helping
us
out
with
ux
recruiting.
A
Okay
thanks
laurie
yeah,
so
I
thought
this
was
really
interesting
verify
it.
There
was
a
meeting
across
the
pm
org,
so
each
stage
is
having
its
own,
and
I
just
I
just
took
the
initiative
to
schedule
the
one
for
verify,
so
I'm
hoping
that
it
it's
the
beginning
of
us
having
some
a
real
pipeline
to
hearing
what
customers
and
prospects
are
saying
and
having
an
ongoing
feedback
loop
so
that
we
can
not
only
get
their
feedback
but
also
hear
what
features
are
important
to
them.
A
D
A
Yeah
yeah,
by
the
way
in
that
agenda
that
I
shared,
if
you
go
to
the
under
purpose
at
the
top
and
there's
a
first
bullet,
it
says
ccs
product
feedback
guide.
That
was
the
guide
that
we
went
through
at
our
meeting
last
week
or
at
a
time,
but
take
a
look
at
that.
It
has
a
lot
of
interesting
perspective
and
goals
of
what
this
this
recurring
meeting
will
be.