►
Description
Weekly call for the working group Merge Request Report Widgets.
This was the last call of this working group. Congratulations and thank you, everyone.
Agenda:
https://docs.google.com/document/d/1bcch8UUkwmgEHFolTWDrQFJtUiiXlv_yQFAGwSSDSUE/edit
A
We
are
live,
welcome
everybody
to
yet
another
very
special
weekly
call
of
the
working
group
for
merge,
request
report
widgets
today
is
our
last
call
for
the
working
group.
So
I'm
glad
to
see
everyone
here
and
essentially
I'll
just
go
straight
to
the
agenda
and
nothing
changed
on
the
checklists.
The
launch
is
still
green
and
the
wrap
up
for
the
working
group
is
obviously
green,
because
it's
already
hinted
that
it's
the
last
call
so
before
I
move
on
to
the
final
point:
is
there
anything
that
anybody
has
to
discuss
any
concerns?
Anything
at.
A
All
awesome
so
forever
hold
your
peace.
Is
that
what
they
say
so
that
brings
me
to
the
final
point
of
the
working
group
which
we
have
been
discussing
this
over
the
past
few
weeks.
The
mission
that
the
working
group
has
set
itself
to
accomplish
has
been
accomplished.
A
Basically,
the
axis
criteria
that
we
have
in
our
page
has
been
fulfilled,
so
I'll
go
I'll,
go
quickly
over
it
just
so
that
we
can
all
have
conscious
of
that.
Just
give
one.
Second,
that's
our
group.
That's
the
exit
criteria.
A
A
Both
both
engineering
and
ux,
we
have
everybody
established
their
own
owners.
The
code
for
the
base
of
component
has
been
implemented
to
implement
the
ux
framework.
Second,
I
lost
myself
a
little
bit
on
the
tabs.
Where
was
I
there?
I
was
so
even
those
that
are
not
shipped.
The
core
component
is
ready
as
much
as
we
can
to
to
to
support
them.
So
now
we'll
let
those
dris
take
that
to
fruition.
A
The
shared
component
follows
the
report
region's
design
guidelines,
as
defined
in
the
pajamas
design
system,
such
as
so
all
the
widgets
that
have
been
deployed
have
been
done
with
ux
approval,
and
that
puts
us
in
a
good
spot
in
terms
of
moving
forward.
The
documentation
reflects
the
capabilities
of
the
shared
component.
A
We
do
have
the
let's
see
if
I
have
it
here
in
my
links,
documentation
the
documentation
documentation.
I
should
have
seen
that
I
should
have
report
widget,
request,
widgets,
sorry,
I
should
have
gotten
this
way.
This
thing
ready,
docs
widget
anyway.
Anybody.
B
A
Link
over
there
that
you
can
help
me
on
try
to
get
the
link
for
the
documentation.
B
A
You
docs
there,
it
is
found
it.
Thank
you.
I
should
have
asked
you
helped
with
it
with
your
mind.
So
this
is
the
documentation
and
everybody's
done
a
great
job
at
basically
making
this
documentation
evolve
over
time
as
we've
added
support,
as
we've
added
all
all
of
the
things,
and
now
that
we
have
a
version
two
in
the
works
that
will
also
update
the
documentation
once
it's
ready.
A
So
coming
back
to
the
report
widgets,
it
reflects
the
capability
of
the
share
component.
It
does
so
indeed,
it
has
been
reviewed
also
by
the
technical
writer
amy
claus.
At
the
end,
we
also
had
samantha
ming,
take
a
look
at
it
and
they
both
approved
it,
and
we
all
felt
it
was
comfortable
enough
to
go
ahead
and
ensure
there
is
clear
documentation
written
for
extending
the
component.
A
So
that
is
also
we
discussed
this
in
the
past
meeting,
where
we
realized
that
the
documentation
for
extending
and
to
contribute
things
to
the
merger
requests
would
fulfill
this
role,
so
that
is
also
fulfilled
and
with
that.
That
concludes
all
the
exit
criteria
and
with
so
I'll
stop
sharing
the
screen
which
basically
gets
us
to
where
we
need
to
be
to
close
off
the
working
group.
I
will
say
that
there
are
still
ongoing
efforts
that
have
been
evolving
basically
outside
of
the
working
group.
A
Already
they
have
owners,
so
basically,
v2
version
is
owned
by
savage
who's
working
on
his
widget
and
that
will
go
on
and
we'll
all
be
involved
as
much
as
necessary
through
ux
approvals
and
all
that
stuff.
But
that's
already
beyond
the
exit
criteria
of
the
working
group
and
we're
very
looking
forward
to
see
that
coming
to
fruition,
the
telemetry
is
also
another
effort,
that's
ongoing.
It's
all
the
issues
have
been
assigned
to
the
dris
of
the
widgets.
A
B
A
Are
the
two
things
that
I
know
about
that?
I
can
mention
here
so
thanks
everybody
who
went
there
who
who
helped
there
and
right
we
have
the
arise
so
that
we
can
take
care
of
any
potential
future
concerns
and
that's
it.
I
don't
have
anything
else
to
add,
but
before
before
the
end
we
I
would
like
to
deeply
thank
everybody
who
contributed
to
this
working
group.
It's
been
a
long
time
running.
A
I
forgot
when
we
created
it,
but
it's
been
oh
august
1st,
so
it's
been
a
year,
so
that's
good.
I
hadn't
even
noticed
that,
but
we
all
know
that
working
groups
do
tend
to
go
a
little
longer
than
expected,
but
we
all
kept
a
good
momentum.
The
the
only
time
that
I
saw
the
working
group
stall
a
little
bit
was
now
towards
the
end,
where
everybody
has
been
aware
that
we're
very
close
to
the
end
we're
just
waiting
for
the
actual
ceremony.
A
But
yes,
thank
you,
everybody
who
contributed
even
those
who
are
not
at
the
company
anymore.
If
you
watch
the
recording.
Thank
you
so
much
for
the
contributions
at
the
beginning.
I
cannot
stress
enough
how
how
much
you
contributed
to
the
success
of
the
working
group.
We
wouldn't
be
able
to
do
it
without
you
yeah,
so
I
wanted
to
pass
the
word.
Does
anybody
want
to
say
anything
tim?
You
have
a
have
a
little
say
here.
So,
yes,.
B
Onto
you,
I
just
wanted
to
underline
everything
that
andre
said
thanks
a
lot
for
everyone's
work,
really
great
job
of
completing
that,
and
I,
as
this
was
really
a
topic
that
was
so
wide.
I
think
it
it's
a
great
accomplishment
to
her
to
to
do
this,
all
over
all
the
different
teams
and
the
sections
and
get
this
done.
B
It's
all
or
multiple
years
of
work,
but
so
seeing
it
now
and
what
was
the
best
reminder
for
me
was
I
saw
a
couple
of
weeks,
a
screenshot
on
a
support
ticket,
seeing
the
merge
request
page
from
error
report
and
how
it
looks
then,
and
how
sorted
it
is
and
knowing
how
well
organized,
and
especially
without
in
the
future,
having
problems
with
people
stepping
on
each
other's
toes
as
this
gets
a
crowded
place
in
that
sense
functionality
wise.
B
I
think
this
is
a
great
accomplishment
and
especially
seeing
that
the
working
group
not
only
has
done
the
job
created
documentation
but
has
really
created
also
a
path
forward
and
a
momentum
forward.
It's
great
to
see
all
all
the
outcomes
of
that
work.
So
thanks
everyone
of
you.
On
top
of
that,
congratulations,
andre
for
completing
your
first
working
group
and
leading
it
really
nicely
well
organized
and
completing
successfully.
So
thanks,
everyone
again,
and
especially
everyone
on
the
call
so.
A
Thanks
tim,
it
was
all
them.
You
know
it's
like
yeah,
so
we'll
take
care
of
the
last
task,
which
will
be
to
update
the
documentation
on
the
handbook
to
move
the
the
working
group
to
the
archive
and
keep
that
updated.
A
A
A
Okay,
I
think
I
got
it
I'll
put
it
in
the
slack
channel.
That's
just
for
internal
consumption.
B
A
Again,
everyone-
and
I
I
bid
you
all
farewell
and
thank
you
for
all
your
hard
work.
It's
done.
Bye
folks,
take
care.