►
From YouTube: CI/CD UX Meeting - 08/02/2023
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
Hey
everyone:
this
is
the
cicd
ux
meeting
on
August
2nd,
starting
with
our
standard
topics
with
the
Hannah
wanted
to
mention
the
Q3
okrs
are
being
defined
and
will
be
available
soon,
so
she'll
share
more
info
once
the
details
are
known,
but
two
of
the
okras
might
send
her
around
the
ux
department,
completing
the
neurodiversity
training
and
resolving
usability
benchmarking
findings
across
verify.
A
Awesome
so
then,
we'll
move
into
the
product
design
section
I,
can
voice
hyannas
because
there's
important
notice
here
about
how
she'll
be
providing
coverage
for
switchboard
at
20,
so
Hands-On
design,
work,
Milestone,
reviews
and
team
rituals,
and
this
will
continue
until
that
role
is
backfilled
and
they
expect
to
onboard
five
customers
to
get
lab
dedicated
by
the
end
of
Q3,
which
puts
a
focus
on
the
ux.
A
So
during
this
period,
if
you
need
support
or
if
she's
blocking
in
any
way,
please
be
explicit
about
what's
needed
and
you
can
ping
DM
on
slack
or
she's,
most
responsive,
okay
and
then
currently
working
on
email,
notifications
and
the
onboarding
flow
Gathering
requirements
to
improve
design
proposals
for
the
deployments
page
for
switchboard.
So
lots
of
updates
to
existing
work
and
that'll
be
kind
of
where
her
Focus
time
will
be,
and
she
shared
a
customer
call
from
switchboard
on
Monday.
C
B
Okay,
I
have
attached
a
report
that
I
wrote
up
about
the
mental
model,
research
study
and
there's
a
lot
of
good
insights
that
came
out
of
it,
I'm
working
on
recording
like
a
video
and
sending
it
out
today
explaining
a
summary
of
that
as
well.
But
right
now,
one
of
our
next
steps
is
to
run
another
survey,
which
is
in
progress
and
already
have
some
data
from
it
to
finalize
the
terms
that
we
use
to
explain
the
concept
buckets
and
then
we're
also
asking
users
where
they
use
those
things
in
their
workflows.
B
This
will
help
us
like
get
a
better
idea
of
really
what
they
think
those
words
are
and
then
we
can
also
use
that
to
look
at
like
pain
points
within
the
workflows
that
they
bring
up.
B
And
then
the
next
item
is
that
our
next
big
thing
for
runners
to
look
at
Runner
cost
visibility,
which
is
focusing
on
users
who
bring
their
own
runners.
So
we're
not
going
to
be
touching
shared
Runners
on
SAS,
because
we
use
like
our
own
pricing
method
for
those
users
and
an
example
of
this
is
like.
B
If
you,
you
create
a
runner
through
AWS,
we'll
provide
you
visibility
into
how
much
that
Runner
is
costing
you
like
the
machine
and
to
run
the
jobs
and
everything
so
I
attached
the
issue
there
Darren
added
like
a
ton
of
details
and
we're
just
gonna
work
on
scoping
it
down,
but
I
talked
about
the
team
today
and
we're
gonna
run
a
think,
big
and
think
small
on
this,
because
my
goal
is
to
have
the
process
of
getting
the
first
iteration
for
this
feature
out
faster
than
what
we
did
for
the
MVC
dashboard.
A
Of
me
so
I
think
I'm
next,
if
no
one
has
any
questions
so
I'm
just
making
progress
this
week
on
updating
kind
of
artifacts
for
design
Sprints,
starting
with
issue
templates
and
slide
Decks
that
you
can
reuse
during
the
Sprints.
A
Just
let
me
know
if
there's
anything
design,
Sprint
related
you'd
like
to
see
templated
out
and
I'll
try
and
get
to
work
on
some
of
those,
so
some
of
the
ones
I
haven't
gotten
to
are
each
day
of
the
Sprint.
Those
issue
templates
as
well
as
I'm,
going
to
make
videos
that
you
can
share
asynchronously
on
how
to
conduct
sort
of
these
activities
or
the
homework
we
were
calling
so
there's
a
few
things
I'm
still
working
on,
but
just
wanted
to
share
progress
on
that.
A
The
second
thing
being
our
we
did
internal
research
on
populating
a
service
list
two
weeks
ago,
now
we're
doing
external
research.
The
good
news
is,
the
results
from
both
internal
and
external
are
really
aligning
we're,
seeing
a
lot
of
the
same
feedback
from
both,
which
is
great,
so
we're
hoping
to
wrap
that
up
in
the
next
few
weeks
and
move
on
to
prototyping
and
MVC
approach.
From
this.
A
Yeah,
that's
what
we
were
worried
about.
We
were
like
I,
hope,
gitlab,
isn't
using
git
lab
differently
enough
that
the
results
will
differ,
but
there's
a
lot
of
the
same
things,
which
is
really
great.
D
Okay,
there
are
no
questions.
I
can
proceed
with
mine.
So,
first
of
all,
thank
you.
Everyone
for
providing
feedback
last
week
on
the
secrets,
POC
prototype
and
you'll
Now
find
a
device
designed
on
the
same
figma
file.
D
The
next
step
for
me
is
to
create
an
interactive
prototype
and
share
the
link
with
everybody
who
has
signed
up
for
the
only
adopter
program
for
secrets
and
then
we'll
just
keep
our
fingers
crossed
to
see
what
kind
of
feedback
Flows
In
beyond
that
I
mean
that
that's
a
big
thing
that
has
that
is
about
to
be
wrapped
up
this
week.
So
and
now
I
can
start
looking
at
CR
job
token
and
variable
work
again.
D
Yeah
besides,
that
I
had
a
chat
with
the
application
security
team
here
at
gitlab
I
as
an
I
organized
a
meeting
with
our
engineering
manager,
product
manager
to
security
engineer
from
appsec
and
myself,
and
it
was
really
interesting.
So
I
tried
to
understand
like
how
is
it
that
they
are
currently
like
their?
D
How
are
their
workflows
related
to
Secrets
being
fulfilled
today
with
the
current
setup
for
features
that
we
are
offering
and
they
kind
of
walked
us
through
it
and
also
contributed
to
the
user
story
map
that
we've
been
working
with?
So
we
definitely
have
to
keep
in
mind,
and
one
of
the
learnings
was
that
we
have
to
keep
in
mind
the
special
kind
of
responsibilities
or
special
permissions
that
any
security.
D
Any
any
individual
responsible
for
taking
care
of
the
security
in
any
team
organization
would
be
requiring
and
that's
going
to
differ
a
little
from
what
we
are
going
to
be
thinking
for
maintainers
owners
so
yeah.
This
was
a
really
good
meeting
for
us
and
that's
all.
C
Oh,
if
you
don't
have
any
other
question,
I
can
move
on
to
mine.
I,
don't
have
so
much
to
share
for
this
week,
so
we
had
a
meeting
last
week-
and
this
is
this
issue
that
I
linked
here
is
the
outcome.
So
we
decided
to
take
a
step
back
and
then
just
like.
Let's
just
forget
about
like
everything
and
then
we
just
focus
on.
C
Flow
and
then
their
context
and
then
see
what
is
the
best
solution
for
them
and
then,
in
which
context,
are
they
starting
to
author,
the
ciamo
pipeline,
or
maybe
they
want
to
come
in
to
the
ciao
and
then
maybe
they
want
to
just
make
some
edit
and
then
probably
that's
the
point
that
they
started
looking
into
the
CIA
template
component,
so
I
like
to
just
list
down
all
the
possible
contacts
and
then
make
a
journey
map
for
itch
workflow
and
things
like
Gina
has
one
question:
do
you
want
to
verbalize
your
question?
Gina.
B
Yeah,
it's
a
little
it's
kind
of
related
I
guess.
I
just
had
a
question
on
the
progress
of
the
cicd
catalog
and
the
navigation
effort,
because
I
saw
on
that
page
now
that
foundations
team
isn't
allowing
navigation
changes
until
January
of
next
year
and
I
was
wondering
like
how
that
impacts.
Your
team
progress.
C
I,
think
of,
of
course
it's
I
I,
don't
know
at
this
point,
because
we
already
decided
to
take
a
step
back
and
then
like
based
on
the
outcome
that
I
come
up
with
like
with
the
journey
map
or
whatever
design.
Then
we
are
going
to
discuss
okay,
which
is
the
best
placement,
so
the
short
answer
would
be
no
I
guess
so
from
my
understanding.
So,
okay,
probably
the
product
navigation,
is
the
best
location.
C
B
Yeah
that
does
one
of
the
things
I'm
in
our
team
call
for
Runner.
Today
we
were
bringing
up
the
fact
that
our
project
runner's
views
and
settings
and
everywhere
else
it's
in
the
navigation
like
in
build
or
an
admin
area.
B
It's
still
called
CI
CD,
but
same
thing
and
I
was
like
yeah
I
mentioned
that
your
team
pipeline
authoring
is
like
going
through
this,
and
it's
been
quite
a
struggle
and
yeah
I'm,
just
I'm
a
little
nervous,
considering
what
I've
seen
from
the
stuff
that
you've
gone
through
already
so
I
might
end
up
talking
to
you
more
about
it
depending
on
I
might
create
an
issue
just
to
get
like
their
input
so
far,
because
someone
actually
commented
about
it
on
the
navigation
feedback
issue,
they
were
like.
B
C
See
yeah,
so
my
suggestion
would
be.
Maybe
you
already
started
to
getting
more
numbers
and
data,
and
also
those
verbal
feedback
from
users
and
then
just
be
ready
to
have
those
conversation
with
the
foundations
and
once
you're
really
sure
about
like
okay.
This
is
the
good
place
for
the
runner
yeah
that'll
be
mine.
Only
suggestion.
Thank.
B
D
So
I'm
going
to
join
the
band
in
you
know
and
I
think
to
Gina's
point
that
most
things
that
we
are
placing
in
CI
CD
settings
I'm
not
like
very
aware
of
what's
happening
with
the
other
settings
option,
but
with
CI
CD
settings,
those
particular
items
are
facing
discoverability
discoverability
issues
and
I
think
we
just
need
to
see
that
what
we
can
do
and
it's
impacting
kind
of
70
percent
of
the
item-
that's
inside
the
settings.
D
A
D
I
have
an
observation
there
that
in
most
of
the
other
products,
because
we
did
a
competitive
Revolution
recently
so
I
was
just
like
passively
looking
at.
There
are
many
options,
our
like
anything,
that's
placed
under
settings
in
any
of
these
sections.
It's
actually
cascading
in
two
steps
and
that's
not
the
case
with
other
products.
They
have
their
settings
navigation,
separate
from
like
everything
all
together.
So
it
doesn't
feel
like
everything
is
very
hidden.
C
Yeah
and
the
one
thing
I
noticed
is
sometimes
we
just
put
things
like
to
configure
also
inside
the
settings,
and
is
it
really
settings
or
is
it
something
to
configure
and
yeah?
That's
sometimes
confusing
to
me.
So
maybe
this
is
a
good
opportunity
for
all
of
us
to
I.
Don't
know.
Do
some
fun
work
like
settings,
UI
version
two.
A
Well,
yeah,
we
even
talked
about
just
removing
protected
environments
from
the
settings
and
just
moving
it
into
the
edit
environments
page
because
we're
like
that
makes
so
much
more
sense.
Actually
it
does.
Actually
it
does
yeah
and
then
maybe
have
an
overview
in
settings,
but,
like
I,
don't
know
it
for
us.
It
doesn't
quite
make
sense
why
it's
sitting
there.
B
D
A
Yeah
just
wanted,
if
there
are
any
other
it
looks
like
research
is
both
away
this
week,
so
I
don't
think
we'll
have
anything
from
them.