►
From YouTube: Backdrop Weekly - Nov 21st 2019
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,
it
is
Thursday
November
21st,
and
this
is
a
meeting
to
talk
about
active
design
in
user
experience
tasks
for
backdrop
that
includes
product,
but
also
all
of
our
websites,
and
this
week
we
have
started
a
massive
sprint,
improving
issues
primarily
with
the
forum,
but
also
with
the
main
website
and
with
the
API
site.
Any
of
our
web
properties
that
need
attention
are
gonna,
finally
get
it,
which
is
great
thanks.
A
Tim
for
organizing
this
Brant
I
think
we
have
pretty
good
kickoff
this
weekend
and
I've
already
seen
the
work
we
were
doing
this
weekend
trickle
into
this
week
as
well,
so
I'm
hoping
that
momentum
will
continue
and
then
we're
gonna
have
another
big
sprint
this
coming
weekend
and
hopefully
be
able
to
close
as
many
of
these
issues
as
possible.
Then
lingering
for
a
while.
So
it's
good
to
see
some
progress
on
the
API
site.
The
primary
issue
we
wanted
to
fix
is
the
menus.
This
is
the
sidebar
menu
when
you're
on
a
mobile
device.
A
It
tends
to
overlap
everything
on
the
page.
I
think
there
might
be
some
CSS
leftover
in
there
from
the
old
theme
where
we
had
a
drawer
menu,
so
it'd
be
good
to
just
check
there
and
make
sure
that's
working
as
its
supposed
to
and
back
to
pc
masta
org,
and
this
actually
is
a
note
that
goes
for
all
of
our
properties.
We've
been
making
some
minor
improvements
to
the
vork
theme.
In
particular,
we
have
a
better
styling
for
code
tags
and
that
would
work
not
only
on
backdrop
see
mr.
A
A
We
want
to
be
able
to
take
that
theme
and
deploy
it
across
all
sites.
That
theme
has
a
couple
of
accessibility
issues
fixed
as
well.
The
base
font
size
was
previously
16.
It's
now
18,
which
is
Google's
minimum
requirement
for
getting
a
good
flick,
PageRank
score,
and
the
blue
color
for
our
Lynx
was
too
light
to
show
up,
on
the
gray
background
that
we
use
all
over
the
theme
and
so
I've
darkened
it
a
smidge
just
to
make
it
match
line
up
with
accessibility
requirements.
So
I
think
it's
now
2
way.
A
Instead
of
it's
not
freest,
oh,
but
it's
2
I
and
we
might
want
to
consider
going
darker
only
where
we
have
dark
backgrounds,
but
that
seemed
like
it
was
going
to
be
complicated
so
for
now
I,
just
like.
Let's
make
it
one
color
that
we
know
is
gonna,
be
accessible
everywhere
in
the
theme
and
then
there's
a
bunch
of
other
tiny
little
improvements
that
have
been
happening
to
vork.
That
haven't
been
deployed
to
like
the
API
reform
site
recently.
A
So
if
you
get
to
get
those
in
there
too,
on
the
forum
there
has
been
so
much
work
going
on.
It's
been
really
great.
We've
gotten
a
couple
of
the
changes
we
did
last
week,
deploy
I.
Think
Peter
did
the
deployment
on
that.
Thank
you
again
and
then
we
have
a
whole
bunch
more
stuff.
Coming
down
the
pipe.
It
looks
like
there's.
Some
big
functionality
changes
we're
hoping
to
get
implemented.
That
will
make
life
easier
on
moderators
and
anyone
who
gets
any
of
their
content
moderated
whether
accidentally
or
flagged.
A
Otherwise
I
thought
to
see
those
getting
done
and
then
anything
else,
as
you
guys
are
noticing
issues
with
the
forum.
Tim's
been
doing
a
really
good
job
of
taking
feedback
from
the
forum
attorney
into
issues,
but
if
anyone
notices
anything
that
you
want
to
have
done
that
isn't
getting
attention
creating
an
issue
in
the
queue
this
week,
in
particular,
is
a
good
way
to
get
noticed
in
the
future.
I
mean
anywhere,
you
can
post.
That
request
is
good,
but
in
the
queue
is
definitely
going
to
get.
It
looked
at
eventually.
A
Alrighty
so
for
backdrop,
the
product
we
have
a
handful
of
user
experience,
issues
that
we
talk
about
every
time
we
go
through
this
meeting.
There
are
a
couple
of
updates
since
the
last
time
we've
talked
about
user
experience,
flexi
templates
are
flexible
templates
or
whatever
we're
calling
them
have
some
confusing
user
interfaces
just
because
the
problem
space
is
confusing.
A
One
of
them
in
particular
that
we've
been
going
back
and
forth
on
about
what
language
to
use
is
how
to
tell
people
how
their
row
widths
will
behave,
and
so
we
have
it
sounds
like
we
have
a
rough
consensus
that
the
current
proposed
language
is
slightly
better
than
the
previous
proposed
language,
and
so
I
would
like
to
look
forward
with
that.
I'm,
not
sure
it's
perfect,
I
think
there's
definitely
still
room
for
improvement,
but
I
think
even
if
we
can
say
this
is
better
go
keep
working,
find
something
else.
A
A
It
looks
like
everybody,
there
wanted
the
same
behavior,
but
it
was
just
a
matter
of
whether
in
some
places
it's
on
one
line,
two
lines
and
I
think
that's
going
to
be
pretty
easy
to
solve
with
adding
a
class
that
would
either
make
the
item
stack
vertically
or
not,
but
we
can
use
exactly
the
same
markup.
We
could
use
the
same
team
function
to
generate
that
so
I
think
that
is
ready.
Hurtful
requests
also
so
yay
for
consensus.
A
It
doesn't
look
like
we
have
a
generic
issue
for
the
next
one,
which
is
for
indenting
any
fields
that
is
dependent
on
any
other.
It
does
look
like.
We
have
a
views
issue
for
that
which
is
number
1968.
No.
B
B
I
think
yes,
so
so
I
originally
seem
to
file
that
back
in
2016
and
I
noticed
it
on
the
in
the
UI.
There's
some
pretty
good
screenshots
there
that
describe
the
issue
in
very
much
detail
and
the
last
screenshot
is
how
it
looks
versus
how
it
should
look
so
yeah
I'll
see
if
we
can
repurpose
it
and
I'll
spot
out
their
issues.
Okay,
sorry
other
places
in
the
UI
where
this
is
like
very
prominent
I
think
yeah,
that's
great.
It
explains
why
I
couldn't
find
the
issue
before,
because
it
was
too
specific,
yeah
well.
A
We
also
have
a
request
to
change
the
way
drop-down
menus
work,
but
that
issue
as
label
those
needs
more
feedback,
because
if
we
do
change
something
like
the
way,
a
drop-down
menus
work
out
of
the
box-
that's
probably
good,
but
it
will
also
affect
all
existing
sites.
We
want
to
make
sure
all
existing
sites
feel
that
the
change
was
an
improvement
and
if
they
had
added
any
of
their
own
workarounds,
we're
gonna
need
to
properly
notify
them.
A
The
changes
have
happened
so
I,
don't
know
whether
that
needs
to
be
like
setting
you
can
opt
into
or
out
of,
or
how
else
we're
gonna
handle
that.
But
we
definitely
should
continue
talking
about
that
issue
drop
down
menu,
behaviors
number,
twenty
three.
Seventy
in
particular,
that's
the
issue
with
top-level
links
not
getting
visited,
even
though
those
really
the
most
important
pages
so
trying
to
either
duplicate
the
link
or
making
it
easier
for
people
to
know
what
action
expanses
of
menu
versus
floor
action
will
navigate
you
to
a
page
through
the
menu.
A
Isn't
that
unique
to
us
is
the
problem
with
all
drop-down
menus
on
the
internet,
but
finding
some
way
to
solve
that,
for
our
purposes
will
be
good.
We
also
have
a
request
to
change
the
way.
Select
lists
work
so
that,
if
you
ever
have
a
select
list
that
has
only
one
item
in
it,
it
will
not
offer
you
the
choice
to
choose
that
it
will
set
that
item
as
the
default
unless
there
is
a
knob.
A
If
it's
not
a
required
field
like
if
you
don't
need
a
value,
you
could
leave
it
out,
but
if
there's
only
one
option
and
it
is
an
option
and
it
is
required-
there's
no
reason
that
we
should
make
people
click
in
the
button
and
select
the
only
option.
We
can
do
that
for
them
and
there's
a
couple
of
approaches
in
that
issue
about
how
to
do
that
added.
A
B
That
we
were
contemplating
between
either
making
those
fields
where
there
as
plain
text
instead
of
sorry
widgets,
instead
of
being
selected,
select,
dropdowns
or
having
them
be
disciples
and
I'm,
not
sure.
If
the
sort
of
like
the
concern
there
is
accessibility,
as
in
its
plain
text,
any
people
cannot
tap
through
it,
so
they
might
not
know.
Oh.
A
A
And
then
we
have
our
long-standing
issue
to
get
promoted
modules
with
here
as
promoted
in
the
Installer.
That's
issue
31
93,
which
I
don't
think
has
made
any
progress
since
less
and
we
talked
about
it.
I
think
we
had
talked
about
updating
the
parent
issue
for
a
list
of
things
we
need
to
do
in
order
to
get
that
done.
A
B
B
A
Okay,
you
know
we
can
move
forward
on
that
one,
maybe
not
all
right.
We
have
a
handful
of
design
focused
issues.
Also
one
of
them
is.
We
talked
about
the
last
time.
This
meeting
was
to
remove
the
color
change
behind
the
site,
name
and
the
basis
theme,
and
that
was
done
and
merged
Ischia
1483,
so
things
everybody
loves
with
that.
A
We
have
another
issue:
number
40
95
about
how
to
fix
the
gap
that
shows
below
the
hero
block
in
basis,
and
this
is
sort
of
raised
a
bigger
question
about
how
do
we
handle
ongoing
CSS
changes
in
court
like
we
want
to
be
able
to
implement
these,
but
we
don't
want
to
make
every
base
I'ts
when
we
do
it.
We
have
an
example
of
this
earlier.
A
How
do
we
deliver
CSS
in
a
way
that
is
backwards,
compatible
CSS
changes
and
the
only
thing
that
I
thought
of
that
would
be
truly
backwards,
compatible
because
a
little
bit
terrifying,
where
we
would
record
like
the
inversion
of
backdrop
that
you
installed
when
you
install
and
if
any
later
versions
of
cor
include
CSS
changes.
We
would
not
include
those
CSS
changes
on
the
org
site.
A
So
in
order
to
do
that,
every
version
that
includes
CSS
changes
would
need
to
include
a
separate
CSS
file
that
can
be
excluded
so
that
we
only
add
the
CSS
files
that
you
need.
This
is
less
terrifying
now
that
we
have
CSS
aggregation
enabled
by
default,
so
we're
not
going
to
be
creating
like
a
bunch
of
extra
files
added
in
the
header,
but
it
is
going
to
be
a
little
bit
messy
in
terms
of
us
continuing
to
maintain
the
basis
theme
with
a
bunch
of
additional
Styles.
A
One
thing
to
keep
in
mind,
though,
is
that
we
could
come
up
with
a
some
kind
of
a
policy
about
at
what
point
those
CSS
files
get
merged
into
the
core
base
theme.
So
we
could
have
something.
That's
like
obviously,
when
we
get
to
2x
will
expose
all
of
those
into
the
main
file.
But
what
if
we
had
something
that
happened
more
recently
so
like
we
can
give
people
some
kind
of
a
warning
on
their
status
report.
A
That's
like
hey
you're,
only
including
style
sheets,
from
whatever
you
should
test
this
on
your
site
and
see
if
it
works
yes
or
no,
and
when
they
click
that
button
like
I've
tested
it
all
or
whatever.
We
could
update
the
version
in
their
database
and
then
I'll
include
those
files
and
suddenly
could
have
something
you'll
be
like.
After
a
year,
we
squash
those
files
into
the
main
one
I,
don't
know
it
would
be
some
kind
of
internal
policy
thing
that
we
could
build
into
core.
A
That
might
make
it
a
little
easier
on
people
and
give
them
more
time
to
like
test
the
changes
that
are
applied
to
see
if
they
break
or
not
fix
them
or
not,
and
then
they
could
have
that
warning
go
away
on
their
status
report
if
they
aren't
updated
and
then,
if
they
didn't,
it
would
continue
to
be
there
like
at
some
point.
Your
sites
can
break
hoping
first,
these
days
so
yeah.
A
C
A
We
need
some
kind
of
naming
convention.
I
was
thinking
about
even
including,
like
their
version
number
in
the
file
name,
and
then
we
could
just
have
a
tool
that,
like
looped
loop,
therefore,
all
the
file
names
and
included
anything
that's
like
less
than
you're,
installing
the
verb,
something
like
that
or
we
could
just
include
them
all
one
at
a
time
depending
I.
Don't
know
how
many
versions
are
gonna,
how
many
core
minor
changes
to
the
game,
it
probably
will
be
all
done.
Would.
B
D
Are
you
cutting
it's
gonna
ask
about
sort
of
an
alternative
approach
that
similar,
which
is
just
to
have
a
single
option
in
the
theme
which
says
I'd,
either
like
to
freeze
my
CSS
or
or
feel
free
to
push
changes
my
way
and
then
it's
just
a
single.
You
know,
then
all
new
changes
can
go
into
one
file
and
the
user
would
be
giving
us
a
blanket
like
no
don't
touch
my
CSS
for
sure
I
can
handle
it,
and
then
we
would
different
iterations.
B
Of
something
advices
and
keeping
the
base
theme
for
everyone
and
make
an
additional
step
for
people
that
want
to
actually
but
I'm,
not
sure
how
versioning,
because
everything
that
is
included
in
core
it
inherits
the
version
from
core
with
each
release
and
I'm,
not
sure
if
we
could
sort
of
like
have
semantic.
Versioning
has
three
digits.
If
we
had
a
fourth
we'll
just
Isis
or
something
like
that
for
the
thumbs
up
in
some
places.
So
the
idea
was
that
everyone
keeps
their
basis
version
like
the
main
theme.
A
Still
have
this
exact
same
problem,
though,
if
we
had
changes
in
the
sub
theme
that
need
to
be
made,
so
we're
not
avoiding
the
problem,
all
right,
not
solving
it,
we're
just
creating
another
place
for
it
to
appear,
and
there's
also
a
kind
personally
against
adding
more
themes
to
core,
because
that
ends
up
getting
really
confusing,
especially
if
they're
base
themes
are
people
who,
like
don't
know
where
they're
like
install
the
main
one,
and
then
it's
all
the
sudden
they're
like.
Why?
Is
it
not
different?
It's
just
not
a
like.
A
B
B
Yeah,
that's
that
sounds
a
bit
more
yeah,
but
then
we
need
to
come
up
with
a
policy
that
says
that
if,
if
I
see,
exchanges
are
actually
bad
fixes,
we
are
allowed
to
do
it
but,
for
example,
things
that
are
opinionated
as
in
removing
the
background
color
from
the
logo
or
something
like
that,
they
should
go
in
a
sub-theme.
It's
at
some
point
we
merged
into
poor
or
something
anything.
A
In
the
theme
is
sort
of
subjective
as
to
whether
it's
about
fix
or
whether
opinionated
like
that
an
image
flow
thing
right,
we
thought
it
was
a
bug
fix,
but
then
it
broke
everything,
and
so
that's
something.
That's
like
it's
not
safe,
even
though
it's
a
bug
fix,
it's
not
safe.
To
put
it
in
the
base
theme,
so
I
think
that
that
kind
of
issue
we're
dealing
with
now
is
like
well
is
it.
B
The
thing
that
you
mentioned,
it
was
an
exception.
It
was
actually
we
thought
that
it
was
a
fix
and
we
didn't.
We
didn't
know
that
it
was
changing
things
like
breaking
things
from
sites,
whereas
the
change
with
the
background
of
the
log
home,
like
the
name,
the
site
name,
we
knew
the
side
effects
like
we
knew
what
we
were
changing
and
we
knew
what
it
would
affect,
whereas
the
other
thing
we
just
regretted
it,
because
it
was
unintentional,
we
didn't
mean
to
break
feet.
The.
A
A
D
A
Think
I
think
they're
I
think
we
need
to
be
able
to
like
have
a
policy,
but
every
every
issues
to
only
subscribe,
stand
on
its
own
merit
and
be
like
this
is
gonna,
make
it
easier
for
new
people
to
place
hero
blocks
on
their
feet,
like
that's
an
important
thing,
I
think
and
that
might
outweigh
it.
Like
opinion
of
the
person
who
have
the
original
theme
that
intended
there
only
be
one
yeah.
B
A
It
also
check
the
way
that
Drupal
worked
is
that
if
you
had
a
corporate
a
core
project
name
basis
and
a
kinship
project
name
basis,
the
kinship
project
would
win.
You
could
do
the
same
thing
in
backdrop
if
we
did
have
anything
super
opinionated,
but
that
means
that
every
time
we
had
a
core
release,
we'd
have
to
have
like
a
I,
really
said,
the
basis
theme
at
the
same
time.
That
includes
all
of
the
same
changes
that
we
wanted.
It
that's.
B
A
I'm
true
interesting,
yeah
I
was
thinking
if
we
just
had
a
copy
of
basis
in
contribute
win.
That
war
see
like
I
like
to
use
the
core
one
that
has
all
the
spirits
I've
already
use
it
like
fixed
one
and
can
trip,
and
then
it
wouldn't.
You
wouldn't
have
that
issue
of
like
it's
two
themes,
so
you
still
just
have
one
theme
you're
just
overriding
the
whole
thing
Gil
got
that,
but
it's
adoption
does.
A
But
yeah
I
personally
would
like
to
be
able
to
include
CSS
changes,
in
course,
so
that
new
installs
are
better.
You
know,
ask
somebody
who's
running
a
lot
of
older
backdrops.
Next
I
also
feel
the
pain
of
like
not
wanting
to
break
things
you
weren't
expecting
to
break
when
you
do
a
core
update,
you're
like
yeah
it'll,
be
fine
you're
like.
Why
is
my
theme
not
working
and
so
having
some
way
to
be
able
to
those
changes
or
not
I.
A
Think
it's
important
I
do
like
the
idea
of
having
only
one
thing
to
include
Tim
like
either
include
the
CSS
or
don't,
and
that
also
could
be
something
that
would
be
pretty
easy
to
document.
I
feel
like
if
you
update
a
core
and
your
theme
is
broken,
go
and
check
this
box
and
it'll
put
it
back
the
way
it
was
before.
I
think
that's
gonna
be
easy
for
people
to
understand.
B
So
I
was
so
under
yeah.
Sorry,
we
could.
We
could
have
like
a
second
basis,
heads
or
something
like
that.
We
could
have
a
policy
and
say
that
this
any
breaking
changes
got
go
into
that
and
people
can
only
intentionally
switch
to
that
and
we
sort
of
say
that
yeah.
If
you
rely
on
a
basis
of
thing-
and
you
want
on
the
you
you,
you
are
aware
of
those
changes
and
breakages
and
that
you
will
may
have
to
fix
your
theme.
Then
you
switch
to
that.
If
you
want
to
be
safe,
just
stick
with
basis.
B
A
Version
that's
fixed
having
something
like
that,
or
at
least
it
fixes
fix
and
stuff
from
basis.
It's
gonna
be
really
hopeful,
I'm,
not
sure
that
it
meets
yeah,
I,
don't
know,
I.
Think
I
think
it's
good
to
kind
of
keep
an
eye
on
what
people
are
doing
with
it.
But
I
would
like
to
continue
to
improve
backdrop
as
installed,
and
sometimes
that
might
be
big
breaking
changes.
Yeah.
B
C
A
B
D
A
It
would
be
good
to
know
that
we
have
other
options
too,
but
the
problem
is
if
they
stay
in
core.
So
if
you
get
to
come
up
with
solution
for
like
how
do
we,
how
do
we
improve
core
without
hurting
injury
or
any
custom
whatever,
but
I
think
like?
If
we
do
have
something
that
is
drastic
coming
up
with
a
way
to
deal
with
that,
whether
it's
add
a
new
core
theme
like
or
trust
us
or
it's
free
to
contribute
over
at
court
or
whatever?
It
would
be
good
to
have
another
option.
D
Well,
if
we
do
have
a
basis
to
trim
things
managing
that
and
like
shouldn't,
you
know,
is
there
any
effort
being
made
to
cross
port
our
changes
to
face
the
coalface
is
core
to
that
can
trip
be,
then
we
don't
have
to
do
it
today.
We
might
want
to
talk
about
what
you
don't,
what
the
status
of
that
consume
is
and
how
we
are
using
this.
A
Yeah,
so
the
contributing
we
have
now
was
developed
for
four
basis,
one
in
the
core.
Just
for
testing
and
I.
Don't
think
it's
been
updated
since
basis
one.
So
it's
sort
of
the
opposite
of
what
we're
talking
about
now.
Well,
that
doesn't
mean
we
couldn't
change
its
purpose
right
now.
It's
sort
of
abandoned
like
oh.
This
was
useful
once,
but
now
we're
ignoring
it.
A
But
if
we
were
to
take
it
back
and
say,
hey,
let's
make
this
into
something
where
we
can
test
new
changes
and
we
can
even
have
people
install
the
basis,
can
trip
themed
and
see
if
it
breaks
there,
some
themes
or
whatever
that
might
be.
It
might
still
be
a
good
testing
tool,
even
if
it
wasn't
a
recommended
and
useful
that
it
could
be
both
yeah.
B
So
the
current
description
of
the
of
that
thing
is
contributing
of
the
fall
team
and
backdrop.
This
repo
is
used
to
create
experimental
features
and
may
add
features
that
we
don't
plan
to
add
the
core.
So
it's
sort
of
like
fits
the
purpose
on
the
description
and
in
the
last
commits,
has
been
like
three
or
four
years
ago.
Sorry,
yeah.
D
E
D
A
D
D
B
B
D
D
You
know:
I
want
to
make
I
wanted
to
create
a
starter
yet
to
something
tap
suit
and
I'm,
starting
to
regret
that
decision
a
little
bit,
partly
because,
on
the
one
hand
like
updates,
you
know
the
reason
for
something
being
things
is
that
I
want
to
get
benefits
from
from
poor.
But
now,
if
we've
got
tirta
to
steps
in
there
right
now,
I
think
OSHA
made
the
Turkish.
B
D
Get
that
and
I
mean
I
have
to
make
this
decision
on
my
own
I
don't
know.
Maybe
this
doesn't
relate
to
the
other
discussion,
but
I
mean
it
only
sort
of
relates
to
it.
Did
that
you
know.
One
of
my
goals
is
to
help
make
it
easier
to
something
and
I'm
sort
of
doing
that
through
tattoo.
It's
not
putting
a
starter
kit
into
tattoo,
and
it's
like
you
know,
maybe
this
I
don't
know
I'd
like
to
go
back
to
that
is
there?
D
B
A
A
C
D
D
A
A
But
I
also
would
be
curious
to
know
like
what
kind
of
problems
you're
having
with
text
being
a
subhuman
core.
I
know
there
was
a
bunch
of
stuff
that
they
put
into
like
info
files
in
Drupal
8
that
made
it
much
easier
to
sub-theme
so
like,
for
example,
if
you
don't
want
to
include
things
there's
the
way
you
can
like
remove
things
explicitly
and
I
wonder
if
we
need
more
of
that
kind
of
support
for
something
so
like.
If
you
want
to
say
the
color
disabled
that
easily
so
it'll
be.
D
B
So
this
is
this
is
so
that
something
can
hurt
color
settings
right
yeah,
so
my
my
general
take
on
base
is
that
there's
certain
things
that
are
repetitive
and
can
be
automated
with
creating
sub
things,
and
if
we
can
automate
those,
then
we
lower
the
steps
at
the
time
that
people
require.
So
it
makes
it
more
less
of
a
struggle
how
much
less
it
might
be
just
a
tiny
bit,
but
depending
on
how
tech-savvy
people
are
and
how
proficient
with
Drupal
or
backdrop.
A
Aaron
has
been
working
on
some
fantastic
designs
banner
and
now
that
I
know
we
have
an
event
coming
up
where
we
have
a
booth.
I'm
super
excited
about
it,
so
I
keep
checking
in
on
this
issue,
number
424
in
the
back
drive,
CMS
org
queue
and
the
latest
comment
there.
Our
second
latest
comment
has
a
version
of
the
banner
that
I
think
looks
really
great.
That's
our
logo.
It
has
dragon,
it
has
our
mission.
It
has
some
of
the
reasons
you
might
want
to
choose
backdrop.
A
It
has
our
website.
Url
I,
think
it
looks
really
great
I
would
love
to
see
that
get
finalized
and
then
figure
out
how
to
print
such
a
thing
and
I.
Also
wonder
if
we
need
anything
else
for
a
conference
thinking
about
conferences
that
I
go
to
and
seeing
what
other
people
have
at
their
booths
stickers.
Obviously
we
have
those
do
we
need
a
like
pamphlet
or
our
business
cards
in
that
it
just
has
like
visit
the
website
on
it.
B
D
What
else
is
it
well,
I
think
the
right
approach
to
this
right
is
to
think
about
the
problem
we're
trying
to
solve
what
are
our
goals
at
the
country?
What
do
we
hope
to
get
out
of
interacting
with
people
top
of
my
head,
like
I?
Don't
want
printed
materials
at
conferences
anymore
supposed
to
be
anything
printed
doesn't
feel
like
it
would
be
useful,
but
I
don't
know.
Let's
talk
about
what
you
know,
yeah
I
would
I
would
think
that
the
major
goal
is
to
talk
to
people,
maybe
to
get
a
business
card
in
their
hand.
A
Don't
want
print
materials,
but
I
am
constantly
surprised
by
how
many
people,
though,
do
card
and
like
I,
can't
believe
you
mostly
using
cards,
but
they
are,
is
I'm
like
okay,
what
people
are
using
them
wish
to
have
them.
So
that's
the
thing
I
also
was
thinking
of
doing
some
kind
of
a
like
what
I
want
them.
The
point
of
this
thing
is
we
want
them
to
know
about
back.
We
want
them
to
know
that
it
is
very
similar
to
Drupal
7,
yet
newer,
/,
better
/,
more
affordable,
/,
whatever
it
is.
B
So
I'm
sure
that
this
is
gonna,
be
maybe
mostly,
but
what
you're
describing
is
like
at
EOS
with
a
computer
that
people
can
play
with
and
we
already
have
the
demo
sites.
So
that's
one
thing:
it's
funny.
It's
funny
that
you
mentioned
see
how
you
said:
I
really
like
the
versions,
the
two
versions
that
I
saw
now
that
they
can
haven't
revisited
that
ticket
about
the
banner.
But
one
thing
that
is
missing
compared
to
the
version
before
it
with
the
dragon
out
of
the
egg
is
mentioning
Drupal
7.
D
B
Yeah
yeah,
so
the
thing
is:
if
you
go
to
a
troppo
conference
with
that,
it's
hello.
This
is
a
new
CMS,
whereas
I
think
that
saying
this
is
the
seven
improved
or
this
is
your
go-to
solution,
if
you,
if
you're
having
second
thoughts
about
moving
to
to
d8.
So
if
we
don't
mention
d7
at
all,
then
it
we
are
presenting
it
as
a
totally
new
CMS
and
we
my
my
concern
there
is
that
we
might
lose
a
bit
of
audience
there.
It.
A
I
also
feel
like
this
conference
in
particular,
is
not
a
Drupal
conference.
It's
a
nonprofit
technology
conference,
but
the
primary
reason
we're
there
is
because
all
of
those
people
are
already
on
Drupal,
7
and
so
I
think
having
something
that's
like
hey.
This
will
be
easy,
for
you
is
gonna,
be
important.
I,
don't
know
that
it
needs
to
be
on
our
banner
like
that
banner
could
work
for
other
events
where,
like
people
know
it
don't
know
what
Drupal
is
or
I
mean
there
could
be.
A
People
like
this
audience
also
don't
know
what
Drupal
is,
and
we
still
want
to
invent
something
a
website,
but
I,
don't
I,
don't
know
I
mean
maybe
I
should
be
on
the
banner
we
can
make
another
later.
Maybe.
B
C
D
B
B
A
B
A
A
A
B
Maybe
add
it
so
that
can
be
discussed
during
next
meeting.
So
it's
about
the
UI
pattern.
It
fits
in
the
UX
a
bit,
so
it's
ticket
3385
and
that's
where
I'm
stuck
with
the
state's
problem
that
I
mentioned.
So
the
idea
there
is
to
sort
of
like
reuse.
The
same
UI
pattern
that
we
have
for
the
language
is
the
drug
ability,
because
in
languages
we
have
the
crosshair
that
allows
you
to
drag
them
reorder
them.
So
my
when
I'm
stuck
at
this
moment
is
I'll
file,
a
pull
request.
Cuz
I,
have
it
ready
it
works.
B
But
what
doesn't
work
is
that
if
you
selected
one
default
language
and
the
respective
checkbox
sorry
so
types
it's
item,
the
respective
checkbox
gets
disabled
so
that
you
cannot
have
something
that
is
default
and
at
the
same
time
sorry,
maybe
I
should
say,
gets
locked
as
enabled
so
that
you
cannot
disable
something
that
is
set
as
default.
The
problem
is
that
if
you
move
the
default
options
to
something
else,
this
segment
remains
blocked.
B
So
that's
a
problem
with
us
the
day.
Yes,
I
guess
the
state
system
I'll
try
to
see
if
I
can
fix
it,
but
my
so
I
may
need
help
with
that,
and
this
is
an
existing
bug
like
or
UX
WTF
thing
for
the
language.
So
it's
not
specific
to
this,
and
what
I
would
really
wanted.
Quick
feedback
on
is,
should
I
file
a
pull
requests
as
there
is
now
because
the
problem
that
I'm
facing
is
a
known
problem
because
it
in
other
bids
or
should
we
fix
everything
and
really
get
to.
B
And
what
I
can
do
is
maybe
file
to
pull
requests.
One
does
not
include
any
states
functionality
and
one
does
so
that
you
didn't
see
what
would
happen
like
quick
admits,
the
do
I
fix
like
the
conversion
to
a
typo,
and
then
you
can
use
the
sandbox
that
is
created
by
the
second
year
to
see
black
live.
What
what
what
I'm
talking
to
when
I
say
the
bag
from
his
likes
thing.