►
From YouTube: 2021-11-04 Working Group: Merge Request Report Widgets
Description
Ninth weekly meeting of the WG.
Agenda: https://docs.google.com/document/d/1bcch8UUkwmgEHFolTWDrQFJtUiiXlv_yQFAGwSSDSUE/edit#
A
A
I
do
have
one
one,
a
couple
of
discussion
items
so
we'll
go
straight
to
that
one.
So
I
wanted
to
check
in
kai
kai,
touched
on
a
point
on
the
slack
channel
about
something
that
the
secure
group
is
exploring
about.
Having
a
new
feature
notification
inside
of
the
widgets
and
yeah.
I
have
the
same
question
as
kai
had
like.
Is
that
something
that
we're
accounting
for?
A
A
B
Yeah-
I
don't
at
the
moment,
but
I
could
I
could
find
out.
I
know
that
early
on,
I
had
explored
alerts
in
the
context
of
the
mr
widgets,
so
that's
something
that
I
could
circle
back
with
and
at
some
complexity,
because
if
we
want
it
to
be
an
actual
alert
that
comes
with
aria
live
and
like
actually
notifying
a
user,
so
this
is
more
styled
like
a
like
a
notice,
and
so
that
gets
back
to
different
design
pattern
and
intentions.
So
we'd
have
to
kind
of
circle
back
on
on
a
few
things
for
this.
B
A
B
A
Right
so
again,
I
think
tim
noah
looked
at
the
way
that
we
have
the
process
we
have,
for
you
know,
adding
features
and
stuff
to
our
to
the
merge
request
area
and
the
process
that
that
kai
at
the
time
devised,
involved,
involved
having
the
pms
get
in
touch
and
and
that
at
least
having
that
sort
of
conversation
with
the
group.
In
this
case,
since
we
have
a
ux
framework
overseeing
that
part,
it
would
be
useful
to
get
that
chat.
A
A
It
might
be
useful
for
the
designer
to
join
us
in
the
call
if
they
feel
it's
worth
it
just
so
that
they
understand
exactly.
What's
the
effort,
that's
behind
it.
What
would
be
the
time
frame
for
them
to
roll
something
like
this
out
and
maybe
even
gener
generalize
a
little
bit
of
the
solution,
because
they
might
be
too
specific
for
their
own
case.
But
since
we
have
this
effort
going
on,
it
might
be
useful
to
go
and
a
little
bit
more
broad
and
how
they
do
it.
A
A
All
righty,
so
a
couple
weeks
ago
I
mentioned
a
telemetry
epic,
so
the
where
this
crosses
over
with
this
working
group
is
that
there's
several
merge
requests
report,
widgets
that
are
covered
by
these
telemetry
areas
that
we'd
like
to
track,
and
I
know
that
some
of
them
we
saw
that
it
was
already
done
and
the
ones
that
are
being
rewritten
should
definitely
be
rewritten
with
telemetry
in
mind.
I
I
would
say
so
I
wanted
to
see.
Does
anybody
have
any
ideas?
A
A
Okay,
no
thoughts,
that's
a
thought
too
no
worries.
I
understand
that
telemetry
is
usually
it's
a
little
bit
lateral
or
tangential
related
to
this
group's
effort.
So
that's
fine
scott
to
your
to
your
realm
of
of
influence.
A
little
bit.
Do
we
have
plans
for
the
upcoming
milestones
to
rewrite
widgets?
I
know
I
see
that
the
license
compliance
which
maybe
I
can
check
my
screen,
so
we
can
have
it
on
the
recording.
A
Do
you
see
my
screen?
No,
it
usually
gives
me
a
little
notice
that
I'm
sharing
my
screen,
but
that
it's
being
seen
anyway.
So
this
is
the
epic
that
is
tracking
the
adapting
the
new
framework
to
existing
widgets.
Actually,
this
is
the
actual
epic,
and
I
see
that
we
have
license
compliance
aimed
at
14.6.
C
A
A
C
A
But
yeah
it's
a
stretch,
so
this
might
actually
not
be
completed
during
this
milestone.
So
it
might
oh
wait,
okay,
so
this
might
actually
only
be
schedulable
the
metrics
on
the
following
one,
but
this
is
nice
glad,
I'm
glad
you
did
that,
because
that
way,
as
we
close
off
the
issues,
they'll
just
stop
being
blocked,
I
would
expect
them
to
be
shown
here.
Sorry,
I
know
that
I'm
jumping
around.
I
would
expect
them
to
show
here
as
blocked
some
for
reason.
A
For
some
reason,
they're
not
but
that's
useful,
but
we
we
do
are
picking
license
compliance.
Is
that
it
this
one
here
we're
we're
good
to
go.
No!
Yes,
because
this
one
is
deliverable
right
and
and
phil
is
working
on
this
he
should
be
closing
in.
I
think
it's
in
late
stage
of
review
at
this
point,
so
we
should
close
this
off
in
fourteen
five
get
this
in
on
fourteen
six,
while
we
complete
the
core
support.
A
Okay,
a
question
to
this
then
license
compliance.
If
you
look
at
the
telemetry,
we
have
license
compliance
here
shouldn't
we
schedule
these
two
at
the
same
time
and
probably
even
give
that
to
the
same
person,
rewriting
that
widget
as
you
can
see,
it's
just
like.
Basically
the
expansion
and
I
think
it's
more
like
a
declarative
thing
where
you
have
to
create
the
ammo
things
and
pass
that
to
the
core
component,
so
it
should
be
fairly
straightforward.
C
A
and
we
can't
use
aggressive
metaphors
and
take
care
of
both
at
the
same
time.
You
know
what
I
was
going
for
right:
two
birds,
yeah
all
right
and
then
I'll
just
cc,
neil
carson
and
nicole
schwartz
good,
any
nudge
that
we
can
do
to
get
these
things
scheduled
the
better
all
right.
Then
at
least
we
have
some
some
movement
in
that
area.
Thanks
for
blocking
those
issues,
scott,
that's
really
helpful.
All
right.