►
From YouTube: 2022-01-20 Working Group: Merge Request Report Widgets
Description
Fifteenth weekly meeting of the Working Group.
Agenda: https://docs.google.com/document/d/1bcch8UUkwmgEHFolTWDrQFJtUiiXlv_yQFAGwSSDSUE/edit#
A
All
right
we're
live
on
youtube.
Welcome
everyone
to
yet
another
weekly
meeting
of
the
working
group
for
merge
requests
report
widgets,
I'm
gonna!
Guess
it's
the
15th
session
that
we've
had.
We
have
a
short
agenda,
so
I'll
jump
right
through
it
to
it.
So
last
week
we
discussed
what
happened
when
this
working
group
dismantles
after
it's
it's
closed,
that
the
working
group
label
then
would
no
longer
apply
so
we're
starting
to
prepare
for
that.
A
We
discussed
the
creation
of
one
more
label
that
will
basically
be
used
for
anything
related
to
this
efforts,
especially
as
we
see
more
report
widgets
coming
in
the
future
and
maintenance
and
report
bug
reports
and
everything.
So
it's
good
to
have
something
to
put
it
under.
So
I
created
a
a
a
label.
A
Basically,
I
applied
to
a
couple
of
issues
that
we're
working
on
in
code
review,
but
the
idea
is
to
spread
it
around
use
it
for
anything
that
you
can
come
up
with
anything
you
create
just
add
that
label,
especially
as
the
merger.
The
working
group
is
coming
to
a
close
soon.
Hopefully,
that's
our
the
idea,
the
it
was
slated
for
the
end
of
the
quarter,
so
yeah.
That's
that
I
have
some
questions.
I
created
this
on
gitlab.org,
I'm
guessing.
A
Right
I'll
do
it?
Yes,
do
we
have
any
color
codes
for
the
labels
that
would
apply
in
this
case,
or
is
that
bright,
green
enough,
acceptable.
A
All
right
in
portugal
that
would
be
like
a
two
hour
discussion
about
being
fika
and
sporting
clubs,
but
I
don't
follow
football
right
same
here
in
vienna.
Do
you
have
a
green
one?
A
All
right,
then,
that's
good
thanks
for
the
feedback,
and
so
after
this
call
I'll
just
go
into
the
list
of
issues
epics
and
merge
requests.
I
currently
have
the
working
group
label
and
we'll
apply
this
new
one.
There
will
be
a
bit
of
duplication
for
this
transition
period,
but
I
want
this
to
get
like
started
with
this,
so
that
it
feels
more
natural
to
attach
it
to
the
topic
than
the
working
group,
which
will
go
extinct
soon.
Any
objections
of
applying
that
to
all.
A
Right,
no
right,
that's
it!
For
me.
We
have
great
work
in
fight
this
milestone.
I
didn't
put
it
here,
but
they're
planned
for
the
milestone
code.
Review
is
working
on
a
couple
of
things.
I
know
the
patent
is
working
on
documentation
for
the
polling,
so
it
feels
like
we're
we're
getting
somewhere.
So
I'm
not
entirely
sure
we'll
wrap
up
everything
we
needed
to
wrap
up
by
the
end
of
the
quarter,
but
being
a
working
group,
not
necessarily
in
okr.
I
feel
like
it's
not
the
end
of
the
world.
If
we
slip
over
what?
A
Okay,
then
we're
not
we're
not
in
a
good
place,
we're
reaching
out
the
end
of
the
of
the
list
of
issues
that
are
known.
So,
if
any
of
you
find
any
issues
bug
reports,
please
keep
them
reported
there.
I
don't
know
if
I've
mentioned
this
here,
but
I
am
probably
going
to
go
absent
soon
in
a
couple
of
weeks
in
parental
leave.
A
A
So
please,
if
anything
happens,
you
need
someone
to
move
something
along.
Don't
panic,
reach
out
to
kuchal,
so
yeah
I'll
just
put
here
the
link
to
the
coverage
issue
so
that
in
case
you
know
for
my
parent
relief
and
that's
basically,
it
I'll
be
out.
A
D
Absolutely
that
is
planned
currently
just
sorting
out
my
deliverables
for
this
milestone,
but
I'm
planning
to
speak
with
them
about
this
next
week.
Sure
so.