►
From YouTube: Backdrop Weekly - Jan 3rd
Description
Today’s development agenda: http://bit.ly/2Q9LN1C
A
All
right
we're
on
air:
it
is
January
3rd.
This
is
our
first
developer
meeting
since
New
Year,
so
happy
New,
Year
everybody.
Today
we're
gonna
focus
on
reviewing
the
issues
that
were
slated
for
backed
up
1:12
talk
about
walk
out
in
maybe
what
isn't
gonna
get
in
and
stuff
that
we
should
be
focused
on
between
now
in
at
least
eight.
So
before
we
get
into
that,
we
have
one
new,
contributed
module,
I
wanted
to
highlight
it
serve
2020,
and
this
is
a
pretty
cool
project
that
allows
you
to
do
a
comparison
between
two
images.
A
So
if
you
have
actually
had
this
use
case
for
something
on
Drupal
7
site
or
if
you
have
an
image
from
like
20
years
ago
a
month
from
today-
and
you
want
people
to
be
able
to
see
the
difference
between
the
two
of
them,
this
is
a
great
tool.
That'll
allow
you
to
do
that.
So
thank
you
for
working
on
serve
2020
since
I
didn't
see
that
for
that
drop
for
our
web
sites,
we
are
working
on
issue
number
442
about
improving
the
process
of
selecting
module,
stinkin
layouts
context,
rep
CMS
network,
that
is
underway.
A
Hopefully,
will
come
soon
now
that
we
hit
feature
freeze
but
more
exciting
than
that,
the
forum
site
we
had
some
problems
with
node
preview,
which
I
believe
are
not
fixed,
Joseph's,
probably
another
pull
request
that
I
believe
has
resolved
the
issue
with
comment:
preview
memory
consumption,
it's
a
little
bit
of
a
hack,
but
it
worked
so
I
deployed
it.
We
can
give
it
a
go
and
then
later
on.
A
If
we
want
to
figure
out
why
our
custom
module
required
a
bit
of
the
hack
we
can
revisit,
but
because
it
worked
I
think
it's
better
to
get
it
up
there.
So
I
put
it
to
do
in
the
code
revisit
later
and
deploy
so
happy
new
year
if
anyone
notices
any
other
issues
of
the
forums
like
using
it
this
year,
I
think
that
process
is
great,
really
create
an
issue,
bring
it
up
in
one
of
these
meetings
and
will
ask
for
volunteer
to
help
us
fix
it.
A
B
Alright
man,
it
was
one
action-packed
week
because,
let's
see
what
was
that
Tuesday
New
Year's
Day
was
the
last
day
of
feature,
freeze
or
buster
feature
thaw
and
at
the
beginning
of
each
freeze,
and
so
we
were
rushing
to
get
in
the
last
bits
of
functionality
into
the
1.12
release
that
will
be
coming
out
in
12
days.
So
that's
very
exciting.
We've
got
all
kinds
of
things
that
have
gotten
rich
June,
but
first,
let's
put
a
pause
on
1.12
and
talked
about
the
1.11
bug,
fix
release
and
things
that
have
gotten
in
there.
B
So
last
week,
when
we,
when
we
met
up,
we
said
that
we
were
going
to
hopefully
finish
out
the
drupal
7.6.
You
want
cross
ports
and
that
is
issued
3375.
All
the
remaining
issues
there
have
all
been
merged.
Thank
you
very
much
clone
us
for
making
just
about
every
single
one
of
those
pull
requests
and
her
goal
for
reviewing
almost
every
single
one
of
them.
So
that
was
an
awesome
tag.
Team.
That's
right
there
to
get
all
of
those
cross
ports
made
from
Drupal
over
to
backdrop.
B
That
would
be
for
sure
for
sure
part
of
the
1.12
release
that
bug
fix
queue
is
really
the
best
place
to
look
for
like
small
issues
that
can
be
worked
on
right
now.
That
was
definitely
Kevin
to
you,
the
112
release.
It
will
also
be
in
the
one
11.4
release,
which
will
would
come
out
the
same
day
as
1.12,
so
issues
in
particular
that
could
be
worked
on
in
that
bug-fix
release
include
issue
3209,
which
is
adding
predefined
color
schemes
to
the
basis
team
issued
2873,
which
is
the
maintenance
page.
Basically,
for
this
maintenance
issue.
B
Is
this
something
else
the
installation
requirements
page
looks
broken?
Oh
I
can
put
something
different.
So
if
there's
install
requirements
that
aren't
met,
then
the
page
doesn't
work
quite
right
whose
issue
2873,
let's
see
a
really
minor
issue.
Certain
tests
are
missing
the
type
attribute
and
their
info
file
Oh.
B
Actually,
this
looks
like
something
slightly
different.
There's
a
big
problem
like
the
chord
update.
This
court
updates.
Oh
okay,
I
even
read
over
this
issue.
Sorry
there's
a
problem
with
we
added
the
ability
for
court,
just
self
updating,
1.12
and
the
court
updates
themselves
might
fail
due
to
some
checking
the
properties
that
shouldn't
actually
be
checked
in.
C
B
A
Just
that
I
think
that
that's
important,
if
we're
gonna,
be
exposing
the
ability
for
people
to
do
the
updates.
We
should
address
all
of
the
folks
that
we
know
exist
with
updates.
I
know:
we've
done
that
for
a
handful
I'm
already,
and
this
is
just
one
that
seems
to
be
an
outlier.
So
it's
up
to
get
it
fixed
before
and.
B
B
A
Actually,
a
ton
of
RTL
pull
requests
in
the
queue,
because
we've
got
language
users
now
that
are
using
different
languages
that
go
the
other
way,
and
so
it
would
be
really
nice
if
we
to
kind
of
go
through
the
that
milestone
and
see
how
many
of
those
we
can
get
merged
and
cleaned
up
quite
initially,
so
anyone
who's
really
good
at
testing
left-to-right,
right-to-left
image,
switching
I
think
that
would
be
really
easy.
Just
kind
of
go
through
that
queueing
knock
all
those
oh
yeah.
B
Okay,
yeah
and,
as
I
said
before,
the
111
for
issue
queue
has
50
other
issues
in
it
and
those
are
probably
the
best
place
to
look
first
up.
It
works
that
can
be
done
right
now.
That
will
be
part
of
112
and
111
for
okay,
let's
go
to
112
and
talk
about
the
things
that
are
complete
or
not
complete
for
the
112
Louise.
B
So,
let's
see
we'll
go
through
the
items
that
we
almost
always
go
through
week
after
week
and
talk
about
which
ones
made
it
so
the
first
one
is
adding
a
class
to
the
link
dialog
and
sake
editor.
So
when
you
select
a
link
and
then
I
select
text
them
and
add
a
link
to
it,
you
can
now
also
add
a
class
to
links
that
are
inserted
into
the
rich
text
editor.
That
issue
has
been
merged
and
part
of
3307.
B
Next,
one
up
is
tanks
for
modules,
one
of
the
oldest
issues
that
we've
got
there
still.
That
was
still
open
and
that's
issue
number
37.
So
this
one
has
also
been
marriage
da
I'm,
so
glad
that
that
one
finally
get
that
in
and
stop
talking
about
that
particular
issue.
So
this
makes
it
so
the
tags
can
now
be
placed
on
modules.
The
other
got
info
files.
We
talked
about
this
in
the
earlier
and
the
UX
meeting.
So
for
more
information,
you
can
kind
of
watch
that
video
for
details,
core
updates.
B
B
That
was
split
out
from
a
much
larger
or
request
that
previously
also
handled
doing
it
automatically.
The
automatic
part
is
not
merged
in,
and
that
is
issue
414
and
it
needs
to
be
rear
old
to
be
to
accommodate
for
this
user
interface
that
we've
added
to
enable
manual
for
updates.
So
in
1.12
manual,
core
updates
will
be
available
to
turn
on
via
the
user
interface.
However,
they
are
still
turned
off
by
default.
B
Let's
see,
there's
also
another
issue,
a
couple
of
issues
related
to
poor
automatic
updates
package,
signing
which
is
issued
1992,
as
well
as
removing
authorized
PHP,
which
is
one
second
3208.
Both
of
those
issues
have
been
tabled
for
now,
no
updates
on
those,
and
so,
though,
they'll
be
pushed
into
the
next
milestone.
B
All
right,
let's
see
next
up,
is
config
translation
issues.
704.
The
initial
work
for
this
capability
has
now
been
merged
thanks
to
her
duals
efforts,
primarily
who
pushed
forward
to
make
that
implementation
a
reality.
So
let's
talk
about
what
we
got
in
here
and
what
is
yet
to
be
done.
So
what
issue
704
does
is?
B
We
just
pull
it
out
and
then
we
run
through
T,
which
is
essentially
the
same
thing
that
Drupal
7
was
doing
prior
to
config
existing
at
all.
It
would
just
run
strings
that
were
constant,
but
part
of
site
building
processes
that
were
just
running
through
the
cue
function.
Well,
we've
done
is
we've
basically
formalized
that
and
said:
okay,
that's
still
the
way
that
we're
going
to
do
it,
but
we're
going
to
build
a
system
around
tracking
which
strings
are
translated
inside
of
config
files.
B
So
what
we
have
now
is
we
have
this
new
API
that
says
get
translated
when
you
get
a
config,
T
and
then
config
files
now
have
the
ability
to
keep
a
list
of
what
strings
need
to
be
translated
inside
of
their
config
files.
So
all
that
we
have
right
now
is
the
capability
to
expose
certain
strings
as
being
translatable
and
config
files,
but
we
haven't
actually
gone
through
and
identify
all
of
the
strings
that
need
to
be
translated,
and
so
there
are
two
follow-up
issues.
B
B
Okay
and
then
there's
one
other
issue
related
to
this.
That
is
also
follow
up
and
that
is
contributed
issue
that
the
module
that
is
used
to
extract
strings
from
core
itself
the
and
create
the
translation
template
files
that
the
P
ot
files
is
the
P
ot,
X
module,
and
so
the
P
OT
x.
Module
also
has
an
issue
created
for
it.
B
There's
a
lot
of
moving
parts
to
that
particular
issue,
but
I'm
really
glad
that
we
have
the
first
step
completed,
which
is
adding
the
capability
in
our
translation,
translated
strings
and
start
config
files,
and
then,
from
here
on
out.
It's
now
updating
all
of
our
implementations
to
use
the
new
capability.
C
E
B
Yeah
with
no
core
implementations
of
it
in
place,
yet
really
things
haven't,
haven't
really
changed
at
all,
basically
that
it
was
it
there's
only
additions
right
now
and
no
actual
implementations
outside
of
testing
copy,
Thanks
yeah.
It
would
be
nice
to
have
something
that
was
real
there,
but
as
far
as
like
you
know,
like
a
end
user
thinks,
it's
mostly
is
still
kind
of
been
a
coming
soon,
but
at
least
but
at
least
there
is
something
that
actually
backs
that
up,
as
opposed
to
just
being
code
stuck
in
a
pull
request.
B
Okay,
let's
see
other
nice
things
that
were
merged
this
past
week,
views
now.
If
you
use
the
grid
display
type
in
fuse,
it
now
uses
CSS
grid
attributes
instead
of
an
HTML
table
which
is
very
cool,
yeah
very
nice.
It
also
still
has
backwards
compatibility,
so
you
can
still
use
the
legacy
table
implementation
if
you
so
choose,
but
find
a
fault
when
new
views
are
created,
if
they're
afraid
display
type,
they
will
now
use
CSS
grid,
which
is
very
cool.
That's
a
huge
2811!
You
want
to
get
some
background
on
that
issue.
B
Panel
contact
pain
there,
you
could
pull
arguments
from
the
URL
and
pass
them
to
those
blocks.
Not
capability
has
been
restored,
match
injure,
seven
functionality
and
twenty
eight.
Seventy
eight
and
lastly,
scheduled
content
on
the
content
listing
previously
just
had
published
or
unpublished
as
its
status.
It
now
also
shows
whether
or
not
content
is
unpublished,
but
also
scheduled,
so
it
will
say
that
the
content
is
scheduled
to
be
published
at
a
particular
time.
B
Let's
see,
there
are
a
number
of
one
to
twelve
issues
that
are
actually
still
open,
I
think
there's
twelve
of
them,
and
these
twelve
issues
are
either
cleanup
tasks,
things
that
could
be
done
to
just
kind
of
fit
within
the
minor
updates
that
have
just
code
rearrangement
like
issue
361.
That
is
just
moving
views
out
of
the
default
views
out
of
these
module
and,
if
their
their
respective
like
node
and
use
our
module,
for
example.
B
So
that's
just
a
minor
code
rearrangement
and
about
ten
of
them
are
UX
related
issues
that
have
a
a
modest,
a
minimal
amount
of
code
change.
I
should
actually
say
so
simple
things
like
changing
labels
on
things
or
potentially
like
adding
states,
count
States
to
particular
properties
or
adding
additional
links
in
places
or
just
you
know,
really
small
fixes
here
and
there.
B
That's
in
it,
let's
see
items
that
did
not
get
completed
a
worth,
noting
here
as
well
and
they've
been
moved
to
the
1.13.
Releasing
that
includes
dashboard,
which
was
only
added
to
the
1.12
release.
Like
a
couple
of
weeks
ago,
momentum
kind
of
came
out
of
nowhere
behind
that
particular
initiative
and
I
I
did
do
some
code
review
on
that
one
because
it
did
move
into
needs
review
a
couple
of
times
over
the
past
week
and
it
looks
really
good.
It's
definitely
a
real
solid
start,
but
it's
currently
been
tabled
for
1.13
cuz.
A
I
want
to
interrupt
so
I
updated
the
roadmap
for
all
the
stuff
that
we
got
into
112
and
I
added
dashboard
to
113,
because
I'm
so
excited
about
it.
I
think
everybody's
really
gonna
want
it,
and
I
would
like
to
kind
of
put
our
focus
on
that
one
for
the
next
issue,
because
it's
pretty
close
right
now,
if
we
can
get
in
early,
so
I
think
it'll
also
be
a
great
promotional
future,
be
able
to
announce
that
we
have
a
useful.
That's.
B
Great,
let's
see,
and
the
other
thing
that
we
didn't
get
completed-
that
we
moved
to
113
is
feel
double
file
types,
the
ability
for
files
to
have
bundles
and
fields
on
them.
That's
issue,
26,
32,
I,
haven't
actually
checked
in
on
this
one
Jen.
You
said
that
there
was
some
compromising
going
on
around
the
scope
of
it.
Can
you
elaborate
on
that
sure
so.
A
The
main
reason
everybody
uses
file
entity
in
Drupal
7
is
because
there
are
a
ton
of
other
modules
that
depend
on
it
and
I
think
most
of
the
things
that
those
other
modules
needed
are
la
making
the
file
an
actual
entity
are
included
in
vector
core.
So
it's
the
less
necessary
in
backdrop
than
it
was
in
Drupal.
I.
Think
the
feature
of
having
those
file
types.
The
field
may
not
be
an
80%
use
case.
So
there
was
a
lot
of
conversation
in
the
issue
to
about
like
this
is
a
lot
of
code.
A
The
ball
is
something
that
people
are
starting
to
feel
like,
don't
need
and
so
trying
to
figure
out
how
to
separate
out
the
features
we
do
need
from
the
features
we
don't
need
from
file.
Enemy.
Module
has
sort
of
been
this
sticky
point
where
final
enemy
works
in
the
huge
conglomerate
of
code
that
it
currently
is
so
we're
time
to
just
put
it
all
in.
But
looking
at
the
massive
code
that
actually
turns
out
to
be
is
making
a
couple.
A
People
nervous
mainly
got
plum
on
Nate
have
been
doing
much
work
on
it
and
there
are
people
like
me
were
like:
oh,
let's
just
save
little
tiny
pieces
of
it
and
when
I
go
and
try
and
pull
out
like
the
ability
to
upload
a
file,
it
is
complicated
because
you're
pulling
like
a
little
bit
from
all
of
these
different
parts
in
the
module
and
I'm
not
entirely
sure
my
individually
pulled
out.
It's
gonna
work,
at
least
not
in
the
same
way
as
well
as
it
did
when
it
was
all
part
of
the
huge
magic
code.
A
So
I
think
the
consensus
in
that
issue
was
maybe
this
shouldn't
be
scheduled
for
court
inclusion,
as
is
maybe
we
need
to
revisit
the
pieces
that
are
actually
needed
and
add
those
individually
and
because
there
isn't
even
a
contributor
file
inity
for
backup
right
now,
people
are
starting
to
wonder
like
how
much
it
is
it
that
we
do
really
need.
My
concern
is
because
there
isn't
a
kinship
version
of
file
in
a
new.
We
don't
have
all
of
this
functionality.
There
might
be
people
who
aren't
using
fact
references.
A
They
feel
like
the
functionality
they
need
is
missing.
So
I,
don't
know
what
that
means
long
term,
whether
we
need
to
just
port
the
module
so
that
we
have
something
in
a
state
look.
We
could
take
this
for
requests
and
turn
it
back
into
a
module
and
say
here
are
the
pieces
that
we're
missing.
At
least
people
could
look
forward.
Pickaxe
accurate
usage
counts
on
like
how
many
people
actually
needed
it,
or
if
we
should
just
say,
maybe
it's
not
necessary
and
let's
pull
out
pieces
we
know
are
so
we
don't
know
yet.
A
B
B
Anyway,
it's
still
as
it
has
been
for
all
of
the
1.11
release,
still
in
a
really
good
place
as
far
as
its
implementation,
like
it's
still
all,
really
solid,
it's
basically
direct
for
the
file
entity,
the
parts
that
aren't
already
in
core-
and
so
we
know
from
a
stability
standpoint
that
it's
it's
really
good.
On
that
front,
the
implementation
is
good
and
the.
B
B
That
does
it
for
the
1.12
updates,
there's
a
good
number
of
things
that
have
gotten
in
to
more
things
that
we
could
potentially
still
continue
can't
if
you're
looking
for
work
to
get
in
before
the
one
that
probably
least
check
out
both
the
1.12
milestone
and
the
111
for
milestone
on
github
for
a
list
of
issues
that
are
still
rolling
along.
So
that's
it.
The
next
up,
we've
got
just
kind
of
general
discussion.
B
A
Am
and
now
I'm,
not
muted,
sorry,
yes,
so
last
week
we
talked
a
little
bit
about
how
to
better
manage.
Our
milestones.
Document
in
particular,
had
noticed
that
there
are
a
bunch
of
new
issues
appearing
in
milestones,
and
so,
if
you're,
trying
to
work
on
the
things
that
are
in
a
milestone,
new
stuff
shows
up
in
your
like.
Why
is
this
in
here?
Did
we
talk
about
this?
This
is
something
one
person
wanted
to
be
in
a
milestone,
like
maybe
Jen,
or
is
this
something
that
everybody
has
a
consensus
and
agreeing?
A
A
Somebody
else
needs
to
go
to
the
issue
and
say:
yes,
this
is
a
priority
and
then
market
with
the
milestone,
and
as
long
as
there
are
two
people
who
are
talking
about
the
issue
who
agree
that
it's
a
priority,
then
it
can
go
into
the
milestone
queue,
I
think
for
now,
two
people
is
probably
enough
over
the
long
term.
That
might
end
up
being
really
easy
to
get
a
consensus
on
what
goes
into
the
milestone.
We
might
need
to
have
some
kind
of
gatekeeper
on
the
milestones,
but
we
don't
have
that
much
activity
now.
A
Miles
or
added
a
new
tab
called
milestone.
Candidate
I
think
definitely
recommended
a
better
label.
Milestone
suggestion
something
like
that
which
I
thought
could
be
valuable.
We
could
review
after
a
release.
We
could
review
all
of
the
issues
that
are
tied
with
milestone
candidates.
I
hear
the
any
of
these
here
that
looked
like
obvious
contenders.
A
For
yes,
we
need
this
feature
or
yes,
this
is
a
bug
fix
that
needs
high
priority
or
something
like
that,
and
then
that
way
we
can
sort
of
have
a
list
of
a
backlog
of
things
that
some
people
think
are
super
high
priorities
that
we
can
go
through.
But
there
are
things
in
there
that
we
think
definitely
aren't
a
high
priority.
We
can
remove
label
I,
don't
know
who
the
we
is
there,
but
I
think
having
a
way
to
organize
these
issues.
A
To
start
would
be
good
and
we
can
figure
out
who's
responsible
for
making
decisions
later.
It
could
be
something
that
gets
kicked
to
the
PMC.
So
since
the
PMC
is
responsible
for
deciding
the
future
of
the
project,
they
could
take
a
look
at
them.
After
your
upcoming
a
milestone
and
say,
does
this
look
reasonable.
E
A
A
This
is
something
document
recommended
I.
Think
it's
a
good
one.
We
should
try
it
maybe
Zuko's.
It
also
might
be
good
to
write
down
this
process
for
anyone
new
is
coming
into
the
cork
you
and
wants
to
figure
out
how
things
work
just
having
a
general
introduction
to
working
in
backdrop
core.
This
is
how
she's
getting
image
anyone
can
change
their
tags.
This
is
a
type
you
can
add.
A
Please
don't
change
their
milestones
unless
and
then
have
the
criteria
there
for
whatever
that
is
just
I,
think
a
little
more
visibility
and
explanation
as
to
how
these
things
get
decided
would
be
good,
and
if
we
need
to
change
how
they
get
cited
in
the
future,
a
lot
of
ways
to
update
about
documentation,
community,
so
Tim
I
think
you
asked
last
week
where
that
was
updated.
I
don't
know
if
you'd
had
any
thoughts
about
where
we
should
put
it
like.
Maybe
in
the
setting
of
a
section
or
matchup
Seamaster
org
for
developers,
we.
C
Did
am
I
muted?
No,
we
did
I
think
you
suggested
that
we
created
a
github
issue
to
talk
about
this
and
an
issue
did
get
created.
There
hasn't
been
any
discussion,
although
I
think
we
did
throw
out
that
the
proposed
contributors
guide
on
background.
This
would
be
a
place
to
put
this
that
doesn't
exist
yet,
but
I'm
gonna
try
and
start
working
on
it.
So,
okay
does
that
make
sense.
Yeah.
A
So
we
have
this
book
right
now,
I'm
sure,
I'll
link
it
together,
looking
like
structural
sense,
called
backrub
developer
notes.
It
might
be
good
to
put
our
contributor
guide
in
here.
Okay,
I,
don't
know
how
like
it
makes
sense
to
organize
it,
but
that
might
be
a
place
where
like,
if
you
have
developers
looking
into
stuff
anyway-
and
you
want
to
get
some
introductions
to
each
other.
So
it's
good.
We
also
have,
if
we're
going
to
make
a
contributor
guide
to
things
great
idea.
A
We
also
have
a
bunch
of
stuff
on
the
github
canned
shrimp
group
readme
file.
That
might
be
good
to
include
here
too.
So,
like
you
can
be
a
contributor
to
backdrop.
If
you
never
touch
core
and
I
would
love
that
our
documentation
he
just
is
welcoming
about
that,
is
about
how
the
core
process
works
so
just
somewhere
where
we
can
send
people,
it's
like.
What
is
it
like
to
work
on
back
job
would
be
fantastic
sure.
A
A
A
Can
you
throw
a
link
to
that
if
you
have
it
into
the
Gator
channel
and
don't
I
work
on
that?
Okay,
but
just
that
one
update
from
last
week
was
just
that.
I
did
create
a
tag
and
there
was
a
ton
of
stuff
that
had
been
given
a
milestone
in
the
last
release
where
I
removed
the
milestone,
add
tag
so
that
we
can
start
trying
some
kind
of
process
around
moving.
E
A
A
In
the
design
meeting
a
couple
minutes
ago,
Luke
we
were
talking
about
the
backdrop
birthday
parties
which
should
start
on
the
15.
So
I
am
happy
to
host
the
first
one
at
sideshow,
which
is
a
burger
beer
garden
and
kicking
dog
friendly,
very
convenient
for
us
here
in
the
Bay
Area,
but
I
thought.
That
might
also
be
a
good
point
to
kick
off
user
groups
too.
So
we
talked
about
starting
poisoning,
so
yeah.
E
A
They
have
yes
both
valid
concerns.
They
do
have
two
covered
areas
so
that
if
it
is
raining,
you
don't
get
wet,
they
have
standing
heaters
so
that
it
is
not
uncomfortable,
I'm,
not
sure,
I'll
call
it
comfortable
in
those
situations,
but
we
have
eight
in
there
in
the
district
serious,
it
is
a
little
small,
but
it
doesn't
I,
don't
know
we
haven't
had
problems
like
unless
they're
having
some
kind
of
other
party,
there
it'll
probably
be
okay.
We
can
also
always
relocate
to
yeah
other
places
nearby.
E
Why
don't
we
pencil,
then,
with
like
really
thick
heavy
pencil
at
the
mall
game
and
get
that
get
that
all
together
and
I'll
I'll
try
to
chip
in
with
as
much
you
know:
I,
don't
wanna,
throw
more
things
in
your
plate,
so
so,
whatever
whatever
I,
can
organize
your
plan,
I'll
invite
all
of
my
user
group
people
to
it
and
promote
that.
Okay,.
A
C
E
A
Great
anything
else,
you
guys
mind
chat
about
no
need
anything
dad.
No,
okay,
all
right.
Let's
go
ahead
and
wrap
this
meeting
and
you'll
return.
The
issue
queue
focus
on
the
few
remaining
issues.
We
can
definitely
get
into
112
and
celebrate
the
excitement
about
the
release
date:
ready
room;
okay,
thanks,
everyone,
okay,
bye,
thanks
for
watching.