►
From YouTube: 2022-05-19 Working Group: Merge Request Report Widgets
Description
Weekly call for the working group Merge Request Report Widgets
Agenda:
https://docs.google.com/document/d/1bcch8UUkwmgEHFolTWDrQFJtUiiXlv_yQFAGwSSDSUE/edit
A
And
we're
we're
live.
I
think
yes,
hi.
Everyone
welcome
to
the
weekly
meeting
for
the
merge
request,
report,
widgets
working
group
and
we'll
get
straight
into
the
agenda
so
yeah
as
we've
talked
about.
Actually
I
have
an
announcement.
Dri
dri's
list
has
been
merged
and
is
in
the
handbook
I'll
put
the
link
here,
but
basically
we
we
got
the
list
from
that.
Merge
request
from
that
issue
that
I
opened
and
everybody
pitched
in.
A
A
I
didn't
want
to
put
this
in
the
context
of
the
working
group
for
because
this
will
be
dismantled
soon.
So
the
idea
there
is
that
at
least
it
lives
somewhere
that
we
can
reference
later.
I'm
adding
this
to
the
section
above
it
in
the
table
initially
at
the
agenda
doc,
so
that
we
can
then
dri
list.
So
now
we
know,
that's
it
any
questions
about
that.
The
dris.
A
Cool
right
and
now
I
wanted
to
bring
up
as
a
discussion
item
just
a
bit
a
bit
of
an
overview
about
the
blockers
for
the
rollout,
so
phil
who's,
not
who's
out
of
office
today
is
overseeing
the
the
rollout,
and
I
think,
there's
already
a
couple
of
issues
identified-
that
our
blockers
at
least
need
to
be
resolved
before
we
start
rolling
these
out
and
the
the
first
that
I
saw
was
the
204
how
we
handled
that
loading
state
flynn.
Do
you
have
any
additional
contacts
or
information.
B
Yeah
so
we've
been,
we've
had
a
sink.
A
synchronous
meeting
last
week
is
sevas
and
phil,
and
I,
and
so
us
has
an
mr
that
pipeline's
green
waiting
to
be
merged,
so
that
should
be
merged.
I
think
today
and
then
the
follow-up
was
and
they're
not
quite
blockers,
they're,
just
high
risk,
merge
requests
and
then
I'll
get
to
that
why
they
are
higher,
so
the
204
one
more
or
less
introduces
the
ability,
a
cleaner
ability,
it
reworks
the
pulling
logic
a
bit.
B
The
main
concern
is
that
any
of
these
three
issues
linked
here,
I
think
the
204
one
he
needs
for
the
security
widget,
which
is
not
feature
flagged
out.
So
I
think
the
intent
in
the
global
rollout
is
to
have
that
security
widget
as
part
of
it
license.
Compliance
is
kind
of
lagging
behind,
because
they're
missing
some
back
end
pieces
that
we
need
additional
data
for
the
ui
states,
so
license
compliance
is
not
blocking,
but
the
two
follow-up
issues
one
was
a
refactor
to
kind
of
make
polling.
B
What
we
did
is
we
enabled
the
ability
to
pull
multiple
endpoints
versus
just
the
one
security
reports.
Widget
pulls
like
four
different
security
endpoints,
so
this
is
weird
special
case
so
that
that
204
issue
is
needed
for
the
security
widgets,
which
right
now,
I
guess
it's
intended
to
be
part
of
the
global
rollout.
That's
why
it's
blocking
once
that's
fixed
we're
unblocked
the
two.
The
possible
blocker
follow-up,
I
think,
is
a
possible
blocker.
B
I
say
this
because
it
it
refactors
the
single
endpoint,
which
is
used
by
multiple
different
widgets
for
pull
that
use
polling
and
it's
a
potential
vlogger.
I
say
that
because
we
I
need
to.
I
think
we
need
to
be
very
careful
about
introducing
this
at
what
time,
maybe
after
before
the
rollout,
but
it,
but
you
know
doing
it
after
the
rollout
blocks.
Other
work
like
license
compliance.
B
If
we
do
it
before
we
need
to
make
sure
that
the
polling
works
and
all
these
other
widgets
kind
of
regression
testing.
I
don't
know
how
we
have
unit
tests,
but
I
don't
know
how,
like
you
know,
you
know
we'll
have
any
runtime
errors
pop
up,
because
the
204
was
a
runtime
error
not
caught
in
unit
test.
So
that's
where
I'm
kind
of
leave
it
up
to
the
team
to
decide
if
it's
a
high
risk
follow-up.
B
Mr,
we
just
need
to
be
very
thorough
when
we,
when
we
merge
it,
I
don't
think
it's
a
blocker
for
the
rollout.
I
just
do
think
that
after
we
roll
it
out
and
then
introduce
just
mr,
we
need
to
be
very
sure
we
don't
break
the
things
that
we
just
rolled
out
as
new
thing.
These
features,
you
know
the
new
widgets
and
then
the
expanded
section.
Let
me
share
my
screen
because
I'm
talking
and
not
visually
showing
anything
okay.
So
this
is
the
204.
B
This
is
the
one
that
has
the
merge
request.
I
won't
go
through
it
right
now,
but
that
should
block
unblock
security
report,
widget,
which
I
think
is
the
last
word
that
we're
waiting
on
for
the
release,
global
release
or
global,
enabling
this
one
does
not
block
the
release,
but
it
does
change
how
polling
works
for
the
single
endpoint
ones,
and
we
just
need
to
make
sure
that
whether
we
roll
this
out
before
or
after
the
enablement
is
that
we
don't
cause
any
regressions
in
any
of
the
prior
widgets.
B
This
one
yeah
it's
scheduled
for
15
months
survivors
is
actually
going
to
be
picking
this
one
up
next
wednesday.
I
may
maybe
help
him
get
a
head
start,
but
it's
assigned
to
me,
but
he
may
be
taking
it
over
because
he's
planning
to
work
on
that
one
as
a
follow-up
to
the
the
first
one
and
then
the
last
one
is
license
compliance
specific.
B
I
won't
go
into
details
while
we
need
it,
but
unless
you're
curious,
the
thing
is
license
compliance
because
as
a
204
behavior,
even
for
the
expanded
data,
the
thing
is:
endpoints
are
cached,
so
the
collapse
endpoint
and
the
expanded
endpoint
are
different
in
for
the
security
analyzer
endpoints.
In
that
the
data
is
based
off
of
the
same
report,
but
the
endpoint
or
slightly
different
one
is
the
compressed
version,
one's
expanded
version
and
when
you
hit
each
of
those
endpoints
we
use
behind
the
scenes.
B
I
forget
what
the
name
of
the
caching
mechanism
is,
but
it
needs
to
rebuild
that
cache
and
then
we
will
pull
briefly
for
like
a
second
or
two
while
that's
generated.
So
I
need
to
basically
extend
the
work
that
phil
and
servas
have
been
doing
for
pulling
for
the
single
endpoints
the
expanded
one,
and
then
you
know
again,
but
that's
not
a
blocker
for
the
role.
Actually,
I
should
probably
move
it
then,
but
that
that's.
A
Is
it's
telemetry
related
bug
because
we're
working
on
additional,
adding
telemetry
from
the
base
core
component
so
that
we
can
have
telemetry
for
all
widgets
and
there
was
an
identified
bug
that
was
causing
a
lot
of
remounts
and
stuff
that
was
causing
some
over
counts.
So
we're
going
to
be
addressing
that
in
15-1.
Hopefully,
like
I
said,
all
of
this
will
fall
into
place
in
15-1
and
we
can
start
rolling
it
out
for
staging
and
then
production
and
this
milestone
so
stay
tuned.
B
Okay,
I'm
curious:
have
we
done
any
validation
that,
like
the
ui,
to
revisit
all
the
widgets
and
make
sure
they
all
look
the
same?
Because
we've
had
mrs
land
that
tweak
styles?
And
I
don't
know
if
you've?
Actually,
it
may
fix
the
styling
for
one
widget.
We
may
have
broken
other
ones
in
the
process,
ones
widgets
that
have
been
reviewed
at
ux
review
prior,
but
we
haven't
gone
back
and
revalidated.
So
I
think
we
should
as
an
exercise,
I'm
not
going
to
attract
a
separate
issue
or
have
hdri
spin
up.
B
Know
yeah
so
I'm
having
each.
Maybe
it's
part
of
that
that
that,
and
only
the
rollout
issue
to
have
each
team
spin
up
at
what
their
respective
widget
and
make
sure
that
visually
we
don't
have
any
ux
regressions
because
I
know
like
I
said:
we've
had
ux
sorry,
you
know
styling
tweets
land,
not
you
know
not
too
long
ago,
maybe
like
this
last
milestone
and.
C
A
A
C
B
B
D
A
C
A
Example
for
engineering,
so
that's
the
list
of
the
widgets
that
we
have
identified
that
are
in
development
or
already
developed.
So
we
have
to
have
a
ux
person
for
each
one
of
those.
It's
probably
the
same
for
a
lot
of
them,
but
yeah
ping
me
when
it's
done
and
I
can
set
up
an
mr
to
update
the
documentation
page
to
have
another
column
for
product
product
design,
ux,
okay,.
A
Awesome
all
right
so
moving
on
to
my
to
the
next
point,
so
I'm
I'm
piggybacking
on
what
kai
suggested
on
slack
and
it
feels
like.
There's
like
we've
been
almost
there
for
quite
a
few
weeks,
and
I
think
we
all
felt
that
and
as
we're
seeing
even
though
we're
seeing
movement
and
things
are
being
resolved
and
everything
I
think
it's
an.
It
would
be
very
useful
to
have
a
clear
way
of
knowing
what's
left
right.
A
A
A
And
then,
please
feel
free
to
update
the
list
as
we
go.
The
other
thing
that
I
would
like
to
see
is
like
missing
tasks
for
the
working
group,
so
missing
goals
for
the
working
group.
These
are
things
that
we
need
to
accomplish
before
we
dismantle
the
working
group
and
then
let
the
process
run
itself.
A
Does
anyone
have
any
concrete
goals
that
we
still
need
to
nail
and
we
haven't
I'm
going
to
bring
up
the?
I
guess
it's
great
exit
criteria
now,
so,
let's,
let's
take
a
look
at
it,
add
it
together
right,
so
shepherd
implementation,
a
redesign
of
10
extensions.
I
feel
like
we're,
not
sure.
If
we
have
the
deer
do
we
have
10.
A
Eight,
nine
all
so
ten
are
being
worked
on.
So
that's
good.
The
shared
components
follows
the
report,
regions
design
guidelines.
So
I
feel
like
now
we're
in
a
stage
that
I
think
pretty
much.
Everything
has
been
implemented
so
jeremy
and
gina.
If
you
know
anything
from
the
reports,
regions,
design,
guidelines
or
the
framework
that
is
not
implemented
yet
do
let
us
know,
I
think,
we're
we
have
good
coverage
there.
A
So
probably
we
need
just
a
review
of
documentation.
I
feel
like
that's
the
last
bit
after
we
roll
it
out
to
customers
and
the
robot
is
successful
and
we
make
the
feature
flag
default
to
be
on.
We
have
to
have
documentation
in
place
to
make
sure
that
we
know
how
to
add
new
widgets
and
what's
the
process
there
so
probably
going
to
have
someone
in
charge
of
reviewing
documentation,
and
does
anybody
want
to
take
that
task
upon
themselves
to
complete.
A
I
can
ask
so
one
of
the
things
that
I've
had
chats
in
the
past,
with
our
technical
writer
is
amy.
Qualls
should
definitely
be
available
to
help
revise
like
the
wording
and
the
text
and
everything,
but
we
need
someone
to
drive
the
documentation
review
so
I'll,
probably
ping,
the
team
members.
So
the
working
group
members
and
try
to
come
up
with
a
candidate
to
do
that,
or
I
can
do
it
myself,
but
right
now
the
priority
is
to
roll
out.
A
B
A
A
B
B
It's
it's
a
minor
ux
kind
of
edge
case
where,
if
we're
using
link
and
supporting
text
we'll
end
up
kind
of
this
big
gap
and
then
this
stuff
close
together,
so
I
did
have
a
fix
which
kind
of
made
it
look
like
this.
The
text
would
wrap
to
the
next
layer
level,
but
it
doesn't
look
that
nice,
but
this
is
something
that
I
don't
know
if
we
need
more
ux
feedback
on
or
if
the
solution
I
I
kind
of
came
up
with
is
fine
again.
B
All
I
did
is
just
kind
of
tweaked
the
styles,
but
it's
not
changing
the
elements
per
se
other
than
what
it
kind
of
looks
like.
But
basically
what
happened
is
what
happens
when
the
supporting
text
is
very
long
and
it
will
just
wrap
to
the
next
line
kind
of
like
this.
So
that's,
okay
and
I
only
know
this
applies
to
license
compliance.
I
don't
know
if
the
other
widgets
have
enough.
B
A
A
Yeah
just
get
it
reviewed
by
ux
and
and
as
whether
it's
a
blocker
or
not,
I
mean
functionality
wise,
it's
working,
but
we
definitely
want
to
ship
something
into
good
shape,
so
I'll
treat
it
as
a
blocker
but
definitely
sounds
like
a
small
effort
either.
So
the
other
ones
seem
a
little
bit
longer
to
to
solve.
But
I
don't
want
us
to
get
to
a
position
where,
like
every
single,
like
low
severity,
cosmetic,
potentially
tweak
to
stop
the
block
to
stop
the
launch.
A
I
think
we
need
to
get
this
out
in
front
of
people
as
quickly
as
possible
so
that
we
can
start
getting
like
proper
feedback.
And
it's
that
that
that
conflict
of
iteration
like
we
want
to
release
early
and
iterate.
But
then
we
also
don't
want
to
release
something
that
is
not
properly
filling
our
requirements
so
to
speak.
So,
but
we
faced
that
in
code
review
a
lot
where
we're
doing
shipping,
something
that
we
know
has
a
bug,
but
it's
a
low
severity
bug.
But
we
know
that
the
bug
exists.