►
From YouTube: ci/cd ux meeting APAC 2022-06-15
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
Hi
everyone
and
welcome
to
the
cicd
ux
sync
for
june
14th
or
15th,
depending
on
where
you
are
in
the
world
to
start
with
I'll,
go
through
the
general
slash
manager,
announcements
hayana,
put
here
to
review
this
the
okr's
progress
and
asks
if
anything
is
blocked
or
at
risk,
and
no
one
has
written
anything.
So
that's
good,
there's
a
reminder
that
there's
a
family
and
friends
day
on
june
24th
and
also
a
reminder
that
we're
going
to
be
doing
mid-year,
check-ins
and
hayan
has
created
a
tracking
issue.
A
So
this
is
team
member-led
check-ins,
to
assess
how
things
are
going
from
both
the
team,
member
and
manager's
point
of
view
to
share
feedback
and
help
improve
performance
and
development
plans,
so
make
sure
to
dedicate
an
upcoming
one-on-one
with
hayana
and
do
this
before
july.
22Nd
and
another
announcement
is
welcome
to
emily,
who
is
going
to
be
the
product
designer
on
the
release
team,
so
yeah
welcome
emily.
We're
really
happy
that
you're
here
and
I
just
added
a
a
small
note.
A
I
will
be
in
europe
for
two
months,
starting
next
week,
I'll
be
taking
a
couple
of
days
off
to
deal
with
the
jet
lag,
some
of
those
fall
on
public
holidays
and
family
and
friends
days.
But
I
might
ask
the
channel
to
cover
for
me,
but
I'm
not
expecting
anything.
Major
cool
I'll
just
quickly
go
over
gina's
items,
so
gina
says
that
the
artifacts
page
research
is
complete
and
that
they're
going
to
move
forward
with
the
page
but
have
gotten
a
lot
of
great
feedback
that
will
be
incorporated
into
the
mvc.
A
B
Yeah
I
just
wanted
to
ask
gina
the
question
of.
There
was
some
difference
that
jackie
was
talking
about
between
self-managed
and
sas
users,
and
I'm
just
very
curious.
So
if
she
could
respond
there,
that'd
be
awesome.
A
Cool
next
from
gina
is
the
new
runner
listview
research,
which
is
in
progress,
so
she's
done
unmoderated
research
and
it
was
purely
on
quantitative
data
on
the
usability
of
the
new
view
versus
the
old
view
and
she's
holding
sessions
with
customers
to
get
qualitative
feedback
in
a
couple
of
weeks
as
well
and
last
thing
from
gina
is
drums
update
if
you're
working
with
upgrades
at
all
upgrading
gitlab
runner,
for
example,
we
now
have
an
icon
to
represent
them,
so
that's
cool,
sweet,
I'll
move
on
to
my
stuff.
A
So
I
recently
completed
the
analysis
for
solution
validation
for
the
container
registry
cleanup
policies.
This
feature
allows
you
to
set
policies
to
automatically
remove
items
from
the
registry
to
save
storage
space,
and
this
is
very
similar
to
previous
solution.
Validation,
I'd
done
for
the
package
registry,
so
the
findings
were
not
super
surprising,
but
one
thing
that
I
didn't
anticipate
is
that
users
want
to
make
a
template
of
their
policies
and
apply
them
to
other
projects
erica.
You
had
a
comment.
B
Yeah,
I
think
that's
so
awesome
and
I
want
us
to
be
able
to
elevate
that
into
like
a
report
brief
way.
That's
just
what
I
would
have
done
in
a
previous
role
would
be
to
make
a
really
quick
summary.
You
have
that
actionable
insight,
and
maybe
we
should
just
think
through,
like
how
we
bring
together
all
the
work
around
the
library
like
we
could
link
it
to
that
foundational
research
issue
I
had
or
whatever
you
yeah,
but
we
should
elevate.
A
It
yeah
yeah
hi
nadia,
we've
already.
A
Going
through
the
agenda
just
so
you
know
sure
when
you
say
erica
when
you
say
pull
that
out
into
a
separate
report
brief.
What
what
exactly?
Does
that
mean.
B
It
would
be
like,
instead
of
the
lead
instead
of
you,
leading
with,
like
we
did
this
study
on,
that
it
would
be
like
here's,
the
highlight
of
a
learning
related
to
templates.
That
might
be
helpful
for
us
to
keep
in
mind,
as
we
think
about
a
shared
resource
library.
B
Because
I
think
we
want
to
get
engineers
engaging
with
it
more
and
maybe
we
could
you
could.
You
could
take
the
lead
in
thinking
through,
like
the
things
that
we
would
want,
like,
as
each
of
us
discovered
that
the
things
that
we
would
want
to
report
out,
but
I
looked
at
it
briefly
and
it
was
like
I
noticed
you
asked
about,
like
which
level
like
project
team
or
group,
if
they
had
feedback
like
that
or
like
just
sort
of
this
general
idea,
that
they
love
infrastructure
as.
A
Yeah,
I'm
wondering
how,
because
this
kind
of
this
kind
of
fits
in
with
the
resource
library
stuff,
as
you
were
mentioning
before,
and
I'm
just
wondering
like
yeah,
how
do
I
socialize
that?
What's
the
best
way.
B
A
We
don't
have
to,
we
don't
have
to
solve
it
on
this
call,
but
that
is
maybe
an
action
item
so
I'll
mark
that
after
this
and
my
next
item
is
in
52,
we're
going
to
be
implementing
a
feature
that
we're
gonna
release
with
a
small
subset
of
users
and
monitor
with
snowplow
tracking
and
the
reason
is,
we've
done
two
rounds
of
validation,
but
we're
still
not
certain
if
this
is
disruptive
to
people's
workflows.
So
we're
taking
a
pretty
cautious
approach.
A
A
My
next
point
I've
been
doing
the
touchpoint
interviews
for
a
package
and
I
consistently
I'm
hearing
from
customers
that
the
integration
with
package
and
release
could
be
better.
So
I
had
a
very
I
had
a
one
hour
call
yesterday
and
I
captured
the
feedback
on
an
internal
note.
So
I'm
not
sure
if
you
all
are
going
to
be
able
to
see
it,
but
basically
I
would
really
like
to
work
with
emily
when
she's,
maybe
a
little
bit
more
onboarded
to
improve
this
nadia.
A
Yeah
totally,
basically,
it's
quite
a
lot
of
manual
process
and
a
lot
of
boilerplate
code
that
people
need
in
the
pipeline
and
what
people
are
actually
expecting
is
that
the
they
couldn't
create
a
package
in
the
pipeline
and
just
mark
the
package
as
a
release,
and
they
don't
need
to
do
extra
steps.
A
And,
furthermore,
people
want
to
be
able
to
see
that
a
release
like
the
actual
artifact
of
the
release
comes
from
the
package
registry
and
a
link
to
that,
because
the
package
registry
has
a
lot
more
in-depth
information
for
auditing
and
stuff,
and
at
the
moment,
when
you're
going
on
the
release
page,
you
download
the
artifact
and
that's
it.
You
don't
even
know
necessarily
that
it
came
from
the
package
registry
and
there's
this
whole
wealth
of
information.
So
it
seems
like
ignoring
the
technical
side.
A
The
opportunity
is
quite
clear,
but
I'm
sure
there's
probably
like
some
some
technical
reasons
why
it
is
the
way
it
is
make
sense.
Thank
you.
A
My
next
item,
I'm
starting
to
plan
for
15-2
and
I
think,
there's
some
opportunities
to
start
getting
some
of
these
research
projects
that
we
had
in
the
validation
backlog.
Moving
again,
specifically,
we
want
to
improve
the
package
detail
page
because
there's
a
lot
more
features.
We
want
to
add
to
it,
but
we
kind
of
want
to
do
like
some
problem
validation
to
understand
what
workflows
people
are
like.
Why
are
the
reasons
that
they're
coming
there?
What
are
they
trying
to
achieve?
What's
missing?
A
What's
painful,
just
kind
of
some
foundational
problem,
validation,
research
before
we
start
thinking
about
features-
and
my
last
point
is
continuing
on
my
journey
with
data-
I'm
gonna
try
to
implement
the
missing
front-end
events
tracking,
so
that's
click
tracking
for
package,
we're
only
tracking,
like
twenty
percent
of
the
things
that
people
click
on
at
the
moment.
So
we
have
all
these
like
beautiful,
sci-fence
dashboards,
but
they're,
not
painting
a
really
good
picture
because
we're
missing
a
lot
of
the
tracking.
So
I'm
gonna
attempt
that.
A
C
I
see
erica
is
writing
something,
or
do
you
want
to
keep
a
treat
only
okay,
all
right
so
in
15.3,
and
this
milestone
as
well
like
the
remaining
week
I'll
be
focusing
on
the
pipeline
components.
Mvc
solution,
validation,
currently
I'm
finishing
up
the
interviews
with
internal
users
and
I've
been
talking
to
a
lot
of
the
members
of
our
productivity
engineering
team
and
so
far
the
feedback
that
we've
been
getting
has
been
very
positive
on
our
proposal.
C
We
are
getting
lots
of
ideas
for
improving
the
further
iteration
of
the
future,
but
it
seems
like
our
direction.
C
A
lot
of
our
a
lot
of
the
choices
that
we've
made
so
far
are
on
track
and
seem
like
the
desired
behavior,
and
also
there's
a
lot
of
interest
from
the
engineering
productivity
team
to
dog
food.
Our
product.
We
already
have
an
issue
where
we
will
be
tracking
that,
so
we
expect
that
we'll
start
implementation
in
15.4.
If
everything
goes
well
depends
on
how
quickly
we
can
go
through
the
planning
breakdown.
C
Of
course
there
can
be
unforeseen
challenges,
but,
let's
hope
and
then
yeah
and
then
we'll
be
able
to
dog
food
it
with
our
productivity
engineering
team.
So
they
want
to
kind
of
move
to
our
new
system
for
creating
pipeline
components
and
use
our
feature
to
standardize
their
components
or
ci
templates
so
yeah.
All
of
this
is
very
exciting,
because
we
can
really
see
how
we
will
be
getting
this
into
the
actual
product
and
dog,
putting
it
with
our
own
team.
B
C
I
really
like
the
idea
of
a
sled
bot.
It
hasn't
even
occurred
to
me
to
do
something
like
that.
My
initial
idea
was
to
just
have
an
issue,
but
I
see
how
having
something
flat
like
that
would
be
much
easier
for
the
engineers
to
kind
of
just
type
their
feedback
in
so
maybe
there's
a
way
to
somehow
connect.
C
C
Okay
and
another
thing
I
wanted
to
share
is
around
the
recently
added
guidelines
for
in-product
preference
information
using
drawers,
so
we've
added
some
really
basic
guidelines
outlining
what
kind
of
content
content
you
should
put
into
the
drawers,
what
kind
of
content
you
shouldn't
put
into
the
drawers
and
how
all
of
that
can
be
implemented
either
by
pulling
in
documentation
directly
to
the
drawer,
or
you
can
also
have
your
own
custom
content
that
you
write,
but
it
still
has
to
adhere
to
the
content
guidelines
for
our
documentation
and
we
want
to
actually
store
it
in
a
markdown
file
in
the
docs
repository
that
is
being
done
to
make
sure
that
we
can
actually
test
the
changes
to
help
content
using
the
documentation
pipeline
because
it
does
all
kinds
of
helpful
linking
and
whatnot.
C
So,
following
up
on
that,
I'm
revisiting
the
pipeline
editor
drawer
to
make
it
more
helpful
to
our
users.
So
there's
been
a
lot
of
hype
around
the
pipeline,
editor
drawer,
I
feel
like
like
so
many
people
who
are
interested
in
it
like.
Oh,
it's
it's
so
nice!
It's
this
help
info
and
then
we
start
tracking
it.
It's
huge
and
honestly,
it's
it's
very
low
compared
to
the
oral
pipeline,
editor
usage
and
I
think
there
can
be
like
many
different
ways
to
interpret
it
like.
C
Maybe
our
users
just
don't
struggle
when
they're
going
through
the
flow,
which
I
I
don't
think
is
the
case
or
also
maybe
it's
not
very
discoverable.
It's
not
tied
to.
C
Maybe
it's
not
tied
to
a
specific
task
that
they're
working
on
so
there's
yeah,
we're
kind
of
like
not
helping
them
with
something
specific.
It's
very
generic
and
if
you
look
at
the
guidelines
that
we
put
in
place,
we're
saying
that
we
shouldn't
create
generic
health
drawers
like
here's
help
on
all
kinds
of
topics
that
you
might
think
of.
Instead,
it
should
be
tied
to
helping
the
user
perform
a
very
specific
task,
so
yeah.
C
C
And
so
far
it
looks
like
the
leading
link,
rci
example,
and
also
the
yemen
reference
which,
which
is
something
that
we
would
expect
sorry,
I
have
to
repair.
C
It's
my
first
time
owning
a
cad.
I
can't
discipline
her
she's,
just
climbing
along
me
yeah.
So
I
want
to
take
all
of
this
data
and
I
don't
know-
maybe
we
could
do
some
additional
solution-
validation
as
well
to
gather
some
qualitative
data
around
this,
but
my
next
step,
I
think,
would
be
to
do
some
experimentation
there
with
the
content
and
try
different
ways
of
surfacing
different
information
yeah.
C
So
basically
we
learned
that
it
seems
like
it's,
not
it's,
probably
not
helping
our
users
as
much
as
we
thought
it
were.
So
I
will
be
looking
into
it
and
see
what
we
do
next.
Hopefully
we
can
improve
it
from
there.
A
Cool,
do
we
want
to
move
on
to
the
research
section.
B
Yeah,
so
just
a
general
update,
there
have
been
no
shows
people
are
not
showing
to
sessions
and
it's
actually
just
a
larger
trend.
We
think
related
to
the
changing
of
seasons.
It's
not
you
or
or
our
recruitment.
It's
just
a
general
trend
across
all
studies,
so
I
thought
that
would
be
helpful
and
then
I
have
just
a
couple
of
check-ins.
D
B
Okay
and
then,
and
then,
if
you
guys,
could
go
into
and
link
the
the
research
or
the
studies
that
you've
been
doing
yeah
the
resource
studies
you've
been
doing
that.
I
should
include
in
the
registry
and
synthesis
I'm
still
really
wanting
to
do
that
to
kind
of
go
through.
B
So
it's
just
if
you
have
other
studies
that
you've
completed
or
when
you
do
just
a
reminder,
because
I
was
kind
of
thinking
about
it
and
then,
if
you
can
go
back
through
and
just
take
out
the
studies
or
or
you
can
either
delete
them
from
those
tables
or
just
say
finished.
B
That
would
be
good.
Not
not.
I
won't
beg
you
but
that'd
be
awesome,
but
I'm
it's
not
that
great
I
mean
you
know.
I
can
try
to
figure
it
out
and
then
just
also
that
our
team
looked
just
really
great,
so
good
job,
everyone
with
the
apps
product
directions.
Survey.
B
If
you
look
in
that
async
issue,
you
can
see
that
we're
getting
like
all
this
cross-functional
feedback
and
people
are
just
saying
like
great
job.
Your
your
team
did
a
great
job
on
this.
So
okay.