►
From YouTube: Backdrop Weekly 10/9
Description
Backdrop CMS
A
Alright,
we
are
on
air,
happy
Thursday,
everybody.
There's
this
backdrop
day
happy
backdrop
day.
We
are
here
to
talk
to
you
today
about
backdrop
CMS,
which
is
a
comprehensive
content.
Management
system
for
people
are
particularly
concerned
about
their
budgets,
so
that
would
be
small,
medium
sized
business
nonprofit.
A
Maybe
some
education,
because
Drupal
8
is
going
to
be
very
big,
expensive
enterprise
system
that
can
do
a
whole
lot
of
things,
but
they're
going
to
be
some
people
who
need
a
cheaper,
more
affordable,
lighter
weight
solution
and
we're
trying
to
take
Drupal,
7
and
move
it
forward
to
that
place
that
that
will
work
for
people
who
need
it.
The
lightweight
alternative
to
trip
late
so
backdrop,
CMS,
is
a
fork
of
Drupal
early
Drupal
8,
with
some
things
simplified.
A
Our
long-term
goal
is
to
created
a
tool
that
is
comparable
in
terms
of
features
with
Drupal
8
and
run
on
architecture.
That's
more
similar
to
that
of
triple
seven
while
creating
that
product.
We're
also
going
to
be
fixing
bugs.
So
those
webs
that
were
identified
in
Drupal
7,
as
well
as
fugg,
have
been
identified
in
Drupal
8
and
once
that
we
have
found
ourselves
and
simplifying
existing
systems
so
when
it
doesn't
require
changing
the
APA's
too
much
to
do
so.
A
We're
going
to
be
decreasing
the
abstraction,
increasing
the
performance
and
trying
to
make
the
system
makes
a
little
bit
more
sense.
We're
also
gonna
be
adding
new
features,
so
perhaps
some
of
the
triple-eight
doesn't
have
that
we
find
the
community
needs,
we'll
add
those
in
as
well
as
long
as
it
doesn't
require
a
very
much
a
change
to
do
that
as
well.
A
We're
hoping
to
release
back
to
at
one
point,
0
point
0
this
fall,
so
that
is
very
soon
and
what
the
first
release
will
be
is
just
a
working
version
of
the
product
that
contains
some
of
the
things
that
we're
working
now.
Let's
talk
about
that
later
and
then
after
the
first
version
is
released,
will
continue
to
iterate
and
release
new
versions.
Every
quarter,
so
we'll
have
bug
fixes
as
needed,
and
then
we'll
have
minor
versions
come
out
and
those
minor
versions
can
also
contain
new
features.
A
So
we
don't
have
to
get
to
a
completely
comparable
system
in
the
first
version
of
backdrop,
because
will
continue
to
iteratively,
add
new
features
as
time
goes
on,
which
is
great
in
terms
of
what
we're
working
on
right
now.
We've
got
three
major
issues
which
are
release
blockers.
The
first
is
the
one
I'm
most
excited
about:
that's
the
blocks
and
layouts
initiative.
This
is
something
that
was
taken
on
early
in
the
Drupal
8
cycle
and
dropped
because
of
the
complexity
required
and
getting
it
to
happen.
A
B
Sure
so
visually
things
are
about
where
they
have
been
from
our
demo
a
couple
weeks
ago.
If
you
visit
our
YouTube
page,
then
it
will
probably
be
the
fourth
video
down
after
this
live
stream.
There's
a
demo
of
the
layout
module
in
action
and
things
are
pretty
much
exactly
as
their
demonstrated
in
that
video.
But
since
then,
we've
been
doing
a
whole
bunch
of
work.
You
know
sorry
tightening
up
the
ship
a
little
bit
and
making
it
so
that
everything
works
and
functions
correctly.
B
We
had
a
couple
users
download
and
try
out
layout
module
from
my
branch,
which
is
super
appreciated.
Thank
you
very
much,
specifically
BW
panda.
Thank
you
for
the
excellent
reporting
on
on
the
problems
that
you
encountered
last
week
and
the
week
before,
we
are
saying
that
the
biggest
holdup
was
automated
testing.
But
at
this
point
we
completely
updated
all
of
our
automated
testing
and
so
now
everything
that
block
module,
tested,
we're
testing
all
of
that
and
more
in
layout
montreux.
B
At
this
point,
it's
it's
one
of
the
more
comprehensively
tested
systems
in
backdrop
as
it
should
be.
Considering
it's
it's
brand
new.
It's
likely
to
be
buggy
and
things
like
that,
but
we
really
super
comprehensive
testing
at
this
point.
Checking
conditions
of
writing
pads,
creating
menu
items,
testing
those
menu
items,
work
correctly,
positioning
contexts.
All
of
that
all
that
jazz.
So
we're
we're
pretty
well
all
good.
B
Let's
see
we're
pretty
much
pull
request
ready
at
this
point.
I
think
I'm
still
reviewing
the
code
to
see
that
I'm
not
missing
anything
I
documented
just
early
today.
The
numerous
API
changes
that
that
this
will
have,
because
it
I
mean
blocks,
touch
on
a
lot
of
things
for
sure
and
and
we're
changing
a
bunch
of
stuff
which
is
you
know,
one
of
the
things
that
we're
trying
to
avoid
is
unnecessary
change,
but
the
the
reward
for
this
change
is
so
dramatic
that
it's
it's
going
to
be
well
justified.
B
So
that
doesn't
mean
that
we
don't
need
to
document.
However,
so
I've
been
working
on
on
making
sure
that
I
don't
leave
out
any
API
changes
that
this
causes.
So
that
issue
is
issue
86,
as
always
in,
in
the
backdrop
issue
queue
on
github.
If
you
want
to
follow
along
or
try
it
out,
we'll
probably
see
the
first
pull
requests
here,
maybe
by
tomorrow,
sometime
next
week
at
the
latest
and
we're
hoping
for
a
merge
sometime.
B
You
know
in
the
near
future
in
the
next
week
or
two
assuming
that
we
don't
find
any
more
problems
at
the
very
least
like
we're,
just
in
really
really
good
shape.
I
feel
like
we're
really
good
for
a
first
pass.
Oh
speaking,
of
first
pass,
I
made
a
follow-up
issue
with
a
whole
slew
of
follow-up
tasks.
Creating
new
blocks,
adding
token
support,
custom
text,
support
finishing
up
a
whole
bunch
of
to
do
is
in
the
code
virgins.
B
B
So
if
you're,
upgrading
from
Drupal
7
using
the
Bartik
theme,
all
of
your
all
of
your
blocks
get
moved
over
into
the
new
layout
system,
with
a
Bartok
like
why,
if
you're,
using
something
else,
there
are
capabilities
to
make
it
so
that
your
theme
would
map
to
a
particular
custom
layout
during
the
upgrade
path
and
that's
actually
tested.
We
actually
have
test
for
that
as
well,
but
about
how
that
actually
will
work.
B
A
So
other
thanks
for
working
on
that
are
also
release.
Blockers
is
the
config
management
system,
so
this
it
gives
us
an
ability
to
store
configuration
someplace
other
than
our
database.
The
content
goes
in
the
database.
The
configuration
will
go
into
files
and
then,
when
you
want
to
deploy
a
new
feature
to
your
site,
you'll
just
take
those
configuration
files,
move
them
into
your
staging
directory
on
the
live
site
and
then
import
them,
which
is
great.
We've
got
the
subsystem
in
already.
A
We've
got
a
couple
of
other
systems
in
Drupal
using
config
management,
already
I'm,
sorry
backdrop,
but
we
have
a
couple
of
major
parts
of
backup
that
are
yet
using
config
management,
most
notably
content
types
and
fields,
and
if
you
don't
have
content
types
and
fields
using
cmi,
you
don't
really
have
cmi.
So
we
need
to
get
those
done.
Definitely
before
we
can
release
and
then
there's
a
bunch
of
other
smaller
systems.
We
also
need
to
get
moved
over
the
variables
we've
got
most
of
our
variables
converted,
but
there's
a
handful
left.
A
Some
of
them
need
to
be
turned
into
States
and
someone
who
need
to
be
turned
into
can
fake,
we'll
figure
that
out
as
we
go
through
those-
and
that
is
a
big
sticky
point
remaining
for
us.
So
if
anyone
wants
to
work
on
see
mine
or
see
how
backdrop
is
handling
CM
I
will
of
your
help
on
those
issues
and
the
other
thing
which
is
less
of
a
release.
A
Blocker
is
the
views
in
core
movement
thesis
the
number
one
contributed
module
in
Drupal
7
and
we
we've
put
the
views
itself
in
core
the
views
module,
but
there's
a
bunch
of
things
in
for
the
generate
lists
of
stuff.
It
could
use
views
and
I
know.
We've
had
a
bunch
of
work
not
lately
with
people
generating
some
use
for
us,
but
it
will
be
good
to
get
all
of
those
things
converted
to
use
before
we
ship.
A
B
B
A
B
A
Yeah,
so
we've
got
a
couple
of
things
that
I'll
my
plate
there
I'm
at
and
then
there's
some
other
stuff
that
we're
working
on
in
backdrop
as
well,
most
importantly,
keeping
up
with
what's
going
on
in
the
Drupal
world.
So
anything
that's
been
committed
to
the
latest
version
of
drooping
or
also
needs
to
be
committed
to
backdrop.
As
long
as
we
decide,
we
want
that
changed
most,
notably
the
important
ones
there.
The
security
fixes
straight
when
there's
a
security
problem
with
Drupal.
We
need
to
make
sure
the
same
solution
or
similar.
A
Another
solution
to
the
same
problem
exists
for
backdrop
and
then
other
things
are
little
user
interface
improvements
and
you
know
other
bug
fixes
that
go
into
seven.
We've
got
to
get
those
in
fact
up
as
well,
so
that
we're
not
behind
where
drupal
7
is
and
then
we
also
have
a
sub
lists
of
all
the
changes
that
are
going
on
in
triple
eight,
the
ones
that
we
think
are
most
important
to
get
into
the
first
version
of
backdrop:
we've
got
in
sub
meta
issues,
we've
got
two
that
are
left.
That
needs
some
attention.
A
There
is
the
issue
that
includes
all
of
our
HTML
5
l.
We
want
to
make
sure
backdrop,
is
responsive
and
mobile
friendly
out
of
the
box.
So
there's
a
couple
of
those
remaining
and
we
also
have
a
little
clean
up
on
our
JavaScript
that
just
involves
running
j/s
hint
on
the
code
that
we
have
just
to
make
sure
that
it's
formatted
and
consistent
throughout
all
of
core.
A
So
if
we
have
anyone
who
is
interested
in
working
on
the
html5
improvement,
conversions
or
Jay
ascent,
there's
only
a
handful
of
those
left,
which
is
great
I,
think
we'll
definitely
get
those
done
before
we
ship
backdrop.
One
and
we've
got
a
bunch
of
other
stuff
that
we're
also
working
on.
It
is
not
a
release
Walker
that
we
do
want
to
get
in
backdrop,
the
first
of
which
is
separating
our
identity
from
drupal's
identity.
Since
we're
fourth
of
the
Drupal
project
or
software
looks
like
drupal
and
you
install
backdrop,
it
looks
like
installing
Drupal.
A
We
want
to
make
sure
that
it
feels
completely
different.
So
we've
got
some
new
branding
honor
in
stellar
page,
which
is
good,
but
we
want
new
branding
on
the
administration.
Section
two
I
know:
Julia
swing
a
bunch
of
work
on
design
and
she's
got
some
CSS
changes,
she's
moving
into
our
style
guide
for
us,
which
would
be
great,
but
what
we're
going
to
need
to
do
as
soon
as
we're
done
with
that
and
start
creating
issues
to
actually
apply
those
style
changes
to
the
seven
theme
in
backdrop
and
also
changing
its
name.
A
So
it's
not
seven
and
then
we've
also
got
some
themes
to
some
cleanup
tasks.
A
few
of
these
we're
working
on
right
now,
a
couple
of
other
ones
are
going
to
be
dealt
with
after
the
layout
conversion,
because
Lance
is
going
to
change
so
much
about
beaming
changes.
It's
a
more
important
that
we
get
that
done.
A
Then
we've
got
some
user
experience,
improvements
going
on
as
well
that
just
involve
cleaning
up
of
general
things,
making
sure
names
for
things
are
consistent
using
terminology
that
makes
sense
to
people
and
then,
of
course,
my
personal
favorite
getting
a
rich
text
editor
into
core,
and
that
might
not
be
done
before
the
one
point.
0
point
0
release,
but
if
we
have
someone,
that's
super
passionate
about
getting
it
done.
A
We
would
love
some
pop
with
that,
so
if
we
could
get
it
done,
we
would,
if
not,
we
will
just
do
it
in
one
point,
one
or
one
point
to
something
like
that:
we've
got
a
another
section
here
of
final
reviews,
there's
a
bunch
of
stuff
that
we
want
to
kind
of
do
once
over
before
release,
and
so
far
we've
got
two
things
on
that
list.
We
have
a
CSS
review.
A
We
finished
all
of
our
CSS
cleanup
from
the
meta
issue
of
you
know
backwards
from
Drupal
8,
but
we've
changed
a
little
bit
to
meet
our
own
coding
standard,
sensitive,
triple
Eight's
coating,
we're
adding
that
on
here,
which
is
a
markup
review
for
our
layouts.
So
if
we
could
have
someone
who
is
in
the
HTML,
it's
not
preferably
look
at
our
HTML
and
say
you're
doing
it
wrong,
or
you
know
if
you've
got
improvements
for
how
we
should
do.
It
will
be
great
to
have
that
feedback
on
those
templates
as
well.
A
A
Layouts
right
now,
the
CSS
review
is
a
little
bit
more
extensive.
We
just
want
to
make
sure
all
the
files
are
in
the
correct
directories
named
correctly
and
are
using
our
coding
standards,
so
that
might
be
more
of
a
you
know.
You've
got
a
whole
weekend
free
rather
than
an
hour.
You
want
to
turn
through
all
those
files
to
be
like
you
know,
found
something
in
the
room
place
or
what
have
you
there's
also
a
section
in
this
weekly
meeting
for
updates
from
the
PMC?
A
So
if
we
have
any
issues
that
are
sticky
in
the
issue,
queue
need
to
be
escalated
for
for
the
discussion.
We
take
this
part
of
the
meeting
to
explain
our
decision
and
why
back
to
the
larger
community,
but
we
don't
have
any
issues
that
have
been
sticky
and
escalated
lately,
so
this
is
still
just
kind
of
a
placeholder
in
this
meeting.
So
we've
got
a
bunch
of
stuff
that
we're
working
on.
That
is
not
backdrop
CMS
the
project,
that
is
backdrop
CMS
the
stuff.
A
A
It
needs
a
couple
of
changes
to
its
change
notice,
content
types
that
we
can
get
the
change
notices
in
for
all
the
stuff
that
nice
and
working
on
recently
for
blocks
and
layouts,
and
then,
of
course,
we
need
to
add
all
those
change,
notices,
I
know
around
had
volunteered
a
couple
weeks
ago
to
help
create
of
this
documentation.
For
us,
I
was
going
to
try
and
lean
on
a
little
bit
to
also
change
the
content
types
to
match
our
needs,
since
he
will
know
best
as
creating
them.
A
B
Just
marking
them
there,
although
everything
that
needs
a
change
notice,
we've
been
marking
it
in
the
issue.
Key
with
the
tag,
needs
change,
notice
and
I've
been
pretty
good
about
trying
to
document
them
in
the
github
issue
queue,
but
they
need
more
comprehensive
and
a
centralized
list
of
all
of
them.
I
think,
okay,.
A
So
that
might
be
something
that
would
be
good
too.
If
we
had
someone
who
wanted
to
jump
in
there
go
find
an
issue.
Tagged
needs
change,
notice,
go
create
change,
notice
and
see
what
you
can
and
can't
do
and
make
sure
that
we
can
get
that
ironed
out
too.
So
that
would
be
great.
We
also
need
an
update
server.
Did
you
talk
to
Justin
about
that?
Yeah.
B
Some
things
happened
this
past
week,
Justin
or
large
designs,
as
he's
known
on
on
the
github
Xand,
the
Internet's
did
a
whole
bunch
of
work,
sort
of
strengthening
the
security
and
getting
some
of
her
our
back-end
infrastructure
set
up
this
week,
which
is
super
helpful.
Thank
you
very
much
Justin
that
involves
setting
up
ssl
certificates
on
the
the
flagship
site
and
on
the
api
website
and
he's
taking
a
look
like
after
after
dated
all
of
our
server
administration
and
just
got
it
sort
of
running
a
little
bit
more
smoothly.
B
He
volunteered
to
take
a
look
at
just
thinking
about
how
we
could
manage
packages
and
distributions
and
releases,
but
he
said
that
he's
really
just
going
to
be
thinking
about
it,
because
I
mean
he's
right
that
there's
like
a
ton
of
different
directions.
We
could
go
with
this.
So
what
he's
going
to
give
it
some
thought
so
I
mean
we're
open
to
a
lot
of
options.
Here.
I
mean
we've
imagined
that
the
release
system
will
act
very
similar
to
to
jquery's
website
for
managing
plugins.
B
So
if
you
go
to
plug
in
such
a
query
com,
it's
basically
a
repository
that
is
registered
with
github
and
there's
a
high
amount
of
communication
that
happens
between
back
between
between
github
and
the
jQuery
plugins
website.
And
we're
hoping
to
do
is
something
similar,
but
there's
so
many
tools
out
there
for
package
management's
like
we're
still
open
to
alternatives.
It's
just
that.
We
have
that
in
mind,
but
that's
not
necessarily
where
we'll
end
up.
B
It
depends
on
on
the
tools
and
resources
we
have
available
or
if
somebody
comes
up
with
a
really
awesome
idea,
like
we're
open
to
other
ideas
as
well,
but
the
most
likely
situation
is
that
packages
will
be
managed
on
github,
we'll
use
github
hooks
to
communicate
with
the
flagship
website,
and
then
the
flagship
website
will
be
the
official
repository
of
like
you
know
the
module
names
I,
don't
know
web
porn.
You
know
the
module
named
flag,
you
know,
but
all
of
the
issue.
B
B
Right,
yeah
yeah,
so
so
your
individual
Drupal
I'm.
Sorry,
your
individual
backdrop,
websites
with
update
module,
will
communicate
with
flagship
website
to
check
if
their
updates
for
a
particular
module,
rather
than
you
need
to
go
to
github
and
long-term.
That
can
mean
things
like
we
could.
You
know
not
necessarily
lock
ourselves
in
to
get
up.
You
could
host
your
your
code
in
other
places,
but
the
canonical
resource
of
which
version
is
the
most
recent
will
always
be
backdrop:
CMS
org,
okay,.
A
A
It
be,
but
it'd
be
good
to
put
him
in
touch
with
Kevin.
Cuz
Kevin
also
did
some
thinking
about
all
this
stuff
too.
When
I
was
like,
you
should
work
on
the
github
service
and
he
was
like.
We
need
to
think
about
this
first,
so
he
might
have
some
good
ideas
there
as
well,
and
they
do
all
their
product
management
on
different
platforms
and
whatever
so
he's
got
some
experience
behind
that
too
so
I'm
not
sure
either.
A
B
A
A
We
want
to
do
with
it
and
it's
going
to
get
a
redesign
with
a
new
with
our
new
branding
package
added
sometime
around
time
to
release,
which
is
great,
we've
already
undertaking
some
work
on
getting
our
dragon.
Mascot
illustrated
so,
hopefully
our
new
website
design
will
be
able
to
incorporate
drop
our
dragon
at
some
point,
which
will
be
great.
A
We
also
want
to
add
a
showcase
site,
so
we
can
start
getting
the
sites
that
are
running
back
drop
up
to
somewhere
for
people
to
see
which
would
be
good,
we're
gonna
add
a
list
of
modules,
a
list
of
all
themes.
Of
course
we
need
modules
and
themes
before
we
could
tell
those
lists
of
them,
so
a
slightly
less
of
a
priority.
We
also
have
some
other
ideas,
for
other
things
want
to
add
to
that
website.
There's
a
really
great
examples
of
like
drupal.org
job
suction.
A
We
can
have
a
job
section,
but
we
also
need
to
have
jobs
before
we
shadow
gem
section.
So
we've
got
a
bunch
of
great
ideas,
various
different
priorities,
I
think
getting
the
update,
server
module
theme
thing:
salt
sooner
rather
than
later,
would
be
great,
but
of
course
getting
a
product
out
is
more
important
than
all
of
those
okay
sprints.
So
we
sprint
every
Thursday
today's
Thursday
woohoo.
A
So
after
this
meeting,
if
you
want
to
jump
in
IRC,
if
there's
anything,
you
want
to
work
on
an
airboat
there,
you
want
and
ask
us
any
questions,
make
sure
to
ping
us
first,
because
sometimes
we
have
our
nose
in
the
code
and
we
don't
necessarily
know
people
are
trying
to
get
our
attention.
So
if
you
type
our
names
or
IRC
channels,
it'll
make
a
noise
and
we'll
look
up
and
find
out.
Someone
was
talk
to
us.
So
definitely
join
us
in
IRC,
which
is
great.
A
We
also
have
an
in-person
sprint
coming
up
at
bad
camp,
which
is
the
largest
world's
largest
free,
durable
event.
Bad
cam
is
going
to
be
november.
Six
through
ninth
we're
going
to
be
doing
a
backdrop
sprint
on
Sunday
November.
Ninth,
we
have
a
kind
of
a
sprinting
area
in
the
mezzanine
level.
On
the
second
floor,
which
watts
of
computers
and
internet
and
coffee
and
stuff
there's
gonna
be
a
whole
bunch
of
others,
14
going
on
there's
a
court
of
elements,
print
there's,
you
know
contribs
friend,
there's
a
bunch
of
other
stuff.
A
A
You
want
to
do
not
also
totally
fine
go
sit
next
door,
so
our
first
in
real
life
sprint
for
the
last
few
months,
will
be
at
that
camp,
which
is
super
exciting
and
then
we
might
schedule
some
more
in
the
future
star
them
in
this
agenda
so
that
we
can
see
it
quickly.
There's
a
bunch
of
other
stuff
we're
doing
here
in
the
near
future
to
help
spread
the
word
about
backdrop.
We
are
doing
a
talk
at
the
Pacific
Northwest
rupal
summit
I'm.
A
Just
so,
people
can
hear
what
it
is:
we're
up
to
we're
going
to
do
attack
at
the
html5
developer
conference,
which
I'm
super
excited
about,
because
that's
our
first
chance
to
pitch
software
to
people
who
are
not
Drupal
people.
So
people,
maybe
don't
even
know
what
ripple
is.
So
we
could
just
kind
of
give
them
a
demo
and
show
them
what
it
is
working
on
and
get
some
feedback
on.
What
it
is.
The
outside
community
wants
from
their
CMS,
and
we
also
get
to
have
that.
A
Why
create
another
CMS
talk
which
I
think
will
be
really
fun,
so
I'm
looking
forward
a
lot
to
that,
and
then
we
have
obviously
a
tuck.
Well,
hopefully,
we
haven't
selected
sessions
yet
but
I'm
hoping
to
get
a
talk
in
a
bad
camp
and
then
we
also
have
we're
going
to
Cymphonique
on
in
Madrid,
which
is
going
to
be
super
excited,
I.
Think
I'm,
one
of
the
keynote
speakers
there
on
just
open
source
communities
in
general
and
why?
How
what
and
forks
happen,
which
I
think
would
be
will
be
interesting.
A
So
that's
super
fun.
There's
a
bunch
of
other
stuff.
Coming
up
early
next
year
we
were
requested
to
presenta
backdrop,
talk
at
a
drupalcon,
South
America
and
in
Bogota,
but
it
was
escalated
and
they
decided
they
didn't
actually
want
the
back
job
Chuck.
Even
though
the
you
know
people
wanted
it.
The
organization
didn't
want
it.
A
So
we're
probably
gonna
go
anyway
and
will
give
the
text
on
Drupal
stuff
to
make
people
happy
just
with
another
short
on
talks,
but
we
can
talk
to
people
in
the
hallways
about
backdrop
if
they
want
to
know
about
it
and
that
way
we're
not
on
the
schedule.
We're
not
offend
anyone
but
we're
there.
So
if
people
have
questions
they
can
talk
to
us
in
from
first
thing.
A
But
we
have
also
been
requested
to
give
a
tough
on
backdrop
drupalcon
india,
but
I
don't
know
when
that
is
yet
I,
don't
think
they
have
a
website
yet
and
I
told
the
people
who
asked
me
about
it
to
clear
that
with
the
drupal
association
first.
So
we
probably
won't
be
doing
anything
with
that
for
some
time
to
come
so
exciting
and
I
guess,
that's
all
I
have
and
there
isn't
a
no
need
if
you
want
to
add
anything
else
to
this
week's
discussion.
A
lot
going
on.
B
Yeah,
no
no
I
mean,
as
always,
everyone
that's
interested
in
participating
in
backdrop.
Just
take
a
look
through
the
issue.
Queue
issue
cube
being
on
on
github
I.
Think
that
we
still
have
a
couple
issues
tagged
novice.
If
somebody
wants
to
hop
in
and
do
their
first
full
requests,
it's
pretty
easy
to
to
get
involved
in
and
we
provide
feedback
fairly
quickly,
so
yeah
we're
seeing
an
uptick
and
our
participation,
which
has
been
fantastic
and
it's
great
to
see
momentum
building.