►
From YouTube: Plan group weekly meeting - 2019-07-03
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
I've
only
got
the
only
two
things
so
far,
so
probably
be
pretty
quick,
just
FYI
for
people
who
aren't
on
the
back-end
team.
We're
experimenting
with
so
previously
like
for
wasting
issues
I've
just
done
it
all,
with
the
exception
of
when
I
was
on
parental
leave
when
like
Marioni
am
did
it,
but
that
doesn't
really
scale
and
also
as
we're
playing
split
the
team.
That's
not
going
to
work
for
a
new
engineering
manager
as
well.
A
So
we're
talking
about
ways
to
like
have
the
back-end
team
wait
issues
without
doing
a
whole
planning,
pocus
thing,
which
I
think
is
probably
too
much
overhead.
Given
the
amount
of
issues
we
have
in
a
given
release,
so
there's
a
lot
of
discussion
there
and
some
really
good
ideas
from
the
back-end
team.
Other
back-end
teams
also
do
this,
for
instance,
manage
to
it
so
I'm
also
checking
with
them
like.
What's
worked
for
them,
what
hasn't
and
yeah
that's
just
sort
of
FYI.
A
Basically,
the
upshot
of
that
is
I
had
a
chat
with
Donald
earlier
I.
Put
comments
in
this
issue
where
we
were
planning
12.1
that
it's
kind
of
hard
to
tell
what
the
current
status
is
or
what's
what's,
gonna
make
it
unless
something's
already
merged,
like
it's
hard
to
be
certain,
so
I've
just
put
them
in
a
sort
of
rough
confidence
order
about
where
we,
where
I
see
those
issues
and
Donald's
added
some
as
well.
A
Or
things
from
that,
I
think
that
an
issue
that
has
back-end
and
front-end
both
working
on
it
takes
longer
to
be
closed.
By
doing
thing.
That's
a
problem.
It
just
makes
it
harder
for
me
as
a
manager
when
I'm
looking
at
the
board,
because
the
amount,
the
weight
of
the
issues
that
is
currently
in
progress
like
assigned
to
back-end
engineers,
is
a
huge
percentage
of
the
overall
weight
that
was
on
this
milestone
and
that's
not
because
people
haven't
been
working.
A
It's
just
because
the
issues
aren't
closed
because
they
take
time,
especially
when
this
coordination,
so
that's
sort
of
an
attempt
to
capture
where
we
are
I've
started,
moving
some
of
the
stuff
that
was
at
the
bottom
of
12.1
out
into
later
milestones
and
I.
Think
Donald
said
he
was
doing
the
same
for
front-end.
A
The
first
two
are
in
development,
but
you
know
won't
be
merged
by
the
time
we
start
working
on,
12.2,
I,
don't
think,
and
the
last
one
hasn't
had
anyone
pick
it
up
yet
so
I
think
Donald's
already
asked.
If
we
can
move
that
over,
we
don't
have
four
issues
in
the
description
which
I
think
is
still
valid.
I,
don't
think
anybody's
suggesting
we
we
move
those
out
so
I
think
are
all
good
there.
A
A
Those
settings
like
so,
if
you
access
on
a
different
device,
you
still
have
the
same
lists
collapsed
as
you
would
on
another
device
and
then
finally,
the
board
list
capacity
line
which
we've
talked
about
before
and
then
there's
one
more
I
added,
which
was
Eric
mentioned
as
a
high
priority,
but
wasn't
with
the
direction
label,
which
was
allowing
email
notifications
to
be
disabled.
For
all
users
of
a
group
it
says
all
project,
but
the
the
NBC
we
care
about
here
is
group.
A
So
this
means
that
at
the
moment
my
I
as
a
user
can
say,
don't
give
me
any
emails
from
the
gate,
lab
or
group,
but
the
owner
of
the
gate,
lab
or
group
can't
say
this
group
needs
to
send
no
emails,
because
maybe
they're
sensitive
content
in
this
group
that
can't
be
sent
over
a
channel
like
email
which
isn't
the
most
secure
channel
or
maybe
there's
some
other
reason
but
yeah
whatever
it
is.
Like
you
know,
that's
the
requirement
they're.
A
A
This
issue
I
was
like,
oh
maybe
we
should
bring
something
else
in
I,
actually,
don't
think
we
should
now
because
that's
like
eight
sort
of
fairly
major
issues.
If
we
include
the
three
that
I've
estimated
we'll
probably
have
somewhere
Kaplan
12.2,
there
might
be
more
than
three
there
might
be
less
than
three.
That's
just
an
estimate,
I
think
I
think
it
would
be
too
ambitious
to
take
more
I,
don't
know
if,
if
anybody
disagrees
like
please
comment
like
I
feel
like
we've
got
enough
on
our
plate
and
then
I
was
just
mentioning
at
the
bottom.
A
How
I
was
gonna
prioritize
the
borders
there
itself?
He
did
message
me
on
slack
because
he's
just
trying
to
keep
track
of
things,
even
though
he's
on
vacation
so,
but
hopefully
that
can
be
pretty
lightweight
for
him.
So
at
the
top
there's
gonna
be
security
issues
due
this
month.
I
think
they're
all
back
end
this
month.
So
this
only
affects
the
back
end
team,
but
any
security
issue.
That's
due
this
month.
We
need
to
get
done
to
make
that
SLO.
A
The
features
that
list
interests
they're
as
high
priority,
any
items
that
we're
carrying
over
from
12.1
can
go
then
below
those
two.
In
theory,
they
should
probably
go
above
the
features,
but
the
features
tend
to
be
bigger,
so
I
think
it's
easier
to
slot
those
the
things
they're
carrying
over,
which
are
smaller
below
those.
A
And
then
yes,
I,
think
I
get
what
double
bruh
say
then
P
to
bugs,
because
you
know
those
an
SLO
of
60
days,
I
think
we
say
and
then
just
the
rest.
I
wasn't
really
gonna
bother
with
like
dragging
every
single
thing
to
the
exactly
right
position
and
the
board,
because
some
it's
not
how
we
work
so
I'm
gonna
pick
on
someone
I
like
sisters
that
sound
good
to
you.
Any
concerns
about
those
issues
that
we're
bringing
into
12.2
or
the
ones
that
might
carry
over
from
12.1
into
12.2
yeah.
A
So
there's
the
three
here,
so
we
don't
know
because
we're
still
working
on
it.
The
three
here
are
the
most
likely
to
have
some
work.
Happenin
12.2
now
when
I
say
happen
in
12,
that's
also
kind
of
confusing,
because
if
we
finish
something
early
and
12.2
development
milestone,
it
might
still
actually
end
up
in
the
12.1
release
on
the
22nd
of
the
month.
A
But
yeah.
There
is
a
losing
the
three
that
I'm
most
likely
to
have
some
work,
which
I
would
count
as
a
significant
amount
of
work
to
happen
in
12.2,
and
then
these
four
are
the
sort
of
things
we're
starting
on
sorry,
these
five
other
things
we're
starting
on
next
month
as
well
as
sort
of
major
features
that
we
would
some.
B
A
C
A
And
I
got
to
mention:
I
haven't
checked
capacity
for
back
India,
but
because
these
will
be
at
the
top
I'm,
just
assuming
I'm
going
to
be
pushing
other
stuff
out
in
favor
of
these.
Unless
we
think,
like
you,
know,
front
end
wise,
we
can't
do
it
because
you
know
we
can't
really
have
one
person
do
two
of
these
issues.
If
they're
high
priority
I
guess
unless
it's
a
tiny
frontside
one
crate
yeah.