►
From YouTube: Plan | Weekly Sync 2023-03-01
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
All
right
cool
plan
stage,
weekly
meeting
first
of
March,
2023
kushal,
everyone.
B
I
already
introduced
Joseph
in
our
plan
Channel,
but
yeah.
Please
join
me
welcoming
Joseph
to
product
planning.
He
moves
into
product
planning
team
from
manage
Integrations.
As
a
senior
back-end
engineer,
he's
been
with
gitlab
for
over
three
years,
so
new
to
the
team,
not
really
new
to
the
company.
So
Joseph.
You
want
to
go
ahead
and
introduce
yourself.
C
Yeah
thank
you.
I
joined
last
week,
but
I'm
gonna
be
with
the
foundations
team,
I
think
for
through
Milestones
on
learn
and
then
I'll
I'll
come
back,
but
I
think
you'll
see
me
around
in
much
request
so
that
I
can
catch
up
on
what
you've
all
been
doing.
D
C
I
wrote
a
bit
about
myself
in
the
dock:
yeah
I'm
in
there
I'm
in
the
Netherlands
and
moved
here
in
2021,
but
I'm
from
Kenya
originally
and
I
I
was
in
support
for,
for
the
first
part
of
my
gitlab
career
I
can
see.
Ben
is
on
the
call
we're
back
together
in
the
support
team
and
then
last
year
I
moved
over
to
the
Integrations
team,
yeah
yeah.
So
that's
me.
A
A
Welcome-
will
be
in
a
future
plan
meeting
stay
tuned
for
that,
but
they
I
won't
put
them
on
the
spot
right
now
by
asking
them
to
introduce
themselves
and
all
that
extra
stuff.
We'll
leave
all
the
good
stuff
for
two
weeks
when
it's,
hopefully
in
all
of
their
time
zones
again
sound
good.
Does
anyone
want
to
go
night?
Anyone
want
to
get
it
over
with
Casio
Naman
Giannis.
A
Awesome:
okay,
great
yeah,
build
the
anticipation
for
a
couple
of
weeks
from
now.
Yeah,
definitely
a
reason
to
come
back
to
the
plan
weekly
meeting
in
two
weeks.
Awesome
all
right,
because
I'll
give
the
next
one
as
well,
then
yeah.
B
Before
I
do
that
I
just
noticed
that
Donald
was
driving
and
also
attending
this
call,
so
I
I
hope
he's
pulled
over
before
going
seeing
the
rest
of
the
agenda
are
getting
discussed
yeah.
So
since
we
don't
have
any
demos,
just
I'm
basically
going
to
share
it.
So
basically
we
are
introducing
a
new
feature
to
work
items
that
is
toggling
the
notifications
on
work
items
much
like
how
we
do
for
issues
Mrs
and
epics.
So
the
the
question
is:
what
do
we
name
this
widget?
B
Because
naming
is
hard,
so
we
are
basically
we
are
inclining
towards
one
particular
widget
name
but
I've
linked
the
issue
so
feel
free
to
chime
in
your
thoughts,
because
it
is
the
first
Boolean
widget
like
all
the
widgets
that
we
have
had
so
far
are
essentially
input
type
Fields,
but
this
will
be
just
Boolean
and
using
can
expand
more
on
the
thought
process
behind
the
widget.
E
Yes,
I,
don't
know
if
we
have
to
discuss
this
if
we
want
to,
but
basically
one
of
the
reasons
why
this
is
hard
to
name
is
because
it
behaves
quite
differently
to
the
existing
widgets
and
and
the
information
it
returns
and
the
action
it
provides
and
it's
a
bit
different
to
what
we
have.
So
this
might
be
an
opportunity
to
set
a
standard
of
how
we
want
to
mention
this
name.
This
we
should
see
in
the
future.
For
example,
we
would
have
confidentiality
and
also
lock,
to
lock
an
issue.
E
Those
are
the
things
that
are
also
like
behaves
like
a
toggle
and
that
will
return
true
or
false,
and
so
in
that
case,
maybe
if
we
can
agree
your
name
and
start
applying
it
now,
but
anyone
can
if
they
can
vote
on
their
comment.
That's
the
easiest
way
or
just
add
a
new
proposal
or
any
feedback
is,
would
be
great
thanks.
F
All
right,
if
there's
nothing
else,
I'll
move
on
to
my
item,
so
I
wanted
to
bring
visibility
to
an
okr
that
we
have
this
quarter.
The
link
is
there
and
it's
around
basically
making
sure
work
items
are
aligned
to
the
pajamas
or
design
system
and,
as
you
all
know,
aligning
to
pajamas
is
a
way
that
we're
bringing
consistency
to
end
users
and
deeply
tied
to
sus.
F
So
in
the
past,
I
know
that
we've
deviated
from
our
design
system,
basically
to
optimize
for
making
timelines,
which
I
think
is
not
necessarily
a
bad
decision.
But
what
I'd
like
us
to
do
is
just
be
more
diligent
around
recording
instances
when
our
design
system
doesn't
meet
our
needs
and
working
with
the
team,
with
the
pajamas
team
to
record
that
and
make
changes
to
our
design
system
if
needed.
F
We're
doing
that
as
part
of
the
ore
filtering
epic,
where
we're
basically
making
changes
to
multi-select
Upstream,
which
is
great
because
one,
not
everyone
in
the
company,
can
take
advantage
of
that
new
pattern
into
it.
Elevates
our
design
system
so
just
be
on
the
lookout
for
those
submit
issues
to
the
design
system,
team
and
work
with
your
designer.
When
you
encounter
those
situations,
please
I,
don't
know
if
Jackie,
to
put
you
on
the
spot
a
little
bit.
If
there's
anything
else,
you
want
to
say.
G
We're
gonna
be
spending
like
Melissa
said
we're
gonna
be
spending
a
bunch
of
time.
This
quarter
going
through
I
think
there
are
stuff
and
plan
in
figuring
out
where
we've
diverged
from
the
design
system.
H
A
A
Okay,
I'll
jump
on
to
the
next
one
last
minute:
entry
from
me,
sorry
Taking,
Liberties
yeah.
So
how
will
we
work
to
make
okrs
generally
available,
given
that
they're
like
open,
ux
questions
around,
for
example,
how
to
create
a
an
objective
and
that
kind
of
thing
we
did
some
things
that
we
wouldn't
have
otherwise
done,
because
it
was
completely
internal
I,
believe
the
whole.
Creating
an
objective
from
within
an
issue
list
like
would
not
have
been
done
if
you're
shipping
it
to
customers
sort
of
like
I'm
out
of
the
loop
a
little
bit.
A
Do
we
have
a
single
like
list
of
things
that
we
need
to
do
to
deliver
this
to
customers?
Do
we
not
want
to
deliver
it
to
customers
for
a
while?
What's
the
plan.
F
So
we
do
want
to
make
this
generally
available
to
customers,
there's
not
a
particular
end
date
and
actually
the
owner
for
okrs
is
avalash
from
the
seg
team.
F
So
we
should
sync
with
him
to
see
what
the
list
of
capabilities
are,
but
there's
definitely
some
ux
cleanup
that
we
need
to
do
like,
for
example,
I
would
want
us
to
complete
the
okr
for
that
modal
to
be
aligned
to
pajamas,
at
least
having
the
list
of
the
deviations
and
making
a
decision
based
on
that,
and
definitely
what
you
mentioned
with
that
create
pattern
just
having
a
path
forward
of.
Is
that
how
we're
going
to
do
it
for
all
work
items?
F
Is
that
we're
working
toward
or
is
it
something
else?
So
that's
definitely
a
decision
point
but
tldr.
We
should
talk
to
avilash
and
our
design
system
team
likely
at
the
end
of
the
quarter
once
we
are
through
some
of
that
ux.
Okay,
our
work,
not
okay,
but
our
goal.
Okay,.
B
So
I
had
a
follow-up
question
on
that,
so,
while
I
know
that
okrs
has
a
product
may
be
under
the
ownership
of
scg,
but
given
that
it
is
all
work
items
underneath,
any
changes
we
do
with
regards
to
its
ux
is
going
to
affect
work
items
in
general
and
so
I
believe
the
ownership
of
that
will
still
remain
with
the
plan
stage.
Yes,.
F
That's
correct:
we'll
continue
to
have
a
collaboration
like
we
have
up
to
this
point
right
where
we
built,
for
example,
comments
and
labels,
and
things
like
that,
some
of
the
shared
components
and
avilash
build
the
okay
are
specific
things.
It
will
continue
to
be
a
close
collaboration
like
that.
D
I'm
just
going
to
link
the
the
roadmap
of
features
that
avalash
will
be
working
on
so
not
specific
to
the
work
items,
kind
of
ux
cleanup,
but
just
for
reference.
So
you
can
see
I,
don't
know
for
sure,
if
he's
planning
on
completing
everything
in
the
viable
portion
of
the
table
before
General
availability.
But
that
gives
you
an
idea
of
the
other
things
that
he'll
be
working
on.
While
we're
working
on
the
kind
of
cleanup
of
work
items
related
stuff.
D
A
Course,
Burger
menu
to
convert
these
into
tasks
appears
in
the
next
table
cell.
A
Have
you
tried
this
like
if
you
mice
over
them
most
over
the
check
boxes
in
the
table
cells,
the
burger
menu
appears
so
I
think
it's
called
The
Burger
menu,
so
I'm
going
to
call
it
that
it
appears
in
the
next
table.
So
I'll
open
an
issue.
D
I
A
K
Hello,
everyone,
my
name
is
Naman
Gala
I
am
based
out
of
India
Mumbai
I
mean
I
stay
nearby
Mumbai,
but
majorly
people
know
Mumbai
and
India.
I
have
around
10
years
of
experience
in
in
product
development,
I
joined,
gitlab
four
months
back
so
I'm
little
new
to
gitlab,
as
in
pages.
So
we
were
previously
in
editors,
created
a
test
team.
K
Then
now
we
move
to
plan
knowledge,
so
basically
I
joined
as
a
go
programmer
and
now
learning
Ruby
as
it's
a
basic
requirement
in
gitlab
I
mean
you
can
ask
me
anything
anywhere.
You
can
bring
me
on
slack.
We
can
definitely
collaborate
and
I'll
send
out.
The
coffee
chat
invites
to
you
all
to
have
a
discussion.
G
H
My
name
is
Casio
I
live
in
Dublin
well
near
Dublin,
Ireland,
yeah,
John
hopes,
land
I've
been
in
git
lab
for
three
years
and
two
months
now,
I
started
in
gitlab
just
before
the
end
of
the
world
in
January
2020
and
the
group.
Import
and
I
stayed
there
for
almost
two
years
and
then
I
moved
to
group
Editor
to
work
in
the
pages
product
where
I
had
to
learn,
go
and
I
actually
wrote
very
little
goal
up
to
now.
H
I
still
writing
a
lot
of
Ruby
and
now
again
I'm
moving
to
Glenn
knowledge
where
I
don't
know
what
I'll
be
writing
but
I'll
be
probably
working
with
a
lot
of
Ruby
and
go
with
pages
and
the
wiki
feature
I'm
very
open
as
well:
pink
Mission,
It
Anyway,
anything
I,
don't
work
in
linear
hours,
I'm
very
fuzzy
on
my
day,
so
I
work
a
little
bit
in
the
mornings
and
then
a
little
bit
in
the
afternoons
and
evenings
and
I
travel
a
lot
so
not
fix
time
zones
as
well.
B
A
J
We're
gonna
start
like
a
guitar,
related
argument
here.
G
Hi
everyone
I'm
Jackie
I've,
been
I
get
loud
now
for
almost
four
years
will
be
four
years
in
June
and
I
have
been
working
on
the
Fulfillment
and
growth
team
up
until
nowish,
so
quite
different
for
me
to
work
on
on
plan,
which
is
a
lot
more
part
of
the
core
product,
whereas
I've
been
working
on
like
trials
and
registrations
and
purchase
flows,
and
things
like
that,
so
I'm
super
excited,
I,
live
in
Austin
Texas
and
what
else
can
I
say
about
me?
G
I
live
in
Austin
I
prior
to
get
love,
I
worked
at
Visa
and
I
also
worked
at
a
company
called
Rackspace,
which
some
of
you
might
know
of
because
they
do
like
they're,
not
hosting
stuffs
and
I.
Have
a
couple
of
dogs
and
I
like
to
cook
and
garden
and
have
a
lot
of
plants.
G
Yeah
yeah
and
Melissa
and
I
worked
together
on
the
same
cloud.
What
was
that
called
reach?
Cloud
portal?
Thank
you
a
long
time
ago,
like
probably
five
more
than
five
years
ago,.
G
L
L
I
think
I
think
that
no
I'm
I'm
Janice
I'm
with
gitlab
for
about
one
and
a
half
years,
a
little
bit
more
I
joined
in
incubation
engineering
and
I
had
the
jumpstack,
seg
and
I
was
working
a
lot
with
on
the
future
of
pages.
So
that's
why
I've
been
moved
to
to
plan
pages
or
yeah
plan
knowledge,
yeah,
I,
hope
I
can
continue
in
that
in
that
role
here,
I'm,
actually
a
full
stack
engineer,
so
working
been
working
with
Ruby
go
front,
end
vue.js.
B
L
Lot
yeah.
L
I'm,
actually
for
for
Hobbies
I'm
I'm,
currently
getting
a
sailing
license.
So
I'm
trying
to
be
able
to
say
old,
sailboat
I
live
in
Hamburg
Germany,
which
is
very
close
to
the
Sea.
L
L
Right
now,
I
sailed
with
a
skipper
on
board
and
he
tells
me
go
left
go
right.
So
my.
J
L
I
was
fine.
The
first
time
I
went
out
was
like,
like
I've
always
done
it.
You
know
I
I
used
to
do
glider
flying
when
when
I
lived
closer
to
the
mountains,
it's
not
a
particular
good
option
up
here.
L
Mean
it's
one
less
dimension
to
work
with
it's
navigation
and
like
the
whole
theory
of
wind
and
stuff
like
that
and
meteorology,
is.
L
L
A
Well,
this
was
really
nice
because
I'm
going
to
share
this
video
with
everyone
who
can't
normally
make
the
Emir
friendly
portion
of
our
team
meeting
so
it'll
be
really
nice
for
everyone
to
get
to
know
most
of
the
new
people
who
are
joining
plan.
We
still
have
I
think
one
or
two
others
himanshu
definitely
hasn't
been
introduced
yet
but
yeah.
So
this
will
be
really
nice.
I'm
gonna
stop
recording.
So
we
can
continue
to
talk,
but.