►
From YouTube: Plan group weekly 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).
B
C
So
I
just
wanted
to
integrate
Valmer,
and
this
is
his
first
meeting
with
the
plant-eating
and
now
he
is
joined,
as
most
of
you
know
like
is
joining
the
quality
team
as
senior
test
automation,
engineer
and
working
closely
with
our
team
and
Elmo.
Do
you
want
to
just
tell
a
few
words
about
yourself,
yeah.
D
Sure
so
yeah,
first
of
all,
I'm
very
glad
to
be
part
of
the
team
and
they
have
been
working
with
software
test
automation
since
2009
and
quality
assurance
in
general,
since
2004
so
I
think
they
have
some
experience
and
I
am
willing
to
to
help
us
to
have
a
better
product
and
yeah
I.
Imagine
that
they
will
be
working
sometimes
helping
things
specifically
specifically
to
the
plan
team.
Sometimes
when
were
like
QA
engineering
stuff,
well,
yeah
I'm
very
happy
to
be
here.
B
B
Yes,
sorry
just
took
me
a
second
to
find
a
mute
button.
Yes,
so
I
created
an
issue
for
the
next
group
conversation,
the
slides
I
just
marked
down
in
that
repository,
so
I'm
going
to
create
slides
for
the
basic
outline
I
put
there
and
then
because
it's
a
get
lab
pages
site,
but
we
don't
have
review
apps
to
get
lab
pages.
I'm
just
gonna
go
ahead
and
merge
those
initial
slides
and
then
we
can
change
them
from
there.
B
Basically
so
I'll
ping
people
either
in
the
mode
request
or
in
the
plan
channel
or
both
if
I,
if
I,
if
I,
really
want
a
response
from
you
over
the
next
week
or
so,
and
then
we'll
have
the
group
conversation
on
Tuesday.
The
format
has
changed
so
that
we
don't
actually
present
the
slides
at
all,
so
they
probably
need
to
be
a
little
bit
wordy
than
they
have
been
in
the
past.
Either.
B
A
B
Pedro
yeah
you've
been
away
yes,
so
the
new
format
is
that,
for
the
group
conversation
the
slide,
every
group
conversation
shares
an
agenda
Google
Doc
and
in
the
you
know
today's
group
conversation.
The
slide
should
be
linked
like
before
the
meeting
of
course
like
normal,
but
the
expectation
now
is
that
everybody
just
reads
the
slides
in
advance
and
then
the
group
conversation
meeting
time
is
entirely
for
questions.
There
is
no
question
section
at
the
end
after
the
presentation.
It's
all
questions.
There
is
no
presentation.
B
I
did
suggest
at
one
point,
but
I
haven't
followed
up
on
it
about
just
making
the
group
conversation
slides
blog
post,
because,
if
we're
not
presenting
them,
we
could
just
you
know,
make
them
prose,
but
haven't
got
around
to
that
yet
and
I
don't
want
to
do
that
this
time,
because
I'm
lazy
and
it
easier
to
write
flies
than
destroy
goalposts.
So
gonna
not
touch
that
for
now.
Thanks.
A
A
Voting
again
and
and
people
and
you're
new
to
be
one,
people
are
new
to
you,
but
I
wanted
to
encourage
everybody
to
participate
in
a
group
conversation
in
the
past,
so
some
history
long
time
ago
we
had
what
we
were.
They
were
not
called
food
conversation.
They
were
called
functional,
something
updates
a
group.
A
A
Just
dis
contribute
and
also
don't
leap
or
Sean
to
approve
your
change
in
the
merge
request,
just
just
like
just
just
put
it
and
don't
ask
for
permission
and
and
just
put
things
through
and
then
we'll
fix
them
for
Monday.
So
so
please
contribute
thank
you,
and
so
sean
has
just
been
pushing
us
in
the
great
format.
I
think
we're
one
of
the
only
two
groups
that
does
it
using
this
format
instead
of
like
Google
PowerPoint,
which
is
really
awesome,
I
think
so
so
please
participate
in
every
way
you
can
on
to
your
ex
people.
F
F
E
Yeah
so
I'm
in
Peru,
I'm
now
but
I
mean
for
one
year
Alexandre
and
also
Donald
I
mean
I
already
talked
with
Alexis
yesterday,
so
I'm,
a
UX
designer
at
plan
I've
been
in
parental
leave
for
the
past
one
month
and
a
half
which
is
almost
six
months
in
get
lap
time.
So
there's
a
lot
of
catching
up
to
do
so
many
new
faces
when
I
left
for
Patera
parent
parental
leave.
We
were
400
people
and
now
we're
500
people
in
the
company.
So
yeah.
E
It's
really
things
go
fast
here
and
yeah
I'm
I'm,
mostly
working
on
the
project,
management's
features
and
Annabel
working
on
portfolio
management,
and
now
we
have
Alexis
on
the
team,
which
is
great
and
we're
going
to
be
able
to
do
even
more
work
and
more
awesome
work
and
have
a
better
user
experience
for
plan
so
yeah.
That's
me:
okay,.
F
G
Yeah
I
am
in
Chicago,
like
I
mentioned
a
little
bit
earlier
as
a
designer.
My
background
is
actually
in
advertising.
I
started
in
advertising.
I
was
in
accounts,
which
is
basically
pretty
close
to
UX
research,
but
it
was
kind
of
a
bummer.
It
was
kind
of
soulless
just
like
selling
to
people,
so
I
went
back
to
school
about
my
MA
and
human-computer
interaction
and
I've
just
been
doing
kind
of
product
design.
G
Ever
since
my
last
job
was
I,
start
up
in
Chicago
called
sprout
social,
so
I've
been
mostly
working
like
analytics
products,
doing
a
lot
of
visualizing
data,
so
I'm
excited
to
do
something
a
little
bit
different
and
I've
never
worked
remote
before
so.
This
is
also
different,
so
yeah
excited
to
work
with
y'all
it's
my
eighth
day.
So
it's
only
going
up
from
here
and
we're
gonna
get
more
and
more
involved
that
I'm
really
excited
about
that.
Otherwise
yeah.
F
So
that's
exciting,
so
the
next
part
of
the
agenda
is
discussing
how
we're
gonna
split
up
work
amongst
the
three
of
us
and
how
we're
going
to
collaborate.
I
mentioned
that
for
a
while
I
was
working
mostly
on
portfolio
management
features.
Well,
page
I
was
handling
project
management,
like
you
just
said,
but
now
we
have
three
so
Pedro.
Do
you
want
to
talk
about
what
you
wrote
sure.
E
Maybe
it
might
make
sense,
just
slowly
assign
her
some
issues
that
have
small
impacts
and
and
I
don't
know
if
we
already
have
a
lot
of
issues
for
the
certify
area
or
the
certified
group
and
if
so
I
mean
just
slowly
pinger
and
involve
her
so
that
she
has
enough
time
in
the
next
few
milestones
to
understand
how
we
work
and
all
of
that.
So
in
terms
of
splitting
up
work,
I,
don't
think
we
have
like
a
big
problem
there
or
not
necessarily
a
problem,
but
something
that
we
need
to
optimize.
F
H
Well,
yeah
I
mean
for
me
was
that
I
wanted
to
contribute
like
right
away
cos
that
helped
me
to
kind
of
set
up
the
environment
and
all
the
stuff
that
I
guess
like
it
took
me
a
couple
weeks
to
freely
kind
of
dive
a
little
bit
into
into.
What's
going
on
first
week
is
really
a
lot
of
information
coming
down
on
you
and,
and
you
feel
at
least
for
me.
D
D
It's
it's
impossible
to
read
through
all
all
the
things
that
are
there
in
just
one
week,
because
yeah,
because
you
go
to
a
link
that
links
to
other
things
that
you
want
to
read
as
well,
and
it's
like
I
I,
think
I
will
be
able
to
to
finish
my
own
body
initiative
this
week
and
then
yeah
I'm,
looking
forward
to
start
contributing
more
in
terms
of
like
putting
my
hands
on
the
code
and
things
that
but
yeah,
that's
my
feeling.
So
far.
H
H
G
Yeah
I
think
I'd
like
to
I
kind
of
run
it
in
the
doc
just
kind
of
understand
the
full
scope
of
what's
going
on
and
plan
first.
So
I
like
the
idea
of
me,
helping
out
with
little
things
here
and
there
like
across
everything
before
I
start
kind
of
like
funneling
down
into
one
area,
I'm,
not
sure
how
fleshed-out
certifiers
yet
Viktor.
G
Maybe
you
could
speak
to
that
more
but
and
I
also
might
know
a
little
more
after
talking
with
Christie
I
haven't
had
a
one-on-one
with
her,
yet
my
manager
so
I
think
it's
kind
of
to
be
continued
for
me,
but
yeah
I'd,
like
to
kind
of
just
get
a
better
feel
for
everything.
E
Yeah
I
think
in
the
first
weeks
as
well,
Mia
was
saying,
is
doing
all
of
the
onboarding
tests.
I,
don't
think
you'll
have
a
lot
of
time
to
do
actual
work
on
issues
for
for
your
stage,
but
I
mean
in
I'm
expecting
that's
all
ready
for
the
next
milestone.
So
in
one
month
from
now,
you
already
have
a
couple
of
issues,
at
least
to
like
get
your
feet,
wet.
A
A
So
there's
team
planning,
Enterprise
planning
and
certified
and
so
certify
I
would
not
worry
about
at
all
for
any
new
person
at
your
lab
pretty
much
and
once
we
are
ready
to
move
forward
with
that,
then
I
think
we
can
pick
that
up
because
it's
not
it's
not
super
high
priority.
Right
now
and
I
wanted
to
comment
what
you
said:
Pedro
regarding
picking
up
specific
tasks,
I'm,
sorry
I
think
for
Alexis
I
would
recommend
that
you
can
do.
A
However,
you
want
to
learn
so
I
mean
we
just
heard
from
you
from
well
Mary
from
Alexandria,
and
it
seems,
like
everybody,
has
slightly
different
ways
of
learning
and
getting
comfortable,
which
I
think
is
fine.
We
don't
I
mean
it's
literally
just
a
couple
of
weeks
up
to
a
month
and
so
everybody's
going
to
be
up
to
speed
really
quickly,
so
I,
don't
think
we
have
to
dictate
a
process
that
much
so
what
I
would
recommend
is
between
Pedro
and
animal.
A
You
you
folks,
can
work
with
Alexis
on
on
specific
assign
work
like
you
said,
but
I
would
also
recommend
Alexis
you
work
with
them
and
if
you're
interested
you
can
say
like
can
you
know
to
show
me
some
ongoing
work?
That's
interesting
and
I.
Could
you
know,
offer
some
feedback
along
the
way,
but
you
don't
have
to
be
assigned
to
deliver.
A
Unburn
work
no
I'm,
like
Alexandra
I,
like
I,
like
doing
work
as
a
way
to
learn,
because
it
forces
me
to
because
I'm
more
a
more
reassured,
maybe
I
just
lacked
assurance
and
I'm.
Very,
not
that's,
not
what
I'm
not
I'm,
not
unsure
I'm
unsure
of
myself
until
I
can
produce
some
output
and
can
validate
it
and
when
I'm
just
reading
things
I'm,
not
certain
that
I'm
learning
something
and
I
feel
uncomfortable.
So
for
me,
the
best
way
to
learn
is
actually
to
do
something.
A
E
So
this
was
I.
I
didn't
talk
with
anyone
still
about
this,
because
it
was
very
late.
My
afternoon,
I
had
my
one-on-one
with
with
Christy
the
UX
director
and
she
shared
some
concerns
about
what
we
were
going
to
do
with
create
in
the
meantime,
because
we
don't
have
any
wax
designers,
they're,
just
sue
left
and
we're
hiring
I.
Think
it's
going
to
be
three
people
until
the
end
of
the
year.
E
We
have
one
person
that
I
think
will
start
soon,
but
none
of
the
less
it's
one
of
the
most
mature
stages
that
we
have
in
the
product
and
not
having
someone
there
with
experience
in
the
product
and
I
think
it
will
be.
It
will
take
longer
for
those
people
that
join
to
actually
start
contributing
in
a
meaningful
way.
E
So
my
suggestion-
and
it's
something
that
we
need
to
discuss,
it's
not
final
or
anything.
It's
just
a
suggestion.
An
idea
is
for
me
to
move
there
and
become
the
interim
UX
designer
and
creates
until
the
first
create
UX
designer
has
I
mean
fully
onboard
and
like
they
feel
comfortable,
and
maybe
they
at
least
they
feel
comfortable
enough
of
about
having
another
person
joining
the
team,
the
second
UX
designer
and
onboarding
that
person
you
know
so
like.
I
How
to
fish
so
they
can
fish
on
their
own,
essentially
Bichir.
My
immediate
question
is
I
was
under
the
impression
that
Dimitri
was
gonna,
be
handling
that
hand
over
is
the
idea
to
just
like.
Have
you
and
Dimitri
help
out
on
the
and
the
minterm
meantime?
Or
would
you
just
be
coaching
Marcel
that
the
new
new
hire
yes.
E
E
They
sorry
the
internship
for
for
product
manager,
and
he
is,
as
you
were,
saying,
also
doing
as
a
backup
designer
for
creates,
but
talking
with
Christy,
it's
not
something
that
she
was
willing
to
do
to
move
the
Metreon
have
him
more
assigned
to
create.
She
was
more
comfortable
if
I
were
to
do
that.
E
I
I
E
I
mean
it's:
it's
not
I,
don't
think
it's
ideal
solution,
but
given
like
all
of
the
resources
that
we
have
and
the
needs
I
feel
like
if
I
were
to
be
more
in,
create
I
mean
I
would
still
be
involved
and
tried
to
help
in
any
way.
I
can,
with
things
in
plan,
not
doing
the
issues
and
I'm
being
super
involved
that
at
least
knowing
what's
happening
in
my
opinion,
every
now
and
then
I
think
Annabelle
is
I,
think
she
she
is
comfortable
enough.
I
mean
I
was
one
month
and
a
half
away.
F
I
A
E
D
Can
go
first,
okay,
okay,
I
can
go
then
so
yeah
I
just
thought
of
explaining
a
little
bit
about
the
way
I
used
to
work
so
that
you
can
know
like
how
I've
been
using
to
work
at
least
and
and
then
we
can
align
if
this
is
the
right
way
to
go.
So
as
software
test
automation,
engineer,
I
I
would
like
to
consider
that
the
test
automation
is
not
just
a
responsibility
of
the
the
people
working
in
the
quality
department.
E
D
Not
saying
you're
not
collegiate
on
me,
but
I
like
to
be
involved.
You
know
I,
like
in
my
previous
job,
I'd,
be
not
just
reviewing
testing
code
but
I,
also
like
front-end
and
back-end
code,
so
yeah,
just
please
involve
me
and
yeah
I
like
doing
their
programming,
at
least
in
the
beginning
as
well
to
get
used
to
the
product.
So
every
involvement
in
like
if
you
were
working
on
something
that
is
completely
new
and
it's
not
very
simple,
then
I
think
two
hats
can
think
better
than
just
one.
D
I
I
We
need
that
involvement
to
happen,
anyways
to
make
sure
that
you
understand
the
feature
that
you're
writing
the
complete
test
for
everything
and
we've
done
that
in
the
past,
but
it's
usually
a
little
bit
more
loose,
but
maybe
that's
a
good
way
to
experiment
going
forward
to
see
how
we
can
benefit
from
those
things
for
more
exchange,
so
I.
Thank
you
for
that.
In
fact,
for
that
intro.
A
Andre
so
wanted
to
mention,
because
last
time
we
chatted
on
this,
this
weekly
call
that's
becoming
bi-weekly.
We
said
that
we
wanted
to
do.
Custom,
workflows
and
I
wanted
to
mention
that
I
want
to
apologize,
because
we
keep
switching
I
mean
I,
don't
apologize
for
changing
it,
because
I
don't
think
you
should
slow
down
until
that,
but
apologized,
nonetheless,
that
we
have
to
you
know,
endure
this
cost
of
context.
A
Switching
at
gitlab,
but
I
think
it's
a
good
thing
overall
and
so
last
time
we
chatted,
and
especially
since
I
asked
animals
specifically
to
really
jump
on
it,
and
then
you
know
within
one
of
these
cycles
of
these
calls.
Now
we're
not
doing
it
so
I
want
to
thank
Annabelle
as
well
for
quickly
switched
over
in
terms
of
design
and
also.
A
A
And
then
so
within
the
product
organization,
there's
the
chief
product
officer
and
that
Sid
who's
also
known
as
the
CEO.
So
until
that
we
don't
have
a
chief
officer,
you
have
said,
don't
know
if
it's
in
the
handbook
I
think
it's
in
the
handbook
somewhere
where
it
says.
If
you
said,
people
are
like
new
and
looking
ahead
book,
so
there's
another
rabbit
hole
for
you
to
look
at.
It
says
somewhere
in
our
leadership
thing
where
we
split
our
organization
in
terms
of
product
and
operations,
I,
think
and
then
in
or
some
like.
A
Maybe
the
operations
are
a
product
and
like
sales
and
forget
whatever,
but
anyways
you'll
notice,
like
within
the
product
development
side
of
the
organization.
We
don't
have
c-level
people
right.
We
have
VP
of
engineering,
we
have
VP,
we
go,
have
the
VP
of
Product.
We
have
a
head
of
product
right
now,
it's
sort
of
confusing
that
were
a
different
time,
but
we
have
I
think
we
have
VP
of
other
things
like
alliances,
I
guess,
but
then
we
have
like
chief
revenue
officer
via
chief.
What
else
do
we
have
so
anyways
I'm?
A
Clearly,
not
remembering
all
this,
but
it's
just
interesting.
If
you
look
at
how
many
were
in
the
organization
anyways,
so
mark
Cusack
reports
to
Sid
and
then
I
reported
him
and
direct
me
via
a
director,
and
so
our
leadership
in
product
is
heavily
involved
in
our
product
day
to
day
product
decisions
for
better
or
worse.
So
it's
a
bad
thing,
I
think.
Sometimes
you
guys
I
think
we're
being
micromanage
a
little
bit
too
much,
because
then
we
can
move
as
quickly
and
we're
not
empowered
to
make
all
the
decisions
that
we
can
make.
A
But
I
think
it's
also
a
good
thing,
because
our
leadership
is
actively
involved
in
our
product,
which
is
not
something
you
see
in
many
organizations,
and
so
you
get
the
benefits
of
alignment
direction
and
vision
to
a
very
low
detail.
So
so
it's
it's
scary
and
exciting.
That
Sid
starts
commenting
a
new
issue
and
then
wants
something,
but
you
know
try
to
see
the
good
side
of
it.
I
mean
it
doesn't
happen
for
every
single
thing,
fortunately
so
and
I
think
it
happens
for
very
strategic
thing.
A
A
Is
gonna
be
design,
design,
artifact
design
thing,
but
anyways
there
was
a
long
conversation
about
whether
that
should
be
I.
Don't
know
what
really
I
don't
know
what
the
word
is,
but
it's
a
word
but
I
last
time,
I
checked
the
decision
was
that
it's
going
to
be
a
separate
abstraction
and
then
I'm
just
bringing
up
that.
A
There's
many
of
these
conversations
going
on
at
the
bar
and
so
I
think
that
custom
workflows
should
be
a
their
own,
so
customer
close
leaving
the
ballast
tree
management,
but
custom,
workflow
stages
or
states
I
think
should
be
their
own
things
and
they
should
not
be
built
on
top
of
labels.
I've
made
that
case
multiple
times,
so
this
is
what
I
I
believe
is.
Is
the
correct
solution?
A
Well
I'm
correct
in
the
sense
that
I
think
it's
it's
the
best
decision,
given
everything
that
I've
looked
at
everything
that
this
team
has
told
me
everything
that
I've
looked
at
everything
that
I've
thought
about
in
terms
of
risk
in
terms
of
advancing
a
product
in
terms
of
best
decision,
short
term,
medium
term
and
long
term.
I
still
think
that
does
the
best
decision.
Marx
disagrees
and
I
don't
think
we
need
to
agree
to
proceed,
but
he's
also
hasn't
said,
like
you
must
do
this
Victor,
so
I
think
at
good
lab
I.
A
A
Until
that
happens,
I
certainly
don't
see
in
the
handbook,
but
I
just
wanted
to
mention
that
that
is,
though,
that's
the
case
right
now
that
there's
a
disagreement,
and
so
we
said
the
best
way
forward
is
that
we
just
work
another
feature
that
may
or
may
not
contribute
to
custom
workflows
in
the
future
and
make
evaluations
so
I
wanted
to
open
up
to.
If
there's
any
other
comments
or
discussion.
Because
again
it's
like
a
big
change
and
it's
that
urgent
change,
so
I.
G
A
I
think
my
internet
is
not
working
very
well,
so
any
other
comments
or
questions.