►
From YouTube: CI/CD UX Meeting - 2021-07-28
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
We
have
a
couple
of
fyis
in
the
agenda,
so
please
have
a
look,
some
time
off
and
updates
in
process,
and
I
want
to
start
with
the
good
news,
so
katie
mccoy
signed
the
contract
with
gitlab
and
she's
going
to
join
as
product
designer
for
package
in
september.
Super
excited
another
another
girl
in
our
team.
A
That's
super
fun
and
she's
based
in
new
zealand,
so
we're
gonna
have
well
not
yet.
A
So
that
means
we're
going
to
have
to
figure
out
what
to
do
also
with
gina
and
all
with
the
team
meetings,
and
we
had
a
discussion
I
think
two
weeks
ago
and
then
see
how
we
can
apply
that
to
yeah
keep
the
conversation
moving
ac
but
still
give
them
the
sense
of
yeah
the
teamwork,
so
the
starting
date
is
september,
the
6th
of
september,
so
there's
some
time
to
plan
the
the
transition
on
boarding
etc.
A
So
I'll
be
reaching
out
to
you
later
on
with
more
details
about
that
also
a
couple
of
announcements
for
me
from
me,
your
actual
case,
we
have
another
one
in
august
for
ci
cd,
so
I
hosted
the
one
right
that
you
presented.
I
think
two
weeks
ago,
so,
first
week
of
second
week
of
august,
we
have
one
for
ci
cd.
So
this
time
I
added
daniel
and
gina.
A
If
you
want
to
prepare
something
async
really
up
to
you,
you
don't
have
to
so
I'm
going
to
do
like
what
I
did
last
time.
Try
to
see
if
you
can
get
a
designer
from
a
different
product
area
in
america's
or
here
in
europe
to
present.
So
no
pressure
on
you,
but
if
you
want
to
participate
just
let
me
know
or
add
yourself
there
and
ping
me:
okay
and
what
else
gitlab
commit
it's
now
in
august,
the
first
week
of
august,
if
you
haven't,
subscribed
yet
signed
up.
A
Please
do
so
so
I'm
gonna
link
here
the
url
and
my
last
announcement.
I
I
think
I
reviewed
this
with
the
both
of
you,
but
let
me
vocalize
that
360
reviews
right.
So
the
survey
launches
next
week
on
monday,
I
think
I
mentioned
to
you
in
norwana
once
to
pick
three
to
five
people
to
provide
feedback.
But
the
handbook
says
only
three
people
so
select
three
peers:
that
you'd,
like
feedback
from
and
I'll
be
able
to
adjust
that
on
culture.
A
Amp
spent
a
time
in
your
calendar
for
this
and
as
christie
announced
yesterday,
I'm
not
sure
if
you've
seen
it
we're,
also
going
to
be
discussing
the
results
of
this
360
feedback
as
a
mid-year
performance
check
checking.
So
it's
not
the
formal
process,
but
we're
going
to
talk
about
performance
and
how
that
can
influence
your
the
yearly
performance
review
and
here
the
link
to
the
video
the
youtube
video
with
a
walkthrough
from
rose
explaining
how
the
process
works.
B
I
haven't
watched
the
video
yet
so
maybe
it
answers
my
question,
but
I
was
wondering
if
there's
guidelines
on
like
what
do
you
need
to
have
a
certain
mix
of
people
that
you're
asking
feedback
from
like
it
should
be
like
one
of
the
product
designers?
Maybe
your
product
manager
and
I
don't
know,
are
we
supposed
to
or
are
we
allowed
to
include
you,
for
example,
as
our
manager
or
should
we
would?
You
say
we
should
more
focus
on
our
product
teams.
A
So
you're
going
to
have
to
nominate
me
myself.
This
is
the
handbook
by
the
way
manager
you
don't
have
any
direct
reports
and
a
selection
of
three
peers.
So
me
and
three
other
folks
since
design
in
general,
we
work
in
a
very
heavily
cross-functional
teams
and
we
have
cross-functional
roles
I
would
say
select.
You
know
your
pm,
one
engineer
that
you
collaborate
closely
with
and,
for
example,
another
product
designer,
so
I
think
that
represents
a
good
mix
right
from
yeah
to
get
a
perspective
from
these
different
roles.
A
I
would
say
I'm
I
want
to
say
as
researchers,
but
with
our
team.
Now
it's
it's
limited,
but
I
would
say,
focus
on
the
people
that
you
interact
the
most
with
and
that
you
think,
okay,
their
feedback
will
be.
You
know
important
and
relevant
to
me
as
part
of
this
process.
So
does
that
clarify?
Does
that
answer
your
question.
A
So
years
ago,
pm
engineer
doesn't
matter,
but
myself
and
three
and
then
after
you
do
that
I
have
to
approve
and
review
before
you
can
these
people
get
the
alert
notification
so
I'll
talk
to
you?
Okay,
maybe
not
this
person,
maybe
that
other
one
so
you
can
go.
There
sounds
good.
C
A
And
there's
going
to
be
a
ask
me
anything
session
today:
there's
a
doc
yeah!
You
should
have
that
in
the
agenda,
but
there's
a
doc
with
a
couple
of
asian
questions.
If
you
have
any
other
questions
or
if
you,
if
you
want
to
clarify
or
see
what
other
people
are
asking
check
that
I'm
gonna
add
the
document
here.
A
A
Life
cycle,
so
jeremy
posted
this.
I
think
last
week
the
ux
week
day
wax
call
so
they
moved
it
up
right
in
pajamas
and
the
contribute
content
also
changed
and
this
to
help
discoverability
and
also
better
grouping
of
the
process.
There
are
a
couple
of
changes.
Also,
some
some
parts
of
the
process
were
deprecated,
so
please
read
become
familiar
with
that.
A
That's
important,
not
only
not
only
if
you
are
working
on
building
new
components,
but
if
you
are,
for
example,
adding
a
new
details
to
the
guidelines
or
working
or
updating,
figma
components
so
have
a
read,
and
next
week
we
can
just
you
can
touch
base
on
doing
a
one-on-ones.
If
you
have
any
questions
and
if
you
have
you
have
two
comments
here,
one
of
us.
C
Yeah,
I
do
have
so.
First
of
all,
I
I
did
take
a
note
of
it
and
I
found
it
very
useful,
like
the
changes
that
we
have
made
to
the
life
cycle
and
the
contribution
tools.
Secondly,
there
are
a
couple
of
people
who
have
been
reaching
out
for
another
part
of
kit
lab,
maybe
as
a
part
of
their
educational
curriculum.
C
They
are
looking
to
they're
looking
at
places
where
they
can
make
a
contribution
to
their
designers,
but
they
want
to
make
a
make
an
open
source
contribution
and
I've
been
getting
requests
around
like
how
they
can
make
a
contribution
to
gitlab
like
and
what
are
the
issues
they
should
be.
Looking
at,
I've
mostly
been
sharing
this
competent
life
cycle
link
and
the
link
to
the
pajamas
project,
but
is
it
something
that
we
are
going
to
maybe
move
our
focus
to
in
time
to
come
are
like?
C
Do
you
think
that,
looking
at
the
states
that
the
product
is
in
that
as
a
company
gitlab
we
are
at?
This
is
something
that
would
come
much
later.
A
Let
me
defend
this
incorrectly
you're
asking
about
the
community
contributions
and
pajamas.
A
I've
heard
some
conversations
in
the
past
about
this.
I
think
the
goal
right
is
to
it's
open
source
as
everything
we
do,
and
we
do.
We
do
have
a
couple
of
people
that
they
contribute
regularly
and
I've
seen
in
the
past,
when
I
participated,
for
example,
of
what
hackathons
and
I
saw
community
contributions
coming
specifically
to
pajamas
from
other
designers
of
frontendes
et
cetera.
A
I
do
think
this
is
a
it's
a
criteria,
but
I'm
not
sure
entirely
sure
if
it's
a
focus
today
or
if
that
would
be,
for
example,
next
quarter
or
next
year.
I
think
in
general.
Yes,
it's
part
of
the
idea,
but
not
that
the
foundations
team
is
working
actively
on.
It
now
say,
check
it
out
to
them
ping
them
in
in
slack
and
ask
about
that.
It
might
be
in
their
roadmap
and
they
might
have
a
plan
also,
for
example,
for
us,
but
this
this
updates
to
the
component
lifecycle.
A
Of
course,
it's
to
help
us
help
designers
contribute
not
only
more
actively
but
they
easily
to
pajamas.
That
was
part
of
feedback
right
that
was
collected
with
that
survey
and
yeah
also
aims
at
making
this
easier.
For
the
community,
oh,
I
hope
that
answers
your
question
without
answering
your
question.
A
So
gina
created
this
short
video,
the
reflection
on
her
onboarding
process
so
far,
and
I
see
that
we
all
left
our
comments
here,
but
I
want
to
say
that
I
was
really
impressed
that
gina
gina
is
really
a
pro
and
she
was
so
so
comfortable
and
talking
so
easily
about
her
process
so
clearly
in
a
very,
very
short,
video,
so
dina.
If
you're
watching
this
later.
A
It
was
awesome
really
proud
of
you
already
demonstrating
this-
the
async
values
right
and
capabilities,
and
I'm
really
excited
to
see
how
to
gonna
get
started
with
the
ux
workout
process.
So
update
on
that
vitica,
so
gina
will
participate
of
that.
That
kr
for
the
lyric
scorecard
we're
gonna
do
that
differently.
A
So
we're
gonna
get
her
to
do
the
whole
score
card
and
then
you
will
just
help
as
if
you
were
doing
the
the
buddy
buddy
process.
So
I'm
really
I'm
really
excited
to
see
how
gina
will
evolve
and
you
know,
perform
globally,
collaborating
with
the
wither
the
other
stakeholders
etc.
So
without
them.
And
then,
if
you
want
to
voice
your
comments
here
so
feel
free,
otherwise
we
can
jump
to
the
next
item.
B
I
can
sorry
I
haven't
realized
that
my
comment
was
next
yeah.
I
I
really
liked
the
video
and
I
really
liked
how
concise
and
clear
it
was,
and
I
even
gotta
be
jealous
like
I
can
never
learn
to
talk
like
that,
but
I
want
to
so
gina
if
you're
listening
to
the
recording
and
you
have
any
tips
for
for
like
making
a
recording
where
you
don't
don't
say,
filler
words
and
don't
mumble
and
ramble
on
that
tends
to
happen
to
me.
C
Yeah,
I
totally
resonate
with
that
thought.
Even
I
felt
that
the
whole
video
was
very
to
the
point
and
full
of
substance,
so
it
was
like
she
shared
some
pretty
great
insights
without
without
mumbling
and
without
fillers.
Of
course,
lady
speakers.
A
A
B
B
If
you
want
to
read
more
about
the
problems
that
we've
uncovered
and
the
research
behind
it,
and
things
like
that,
you
can
just
check
out
the
parent
epic
for
the
issue
that
I've
linked,
but
basically
now
now
that
we've
created
this
vision,
we
want
to
start
validating
it,
because,
even
though
it's
based
on
a
lot
of
insights,
the
actual
solutions
that
we're
proposing,
we
don't
have
a
very
high
confidence
about
many
parts
of
it.
B
So
we
want
to
validate
it
with
customers
over
the
next
milestone,
or
so
maybe
miles
and
a
half
and
we'll
probably
talk
to
a
mix
of
customers
and
internal
and
external
users.
I'm
going
to
create
an
issue
for
solution
validation
this
week
and
we
will
start
strategizing
how
to
go
about
it.
So
we
want
to
keep
it
as
lean
as
possible,
but
at
the
same
time
we
want
to
achieve
like
two
kind
of
different
goals.
B
We
want
to
validate
the
overall
direction,
the
overall
vision,
but
also
get
a
sense
for
what
should
be
our
top
priority.
What
are
the
things
that
we
can
prioritize
as
an
mvc
to
create
the
most
impact
and
provide
the
most
value,
because
yesterday
dave-
and
I
were
talking
about
our
team
being
a
bit
short
on
resources.
B
So
currently,
one
of
our
front
engineers
is
on
parental
leave
and
we
just
don't
have
enough
people
to
to
be
building
this
vision,
because
we
also
need
to
stay
within
the
air
budgets
and
take
care
of
bugs
and
things
like
that.
So,
for
example,
with
this
milestone,
I
think
we
have
like
only
a
handful
of
issues
where
we're
addressing
usability
problems
and
the
rest
are
bugs
and
some
carryovers
from
previous
milestones.
B
So,
basically
we're
moving
quite
slowly
and
we
feel
like
it's
really
important
for
us
to
be
very
strategic
about
the
things
that
we
will
be
working
on,
because
we
want
to
still
move
the
needle
on
gmail
for
the
pipeline
authoring.
B
So
we'll
see
how
that
goes.
I
will
keep
you
posted
on
like
what
ideas
we
have
at
this
point.
I
don't
know
how
we
will
be
structuring
the
study
to
to
kind
of
get
our
answers,
but
first
we
will
start
by
figuring
out
exactly
what
kind
of
questions
we
have
and
what
information
we
need
to
get
and
we'll
go
from
there.
A
Yeah,
that's
super
important
thanks
for
the
the
overview
and
idea.
That's
super
important
having
like
what
you
say:
the
high
level
of
confidence
right
from
the
solutions,
but
also
yeah
identifying
what
what
the
mvc
and
my
comment
here
is.
Also,
you
know,
think
about
not
only
the
boring
solution,
the
nbc,
but
how
you're
going
to
incrementally
build.
On
top
of
these
boring
solutions,
we
had
a
similar
challenge
in
the
now
different
release
management
team.
A
With
the
release
page
right,
we
did
the
research
and
was
like
okay,
we
have
to
redesign
everything.
We
don't
have
the
resources.
How
do
we
build
this
incrementally?
So
I
linked
here
the
epic,
it's
an
epic
that
breaks
down
how
we're
going
to
make
it
viable
so
from
going
api.
First,
that's
what
happened
to
us
going
api
first
to
giving
users
the
ability
to
edit,
but
not,
for
example,
creating
the
ui
and
the
reasoning
behind
it.
A
So
you
find
in
these
issues
how
kind
of
we
would
build
the
blocks
to
the
points
that
it
was
viable,
not
the
the
feature,
not
a
category
in
itself,
but
the
ability.
A
Releases
right
was
was
viable
so
to
share
with
you
here
in
this
example.
So
let's
consider
that
in
your
next
steps.
B
Yeah,
what
is
really
helpful
for
us
is
that
we
already
have
implementation
proposals
in
place
that
are
quite
fleshed
out,
so
that
gives
us
an
idea
for
like
what
things
are
possible.
B
So
I
think
once
we
get
some
insights
from
from
customers,
it
will
be
easier
to
see
the
path,
because
at
this
point
we
do
see
some
potential
nbc
paths
we're
just
not
sure
which
one
we
would
take
and
then
once
we
see
what
path
we
need
to
take,
we
will
be
fleshing
out
the
designs
further,
just
in
a
smaller
scoped
issue
and
then
probably
doing
some
lightweight
solution,
validation
on
the
details
of
the
experience
as
well.
B
And
last,
the
next
thing
is
that
I
started
documenting
new
jobs
to
be
done
around
pipeline,
optimization
they're,
based
on
the
research
insights
that
came
out
of
solution,
validation
around
the
pipeline
graph,
specifically
the
job
dependencies
view.
We
learned
that
the
job
dependencies
view
is
used
very
heavily
by
people
who
optimize
pipelines
and
yeah
at
gitlab.
B
We
have
people
who
are
dedicated
specifically
to
optimizing
pipelines
all
day,
so
it
was
very
interesting
to
talk
to
them
and
learn
about
the
use
case
and
what
goals
they're
trying
to
achieve
and
what
kind
of
information
they're
looking
for
so
yeah
feel
free
to
comment.
I
see
vitica
that
you
already
made
some
comments.
There
feel
free
to
voice
your
comment
here.
C
A
C
Also
put
some
comments,
so
that
was
a
learning
as
well
for
me
to
understand,
like
what
kind
of
impact
could
the
jobs
to
be
done
have
on
your
scorecard
exercise,
and
so
I'm
more
vigilant
now.
I
would
also
need
your
help
once
we
are
done
with
your
mr,
to
kind
of
rephrase
the
jobs
to
be
done,
that
we
have
for
pipe
and
execution.
B
Like
also
with
using
the
word
pipelines,
on
the
one
hand,
it's
specific
to
gitlab,
but
it's
not
really
only
specific
to
gitlab.
There
are
many
other.
It's
also
just
a
concept
of
like
your.
B
You
know
it's
not
just
related
to
github
product
offering
pipeline
is
used
interchangeably
with
the
workflow
for
when,
when
other
organizations
use
other
tools,
so
I'm
not
sure
it's
like
so
black
and
white
here
with
the
word
pipeline
and
also
using
the
word
workflow,
for
example,
github
uses
workflows
right
to
call
their
workflows,
workflows.
C
So
how
I
am
the
suggestions
that
are
put
in
your
mrs
right
now
so,
for
example,
this
one
this
the
one
that
says
when
viewing
up
running
pipelines,
so
I
kind
of
change
that
to
in
the
automation
process
so
because,
through
pipelines,
what
we
are
trying
to
do
is
we
are
trying
to
automate
tasks
so,
like
I,
I've
used
the
most
simple
words
that
that
I
could
come
up
with
for
to.
B
Yeah
thanks
so
much
for
for
going
ahead
and
making
those
suggestions.
I
think
automation
process
sounds
pretty
good
and
on
the
one
hand
it
sounds
a
bit
weird,
but
on
the
other
hand,
when
I
read
the
whole
job
to
be
done,
I
do
see
the
benefit
of
having
something
that
that's
at
a
higher
level.
Suddenly
you
take
a
step
back
of
something
that
is.
It's
not
like
pro
pipeline
is
not
necessarily
product
specific
me,
but
it's
solution
specific
still,
so
taking
a
step
above
that
makes
sense.
C
Okay,
so
we'll
move
to
the
next
point,
which
is
by
me.
The
first
thing
that
I
wanted
to
talk
about
was
a
recent
issue
that
I
worked
on.
This
had
been
there
since
a
very
long
time
and
it's
a
very
important
issue.
It
talks
about
substituting
the
id
with
iid,
which
is
like
the
idea
that
the
unique
id
that's
more
specific
to
the
project
rather
than
like
the
overall
thing
on
the
sas
platform,
so
that
id
would
definitely
be
shorter
than
what
we
see
as
pipeline
id
right
now
on
gitlab.
C
Now
it
has
many
uses,
like
some
users,
feel
that
it's
very
critical
to
their
workflow,
because,
for
example,
there's
a
use
case
where
the
file
version
field,
which
can
only
take
up
to
16
bit
integers
and
in
most
cases
id
has
exceeded
like
the
pipeline
id,
has
exceeded
16
bit,
and
so
it
kind
of
breaks
their
versioning
schema
and
that's
where
iid
would
really
be
helpful.
But
today
we
don't
show
id
on
the
ui.
C
I
mean
at
some
point
we
used
to,
but
I'm
not
very
sure
like
what
was
the
feedback
cycle
like
for
that?
Why
that
was
removed.
Exactly
but
there's
definitely
a
need
to
bring
it
back,
but
bringing
it
back
would
also
have
brought
back
the
previous
problem
that
we
were
facing,
which
is
having
a
very
cluttered
like
overly
populated
pipeline
index,
page
with
all
kinds
of
information.
C
So
we
had
to
make
sure
that
there's
a
way
to
surface
the
iid
on
the
pipeline
index
page.
Then
we
also
have
to
keep
in
mind
that
there
are
still
users
who
heavily
use
the
id
in
their
day-to-day
workflows.
So
we
shouldn't
be
excluding
those
or
to
include
include
the
bunch
that
finds
the
other
id
useful
and
those
ids
once
they're
surfaced.
They
also
had
to
be
clickable.
So,
given
these
many
constraints,
I
came
up
with
like
a
solution,
and
I
took
inspiration
from
how
other
pages
use
the
filter
bar.
C
So
I
figured
out
that
we
do
not
use
check,
boxes
or
switches
beyond
like
below
the
filter
bar
to
add
additional
filtering
criterias,
so
I
tried
accommodating
a
new
drop
down
in
the
same
space
and
yeah.
This
is
the
solution
that
we
kind
of
have
settled
for,
but
this
is
also
interesting
because
it
touches
upon
the
discussion
that
nadia
you
and
I
have
been
having
recently
about
like
what
identifiers
we
should
be
servicing
to
users,
so
that
conversation
was
more
on
the
side
of
surfacing
more
human-readable
ones.
C
But
we
also
have
to
evaluate
that
out
of
those
many
ideas
and
many
numbers
that
we
show
on
these
pages,
which
ones
should
take
precedence,
which
one
should
be
clickable
and
not.
A
Yeah,
sorry,
I
was
looking
at
the
other
prototype.
What
did
it
say?
Yeah,
it's
just
fyi,
I
think
daniel
is
also
looking
at
the
ui
improvements
and
usability
he's
a
big
roommate,
the
environment's
patient.
He
might
benefit
from
this
discussion,
video
of
what's
important,
and
why
and
how
do
we
display
it
and
then,
of
course,
with
the
with
guidance
from
the
the
foundations?
A
The
foundation's
fault
be
stable.
The
tabular
elements
they're
really
a
headache,
so
I'm
glad
you're
having
these
discussions,
and
so
I
have
a
side
question
here,
not
yet
sorry
for
jumping
into
it.
When
you
showed
when
you
decided
to
show
these
elements
in
the
in
the
drop
down
the
the
pipeline
id.
Was
there
already
like
a
way
in
the
product
today
to
kind
of
hide
and
show
elements
in
in
dui
or
in
the
in
the
list
that
you
that
you
could
replicate?
C
So
we
started
showing
the
iid
at
some
point
when
this
issue
was
created,
so
this
issue
was
created
in
reaction
to
that
and
it's
weird
because
I
at
like
a
month
back,
I
proposed
to
close
this
issue
because
the
description
that
we
had
upon
this
was
very
contradicting
to
the
requirement,
which
is
the
real
requirement.
The
issue
initially
said
that
we
have
all
these
different
ids
on
the
python
index
page
and
there's
hardly
any
use
for
the
id.
So
why
are
we
also
showing
the
id?
It
all
looks
so
confusing.
C
So
I
went
back
to
check
like
how
are
we
doing
it
today,
so
I
saw
we
don't
show
the
id
anymore.
I
mean
there
is
a
way
to
for
us
to
fetch
it,
but
we
are
not
surfacing
that
in
the
ui
anymore.
I
thought
maybe
that's
the
solution
to
this
problem,
so
I
proposed
closing
it,
but
then
you
would
see
that
many
comments
followed
after
my
comment
and
users
came
back
to
reiterate
what
the
real
problem
is
and
that's
when
jackie
and
I
went
ahead
and
changed
the
whole
description.
C
So
there
is
no
like.
I
did
not
replicate
any
existing
way
of
doing
it.
I
had
to
introduce
a
new
pattern
to
make.
It
appear.
B
I
have
I
have
a
couple
of
questions
and
comments.
So
do
you
have
a
sense
for
how
many?
What
is
the
percentage
of
the
users
that
use
ids
versus
ids.
C
Not
really
so
jackie-
and
I
also
thought
of
getting
in
touch
with
the
growth
team,
to
maybe
conduct
an
experiment,
but
in
the
meanwhile,
whatever
solution
we
would
have
rolled,
we
wanted
that
to
have
like
the
least
impact
on
both
the
sites
of
the
user,
like
people
who
want
to
use
the
id
people
who
want
to
use
the
id.
B
And
so
you
mentioned
that
the
reason
why
some
of
those
users
wanted
to
use
ids
because
using
the
regular
id
would
break
this
their
system
because
it
would
get
too
long.
B
So
that
makes
me
thinking
that
it's
not
like
a
pear
user
problem,
but
it's
per
project
problem,
or
maybe
even
per
organization,
because
based
on
their
workflows,
their
id
gets
long
and
it
breaks
their
system.
So
that
got
me
thinking
that
maybe
it
should
be
a
setting
at
a
project
level,
perhaps
like
ci
cd
setting
rather
than
having
a
toggle
in
the
ui,
because
it
seems
like
someone
would
make
a
choice
to
do
this
not
like
on
a
daily
basis
and
change
their
mind.
B
But
it's
more
like
a
choice
that
the
project
owner
makes
that
hey.
We
use
id
id
for
our
pipelines.
So
let's
show
it
in
the
ui.
C
C
I
couldn't
say
that
I
mean
I
would
say
yes,
but
not
with
a
lot
of
confidence.
I
would
get
a
better
confidence
once
we
start
tracking
this
information
and
so
far
there
was
no
way
and
we
also
did
not
realize
the
requirement
to
track
it.
So
we
don't.
C
B
Yeah
because
I
feel
like
if
there
is
no
need
to
allow
different
users
to
change
the
setting
like,
let's
say,
you're,
just
viewing
the
pipelines
page
and
you're
like
hey.
Let
me
check
out
the
id,
so
you
use
the
toggle.
It
feels
more
like
something
you
would
set
and
forget
like
I
want
to
use
id.
So
let
me
select
the
setting
in
ci
cd
settings
and
then
it's
applied
by
default,
but
I
don't
really
know
like
the
workflows.
C
That's
a
useful,
like
suggestion,
because
I
mean
this
is
also
the
first
time
I'm
coming
across
this
use
case.
So
I
also
don't
have
a
very
in-depth
knowledge
about
it.
C
But
yeah
your
point
about
whether
or
not
this
is
a
user-specific
requirement
or
project
specific
requirement
that
definitely,
that
is
definitely
what
we
should
be
kind
of
evaluating
because,
if
like,
if
a
team
is
working
in
a
certain
way
that
there's
that
definitely
makes
it
a
project
level
requirement
right
and
it
shouldn't
be
a
requirement
for
every
person,
who's
working
on
the
project
to
go
and
make
this
change
in
the
toggle.
Rather,
as
you
said,
it
should
be
set
and
forget
option
for
them
like
the
default
that
we
should
be
providing.
B
Yeah
also,
another
reason
that
I
can
think
of
to
have
it.
This
way
is
for
compliance
reasons.
So
if
an
organization
is
if
a
large
organization
wants
to
have
like
a
coherent
track
record
of
different
pipelines,
they
would
want
to
have
one
single
way
of
identifying
that
pipeline.
B
So
when
the
someone,
when
they're
being
audited,
they
don't
have
like
someone
uses
ids
someone
uses
ids,
and
now
it
can
be
confusing
so
like
having
a
standard
practice
that
is
applied
either
at
a
project
level
or
I
can
see
someone
might
even
want
to
set
it
at
group
level.
So
this
is
also
something
to
consider
you.
B
Maybe
you
could
also
check
with
the
compliance
team
to
see
if
they
have
any
insights
around
this,
because
they
have
a
better
understanding
of
like
different
standards
that
organizations
might
want
to
enforce,
and
sometimes
they
have
weird
things
like
that,
like
you
need
to
have
some
very
specific
ways
to
identify
different
events.
C
Yeah,
that's
a
good
point,
so
maybe
the
first
step
towards
this
should
be
setting
up
a
tracking
to
understand
like
how
many
users
are.
A
C
C
Yeah
sure
so
I
I
mean
individually,
I
went
across
the
initial
structure
for
documenting
this,
the
permissions
against
the
operations
with
both
of
you
individually,
but
I
put
a
snapshot
of
that
in
a
comment
that
I
in
the
latest
comment
in
the
epic
that
I've
linked.
So
that's
how
it
it
used
to
look
like.
But
in
the
conversation
that
I
had
with
fabio
yesterday,
there
were
many
things
which
were
uncovered
that
it
was
also
very
interesting
to
learn
about
how
we
like
set
policies
and
permissions
on
gitlab.
C
So
we
use
something
that
we
call
declarative
policies
and
generally
with
declarative
policies,
it's
very
easy
to
manage,
but
the
only
bumpy
part
with
that
that
experiences,
that
your
permission
model
is
kind
of
scattered
across
so
many
different
files.
C
Now
we
figured
that
the
ideal
way
of
making
doing
this
mapping
is
going
to
be
like
pick
an
operation
create
a
whole
matrix
of
conditions
and
roles
and
see
like
how
which
combination
of
roles
and
preconditions
would
allow
users
to
perform
in
action.
But
that
would
be
a
very
difficult
and
very
tedious
work.
To
do.
I
mean
imagine
one
spreadsheet
for
every
single
operation,
so
that's
definitely
not
not
something
that
we
we
should
take
up
doing
in
a
manual
way.
C
So
we
have
this
discussion
to
understand
like
how
much
value
we
would
provide
if
we
are
going
to
map
it
and
how
are
we
going
to
kind
of
decipher
the
learnings
out
of
it
so
far,
we
suggested
one
very
good
point
that,
instead
of
like
just
mapping
for
the
sake
of
it,
we
should
try
to
understand
like
how
the
chain
the
chain
and
the
flow
of
like
how
does
the
precondition
cascades
down
to
other
operations.
C
So,
for
example,
if
you
want
to
maybe
delete
a
build,
then
for
that
the
precondition
is,
you
should
be
able
to
have.
You
should
have
the
permission
to
maybe
like
some
editing
rights
on
the
project.
For
that
you
need
some
preconditions
to
do
something
at
the
group
level,
and
so
it's
it
it's
kind
of
it.
It
goes
in
that
way.
C
So
we
thought,
if
we
document
in,
like
the
cascading
levels
of
these
permissions,
we
would
be
able
to
establish
a
baseline
for
every
operation,
like
what's
the
baseline
permission
that
you
need
for
each
operation
and
at
the
same
time,
for
example,
if
we
need
to
bring
in
a
new
operation
and
fit
it
in
an
hierarchy,
we'll
get
an
idea
about
what
are
the
preconditions
that
should
come
checked
for
this
operation.
C
So
that
way,
our
future
decisions
will
be
so
much
more
easier,
especially
for
ux
designers,
to
make
a
case
of
what
should
and
should
not
be
allowed.
It
would
be
like
we
would
be
able
to
make
much
more
rational
decisions
around
things.
A
Now
I'm
going
to
open
with
my
sidebar
here,
I
love
that
there
is
a
vhs
emoji.
I
didn't
know
that,
but
also
I'm
really
glad
vitika
that
you
have
any
discussions
on
how
to
set
up
this
process
and
yeah
how
and
why
you're
documenting
this
before
jumping
into
the
mapping,
because
that
I
think
that
was
my
gut
feeling.
It's
like
okay,
this
this
is
too
complicated.
It
looks
like
something.
A
Off
not
only
a
lot
of
time,
but
a
lot
of
effort,
so
I
would
say
you
know,
since
you're
ready,
you
have
the
discussions
with
fabio
and
looking
at
the
preconditions
via
a
pilot.
You
know,
rather
than
I'm
going
to
do
everything
for
ci
or
for
whatever
just
do
a
pilot
and
see
how
that
looks
in
a
very
small
scope
and
then
how
how
you
can
progress.
C
Right
so
I
think
nadia
and
I
discussed
yesterday
that
we
would
be
running
a
pilot
with
the
pipeline
index
page
just
to
begin
with,
and
I
also
had
a
conversation
with
jackie
just
to
state
that
we
shouldn't
be
time
boxing
this
exercise,
because
it's
it's
possible
that
this
is
going.
This
might
take
a
lot
of
time,
but
at
the
same
time
this
is
not
blocking
any
of
our
ongoing
efforts,
so,
like
we
can
take.
This
is
something
that
could
run
on
the
side.
C
B
Yeah,
I
think
the
current
process
sounds
good
and
also
once
we
have
a
better
idea
for
exactly
how
we're
going
to
break
it
down.
B
I
think
it
could
be
useful
to
create
issues
separate
issues
for
each
part
or
like
for
the
pilot
that
you
mentioned
just
for
the
pipeline
index
page
just
so.
The
scope
is
clear
for
what
is
the
first
kind
of
piece
of
it
that
needs
to
be
addressed,
so
that
will
make
it
easier
for
everyone
to
see
how
much
effort
it
is
because,
looking
at
the
whole
thing,
it's
big
and
scary,
and
it's
difficult
to
understand
like
where
you
want
to
get
started.
B
And
another
thing
I
think,
once
we
have
the
pilot,
it
would
be
really
good
to
document
the
process,
so
others
can
also
follow
it.
So
it
doesn't
have
to
be
something
that
we're
doing
alone
even
on
a
cicd
team,
but
it
should
be
like
a
process
that
other
can
replicate
and
extend
it
and
document
it
in
a
way
that
is
like
standardized.
C
Yeah
right,
that's
that's
the
plan
and
I'm
trying
to
that's
why
I'm
trying
to
keep
it
like
arrive
at
a
process
which
is
very
easy
to
follow,
because
each
time
going
through
this
whole
circle,
I
don't
think
it
would
be
worth
it.
A
Yeah-
and
I
think
a
good
reference
in
general
is
a
what
the
foundations
team,
what
they
always
do,
that
they're
so
very
detailed
with
the
process
right.
So
you
get
an
issue
assigned
to
you.
There's
like
this
checkboxes
and
the
steps
like
that
that
you
need
to
do.
I
think
that's
also
going
to
be
once
you
go
through
this
you're
going
to
have
that
idea
and
then
figure
out
how
to
break
that
down
so
that
people
just
follow
it.
You
know
with
ease
and
they
can
be
yeah.
A
A
We
are
almost
at
time
or
maybe
we
are
at
time,
so
I'm
gonna
power
through
the
next
couple
of
items
for
that
team,
runner
so
for
every
package
so
for
package.
First,
we're
gonna
continue
validating
the
jobs
to
be
done
for
package.
We
have
two
jobs
to
be
done.
Two
categories,
sorry
and
nadia
is
gonna,
be
helping
us
with
that.
So
thank
you.
Nadia
shout
out
to
nadia
for
helping
us
in
q3
until
the
new
designer
joins
in
september,
but
by
the
time
they're
on
board
at
the
quarter.
A
It's
already
over,
so
nadia
will
be
working
on
that,
and
also
for
runner,
shout
out
to
vita
for
testing
runner,
shout
outs
to
vidiq
for
helping
us
with
the
research
and
project
quality
summary
for
testing.
That
was.
C
A
And
I
know
that
you're
working
on
next
steps-
so
I'm
gonna,
follow
up
on
this
with
you,
so
that
can
also
transition
this
out
to
vitica
at
some
point.
But
thanks
again
for
your
help
and
it
was
fun
and
small
updates
on
testing
merge
requests
we
just
redesigned.
So
this
is
part
of
the
it's
gonna,
be
a
q3
kr,
but
it's
it's
a
follow-up
from
the
q2
kr
on
improvement,
stability,
improvement
to
the
merger
quest
the
foundation
team's
investigating
how
investing
in
how
to
execute
these
improvements.
A
As
in
what
is
the
process,
what
needs
to
be
changed?
Who
does
what?
But
the
thermo?
This
is
happening
at
this
quarter
and
I'm
still
the
dri
while
genome
boards
and
then
gina
would
take
over
and
possibly
help
with
the
with
these
improvements
and
for
runner,
also,
enterprise
management.
It's
going
to
be
still
a
big
thing
for
us,
but
we
didn't
have
ux
capacity
to
focus
on
it
in
the
last
couple
of
months,
so
the
admin
view
for
runner.
A
It's
a
very
exciting
problem,
there's
so
many
issues,
there's
so
many
jobs
and
scenarios
that
we
have
to
address
and
I'll
be
working.
Also
to
transition
this
out
to
gina
and
help
create
the
design,
the
road
map,
with
the
end
so
similar
to
what
the
night
of
it
does
like
this
amount
of
problems.
How
do
we
break
this
down
the
mvc
and
build
incrementally
to
make
improvements
to
the
admin
page?
A
If
you
have
any
interest
or
any
questions,
please
just
check
out
the
the
issues,
and
I
know
that
we
are
kind.
We
have
a
couple
of
fun
stuff
and
comments.
So
thank
you
for
sharing
the
the
audiobooks
recommendations
and
I
don't
want
to
keep
you,
but
if
you
want
to,
if
you
want
to
go
over
these
items,
just
please
pick
now
or
forever
hold
your
your
comments
on
items.
B
Please
try
victory
and
have
your
mind
blown
it's
like
a
3d
design
tool
that
is
very
similar
to
figment
very
intuitive
if
you've
ever
tried,
learning,
3d
design
and
ever
tried
like
c
cinema
4d
or
things
like
that,
I've
tried
and
never
progressed
just
because
of
how
complex
and
difficult
it
is
to
get
started.
But
with
vectory
you
just
if
you
use
figma,
you
just
instantly
know
how
to
use
it
and
it
has
lots
of
pre-built
3d
textures
and
things
like
that
and
live
rendering.
So
you
guys
the
future
is
here.
B
C
So
from
me
the
update
is
I'll
again
be
speaking
at
the
cc
summit,
but
this
time
around
the
topic
is
a
little
different.
It's
something
that
I
recently
took
interest
in
it's
yeah
and
it's
about
inter-ledger
protocol.
It's
a
web
native
payment
method
which
is
agnostic
of
any
subscription
plans,
any
platforms.
So
let's
say,
if
you
are,
I
we
have
a
website
and
we
add
content
to
our
website.
C
So
we
can
totally
leverage
the
traffic
that
our
content
brings
in
to
our
platform
and
we
don't
really
have
to
abide
by
any
rules
and
any
like
by
the
rules
that's
created
by
the
very
established
platforms
like
youtube
or
medium.
Let's
say
so.
We
can
be
independent
at
our
own
conditions.
So
that's
the
proposal
that
I
mean
the
system
is
already
in
place,
I'm
just
trying
to
like
look
at
more
creative
ways
of
implementing
it.
C
If
anybody
is
interested
in
reading
books,
which
kind
of
touch
upon
play
theory,
it
can
be
in
any
tangent,
so
there's
a
whole
series
of
books
by
mit
around
playful
thinking,
and
I
have
read
two
out
of
those
and
they
are
very
interesting,
but
you
can
like
definitely
make
your
pick
depending
on
whatever
interests
you.
A
It's
awesome,
thank
you
very
good,
viticus
audiobooks,
a
good
resource
for
books
or
anything
in
between,
but
now
I
I'm
I
have
to
go
to
eupd
for
audiobooks,
because,
okay,
if
you
have,
if
you
you
know,
if
your
title
is
available
on
audiobook
put
it
there
on
the
side,
then
okay
definitely
yeah
awesome
right
right,
then
I
think
that's
it
I'll
see!
A
You
see
you
next
time
and
if
I
don't
see
you
by
by
thursday,
I'm
off
by
the
way,
I'm
on
friday
have
a
lovely
rest
of
the
week
and
enjoy
yourself
enjoy
the
weekend.