►
From YouTube: 2021-02-08 Delivery team weekly
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
Everyone
so
happy
monday.
I
hope
you
had
nice
weekend.
A
So
let's
get
there's
a
few
things
on
the
announcements
I
just
quickly
mentioned
my
ones,
so
just
a
little
bit
of
visibility
on
okrs,
so
the
engineering
okls
have
been
put
together,
I'm
working
on
drafts
for
our
okrs,
but
just
to
kind
of
heads
up
and
give
you
a
chance
to
have
a
read
through.
We
can
talk
about
these
later
on
in
the
week
as
well,
and
then
second
one
is
just
a
kind
of
a
again
visibility.
A
Is
that
the
dev
escalation
process
has
been
extended
so
that
now
covers
release
post
publishing.
So
if
you
have
any
troubles,
publishing
release
posts
for
any
reason
like
it
probably
won't
come
for
us,
but
just
so
you
know
it.
We
can
also
use
this
process.
There's
an
mr
open
as
well
to
also
extend
the
dev
escalation
process
to
cover
broken
master.
So
we
can
hopefully
use
that
as
well.
Quite
soon,
then,
I'm
going
to
be
out
on
friday,
scubak.
B
Just
some
light
reading
there's
an
epic
discussing
the
container
registry,
auto
deployment,
and
this
is
kind
of
required.
They
want
to
implement
a
database
and
we
want
to
not
be
a
blocker
for
their
deployments.
So
for
those
that
are
interested,
I
created
a
sync
meeting
for
tomorrow.
C
Yeah
light
reading,
yeah
sure,
and
so
my
point
I
I
was
working
on
summer's
request
and
I
found
this
youtube
video
and
then
I
realized
it
was
shared
today
in
the
engineering
we
can
review.
So
this
is
a
recording
for
it's
kind
of
discussing
the
handbook,
something
like
that.
There
is
eric
and
all
of
our
distinguished
engineer
plus,
and
they
are
discussing
this
ic
engineering
ic
leadership
page,
which
is
the
one
that
jar
and
I
worked
on
the
when
we
were
at
the
beginning
of
the
ic
gearing
group.
C
D
No,
I
mean
that's
true
the
doc
just
links
to
the
agenda.
I
couldn't
quickly
find
anything
about
it,
but
maybe
I'm
blind
and
the
video
is
45
minutes
so
just
wondering
if
there's
like
a
quick
summary
of
it
somewhere.
C
The
link
should
point
to
the
item
in
the
agenda,
but
there
is
there's
the
tldr
is
just,
as
I
told
is
our
distinguished
engineer,
plus
and
eric
that
are
discussing
four
archetypes
or
the
type
of
work.
That,
let's
say
I
see
leader
is
engineering.
I
see
leader
is
doing
so
it's
more
about
iteration,
it's
about
empowering
others.
It's
about
scope
of
influence,
this
time,
so
they're
just
sharing
their
thoughts
on
on
it.
D
A
Cool
thanks
for
sharing
so
on
to
discussion
points
on
wednesday.
We
have
an
ama,
so
please
attend
that.
What
I
thought
we
might
use.
So
what
the
last
couple
have
had
some
interesting
conversations,
but
we
don't
get
a
whole
load
of
questions.
But
often
we've
had
like
a
bit
of
conversation
and
then
some
questions
come
in.
So
what
would
you
think
about
us?
A
Just
framing
this
month's
one
around
coding
at
scale,
and
we
can
just
kick
off
and
have
a
discussion
about
coding
at
scale
and
it
like
whatever's
interesting
to
us
so
like
thinking
about
some
of
the
incidents
we've
had,
maybe
or
like
talking
about
rollbacks
and
what
we're
doing,
but
just
generally
starting
to
make
this
more
conversational.
And
then
we
can
invite
people
in
to
kind
of
join
us
and
then
just
kind
of
see
where
that
goes.
A
Does
that
sound
like
it
would
be
worth
trying
at
least
like
there's,
no
saying
how
it
will
turn
out,
but
like
does
it
seem
worth.
C
Trying
so
what
do
you
have
in
in
mind
amy?
So
you
want
to
start
discussing
it
like
introducing
the
topic
or
is.
A
A
Actually,
framing
this
one
and
so
actually
putting
out
the
announcement
like
tomorrow
that
we'll
we
have
a
name
ama
and
yeah,
we'll
take
regular
questions,
but
we're
also
looking
to
hold
a
conversation
about
coding
at
scale
and
then
I'll
put
together,
something
which
has
some
of
that
information.
So,
for
example,
like
recent
incidents
that
were
you
know,
coding
at
scale
issues
or
try
and
frame
a
little
bit
about
why
we're
looking
at
rollbacks
and
like
what's
difficult.
A
So
everyone
loves
the
idea
of
rollbacks,
but
not
many
people
understand
why
we
don't
have
them
yet
so
actually
trying
to
just
get
some
things
together.
So
people
can
like
look
through
that
beforehand
and
then
we
can
like
open
up
the
conversation
like
and
it
can
be.
A
It's
fine.
I
think
it's
totally
fine.
If
it's
just
a
conversation
between
us
and
then
we'll
see
where
that
takes
us.
D
I
have
a
completely
different
remark.
Amy,
can
you
send
me
an
invite
to
the
event
because
it
is
in
the
team
calendar,
but
I
can't
click
join
there.
It
shows
up
in
my
search,
but
then
google
very
helpfully
says,
can't
open
the
event
and
if
I
show
the
client
events
it
doesn't
show
up
either.
So
I
don't
know
what
google
is.
A
Doing
we'll
have
a
think
about
it.
What
I'll
do
is
I'll
put
together
some
stuff,
as
I
say
it,
I'll
have
to
find
out
how
to
add
your
site,
uric
I'll,
add
I'll,
put
together
some
stuff
and
like
it
totally
is.
If
the
conversation
goes
somewhere
else,
absolutely
fine,
but
I
do
want
people
to
start
being
a
little
bit
more
conversational
about
this
coding
at
scale,
because
I
think
it
will
really
set
up
a
lot
of
what
we're
going
to
be
working
on
in
the
future.
A
So
we'll
see
how
it
goes
anyway.
Also,
if
you
have
any
random
questions,
you'd
like
to
bring
along
to
that
ama.
Obviously
it's
not
just
us
answering
other
people's
questions.
It
can
be.
I
was
posing
questions
or
if
we
want
to
talk
about
anything
within
the
team
that
we
haven't
had
a
chance
to
discuss,
we
can
also
use
that
time
as
well.