►
From YouTube: 2022/01/27 - Design/UX
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
Hello,
everyone-
this
is
the
weekly
backdrop,
design
ux
meeting
for
thursday
january
27th
and
just
in
some
parts
of
the
world
as
as
is
our
practice
we'll
start
the
meeting
by
going
around
and
have
everyone
give
a
brief
introduction
of
himself
where
they're
from
say
a
few
words.
If
you
like
about
what
you're
working
on
or
excited
about,
I'm
robert
wang,
bun
folder
on
the
internet,
coming
to
you
from
altadena
california,
I've
been
working
on
contrib
modules,
lately
pass
it
over
to
tim.
B
Yep,
my
name
is
tim
erickson,
I'm
st
paul
tim,
I'm
in
deerwood
minnesota
and
I
suppose
the
thing
most
of
my
mind
about
backdrop
right
now
is
outreach
and
getting
ready
for
the
the
that
much
backdrop
live
joseph.
C
C
D
Kessler,
do
you
want
to
go
yeah,
justin,
christopherson
and
denver
colorado,
and
I
just
helped
with
infrastructure
once
in
a
while
and
you're
kind
of
lurking?
In
the
background
on
this
one.
B
Jen,
if
you're
around
and
you
want
to
jump
in,
go
ahead,
otherwise
we'll
move
ahead.
You
might
not
be
available
right
now,
because
you're
actually
looking
at
our
agenda,
so
we
have
an
agenda.
B
We
don't
have
anything
too
specific
on
it,
although
there
is
one
issue
for
sure
we
want
to
talk
about,
and
maybe
we'll
come
back
to
the
thing
we
were
talking
about
before,
but
the
one
issue
that
was
in
the
forum
post
about
today
was
an
update
on
the
pathless
nodes.
B
The
andy
is
joining
us
as
well,
and
that
was
put
on
the
agenda
before
we
had
a
big
discussion
at
the
weekly
dev
meeting
last
week.
So
I
think
our
the
urgency
of
that
discussion
for
today
has
went
down
a
bit,
but
there's
still
a
couple.
Well,
I
think
mainly
what
I
just
want
to
do
today
is
updated.
We
we
just
it
was
hung
up
on
the
fact
that
we
had
decided
to
move
from
well
actually
andy.
B
I
don't
know
if
you're
able
to
to
talk
with
us
today,
but
I
know
you
weren't
on
the
dev
meeting
last
night
last
week,
so
I
don't
know
how
you
caught
up.
You
are
on
this,
but
we,
as
we
were
getting
to
the
end
of
the
pathless
nodes
issue
for
the
last
release.
I
think
you
were
one
who
is
advocating
that
we
use
layouts
instead
of
instead
of
views
to
display
these
new
notes
that
we
were
creating,
and
I
don't
know
if
you
saw
where
we
got.
B
Okay,
I
didn't
notice
that
and
yeah.
So
I
I
don't
know
if
you
have
any
we,
it
was
getting
to
the
stage
where
we
were
talking
about
now,
adding
a
new
layout
to
core
in
order
to
help
solve
that
problem,
and
at
that
point
I
think
we
all
just
sort
of
said
wait.
This
is
spiraling
out
of
control,
and
maybe
we
need
to
stick
with
the
news
for
now
and
follow
up
with
moving
this
into
a
layout
later.
B
B
E
B
Yeah
I
mean
we
could
talk
about
that.
Some
of
the
things
we
ran
into
were
number
one.
If,
if,
if
we're
going
to
use
layouts
to
me,
then,
ideally
we
want
a
layout
with
with
three
regions
in
a
row.
B
B
Another
one
is
that
if
we
do
notes,
olaf
was
pointing
out
that
if
we
do
nodes
in
an
existing
block,
an
existing
content
blocks
and
put
them
in
a
layout,
we
can't
move
the
the
image
above
the
title
currently
there's
an
open
issue
for
that,
whereas
we
are
able
to
do
that
with
views
and
in
his
view
that
is
sort
of
the
standard
way
that
most
people
do.
B
These
kinds
of
tiles
is
that
the
image
is
it's
at
the
top
and
then
the
title
and
we
you
know
we
won't
be
able
to
do
that.
So
I
mean
personally,
I
think
we
could
probably
get
away
with
putting
the
title
at
the
top,
although
there
are
that
becomes
problematic,
especially
if
you
have
like
one
of
them
has
a
single
line
title
and
the
next
one
has
a
two-line
title.
Then
the
images
don't
line
up,
you
know
nicely
and
it
just
gets
complicated.
B
So
those
were
at
least
two
of
the
main
issues
that
came
up
and
then,
as
we
started
to
resolve
them,
it
was
like.
Are
we
going
to?
You
know,
change
the
front
page
layout
to
another
core
layout?
Are
we
going
to
create
a
flexible
layout
template
and
we
seem
to
be
moving
in
the
direction
of
well?
If
we're
going
to
do
this
right,
we're
going
to
need
to
create
a
new
layout
for
the
front
page
and
head
it
to
core.
A
I
wasn't,
but
I'm
going
to
be
the
gen
poster
jen's
posting
that
says
we
can
put
the
image
at
the
top
and
the
title
below
and
she
I
thought,
that's
not
what
we
I
thought.
That's
not
what
we
decided.
B
Yes,
that's
what
we
decided
we're
just
talking
about
this,
because
andy
wasn't
on
that
call,
so
I
just
wanted
to
update
andy
on
where
we
were
at
and
see
if
he
had
any
any
thoughts
he
wanted
to
share.
But
so
when
I
said
we
couldn't
do
that,
I
was
explaining
why
we
made
the
decision
to
go
with
views
instead
of
so.
A
What
wasn't
one
one
of
the
motivations
for
making
that
issue
was
that
all
the
other
options
required
substantially
more
development
work
like
turning
titles
into
a
field
that
could
be
moved
up
and
down
in
display
things
like
that
and
that
doing
it
in
views.
We
could.
We
could
get
it
out
pretty
quickly
and
then,
because
this
only
affects
new
installs.
B
Well,
I
think
we
could,
I
mean
andy
jump
in
if
at
any
point,
you
want
to
ask
any
more
questions
or
say
anything
about
that.
I
think
the
status
of
that
issue,
and
I'm
not
looking
at
it
right
now
and
I
should
be-
is,
I
think,
there's
three
big
things.
One
we
have
to
decide.
I
had
forgot
totally
forgotten
about
this
until
this
morning
was
that
I
believe,
where
we
left.
This
off
was
olaf.
B
It
provided
with
us
with
like
six
sets
of
images
for
the
posts
and
we
were
deciding
which
ones
to
use,
and
I
think
we'll
be
able
to
manage
that.
And
then
I
don't
think
we've
had
a
lot
of
feedback
on
the
content
that
that
I
put
in
the
pr,
and
so
we
probably
need
a
little
fine-tuning
of
that
and
then
I
think,
tess
there's
a
number
of
tests
that
are
failing
and
I'm
not
sure
if
we're
going
to
need
any
new
tests.
B
I
ignored
tess
because
I
felt
like
it
was
so
much
in
flux
that
there
was
no
point
worrying
about
texas
tests
until
we
knew
what
which
direction
we
were
going,
and
I
think
we're
at
that
stage
now,
where
we
could
figure
out
either
the
current
problems
with
tests
and
or
find
out
if
we
need
any
new
ones,
and
I
think
at
some
point
early
much
earlier
in
this
discussion,
there
was
a
concern
that
this
would
break
a
break
or
require
a
lot
of
tests.
B
And
I
it
seems
to
me
that
we've
kind
of
determined-
that's
not
in
fact
the
case
that
it
shouldn't
be
too
bad,
but
I
don't
fully
understand
the
implications
in
terms
of
what
we
might
need
for
tests
on
this,
so
anybody
that
can
help
with
that.
So
I
don't
know
that
we
need
to
talk
about
this
anymore
today,
other
than
to
say
that
that's
the
status,
if
anybody
has
any
opinions
or
wants
to
talk
about
the
issues
with
the
text
or
the
tests,
please
jump
in
now.
B
E
I
think
my
my
issue
with
it.
It
wasn't
really
in
my
issue,
but
I
think
somebody
made
the
point
that
if
we
use
views
then
anytime
the
user
makes
an
up
a
new
one
of
those
nodes,
the
card
node
or
whatever
we
decided
to
call
it.
Then
it
would
automatically
appear
on
the
front
page.
E
E
A
A
E
B
And
I
believe
that's
what
they
do
right
and
jen's
pointing
out
that
we
certainly
can
do
that.
I
mean
it's
yeah,
it's
I
think
it's
I
think
so
the
the
point
would
be
is
that
the
the
use
case
that
we're
kind
of
promoting
for
those
blocks
suggests
that
they
might
be
stable
and-
and
you
know
in
fact
they're
not,
but
that's
not
a
big.
I
don't
see
that
as
a
big
problem
and
if
nobody
promotes
another
info
block,
it
won't
disrupt
that.
But
yes,
I
think
olaf,
you
know
like
created
a
test.
B
Olaf
created
a
test
post,
a
new,
hidden,
node
and
then
noticed,
of
course,
that
that
he
must
have
promoted
it.
I
mean
we'll
have
to
verify
that
we
are
using
the
promoting
checkbox
we
should
be.
It
might
be
that
we
weren't,
and
that
was
the
problem
and
that's
fixable
but
yeah.
I
I
think
we
can
address
some
of
those
issues
and
again
it
might
not
be
perfect
out
of
the
box.
But
the
nice
thing
about
this
issue
is
it's
just
in
the
install
profile.
B
We
can
easily
tweak
it
and
improve
it
for
future
releases.
Even
bug
fix
releases,
I
would
assume,
without
you
know,
breaking
anybody's
sites
from
even
impacting
any
website.
So,
okay.
Well,
if
nobody-
I
I
again,
I
think
we're
close
on
the
images.
I
think
we
can
probably
make
a
decision
on
that
and,
if
something
so
we're
getting
feedback
on
the
feedback
on
the
content
and
the
tests
we
can
move
on
on
this
issue,
so
I
think
we
could
go
on
to
another
anything
else.
The
problem
is,
I
don't.
B
B
Currently
ux
marked
issues
that
are
most
recently
updated.
Are
I
I
have
the
feeling
that
I
don't
want.
I
haven't
been
super.
Oh
jen's
got
one,
she
wants
to
stop,
but.
B
I
haven't
been
watching
the
issue
2
as
closely
as
I
do
sometimes,
but
my
sense
is
that
at
the
moment
there's
a
bunch
of
kind
of
technical
issues
that
are
not
very
ux
related
that
are
getting
the
most
attention
there.
There
are
a
few
of
those
ux
issues
that
I
I've
seen
pop
up
and
let's
check
out
john's
issue:
40
29.
B
Oh,
this
is
a
great
one
and
I
did
notice
that
this
one
was
getting
some
attention
and
I
would
ask
jen
to
update
us
on
it,
except
that
she
doesn't.
It
seems
to
be
having
audio
problems,
so
I'm
going
to
scroll
down
if
anybody
else,
there's
no
new
comments
on
it
jen.
I
know
I
saw
that
you
had
some
you've
been
making
updates
to
the
pr.
So
can
you
give
us
a
thumbs
up
or
say
something
to
indicate?
Does
your
pr
address
some
of
that?
B
The
the
ideas
that
the
last
comments
were
from
gregory
and
my
gregory
proposed
kind
of
a
an
option
to
solve
jen
had
a
the
history
on
this
is
gen
head
of
pr.
This
is
a
user
compare
visibility
rule,
so
this
is
on
a
block
you'll
be
able
to
compare
whether
the
user.
B
B
Okay-
and
it
sounds
like
jen-
has
a
pr
that
addresses
that
so
jen,
I
don't
know
what
more
we
can
do
in
the
meeting
other
than
if
we
have
to
actually
open
this
up
and
looked
at
it,
which
I'd
be
willing
to
do
if
we've
got
nothing
else,
but
I
will.
I
will
definitely
take
a
look
at
that.
B
I
like
this
issue-
and
I
remember
commenting
on
it
before
so-
okay,
good
so
jen,
saying
in
chat
really
she's
just
looking
for
more
people
to
look
at
the
the
than
this
pr
and
provide
feedback.
So
I'll
do
my
best
to
do
that.
If
anybody
else
wants
to
do
that.
B
B
B
If
it's
okay,
let's
talk
briefly
about
that,
because
it's
not
necessarily
a
a
core
design,
ux
issue,
but
it
so
it's
a
contribution
really,
and
so
I'm
not
sure
what
meeting
to
bring
it
to,
and
since
we
have
a
little
bit
of
time
here,
what
we
were
talking
about
when
you
joined
us
jeb
well,
actually
that
I
think
it
was
was
discover
the
the
the
issue
that,
when
you
approached
me
yesterday
about
that
module
that
I
I'm
not
listed
as
a
maintainer
off-
and
I
didn't
even
remember,
reporting
that
module
is
that
I've.
B
It's
we're
having
it
like.
There's
no
way
for
me
to
just
print
out
a
list
of
all
the
modules
that
I've
listed
as
maintainer
on
and
robert
was
pointing
out
that
we
have
added
the
ability
to
track
maintainers
through
the
dot
info
file
of
modules.
But,
of
course,
that's
going
to
be
only
moving
forward
right.
We've
got
800
modules
where
that's
not
listed
plus.
That
would
require
that
somebody
release
a
module
before
that.
B
Would
get
to
backdrop.org
and
I've
been
debating,
although
I
don't,
I
I've
been
debating,
trying
to
do
some
sort
of
data
poll
from
github
to
see
if
I
could
create
a
list
of
modules
that
I
could
play
around
with
and
experiment
with,
but
even
if
I
did
that,
I
couldn't
get
the
maintainer
right,
because
there
isn't
any
github
doesn't
show
who,
like
loans
or
who's,
the
the
key
developer
on
a
a
contrib
project
right.
So
really
the
only
place
you
can
get.
B
The
maintainer
is
from
the
readme
and
even
in
the
readme,
there's
no
standard
way
of
doing
it.
So
I
might
be.
I
might
have
listed
myself
as
saint
paul
tim
as
the
maintainer
of
one
module
and
tim
erickson
is
the
maintainer
of
another
module
and
if
I
do
it
so,
even
if
I
did
some
sort
of
scrape
of
all
the
the
dot
info
or
the
breebies,
it
wouldn't
be
very
clean.
Wouldn't
it
and
I'm
just
so.
B
I
think
what
I'm
asking
right
now
one
is:
if
there's
any
thing,
I'm
missing
in
terms
of
a
way
to
do
that
for
me
to
like,
find
all
the
modules
or
create
a
system
for
other
people
to
do
that,
android
2!
Is
there
any
way
we
can
take
this
change
that
we
made
to
the
dot
info
file
and
get
that
up
to
date?
B
You
know,
even
if
it's
like
a
sprint,
you
know
spending
a
saturday
going
through
and
writing
prs
for
all
the
modules
that
update
their
their
dot
info
files
and
hoping
that
the
maintainers
merge
them.
A
B
A
Mean
I
might
the
module
search
function.
Does
a
full-text
search
of
the
module
node
info
that
comes
from
the
readme
file.
So
since
you
have
a
relatively
unusual
name,
if
you
were
to
search
for
ericsson,
it
will
pull
up
the
projects
that
have
erickson
and
the
readme
and
similarly
st
paul
tim.
B
I
think
it
would
nice
I
mean
I
can
think
of
it.
You
know
it
might
be
interesting
to
see
all
of
the
modules
that
the
andy
that
will
maintains
just
because
I'm
sometimes
impressed
by
all
the
work
he's
done,
but
you
know
I
don't
know
how
urgent
that
is,
but
the
most
the
you
know
I
just
often
wondered
like
how
how
how
do
I
find
all
the
modules
that
I've
listed
myself
as
maintainer,
and
I
think
you
said
you
searched
you
use
github,
and
so
I
take
it.
B
What
you're,
I'm
not
quite
sure
how
you
do
that
other
than
maybe
no
no,
I'm
saying
john
I'm
talking
about
jen
in
the
chat
jen
said
that
she
uses
github
the
search
to
find
all.
B
Okay
and
and
oh
yeah,
then
robert,
you
provided
an
example
of
how
to
to
do
that.
Search,
okay.
Well,
I
wanted
to
throw
that
out
there
and
see
if
people
had
input
and
you
had
a
there's
a
few
ideas
out
there.
That
would
help
me
a
little
bit.
I
think
we
should
think
about,
though,
how
to
better.
B
In
you
know,
in
drupal.org
you
can
give
every
user
that
lists
all
the
modules
that
they
contribute
to
or
maintain,
and
we
don't
have
anything
like
that
and
I
I
feel
like
we
should
have
something
at
least
sort
of
like
that.
But
I
don't
know
if
this
is
the
right
time
or
meeting
to
talk
about
that.
Maybe
we'll
bring
that
up
in
a
section
of
backdrop,
live.
B
If
nobody
else
has
any
ux
issues,
I'm
inclined
to
wrap
up
this
meeting
and
get
ready
for
the
next
one.
E
Just
on
the
last
issue,
we
just
spoke
about
sure
not
particularly
searching
by
maintenance.
I
suppose
that,
probably
might
not
have
you
know
a
lot
of
use.
E
I
can
imagine
if
you
know
eventually
not
an
individual
person,
but
if
you
have
an
organization
that
started
making
lots
of
modules,
it
might
be
useful,
as
opposed
to
to
find
all
the
same.
You
know
the
simple
theme
modules
you
know,
but
maybe
not,
but
I
I
just
want
to
say
that
the
other
functionality,
though,
being
able
to
put
more
data
in
the
info
files.
I
think
that
some
of
that
could
be
useful
and
we
should
look
into
using
that
functionality.
E
E
You
know
more
more
easily
if
you
want,
you
know,
modules
that
specifically
deal
with
user
access
or
something
like
that
right
now,
it's
impossible
to
do
that.
If,
right,
if
you
want
themes
that
you
know
special
specific
categories
of
things,
it's
impossible,
so
I
think
that's
something
that
we
should
do
right.
Drupal
definitely
does
it
on
the
drupal
module
listing
page.
You
know
you
can
search
by
lots
of
stuff
maintenance
status,
development
status.
B
Well,
I
think
we,
the
fact
that
we've
added
the
capability
to
start
doing
those
kinds
of
things
we
haven't
published
like
there's,
no
blog
post,
we
haven't
officially
rolled
it
out
in
any
way.
Right
I
mean
basically
drupal
so
or
excuse
me
is
my
understanding
right
that
we've
that
backdrop.org
will
read
that
information
already
from
the
dot
info
files.
If
people
add
it,
but
we
just
don't
we're
not
exposing
it
in
any
way
right,
yes,
yeah,
so
the
the
capability
for
that
to
start
working
is
there.
B
We
just
need
to
figure
out
how
to
actually
have
the
filters
and
the
displays
to
make
the
information
useful,
but
it's
a
little
bit
of
a
chicken
and
egg
thing
right,
like
exposing
those
filters
right
now
wouldn't
help
much
because
of
the
seven
six
or
seven
hundred
modules
we
have.
Almost
none
of
them
have
done
it
yet.
B
So
one
of
the
first
things
we
need
to
do
is
get
people
to
start
updating
their
info
files
to
include
that,
and
it
seems
to
me
maybe
we
need
to
communicate
better
as
a
as
someone
who
maintains
a
number
of
contrib
modules.
I
have
no
idea
what
it
is
I
should
be
doing.
I
think
I
went
in
and
updated
one
or
two
of
my
themes
with
new
image
files,
because
I
knew
that
I
could
do
that.
B
It's
the
only
change
I've
made
any
of
my
my
trip
modules
and
until
someone
sort
of
gives
me
a
list
of
what
I
should
do
I'd
probably
you
know
I
probably
wouldn't
make
any
changes,
and
so
we're
not
going
to
get
this.
It
isn't
going
to
be
useful
until
we
we
really
start
telling
maintainer
have
you.
Can
I
put
you
on
the
spot,
robert?
You
have
a
number
of
modules.
Have
you
started
to
update
all
your
dot
info
files,
yet.
A
B
D
B
Yep
yeah
jenna's,
just
saying
in
in
chat
that
we
could
also
start
filing
tiaras,
and
one
of
my
ideas
was
that
we
have
a
a
beginner
sprint
contrib
sprint,
where
we
get
invite
some
folks
that
want
to
learn
how
to
do
pr's,
and
these
would
be
great.
You
know
this
would
be
a
great
way
to
learn
how
to
do
pr's,
because.
D
B
A
really
simple
change:
we,
you
know
we
could
even
you
know,
call
it
a
training
session.
I'm
writing
prs
for
a
big
crib
and
then
use
it
to
generate
a
bunch
of
prs
and
update
that
info
files
for
maintainers.
B
So,
okay,
let's
so
these
are
some
good
ideas.
I
think
we
should
start
to
promote
that,
and
I
I'd
also
like
to
start
thinking
about.
We
don't
know
again
none
of
our
meetings.
Is
this
really
really
on
topic?
B
So
I
suppose
it
could
come
up
in
any
of
them,
but
we
might
want
to
start
thinking
about
if
that's
part
of
the
reason
why
nothing's
happening
on
this
is
we
don't
have
a
meeting
that
handles
this
kind
of
contribution.
So
jen
just
asked
robert
what
happened
to
the
layout
page
cleanup
issue:
did
you
get
that
in.
A
A
Yeah
so
yeah
that
one,
oh,
the
one
that
grouped,
I
don't
think
that
one's
in
yet
I
don't
think
so.
I'll
have
to
go
look
up
where
it
is.
B
B
B
B
I
think
we
talked
about
this.
The
issue
like
two
weeks
ago
and
people
like
martin
went
and
posted
on
it
right
away,
so
there
should
be
50
77
jen's,
looking
through
the
issue.
B
Okay
yeah
so
two
weeks
ago,
I
think
we
talked
about
it.
It
looks
like
wilbur
went
out
and
tested
it
yeah
and
and
martin
a
couple
people
went
out
and
commented
on
it
right
after
the
meeting
two
weeks
ago,
yeah
I
thought
we'd
talked
about
that
recently.
Okay,
let's
really
end
this
meeting,
though,
because
it's
three
minutes
before
the
hour,
so
the
next
meeting
is
starting
soon
talk
to
you
guys
well
I'll
talk
in
a
few
minutes.
Bye
give
me
a
second
to
find
the
button.