►
Description
Weekly team meeting from 15 July, 2019.
A
I'm
a
star
because
we've
got
the
hour
actually
Adam
was
supposed
to
join,
but
in
might
incur
during
an
issue.
So
the
goal
was
to
introduce
him
because
we
don't
know
we
don't
introduce
a
new
hire
anymore
in
the
company
hall
and
as
it
was
supposed
to
join
here,
I
just
wanted
me
to
be
none
from
you
anyway.
Just
move
to
to
the
next
items
in
the
agenda,
and
we
go
back
to
to
be
me
if
you
chose
Tomas.
Okay,.
B
Yeah
I
just
jumped
in
line
so
anyway,
making
it
known
to
everybody.
First
of
all,
happy
Monday,
I,
hope
everybody
had
a
great
weekend.
Second
of
all,
we
have
a
lot
of
news
charters
this
month
and
so
I
just
wanted
to
go
ahead
and
call
out
who
they
are
and
what
team
they
are
and
what
seem
they
are
in.
So
we
will
we'll
make
sure
to
introduce
them
within
within
the
slack
channel,
but
for
but
on
this
particular
team.
B
We've
got
Stacey
who
joined
us
a
couple
of
weeks
ago
and
cam,
who
will
be
starting
on
Wednesday
or
at
least
Wednesday
our
time?
Okay,
so
that's
a
both
of
them
are
located
in
the
APAC
region,
which
is
necessitating
some
some
rethinking,
on
my
part,
at
least
for
schedules,
and
how
we
support
team
members
within
that
within
that
those
particular
time
zones
with
an
SCA
I
mean
Adam
I'm,
not
gonna,
steal,
Olivia's,
thunder,
but
also
Moe
joining
last
week.
So
that's
for
this
month
already
and
there's
more
coming
so
I
just
wanted
to
call
it.
B
If
you
see
them
around
slack,
please
don't
hesitate
or
be
shy.
Please
introduce
yourself
say
hello
and
if
you
have
to
if
it
happens,
to
be
convenient
for
you
during
your
tide,
during
your
normal
working
times,
to
have
a
coffee
chat
with,
and
please
do
so
and
so
with
that
we'll
go
on
down
and
I.
Don't
know
who's
got
number
three
in
the
agenda.
A
Information
yeah
so
yeah.
You
can
leverage
the
operation
that
about
this,
where
this
was
explained
in
the
next
and
the
previous
stuff,
meaning
citrus
everything
and
the
issue
was.
We
are
some
fade
pipeline
and
some
of
our
project
and
it
looks
like
nobody
is
aware
of
them
so
on
in
until
we
have
a
great
notification
in
place
for
this
project
and
automated
QA,
you
can
set
up
the
operation
dashboard
to
track
and
monitor
the
project
that
you're
working
on,
and
this
is
very
nd
for
a
quick
overview
about
the
states
and
next
one
is
Philippe.
C
Yeah
sure
thanks
just
wanted
to
remind
you
that
you
need
your
detours
and
client
instruction.
Is
there
if
needed
and
make
sure
you're
up
to
date
because
I,
so
some
arts,
even
our
bit
in
there?
It's
not
only
the
thing
with
the
with
the
camera.
We
don't
care
that
much
about
the
camera
we
optimizing
or
or
meetings
on
YouTube.
So
it's
not
a
really
big
deal
for
most
of
us,
but
the
DRC
might
be
something
so
just.
D
So,
for
the
back
end,
we
we've
been
waiting
our
issues
and
it's
you
know
always
good
to
be
calibrated
on
how
we
weight
those
issues
and
I
sorted
across
these.
These
links
for
four
labels
for
kind
of
a
rough
idea
of
how
one
could
weight
them.
I
guess
they're
kind
of
new,
but
just
the
general
question
was
just
roughly
how
we
weight
them
and
I
think
I
think
there
wasn't
any
disagreement
on
that,
but
and
certainly
discuss
that.
E
Now
so
just
to
give
comb
some
context
to
these
labels.
These
have
been
created
by
create
or
plan
I'm
unsure,
maybe
by
both
in
order
to
facilitate
the
experiment,
because
they
had
a
problem
that
splitting
issues
didn't
work
for
them.
Then
I
put
the
individual
weights
into
the
issue.
Description,
which
always
needs
leads
you
to
need
to
click
into
the
issue,
and
this
is
basically
the
workaround
they
come
came
up
with.
F
E
D
So
right
now
we're
kind
of
hijacking
the
weight
most
of
the
time
for
the
back
end
and
the
front
end
can
weight
it.
So
that's
that's
a
good
discussion
as
well.
This
is
really
just
for
calibration,
but
if
we
want
to
discuss
like,
if
we
want
to
did
are
their
corresponding
front
in
weight
labels
I'm
assuming
IP,
if.
E
B
F
F
I
You
know,
cuz
Fibonacci
I
mean
obviously
the
higher
the
number
the
you
know,
the
the
the
longer
or
more
complex
it's
going
to
be
use
as
far
as
effort
or
complexity.
But
do
we
have
a
cap
for
that
number
right?
So
we
don't
really
understand
what
that
means.
That's
why
maybe
t-shirt
sizing
can
simplify
things
small
medium
large.
You
know,
anyway,
just
food
for
thought
will.
B
Iterate
we
what
we
have
right
now.
What
we're
doing
right
now
is
certainly
not
perfect.
It
is
certainly
a
V
1.1,
it's
the
first
step
at
least
trying
to
understand
capacity
and
may
ends
as
far
as
I
and
as
far
as
what
we're
doing
for
the
throughput
above
and
beyond
velocity
of
Mars
being
merged.
So
in
any
case
well,
we
can
keep
working
on
this
agreed
that
this
needs
to
end
up
in
the
handbook.
I.
B
B
Okay,
all
righty
since
I'm
next,
alright
casting
call
for
brown
bag
sessions,
so
I've
always
heard
these
as
brown
bag
sessions.
I've
also
heard
them
called
it's
chalk
talks
and
things
along
those
lines,
but
and
I'm
stealing
from
the
description
that
is
in
the
epic
that
has
been
filed.
However,
we
have
we
occasionally
run
into
topics
that
everyone
can
benefit
from,
but
do
not
fit
within
the
context
of
a
single
bullet
point
on
in
a
weekly
conversation,
the
examples
that
are
in
the
epic
that
you'll
sees
like
it
could
be
about
how
extends
works.
B
It
could
be
there's
there's
another
one
in
there
and
I
gotta.
Remember
it
as
well
is
worth
a
weekend
happened.
Why
are
we
using
doctor
and
doctor?
Why
do
we
want,
and
why
do
we
want
to
get
rid
of
it?
These
are
some
big
meaty
topics
that
is
useful
for
us
to
understand.
It
is
also
useful
for
us
to
dig
in
and
frequently
we're
going
to
have
someone
with
on
this
new
who's.
B
Gonna
master
one
of
these
topics,
so
this
is
an
epoch
where
I'm,
inviting
please
everybody
file,
issues
on
things
that
you
think
would
benefit.
Everyone
would
benefit
from
that
need
more
breathing
space
than
two
to
three
minutes
in
a
weekly
conversation.
The
intention
is
that
these
will
be
recorded.
They
will
go
up
on
get
lab,
unfiltered
and,
and
that
way
we
can,
we
can
have
these
for
our
own
benefit.
The
team
member
benefits
going
forward
as
we
as
we
dive
into
these
issues.
B
F
E
C
Think
that
the
difference
is
many
the
topic
actually,
the
dive
is
something
very
broad
that
could
last
for
more
than
thirty
minutes,
whereas
in
this
case
it's
something
that
would
be
too
big
just
for
or
weekly.
We
don't
want
to
spend
10
minutes
on
on
one
topic
and
it's
also
something
really
optional
so
compared
to
the
weeklies.
So
it's
something
very,
very
small,
specific,
like
the
extents
or
all
extensions
is
working
in
the
github
sky.
Configuration
make
sense,
yeah.
F
B
C
Sorry
I
would
just
say
also
that
the
audience
might
be
a
bit
different,
the
deep
dive,
our
our
January
for
the
world
company,
whereas
these
provocations
are
more
important
or
the
goal
is
to
raise
the
bar
in
the
team,
not
especially
in
in
the
company.
So
we
can
be
very
specific
on
what
we're
doing
insecure.
Instead
of
you
know
getting
very
I'll
over
with
with
other
topics
that
make
sense.
We
all.
H
B
Then
I'll
take
the
floor
back
sorry
Kenny,
you
win,
you
go
for
it.
I
would
say.
That's
awesome,
it's
great
in
that.
Yes,
yes,
more
feedback,
the
better.
We
appreciate
it
all
right,
I
wanted
to
go
ahead
and
broadcast
my
intended
work
schedule
none.
This
is
not
an
expectation
of
everybody.
However,
as
we
mentioned
earlier,
we
now
have
a
pact
based
employees
and
I'm
trying
to
find
a
way
to
to
provide
as
good
an
employee
experience
as
I.
B
Possibly
can
so
I'm
not
want
to
go
ahead
and
let
everybody
know
this
is
what
I'm
planning
to
do
these.
These
are
Eastern
u.s.,
Eastern,
Time,
so
East
Coast
time,
so
what
I
will
be
doing
is,
instead
of
inviting
people
to
watch
a
recording
of
us
talking
or
weeklies
I'm,
going
to
be
repeating
these
on
Monday
evenings
so
Tuesday
morning
for
those
that
are
in
Australia
or
the
Philippines,
and
also
going
ahead
and
conducting
one-on-ones,
and
there
will
be
a
second
coffee
chat
scheduled
in
the
in
u.s.
evening
times.
B
B
So
these
will
be
broadcast
on
the
secure
team
channel,
a
secure
team
calendar
as
well
so
that
you'll,
so
that
everybody
will
have
the
option
of
attending,
but
at
the,
but
it's
specifically
aimed
for
a
pack
based
employees.
That
way
we
can
provide
as
good
an
employee
experience
as
possible.
So
just
let
anybody
know
what
my
intended
work
schedule
is
that
way
if
you're
looking
for
me,
this
is
this
is
what
up.
F
I
just
want
to
say,
I
know,
I,
love
that
this
team
is
continuing
to
do
ongoing
grooming
throughout
the
iteration,
and
so
I'm
I
have
this
board.
This
is
my
de
facto
board
for
scheduling
and
prioritization.
There's
still
a
couple
of
places
where
it's
buggy
in
terms
of
stickiness
of
prioritization,
but
I'm
going
to
maintain
this
board
as
a
planning
board.
So
you
can
look
ahead
at
like
12.3
and
12.4
and
know
that
it's
there
and
prioritize,
and
so
that
also
means
and
I've
said
this
repeatedly.
F
The
the
board
prioritization
is
not
a
great
place
for
having
a
discussion,
but
please
don't
let
that
limit.
The
fact
that,
like
oh,
this
doesn't
make
sense
that
this
is
prioritize.
This
way
feel
free
to
comment
to
me
and
slack
or
other
places
that
this
should
be
ranked
differently
or
you
have
an
opinion
about
it.
This
isn't
like
product
throws
a
prioritization
out.
It's
just
really
hard
to
have
a
collaborative
discussion
about
prioritization
in
our
tool,
but
please
don't
let
that
limit.
If
you
want
to
have
a
discussion
having
one.
I
All
right
so
I
got
the
next
one
which
is
and
I
didn't
get
it
in
fast
enough
on
the
list
where
we
were
talking
about
new
people,
starting
so
Seth
burgers
starting
tomorrow,
he
will
be
another
back-end
manager
and
I
believe
he's
going
to
be
taking
over
dynamic
analysis.
So
I
just
thought
I'd,
let
everybody
know,
since
we
don't
have
the
the
announcements
anymore.
So.
B
F
A
Sorry
Adam,
my
bad
I,
it
looks
like
I
gave
you
the
wrong
link
to
zoom
chat.
That's
okay!
It's
my
fault
here
eventually,
so
yeah,
please
welcome
Adam
as
terming
as
Thomas
Edison
in
DC
ATM.
So
could
you
please
introduce
yourself
to
the
team
where
you
were
before
gitlab,
where
you
wanted
to
join
the
team
where
you're
located
and
what
you
like
to
do
in
your
spare
time.
Sure.
J
So
my
name
is
Adam:
I
am
living
normally
in
Sydney
Australia,
but
for
now
I'm
in
Canada
visiting
my
parents
were
emergently
from
and
yeah
it's
great
to
be
part
of
the
team.
I
was
working
for
a
company
called
Westfield
before
this,
which
was
a
large
retail
shopping
company,
doing
identity
management
using
go
and
before
that
Ruby
on
Rails
I'm
excited
to
be
joining
gitlab
I
really
like
the
product.
We
spent
so
much
money
in
so
many
hours.
Doing
very
similar
things
to
you
know
what
the
the
get
loud
product
is.
J
So
it
seems
like
it's
a
really
useful
system
and
I'm
excited
to
be
on
the
secure
team,
because
I've
been
getting
more
and
more
into
secure
aspects
of
software
development.
In
my
spare
time
when
I
lived
in
Canada
I
used
to
enjoy
snowboarding,
but
now
since
in
a
Sydney,
it's
mostly
being
on
the
beach
and
I
play
a
lot
of
beach
volleyball.
So
yeah.
That's
me.
A
J
B
Righty
with
that
we'll
go
ahead
and
close
up
shop,
listen
anybody
has
any
last-minute
additions
to
the
agenda,
all
right
hearing,
nothing!
Thank
you.
Everybody
for
your
time
appreciate
it
do
not
forget
backlog
grooming
tasks,
please,
let's
keep
those
on.
There
are
more
in
the
list
than
there
were
last
week
because
there
were
some
items
that
are
just
slipping
out
of
12-1,
so
they've
been
put
in
12
and
we
never
put
weights
on
them.
So,
therefore
we
need
to
groom
those
as
well.