►
From YouTube: Backdrop Weekly - June 9th 2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
we're
live
today,
2022.
This
is
our
weekly
developer
check-in
meeting.
We
don't
have
a
whole
lot
on
the
agenda
for
today,
but
we
will
get
to
it
after
some
introductions.
A
And
if
the
next
person
could
call
me
I'm
joining
from
oakland
california,
today,
I'm
working
on
some
automation
tools
for
the
events
website
and
hopefully
I'll
have
those
up
afterwards
tim.
I
I
elaborated.
A
Game,
but
I
can
share
them
with
you
when
we're
done
here
if
you're
curious,
sure,
let's
go
with
alejandra.
E
And
tim,
okay,
I'm
tim
erickson,
saint
paul
team
in
deerwood,
minnesota
and
jen.
Just
so
you
know
your
your
connection
seems
to
be
a
little
unstable.
B
A
Yeah
not
sure,
if
there's
anything,
I
can
do
it.
If
it
becomes
a
problem.
There
is
a
theoretically
less
good
wi-fi
option.
I
could
try
if
the
more
good
one
becomes
less
good,
so.
B
A
Keep
we'll
see
how
it
goes
all
right.
So
in
the
last
week
we
do
have
one
a
new
contrib
module.
It
is
the
print
module,
so
the
print
module
for
drupal
was
ported
to
backdrop.
We
had
an
early
version
of
it
that
didn't
have
an
official
release.
A
I
don't
think,
and
then
in
drupal
the
print
module
became
marked,
unsupported
and
so
the
backdrop
team
was
collaborating
with
the
drupal
team
so
that
when
the
drupal
version
became
re-supported,
the
backdrop
version
now
also
includes
all
of
the
same
security
enhancements
that
are
in
the
drupal
version,
and
so
now
its
release
is
out
with
all
of
those
fixes
in
it.
So
for
the
backdrop,
I
think
it's
an
alpha
release,
but
there
is
a
new
release
field.
A
So
if
you
need
print,
you
can
have
it,
which
is
great
there
weren't
any
posts
in
the
forum
topic,
and
I
think
that's
because
when
I
checked
this
morning
instead
of
having
a
forum
topic
for
today,
we
had
one
for
next
week.
If
I
checked
next
week,
so
there
weren't
any
there
either.
So
if
anyone
did
have
anything
to
add
today
and
the
forum
topic
wasn't
there
earlier,
I
apologize
for
that.
I
have
also
now
added
form
topics
through
mid-september,
so
we
should
not
have
that
happen
again.
If
I
did
it
correctly.
A
So
sorry
about
that
also,
if
anyone
notices
the
topic
is
missing,
you're
welcome
to
create
one
for
that
week.
If
there's
something
very
important
you
want
on
the
agenda,
we
will
check
all
of
the
recent
topics.
A
Sorry
about
that.
I
did,
however,
work
on
a
issue
yesterday
that
I
think
I
would
like
some
feedback
on
it's
issue
number
4029
and
this
is
adding
a
user
account
comparison,
visibility
selection.
So,
if
you're
placing
a
block
on
a
page-
and
you
want
to
compare
two
different
user
accounts
so
like
am
I
looking
at
my
own
profile,
page
I'll,
compare
my
user
account
to
the
page,
I'm
looking
at
that's
the
most
common
use
case.
A
There
are,
of
course,
a
bunch
of
other
cases
where
you
might
want
to
compare
two
users
like
if
you
had
an
author
context,
and
you
want
to
know
if
you
were
the
author,
maybe
you'd
show
something
that
way.
So
we're
trying
to
figure
out
how
to
provide
a
user
interface
for
people
to
figure
out
how
to
specify
the
two
user
accounts.
That's
not
completely
confusing,
and
so
what
I
ended
up
doing
is
I
looked
tim
made.
Some
suggestions.
Gregory
made
some
suggestions.
A
They
all
looked
really
hard
to
implement,
based
on
the
current
selection
tool
that
we
have
now,
and
so
I
implemented
something
a
little
different
where
I
just
assumed
the
first
user
were
comparing
account
we're
comparing
two
is
always
the
logged
in
user
account,
and
so
I
could
reduce
the
number
of
questions
we're
asking
to
one,
so
it
basically
says
which
user
account
should
I
compare
to
the
currently
logged
in
user
and
I
think
it
makes
a
little
more
sense
the
way
it
is
now,
rather
than
asking
two
questions
that
are
really
similar,
that
the
person
doesn't
really
care,
which
one
is
which
anyway,
I
just
want
to
know
if
they're
the
same
or
not,
but
I
could
definitely
use
some
help
with
the
language
around
the
labeling
for
the
questions.
A
The
available
answers
for
the
questions,
the
description
text
for
the
block
once
it's
placed
on
the
page
and
then
the
end
result
is
a
a
rule.
That's
called
user,
compare
user
account
compare
and
that
might
also
want
to
be
updated.
If
it's
something
like
am
I
logged
in
or
not
or
I
don't
know
like,
there's
just
a
bunch
of
terminology
that
is
a
little
confusing
and
if
anyone
could
look
at
those
screenshots
and
identify
something
that
you
think
could
be
clear,
I
would
love
just
more
eyes
on
that.
A
So,
in
the
last
comment
on
that
thread,
there
are
two
screenshots
of
the
configuration
interface
and
the
description
text
on
a
block.
You
can
look
at
those
or
you
can
try
it
in
the
sandbox
and
see
what
it
feels
like
there,
but
I
think
it
makes
more
sense
than
it
did
before
and
it
was
easier
to
implement
than
better
suggestions.
C
I
think
that's
that's
pretty
clear.
I
like
the
screenshot,
the
last
one
that
that
you
have
there
in
that
issue.
I
think
it
makes
a
lot
of
sense.
My
only
question
was
you
changed
logged
in
to,
I
think
current
user
was
there
before
and
now
it's
locked
in
user.
You
know
someone
who's
not
knocked
in
is
is
an
anonymous
user
and
it's
a
current
user.
So
I'm
not
sure
if
this
comparison
also
applies
to
anonymous
users.
I.
A
Don't
know
if
it
would
apply
for
anonymous
users,
but
the
problem
with
current
is
that
it
can
be
the
currently
logged
in
user
or
it
can
be
the
current
page
you're
on,
and
so
I
had
a
hard
time
identifying,
which
current
was
current,
like
whether
it
was
the
currently
logged
in
one
or
the
currently
loaded
one
or
the
current,
whatever
like
there
could
be
any
number
of
currents,
and
so,
if
there's
another
word,
that's
more
specific,
I'm
open
to
those
two.
A
Yeah,
I
just
words,
are
hard,
I'm
not
sure,
there's
a
good
option
here
to
figure
this
out,
but
I'm
definitely
open
to
any
suggestions.
C
C
D
E
A
We
so
it
also
in
the
in
that
pull
request
changed
some
other
instances
of
current
user
to
logged
in
user
to
make
it
consistent,
but
those
were
all
around
access
checking
because
there
were
a
bunch
of
other
uses
in
the
layout
system
and
if
we
find
other
things
like
tokens,
do
it
better.
I
would
be
okay
with
changing
everything
to
be
consistent
to
match,
whatever
tokens
are
doing
or
if
we
find
that
whatever
we
land
on
for
this
one
is
better.
We
can
also
change
the
human
visible
labels
for
tokens.
A
We
obviously
can't
change
the
actual
token
values,
but
we
could
put
some
description
text
in
there
if
that
was
helpful
too.
So
I
I
like
consistency,
but
I
think
in
this
issue
we
have
an
opportunity
to
go
either
way
with
the
consistency.
F
C
A
We
could
also
just
call
it
the
currently
logged
in
user
everywhere
too.
It's
more
words.
E
A
A
Hey
we're
getting
nice
and
specific.
So
that's
what
I
wanted
right:
okay,
other
things
on
our
agenda
for
today,
that
was
the
only
open
q,
a
item
I
had
with
anyone
else
and.
E
I
was
going
to
suggest
I'm
going
to
share
my
screen,
really
quick
since
we're
talking
about
this
and
I'm
trying
to
give
feedback
on
the
fly,
which
is
a
little
bit
dangerous,
but
for
some
reason
this
middle
block
is
bothering
me
a
little
bit.
It's
confusing
me
and
I
think
it
would
be
possible
to
move
that
to
the
end.
So
you
see
your
current
user.
E
Then
you
see
okay
check
display
if
the
maybe
not
okay.
Maybe
I
need
to
just
play
with
this
before
I
try
commenting,
but
for
some
reason
that
middle
part-
I
I
do
like
you
know
in
general,
I
think
you're
under
to
the
right
solution,
but
I'm
still
a
little
bit
confused.
But
I
think,
though,
this
little
middle
box
is
still
going
to
confuse
people
a
little
bit
and
I
need
to
come
up
with
a
constructive
suggestion.
E
For
a
second
I
was
thinking,
and-
and
maybe
this
will
turn
out
to
be
okay
for
a
second.
I
was
thinking
to
just
move
that
to
the
end
would
help,
but
I
I
need
to
think
more
about
the
relationship
between
those
two
and
maybe
it
doesn't
just
because
I
thought
that
maybe
making
this
that
bottom
choice
would
help
me
understand
the
second
block,
but
I'm
not
sure
that's
true.
A
I
think
we
could
also
like,
because
the
options
and
the
bottom
block
say
the
same
as
the
logged
in
user
account.
We
might
not
need
user
account
to
compare
to
the
logged
in
user
account
as
a
label
that
might
just
be
a
little
overwhelming
or
if
it
was
like
user
account
to
compare
you're
like
okay.
This
is
the
one
I'm
comparing
to
and
your
two
options
are
like.
Is
it
logged
in
or
is
it
not
logged
in
that?
Might
it
might
be
more
clear
with
less
explanation.
A
But
yeah,
I
also
struggled
with
a
little
bit
of
the
order,
because
that
last
question
is
like
negate
or
not
that's
what
the
actual
question
is.
So
I
had
to
like
work:
rework
it
around
a
little
bit
to
try
and
make
it
match
the.
E
E
C
I
wanted
to
mention
also
there's
a
related
issue
that
I
did
some
work
on
yesterday
and
it's
the
ability
of
layouts
to
detect
whether
there
are
enough
contacts
for
or
visibility
condition,
for
example,
for
this
particular
visibility
condition.
You
need
two
users,
you,
if
you
don't
have
two
users.
This
should
not
appear,
for
example,
when
you're
viewing
the
home
page,
unless
you
actually
add
a
con
user
in
the
context
manually.
C
C
I
was
also
wondering
about
some
of
the
rtbc
issues
that
don't
have
milestones,
I'm
finding
that
I'm
not
sure
it's
taking
a
long
time
for
those
two
to
get
milestone.
Is
that
the
usual
procedure?
Or
are
we
supposed
to
be
actually
assigning
milestones
to
these?
Because
there
is
like
five
or
six
that
I've
done
recently
and
in
the
upsell
has
actually
reviewed
them,
and
a
couple
of
those
are
marked
rtbc.
But.
A
Something
gets
merged,
it
will
get
added
to
the
milestone,
it'll
be
released
in
so
when
it
gets
merged,
it'll
get
a
milestone
if
it
doesn't
have
one
already.
I
don't
know
if
all
core
committers
look
at
the
rtbcq.
Some
of
them
might
look
at
milestones
and
if
that's
the
case,
then
it's
likely
that
those
would
get
missed.
A
A
Yeah,
I
think
that's
true
for
all
whether
it's
a
a
new
feature
or.
A
New
feature,
it
would
also
need
a
advocate,
but
as
long
as
there's
two
people
on
that
issue,
it
can
go
into
the
milestone.
So
I.
C
E
Right,
I
see
okay,
any
two
people,
but
we
actually
on
the
milestone.
On
the
page.
We
say
that
we
have
an
exception
where,
if
something's,
right
rtpc,
so
this
is
bug,
fix,
release,
milestones
and
it
gives
the
criteria,
but
it
says
one
exception.
If
the
issue
has
a
pull
request
in
a
near
ready
state
that
has
earned
the
rtpc,
then
the
milestone
can
be
added
even
by
the
same
person
wow.
So.
D
F
F
A
A
I
said
in
order
for
an
issue
to
reach
rtbc,
it
means
that
a
second
person
has
to
look
at
it.
So
I
think
the
whole,
like
requirement
of
two
people
thing,
isn't
necessarily
about
who
adds
the
label
we're?
Not
just
we
don't
want
one
person
creating
an
issue
filing
on
pull
requests,
marketing
rtp's
putting
into
the
next
milestone
without
anyone
else,
which
some
of
us
might
be
tempted
to
do.
E
Yeah,
well,
the
other,
but
the
other.
Should
we
can
get
an
issue
into
the
milestone
too
without
being
rtbc.
If
you
know
two
people
agree
to
it,
that's
the
main
thing:
okay,
I'm
sorry
jen
you're
frozen
again.
A
Because
I
can't
tell
when
I
because
you
guys
don't
freeze
so
like
I
don't
know
what's
going
on
but
yeah,
I
don't
even
know
what
I
was
gonna
say
but
sounds
like
we've
got
it
covered.
I
think
so.
Okay,.
A
E
E
C
Right
there's
a
couple
that
are
related
to
views
handlers
and
then
one
related
to
layouts.
E
A
Should
I
try
moving
on
okay,
so
I
was
just
gonna
go
to
the
123
milestone.
We
have
a
couple
of
exciting
new
features
slated
for
123.,
first
of
which
is
entity
reference
module
last
week.
It
doesn't
look
like
it's
got
any
updates
since
last
week,
but
last
week
we
were
talking
about
it.
A
Looking
reasonably
close,
there's
a
lot
of
kind
of
crafty
old
code
in
there,
but
it's
all
working,
and
so
I
think
everybody's
indication
is
just
to
just
put
it
in
since
we
have
something
that's
working
and
we
can
clean
it
up
later
as
needed,
and
I
think
that
will
make
the
what
reference
module
do.
I
use
problem
much
easier
for
people
also
entity
reference
being
the
most
popular
contrib
module
and
drupal
7
will
make
it
a
lot
easier
for
people
who
are
upgrading
so
all
around.
E
Yeah,
yes,
I
agree
with
everything
you
said.
I
just
want
to
comment
on
a
personal
scenario,
which
is
we,
I
have
a
backdrop
site
admin
development
where
we
used
a
term
reference
field,
and
now
we
want
features
that
are
specifically
available
in
entity
reference
on
a
new
field
and
it
seems
weird
to
have
both
of
them
going.
E
So
I
asked
this
question
and
I
think
archie
channel's
already
checked
in
on
it
in
the
forum,
which
is,
if
I
you
know,
add
a
if
I've
got
a
bunch
of
the
this
is
an
upgrade
site.
So
the
the
term
reference
field
is
from
seven
and
so
there's
all
of
this
term
reference
data,
and
so,
if
we
add
an
entity
reference
there,
if
we
add
the
entity
module
and
we
do
the
upgrade,
is
there
not
actually,
maybe
it's
easier
to
upgrade
it
from
drupal
or
maybe
not?
E
I
don't
know
I'm
not
necessarily
looking
for
an
answer
on
this
call
or
this
meeting
today.
If
anybody
has
a
recommendation,
I
think
rj
piano.
You
pointed
me
towards
that
that
that
module,
which
is
designed
to
port
data
from
an
existing
backdrop
site
a
node
or
a
user
reference
given
entity
reference,
and
I
think,
there's
a
there's.
A.
E
Or
possibly
robert,
I
don't
know,
but
there's.
Apparently
there
is
a
module
which
ports,
user
and
node
data
into
entity
reference,
but
there's
a
lack
of
clarity
on
whether
or
not
it
works
for
term
reference.
A
I
have
done
that
before
tim
in
a
custom
update
hook.
E
A
I
could
send
you
you
need
to
know
like
the
field
names
of
the
old
one
in
the
new
one,
but
it
would
basically
allow
you
to
create
a
new
field
with
a
new
field
name
and
then
migrate.
The
data
from
the
old
field
into
the
new
one,
and
it
was
a
term
reference.
It's
now
any
reference,
if
you
have
all
the
same
data,
but
just
keep
in
mind
that
there's
a
lot
of
features,
you
don't
get
from
any
reference
that
you
do
get
from
term
reference.
A
E
A
Yeah,
there's
there's
benefits
to
each
that
we
don't
have
in
both
yet,
but
we
do
have
a
long-term
plan
to
make
sure
that
everything
gets
into
entity
reference.
So
I
think
moving
any
reference,
isn't
the
wrong
move,
but
I
would
say,
because
it's
not
there
yet
just
make
sure
you
don't
need
any
of
the
user
interface
stuff
for
terms
that
we
don't
have
ready
for
entities.
A
Yeah
they
will
because
term
reference
is
going
to
stay
in
core
for
a
while
until
we
get
all
the
stuff
we
need
in
any
reference
and
right
now
you
know.
Obviously
there
are
plenty
of
drupal
7
sites
running
and
be
referenced
with
term
references,
also
because
that's
been
in
core
for
forever,
so
there
shouldn't
be
any
problem
having
them.
C
And
even
I
was
looking
a
little
bit
into
entity
reference
and
it
has
a
selection
handler
that
allows
you
to.
If
you
refer
to
taxonomy
terms,
it
will
actually
save
in
the
correct
table.
So
if
you
do
update
to
a
taxonomic
term
that
will
actually
be
modified
in
the
table
itself,
so
there
it
has
a
specific
handler
for
taxonomic
terms.
So
I
don't
you
know,
I
think
it's
there's
a
lot
of
flexibility
there.
Okay,
that's
great.
E
Well,
I
think
we're
going
to
be
getting
a
lot
of
these
questions.
If
we
once
we
make
this
move
a
lot
of
people,
so
we
might
want
to
do
a
a
little
special
faq
or
something
about
enemy
reference
once
we
move
it
into
core
to
just
save
a
lot
of
answering
the
same
questions
over
and
over.
A
All
right
anything
else
on
a
reference
there's
a
sub
issue
here
related
issue
5633
to
separate
out
term
reference
since
we're
talking
about
term
references
from
taxonomy
module.
So
that's
been
a
part
of
taxonomy
for
a
really
long
time.
A
B
A
Right
now,
without
the
separation,
you'd
have
to
turn
off
taxonomy
in
order
to
get
rid
of
that,
which
means
you'd
lose
your
term
references
anyway,
and
so
this
will
just
separate
the
ability
to
have
the
reference
field
separate
from
the
taxonomy
system
as
a
whole.
So
it
sort
of
makes
sense.
E
Good,
so
somebody
had
come
up
with
a
bug
in
the
entity
reference
and
I
think
we
were
deciding
whether
or
not
that
was
significant
enough
to
slow
us
down,
but
did
that.
I
think
I
saw
a
pull
request
come
in
it's
right.
C
There
there
were
three
pull
requests
that
hurdle
merged
in
the
last
week
or
so,
but
I
don't
think
those
changes
were
actually
pushed
into
the
pr
that's
currently
sitting
there
for
backdrop.
C
Yeah
and
those
those
were,
I
think
one
of
them
was
related
to
migrated
or
upgraded
sites
from
drupal
7..
There
was
some
legacy
stuff
there
that
needed
to
be
fixed
and
the
other
two
were
because
you
know
the
entity.
Reference
in
backdrop
doesn't
use
c
tools,
so
he
whoever
supported
this,
actually
adopted
that,
and
so
there
were
a
few
cases
that
were
not
that
were
kind
of
overlooked.
C
That
produced
some
notices,
php
notices-
and
I
discovered
it
when
I
was
working
with
organic
groups,
because
organic
groups
uses
entity
references
and
defined
some
handlers.
C
A
I
have
a
first
draft
of
a
pull
request
that
gets
field
group
module
in
core
and
it
does
one
small
user
interface
improvement
and
it
takes
the
button
for
configuring,
your
field
group
and
turns
it
into
a
drop
button
for
configuring
it
and
it
behaves
more
like
a
field
setting.
So
if
you
click
the
configure
link,
it
goes
to
a
separate
page
and
asks
you
for
all
of
the
settings
on
your
field
and
then
you
click
save,
and
it
takes
you
back
to
the
first
page.
A
It's
your
field
listing,
which
is
how
a
field
would
behave,
field
group
previously
just
sort
of
shoved
the
form
directly
into
that
page.
So
it
was
a
very
different
user
feel
than
the
rest
of
field.
So
I
made
it
feel
more
like
the
rest
of
fields,
but
there's
still
a
lot
that
could
be
done
to
improve
and
the
main
question
I
have
is
on
this
ability
to
clone
a
field
set.
A
It
adds
a
vertical
tab
to
the
bottom
of
the
field,
ui,
which
is
a
little
overwhelming
and
gives
you
the
ability
to
clone
a
field
group
from
a
different
content
type
or
a
different
view
mode
onto
the
one
you're
looking
at.
So
it's
not
like
we
could
at
I
mean
so.
The.
A
You're
on
the
basic
page
and
you
click
clone
field
group,
and
it
says
which
content
type
do
you
want
to
clone
this
to,
and
you
can
say
I
want
to
clone
it
to
post
and
then
it
will
put
it
over
there,
but
I
think
the
way
it's
set
up
right
now
or
if
you're
on
the
post
type
and
you're
like
I
want
a
field
group
and
it
says
which
one
do
you
want
you
can
choose
basic
page
makes
a
lot
more
sense.
A
We
just
need
to
figure
out
a
better
interface
for
adding
that
that
isn't
a
vertical
tab
on
the
bottom
of
the
field.
Ui
and
there's
a
couple
of
recommended
solutions
in
the
pull
request.
One
of
them
is
adding
an
action
link.
That
says,
add
field
group
which
I
think
sounds
good
and
then
the
question
is
how
much
of
that
do
we
want
on
field
group
before
it
goes
in
core,
so
what
we
could
do
is
pull
off
the
clone
option
and
move
the
whole
thing
to
another
issue.
A
That's
like
added
back
in
a
way
that
makes
more
sense
or
we
could
put
it
in
the
way
it
is
now
and
have
the
second
issue
be
fix
it
to
make
it
make
more
sense,
or
we
could
say
we
really
wanted
to
make
sense
before
it
goes
in
and
we
don't
want
to
lose
the
feature
and
we
try
and
do
that
now.
We've
got
you
know
some
time,
so
we
could
try
that
and
we
and
greg
had
a
pretty
good
outline
of
a
workflow
for
what
that
might
feel
like.
C
A
Well,
right
now
we
have
different
people
working
on
one,
so
I
think
it's
okay.
If
all
of
a
sudden,
I
I
needed
an
editing
reference
and
herb's
needed
on
field
group
which
could
happen
at
any
moment.
I
think
harp
is
the
current
maintainer
for
the
field
group
contrib
module
too.
So
there's
a
lot
of
crossover.
A
E
Yeah
I
mean
we
should
clarify
to
rg
piano
that
that
slighted
simply
means
that
that
we
aspire
to
getting
it
there.
Some
sometimes
things
are
slated
for
three
or
four
minor
releases
before
they
actually
get
finished,
and
we
don't
consider
that
to
be
a
you
know,
an
awful
thing
right
when
we
make
a
commit.
You
know
when
we
add
something
to
a
milestone.
That
doesn't
mean
that,
like
we're
putting
a
really
high
expectation
that
it
gets
in
there,
it
just
means
we're
trying
right
and
hopefully
hopefully
it
will.
A
And
I
do
think
entity
reference
should
take
priority.
If
we
had
to
choose.
I
think
it's
more
important,
but
hopefully
we
don't
have
to.
E
It
does
make
for
a
pretty
exciting
release
if
we
got
both
of
these
new
features
in.
I
think
we
should
plan
a
big
press
release.
A
All
right
and
then
our
last
issue
is
allowing
an
administrator
to
hide
the
title
on
comments.
This
issue
45-69.
A
We
think
this
one
is
currently
stuck
awaiting
core
committer
feedback,
just
to
look
at
the
two
proposed
options
and
make
sure
they
are
both
viable
because
if
one
of
them
was
not,
we
would
just
go
with
the
other.
D
Yeah,
and
and-
and
I'm
just
wondering
like
what's
what's
sort
of
the
philosophy
is:
is
it
that
the
core
change
shouldn't
override
what
the
contrib
module
does
or
do
we
need
to
tell
control
module
users
you
need
to
with
this
for
change?
You
need
to
stop
using
this
and
re
redo
your
configuration
core
solution.
How
is
that
done?
It.
A
A
It
would
notice
the
contrib
module
was
being
run
disable
it
check
the
settings
and
copy
the
settings
into
the
core
so
that
when
it
was
done,
the
module
would
be
disabled
and
your
site
would
be
functioning
exactly
the
same
way.
It
was
before
now.
That's
only
possible
if
the
exact
same
feature
that
was
in
contrib
got
moved
into
core
in
the
same
way.
I
don't
know
tim.
A
If
that's
what's
happening
or
not,
you
would
know
more
than
I
would,
but
it's
often
that
there
are
a
lot
of
settings
that
the
contrib
module
provides
and
we
only
move
a
subset
of
that
directly
into
core,
and
in
that
case
the
module
would
need
to
handle
that
gracefully,
because
we
don't
want
to
turn
it
off
entirely.
In
case
people
want
in
all
the
rest
of
the
settings,
we
would
just
need
to
figure
out
some
way
that
it
would.
You
know
we
test
it
ahead
of
time.
A
Make
sure
your
site
doesn't
explode
after
you
do
the
update
and
then
it
would
either
set
some
kind
of
a
message.
That's
like
you
might
want
to
use
the
course
setting
instead,
or
you
know,
this
setting
is
deprecated
check
the
course
setting.
However,
the
maintainer
wants
to
handle.
It
would
would
be
fine,
and
I
don't
know
what
that
would
be
if
it's
possible
to
have
both
on
at
the
same
time
or
if
they
need
to
get
each
other.
I
would
have
to
look
at
it
more
specifically,
but.
D
A
And
we
do
have
a
a
list
of
kindred
modules
in
core
that
already
handle
this,
because
we
did
it
with
a
bunch
of
stuff,
as
it
moved
into
course.
So
we
just
need
to
make
sure
that
your
module
gets
put
into
that
list
so
that
it
knows
to
turn
it
off
and
then,
if
there's
a
setting
that
needs
to
be
renamed
or
moved
to
a
different
file
that
would
handle
in
that
update
hook.
Also.
E
Honestly,
I
haven't
thought
at
all
about
this,
yet
I
mean
I
think
I
started
started
with
your
your,
the
the.
I
think
you
you're
maintaining
a
drupal
port
of
a
module,
and
I
think
we
looked
at
that
code.
It
has
changed
somewhat
and
we
have
changed
the
settings
options
a
little
bit
in
a
way
that
I
don't
think
is
in
that
module.
But
I
don't
know
if
it's
in
a
way
that's
incompatible
at
all.
I'd
have
to
look
and
see
right.
C
I'm
looking
robert
your
module,
basically
just
wipes
out
the
title.
Just
yeah
makes
it
an
empty
string.
Basically,
I
think
jim,
that's
how
you
start
it
yeah.
C
Readers,
I
think,
and
just
having
the
screen
reader,
you
know
having
empty
html.
C
D
Think
the
chord
change
is
way
better
than
the
module
so
yeah
just
how
to
gracefully
do
the
transition,
but
I
yeah
that's
why
I
think
the
module
what
the
module
did
is
a
subset
of
what
the
core
would
do
now.
Okay,
it
should
make
it
easy.
Yeah,
yeah.
E
Well,
if
you,
if
you
are
willing
I'll,
take
a
look
at
both
and
if
you're
willing
to
weigh
in
on
the
issue,
it
would
be
helpful
to
have
a
few
more
voices
because
yeah
jen
and
I
are
losing
and
you
can
help
us
lose
or
you
could.
A
I'm
going
to
add
an
update
to
the
minor
minor
release
checklist
to
review
the
list
of
kindrip
modules
included
in
core.
So
we
don't
accidentally
forget-
which
I
think
we've
done
in
the
past,
so
just
reminding.
D
E
C
A
A
E
The
the
the
little
project
I've
been
working
on,
which
I
don't
know
if
you've
had
a
chance
to
look
at
china,
but
excuse
me-
and
you
may
have
some
strong
feelings
about
this.
So
I'd
like
you
to
at
least
think
about
it
and
get
back
to
me.
I
went
ahead
and
set
up
this
site
the
original
idea
that
the
the
the
impetus
is
that
I
find
it
one
a
little
bit
hard
hard
to
sort
of
search
and
maintain
and
compare
projects
with
releases
and
those
without
releases.
E
It's
like
navigating
through
unreleased
modules
on
github
is
a
bit
more
of
a
challenge
than
it
is
on
backdrop.org.
The
backdrop.org
has
limited,
only
has
the
release
modules.
Also
things
like
we
don't
track
maintainers,
and
things
like
that.
So
I
was
experimenting
with
what
we
could
do
with
the
api
and
I
set
up
sort
of
a
site
and
I
pulled
in
all
of
the
projects
from
github
with
some
help.
E
I
got
some
great
code
from
vfu
panda
and
basically
have
a
list
of
all
of
the
projects
in
github,
and
this
is
sort
of
related,
and
I
start,
but
there's
really
no
good
way
that
I
can
think
of
that.
I'm
open
to
ideas
to
scrape
the
maintainer
data,
so
I've
been
manually
adding
it
with
a
little
bit
of
help
from
some
other
people,
and
I've
got
200
projects
already
of
the
926
projects.
E
My
motives
here
are
really
just
experiment
and
play
with
this.
This
could
stay
an
independent
site.
Some
of
these
features
might
once
we
play
with
it.
We
might
decide
what's
important
and
pull
that
into
backdrop.org.
E
I
don't
think
we'd
want
all
of
this
for
sure
in
backdrop.org,
but
this
is
a
good
way
to
just
sort
of
play
around
and
experiment
with
it.
So
I
welcome
people
to
take
a
look
at
it
and
get
back
to
me.
You
know
it
it.
It
does
give
us
the
ability
to
see
things
like
you
know,
have
a
complete
list
of
all
the
different
maintainers.
We
have
and
see
how
many
different
modules
are
you
piano,
so
some
people
are
getting
underrepresented
based
on
the
ones
I've
I've
done
so
far.
E
Other
other
people
well
indigozala
jumped
in
and
helped
out
tag.
Her
so
and
nicozella
has
a
whole
ton
of
projects
because
she
went
and
helped
take
hers.
So
she's
got
36
projects
that
she.
A
E
So
if
you
log
in
you'll
be
able
to
edit
any
of
these
notes,
the
maintainer
field
also,
I
created
I'm
not
sure
if
I
want
to
keep
this
a
community
tags
field,
which
is
just
arbitrary
tags
that
anybody
can
put
in
for
a
project
and
that
may
or
may
not
be
helpful
in
the
end,
we
do
have
tags
in
the
dot
info
files,
but
one
of
the
one
of
the
you
know
so
few
projects
have
used
them.
E
A
E
Right
so
I
think
we'll
be
able
to
use
this
data
in
a
lot
of
interesting
ways.
You
know
once
we
kind
of
have
it
together
and
I
just
love
for
people
to
take
a
look.
You
know
right
now.
I
did
I'm
playing
with
a
feature
where
people
can
favorite
cam
log
in
and
favorite
their
favorite
modules,
whether
or
not
we
keep
that.
E
I
don't
know,
but
I
I
like
to
just
you
know
once
I've
got
this
data
in
here,
it's
fun
to
experiment
with
different
features
and
and
see
again
whether
or
not
this
stays
its
own
site
or
whether
or
not
you
know
like
that.
I
just
managed
because
the
community
doesn't
want
to
take
on
the
overhead
of
managing
a
site
like
this.
That's
one
option,
but
I'm
happy
any
of
the
data
that
we
wanna
or
or
features
that
like
seem
really
valuable
here,
that
we
wanna
pull
back
into
backdrop.org.
We
can.
A
E
E
That
we
will
now
be
able
to
see
clear,
but
you
know
I'm
running
into
interesting.
Examples
like
there
are
a
few
projects
that
that
well,
I
found
at
least
one
project-
that's
completely
empty,
and
there
have
been
some
projects
that
have
been
deprecated
and
having
a
list
like
this
will
give
us
the
ability
to
to
maybe
more
productively
figure
out
what
to
do
with
some
of
those
projects.
E
E
I
did
not
use
the
github
project
feed.
Basically,
the
quick
history
is,
I
opened
an
issue
in
the
backdrop.org
issue
a
couple
months
ago
saying
that
we
should
have
a
feed
of
of
all
the
data
we
have
and
bw
panda
said.
Well,
we
can
get
anybody
can
get
that
data
already
from
github
yeah
and-
and
he
gave
me
a
code
snippet
that
he
had
actually
worked
out,
which
actually
gets
it
directly
from
the
the
github
feed
without
using
the
module.
I
discovered.
A
E
If
you
were
just
getting
right,
so
I'm
getting
it
directly
with
with
the
code
and
I've
modified
the
code
quite
a
bit.
But
this
is
a
direct
request
of
github
not
using.
There
is
a
github
api
module
for
background,
which
I
discovered
as
part
of
working
on
this
project
like
oh.
What?
What
is
this
module
here
and
I
think
that's
the
module
that
was
developed
for
core
yeah
or
for.
A
The
first
one
would
allow
you
to
write
to
github,
which
I
don't
think
you
need
for
this
purpose
but
like
if
you
wanted
to.
You
know
like
what
we
do
is
package
the
releases
and
attach
that
to
the
github.
So
that's
where
you
need
the
api
access
you
have
to
like
prove
who
you
are,
but
just
pulling
the
data
in
a
from
a
public
feed.
I
think,
is
exactly
what
you
need
here.
So
I
think
this
is
great
yeah.
E
Yeah
and
I'm
able
to
get
quite
a
bit
of
data,
not
everything
I
wanted
things
like
the
number
of
releases
is
not
in
the
main
feed,
so
you
have
to
do
a
secondary
call
to
the
releases,
and
then
I
have
you
know
it
doesn't
even
in
that
it
doesn't
have
the
total,
so
you
basically
just
have
to
total
them
up,
and
so
I'm
interested
in
things
that
people
would
like
me
to
parse
out.
There's
a
few
things
like.
E
I
would
like
to
show
the
the
latest
release
or
should
be
part
of
this
or
well.
I
I
right
now
right
now,
for
example,
the
releases
is
it's:
either
you
have
some
releases
or
you
don't
so
the
assumption
is
anything
with
some
releases
is
on
backdrop.org,
but
that's
not
actually
true,
because
again
that
we
do
have
these
modules
that
have
been
deprecated.
So
there
might
be
modules.
A
A
D
But
yeah
most
of
my
modules
started
as
alpha
and
beta
I
mean
because
I
and
I
waited
for
people
enough
people
to
download
them
from
backup.org
and
I
verified
they
were
there.
A
So
we
decided
not
to
do
that,
because
we
didn't
want
someone
to
install
something
that
was
going
to
make
their
site
explode,
using
a
tool
that
they
had
no
ability
to
undo.
So
we
decided
alpha
and
beta
weren't
safe
and
it
had
to
be
in
whatever
format,
but
I'm
not
sure
we
ever
actually
like
added
anything
to
the
site.
To
stop
that
from
happening.
I
think
we
might
thought
might
have
thought
that
would
happen
just
from
the
format
of
the
module.
D
That
the
behavior
you
described
is
present,
if,
if
you
have
a
because
we
ran
into
this
very
recently,
if
you
have,
let's
say
version
1.1.,
you
know
1.1,
and
then
you
create
a
1.2
alpha
and
release
it.
It
doesn't
show
up
as
the
recommended
release
on
what
tim
is
showing.
Now
you
won't
see
the
the
higher
numbered
alpha
release.
You'll,
see
the
the
lower
numbered
stable
release,
because
that
situation
arose
just
within
the
last
month.
I'll
say.
E
A
No,
it's
supposed
to
be
the
same,
because
you
can
install
a
module
from
backup
cns.org.
Even
if
you
don't
you
can't
anymore
yeah,
I
don't
know,
maybe
that
maybe
I'm
not
sure
we
should
change
it,
because
it's
now
people
are
probably
used
this
way.
But
I
wonder
if
putting
that
limitation
into
the
installer
and
not
on
backup
cms.org
might
be
a
better
way
to
fix
it.
So
we
don't
have
to
change
backups
to
work,
but
yeah.
That's
interesting!
Another.
E
Thing
that
the
more
I
play
with
this,
the
more
I
realize
that
we
need
to,
I
think
it's
really
valuable
to
have
released
and
unreleased
modules
available
in
one
place,
but
we
need
to
be
really
clear
about
which
ones
aren't
released,
so
that
people,
because
some
of
them
are
just
plain
broken
and
we
might
find
a
way
to
flag
those
like
ones
that
don't
work
at
all,
don't
even
bother
to
try
this
there's
others
that
will
work
but
they're.
E
A
I
kind
of
after
seeing
this
time
that
makes
me
want
those
on
backdrop,
statement,
stainless
steel
but
like
in
a
different
area,
so
you
can't
just
search
for
modules
and
find
it.
There
would
also
be
some
sidebar
thing.
That's
like
we
might
have
an
unsupported
version
of
this
module
and
then
you
go
into
some
other
area
of
the
site.
That's
like
these
are
all
potentially
dangerous,
but
you
can
find
everything
there.
I
don't
know
what
it
feels
like
could
be
really
valuable.
A
E
Great
okay,
I
think
the
big
question
that
is
is
do
we
want
to
do
something
to
more
officially
track
their
maintainers
like
should
that
be
part
of
the
dot
info
file
or
something.
A
Yeah,
well,
we
have
it
on
github.
We
just
haven't
figured
out
how
to
get
it
right
off
of
github
right
like
we
know
who
created
each
release
right,
we
could
tag
even
each
release
with
its
individual
maintainer.
If
only
we
could
get
that
data
out
and
I'm
sure
it's
there
somewhere
and
we
probably
can
get
it
out.
We
just
haven't.
A
Or
maybe
only
one
of
them
ever
cuts
early
yeah
we
did
have.
I
think
this
was
in
the
issue
for
adding
more
information
to
the
info
file,
but
yeah.
We
also
have
the
like
human
versus
machine
name
thing
too
right
where,
like
we
want
the
github
username,
so
that
we
can
do
like
the
single
sign-on
thing,
but
we
also
need
the
human
readable
name
like
if
we're
going
to
list
a
maintainer
would
be
nice
could
link
that
to
their
profile.
A
G
E
Okay,
that's
it
so,
please
folks,
kick
the
tires,
feel
free
to
log
in
and
play
with
it
and
give
me
suggestions.
C
A
E
E
If
people
have
ideas
that
know
more
about
that
than
me,
let
me
know
like
how
you
know
what
the
best
way
to
do.
Searches
on
a
site
like
this
would
be
right
now,
I'm
just
using
views
filters.
A
E
E
E
I
don't
know,
and
maybe
that
we
would
put
the
tags
into
that
as
well.
Then
I'm
kind
of
debating
how
to
handle
tags
because
I
think
having
a
free
tagging
option
is
nice
because
so
few
are
tagged,
but
then
there's
some
duplication
there.
So
I
don't
know
if
I
should
just
automatically
pull
in
the
the
dot
info
tags
into
the
free
tag
or
whatever
also
we
have
project
type,
which
is
in
a
way
like
a
tag
I
don't
want
to
have
to
you
know
the
themes
on
this
side.
E
E
E
E
No
but
unfortunately,
I'm
using
the
same
tags
field
for
the
community
and
the
dot
info
tags,
I'm
not
showing
the
dot
info
tags,
but
the
data
is
here.
The
project
type
is
its
own
taxonomy,
and
maybe
that
was
a
mistake.
Maybe
I
should
have
made
that
used
to
say
that
maybe
that's
what
I'll
do
that
might
solve
the
problem
is,
if
the
the
you
know,
it's
there's
only
three
tags
in
the
project
type,
the
vocabulary
and
all
three
of
them
could
legitimately
be
community
tank.
So
why?
Why
did
I
do
that?
That
stuff.
A
So
I
think
it's
still
still
valuable
to
have
those
separate,
but
you
might
also
add
the
data
into
the
community
tags
field
too.
Well,.
E
E
Well,
I
I
didn't
before
it
just
occurred
to
me
now
that
I
could
that
that
might
work.
A
A
All
right,
I'm
going
to
have
to
run
okay,
but
very
cool
project
tim.
Thank
you
for
sharing
that.