►
From YouTube: 2022-06-21 Package: Weekly Team Meeting
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
Hi,
everyone
welcome
to
our
weekly
sink
today
is
june
21st
and
I'm
not
sure
on
which
of
our
process
for
the
week.
We
are
right
now.
It
theory
should
be
week
three,
but
we
are
not
yet
on
the
middle
of
the
milestone.
So
let's
go
on
the
flow
and
see
what
we
have
on
our
agenda.
So
the
first
one
for
announcement.
A
Next
one
is,
I
want
to
talk
with
everyone
about
the
liberalization
guidelines,
I'm
going
to
go
with
the
whole
context
in
case.
You
didn't
have
time
to
read
about
this
in
the
previous
weeks,
so
there
is
a
working
group
trying
to
make
sure
that
we
find
better
ways
to
prioritize
our
work
at
gitlab,
so
we
really
drive
impacting
our
users,
and
this
means
that
we
want
to
make
sure
that
we
balance
the
amount
of
issues
that
we
work
on
every
milestone,
trying
to
have
a
percentage
of
around
60
on
futures
30
in
maintenance.
A
The
official
asks
is
that
we
have
dris
for
this.
So
as
em,
I
should
be
prioritizing
maintenance
work
sophia,
as
quality
should
be
prioritizing
books
and
officially
we
should
present
this
list
to
teams.
So
team
can
say
what
we
are
going
to
be
working
on.
I
honestly
prefer
that
we
continue
with
our
process
in
the
way
that
we
do
it.
That
is
more
freely
and
everybody
can
contribute
to
it,
and
I
prefer
that
we
just
take
a
look
to
our
dashboard
that
I
didn't
link,
but
I'm
going
to
put
the
links
on.
A
I
don't
even
know
if
I
have
it
we're
going
to
have
this
dashboard.
That
is
going
to
show
us
the
percentage
of
issues
that
we
have
on
this
feature
maintain
answer
box
and
just
trying
to
be
close
to
those
percentages.
If
we
are
not
close
to
it,
it's
not
bad.
It's
just
like.
We
need
to
present
why
we
are
not
on
it,
considering,
for
example,
that
container
migration
is
a
feature
we
are
going
to
be
very
high
in
future,
or
we
were
in
previous
milestones.
A
B
A
C
We
could
just
include
the
dashboard
in
the
milestone
planning
issue
as
well.
We
could
look
at
it
there.
I
I
think,
we've
been
doing
a
good
job
of
this
already
sort
of
including
all
these
things,
and
I
think
this
process
is
for
teams
where
the
quad
has
not
been
working
so
well
to
balance
work
fairly.
I
think
that
michelle
and
sophia
and
katie-
and
I
have
done
a
good
job
of
that,
but
we
have
to
stick
stay
in
line
with
these
numbers,
and
I
expect
that
we
will
need
to
defend
our.
A
And
we
are
going
to
be
have
like.
It
was
a
conversation
that
we
have
on
the
em's
channel,
that
there
is
going
to
be
also
a
lot
of
cases
where
we
are
going
to
be
prioritizing
books
that
have
more
impact
on
customers.
A
A
Okay,
I
can
do
that
later.
Any
other
comment,
questions
on
this.
D
D
A
C
I'm
just
catching
up
because
after
so
after
a
long
weekend,
so
unfortunately
I
didn't
get
to
populate
that
information
for
today,
but
my
quick
update
that
I
shared
last
week
because
I've
just
been
working
on
a
quarterly
plan
for
next
fiscal
quarter,
so
q3
following
the
same
vein
of
what
we
did
for
q2.
So
I
think
I
tagged
people
in
that.
So
if
you
could
take
a
look-
and
let
me
know
your
thoughts,
that
would
be
great
and
I
have
like
a
plan
for
milestone.
C
15
3,
it's
a
I'll
it'll
be
ready
like
tomorrow.
I
just
want
to
finalize
a
few
things
and
it
will
be
just
to
set
expectations.
It
will
be
a
bit
lighter,
especially
on
the
rail
side,
because
we
have
our
rails
engineers
have
some
much
needed
vacation
coming
up,
so
there
will
be
less
deliverable
issues
for
for
15
3.
From
that
perspective,.
A
Good
yeah,
I'm
also
touching
up,
so
I
also
I'm
not
quite
sure
where
we
are
right
now.