►
Description
Today’s development agenda: http://bit.ly/2ah1bUK
A
There
we
go
hey,
welcome
everybody
to
the
weekly
backdrop,
developer
meeting,
it's
August
4
2016,
some
general
net
foods
cake
stuff
off
the
kallah
box.
Beta
3
is
now
out.
Calub
boxes
got
great
support
for
backdrop,
and
when
you
install
with
Calla
box,
you
also
will
get
a
fully
functioning
drush
and
if
you
want
to
try
out
some
fancy,
docker
based
workflow
with
backdrop,
give
Kayla
box
a
shot.
You
can
donate
to
backdrop
CMS
at
backdrop.
A
Cms
org
slash
contribute
and
you
can
get
a
dragon
t-shirt
as
a
thank
you
for
your
donation
or
a
hoodie.
Although
we
are
running
out
of
both
of
those
things,
the
website
is
up
to
date
with
the
sizes
that
we
have
available
left.
So
if
you
would
like
to
donate-
and
we
have
a
size
that
fits
you,
then
we
can
send
you
a
t-shirt
or
hoodie.
A
A
So
we
will
just
keep
rolling
on
infrastructure
tasks,
so
infrastructure
things
around
backdrop
that
isn't
the
software
itself
and
we'll
start
off
by
talking
about
the
packager.
The
packager
hadn't
been
broken
for
a
little
while
that
was
preventing
a
fully
built,
zip
files
from
being
uploaded
back
to
back
to
github.
When
a
new
release
was
made.
This
has
finally
been
fixed,
its
issue
to
64.
A
In
the
backdrop
CMS
mortgage,
GQ
Gore,
had
done
some
work
a
couple
ago
actually
to
update
the
github
API
module,
but
we
needed
to
do
some
work
and
some
testing
to
get
that
actually
up
and
running
on
backdrop
CMS
org
now
that
is
in
place
and
the
packager
should
be
corrected.
We
also
went
through
the
past
couple
of
months
and
found
the
packages
that
hadn't
been
processed
correctly
and
rebuilt
those
so
we
had.
A
It
was
only
like
four
or
five
packages
that
actually
ended
up
being
broken
over
that
period,
because
it
looks
like
a
lot
of
the
time.
The
package
is
actually
were
working,
but
sometimes
it
was
just
a
the
first
time
wouldn't
work,
but
the
second
time
would
so
anyway,
now
it's
fixed
so
that
it
should
work
every
time.
So
that's
great.
We
can
remove
this
from
the
agenda
for
next
week
as
an
enhancement
to
our
packager.
A
We're
also
evaluating
issued
1992
in
the
backdrop
issue
queue,
and
that
is
that
we
want
to
add
an
md5
checksum
for
for
all
of
the
projects.
I
said
builds.
So
that
way,
you
can
verify
that
the
archive
hasn't
been
tampered
with.
There's
any
progress
on
this
one,
it's
just
mostly
an
idea.
I
think
this
would
probably
be
most
helpful
not
for
manual
checking,
although
manual
checking
is
great
too,
but
also
for
for
verifying
archives.
A
Okay,
let's
see
testing
infrastructure
is
the
next
item
on
the
agenda.
I,
don't
think
that
there's
actually
much
going
on
here
in
this
testing
infrastructure
issue.
A
We
have
one
issue
issue
1478
that
is
tracking
all
of
our
random
failures
that
have
been
happening
in
our
testing
suites,
although,
as
I've
been
seeing,
the
random
failures
have
been
decreasing
really
pretty
regularly
and
I.
Think
that
now
that
we've
disconnected
Travis
CI,
which
was
having
a
bunch
of
problems,
Zen
CI,
has
been
really
pretty
effective
about
running
consistently
and
the
random
failures
that
were
saying
haven't
been
cropping
up
so
much.
A
Let's
see
West
regarding
basis
China
up
on
blacktop,
see
when
startled
org.
So
this
is
back
on
the
packager.
Have
you
made
a
you
made
an
official
release
of
basis,
I'm
guessing?
It
shows.
A
I
wouldn't
try
it
again
today,
if
you
haven't
already,
because
it
should
the
changes
just
went
in
yesterday.
Let's
see
wondering
geez,
oh
yeah
yeah,
so
you
so
you
need
to
actually
click
on.
So
it
has
a
tagged,
but
it
doesn't
have
a
release
which
I
know
is
a
weird
thing.
A
No
yeah
yeah.
So
if
you
look
at
the
releases
on
github,
it's
it's
weird
the
way
github
works.
When
you
push
a
tag
it
it's
not
the
same
thing
as
a
release,
so
you
actually
need
to
edit
the
tag
on
github
and
then
add
some
release
net
notes,
and
then
it
becomes
a
release
in
bed
all
right,
yeah,
it's
okay,
it
is,
it
is
kind
of
confusing.
That's
github
has
that
separation.
We
could
actually
fire.
A
A
Okay-
let's
see
so
we
another,
no,
we
turned
off
travis
CI
we're
using
zen
CI
now
for
all
of
our
continuous
integration,
which
is
continued
to
be
awesome,
a
good
job
corps
on
net.
I
have
a
bullet
item
in
here
that
I'm
a
I
was
going
to
evaluate
style
CI,
which
does
code
style
checking
but
I,
actually
almost
immediately
after
looking
at
it.
It
didn't
take
me
very
long
to
look
at
and
go
this
isn't
very
good.
A
It
only
does
a
it
only
does
PHP
style
evaluation
and
it
is
very
limited
what
it
is
actually
capable
of
doing
so.
I,
don't
know
I
guess
we
could
still
have
it
there
as
a
as
a
starting
point
might
be
good,
but
I
know
gore
is
also
working
on
style
checking
for
presents
Yannick
I'm,
not
really
sure
if
it's
worth
pursuing
anyway,
if
anybody
has
any
strong
feelings
about
style,
like
code
style
check
your
checkers
or
has
any
experience
with
them,
I'd
love
to
hear
about
possible
options
there.
A
Let's
see
JavaScript
based
testing.
We
do
not
have
any
javascript
javascript
testing
in
in
backdrops
implementation
of
simple
test.
Although
it's
been
noted
that
Drupal
8
added
javascripts
testing
in
8.1,
but
all
of
it
is
still
simple
test
based,
so
it
is
possible
for
us
to
imitates
most
of
those
fixes,
because
simple
test
is
mostly
the
same
between
Drupal
7
in
Drupal
8.
A
A
Okay,
let's
see
we
also
haven't
many
automatic
updates,
is
a
thing
that
are
a
topic
that
we
have
been
discussing
recently.
In
the
backdrop
issue
queue
issue
2024
in
which
we're
trying
to
think
about
way
is
that
we
can
may
so
that
backdrop,
besides,
just
being
able
to
install
new
modules,
could
automatically
update
modules
that
you
have
installed
and
possibly
backup
itself.
A
It's
one
of
those
things
that
it's
a
really
hairy
problem,
but
it
would
also
be
fantastic
for
us
to
to
accommodate,
for
at
least
security
updates,
to
make
it
so
that
users
weren't
spending
all
of
your
time
just
updating
backdrop
sites
if
they
have
a
little
bunch
of
them,
fits
in
nicely
with
our
our
mission
to
make
website
development
more
affordable.
If
we
can
reduce
the
amount
of
maintenance
that
is
required,
while
still
keeping
people's
sites
secure,
that
would
be
huge
win
for
us
right
now.
It's
just
a
meta.
A
Okay,
next
item
on
the
agenda
and
infrastructure
is
back
top
CMS
org
our
flagship
website,
things
that
were
working
on
currently,
that
should
be
coming
soon.
Single
sign-on
with
hub
is
backdrop
CMS,
org
issue,
178
I
know.
Last
time
we
checked
down
this
Gordon
been
saying
that
he
built
single
sign-on
into
the
github
API
and
Jen
was
going
to
try
it
out
and
test
it.
A
A
Looks
like
well,
maybe
not
completed,
but
it
looks
like
we
have
a
content
type
built
out
and
we're
looking
for
content.
So
if
you
have
a
showcase
website
that
you
would
like
to
include
on
bike
shop,
CMS
torg,
it
looks
like
you
should
be
able
to
add
a
showcase
note
on
my
top
CMS
Targ
and
the
natural
presentation
will
be
working
on
the
future.
It
looks
like
you
can
check
in
more
about
the
showcase
section
issue
176.
A
In
the
backdrop,
issue
queue
as
far
as
the
support
section
goes:
we're
working
on
building
that
documentation
in
the
support
section
of
the
websites.
That's
issue,
55
I
know
doc.
Wellmont
has
been
doing
a
bunch
of
work
in
ER
documentation
recently,
so
it's
been
great
to
see
that
growing
and
off
these
items,
as
he
goes
through,
goes
through.
The
maze
got
a
good
number
of
them
completed.
A
Okay
forums:
we've
got
a
lot
of
ideas
about
forums
you
can
check
in
there
issue
18
and
issue
a
250
both
in
the
backdrop
CMS
or
issue
queue.
I
think
that
we've
both
been
looking
at
well,
we've
been
looking
at
the
forum
module
that
Drupal
7
had
and
we're
also
looking
at
alternative
form
modules,
the
name
of
which
eludes
me
at
the
moment.
But
it's
there
in
su
250
I
believe.
A
Let's
see
updates
underway
some
things
that
we
need
some
additional
help
with
usage
statistics.
We
have
these
uses
statistics
reporting
accurately
now,
but
they're
not
easily
accessible
on
the
site.
So
if
you
would
like
to
work
on
making
it
so
that
we
have
a
block
or
an
item
to
actually
show
the
number
of
sites
that
are
out
there
running
a
particular
project,
you
can
participate
in
that
issue
at
issue.
243
find
modules,
themes
and
layouts
pages.
A
Let's
see,
oh,
this
is
still
usage.
Statistics
related
sounds
like
Jeff
isn't
with
us
today,
but
he
looks
like
jeff
has
been
doing
some
work
on
this
making
it
so
that
you
can
get
usage
statistics
using
the
github
API
module,
but
it
looks
like
he's
stuck
because
he's
making
so
many
requests
that
he's
running
he's
being
rate
limited
by
the
github
API,
but
we
can
use
if
we
authenticate
them
that
drastically
increases
our
our
rate
of
queries
that
we
can
do
against
github,
so
that
might
unblock
him
there.
A
Okay,
excellent
that
looks.
That
would
be
fantastic.
So
once
we
have
the
usage
numbers,
oh
I
mean
we
have
usage
numbers,
but
we
also
can
get
why
download
numbers
and
I
think
that's
what
I
think.
That's
what
Jeff's
talking
about
here
yeah,
because
yeah,
because
issue
95
is
about
displaying
the
number
of
active
installs
and
the
number
of
downloads,
and
so
we
have
the
number
of
active
installs
from
Project
module,
but
the
number
of
downloads
is
currently
only
stored
on
github,
because
github
holds
our
our
archives
themselves.
A
A
Ok,
I
will
just
remove
this
one
John.
Alright,
let's
see
the
event
listing.
If
you
visit
the
backdrop
sea
monster,
org,
slash
events,
this
page,
which
is
kind
of
thrown
together,
but
but
it
doesn't
have
any
a
designer's
touch-
has
never
been
on
this
page.
So
if
you
have
design
skills
and
I've
taken
a
look
at
the
rest
of
our
websites,
a
review
of
the
of
that
event
page
would
be
nice,
but
really
it's
it's
actually
already
all
built
out.
A
C
Well,
the
ones
this
thought
that
see
how
we
have
the
list
of
features
in
the
front
page
with
the
and
icons
and
everything
the
idea
was
to
have
separate
notes
for
its
future
and
with
with
videos
or
screenshots
or
whatever
we
needed,
and
that
automatic
be
picking
up
certain
fields
like
that.
I
know
of
verb
and
some
small
description
and
then
putting
that
together
as
a
view
in
the
front
page.
But
then,
when
people
click
on
each
individual
feature,
it
goes,
and
it
tells
them
more
details
about
that.
C
C
A
C
A
C
A
Alright,
let's
see
service
listing
follow-ups
to
this
issue,
194
in
the
backdrop
CMS
or
guess
you
too,
I'm
not
familiar
with
this
issue,
either
without
Jen
around
today.
I'm
kind
of
stumbling.
Through
this
backdrop,
CMS
org
section-
doesn't
look
like
there's
been
any
updates
recently,
but
we
have
some
items
that
we
would
like
to
polish.
A
A
That
50
also
has
some
features
that
will
probably
push
into
you
not
bug
fixed
release,
but
into
the
next
minor
release.
So
it'll,
be
at
one
point
with
legends,
including
one
of
the
most
interesting
ones
to
me
is
full
utf-8
support,
which
means
that
it
that
backdrop
probably
able
to
support
emojis
right
now.
A
Let's
see
a
one
point,
four
point:
four
I'm
pointing
forward
for
is
the
next
bug-fix
release.
It
will
be
coming
out
imminently:
we've
got
a
yeah
some
items
here
that
I've
been
brought
up
the
path,
auto
path
auto
when
you
set
up
a
content
type,
oh
wait,
a
target,
token
field.
Sorry,
this
is
a
different
one.
I
think
I
already
gave
this
review,
but
maybe
it
needs
another
one.
A
Just
when
you
add
a
pattern
to
a
content
type
when
you're
setting
up
the
initial
path,
auto
pattern
that
when
you
open
the
token
dialogue
it
you
just
focus
the
fee
yield
yeah,
it
looks
like
jeff
has
come
back
in
an
updated.
The
polar
quest
looks
like
I
just
need
to
know
to
another
review
the
front
page,
not
back
to
the
number
of
post
settings
issue:
20
21,
that's
been
merged.
A
Okay,
so
a
couple
more
issues
that
can
maybe
slip
into
one
point,
four
point:
four:
we
have
a
special
section
in
here
for
major
bug,
fixes
that
need
to
be
addressed,
two
of
which
have
been
knocked
out.
The
third
one,
that's
still
in
progress
that
needs
review
and
a
fourth
one
that
is
fixed
but
needs
a
test
case.
So
the
first
one
is
a
safari
flexbox
problem.
We've
gotten
confirmation
from
gem
that
we
finally
affixed
a
flexbox
problem.
It
Safari
West
we're
going
to
chance
to
confirm
that
as
well.
A
Well,
good
today,
I
did
not
okay
yeah.
We
actually
found
a
bug
in
in
bootstrap
itself
in
the
grid
system,
which
we've
posted
feedback
back
upstream
to
to
bootstrap,
to
see
if
they
can
reproduce
or
fix
that
problem
in
bootstrap
itself.
It's
funny
we
fixed
the
problem
in
backdrops,
bootstrap
grid
system
CSS
file,
but
in
Jen's
situation
she
had
the
full
bootstrap
library
also
loaded
on
her
client
site,
and
so
even
though
we
fixed
it,
the
full
stock
bootstrap
library
broken
again,
which
was
a
very
unpleasant
surprise
yeah.
A
So
obviously
we
need
to
get
that
fixed
upstream
as
well,
and
then
that
would
solve
the
problem
for
everybody
ckeditor.
Every
time
you
upload
an
image
it
unloads
ckeditor
that
has
been
fixed
by
Jeff.
Thank
you
and
has
been
merged,
we're
just
waiting
on
that
their
release
images
are
being
deleted
after
six
hours,
if
you
upload
them
into
a
block
or
into
other
configurations
stored
items.
I
know
this
has
been
waiting
on
review
for
quite
a
while
and
I'm
hoping
I'll
get
to
it
this
week.
A
Pat
settings
do
not
get
saved
when
creating
a
new
content
type.
This
has
been
fixed
but
needs
a
test
case
yeah
the
ad
mentioned
in
previous
weeks
that
as
soon
as
we
fix
any
one
of
these
issues
that
we
should
ship
one
point
four
point:
four:
we
fixed
two
and
a
half
of
them
at
this
point
just
that
the
test
missing
from
that
one.
So
we
should
be
releasing
back
up.
A
One
point
four
point:
four
eminently
I
had
actually
hoped
to
do
it
yesterday,
but
the
packager
fix
and
took
a
little
bit
more
time
than
I
expected
so,
but
we
will
be
pushing
a
one
point.
Four
point,
four,
very
very
soon
on
almost
certainly
this
next
week,
but
maybe
as
soon
as
today
or
tomorrow.
It's
really
as
soon
as
possible.
Okay,.
A
We
also
have
a
bunch
of
other
things
that
are
tagged
for
one
point,
four
point,
four
for
the
next
bug-fix
release,
but
in
the
event
that
they
take
more
work
than
just
something,
bridging
them
they'll
probably
get
pushed
to.
One
point
four
point:
five
and
we
need
to
push
out
one
point
four
point:
four:
as
soon
as
possible,.
A
Okay,
the
1.5
release.
It's
the
next
minor
release
comes
out,
September,
15
2016,
that's
coming
up
real
soon,
now
we're
getting
to
the
point
that
it's
only
that's
less
than
a
month
and
a
half
away,
which
is
a
little
bit
stressful
because
we
haven't
merged
any
of
our
minor
features
yet,
but
we've
made
some
good
progress
on
a
lot
of
them.
A
D
D
So
I
have
just
wow.
They
just
really
started
that
okay,
I've
just
been
playing
with
trying
to
get
the
entity
reference,
be
able
to
do
reference
arbitrary
entity
types
depending
on
what
you
want
and
I
just
posted
an
update
to
the
ticket.
With
my
new
sort
of
thing,
where
you
have
a
checkbox
on
the
fields
instance
to
say
which
types
of
entities
/
bundles
should
be
referenced
and
then
when
the
user
can
either
select
one
of
those
that
are
available
or
if
only
ones
available,
just
has
the
autocomplete.
A
D
The
asanas
the
autocomplete
needs
to
know
the
base
table
that
is
auto
completing
on
so
it
can't
autocomplete
across
different
base
tables
yeah.
So
if
you
want
to
be
able
to,
if
you
want
to
be
able
to
reference
different
types
of
entities
within
the
same
field,
you
need
to
have
like
a
selection.
Tells
you,
like
you
know,
which
base
table
your
your
auto,
completing
against.
A
Yeah
interesting.
A
C
D
A
Okay,
excellent
next
item,
a
new
front,
end
demon
core.
We
had
to
design
meeting
today
in
which
we
discussed
this
a
little
bit,
but
sorry
Wes
I'm,
going
to
make
you
do
it
again:
abbreviated,
an
update
on
the
basis
theme,
yep.
B
Working
through
issues
just
got
a
PR
up
for
one
gram,
reported
and
I'm
running
through
basis
right
now
to
a
kitchen,
a
few
little
things
here
and
there,
but
yeah
I'm
in
the
queue
trying
to
resolve
those
things
and
at
least
respond
and
should
be
making
a
lot
of
progress
here
soon.
Oh
and
I
I
might
have
a
real
release
that
shows
up
shows
up
when
you
search
for
it
all
right.
I'll.
A
Okay,
great,
let's
see
we
also
have
a
to-do
checklist.
This
is
said
that
yeah,
it's
likely
this
is
going
to
be
kicked
to
1.6
and
I'm.
Fine,
with
that,
let's
say:
let's
just
keep
going
new
homepage
layout
is
issued
1042.
We
want
to
have
a
page
that
is
that
ships
with
backdrop.
That
is
a
layout
that
just
handles
the
front
page
and
is
made
up
of
blocks
instead
of
being
that
weird
/
node
page
ten.
A
Let's
see
rich
text
editor
meta
issue
1087.
We
have
a
whole
bunch
of
items
that
we
could
be
improving
about
the
way
the
ckeditor
works.
There's
some
features
in
the
new
version
of
ckeditor
that
we
already
have
that
we're
just
not
utilizing
yet
things
like
copy
paste
image
supports,
drag
and
drop
uploads
those
sorts
of
things.
So
we
have
an
issue
that
lists
a
whole
bunch
of
sub
items
at
1087.
I,
don't
think,
there's
been
any
serious
progress
on
any
of
these
items
as
of
yet
so.
A
A
C
B
C
A
So
there's
there
is
work
out
there.
It's
actually
a
little
bit.
It
seems
like
we're
already
getting
into
a
situation
where
demand
is
outstripped
by
as
far
as
developers
are
concerned,
which
is
great
for
developers,
and
so,
if
you
are
such
person,
you
should
be
listing
your
services
upon
backdrops.
You
must
order
to
help
people
find
you
news
and
announcements.
A
Let's
see,
we
have
an
official
blog
schedule
posted
up
on
the
backdrop.
Cms
org
issue
queue
issue,
158
Jen,
rode
up.
Think
jen
is
one
that
wrote
up
this
a
Twin
Cities
Drupal,
yeah,
Twin,
Cities,
Drupal
recap,
which
was
great
and
also
talked
a
little
bit
about
our
efforts
in
trying
to
pursue
automatic
updates.
So
that's
great,
it
was
really
it
was
a
really
good
camp
that
was
a
while
ago
now,
but
a
way
to
really
excellent
time.
Jen
is
actually
add
another
camp
doing
another.
A
Could
watch
she's
not
in
this
meeting
with
us?
If
you
have
an
idea
for
a
blog
post,
you
can
comment
on
the
issue
158.
You
also
can
just
create
a
note
on
backdrop.
Cms
org
and
write
up
anything
backdrop
related
that
you
feel
like
would
be
great
to
distribute
with
other
people
yeah
we're
really
pretty
open
to
any
posts,
because
we
really
would
like
to
have
a
regular
stream
of
news
coming
out
from
back
top
CMS
org.
A
A
Okay,
let's
see
newsletter
schedule,
we
have
an
issue
for
this
at
177
we
have
not
sent
out
gosh.
This
is
embarrassing.
We
haven't
send
out
a
newsletter
for
the
1.4
release,
so
we
should
just
send
out
a
note
to
all
of
our
subscribers,
which
I
have
like
several
hundred
I
think
we
have
like
six
or
seven
hundred
people
subscribe
to
our
newsletter,
so
we
can
reach
a
lot
of
people
that
way
whenever
we
feel
like
it,
but
we
haven't
been
real
good
about
actually
utilizing
it.
So
we
would
like
to
write
up
a
basic
newsletter.
A
A
A
A
However,
we
also
regularly
communicate
on
git
er.
We
have
a
git
er
IRC
channel
that
you
can
access
from
those
repositories,
but
the
URL
to
it
is
get
on
IM
/
backdrop
/
backdrop
dash
issues,
and
that
gets
you
to
our
primary
channel,
in
which
we
talk
about
all
things
backdrop.
In
real
time
there
is
an
IRC
channel,
although
we're
really
trying
to
funnel
people
into
Gator
as
being
a
primary,
a
place
of
communication.
A
Irc
it's
on
freenode
/
backdrop:
you
can
also
use
I
receive
your
diehard
fan.
You
can
use
IRC
to
connect
to
get
er,
and
then
you
can
use
your
regular
tools
to
communicate
with
everybody
else.
That's
online,
using
git
er.
We
also
have
a
reddit
channel
I,
think
that
I
might
remove
this,
but
the
reddit
channel
is
basically
just
for
around
the
web.
Conversation
is
about
pack
Trump,
reddit.com,
/,
r,
/
backdrop
upcoming
events.
A
So,
if
you
are
in
the
Iowa
Midwest
area,
you
should
go
to
cedar
rapids
and
check
out
drupal
corn
happening
there's
also
drupalcamp
asheville,
that's
coming
up
in
just
a
week,
looks
like
that
would
be
next
weekend's,
not
not
tomorrow,
but
the
week
afterwards,
in
which
we
will
also
have
some
backdrop.
People
present
you
can
check
out
more
there's
a
whole
slew
than
a
bat
bag,
drops
a
mess,
org
/
news,
/
events
books.
A
We
like
touting
this
just
because
it's
so
exciting
there
are
two
full-length
well
yeah,
two
full-length
books
available
on
backdrop
beginning
backdrop:
CMS
is
out
on
a
press
and
you
can
get
it
from
amazon
as
well
as
migrating
from
Drupal
to
Mac
drop,
which
is
a
slimmer
volume.
So
we're
really
excited
to
have
those
pieces
of
literature
available.
The
really
pretty
great
books
I've
been
yet
owned.
A
A
copy
of
beginning
Petra
CMS,
but
from
what
I've
seen
in
what
I've
read
it
looks
really
excellent
and
todd
thompson
has
a
great
history
of
excellent
drupal
books,
so
lots
of
confidence
there
that
does
it
for
the
agenda
this
week.
Does
anyone
else
have
anything
else?
I
would
like
to
bring
up
and
discuss.
C
Just
a
real
quick
one
for
each
release
like
when
it
happens.
Do
we
have
like
a
task
list
of
things
that
need
to
be
happen
happening
afterwards?
Like
you
know,
we
have
various
people
doing
various
tasks
like,
for
example,
being
the
feature
list
that
we
mentioned
before.
So
it's
time
a
new
version
comes
out.
Some
people
need
to
go
through.
The
new
features.
Editor,
then
add
those
as
nodes
on
the
main
website.
So
do
we
have
a
list
of
things
that
we
can
just
take
off?
Do
we
have
anything
like
that,
so
we're
available.
C
A
You
know
we
don't
I
would
love
to
start
delegating
that,
because
right
now,
what
it
is
is
at
least
the
past
couple
of
releases,
I've
written
up
the
release,
notes
and
the
announcements
and
done
the
release,
which
basically
takes
up
like
three
whole
days
of
just
doing
everything
so
actually
planning
I,
don't
think
we
do
but
I
think
that
would
be
great
and
I
think
for
the
first
starters.
A
It
would
make
sense
if
we
just
made
an
issue
in
the
main
repository
that
was
like
planning
for
the
1.4
release
and
just
had
assignments
of
like
who's
writing
up
the
announcements.
Who
is
writing
up
the
newsletter
like
it
would
be
nice
to
have
that
done
beforehand.
Actually,
if
we're
doing
any
videos
or
screencasts
or
anything
like
that
and
then
actually
have
that
planned
out,
rather
than
it
just
being
like
a
surprise
like
it's
all
out
and
basically,
I
need
to
do
nothing
but
do
a
release
for
a
couple
days.
C
Seemed
like
we
could
put
together
like
a
Google
Doc
like
the
agenda,
pretty
much
that
we
have
as
a
template
and
with
its
release.
We
create
an
issue
somewhere
in
the
queue
and
then
that
will
have
people
assigned
to
it
stopped
asking,
and
we
can
sort
of
like
take
things
as
we
do
them
and
once
we're
like
ninety
percent
ready,
we
just
release,
or
at
least
we
have
a
general
idea
where
we're
at
and
who
needs
help
with
West.
A
Okay,
excellent
thanks
for
a
great
alright
we're
losing
people
left
and
right
because
we're
at
the
top
of
the
hour
but
yeah.
Thank
you
everybody
for
watching.
Thank
you!
We're
ready
for
joining
we'll
be
meeting
up
next
week,
as
I
mentioned,
there's
the
community
outreach
meeting
next
week
and
then
right
after
that
would
be
this
developer
meeting.
What's
so
thanks
everybody
for
joining
and
thanks
everybody
for
watching.