►
From YouTube: Applied ML weekly team 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
Yes,
so
we
applied
ml
weekly
team
meeting-
hey
taylor,
hey
alexander,
get
going
here
is:
please
join
me
in
graduating
with
me
at
the
agenda
in
congratulating
mon
on
her
new
role
as
engineering
manager
for
the
applied
machine
learning
and
anti-views
team
she's
a
currently
current
gitlab
team
member,
and
has
extensive
background
in
leading
machine
learning.
Engineering
teams
also
having
experience
in
preventing
fraud
and
money
monitoring
mine
is
in
australia
and
most
team
members
are
in
the
americas
or
emea
time
zone.
C
A
B
Cool
so
also
mihao
has
decided
to
move
back
to
the
threat
insights
team.
We
really
appreciate
his
help
for
the
last
couple
months
with
his
background
machine
learning
and
other
things,
and
he
thought
about
both
teams,
but
feels
it's
a
better,
the
other
team's
a
little
better
fit
for
him,
at
least
in
the
in
the
short
to
medium
term.
B
So,
thanks
for
all
your
help,
he'll
continue
to
finish
up
in
process
work
for
applied
ml
and
will
continue
to
stay
involved,
to
give
us
advice
and
the
slack
channel
and
his
team
meeting,
etc
and
mon,
and
I
will
get
the
job
listing
posted
for
the
role
in
q3,
which
will
promote
both
internally
and
externally
and
we'll
have
net
new
roles
as
well
already
planned
as
part
of
budgeted
hires
in
q4
alexander,
a
quick
update
on
an
review
in
dangerbot
and
gilly.
A
Yeah
yeah,
quick,
update
so
and
review
now
works
with
dangerboard
bots
for
gizly,
so
I
have
provided
a
merch,
a
link
to
the
merch
request.
Please
help
me
to
get
it
reviews
because
I
think
yeah
a
lot
of
discussions.
We
will
make
a
lot
of
discussions
there.
So,
okay,
that's
the
first
news.
Another
one
is
the
recommender
service
now
works
both
as
a
jrpc
and
srs
service
after
integrating
and
voice
a
sidecar
proxy.
A
So
just
it's
more
technical,
but
also
quite
interesting.
So
you
can
also
check
how
and
review
works
with
danger
bots
in
the
merch
request.
I
have
provided
in
the
doc
file.
So
this
is
the
fourth
version.
This
is
the
fork
gita
project
because
I
needed
to
provide
some
additional
environment
variables
and
I
couldn't
do
that
in
in
the
in
the
main
gitli
project.
So
I
made
a
fork
you
can
you
can
you
can
see
how
it
works
there
and
please
help
me
with
with
immerse
requests.
B
I
also
thanks
alexander.
I
also
tagged
me
how,
as
he
is
a
maintainer
in
training-
I
I
don't
think
forgiving,
but
for
other
things,
so
he
can
potentially
give
some.
So
where
is
the
unreview
want
to
share
your
screen
on
this
and
show
us
maybe
walk
us
through
the
example.
A
That's
the
first
time
from
this
account
yeah
this
one
yeah
this
one.
B
A
B
A
B
Just
another
just
reading
through
the
text,
another
thought
is,
I
see
it
says,
contact
us
in
our
applied
ml
slack
channel.
Just
something
to
keep
in
mind
is
that
we
take.
We
take
merge,
requests
from
non-employees
from
non-team
members
so
from
from
the
public,
so
they
won't
have
access
to
that
channel,
so
it
doesn't
need
to
change
now.
This
is
a
great.
I
think
this
is
just
fine
for
an
mvc.
B
B
C
C
I
do
think
we
want
to
maybe
think
about
like
hey,
if
you
don't
agree
with
these
reviewers
like
put
a
label
on
the
issue
or
something
that
way
we
can
query
for
them
and
see.
C
B
A
B
Great
and
any
anything
other
than
time,
having
the
time
available
to
finishing
that,
are
you
waiting
on
anybody
else
or
any
other
teams
or
access
etc?
Are
you
good
to
go
on
that.
B
Two
two
quick
questions,
and
again
this
is
great.
It's
great
to
see
something
in
action
like
this
makes
me
very
happy
is,
since
we
have
reviewers
separate
from
maintainers
under
view
is
recommending
reviewers
should
we
also
have
unreview
recommend
a
maintainer,
so
basically,
a
maintainer
is
one
of
the
to
probably
oversimplify
a
reviewer
who
has
maintainer
rights
for
the
project
and
it's
supposed
to
be
separate
people.
So
would
we
want
on
review
in
a
future
iteration
and
not
just
recommend
reviewers
but
recommend
maintainers
too.
A
Yeah,
of
course,
but
assigned
the
suit
gitlab
didn't
have
a
reviewer
section
right.
So
that's
why
right
now,
unreview
takes
everyone
from
the
from
from
the
approvers
and
call
them
reviewers.
A
Yeah
because
yeah,
because
so
I
didn't
have
an
access
to
to
the
because
reviewers
they
didn't
appear
at
gitlab
for
a
long
time,
only
approvers.
So
that's
why
that's
why
italy
and
gitlab
itself
these
projects,
they
don't
have
reviewers.
They
have
only
approvers
in
their
past
history,
okay,
so.
B
B
What
why
did
you
decide?
I'm
just
curious
on
getting
first
versus
gitlab
itself.
A
Because
because
we
start
with
this
project,
that's
the
first
thing
another
thing.
I
know
this
project
a
bit
and
the
third
thing
is
that,
like
weeks
week,
I
extracted
the
data
set
for
italy
first
and
not
to
be
blocked
with
some
other
tasks.
I
decided
to
focus
on
guilty
first,
but
that's
not
an
issue,
so
maybe
we
can.
We
can.
B
I'd
love
to
see
it
on
git
lab
itself,
in
addition
to
ghibli
at
the
right
time
and
potentially
part
of
the
poc
as
well.
The
proof
of
concept
as
well
is
also
running
on
gitlab.
This
is
great
we're
going
over
after
the
first
run
of
underview
on
actually
the
getaly,
a
giveaway
merge
request,
which
is
kind
of
neat.
A
B
And
always,
I
think
you
already
covered
my
item
number
four.
Well,
we
already
covered
number
four,
but
this
is
great
anything
else
we
wanted
to
discuss
today.