►
From YouTube: Data Team Issue Triaging
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
Hi,
my
name
is
Emily
cheerio
and
I'm.
A
data
engineer
here
at
get
well
today,
I'm
gonna
show
how
we
handle
issue
triaging
when
you're
on
triage
day,
so
I'm
gonna
go
ahead
and
share
my
screen,
but
you'll
see
that
I
have
here
is
the
handbook
open
to
the
triage
section
and
the
number
of
issues.
So
we
had
two
issues
come
in
today
from
people
not
on
the
data
team,
which
are
the
only
issues
that
the
tree
answer
needs
to
be
concerned
about
the
first
one
here.
A
So
we
can
see
the
description
of
responsibilities
which
say
that
issue
triaging
is
really
just
about
making
sure
people
know
that
we're
acknowledging
their
response.
What
we
want
to
do
is
make
sure
we
assign
the
appropriate
labels.
Excuse
me
and
ask
any
clarifying
questions.
So
if
we
look
at
the
instructions
are
on
issue
labeling,
we
can
see
what
they
are
here.
A
We
might
not
know
what
team
page
arrow
is
on
I
do.
But
if
we
go
to
about.com
slash
team,
it's
gonna
redirect
to
slash
company,
slash
team
and
that's
gonna,
show
you
the
team
page
at
which
point
you
can
command
s
for
Pedro
and
that'll.
Show
you,
okay,
he's
a
product
designer
which
means
he's
on
the
UX
team,
which
means
he's
an
engineering.
So
when
we
look,
we
know
that
we
can
assign
the
label
of
engineering.
A
We'll
look
at
snow
cloud
data,
so
snowplow
is
pretty
much
modeled,
so
this
is
an
aspir,
a
dashboard
in
periscope.
The
data
being
touched
is
snowplow.
This
would
be
an
analytics
and
this
would
be
an
enhancement.
It's
a
new
dashboard,
pretty
straightforward.
Nothing
in
particular
jumps
out
to
me.
There's
no
clarifying
questions.