►
From YouTube: CI/CD UX Meeting - 2022-09-21
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
All
right,
so
this
is
the
CI
CD
ux
meeting
for
September
21st.
So
first
off
some
standing
announcements
write
an
update,
so,
okay,
our
progress,
okay,
left
a
comment
here
about
the
SAS,
the
S2
issues
for
package
that
were
planned
for
55
they're,
not
going
to
be
able
to
deliver
on
that.
A
She
already
left
a
comment
and
then
we
already
Airline
on
this
Emily
I
know
that
for
release,
everything
is
already
done
and
I
think
we
have
a
couple
of
issues
open
for
pipeline
authoring,
but
I
yeah.
What
I
just
want
to
voice
is
if,
in
the
future,
what
we
are
looking
at
okrs
rights
that
relate
to
sus
or
issues
that
yeah
we
have
a
commitment
to
deliver.
A
I
think
it's
good
to
align
with
the
stage
groups
with
the
teams
that,
if
you're
not
improving
the
usability
through
the
commitments
of
the
opr,
then
what
is
the
Improvement
that
the
team
is
proposing
right.
So
that's
we
make
sure
they
were
talking
about
a
trade-off
and
not
yeah,
really
prioritized
right.
Cool
things
happen.
But
what's
the
plan
to
later
prioritize
those
issues
or
disability
improvements?
Or
what
are
we?
What
are
we
turning
off
right?
A
So
I
just
want
to
put
this
comment
there,
but
thanks
Katie
for
giving
the
update
and
then
next
up
is
title
assessment.
It's
coming
up
soon
we're
they're
launching
mid-october,
so
October
November,
we're
gonna.
Have
the
talent
assessment,
Logistics
close
exactly
it's
TBD,
so
I
link
here
the
handbook,
page
and
I
think
they're
also
changing
some
things
in
the
process.
I
think
the
the
team
member
assessment
is
going
to
be
optional.
A
The
manager
is
mandatory,
it's
an
interactional,
but
that
might
change
right
now
that
we
are
under
product
things
might
change
in
the
process,
so
yeah
manager
is
going
to
update
you,
but
keep
an
eye
folks
in
the
listening
book,
page
and
Katie's-
not
here
but
I'll
make
the
announcement.
Since
this
is
gonna,
come
out,
it's
gonna
be
a
you
know,
public
knowledge
soon,
so
Katie
is
going
to
transition
to
the
machine
learning
team,
so
she
applied
internally
and
she's.
A
Changing
teams
should
be
managed
by
Tori
starting
in
October,
but
she
would
still
be
covering
for
package
half
the
compare
capacity
on
team.
Backfield
will
go
so
she
will
transition
out
in
15-6,
because
this
Milestone
she's
doing
beautifying
our
UI,
but
once
that
ends
she'll
start
on
boarding
the
new
team
and
then
supporting
package
until
we
backfield
the
role.
Okay,
very,
very
sad
to
see
Keego,
but
it's
such
a
great
opportunity
and
yeah.
You
know
I
think
she
she'll
do
great
in
the
in
the
machine.
Learning
team
right.
A
Gina
is
not
here
today,
but
I'll
just
quickly
go
through
her
updates.
Ronald
Fleet
was
evaluated
at
complete.
So
that's
huge
right.
You
can
check
the
updates
in
the
dovetail
project,
and
then
she
has
an
async
comment
here
about
browsing
a
job
artifact
file,
they're,
going
to
be
working
on
making
it
easy
to
find
that
file
in
this
particular
issue
that
you
link
here.
So
we
can
find
more
details.
What
is
that?
Oh,
it's
a
it's
an
actual!
A
It's
an
Insight
from
for
disability.
That's
called
both
landslides
right.
A
So
that's
that
Emily!
Do
you
want
to
take
over
for
for
release.
B
Yeah,
so
I
don't
have
much
of
an
update
I'm
catching
up
on
like
a
little
over
two
weeks
of
PTO
today,
so
not
much
from
the
product
to
update,
but
I
will
be
hosting
another
release
office
hours
tomorrow,
with
some
focus
on
like
ux
and
front
end,
so
how
Community
contributors
can
get
ux
feedback
front-end
feedback
on
their
contributions,
so
I'll
have
an
update
on
how
that
goes
on
our
next
meeting,
but
excited
because
our
last
office
hours
had
a
pretty
good
turnout
and
people
were
open
to
asking
questions
and
everything.
B
B
And
then
looks
like
vitica
is
also
not
here
and
is
on
some
time
off
today.
So.
A
I
can
voice
Katie's
comments,
as
I
mentioned
she's
working
on
verifying
REI
this
Milestone,
and
now
that
also
the
Nadia
left
light
is
not.
His
last
name
was
yesterday
right,
Katie's
taking
over
some
of
the
issues
and
some
of
the
proposals.
The
Nadia
was
working
on
less
Milestone,
so
that's
super
cool
too
and
then
she's
working
with
Anna
right,
a
front-end
engineering,
and
they
have
a
you
have
a
comment
here.
Do
you
want
to
watch
that.
B
Yeah,
so
I
came
up
with
a
bunch
of
ideas
for
beautifying
our
UI,
but
our
login
page
ended
up
taking
the
whole
Milestone.
So
I
kind
of
have
a
bunch
in
that
issue
that
if
any
are
interesting
Katie
you
can
kind
of
take
them
over
and
but
yeah
our
login
page
went
out.
So
that's
really
exciting.
So
yeah
you'll
see
a
different
login
page
now,
yeah.
A
I
was
like:
oh,
my
God.
It's
in
production
I
saw
that
earlier
this
week
it
was
nice
yeah
thanks
for.
A
The
heads
out
there
and
then
I'll
just
read
out
Katie's
second
Point
they're
working
through
adding
a
banner
to
the
product
UI
as
a
call
to
actions
for
survey.
Customers
stretchable
for
package
1955.
Erica,
is
that
the
good.
C
So
they're
working
on
the
integration
for
package
and
how
they're
going
to
support
that,
and
so
they
wanted
to
get
just
like
tactical
Quant
data
around
which
packages
which
types
of
packages
people
wanted
to
import
and
then
like
how
large
they
are
and
I
think
they're,
asking
like
a
background
question
on
company
size.
C
But
I
think
that
would
be
really
helpful
and
important
because
we
asked
it
in
a
more
Global
Way,
which
is
not
like
just
at
that
one
artifactory
migration.
It
should
kind
of
help
the
team
if
they
can
get
Quant
data
around
like
which
one
might
be
next
based
on
what
people
are
asking
for.
So
that's.
A
Smart,
nice
and
it
is
going
to
be
rolled
out
in
both
SAS
and
self-hosted
great.
It.
A
I'll
copy
Katie
here.
A
We
go,
let's
see,
Julio
anything
else,
any
other
comments
on
the
on
this
one,
then
I'll
just
jump
to
I'm
reading
out
all
the
where's.
Our
team
like
before
going
back
to
the
you
know
all
different
time
zones.
A
So
it's
funny
because
we
had
everybody
like
the
online
for
a
period
of
time,
so
that
was
nice,
Nadia
left,
gitlab
and
then
Kevin
Kevin
komodi
product
designer
for
growth
he's
going
to
be
covering
for
pipeline
all
three
as
a
borrow
until
15
8.,
so
we'll
be
allocating
60
of
this
capacity
and
I'll
I'll
link
here
the
transition
for
verified
pipeline
altering.
A
So
you
folks
can
see
what
work
so
Kevin
will
be
tackling
mostly
the
some
of
the
research
items
so
Erica
they
were
pending
or
their
ongoing
for
pipeline
authoring.
So
he
starts
looking
to
this
tomorrow
and
then
he
will
start
onboarding
on
the
product
stage
next
week
and
there's
already
a
plan
with
those
with
a
PM
about
what
are
the
priorities.
A
There's
a
solution,
validation
for
the
catalog,
like
the
yaml,
syntax
right
breaking
down
that
one
and
also
secret
management,
Nadia
finished
up
the
jobs
to
be
done,
but
then
yeah,
another
dog
wants
to
prioritize
Secrets
management
and
then
start
with
the
design
work.
So
you
have
to
ramp
up
on
that.
A
So
if
you
ask
for
anything
and
then
yeah
just
let
me
know
also
so
I
can
we
can
help
him
out,
but
I
think
it's
good
to
triple
check
if
there's
any
research
pending
or
if
there's
any,
if
the
plans
for
pipeline
altering
have
changed.
So
if
you
need
to
know
what's
an
fdos,
because
these
owners
making
those
decisions
right
now
and
then
there's
also
solution,
validation
for
which
right
trigger
jobs,
I,
don't
think
she
has
started
mother
has
started
with
that
one.
Yet
she
has
the
issue.
You.
C
I
was
thinking
that
I
would
create
an
issue
to
like
walk
people
through
all
the
research
to
date,
because
we
have
like
a
research
program
around
Secrets,
so
good
to
know.
I
don't
have
like
three
weeks.
C
I'll
do
that
next
few
days
and
then
like
Link,
Link,
Kevin
and
then
I
will
also
invite
him.
I
set
up
a
bi-weekly
meetings
every
two
weeks
with
Dove,
so
I
can
also
invite
Kevin
there
and
then,
if
he
has
any
questions,
I
did
get
some
resolution
yesterday,
when
I
met
with
Dove
about
it's
the
double
negative.
But
it's
like
you
should
make
the
unmasking
a
default.
C
That
we
don't
need
research
on
that
in
part,
I
will
be
my
announcement
later.
We
have,
we
were
able
to
because
of
Gina's
health
and
Daddy
has
helped.
You
were
able
to
use
those
Pilots
to
just
get
great
data,
so
we
ran
11
participants
in
our
secret
workflow
and
we
saw
that
debugging
specifically
they're,
using
unprotected
secret
values
and
they're
using
the
cicd
variables.
So,
while
it's
not
good
practice,
Yeah.
B
C
Also
got
one
alienate
users
and
one
thing
that
one
of
them
said
so
the
prompt
in
the
study
is
like
what,
if
we
encrypted
these
values,
what
would
you
do
so
that
would
be
like
the
proxy
for
if
they're
inaccessible
and
one
of
them
was
like
I'll
file
a
ticket
with
gitlab.
C
So
that's
like
an
example
of
like
we
don't
really
need
a
mass
amount
of
influx
in
our
tickets
right.
B
C
Yeah
so
I'll
find
this
specific
I
will
make
a
note
to
comment
on
the
Erica
to
find
issue
and
make
a
note:
don't
need
more
research
like
we're
just
going
to
make
it
configurable
whether
or
not
the
default
yeah
okay,
yeah.
C
A
Half
years
ago,
we
all
I
also
remember
hearing
this
type
of
feedback.
That's
why
I
told
Nadia
like
checking
with
Erica.
Maybe
you
want
to
ask
people
if
I
don't
know
anything
has
changed
and
then
indeed
like
Vault
and
then
sequence
management?
That's
why
we
want
to
separate
CI
variables
from
Secrets
yeah
we're
on.
C
A
Awesome
being
mean
to
issue
I'll
I'll,
give
you
some
of
my
updates
after
everybody
will
always
through
their
items,
but
I
also
have
contacts
and
I
work
on
sequence
management
before
so.
I
can
help
out
there
pointing
out
to
whatever
maybe
historical
knowledge
that
that
you
and
the
team
might
need,
but
I'm,
not
sure
I
I.
Don't
remember
exactly
Dolph
told
me
yesterday,
the
day
before
yesterday,
but
I
don't
know
when
he
wants
to
schedule
any
of
the
secrets
work
for
design
just
yet.
He
has
a
the
team.
A
C
What
one
more
update
around
this
would
be
that
I
I
saw
that
the
engineering
team
was
like
wanting
more
preparation
for
being
tagged
and
needing
to
respond
to
stuff,
so
to
be
proactive
about
that.
I
asked
them
if
they
could
set
aside
a
little
time
for
planning
as
we
get
the
kubecon
secrets.
Research
like
that
should
be
big
juicy
stuff,
so
we'll
want
them
to
like
digest
it,
but
we
also
don't
want
to
ask
too
much
So.
C
The
plan
is
the
first
or
second
week
of
November
to
set
up
a
think,
big
think
small
exercise
around
that
and
those
findings
with
the
idea
that
that's
like
low.
C
A
But
okay
yeah
have
you
talked
to
to
Mark
about
that
Mark,
Newton,
okay,.
A
C
C
He
also
had
the
assistant's
performance,
Workshop
I,
think
I
was
sick,
I
was
sick
and
so
I
missed
it,
but
one
of
my
things
is
to
watch
it
and
follow
up
and
I'm
excited
to
see
how
that
worked,
even
with
our
team
right
of
doing
the
sync,
because
I
have
been
like
no,
no,
no,
we
should
never
do
that,
but
I
think
it
went
really
well
so
I'm
excited
to
watch
it.
We
should
maybe
link
to
it.
C
And
then
mine
are
just
that
we
have
these
four
reports
on
the
secrets
secrets
in
the
workflow.
So
it's
the
debugging
workflow,
creating
a
CI
template,
creating
a
Secret's
policy
and
what
happens
when
you're
blocked
when
your
Mr
is
blocked,
because
you
have
a
secret
value
in
there
and
so
like
tldr
debugging.
We
need
the
unprotected
values
who
we
need
to
solve
for
that,
and
it
will
create
a
bottleneck
in
that
workflow,
especially
because
the
Ops
are
usually
the
only
ones
who
can
access
those
values.
C
So
that's
the
debugging
and
then
the
Mr
report.
We
want
to
look
at,
we
kind
of
looked
at
what
happens
when
you're
blocked
and
now
we
want
to
look
at
when
we
go
to
kubecon.
C
We
could
unblock
you
in
advance
or
like,
and
one
of
the
things
was
that
the
team
said
the
the
create
team
said
that
they
have
something
already
in
place
to
prevent
secrets
from
going
into
a
repository,
but
I.
Don't
none
of
our
users
knew
about
it.
C
Well,
yeah,
so
I
think
the
grander
thing
we
need
to
do,
which
is,
as
we
roll
out
our
secret
solution.
We
need
to
be
like
and
have
you
do
you
know
about
these
things
right
like
so,
it
won't
just
be
like
what
Dove
and
team
are
working
on.
It'll
be
like
our
suite
of
offerings,
so
we
can
put
those
together
based
on
these
findings
and
then
part
of
the
creating
a
secret
policy
which
I
think
is
helpful
for
us
and
will
be
helpful
for
Kevin
is
to
know
that
this
is
like
obvious.
C
But
it's
important
is
that
as
they're
creating
a
policy,
so
there's
like
three
drivers
for
the
policy,
Developers
Ops
people
or
compliance
requirements,
and
so
because
cicd
variables
can
be
a
secret
or
not
a
secret.
An
explicit
step
for
them
is
like
okay.
Is
it
a
secret?
Is
it
not
a
secret
and
I
think
that's
really
helpful,
because
it's
not
my
Rodeo
but
for
the
design,
cow
people
who
are
like
well
we're
trying
to
figure
out
what
the
elegant
solution
is.
C
A
I'm
sorry
I
think
thanks
Erica,
that's
really
helpful
and
I.
Think
Nadia
has
put
together
also
like
so
like
there's
an
issue
with
like
a
list
of
things
around
the
secrets
that
she
thinks
that
she
found
relevant
right
to
onboard
the
ramp
up
on
that
I
think
we
can
follow
up
that
on
that
with
with
Gavin,
see
if
there's
anything
else
that
he
can
consume
any
other
information.
That
is
more
up
to
date,
like
what
you're
saying
about
the
reports
or
yeah
yeah
just
stuff.
A
That
will
be
relevant
not
just
to
build
that
like
that
knowledge
of
Secrets.
But
here
are
the
things
that
we
need.
You
know
to
address
now
on,
as
you
say,
building
that
decision
process
because
yeah
it
should
be
safe.
Okay,
I,
remember:
I
did
the
ux
I
did
a
maturity
scorecard
with
a
Jackie
on
vault
integration
many
moons
ago,
and
no
one
could
complete
the
score
card.
A
The
scenarios
because
it
was
so
complex
to
set
things
up
so
yeah
we'll
see
we'll
see,
yeah
awesome
anything
else,
any
read
only
cool
stuff,
actually
I
I
want
to
I.
Have
a
comment.
That's
what
I
wanted
to
talk
about
so
we're
gonna
have
three
openings
in
our
team
team
product
line
opening
soon
so
for
a
package
for
pipelining
sites.
We're
hiring
another
designer
and
Gina
will
be
moving
to
Runner
full
time.
A
So
now,
she's
played
right
by
playing
cycling,
Runner,
so
Gina
will
move
to
Runner
and
we
have
pipeline
altering
so
I'm
working
on
the
requirements
for
the
roles,
but
once
I
have
those
open
and
we
have
the
jobs
postings
I'm
going
to
share
with
our
team,
and
if
you
know,
someone
already
that
you
think
is
going
to
be
a
good
fit
for
our
team
right,
send
them
my
way.
Yeah
tell
them
to
prepare
their
LinkedIn
profiles
and
their
CVS
because
yeah,
it's
gonna,
be
three
new
hires
this
year.
C
C
So
maybe
that's
like
those
two
things
are
enough
to
make
me
I
mean,
on
the
other
hand,
if
I
can
pull
it
off
myself,
that
might
be
helpful
for
them
as
they
land
so
but
I
just
wanted
to
say
out
loud
that
I.
That
made
me
debate
more.
If
I
should
read
on
that
yeah.
A
Checking
with
them
and
then
I'll
say
also
make
your
recommendation
right,
because
she's
she's
still
no
she's,
she
won't
be
covering
for
Integrations
anymore
and
then
I
also
don't
know
when
we're
going
to
backfill
the
role
right.
It
might
be
that
we
do
like
in
a
month
or
two
or
four
months,
hopefully
not,
but
if
it's
a
go
project
and
yeah.
A
If
you
there
was
a
plan
to
execute
this
year,
let's
say
all
right,
then
she
I
think
they
will
need
to
make
some
trade-offs,
because
Katie
will
only
be
at
50
for
her
capacity.
C
I
think
it's
really
great
that
Katie's
like
worked
with
us
and
then
we'll
do
the
ml
thing,
because
then
it
has
really
good
tie-ins
with
our
team
right,
yeah
I.
B
C
Thought
it
was
I
just
saw
her
integration
stuff
because
she
had
a
question
in
slack
and
I
thought
that
was
smart
too
I
was
like.
Oh
hang
on
it's
on
it,
she's
just
making
sure
that
we're
we're
like
touching
all
that
it's
good.
It's
good,
though,
because
I
think
like
we
want
to
figure
out
how
to
cross-pollinate
yeah
that
stuff.
So.
A
A
You
know
Emily
came
from
a
complete
different
area,
different
perspective,
also
yeah
yeah,
it's
difficult
to
know.
No
one
knows
everything,
but
it's
also
difficult
to
gain
that
context
without
actually
working
on
the
further
barrier.
You
know
yeah,
awesome,
right,
I,
think
I.
Think
that's
that
you
can.
Let
will
know
that
we
finish
without
him.
I
finished
this
meeting
yeah
and
then
I'll
see
you
I'll
see
you
next
time.
Good,
bye,
bye,.