►
From YouTube: CI/CD UX meeting 05/18/22 - APAC
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
welcome.
Everyone
today
is
the
18th
of
may
and
we
are
meeting
for
a
ci
cd,
qx
meeting
the
a
park
edition
getting
started
with
the
agenda.
We
have
a
kind
of
a
full
agenda
today
and
a
lot
of
items
under
general
and
manager,
announcements
I'll
start
with
that.
The
first
one
is
to
review
the
okr's
progress,
and
this
like
mark
the
progress
in
the
issue
and
also
make
a
note
if
anything
is
blocked
or
at
risk,
and
everyone
should
get
in
touch
with
their.
A
B
Yeah,
I
was
just
wondering
if
this
goes
for
the
country
where
you're
physically
currently
present
or
your
official
country
of
residence.
I
would
assume
it's
your
official
country
a
president,
but
it's
just
not
very
clear,
so
yeah.
I
just
wanted
to
clarify,
because
for
someone
like
like
me,
that
makes
a
big
difference.
Usually
I
take
polish
holidays
off,
but
I'm
also
happy
to
take
indonesian
holidays
off.
If
that's
so
loud.
A
A
Moving
on
to
the
other
agenda
items,
so
the
first
one
is
here
by
gina
gina
is
talking
about
the
validation
study
that
you
would
be
working
on
and
also
the
road
map
that
should
be
working
on
with
her
new
pm
joslin.
So
there's
some
updates
about
that.
Please
take
a
look
at
that
and
drop
any
comments.
If
you
have
thoughts
around
it
and
the
next
one
is
katie
katie,
do
you.
C
So
this
week,
I'm
mostly
focused
on
doing
some
solution:
validation
for
the
nbc
of
the
container
registry,
cleanup
policies,
just
a
bit
of
background
information.
This
feature
actually
already
exists
in
production,
but
there's
been
a
lot
of
customer
feedback
for
the
past
two
years
about
certain
features
that
are
missing
from
it:
there's
quite
a
lot
of
technical
constraints
with
the
container
registry
and
any
implementation.
C
So
we
have
a
very
kind
of
minimal
like
mvc
and
part
of
the
questions
that
we're
trying
to
answer
with
the
solution.
Validation
is:
is
this
too
minimal
like?
Is
it
still
worthwhile
to
make
these
changes?
So
I
have
just
done
my
fifth
session
before
this,
so
I've
got
one
more
and
then
I'll
be
doing
analysis
this
week
and
I'll.
C
Let
everyone
know
how
it
goes,
and
my
second
item
that
I'm
focusing
on
I'm
trying
to
upskill
myself
in
kind
of
data
related
just
like
like
making
design
decisions
based
off
of
data.
I
also
saw
that
there's
recently
been
a
handbook
page
added
about
this,
and
I've
been
working
with
matthew
peterson
who
works
on
the
growth
team.
To
answer
some
of
these
questions
and
he's
setting
some
stuff
up
for
me
and
my
hope
is
eventually
I
can
use
what
he
set
up
to
kind
of
write.
C
A
C
The
I
created
the
sheet
almost
like
as
soon
as
I
joined
git
lab
just
having.
I
had
some
questions
about
design
decisions
I
wanted
to
make
and
data
that
would
maybe
support
those
questions
and
the
problem
was
our
engineers
in
the
package
team
are
so
busy
that
they
don't
have
time
to
support
with
this
at
the
moment,
and
so
I
started
talking
to
the
growth
team.
C
Yeah,
I
would
love
to
maybe
eventually
make
this
a
ux
showcase.
What
I
need
to
understand
is
there's
basically
tables
of
data
and
the
data
has
names
and
then
there's
sql
and
you
put
the
two
things
together,
so
maybe
eventually
matthew
and
I
can
make
write
a
tutorial
or
or
guidelines
of
you
know.
If
you
wanted
to
approach
this
yourself,
how
would
you
do
it,
but
we're
still
very
early
days
so
yeah
we'll
see
if
that's
possible.
B
Yeah,
so
I
wanted
to
share
some
solution.
Validation
results
around
variables.
If
you
want
to
check
out
the
research
issue,
it's
linked
right
there
at
the
beginning,
so
the
core
insights
were
that
the
current
processing
mechanism
for
variables
was
not
clear
to
our
users
at
all.
So
currently,
if
you
use
a
dollar
sign
in
your
variable,
it's
it's
interpreted
as
the
start
of
a
new
variable,
which
is
essentially
something
you
would
do
only
if
you
want
to
create
a
variable
inside
a
variable.
B
Otherwise,
usually
you,
when
you
create
a
password,
for
example,
it
might
contain
a
dollar
sign,
especially
if
it's
machine
generated
for
security
purposes
and
it's
a
surprise
to
the
users
that
by
default
it
will
be
expanded.
Usually
they
kind
of
learn
it
the
wrong
way.
You
know
the
pipeline
just
doesn't
work.
The
credential
doesn't
work
because
it's
misinterpreted,
then
passwords
were
expected
to
be
masked
for
security
purposes
and
evaluated
as
a
raw
string.
B
We
have
this
form
of
several
different
options
where
you
can
protect,
variable
mask
variable,
and
now
we
want
to
add
another
option
to
process
it
to
the
raw
string,
it's
starting
to
become
overwhelming.
So
in
the
future,
we
want
to
look
into
adding
some
predefined
variable
configurations
based
on
the
variable
type,
for
example,
instead
of
having
to
look
at
the
form
and
evaluate
all
of
the
different
options
that
are
available
to
you
and
how
to
put
them
together
to
get
desired
result,
we
might
consider
suggesting
that
hey.
A
Yeah,
so
this
making
like
masking
the
variables
by
default
for
certain
requirements,
it
came
up
in
one
of
the
discussions
that
we
were
having.
I
think
it's
a
part
of
ops,
think
like
long
back
about
six,
seven
months
back
when
we
talked,
we
were
talking
about
secrets
that
we
provide
many
options,
but
our
default
like
how
we
treat
these
variables
and
secrets
by
default.
It's
not
like,
even
though
we
have
a
lot
of
capability,
we're
not
using
them
right.
A
B
B
B
B
B
B
If
the
documentation
content
for
some
reason
doesn't
work,
and
then
you
will
still
have
to
follow
the
documentation
guidelines
around
how
you
structure
that
content
and
technical
writing
will
have
to
be
involved
for
sure
they're
helping
out
with
the
copy,
but
yeah
the
guidelines
are
still
a
work
in
progress.
It's
the
lmr
is
still
being
refined,
there's
a
bunch
of
threads
there
and
questions.
B
So
if
you
have
the
time
feel
free
to
jump
in,
especially
if
you
think
there
might
be
a
need
for
a
help
drawer
in
your
stage
group,
because
we
need
to
account
for
all
kinds
of
different
use
cases
and
we
had
some
interest
from
several
different
stage
groups.
But
I
think
the
requirements
might
really
vary
depending
on
what
kind
of
task
you
want
to
support
and
what
kind
of
content
you
want
to
show.
So
we
want
to
make
sure
we
account
for
those.
C
A
Take
it
away
all
right,
so
I
just
have
like
very
small
updates.
I
have
I'm
still
busy.
In
fact,
I
just
did
the
last
interview,
the
ninth
interview
for
the
foundational
research
for
pipeline
execution,
and
it's
going
very
well
and
I
would
be
sharing
the
results
on
friday,
mostly
for
this,
and
I
have
added
the
dovetail
link
which
has
about
six
interviews
uploaded
until
now,
so
this
I
would
update
this
further
and
share
with
the
team
and
with
the
findings.
A
Of
course,
the
next
thing
is
james
and
I
have
worked
on
the
priority
for
design
issues
for
this
quarter.
So
if
you
just
go
to
this
epic,
you
would
be
able
to
see
a
reprioritized
list.
So
that's
what
that's
how
I
would
be
going
about
working
on
these
design
issues
in
the
same
sequence,
as
you
see
in
front
of
you
like
the
one
on
the
top,
is,
is
of
the
highest
importance
to
us,
and
I
mean
nadia.
If
you
see
the
top
issue,
it's
something
that
we
have
discussed
about.
A
A
And
yeah,
that's
it
nothing
more
from
my
side,
let's
see
what's
there
in
the
ux
research
thread,
so
we
have
a
new
page,
our
ux.
Our
training
resources
has
a
new
page
on
using
quantitative
data
to
find
insights.
You
can
go
and
check
there
and
then
will
and
erica
have
posted
a
link
to
their
privatization
issues
and
that's
it
anything
else
before
we
wrap
up.