►
From YouTube: Diagnostics WG 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).
A
B
This
could
very
well
be
discussed
in
the
standard
agenda
as
well,
but
I
just
want
to
say
that
the
in
diagnostic
session
in
the
club
summit
last
week
went
well.
I
was
able
to
explain
the
philosophy,
current
status,
challenges
and
opportunities
for
both
her
user
journey
based
deep
Drive
and
diagnostic
best
practice.
Documentation.
B
Of
course,
the
overall
numbers
were
pretty
less
so
I
guess
around
pleasant
and
members
participated.
Hopefully
we
should
see
some
new
comers
joining
the
working
group.
Hopefully
yeah.
That's
pretty
much
from
my
side.
A
A
B
B
B
So
right
now
the
change
from
that
status
is
that
we
have
a
fair
process
in
place
for
the
documentation
work.
We
have
a
good
structure
in
place
about
how
a
best
practice
documentation
should
look
like,
for
example,
a
set
up.
We
have
a
prerequisite
and
then
we
have
different
flows
step
one
step,
two
step,
three
kind
of
which
uniquely
picks
up
one
specific
tool
to
address
the
user
journey.
So
I
guess
we
are
more
or
less
sticking
to
that
that
style
or
that
format
for
for
the
user
journey.
B
So
far,
so
with
that
in
place,
if
the
question
is,
can
we
directly
think
about
publishing
to
the
website?
Yeah
I
think
it
looks
interesting?
Look
if
it
looks
promising
to
me-
or
at
least
we
could
start
looking
at
publishing
the
existing
documentation
and
see
how
it
goes.
What
is
the
experience
like.
A
A
A
To
make
it
available
on
the
diagnosis
repository
it's
simply
to
reading
from
from
our
users,
the
new
website
is
not
that
popular,
yet
it's
not
been
officially
published,
they
are
taking,
but
at
least
when
it's
published
we,
it
would
have
the
guys
there
so
like
wolf.
Bring.
This
up
is
revisiting
our
decision
to
have
everything
on
the
Diagnostics
report.
A
A
B
B
Following
the
current
procedure
of
height
rating
in
the
diagnostic
working
group,
so
that
we
have
a
proper
review
on
the
documentation
and
then
once
we
have
the
documentation
landed
in
the
repo
doing
some
automation,
such
as
a
pipeline,
which
will
take
it
up
and
publish
in
the
new
website
in
a
completely
automated
manner,
looks
like
a
good
idea
to
me,
because
it
doesn't
compromise
on
the
the
quality
which
we
want
on
the
documentation.
At
the
same
time
reduces
the
effort,
duplication
of
effort
also.
A
B
Okay,
yeah.
The
reason
why
I
ask
is,
for
example,
we
from
the
diagnostic
working
group
or
from
the
project
as
a
whole
provide
this
content,
saying
that
this
is
the
best
practice
documentation.
Please
publish
this,
but
if
there
is
a
another
entity
sitting
in
the
website
side
who
wants
to
review
the
content
from
these,
the
takes
and
other
other
structural
considerations
look
and
feel
and
other
things,
and
there
is
another
another.
A
A
B
B
B
C
A
A
A
Having
some
way
to
the
Diagnostics
or
group,
be
aware
of
those
suggestions
is
something
that
we
should
consider.
Condo
owners
is
one
option.
Another
option
is
having
our
contact
information
on
the
bottom
of
those
guides
or
maybe
having
a
link
to
the
Diagnostics
before
story,
but
I
think
it
should
be
clear
that.
B
Yeah
and
in
another
scenario,
where
a
user
who
is
consuming
this
documentation,
may
have
a
a
specific
work
clue
which
he
has
been
running
and
it's
not
completely
covered
in
the
documentation
or
in,
in
which
case
he
could
actually
come
to
the
diagnostic
report.
Butte
feareth
contributed
back
to
the
repo
which
is
a
right
fit
for
the
coverage.
So
in
that
aspect
also,
we
should
have
a
linkage
from
the
documentation
to
the
repo.
In
my
opinion,.
C
A
A
A
A
B
Yeah
in
terms
of
visibility,
discoverability
I
think
this
left-hand
side.
Pane
is
a
very
good
location,
because
this
is
this
is
exactly
the
location
where
the
API
is,
and
the
the
actual
largest
functionalities
or
features
are
discussed.
But
if
we
spread
the
content
as
top-level
sections,
then
definitely
the
number
of
items
grow
large
and
it
will
mutually
literally
reduce
the
discoverability
and
reduce
the
overall
user
experience.
So
either
have
a
documentation
section
at
the
top
level.
A
A
A
Okay,
I'll
try
to
find
out
the
answer
to
some
of
the
questions
we
raised.
I
didn't
sucked
an
agenda
today,
because
I
was
preparing
for
more
depth,
IV,
anything
but
later
I'm,
going
to
rewatch
the
recording
in
Brighton
Adrian,
insensitive
repository.
Maybe
you
should
start
an
agenda
to
the
following
tip
types
as
well
in
parallel
with
the
dip
dive
duck.
A
Here
we
have
discussed
performance
memory,
leaks
and
process
crashes
so
far,
and
the
only
other
user
journey
I
can
think
of
is
unexpected,
behavior,
so
I
suggested.
We
could
talk
about
this
one,
but
maybe
I'm
not
thinking
of
some
violent
user
journey.
So
those
in
you
can,
then
you
won't
think
of
other
user
journeys
or
other.
A
C
A
C
A
So,
for
example,
hooks
on
the
system
could
be
used
to
performance
issues
or
memory
leaks
or
unexpected
behavior,
but
they
are
not.
The
user
journey.
Percy
I
said
the
more
as
a
DPF
thing,
which
we
should
probably
when
you're
visiting
user
journeys.
We
should
probably
talk
about
hooks
as
well,
but
that
don't
see
it
as
a
user
journey
Percy.
C
C
B
B
Yeah,
but
if
you
look,
if
you
look
at
the
original
premise
in
which
the
user
journey
initiative
was
doctored,
it's
like
too
many
tools
and
not
necessarily
all
the
tools
are
covering
a
specific
user
journey,
end
to
end
some
of
the
tools
work
for
certain
scenarios,
but
not
not
necessarily
covering
a
common
scenario
at
all.
So
we
had
so
much
of
such
tools.
Some
other
tools
were
not
properly
maintained.
B
So
if
you
look
at
some
of
the
documentation,
we
have
step
one
step,
two
step
three
step:
four,
where
multiple
tools
are
contributing
to
save
user
journey,
and
that
is
accommodated
in
different
steps.
So
those
those
are
the
scenarios
where
multiple
tools
are
useful
or
redundant,
alternatively,
available
to
debug
same
or
similar
scenario.
B
So
if
we
have
more
tools
like
for
performance,
definitely
there
would
be
a
lot
of
tools
and
even
for
live
debugging
I
believe
there
could
be
many,
so
the
idea
should
be
added
across
different
steps
in
the
documentation
in
the
deep
dive.
Yes,
if
we
have,
if
we
have
a
tool
that
fits
into
one
of
the
existing
user
journeys,
we
could
always
revisit
that
and
fit
that
the
tool
fit
meaning
we
can
discuss.
Where
is
the
relevance
coming
in
and
attach
it.
A
A
We
gave
a
suggestion
to
explore
the
idea
of
using
easing
hooks,
for
example,
but
after
all
the
user
journeys
focusing
on
the
tool
the
from
the
symptoms.
What
are
the
most
common
tools
you
can
use
versus
water.
All
the
tools
you
can
use
I
think
we
can
do
a
second
pass
on
how
the
user
journeys
once
we're
finished
and
added
another
section:
we've,
okay,
so
those
tools
that
we
showed
so
far
or
use
it
on
most.
A
A
A
A
A
C
Would
think
if
we
can
maybe
and
the
document
that
you
will
presented
in
growth
Queen?
You
know
this
document
into
it
ripple
so
that
we
can
work
continue
working
on
this
top
document
with
github
P
up
with
this
offline.
So
for
most
of
the
document
and
acts
a
doctor,
anything
we
don't
have
to
put
it
written
in
the
meeting
and
discuss
them
in
and
we
can
have
a
rare
agenda
to
extract
or
discussed
in
the
meeting
if
necessary,
so
that
we
can.
A
C
A
The
idea
was
that
this
document
was
mostly
done,
except
for
the
two
dues,
and
we
should
be
moving
to
the
next
case
now,
which
is
even
expected
here,
but
also
we
need
to
start
turning
these
into
guides
like
we
did
with
the
the
other
user
journeys.
I
think
we
should
continue
how
we
were
doing
when
someone
have
the
time
they
can
pick
the
user
journey
and
write
one
of
the
guides.
A
One
of
one
of
the
reasons
that
we
start
the
tip
types
on
user
journey
was
that
don't
have
the
time
to
war
on
it.
So
having
a
meeting
where
we
were
discussing,
helping
us
allocate
this
time
every
two
weeks
and
also
it
gave
good
results,
50
discussions,
so
we
started
for
one
reason
and
I
believe
we've
got
a
few
other
benefits
out
of
it.
So
I
wouldn't
mind
trying
the
same
to
write.
The
purpose,
for
example,
I
think
it
would
have
good
results
too.
A
User
journeys
that
we
discussed
so
far
are
on
the
on
the
meeting
for
this
week.
Maybe
someone
should
go
through.
This
is
erroneously
st
use
cases
and
tolling
we
have
and
make
a
list
of
which
ones
we
already
repository.
I
can
try
to
do
that,
but
I
I
can't
make
any
promises.
My
schedule
is
a
bit
weird
lately.
A
A
There
are
two
questions
on
the
chat
gives
what
we
are
going
to
look
upon.
I
believe
it
was
a
question
on
what
we
would
be
discussing,
so
we
have
weekly
meetings
on
the
Diagnostics
working
group
every
other
week.
We
have
a
similar
meeting
where
we
get
the
agenda
based
on
items
flagged
for
the
working
group
across
the
entire
notice
organization
and
in
the
other
two
weeks
we
have
the
pipe
meetings
where
we
discuss
specific
topics.
For
the
past
few
months
you
have
been
discussing
diagnostic
user
journeys.