►
From YouTube: All Ops UX Design review 2020-06-04
Description
03:45 - Design an interface focused on enabling users to add the ability to connect and setup remote and virtual repositories by Iain Camacho
A
A
That's
amazing,
so
Justin
I
mean
it
would
be
actually
curious
to
hear.
How
do
you
do
the
design
reviews
in
your
team,
but
in
ours
it's
yeah.
We
usually
have
like
two
designers,
one
or
two
designers
per
session,
bringing
some
of
the
design
work,
that
research
work,
something
interesting
visual
to
show
or
something
that
we
learned,
something
that
we
want
to
discuss
or
maybe
get
some
ideas
feedback
on,
and
we
usually
like
have
those
discussions
during
this
session.
B
So
we
have
three
15-minute
slots
available,
but
to
be
honest
with
you
in
that
many
people
sign
up
to
do
design
reviews
in
our
meetings.
So
we
end
up
talking
a
bit
more
about
announcements
or
any
concerns,
or
you
know
you
know
feedback
from
anyone
else
stuff
like
that.
So
that's
why
I
thought
this
might
be
a
good
idea.
Cuz.
It
might
force
people
to
actually
share
their
work.
It's.
A
Cuz
I
thought
he
had
a
really
interesting
thing,
but
he's
in
Japan
this
day.
So
hey
it's
like
12
11
o'clock
p.m.
right
now
so
he's
it
bad,
but
yeah
I,
don't
know
it
doesn't
even
have
any
questions
about
the
goals
for
the
sessions
or
about
how
are
we
going
to
be
doing
them
before
we're
gonna
jump
into
the
actual
videos.
A
C
C
So
what
I
wanted
to
share
with
everyone
and
get
your
feedback
on
is
the
remote
and
virtual
registries
that
we're
trying
to
create
on
the
package
side.
This
is
a
new
evolution
on
the
category
we
already
have,
and
it
will
provide
a
lot
of
features
that
will
make
us
much
more
competitive
with
some
of
our
direct
competitors
in
the
package
registry,
realm
I,
I
level,
I'm,
really
looking
for
that
initial
temperature
test
of.
Does
this
make
sense?
C
Does
this
match
get
lab
design
standards
we're
creating
a
lot
of
new
features
in
new
UI,
so
that
high
level
response
would
be
really
beneficial
for
a
quick
reminder,
the
packaged
stage
and
what
we
focus
on
is
taking
bundled
up
code
and
ready
to
deploy
assets
and
storing
them
and
then
allowing
them
to
be
deployed.
That
could
be
a
code
package
like
an
NPM
package
or
it
could
be
an
image.
Today's
conversation
focuses
on
the
dependency
proxy.
If
you
notice
it
says
minimal
right
now.
C
What
we
handle
is,
if
you
ask
us
for
an
NPM
package,
you
can
enable
a
feature
that,
if
we
don't
have
it
in
get
labs
registry,
we'll
go
check,
NPM
jas
org,
that's
a
really
foundational
level
feature
and
what
our
customers
need,
especially
the
larger
scale,
customers
there's
a
much
more
robust
mechanism
to
do
that
kind
of
fetching
of
packages.
So
this
will
hopefully
push
us
out
to
a
whole
new
level
for
the
dependency
proxy
initiative
goals.
C
C
A
lot
of
code
bases
right
now:
users
and
developers,
and
the
CI
CD
tools
have
to
know
which
packages
are
from
where
and
that
creates
a
really
cumbersome
experience
from
a
user
goal.
We
want
an
easy
way
to
manage
an
easy
to
made
a
tool
that
enables
safe
and
secure
use
of
internal
and
third-party
dependencies
in
a
codebase.
One
of
the
disadvantages
of
going
out
to
NPM
j/s
is
that
we
can't
do
say
security
scanning,
and
so
we
want
a
way
to
address
that
as
well.
C
So
the
simplest
way
to
break
down
the
current
user
problem
is
where
oh,
where
is
my
package
when
you
want
to
pull
down
a
package,
whether
it's
into
your
local
environment
or
through,
including
another
team's
package
that
they've
created
or
going
out
to
the
default?
It's
really
confusing
for
users
to
know
where
to
go,
and
it
means
that
their
local
setup
files
can
be
really
cumbersome
and
have
a
lot
of
exceptions
and
if
statements
and
it
kind
of,
doesn't
enable
users
to
find
things
quickly
and
most
organizations.
C
That's
really
not
what
you
want
your
engineers
devoting
their
time
to
is
finding
where
the
packages
they
just
want
to
include
it
and
forward
a
little
bit
of
history.
The
defensive
proxy
for
gillip
package
repositories
was
actually
opened
by
Dmitri
a
year
ago.
It
hasn't
really
been
touched.
We've
been
focusing
on
some
other
things,
and
so
now
it's
kind
of
come
back
to
life.
C
We've
been
speaking
to
our
customers,
especially
the
larger
scale
organizations
and
get
loud
not
having
a
robust
solution
around
this
area
has
been
keeping
them
from
really
utilizing
the
gitlab
registry
offering
and
making
it
beneficial
for
them
to
use
other
services
and
third-party
registry
managers.
Obviously
we
want
to
bring
everyone
into
the
one
DevOps
environment
last
milestone.
We
conducted
problem
validation,
research
around
this
area,
Tim
did
a
bunch
of
interviews
and
I
synthesize
the
data,
and
we
discovered
kind
of
what
the
actual
problem
was
in
ways
that
we
could
solve
it
currently
running.
C
Right
now
is
the
investigation
issue.
We
shared
the
research
results
in
our
last
thing,
big
and
we
have
David,
who
is
a
back-end
engineer
coming
in
and
understanding
the
technical
ramifications
of
how
to
build
a
solution
like
this.
One
of
the
cool
parts
about
working
on
this
initiative
is
that
the
technical
investigation
is
happening
at
the
same
time,
I'm
doing
the
design
of
the
interface,
and
so
we've
been
able
to
go
back
and
forth
and
I
can
check
in
a
way
the
work
that.
C
The
questions
and
feedback
I'm
looking
for
from
everyone.
This
is
a
large-scale
improvement
for
the
package
registry
and
there's
a
lot
of
new
technology
and
terminology
and
concepts
and
utilities
I
really
want
to
make
sure
that,
at
a
high
level,
it
makes
sense
and
kind
of
resonates
with
the
way
that
gitlab
talks
about
things.
C
For
example,
we
have
a
dependency
proxy,
hosted
registry
or
remote
register
into
virtual
registry
and
all
of
those
combined
into
creating
the
solution,
so
I
want
to
make
sure
that
they
resonate
with
you,
know
fellow
designers
and
make
sure
they
make
sense,
and
the
latter
half
is
at
the
high
level.
I'll
show
a
couple
of
UI
screens
concepts
that
we
put
together
and
I
want
to
make
sure
that
they
embody
the
solution,
as
you
understand
it,
as
well
as
good
old-fashioned
design
feedback
really-
and
this
meme
says
this
gift
says
it
wonderfully.
C
C
Some
terminology,
the
dependency
proxy,
is
the
overarching
tool
that
allows
us
to
fetch
dependencies
from
multiple
resources,
whether
that
is
a
hosted
registry,
which
is
when
the
git
lab
has
or
remote
registry,
which
is
a
third
party
tool.
I
just
reviewed
this.
A
hosted
registry
is
currently
what
the
packaged
registry
offers.
So
we
have
PI
API
and
Conan
and
NPM
packages
you
can
create
them,
deploy
them
by
CI
and
store
them
in
the
registry.
B
C
Then
you
can
pull
them
later.
We
have
remote
registries
which
are
hosted
on
third
parties,
and
this
can
be
a
variety
of
third
parties.
It
could
be
the
native
package
manager,
so
for
NPM
this
goes
to
NPM
JSO
org,
or
this
could
be
on
s3
or
many
other
different
third-party
tools.
That
kind
of
manage
packages.
C
The
last
term
that
we're
kind
of
adding
or
introducing
around
this
is
the
virtual
registry.
This
is
the
connection
between
multiple
registries
using
a
single
API
point,
so
it
could
be
hosted
registries
wherever
on
gitlab
or
it
could
be
remote
on
a
third-party
tool,
and
each
virtual
registry
can
only
contain
one
package
type.
So
this
is
the
NPM
virtual
registry
or
a
maven
virtual
registry.
C
A
F
C
Cool
I
appreciate
everyone
following
along
I
know,
this
is
kind
of
tricky.
I
will
admit.
One
of
the
reasons
I
wanted
to
get
feedback
is
also
to
make
sure
that
I
understand
and
can
explain
what
we're
trying
to
do
before.
We
do
solution
validation
next
miles
down,
so
your
guinea
pigs
on
top
of
guinea
pigs.
Thank
you
all.
So.
A
C
So
we
are
going
to
do
solution.
Validation
next,
milestone,
we're
going
to
use
the
design
to
kind
of
explore
all
the
different
technical
aspects
of
this
and
make
sure
it
makes
sense
we're
using
a
combination
of
terminology.
Our
competitors
are
using
and
aligning
on
there's
some
deviation,
but
pretty
consistent
as
well
as
the
way
that
we
internally
have
talked
about
packages
and
stuff
like
that
and
the
registries
that
we
use.
So
it's
trying
to
be
a
balance
of
both
of
them.
C
E
C
Pressure
we,
when
we
implement
the
solution
and
start
actually
rolling
it
out.
One
of
the
things
we'd
like
to
do
is
for
the
documentation
to
be
ahead
of
our
development
a
little
bit.
So
users
can
start
to
see
it
and
understand
it.
I'm
working
with
Suzanne
on
putting
those
I,
Mars
together,
I
think
we're
going
to
do
the
solution,
validation,
first
and
then
move
on
to
that
next
stage.
E
D
C
So
far,
I
have
had
Suzanne
come
in
on
the
design
issue
and
constantly
asking
hey.
Does
this
make
sense?
Is
this
an
alignment?
Does
the
API
match,
etc
so
I'm
working
hard
to
make
sure
ever
everyone
is
using
the
same
terms
moving
forward.
It's
one
of
the
advantages
of
the
investigation
issue
happening
at
the
same
time
is
that
we
don't
necessarily
just
have
to
use
whatever
the
API
uses,
and
we
have
the
opportunity
to
all
come
together
to
discuss
the
different
terms
and
how
will
you
use
them
internally.
D
C
So
the
proposed
solution
is
at
a
very
high
level.
Basically,
what
I'm
showing
you
the
developer
will
want
to
pull
in
a
package
they
will
pull
in.
They
will
put
in
the
URL
for
a
virtual
repository
depending
on
the
package
type.
So
if
you
want
an
NPM
package,
you
go
to
your
organization's
NPM
virtual
registry.
C
If
you
want
up
ipi
package,
you
go
that
route
get
lab,
will
take
that
as
an
API
call
and
then
search
in
an
order
in
an
ordered
list
of
the
different
registries
until
it
finds
a
package
matching
that
type
and
then
returns
it
for
you.
So
the
dependency
proxy
is
the
overall
idea
of
all
the
different
ways
that
you
can
connect
to
different
packages,
and
then
the
virtual
registry
is
the
specific
API
you
call
and
the
order
of
which
you
look
at
the
different
registries.
C
So,
starting
at
the
high
level,
this
was
the
initial
screen
that
I
put
together
so
to
navigate
to
here.
You
would
look
at
your
organization's
group
page
or
whatever
group
really
navigates
the
packages
and
registries
and
hit
the
dependency
proxy,
and
you
would
be
introduced
with
a
screen
like
this.
You
have
the
ability
to
add
a
registry
or
create
a
virtual
registry,
and
then
you
have
a
list
of
everything
that
is
connected
to
your
dependency
proxy.
That
could
be
an
internal
package
registry.
C
That's
hosted
on
Kate
lab
either
in
this
group
or
in
a
total
third-party
group.
They
don't
necessarily
have
to
be
connected
registries,
that
you
have
added
your
authentication
information
for
third
parties,
so
going
out
to
AWS
or
a
public
NPM
registry,
or
a
private
NPM
registry
to
pull
it
in
or
a
virtual
registry
that
you
have
created
and
it
just
kind
of
lists
everything
out
in
the
dependency
proxy.
For
this
group,
any
thoughts.
D
There
is
accessed
accessed
by
dependency
proxy
middle
of
so
there
are
like
three
different
levels
just
to
access
one
package
within
with
them.
Good
luck!
Isn't
there
any
way
how
we
might
maybe
abstract
some
of
those
layers
out
or
maybe
yeah.
So
this
is
my
my
question
is
there
way
we
might
abstract
something
out?
First,.
C
You
were
so
right
now
the
simpler
solution
or
the
one
that
doesn't
have
as
many
layers
is
that
you
as
an
end-user
know
where
your
package
is
located,
and
so
you
just
directly
go
there
to
go,
get
it.
So
you
can
go
to
a
get
labs
package
registry
and
pull
down
the
package
or
if
you
know
that
it
is
in
NPM,
you
can
go
directly
to
NPM
and
this
solution
doesn't
stop
you
from
doing
that.
C
The
idea
here
is
that
a
DevOps
manager
could
create
one
API
for
you
and
tell
you
to
use
this,
and
you
will
be
able
to
get
that
one
package,
no
matter
where
it
is,
so
you
as
the
end
user.
You
is
the
engineer
on
a
large
dev
team.
Don't
have
to
know
where
each
package
is
so
part
of
this
is
that
the
admin
would
set
this
up
for
you.
The
engineer:
does
that
make
sense.
It.
E
Is
there's
a
lot
of
layers
yeah,
that's
kind
of
related
to
my
question,
because
this
is
on
a
group
level
right,
so
managers
of
users,
with
a
specific
permission,
should
be
able
to
yeah
access
this
page
and
I'm
just
used
to
see
how
this
would
cascade
or
how
this
would
translate
on
a
project
level.
Would
there
be
like
an
area?
How
could
you
say
that
people
know
where
to
find
it,
but
where
can
they
see
another
hops
engineer
how
things
are
set
up?
Does.
C
We
need
to
know
that
right
that
is
kind
of
the
premise
we're
running
on
and
I'm
gonna
make
a
note
to
make
sure
to
include
that
during
the
solution.
Validation
is
that,
if
you
were
already
at
the
project
level
registry
UI,
you
know
your
packages
there,
and
so
this
dependency,
proxy
and
virtual
registry
won't
help
you
directly.
C
E
It's
kind
of
it
makes
me
think
of
the
releases
and
the
asset
and
packages
and
everything
that
yeah
we
are
doing
on
release
management
and
for
us
at
least
users
that
have
like
developer
access.
They
would
still
see
everything
reflected
in
the
in
the
project
level.
We
know
these
are
set
up
in
the
proof,
but
yeah
they
cannot
add
it
just
because
they
need
to
stay
informed,
yeah
but
anyways.
Just
a
listening
question
there,
because
I
think
it
relates
so
as
you're
trying
to
wrap
my
head
around
it.
D
C
C
So
one
of
the
advantages
is
that
you
can
connect
a
virtual
repository
to
CI
and
it
will
pull
in
all
of
your
NPM
packages
and
your
custom
packages
and
the
one
you
just
built
into
your
codebase
and
let
it
flow
through
the
pipeline
with
only
one
access
token
and
one
URL.
Currently,
users
have
to
spell
out
each
package
or
package
type
to
be
able
to
do
that.
F
I
have
a
question
about
the
CD
ace
there.
So
there's
a
button
to
create
virtual
registry,
which
is
clear
to
me
that
creates
a
virtual
registry
and
then
add
registry
doesn't
create
a
hosted
registry
and
github.
So
this
is
like
this
is
something
I
had
to
think
about.
Maybe
it
would
be
more
obvious
to
the
target
user,
because
I
literally
know
nothing
about
about
the
stuff,
so
I'm
just
wrapping
my
head
around
how
it
all
works.
C
E
It's
related
to
the
filter
field
here,
to
my
name:
yes,
and
the
button
create
virtual
registry.
Yeah
I
assume
that
you're
using
the
pajamas
or
the
components
and
I
just
wanted
to
know
like
that.
They
look
very
similar.
I
had
to
look
twice
because
one
it's
a
button
and
the
other
one
is
actually
an
input
field
and
I.
C
E
D
A
C
So
this
one
I
would
really
appreciate
feedback
on
just
the
overall.
Does
it
articulate
the
idea?
So
this
is
a
virtual
registry.
This
is
the
complicated
one
we
talked
about,
which
is
one
registry
with
one
API
URL
endpoint.
That
goes
out
and
looks
for
many
different
looks
through
many
different
registries
to
find
a
package,
and
it
does
it
in
the
order
that
it's
displayed,
and
so,
if
you
change
the
order
in
the
UI
will
change
how
the
API
acts
and
I'm
feeling
kind
of-
not
it's
not
quite
there.
So
I'd
appreciate
some
feedback
on
that.
C
Registry
and
it
links
to
the
documentation
to
explain
it
more,
which
our
users
have
the
users.
I've
talked
to
have
really
appreciated
that
kind
of
direct
connection.
You
use
this
URL
that
you
can
copy
to
say,
npm
get
this
package
location
and
you
put
this
URL
in
and
it
will
search
all
the
different
npm
registries.
C
This
is
the
component
that
is
currently
in
the
epic
UI
that
allows
you
to
reorder
issues
and
add
issues
inside
of
an
epoch.
It
doesn't
directly
result
in
any
change
to
the
API
or
infrastructure.
It's
just
a
static
change
right
now,
and
so
the
thing
I'm
concerned
with
is
that
these
individual
items
you
can
drag
and
drop
to
reorder,
but
I'm
concerned
that
it
isn't
apparent
enough
that
one
that
reordering,
that
you
can
reorder
it
and
two
that
it
will
have
an
impact
of
the
way
that
you,
the
API,
works.
E
And
then
my
question
there
is
that:
do
you
have
like
an
entry
stage
before
this
view,
where
users
say,
can
click
Edit
or
reorder
list
and
then
confirm
because
I
see
that
your
buttons
are
disabled,
cancel
an
update
order,
but
I
wonder
if
this
is
just
how
you
land
on
it
or
users
need
to
activate
this
view,
because
I
imagine
that
you
know
proactively
clicking
something
to
reorder.
If
it's
so
sensitive
like
we
ordering
this
this
items,
oh
yeah
could
have
a
you
know.
C
That's
a
really
good
call:
I
am
still
working
through
the
actual,
create
a
new
virtual
registry
page.
My
idea
was
that
the
add
registry
functionality
would
be
similar
to
the
issues
at
issues
to
epic,
where
you
can
search
for
the
issue
name
or
in
this
case
search
the
registry
name
and
it
pops
up
and
you
can
check
multiple
ones
and
then,
when
you
hit
confirm
it
adds
them
to
the
list
and
then
you
can
reorder
them
there.
I
do.
C
Idea
of
being
explicit
with
an
action
button
that
says
like
reorder
registries
or
something
like
that
that
just
instead
of
trying
to
do
I
am
trying
to
do
it
the
other
way
where,
if
you
move
the
order
at
all
the
buttons
become
available,
and
you
can
update
it,
but
I
think
your
suggestion
would
work
better.
Now
that.
C
That
was
exactly
my
concern.
Was
that
it
doesn't,
you
can
reorder
them,
but
like
it
doesn't
impact
anything
apart
from
the
order
it's
displayed
in
and
that's
different
than
it
is
here,
but
I
didn't
want
to
create
a
whole
new
component
just
for
this
either.
If
I
could
avoid
it
so
I'm
trying
to
find
a
nice.
E
Different
component,
or
just
a
state
within
this,
what
they
call
this
component
or
this
musi,
whatever
you
but
yeah.
This
could
be
useful,
for
example,
when
you're
creating
a
release,
creating
or
editing
a
release
in
your
ad
in
ask
assets.
For
example,
are
you
adding
new
leads,
etc?
It
might
be
in
the
future,
because
you
want
to
have
drag-and-drop
to
upload
things,
but
might
be
a
use
case
where
users
want
to
the
reorder
or
just
change
some
things
related
to
the
package.
A
Yeah
I
agree
here
like
actually,
and
maybe
something
like
from
the
side.
Feedback
like
I,
wouldn't
read
that,
like
I'm
from
one
of
those
people
who
don't
really
read
text
and
actually
only
like
later
I
noticed
that
you
had
tried
to
describe
changing
the
order
of
the
least
like
what
effect
this
will
have
so
and
for
me,
like
it
was
like
I
was
actually
one
just
seen
your
screen
I
was
wondering
why
cancel
an
update
order?
A
Buttons
were
disabled
and
it
wouldn't
come
to
my
mind
to
try
to
move
these
things
around
to
get
the
buttons
enabled
but
yeah,
maybe
that's
you
know,
they're,
just
from
working
from
a
static
image,
I'm
missing
some
kind
of
like
a
visual
clue.
Usually
those
elements
like
have
a
little
bit
of
like
of
a
drag
I
can
there's
something
like
there
are
three
thoughts
or
something
that
they
indicate
that
these
components
are
movable.
A
E
A
Yeah,
but
it
would
be
exactly
like
what
I
mean.
Sometimes
they
had
three
dots.
Sometimes
it's
a
little
hamburger,
and
sometimes
it's
like
this
all
nineties,
like
I,
think
it's
like
this
cross
with
a
little
like
I,
don't
know
what
it's
like
this
handle
that
you
have
in
the
windows
UI,
but
something
like
that.
That's.
C
F
Of
sort
of
a
timeline
also
maybe
showing
like
direction
I,
don't
know
I'm
just
thinking
about
any
additional
clues
that
we
could
give
to
the
user
because
numbers
for
example.
For
me,
it
probably
wouldn't
be
the
best
way.
Maybe
it's
also
different
from
the
user
to
user.
You
know
different
people
process.
Information
differently,
like
like
Nadia,
said
that
she
doesn't
read
text
to
meet
the
numbers
like
for
me.
Visually
I
think
it
would
be
more
helpful.
E
C
What
am
I
thinking
it's
so
late
in
the
day?
Okay,
it
could
also
be
reminiscent
of
the
pipeline
view
where
you
see
all
the
different
jobs
and
they're
kind
of
connected
by
that
line.
We
could
take
some
of
that
UI
language
and
apply
it
here
as
well,
because
the
in
theory
is
the
same
idea
of
this
is
the
order
of
operations,
which
is
what
we
want.
B
C
E
A
C
C
Could
point
me
in
the
direction
of
a
nicer
less
wide?
For
the
auth
token,
it
makes
sense
for
technically
by
the
pajamas
guidelines.
If
I
understand
it
right
that
package
type
drop-down
that
I
have
up
here
in
the
top
right
should
actually
be
the
full
width
and
the
words
are
like
eight
characters,
long
at
the
most.
So
that's
kind
of
a
ridiculous,
drop-down
and
I'm
trying
to
avoid
that.
E
We
have
the
beige
containers
layout
figma,
those
are
not
implemented
yet.
So
the
thing
is
that
I
don't
share
which
configuration
you
have,
but
you
can
changing
the
settings.
How
you
want
to
see
the
pages
or
I
think
it's
lovely
out.
You
can
have
it
forward
or
you
have
no
812
columns
within
the
page,
retainer
I
hate
working
with
forms,
because
they
always
look
like
this
very
difficult
because
pajamas
and
we
say
that
the
form
should
be
in
line
like
in
line
block.
E
A
The
question
here,
if
you're
going
to
be
viewing
it
on
like
large
wide
screen
like
I,
have
left
at
my
other
house,
then
the
package
type
thing
could
end
up
fully
on
right
and
maybe
I
would
notice
that
we
would
like
become
really.
Why
don't
you
keep
this
width
and
then
like
leave
the
white
screen
there.
B
E
Yeah,
that's
my
only
employed
and
it's
weightless
like
yeah
I've,
been
boring,
because
if
you
for
some
lay
out
there,
it's
going
to
break
in
other
views
and
we
also
have
a
lot
of
legacy
forums
where
you
have
like
two
columns.
Layouts
right
clicking
settings
would
have
text
on
the
left
and
then
far
as
the
Brighton's.
It's
a
bit.
It's
a
catch-22
who
performs
learned.
A
D
C
A
B
Also,
I,
don't
think
that
this
is
one
format
that
you
can
certainly
take,
which
is
sort
of
showcase
II,
but
you
can
also
simplify
it
and
just
show
mock-ups
that
you
can
talk
through
you
know
it
doesn't
have
to
be.
This
formal
ian
had
a
lot
of
questions
that
he
wanted
to
get
answered,
so
it
makes
sense
that
the
you
know
did
it
in
this
way,
but
I
just
don't
want
anyone
to
sort
of
get
scared
and
say.
Oh
now,
I
have
to
create
another
presentation
for
another
meeting.
It
doesn't
have
to
be
like
that.
E
Many
years
are
the
notes
of
feedback
sessions
for
this
for
today,
and
my
thought
is
that,
since
this
is
a
monthly
right
call,
I
think
will
be
nice.
The
same
thing
we
do
for
the
CI
CD
for
the
verify
release
Nadia,
unless
you
maybe
give
a
chance
for
more
people
to
present
kind
of
yeah,
at
least
to
two
presenters,
a
wheat
or
at
least
two
topics,
yeah
I
loved
it
I
didn't
have
anything
to
present
what
I
think
will
be
nice.
Even
we
are
yeah
more
designers.
Well,.