►
From YouTube: Backdrop weekly 8/27
Description
Weekly check-in on development and infrastructure tasks for BackdropCMS.
B
A
A
status
of
backup,
so
general
announcements,
we
do
still
have
phpstorm
licenses
for
backdrop,
contributors,
some
email
to
info
backdrop,
CMS.
If
you
want
one
of
those,
we
have
another
announcement
this
week,
which
is
kind
of
exciting,
and
that's
that
we've
been
contacted
by
the
organizers
of
the
drupalcamp
Utah
I'm,
which
will
be
happening
in
February
of
2016
and
they're,
specifically
looking
for
people
to
come
and
talk
about
backdrop,
so
there
are
some
great
benefits
about
this
camp.
In
particular,
you
thought
in
February
is
excellent,
see
territory.
A
So
if
anyone
is
an
avid
skier
snow
blower,
but
that
can
be
kind
of
a
fun
vacation
to
take.
If
you
wanted
to
use,
they
also
have
grants
for
presenters.
So
you
can
get
up
to
five
hundred
dollars
to
offset
your
travel
costs
if
you're
interested
in
presenting
there
and
if
you
work
for
a
company
that
sends
you
they're
happy
to
list
that
company
as
a
sponsor
on
the
camp
website.
So
if
anyone
wants
to
work
any
of
those
angles
to
try
and
get
to
Utah,
they
would
love
to
have
backdrop.
A
People
come
and
talk
about
backdrop.
So
that's
on
the
backdrop.
Events,
calendar
in
February
and
funny
one
wants
to
think
about
plans
for
2016
that'd
be
a
good
place
to
start
all
right.
We
don't
have
any
updates
from
the
PMC
this
week,
so
we'll
go
right
into
community
growth
Nate.
Do
you
want
to
talk
a
little
bit
about?
What's
happened
since
last
week,
yeah.
B
So,
let's
see
our
total
contributors
is
38.
No
new
member.
Since
last
week,
I
said
every
week,
if
you're
interested
in
porting
a
module
backdrop,
we'd
love
to
have
it
in
the
King
trib
group.
That's
where
we
put
all
of
our
modules
and
right
now
it
is
a
requirement
that
you
put
to
your
module
in
that
group.
If
it's
going
to
be
listed
on
backdrop,
CMS
org,
which
we'll
talk
about
later,
but
we
have
104
to
total
projects,
including
themes,
layouts
and
modules.
B
One
new
project
since
last
week
and
around
sixty
two
projects
with
official
releases
that
have
been
synchronized
with
backdrop,
CMS
Borg,
so
a
little
a
little
slow
on
the
growth
in
the
past
couple
weeks,
but
we're
hoping
that
that'll
pick
up.
We
still
have
like
a
tremendous
number
of
modules
and
I
think
the
upcoming
release
and
September's
going
to
be
a
great
boon
for
us
with
all
the
new
features
and
functionality.
It
is
going
to
include
so
still
looking
great
overall,
hey.
B
B
Okay,
yes,
so
yeah
lots
of
great
stuff
happened
this
week.
Actually,
as
far
as
backdrop
CMS
org
goes,
we
did
a
bunch
of
work
on
project
usage
this
week,
trying
to
get
that
accruing
numbers.
We've
been
collecting
raw
usage
information
from
all
of
the
sites
that
have
been
out
there
that
have
installed
backdrop,
but
they
haven't
been
aggregating
correctly
and
we
set
up
the
cron
job
to
start
aggregating.
B
But
it's
it's
been
a
little
bit
on
the
fritz,
so
the
original
numbers
were
too
low
based
on
the
raw
numbers
that
were
coming
in
and
then
and
then
the
most
recent
week.
It
said
that
there
were
no
sites
out
there,
which
is
totally
incorrect.
So
it's
it's.
It's
a
little
bit
funny
we're
going
to
need
to
work.
The
numbers
work
out
the
statistics
on
generating
those
numbers
before
we
publicly
make
those
accessible,
but
they
are
there
for
administrators,
can
see
usage
statistics
on
backup,
CMS
org,
but
they're
all
they're,
all
wonky.
B
Let's
see
a
project
browser
a
project
browser
made
some
nice
progress.
This
week
we
set
up
a
project,
stop
backdrop
CMS
org,
which
is
going
to
be
a
sub
domain
that,
if
necessary,
we
could
put
a
CDN
in
front
of
or
something
like
that
to
make
it
so
that
it
could
handle
the
requests
that
come
in.
From
all
the
backdrop,
sites
that
are
out
there
project
browser
makes
it
so
that
you
can
install
a
module
or
theme
from
within
the
UI
of
backdrop
without
ever
leaving
your
website.
B
B
Dark,
Wellmont
and
I
have
been
going
back
and
forth
on
that.
A
little
bit
there's
some
issue
that
page
ring
isn't
working
like
it:
fish
more
than
10
results.
It's
showing
you
more
than
10
when
really
it
should
be
splitting
them
up
into
pages.
So
we
have
a
little
bit
of
implementation
that
we're
working
out,
but
but
it's
coming
along,
it's
going
to
need
that
it
all
actually
works
to
the
point
that
you
can
browse
modules
from
your
site
and
install
them,
so
we're
just
having
some
issues
that
deal
with
scalability.
B
A
So
I
think
I
only
did
a
little
bit
of
work
on
that
since
last
week.
I
think
I
know
what
we
need
to
do
to
make
it
work,
but
I
haven't
actually
gotten
working,
so
maybe
I'll
spend
some
more
time
on
that
today.
I
would
really
like
to
get
very
least
like
the
rush
dl
command
working,
which
can
be
kind
of
tricky
because
those
are
gonna
have
people
and
stuff
from
github.
A
But
we'll
see
that's
my
golfer
today,
okay,
moving
on
big
news
on
the
flagship
website,
which
is
a
next
time
on
our
agenda
here,
we
finally
launched
the
modules
things
and
layouts
pages,
so
we
got
designs
from
Darius.
We
got
them
implemented
by
Wes.
They
sat
out
there
for
about
a
week,
letting
us
kind
of
look
at
them
employee
with
them
and
see
if
they
were
working.
A
A
I
think
people
will
start
to
be
able
to
find
modules
via
the
backdrop
website
now,
instead
of
through
github,
which
is
really
good
and
I'm,
hoping
that
this
will
also
encourage
people
who
have
ported
modules
and
left
them
and
get
hype
repositories
to
make
official
releases
so
that
they
will
show
up
now
on
the
public
website.
So
I
think
we're
looking
pretty
good
in
terms
of
getting
that
happen.
A
Super
excited
that
we
got
all
that
done
and
we'll
just
keep
working
on
the
last
few
sets
of
things
lesson
I
were
talking
earlier
today
in
the
design
call
about
setting
up
a
issue
queue
for
the
backdrop,
CM
esta
org
site
of
all
of
the
tasks
that
are
yet
to
be
done
on
these
pages.
So
things
like
you
know,
we're
missing
an
issue
tracker
or
we're
missing
a
download
counter
or
whatever
it
is.
A
We
should
we
should
get
those
in
tickets
so
that
we
can
get
the
development
done
or,
and
some
Nate
was
asking
if
we
should
maybe
remove
like
themes
and
layouts
until
we
have
themes
and
layouts
but
I
think
that
seeing
them
there
will
encourage
people
who
have
themes
and
layouts
to
make
releases
of
them.
So
I
don't
know
how
do
people
feel
about
that?
Do
you
think
we
should
take
down
the
pages
or
at
least
remove
them
from
primary
navigation
until
we
actually
have
more
games
and
Lance?
B
A
B
A
B
B
B
Maybe
it
should
be
like
you
know,
extend
or
something
like
that.
It's
as
a
I,
don't
know
because
it's
a
little
bit
weird
like
if
I
were
just
housing.
This
website
and
I
was
like
okay
I'm
going
to
go
to
the
homepage.
I
go
to
the
homepage,
I'm
gonna
go
to
the
handbook
and
the
hanbok
pop
sounds
like
okay.
This
is
the
stuff
in
the
handbook,
but
then
I
get
down
to
modules
and
it
just
like,
as
somebody
that's
just
I,
don't
know,
I
get
I.
B
A
B
Yeah,
okay,
it's
just
a
yeah;
it
maybe
I'm
just
having
trouble
adjusting
to
the
shift
in
the
purpose
of
backdrop.
Cms
tile
to
work
I
mean
I.
We
know
it
was
coming,
but
yeah
the
top
of
them
have
including
functional
things
like
that.
This
is
thrown
there
anyway.
Sorry,
oh,
we
all
talked
about
it
plain.
A
Mm-Hmm
and
I
know
project
sounds
like
that.
Word
has
other
meaning
to
other
people.
No,
no
we'll
figure
it
out.
Somehow
they
are
projects.
Okay,
other
things,
we're
working
on
having
these
pages
up
obviously,
is
great.
We
need
to
work
on
them
a
little
bit
more
in
the
future.
We
want
to
add
a
showcase.
A
So,
let's
talk
about
a
backdrop,
the
project,
so
we
had
a
release
last
week,
which
was
great
and
included
a
bunch
of
little
teeny,
tiny
bug
fixes
and
some
security
issues
that
we
coordinated
with
Drupal.
We
now
have
the
next
minor
release,
which
is
one
point.
One
point
four
is
not
currently
scheduled.
There
are
a
couple
of
little
tiny
things
that
have
been
assigned
to
that
milestone,
but
that
was
just
stuff.
A
I
was
doing
the
other
night
and
it
was
late
and
I
was
mad
mad
and
so
I
said
this
should
be
done
soon,
but
I'm
not
sure
actually
priorities.
We
will
take
a
look
at
that
and
when
we
have
a
bunch
of
things
that
seem
like
they're
urgent
will
issue
a
new
release.
Nothing
currently
on
the
list
for
that
right
now.
Nothing
reckon
1.2
is
our
next.
B
Okay,
sorry
I
had
a
lot
of
tabs
open
and
I
lost
the
Hangout
tab.
So,
okay,
okay,
so
one
point
two
lots
of
exciting
things
in
the
past
week,
so
the
rich
text
editor
meta
issue
is
1087
and
1087
includes
a
chunk
of
things
that
we
want
to
expand
in
our
rich
text.
Editor
integration
and
a
lot
of
great
stuff
is,
has
come
up
in
the
past
week.
Graham's
been
doing
down,
parently
actually
is
running
a
production
site
off
the
dev
version
of
backdrop.
B
So
that's
turning
of
all
kinds
of
great
stuff
because
he
was
saying
he
was
walking
his
client
through
adding
an
image,
and
then
this
happened
and
I'm
like
this
is
fantastic
because
we're
getting
all
of
this
great
and
user
feedback
from
from
our
production
site,
which
is
maybe
not
recommended,
but
is
awesome
for
our
purposes
of
testing
out.
However,
that
works.
B
A
B
Exactly
so
like
yeah,
it's
it's
really
silly,
so
we're
hoping
to
clean
up
some
of
that
stuff
because
it's
totally
obsolete
at
this
point,
but
right
now
it's
the
same
situation
is
triple
seven,
where
you
have
the
filter
tips,
even
though
filter
tips.
Don't
really
do
you
any
good
anymore
and
the
editors
at
the
same
time,
so
we're
up
and
clean
that
up
a
little
bit,
let's
see
a
email
field,
hoping
that
a
simple
email
field
hellenistic
at
made
a
pull
request
a
couple
of
weeks
ago.
B
I
picked
it
up,
let's
see
day
before
yesterday,
to
review
it
for
commit.
It
looks
really
good.
It's.
It's
really
simple.
I
didn't
quite
realize
how
simple
the
email
field
module
actually
was,
after
getting
after
trimming
down
the
functionality
to
the
basics,
the
entire
modules
like
three
hundred
lines
of
code,
so
I'm
feeling
really
good
about
that.
B
I
would
like
to
make
sure
that
we
get
an
update
hook
put
in
they're
so
that
people
are
notified
that
there's
a
core
version
of
email
module
if
you're
running
the
existing
version
of
email,
module
kind
of
similar
to
what
we
did
for
ckeditor
just
to
notify
people
that
they
can
disable
the
old
email
module
if
they
so
choose
and
replace
it
with
a
new
one.
That's
in
court,
let's
see,
link
module,
link,
module,
also
hoping
to
add
decor
for
1.2.
This
is
pretty
much
done
at
this
point.
B
The
issue
is
issue
number
240
I
took
Jeff's
center
deputies,
Paul
request
and
worked
on
that,
a
little
bit
and
I
cleaned
up
all
the
code
style
and
got
all
the
paths.
The
tests
passing
and
I've
gone
over
that
one
three
or
four
times
now
and
I
think
that
it's
it's
ready.
It
would
be
great
to
have
some
confirmation
of
that
if
anybody
else
gets
a
chance
to
do.
A
review
Jeff
in
particular,
be
handy
since
you'd
already
done
a
bunch
of
work
on
link
2
to
try
that
out
and
see.
B
Ok,
cool
he's
already
reviewed
it.
Ok,
excellent,
well,
I
think
that's
pretty
much
ready
to
go.
We'll
probably
see
that
in
the
next
week,
which
should
be
exciting
and
then
email
I
think
we're
also
probably
see
email
in
the
very
near
future
as
well.
So
that's
great
I
mean
for
almost
I
mean
right
now
we're
one
out
of
four
things
that
we
want
to
have
done,
but
I
don't
know
we're
really
close
to
having
this
to,
and
m23
done
is
as
well
between
rich
text,
editing,
email
and
Link
field.
B
So
this
look
like
that's
all
going
to
happen
date.
Field
is
the
one
that
is
the
biggest
remaining
thing
and
is
the
one
that
I've
looked
at
personally,
the
least.
So
we
really
need
some
help
over
in
the
date
issue,
which
is
issue
4
78,
and
maybe
it
doesn't
actually
need
a
whole
lot
of
work.
Maybe
does
I'm
not
really
sure,
but
what
we
need
most.
B
There
is
reviews
of
the
code
that
has
been
posted
grams
said
that
sees
taking
a
break
from
it's
because
he's
done
this
as
much
as
he
knows
to
do
and
that
he
needs
additional
feedback
before
you
do
anything
else.
So,
but
I'd
like
to
see
hopefully
before
next
week
I'll,
I
will
have
had
a
chance
to
look
at
that
and
I
can
give
us
a
better
update
on
the
status
of
date.
B
How
do
we
review
that?
So
if
you
look
at
issue
478,
you
can
find
the
pull
request.
The
gram
made
and
you
do
a
check
out
just
do
a
git
checkout
of
his
branch
of
that.
So
you
add
his
his
repository
as
a
remote
and
then
you
pulled
down
his
copy
of
that
branch
and
then
you
can
get
you
can
type
in
any
pull
request
that
way.
Ok,
you
have
his
remote,
so
you
just
say,
but
he
has
no
branch.
B
I'm
taking
a
look
here:
real,
quick,
oh
yeah,
it
looks
like
he's
just
using
these
1x
branch,
for
that
so
make
your
own
branch.
That
is,
like
a
you
know,
call
it
date
field
or
whatever
and
then
get
pull
his
remote
name,
1
dot
x
and
that
will
pull
is
1
dot
x
into
your
branch
with
it
with
a
different
name.
B
B
Ok,
let's
see
and
there's
some
other
issues
that
we'd
like
to
see
in
1.2,
besides
those
kind
of
major
ones
and
there's
a
list
of
them.
If
you
go
to
the
issue,
the
issue
queue
and
select
the
milestone
for
1.2
there's
some
other
issues
in
there.
That's
we're
trying
to
get
in
as
well
better
peripheral,
but
still
would
be
great
if
we
could
include
them.
B
B
A
I
went
through
the
meta
issue
of
modules
that
were
included
in
Drupal
8
core
and
the
list
of
things
that
we
wanted
to
put
in
backdrop
and
two
of
those
the
menu
you
I
in
administration
of
use.
Where
to
that,
there
were
like
one
of
the
two
of
the
last
ones
that
were
interpolate,
that
we
didn't
have
a
cold
ones
for
in
backpack
job,
so
I
just
say:
you're
getting
those
on
there
should
be
pretty
easy.
A
We
already
have
issues
that
are
kind
of
half
done
on
on
both
of
those,
so
I
think
just
wrapping
them
up
and
getting
them
in
gives
us
some.
You
know
leverage
when
you
say
these
are
all
the
modules
that
went
into
Tripoli,
and
these
are
all
the
mantra
someone
in
the
back
trip,
if
those
are
comparable,
I
think
that
looks
good
and
isn't
seeming
like
they're.
A
A
A
Tripoli
has
a
ton
of
field
modules
in
there
things
like
phone,
which
I'm
not
entirely
sure
applies
to
the
eighty
percent,
but
we
can
reevaluate
that
too,
and
if
there
are
modules
that
are
used
for
the
eighty
percent
in
backdrop
that
weren't
in
drupal,
that
might
also
be
a
good
time
to
start
looking
at
our
actual
usage
statistics
and
see
what
people
are
doing
with
backdrop
and
see
if
our
priorities
should
become
different
from
drupal's.
So
that's
a
good
good
place
to
kind
of
do
an
evaluation.
A
We
also
have
a
bunch
of
other
user
experience
issues
on
github.
I
wish,
on
their
last
few
days
creating
a
handful
of
my
own
and
I
notice
they're
a
bunch
of
other
ones
on
there,
which
is
fantastic
and
a
whole
bunch
of
really
good
ideas
about
how
to
solve
some
of
the
problems
that
were
we're
facing
and
have
been
facing
and
drupal
for
a
long
time.
So
I'm
super
excited
to
see
all
the
work
going
on
in
that
and
there's
also
a
tech
for
developer
experience.
Issues
too.
A
We
just
need
to
fix,
but
if
we
can
get
them
fix
them,
that
experience
is
going
to
be
much
better,
but
there's
also
just
a
bunch
of
weirdness
that
we've
got
in
fact,
droplets
left
left
over
from
Drupal
steam
system
that
we
should
maybe
evaluate
and
figure
out.
You
know
I've
done
a
lot
of
work,
thinking
about
Drupal
steam
system
and
how
to
make
it
better.
A
So
I
think
having
a
good,
solid
product.
Ready
is
going
to
be
really
important
for
us
and
thank
you,
everybody
for
all
the
work
that
you've
been
doing
to
help
us
get
there
too.
So
it's
pretty
exciting.
Ok!
So,
today,
after
this
meeting
we're
going
to
have
a
little
sprint
in
IRC-
and
we
usually
do
this
every
Thursday
afternoon-
so
if
you
can
get
time
to
contribute
to
the
backdrop
project,
Thursdays
you're
a
good
day
to
do
it,
we
meet
in
IRC.
Our
IRC
channel
is
a
pound
backdrop.
A
We're
also
all
over
the
github
issue.
Queue
of
IRC
isn't
your
thing:
we
have
a
run
it
as
well
and
we
are
looking
into
other
places
where
the
community
can
interact
so
we're
going
to
try
and
figure
out
how
to
get
single
sign-on
in
our
website
and
the
more
open
figuring
out
like
how
we
can
use
that
for
collaboration.
Communication
as
well,
so
we'll
be
looking
into
that
here
in
the
next
few
months.
Upcoming
events
we
have
slides
for
anyone,
that's
doing
a
presentation
on
backed
up.
A
In
the
backdrop,
ops,
github
group,
there's
a
project
called
slag
glass
has
done
a
bunch
of
work
on
making
I
reveal
j/s
a
kit
there.
So
if
anyone
wants
to
pull
slides
from
existing
presentations
or
just
use,
reveal
j/s
with
the
backdrop
theme,
that's
all
there.
Anyone
who
does
a
presentation
using
that
kid,
if
you
add
your
own
sites,
would
love
to
have
them
back.
A
You
can
just
create
a
forward
quest
there
and
we'll
try
and
make
that
kind
of
a
repository
for
information
for
anyone
who
either
wants
to
watch
slides
on
vector
or
give
talks
of
their
own,
which
I
think
will
be
a
good
resource
for
the
community
and
in
the
near
future.
We
also
have
drupalcamp
la
which
weight
set
it's
this
weekend
last
weekend.
A
Is
this
weekend
it's
tomorrow
so
this
weekend,
if
you
were
in
Los
Angeles,
you
can
go
to
gerbil
camp
LA
they're
back
to
a
friendly
event,
so
people
there
will
be
chatting
about
backdrop,
which
is
a
good
thing
to
do
friendly,
chitchat
banter.
All
of
that
I
don't
know
if
anyone's
actually
presenting
on
factor
up
there,
but
that
would
be
interesting
to
hear
about.
A
If
someone
does
and
then
in
two
weeks
we
have
nerd
summit,
which
is
the
north-eastern
something
or
other
it
I,
don't
remember
which
city
it's
in,
but
we
will
figure
it
out.
Amherst
area.
Thank
you
like
I
know
I
just
bought
a
plane
ticket,
but
I
get
remember
where
we're
going.
So
that's
coming
up
that
I
think
is
super
exciting
because
that's
the
second
event
that
we've
attended.
That
is
not
a
specific
Drupal
event,
and
this
is
a
big
chunk
of
our
target
audience.
A
It
is
your
full
and
WordPress,
and
what
backed
are
trying
to
sit
right
in
the
middle
it'll,
be
super
interesting
to
talk
to
WordPress
people
about
doctor
and
see
what
they
think
it'd
also
be
good
to.
You
know
talk
to
our
our
Drupal
folks
and
see
what
they
think
I
think
it's
going
to
be
a
lot
of
going
to
be
a
CMS
panel
on
Saturday,
where
I
think
a
bunch
of
it
we're
going
to
ask
a
bunch
of
different
questions
to
you
know.
How
do
you
solve
this
problem?
A
A
A
If
anyone
watching
this
meeting
knows
about
another
jubilantly
you're
going
to
be
talking
about
backdrop,
let
us
know-
and
we
can
throw
it
onto
our
calendar
and
we'll
eventually
get
a
listing
of
events
up
on
our
website,
where
people
can
consult
that,
but
right
now
there's
an
ical
fee
that
is
available
on
the
contribute
page
on
by
trip
seamless,
org
and
on
our
reddit
page.
So
hopefully
you
guys
can
go
and
find
that
easily
enough.
A
A
A
A
So
yeah
I,
don't
I,
don't
know,
I
would
say,
put
your
put
your
thinking,
hats
on
and
we
can
start
with
an
issue
on
github
right
now
as
a
put
it
in
the
contributory
or
something
and
see
if
we
can
start
keeping
track
there.
But
it
would
be
good
to
have
another
way
to
tell
I
mean
keeping
track
of
issues
for
their
most
or
modules
that
are
most
downloaded
for
Drupal
I
mean,
but
our
top-top
modulus
is
what
we've
been
working
for
lately
to
see.
A
There
Andy
also
asked
a
question
about
libraries,
handling
and
backdrop.
So
I
don't
know
Nate.
Maybe
you
can
talk
better
to
this
than
I
can
but
I
think
our
general
consensus
is
the
reason
that
we
had
to
have
a
libraries
module
for
Drupal
is
because
you
couldn't
include
libraries
with
your
drupal
module,
so
you
needed
some
way
to
manage
that
and
backdrop.
A
You
probably
don't
want
to
do
that,
but
I
don't
know
I
mean
maybe
yeah
having
some
way
to
if
you
had
a
different
module.
That
also
included
seek
editor,
making
sure
that
you
didn't
get
two
copies
of
it,
and
this
is
C.
Gators
a
bad
example
for
this,
but
something
like
slideshows
right,
you
might
have
a
view:
slideshow
module
on
a
field.
Slideshow
module
needs
the
same
library,
but
you
don't
want
to
download
that
library
twice
so
yeah
I
don't
know,
and
we
need
to.
A
We
need
to
examine
that
problem,
space
more,
which
I
think
we
can
do
once
we
have
once
we
have
actual
controls
that
use
libraries,
it's
a
little
hard
to
guess
what
we
need
to
do
before
that
problem.
You're,
probably
running
into
India's
that
when
you're
porting
modules
that
require
libraries
I
want
you
to
say
what
we
need
to
do
when
we're
14
modules
is
removed,
that
dependency
and
just
add
the
library
and
then
we'll
start
figuring
out.
You
know
how
to
manage
those
long-term.
A
B
There's
a
whole
new
discussion
that
is
happening
in
this
space
right
now.
That's
not
about
JavaScript
libraries,
about
PHP
libraries
and,
let's
see
a
mat,
opened
up
an
issue
from
Allah
bot
actually
opened
up
an
issue
about
how
we
should
include
PHP
libraries
and
modules,
which
got
into
a
little
bit
of
a
composer
discussion
and
there's
an
issue
issue
1123
here,
I'll
link
to
it
and
now
yeah
there
we
go
this
one.
B
You
guys
haven't
seen
that
so
there's
the
discussion
that
he
brought
up
there
about
embedding
PHP
libraries
and
modules
and
how
that
probably
wouldn't
I
mean
PHP
libraries
are
more
likely
to
be
used
by
a
group
of
modules
in
some
cases,
depending
on
what
that
PHP
library
is,
especially
if
it's
something
like
some
symphony
component
or
something
like
that.
That
is
a
general
purpose
thing
and
right
now,
I,
don't
really
have
a
lot
of
extra
input
on
it,
because
I
haven't
finished
reading
through
everything.
B
That's
going
on
there
there's
a
discussion
that
just
started
on
the
Drupal
q
two
weeks
ago
about
using
a
packages
instead
of
or
in
place
of
or
in
addition
to
drupal.org
for
module
management
and
how
that
interacts,
with
modules,
using
composer
and
using
composer
to
install
modules.
So
there's
all
kinds
of
crazy
things
all
around
that
discussion.
But
this
thread
is
like
really
really
long
and
really
for
both
so
I
think
gotten
through
it.
Yet,
but.
A
Nobody
would
keep
in
mind
that,
like
things
that
are
going
on
in
the
drip
world
might
not
be
wrong
and
to
us
too
I
mean
do
eighty
percent
of
WordPress
users
use
composer
like
I
feel
like
that
is
maybe
a
non-issue
for
us
and
we
should
not
be
I
mean
yeah.
These
tools
are
good
and
like.
If
we
can
allow
people
to
use
them,
we
should.
A
We
should
not
require
that,
because
it's
going
to
severely
increase
the
barrier
to
entry
for
installing
libraries
if
we
have
to
do
that
through
something
like
composer
tour
packages,
so
I
think,
like
there's
a
simple
solution
which
we
need
to
consider
first
and
then
there's
like
the
best
solution
that
we
also
need
to
consider.
But
I,
don't
I
mean
I.
Think
for
now.
B
A
B
A
All
right:
well,
then,
we
will
end
this
meeting.
Definitely
if
anyone
has
any
ideas
about
the
library
stuff
throat
and
the
issue
queue
read
what's
going
on
in
drupal.org.
Let's
keep
that
conversation
going
cuz,
it's
super
interesting,
but
yeah.
We
will
see
you
all
on
in
the
github
queue
or
next
week,
thanks
everyone
from
joining
and
keep
up
the
good
work.
We're
really
excited
to
see
all
the
momentum
in
progress.
That's
been
happening
in
backdrop,
one
job,
everybody,
I'm
a
good
thursday.
All.