►
From YouTube: Backdrop Weekly - Mar 28th
Description
Today’s development agenda: http://bit.ly/2TOaBTz
A
All
right
we're
on
air
today
is
Thursday
March
28,
and
this
is
a
meeting
to
check
in
on
active
development
tasks.
For
our
backdrop,
CMS,
where
we
get
into
what
we've
been
working
on
lately,
I
want
to
say
a
quick
welcome
to
pull
for
being
here
and
even
in
the
meeting
today,
which
is
great
and
vasa
I,
don't
know
fastest
real
name
but
for
porting
menu,
import
module
and
working
on
backdrop
talkers.
So
it's
always
great
to
see
new
faces
in
the
net
community.
Thanks
for
joining.
B
A
C
C
C
It
works
for
myself
locally
and
from
the
command
line
on
the
server,
but
for
some
reason
that
version
of
PHP
my
code
or
something
doesn't
work
well,
and
so
my
theory
is
that
when
we
switch
to
a
new
server,
the
demo
button
will
start
working
again.
So
for
now
we're
kind
of
marked
the
demo
button
is
being
pending
on
the
server
upgrade,
because
I
think
those
two
things
will
just
kind
of
go
together
or
one.
C
Will
fix
the
other
one?
So,
let's
see
see
this
comment
from
how
to
test?
Yes,
you
can
test
any
of
the
new
servers
by
adding
an
entry
to
your
hosts
file
and
then
pointing
at
the
new
IP
address
that
include
it's
the
forum,
the
localization
server
backdrop
CMS
stored
the
API
website
and
did
I
mention
the
forum
already
yeah,
all
of
those
so
ready
for
cut
over
question
mark.
That
is
a
good
question.
C
When
we
actually
do
the
cut
overs,
we
only
need
to
basically
do
two
things:
dump
the
database
move
over
the
files
and
config
and
then
and
then
cut
over
the
domain
name,
so
everything
the
whole
code
base
and
everything
is
already
on
for
all
of
those
servers.
It's
just
for
me
to
replicate
all
new
content
before
we
do
any
kind
of
Reese.
A
Justin
said
he
was
going
to
post
a
schedule
in
Makena
for
us,
where
of
you,
my
guess
was
that
we
should
not
do
all
of
the
sites
at
once.
We
should
start
with
something
like
API
just
to
make
sure
that
that
goes
smoothly
and
then
once
we're
sure
that
that's
right,
then
we
can
do
it
once
yeah,
okay,
so
I
asked
him
to
close
to
schedule
at
work
to
put
them.
So
you
know
what
days
I
asked
me
give
us
a
week
to
do
some
testing.
A
C
C
C
All
right,
so,
let's
move
on
to
backdrop.
The
product
will
give
a
little
update
here
on
the
Nexus,
but
fixed
version.
We've
got
a
hit
list
of
a
large
number
of
items
that
we've
got
prioritized
for
immediate
fixing
as
soon
as
possible
in
the
112
six
release,
which
will
be
put
out.
Basically,
whenever
we
collect
this
a
significant
number
of
fixes,
so
RTL
issues
we've
still
been
like
rocking
on
these
RTL
issues.
C
I
think
maybe
it's
time
for
us
to
maybe
stop
mentioning
them
during
the
weekly
meetings,
even
though
it's
still
awesome
that
they're
coming
in,
like
we
got
through
like
15
RTL
issues
in
the
past,
but
there's
new
ones
still
coming
in,
but
mostly
thanks
to
Gregory
I.
Think
having
all
of
this
just
incites,
but
also
that
that
contributor,
what
was
his
name
shot?
Chiapas
midi,
said
about
something.
C
D
C
Yeah
I
had
been
going
through
RTL
issues
earlier
in
the
week,
and
I
accidentally
marked
a
couple
of
them
incorrectly,
because
I
posted
I
got
all
confused
about
it.
So
there's
one
for
ckeditor
icons
that
is
issued
3504.
That
has
been
fixed
functionally
how
it
works
in
RTL,
but
it
has
some
margin
problems.
So
there's
a
Shyama
therefore
request
to
help
figure
out
this
small
margin
issue.
It's.
It
looks
like
it's
just
a
matter
of
CSS
specificity
that
the
padding
on
unordered
lists
is
affecting
RTL
in
a
way
that
it
should
be.
C
C
Let's
see
other
options
or
other
things
that
we're
working
on
supporting
multiple
equivalent
security
releases.
This
is
3524
now
that
we
officially
support
the
current
release.
Current
minor
version
like
which
is
112
right
now
and
the
previous
version,
which
is
111
right
now.
We
need
a
way
to
make
it
so
that
security
updates,
don't
yell
at
you
if
you're
running
111,
because
you're
fully
patched
you're,
just
not
on
the
latest
version,
so
35
24
is
issued
to
make
that
possible.
C
The
discussion
is
kind
of
complete
there,
or
at
least
we've
got
ideas,
but
there's
no
code
behind
that.
Yet,
let's
see
we're
kind
of
a
regression
or
an
upgrade
issue
for
all
the
1.12,
thus
far
that
we
merged
options
element
into
court.
But
you
get
a
fatal
error
if
you
were
using
options
element
previously.
This
is
issue
3485
Gregory
brought
up
something
that
was
really
smart,
saying.
C
Don't
we
have
a
function
for
like
managing
this
for
the
keeping
track
of
modules
that
have
been
merged
into
court,
and
we
do
it's
called
backdrop
merged
modules,
which
it's
up
their
mind
that
we
already
have
done.
Something
similar
for
previous
modules
and
so
backdrop
emerged
modules
will
prevent
the
old
module
from
being
turned
on
on
newer
versions
of
the
backdrop.
C
So
that's
good
and
it
will
also
not
load
the
install
file.
So
in
theory
in
theory,
this
might
make
it
so
that
you
can
visit
update
dot
PHP
without
it
crashing
on
you.
If
we
just
add
options,
element
to
that
function,
that
lists
modules,
and
then
we
could
read
an
update
hook
that
turns
off
that
old
module.
I
actually
think
we
might
even
have
an
update
hook
that
turns
off
that
old
module.
C
Let's
see,
we
have
an
issue
that
layout
clone
breaks,
the
layout
that
is
created
and
the
layout
that
was
cloned,
which
is
big
problem,
2673
still
needing
tests
on
this.
It's
been
confirmed
multiple
times
that
the
fix
a
pull
request,
that
is
present,
corrects
the
problem,
but
we
don't
have
tests
for
that.
That
looks
like
Jam,
you
might
have
made
a
new
issue.
Label
for
status
needs
tests,
which
is
appreciated.
B
C
Let's
see
another
issue
that
is
test
related,
actually
3462
is
an
issue
where,
if
you
delete
a
file
out
from
under
backdrop,
while
creating
content,
sometimes
that
causes
a
fatal
error
but
we're
in
a
situation
where
nobody's
been
able
to
reproduce
the
problem.
Jen
reported
it
there's
no
tests
and
actually
test
the
problem,
but
it
don't
fail,
even
if
you
run
an
unpatched
traditional
backdrop,
so
still
waiting
to
see
if
this
is
an
actual
problem
or
something
related
to
another
module.
There's
an
environment
related
we're
not
sure.
A
I
even
did
a
core
update
for
that
site
recently,
where
I
applied
a
new
version
of
cord
didn't
put
the
patch
that
I
originally
put
on
that
issue,
and
my
site
didn't
explode
was
like
a
site
broken
before,
so
it
might
also
be
relieved
to
PHP
version,
so
I'm
going
to
test
that
next
and
see,
if
maybe
it
only
happened
done
like
because
my
old
servers
was
the
same
site.
My
a
triple
six
light
was
running
on,
so
it
could
be
that
that
version
of
PHP
clastic.
C
C
E
C
A
C
C
No
I
think
I.
Think
in
the
evening
is
fine,
especially
you
know
we're
west
coast,
so
it's
only
7
p.m.
for
me
and
I.
Don't
think
it'll
take
long,
I'm,
not
even
actually
mature.
If
we
need
your
assistance
really,
because
it's
just
updating
the
domain
name,
the
API
side
especially
has
less
content
and
less
updates
than
other
ones.
Yeah.
E
E
C
E
C
E
A
B
E
C
A
C
A
A
So
this
is,
if
you
have
like
tests
in
your
module
and
the
tests
don't
have
a
like
by
pupils
module
line,
there's
something
somewhere,
that's
checking
for
module
step
explodes
because
that
type
definition
isn't
in
the
test
file.
So
it
shouldn't
be
checking
in
tests
for
that
particular
thing,
but
it
is.
This
is
actually
for.
D
D
We
had
a
position
that
we
fixed.
We
fix
things
for
the
tests
by
excluding
them
from
the
regular
expression
that
tests
for
sex
for
type
equals,
and
then
we,
the
same
problem,
came
up
with
profiles
and
I
think
filed
a
pool
request.
That
I
tried
to
also
exclude
these,
but
then
it
wasn't
taking
account.
It
was
only
checking
in
to
account
for
profiles
and
not
country
profiles
or
were
customized
and
that
might
have
might
cause
a
problem
into
it.
D
Look
it
wasn't
future
proof,
and
so
the
simple
solution
for
the
there
was
an
alternative,
PR
and
then
I
actually
filed
a
separate
ticket
for
it
and
all
I
did
was
just
add
type
equals
profile
to
all
the
core
profiles.
And
here
we
thought
that
it
was
more
elegant,
simple
solution
that
we
can
get
in,
but
we
have
no
way
to
test
it
actually.
D
A
C
D
So
I
know
that
I
will
file
a
follow-up
after
that.
I
know
that
we
got
the
the
regular
expression
in
in
place
to
exclude
tests,
but
I
think
that
we
should
reconsider
an
address
type
equals
test
the
test
files.
It
will
make
it
easier
instead
of
having
weird
situations
where
tests
are
nested
within
some
folders
of
custom
modules
and
whatever,
and
then
they
fail.
I
think
it
might
be
safer,
but
I
will
file
a
follow-up
for
that
and
we
can
consider
it
cool.
C
Ok,
excellent,
it's
so
nice
and
I
find
ya.
It
looks
RTB
see
now.
Ok!
So,
let's
see
contextual
links
for
views
2690
I
saw
there's
a
new
poll
request
there
that
takes
a
novel
approach,
basically
moving
where
the
contextual
links
are
stored,
rather
than
trying
to
do
some
kind
of
CSS
fix
or
where
this
contextual
link
is
placed
on
the
page
needs
review
seems
like
a
good
approach
by
my
eyeballing,
but
yeah
that
looks,
looks
promising.
C
A
Want
to
add
that
we
added
a
new
issues
label,
and
this
really
applies
mostly
to
you
and
her
Nate,
but
there's
a
new
RT
BC
label,
which
is
our
TPC
Plus
code
review.
So
it's
March
arts
would
be
C
by
the
people
who
have
tested
it,
but
maybe
they
haven't
like
they
aren't
sure.
If
the
code
is
gonna
pass,
muster
or
not
so
I,
don't
know
if
that's
beneficial
to
you
to
have
two
Q's
to
have
to
check,
but
it
doesn't
make
it
clear
like
what's
ready
to
be
merged
and
what's
not
yeah.
This.
D
Was
a
request
that
came
from
herb
a
couple
of
weeks
ago
and
he
said
that
we
should
encourage
people
to
just
test
things
and
Mark
the
Maserati
BC
if
they
tested
it
and
it
works
for
them
and
then
have
a
separate
label
so
that
people
can
then,
with
you
and
say
that
this
is
also
being
code
reviewed.
So
we
can
have
less
less
technical
users
come
and
test
things
from
the
user
perspective
like
from
the
user
interface
using
the
sandboxes.
Or
what
have
you
alright
deeper
needs,
further
review.
C
Interesting
DBC
but
yeah
I
kind
of
even
think
it
might
be
better
if
there
were
just
two
separate
like
it
not
like
leave
our
TBC,
which
you
guys
do
not
ready,
but
it
ended.
Well,
don't
already
have
status
needs
coverage.
It
needs
code
review
where
we
only
have
status
needs
to
interview
you
yeah.
Maybe
we.
C
D
C
Like
reviewed
by
committer,
or
something
like
that,
you
know
like
like
I,
started
like
if
herb
comes
through
and
says
that
it
looks
good
to
him,
but
he
doesn't
commit
it,
which
honestly
I
kind
of
would
prefer
that,
like
we
didn't
have
that
additional
gateway
in
there
like
and
I
kind
of
find
actually
her
and
anybody
else.
Just
saying
you
know,
I
read,
it
looks
good,
but
I
understand
it.
There
there's
some
hesitation
there
and
just
commits.
A
C
C
Right
yeah,
it's
interesting
that
what
we
kind
of
have
right
now
is
we
have
like
there's
our
TBC
and
then
there's
like
RTB
c++,
where
herb
comes
in
and
says
I've,
given
this
an
additional
review
on
top
of
the
RT
bc,
but
I
still
haven't
committed.
It
is
that
is
that
the
situation
that
we're
talking
about
right
now,
basically
yeah.
D
Yeah
I
know,
and
also
the
fact
that
people
are
scared
to
mark
issues
as
TBC
when
they
have
tested
them.
They
just
leave
them
as
need
review
where
they
have
actually
tested
it,
so
they
have
no
way
to
say
a
Festivus.
It
works.
For
me
it
could
be
a
an
issue
that
says,
looks
good
to
me
or
works
for
me
interesting
yeah,
something
that
people
can
use
DeMarcus.
You
know
what
I've
tested
it
in
the
sandbox
and
it
works
as
expected
works
as
expected.
Something
like.
C
A
C
That
is
separate
from
our
TBC
I
think
it
should
be
our
TBC
plus
something
else.
You
know
that
way.
I
still
only
have
to
check
the
ret
vcq,
but
then
there's
an
additional
label.
That
means
something
you
know
saying
like
you
know:
RGB
C++
or
something
I,
don't
know,
maybe
just
a
plus
plus
label
whatever
in
status,
is
it's
more
than
that.
D
C
A
A
So
what
I
could
do
so?
What
I
have
now
is
I
have
a
PR
needs
testing
and
a
peer
needs.
Code
review
and
I
have
a
PR,
reviewed
and
tested
by
the
community
and
a
PR
works
for
me,
but
maybe
I
should
change
the
name
of
testify
community
to
ready
to
be
committed
because
works
for
me
is
the
same
as
read
anticipated
community.
It's
just
I
in
the
community
right
and
our
TVC
is
now
our
like
ready,
yeah.
D
A
C
C
A
A
C
C
C
C
Somebody
was
asking
about
going
through
the
application
process
and
we
have
these
special
tags
for
like
contributor
application,
but
we
don't
have
any
templates
over.
In
the
backdrop,
can
trip
the
positive
or,
in
the
backdrop
ops
slash,
can
trip
repository.
That
would
be
a
perfect
place
for
us
to
make
an
issue
template
for
maintainer
application.
C
A
There
is
an
issue
for
that
under
bankruptcy,
matzo
RQ.
The
document
has
been
recently
that
so
make
it
easier
to
become
maintain
your
cooking
trip.
I
think
it'll
be
good
to
add
this
into
there.
Some
of
them
make
it
easier
than
issue
number
five
team.
There
you
go
just
throw
this
into
the
DVD
section.
Today's
agenda
cool.
C
Okay,
resuming
product
updates,
so
minor
version
that
expiration
will
be
1.13
which
will
come
out.
May
15th
feature
breeze
will
be
May
1st,
and
we
have
a
number
of
issues
here
that
we've
got
prioritized
so
the
first
one
that
we
have
is
adding
back
last
field
for
matters
its
who
issued
13.
Setting
these
fixes
add
some
new
or
restores
some
hooks
actually
for
for
making,
so
that
field
for
matters
can
have
settings
I
think
that's
what
this
is
now
has
tests,
which
is
awesome,
herb
dual
added
the
man
or.
C
Let's
say:
okay,
so
Hercule
added
in
tests
maybe
or
suggested
that
we
take
some
tests,
I
think
I
think
maybe
the
tests
aren't
actually
in
the
poll
requests
yet,
but
there
are
tests
that
we
can
copy.
Maybe
that's
the
size
of
things.
It's
currently
still
mark
needs
work,
but
there
are
tests
that
we
can
pull
from
to
make
it
so
that
that
would
be
complete
the
function.
The
implementation
has
already
been
our
TBC,
but
that's
one,
the
ones
that
I
said
needs
to
us.
So
once
we
have
tests
that
should
be
complete.
C
Telemetry
issued
285
concept
here
is
that
we
want
to
start
collecting
information
about
the
environments
and
the
ways
in
which
people
are
using
backdrop
and
then
start
recording
that
through
an
opt-in
system,
there's
no
code.
Yet
behind
this
issue.
Still
it's
like
we
keep
talking
about
how
great
it
would
be,
but
yeah
we're
looking
for
kind
of
a
champion
to
work
on
to.
Let
me
treat
dashboard
issue
495
status
currently,
as
needs
tests
done,
I
mean
think
you'd
like
to
add
about
dashboard.
A
No
I
think
we've
got
it
at
a
point
where
it's
mostly
ready.
You
know
Gregory's
working
on
one
pull
request
to
change
some
a
whole
bunch
of
little
things.
If
anyone
else
wants
to
give
it
a
test,
I'm
open
to
changing
anything,
if
you
notice
any
typos
are
wrong
terminology
or
whatever
that's
probably
stuff
Greg's
working
on,
but
there
could
be
plenty
of
other
changes
in
there
in
general.
I
think
we're
happy
with
the
initial
blocks.
But
if
you
have
ideas
for
other
things
you
want.
C
C
Sorry:
okay!
Okay!
Here
we
sorry,
that's
not
the
meta
issue,
that's
the
one
that
actually
needs
review,
which
is
which
adds
in
translation
for
site,
name,
site,
slogan,
maintenance
message
and
the
welcome
emails,
so
that
one
has
been
these
reviewed
quite
some
time.
It's
yeah
basically
just
needs
eyeballs
on
that
and
once
I
think
her
goal
has
been
doing
those
conversions
and
once
we
get
an
approval
on
the
basic
approach,
then
I
think
he's
looking
to
get
approval
on
that
and
then
we'll
go
through
and
start
converting
a
bunch
of
other
config
files,
in
course.
C
And
lastly,
package
signing
issue
in
1992
needs
reviewing
and
feedback
still
prototype.
John
Franklin
put
up
two
separate
modules
for
enabling
signing
using
two
different
encryption
methods
and,
yes,
still
needs
needs,
review
and
feedback.
There's
a
lot
to
go
through
there
and
I
think
he's
looking
for
my
feedback
in
particularly
but
other
feedback,
which
is
definitely
definitely
appreciate
it.
A
That's
like
highlighting
the
good
things
about
coming
in
gerbil,
and
a
couple
of
the
things
we
mentioned
were
how
many
Drupal
modules
are
core,
which
is
more
than
60.
How
many
of
the
top
100
King
trim
modules
are
backdrop
ready,
and
the
upgrade
status
module
from
general
should
probably
have
virgin
is
backdrops
contributory,
where
it
would
check
against
backdrop
status
instead
of
checking
against
triple
status,
with
your
blade
status
of
triple
7
modules
and
I
I.
Think
that
was
it.
D
There's
a
couple
of
things:
first
of
all,
we
have
like
13
issues.
There
are
TBC
if
you
count
that
simple
one
with
the
dirty
profiles
for
the
profile
6:14.
So
maybe
we
should
they
and
two
or
three
of
these
issues
are
kind
of
serious
bags.
So
maybe
we
should
aim
for
like
the
week,
the
next
week
or
the
week
after
that,
to
have
a
small
minor
release
with
those
and
the
other.
One
was
during
the
ritual
user
group
that
we
had
a
couple
of
days
ago.
D
We
sort
of
like
discussed
about
how
easy,
and
so,
in
general,
the
process
of
upgrading
from
Drupal,
6
and
7
to
bactrim,
and
it
was
mentioned
that
there
is
something
that
it
was
sort
of
like
things.
I
realized
is
that
there
is
a
there
is
a
way
and
a
reason
to
upgrade
to
either
upgrade
were
migrated
from
d7,
depending
on
whether
you
want
to
change
data
on
the
existing
database,
and
we
found
that
documentation
regarding
the
upgrade
over
the
Suites
in
general
is
sort
of
like
misleading
in
certain
places.
So
we
need
to.
D
We
need
to
heavily
like
update
things
and
start
testing
things.
One
of
the
things
that
was
proposed,
these
all,
have
had
a
test
site.
His
personal
side,
I
think
he's
facing
a
few
issues
and
his
his
there's.
No
objection
if
to
provide
the
database
even
unsanitized,
just
the
password
may
be
removed
so
that
we,
that
was
a
Jeff
suggestion
that
we
all
have
something
like
a
common
ground
that
we
are
testing
off
of
in
order
to
try
to
solve
problems
with
upgrades
from
d7.
D
Doesn't
have
to
be
so.
If
we
share
the
database,
then
people
can
install
it
on
the
local
and
start
playing
with
upgrading
and
if
issues
come
up,
then
file
problems
come
up
and
file
respective
issues
in
github
and
if
they
are
able
to
solve
those
issues,
then
file
pull
requests
to
sort
these
issues
out.
We
just
need
something
like
a
common
sort
of
like
common
ground,
where
we
all
test
the
same
problems.
D
A
Definitely
have
a
bunch
of
sites
that
I
get
offers
anything,
but
I
wonder
if,
like
having
the
same
site,
upgrade
is
going
to
be
valuable,
I
feel
like
any
time
any
one
of
us
runs
into
an
issue
we
should
probably
post
at
least
anti
search
and
potato-based
were
using,
but
I
think
it
would
be
better
if
we
all
came
from
different
places
to
find
good
problems.
Otherwise
we're
gonna
miss
a
bunch
that
don't
happen.
A
D
A
Maybe
what
we
need
is
like
a
utility
that
will
give
them
the
same
see
at
least
like
any
picture
we
get
sequins
and
trash
and
then
maybe
even
something
and
back
up
a
migrate.
That
would
be
like
a
sanitized
checkbox
or
something
so
that
we
can
respond.
A
Cuz
I
feel
like
we're
gonna
run
into
this
issue,
regardless
of
you
know
what
we
trying
to
do
to
protect
it
and
what
we're
doing
and
the
best
solution
would
be
make
it
possible
for
people
are
running
an
issue
report,
the
problem
in
a
way
that
we
can't
reproduce
it
that's.
What
actually
is
thank
you
I.
D
Think
that
the
discussion
that
we
had
in
that
in
the
last
video
of
user
group
is
going
to
be
repeated
for
the
next
couple
of
years,
because
people
are
going
to
decide
whether
they
are
going
with
d8
or
backdrop
and
they're
gonna
start
doing
things.
So
we
need
to
improve
the
documentation.
That's
one
thing,
but.
D
We
need
to
cover,
in
both
cases
scenario
because
I
didn't
even
know,
then
you
were
in
part
of
that
and
I'm
sure
Tim
mentioned
that
most
of
the
switches
that
you
have
done
are
actual
in-place
upgrades,
but
it
was
brought
during
the
discussion.
I'm,
not
sure
if
you
what's
the
video
that
was
recorded,
that
there
are
valid
reasons
for
people
to
solve,
like
do
migrations
as
clean
up
the
database
and
then
do
it.
And
then
another
problem
that
came
up
was
features.
D
Module
is
being
used
in
like
three
more
than
300,000
sites
and
so
far
the
recommendation.
It's
not
reading
in
documentation,
but
the
recommendation
is
to
use
the
unfit
rise.
Module
and
I
was
wondering
if
we
can,
like
it
quark
and
grab
things
and
convert
them
into
CMI
directly.
Certain
things
features,
I,
don't
know,
have
features
like
I.
Don't
have
a
low-level
understanding
of
health
features
work
like
is
it
only
creating
content
types.
A
Yeah
I
think
anything
that
uses
C
pools.
It's
portables,
that's
kind
of
the
majority
of
what
features
works
really
well
on.
We
could
probably
provide
a
conversion
from
the
sequel's
it's
portable
to
a
backdrop,
config
file.
The
issue
would
be
if
whatever
module
it
is,
has
been
boarded
the
backdrop
and
handles
config
in
the
way
we
expect,
based
on
it
being
sequels,
because
I
mean
anyone
who
created
anyway.
Those
controls
could
have
chosen
to
so
in
a
perfect
world.
A
D
A
Breaks
helps
usually
it
all
sort
of
has
like
conditional
overrides
of
things
which
gets
super
weird,
because
backup
doesn't
have
any
way
to
intercept
the
information.
A
quick
config
file
in
the
same
way
that
Drupal
has
a
way
that
you
could
ever
touch
a
variable,
so
we
don't
have
an
equivalent
for
Starlin.
All
we
would
do
is
like
change
the
value
and
that,
if
they
were
using
strong,
are
that's
probably
not
what
they
wanted.
A
D
A
I,
do
it's
like
I'm
from
features
I
go
through
the
features
and
I
save
them
annually
on
April
7
site
by
using
the
interface
and
then
I
delete
the
feature
module
over
a
none
future
ice
to
get
stuff.
That
might
not
be
in
the
Davis
in
duty
case
and
then
I
put
that
in
there
with
the
features
I
might
see
if
it
still
works,
and
if
it
does
then
I
just
run
the
regular
upgrade
and
it
works.
The.
D
A
We
could
automate
that
over
I
put
everything
back
in
the
database
in
the
way
that
you,
like.
You
know
how
there's
like
a
feature
set.
If
you
all
come
in
look
if
there
was
the
opposite
of
that,
it
was
like,
rather
than
like
revert
everything
to
what
some
code
would
be
like.
Take
all
the
code
and
put
it
back
in.
A
A
A
D
A
D
E
A
A
D
For
its
for
each
entry
in
the
respective
module
of
what
would
be
the
great
status,
we
could
have
a
sort
of
like
reading
your
instructions
that
points
the
documentation
specifically
for
that
mojo.
If
there's
something
specific
that
users
need
to
do,
it
could,
for
example,
have
a
yellow
status
instead
of
a
green,
which
means
that
it's
not
automatically
migrated,
but
you
have
to
do
some
manual
steps,
read
the
readme
not
willing
to
for
more
information,
something
like
that.
Yeah.
A
D
The
hope
there
is
that
if
we
have
more
people
coming
in
which
I'm
sure
more
will
I
know
that,
there's
these
two
person
and
being
about
people
contributing
from
the
homes
so
like
total
of
users.
So
if
we
have
the
respective
2%
coming
name
like
one
user
every
now
and
then
coming
in
and
just
tackling
small
things
that
we
have
in
our
to-do
list,
it
would
be
helpful,
so
I
think
organically.
This
will
happen
until
then.
It's
it's
ok.