►
From YouTube: CI/CD UX Meeting - 2020-02-10
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
Welcome
officially
to
the
cicd
ux
team
meeting,
we
have
a
full
agenda
for
today
and
I
want
to
invite
you
to
take
a
moment
to
look
at
the
fyi
read
only
items
we
have
showcase
coming
up,
ui
taxi
ux
day
growth,
they
coming
up
printed
family
days
and
pair
designers
were
assigned
again
so
we're
switching,
and
I
see
that
ian
left
a
comment
here
on
the
txt
ux
growth
day.
A
If
you
don't
have
a
comment,
basically
to
dive
into
that,
and
so
I'm
going
to
start
with
the
the
new
ux
okrs.
I
think
you
all
saw
it,
but
I
just
wanted
to
give
a
heads
up
again
that
I
created
a
tracking
issue
for
all
of
us.
A
The
focus
would
be,
as
you
know,
on
accessibility,
training,
career
development,
and
then
we
also
have
a
ui
polish
epic.
We
all
need
to
identify
at
least
three
items
for
your
stage
group
ens
here.
If
you
have
no
ui
polish
or
no
usability
issues,
what
do
you
do?
I
would
say
good
good
for
you
if
you
don't
have
any
problems
with
that
ian.
A
I'm
going
to
add
this
to
the
agenda,
but
if
you're
watching
this
recording
later
on,
I
think,
if
you
don't
have
any
ui
polish,
then
you
don't
have
to
create
problems
right
for
yourself.
A
first
stage
group
just
make
sure
you're
communicating
why
you're
not
participating
on
this
ocr
and
yeah.
What
else
can
you
do,
for
example,
to
look
into
the
system,
usability
score
or
usability
in
general
in
this
quarter,
and
we
also
have
a
student
open,
open,
kr
on
dog
food
or
portfolio
management?
B
A
Yeah,
there's
no
description
so
far.
I
think
yeah
no
description
at
all
it
might
be.
I
don't
want
to
say
anything,
but
in
my
video
we
drop
it.
Do
you
know
laurie
if
any,
what's
going
to
happen
about
this
kr,
the
portfolio
management,
if
you've
heard
anything,
no,
no
yeah
so
keep
an
eye
on
it,
I'll
keep
you
all
posted
and
then
for
the
very
five
people.
That's
all
of
us
since
ian
and
daniel
are
not
here
yet
we're
gonna
have
a
team
day
on
february
22nd.
So
I
think
you
received
an
invite.
A
A
Plan
for
that
day,
so
please
make
sure
that
you
can
participate,
can
be
very
interesting
for
us
to
always
together
and
get
the
exposed
to
the
same
the
same
knowledge
and
information
around
our
strategy.
A
Julio
me
again,
my
goodness.
A
I
already
know
that
taking's
important,
thank
you
so
much
vitica
for
creating
the
transition
issue.
That's
awesome!
The
super
quick
response,
fair
nadia!
Do
you
have
the
chance
to
to
look
into
the
discussion
or
you
have
any
questions
so
far.
A
A
B
By
the
way,
there
isn't
a
lot
that
that
was
happening
or
was
parked
or
was
in
progress
for
that
particular
category.
So
it
would
be
easier
for
you
to
learn
about
the
past
activities.
D
B
Okay,
perfect,
so
I
think
I
don't
know
in
which
forum
I
kind
of
discussed
about
having
an
issue.
I
think
I
think
lorry
in
the
ux
research
channel,
that
we
want
to
have
like
a
generic
link
to
recruit
users
like
instantaneously.
B
So
we
are
not
going
exactly
the
same
path,
but
what
we
have
thought
of
doing
now
is
so
since
tau
speaks
with
a
lot,
many
customers
as
a
part
of
her
role
and
most
of
those
conversations
they
are
there
on
chorus.
B
So
what
we're
trying
to
do,
or
on
some
other
platform,
what
we
are
now
trying
to
do
is
we
have
one
dovetail
project
for
general
research
around
ci
and
we'd,
be
kind
of
exporting
all
those
data
from
all
different
places
to
one
place
so
that
I
mean
in
case
mostly,
they
always
have
some
valuable
insight
connected
related
connected
to
them
and
yeah.
So
we'll
have
just
one
place
to
go
to
whenever
we
are
in
doubt
or
whenever
we
are
looking
for
some
sort
of
quick
validation
for
a
small
little
decisions.
C
That's
a
great
idea
after
you
guys
do
it
for
a
little
while,
like
I
don't
know
like
a
month
or
something,
and
if
it
goes
well,
I
think
you
should
put
it
in
the
ux
channel
write
a
blog
post
about
it
like.
Let's
get
that
idea
out
there
and
then
even
update
the
handbook
with
a
hey
here's
a
helpful
hint.
You
can
do
this
too.
B
And
I
think
nadia
would
also
have
something
for
you
like
to
share
with
you
at
the
end
of
this,
because
I
mean
users
are
kind
of
suggesting
sort
of
like
integrating
workflows
in
a
way
that
we
hadn't
thought
before.
So
that's
very
interesting.
D
That's
awesome.
I
can't
wait
to
see
and
also
wanted
to
ask
unrelated
note.
Do
you
know
if
it's
like
a
gitlab
white
thing?
Do
we
have
a
chorus
ai
account
that
pm's
use
for
their
calls
or
yeah.
B
Yeah,
so
they
do
use
and
taro
had
suggested
that
I
get
a
listener
access
which
I
did
through
by
placing
an
access
request
and
uploaded
for
me
cool
thanks.
So
you
can
just
go
there
and
copy
the
same
request
and
create
one.
A
I
think
that,
with
the
course
you
I
just
ai,
not
ui,
we
we
all
need
to
get
access
to
it
right.
We
need
to
access
to
request
access.
Okay,
for
you.
B
Right-
and
I
also
did
request
access
for
hannah-
you
would
be
knowing
for
zendesk
and
salesforce
as
well,
because
I
see
that
those
conversations
that
our
times
have
with
the
customers.
They
are
all
important,
and
I
mean
it's
very
important
to
have
a
look
at
those
as
they're
like
happening
there
other
than
somebody
giving
you
a
summary
of
that
on
some
of
the
platforms.
C
A
Can
you
share
with
us
the
link
to
the
the
goodness?
No,
no,
no,
the
dolphin
project
to
make
the
generic
references?
If
you
have
that
will
be
cool
to
let
the
others
come
to
the
agenda
and
see.
Thank
you.
B
B
D
B
C
They
should
use
hey
daniel,
they
should
use
chorus.
I
don't
know
how
how
much
they
are.
So
I
think
jackie
might
split
between
chorus
and
zoom
and
then
put
things
in
dovetail,
so
it
just
depends
on.
I
think
the
cut
the
customer
they're
talking
to
too
versus
they're,
like
whatever
they're
used
to
as
well,
so
just
find
something
and
use
it
consistently.
D
D
C
C
A
Laurie,
just
so
maybe
you
know
this
is
there
and
any
other
than
what
you
already
discussed?
Is
there
a
reason
why
we
use
the
chorus
in
terms
of
not
privacy,
but
the
information
that
we
we
shouldn't,
be
adding
or
updating
on
our
dovetail
or
on
you
know
the
open
channels.
C
Dovetails
not
that
open,
it's
only
open
to
people
in
the
company.
So,
even
though
people
have
viewing
access,
it's
people
with
get
lab
addresses,
so
those
are
like
your
sales
people,
so
they
don't
need
to
go
write.
Anything
they
just
want
to
watch
the
video
or
something
course
is
the
same
way.
I
think
it's,
I
think,
really
it's
like
the
sales
organization
and
pms
thought
hey.
We
need
a
tool,
they
got
chorus,
they
use
chorus.
Then
we
needed
a
tool.
We
got
help.
We
used
dovetail.
I
think
that's
really
where
it
came
from.
C
A
I
think
maybe
we
should
open
a
bulk
access
request,
then,
because
we're
all
going
to
need
at
some
point
to
see
that
so
nadia
since
you're
opening
for
yourself,
can
you
add
my
name
to
the
access
request
too
and
then,
if
other
people
want
sure
yeah.
I
can
just
thank
you.
D
A
Thank
you
so
much
next
up,
it's
vitica
again.
I
think.
B
Yeah,
so
this
was
supposed
to
be
just
a
review
only
but
in
case,
if
anyone
has
questions
or
like
they're
wondering
what's
happening
with
moisture
and
snacks.
So
now
there's
a
very
well
organized
epic,
which
is
in
place,
and
it
has
the
latest
updated
description.
B
It
kind
of
like
talks
about
all
the
major
issues
which
are
in
works
and
there's
also
five
minutes
video
for
like
if
you're
looking
for
an
even
quicker
overview.
A
A
I
have
another
item.
Actually
I
just
wanted
to
share
the
tracking
usability
issues
for
the
fitnessability4kr
and
I
just
wanted
to
share
with
you
how
I'm
doing
for
that
scene.
Runner
if
you
haven't
started
looking
into
this
yet-
or
maybe
you
already
have
epics
like
this-
this
has
been
working
for
me
has
worked
for
me.
A
The
passing
release
management,
so
I'm
trying
to
replicate
this
behavior
for
testing
runner,
so
I'm
creating
like
a
usability
epic
and
then
some
epics
for
ux
that
ui
polish,
so
that
I
can
keep
track
of
all
this
informations
in
one
place,
but
also
help
pms
in
a
way
see
how
many
items
we
have
and
how
we
can
prioritize
them
this
quarter.
So
I
just
thought
it
would
be
nice
to
share
how
I'm
doing
for
the
team
and
if
you
find
useful,
you
know
something
like
that.
Yeah.
D
Yeah
I
just
talked
to
dove
about
creating
dashboards
to
trade,
to
track
ui
polish
and
your
steps.
So
we'll
also
do
that,
but
we
could
probably
link
those
in
the
epics
that
could
be
handy
as
well
to
visualize
our
progress.
A
I
wonder
if
we,
because
we
have
a
performance
indicator
for
your
wax
for
your
accident,
I'm
not
sure
if
we're
probably
going
to
have
one
as
well
for
you.
Why
polish?
But
maybe
we
already
have
an
idea,
I
would
say,
check
on
on
periscope,
because
you
might
have
something
like
that.
But
good
idea
as
well.
A
Where
he
has
to
burn
down
three
or
at
least
to
help
prioritize
so
you're
not
responsible
for
closing
the
ux
step
issues
or
if
the
tpm
doesn't
close
or
don't
prioritize.
What
we're
being
asked
to
do
is
to
identify
them
and
say
here
the
three
low-hanging
fruits
that
you
can
work
on
this
quarter.
So
only
three,
not
a
lot
of
stress.
A
Else
so
one
share
the
fun
thing
who
share
this.
This
medium
link.
B
All
right,
so
I'm
saying
that
I
I
was
like
reading
this
a
few
minutes
back,
so
this
is
fresh
in
my
head.
It's
a
good
comparative
study
between
circle,
ci
and
gitlab,
so
it's
not
kind
of
like
taking
side
of
any
of
the
tool,
it's
kind
of
for
just
like
explaining
how
based
on
what
kind
of
context
and
restrictions
which
tool
you
should
be
going
for.
But
it's
good
to
know
like
the
points
they
have
listed
are
good
to
know.
A
And
I
just
noticed,
I
removed
the
link
to
the
verified
theme
day,
there's
already
some
slides
prepared.
So
I
added
here
to
the
agenda.
Let
me
also
share
here,
so
you
know
what
I'm
talking
about.
So,
if
you
have
a
look,
oh,
they
already
added
content
about
the
vision
items.
So
it's
good
for
us
to
not
be
surprised
about
that.
Coming.
A
B
D
D
I
just
I
just
had
a
meeting
about
it
with,
so
I
just
had
a
meeting
with
growth
with
kevin
their
product
designer
and
with
michael
they're,
a
product
manager
and
we're
starting
to
really
collaborate
much
closely
on
leveraging
the
pipeline
editor
in
github's
onboarding
flows.
So
what
we
realized
is
that
authoring,
a
pipeline
aka
working
with
your
ci
cd-ml
file,
is
a
step
to
enable
many
of
gitlab's
features.
D
For
example,
now
we're
working
on
kind
of
a
joint
efforts
to
make
it
easier
to
onboard
users
onto
code
quality,
so
that
involves
you
to
use
a
code
quality
template
and
to
run
a
pipeline,
so
we're
trying
to
figure
out
how
we
can
maybe
leverage
the
pipeline
editor
to
show
some
additional
guide
guidance
in
addition
to
the
template
itself.
So
we
have
some
comments
in
the
template
that
kind
of
help
you,
but
really
it's
not
very
effective.
D
So
I
will
share
my
screen
actually
and
show
you
what
is
what
what
is
the
main
idea
that
we
have
so
we'll
be
implementing
a
drawer
inside
the
pipeline
editor
that,
as
an
mvc
will
just
hold
documentation?
Basically
just
some
steps
to
guide
you
through
setting
up
your
pipeline
and
we're
playing
with
different
ideas.
For
example,
we
can
have
like
a
very
simple
pipeline
template
that
has
a
typical
structure,
three
stages,
just
jobs,
to
illustrate
how
it
all
works,
and
then
we
visualize
it
right
here,
just
statically.
D
It
was
just
an
illustration
and
then
we
started
thinking
that
okay,
we
have
this
static
content,
but
we
could
also
play
around
with
showing
custom
content
depending
on
what
kind
of
template
they're
using.
So,
for
example,
if
they're
going
through
an
onboarding
flow
to
set
up
code
quality,
then
when
they
land
inside
the
pipeline
editor,
they
will
already
have
the
code
quality,
template
pre-filled
and
we
can
work
with
the
growth
team
and
whoever
is
responsible
for
code
quality.
I
don't
remember,
I
think
hayana
is
it
you?
D
Yeah,
so
we
will
have
to
collaborate
on
this
because,
for
example,
we
could
include
some
additional
information
inside
the
drawer
to
guide
you
through
the
code
quality
template
and
explain
to
you
how
to
set
everything
up.
So
the
mvc
of
the
of
this
drawer
is
currently
scheduled
for
14,
I
think
so
in
13
13.10
we
will
not
be
working
on
it
yet,
but
once
we
have
the
drawer,
it
just
opens
up
so
much
so
many
new
opportunities
for
us,
because
the
drawer
can
hold
pretty
much
everything
or
anything
whatever
we
want.
D
So
yeah
just
want
to
share
it
in
case.
You
also
get
some
ideas
because
we
can
get
quite
creative
here.
I
think.
A
Can
you
link
the
issue
to
the
agenda
nadia,
so
we
can
refer
to
it
later
on
yeah
yep.
Thank
you.
It's
gonna
be
interesting,
and
then
we
already
have
the
iteration
plan
for
it
and
on
after
the
mvc.
A
What
the
next
step
should
look
like
in
a
way
that
we
can
try
to
align,
maybe
the
the
smaller
pieces,
with
the
with
the
pms
to
not
overwhelm
them.
With,
with
the
this
bigger
picture,.
D
Yeah,
so
we're
really
taking
a
step
back.
Oh
what
did
I
do?
I
just
said
the
comment
for
some
reason.
D
Instead
of
linking
the
issue
but
yeah
so
right
now
we're
we
just
have
the
mvc
step
laid
out,
not
really
sure
where
it's
gonna
go
beyond
that,
we'll
be
doing
some
validation,
solution,
validation
and
learning
more
about
where
we
need
to
take
it,
because
at
this
point
for
nvc,
like
we're
very
confident
in
this
mvc
solution,
because
it's
existing
documentation
that
we
already
have
it's
not
a
new
feature.
D
So
we
haven't
done
any
solution,
validation,
but
we'll
be
following
up
with
that,
and
then
we
will
plan
out
the
further
iterations.
But
generally
we
have
an
idea
that
next
would
introduce
code
snippets
that
you
would
be
able
to
copy
and
paste.
So
we
would
add,
maybe
tabs
inside
the
drawer.
So
there
would
be
like
a
getting
started
tab
that
just
tells
you
what
is
cicd
and
what
is
a
pipeline
just
laying
out
some
basic
terms.
Then
there
would
be
a
tab
where
you
can
copy
and
paste
some
very
basic
code
blocks.
A
That's
awesome,
that's
very
interesting
because
this
can
unlock
so
much
potential
and
adoption,
and
you
know
on
that
exactly
what
you
say.
This
flow
from
ci
to
other
features
right
and
those
are
the
things
that
we
don't
have
the
visual
individualization
right
now,
just
with
the
static
file
and
the
text.
So
this
is
a
very
interesting
problem.
I'm
looking
forward
to
the
the
next
steps
and
what
the
the
empathy
and
the
validation
are.
Gonna
look
like.
C
And
nadia
have
you
have
y'all
thought
about
any
support
for
people
who
are
moving
from
a
different
code
to
ours,
different
yaml
to
ours,
because
when
I
did
that
research
for
adoption,
that's
what
it
was
months
ago,
people
were
like
yeah.
This
is
so
different
from
insert
name
of
competitor
here
I
don't
really
know
where
to
start,
and
they
usually
found
themselves
a
stack
overflow,
because
that
provided
them
some
information
on
how
to
get
started.
C
D
Yeah
definitely,
I
agree
with
you
100
and
we
are
not
going
to
work
on
it
just
yet,
but
we
have
this
epic
to
handle
all
of
the
pipeline
editors
empty
states
specifically.
I
need
to
rename
this,
but
this
deals
specifically
with,
like
the
first
experience
empty
states.
So
how?
Where
do
you
come
to
python
editor
from?
And
what
do
you
want
to
do
and
how
do
we
address
that
need?
D
So
we
have
identified
some
different
use
cases
here,
and
one
of
the
use
cases
is
that
you
have
some
kind
of
configuration,
but
it's
not
google
ci
and
you
want
to
translate
it
basically
and
I
think
an
nvc
will
look
something
like
having
an
empty
state
with.
Maybe
a
button
here
like
translate
your
ci
configuration
and
an
nvc
will
be
just
to
link
to
the
documentation
just
to
link
to
the
guide,
and
I
think
that
will
already
be
huge
in
terms
of
connecting
this
workflow.
D
So
it's
not
scheduled
yet
actually
I'll
create
an
issue
following
this
meeting.
But
that's
that's
the
idea.
It's
just
not
prioritized
yet,
but
now
that
the
jenkins
importer
is
moving
to
pipeline
authoring.
I
think
we'll
be
focusing
more
on
it.
B
Yeah
and
on
that
note
nadia,
I
have
added
a
comment
to
the
document.
I
might
have
to
jump
off.
The
call
regarding
the
research
issue
that
lori
just
referred
to
that
could
be
a
big
source
of
information
for
you
when
you'll
start
looking
at
gen
kids
in
portland
awesome.
Thank
you
and
I'll.
I've
taken
this
as
a
point
for
me
that
I
would
add
the
link
to
the
transition
issue
as
well.
All
right.
A
Bye
are
we
inside
my
goodness,
yep
daniel,
feel
free
to
voice?
Your
comment.
E
Actually,
I
have
another
meeting
in
one
minute
as
well.
That's
also
why.
C
E
In
the
doc,
but
very
quickly,
nadia
super
interested
in
this
in
this
solution
that
you
came
up
with
and
anything
that
invests
documentation
the
product
for
me
is
always
a
plus.
D
Yeah,
to
be
honest,
we
haven't
really
gotten
that
far
right
now,
it's
just
static
like
what
we've
shown
the
drawer
is
just
going
to
be
static
documentation,
but
we
will
iteratively
be
figuring
this
out.
So
at
this
point
can't
answer
your
question,
but
if
you
have
any
ideas,
also
hit
me
up
anytime
and
yeah
happy
to
discuss
this
in
more
detail,
maybe
in
a
coffee
chat.