►
From YouTube: CI/CD UX team meeting - 12 Jan 2022
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,
hi,
everyone
today
is
the
12th
of
jan
and
we
are
meeting
for
the
cicd
ux
meeting
today.
It's
just
me
and
nadya
in
the
meeting
hello
from
us,
okay,
so
starting
with
the
topic,
so
for
the
general
topic,
we
have
something
from
hannah,
which
is
the
review
for
the
okr
progress.
A
So
if
you
have
any
updates
or
any
sort
of
item
to
talk
about
there,
you
can
go
and
add
to
the
progress
of
the
occurs
and
then
next
up
is
async.
Video
updates
and
gina
has
provided
an
async
update
about
the
work
that
she
is
doing
for
testing
and
runner
in
the
form
of
a
video
thanks
tina
for
that.
A
Then
we
will
okay
up.
Next
is
ux
research
update
the
first
one
is
from
release,
which
is
by
will-
and
he's
mentioned
here,
about
new
research
planning
issue
that
he
has
created
for
january
to
april,
where
he's
soliciting
ideas
for
the
research
needs
and
the
teams
which
are
contributing
to
that
are
released,
configure
and
monitor
teams
and
he's
working
with
kevin
to
prioritize
those
requests.
B
No
no
comments,
yet
I
have
to
go
through
the
planning
issue,
I'm
still
catching
up
from
my
time
off.
So
I
have
to
get
to
that.
But
I'll
make
sure
to
comment
this
week.
A
Yeah,
understandable,
all
right
and
for
erica
erica
had
given
a
good
kind
of
summary
of
what
she
was
working
on
in
our
previous
meeting.
But
this
is
something
that
I
just
copied
and
pasted
from
slack,
because
she
had
posted
an
update
about
a
research
work
that
she
was
doing
where,
like
the
summary,
is
here
in
the
comment
and
the
deck
is
also
attached,
and
since
this
is
already
something
that
was
shared
before
so,
I
would
not
like
go
through
the
whole
thing,
but
it's
just
an
fyi
that
this
is
like.
A
A
All
right
up
next
is
an
item
by
daniel,
so
daniel
is
working
on
a
couple
of
big
things.
The
first
one
is
big
restructuring
for
the
release,
jobs
to
be
done,
for
which
he
has
created
a
video,
and
he
has
also
requested
katie
to
drop
a
comment
around
this
or
some
feedback
around
this,
because
they
have
some
sort
of
overlapping
in
their
efforts.
B
A
Sure
then,
we
can
just
quickly
just
go
through
and
one
thing
that
one
suggestion
that
I've
left
for
daniel
is
so
when
I
watched
the
video
for
jobs
to
be
done.
I
was
trying
to
understand
like
what
triggered
this
restructuring
like.
Was
it
some
learning
from
any
recent
study
or
was
it
through
some
feedback
on
an
issue?
A
I
was
not
able
to
make
connections
very
well,
and
I
would
love
some
information
around
that
and
the
next
item
by
daniel
is
like
another
big
work
that
he's
doing,
which
is
for
group
environments
page,
and
I
also
haven't,
checked
out
the
video
for
this.
Yet
I'm
so
sorry,
all
right
and
the
last
one
is.
A
Then
the
next
item
is
by
katie.
She
has
been
doing
some
research
work
and
the
first
point
here
is
an
update
about
a
solution.
Validation
exercise
that
she
was
doing
around
package
cleanup
and
apart
from
that,
she's
also
mentioned
that
in
the
process
and
in
the
learning
she
discovered
some
work.
That
could
be
done
for
the
settings,
which
I
absolutely
agree,
thanks,
gina
and
keri
for
highlighting
that
on
slack.
A
B
B
It
took
me
a
few
days
actually
to
recruit
those
participants,
because
the
screener
was
much
more
strict,
I
would
say,
but
it
allowed
me
to
get
to
find
those
qualified
participants,
so
just
wanted
to
say
that
if
you've
struggled
with
this
in
the
past,
reach
out
to
katie
to
have
her
look
at
your
screeners,
because
you
might
be
able
to
actually
get
really
good
participants
on
user
testing.
It
just
requires
a
bit
of
wizardry
and
trickery
to
actually
filter
out
those
people
that
you
don't
need,
and
I
100.
A
Agree
with
that,
so
eric
of
course
helped
me
as
well
in
my
previous
solution,
validation
that
I
did
with
user
testing
and,
like
you
said
it
did,
take
a
lot
of
time.
I
was
very
worried
because
at
my
previous
studies,
things
used
to
happen
like
so
fast,
but
it
took
time
and
I
was
so
happy
to
see
the
results
because
they
were
really
good
participants.
They
were
very
relevant
people
who
actually
did
the
test.
So
thank
you
so
much
harika
for
that.
If
you're
listening
to
this.
A
B
Yeah,
so
I've
just
finished
solution,
validation
for
the
pipeline
simulation
mvc.
Many
of
you
have
provided
your
feedback
on
the
previous
design
iteration,
so
the
solution
validation
went
really
well
by
the
way.
This
is
the
solution.
Validation
study
that
erica
helped
me
with.
So,
if
you
want
to
have
a
look
at
the
screener
that
I
used,
you
can
click
through
to
see
the
insight
summary
issue,
which
is
the
research
issue
and
there's
a
user
testing
link
there
at
the
bottom.
B
B
That
will
help
us
iterate
on
the
mvc
design
proposal
and
also
inform
the
further
iterations.
We
think
you
had
some
comments
here.
It's
similar
the.
A
To
what
I
had
said
for
katie's
update,
which
is
like
erica
added
jobs,
to
be
done
first
in
the
in
the
screening
like
filtering,
on
the
basis
of
jobs
to
be
done,
which
is
very
new
to
me,
and
I
think
it
should
have
worked
and
also
I
took
a
look
at
the
insights
that
you
have
posted
and
they
look
very
interesting.
But
I
definitely
need
to
go
and
look
at
a
couple
of
videos,
at
least
because
from
your
insights,
it's
very
clear
that
the
participants
understood
like
they
had
their
expectations
aligned.
B
So
I
I
can
recommend
if
you
wanna,
have
a
look
at
the
demo.
So
if
you
go
to
the
design
issue,
I
think
I
linked
it
here
in
the
agenda
yeah,
it's
this
one.
Oh,
so
I
so
I
linked
the
wrong
issue.
It's
not
where
you
find
the
inside.
It's
where
you
find
the
demo,
I'm
gonna.
A
B
The
insights
issue,
but
there's
a
three-minute
prototype
walkthrough.
B
You
can
have
a
look
at
that.
That's
very
helpful.
Thank
you
so
much
for
this
sure.
Okay,
so
that's
that
for
the
pipeline
simulation.
So
now
I'm
iterating
on
the
designs
and
in
14.8
we
will
be
starting
the
discussions
around
how
we're
going
to
break
this
down
for
implementation
and
we'll
be
taking
a
full
milestone
to
kind
of
wrap
up
the
design,
discussions
and
move
it
into
implementation,
because
in
the
past
we've
been
kind
of
struggling
with
brushing
things
too
quickly
into
implementation.
B
B
So
I
don't
know
if
you've
seen
my
update
on
all
of
the
work
that
is
happening
around
object,
object,
modeling
and
the
the
things
that
we're
working
on
with
pedro
and
tory
on
creating
contribution
guidelines
for
adding
objects
to
pajamas.
B
So
we
currently
already
have
an
object
overview
page
that
you
can
check
out
to
learn
more
about
object,
modeling.
Why
we're
doing
it?
What
are
the
benefits
of
creating
a
conceptual
object
model
and
right
now
we
only
have
the
merge
request
documented
in
pajamas,
but
there's
some
other
objects
that
are
being
documented
kind
of
that
are
work
in
progress
and
you
can
find
those
in
a
figma
file
called
conceptual
model.
B
If
you
look
for
it
on
figma,
you'll
see
it
and
there's
kind
of
lots
of
drafts
there
already
and
if
you're
interested
in
contributing
to
to
this
whole
effort.
If
you
want
to
document
an
object
check
out
the
epic
did,
I
did
I
link
the
right
thing.
I
think
I
did.
B
Link
the
epic,
I
think
I
didn't
link
the
epic,
but
anyway,
I
will
add-
I
will
edit
here
later,
but
for
this
particular
part
of
the
process,
I'm
working
on
documenting
a
job
as
an
object,
and
you
can
comment
on
the
work
in
progress
diagram
that
I
already
have
by
going
to
this
issue
thread
or
you
can
also
jump
into
the
figma
file.
B
B
If
you
look
at
the
issue,
comment
that
I
linked,
you
will
see
some
specific
questions,
kind
of
the
specific
feedback
that
I'm
looking
for
and
there's
also
a
legend
there
that
I
added
that
makes
it
easier
to
understand
the
diagram
and,
if
it's
all
entirely
new
to
you,
then
check
out
the
object
overview
page
and
there's
a
link
there
to
a
really
good
article
about
object.
Modeling
that
explains
all
of
the
details
behind
this
process.
So
it
will
give
you
the
context
necessary
to
understand
what
we're
doing
yeah.
B
So,
if
you
have
the
time,
have
a
look
and
provide
your
feedback.
That
would
be
greatly
appreciated,
and
one
last
thing
that
I
wanted
to
share
is
some
of
the
amazing
work
that
our
incubation
engineers
are
doing.
So
we
have
several
incubation
group
engineers
that
are
like
single
teams.
Basically,
so
one
engineer
is
working
on
the
product
strategy,
the
ux
research,
the
design,
the
implementation,
everything
for
solving
a
specific
problem.
B
A
lot
of
the
work
that
they're
doing
is
very
experimental,
they're
innovating
a
lot,
and
it's
really
really
inspiring
to
see
and
also
very
exciting
for
the
pipeline
authoring
team,
because
they're
working
on
some
things
that
are
really
aligned
with
the
things
that
we're
working
on
so
first
off,
we
have
eduardo
who
is
currently
investigating
the
needs
of
data
scientists
when
it
comes
to
pipelines-
and
I
knew
nothing
about
it
until
the
point
when
I
started
seeing
his
weekly
updates
so
every
week
he
records
some
videos
about
what
he
learned
and
what
what
he's
doing
next,
so
apparently
data
scientists
in
machine
learning
use
pipelines
to
do
their
machine
learning
things.
B
I'm
not
I'm
not
even
sure
exactly
what
they're
doing.
But
you
know
they
use
this
kind
of
automation
to
do
a
bunch
of
like
processing-
and
I
don't
know,
machine
learning,
wizardry
so
I'll,
be
meeting
with
him
tomorrow
to
learn
more
about
this
and
I'll
record
everything
to
share
with
you.
B
B
So
we'll
see,
if
you
have
any
questions
around
this
whole
thing,
feel
free
to
send
them
to
me.
So
I
can
ask
them
on
my
call
with
the
daughter
tomorrow
and
another
incubation
group
engineer:
janice
he's
working
on
a
yaml
builder,
so
he
actually
already
created
a
pretty
much
fully
functional
yaml
builder.
That
allows
you
to
create
your
pipeline
using
a
ui,
so
you
can
check
out
a
demo
of
the
yaml
builder.
Here
I
linked
the
video.
B
It's
pretty
short
and
really
impressive
and
there's
already
an
issue
where
the
pipeline
authoring
team
is
discussing
how
we're
going
to
make
it
part
of
the
pipeline
authoring
experience,
so
there's
multiple
different
ways
that
we
could
integrate
it.
So
if
you're
curious,
have
a
look
at
the
discussion
feel
free
to
drop
your
comments.
If
you
have
any
thoughts
on
that,
this
is
very
interesting.
A
Do
you
know
nadia
if
this
is
some
sort
of
I
mean
workflow?
Why
is
this
some
sort
of
reverse
engineering,
like
you
start
with
you
start
with
stating
that
what
is
your
intention
with
the
project
and
based
on
that
you
create
the
yaml
or
generate
the
yaml
for
that.
B
Sorry
one
second,
can
you
repeat
it?
It's
just
someone
like
a
delivery.
Guy
came.
I
had
to
okay
all
right,
so
I
was
saying.
A
That
looking
at
this
second
one,
the
video
that
you
have
added,
I
mean
I
quickly
just
clicked
through
different
screenshots
and
it
seems
like
this
flow
is
about
like
as
a
user,
I'm
going
to
state
that
this
is
what
I
this
is
what
my
intention
is
with
my
project
and
based
on
that
something
gets
automatically
generated
in
the
on
the
yaml
side
that
you
can
use
that
I
can
use
as
a
pipeline.
B
So,
as
far
as
I
understand,
it's
not
generated
based
on
the
project
yet,
but
it's
generated
based
on
the
template,
so
we
currently
have
so
just
a
bit
of
background.
Janice
started
creating
this
yaml
builder,
specifically
for
github
pages
first,
so
we
have
a
yaml
template
for
deploying
to
github
pages
and
he
was
focusing
specifically
on
that
use
case,
which
was
very
exciting
to
me,
because
I
always
felt
like
the
github
page
is
such
a
great
feature,
but
it's
completely
like
the
ux
is
non-existent,
so
he
created
a
ui
for
that.
B
But
while
he
was
working
on
that,
he
realized
that
it's
actually
very
easy
to
make
the
same
experience
work
for
any
yaml
template,
so
he
kind
of
made
it
template
agnostic.
So
currently
what
happens?
Is
you
can?
So
we
have
these
templates
based
on
languages
for
the
most
part
like
a
node.js
template.
We
have
also
specific
templates
to
do
like
this
specific
job
like
deployed
to
gitlab
pages.
B
If
you
want
to
use
any
of
these
templates
with
a
wizard,
you
just
need
to
create
a
separate
yaml
template
that
defines
a
wizard
for
for
that
template
so
like.
If
you
can
imagine
two
yama
templates
together,
let's
say
a
page.yaml
template
and
a
wizard
pages
yaml
template
to
get
together.
They
give
you
this
visual
ui
experience,
so
it
can
be
used
for
any
of
yaml
templates
and
I
guess
the
trigger
would
be
for
you
to
select
a
template
or
technology.
B
We
can
frame
it
in
many
different
ways,
so
it's
not
automatic,
but
I
guess
we
can
frame
it
this
way
a
little
bit,
because
we
can
ask
you
what
do
you
want
to
do?
You
answer
deploy
to
pages,
and
then
we
provide
you
with
a
wizard
for
deploying
to
pages.
So
it's
not
really
smart,
but
I
guess
kind
of
creates
that
impression
for
the
end
user.
B
B
This
is
kind
of
the
idea,
and
this
is
the
direction
I
think
we'll
kind
of
move
towards,
but
the
pipeline
authoring
team
is
now
at
a
stage
where
we're
we're
trying
to
better
understand
what
do
we
want
to
prioritize?
Do
we
want
to
integrate
this
wizard
into
pipeline
authoring
on
boarding
like
when
you're
just
starting
with
your
pipeline,
or
do
we
want
to
use
it,
for
example,
to
add
extensions
to
your
pipeline?
B
A
Nice,
that
sounds
really
good.
I
hope
this
I
mean
if
this
whole
experience
is
integrated
with
the
piping
authoring
experience.
That
would
be
really
something.
A
Very
excited
about
it,
nice
and
for
an
update
on
your
previous
topic.
So
I
have
dropped
a
comment
on
the
I
mean
I,
I
dropped
comments
in
the
morning
on
the
fedma
file
for
the
object
model,
but
apart
from
that,
I've
also
posted
an
update
on
the
issue,
because
it
occurred
to
me
that
I
totally
forgot
about
the
sources
for
pipelines.
A
A
Pipeline
but
I
don't
think
sources
apply
to
jobs
very
directly,
just
the
pipelines,
so
it
would
only
be
for
one
side.
I
guess
for
for
the
pipeline.
B
A
Okay,
anything
else,
or
can
I
move
to
my
points.
A
All
in
my
end,
thank
you
so
much
all
right,
so
one
update
from
my
side
is
about
the
auto,
merge
solution,
validation,
research
that
I
was
conducting
in
the
previous
week,
again
using
user
testing
and
with
erica's
help,
and
that
worked
really
well,
and
we
received
a
lot
of
really
good
insights
that
is
going
to
help
us
frame
our
path
forward.
A
So
what
the
intention
that
we
had
with
this
research
was
so
the
problem
was
that
the
labels
that
we're
presenting
to
our
users
to
communicate
our
mood
strategies
and
options
selected
for
that
particular
project
that
they're
using
when
they
are
going
to
merge
their
changes.
A
It's
very
lengthy
and
they
also
do
not
comply
the
label
text.
They
do
not
comply
with
the
nn
troops
for
value
for
better
link
labels,
which
is
like
they're,
not
success,
they're,
not
simple,
I'm
forgetting
the
other
two.
So
we
wanted
to
make
it
like
really
simplify
it
to
just
auto
merge
like.
Instead
of
writing
those
lengthy
statements,
such
as
start
merge,
train
when
pipeline
succeeds.
Why
not
just
give
this
option
to
set
auto
merge
and
we
want
to
see
like
how
users
react
to
this.
A
But
while
I
was
working
on
those
designs,
I
discovered
that
it's
not
that
users
only
want
like
want
to
auto
merge
at
the
stage
when
they're
merging,
but
in
fact
they
would
really
love
to
have
this
option
set
right
at
the
beginning
of
the
process,
which
is
when
they
are
creating
the
merge
request.
So
let's
say
if
it's
a
very
simple
change
and
I'm
creating
a
merge
request,
and
I
know
that
there's
hardly
going
to
be
any
complication.
A
Maybe
it's
just
a
typo
or
I'm
just
adding
an
image,
so
no
critical
pipelines
to
run
for
that.
So
why
not
just
set
auto
merge
at
that
stage
so
that
it
doesn't.
It
wouldn't
need
any
manual
interventions
again
and
again
to
get
merged.
A
A
We
sensed
that
they
were
definitely
so
much
more
confident
about
like
using
that
feature
when
it
comes
to
the
widget,
because
the
new
widget
design
that
the
code
review
team
has
worked
on
or
the
create
team.
It's
very
clear.
It's
very
succinct.
It
clearly
states
like
what's
the
progress
of
the
merging
process
and
what
are
the
checks
that
have
to
run
what
the
checks
that
have
run
already
and
where
is
it
that
you're
at
so
that
kind
of
information
and
the
illustrated
progress
report
that
users
are
getting?
A
It
really
boosts
their
confidence
to
use
an
automatic
feature
there
and
that's
really
required.
So
one
very
recurring
question:
when
participants
were
looking
at
the
new
pipe
and
new
merch
request
creation
page
and
this
label,
auto
merger
was
that
that
I
haven't
even
started
the
pipeline.
I
don't
even
know
how
it's
going
to
go.
How
can
I
like?
A
How
can
I
just
set
it
on
auto
merge,
so
they
lack
the
confidence
there
and
that
clearly
shows
that
we
have
some
work
to
do
there,
maybe
some
capabilities
that
we
would
be
able
to
predict
like
how
the
merge
process
is
going
to
go.
A
So
that
was
a
brief
summary
about
this
whole
thing,
and
another
point
that
I
have
to
share
is
like,
while
working
on
many
different
new
issues
which
are
related
to
providing
a
better
visibility
to
ci
minutes
to
our
users
and
also
like
hardening
the
ci
limit,
ci
minutes
limit
for
free
and
public
users
that
we
are
working
on.
So
we
are
envisioning
many
different
use
cases
there.
A
So
I
want
to
know
that
when
you
as
a
member
of
as
a
designer
for
the
verify
stage,
groups
or
package
or
release
when
you
hear
this,
these
words
like
cost
factors
ci
minutes
quotas-
were
the
questions
that
come
to
your
mind
and
I
would
soon
be
opening
an
issue
around
this.
But
if
you
are
able
to
think
of
any
questions,
please
let
me
know
about
that.
So
I
can
include
that
when
I
create
a
video
yeah,
I
added
a
question:
what
is
a
cost
factor?
A
Okay,
I
can
answer
this
one
quickly
and
I'll
show
you
this
for
later
cost
factor
is
the
so
let's
say
you
are
a
free
user
today
and
you
have
a
linux
based
runner
for
your
project,
so
the
cost
factor
that
will
apply
to
you
is
going
to
be.
I
guess
one
that
means
the
it's
the
rate
of
consumption
of
the
allotted
ci
minutes,
but
if
you're
using
another
mac
runner
in
your
project
as
well,
that's
going
to
exhaust
your
ci
minutes
at
a
faster
rate.
That
means
it
will
have
a
higher
cost
factor.
A
So
cost
factor
is
that
rate
of
exhaustion
of
ci
minutes?
That
we
add
to
those
runners.
A
Always
associated
with
runners,
okay,
make
sense,
and
lastly,
we
have
an
item
by
gina,
which
is
the
first
point
is
around
work
that
she's
doing
to
introduce
bulk
deletion
for
the
runner
fleet
management.
If
I'm
not
wrong,
so
she
has
linked
the
designs
here
and
the
feedback
that
she's
looking
for
is
on
how
the
bulk
selection
works
with
pagination,
as
well
as
confirmation
messages.
A
I've
dropped.
A
small
comment
which
I
can
show
once
I
read
through
all
the
items
and
next
is
darren-
has
come
up
with
this
opportunity
to
meet
with
customers,
regina
who
are
managing
fleets,
so
they're,
very
interested
in
giving
their
feedback
to
for
the
designs
and
they're
discussing
the
plan
for
starting
office
hours
with
customers
so
office
hours.
I
think,
is
a
point
that
was
brought
up
by
jackie
in
the
upcoming
quarters
plans.
A
So
I
think
most
of
our
teams
are
going
to
be
following
this
in
the
upcoming
quarter
and
that
would
be
very
exciting
and
lastly,
for
testing
she's,
consolidating
all
the
testing
research
in
one
place
with
erica's
new
research
synthesis
project,
and
this
should
help
identify
gaps
that
we
don't
have
documented
yet
specifically
for
artifacts.
B
I
think
the
idea
of
office
flowers
is
really
interesting,
probably
because
I'm
not
caught
up
on
everything.
Yet
I
don't
know
about
the
next
quarter
plants,
but
I
was
wondering
if
vitika
you
had
a
link
to
that
somewhere,
where
I
can
read
more
about
it.
A
Okay,
I'll
need
some
time
to
go.
Look
for
that,
but
I'll
definitely
send
it
to
you
on
the
slack
channel
on
uxci
cd's
channel
in
the
meantime
that
so
I
was
looking
at
the
bulk
deletion
of
runners
in
the
table
and
one
feedback
that
I've
left
for
gina
is
I'll
quickly
share.
My
screen.
A
Okay,
I
think
we
are
over
time
so
I'll
be
very
quick.
So
one
thing
that
I
just
noticed
in
this
design
was:
there
was
an
option
to
select
on
and
deselect
all.
So
what
I
figure
is,
if
you
are
providing
a
selection
option
on
the
at
the
level
of
the
header,
then
we
don't
really
have
to
give
the
these
options.
They're
kind
of
implied
that
when
you
are
clicking
when
you're,
selecting
and
unselecting
from
the
top,
you
are
automatically
selecting
and
deselecting
the
all
the
items
in
one
go.
A
So
something
that
I
was
interested
in
was
like
what
would
be
the
flow
when
I
am
moving
from,
let's
say
a
partial
selection
to
complete
deselection
and
when
I
say
that
what
I
mean
is
so,
let's
assume
that
I'm
clicking
on
three
of
these.
So
this
will
get
a
partial
selection
status
right
like
that
minus
symbol
in
the
in
the
middle
of
the
checkbox.
So
how
do
I
go
from
that
to
deselect?
Would
the
would
it
be
like?
A
B
B
Way,
but
it's
the
way
that
I'm
used
to
it's
the
known
way:
yeah,
it's
a
known
way.
I
will
have
a
look
at
this
gina
and
get
back
to
you,
I'm
trying
to
now
kind
of
bulk
schedule.
All
feedback
requests
for
fridays.
Vitica
gave
me
an
idea
for
this
a
couple
months
ago.
So
you
can.
You
will
hear
back
from
me
on
that
on
friday,.