►
From YouTube: 2021-09-09 Working Group: Merge Request Report Widgets
Description
Third weekly meeting.
Agenda:
https://docs.google.com/document/d/1bcch8UUkwmgEHFolTWDrQFJtUiiXlv_yQFAGwSSDSUE/edit#
A
A
So
this
is
this
is
the
epic
that
we
discussed
previously
that's
going
to
track
the
two
engineering
efforts.
One
is
the
updating,
the
core
component
with
the
functionality
and
the
support
of
the
ux
framework,
and
the
other
is
the
actual
rewriting
of
the
actual
widgets
to
use
that
core
component
scott
scott
is
going
to
lead
that
effort
to
rewrite
the
extensions
and
he's
going
to
kick
the
tires
of
the
core
component
and
then
we'll
go
from
there,
but
they're
created.
A
B
Yeah,
I
didn't
think
I
would
be,
but
here
I
am
yeah.
It
looks
like
this
has
already
kind
of
been
discussed
a
little
bit,
but
I
wanted
to
make
sure
or
just
find
out
if
it
was
possible
when
this
is
being
implemented
or
built
out
to
keep
in
mind
that
it
would
be
really
fantastic
if
we
added
telemetry
to
the
same
areas
of
each
widget.
So
we
have
consistent
data
across
each
widget
and
I
see
that
we
already
have
some
unlike
the
expand
button,
which
is
a
good
place.
A
A
C
Yeah,
I
can
finish
typing
this,
I
think,
from
a
product
perspective,
this
would
be
invaluable.
It's
one
of
the
questions
that
we've
had
sort
of
from
the
beginning.
Anyways
is
how
valuable
are
these
widgets
and
should
they
be
in
the
merch
request
to
begin
with,
and
so
that's
sort
of
the
questions
we
need
to
continue
to
answer.
C
We
know
we
need
to
fix
all
these
inconsistencies
first
and
then
the
next
question
we
want
to
answer
is:
should
they
be
there?
How
much
interactions
do
they
actually
get
compared
to
all
the
other
actions
and
information?
We
ask
people
to
take
on
a
merge
request,
and
so
I'm
very
supportive
of
doing
this.
The
code
review
group
instrumented,
actually
several
groups
widgets
that
weren't
instrumented
at
all,
which
is
why
there
is
some
tracking,
because
we
we
need
to
just
start
answering
that
question
already,
but
I'd
say
this
is
important
to
keep
in
mind.
A
Any
more
thoughts
here
can
we
move
on
sweet
ryan
has
a
point
since
she's,
not
here
I'll
voice.
So
once
the
team
start
working
on
widgets
and
components,
please
help
us
facilitate
the
ux
review
of
the
design
framework
by
assigning
the
mrsa
product
designer
based
on
the
assignments
in
the
appropriate
devops
stage.
Group.
A
Okay,
I
can
reply.
This
is
useful
to
know
because
that
we
already
planned
to
include
ux.
This
provides
a
mapping,
so
it's
gonna
be
useful.
I
do
think
there's
probably
tim.
You
might
might
have
some
insight
into
this.
The
ux
framework
is
in
itself
a
deliverable.
So
when
we
update
the
core
component,
we're
going
to
be
using
that
ref,
that
is
reference
we
will
still
want
to
have
that
work,
reviewed
and
that
will
go
to
either
one
of
the
members
either
you
or
marcel
or
ryan
right.
D
A
A
That's
good,
but
this
is
really
good
I'd
say
no.
On
that
sense,
the
I
can
provide
an
update
on
on
the
the
state
of
it.
We
we
are
attending
an
effort
to
break
down
the
epic
I
already
informally
discussed
with
phil,
but
I
plan
on
on
doing
it
until
the
end
of
this
week
to
break
down
into
further
issues
and
I'll
be
tagging.
You
I'll
be
sharing
it
in
the
slack
channel
about
which
who
would
be
available
to
pick
what
are
the
issues?
A
So
the
idea
is
to
paralyze
the
effort
to
update
the
core
component
and
with
an
upcoming,
milestone
and
backhand
kind
of,
like
still
focus
on
the
engineering
allocation,
to
provide
this
ample
time
to
to
spread
that
around
with
many
people
so
update
on
the
epic
deconstruction
into
issues
it's
coming.
I
feel
like
that's
a
good
summary
until
the
end
of
the
week.
A
All
right,
we
don't
have
anything
else
on
the
agenda,
I'd
like
to
take
the
opportunity
that
we
have
tim
on
the
call
for
the
first
time
and
you're,
like
the
the
sponsor
of
the
working
group,
is
there
anything
in
your
mind.
That
is
not
clear
about
the
working
group,
anything
that
you'd
like
to
clarify
from
your
end.
Are
you
happy
with
what
you've
seen
so
far
give
us
your
feedback
so
far.
D
D
E
It,
but
I'm
just
here
that
that's
the
main,
the
only
thing
I
can
do
anyway.
First
of
all
the
times
that
worked
for
me,
I
was
just
on
holiday
in
august,
and
I
really
enjoyed
it.
Quick
food
highly
highly
appreciates
to
already
miss
it
a
week
later,
but
the
time
still
works
for
me,
it's
just
that
we
have
currently
the
dot
com
stand
up,
which
is
right
before
that
call.
So
this
normally
works
quite
well
for
me,
so
happy
with
that.
E
E
A
Not
entirely,
but
that's
a
great
idea
to
have
the
board,
I
think
once
the
once.
The
issues
start
filling
in
I
feel
like
that
would
be
useful.
Oh
sorry,
it
would
be
useful
to
have
the
overview
and
we
did
talk
about
having
issues
to
track
the
updating
of
documentation
discussing
the
process.
This
telemetry
might
be
another
one,
so
as
the
epic
gets
filled
up
will
will
take
care
of
we'll
open
a
board
as
well
and
I'll
share
it.
Here.
That's
a
good
idea.
E
And-
and
the
other
question
for
me
always
in
working
groups-
is:
do
we
already
know
to
100
what
we
need
to
do,
or
is
it
rather
like?
We
want
to
get
to
this,
but
we
have
no
clue
yet
how
we
are
going
to
resolve
it
so
that
we
might
hit
some
roadblocks
across
the
path
here
it
seems
we
are
way
more
already
focused
on
a
very
quite
clear
path.
We
know
what
we
need
to
do.
E
We
just
we
will
follow
it
through
with
the
working
group,
because,
for
example,
I
have
currently
that
I'm
sponsoring
the
other,
the
observability
in
front
and
working
group,
and
there
it
was
there
was
just
we
want
to
improve
observability,
but
we
don't
know
exactly
yet
and
now
we
have
had
hit
the
roadblock
where
we
rather
want.
The
first
thing
that
we
want
to
get
done
is
upgrade
sentry,
which
is
now
a
budget
discussion,
etc.
So
we
are
basically
pausing
it.
So
I
just
wanted
to
know
if
you
still
see
any
roadblocks.
E
A
I'll
start
with
my
tape,
but
please
everyone
else
fill
in
so
yeah.
I
think
you're
right.
I
think
here
we
have
a
clear,
clearer
distinction,
clear
idea,
what
we
need
to
where
we
need
to
get
there
where
we
need
to
get
to
and
how
we
need
to
get
there.
It's
more.
The
challenge
is
more
about
coordinating
the
efforts
in
making
sure
that
everybody
is
on
the
same
page
and
having
the
working
group.
A
We
decided
last
week
whether
we
should
have
it
at
the
end
of
the
quarter,
the
current
quarter
or
the
end
of
the
second
of
the
next
quarter,
and
the
idea
is
that
we
are
going
to
target
to
finish
as
many
widgets
as
we
can
during
this
quarter,
but
there's
still
going
to
be
cleanup,
documentation,
updates,
process,
revisions
and
all
that
that
we
want
to
make
sure
that
are
useful.
So
the
exit
criteria
is
pretty
clear
and
on
the
epic
we
have
shepherding
the
implementation
and
then
making
sure
that
the
shared
component
follows
the
reports.
A
So
here
on
the
app
we
have
this
shepard
implementation.
Are
you
seeing
my
screen?
Yeah,
okay,
shepherding
the
implementation
of
redesign
of
the
10
extensions,
the
full
list
there?
The
shared
component
follows
the
report
region's
design
guidelines.
That's
that's
what
we
usually
call
ux
framework.
We
have
the
documentation
reflecting
the
capabilities
of
the
shared
component
and
there
is
a
clear
documentation
written
for
how
to
extend
the
component.
That's
because
we're
not
going
to
be
by
default,
offering
the
option
of
slots.
A
So
these
are
the
main
four
end
goals
and
I
think
it's
pretty
clear
that
we
can
start
these
two.
In
parallel,
the
last
two
will
be
ongoing
and
if
I'm
not
mistaken,
the
process,
documentation
and
everything
has
been
claimed
by
tim
noah
to
make
sure
that
that
gets.
It's
not
it's
probably
too
early
to
start
delivering
on
that,
but
it
is
on
his
field
right,
jim
yeah,.
D
Correct
there's
a
reason
why
I
didn't
create
the
issue
just
before
I
left
and
I
need
to
have
a
quick
conversation
with
kai.
We
can
probably
do
this
async,
but
it's
just
in
relation
to
making
the
the
the
ux
review
and
also
just
the
implementation
review
of
the
actual
framework,
a
subset
of
what's
already
existing
within
the.
I
believe
it's
called
the
collaboration
the
murder
cast
experience,
so
I
just
want
to
make
sure
that
I
don't
create
something
that
is
in
tandem
I'd.
D
A
All
right
sounds
good.
Is
that
clear?
Does
that
answer
the
question
tim
is?
It
sounds
good
all
right,
scott,
since
you're
on
the
call,
can
we
ask
for
a
little
update?
What's
your
plan
on
on
the
start,
to
rewrite
the
more
basic
extensions
that
we
have
is.
Is
that
something
that
you're
aiming
for
the
next
milestone?
What's
what's
the
situation
and
plan
so
far,.
F
So
trying
to
get
it
started.
Hopefully
this
milestone
if
we
have
capacity,
but
definitely
the
next
milestone.
I've
asked
either
miranda
payton
or
jose
to
start
take
up
either
low
performance
for
web
performance
whenever
they're
ready.
So
I
pinged
them
all
on
each
of
those
issues
shown
demo
projects.
So
it's
easy
for
them
to
take
up
and
clone
locally.
A
Awesome
that
sounds
sounds
good
and
by
that
time
we
also
expect
to
start
extending
the
car
component
with
the
ux
framework
adjustments.
So
from
what
the
looks
of
it
is
going
to
be
around
one
issue
for
adding
the
icons
one
issue
for
aligning
the
buttons
and
the
other
one
for
like
alignment
generically
speaking
and
we're
going
to
kick
start
that
up.
We
do
have
some
struggles
with
capacitive
144
for
code
review,
which
is
where
phil
is,
but
we
do
expect
I'll
be
able
to
fit
in
a
bit
of
that.
A
That's
why
we're
looking
for
potentially
some
other
help,
but
I'll
I'll
share
it
on
the
channel
once
we
have
the
epic
broken
down,
and
it
feels
like
14
4,
we'll
start
to
see
some
movement
from
the
engineering
side
on
both
sides.
So
scott,
my
question
to
you
is
there
is
an
expectation
just
making
sure
is
the
expectation
that
once
we
start
that
work
we'll
be
delivering
it
right
on
that
milestone
the
final
version
of
the
rewrite
or
is
it
understanding?
A
F
Yeah,
it's
something
I've
been
thinking
about
as
well.
We
might
feature
flag
it
instead,
if,
if
we
find
that
it's
not
the
the
core
component
is
not
quite
enough
for
the
the
proposed
design.
So
if
we
feature
flag
it,
then
we
can
follow
up
with
some
issues
afterwards
and
add
it.
I
would
like
to
have
like
a
closed
issue
in
14
4
and
maybe
propose
some
like
follow-up
issues
to
either
update
the
icons
or
whatever
is
needed.
There.
A
Okay,
keep
the
group
posted
on
the
feature
flag
approach,
as
I
expect
there'll
be
other
cases
and
we'll
be
imported
to
discuss
how
we'll
be
implementing
that
feature
flex
system,
whether
we
have
one
feature
flag
for
all
of
them,
whether
we
have
one
feature
flag
for
each
one
of
them,
making
sure
that
everybody's
on
the
same
page.
So
we
don't
have
like
different
approaches
for
each
one
of
them,
but
yeah
just
post.
It.