►
From YouTube: 2022-02-17 Working Group: Merge Request Report Widgets
Description
Nineteenth weekly meeting of the WG.
Agenda: https://docs.google.com/document/d/1bcch8UUkwmgEHFolTWDrQFJtUiiXlv_yQFAGwSSDSUE/edit
A
Hi
everyone
welcome
to
yet
another
weekly
call
for
the
merge
request
report
widgets.
I
have
lost
count
on
what
call
this
is,
but
it's
a
great
one
for
sure.
So,
let's
go
straight
to
so
announcements.
Ryan.
You
need
to
drop,
that's
fine.
Whenever
you
have
to
drop
drop
and
fernando
you
have
the
first
point
to
discuss.
B
Sure
so
yannick
and
I
met
earlier
this
week
to
sync
up
on
the
mr.
We
did
extensions
for
license
compliance.
You
know
I'm
picking
up
the
work
that
he
had
started,
but
some
questions
came
up
so
so
I
just
wanted
to
confirm
that
the
feature
flag
strategy
for
this,
so
I
think
we
were
digging
around
and
we
saw
the
refactor
mr
widget's
extensions
feature
flag.
B
So
first
part
of
the
question
is
that
the
correct
one
and
then
the
second
part
is:
do
we
plan
to
roll
these
out
together?
As
in
all
the
I
guess,
the
the
current
parts
of
the
merge
requests
that
are
using
are
going
to
be
migrated
to
these
extensions.
Are
they
all
rolling
out?
At
the
same
time,
okay,.
A
So
yeah
there's
those
two
steps
to
that
answer,
so
the
first
is:
there's
still
some
things
we
need
to
do
because,
right
now,
as
you
see
on
the
example,
mr,
when
the
feature
flag
is
enabled,
we
display
both
the
old
ones
and
the
new
ones
right.
So
that's
one
thing:
we
have
an
issue
for
it,
it's
currently
being
scheduled
for
this
next
milestone.
I
need
to
confirm
that
whether
it
gets
in
or
not,
but
it's
just
a
simple,
like
toggle,
just
not
render
the
old
ones.
A
If
it's
on
it's
very
simple,
that's
the
first
step.
The
second
is
basically
how
we're
going
to
start
to
roll
this
out,
and
in
this
moment,
when
you
enable
the
feature
flag,
all
of
them
will
be
shown
the
ones
that
are
currently
available
as
more
so
for
the
ones
that
are
still
in
development,
they're,
probably
going
to
need
individualized
feature
flex
from
then
on,
so
the
ones
that
are
ready.
A
I
think
the
one
the
the
strategy
that
we
discussed
in
the
past
was
that
once
we're
ready
to
turn
to
turn
it
all
on
and
the
the
full
support
of
the
core
widget
component
is
being
added.
We
can
start
rolling
it
out
for
gitlab.com
www.gate.com
and
then
gitlab
work,
gitlab
project
and
we'll
let
that
roll
for
a
couple
of
weeks
and
see
how
the
feedback
rolls
in
and
then
we'll
realize.
Is
this
mixed
look
a
problem?
A
Is
it
not
and
what
are
the
things
we
need
to
address
as
we're
developing
say
that,
for
example,
in
your
case,
you're
developing
a
widget,
and
it's
not
ready
yet
as
we're
about
to
turn
it
on.
We
can
then
make
that
call
whether
to
wait
for
you
or
just
to
roll
these
out,
and
you
just
introduce
one
individualized
feature
flag
for
your
own
widget,
and
that
way
you
can
control
when
you
want
to
turn
that
on.
B
Okay,
so
I
think,
and
that
now
that
clarifies
that's
what
I
suspected
something
along
the
lines
would
happen.
My
only
concern
is
like
nested
feature
flags
like
two
of
them
get
a
little
iffy
there,
but
I
mean
it's
doable.
So
I
think
what
I
can
do
is
it
sounds
like
in
the
meantime,
if
I
have
incremental
merch
requests
to
work
on
license
compliance,
I
don't
need
a
specific
feature
flag,
quite
yet
not
right
now,
but
I
should
at
least
keep
the
group
updated
in
these
weekly
sinks
on
the
status.
B
A
B
So
I
I'm
not
sure
if
you
guys
seen
the
screen
before,
maybe
in
the
past,
as
I
wasn't
in
the
earlier
meetings,
but
this
is
the
mr
widget
mox
for
licensed
compliance
and
what
had
been
discussed
before
is
like
the
sub
groupings
or
l3
feature.
I
guess
so.
The
question
was
I
I
think
I
have
three
options
here.
I
could
wait
for
l3
support.
I
could
help
with
l3
support.
B
You
know,
help
speed
that
up
and
then
I'd
be
able
to
do
something
like
this.
The
denied
uncategorizer
allowed
or
which
I
think
is
is
the
other
option
was
I
mean
kind
of
came
from.
The
discussion
was
if
we
had
if
we
had
no
l3
support
and
no
grouping,
and
these
were
just
all
one
level.
You
know
we
wouldn't
really
know
what
these
are.
B
The
only
indication
of
grouping
we
would
have
is
by
the
symbol,
the
icon,
but
you
have
no
context
to
it
so
that
brought
up
the
question
of
you
know
is
hovering
over
and
having
a
tool
tip.
You
know
part
of
the
ux
design
spec
for
these
generic
sorry
for
these
widget
extensions,
I
don't
know
what
the
stance
is
on
tool
tips.
Is
it
you
know
very
specific
to
certain
ui
components
or
it's
a
general
rule
that
you
know
for
how
those
should
be
implemented.
A
No,
I
can
answer
the
part
of
the
level
three,
so
level
three
was
already
on
schedule
for
this
milestone.
We
we,
I
think,
it's
slipping
for
the
next
one,
because
we
we
got
sidetracked
on
a
couple
of
other
stuff,
but
it
is
coming.
So
if
anything,
phil
from
what
I
heard
from
phil,
he
was
very
confident
in
the
way
that
he's
going
to
tackle
that.
So
I
don't
think
help
is
necessary.
A
You
are
kind
of
blocked
by
that
a
little
bit
so
eventually
he
can
send
it
for
your
review.
I'll
drop
a
line
to
him
for
him
to
be
aware
of
that,
but
I
don't
think
we
need
to
circumvent
that.
I
think
it's
coming
within
a
couple
of
not
days
but
a
week
or
so
should
be
coming
so
just
plan
for
that.
Accordingly,.
A
C
B
I
I
guess
I
I
guess
it's
a
follow-up
question
for
planning,
because
right
now,
I'm
technically,
I
could
be
unblocked
by
you-
know
not
having
them
grouped
just
not
having
l3
support
right.
But
then
the
question
is:
if
I
go
through
that
effort
and
we're
not
enabling
that
flag
anyway,
then
that
implementation
is,
you
know
it's
not
going
to
be
used
anyway
and
I'll
be
adding
l3
support
down
the
line
anyway.
B
So
I'm
in
this
in
between,
should
I
just
wait,
work
on
some
other
stuff,
which
is
I'm
leaning
towards
that
option,
and
I
could
convey
that
to
my
engineering
manager
and
I
can
work
on
other
stuff
because
you
know
originally.
I
think
the
plan
was
to
get
it
landed
last
milestone
in
the
interim,
but
if
we're
not
enabling
the
flag
anyway,
the
work
is
done
and
we're
going
to
end
up
migrating
it
to
the
l3
support
anyway.
So
what
kind
of
this
moon
will.
A
Stay
yeah.
I
think
I
think
if
we
had
the
feature
enabled
already,
we
would
follow
the
iteration
approach
and
you
would
yeah
roll
out
whatever
you
can,
but
it's
disabled.
So
I
think
it
might
as
well
just
wait
a
week
or
two.
You
can
still
have
it
in
the
milestone.
I
wouldn't
prevent
it
from
being
in
49,
but
maybe
plan
it
for
the
second
half
of
it.
Probably.
A
Okay,
thanks
for
clarifying
that
was
helpful
thanks
for
the
questions
anything
else
for
us
to
discuss,
I
forgot
to
announce,
but
the
documentations
have
been
merged.
I'm
going
to
find
the
link
it's
in
the
channel
topic
thing
bookmarks,
so
that's
a
technical
documentation
thanks
for
everyone
who
helped
with
that.
I'm
going
to
put
yes
thanks,
ryan.
Thank
you
so
much
for
the
note
taking
very
much
appreciated
so
there's
the
link.
A
A
A
Yep
so
who
will
run
the
meeting
in
your
absence?
I've
I've
asked
and
phil.
Sorry
tim
stepped
up
he's
not
here
today,
but
I'm
still
here,
but
he's
in
charge
of
making
sure
that
the
com
that
the
call
happens,
the
streamings
and
recordings
are
made
available.
So
if
he
can't
be
here,
we'll
find
someone
to
delegate
too
so
if
he
can't
probably
expect
him
to
ping
you
or
something
but
tim
tim
zalman,
so
just
to
be
clear
because
that's
also
team
noah
tim
zalman
will
be
my
replacement.