►
From YouTube: CMS Sprint Retrospective 01/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
A
It's
deployed
hasn't
been
any
issues
with,
adding
that
I
am
now
aligned
with
security
on
how
to
set
up
our
oauth
application
and
I'll
be
filing
an
issue
with
infrastructure
for
getting
that
set
up,
and
the
templates
that
I
received
from
tina
they've
been
really
helpful
and
guiding
for
how
we're
gonna
build
out
the
templates,
pastor,
retina.
B
Okay,
so
a
few
things
that
I
think
went
really
well
a
collaboration
overall,
specifically
with
the
design
system
team
for
the
ui
implementation,
working
with
real
content
on
real
pages
allowed
us
to
hone
in
on
areas
that
needed
immediate
attention,
for
example,
card
anatomy,
which
is
something
that
we've
created
a
separate
issue
to
start
working
on
insights
gained
from
key
members
who
managed
the
sections
that
were
improving
have
been
invaluable.
B
It
has
helped
us
focus
on
small
iterations
that
deliver
big
wins,
prevents
us
from
working
on
assumptions
and
solely
relying
on
best
practices
so
that
we
can
give
or
provide
solutions
that
the
contributors
actually
need.
B
Also,
the
figma
templates
that
we
created
can
be
reused,
so
that's
great
they're
flexible.
We
can
use
them
for
future
cms
integrations.
We
can
use
them
on
other
site-wide
updates
and
some
elements
can
be
repurposed
for
the
design
system
work.
B
Next,
we
want
to
talk
about
things
that
could
be
improved
on.
I
only
had
one
point
here:
kind
of
throwing
it
out
there
that
maybe
we
could
use
a
laundry
list
of
the
blocks
that
we're
building
specifically
for
the
cms
that
outline
usage
and
behavior.
I
know
that
the
design
system
team
is
also
working
on
in
this
area,
so
maybe
some
kind
of
cross-referencing
with
them.
The
usage
for
the
stuff
that
we're
using
in
the
cms
might
be
different
for
the
usage
in
the
design
system.
B
So
that's
just
something
that's
coming
front
of
mind
as
we're
moving
forward
with
other
parts
of
the
site
before
things
get
too
messy.
A
B
Yeah
and
I'm
wondering
if
the
figma
file
itself
provides
like
enough
information
about,
you
know,
usage
and
behavior
yeah.
So
that's
maybe
an
action
item
that
we
need
to
yeah.
A
A
Yeah
I'll
jump
in
to
the
second,
so
the
work
to
implement
a
content
type
template,
for
example,
the
topics
page
and
deployed
to
the
www
repo
is
gonna,
live
within
one
merge
request,
but
there's
many
steps
and
issues
tied
to
that.
So
I
have
outlined
five.
The
first
step
was:
we
have
to
build
the
template
in
figma.
Tina
did
a
great
job
at
that
and
it's
been
really
awesome
for
outlining
it.
The
second
step
is,
I
have
to
build
the
functionality
of
it,
so
how
the
content
is
going
to
be
stored.
A
How
the
data
file
is
going
to
be
structured,
then
I
need
to
migrate
an
existing
topic
into
that
template
form
so
migrating
that
content
into
the
data
file
structure
and
then
adding
styling,
and
then
we
can
deploy
it
and
once
we
deploy
it,
it's
live,
and
I
don't
want
to
do
that
until
it's
good
to
go
because
it's
essentially
a
new
it's
a
new
version
of
the
page.
A
We
only
want
one
of
those
so
one
mr
attached
to
many
issues
which
is
okay
but
trying
to
think
of
a
better
way
to
represent
that
in
our
sprint.
A
B
It
looks
like
you're
doing
a
lot
of
this
stuff
on
your
own,
with
resourcing
help
a
little
bit.
Adding
you've
got
a
larger
team
now,
just
assigning
some
things
to
other
folks.
A
Yeah
I
yeah.
We
need
to
definitely
loop
in
some
other
resources
on
our
team
to
help
you
build
build.
This
functionality
out.
Tyler
comes
to
mind,
he's
just
finishing
up
onboarding,
so
that'll
be
a
great
resource.
A
A
B
I
think
that's
okay
same
with
ux,
like
here's,
a
document,
here's
a
google
form
survey.
A
B
Yeah,
based
on
what
you
showed
me
today,
it
looks
like
it's
going
much
smoother
than
some
of
you
know.
We
previously
anticipated.
So
that's
great
good
work.
I'm
super
excited
to
get
my
hands
in
there.
I
don't
see
many
action
items
really.
We
need
to
go
over
then,
aside
from
maybe
talking
about
resourcing
next
week,
yeah.
A
Yeah,
we
definitely
need
to
loop
in
another
dev
because
and
tyler
is
a
good,
a
good
one,
because
it's
a
a
whole
repo
infrastructure
thing
and
it'll
also
be
introductory
for
starting
to
learn
our
way
around
the
templates
or
haml
syntax.
B
Okay,
so
I'll
set
up,
maybe
a
meeting
with
the
three
of
us
and
whoever
else
wants
to
join
next
week,
just
to
bring
them
up
to
date.
With
what
we've
been.
B
A
Initial
like
base
template
and
then
we'll
want
someone
to
go
in
there
and
make
it
pretty
or
if
we
do
need
to
change
stuff
yeah,
then
someone
from
front
end
from
from
that
part:
okay,.
B
All
right
is
there
any
final
words
till
we
meet
again
on
monday.
A
I
really
liked
the
sigma.
It
was
easy
to
work
through
the
different
parts,
the
wire
frames
or
the
wire
yeah.
The
wire
frames,
the
pressure
test,
the
this
version
of
the
blocks
yeah.
It
was
a
clear
outline
for
what
needs
to
get
built
and
whether
we
have,
but
then
you
know
what
the
new
parts.
B
Are
great,
are
there
any
improvements
you
would
recommend
in
terms
of
the
way
we're
annotating
things
and
making
note
of
you
know
different
kind
of
usages
and
stuff
like
that
or
keep
going
this
way
for
now.
Yeah.