►
From YouTube: Work Item Weekly Sync - 2021-09-21
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
B
Know
I'm
gonna
zoom
in
so
I
I
spent
some
time
exploring
ways
to
add
the
type
selector
option.
I
mean
I've
gone
through
several
iterations,
including
down
here.
B
Actually
this
is
the
selector,
so
I
started
out
experimenting
with
different
ways
to
present
the
select
type
button.
I
explored
a
lot
of
different
styles,
going
with
an
actual
button,
going
with
a
drop
down,
exploring
various
options
and
chatted
with
gabe
sum
yesterday,
and
I
know
that
you
had
also
echoed
this
previously
donald
that
it's
it's
beneficial
from
an
engineering
standpoint
to
have
consistency
in
the
create
view
and
the
detail,
view
or
view
version
of
the
page.
B
So
now
I'm
exploring
going
with
more
of
an
explicit
title
and
then
perhaps
select
button,
but
then
once
you
have
applied
something
you
know
it
would
look
a
bit
more
like
this
because
we're
not
giving
them
the
option
to
go
back
and
change
initially,
at
least
for
mvc
from
one
type
to
another
and
so
any
questions
or
concerns
about
just
kind
of
going
with
an
approach.
That's
a
bit
more
like
this.
B
Part
of
also
what
I
was
striving
to
accomplish
was
the
view
that
had
the
select
type
like
over
here
and
add
a
signee-
and
this
is
probably
a
bit
more
for
martian-
was
that
I
was
looking
to
be
a
bit
more
instructive
and
offer
a
bit
more
guidance
to
the
user
as
to
what
to
do
so.
I'm
hoping
that
this
helps
to
kind
of
address
both
problems
and
that
we
have
some
language
that
gives
them
guidance.
B
B
Something
else
that
I
am
also
proposing
is
that
currently,
our
radio
buttons
look
a
bit
more
like
this
in
the
product,
but
I'm
going
to
propose
that
we
go
with
something
that's
a
bit
more
like
this,
particularly
for
mobile,
so
it
would
have
a
selected
state.
That
would
maybe
be
like
a
solid
background.
I
think
that's
a
little
easier
in
a
mobile
setting
in
particular
to
quickly
identify
what
has
been
selected
as
opposed
to
just
a
tiny
radio
button.
B
A
Holly,
what's
the
what's
the
process
look
like
for
that,
when
you
say
proposing
it,
is
that
proposing
it
to
the
foundations
team
for
a
change
within
pajamas
or
proposing
it
for
the
pattern
we're
going
to
use
within
work
items.
B
That
is
a
very
good
question.
It's
kind
of
both,
but
because
this
is
a
new
pattern,
foundations
will
need
to
be
looped
in
I.
I
don't
really
know
that
they're
going
to
push
back
too
much,
but
they
might
so.
My
proposal
is
definitely
for
the
group,
but
then
separately.
I
will
need
to
include
them
in
that
conversation
just
so
that
they
know
that
this
is
what
I'm
suggesting
and
then
also
I
have
to
talk
about.
B
Why,
of
course,
I'm
not
looking
to
use
an
existing
pattern
again
if
we
find
that,
for
whatever
reason
the
foundations
team
has
strong
concerns
and
we
need
to
go
back
to
more
of
a
radio
button
approach,
I'm
I'm
not
thinking
that
it's
going
to
be
a
critical
negative
impact
on
the
user
experience
if
we
go
with
traditional
radio
buttons.
I
just
think
that
it's,
maybe
not
quite
as
clear.
B
So
I
don't
mind,
you
know
adapting
the
current
standard
if
they
prefer
for
mvc
and
then
exploring
ways
to
maybe
improve
that
experience
for
mobile
in
the
future.
Does
that
answer?
The
question
summary
is
yes
for
this:
yes
for
foundations,
but
then
also
the
foundations.
If
they
push
back
a
lot
or
if
they
have
strong
concerns,
maybe
from
an
accessibility
standpoint,
then
I
will
at
that
point
be
content
to
roll
back
to
more
of
a
traditional
radio
button.
If
we
need
to.
D
Another
question
so
holly
on
the
type
selector
when
that
kind
of,
like
which
looks
very
nice
by
the
way.
So
are
you
saying
about
this
view
yeah?
So
you
you
tap
like,
I
guess
you
tap,
select
type
on
the
sort
of
initial
form
and
then
this
opens
up
and
then
you
can
choose
which
of
the
the
types
you
want.
What
will
this
look
like
on
on
desktop?
Like
would,
would
you
expect
the
same
behavior
or
would
it
just
be
a
drop
down?
I'm
just
curious.
B
That's
actually
a
great
question
as
well,
and
something
that
I
forgot
to
mention
is
in
this
view
the
thought
is
that
you
open
up
this
view,
which,
in
mo
mobile
environment,
would
be
like
a
panel
that
overlays
you
select,
maybe
feature,
and
then
it
would
apply
and
close,
I'm
still
thinking
through,
like
the
consequences
of
that,
because
I
do
wonder
if,
if
it
puts
people
in
a
difficult
situation
where
they
may
have
selected
the
wrong
thing
and
didn't
realize
it,
but
they
do
have
confirmation
on
this
screen
as
to
what
they've
selected
on
the
this
view
here.
B
So
I'm
not
as
concerned
about
that
in
a
desktop
setting.
I
have
not
created
that
design
yet
so
I
haven't
fully
thought
through
it,
but
the
proposal
for
desktop
previously
has
been
that
these
elements
would
all
function
very.
Similarly,
it
would
just
be
in
kind
of
a
like
a
little
pop
over
box,
so
I
would
expect
it
to
be
the
same.
In
that
case,
it
would
just
be
a
pop
over
as
opposed
to
a
full
screen
overlay
like
it
is
in
mobile
and
I'm
happy
to
show
the
prototype.
If
that
would
be
helpful
as
well.
D
I
don't
specifically
need
to
see
the
prototype.
I
think
I
get
it.
That
sounds
good
and
then
a
second
question
with
regards
to
and
and
feel
free
to
tell
me
that
this
is
like
we're
designing
for
the
the
mvc
and
just
not
going
past
that
curious
about
a
environment
where
we
might
have.
You
know
if
there's
a
situation
where
there
are
dozens
of
types
would
we
put
like
a
search
for
the
type
that
you
like?
Hopefully
that's
not
the
case
right
like
I.
D
Ideally
we
don't
have
users
making
you
know
hundreds
of
different
types
and
and
creating
them,
but
yeah
I'm
curious.
Would
we
would
we
need
to
do
that?
Like
would
we
need
to
have
like
some
sort
of
filtering
for
the
types
themselves
when
you're
selecting
them.
B
I
think
that's
a
great
question
that
might
be
something
gabe
would
want
to
comment
on
as
well,
but
I
think
the
long-term
vision
for
it
is
that
they
can
create
their
own
types.
Is
that
correct
gabe?
In
which
case
there
could
be
any
potential
number?
I
would
imagine,
and
a
search
makes
sense
to
me
in
that
in
that
situation
to
offer
some
filtering.
C
B
From
an
engineering
standpoint,
once
these
decisions
are
finalized-
and
I
say
that
pretty
confidently,
because
I
they're
very
minor
changes
in
my
opinion
from
what
was
originally
proposed,
and
I
definitely
don't
see
pushback
necessarily
from
foundations
for
these
proposals.
It's
just
maybe
the
the
challenge
of
whether
or
not
we
go
with
the
sort
of
blue
highlighted
box
versus
this
box.
B
What
would
be
beneficial
to
you,
the
engineers
in
terms
of
documentation,
for
me
to
get
this
to
you?
How
can
I
communicate
this
to
you
in
the
best
way?
That
would
be
most
valuable
for
you.
A
From
our
side,
I
think
just
we
can
update
the
designs
within
the
design
issue
and
then
we'll
just
add
a
comment
or
description
or
something
in
the
description
for
some
of
the
like
the
crate
issue
or
the
great
feature
issue,
and
the
view
feature
issue
saying
that
hey
these
designs
have
have
changed.
Please
revisit
I
put
a
comment
in
the
zoom
chat,
but
it
would
also
be
helpful
if
you
showed
this
tomorrow
in
our
plan
weekly.
A
Just
I
think,
there's
more
participants
there
and
then
we
might
be
able
to
get
real-time
feedback
from
the
people
that
are
at
that
meeting.
Learn
that
I
think
that's
from
our
side.
That's
probably
all
we
we
need
if
there's
any
like
acceptance
criteria
that
needs
to
be
changed
off
of
the
designs,
which
I
don't
think
there
are
because
we're
not
really
changing
functionality,
but
we
can
go
ahead
and
go
ahead
and
change
that
after
the
designs
are
finalized.
A
B
I'm
making
a
note,
so
I
am
happy
to
update
the
the
view
issue
the
create
issue,
and
then
I
also
had
that
sort
of
overall
in
the
c1
design
issue.
So
I'll
update
all
of
them
with
the
final
proposal
and
then
I'm
happy
to
present
tomorrow
as
well
just
to
get
everybody
up
to
speed.
C
So
you
were
thinking
about
these
text-related.
C
The
questions
are
you
like:
how
can
I
help
like?
Are
you
still
deciding
or
are
going
to
share
it
with
other
people.
B
I
would
love
your
thoughts
at
any
given
moment.
So
if
you
see
anything
here
that
you
would
like
to
change
like
this
verbiage,
for
example,
that's
associated
with
each
of
these
items,
I
pulled
from
an
issue
that
we
have
in
place
currently
for
issue
types.
I
think
maybe
myself
or
gabe
wrote
this
up
at
some
point.
B
It
almost
certainly
needs
to
be
revisited
and
maybe
cleaned
up
and
tweaked
a
little
bit
so
any
thoughts
you
have
on
that
any
thoughts
you
have
on
the
micro
copies,
such
as
the
verbiage
surrounding
kind
of
instructing
the
user
in
this
create
state
any
any
thoughts
that
you
have
surrounding
those.
I
would
love
to
hear
and
marsha
and
I'll
tag
you
in
those
issues
as
well.
C
Do
it
I
don't
know
issue
or
what's
the
the
closest
to
the?
I
guess
you,
you
start
working
in
figma,
so
figma
is
fine.
B
I
I
do,
but
it's
probably
beneficial
for
other
folks
to
see
the
conversation
too.
So
I'll
just
put
it
in
the
issue.
If
that
works
for
you
and
then
I'll
also
I'm
happy
to
reference
the
figma
file
in
case.
You
want
to
jump
in
there
too,
but
it
might
be
better
for
us
to
have
that
discussion
in
the
issue.
Just
so
everybody
else
can
be
on
the
same
page.