►
From YouTube: CI/CD UX Team Meeting: October 19, 2022
Description
The CI/CD UX team shares work that is happening in each group and what is coming up that may include cross-group collaboration.
A
Hello,
everyone-
this
is
the
cicd
ux
team,
we're
meeting
today
on
October
19th
and
there
are
some
manager,
announcements
in
the
beginning.
I'll
just
go
over,
and
then
we
decided
this
meeting
that
we're
gonna
switch
up
the
order,
so
we're
gonna
start
at
the
bottom
of
the
agenda.
A
So
there
was
a
there's,
a
thread
for
okr's
Progress.
If
there's
anything
blocked
or
at
risk.
Hayana
was
asking
for
you
to
list
it,
but
it
doesn't
seem
like
anything's
there
and
then
there's
some
upcoming
family
and
friends
days,
dates
that
were
released
for
November
through
January,
and
then
the
talent
assessment
officially
kicked
off
today
and
it's
open
until
November
4th
to
get
that
first.
I
think
this
is
specifically
to
fill
out
the
performance
sheet
that
we
were
all
given.
A
Anything
any
questions
or
anything.
B
A
Right
so
then,
if
we
scroll
all
the
way
down
will
do
you
want
to
start
off,
and
maybe,
if
you
know
if
Erica
has
anything
you
can
go
over
that
too.
C
Yeah
sure
so
I
know
that
Erica
is
also
going
to
be
at
qcon
I'll,
be
there
as
well
Gina
I,
think
you're
also
going
to
be
there
so
be
great
to
actually
see
a
handful
of
people.
C
I've
I've
met
just
a
couple
of
git
lab
team
members
before,
but
I'm
excited
to
actually
meet
people
within
the
department,
so
we'll
be
out
doing
some
research
I
think
she's
doing
Erica's
doing
like
her
own
survey,
that
I
think
Gina
you've
been
working
on
her
with
I'm
doing
something
for
a
distribution
team
like
a
survey
and
some
interviews
and
then
Eric
and
I
are
also
teaming
up
with
the
market
insights
team
to
do
some,
like
buyer
Persona
research,
where
we're
trying
to
identify
people
that
are
likely
to
buy
it
lab
and
then
talk
to
them
for
a
little
bit
and
then
see
if
they're
open
to
like
focus
groups
later
in
the
week.
C
A
One
other
the
the
stuff
that
you're
saying
that
Erica
was
doing
for
kubecon.
I
only
have
insight
into
one
of
them,
which
is
about
Secrets,
but
she's
been.
There
was
like
some
previous
work
that
she
had
piloted
and
ended
up,
getting
like
a
lot
of
data
from
around
I
think
that
one
was
specifically
Secrets
within
the
workflow,
so
kind
of
figuring
out,
like
what
developers
were
expecting,
ideally
for
how
that
would
work
and
she's
going
to
continue.
Looking
at
that
for
kubecon,
but
focus
on
finding
out
metadata.
That's
important
around
secrets.
D
Sure,
thanks
yeah
for
me
not
a
lot
of
updates,
but
mainly
one
of
the
issues
that
I've
been
working
with
and
that
I
shared
the
last
time
was
about
not
really
massed
variables
and
kind
of
what
happened
is
after
discussing
with
the
team,
we
kind
of
agreed
to
take
another
path
and
kind
of
diverge
on
this
and
decorate
secrets
and
variables,
so
I've
kind
of
sketch
out
some
really
raw
wireframes
of
what
that
would
look
like.
D
If
anyone
has
some
thoughts,
please
weigh
in,
but
essentially
the
next
steps
are
going
to
be
to
dive
a
bit
deeper
as
to
what
this
would
look
like
introducing
a
whole
path
for
creating
and
managing
secrets,
and
that
is
the
first
point.
Second
point
is:
you
may
have
seen
this
in
the
uxcicd
channel,
but
there
is
a
proposal
from
an
engineer
Fred
to
redesign
the
pipeline
overview
page.
D
So,
instead
of
having
like
the
pipeline,
I
think
it's
pipeline
graph,
you
call
it
with
the
different
jobs
and
stages
that
would
be
a
different
visualization.
That
kind
of
highlight
more,
like
the
number
of
failed
jobs
and
also
like
higher
pipeline
is,
is
doing
so
I'll.
Be
helping
him
kind
of
iterating
on
this
design,
but
potentially
also
go
through
research
and
validate
it.
D
So
that's
it
for
me
again.
If
you
have
any
thoughts
on
that
feel
free
to
weigh
in
the
issue,
I
think
there's
a
link
to
his
video
that
he
created
in
the
issue.
Otherwise
you
might
be
able
to
find
it
in
the
slack
thread
so
yeah,
that's
it.
D
E
One
looks
good,
I
was
going
through
your
proposal
and
like
crunching
the
comment
box
to
a
small
area
and.
D
E
Landing
straight
on
the
summary
tab:
did
you
also
I
I
haven't
read
through
your
comment,
but
was
there
a
discussion
around
removing
the
failed
jobs
or
that's
something?
That's
okay,.
D
D
E
Okay,
all
right,
so,
first
of
all,
we
had
enabled
tracking
for
a
bunch
of
pipeline
related
actions,
and
now
what
we
are
doing
is
I
will
quickly
find
this
license
link.
E
So
we
are
able
to
get
a
lot
of
information
about
what
are
the
actions
that
our
users
are
performing
more
frequently
and
which
are
the
links
they
are
clicking
on
on
the
pipeline
list
View.
So
we
had
our
monthly
check-in
around
that
information.
Here's
the
dashboard
I'm
linking
it
here
yeah.
This
is
the
dashboard
and
we
kind
of
thought
of
different
ways
in
which
we
can
act
upon
the
information
that
we're
getting
from
there.
E
So,
for
example,
we
already
had
a
bunch
of
concerns
related
to
speed
so,
but
our
front-end
team
did
was
they
used.
Lighthouse
runs
to
figure
out
like
which
are
the
areas
which
are
costing
us
the
most
in
terms
of
performance,
and
how
can
we
tie
in
the
insights
which
are
we
are
receiving
through
this
set
of
data
and
come
up
with
new
proposals?
So
if
you
go
down,
I
have
proposed
a
new
method
to
kind
of
just
suggest
a
proposal,
and
that
would
be
broken
into
three
parts
like
proposal.
E
The
assumptions
that
we
are
taking
into
account
and
the
evidence
to
support
the
proposal,
which
can
be
a
combination
of
both
the
metrics
we're
getting
through
Data
Tracking,
as
well
as
the
insights
from
previous
researchers
and
at
the
end
like
once,
we
have
a
bunch
of
these.
We
would
do
a
round
of
voting
and
so
far.
E
My
idea
is
that
we
would
vote
on
the
basis
of
like
which
one
has
the
least
risky
assumption
associated
with
it,
and
it
would
be
most
impactful
so
keeping
those
two
parameters
in
mind,
yeah
and
then
we
would
just
get
started
on
the
like
design
proposal.
For
that
particular
proposal.
That
kind
of
gets
the
highest
number
of
words
coming
to
the
next
point,
which
is
the
pnps
and
SAS
feedback
assessment.
So
we
Revisited
feedback
from
past
four
quarters
because
we
really
wanted
to
get
to
like
work
on
such
impacting
issues.
E
That
would
have
the
highest
impact
and
we
were
desperate
to
take
a
different
approach
than
just
like
going
through
like
burning
down
through
a
list
of
S1
and
S2s,
because
we
wanted
this
to
align
with
what
our
users
are
feeling
and
how
they
are
like
sharing
their
experiences
with
us.
E
Now,
this
assessment
I
was
able
to
understand,
like
what
are
the
most
frequently
emerging
themes
across
the
feedback,
and
the
two
that
were
most
recurring
were
one
was
definitely
around
improvements
to
talks
like
adding
more
examples
and
improving
the
instructions
around
CI
CD
and
the
next
one
was
reducing
the
number
of
steps
for
primary
task.
E
This
was
like
a
lot
of
users
mentioned
like
share
feedback
around
it,
taking
a
lot
of
time
and
a
lot
of
number
of
clicks
to
get
and
to
perform
an
action
or
to
perform
a
task
which
we
can
say
is
primary
to
the
area.
So
we
want
to
make
a
collection
of
all
the
existing
issues
which
are
sauce
impacting
which
relate
to
this
insight
and
bring
them
together
in
an
epic,
with
a
very
clear
exit
criteria.
E
A
Voice
that
one
this
was
related
for
your
to
your
first
topic.
It
was
it's
just
interesting
that
that
that
issue
is
more
about
like
load
performance,
which
makes
perfect
sense
and
that
we
have
in
pipeline
insights.
We
have
a
feature
around
load
performance
and
it's
supposed
to
help
track
those
types
of
things,
but
it's
clear
that
the
products
that,
like
that
your
team
is
using,
is
showing
results
or
data
in
much
more
depth
than
what
our
feature
does.
A
So
it
gives
me
some
ideas
of
how
we
could
improve
that
area.
We're
not
even
focused
on
performance
testing
as
like
a
whole
in
pipeline
insights,
but
something
for
the
future,
at
least
that
we
could
think
of.
E
I
wasn't
aware
of
this
so
far,
and
this
is
the
first
time
I'm
looking
at
one
such
product
that
provides
these
informations
yeah
yeah.
They
do
a
good
job
all
right.
So
that
was
me
passing
it
on
to
Emily.
F
So
last
week,
I
was
kind
of
wrapping
up
our
solution.
Validation
around
pending
deployment
approvals
into
do's,
and
just
there
are
some
interesting
stuff
that
came
out
of
this
study.
That
kind
of
correlated
with
some
of
the
competitive
reviews
we've
done.
Slacks
seemed
to
be
the
most
popular
tool.
Users
are
using
to
notify
each
other.
Since
we
didn't
offer
it,
they
were
figuring
out
with
Bots
or
doing
it
manually
through
slack
channels.
F
But,
interestingly
enough,
like
users
were
looking
for
a
way
to
integrate
pending
deployment
approvals
with
slack,
so
they
didn't
have
to
depend
on
the
gitlab
UI,
and
we
saw
this
when
we
reviewed
harness
as
well.
Harness
was
using
slack
Integrations
for
pending
deployment
approvals
more
so
than
their
own
notification
system.
F
So
good
takeaway
of
this
is
we
were
going
to
implement
this
within
to
do's
and
we
think
now
a
good
MVC
is
just
to
allow
users
to
kind
of
integrate
these
deployment
pending
deployment
notifications
within
slack
and
within
their
current
workflow.
So
that's
kind
of
the
way
we're
going
to
take
this.
They
did
like
the
idea
of
being
notified.
They
thought
to
Do's
made
sense,
but
there
was
warnings
about
how
our
to-do's
are
are
pretty
busy
already.
We
have
no
way
to
prioritize
to
Do's.
F
They
kind
of
just
land
in
the
list,
so
I
think
there's
additional
work.
We'd
have
to
do
to
get
them
in
the
to
Do's,
but
they
would
also
see
that
workflow
as
being
something
useful,
just
there's
more
work
in
there,
so
our
MVC
we're
now
landing
on
is
focusing
more
on
Integrations
and
yeah
I
linked
the
research
issue
in
dubs
till
study.
If
you
want
to
read
more
but
yeah
a
big
thanks
to,
will
he
helped
and
supported
with
like
all
stages
of
this?
F
Cool
and
then
the
second
one
is
one
of
the
bigger
design
initiatives
we've
had
is
supporting
multiple
approval
roles
in
the
project
level,
protected
environment
settings
UI.
This
really
gives
users
a
lot
more
flexibility
into
setting
approval
rules.
So
now
people
who
can
improve,
don't
always
have
to
deploy
you
can
set,
who
can
deploy?
F
Who
can
approve
different
types
of
approval,
rules
which
we're
really
excited
about,
because
this
gives
them
a
lot
more
configuration
options
within
the
UI,
whereas
before
we
only
gave
this
through
access
with
the
API
so
excited
for
that
to
come
out
as
well,
and
then
my
last
thing
is
I
did
mention
this
on
slack,
but
I
will
also
be
having
lower
availability
next
week,
I'll
be
using
my
visiting
Grant,
so
I
might
be
just
lower
availability
for
sync
calls.
F
It
might
be
late,
responding
to
messages,
if
you
need
me,
so
that's
more
of
just
an
FYI.
A
All
right,
the
first,
both
actually
both
of
these
items,
are
around
pipeline.
Insights.
I
have
work
going
on
for
a
runner
too,
but
I
felt
like
these
were
more
interesting,
so
the
the
first
one
here
is
about
the
new
artifacts
browser
design.
A
This
also
kind
of
goes
along
with
what
Vita
was
saying
about,
having
basically
like
allowing
for
Less
clicks
to
get
to
the
thing
that
you
need
to
get
to
so
the
browser
right
now.
If
you
were
to
go
into
a
job
and
browse
artifacts
from
there,
you
have
to
click
into
each
folder,
it's
like
it's,
so
there
can
be
so
many
nested
folders
to
be
able
to
get
to
that
final
file.
So
what
I
ended
up
doing?
A
If
you
look
in
the
design
there
I
kind
of
Consolidated,
all
of
those
folders
if
they're
empty
into
a
single
file
pack
and
then
I
just
indented
the
the
file
within
like
underneath
there.
So
it's
clear
that
it's
still
part
of
that
folder,
but
if
you
have
any
feedback
on
that
design,
I
also
linked
a
video
of
me
going
through
the
proposal
in
the
York's
co-working
Channel.
A
If
that
helps
as
well-
and
the
other
thing
I
had
here
was
we
are,
we
did
a
bunch
of
research
to
understand
for
review
apps
kind
of
like
we
heard
that
the
view
app
button
wasn't
prominent
enough
people
couldn't
find
it
so
I
wanted
to
understand
really
why
and
what
was
going
on,
and
we
found
out
that
it's
really
just
not
integrated
into
the
review
workflow
as
much
as
people
were
expecting
it
to
be.
A
So
what
we're
planning
on
doing
is
adding
The
View
app
button
into
that
code
drop
down
when
you
go
to
a
Mr,
and
this
also
allows
it
to
kind
of
be
like
stuck
to
that
Global
header,
because
that
heading
is
sticky
when
you
scroll
down
the
page-
and
it
also
is
closely
integrated
into
the
the
review
workflow
there
there's
some
some
specific
things
where,
like
only
certain
projects,
have
review
apps
enabled
so
we
won't
be
showing
that
menu
item
all
the
time
unless
the
review
app
is
enabled
for
that
project.
A
F
I
want
to
say,
I
love,
this
change,
because
I
don't
know
how
many
times
I
send
trying
to
scroll
down
the
page.
Looking
for
that,
like
view
app
button,
so
having
it,
just
in
one
place
would
be
so
nice.
A
A
B
A
D
B
Oh
okay,
that's
all
right:
okay,
okay!
So
yes,
we're
gearing
up
for
kubecon
and
then
just
in
my
personal
life,
my
child
has
been
sick
and
then
yesterday
we
tested
him
for
kova
and
he
gets
killed.
Oh
no,
do
we
all
have
covered,
so
it's
just
so
I'm
like
oh,
no,
what's
the
conference,
so
I'm
gonna
have
to
figure
that
out
so
will
and
Gina
and
I
so
I
just
I'm
like
waking
up,
because
that's
why
I
was
a
little
late
but
miraculously
I
woke
up.
I
was
like
oh
there's.
B
So
we
now
have
to
kind
of
figure
out
what
to
do
about
my
potential
absence,
but
maybe
I'll
be
healed,
but
what
I
can
do
is
show
share
with
you
this
deck.
If
I
can
do
it
well,
we'll
see
it.
I
can
just
give
you
the
general
updates,
so
we
are
going
to
be
at
kubecon.
Doing
a
lot
of
things
will
and
I
both
have
a
survey
that
we're
Fielding
and
then
we
are
going
to
be
doing
some
interviews
with
buyer
personas.
B
The
PMS
from
Ops
especially
have
kind
of
come
up
with
some
questions,
and
so
people
will
kind
of
come
up
to
the
booth
and
if
they're,
a
buyer,
Persona
they'll
get
put
into
this
buyer
Persona
interview
round
slash
recruitment
for
focus
groups
and
then,
if
they
are
foreign,
not
a
buyer,
then
they
can
either
come
to
the
area
where
we're
going
to
have
a
station
at
the
booth
or
there's
actually
two
booths.
B
They
might
also
just
complete
these
interviews
from
the
PMS.
So
it
would
be
good
to
get
your
eyes
on
that
stuff.
So
I'll
link
that
issue.
We
have
like
seven
questions
that
we're
going
to
ask.
B
And
then
we've
set
up
qualtrics
so
that
all
of
those
questions
and
the
questions
for
the
buyers
and
all
the
other
questions
are
in
qualtrics
and
then
that'll
be
a
note.
Taking
mechanism
where
attendees
can
kind
of
take
notes
on
those
interview,
questions
and
then
James
was
going
to
kind
of
lead
those
PMS
in
a
sus-like
approach,
where
he
kind
of
summarizes
it
in
an
issue.
The
findings
and
then
we're
going
to
invite
people
to
follow
up
with
those
participants.
B
So
I'm
sure
it's
all
going
to
work
out
and
now
miraculously
not
have
coveted
in
like
a
day.
I
can
go
yep
so
and
besides
that
we're
working
on
the
prioritization
stuff
for
Q4.
B
So
if
you
haven't
had
a
chance
yet
it
would
be
good
to
link
the
Q4
projects
that
you
want
and
we're
going
to
put
that
through
the
research
prioritization,
but
because
also
our
PMS
are
going
to
be
at
kubecon.
B
We're
going
to
wait
to
finalize
that
until
everyone
gets
back
on
November,
8th
and
another
thing
that
I'm
probably
going
to
ping
you
about
is
I'm
gonna.
Try
to
do
the
research
prioritization,
the
research
sense
of
this
I
forget.
We
have
like
a
longer
name
for
it,
but
basically,
where
I
go
back
through
and
according
to
our
research
questions.
Like
summarize,
all
the
research
we've
found
for
this
quarter,
so
that
will
be
something
I
can
link.
B
So
I'll
just
be
asking
you
to
include
studies
that
you
would
like
kind
of
included
in
that
synthesis,
and
the
idea
is
our
great
Jackie
will
return,
and
we
want
to
like
have
that
as
a
way
of
helping
her
come
back.
Is
to
kind
of
summarize
the
research
so
far
and
if
I
don't
go
to
kukon
I'm
going
to
be
really
bored.
B
And
then
I
think
another
thing
to
put
out:
there
is
I
and
I
posted
this
on
slack,
but
to
help
us
like
digest
the
secrets
findings.
As
a
team
we've
set
up
three
meetings.
The
first
is
totally
just
optional
and
informal
and
will
be
me
reading
out
the
the
secret
features
prioritization
survey
responses
with
some
PMS
like
cross-functionally
PMS,
so
they'll
be
like
in
that
report.
We
can
do
like
a
q,
a
and
then
the
second
week
of
November.
B
We
have
a
think
big
set
up,
and
so
you
all
should
attend
that
and
I
will
maybe
easier
for
me
just
to
post
the
slack
meetings,
but
there's
two,
the
slack.
Oh
my
gosh,
the
slack
comment
where
I
linked
all
of
these
things,
which
is
in
the
cicd
channel,
but
there's
two
time
zones
so
that
should
hopefully
work
out
for
everyone,
and
hopefully
you
guys
can
attend
that,
and
hopefully
we're
getting
this
on
your
Radars
really
enough,
so
that
you
can
plan
around
that.
A
B
C
E
B
E
B
At
the
at
the
end,
the
last
one,
a
lot
of
people
kind
of
had
it
I
was
like
really
like
OCD
about
it
and
I.
But
did
you
know
this
story?
I
was
I,
didn't
get
it
at
coupon
and
traveling
to
Spain,
and
then
I
came
home
and
my
partner
had
it
yeah
I.
Remember
that
so
it's
just
you
know
whatever
we
can
do,
but
but
yes,
so
Gino
we're
gonna
need
to
kind
of
decide
today,
like
a
backup
plan
for
the
yeah,
the.
B
A
B
We're
gonna
probably
need
to
meet
and
we
just
because
I
can
scope
down
that
whole
project.
Okay,
if
we
want-
and
so
it
just
depends
on
what
you
want
to
do-
I
had
even
talked
to
James
about
when
we
met
to
talk
about
the
think.
Bigs,
James
and
I
had
kind
of
talked
about
scoping
that
down
anyway
and
just
making
the
question.
Could
we
do
this
research.
B
A
Definitely
I'm
around
like
all
afternoon,
my
okay,
it's
fully
fully
available
so
good
to
do
that.