►
From YouTube: CI/CD UX Meeting - 2021-04-07
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
B
A
And
I
see
a
couple
of
fyi
items
so
vitica.
Why
don't
you
get
started.
B
Sure
so
this
is
just
to
notify
that
there's
a
doesn't
there's
a
merge
request
up
for
the
cicd
variables
blog.
So
if
anyone
wants
to
go
and
give
their
feedback
and
review
the
content,
please
feel
free
to
do
so.
And
the
next
thing
is,
I
started
off
on
a
very
elaborate
exercise
which
is
visualizing
the
merge
strain
index
page.
So
it
is
an
ongoing
work
and
I
think
this
will
continue
for
at
least
one
more
milestone,
including
this
one.
B
So
it's
still
in
the
process
of
being
shaped
up,
but
if
you
feel
that
there's
something
that
you
would
like
to
make
me
aware
of,
or
just
like
review
the
designs
again,
which
are
posted
on
the
issue,
I'll
be
really
happy
to
get
your.
C
A
I
think
you
up
next.
C
The
package
stage
is
doing
a
lot
of
work
to
bring
quality
up
to
the
quad
planning
level,
so
product
management,
product
design,
engineering
manager
and
engineers
and
test
all
operating
in
strategy,
and
we
haven't
been
doing
a
good
job
of
that.
So
I
was
just
wondering
how
everyone
else
has
that
relationship
with
that
team
member
and
how
you
all
work
together
to
to
make
the
quality
aspect
kind
of
the
first.
B
Priority
one
thing
that
I'm
aware
of
that
happens
in
ci
is
like
tiffany
who's
from
testing
she.
She
is
a
part
of
almost
all
those
strategic
meetings
are
quad
planning
and
she's
kept
aware
and
she's,
especially
like
she
really
helps
with
the
team,
with
setting
up
the
environments
and
all
of
that
during
the
research.
That
might
not
be
the
area
that
we
want
to
look
at,
but
I'm
just
putting
that
across
that
she
helps
us
with
that
as
well.
B
Group
ian,
could
you
could
you
kind
of
elaborate
on
what
exactly
like
what
kind
of
participation
or
partnership
you
are
looking
to
hear
about.
B
C
B
It
does
I
was.
I
was
also
curious
about
whether
you're
looking
for
a
better
partnership
of
us
as
designers
for
the
quality
engineers
in
some
way,
because
as
of
today,
what
I'm
absolutely
sure
about
is
that
my
interaction
with
the
quality
engineer
is
very
limited,
and
in
my
process
they
do
not
have
much
involvement
at
all.
C
That's
the
thing
that
I've
been
experiencing
and
I've
been
struggling
to
figure
out
a
way
to
make
a
change
in
that,
and
so
I
started
inviting
that
engineer
directly
for
feedback
and
being
more
part
of
those
conversations,
but
how
we
enable
each
other
is
still
not
the
conversation
that
is
happening,
and
I
really
I'm
used
to
being
the
designers
kind
of
left
behind
while
pm
an
engineer,
just
kind
of
runs
with
it.
I've
experienced
that
in
past
companies
and
so
seeing
quality
in
that
same
almost
left
behind
feeling.
D
A
A
To
me,
that's
very
interesting,
because
I
have
no
idea
who
the
quality
engineers
for
my
teams,
so
it's
really
about
being
a
maintainer
or
that
specific
role,
and
I
see
here
that
we
only
have
four
in
terms
of
like
globally
speaking
in
terms
of
gitlab,
and
I
wonder
if,
in
your
teams,
do
you
have
a
like?
A
You
know,
it
looks
like
you
have
someone
that
it's
assigned
to
do
qa
right
in
in
package,
but
do
you
danny
or
vitica
know
if
there
is
one
specific
person
in
your
stage
group
that
does
that,
because
in
my
case
for
example,
I
take
it
take
into
consideration
that
if
it's
a
front-end
change,
an
update
and
things
relate
to
the
user
experience,
I'm
the
qa.
A
So
that's
implicit,
but
I
just
I'm
just
curious
to
hear
how
how
you,
how
you
handle
it.
B
B
I
think
she
does
the
metal
testing
as
well,
if,
if
required,
so
she
kind
of
takes
care
of
any
kind
of
testing,
that's
required
for,
if
you're
pushing
a
new
feature
of
if
you're,
making
some
substantial
change
in
the
workflow.
So
she
takes
different
things
into
account.
D
Right
yeah,
I
think
I
think
it
might
make
sense
to
to
broaden
this
discussion,
maybe
in
the
ux
like
channel
ian,
because
at
least
for
me
perhaps
that's
because
I
just
just
got
here,
but
I
don't.
I
don't
really
see
where
q
and
q
fit
in
our
current
development.
Workflow
right.
I
I
knew
we
had
some,
but
I
don't
like.
If
you
ask
me,
I
don't
know
for
sure
what
exactly
they
do
in
which
step
of
the
process.
C
D
A
Good,
we
are
all
lost,
that's
positive,
yeah!
So
ian,
do
you
want
to
bring
that
to
the
discussion
in
the
ux
channel
and
having
the
finding
back
awesome.
C
B
Oh
yeah,
so
I
wanted
to
talk
about
a
collaborative
effort
which
is
happening
on
the
cine
code
review
site,
and
this
is
something
that
was
long
awaited
for
so
it's
high
time
that
we
take
care
of
it
and
what
we
are
going
to
do
is
we
are
going
to
condense
all
the
complex
mode
strategies
such
as
merchant
pipeline
succeed,
most
merge,
train,
merge,
start,
merge,
train
when
pipeline
succeeds
all
into
this
one
global
kind
of
terminology
which
is
auto
merge,
and
this
is
because
it
punches
improve
the
usability
of
the
whole
merge,
widget
and
pipelines.
B
It's
going
to
relieve
ci
of
so
many
different
problems,
because
I
can
literally
pull
out
a
list
of
issues
a
very
long
list
of
issues
which
only
revolve
around
how
the
terminologies
in
the
different
scenarios
in
the
merge
widget
they
have
this
wrong
messaging
to
the
users
and
messages
are
ambiguous.
Messages
are
confusing
and
just
to
fix
those
small
problems
we
have
to
like
take
very
huge
efforts
from
the
back
inside
from
the
front
inside
from
the
ux
side.
So
what
we're
going
to
do
next,
like
with
auto,
merge?
B
We
are
going
to
like
deal
with
that
big
umbrella
of
problems
and
try
to
have
a
very
simple
interface
for
users
to
deal
with.
So
I
wanted
to
know
like
if
this
touches
upon
your
stage
group
in
any
way
and
there's
something
that
I
should
be
concerned
about
and
having
a
meeting
about
with
any
of
you
or
all
of
you.
I
would
like
to
know
about
it.
C
B
A
I
did
work
on.
What's
it
I
think
was
management
pipeline
succeeds
when
we
were
still
progress,
delivery
and
release
management,
I'm
not
sure
how
this
would
impact,
for
example,
testing
or
runner
like
directly.
I
don't
think
he
would,
but
maybe
this
is
a
good
point
to
do.
I
think
we
have
a
think
week
next
week
this
week,
no
we
postponed
to
next
week
or
just
throw
this
in
the
the
ops
channel
to
see
what
others
have
to
say.
So
we
can
start
discussion
in
the
issue.
A
I
think
it
will
concern
a
bunch
of
stage
groups,
especially
related
to
cd,
so
they
know
that
that
for
you,
since
you
inherited
most
of
my
work,
but
it's
been
so
long
that
I
don't,
I
don't
feel
confident
saying
exactly
where
it
will
impact,
but
I
have
a
feeling
that
this
would
need
some
cross
collaboration.
A
B
D
Daniel,
yes,
so
I'm
currently
working
on
the
on
the
issue
for
manual
actions
for
deploy
jobs,
and
one
of
the
possibilities
that
was
raised
by
nadia
is
to
have
a
ui
for
approving
or
rejecting
the
deployments
in
the
merge
request,
page
itself,
which,
from
the
ux
perspective,
is
something
I'm
trying
to
figure
out
still,
but
but
more
on
the
collaboration
and
ui
side.
I
didn't
really
find
any
written
documentation
for
how
to
create
a
merge
request
with
a
widget
or
how
to
contribute
to
it.
D
There
are
a
couple
of
things
on
the
pajamas
ui
kit,
but
but
yeah
it's
just
like
general
principles.
Nothing
really
specific.
C
So
funny
enough
that
you
bring
up
the
mr
widget,
we're
kicking
off
a
really
big
effort
that
I'm
just
getting
on
board
into
around
looking
at
the
merge
widgets
how
they
should
be
acting.
That's
the
research
that
we're
doing
what
users
are
expecting
from
it
to
make
improvements
and
then
from
there.
What
we're
hoping
is
to
make
some
guidelines
for
this
is
how
to
make
a
widget.
This
is
the
action
area.
This
is
the
content
area.
C
This
is
how
you
do
a
warning
in
a
widget
kind
of
sets,
some
of
those
standards
and
then
there's
talk.
I
believe
in
q2
of
having
the
team
work
together
on
the
broader
scale
of
this
widget
is
for
secure
and
does
all
their
scared
is
getting
okay,
all
right.
Here's
the
standards
we
came
up
with
here's
the
research
data,
go
improve
the
design
and
then
we'll
work
it
in
maybe
the
quarter
afterwards.
C
D
Right
yeah,
I'm
still
not
sure
if
this
feature
should
be
there
and
if
so
how,
especially
because
the
fact
that
it
concerned
the
concerns
deployments
means
that
the
merge
requests
might
already
be
merged,
but
then
there's
something
pending
right,
because
the
deployment
hasn't
been
approved,
so
that
could
be
kind
of
weird.
But
I'll
tell
you
what
next
time
we
have
a
chat
later
today,
I'll
show
you
some
of
the
stuff
I'm
working
on,
and
then
you
can
give
me
more
specific
feedback.
A
Perfect
timing
and
I
linked
here
another
umbrella
issue
that
pedro
created
to
yeah
to
store
all
this
information
related
to
the
redesign
of
merge
requests,
widgets
just
for
future
records.
A
Let's
see
team
retro,
do
you
want
to
do
this?
We
never
do.
This
has
been
sitting
here
since
nadia,
not
this
time
and
I
feel
comfortable
with
removing
it
but
yeah.
Just
let
me
know
if
you
want
to
go
over
it
or
if
it's
something
that
we
can,
we
can
skip
and
go
to
the
fun
stuff.
A
If
you
haven't,
I
think
they
opened
a
new
one
for
the
upcoming
milestone:
okay,
more
fun
stuff,
but
first
up
is
vidica.
B
Yeah
so
this
time
this
year,
I'm
participating
in
the
36
days
of
type,
mostly
because
of
peer
pressure.
I
was
also
asked
to
participate
in
that
inktober,
which
I
did
not
do
so.
I'm
kind
of
just
making
things
fine
with
my
friends
by
doing
this,
but
the
theme
that
I'm
choosing
for
this
year
is
devops.
So
all
the
illustrations
would
have
like
there
would
be
letters,
of
course,
but
the
word
would
be
related
to
devops,
so
the
first
one
is
agile.
D
Thanks
vitica,
do
you
know
the
the
illustrations
from
egghead?
It's
the
it's,
it's
a
online
courses
platform
and
they
have
a
lead
illustrator.
I
think
her
name
is
maggie
apoton
and
she
makes
these
amazing
illustrations
for
very,
very
abstract
concepts
like
there's
a
course
for
redux,
and
then
she
makes
this
amazing
illustration
that
perfectly
communicates
what
redux
is.
It's
it's
wild
as
enjoying
can
add
to
the
notes,
because
it's,
I
think
it
has
a
lot
to
do.
You
know
you
communicating,
also
abstract
concepts
from
from
devops.
A
That's
awesome.
It
makes
me
want
to
do
design
when
I
see
vitika's
illustrations
on
the
on
twitter
and
nadia.
Also,
I'm
sure
if
you'll
follow
nadia,
but
I
think
she
posted
yesterday
or
maybe
it
was
today
a
new
illustration
yeah.
It's
super
cool
that
is
nice.
Yeah
awesome.
My
my
point
is
well.
It's
a
shout
out.
We
have
a
couple
of
a
couple
of
other
attending
conferences.
This
quarter,
daniel
attending
the
web
directions
conference
and
vdk
nadia
the
pet
conference
ian.
A
C
C
A
That's
awesome:
can
you
bring
some
of
the
the
insights
to
us,
I'm
sure?
Well,
if
this
is
the
the
outlet
you
want
to
use,
but
I
would
love
to
hear
more
about
your
learnings
and
share
that
with
the
with
not
just
with
us,
but
I
think
other
designers
would
benefit
from
from
the
learnings.
What
do
you
say.
C
Yes,
there's
a
couple
of
us
attending
this
conference
and
I
think
we're
working
together
on
creating
something.
So
I
don't
wanna,
I
don't
wanna
steal
anybody
else's
thunder
by
accidentally,
giving
away
something
cool
too
really.
A
B
So
ian
I
wanted
to
ask
like
this:
this
shows
that
it
has
multiple
tracks.
One
is
strategy,
then
product
data
design,
so
would
it
be
like
you'll,
be
attending
all
of
those
in
the
future
scheduled
in
the
future,
or
was
this
a
pass
for
this
particular
like
strategy
track.