►
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
Yeah,
hey
everybody,
I'm
Amanda,
Aretha
and
I'm
a
senior
product
manager
at
git
lab
in
the
plan
stage.
I
want
to
show
you
how
I
use
gitlab
for
my
own
tasks,
my
daily
work
and
in
this
video
I'm,
going
to
show
you
how
I
use
to-do's
in
in
each
issue
to
track
the
things
I
want
to
accomplish
for
the
week.
So
this
is
a
pretty
boring
approach.
There's
way
more
complicated
methods
out
there
with
more
complexity
in
terms
of
different
applications
and
methods
and
methodologies.
A
But
for
me,
I
found
the
way
to
stick
to
it
is
making
it
really
simple
and
using
a
git
lab
issue
totally
works
for
me
in
that
regard.
So
what
I
do
is
every
Friday
I
create
a
weekly
plan
for
myself
and
then
I
add
tasks
to
that
plan.
I
have
some
kind
of
loose
labels
here.
I
I,
usually
just
use
them
for
quick,
like
ease
of
reading,
for
example
like
important
over
reading.
A
If
I
have
time
to
do
something
and
pick
the
important
before
I
do
the
reading,
but
I
do
schedule
these
things
on
my
calendar
as
well,
so
that
they
come
up
with
my
natural
rhythm
of
my
day
and
I
block
time
out
for
them.
So
these
things,
these
tasks
that
are
listed
here
are
not
my
like
gitlab
to
Do's
they're,
not
my
notifications
or
things
that
come
up
day
to
day
emails.
Things
like
that
these
are
above
and
beyond
those
things
that
I
need
to
do
so
in
this
example.
A
A
But
some
things
I
definitely
know
I'm
going
to
carry
over
to
next
week,
for
example
like
firming
up
the
1511
planning
issue,
I'm
still
in
the
middle
of
planning,
and
we're
working
with
my
colleagues
on
this,
so
I'm
going
to
want
to
move
this
to
my
next
week's
plan,
which
is
being
created
today.
So
in
order
to
do
that,
I'm
just
going
to
make
note
of
the
title
from
up
1511
planning
issue
and
I'm
going
to
from
task
select
existing
tasks
and
I'm
just
going
to
type
firm
up
the
planning
issue.
A
Now
there
isn't
a
lot
of
content
in
this
particular
repo,
because
this
is
my
personal
kind
of
sandbox
and
so
I
don't
have
to
type
too
much
to
get
to
what
I'm
looking
to
do.
So,
if
I
refresh
this
planning
issue
from
last
week,
you'll
see
that
it
falls
off.
So
that's
how
I
can
move
things
if
I
don't
get.
A
A
Relationship
management,
so
that's
just
something
that
I
want
to
remember
to
do.
I
can
quickly
open
it
and
add
my
labels
I'm
going
to
assign
myself,
but
this
is
my
project,
so
I
don't
have
to
but
labels
this
one's
important,
because
I
really
need
to
get
this
thing.
Moving
and
I
could,
in
the
description
link
to
the
reference
information
there,
which
I
actually
have
here
in
this
week's
version
of
moving
that
project
along
which
is
a
slightly
different
task.
Oops,
okay,.
A
Okay,
great
so
I
think
I
saw
that
that
didn't
stick.
Oh
there,
it
did.
Okay,
so
yeah,
so
I
wanted
to
show
you
how
I
use
tests
in
an
issue
just
to
keep
myself
organized
with
my
kind
of
higher
level
tasks
that
I
set
out
for
the
week,
and
so
this
is
a
really,
as
I
mentioned,
lightweight,
boring
approach
to
use
gitlab
to
keep
yourself
organized
and
I
hope.
You
found
this
helpful
thanks
a
lot
bye-bye.