►
From YouTube: Digital Experience Retro - Dec 15, 2022
Description
Digital Experience handbook page: https://about.gitlab.com/handbook/marketing/digital-experience/
A
Hi
everyone
welcome
to
digital
experience.
This
is
our
iteration
retro
on
ending
on
today,
Thursday
December
15th
we'll
go
over
some
of
the
things
that
came
up
this
iteration
things
that
went
well
and
things
to
improve
on
so.
First
up
we
have
a
thing
to
bring
up
by
John
he's
working
async
out
of
Malta,
so
I
will
vocalize
his
point
here,
but
he's
talking
about
highlighting
the
possibility
of
having
a
centralized
image
bucket
or
server
where
we
can
store
images
used
across
multiple
digital
experience
projects.
A
We
would
improve
certain
important
things
in
his
opinion
and
he
goes
on
to
talk
about
images
that
are
duplicated,
such
as
the
infinity
image
across
buy
our
experience.
It's
hard
to
only
have
one
image
without
duplication,
as
we
have
four
different
working
groups
and
we
do
not
spend
time
searching
if
an
image
is
already
exists
across
those
folders
in
next
images.
Folder.
If
we
have
a
centralized
bucket
I
think
this
could
be
possible
to
handle
that
solution
using
folder,
structurization,
structuration
naming
conventions
and
ey
Gallery.
A
A
We
have
projects
that
work
as
libraries,
such
as
navigation
slippers,
showing
images
in
these
projects
is
really
complex,
as
the
images
should
be
handled
by
webpack
in
order
to
show
them
using
images
as
external
files
fixes
these
issues.
I
know
there
are
cons
of
using
these
types
of
servers,
but,
in
my
opinion,
I
believe
that
having
one
would
improve
the
way
we're
handling
images
today.
Thank
you.
So
his
speech
is
done.
Miguel
I
see
that
you
have
a
point
in
there.
Do
you
want
to
go
ahead.
C
D
C
I
I
don't
know
about
an
MBC,
but
I.
Remember
that
we
talked
about
this
with
Tyler
and
he
mentioned
that,
since
we
are
already
using
gcp
Services
all
over
gitlab,
we
could
use
the
cloud.
Storage,
buckets,
I
believe
it's
called,
which
is
the
equivalent.
So
it's
just
a
service
that
he
hosts
static
objects,
yeah.
B
B
Every
time
a
pipeline
runs.
We
have
to
like
process
all
thousands
of
images,
so
getting
those
out
of
there
onto
a
S3
bucket
would
be
awesome
and
then
also
we've
explored
this
in
the
past.
It's
been
an
ongoing
conversation
since
I've
been
here
and
every
time
we
start
making
progress
towards
it.
It
doesn't
happen
for
some
reason,
so
I've
linked
to
three
issues
there
for
as
far
as
we've
gotten.
B
B
E
Yeah
and
one
of
the
plus
one
I
hope
we
can
have
something
like
this
soon.
It's
exciting
but
I,
know
looking
ahead
to
the
2023,
okrs
and
and
goals
with
like
having
a
CMS,
possibly
maybe
whatever
solution
is
picked
for
that
might
have
their
own
bucket,
that
or
or
preference
of
like
bucket
tools
to
use.
So
it's
not
just
something
to
keep
in
mind.
F
B
F
A
A
So
we
still
get
some
face
time
with
each
other
and
then
working
asynchronously
when
we
don't
and
then
also
I
noticed
that
last
week
in
Montreal,
with
Parker,
Michael
and
Justin
being
in
Montreal
and
me
and
Nathan,
most
of
the
leadership
team
was
gone
last
week.
Hobby
wasn't
there,
like
you
know,
we've
really
abandoned
a
lot
of
people.
So,
thanks
to
everyone
who
kept
the
fort
holding
the
fort
kept
the
fort
down,
I
don't
know,
but
the
terms
thank
you
all.
A
A
I
also
want
to
say
that
that,
for
the
people
who
weren't
in
Montreal,
we
had
to
switch
teams
with
field
marketing.
I
guess
I
can
stop.
Recording
here,
but
I'll
finish
my
story.
We
had
to
switch
teams
with
field
marketing,
so
we
had
to
learn
what
that
team
did
and
try
to
improve
sales
pipeline
and
hobby
was
our
senior
director
of
field
marketing.
He
went
up
and
did
our
presentation
and
it
was
comedy
he
had
people
laughing.
He
had
people
crying.
He
had
people
in
their
feelings.