►
From YouTube: [Bi-Weekly] Status Devs 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).
C
C
A
A
A
A
A
I'm
sorry,
having
someone
to
door
so
I
have
to
get
this
I
mean
it's
it
four-wheel.
It's
like
all
other
calls.
We
just
go
through
it
steams.
If
there's
an
updates
and
then
there
is
magenta
eirick.
Sorry
I
thought
this
I
thought
this
was
already
handed
over
because
I
talked
I
talk
to
you
a
bunch
of
times
and
I've.
Also
painting
people
up
some
bit
confused
too,
but.
A
D
Again
give
a
short
update
yeah,
so
for
you,
a
with
that,
we
have
Andrew
who's
working
on
Moochie
account
from
status
react
side
along
with
some
changes
from
Andrea
to
use.
Moochie
account
functions
instead,
simple
accounts
from
user
accounts
and
this
PR
waiting
for
this
pair
to
be
merge
to
continue
the
integration
of
moody
accounts.
This
time
on
studies
go
side.
D
There's
been
a
lot
of
fixes
for
the
release
but
as
discussed
earlier,
where
we
won't
release
yet
because
there
is
a
bag
with
forbids
bills
and
it's
required
for
the
Play
Store
after
first
up
okay.
So
we
don't
want
to
take
the
risk
really
something
now
and
then
being
trapped
and
not
able
to
update
because
of
the
64.
It's
buggy.
So
that's
one
of
our
priority
to
fix
the
to
find
solution
to
a
64-bit
but
I
think.
F
Yeah
sure
I
can
give
a
quick
update
about
key
card
so
for
the
integration
within
the
app
Dmitry
is
working
on
it.
We
are
almost
done
it's
a
matter
of
days
now.
What's
left
to
do
is
to
the
login
and
the
own
body.
The
login
Dimitri
has
released
the
pr
last
week
it's
waiting
for
reduce
by
the
way
and
for
onboarding
I
think
once
the
recovery
PR
will
be
merged.
F
We
have
a
quick
integration
of
card
and
we
want
to
also
change
the
pin
screen
that
we
use
in
key
card
embodying
they,
then
with
the
ones
from
the
login
PR.
But
that's
really.
These
are
quick
things,
so
we
are
yeah,
it's
a
couple
of
days
from
having
the
key
card
integrated.
Now,
apart
from
that,
we
are
progressing
on
the
iOS
Swift
SDK
McHale
is
working
on
that
and
we
have
a
repo
setup.
F
B
C
Token
economic
stuff
we're
gonna
shift
to
starting
to
discuss
the
economics
around
the
teller
network.
As
this
you
know,
status
strategist
shift
seems
reasonable
to
move
towards
things
that
are
more
focused
on
the
status
network
as
a
whole.
Have
a
good
transition
and
doing
things
like
that,
and
then
from
there
we'll
move
to
other
things.
Barry
posted
an
article
on
f3
search
around
her
rate,
someone's
interested
in
kind
of
how
you
evaluate
these
types
of
things.
B
G
Sure
so
we
essentially
were
yeah
those
two
things.
One
was
that
we're
really
just
talking
up
things
and
watching
lots
of
documentation
by
browns
checking
the
code
with
different
tools,
just
a
lot
in
preparation
for
four
external
security
audit.
So
we
have
the
proper
documentation
and
also
address
whatever
issues
they
could
come
up
with
initially
and
then,
after
that,
we
we
have
not
like
a
new
designer
and
did
a
lot
of
improvements
or
we
actually
implemented
some
of
those
improvements.
B
B
A
A
Also,
we
started
trying
to
get
NIM
into
into
console
clients,
so
we
can
actually
use
the
whispering
foundation
of
in
Nimbus,
and
you
said
to
talk
through,
says:
consultant
starts
happening
as
well,
I
think
that's
mostly
it
for
protocol
and
then
I
guess
just
sorry.
It's
my
bad
in
terms
of
handle.
If
this
meeting
so
sorry
for
putting
you
on
spotted
on
me.
Thank
you.
So
much
for
the
help
I
guess
is
to
any
other
swamp
that
hasn't.
Given
you
update
and
something
that
people
feel
like
like
they
want
other
people
to
know
about.
A
D
Yeah
but
then
I
just
saw
that
you
see
the
new
one
right,
so
I
I
could
be
pacing
and
then
I
lost
the
page.
Okay
I
got
the
basement,
so
why
did
I
put
first
technique
yeah,
but
instead
that
I
have
much
to
say
about
it,
but
more
because
there
is
a
discussed
post
about
it.
I
don't
know
if
everybody
else
in
it,
but
there
is
a
discussion
about
hiring
technique
and
there
is
a
novel
position
in
on
the
website
and
Andrea.
D
H
So
can
I
just
qualify
a
bit
my
opinion,
because
if
you
read
the
post
carefully,
I,
never
I,
don't
think
the
problem
is
that
we
are
hiring
attack
leader,
never
oppose
the
decision.
So
what
I
have
my
concern
was
not
about
whether
we
want
to
or
whether
is
needed,
to
hire
a
technique.
That's
discussion.
We
can
have
if
needed,
it's
more
about
the
process
and
the
fact
that
we
are
hiring
attacked
heed
to
solve
a
problem
that
hasn't
been
stated
in
the
team.
As
far
as
I'm
concerned,
I
never
heard
this
kind
of
problem,
sir.
H
The
problem
is
that
Camilla
King
looks
like
a
solution
was
handed
down
weed
out
a
disc,
a
proper
discussion
and
I
think
that
is
more
concerning,
because
it
means
that
we're
not
the
current
problems
that
the
team
airs,
which
some
people
have
you
know
clearly
may
be
identified.
They
have
not
stated
to
the
team
and
so
I
think
it
looked
to
me
like
we're,
trying
to
look
for
a
silver
bullet,
but
until
we
acknowledge
what
the
problems
are
we
make
in
public,
we
understand
how
to
fix
them.
A
So
I
mean
I
I
have
some
thoughts,
but
this
is
a
simple
example.
The
fact
that
that
Igor
left-
and
it's
not
coming
back
like
I-
think
those
sorts
of
things
he
was
doing.
That
was
very
valuable
in
terms
of
being
sort
of
the
point
person
for
the
core
team
and
being
sort
of
having
native
mobile
experiences.
So
on
and
I
think
both
of
those
two
things
are
things
that
we
are
lacking
with
him,
leaving
and
I
haven't
in
either
area.
A
H
It
is
a
bad
feeling,
but
I
mean
if
you
I
mean
that's
one
of
the
aspects
which
clearly
I
agree
that
you
know
that
we
need
some
more
technical
expertise
in
that
department
to
know
for
sure
whether
I
mean
the
two
things
that
are
completed.
So
they
were
saying
that
you
know
we
lack
of
technical
people
in
these
and
we
want
to
take
that
into
two
things.
You
know
a
person
might
have
both
qualities,
but
not
necessarily,
but
you
know
like
if
you
want
more
expertise
in
Android,
you
can
type
some
technically
competent
in
Android.
A
H
Problems
that
clearly
that
were
for
most,
like
you
know,
people
like,
for
example,
has
to
reply.
There
was
very
little
mention
of
DS.
You
know
she
mentioned
very
different
problems.
Estimates
you
know,
like
code
complexity,
these
kind
of
things
which
you
know
like
I
think
is
something
that
needs
to
be
dealt
with
in
the
team
as
well.
First
and
then
you
know
again,
you
know,
like
I,
raised
some
issues
about
the
hiring
process.
Current
is
very
vague
and
you
know
like
again,
team
team
changes
have
been
very
opaque
on
the
town.
H
B
H
H
My
side
I
think
you
should,
we
should
just
improve.
You
know
identify
where
we
lack
I
mean
Tim
leader,
Tim,
Lee,
discussion
aside.
That's
again,
you
know,
I
think
it
might
be
worth
hiring
might
not
be
what
definitely
we
did
some
work,
so
you
should
identify
where
we
laugh
and
what
the
current
problems
are
as
identified
by,
for
example,
you
Rachel
by
aster,
which
are
things
that
do
need
to
be
addressed,
and
so
we
can
start
addressing
those
points.
Somehow
yeah,
because
definitely
I
mean
even
if
we
have
a
team
need.
H
E
Has
the
point
of
having
yeah
half
the
point
in
having
the
team
leaders
to
help
to
enforce
certain
changes?
Behavioral
changes
within
the
team,
Frank
I'm,
just
supporting
a
team
in
general
so
and
something
like
we've
discussed
just
recently,
I
mean
today
or
we
have
certain
pain
points
in
our
process.
Like
the
the
estimation
of
ours,
for
instance,
is
it's
not
ideal
right
now
and
aundrea
and
I
have
have
discussed
this
a
little
bit
privately
one-to-one
and
we're
planning
to
talk
later
this
week
about
what
we
could
do
to
improve
development
process?
E
B
C
If
you
feel
as
though
there's
something
that
you
can
do
or
would
like
to
do
then
say
something
to
somebody
on
picking
up
that
responsibility,
whether
or
not
that
happens
after
we
bullet
point
all
the
things
that
we're
lacking
currently
and
then
we
can
start
to
look
at
what
role,
what
roles
could
potentially
fill
those
things.
But
if
we
think
internally
and
you
feel
like
there's
something
you'd
like
to
do-
you
should
say
something
to
someone
and
and
so
that
we
can.
We
can
strata
to
strategize
around
that
and
allow
for
me.
A
You
know
that
will
one
step
further
I'd
like
just
do
it
like
II
go
left
left
a
month
ago
and
I
don't
know
it
seems
it
seems
like
there's
been
certain
things
were
not
been
able
to
do
due
to
lack
of
native
experience
and
and
and
so
on
so
I
mean
I.
Guess
like
there's.
No,
it's
the
role.
That's
put
up
here
like
it's.
Not
this
like
a
super
privilege
thing
is
not
it's
not
like
I'm.
A
Like
anyone
is
free
to
take
up
the
responsibility
right,
yeah
there's
no,
no
one,
nothing
blocking
my
from
this
there's,
no
specific
access
or
anything
right
like
and
in
terms
of
these,
outside
of
the
core
cause
where
this
could
be
brought
up.
I,
don't
know
to
what
extent
has
been
brought
up,
but
it's
been
discussed
in
in
janitors
and
my
history
to
join
those
cause
as
well,
and
all
the
corners
are
public
and
and
then
draw
ad
hoc
conversations,
I'm,
not
sure
exactly
in
terms
of
making
Bo
transparent,
I
agree.
A
A
H
Mean
I
think
yes,
I
mean
is
the
problem
is
a
huge
deal
if
you
have
a
team
and
you're
not
happy
with
the
performance
of
the
team,
which
is
what
we
currently
know
like
it's
what
we
it
seems
to
be
the
problem,
and
that
has
never
been
discussed
with
the
team
like
what
else
is
to
be
transparent
about
migrate?
That's
a
huge
thing:
it's
like
you
are
discussing
performance
of
the
team
and
you
haven't
been
transparent
about
it.
Performance
of
the
team,
but.
A
B
H
E
To
agree,
I
think
that
there's
more
than
I
expect
out
of
this
potential
role,
then
Igor
was
actually
operating.
The
Negro
was
actually
responsible
for
and
so
yeah
I
can
see
like
where
your,
where
feedback
is
coming
from
Andre,
because
it
was
kind
of
it's
as
if
we
make
the
decision
already
and
it
was
announced
in
a
discuss
post.
E
But
we
didn't
bring
up
the
gaps
that
working
to
fill
in
beforehand
and
I
do
think
that
there
are
blockers
to
people
stucking
in
and
and
stepping
up
and
taking
on
additional
responsibilities,
and
that's
just
that
everybody
has
a
very
full
plate
trying
to
get
ready
for
d1.
So
what
incentive
do
they
have
to
take
on
the
role
of
things
that
you
girl,
we're
doing,
or
the
role
of
a
tech
weed
on
top
of
their
work?
Well
right
so.
A
I
Oscar
just
respond
to
that
yeah
I
think
that
would
be
a
great
idea,
because
now
there's
input
from
some
people,
like
myself,
I'll
discuss
I'd
love
to
hear
from
others
what
they,
what
they
think
the
issues
might
be,
or
maybe,
like
others,
see
it
as
Darren.
There
are
no
issues
to
resolve.
One
thing:
I
do
want
to
note,
because
I
I
heard
the
work
team
come
up
a
couple
times
for
me.
Two
issues
that
I've
seen
have
nothing
to
do
with
the
performance
of
a
individual
team.
I
So
I
just
want
to
get
like
put
that
on
the
table.
That
it's
this
is
to
me
not
about
the
individual
performance
of
a
team
but
more
about
a
organizational
element
that
we
seem
to
be
missing,
which
is
the
like
an
overarching
thing.
Next
to
these
calls,
like
the
port
of
calls
that
binds
the
work
of
the
teams
together
and
understands
how
they
impact
each
other.
C
F
Reading
as
we
speak,
the
West
next
for
status,
discuss
post,
but
the
need
I
saw
is
also
this
over
taking
roll
over
teams
that
understand
the
food
architecture
of
status
and
like
this
central
person
that
can
centralize
all
the
technical
aspects
and
architecture
we
can
talk
to.
When
we
we
try
to
see
the
implication
of
a
given
requirement.
H
Yeah
to
me,
like
that
sounds
like
I
mean,
doesn't
seem
to
be
like
the
best
person.
I
understand
the
people
who
are
not
technical,
wanting
to
have
a
center
point.
But
again
you
know
like
if,
if
you
had
such
a
bad
experience,
you
probably
talked
to
I,
don't
know
how
we
were,
but
clearly
you
you
know
a
hue,
maybe
like
a
single
developer
and
ask
for
estimate
which
clearly
is
not
a
good
process.
H
So
I
think
you
know
we
need
to
do
kind
of
like
we
need
to
sort
of
balance
a
bit
technical
and
non-technical
people.
We
both
need
to
understand
that
what
we
can
do
and
what
we
should
do
in
to
some
extent
and
also
like
having
a
single
person.
It's
fine
to
have
exactly
you
know,
but
having
a
single
person
who
has
all
the
knowledge?
It's
not
a
good
thing.
We
need
to
spread
out
the
knowledge
across
team
members.
I
H
A
Would
agree
with
that
I
guess
when
it
comes
to
specificity,
multi-account
stuff,
because
I
think
that's
been
giving
a
lot
of
headache.
Maybe
I'm
not
sure
Jessica
at
what
you
guys
are
saying.
But
it
is
different
angle,
but
to
me
their
problem.
There
is
that
there
was
no
clear
signal
taking
a
lead
and
the
responsibility
and
context
kept
being
passed
around
and
that's
what
that's
why
it
became
such
a
cost
effect,
because
there
was
no
one
not
even
like
a
functional
role
owning
the
whole
thing
end
to
end.
A
D
It's
not
about
a
roller,
but
it's
more
about
the
step
that
we've
missed.
Just
like
you
have
a
design
step
where
the
design
team
explores,
so
they
can
do
the
UX
and
what
would
work
best.
We
missed
that
step
in
development,
so
it's
not
about
one
person
assuming
that
role,
but
rather
a
discussion
about
how
we
proceed,
because
that
was
change
that
involves
telesco
status,
react
and
many
developers
of
both.
So
it
would
have
been
much
better
if,
before
the
implementation
of
the
screens
and
everything
started,
we
already
had
an
idea
of
what
we
want.
D
Everything
to
look
at,
look
like
and
I
think
it
will
be.
So
we
have
to
think
about
that
in
the
future,
and
it
would
be
probably
improved
by
the
fact
that
we've
kind
of
we
transitioning
to
having
more
like
before
status
go
was
always
consumed
as
a
simple
method
that
work
imposed
on
Sri,
Sri
exile,
and
now
we
have
more
often
functional
API,
where
we
ask
that
it's
good
to
do
things.
D
That's
helped
by
the
fact
that
data
has
been
transferred
to
stairs
good,
so
I
think
from
a
architecture
point
of
view
in
it
will
be
more
important
in
the
future
and
more
juice.
How
to
manage
that
step
like
before
developing
an
estimate
to
help
with
estimates
to
have
a
an
idea
of
what
they
do.
Is
that
between
sales
go
and
react?
Would
look
like
and
yeah
have
a
design
face
for
software,
and
not
just
for
yikes.
I
Yeah
I
definitely
think
that's
a
good
idea.
I
think
that
sounds
like
something
we
need
just
a
question
in,
so
we
have
this
structure
for
developing
new
features.
That
is,
as
I
recall,
like
specification
design
implementation
as
the
three
broad
faces,
maybe
Oscar,
which
you
can
fill
unify
missing
any
where,
where
would
you
say
like
most
of
those
activities
can
fall
or
do
we
need
to
like
introduce
another
face
for
that
process?.
A
A
From
my
point
of
view,
the
problem
is
that
we
don't
have
any
any
clear
mobile
native
experience,
especially
on
Android.
Additionally,
there's
no,
no
clear
technical
point
person
on
the
core
team,
I
think
I,
sort
of
actors
as
a
point
person
and
in
terms
of
understand,
what's
going
on
and
and
and
sort
of
rough
road
map
and
taking
ownership
of
the
client
asses.
A
Those
are
the
main
things
as
I
see
it,
which
is
kind
of
similar
to
what
ego
was
doing.
One
difference
I
would
make
is
maybe
in
terms
of
having
I,
was
pushing
for
this
before
you
having
more
Android
focus
because
I
think
that's
sort
of
been
holding
us
back
a
bit
in
terms
of
when
it
comes
to
performance.
That's
the
only
minor
thing.
E
B
You
guys
to
kind
of
follow
up
with
what
Rachel
said
when
it
maybe
make
sense,
that's
kind
of
like
what
next
step
should
be
for
this.
Like
should
everybody
I
guess
like
comment
on
the
thread
with
discuss
and
that
way
people
up
so
I
guess
can
when
hiring
this
lead
role
or
technical
role,
understand
I,
guess
kind
of
what
the
needs
are
in
the
space
so
that
you
know
we
there's
like
a
better
understanding
of
who
to
bring
on
we're
what
to
do.
E
B
Perfect,
so
let's
just
take
that
to
everybody
for,
like
opinions
and
stuff
I
guess
add
to
the
discussed
posts
of
your
opinions
are
kind
of.
What's
next
for
this
role
but
you're
looking
for
concerns
and
then
hopefully
we
can
go
from
there
and
kind
of
figure.
It
help
solve
these
problems
that
were
having
any
other
comment
on
the
role.
B
D
D
So
now
we're
we
have
one
less
option
to
explore
before
a
grading
status.
React
started,
react
needed
it's
a
something
good.
A
blogger
could
help
with
we
wondering
with
Andrea.
If
studies
go,
is
it
doesn't
importance
what
if
that
is
Boris
as
a
64-bit
version
to
link
to
the
app,
and
if
that
that
could
be
the
issue
action
so
there's
any
one
with
the
person
we
can
discuss
that
with
instead
of
question.
D
A
Guess
it
just
had
one
question
in
terms
of
I
know
that
there's
a
core
core
I'd
stand
up
earlier
today
and
then
we
have
did
these
meetings
and
everyone
is
roof
down
in
most
people
are
focusing
on
shipping
b1.
So
what
are
people's
thoughts
on
on
how
to
deal
with
that
in
terms
of
its
cost
being
being
useful,
and
so
on
like
what?
What
would
be
good
format?
A
D
Personally,
I
would
be
in
favor
of
not
doing
the
team
updates
at
moonray
if
it
wouldn't
be
more
efficient
to
just
write
something
and
post
it
on
discuss
as
a
weekly
team
update
post
or
something
like
this,
because
it's
a
it's
an
odd
ritual
to
me.
I,
don't
know
if
anybody
is
against
this
ID,
but
it
would
make
the.
A
D
D
A
In
fury
absolute
epic,
would
you
agree
to
before
is
that
people
should
give
up
this
if
there's
anything,
that's
relevant
to
other
people
in
terms
of
future
resistance
and
so
on?
That's
not
always
what
happens
and
another
thing
is
in
practice,
even
though
we're
so
said,
like
people
should
post
updates
before
and
so
on,
that
doesn't
happen
and
trying
to
force
that
it's
a
bit
of
a
pain
in
the
ass.
To
be
honest,
so
it's
a
question
of
like
what's
gonna
happen
in
practice
as
well.
I
think.
E
D
E
A
A
This
could
be
useful
call
for
that
similar
to
the
court,
of
course,
on
in
a
forum.
But
it's
not
clear
to
me
what
that
looks
like,
given
that
we
also
have
more
specific,
also
become
who
had
their
protocols
calls
with
fewer
participants
here
and
I
know
that
there's
some
cost
between
embark
and
Nimbus
and
so
on.
So
I
would
also
be
curious
to
hear
people
from
outside
stars
core
what
their
perspective
is
in
terms
of
how
what
would
be
useful.
B
A
B
A
I
know
I'm
up
for
it,
but
I
also
have
another
question,
which
is
that
historically,
we
have
had
lots
of
issues
in
terms
of
actually
getting
things
into
debt
and
especially
so
well
prepared
items.
Sometimes
they
come
in
and
so
on,
but
usually
it
requires
a
lot
of
pooling
and
so
on
and
and
and
often
people
come
with
ideas
like
last
minute,
which
is
better
than
nothing
right
but
but
I
don't
know
how
people
have
seen
his
work
better
because
I
agree
with
URI
absolutely
like.
D
Well,
personally,
I
would
encourage
a
bit
more
participation
and
discuss
and
one
way
to
fill
up.
The
dev
agenda
is
to
pick
up
the
issues
in
disgusting
in
disgust
that
seem
to
be
a
bit
lagging
and
to
regime
to
dynamize
them
to
bring
up
to
the
agenda
so
that
they
are
discussed
life
and
maybe
moving
forth
so
kind
of
like
yeah
kind
of
what
we
did
with
the
with
the
tech
lead
discussion.
A
B
Okay,
so
let's
do
that
going
forward,
let's,
starting
in
the
month
of
August,
we'll
make
it
kind
of
maybe
toward
like
late
August
the
develop,
call
and
set
it
up
that
way
and
then
take
the
discuss
points
from
there
discuss
in
there
and
then
also
do
I
guess
we
can
send
the
agenda
out
maybe
week
before
the
meeting,
so
that
teens
can
add
any
other
additional
talking
points
and
I'm
just
doing
some
additional
follow-up
before
the
meeting
happens.
Does
that
work
with
everyone.
B
Cool
so
I
made
the
changes
on
everyone's
calendars
for
next
month
and
then
I'll
send
the
agenda
out
and
then
maybe
I
can
make
maybe
more
like
a
template
for
like
team
updates,
where
people
can
enter
in
kind
of
updates
from
there
and
then
we
can
have
a
section
for
discuss.
So
it's
a
little
bit
more
organized
and
people
can
add
the
talking
points
in
that
way.
So
let's
try
that
out
and
then
we'll
give
it
a
test
run
next
month
and
see
how
it
goes
and
then
obviously
we
can
improve
from
there.
G
B
It'll
be
really
fun.
Yeah,
there's
also
discuss
pose
for
Turkey
I'm.
Talking
about
what
the
agenda
speaking
of
agendas
should
be
for
kind
of
what
we
discussed
as
a
team,
so
I
would
love
kind
of
everyone's
input
of
what
and
how
discussions
should
go
for
Wednesday
and
Tuesday
when
we're
all
together.
So
please
add
your
thoughts
in
there
and
so
that
we
can
be
as
class
and
successful
as
possible
when
we're
all
together.