►
From YouTube: 2022/03/24 Weekly UX/Design
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).
A
All
right
we
are
being
live
streamed
today
is
thursday
march
24th
in
most
of
the
world,
and
this
is
our
fortnightly
design
meeting
before
we
jump
into
the
agenda.
We
should
go
around
and
do
some
quick
introductions
I
like
to
do
popcorn,
so
one
of
us
will
introduce
ourselves
and
then
call
on
another
person
at
random
to
introduce
themselves.
I'm
gonna
go
first.
My
name
is
jen
lampton.
A
B
C
Martin,
I'm
martin
and
the
uk
york's
putting
on
the
internet
we're
working
on
a
we're
working
on
a
sign,
just
started
working
on
just
started
working
on
another
one.
First,
first
paid
backdrop
site,
so
we're
quite
excited
about
that
and
yeah
and
fixing
a
few
books
and
and
developing
things
along
the
way
and
go
to
our
arena.
D
E
My
name
is
tim
erickson,
I'm
st
paul
tim,
I'm
in
deerwood
minnesota,
where
it's
money
out
lots
of
melting
snow.
We
had
a
bunch
of
mud
and
then
it
snowed
again
and
now
we
got
more
money.
Did
you
go
robert
already?
A
Okay,
let's
see
so
we
have
three
or
four
items
to
discuss
today
in
our
designing
user
experience
meeting
the
first
one
is
a
obscure
issue
about
bartik
tim.
I
don't
know
if
you
want
to
give
us
an
update
or
maybe
just
tell
the
story
of
how
we
ended
up
there
in
the
first
place,
because
that's
kind
of
exciting.
E
So
the
the
a
lot
of
obscure
issues
have
been
getting
addressed
over
the
last
two
or
three
weeks,
because
we
have
been
involved
in
the
open
force,
2022
code
spread,
which
is
trying
to
get
new
students
involved
in
in
open
source
in
general
and
we're
one
of
the
featured
projects,
so
we're
seeing
lots
of
little
text
change
issues
that
have
been
getting
work
done
and
merged
some
of
them
a
little
bit
more
complicated
than
that.
This
issue
actually
didn't.
E
This
is
was
inspired
by
that,
but
not
exactly
most
of
the
participants
in
open
force
are
from
india
and
we
didn't
have
any
office
hours
in
that
time
slot.
We
thought
it
would
be
a
good
idea-
and
I
work
with
some
colleagues
in
bangladesh
who
have
been
trying
to
get
involved
in
in
backdrop,
and
you
know,
and
the
core
issue
a
little
bit
more
and
I
thought
let's
go
ahead
and
schedule
office
hours.
E
Basically,
it
would
be
like
10
p.m.
California
time
it's
midnight
for
me,
but
that's
right
around
noon
in
bangladesh,
india-
and
I
would
just
work
with
my
team
on
some
on
some
issues
in
core,
but
we
would
open
it
up
to
anybody
else,
and
so
we've
been
doing
that
the
last
two
weeks,
and
so
we
also
just
dumped
it
jumped
in
with
some
really
basic
issues.
We
found
this
one,
which
we
thought
would
be
a
little
better
than
a
simple
text
change
a
little
bit
more
complicated.
E
E
We
got
a
little
bit
of
a
device
from
pw
panda,
but
then
I
went
into
the
the
base
star
the
basis
menu
as
well.
This
the
the
existing
menu
was
specifically
for
arctic
and
in
basis
they
don't
work.
The
way
we
were
told
they
should
work
either
and
they're
also
broken,
although
maybe
slightly
less
broken,
or
they
look
they're.
I
would
say
they
look
broken,
but
they
they
look
a
little
less
hungry
this.
The
theme,
the
the
title
of
this
issue
is
perfect
main
menu,
somewhat
ugly
anyways.
E
I
don't
know
if
the
solution
is
just
to
say
that
this
issue
is
too
obscure
and
we
should
just
close
it
or
if
we
should
talk
a
little
bit
about
hierarchy.
You
know,
maybe
there's
some
value
in
talking
about
why
hierarchical
venues
are
hard
to
understand
and
or
why
they
aren't
working
and
maybe
there's
a
bigger
issue
here
that
could
be
fixed
if
we
talked
about
it,
but
I'm
not
sure
what
that
issue
is
because
I'm
a
little
confused
on
what's
supposed
to
be
happening.
A
I
would
agree
that
this
use
case
is
probably
not
super
common.
I
see
the
drop
down
menu
used
a
lot
and
just
a
list
of
horizontal
links
used
a
lot,
but
I
could
see
a
scenario
where,
if
you
had
like
a
super
short
menu
of
three
items
or
something
you
might
want
to
have
like
a
vertical
display
in
the
header
area
somewhere
rather
than
horizontal
display,
I
don't
know
if
that
meets
the
like.
A
I
don't
know
if
that
makes
it
important
enough
that
we
need
to
spend
a
lot
of
time
fixing
it,
but
it
would
be
nice
if
it
looked
not
broken.
A
E
You
have
a
lot
of
obscure
issues
in
the
issue
too
that
like,
if
somebody
ever
has
time
to
work
on
them.
That's
great,
and
this
could
remain
that
I'm
just
reluctant
to
leave
it
as
that,
if
we
don't,
even
unless
we
could
at
least
give
some
some
direction
and
what
it
should
look
like
and
that's
where
it's
kind
of
like
right
now,
it's
marked
as
a
good
first
issue,
but
you
know
I've.
I
consider
myself
more
than
a
beginner
and
I
have
no
idea
like
what
this
would
look
like
it
would
work.
E
A
E
I
wish
I
could
have
the
site
my
demo
site
set
up,
but
I
don't,
but
this
screenshot
might
be
enough.
Okay,
basically
in
both
bases.
Well,
here's
the
the
original
issue
of
how
it
looked.
E
Let's
broadway
up
to
the
top,
was
the
reason
that
that
it
was
flagged
was
just
that
it
was
with
these
rounded
tabs
they
sort
of
overlapped
and-
and
I
think
that
would
look
ugly
and
I
think
the
original
idea
was
just
sort
of
I'm
guessing.
I
don't
know
if
it
was
clearly
spelled
out,
but
just
to
make
it
look
a
little
less
ugly,
but
I
mean
to
me
that
still
would
look
broken
if
like,
why
would
we
have
floating
tabs
with
others
just
underneath
them?
E
If,
in
fact,
that's
okay,
and
if
we
had
a
third
level-
and
we
had
three
levels
stacked
like
this,
then
that's.
I
guess
that
is
fixable
and
we
could
do
that.
But
is
that?
Is
that
really
an
improvement
that
doesn't?
It
seems
to
me,
like
somebody's
still
going,
to
have
to
retheme
this
anyways
like
using.
E
E
The
other
thing
about
I'll,
just
mention
is
something
quickly
uncovered.
Is
that
if
you
add
a
sibling
issue
in
the
hierarchy
to
the
one
underneath
it
that
goes,
underneath
it
and
bw
panda
said
to
me
well,
sibling
ones
should
line
up
across
well,
I
went
to
the
bases
and
checked
and
they
don't
line
up
across
the
bases
either
so
whatever
that,
so
that
problem
is
a
little
bit
different
than
the
one
that
was
originally
flagged,
but
they're,
both
relevant
and
and
in
basis.
E
A
A
D
A
Would
I
would
say
for
this
issue
if
we
were
to
remove
the
rounded
corners
from
any
item?
That's
not
a
top
level
item.
That
would
probably
be
enough.
I
agree
to
him.
It's
not
fixed,
but
I
feel
like
that
was
the
original
oversight
was
that
hey
the
rounded
corners
are
appearing
where
they
shouldn't
and
then
we
found
a
whole
bunch
of
other
stuff.
That's
also
wrong.
D
A
Just
fix
the
shape
and
then
we
can
have
a
follow-up
for
like
what
should
it
stack
like
where
we
can
answer
the
questions.
We
don't
know
how
to
answer
yet
and
then,
once
we
have
like
a
screenshot
or
a
description
of
what
we,
how
we
do
want
to
have
it
behave,
then
that
might
become
a
for
a
good
first
issue,
but
I
think
until
we
have
some
kind
of
direction,
you're
right
that
this
is
too
too
unjust.
Non-Descript
for.
E
E
A
E
E
Actually,
no,
although
I'm
not,
I
don't
know
if
this
would.
The
example
is
specifically
on,
unlike
the
about
page,
and
I
don't
know
why.
Well
because
the
home
page,
I
think
the
assumption
was
the
home
page,
wouldn't
have
a
child,
so
only
the
about
page
would
and
so
we
put
in
the
example.
We
specifically
put
the
child
on
the
about
page
anything
about
layout,
but.
G
E
Well
I'll
just
comment
that
there
was,
and
some
of
these
issues
are
that
get
uncovered.
I
think
they
only
get
uncovered
by
core
contributors
who
are
fixing
one
obscure
bug,
and
then
they
find
another
obscure
bug
and
it
like
might
be,
that
a
user
would
never
ever
run
into
this.
But
you
know-
and
so
there
was
a
there-
was
a
somewhat
related
issue
and
that
I
found
there
is
a
check
box.
E
That's
on
the
menu
tab.
That
says
always
display
menu
items
or
something,
and
I
spent
a
half
an
hour
one
day,
trying
to
figure
out
what
that
checkbox
was
supposed
to
do,
and
it
was
finally
explained
to
me
that
that
checkbox
was
specifically
for
hierarchy,
which
again
I
didn't
understand
and
bw
panda
suggested
a
little
better
help
text
for
that
and
one
of
our
open
force
contributors
just
completed
a
pr
yesterday
to
commit
that
better
text
to
explain
what
that
checkbox
was
for
hierarchical
findings.
A
All
right,
the
next
issue
in
our
agenda
is
layout
page
cleanup.
This
is
issue
number
5077.
This
one
has
been
installed
for
a
while.
It
needs
somebody
other
than
robert
and
myself
to
test
it
and
in
ideal
world
do
a
code
review.
A
A
B
So
this
started
as
suggestions
for
what
happens
if
you
delete
something
from
the
layout
listing
page
and
moved
it
to
a
new
issue.
This
is
issue
5511
and
basically
the
current
pr
which
I'm
just
looking
for
feedback
from
people
saying
yep.
I
agree
that
this
is
what
it
should
be
done.
B
The
first
is
on
the
confirmation
page
when
someone
tries
to
delete
a
layout
and
we
get
a
confirmation
page
add
an
option
for
them
to
disable
delay
the
layout
and
not
just
delete
it
so
that
as
if
they
delete
it,
the
whole
page
goes
away.
If
deleting
or
disabling
the
layout
would
remove
a
page.
That's
used
on
the
site.
B
Information
page
like
home
or
404
403,
put
up
a
warning
on
the
on
the
delete
confirmation,
page
and
after
the
person
confirms,
put
up
a
warning
message
directing
them
to
go
to
the
site
information
page
to
fix
the
thing
that
would
now
be
broken
and
in
the
process
of
doing
those
two
things.
B
So
what
I'm
looking
for
is
just
feedback
on
the
behavior
of
those
actions
and
the
wording
on
the
warning
messages
and
the
reason
I'd
like
to
get.
That
is
because
these
are
things
that
will
need
automated
tests,
but
automated
tests
will
check
for
specific
warning
and
I'd
rather
only
write
those
tests
once
and
so
just
I
would
ask
for
people
to
give
some
feedback
on
this
on.
What's
there
to
say
yep,
I
agree.
This
is
the
way
it
should
be,
and
then
the
next
step
will
be
to
write
the
automated
tests.
B
I
don't
know
the
other
place
that
supports
this.
Pr
is,
if
you,
if
you
select
delete
if
you
try
to
delete
a
layout
and
it's
one
of
these
important
layouts,
the
suggestion
was
to
add
a
disable
button.
So
that
and
say
do
you
want
to
delete
this
or
do
you?
Would
you
rather
just
disable
it?
You
know,
since
the
delete
is
irrevocable,
and
so
that's
that's
the
two
ways
yeah
to
disable.
A
E
If
you
haven't
looked
at
it
john
then
yet
in
theory
it's
mergeable
other
than
feedback,
you
know
or
getting
somebody
to
say
yeah.
This
works
for
me
really,
I
think,
since
all
of
them
I
worked
on
it.
Has
anybody
else
actually
commented
on
the
solution.
E
Sometimes
the
numbers
just
come
out
in
different
orders.
I
think
irena
did
comment
on
it
after
the
last.
My
last
plea,
thank
you
I
mean,
but
I'm
not
sure
if
anybody
else
has
looked,
I
may
be
into
somebody.
A
E
Well,
I
don't
know
if
we
need
to
talk
about
that,
the
main
app
really
the
main
thing
is
just
if
anybody
I
don't
know
if
it
would
help
talk
about
it
in
a
group,
and
people
want
to
just
if
we
had
two,
I'm
really
I'm
thinking
that
a
core
committer
is
going
to
want
to
see
a
little
bit
more
approval
of
this
before
they
commit
something
this
bank.
So
if
we
had
one
or
two
more
people
sort
of
comment
on
this
last
round,.
B
E
D
D
D
My
only
question
since
this
is
a
ux
meeting
relates
to
one
of
the
notes
from
backdrop
live
that
images
with
beautiful
mountains
are
make
all
sides
look
better
than
wondering.
If
it
would
be
possible
to
select
a
slightly
different
image
it
will.
It
will
make
a
very
big
impact
on
what
it
looks.
A
And
yeah,
I
think
that
that's
tricky.
We
had
like
a
pretty
long
discussion
in
the
queue
about
what
images
should
be
used.
I
don't,
I
think
one
thing
that
we
might
do
is
send
the
whole
home
page
as
it
is
now
off
to
I
don't
know
like
darius
or
whoever
did
the
brand
for
backdrop
core
stuff
and.
A
We're
about
to
major
change
to
backdrop.
What
do
you
think
of
these
colors
cards
images
whatever
and
if
he
says
yeah
it's
fine,
then
we
use
it
because
it's
already
been
sort
of
a
community
signed
off
on.
But
if
he's
like
hey,
can
you
make
this
green,
this
color
and
this
yellow
this
color
and
this
blue?
This
color
and
they'll
fit
better
with
the
whatever
we
could
make
those
kind
of
changes.
A
I
think
if
he
wants
pictures
or
if
we
mentioned,
like
hey
it'll,
be
nice
to
have
pictures,
there's
like
a
lot
of
sourcing
that
needs
to
go
into
that,
to
make
sure
that
we
can
find
pictures
that
are,
you
know,
for
distributing
with
an
open
source
distribution
and
that
sort
of
thing
and
then
trying
to
find
those
that
would
work
in
this
scenario.
A
That
could
be
something
that
might
prevent
this
from
getting
into
the
next
release,
and
so
my
instinct
would
be
if
we
can
say
ship
it
now
and
then
later
be
like.
Maybe
if
we
need
to
change
images,
we
can
change
the
images.
That
would
be
something
that
I
would
not
want
to
prevent
this
from
getting
into
the
next
release.
So
I
think
it's
worth
discussing,
but
I
would
say
like:
let's
make
sure
we
get
it
good
enough
first
and
not
let
that
prevent
the
feature
from
getting
in.
That
would
be
my
preference
anyway.
B
In
the
earlier
history
of
this
one,
we
actually
had
kind
of
a
a
comparison
with
pictures
is
one
option
and,
and
then
this
and
I'd
actually
preferred
the
pictures.
But
these
are
fine
and
I
think,
we're
better
off
getting
it
out.
Even
if
it's,
if
not
every,
it's,
not
first
choice
for
every
single
person,
so.
E
Yeah
I
I
wanted
to
sort
of
echo
that
same
thing.
We
actually
have
like
four
different
versions
of
these
cards.
One
of
them
had
photos,
one
of
them
had
icons,
one
of
them
had
abstract
images,
and
we
had
a
bit
of
a
discussion
about
it
and,
to
be
honest,
I
think,
as
it's
not
unsurprising
in
an
open
source
community,
the
least
objectionable.
E
E
I
will
say
even
earlier
in
this,
there
was
discussion.
Should
this
be
a
whole
redesign
of
the
front
page,
and
I
provided
one
mock-up,
which
had
a
new
image
for
the
welcome
to
backdrop,
a
hero
image
and
that
right
away
got
like.
Oh,
no,
no,
no.
If
we
try
to
do
too
much,
this
will
never
get
in.
We
got
to
pick
one
thing
fix
it,
and
then
we
can
pick
another
thing
and
fix
it.
G
D
D
E
So
another
thing
about
this
irena
is
that,
and
I'm
curious,
like
you're,
totally
excited
about
this
issue
and
I
suspect,
mostly
you're
excited
about
the
information
in
the
display
on
the
front
page.
This
issue
isn't
even
about
what
wasn't
originally
about
that.
This
issue
was
originally
about
adding
a
content
type,
and
so
that's
why,
when
like,
when
we
started
to
change
the
hero
image
in
what
it
started
out
as
an
issue
about
adding
a
content
type
people
quickly
became
concerned
about
scope
creep.
E
So
what
what
we
might
do
is
just
go
with
this
and
then
go
back
and
say:
let's
have
a
new
issue
which
is
redesign
the
front
page
and
get
a
designer
involved
and
actually
do
something,
that's
more
comprehensive
and
has
some
designer
input,
but
I
think
trying
to
do
that.
Right
now
would
just
sort
of
stall
this
and
it's
not
what
this
issue
set
out
to
be.
D
I
don't
I
don't
like
to
insist
on
things
sometimes
so
people
feel
like
that's
too
complicated.
Maybe
it
is
too
complicated.
I
think
that
design
for
the
if
you
ship
system
that
has
same
background,
that
you
have
on
the
front
page
effect
of
cms,
which
probably
does
not
require
too
much
discussion.
E
D
I
think
that
maybe
having
a
designer
in
this
conversation
like
darius
or
nica,
might
solve
lots
of
problems
because
we
all
have.
We
did
read
all
this
discussions
about
design
by
committee
and
when
I
worked
with
nika,
she
made
the
design
and
I
simply
implemented
the
design
that
she
did.
That's
her
she's
expert
in
this
and
then
I
was
very
careful
about
like
oh
she
that
was
her
offset.
D
This
is.
There
was
a
reason
why
offset
was
like
in
the
middle
of
the
card
or
the
top
of
the
card,
and
I'm
trying
to
pay
attention
to
what
designers
put
in,
and
so
I
think
that
like
if
we
want
to
have
a
good
design,
there
has
to
be
a
designer
and
if
we
can
bring
on
board,
as
you
said,
there
are
people
who
are
willing
to
help
so.
E
I
I
would
be
in
favor
of
a
design
issue
to
redesign
the
front
page,
although
that
runs
it
as
soon
as
we
try
to
do
that.
We
run
into
the
problem
that
we
can't
change
basis
in
ways
that
aren't
backward
compatible
right.
So
the
design
is
very
much
affected
by
the
theme
of
basis,
and
so
any
changes
we
make
have
to
be
backward
compatible.
They
can't
break
existing
basis
site,
and
so
that
also
complicates
it.
I.
A
Think
we've
got,
we've
got
a
couple
of
things
going
on
here
that
I
think
we
can
do
like.
One
thing
I
am
planning
on
doing
is
emailing
darius
and
be
like
hey
check
out
this
issue,
we're
about
to
ship.
This
thing
anything
you
want
us
to
know
about
before
we
do
that
because
he
just
he
said
no,
we
should
we
should
email
wes
right
because
he
did
the
original
basis
home
page.
A
So
all
email
us
and
we're
about
to
do
this,
and
let
us
know
what
you
think
and
if
he
has
any
immediate
reactions
that
are
like
hey.
You
know
this
gray
needs
to
be
three
hexadecimals
darker,
whatever
it
is
designers
know
about,
he
can
make
those
kind
of
small
changes
and
we
can
implement
those
with
no
problem.
Something
like
a
whole
redesign
of
the
home
page
is
going
to
be
something
that
is
going
to
be
a
bigger
lift.
A
Compatibility
with
the
basis
theme
give
us
a
little
more
flexibility
and
it
could
be
something
that
could
be
a
big
splash
for
you
know,
ta-da's
backdrop
too:
maybe
we
don't
break
any
apis
but
really
break
the
homepage,
design
or
something
that
could
work,
but
I
don't
think
we
have
time
to
do
that
for
this
particular
feature.
A
I
do
think
we
have
time
for
a
designer
review
and
minor
iterations
on
what
we
have
now
so
I'll
email
us
and
see
if
he
can
take
a
look
at
the
issue
he's
you
know
great
in
working
in
the
issue:
queue
and
we'll
probably
just
jump
right
in
and
yeah,
I
think
room
for
improvement,
but.
A
Okay,
well,
we
could
go
ahead
and
stop
this
recording
and
then
we
will
meet
again
in
10
minutes
to
talk
about
the
design
meeting,
so
we
can
have
a
little
chit
chat
until
then.
If
you
want.