►
From YouTube: CI/CD UX Meeting - 2021-07-14
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
citdux
call
for
july
14th
every
time,
I'm
I'm
amazed
that
it's
already
so
further
down.
Let's
see
what
we
have
here,
the
couple
of
fyi,
so
I
think
we
all
seen
that
I
was
a
bit
surprised
to
have
friends
and
family
day
this
friday.
A
It
feels
like
again
the
another
friends
and
family
they
coming.
I
think
you've
already
scheduled
that
new
calendars,
if
you
haven't,
please
do
so
and
of
course,
you're
always
welcome
to
push
it
to
a
different
day
of
the
week.
So
remember
that
as
well.
If
you
don't
want
to
have
this
friday
off
and
couple
of
announcements
from
my
site,
we
now
require
formal
tracking
of
manager,
approval
for
learning
and
development
opportunities,
so
that
includes
conferences,
workshops,
professional
memberships
for
online
trainings
etc.
So
I
linked
here
the
merge
request.
A
Please
review
it!
If
you
have
any
questions,
bring
it
to
me
during
your
101st
or
async.
I
also
have
to
get
up
to
speed
with
this
process,
but
pretty
much
you're
gonna
need
not
only
the
verbal
approval
but
the
written
approval
from
me
before
you.
You
apply
or
pay
for
any
any
trainings
now
yeah
and
let's
see,
and
this
topic
about
gina.
A
So
let's
hear
some
answers
already,
but
I'm
gonna
voice
here
in
case
you
know
what
it's
called
later
on,
but
now
you
know
the
only
member
in
the
america
she's
in
you
go
to
boston,
and
I
think
now
it's
like
four
in
the
morning
for
her.
My
question
is
here
is
what
we
want
to
do
with
these
meetings
would
be
nice
for
her,
especially
in
the
beginning,
to
have
a
sinkhole
with
all
of
us
to
get
that
sense
of
yeah.
B
A
Theme
being
part
of
yeah,
the
the
design
group
etc,
but
I
wanted
to
know
from
you
your
ideas
I
thought
here.
Maybe
we
could
either
extend
that
this
call
a
bit
later
in
the
day,
so
it'd
be
late
for
nadia
and
vitica,
but
early
for
gina,
or
we
just
yeah
rotate
the
call.
If
you
want
to
scale
I
have
with
the
synchronous
meeting.
I
haven't
thought
about
async
yet
and
when
I
see
that
your
comments
are
around
that,
so
if
you
want
to
avoid
nadia.
Thank
you.
First.
B
Yeah,
I'm
always
against
like
having
anyone,
wake
up,
early
or
or
late
unless
it's
like
an
emergency
or
like
a
one-off
thing.
You
know
I
definitely
wouldn't
want
to
schedule
a
recurring
meeting
that
we
know
is
outside
of
working
hours
for
someone
from
our
team
and
the
way
we
address
it
on
the
pipeline
authoring
team,
for
example,
is
we
have
a
rotation?
So
sometimes
we
have
at
this
time.
B
Sometimes
we
have
at
that
time
and
some
people
are
able
to
join
both,
but
we
also
make
sure
to
share
the
recordings
and
things
like
that
for
others,
so
I
think
rotating
would
be
great,
and
then
we
can
also
like
double
down
on
async
participation
in
the
meetings
so
like
we
have
async
participation
meetings
at
gitlab
and
we
could
maybe
get
better
at
making
sure
that,
even
if
you
don't
join
the
meeting
that
you
add,
some
like
talking
points
something
to
share
or
record
a
video
ahead
of
time
like
there
are
many
things
that
we
could
kind
of
try
out
and
see
if
it
helps
us
stay
more
in
touch
without
like
yeah
scheduling
something
at
an
inconvenient
time.
A
Yeah,
I
like
that
idea
of
us
being
more
prepared
to
this
calls
and
adds
things
to
the
agenda
without
any
any
type
of
assets
right
ahead
of
time.
A
What
my
only
concern
about
generating
a
video
is
that
you're
gonna
have
yet
another
commitment
to
made
a
recording,
and
I
don't
want
to
make
that
the
rule
of
everyone
has
to
record
something
once
a
week
or
every
two
weeks
about
what
we're
doing
yeah.
If
we're
able
to
yeah
have
it
free
form
and
if
you
want
to
record
something,
that's
fine,
but
make
sure
that
we
add
things
ahead
of
time
and
whoever
is
able
to
join,
we
discuss
and
go
over.
A
I
think
it
even
for
us
to
keep
working
on
this
format.
My
experience
with
gitlab
is
that
it,
you
know
asking
people
to
record
things
at
the
point.
It's
gonna
suck
because
we're
all
too
busy,
but
that's
my
opinion.
That's
what
I
that's
why
I
would
like
us
to
have
some
still
face
to
face
contact
but
daniel.
I
know
that
you're,
you
wrote
your
comments.
John.
C
Yeah,
no,
I
I'm
gonna
echo
an
idea
suggestion
I
think
async
is
definitely
having
a
rotation
and,
and
one
week
some
part
of
the
team's
async
and
the
other.
The
other
parts
they
think
is
the
better
way.
I
I
like
recording
stuff.
So
for
me
it
would
be
fine.
The
the
release
group
has
the
same
the
same
rotation
because
we're
also
across
many
time
zones,
but
our
weekly
meetings
are
not
recorded
so
so
for
me,
I
participate
async.
I
had
stuff
on
the
agenda,
but
it's
it's
kind
of
hard.
C
Like
sure
I
can
see
what
was
discussed,
but
it's
not
the
same
thing
as
being
part
of
the
of
the
meeting,
so
I'm
actually
excited
to
be
able
to
record
a
video.
Then,
like
my
videos,
played
as
part
of
the
meeting
and
then
afterwards
I
can
watch
everything
and
it's
almost
like
I've
been
there,
so
so
yeah,
but
I
understand
like
if,
if
you
can
that
week,
it's
fine
just
add
to
the
agenda,
don't
record
anything.
A
Right,
okay,
so
let's
do
that?
Let's
keep
as
is,
and
we
can
try
to
rotate
a
couple
of
times.
A
You
are
going
to
come
back
to
europe
right
at
some
point,
so
we're
gonna
have
to
either
have
the
discussion
again
or
try
to
try
out
this
format
and
see
what
time
of
the
day
we're
going
to
have
to
to
reschedule
this
call
to
to
to
adapt
not
only
to
vitica
but
also
a
little
bit,
maybe
later
in
the
day,
just
to
give
an
idea
of
how
that
would
look
like.
A
But
let's
talk
about
that
when
the
time
comes
and
I'll
I'll
write
it
down
in
slack,
so
that
videka
and
angina
can
also
be
on
top
and
of
course,
we're
gonna
we're
hiring
someone
else
for
package
and
we
don't
know
where
the
person
is
gonna
be
so
let's
see,
let's,
let's
try
out
this
format
so
yeah
thanks
for
your
input,
awesome
and
then
now
we're
over
to
stage
group
updates,
then
you're
here.
First.
C
Yes,
so
before
I
start,
I
added
right
right
after
at
the
fyi
for
the
friends
and
family
day
I'll
be
out
of
office
tomorrow,
I
was
gonna
actually
schedule
my
out
of
office
for
friday,
but
then
I
thought
you
know
what
friday's
such
a
calm
day,
I'll
schedule
it
for
thursday
and
then
three
days
later,
I
figure
out
friday
was
our
friends
and
family
days,
like
yes,
jackpot
really
long
weekend,
but
yeah
with
that
out
of
the
way.
C
C
Let
me
see
here
yeah,
but
this
this
was
a
a
nice,
a
nice
process,
because
essentially
this
is
the
combination
of
working
in
a
lot
of
smaller
issues
for
the
environments
page
and
the
table
and
over
time,
realizing
that
a
lot
of
them
were
either
unfixable
because
of
the
state,
the
pages
at
or
just
like
right,
less
relevant
compared
to
a
bigger
redesign
right.
C
Another
another
issue
that
corroborated
this
was
this
issue
that
that
I
just
worked
on
this
one
so
essentially
to
to
improve
the
stop
button
on
the
environments
page,
because
it
really
gives
no,
no,
no,
no
good
feedback
and,
and
then
the
result
of
improving
this
button
is
that
it
breaks
the
page
even
further
right.
So
adding
a
label
here
meant
that
we
would
introduce
a
regression
insert
on
certain
viewports.
Where
is
it
yeah
here?
C
It
is
right,
so
on
one
hand,
we're
fixing
something
but
also
breaking
it,
and
we
would
have
to
add
an
exception
exception,
the
code
to
make
it
work,
but
then
any
day
that
we
added
one
extra
button,
it
would
break
again
right.
So
it's
it's
more
more
proof
that
really
we
need
to
take
a
step
back
and
rethink
this,
and
the
team
was
very
supportive,
everyone's
like
yeah
for
sure
it
definitely
needs
to
be
redesigned.
C
So
so
I
was
happy
to
start
with
smaller
iterations,
but
then
build
the
trust
with
the
team
and
build
the
understanding
that
yes,
we
need
to
take
a
step
back
and
really
redesign
this
from
from
the
bottom
up.
So
that's
what
I'm
gonna
be
working
on
on
fourteen
two,
one
of
the
one
of
the
first
steps
I
took.
I
think
I
already
shared
here,
but
was
the
mapping
of
the
objects
for
environments?
C
There's
an
mr
to
add
this
to
pajamas
and
then
the
next
step
is
essentially
the
next
step,
that's
already
on
pajamas.
So
if
we
go
merge
request.
C
So
that's
what's
coming
up
in
42,
it's
essentially
the
whole
milestone
really
excited
to
have
this
big
chunk
of
design
other
than
that
I
shared
late
last
week
and
earlier
this
week,
this
little
project
like
it's,
how
I
do
these
things
with
alfred.
I
had
mentioned
this
to
hayana
a
long
time
ago,
just
like
yes
make
a
blog
post,
make
a
video
so
finally
made
a
video
out
of
it.
It's
on
youtube.
C
I
plan
on
adding
this
to
the
handbook
as
well,
because
some
of
this
information
could
definitely
go
back
there
and
maybe
also
create
a
blog
post,
but
I'm
not
sure
what
is
our
current
status
for
for
design
blog
posts.
So
let
me
know
and
and
when
I
know
that
I'll
definitely
write
a
post
for
that.
A
A
quick
apprenticeship
there
danielle
did
you,
do
you
have
the
chance
to
look
into
the
the
blog
post,
the
technical
part
of
it,
because
I
haven't
looked
back
since
I
came
back
from
a
pto.
A
What
I,
what
I
heard
from
marketing
was
that
they
want
us
to
have
at
least
five
blog
posts
by
the
ux
team
by
the
wax
department
released.
For
I
don't
know
if
it's
monthly
or
every
two
months,
there's
a
there's
a
time
box,
but
we
have
that.
So
what
I
need
to
do
is
get
back
to
the
marketing
folks
and
show
the
data
saying
that
we
do
publish
posts
like
monthly
you.
You
know
you're
gonna
justify
having
a
category
and
then
helping
you
again
once
those
conversations
start.
C
Over
yeah
yeah
for
sure,
do
you
think
it's
necessary
for
us
to
to
have
some
sort
of
of
process
just
like
we
have
the
krs,
like
each
group,
writes
one
blog
post
per
quarter
or
something
like
that.
C
A
I
would
say
we
have
enough
organic
and
that's
also
what
I
see
from
christy,
so
she
she
messaged
me
just
showing
some
of
the
data,
so
I'm
gonna
look
into
it
again
and
just
yeah
format
a
little
bit
that
for
us,
but
I
wouldn't
be
concerned
about
that,
especially
if
I
write
supposed
post
every
month
and
yeah,
so
I
wouldn't
be
concerned
but
I'll.
Thank
you
on
that
comment.
C
And
then,
lastly,
it's
something
else
I've
been
playing
with,
but
it's
I
I
imported
this
view
package
that
is
essentially
I
like
live
editor
on
the
browser,
so
you
can,
we
can
play
around
with
like
danger,
perhaps
yeah,
so
you
can
play
around
and
just
create
whatever.
Whatever
layout
you
want,
with
our
design
system
components.
C
The
goal
for
this
is
to
I'm
going
to
open
an
issue
in
mr
with
pajamas
team
to
have
this
integrated
into
into
our
documentation,
and
then
I
think,
the
the
the
jump
that
that
that
makes
this
really
useful
is
this
example
from
from
alt0,
where
you
can
actually
share
the
code
snippet.
C
So
it
adds
all
the
code
you
wrote
into
the
url,
so
you
can
very
quickly
like
do
some
quick
prototype
or
some
pair
of
programming
with
a
with
an
engineer,
and
then
you
generate
a
code
sample
that
you
can
share
with
other
people
and
when
they
open
it,
it
shows
exactly
the
code
that
you
had
there.
I
had
this
in
a
previous
job.
I
built
it
for
react
and
it
was
super
useful
to
just
sit
down
and
very
quickly
prototype
something.
C
A
Is
super
cool
daniel?
Have
you
been
working
or
collaborating
with
the
foundation's
folks
on
this
or
it's
just
a
your.
B
C
Copy
pasted
some
com,
random
configuration
and
it
worked
like
yay,
I'm
able
to
share
it
because
it
was
working
only
on
my
machine.
This
is
on
gitlab
pages,
but
then
I
added
something
and
made
it
work,
so
I'm
gonna
share
it
with
them
today
and
see
where
it
goes.
This
is
super
cool,
I
would
say
if
you
don't
have
an
issue
open
for
this.
A
Yet
and
like
you
know,
keep
track
of
it
and
get
more
people
to
contribute
I'll
say
do
so,
because
this
is
really
next
level
for
us
in
terms
of
how
we
can
use
pajamas,
not
only
as
this
static
sort
of
truth
right,
but
yeah,
a
prototyping
tool
for
for
us
for
design
so
broadcast.
Please.
B
Yeah,
this
is
really
cool.
I
think
it
can
also
be
a
great
learning
tool.
I
personally
don't
feel
super
comfortable,
making
changes
to
the
components
and
like
I
can
do
some
small
things,
but
I
think
using
this
could
really
help
just
learn
different
parts
of
the
components
and
how?
How
do
you
modify
them,
because
when
you
look
at
the
whole
layout
right,
it's
very
like
intimidating,
there's
a
lot
of
stuff
there
when
you're
looking
at
a
whole
page
here,
you
can
start
looking
into
exactly
what
does
one
component
look
like?
C
A
I
think,
especially
for
my
workflow
and
the
way
I
work
today,
where
I
don't
prototype
as
much,
but
as
you
need
to
communicate
the
ui.
I
would
use
this
rather
than
yeah
and
if
you
could
embed,
for
example,
anything
like
a
working
prototype
in
the
issues
or
have
a
link
to
something,
you
know
that
it's
a
whatever
just
hold
it
in
any
environment,
better,
be
perfect.
This
is
the
next
level
design
management.
C
B
Yeah,
so
I
will
share
an
update
on
the
visionary
mock-ups
for
ci
and
boarding
so
for
the
past
couple
milestones
dove
and
I
have
been
really
diving
deep
into
research
around
different
areas,
like
we've,
wrapped
up
the
cms
study,
where
we
mostly
looked
at
the
pipeline
editor
and
like
how
do
you
get
started?
Building
a
pipeline?
B
Well,
not
only
pipeline
editor,
a
lot
of
participants
use
their
local
editor
actually,
but
that
experience
we
learned
a
lot
about
and
also
learned
a
lot
about.
How
do
you
uci
templates
and
like
how
do
different
teams
collaborate
on
ci
templates?
How
do
they
create
template
libraries?
How
do
they
onboard
developers
onto
their
csd
practices
so
based
on
all
of
this
information?
B
I've
been
creating
these
mockups,
so
I'll
share
my
screen.
So
the
idea
here
is
to
have
an
onboarding
experience
that
uses
the
templates.
B
Like
relies
mostly
on
the
templates,
but
by
surfacing
additional
metadata
about
the
templates
and
sorting
the
templates
into
appropriate
categories,
we
can
make
it
much
easier
for
you
to
actually
find
a
template
that
will
allow
you
to
get
started
very
quickly
and
another
thing
is:
we
will
allow
organizations
to
create
their
own
template
libraries
and
those
will
need
to
be
surfaced
in
ci
and
boarding.
B
So
when
a
developer
like
for
this
mockup
that
you're
seeing
this
is
like
a
developer
on
boarding,
let's
say
the
gesture
in
the
company
and
they
they're
joined
the
product
and
the
project,
and
they
need
to
create
a
pipeline
for
that
project.
But
they
need
to
use
the
templates
that
the
organization
created,
because
for
compliance
reasons
and
just
to
enable
like
consistent
csv
practices,
they
need
to
distribute
those
specific
templates.
B
So
we
would
detect
your
repo
language
and
we
would
recommend
the
template
that
is
from
that
custom
library
and
we
will
be
like
hey.
You
have
a
go
project.
Here's
a
here's,
a
go
template
that
your
company
created,
use
that
and
then
also
we
want
to
introduce
additional
capabilities
for
browsing
the
templates.
We
will
have
organizational
workflows
so
like
these
are
the
custom,
workflows,
git,
lab
workflows
and
maybe
community
workflows
as
well,
and
you
would
be
able
to
filter
them
using
filter
search.
This
is
visionary.
So
just
keep
that
in
mind.
B
I
don't
know
if
it's
gonna
end
up
looking
this
way,
but
this
is
the
idea
and
dope
was
really
on
board
with
this
as
well.
So
this
is
still
work
in
progress,
but
the
idea
here
is
that,
from
what
I
learned
from
ux
research
around
ci
templates
people
like
how
they
they
can
they
separate
templates
into
so
many
different
categories.
Like
one
template
can
be
about
deployment.
It
can
be
about
a
specific
language.
It
can
be
about
like
a
specific
technology.
B
Are
you
deploying
to
aws,
or
are
you
deploying
like
to
kubernetes
all
kinds
of
things
like
what
kind
of
tests
you
want
to
be
doing
so,
when
you're
searching
for
something
that
can
help
you
create
your
workflow
you're
thinking
something
like
okay?
So
I
have
a
go
project
and
I
want
to
deploy
to
aws,
and
I
also
want
to
do
like
those
specific
tests
or
like
I
want
to
test
x
y
z
and
we
could
use
filtered
search
if
we
had
tags
for
those
different
things.
B
So
the
idea
is
to
create,
allow
you
to
create
tags
associated
with
templates
and
we
will
create
those
stacks
for
github
maintain
templates.
So
you
would
be
able
to
find
to
have
like
this
really
granular
search
control.
You
would
be
able
to
search
for
exactly
what
you
need
and
we
will
recommend
you
a
template
and
then
also
looking
into
some
ui
polish
for
the
pipeline
editor.
B
I
will
be
collaborating
on
the
with
the
editor
team
on
that
as
well
like
the
dream
dome-
and
I
have
is
that
someone
who
uses
vs
code
on
the
day-to-day
when
this
when
they
switch
to
the
pipeline
editor.
They
don't
feel
pain
because,
like
it's
such
a
feature-rich
editor,
it's
great
has
great
ux,
looks
good
lots
of
plugins
and
everyone
customizes
their
editor.
B
Just
like
it's
like
their
baby,
you
know
developers
get
really
attached
to
their
editor
of
choice,
and
so
we
need
to
make
the
pipeline
editor
good,
and
we
also
need
to
make
sure
that
it's
kind
of
in
line
with
what
we
have
in
the
web
ide
so
we'll
be
collaborating
on
like
creating
one
single
way
to
commit
in
github,
for
example,
because
right
now
we
have
different
different
patterns
for
committing
in
the
web
id
and
in
the
single
file
editor
for
instance,
and
now
we
have
the
pipeline
editor,
which,
which
would
be
like
a
whole
new
thing,
so
we
will
need
to
align
on
some
things
there
yeah
and
also
we're
planning
to
allow
you
to
customize
the
content
in
the
sidebar.
B
So
if
you
have
an
organization
with
their
own
custom
cicd
practices,
they
would
be
able
to
set
it
up,
maybe
in
cic
aesthetics
at
the
gift
level
and
be
like
hey.
This
is
how
you're
supposed
to
set
up
your
pipeline.
According
to
our
standards
use,
this
template
include
this:
do
that
and
yeah,
so
you
can
just
kind
of
follow
the
steps.
Maybe
we
could
even
have
like
interactive
checklist
in
the
sidebar,
so
you
can
actually
check
things
off.
B
That
would
also
be
cool,
so
yeah
we're
looking
into
things
like
that,
and
when
you
use
the
templates
inside
the
pipeline
editor
you
we
would
separate
them
into
buckets
workflow
templates,
which
are
like
end-to-end
pipeline
templates
that
you
use
kind
of
as
a
backbone
when
you
get
started
with
the
pipeline
and
then
workflow
extensions,
which
are
all
of
the
yaml
pieces
that
you
would
use
with,
include
or
extend
keyword
and
so
on.
So
these
can
be
jobs
or
can
be
like
mini
workflows,
that
kind
of
provides
like
specific
functionality.
B
So
when
you
click
on
add
workflow
extension,
you
would
see
something
like
this.
Let's
say
so.
These
are
like
gitlab
extensions.
So,
for
example,
the
sas
scan
it's
an
extension
you're
meant
to
use
with
an
include,
and
also
you
would
be
able
to
use
the
filter
search
here
as
well
yeah.
So
this
is
really
exciting,
because
I
think
we've
gathered
so
many
insights
that
we're
really
starting
to
get
more
clarity
around
where
we
need
to
be
heading
and
these
mock-ups.
B
We
will
be
using
to
facilitate
the
discussion
across
gitlab
and
with
our
customers
made
with
the
sales
team
gitlab
users
like
once
we
have
the
mockups,
we'll
figure
out
exactly
how
we're
going
to
communicate
it,
because
I
think
we'll
need
to
be
strategic
about
it,
because
there's
also
oh
shiny,
is
working
on
the
big
proposal
for
overhauling
everything
about
the
templates
and
it's
really
really
good
and,
for
the
most
part,
we're
aligned.
But
we
need
to
make
sure
we
have
like
leverage
to
lead.
B
This
feature:
development
from
the
place
of
user
research
and
the
insights
that
we've
been
gathering
and
what
the
customers
need,
because
so
far
it's
been
really
like
dominated
by
the
engineering.
The
whole
conversation
about
it.
So
hopefully
the
mock-ups
will
allow
us
to
like
communicate
the
vision
in
a
more
clear,
cohesive
way.
So
we
can
move
things
forward
and
the
plan
is
that
in
14.2
we
will
be
having
discussions
around
these
mock-ups,
like
hashing
things
out
figuring
out.
B
If
there's
any
gaps
that
we
haven't
considered
and
then
we
want
to
see
if
we
can
define
the
mvc
steps
to
start
the
development
in
14.3
to
start
taking
steps
in
this
direction.
A
And
I
have
a
question
not
in
not
in
terms
of
the
flows
or
or
anything
related
to
the
vision.
But
when
I
look
at
it,
I
see
some
things
that
don't
look
like
pajamas
and
I
just
wanted
to
know
if
you're
also
like
creating
new
pieces
of
ui
or
changing
components,
or
you
try
to
use
everything
that
you
have
today
in
your
visionary
mock-ups.
B
Well,
these
are
visionary,
so
I,
like
I
kind
of
decided
that
it
doesn't
really
matter
at
this
stage,
because
the
idea
is
to
communicate
the
functionality
and
the
underlying
like
ux
and
even
like
information
architecture,
because
that's
kind
of
the
main
blocker.
We
need
to
figure
out
how
the
templates
will
work,
so
I
foresee
that
the
ui
will
be
reworked
quite
a
bit,
so
the
things
here
that
do
not
comply
with
pajamas.
I
guess
it's
the
editor
layout,
but
it's
also
like
not
in
the
pajamas.
B
We
have
so
many
different
editors,
like
everything
in
the
editors
is
custom
like
in
the
web
id
also
their
navigation
and
everything
it's
one
of
a
kind.
So
in
other
words,
this
is
something
that
I
will
be
considering,
and
we
will
definitely
do
our
best
to
reuse
things
that
are
already
available
in
the
product
and
if
not,
we
will
have
to
also
look
for
ways
to
align
it.
B
So
I
think
a
lot
of
work
will
have
to
be
done
for
aligning
the
editor
ui
with
the
editor
team
and
web
id
specifically,
because
what
we
see
is
that
pipeline
editor
is
already
used
the
most
for
pipeline
configuration
among
all
different
editors
that
we
have
in
gitlab,
like
the
majority
of
people
who
use
a
web
editor
for
pipeline
editing,
they
use
the
pipeline
editor
already.
B
However,
web
id
is
well
loved
by
github
users
as
a
whole,
like
it's
a
pretty
good
editor.
So
if
we
need
to
come
into
alignment
a
bit
more
with
the
web
ide,
I
think
we
would
be
doing
that
as
well.
But
at
this
point
like
again,
this
is
just
to
set
the
vector
for
discussions,
and
I
think
this
will
really
shift.
The
ui
will
keep
shifting.
As
we
have
these
conversations.
A
B
A
This
would
be
a
good
opportunity
to
do
something.
That's
similar
to
what
daniel
is
going
to
do
for
environment,
add
to
pajamas
like
to
the
objects
right
area,
because
it's
such
a
complex,
yeah,
just
a
complex
ui.
You
have
so
much
that
can
be
customized.
That
needs
to
be
like
what
you
say:
aligned
with
other
product
areas,
so
that
could
also
be
part
of
a
car.
Imagine
that,
after
your
vision
right,
how
do
we
reuse
that
awesome?
Thanks
for
answering.
C
So
my
quick
comments
on
it.
I
love
this
nadia.
C
I
think
it
makes
a
lot
of
sense
in
terms
of
pipelines
being
the
the
glue
that
ties
everything
together
on
gitlab,
so
I
could
see
this
becoming
not
just
an
onboarding
to
how
to
get
started
with
a
pipeline
for
your
project,
but
how
to
get
started
with
your
project
period
and
really
being
one
of
the
big
gateways
to
start
using
gitlab
as
either
as
a
individual
developer
or
as
a
team
or
as
an
organization,
so
very
excited
with
this,
and-
and
I
needed
this
like
three
days
ago
when
I
started
the
this
pajamas
playground,
because
I
needed
to
find
a
way
to
host
vue.js
app
and
gitlab
pages
and,
like
I,
google,
five
different
versions
and
ironically,
the
version
I
found
was
hosted
on
github,
even
though
it
was
specifically
like
how
to
host
vjs
and
gitlab
pages,
and
it
wasn't
github.
C
So
I
don't
know,
maybe
maybe
helping
people
set
up
a
mirror
for
that
kind
of
thing,
but
but
I
think
yeah
in
terms
of
community
this.
This
is
something
that
will
definitely
draw
draw
people
into
gitlab,
because
it's
a
direct
benefit
to
to
hosting
your
your
repositories
for
pipelines.
There
so
really
excited
to
see
where
it
goes.
B
Yeah
thanks
we're
also
going
to
collaborate,
probably
with
the
configure
team
around
autodevops,
because
the
vision
that
they
have
for
other
devops
is
quite
similar.
It
seems
like
we're
starting
to
move
in
the
same
direction,
using
ci
and
autodevops
to
enable
gitlab
features
and
to
aid
devops
adoption,
because
in
the
end,
that's
our
goal
like
as
a
platform,
we
need
to
increase
stage
adoption
and
cinboarding
and
autodevops
could
both
really
help
with
that.
It's
just
kind
of
like
two
different
flavors
of
doing
the
same
thing.
B
Other
devops
would
be
this
other
magic
or
the
automatic
way,
but
yeah.
I
think
it
will
take
us
a
few
milestones
to
just
like
really
figure
out
the
roadmap.
For
this
and
hash
things
out.
We
will
be
doing
solution,
validation
as
well,
so
it
will
take
some
time.
C
Yeah-
let's
definitely
collaborate
on
this,
because
I
also
want
to
be
closer
to
the
configure
team
since,
since
it
makes
sense
for
us
to
work
with
it
together.
Another
question
I
I
from
from
something
that
was
in
the
mock-up
the
within
the
pipeline
editor
the
commit
button.
Do
you
have
any
plans
to
find
ways
to
make
this
feedback
loop
faster?
Because
that's
something
else
I
saw.
C
I
was
working
locally
on
on
my
pipeline,
but
I
had
to
like
keep
making
commits
and
pushing
like
five
six
seven
eight
times
until
until
my
pipeline
was
was
ready.
I
guess
using
the
webinar
web.
The
pipeline
editor
on
on
the
web
would
make
it
a
bit
faster,
but
even
so
like,
since
I'm
already
within
gitlab,
it
could
be
nice
to
have
a
way
to
like
not
commit
the
pipeline,
because
I'm
just
it's
just
a
draft
that
I'm
running
until
it's
it's
working
right.
B
Yeah
we
have
an
issue
around
it
or
do
we-
maybe
I
just
created
it
in
my
head,
but
basically
I
uncovered
the
related
insight
in
in
research
that
I'm
currently
analyzing.
So
probably
there's
no
issue
yet,
but
it's
my
to-do
list.
We
want
to
allow
you
to
test
your
pipeline
before
committing
there's
been
lots
of
discussions
around
it
like
for
like
half
a
year.
B
Every
time
we
talk
to
michael,
he
talks
about
it
and
we
heard
it
from
developers
as
well
dopes
engineers,
especially
those
who
are
creating
really
complex
pipelines
like
you,
don't
want
to
sit
down
and
write
your
gigantic
hundred
job
pipeline
in
one
sitting.
It
doesn't
happen
this
way,
you're
going
to
iterate
on
it,
so
you
want
to
test
it
somehow
locally.
The
thing
is:
it's
just
difficult
technically
to
figure
this
out,
and
it
would
be
a
huge
undertaking
for
us
to
take
it
on,
but
we're
starting
to
explore
these
ideas.
B
We
just
have
like
lots
of
other
things.
Kind
of
that
are
high
priority
right
now,
but
we'll
we'll
be
looking
into
this
and
to
take
this
further,
we
were
also
discussing
making
testing
possible
in
different
contexts.
So
it's
not
enough
to
allow
you
to
test
your
pipeline
just
on
the
default
branch
or
or
like
if
you
have
a
complex
pipeline,
the
yaml
that
you
have
is
not
necessarily
the
pipeline.
That
runs
because
you
have
all
kinds
of
different
conditions.
B
B
Yeah,
I
just
added
this
little
screenshot
so
for
these
mockups
dom,
and
I
really
wanted
to
highlight
exactly
those
technologies
and
features
and
templates
that
are
used
the
most
just
to
make
it
more
exciting,
so
turns
out
we're
tracking
this.
So
in
the
screenshots
that
I
added
you
see,
the
top
templates
are
used,
as
includes
so
you
see
that
at
the
very
top
we
have
auto
devops
aws
deployments
security
scans
sas.
Is
there
secret
detection?
Is
there?
B
So
these
are
all
gitlab
features
that
are
enabled
with
those
templates
and
they're
the
top
used
templates.
So
people
use
gitlab
to
enable
gitlab
features.
It's
just
the
ux
is
horrible.
We
basically
don't
provide
any
guidance
at
all
they're,
just
buried
there
in
the
repo,
with
all
of
those
other
templates
with
not
even
description.
So
that
also
like.
B
I
think
it's
an
indication
that
if
we
create
a
really
good
user
experience
around
ci
and
boarding
and
really
show
the
value
of
what
those
templates
do,
because
we're
not
giving
the
user
a
template,
we're
giving
them
a
feature.
So
we
need
to
communicate
the
value
and
what
what
job
this
thing
will
solve
for
them,
rather
than
being
like
here's,
a
ci
template
that
has
like
all
of
those
jobs
that
you
you
don't.
B
Maybe
you
don't
even
understand
the
ci
syntax
at
that
point,
but
you
could
still
take
advantage
of
what
it
can
do
for
you
so
and
also
I
haven't
edited
the
agenda.
Why?
B
But
we
also
found
some
insights
around
what
templates
are
used,
the
most
as
a
part
of
the
onboarding,
so
like
the
workflow
templates
and
it's
what
you
would
expect
to
see
the
hello
world
template
is
by
far
used
the
most
hold
on.
I
will
pull
up
a
screenshot,
so
it
also
proves
our
hunch
that
we
need
to
provide
something
super
easy
for
you
to
quickly
get
started,
because
when,
when
you
hear
about
gitlab
ci,
you
don't
sit
down
and
learn
syntax
for
three
days
and
write
your
100
job
pipeline.
B
B
Okay,
there
you
go
yeah,
so
you
see
that
hello
world
is
at
the
very
top
and
it's
like
three
times
more
than
three
times
more
used
than
the
next
one,
which
is
docker
and
then
node.js
and
python.
So
like
either
you
use
hello
world
or
you
just
select
a
template
that
matches
your
language.
B
Actually,
I
think
this
data
might
be
a
bit
skewed.
Probably
I
just
thought
about
it
by
the
experiment
that
we've
been
running
with
the
growth
team,
because
there
was
an
experiment
for
an
empty
state
with
the
hello
world
highlighted,
but
still
actually
I
mean
it
still
proves
the
same
point
that
people
use
hello
world
because
there
were
other
templates
there
in
the
empty
state
as
well.
Even
though
hello
world
was
highlighted
as
hey
this,
it
was
like
a
standalone
option,
but
most
people
went
with
it.
A
Thank
you
I'll
power
through
the
next
couple
of
items
that
we
place
out
of
office
today,
but
I
had
to
hear
some
of
the
things.
I
know
that
she's
doing
she's
helping
me
out
with
testing
research
for
testing
on
product
quality
dashboard,
and
I
know
that
the
special
guide
is
ready
and
that
victory
and
james
will
start
interviews
soon
start
looking
for
participants
for
this
interview
and
vitica
is,
of
course,
going
to
be
gina's,
onboarding
buddy.
A
So
if
you
haven't
met
gina,
yet
you
so
schedule
a
call
is
the
official
body,
but
we
all
should
be
connecting
and
helping
her
out
on
board
kid
lab
and
for
me,
testing
running
I'll,
be
prepping
a
ux
transition
issue
for
gina
in
the
upcoming
week.
So
I'm
really
hoping
that
you
focus
on
the
gateway
onboarding
danny.
I
went
through
it.
A
You
know
how
how
long
and
time
consuming
that
can
be
and
also
start
the
ux
on
boarding
next
week
and
do
that
painful
task
of
setting
up
all
the
devops
and
deploying
an
application,
and
for
her
specifically,
I
asked
her
to
write
some
testing
pipelines
and
you
know
configure
her
runner
so
that
she
understands
a
little
bit
about
the
product,
reuse,
documentation,
etc.
So
getting
up
to
speed
with
the
operation
side
of
that
I
have
gitlab
and
after
that
I'll
transition.
A
The
testing
runner
ux
work
to
her
in
the
meantime,
for
this
for
testing
I'll
be
working
with
the
create
team
to
coordinate
the
the
mr
widgets
framework
for
testing.
So
this
is
part
of
the
kr
that
we're
working.
What
they're
working
on
q2
to
define
the
standards
defined
one
needs
to
be
updated,
india.
Why?
A
So
at
this
point,
it's
not
planning
any
implementation,
but
looking
at
how
that
would
change
our
updates,
the
component
or
the
the
testing
widgets
in
the
merge
request,
and
then
gina
would
be
the
dri
once
she
she
fully
onboards
that
scene
runner.
So
that
probably
should
be
one
of
her
first
tests.
We're
gonna
have
to
speak
with
that,
so
that
she
can
support
the
usability
problems.
That's
real
improvements
in
testing
and
the
next
update
on
my
planet
from
package.
A
So
I
think
I
mentioned
this
in
the
beginning,
not
sure,
but
we're
going
to
be
moving
forward
with
one
of
the
candidates
for
testing
this
week.
So
fingers
crossed
everything
goes
well.
We
should
have
someone
joining
soon
and
then
our
team
will
be
will
be
complete
again
and
more
information
we'll
follow.
But
you
know
we
have
two
minutes
anything
else.
You
want
to
add
anything:
fun,
resources,
book,
tutorials
conferences,
articles
or
anything
else.
C
I
forgot
to
to
mention
on
the
release
group:
we
are
hiring
for
a
project
manager.
I
was
part
of
some
of
the
interviews
with
our
engineering
manager,
nicole,
and
we
are
moving
forward
with
with
one
candidate,
so
hopefully
we'll
have
a
full-time
pm
on
the
team
so
happy
about
that
as
well.
A
This
is
awesome,
and
I
know
that
is
also
part
of
the
interview
panel
for
the
the
pipeline
execution
pm.
So
hopefully
we're
gonna
have
a
you
get
left.
Remember
yes
in
this
quarter,
so
fingers
crossed
right.
A
We
made
it
one
minute
to
spare
hope
you
enjoy
your
day.
I'll
see
you
see,
you
later
see
you
later
bye.
Thank.