►
From YouTube: Backdrop Weekly - June 27th
Description
Today’s development agenda: http://bit.ly/2RnvccI
A
All
right
we're
on
our.
It
is
Thursday
June
27th,
and
this
is
the
meeting
to
check
in
on
an
active
developer
tasks
for
backup
CMS,
starting
with
an
announcement
of
updates
of
contributed
projects.
We've
had
a
ton
of
new
modules.
This
week
filled
wrappers
unique
field
menu,
node
views.
When
you
know
the
API
and
easy
breadcrumbs
all
had
official
releases
this
week,
so
I
don't
know
it's
been
busy
somebody's
been
busy,
it's
great,
so
yeah,
that's
great
okay
time.
For
word,
it
looks
like
there's
an
announcement
here
about
vector
CMS
being
available
on
packages.
B
A
B
B
Uwp
and
I
got
us
some
better
multi
site
support.
That's
great
I
was
working
on
testing
infrastructure,
so
I
have
some
basic
sanity
checks
in
there,
where
it
can
chest
just
for
exit
code,
zeros
of
a
lot
of
the
Drucker
commands
and
likewise
test
them
on
a
Drupal
install
to
make
sure
we
didn't
break
things
over
there
and
jackpot
has
a
PR
for
dress
user
created
and
we
could
use
a
works
for
me
review
there,
but
I
think
it's
looking
pretty
good
and
I've
included
in
the
tests.
A
B
C
C
C
Working
through
getting
the
tests
validate
their
general
like
work
this
week,
getting
the
tests
ported
from
the
triple
version
of
the
same
issue,
and
it
looks
like
we're
unblocked
on
that
now
that
the
testament
passing
but
some
feedback
from
directories
and
it's
a
gymnast
it's
going
on
there
so
once
that
set
of
tests
is
passing,
I
can
go
and
that
might
be
valid
enough
for
us
to
make
a
and
it
releases
once
that
goes
through.
There's
also
been
a
number
of
other
smaller
bug
fixes
and
changes
going
through
as
well.
C
Thanks
to
you
know,
merges
and
changes
that
have
been
going
on
I'll,
say
it
on
the
record
to
that
last
week
asked
for
basically
a
little
more
help,
but
more
King,
stuff
and
I
got
it
so
yeah.
Thank
you
core,
committers
for
for
marching
and
and
putting
stuff
in
all
week.
Long.
So
that's
been
awesome.
One.
D
Thing
to
mention
before
we
move
to
the
next
to
the
minor
release
is
that
herb
made
a
call
for
like
we
have
around
400
tickets,
they're
back
I
just
label
those
bags.
So
maybe
we
should
focus
on
those
as
well.
I
know
that
we
get
over
excited
with
the
new
features
and
we
mostly
work
on
boys
but
yeah
and
currently
they're,
not
like
other
than
that.
D
E
C
Yeah,
usually
the
the
ones
that
are
quote
important
are
usually
moved
into.
The
next
bug
fix
release,
so
the
one
so
tech,
113
3,
for
example,
and
they're,
currently
44
open
issues
that
are
almost
entirely
bugs
that
are
in
that
tank.
And
so
we
could
continue
that,
like
adding
more
items
in
there,
although
I
think
a
good
area
of
focus
would
be
concentrating
on
the
ones
that
are
already
10,
2013
3
those
44
issues
and
and
and
I'm
working
through
those
they're
all
in
I'm.
A
D
Good
indicator,
although
not
perfect
at
the
point
to
see
what's
important,
is
how
many
comments
are
in
it's
bad
thing,
because
it
might
be
I
personally
even
have
filed
some
bugs,
like
maybe
2016
and
I,
haven't
been
able
to
reproduce
them
ever
since
or
not
able
to
reproduce
them
consistently
or
find
a
pattern
for
them.
So
I'm
just
waiting
for
other
people,
you
just
come
and
say:
yeah
I
just
had
that
too.
C
C
There
are
seven
that
have
works
for
me,
labor
lemon
and
our
ETB
see
there
are
three
and
so
yeah,
there's
a
good
number
there.
That's
all
that
they're
really
needing
is
review,
or
at
least
up
until
they
get
it
with
you,
and
maybe
after
that
we
would
find
more
issues
there.
Twenty
two
of
them.
The
poll
requests,
need
work.
So
a
lot.
A
lot
of
those
have
already
received
feedback
and
just
need
to
be
updated
to
include
the
interest
feedback.
It
might
actually
be
easier
to
start
what
the
needs
work.
C
But
yes,
we
can
add
more
issues
into
that.
If
we
want
triage,
more
important
issues
or
any
issue
that
needs
to
be
surfaced,
yeah
add
milestone
candidate
bug
fix.
You
know,
saying:
I
think
this
is
a
high
priority
issue
and
then,
if
it
gets
second
it
then
then
we
move
it
into
the
into
the
113th
remaster.
Okay,.
C
D
But
like
when
we
started
that
the
process
was
compiler
serious,
so
all
targeted
for
the
next
bug-fix,
but
that
was
unmanageable,
so
I
need
it
sort
of
like
have
a
smaller
set
and
the
miles
has
been
used
and
I
find
that
a
good
what
you
wanted
a
good
move,
but
if
something
is
important
enough,
it
will
eventually
get
attention.
Someone
will
look
implying
and
the
the
milestone
label
will
be
added
anyway.
So
it's
not
that
we're
gonna
miss
anything
important.
D
C
E
D
D
E
Am
interested
in
the
process
here
in
less
than
that
specific
one,
and
so
one
good
reason
to
make
that
to
give
it
the
milestone
candidate
is
that
it's
obviously
really
important
right.
It's
it's
hurting
people's
uses.
This
one
is
maybe
not
I,
wouldn't
consider
important
in
that
sense,
but
on
the
other
hand
it
might
be
easy
and
it's
very
visible.
Yeah.
A
C
Yeah
process
is
why
this
is
exactly
why
we
have
miles
from
Canada
in
the
first
place
and
master
on
Canada
is
a
personal
opinion.
I
think
that
this
is
important.
So
if
you
think
it's
important,
that's
all
that
you
need,
like
we
market
miles
from
candidate,
because
the
confirmation
and
then
moving
into
the
milestone
is
when
other
people
am
saying.
I
also
think
this
is
important,
so
you
know
completely
free
rein
and
are
encouraged
to
mark
things
miles
when
candidate.
C
When
you
personally
feel
it's
important
regardless
of
anybody
else,
and
then
you
get
the
confirmation
or
well
have
a
discussion,
possibly
usually
it's
just
me
too.
You
know
we
haven't
even
had
had
it
happen.
Frequently
people
are
like
no,
this
isn't
important,
but
it
happened
frequently,
but
it
does
happen
like.
C
Thank
you,
Tim,
okay,
so
114
114
is
the
next
minor
version
of
backdrop
that
will
include
new
features,
its
September
or
it
will
be
released,
September
15th
2019.
It
still
seems
far
away
like
there's
so
much
summer.
Between
now
and
then
it's
just
wonderful
I
have
been
noticing
seems
people
actually
have
more
time
recently
like
there's
a
lot
of
stuff.
That's
going
on.
C
It's
been
wonderful!
So
let's
see
the
first
item
that
we've
got
oh
and
the
feature
freeze,
of
course,
would
be
September
roughly
two
weeks
before
the
release.
So
the
first
item
that
we've
got
on
the
docket
here
that
has
been
seeing
a
lot
of
activity
this
week
and
I
just
wanted
to
mention
it
is
adding
a
composer
JSON
vinyl
to
core
itself.
C
D
Quick
summary,
a
quick
summary
of
that
is
that
there's
some
resistance
and
with
legitimate
reasons
why
we
shouldn't
have
had
a
composer
dot
JSON
file
as
it
is,
but
the
alternatives
that
were
proposed
was
to
add
something
like
along
the
lines
of
default,
dot,
settings
or
something
we
could.
We
could
add
something
that
denotes
it
as
optional
as
an
optional,
optional,
Dutch,
composer,
notation
and
I
think
that
most
people
are
not.
We.
D
A
Also,
I
made
a
recommendation
that
we
could
include
it
in
the
get
the
contour
movement
by
the
packaging
script,
but
that
way,
the
clients
of
people
who
are
likely
to
download
the
tarball
wouldn't
be
scared
away
by
a
composer
file.
But
the
kinds
of
people
who
are
likely
to
do
a
git
clone
would
have
it
so
separate
that
presence
of
the
file
by
the
type
of
person
who's
retrieving
it
yep.
A
There's
just
a
lot
of
options
in
there
like
how
we
could
approach
that
and
I
think
we
just
need
much
more
of
people
weigh
in
I.
Think
for
now.
Jack
your
solution
is
great,
but
I
think
we
should
still
talk
about
it
so
see
if
there's
a
better
way
to
handle
it
and
I
think
that's
type
of
114,
because
we
wanted
to
have
people
talk
about
it
until
the
next
release,
not
urgent,
but
yeah.
C
This
work
has
been
led
by
John
Franklin
and
it's
on
my
plate.
Basically,
to
get
project
module
working
with
the
code
that
John
has
assembled
for
us.
I
haven't
made
progress
on
this
issue
in
the
past
two
weeks.
Actually,
but
I
am
hoping
to
continue
to
work
on
project
module.
First,
get
back
drop,
CMS,
org,
signing
and
updating.
C
Projects
archives
like
as
they've,
been
created,
get
the
digital
signatures
into
projects
and
then
we'll
work
on
the
corresponding
part
to
make
backdrop
itself
actually
start
respecting
those
signatures,
so
I
don't
have
any
other
updates
there.
Unfortunately,
so
I'll
just
continue
on
field
about
files.
This
is
your
issue.
Jim
26:32.
A
Haven't
made
any
progress
on
this
since
last
week,
but
where
I
was
last
week,
is
that
I
started
moving
all
of
the
file
display
settings
into
a
widget
II
thing
on
the
fields
display
settings,
but
I
ran
into
an
issue
that
I
was
testing
when
I
tried
to
upload
a
file
using
the
individual
file.
Upload
form
and
I
got
a
fatal,
so
I'm
currently
trying
to
figure
out
the
file
upload
fatal
problem
first,
but
making
progress
on
the
UI
stuff
cool.
D
So
there
hasn't
been
any
movement
in
that
issue
for,
like
two
weeks
now,
and
it's
just
waiting
for
review
Jenkins
from
feedback
just
to
change
the
link
to
the
documentation
to
go
to
API
and
done
that.
So
I
just
need
people
to
review
it.
So
look
the
way
that
this
has
been
implemented
is
that
it's
less
intrusive
than
d8
cause
in.
We
warned
people
about
not
having
specified
trusted
hosts
and
we
support
setting
them,
but
we
do
not
enforce
them.
D
There's
follow-up
for
that
to
allow
editing
those
hosts
from
the
user
interface
but
I
can
come
follow.
This
is
the
basic
basic
implementation
of
Ovid
in
the
same
space
before
and
the
user
interface
facing
parties,
the
respective
entry
in
the
status
page
beside
status,
Bates
yep,
cool
people
that
wanna
review
it
welcome.
C
D
There
was
some
feedback
there
about
how
to
move
forward,
but
there
are
some
things
that
are
unclear
he's
still
working
on
it.
We
still
need
reviews.
I,
figured
I,
found
out
some
timing
issues
here
and
there
and
I'm
currently
working
on
a
full
request
to
just
automatically
generate
icons,
because
it's
one
of
the
things
that
he
asked
how
to
move
forward
with
I
think
that
was
a
proposal
by
exam
that
we
need
a
different
icon
and
half
way
in
generating
automatic
the
icons
with
the
respective
regions.
D
C
D
C
D
Cool
yeah
and
and
I
thought
that
maybe
the
the
ones
that
ship
with
core
we
can
later
on
as
a
follow-up,
are
they
the
ability
to
clone
them,
and
then
they
become
so
like
configurable?
We
make
clones
of
them
and
then
people
can
add
rows
and
things
on
default.
Examples,
there's
more
ideas
after
that
I.
A
A
A
A
C
C
E
Think
it's
almost
done.
We
it.
The
story
was
after
after
the
we've
got
dashboard
into
a
court
in
one
question:
1.13
wasn't
it
then
a
following
issue
was
to
include
some
sort
of
a
news
block
and
I
had
been
noticing.
That
is
every
time
I
have
walked
into
that
dashboard.
I
was
kind
of
missing
that
block.
It's
like
this
would
be
a
really
good
for
sort
of
outreach
and
communication
with
users
the
ticket
existed,
so
I
just
went
ahead
and
commented
on
it.
E
I
was
thinking
about
like
is
this
worthy
of
advocating
for
or
something
and
as
soon
as
I
commented
on
it,
there
was
a
whole
flurry
of
activity
and
within
a
day
or
two,
a
pull
request,
and
it
was
like.
Okay
do
I
even
need
to
advocate
for
it,
because
it's
it's
moving
faster
than
I
can
keep
up
with,
but
I
went
ahead
and
put
my
name
on
it.
We
added
it
as
a
milestone.
Candidate
I
did
I,
went
ahead
and
did
an
issue
summary
because
it's
getting
to
be
pretty
long
issue,
there's
about
I.
E
You
know,
keep
this
very
specific
to
the
tasks
we
set
out
and
if
there
was
interested
in
a
flexible,
JSON
block,
I
created
a
new
issue
for
that
where
it
could
be
discussed.
Although
I
think
the
the
consensus
seems
to
be
that
that's
probably
a
control
project,
so
then
I
just
want
to
mention.
I
went
ahead
and
did
because
I'd
like
feedback
on
this
I
went
ahead
and
created
a
contributor
place
for
a
module.
It
adds
some
blocks
to
the
net,
dashboard
and
I.
E
Don't
know
if
that's
normally
the
way
we
would
do
things
I
then
actually
did
go
ahead
and
create
some
code
for
a
simple
dashboard
block
that
just
like
has
some
useful
links
in
it.
But
I
would
like
to
get
some
other
dashboard
blocks
in
that
control,
so
anyways
anything
that
people
feel
like
they
would
have
liked
to
seen
in
the
dashboard
but
hasn't
got
there.
I
think
we
could
test
it
in
this
control
and
then
maybe
bring
it
to
court
later
anyway.
The
one
other
big
holdup
on
this
was
it.
E
We
can't
really
create
the
block
unless
we
have
a
feed
right
No.
So
the
other
issue
that
was
created,
I
think
Jen
went
ahead
and
created
an
issue
for
creating
a
feed
from
bat-crap
org
back
crack's,
ms
org
and
and
maybe
Jeff.
Could
you
update
me
I
mean?
Have
you
basically
created
that
and
we're
just
waiting
that
to
get
approved
yeah.
A
E
D
D
E
C
Well,
Tim
you're
doing
it
you're,
advocating
and
I
think
this
is
a
perfect
example
of
how
a
lot
of
times
people
just
need,
encouragement
and
direct
and
then
like
getting
that
fulfillment
like
that
is
enough
of
a
drive
to
like
oh
there's,
somebody
that's
actually
going
to
look
at
my
work.
If
I
do
it
and
I
think
that
everybody
finds
that
to
be
very
encouraging
and
a
purpose
for
for
contributing,
so
there
we
go
yay.
This
is
great.
C
C
C
Don't
think
that
we've
got
anything
here
to
discuss
really
it
just
kind
of
like
to
be
determined
like
if
there's
anything
that
we'd
like
to
add,
then
we
can
discuss
it
here.
If
you
guys
have
anything
that
seems
like
it
would
be
115
like.
Should
we
be
talking
about
anything
at
this
point,
I
think
that
as.
D
A
Kind
of
want
to
advocate
for
reference,
because
I've
been
doing
a
bunch
of
work
on
that
for
a
couple
of
my
client
sites,
but
I'm
more
motivated
to
work
on
files
stuff
for
courts.
I
mean
that's
more
urgent,
so
I
have
a
idea
of
putting
that
on
that
list,
but
I'm
not
ready
to
do
it.
Yet
you
want
to
get
Bo
closer
Fort,
Smith,
yeah.
C
E
Me
use
this
opportunity,
I,
don't
know
if
I've
mentioned
it
before
something
I've
been
thinking
about
advocating
for
that
I
know.
I
couldn't
do
myself,
but
I
understand
it
was
the
backup
in
my
grade
in
court
and
but
what
I'm
curious
one.
Is
that
a
good
one
and
two?
Is
it?
How
hard
is
it
going
to
be?
Is
that
going
to
be
a
really
huge
project,
or
is
that
manageable?
You
think
so
I'd
like
be
back
on
that
not
necessarily
now,
but
that.
D
D
A
D
Think
that
are
done,
I
think
things
that
there
comes
to
it.
I
think
that
the
consensus
was
that
we
get
a
very
minimal
thing
of
the
requirement
for
core
would
be
because
there's
automated
core
updates.
Now
we
need
a
way
for
people
to
roll
back.
So
it's
not
like
a
sword
like
a
checkbox
markup
things
before
you
update
and
then
that
somebody
that
says
things
will
went
wrong,
restore
things
for
them
that.
A
A
And
I
think
if
you
need
sits
him
like
if
you're
advocating
for
this
issue-
and
you
feel
like
you-
need
that
one
conversation
like
bring
it
like
this
and
a
meeting
is
good
or
even
calling
on
whoever
it
is
that
has
thoughts
on
it
to
chat
and
get
her
at
a
specific
time.
You,
okay,
let's
hash
this
out
together,
we
want
to
do.
C
All
right,
we've
got
one
item
in
the
general
discussion
and
open
Q&A,
which
has
an
interesting
I,
don't
know,
but
this
in
here,
but
as
a
question
can
we
bump
the
character
limit
per
line
to
124
to
X,
so
we
currently
at
the
coding
standards,
say
at
80
characters
you
indent
and
go
down
to
the
next
line
whenever
possible
way.
Out
of
this
question,
zip.
B
Import,
it's
just
like
that.
Bothers
me
a
lot,
it's
kind
of
hard
to
meet
that
eighty
kick
it's
not
it's
not
hard,
but
when
it's,
but
what
it's
there
it
can
be
hard
when
you
get
to
the
80
characters.
Thank
you,
I
think,
like
Symphony
and
stuff
does
120
a
lot
of
JavaScript
stuff
does
120.
They
would
make
my
life
easier.
That's.
A
Interesting
because
any
characters
is
about
the
length
a
human
is
capable
capable
of
reading
before
their
eyes
get
uncomfortable.
So
this
is
like
a
number
of
characters
that
people
strike
when
you're
writing
content,
even
though
your
screen
is
really
wide,
you
never
want
the
content
to
get
more
than
80
characters,
but
I
wonder
if,
like
developers,
come
train
themselves
to
read
differently
than
human
beings
as
a
general
sentence,
and
so
that's
why
these
languages
they're
like
right.
B
A
I
just
feel
like
I,
don't
so
Nate
has
some
really
good
ideas
about
like
how
to
make
like
I've
seen
some
stuff
fit.
That
I
think
also
makes
it
make
more
sense
as
a
human,
when
you
read
it
like,
if
you
turn
eat
chips
even
into
a
variable
and
like
the
variable
says
what
the
thing
is,
then
it
makes
more
sense
to
read
as
a
human,
so
I
would
wonder
like
like.
It
would
be
good
to
see
some
specific
examples
of
things
that
don't
fit
like
string.
D
It
seems
weird,
even
the
explanation
that
you
just
presented.
I
knew
that
for
my
fondant
point
that
you
know
you
need
to
keep
the
width
up
aids
at
a
specific
sort
of
like
pixels
width,
but
I
always
thought
that
historically,
these
80
80
character
limit
was
because
that
was
the
size
of
the
screen
like
DOS
command
line.
Whatever
in
like
back
in
the
days
and
I
thought
that
maybe
this
was
a
carryover
from
like
the
olden
times.
Yeah.
A
There's
also
that,
where,
like
people
use
only
able
to
be
able
to
see
how
many
characters
in
their
screen
but
I
don't
know
like
I,
don't
know
where
that
like,
where
one
becomes
the
other
like
where
it's
like
I,
don't
know
if
it's
better
to
like
show
more
characters
per
line,
or
maybe
it's
like
this
is
an
interesting
conversation.
I
would
love
to
access
that
yeah.
C
Because
there's
a
lot
of
different
viewpoints
and
values
here
as
well
like
I,
have
to
add
my
two
cents
here
like
like
having
short
having
longer
lines,
means
that
there's
more
code
and
makes
it
so
whether
you
change
your
modify,
that
line
your
it's
harder
to
parse
for
like
a
core
committers
like
you're
Jeff
for
myself
to
like
so
what
that
line
is
actually
doing,
and
it's
also
more
likely
to
be
changed.
If
one
line
is
doing
more,
then
that
means
it's.
You
know
like.
C
A
D
D
There
are
cases
even
in
core,
where
we
have
I,
don't
know
properties
in
arrays
where
people
have
aligned
vertically
the
the
equal
greater
than
sign
just
to
make
that
one,
readable
and
I
can
see.
I
can
see
the
point
that
it
does
make
it
more
readable,
but
it
is
against
the
the
agreed-upon
coding
standards
so
either
need
to
change
the
coding
standards.
If
that's
decided
or
just
change
the
places
in
core
where
they
violate
that
yeah.
C
B
C
D
A
B
C
C
D
A
good
idea,
but
I
would
also
like
to
point
that
and
the
way
that
I've
seen
this
work
internally.
The
agency
that
I
work
for
the
lien
thing
might
be
a
different
test.
So
we
may
have
the
PHP
tests
passing
and
then
ignoring
those,
but
slowly
fixing
all
the
tests,
but
yeah
I
know
it
would
be
a
bit
noisy
in
the
queue
in
the
requesting.
I
understand
that
as
well
look,
but
the
point
is
that
maybe
it's
also
dangerous
to
just
have
a
whole
I.
Don't
know
huge
branch
that
that
we
work
on
the
linting.
C
Yeah
and
then
then,
going
back
to
the
original
question,
I
think.
Maybe
we
could
have
enforced
limit
of
120
characters
like
the
linter
would
actually
yell
at
you
like
or
fail.
If
you
went
over
120
characters,
but
our
coding
standard
recommendation
would
still
be
80,
possibly
some
kind
of
compromise
like
that,
where
we
would
actually
have
a
hard
limit
that
what
is
only
that
soft
word
that
was,
like
you
know,
subjective
we.
C
C
B
D
And
I've
seen
I've
seen
different
implementations
in
translated
strings.
Some
people
choose
to
have
multiple
sort
of
like
concatenating
sentences
in
a
variable
and
then
doing
the
deeds
per
line.
I
guess
or
things
like
that
or
adding
slash
ends
or
splitting
paragraphs
like
separate
paragraphs
and
separate
D
functions
being
the
variable
and
then
concatenating
all
these,
so
I've
seen
different
things
being
done
so.
C
I'm
not
quite
sure
where
to
go
with
this
right
now
like
we
can
open
an
issue
to
kind
of
discuss
where
we
want
to
be,
but
because
right
now
we
don't
have
any
wenting
it
any
decision
we
make
would
really
just
be
kind
of
updating
the
coding
standards
page
and
saying,
like
you're,
really
not
allowed
to
have
characters
over
120
characters,
so
that
would
be
valuable
as
opposed
to
to
establish
an
official
standard
and
then
update
our
coding
standards
page
around
120
characters
versus
80
characters.
I
think
a
discussion
around
that
would
be
valuable,
yeah.
E
A
D
Don't
feel
it
has
to
be
a
2
dot,
X
coz,
2
dot
X
is
reserved
for
divergences.
Only
a
code-breaking,
but
it
could
be
just
colleague
started
changing,
so
the
actual
code
would
still
make
it
remain
the
same,
so
it
can
be
done
in
one
vertex.
It
will
just
take
along
a
lot
time.
It
would
be
a
similar
situation
to
the
user
experience
tasks
that
we
have.
We
cannot
fix
everything
at
once,
so
we
have
smaller
tasks.
Maybe
we'll
do
that.
D
I,
don't
know
the
dot
module
files
first
and
then
project
or
per
module,
Inc
or
or
per
folder
or
per
file.
It
will
just
it's
unmanageable
if
we
try
to
do
all
at
once.
Unless,
as
I
said,
we
we
create
a
separate
branch,
but
then
people
need
to
work
on
that
Branson
yeah
and
we
need
to
keep
it
up-to-date.
D
A
What
I've
secretly
been
doing
with
like
removing
the
blank
space
at
the
top
of
every
file
I've
been
doing
CB
s
line
so
every
time
I
edit
a
file
and
I,
see
it
there
I
take
it
out
and
talk
about
atlona's
like
what
are
you
doing
and
I'm
like?
Well,
it
doesn't
make
sense
to
do
all
the
court
once
the
like
any
time,
I
edit,
if
I
always
see
a
take
it
out
so
I
think
like
that
kind
of
works,
but
we
also
don't
have.
A
D
Right,
I
kind
of
secretly
do
that
with
my
pull
request
or
you
might
see
a
dot
from
the
doc
look
above.
What
I'm
working
in
is
just
I
saw
it.
It
was
annoying
I'll
still
do
it.
It's
not
related.
It's
not
related
to
the
thing,
but
it
just
annoys
me
so
I
just
fix
it.
It's
harmless
especially
comments
in
Dropbox
but
yeah.
The
point
is
that
if
we
do
that
consistently
with
each
pull
request
yeah,
what
was
that
a?
What
did
you
say?
Was
it
a
grant?
Grant
PHP
PHP.
C
C
C
And
actually
I
think
about
it.
Of
course
it
wouldn't
matter
for
core
itself,
because
you
wouldn't
be
using
composer
to
get
the
poll
request.
Changes
you'd
be
syndicate
repository
that
includes
the
branch
and
everything
so
yes,
nevermind,
not
relevant,
let's
see
and
regarding
the
Travis
file,
also
go
with
call
out
to
issue
number
37
in
the
project:
module
queue
that
I
filed
a
about
a
month
ago
that
that
is
the
issue
for
adding
the
ability
to
exclude
certain
files
from
the
packager.
C
So
that
would
apply
both
to
composer
and
like
any
other
CI
tools
that
we
build
into
core
like
Travis
or
whatever,
I,
also
just
purely
advocated
or
wanted
to
advocate
for
that
just
because
right
now,
I'm
seeing
what
hours
NCI
file
is
doing
is
really
difficult
because
that
lives
like
how's
NCI
works.
The
file
is
on
backdrop,
CMS
org,
instead
of
in
the
repository
and
I,
think
that
we
should
move
it
into
the
repository
so
that
we
can
see
what
the
heck
it's
doing
and
then
exclude
it
from
the
package
er
so
yeah
that.
D
D
C
All
right
anything
else
that
we
should
discuss
we're
kind
of
running
long
on
this
meeting.
Okay,
okay,
all
right!
Well!
Thank
you,
everybody
for
joining
the
meeting.
As
always,
and
thank
you
for
all
of
the
great
work
this
past,
where
you
can
contribute
in
core
and
documentation
and
in
community
or
yeah
a
lot
of
really
great
things.
So,
thanks
again,
everyone
we'll
see
you
guys
next
week
and
on
the
Internet.
Okay.