►
From YouTube: 2022-02-24 Working Group: Merge Request Report Widgets
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
Sure
so
I'm
sharing
my
screen
here
and
I
am
following
up
on
this
particular
issue
from
last
week.
So
I
guess
I'm
inheriting
this
work
from
yannick
and
the
this
has
a
I
guess,
prototype
and
mar
that's
like
a
proof
of
concept.
I
think
it
works
just
fine,
but
we're
in
this
in
between
state,
where
we
have
two
options.
We
could
try
to
push
forward
with
this
and
go
we're
missing
in
terms
of
the
designs.
B
I
think
we're
missing
level
three
support,
which
essentially
was
being
able
to
group
the
I'm
trying
to
find
a
good
screenshot
here
being
able
to
group
to
the
issue
being
able
to
group
the
categories
right
denied
uncategorized
allowed
and
I
think
that's
a
level
three
support
option.
So
the
workaround
was
to
roll
this
out
just
with
level
2
support.
B
But
what
I
was
saying
is
that
even
if
this
gets
merged
in
the
way
the
feature
flags
are
set
up,
this
may
not
ever
end
up
being
released
in
this
current
version,
because
right
now
the
feature
flag
is,
is
kind
of
like
a
bulk
flag,
where,
like
really
whatever
memoir
widgets,
are
being
rolled
out
in
the
first
batch.
You
know,
so
the
other
option
is
to
add
an
additional
feature,
a
separate
feature,
flag
and
roll
this
out
separately.
So
my
question
to
the
working
group
is:
do
we
want
to
wait
until
we're
like
the
spec?
B
I'm
sorry
that
you
know
the
support
in
the
extensions
is,
is
compliant
with
the
spec
completely
or
do
we
want
to
roll
out
what
we
have
now?
Does
that
like?
I
need
to
provide
the
feedback
to
the
engineering
managers
like?
Should
we
pursue
this
current
version,
or
should
we
wait
until
we
have
level
three
support
and
then
roll
out
with
that
and
roll
it
out
with
the
other
extensions
that
are
seem
to
be
going
out
at
the
same
time
right,
because
we
only
have
one
flag
to
control
all
this
so
yeah?
I
can
maybe.
C
C
So
it's
that's
the
main
reason
why
we
have
all
of
them
behind
one
flag.
If
you
now
have
a
case
where
we
would
have
an
mmr
widget
that
doesn't
yet
fully
comply
with
the
designs,
I
would
say
as
long
as
I
would
actually
make
the
decision
based
on
how
much
extra
work
is
it
to
add
that
in
later,
or
should
that
work
already
or
would
that
work
be
like
automatically
be
done
when
we
have
the
the
main
component
correctly
done.
B
Sure-
and
I
think
right
now,
it
like
the
way
we're
implementing
code
is,
I
can't
implement
with
the
l3
component
because
it
doesn't
exist
yet
so
it
wouldn't
be
like
once
it
exists,
we
can
use
it.
So
what
would
probably
happen?
Is
we
released
the
version
like
this?
We
added
new
feature
flags
to
toggle.
This
one
on
we
would
then
have
to
when
l3
is
available.
Support
is
available.
Then
we
have
to
go
back
and
update
that
component.
B
So
if
and
by
the
way
like
like
what
happened,
was
we
had
a
restructuring?
So
I
think
the
goal
initially
was
to
roll
this
out
last
milestone
now
under.
This
is
under
composition.
Analysis
now
that
I'm
under
it's.
This
is
being
pushed
forward
now
by
different
engineering
manager
and
they're
like
well.
We
could
wait,
and
I
and
the
pro
the
pm,
nicole
for
composition,
analysis
who
owns
this
area
is
like
yeah.
We
could
wait.
B
So
if
that
sounds
like
the
better
strategy,
just
for
consistency's
sake,
then
then
I
could
bring
that
feedback
back
and
we'll
just
defer
it.
I
just
didn't
want
to
derail
the
initial
efforts
as
I
inherited
this
work
and
there
was
a
lot
of
progress
made,
but
it
seems
like
the
decision
is
at
that
point.
We
should
wait,
but
I
will
build
on
this.
C
Everyone,
I
think
that
makes
a
ton
of
sense.
Thank
you
and
yeah.
I
I
just
want
to
make
sure
as
soon
as
we
have
this
l3
support,
that
it
won't
like
delay
the
other
pieces
even
further,
because
as
soon
as
we
have
the
core
component
really
ready,
it
would
be
really
amazing
to
have
all
the
other
widgets
soon
be
ready
and
then
switch
the
complete
feature
flag
very,
very
quickly
afterwards.
B
I
think
there
is
one
thing
on
the
designs.
Let
me
start
to
pull
that
up.
There
is
actually
no
nevermind
just.
I
think,
I'm
trying
to
think
while
everyone
wants
to
hear
was
it
like
icons
with
tooltips.
I
think
so.
I
don't
know
if
someone
here
had
commented
on
that,
like
that's,
not
a
pattern
right,
because
it
has
to
be
something
that
tool
tips
supposed
to
be
something
on
something.
That's
actionable
right,
because
I
think
that
was
the
feedback
I
got.
C
B
So
I
just
got
into
this,
so
actually
yannick
did
a
lot
of
the
preliminary
work
and
we
had
the
reorga
inherited
this
work,
so
I'm
still
kind
of
getting
up
to
speed
on
the
spec
and
the
designs
and
stuff.
So
as
of
now,
it's
making
sense,
but
I
haven't
had
enough
time
to
deep
dive
because
he
did
like
95
of
the
work
already.
D
B
D
A
C
I
can
give
my
own
impression
on
what
I've
seen
so
far
and
that's
most
often
it's
the
stage
group
designer
being
brought
in
but
oftentimes
they
reach
back
out
to,
for
example,
jeremy
or
to
other
designers
who
are
involved
in
that,
and
that's
one
big
reason
as
well.
Why
we
have
this
sample
project
where
all
of
the
mr's
have
or
where
one
mr
has
all
of
the
widgets
at
the
same
time,
so
that
we
can
also
spot
differences
quicker
afterwards.
C
E
C
A
Okay,
cool
thanks
for
clarifying,
and
I'm
asking
this
because
I
know
that
forecasting
now
pipelining
fights
with
you
have
a
couple
of
those
that
have
been
also
on
the
l3
and
it's
been
very
quiet
for
a
while.
So
I
just
wanted
to
hear
if
it
anything
changed
in
terms
of
ux
reviews
over
the
last
few
weeks.