►
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).
B
A
Everyone
cool
so
we're
just
going
to
quickly
go
through
the
items
we
have
in
mind
in
1511,
our
team
is
operating
at
approximately
70
capacity.
Nikola
has
been
on
paternity
leave
last
month
and
he's
still
opportunity
to
leave.
We
expect
he'll
be
back
roughly
the
end
of
this
month.
Our
top
priorities
are
roughly
threefold.
A
First
off
we
want
to
wrap
up
our
rubies
3.0
work.
Ruby
3.0
has
now
been
deployed
to
tip
lab
SAS.
We
are
going
to
run
a
retro
to
document
our
learnings
and
there
is
some
small
amount
of
cleanup
items
that
our
team
is
responsible,
for
there
are
some
additional
optional
work
items,
but
we're
gonna,
basically
forward
them
to
the
rubies
3.1
upgrade
stream
for
consideration
and
prioritization
the
other
major
area
of
this
theme.
The
other
major
theme
of
this
Milestone
is
for
us
to
continue
ramping
upon
real-time
features
across
git
lab
in
1510.
A
We
prioritize
the
contacts
transfer
about
real-time
text,
editing
due
to
a
team
member
departure
and
updated
documentation
to
capture
our
current
state
of
work,
because
we
estimate
that
real-time
text
editing
is
over
a
year
from
production.
Readiness
we've
decided
to
pause
this
worksheet
in
favor
of
improving
our
current
real-time
stack,
we're
gonna
ramp
up
on
our
current
real-time
stack
by
extending
issue
epics
to
use
real-time
updates
using
our
current
technology.
A
A
B
Now
that
we've
actually
we're
able
to
see
how
it
looks
on
the
UI,
and
so
once
we've
done
that
towards
the
end
of
this
iteration
I
think
our
plan
is
to
spend
around
a
week
or
so
time
boxed
and
looking
into
some
of
the
the
slow
Pages
within
gitlab
that
get
a
lot
of
traffic
through
a
prioritized
list
and
try
to
look
for
any
cross-cutting
improvements
that
we
can
make
across.
That
there's
been
a
few
teams
that
have
contacted
us
to
around
with
some
performance
issues
that
they
think
we
could
help
with.
B
So
we're
going
to
try
and
look
to
kind
of
prioritize
those
as
well,
and
we
will
hopefully
use
some
of
this
new
tooling
and
the
profiling
support
that
we've
built
to
support
that.
A
Yeah,
it's
super
exciting
and
then
lastly,
just
two
small
maintenance
items
to
call
out
here,
one
is
a
small
bug
around
Prometheus
metric
samples
and
some
spikes
that
we
see.
We
think
some
of
this
work
could
be
helpful
as
we
support
our
real-time
working
stream,
because
we
expect
this
problem
to
exacerbate
as
we
increase
our
graphql
queries
across
our
system
and
as
another
maintenance
item,
there's
a
dependency
update
here
for
go
1.19
that
will
address
with
gme
as
well
anything
else
Paul
that
you've
got
in
mind.