►
From YouTube: CI/CD UX Meeting - 2021-08-25
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
august
25th
2021..
A
We
have
a
couple
of
fyi
items
and
read
only
please
check
them
out,
and
I
also
want
to
voice
an
announcement
I
made
yesterday
during
the
ux
weekly.
We
made
some
updates
to
the
ux
scorecard
process
that,
of
course,
I
didn't
link
here,
but
we
pretty
much
removed
the
heuristics
table
so
before
you
had
to
go
through
the
process
while
evaluating
and
rate
every
single
aspect
of
the
experience
right.
A
So
if
this
button
meets
heuristic
abc
and
then
scored
that
it
was
too
much
and
we
removed
that
to
match
the
changes
that
we're
going
to
propose
for
the
comparator
evaluation,
so
I'm
going
to
link
here
the
merge
requests
for
you
to
see.
So
I
think,
but
the
both
of
you
right
are
working
on
that
kr
gina
and
daniel
for
the
for
the
horrific
valuation.
So
just
keep
in
mind
it's
one
step
less
that
you
have
to
do
so.
It's
a
good
change
right
and
did
I
have
a
comment?
B
Yeah,
I
just
wanted
to
say
I
so
I
ended
up
using
it
purely
because
I
haven't
done
one
of
those
exercises
before
and
I
wanted
to
learn
kind
of
how
the
heuristics
fit
in
and
becca
had
opened
up
this
issue.
That
is
about
possibly
keeping
somewhat
of
the
heuristics
in
the
score,
at
least
the
scoring
process,
and
I
just
wanted
to
say
that
I
I
do
like
I'm
not
really
sure
how
we
would
score
it.
B
A
I
was
saying
that
you're
still
going
to
grade
the
experience,
but
as
a
whole,
we're
going
to
use
you're
going
to
use
the
the
rubric
grading
to
rate
that
the
whole
score
scorecard.
So
is
this.
Is
the
the
merger
question
linked
here
right
to
the
issue
the
becca
open?
I
think
it's
a
it's
a
good
discussion,
it's
valid,
but
the
idea
is
that
you
don't
have
to
make
that
scorecard
process
so
complex
right.
A
That's
also
why
we
removed-
and
we
clarified
when
to
do
the
heuristic
versus
when
to
do
the
a
testing
right
or
just
the
interviews,
not
at
the
end
sorry
interview
with
you
with
the
some
internet
external
customers.
C
Yeah,
for
me,
it
gets
a
little
bit
complicated
because
the
merge
request,
the
the
grading
rubric
is
in
a
google
spreadsheet.
So
the
merging
quest
is
not
necessarily
editing
it,
but
if
I
understood
it
correctly,
the
idea
is
that
we
should
go
over
each
one
of
these
heuristics,
the
visibility
of
system
status,
user
control
and
freedom
etc.
For
the
whole
experience,
not
for
each
specific
point
that
we
go
through.
A
And
I'll
tell
you
what
I
did.
I
think
I
did
the
first
one
of
the
first
court
cards
when
we
came
up
with
with
this
framework
and
it
used
to
be
overly
complicated.
A
It's
just
a
yeah
double
the
effort
to
score
that
experience,
and
I
think
especially
now
that
we
are
with
going
to
some
of
these
evaluations
with
a
focus
on
usability
or
onboarding
new
users
right.
So
you
have
some
of
the
heuristics
in
mind.
I
would
say
that
yeah
our
top
priority
or
that
you're
really
targeting
during
that
scorecard.
A
But
let's
see,
let's
see
what
the
discussion,
with
with
backup
how
that
will
evolve
yeah,
but
thanks
for
asking
any
any
other
questions
before
we
jump
to
the
next
items,
all
right
then
over
to
will
so
welcome.
Will
the
first
time
in
our
team
thanks.
D
Happy
to
be
here
and
appreciate
the
the
fun
tour
that
we
got,
that
was
that
was
pretty
exciting,
makes
me
excited
to
to
own
a
house,
eventually,
I'm
still
in
an
apartment.
D
So
we
built
out
a
survey
for
that
kevin
took
like
a
first
stab
at
it,
and
then
I've
built
it
out
in
a
qualtrics
version,
so
you're
welcome
to
try
out
that
link
and
give
any
feedback
around
it.
D
I
think
kevin's
actually
coming
back
from
being
out
of
office
tomorrow,
so
certainly
welcome
any
feedback
in
the
meantime
and
then
hopefully
we'll
push
it
out
pretty
soon
and
I'm
looking
a
little
bit
of
the
comments.
Yes,
we
do
have
an
issue,
so
I
will
pop
that
in.
D
Let's
see
sorry
a
little
bit
disorganized
right
now.
I
think
it
is
issue
number
1509.
D
Thanks
appreciate
you
adding
that
so
we're
trying
to
do
that
survey
to
identify
some
numbers
behind
kind
of
what
systems
people
are
using
for
release
if
they're
not
using
get
lab.
D
Why
kind
of,
like
we
kind
of
brainstorm,
some
of
the
reasons
potentially
why
users
might
use
other
types
of
systems
instead
of
get
labs?
So
we
included
that
in
the
survey
as
well,
so
we
can
at
least
get
an
idea
of
what's
out
there
and
then
we're
going
to
do
some
follow-up
interviews
as
well.
D
A
A
Let
me
think
of
of
the
word
the
reach
for
this
research
initiative.
This
survey,
how
different
how
different
it
is
from
the
research
that
we
did
a
year
ago
about
understanding
why
customers
were
not
deploying
with
git
lab,
and
I
linked
here
the
research,
but
also
the
opportunity
canvas
that
there
was
a
solution,
validation
effort.
So
I
was
wondering
if
it's,
if
it's
a
follow-up
of
this,
this
validation
or,
if
you're,
looking
at
it
from
a
different
perspective
or,
for
example,
looking
at
a
different
business
case.
D
So
good
question:
I'm
not
really
familiar
with
the
issue.
I
may
have
seen
this
opportunity
canvas
before
I
know
I
kind
of
looked
over
a
couple
before
diving
into
this
project.
C
Yeah
so
this
this
has
been
a
push
from
cabin,
but
as
far
as
I
know,
it's
two
two
points
that
we
want
to
to
reinforce
with
this
research
on
top
of
the
previous
one.
One
of
them
is,
we
know
that
customers
are
not
using
gitlab
when
we
have
some
pointers
that
that
explain
why.
C
But
we
also
want
to
have
more
visibility
on
what
they
are
using
instead
right
so
understand,
more
the
competitive
landscape
and
and
then
connect
what
we
know
about
customers
today,
to
which
features
they
are
using
in
these
other
other
products.
And
why
and
then
the
second
is,
is
an
ask
more
from
the
business
side
as
well
to
understand
why
gitlab
users
are
are
using
verify
and
and
what
are
the
reasons
why
they
stop
at
verify
and
don't
use,
release
or
maybe
they're,
using
their
verify
features
to
release,
and
not
necessarily
using
the
dedicated
release.
A
No,
that
makes
sense
yeah
thanks
danielle,
for
for
explaining
a
little
bit,
because
I
was
a
bit
of
who
already
are
we
redoing,
something
that
we've
researched
already
like
a
year
ago?.
C
To
be
honest,
I
I
think,
there's
a
little
bit
of
overlap
to
make
sure
that
that
this,
this
iteration
of
the
team
also
builds
the
the
knowledge
around
that,
but
also
pointing
to
to
to
things
that
the
previous
research
started
to
uncover.
But
didn't
did
it
go
far
enough
to
complement
it.
A
A
Well,
I
think
it
now
it's
where
we
were
supposed
to
to
be
right,
but
we
had
two
different
priorities
for
release,
though
yeah
what
you
say
that,
then
you
understand
not
only
why
they're
not
deploying
it's
too
complex,
and
they
just
don't
know
that
they
can
apply
wiggitlab.
But
what
are
they
doing
then,
that
that's
a
really
great
way
to
frame
the
problem.
So
thanks
for
the
for
the
insights.
C
D
C
Yeah,
so
this
is
just
a
quick
share
on
the
problem:
variation
we're
doing
for
environments.
We
currently
have
a
banner
on
the
environments
page
inviting
users
to
reply
to
a
survey
and
it's
going
really
well.
We
have
over
100
responses
already,
which
was
more
or
less
what
what
I
was
expecting
to
have
in
order
to
close
the
research,
but
hayana
left
a
really
good
comment
poking
a
hole
in
in
the
process,
because
we
don't
really
have
a
lot
of
responses
from
from
large
enterprise
customers
and
then
it
dawn
on
me.
C
So
from
that
we
started
a
conversation
and
involved
kaitlyn
as
well
from
from
research
coordination,
so
we're
gonna.
Also
sorry
we're
gonna
also
push
the
the
survey
to
customers
in
first
look
larger
customers
to
see
who
can
balance
out
the
the
pool
of
responses
a
little
bit.
So
the
plan
is
to
run
run
this
additional
time
of
the
of
the
survey
until
the
next
next
week
when
I'll
be
back
from
auto
office,
and
then
at
that
point,
if
we
have
a
good
pool
of
responses,
there's
more
balance
rate.
C
If
we
don't,
then
we'll
wrap
it
up
anyway
and
then
contact
these
larger
customers
directly.
Some
of
them
that
already
replied
some
of
them
from
first
look
to
to
have
some
interviews.
Maybe
there
can
be
some
overlap,
will
between
sorry
one
moment
some
overlap
between
between
the
questions.
You
would
ask
as
a
follow-up
for
the
deployment
and
this
one.
A
C
We
can
it
turned
out
that
the
timing
where
dmr
went
live
was
between
releases,
but
the
next
code
phrase
for
for
the
next
self-managed
version
is
on
the
16th
of
september.
C
So
if,
if
we
have
we,
if
we
still
have
the
the
banner
there
by
16
of
september,
it
will
be
rolled
out
to
to
self-managed
customers,
which
would
actually
be
a
problem,
because
then
it
gives
us
like
one
month
with
the
banner
there
until
we're
able
to
actually
remove
it.
So
I
would
love
to
have
a
more
practical
way
to
add
and
remove
this.
C
I
also
mentioned
in
the
triad
that
we
could
have
wrapped
the
the
banner
in
a
feature
flag
that
would
have
helped,
because
then
we
will
be
able
to
turn
on
and
off
for
sas
customers,
but
the
the
ideal
solution
in
my
my
view
would
be
to
have
some
sort
of
like
hot
jar
like
script,
that
it's
everywhere
in
gitlab
and
then
you
can
configure
elsewhere,
and
then
it
adds
the
banner
dynamically
without
actually
having
to
open
an
mrr
and
update
the
code.
There
is
a
discussion
about
that
for
merge.
Requests.
C
Pedro
is
trying
to
add
a
banner
in
merge
requests
to
do
exactly
this,
but
it's
it's
so
far
is
also
an
ad
hoc
solution.
Like
I
added
on
the
environments
page,
they
want
to
add
on
the
merge
request
page
so
so
there
is
an
opportunity
for
a
more
high
level
collaboration
here
to
make
this
process
easier,
because
for
for
how
simple
it
is
of
an
initiative,
it
was
quite
a
bit
of
work.
C
The
emr
took
a
while
to
be
closed
and
now
like
it's
another
coordination
to
remove
it
again,
so
it
could
definitely
be
made
easier.
A
Yeah,
I
think
you're
touching
a
great
point.
It's
just
so
much
work
for
such
a
right,
a
small,
not
small,
research
itself,
but
what
we
are
showing
to
the
users.
So
I
think
it's
also
good
for
us
to
consider
in
the
future.
Looking
at
who
do
we
want
to
target.
A
Maybe
using
these
banners
directly
on
the
interface
is
not
better.
It's
it's
not
the
best
solution,
yeah,
but
it's
a
good
thing
that
you
went
through
that
process,
and
now
we
know
how
painful
it
is.
So.
Thank
you.
A
I
will
read
nadia's
points:
real,
quick,
she's
participating
in
sync,
both
nadia
and
vitica,
so
nadia
is
working
on
a
couple
of
issues
related
to
jobs
in
the
pipeline
graphs.
So
it's
linked
here
to
design
issues
related
to
we're,
trying
fail
jobs
in
downstream
pipelines
and
also
retry
manual
jobs
in
variables.
A
A
She
documented
the
empty
states
for
pipeline
execution
and
identified
some
of
the
gaps
both
vitica
and
nadia
were
doing
or
helping
out
with
this
akr
for
pajamas.
So
if
you
open
the
issues,
it's
a
foundation
skr
where
the
team
is
reviewing
the
four
empty
states,
four
pajamas
and
evaluating
looking
at
learnability
of
the
features
so
similar
to
what
we
did
for
merge,
requests
they're
going
to
come
up
with
recommendations,
and
then
we
go
into
pajamas
feed
that
information
and
then
do
the
redesign
or
polish
the
empty
states
in
each
stage
group.
A
So
vitica
shout
out
to
gina,
appreciate
your
participation
and
prospective
addition
on
this
issue.
Well,
thank
you
gina
for
helping
me
out
and
there's
also
a
read
only
about
a
ux
scorecard
on
enterprise
management,
so
in
heuristic
evaluation.
A
D
Right
yeah,
so
for
the
read
only
I
all.
D
B
Sorry
about
that
that
was
me.
Let
me
see
if
I
can
grab
that
link
it's
in
the
ux
scorecard
issue
too.
Let
me
just
grab
it.
I
just
did.
This
is
my
first
walkthrough
that
I
did
so.
Hopefully,
it's
good
and.
A
B
B
B
So
this
is
something
that
I'm
shadowing
vitaga
on,
so
I
can
learn
more
about
like
this
picking
up
a
design
issue
and
how
to
go
through
that,
and
it's
about
displaying
usage
of
mac
os
minutes
in
the
usage
quotas
page
so
just
to
give
some
context
around
what
the
current
experience
is
when
you're
looking
at
a
project
today
and
then
you
want
to
see
the
usage
quotas
from
there,
you
can
see
how
much
of
the
pipelines
you
should
usage
you've
used,
and
that
is
tracked
through
ci
minutes.
B
So
I
I
think
that
court
like
correlates
to
just
how
many
minutes
the
pipeline
is
running
for
and
today
we're
we're
using
one
metric,
so
all
of
whether
you're
on
a
mac
or
like
a
linux
operating
system,
they're
all
merging
to
the
same
category.
I
guess
so
this
right
now
like
depending
on.
If
you
have
a
limit
for
the
number
of
minutes
you
could
use,
you
would
either
see
a
limit
like
a
number
or
unlimited.
B
Most
of
us
will
have
unlimited
on
our
like
gdk
instance.
If
you
have
that
running
so
this
was
to
specifically
split
these
minutes
up
into
mac
os
and
linux
now,
and
we
vithika,
and
I
met
together
and
just
chatted,
synchronously
and
came
up
with
this
solution
where
we're
now
copying,
actually
the
same
design
pattern.
B
That's
used
on
the
storage
tab
to
show
two
different,
like
values
in
that
larger
value,
and
so
we
just
use
the
same
thing,
we're
having
the
total
minutes
and
then
the
you
know
linux
and
mac
os
here
and
then
for
this:
we're
not
going
to
change
anything
with
the
progress
bar,
that's
just
showing
the
percentage
of
the
total
that's
being
used.
B
But
what
I
did
do
was
I
created
this
follow-up
issue
if
we
wanted
to
it's
a
ui
polish
issue
to
be
able
to
show
the
two
different
types
within
that
graph,
and
we
kind
of
already
do
that
on
one
of
our
on
our
project
page
when
we're
showing
the
different
languages
that
are
being
used
with
code,
which
I
screenshotted
here.
So
we
could
just
like
reuse
that
same
pattern
but
yeah.
That's
that's
what
we
have
so
far.
B
Is
there
any
feedback
or
anything?
If
there's
any
areas
that
this
touches,
that,
maybe
we
haven't
thought
about,
that
would
be
nice
to
know
too.
If
you
have
thoughts.
A
Thinking
of
the
component
gina
this,
this
progress
bar
that
you
showed
here
is
this:
do
you
know
or
have
you
discussed
it
vitica?
If
this
is
a
reusable
component
that
we
have?
I
don't
know
in
view
or
if
it's
in
the
in
gitlab,
ui
or
even.
A
Okay,
I'll
link
in
the
agenda,
the
the
link
to
the
progress
bar
component
in
pajamas,
and
you
can
have
a
look
later.
I
think
that
it's
built,
but
it's
not
in
use
it's
not
in
production.
Okay.
So
just
keep
that
in
mind.
If
it's
a,
I
know
it's
a
follow-up
issue,
but
if
it's
something
that
yeah
you
want
to
polish
or
you
want
to
reuse
from
a
different
product
area,
you
might
trigger
a
design
system
issue
right
to
improve
that
component
either
before
you
can
use
before
it's.
It's
pushed
to
production.
B
A
Yeah,
so
mine
is
a
heads-up,
so
katie
the
new
product
designer
for
package
is
going
to
join
a
bit
earlier
so
a
week
early.
Actually,
so
next
monday
will
be
her
first
day,
the
30th,
oh,
my
goodness,
it's
almost
september
30th
of
august
and
she's
located
in
new
zealand.
So
not
a
lot
of
overlap
for
most
of
us
yeah,
but
make
sure
that
you,
you
know
you
try
to
schedule
a
coffee,
chat
and
say
hello.
Nadia
will
be
her
ux
buddy,
so
similar
to
what
the
vitica
and
gina
are
doing
today.
A
She
will
be
helping
me
on
board
katie
going
through
the
ux
processes
and
also
helping
her
with
a
similar
exercise.
The
scorecard
exercise
that
gina
is
doing
today
we're
going
to
do
that
for
package,
and
if
you
have
any
questions
about
katie
or
her
role
or
anything
just
let
me
know
we
can
chat
async.
A
B
Yeah
yeah
sure
I
had
mentioned
to
you
all
that
I
was
working
with
boston
high
schoolers
this
summer
and
I
was
running
a
design
workshop
with
an
old
co-worker
and
I
ended
up
writing
a
blog
about
it
if
you're
interested
it's
pretty
long
so,
but
it
was
really
fun
and
I
just
talked
about
some
of
the
things
that
we
did
for
the
workshop
and
how
to
run
something
like
that
in
a
virtual
world
which
was
really
different
and
then,
if
anyone's
interested.
B
What
may?
The
the
woman's
name
is
mary
that
I
was
working
with
mary
and
I
were
going
to
talk
about
trying
to
get
others
involved
and
things
like
that.
So
if
anyone
is
interested
in
maybe
helping
out
with
something
like
that
in
the
future,
let
me
know
because
I
think
it's
really
fun
and
it's
really
rewarding
and
it
really
doesn't
take
like
a
ton
of
work
to
prep
for
or
anything
so
yeah.
If
you're
interested.
Let
me
know.
A
Jina,
can
you
tell
us
a
little
bit
about
what
this
is
and
what
are
you
doing
exactly
just
yeah,
so
we
understood
a
bit
better.
B
B
B
So
there
they
were
interning
at
two
of
the
biggest
hospitals
in
massachusetts,
and
they
were
doing
that
for
the
entire
summer,
and
they
had
these
electives
to
pick
from
during
that
internship,
and
one
of
them
was
this
design
technology,
but
there
was
a
bunch
of
other
ones
like
coding,
more
about
business
stuff
like
that,
and
so
what
we
did
is
mary
is
really
like
involved
in
these
volunteering
opportunities,
and
so
we
teamed
up
with
this
organization
called
pic.
B
It's
like
a
pick
program
is
what
it's
called
and
that's
for
boston,
high
school
students
who
don't
usually
have
opportunities
to
do
stuff
like
this,
would
be
able
to
get
internships
and
then
learn
more
about
ux
or
whatever
it
happens
to
be
so.
There
are
more
internships
like
this
hospital
one
that's
going
on,
but
we've
had
like.
B
A
That's
awesome
and
I
added
here
a
couple
of
links
that
I
know
in
the
handbook
about
how
gitlab
can
support
this
type
of
initiatives.
I'm
not
sure
if
you
already
thought
about
reaching
out
to
people
ops
or
to
diversity,
inclusion.
Folks,
there
is
also
a
section
somewhere
in
the
handbook
that,
if
you
are,
you
know,
participating
or
are
supporting
this
type
of
programs.
A
You
can
add
it
there
and
to
also
make
it
yeah
highlight
it
for
other
members
of
the
company
if
they
also
want
to
to
join
and
understand
more
so
I'll
link
here,
you
can
have
a
look.
Okay.
Thank
you.
That's
helpful.
C
Yeah
there
was
a
slack
thread
today,
leon
from
from
from
the
diversity
and
inclusion
group
created
a
sheet
for
for
to
list
organization.
So
maybe
you
can
add
yours
there
and
then
start
this
conversation.
A
A
A
Then,
if
not,
let's
go
back
to
to
our
lives
thanks
for
joining
it's
good
to
see,
you
will
and
gina
I'll
try
to
make
this
synchronous
meetings
happen
more
after.
I
know
that
now,
with
now
a
team
member
in
new
zealand,
it
might
become
even
a
bigger
challenge,
but
please
let
me
know
how
we
can
make
a
set
up
right,
our
team
meetings,
but
also
our
rituals
to
be
more
friendly
to
your
time
zones.
So
just
reach
out
awesome
good,
see
you
later
good.