►
From YouTube: CI/CD UX Meeting - 2021-06-02
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
So
this
is
the
cicd
ux
meeting
for
what
is
today
during
his
second,
it's
great
june.
I'm
gonna
go
and
read
a
couple
of
fyi
announcements,
so
the
first
one
is
that
okay,
ours
they're
still
here
they're
happening,
and
I
sent
you
all
a
reminder
to
complete
the
training.
So
we
have
the
linkedin
trainings
for
wonder,
diversity
and
inclusion's,
not
only
training,
it's
an
internal
training
and
the
other
one
about
how
to
make
the
user
experience
happen.
A
As
a
team,
I
recommend
you
use
focus
friday
to
do
that
and
of
course
you
have
any
questions
or
anything
that
needs
to
be
re-prioritized
or
shipped
around
just
yeah
reach
out,
and
we
can.
We
can
talk
about
if
you're
not
able
to
prioritize
that
this
week,
I'll
jump
to
the
next
one.
The
foundation
survey,
not
sure
if
everyone
answered
a
few
or
not
presents
yesterday,
also
in
the
ux
call,
so
the
folks
are
gathering
more
feedback
on
how
the
create
build
style.
A
A
I
think
it's
you
so
forward
to
give
that
feedback
so
that
they
have
an
idea
of
how
that
looks
like
for
designers
that
yeah
don't
have
as
much
experience
with
the
germans
last
one
excuse
me.
A
We
now
are
part
of
the
product
manager
interview
process,
so
I
created
that
merge
request,
adding
product
designers
to
be
able
to
interview
pms,
together
with
the
em
interview,
so
we'll
be
a
duo,
a
shared
interview
with
engineering
managers
and
moving
forward
we'll
be
able
to
be
part
of
the
conversation
as
well,
so
in
the
same
way
as
pm's
to
they
interview
product
designers,
we're
going
to
interview
them.
If
you
haven't
completed
interview
training,
yet
I
think
we're
all
either
currently
in
process
or
you
have
to
start.
A
Please
do
so
try
to
prioritize
because,
as
you
know,
I'm
interviewing
folks,
but
also
what
we've
decided
is
that
if
you
haven't
completed
interview
training,
you
will
shadow
your
manager
or
another
designer
that
has
completed,
and
I
will
count.
Excuse
me
as
part
of
your
interview,
training
process,
so
pause
for
all
the
announcements.
If
anyone
has
any
questions
or
any
comments,.
B
A
Then
I
think
you
can
jump
to
the
stage
group
announcement.
So
then
you
have
the
the
first
first
points
agenda.
C
Yes,
yeah,
I
just
added
I
I
shared
in
the
onslack
already,
but
I
wanted
to
to
call
out
the
feature,
mapping
that
I
did
for
release.
That
was
really
good
to
me
because
I
only
made
it
I
think
last
week,
but
it
already
helped
me
have
a
much
stronger
visibility
of
all
the
pages
and
all
the
usability
issues
that
we
have
on
the
release
pages,
especially
for
me,
working
on
environments
having
a
map
of
everything
environment
related
has
been
super
helpful,
so
yeah
thanks
for
for
the
nice
reaction
to
it.
C
I'll
definitely
add
it
to
the
handbook
soon,
still
not
sure
how,
because
this
format
with
fake
jam
is
also
super
useful.
So,
ideally,
I
would
keep
both
but
yeah
feel
free
to
leave
any
feedback
with
that
said,
I'm
working
on
some
improvements
from
the
environments
page,
so
I'm
gonna
quickly
share
my
screen
to
show
what
I'm
going
through,
and
maybe
you
can
also
give
me
some
feedback
on
this
right.
So
the
current
issue,
I'm
working
on,
is
an
issue
to
add
a
new
information
to
the
environment,
stable
called
deployment
tier.
C
The
problem
is
the
environment.
Environment.
Stable
is
not
in
good
shape,
right
now
to
the
point
where,
if
we
add
any
other
field,
it
just
breaks,
it
no
longer
has
the
space
to
add
anything
else.
So
the
mvc
proposal,
I'm
going
to
forward
I'm
going
to
share
on
the
issue,
is
just
add,
like
environment
and
tier
here,
and
then
a
label
underneath
which
is
not
great,
but
we
currently
have
this
feature
and
it's
not
visible.
So
I
think
it's
a
valid
compromise
for
now.
C
The
solution
I
want
to
get
through
requires
a
small
refactor
of
the
environment.
Stable,
so
essentially,
first
thing,
that's
very
visually
broken
are
the
environment
folders
right
like
even
even
on
an
empty
state,
it
looks
really
bad
and
I
figure
out
there's
one
css
class
that
you
change
and
just
fixes
it.
So
that
will
be
the
first
step.
The
next
step
is
this
nested
nested
overview
within
the
folders.
C
So
basically,
the
proposal
is
to
instead
of
having
it
nested
by
space
we
nested
by
color,
with
this
gray
background
and
then
now
in
order
to
be
able
to
add
a
new
a
new
field.
We
just
make
the
table
full
screen,
because
at
this
point
it's
already
breaking
in
a
really
large
16
inch
screen.
So
imagine
for
users
with
with
much
smaller
screens
that
have
the
sidebar
open,
so
we
make
it
full
screen.
C
We
move
the
show
out
button
here
to
the
top,
so
it's
it's
also
something
else.
That's
breaking
the
layout,
because
it's
something
centered
on
a
table
doesn't
make
a
lot
of
sense.
So
we
move
it
here
to
the
top
and
then
we're
able
to
add
the
deploy
the
deployment
here
very
easily
and
it's
much
more
cleaner
visually.
C
I
I
was
just
wrapping
this
up
this
morning
I
created
a
couple
of
issues
already
which,
with
each
one
of
these
changes,
but
to
be
honest,
most
of
these
are
prototyped
in
the
browser
just
changing
css
classes.
So
I
imagine
a
frontend
developer
would
be
able
to
do
this
in
one.
C
Mr
there's,
a
bunch
of
other
environments
fixes
that
are
already
in
line,
but
in
my
opinion
this
yields
so
much
gain
with
so
little
effort
that
honestly,
like
it
should
just
shoot
to
the
top
of
the
list,
because
it's
very
easy
to
implement
and
that's
that's
me.
A
I
have
a
couple
of
questions
danielle.
First,
I
wanted
to
kind
of
listen.
What
is
the
goal
of
this
cleanup?
What
is
the
that
you
that
you
want
to
achieve
with?
I
think
how
did
you
call
the
first
one
didn't
take
note
of
that,
but
yeah
the
tire
environment,
tire
yeah.
C
They
just
see
the
names
and
there
are
use
cases
of
customers
that
have
environments
with
names
that
are
automatically
created,
so
just
they're,
just
long
ids
that
don't
make
any
sense,
so
they
would
need
this
feature
to
to
be
able
to
actually
see
which
environments
are
production
or
keyway
or
or
development
ones,
and
yet
today,
there's
no
space
to
add
this
to
the
table
because
it
just
breaks
it.
So
we
can
do
this,
just
add
a
badge
underneath
the
name
that
works,
but
the
table
is
still
very
hard
to
read.
A
Not
can
you
understand
now,
then
then.
I
think
it
makes
sense
to
my
next
couple
of
comments
so
one
I
don't
think
this
is
even
a
table,
probably
if
you,
if
they
change
that,
but
in
the
markup,
I'm
not
sure
which
components
they
are
using.
A
A
So,
for
example,
some
of
the
pages
you
cannot.
You
cannot
remove
that
the
gap
right
the
gutter
say
of
the
layout,
because
that's
how
it
will
show
in
every
page,
so
not
only
this
one.
So
just
keep
that
in
mind
that
you'll
still
be
limited.
If
the
user
says,
I
want
to
see
the
girls
and
if
not,
then
everything
is
full
screen.
Have
you
checked
that.
C
No,
I
didn't
know
there
was
that
setting
thanks
for
bringing
that
up.
I
will
check
that
yeah.
A
Yeah
check
that,
because
I
think
that's
in
terms
of
layout,
that's
the
most
impactful
thing,
for
you
know
what
I
can
see.
C
To
be
honest,
like
a
conversation
had
with
reid
like
already
some
time
ago
like
we
both
agree
that
this
likely
shouldn't
be
a
table.
We
should
have
a
better
way
to
display
this
information,
because
the
table
also
doesn't
doesn't
prioritize
anything
right.
Everything
has
the
same
importance
here
and
most
of
the
information
is
clipped,
so
you
have
to
hover
over
to
see
the
full
names
so
so
the
layout
is
already
breaking.
Even
if
it's
not
visually
breaking
like
it's,
not
it
doesn't
hold
this
much
content
anymore,
but
that's
quite
a
big
change.
A
A
I'm
gonna
do
some
research,
because
I
know
that
someone
did
some
redesign
of
this
in
the
past
and
it
was
not
implemented.
If
you
were
not
none
of
you
folks
here
in
the
call
like
viticarnadia,
I
think
he
was
someone
working
in
the
maybe
in
the
planting.
I've
seen
something
like
that.
So
I'll
try
to
find
here
and
give
you
as
a
reference
thanks
yeah,
because.
B
Not
sure,
but
it
could
have
been
emilia
for
the
incidents
table
or
something
like
that,
but
maybe
not
maybe
I'm
just
dreaming
it
up,
so
just
to
guess
yeah
yeah.
This
is
super
cool
danielle.
Thanks
for
sharing.
I
I
was
gonna,
ask
a
question
like
have
you
considered
redesigning
this?
So
it's
not
a
table,
so
we
can
actually
give
more
weight
to
some
things
that
are
important
and
maybe
even
hide
some
things
or
like
make
it
possible
to
expand
additional
information
or
whatever.
C
Yeah,
there's
also
a
really
interesting
discussion
going
on
about
how
how
we
prioritize
the
concept
of
environments
versus
the
concept
of
deployments,
so
it
might
be
the
case
that
would
not
only
change
how
it's
visually
represented,
but
also
what
we
are
giving
more
weight
in
the
ui
and
how
we
are
communicating
things.
So
it's
definitely
a
higher
level
approach,
although
I
don't,
I
want
to
be
giant.
Of
course
it's
not
that
big,
but
it's
it
will
benefit
from
some
more
long-term
thinking.
D
Okay,
I,
as
long
as
you're
planning,
to
go
with
a
table
like
layout.
I
wanted
to
make
you
aware
of
this
refactoring
work
that
patent
was
involved
in
in
ci,
so
the
jobs
index
page
and
pipeline
index
page
table
that
you
see
patent
has
refactored
those
and
in
the
process
we
have
also
collaboratively
like
redesigned
it,
so
he
has
made.
I
mean
from
a
front
in
engineer
perspective.
D
He
has
also
made
some
very
thoughtful
decisions
in
the
process
and
I
have
kind
of
highlighted
those
in
the
issue
that
I
have
talked
so
maybe
you
could
take
some
inspirations
from
there
and
I
see
that
that
you're
also
running
into
a
problem
which
is
very
similar
to
ours,
which
is
how
different
content
is
truncated
and
broken
up
into
parts
in
the
table,
like
view
and
the
number
of
action
buttons
at
the
end
I
saw
like
there
are
about
six
actions
in
the
screen
shot
that
he
was
showing
so
in
ci
what
we
are
doing,
yeah
come
again.
D
D
Right
so
I
also
kind
of
anticipated
a
similar
problem
and
that's
when
I
took
a
break
and
I
involved
jeremy
from
foundations,
and
I
started
working
on
a
different
proposal
for
action
buttons,
specifically
in
the
table,
which
was,
let's
put
the
most,
I
mean
the
most
interacted
with
actions,
upfront
and
everything
else
in
a
kebab
menu
that
could
be
accessed
from
a
drop
down.
So
maybe
you
can
try
that
approach
as
well.
It's
all
mentioned
in
this
issue
that
I've
tagged.
A
I
would
say
the
best
really
way
for
you
to
find
that
information
just
asking
slack
and
then
share
your
problem
and
see
if
someone
has
worked
in
this
in
the
past,
because
I'm
sure
that
there
are
some
investigation
and
even
some
research
done
there
on
how
to
improve
this
component,
but
also
the
usability
and
the
discoverability
of
all
these
actions
so
checking
with
the
with
the
folks
before
you.
You
move
forward
with
proposals
and
changes.
I
think
that's
a
good
approach.
B
Yeah,
so
I
will
just
quickly
go
over
those
issues
and
share
my
screen,
probably
as
well.
B
All
right,
so
one
big
thing:
I've
been
working
on
for
the
past
two
weeks
was
the
autodevops
design
sprint
and
we
collaborated
across
several
different
stages:
configure
secure
pipeline
authoring
and
in
the
design
sprint
there
were
product
designers,
engineers
and
product
managers
as
well,
and
together
we
tried
to
work
out
the
like
work
out.
What
are
the
main
problems
with
autodevops?
B
What?
What
is
the
vision
that
we
want
to
move
towards?
Because
because
we
kind
of
have
this
vision,
that
autodevops
is
this
magic
that
allows
you
to
automatically
enable
everything
that
you
need
for
like
a
good,
auto,
devops,
good,
devops
workflow,
so
it
kind
of
automates
for
you
setting
up
security
and
tests
and
delivery
and
whatnot,
but
in
reality
it
doesn't
really
happen.
So
it
doesn't
really
work.
B
It
works
for
some
specific
cases,
but
it
very
easily
breaks
it's
kind
of
a
pretty
fragile
solution,
but
it
the
idea
is
very
powerful.
So
let's
have
this
feature
that
makes
it
easy
to
have
all
of
the
amazing
gitlab
features
on
by
default.
So
you
just
create
a
project
and
out
of
the
box,
you
have
the
whole
cicd
pipeline
working,
basically,
which
enables
all
of
gitlab's
magic
so
like
before
this
design
sprint.
When
the
whole
discussions
around
autodevops
started.
B
I
I
was
just
convinced
that
autodevops
needs
to
needs
to
work
together
with
ci
cd,
to
offer
like
an
easy
to
understand
package
of
tools,
basically
for
automation,
for
workflow
automation,
because
right
now
we
have
auto
devops
and
we
have
ci
cd
and
they're
completely
disconnected
as
far
as
user
experience
is
concerned,
and
but
they're
competing
tools,
they're
solving
the
same
job
to
be
done
and
for
some
reason,
the
user
experience
is
just
completely
disconnected
where
we
don't
consider
each
other
much
when
we
are
kind
of
moving
forward
with
new
features
and
so
on
so
feel
free
to
look
through
this
epic
and
read
through
this
summary,
because
and
also
have
I
added
the
video
here.
B
No,
but
I
will
add
the
video
I
will
share
it
in
the
ci
cd
channel,
because
we
talked
a
lot
about
ci
and
deployments
and
things
that
you
would
be
probably
interested
in
learning
about
like
how
what
is
their
vision,
because
they
configure
with
other
devops.
Now
I
think
they're
thinking
on
focusing
on
deployments
primarily
and
using
other
devops
as
a
way
to
like
automate
your
deployment
setup.
B
That's
one
thing
that
would
probably
be
interested
interesting
from
the
release
point
of
view
and
then
for
ci.
We
generally
talked
about
how
to
align
the
user
experience
for
auto
devops
and
ci
cd,
because
essentially
these
are
pipelines.
So
we
have
different
kinds
of
pipelines
in
gitlab.
You
can
have
it
on
a
devops
pipeline
or
you
can
have
a
ci
cd
pipeline
that
you
just
defined
manually
in
your
yaml
and
now
there's
also
compliance
pipelines
which
is
like
they
don't
have
a
separate
ui
or
a
place
to
create
that
pipeline.
B
But
it
is
a
different
kind
of
type
of
pipeline,
so
we
weren't
able
to
create
a
prototype
of
autodev
solution
in
the
end,
that
was
the
initial
goal
to
create
a
prototype
to
test
with
users,
but
the
main
outcome
was
that
we,
at
least
for
me
from
like
my
point
of
view
from
pipeline.
B
We
aligned
on
having
like
a
single
experience
like
smooth
experience
in
the
ui
for
onboarding,
for
like
github
automation,
onboarding.
So
eventually,
we
would
like
to
have
one
way
for
you
to
set
up
your
project
with
automation
and
then
you
would
be
able
to
choose
like
do.
I
want
something
super
automatic
like
this
and
you
select
on
a
devops
or
you
can
build
out
your
own
custom
pipeline
and
in
the
ui.
B
So
right
now,
when
you
have
autodevops
enabled
you
just
see
the
empty
state
for
the
pipeline
editor
and
it
says,
like
hey,
create
ci
cd,
so
create
the
csd
configuration,
but
it
doesn't
really
make
sense.
So
it
makes
sense
to
provide
a
way
to
create
a
csc
config
if
you
want
to
switch
from
autodevops
to
running
something
fully
custom,
but
it's
a
pipeline
and
it's
a
configuration
of
a
pipeline
even
if
it's
automatic
it
needs
to
be
explicit
and
like
users
need
to
be
aware.
B
Okay,
this
is
the
thing
that
is
actually
running.
If
you
don't
want
to
edit
it
that's
great
if
you
want
everything
to
work
automatically,
but
we
need
to
at
least
show
it
so
like
things
like
that
and
from
ci
perspective,
since
we
were
talking
about
making
autodevops
pipelines
kind
of
show
up
in
the
ui
and
run,
and
you
know
just
as
any
other
pipelines.
So
that's
also
some
kind
of
consideration
for
the
ci
team.
B
So,
like
the
main
thing
we
agreed
on,
let's
keep
each
other
in
the
loop
on
literally
everything
that
we're
doing
like
any
new
features,
because
there
is
likelihood
that
there
will
be
some
overlap
or
maybe
there
is
some
potential
synergy
for
us
so
yeah.
That
was
a
big
one
and
yeah,
and
I
know
we
don't
have
a
lot
of
time.
So
I
want
to
leave
some
some
more
time,
but
I'll
just
keep
the
second
point,
and
I
wanted
to
highlight
the
collaboration
with
the
growth
team
that
we're
doing
right
now.
B
That,
hopefully,
will
make
it
make
like
cinboarding
easier
as
well.
So
we
have
this
widget
in
a
mars
where
we're
suggesting
to
try
github
pipelines
and
right
now,
it's
broken
and
an
easy
fix
would
be
to
just
redirect
users
to
the
pipeline
editor
and
we're
working
out
like
the
best
copy,
with
the
growth
team
and
so
on.
So
a
lot
of
interesting
things
generally
are
happening
with
cn
boarding
and
next
we're
planning
to
create
a
guided
walkthrough.
B
So
as
an
mvc,
you
would
click
on
the
cta
in
the
widget,
and
it
would
will
just
take
you
to
the
pipeline
editor
and
then,
as
the
next
step
will
be
collaborating
with
the
growth
team
on
creating
a
walkthrough
with
a
little
powers
throughout
the
ui.
So
we
can
guide
the
user
around
the
pipeline.
Editor
ui
because
it's
starting
to
become
a
bit
like
feature-rich
to
the
point
where
we
feel
like
it
could
be
helpful
to
provide
some
extra
guidance
during
initial
onboarding.
B
Some
questions
I
see
here
around
autodevops.
D
Yeah,
I
I
did
not
know
I
mean
this
is
the
first
time,
I'm
realizing
that
the
pipeline
doesn't
show
up
anywhere
and
what
you
may,
what
you
just
said.
It
makes
absolute
sense
that
it
should
appear
in
the
place
of
the
regular
yaml
file
and
it
like
it's
just
that
it
was
populated
automatically
like
like
the
system,
did
it
for
you,
but
you
should
be
able
to
go
ahead,
make
modifications
or
even
just
replace
it
with
something
else.
D
B
Yeah,
it's
it's
like
a
difficult
problem,
because
it's
not
as
easy
as
just
showing
it
there,
because
it's
kind
of
a
bit
of
a
different
implementation.
B
So
it's
a
pipeline,
but
it's
it
has
different
processing,
but
it
is
possible
still
so
we're
starting
those
discussions
right
now
and
I
think
it
does
show
up
in
the
ui.
But
I
know
for
sure
that
an
autonomous
pipeline
shows
up
in
the
pipelines
page
like
in
the
pipelines
list,
but
I
don't
know
how
it
shows
up
in
the
pipeline
graph
like
what
the
detail
view
looks
like
and
from
the
pipeline
authoring
perspective,
it's
a
complete
black
box
is
no
way
for
you
to
like
well.
B
Go
somewhere
in
you
can
go
in
the
repo
and
chase
down
those
those
files,
but
and
then
it
will
break
everything
most
likely
it's
very
difficult
to
customize.
So
it's
going
to
be
a
big
project
but
yeah.
I
just
wanted
to
make
sure
that
you
all
are
aware
because,
as
they
start
making
changes
to
other
devops,
we
will
need
to
think
about
like
how
the
facts
are
on
stage.
Work.
B
Okay,
thanks.
C
B
C
This
nadia-
I
just
want
to
make
a
quick
comment
that
auto
devops
is
essentially
a
pipeline
that
is
configured
automatically
and
it's
not
very
visible
for
the
user
right.
B
Yeah-
and
I
think
it
even
is
enabled
by
default
for
some
projects
and
there's
yeah,
there's
not
a
lot
of
visibility
into
what
it
does,
but
I
think
it
handles
deployments
or
attempts
to
handle
deployments
in
some
way.
C
Right
does
in
terms
of
automation.
I
I
remembered
the
the
pipeline
templates
and
packages
that
you
were
working
on,
like
on
small
building
blocks,
that
you
can
use
to
build
your
ci
pipeline
and
and
thinking
automation
between
a
spectrum
from
one
to
one
zero
to
100.
It
looks
like
auto
devops
tried
to
go
to
100,
but
maybe
the
solution
you
were
working
on
is
like
somewhere
in
between.
So
maybe
maybe
the
ideal
state
is
actually
somewhere
in
between
where
the
user
has
some
control,
and
we
also
offer
automated
automation.
C
B
Yeah,
so
so
that
was
kind
of
the
agreement
at
the
end
of
the
sprint
as
well.
That
we
probably
would
need
to
reduce
the
scope
a
little
bit
and
not
attempt
to
make
it
work
for
everything,
and
I
think
that's
why
they're
thinking
that
maybe
deployments
will
be
it
because
it
it
seems
to
provide
a
lot
of
value,
and
it
would
be
easier
for
us
to
automate
that
as
well.
B
B
A
Have
two
minutes
I'll
give
it
to
you
the
floor,
because
you
already
answered
my
question
so
please
please,
two
minutes
quietly.
D
All
right
so
there's
nothing
big
that
I
want
to
share
today,
because
the
large
effort
of
the
ux
scorecard
exercise
around
variables,
it's
still
underway.
I've
added
the
link
to
the
epic,
which
has
the
dovetail
link
the
discussion
guide,
link
and
everything
else.
So
in
case
you
want
to
just
go
ahead
and
have
a
look
at
the
progress
you
can
and
another
small
effort.
A
various
qualifier
that
I
want
to
talk
about
is
a
collaboration
that
happened
on
the
fly.
D
So
peyton
was
working
on
the
refactoring
of
the
jobs
table
and
he
created
this
issue
for
ux
feedback.
We
were
already
aligned
because
we
have
been
a
part
of
many
discussions
in
the
past
regarding
what
problems
we
were
facing
regarding
the
related
to
the
table,
the
pipeline
and
jobs
table
on
the
python
and
jobs
index
pages.
So
this
was
pretty
easy
for
us
and
it
happened
so
that
I
quickly
like
reviewed
it.
D
I
gave
my
inputs
created
two
issues
which
were
closed
the
same
day
I
mean
they
were
worked
on
the
same
day
and
also
kind
of
implemented,
so
that
was
very
interesting
and
here's
a
slack
link
where
peyton
has
posted
a
small,
gif
or
video.
I
don't
remember
exactly
that
shows
like
how
the
new
implementation
looks
now,
and
it
also
shows
a
glimpse
of
a
skeleton
loader
that
we
have
added
to
the
table.
That
would
appear.
B
D
The
plan
was
to
wind
up
interviews
sometime
this
week
and
mostly
that's
going
to
happen.
There
were
a
couple
of
delays
and
responses
and
we
are
trying
to
chase
the
participants,
so
they
are
scheduled
for
this
friday,
but
this
I
mean
the
deadline
is,
I
think,
for
the
next
milestone,
but
I
mean,
if
I
keep
on
continuing
to
work
on
this,
this
should
be
done
by
the
coming
week
like
we
would
be
ready
with
the
recommendations,
the
insights
and
the
recommendations.
B
Okay,
no
rush,
I'm
just
curious
like
because
we're
starting
to
yeah
to
think
about
variables
yeah,
but
I
talked
to
dog
about
it
by
the
way,
and
it's
not
going
to
be
like
an
immediate
priority
for
us
to
start
pumping
out
new
improvements.
B
I
think
we're
just
gonna
focus
for
the
first
milestone
or
two
for
sure
on
the
existing
issues
that
are
like
known,
yeah
bug,
fixes
and
some
improvements
that
are
more
straightforward
and
we
really
want
to
take
the
time
to
like
first
consume
the
insights
that
you
can
create
with
this
scorecard
and
then
also
we're
planning
to
do
our
own
problem.
Validation.
First,
to
learn
about
it
because
at
this
point
feels
like
we're
not
very
knowledgeable
about
variables.
Right.
D
So
if
you
go
to
this,
maybe
it's
not
a
part
of
this
particular
epic,
but
there's
a
there's,
an
issue
separately.
That's
about
proposing
recommendations
based
on
the
learnings
from
this
scorecard
exercise,
so
that
would
involve
a
pipeline
execution
team.
That
is
jackie
and
I
like
creating
some
issues
beforehand
like
for
the
pipeline.
D
A
With
that
we
can
wrap
up
today
almost
a
time,
because
I
think
that's
the
first
and
let's
say
for
all
the
conversation
come
to
the
conversation.
I
think
because
I
think
we
have
way
too
many
good
things
going
on
in
our
team.
So
that's
awesome.
Thanks
for
sharing
and
I'll
see
you
around
bye,
everyone.