►
From YouTube: Backdrop Weekly meeting - Feb 7
Description
Today’s development agenda: http://bit.ly/2G1EUi3
A
All
right
we
are
on
air,
it
is
Thursday,
February
7th,
and
this
is
a
meeting
to
discuss
ongoing
issues
for
backdrops,
EMS
Corps
and
surrounding
things
that
are
important,
starting
with
contributed
projects.
We
have
one
new
release
this
week
is
Ana,
be
referenced,
module,
which
is
a
little
interesting.
My
guess
is
that
probably
the
reason
we
have
that
is
that
there
was
some
other
kinship
project
that
depended
on
entity
reference,
and
so
somebody
thought
that
it
would
be
better
to
just
finish.
A
What
was
there
rather
than
trying
to
rewrite
the
other
thing
that
depends
on
it,
but
we
do
have
another
reference
module
solution
that
we
prefer,
so
it
would
be
good
to
figure
out
what
that
other
module
is.
That
depends
on
it
and
take
a
look
at
that
and
see
what
kind
of
changes
necessary
to
make
those
other
modules
that
depend
on
and
review
reference
to
a
non
reverence
instead
and
to
see,
if
what
kind
of
backwards
compatibility
we
can
provide
to
make
it
easier
for
people
who
are
recording
modules
that
depend
on
M
V.
A
Reference
should
now
depend
on
reference
instead
website
related
in
our
outreach
meeting.
We
talked
in
depth
about
the
modules,
themes
and
layouts
related
changes,
as
well
as
search
in
general,
which
will
also
talk
about
a
little
later
in
this
meeting,
but
here
L
can
watch
that
video
to
find
out
what
we
said.
We
also
talked
a
lot
about
the
homepage
demo
button,
but
we
wanted
to
follow
up
with
me
in
this
meeting
and
see
if
there
was
anything
else
we
need
to
do
for
that.
A
So
far,
a
list
includes
implementing
the
suggestions
that
were
already
made,
linking
up
the
homepage
to
the
new
demo
page
and
then
making
sure
that
the
other
ways
to
install
backdrop
pages
ready
to
go
as
well,
and
then
we're
probably
ready
to
release
that
to
the
wild
I
did
notice
on
this
agenda,
though
neat
it
says
occasionally
fails
making
sandboxes
I
haven't
run
into
that.
Do
you
want
to
talk
a
little
bit
about
that
issue?
Yeah.
B
It
came
up,
I
think
duck
Wilma
encountered
it
when
he
was
doing
his
testing
as
well.
I
took
a
screenshot
put
it
in
the
issue.
I've
encountered
it
several
times
as
well
that
sometimes
you
click
create
a
demo,
and
it
says
a
demo.
Sandbox
could
not
be
created
at
this
time,
but
then
you
click
again
and
then
it
works.
So
wonder
like.
C
One
of
my
colleagues
had
a
similar
problem.
I
think
I
mentioned
this
before,
where
it
was,
it
seemed
to
be
quicky
related,
so
when
he
deleted
all
the
backdrop
same
as
doc,
dog,
which
is
from
his
browser,
everything
started
working
and
for
them
I
think
it
launched
the
the
sandbox,
but
then
it
freaked
out
at
the
end
of
the
Installer
at
some
point
with.
B
Unexpected
error,
I
haven't
had
that
one
occur
but
yeah
they,
the
sandbox
not
being
created,
seems
to
be
the
tugboat.
Sometimes
just
doesn't
provide
a
response
either
that
or
it's
providing
something
that
our
code
isn't
pricing
correctly,
and
so
it
thinks
that
it
fails
I'm,
not
certain,
but
I,
yeah
I,
don't
know.
I.
Think
I
would
like
to
figure
out
the
the
root
of
that
having
it
fail
intermittently.
Even
can
be
really
confusing.
You
know,
because
you
think,
oh,
it
doesn't
work
and
that's
a
very
bad
first
impression.
Although.
A
A
B
A
Like
that
problem
is
probably
less
bad
than
the
now
you
have
to
create
a
Pantheon
account
experience
that
people
get
currently
which
would
just
prevent
them
from
trying
it
at
all
where
I
think.
If
it's
just
a
button,
click
they'll
click
the
button.
Again,
that's
not
a
lot
of
effort
on
the
user.
Just
part,
yeah
I
think
that's
better
yeah.
A
A
B
B
A
Update
I
put
a
note
here,
Olaf
that
you
are
planning
on
working
that
today
and
I
also
added
a
note
that
we
are
gonna
meet
after
this
meeting.
So
it
does
look
like
Jeff's
here,
but
if
anybody
else
is
interested
in
working
on
translation
site
stuff,
maybe
they
should
happen.
That
meeting
and
also
Olaf
has
set
up
a
localization,
specific
Gitter
channel.
So.
A
D
Shortly
I
was
in
last
week,
so
I
couldn't
manage
to
do
a
lot
of
things,
but
I
think
so.
Regarding
a
status.
I
think
the
most
important
thing
at
the
moment
is
to
get
the
English
language
files
so
the
first
the
source
files
for
the
translation
server,
and
that
is
still
an
issue
and
there
are
two
tasks.
So
the
more
difficult
is
to
automate
this.
We
talked
about
this
a
couple
of
times
and
I.
A
B
Okay,
well,
we'll
start
with
112,
which
is
the
next
bug
fix
release.
It
has
been
two
weeks
now
actually
three
weeks
since
the
release
of
backup
112
and
we
promptly
came
out
with
112
one
to
coordinate
with
the
Drupal
security
release.
We
should
probably
get
through
the
issues
that
are
currently
marked
are
TBC
and
then
to
make
a
release
for
this
as
soon
as
possible
and
John
I
think
just
typed
in
the
schedule,
possibly
tomorrow
as
possibly
we
should
schedule
it
for
tomorrow,
which
is
even
better
I,
think
yeah.
B
Yeah
of
note,
we
have
several
really
substantial
issues
that
could
be
corrected.
One
of
them
is
a
regression
actually
the
upgrade
to
views.
Views
now
has
support
for
CSS
grid
and
it
was
supposed
to
be
backwards
compatible
where
the
current
sites
were
going
to
continue
using
the
old
table
based
grids
and
new
views
would
use
CSS
created
by
default,
but
you
could
still
use
the
table
based
one
if
you
wanted
to.
B
In
the
meantime,
it'll
use
the
new
CSS
based
one,
but
if
you
haven't
modified
your
views
to
use
the
new
one
or
set
up
new
ones,
then
they'll
have
an
undefined
value
and
that's
what
this
update
hook,
corrects
it'll
set
it
back
to
the
legacy
approach,
so
that
issue
has
been
marked
directed
BC.
Also,
a
recent
discovery
is
that
github
or
AWS
has
changed
something
about
the
way
that
they
authorize,
download
requests
and
since
AWS
and
github
hosts
all
of
our
release
files,
something
on
their
side
is
now
being
more
strict
and
Drupal
or
spectra.
B
B
Her
bill
filed
an
issue
or
filed
a
poll
request
to
correct
that,
although
he's
unable
to
reproduce
the
problem,
so
anybody
that
is
experiencing
that
problem,
you
could
try
that
poll
request.
That
would
be
really
great
to
know
if
we're
going
to
solve
some
problem
with
that
fix
or
not.
I
think
that
the
code
that
he
submitted
is
going
to
be
fine,
either
way
like
we
should
go
ahead
and
merge.
It
because
it's
not
going
to
hurt
anything,
but
it
would
be
great
to
know
for
certain
that
we've
actually
fixed
the
problem.
B
Let's
see,
there's
also
a
couple
more
RTL
issues
that
we've
been
highlighting
right
to
left
language
issues,
there's
two
more
that
are
in
the
112
milestone
that
need
review
and
one
that
is
our
TBC
and
two
more
that
need
patches
or
need
need
pull
requests.
So
that's
great
I'm
really
happy
to
see
those
RTL
issues
continue
to
roll
in
and
continue
to
be
corrected.
Sorry
can
I
ask
a
quick
question.
C
I
asked
this
in
Gator,
but
I
didn't
get
a
response.
What's
the
current
policy
with
regards
to
bug
fixes
specifically
and
the
milestone
candidate,
talk
that
we
use
do
bug
fixes
still
go
automatically
to
the
next
bug
fix
really
so
do
we
need
to
discuss
it
and
have
approval
by
a
second
person
to
say
that
this
atomizer
on.
A
C
Then
we,
these
numbers
need
to
be
updated
to
five
I
just
filed
another
three
RTL
issues
and
they
don't
have
requests.
I
was
just
wondering
regarding
that:
I'll
leave
a
leave.
One
of
them
specifically
was
a
bit
awkward.
It
had
to
do
with
the
way
that
special
characters
like
greater
then
and
lower
then
treated
when
when
text
is
wrapping
in
left
to
right,
but
I'll
leave
that,
for
the
end
of
the
meeting
to
discuss
sometime.
B
Yeah
also
I
think
that's
good
to
get
additional
eyeballs
on
things,
but
if
anything
is
marked
are
TBC,
regardless
of
its
milestone.
I
frequently
check
the
entire
are
TBC
Q,
so
if
it
gets
to
our
TBC,
it
doesn't
really
matter
what
its
milestone
is.
If
it's
ready
to
go,
if
it's,
if
it's
bug
fixed
suitable
I'll
put
it
in
and
I'll
see
it
at
least
that
that's
my
personal
behavior
I
know,
we've
got
herb.
Dueling
Jeff
as
well.
C
Another
issue
that
I
remembered
I'm,
not
sure
if
it
needs
to
go
to
the
back,
the
next
bug
fix
race
or
it's
a
big
change,
and
then
it
needs
to
go
to
113
so
check
up
on.
They
filed
an
issue
that
is,
as
we
mentioned,
multiple
times
now
that
we
have
multiple
security
releases.
Then
core
complaints.
If
someone
is
hesitated
to
the
latest
previous
security
branch,
but
they
don't
want
to
upgrade
to
the
next
plan.
So
if
they
have
upgraded
to
1.11
they're
in
latest
security
release,
the
the
site
status
complains
about
a
signal.
B
C
Zack
filed
an
issue
for
that.
Let
me
see
if
I
have
that
up
in
some
way
its
issue:
three
five
to
four
and
a
bit
digging
around
and
thank
Allah
for
finding
that
the
respective
issue,
indeed
no
dog
and
held
they
seem
to
have
sorted.
That
issue
for
d8,
was
that
they
temporarily
used
the
workaround
where
they
actually
had
coded
corporations
so
that
it
doesn't
complain,
and
then
they
came
up
with
a
more
robust
solution.
B
I
I
would
say
as
soon
as
we
can
correct
that
that's
bug
fix,
release
worthy
just
making
it
so
that
security
updates,
like
it
can
figure
out.
If,
like
one
three
four
and
one
twelve
one
have
the
same
security
fix.
I'm,
not
sure
I
said
that
right,
but
yeah,
two
different
minor
versions
there
bug-fix
releases
might
both
have
the
same
security
fixes.
I
think
we
need
to
update
our
feeds
so
that
we
specifically
say
like
this.
B
B
C
Yeah
because
then
we
would
have
the
issue
where
imagine
that
we
have
just
this
possible
situation
where
we
have
two
security
releases
for
both
branches,
that
to
latest
branches.
But
then
the
the
logic
accommodates
for
that,
and
we
don't
like
like
if
we
separated
by
a
branch,
then
it's
the
latest
branch
for
some
reason
gets
a
security
release
and
there's
no
equivalent
released
for
the
without
1.11
branch.
C
C
And
because
that's
that's
a
bit
more
elaborate
for
a
solution,
I
think
that's
the
way.
That's
the
reason
why,
in
backdrop,
they
decided
to
fix
the
immediate
problem,
the
the
immediate
problem,
with
with
hand
coding
by
hot
coding
things,
and
then
they
deprecated
that
function
when
they
they
came
up
with
a
better
solution.
Great.
B
A
There
are
a
bunch
of
this
was
in
the
like
open
discussion,
section
I,
just
moved
it
up
to
this
part
of
the
agenda
cuz.
We
recommend
it
now,
but
there
are
a
bunch
of
things
that
we
have
to
figure
out
how
to
handle
this
of
her
really
and
if
we
want
to
do
a
quick
fix
like
the
next
release,
I'm
totally
fine
with
that,
but
we
also
talked
about
like
figuring
out
what
our
policy
is
about
backwards.
Like
previous
version,
security
updates,
I
think
we
had
previously
discussed.
A
That
logic
to
be
like
this
number,
like
minus
three
major
version,
numbers
or
whatever,
and
then
check
the
most
recent
there
sort
of
thing,
but
until
we
have
a
policy
around
how
many
releases
back
are
we
going
to
maintain
secure
versions
of
it's
really
hard
to
code,
something
general
that'll
account
for
it?
I
think
we
should
either
do
the
like
hard
code,
the
specific
versions
that
are
secure
or
we
need
to
adopt
a
policy
that
we
can
double,
because
it's
different
every
release,
that's
gonna,
be
really
hard.
If.
C
We,
if
we
have
the
policy
in
place,
the
logic
would
be
simpler,
but
then
we
we
add
a
lot
of
overhead
in
the
for
that
for
that
core
committers
like
when
they
do
the
releases,
because
they
will
have
to
do
three
simultaneously.
Release
is
correct:
Alissa,
creating
things
yeah
yeah,
that's
something
to
be
decided.
Yeah.
A
So
that's
why
I
think
whenever
PMC
issue
to
talk
about
like
because
I
think
as
long
as
you,
it
consistently
doesn't
matter
what
we
do
and
but
it
should
be
publicly
stated
what
the
policy
is
ever
really
know.
They
have.
You
know
eight
months
instead
of
a
year
or
whatever
it
is,
and
then
as
long
as
long
as
we
do
that
consistently
all
the
time.
That's
fine!
So
if
three
releases
is
too
much,
we
could
do
two,
but
I
think
we
just
need
to
have
something
so
for
this
release.
A
B
C
A
E
E
B
Yeah
and
hopefully,
as
time
goes
on,
you
know
if
auto
updates
actually
become
a
things.
That'll
become
it
it'll
be
interesting
because
the
sites
might
update
more
frequently,
but
also
people
might
stay
on
minor
releases
longer
if
they
ought
to
update
security
fixes
right,
and
so
it
would
actually
make
it
more
valuable
to
provide
a
longer
release
lifetime
for
minor
versions
like
if
we
were
applying
security
fixes
only
like,
because
that
would
be
our
initially
default.
Auto
update
setting
would
be
security
fixes
only
right,
yeah.
C
Just
a
quick,
that's
there!
So
from
the
uses
it
seems
that
out
of
the
more
than
eight
hundred
sites,
half
of
them
436
are
on
one
dot,
12.1
and
then
maybe
another
two
or
three
hundred
are
on
1.11
and
then
you
have
like,
even
in
40
sites
on
1.9
or
1.8,
which
are
really
outdated,
I
think
it's
safe
to
consider
those
sites.
The
respective
thing
of
abandoned,
like
as
the
DC
sites
that
are
just
lingering
on
little
negative
stats.
Maybe.
B
B
A
One
year
because
it
seems
like
a
lot
of
time
for
companies
that
have
a
site
to
get
the
update
done,
and
it
also
is
a
very
easy
amount
of
time
to
remember.
I
think
if
we
did
two
versions,
it's
eight
months
is
hard
for
people
to
keep
track
of.
Like
oh
well,
it's
the
version.
Eight
months
ago
from
now
I
am
concerned
about
the
amount
of
overhead
that
puts
on
core
developers
but
I
think
from
an
end
user
perspective.
C
B
C
B
D
B
You
know
that
does
also
make
it
I.
Like
your
point,
a
lot
about.
We
should
be
consistent,
like
it
shouldn't
be.
Sometimes
they
get
an
orange.
Sometimes
they
get
fewer
with
the
exception
and
maybe
something
that's
really
catastrophic
and
then
like
dribble
getting
two,
which
is
the
one
that
we
went
back
three
versions
for
just
because
that
was
the
second
more
security
vulnerability
ever
intro.
A
E
B
Let's
carry
on,
let's
see
so
those
those
that's
a
summary
for
112,
which
is
not
a
security
release.
We
were
just
thinking
about
security
as
well,
but
that
should
be
coming
out
tomorrow.
If
we
complete
all
of
these,
not
if,
but
it
will
come
out
tomorrow
and
we
hope
to
commit
all
of
the
are
TBC
and
related
downloading
and
updating
issues
as
well
for
113
113
will
be
released.
May,
15th,
2019
and
large
ticket
items
that
we
have
slated
for
at
113
include.
B
Dashboard
dashboard
is
issue
495,
there's
a
working
pull
request
there.
That
adds
essentially
a
port
of
the
total
control
module
from
Drupal
7
to
backdrop.
I
think
we
need
yeah.
We
need
some
feedback
and
thoughts
there
as
to
what
we
and
put
on
that
dashboard
and
how
it
should
work.
Technically,
it's
looking
great
usefulness,
wise
I,
don't
know
I
mean
maybe
its
usability
is
great
or
its
usefulness
is
great,
but
it's
in
my
opinion,
it's
overwhelming.
A
We
want
to
add
to
the
dashboard
and
I
know
right
now:
there's
issues
about
like
adding
charts
and
adding
icons
and
adding
you
know
more
useful
blocks
and
I
think
all
of
that
can
come
later
and
so
I
would
love
to
see
something
getting
as
fast
as
possible.
Just
so
we
know
we
have
something
for
the
next
release.
So
if
we
can
get
more
testers
on
that
to
give
us
our
feedback
on
if
it
is
ready
to
go
in
now
or
not,
that
would
be
great.
That
was
in
one
book.
This
thing
owns
oh
yeah,.
C
B
Let's
say
also
an
issue
that
is
following
up
on
work
from
11234
55
is
adding
translatable
strings
to
core
config
files.
Her
bill
has
started
actually
adding
those
translatable
strings
to
config
files,
and
he
started
with
looks
like
views
and
image.
Styles
views
layouts
and
image.
Styles
use
me
boy.
He
really
is
swinging
for
the
benches
there,
because,
like
the
most
complicated
things
you
can
do,
but
that
that's
awesome
that
will
make
it
so
that
the
string
extraction
translator,
the
PIO
TX
module
ultimately
will
be
able
to
pull
out
translatable
strings
from
config
files.
B
B
We
got
an
updated
technical
like
proof,
basically
from
John
Franklin,
with
an
alternative
for
package
signing
using
open
SSL
as
its
basis
for
signing
it
looks
kind
of
promising.
Possibly
also
has
the
advantage
that,
unlike
the
previous
approach
that
I'd
filed,
it
does
not
require
external
dependencies
for
sorting
it
doesn't
require
any
new
like
bundled
dependencies.
So
that's
another
potentially
like
promising
implementation
there.
That
could
make
it
so
that
our
transitive
packages
is
safe
and
secure.
B
B
A
In
detail
in
the
reach
meeting,
because
it
relates
to
the
work
we've
been
doing
on
the
modules
themes
in
layout
pages
for
backup
CMS
at
work,
but
essentially
the
takeaway
is
that
the
search
module?
That's
in
court
is
super
wonky
and
there's
very
little
of
contribs.
It
checks
thousand
kinship
projects
and
Drupal,
and
none
of
them
implemented
her
cert
rankings
or
hook,
ranking
or
whatever.
It
is
so
I
think
it's
sort
of
low-hanging
fruit
for
getting
a
rewrite.
A
I
think
we
would
break
very
little
if
we
were
to
replace
the
existing
search
with
something
better
and
it
would
pretty
easy
to
add
just
new
API
functions
for
the
new
search
and
leave
the
old
one
market
is
deprecated,
so
I
have
a
core
patch
and
currently
that
fixes
search
so
that
titles
are
ranked
more
heavily
than
body,
and
that
does
have
an
API
change
in
it.
But
I
think
that
there's
a
whole
lot
more.
We
could
do
to
improve
that.
B
B
F
A
This
is
not
that
issue,
but
the
one
I
think
I
tagged
it
as
a
bug
fix.
It
might
have
a
milestone
on
it
neat,
but
just
the
one
to
rank
title
more
have
than
the
string
appearing
in
the
body
that
did
require
an
API
change,
because
I
had
to
pass
the
keyword
that
you
searched
on
into
the
function.
That
does
the
surgery
which
it
wasn't
there
before
so
I
added
a
parameter
to
hook,
ranking
doors
to
make
that
happen.
So
I
think
it's
an
API
Edition
right.
A
B
F
I
guess
I'm
just
asked:
there's
no
process
for
like
group,
this
I
think
what
is
the
next
priority,
it
seems
seems
to
me,
like
things,
get
added
to
the
agenda
just
by
somebody
getting
excited.
Is
that
correct
and
I
mean
you
know?
Could
there
be
a
more
strategic
thought
about
that
like
what?
What
do
we
think
there's
a
group?
We
should
really
focus
on
yeah.
A
Just
have
to
either
ask
for
access
to
edit
document
or
ask
someone
in
my
eyes
X
so
document
to
put
it
in.
We
can
talk
about
it
in
a
meeting
and
it
remains
on
the
agenda.
If
everybody
agrees,
that's
something
we
should
keep
talking
about
and
sometimes
it
gets
removed
from
the
agenda.
If
it's
like
well,
we've
talked
about
that
a
million
times
I,
don't
wanna,
keep
talking
about
it.
It's
not
making
any
progress,
it's
obviously
not
a
priority.
A
A
F
I
get
that,
but
anybody
can
make
a
bet
good,
that
sort
of
process
and
I
under
I
understand
the
reasons
for
this
always
requires
that
for
something
to
proceed
right,
that's
got
one
person,
that's
advocating
it
for
it
is
there
and
is
you
know
and
I?
This
goes
back
to
other
group
or
you
know
other
open-source
projects
as
well.
Is
there
any
merit
to
like
having
a
discussion,
but
as
a
group,
what
do
we
think
we
really
want
to
focus
on
for
the
next
issue?
You.
F
Maybe
you
know
like,
rather
than
just
waiting
for
somebody
to
add
something
for
us
to
say
strategically
like
what
is
what
is
the
gap
we
have
and
I
don't
mean
something
emerges
that
I
think
it's
really
important,
but
it's
just
none
of
our
none
of
us
are
listing
it
as
our
top
priority
and-
and
you
know,
but
if
we
decided
as
a
group
that
was
important,
then
people
would
get
behind
it.
I
don't
know
I'm
just
throwing
that
out.
There
I'm
sure
this
discussion.
A
F
A
Love
to
do
more
strategic
planning,
I
think
we've
been
very
sort
of
what
are
people
already
working
on
planning,
rather
than
what
do
we
need
kind
of
planning?
I,
don't
know
how
to
make
that
happen.
Do
you
have
any
recommendations
on
like
carbon
lending?
Having
like
a
dedicated
meeting
to
talk
about?
It
would
be
good,
like
this
meeting,
we're
very
much
talking
about
like
what
is
the
stuff
that's
already
going
on,
but
I
think
we'll
be
good
to
have
sort
of
a
separate
thing
where
it's
like.
A
Let's
not
look
at
what's
already
going
on.
Instead,
let's
look
at
what's
needed
and
and
talk
about
it
that
way,
I
think
that
would
be
there
and
it
might
be
good
to
do
that
meeting
like
right
after
release,
especially
if
we
don't
have
a
bunch
of
issues
when
you
talk
about
that
are
bug-fix
releases
feel
like
okay,
take
a
deep
breath.
Let's
like
look
at
the
future,
so
I.
F
Yeah
I
agree,
I've
been
thinking
that
these
meetings
are
very,
you
know,
agenda
driven
every
week,
it's
the
same,
and
it
might
be
good
at
least
once
every
released
like
throw
away
the
agenda,
and
you
just
say
hey
what
do
we
want
to
do
different
or
this
discipline
this
release?
Or
you
know
what
big
things
do
we
want
a
surface
that
part
being
surface
trigger
yeah?
You
know
at
least
once
every
release,
yeah.
A
I
think
that
the
problem
with
that
is
that
we
don't
get
as
many
people
in
the
outreach
meeting
and
I'm
not
sure
if
anyone
can't
like
everyone
who's
in
this
meeting
has
time
during
that
reach
meeting
to
join
into
that
conversation,
whereas
I
think
we
want.
We
want
feedback
from
all
the
people
who
are
working
on
poor
and
working
with
backdrop
to
weigh
in
on
that.
If.
C
A
Winding
yeah,
well,
we
could
do
is
Gregory
right,
like
we
could
have
a
meeting
during
outreach
meeting,
and
then
we
could
summarize
that
next
question
during
the
dev
meeting
and
make
sure
that
everybody
in
the
def
meeting
has
a
chance
to
weigh
in
on
it
too,
and
even
if
that
means
that
def
meeting
runs
a
little
long.
I
think
that
would
probably
still
be
good
makes
sense.
Okay,
so
we'll
try
that
we'll
try
after
the
next
release,
but
Tim
do
you
think
we
need
to
have
this
conversation
before
the
next
release?
No.
F
Not
necessarily
I
mean
I
I
may
be
for
outreach
purposes,
only,
not
necessarily
for
the
Deaf
stuff,
I,
wouldn't
mind
having
a
meeting
regarding
outreach
which
isn't
just
like
updating
us
on
which
we've
been
doing
yeah.
You
have
an
outreach
meeting
where
we
say
what
should
we
be?
What
are
we
not
doing?
What's
not
on
our
agenda
that
should
be
yeah.
A
B
Or
also
you
know,
there
are
a
lot
of
things
that
are
priorities
that
sorry
there
are
things
that
should
be
priorities
that
have
been
in
agendas
past,
but
when
a
lack
of
movement
on
them
was
just
making
us
repeat
ourselves,
we
took
them
off
the
agenda
right,
but
those
items
are
still
important
like
from
an
overall
project
direction,
but
there
just
wasn't
enough
enthusiasm
to
actually
push
them
forward.
Noting.
C
B
C
I'm
fed
up
with
many
issues.
What
I
usually
do
is
I
sort
the
the
issues
by
dates
like
that,
but
the
earliest
memory,
a
digitally.
Some
of
them
are
really
2.0
decisions
as
well
that
they
left
there
but
see
like
number
37,
though
we
got
rid
of
yeah,
you
like
to
take
sort
of
like
the
oldest
possible
issue
that
is
doable
for
one
of
the
techs
and
sort
of
like
murder,
porn
yeah
I,
like
that.
This
is
get
rid
of
the
small
digit
number
of
issues.
B
B
A
lot,
that's
basically
our
opportunity
to
quote
throw
away
the
agenda
is,
you
know,
make
a
new
one
at
the
beginning
of
each
release,
yeah
yeah,
which
actually
kind
of
effectively
we
do
kind
of
throw
away
the
agenda,
but
not
always
I
mean
when
stuff
gets
carried
over
from
release
to
release.
Then
it
stays
yes.
B
A
C
A
All
right
so
Nate
last
time
we
had
a
meeting,
we
had
two
things
were
discussing.
This
release
in
particular
seems
to
break
a
lot
of
things
more
than
any
previous
release
had,
and
so
we
thought
it
would
be
good
to
go
back
to
creating
the
preview
release
on
the
day
we
do
code
freeze
like
when
we're
done.
A
That
also
should
have
been
easy
to
identify
beforehand,
but
we
someone
missed
it
so
I
think
we
should
go
back
to
doing
the
preview
really
slow
on
code
free
stay,
and
then
we
also
Gregory
brought
up
the
idea
figuring
out.
We
couldn't
do
some
kind
of
visual
regression
testing,
and
maybe
we
should
do
some
research
to
see
if
any
of
the
tools
that
are
out
there
might
support
open
source
software
projects
and
give
us
a
free
account
and
see.
C
Really,
you
know
we
are
actually
using
a
software
in
the
agency
that
I
work
for
and
I
can
reach
out
to
the
guide.
That
is
providing
the
support
and
mention
if
you
would
be
interesting
to
provide
us
a
free
account
and
we
in
return,
but
of
like
do
the
same
thing
as
in
tag
board.
We
just
mention
it
as
a
form
of
advertising.
A
C
B
So
another
potential
option:
there
is
some
like
yeah
tugboat,
we're
using
four
demos
tugboat
as
that
functionality
as
well
that
it
can
automatically
post
to
a
pull
request
like
the
link
to
a
visual
dip.
Its
mechanism
is
that
it
creates
a
sandbox.
So
what
we're
using
is
NCI
for
right
now
to
make
our
demo
sandboxes
tugboats.
B
Primary
purpose
is
creating
sand
boxes
and
then
as
an
additional
functionality
of
them,
using
that
sandbox
to
do
the
visual
regression
testing,
which
could
actually
cause
some
problems
if
a
user
was
fast
enough
that
they
signed
into
the
demo
and
then
started
like
creating
content
or
modifying
it
prior
to
the
screenshots
being
taken,
but
I
think
it's
probably
not
not
much
of
an
issue
there
anyway.
So
that's
an
option
to
I
can
start
adding
more
providers.
We
could
pivot
some
of
our
existing
stuff
over
to
tugboat,
which
I
think
might
be
good.
B
C
C
That
said,
there's
this
html5
be
be
time
that
we
can
use
when
it
comes
to
certain
strings
that
need
to
maintain
punctuation
or
what
have
you
and
it
seems
to
work,
but
there's
no
I
support
at
all,
so
it
works
for
Chrome
and
Safari
and
all
modern
browsers,
but
it
won't
work
to
fix
things
there.
But
here
is
this
one:
again:
that's
35
26
30
fact:
yeah
I
was
fixing
some
RTL
issues
with
the
options
element
that
we've
added
like
it
was
missing.
Some
padding
the
add.
C
So,
if
there's
enough
room
for
the
whole
thing
to
fit
in
one
line,
the
problem
does
not
occur
when
things
start
wrapping
in
multiple
lines.
It's
some
weird
things
have
start
happening
with
whatever
might
be
considered
the
punctuation,
so
the
workaround
there
was
to
a
file
to
do
pull
requests.
Actually,
one
one
is
a
really
tiny
one.
It
just
goes
directly
to
the
problematic
places
with
with
the
help,
ticks
and
wraps
things
in
BD
tags,
and
it
solves
the
problem
and
the
other
one
is
a
more
sort
of
like,
as
I
say,
bold
pull
request.
B
Yep
yeah,
those
things
seem
like
they
could
easily
work.
I
mean
we
could
also,
you
know,
wrap
each
individual
HTML
tag
in
a
code
in
an
individual
code
tag
with
a
class
on
it
or
something
like
that
and
then
make
it
so
that
or
wrap
each
individual
tag
in
something,
and
then
you
CSS
to
make
it
so
that
it
as
white-space:nowrap
on
each
individual
tag
to
keep
it
all
together.
B
C
B
C
C
Okay,
the
issues
3385,
so
I
started
working
back
on
the
vendor
on
that
one
and
then
I
had
some
time
during
the
week,
because
I
just
I
was
looking
at
that
page
and
it
pissed
me
off
the
way
that
it
is
now
so
the
problem
there
is
this.
This
there's
a
pattern
that
we
use
a
UI
pattern
that
we
use
for
the
languages
page,
which
works
really
nice
when
things
need
to
be
enabled
or
disabled
and
at
the
same
time
one
of
them
has
to
be
a
default
which
works
very
nicely
for
the
languages.
C
So
I
try
to
work
that
I
did
go
enough
like
I.
Have
it
have
it
working
for
the
search
items,
but
there's
some
weird
validation
going
on
or
required
there
to
ensure
that
if,
if
a
thing
is
not
enabled,
it
cannot
be
set
as
the
default
and
if
it
is
set
as
the
default,
it
cannot
be
disabled,
which
seems
to
me
that
it
could
be
easily
done.
C
It
should
be
easily
done
using
States
like
if,
if
a
checkbox
is
ticked,
if
it's
a
text
box
is
ticked,
then
their
respective
radio
button
should
be
disabled
as
cannot
be
unset
from
being
the
default
or
something,
and
though,
but
my
point
is
that
I
does
not
work
as
expected
in
this
situation.
It
just
fails
miserably
so.
B
What
you
might
be
running
into
as
well
as
that,
if
a
form
element
is
disabled,
the
browser
will
actually
remove
that
fields,
value
from
the
submitted
post,
so
a
disabled
field.
It
basically
isn't
on
the
page
at
all.
As
far
as
the
browser
is
concerned
like
when
it
when
it
submits
the
form,
it
won't
include
the
value
of
any
disabled
fields
and
so
yeah.
C
I
haven't
noticed
that
what
I
have
noticed
is
that
on
such
forms,
the
statement
work
because
actually
switching
selecting
a
different
radio
button
does
not
remove
the
checked
thing
from
the
previous
and
does
not
add
the
text
to
the
current
one.
So
it
happens
visually.
But
when
you
check
at
the
same
time
the
code,
nothing
happens.
Oh.
C
My
dad
would
think
yeah
my
job
I
mentioned
this
before
my
javascript
is
really
laughable.
So
what
am
I
might
do
is
just
push
the
code
that
I
have
on
the
pool
request
there,
the
weirdness
and
then
ask
someone
to
just
take
a
look
at
it
and
see
if
it's
the
same
issue.
The
same
issue
exists
with
with
the
languages
the
language
listing
page,
where
you
set
the
default.
It's
just
that
if
they
have
some
really
weird
validation
going
on
there
and
if
states
does
not
work
properly,
then
it
explains
why
it's
there
yeah.
B
C
Point
was
that,
just
as
a
sort
of
like
junior
developer
person's
trying
to
tweak
things,
it
is
a
pain
point
with
that
specific
UI
pattern
that
we
have
that
I
cannot
easily
just
things
into
a
table
and
have
them
work
with
States
when
they
should,
in
theory,
work
at
the
same
that
way
that
state
works
for
every
other
element.
Just
not
you
yet
yeah.
B
Okay,
I
actually
thought
that
we
and
broadcast,
because
now
this
is
not
very
a
broadcast
worthy
material.
Okay,
let's
let's
go
ahead
and
at
least
say
thank
you
everybody
for
joining
the
meeting
today.
If
you
guys
would
like
to
hang
out-
and
after
talking,
we
can
do
that
as
well,
but
yeah
thanks
you're
ready
for
joining
you
guys
on
the
Internet.