►
From YouTube: Backdrop Weekly - May 7, 2020
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
2020-
and
this
is
the
weekly
backdrop
developer
meeting-
we
get
together
every
week
and
talk
about
the
progress
of
backdrop
and
what's
happening
in
the
entire
ecosystem.
From
the
development
standpoint,
we
like
to
do
little
instructions
to
go
through
everybody.
That's
here
on
the
call,
let's
start
with
you,
Jen
sure.
B
A
E
Making
jokes
about
Luke,
muted,
so
probably
better
I
did
see
your
your
effect.
You
know
Luke,
so
I'm
Tim
I'm,
coming
to
you
today
from
my
parent's
basement
and
do
soda
and
I
had
considered
taking
the
week
off
but
realized
we're
talking
about
initiatives
that
being
that
I've
been
pushing
these
for
a
while
I
thought:
I
better
I,
better,
not
miss
the
meeting
so
I'm
here.
G
A
A
Super
ok:
let's
go
into
the
project
report.
We
start
off
with
115.
That's
the
current
version
of
backdrop
and
issues
that
we're
working
on
to
improve,
usually
with
bug,
fixes
and
things
like
that
in
the
current
release.
There's
two
issues
of
note
that
are
getting
some
attention
right
now,
one
of
which
is
one
of
the
follow-ups
to
flexible
layouts,
adding
the
ability
to
disable
the
layout
builder.
A
If
you
don't
want
your
site
or
end
users
to
be
able
to
create
custom,
flexible
layouts,
then
this
issue,
41
61,
makes
it
so
that
you
can
disable
that
functionality
within
layout
module.
It's
been
marked
our
TBC
it's
in
the
115
to
milestone,
which
I
suppose
it
could
stay
there.
It
might
also
be
thing
that
we
might
put
into
1/16
only
I'm,
not
sure
about
that
functionality,
but
that's
what
milestone
a
was
put
into
at
the
time.
So
it's
currently
Mike
115,
2
and
PHP
7.4
support
issue
43082.
A
That
would
be
great
to
get
resolved
as
soon
as
possible.
Joseph
here
joining
us
has
done
a
lot
of
the
work
making
all
those
ports
possible
and
indigo
gsella
has
been
going
back
and
forth
with
him
on
on
addressing
all
the
feedback
so
also
mark
you
guys
about
going
back
and
forth
and
working
those
issues
out.
A
So
both
of
those
would
be
nice
to
get
completed
before
May
15th,
which
will
be
the
release
of
116,
but
it
will
also
be
the
final
release
of
115,
which
will
be
one
15.2,
I
should
say,
except
for
security
updates,
because
115
3
might
come
out
if
there's
any
security
issues.
So
that's
it
for
115
to
116
is
the
next
minor
version
of
backdrops.
That
includes
a
hefty
list
of
new
features.
This
time
around,
which
I'm
very
excited
about
the
once.
It's
have
status
updates
since
last
week.
A
First
of
all,
last
week
was
the
30th
of
April
and
May
1st,
which
was
this
past.
Friday
was
feature
freeze,
and
so
we
have
completed
adding
new
functionality
into
116,
with
some
exceptions
that
minor
UX
changes
can
still
go
in
and
things
like
string
changes
and
things
of
that
nature.
There's
still
some
space
for
those
changes.
A
So,
let's
see
one
major
thing
that
we
got
completed
in
this
past
week
was
a
new
user
interface
for
text
format
configuration
the
text
formats
previously
had
this
rather
unwieldly
long
form
that,
as
you
were,
checking
and
enabling
certain
filters
on
your
formats,
other
parts
of
the
form
we're
changing
and
we've
shortened
up
that
big
long
form
and
moved
the
configuration
of
individual
filters
into
dialogues
making
it.
So
that
form
is
a
little
bit
more
manageable.
A
A
That
just
has
some
minor
suggestions
about
the
way
the
interface
is
displayed,
the
location
of
check
boxes,
for
example,
and
the
styling
on
some
of
the
new
buttons.
So
4378
is
our
follow
up
to
improve
mostly
the
consistency
of
that
new
text:
format,
user
interface-
so
we'll
still
be
working
on
that
one
in
this
next
week,
but
even
if
we
don't
get
it
in,
it's
still
UX
changes,
so
it
could
go
in
even
after
release.
A
But
like
always
this,
when
we
make
the
new
release,
that's
usually
when
we
publicize
a
lot
of
the
new
features
so
really
be
preferable
to
make
it
so
that
the
screenshots
all
look
like
the
final
version
rather
than
making
it
a
release.
Announcement
take
screenshots
and
then
change
it
right
after
points.
A
E
That's
sure
too
much
to
say
other
than
so
that
the
goal
here
was
that
users
can
now
use
tokens
to
modify
that
submitted
by
in
Dateline
on
nodes
and
the
main
thing
we
did
at
the
end
was
we
took
out
that
there
were
some
problems
and
conflicts
with
comments
so
right
now,
this
works
only
on
the
node
itself.
That
doesn't
work
on
comments
and
it
looks
like
it's
been
merged.
Is
that
correct,
yep,
yep.
E
A
Great,
let's
see,
we've
also
got
one
minor
issue
to
try
to
get
wrapped
up,
and
that
is
I
can't
remember
what
this
spun
out
of
that
cache
clear
all
we
had
a
discussion
where
it
was
about
to
be
added
new
cache,
clear.
All
calls
were
going
to
be
added
somewhere
and
I
said
that
we
shouldn't
do
that,
because
we
have
more
granular
alternatives
to
cache
clear
all
and
then
it
was
raised.
Well,
isn't
can't,
does
that
mean
the
cache
Clairol
was
deprecated,
and
the
answer
to
that
was
yes,
but
we
haven't
marked
that
anywhere.
A
So
21:58
is
the
suggestion
that
we
officially
market
is
deprecated
and
at
a
change
record.
So,
although
that's
a
really
small
change
and
won't
actually
affect
anyone,
because
it's
it's
just
documentation,
it
is
something
that,
in
order
to
deprecated
it
in
1/16,
we
need
to
do
in
the
next
couple
of
days.
G
G
A
A
Okay,
21:58
so
deprecated
in
cache
clear
all
we
would
like
to
get
that
done
before
1:16
also
related
to
things
that
needed
change
records
to
document
their
changes.
Early
very
early
in
the
release
cycle
1:16,
we
merged
entity
cache
into
core
issue
number
74,
which
I
think
Joseph
undertook
purely
because
it
was
the
oldest
open
issue.
A
In
our
mark
you
what
so,
congratulations
Joseph
on
completing
issue,
number
74,
even
though
I
know
that
was
done
months
ago,
and
this
past
week
we
got
a
change
record
drafted
Joseph
drafted
the
change
record
for
that
and
we're
reviewing
it
to
get
it
ready
for
publication.
So
that's
looking
really
good.
A
A
Bw
panda
is
checking
the
alternative
that
was
posted
to
the
issue
queue
saying
like
we
might
not
need
this
because
it's
easily
done
without
any
core
modification
and
so
he's
verifying.
If
that
alternative
will
be
suitable
for
his
purposes
and
if
so,
then,
potentially
we
might
close
that
issue
out
entirely
for
now,
31
74
has
just
been
moved
out
of
the
160
milestone,
but
the
issue
itself
isn't
actually
closed
yet.
A
And
that's
it.
The
116
milestone
is
looking
really
sparse
right
now,
we've
only
got
three
issues
in
the
whole
116
milestone,
which
I
think
we
have
covered
all
three
of
those
in
that
update.
So
it
looks
like
it's
gonna
be,
dare
I,
say
it
somewhat.
Leisurely
finished
116,
which
I
absolutely
appreciate.
A
A
A
good
point:
do
we
have
a
testing
release?
Yes,
we
do
so
there's
a
116
preview
tag
that
was
cut
yesterday.
I
think,
however,
and
so
you
can
download
off
of
github
but
I,
don't
think
that
we
published
the
release,
notes
for
it
yet,
and
so
that
means
it's
not
on
backdrop:
CMS
org!
It's
that
right,
Jen,
okay,
so,
yes,
there
is
a
preview
version.
If
you
wanted
to
publicize
it
Tim,
then
you
could
link
over
to
the
tag,
but.
F
A
Not
not
really,
it
doesn't
say
anything
on
that
page.
Currently,
it's
just
like
here's
an
archive
and
because
it's
not
it's
not
a
publisher
released,
it
doesn't
even
have
like
the
official
backdrop,
release
that's
been
cut,
however,
for
core
the
packager
doesn't
really
do
anything
for
core,
so
it
doesn't
need
to
update
the
dot
info
files
or
anything
like
that.
So,
okay,.
A
F
A
E
A
What
ends
up
happening
with
it,
because
it's
like
in
X,
it's
called
it
116
dot,
Oh
preview
and
what
project
module
does?
Is
it
treats
it
as
though
it
were
like
an
alpha
or
beta
version,
and
so
it
doesn't
update
the
current
release.
It'll
still
show
115
to
115,
1
and
you'll
be
able
to
see
it
only
by
clicking,
like
view
all
releases
on
the
project
page
and
then
it'll
be
under
the
list
of
all
releases.
A
Yeah
that
could
be
I
mean
it
would
be
great,
I,
say
longingly.
If,
if
we
had
something
said,
here's
what's
in
116
like
it's
coming
and
then
said,
you
can
try
it
out
now,
like
here's,
the
preview
release,
but
it
also
wouldn't
hurt
I
mean
it
would
I
think
it's
good
to
give
people
an
idea
of
what's
coming
before.
It's
actually
happened
rather
than
116.
Is
here,
here's
all
the
new
stuff
in
it.
A
A
E
I
think
it's
a
little
bit
weird
that
we
chose
today
instead
of
after
the
release,
but
but
yes,
that's
what
we
apparently
decided
a
few
weeks
ago,
so
I
mean
I'm,
not
against
postponing
it
a
little
bit
further.
Although
we
could
talk,
you
know
we
could
have
a
little
bit
of
a
discussion
about
it.
I
don't
know.
B
A
E
E
The
goal
was
today
was
well
okay.
Earlier
this
year
we
did
some
strategic
planning
about
thing.
You
know
how
to
improve
the
way
we
do
business.
In
fact,
one
of
the
issues
that
came
up
was
how
to
prioritize
things
and
focus
our
energy
and
a
possible
solution
that
came
out
of
that
was
this
idea
of
initiatives
and
we
created
it's
been
like
two
months
ago
now:
I
think
we
created
space
on
the
forum
or
anybody
could
propose
an
initiative.
E
We
have
a
rough
idea.
Initiatives
are
sort
of
projects
with
some
definition
still
a
little
bit.
You
know
we'll
be
we're
fleshing
this
out
as
we
go.
Initiatives
might
be,
in
my
view,
fairly
specific,
so
I'll
have
an
end
date.
It
shouldn't
be
an
initiative,
wouldn't
be
like
fix
one
thing,
but
it
could
be
a
group
of
tasks
that
need
to
be
done
to
a
with
some
goal
and
it
might
have
a
none
date
or
it
might
be
kind
of
an
ongoing
thing
that
we
just
want
to
prioritize.
E
In
the
we
want
initiatives
to
have
a
project
lead.
They
should
have
some
definition
and
process,
I.
Think
I,
don't
know.
If
there's
any
other
major
criteria
anyway,
so
we
have
a
place
on
the
background
forums,
a
backrub,
CMS
Touareg,
where
anybody
can
introduce
an
initiative
and
initiatives
will
have
to
be
approved
by
the
PMC,
and
what
we
were
hoping
for
today
was
to
just
talk
about
in
an
ideal
outcome.
Today
we
might
actually
be
able
to
forward
a
couple
of
initiatives
to
the
PMC
for
sort
of
approvals.
E
My
own
idea
is
that
it's
helpful
to
have
sort
of
a
package
of
them
to
get
started
and
buy
a
packet
in
just
me,
two
or
three,
but
then
in
the
future
that
the
PMC
could
add
an
initiative
at
any
time.
They
chose
I'm
an
individual
case-by-case
basis,
but
the
main
reason
for
this
meeting
is
sort
of
like
it's
hard
to
pick
the
first
one,
because
I
feel
like
it's
a
little
bit
hard
to
pick
them
one
at
a
time
at
the
beginning,
because
we
want
to
pick
a
mixture
right.
E
We
don't
if
we
look
at
them
one
at
a
time,
it's
hard
to
say
like
to
get
a
good
mix
of
them
to
start
so
anyway.
So
that's!
The
goal
today
was
just
to
sort
of
look
at
what
we
have
so
far
and
if
an
ideal
world
to
put
forward
some
kind
of
proposal
for
the
PMC
about
which
ones
we
think
are
most
important,
anybody
have
any
questions
or
anything
to
add
to
that
go
ahead.
B
Great
I
was
also
just
reading
your
issue
when
the
PM
CQ
about
how
to
choose
them,
and
it
looks
like
that's
also
still
up
for
conversation
well,
I
think
the
things
you
just
said
about
having
a
clear
definition
having
a
leader
I,
think
those
are
all
solid
things
that
will
make
a
proposal
more
attractive.
E
E
C
C
C
Contained
in
that,
I
would
like
there
to
be
the
ability
to
use
Drupal
modules
or
Drupal
themes,
unchanged,
if
possible.
Now,
currently,
there's
there's
porting
instructions
that
we're
all
familiar
with
to
create
backdrop,
themes
and
backdrop
modules
and
we're
out
of
you
know:
Drupal
7
modules,
but
as
part
of
sort
of
a
welcoming
initiative,
a
welcoming
feeling
courts,
people
wouldn't
become
from
Drupal
I,
was
proposing,
if
possible,
turning
on
a
layer
so
that
you
can
just
say,
okay,
you
know
you
know
what,
without
without
without
any
guarantees
that
it'll
work.
C
If
you
want
to
plug
it
in
and
and
let
it
rip
layer
it,
let's
see
what
happens
now
in
particular,
you
know,
for
example,
with
with
themes
the
the
biggest
difference
that
I'm
aware
of
is
you
know
replacing
I
the
foot
shouting
they've
been
in
Drupal
7
was
provided
by
the
page
tip
of
it
with
layout
manager,
and
you
know,
maybe
it
she's
one
of
there
that
maybe
could
either
apply
a
default
layout
manager,
template
or
actually
use
it.
Simple
tip,
I
mean
I'm,
not
much
you
know.
C
Do
you
guys
are
are
more
familiar
with
what
would
be
involved
with
that
and
and
for
the
for
the
module
I
mean,
obviously
there's
enough.
That
has
changed.
That
did
there's
no
way.
We
could
guarantee
that
the
functionality
would
work,
but
the
difference
would
be.
You
know
the
requirements
had
the
intro
file
changed
in
order
for
to
be
recognized.
What
would
be
would
be
relaxed
with
this
or
you
could
click
a
button.
You're
like
saying,
ok,
show
me
your
Drupal
modules.
Look
fire
it
up.
Let's
what
happens
the.
E
Quick
summary
would
be
to
just
make
easier
to
use
rupal,
seven
themes
and
modules.
Yes,
that's
a
quick
way
to
say
what
I
just
said.
We
got
to
move
through
the
list,
this
kind
of
quickly
I'm,
sorry,
it's
okay,
the
next
one
is
include
several
ready
to
use
themes.
This
Luke
also
proposed
we've
discussed
broadening
that
out
too
just
to
make
it
easier
for
site
builders
to
customize
the
look
of
their
site
without
a
theme,
but
but
you
know
the
the
idea
that
Luke
originally
came
to
us.
E
C
E
I
added
a
couple
of
these:
the
documentation,
one
I'm
not
gonna,
get
very
specific
on,
but
basically
it's
just
at
you
know
make
documentation
better.
I
could
envision
something
like
the
user
that
the
Drupal
just
had
a
big
initiative
to
create
kind
of
an
official
course
on
getting
started,
and
that
might
be
the
kind
of
outcome
of
that
initiative.
I
think
I
also
had
a
better
support
for
contribute.
Maintainer
x',
and
that
was
just
the
idea.
E
C
Me
that's
just
some
o
for
WordPress
s,
ability
to
import
and
export
ideas.
I
think
you
should
be
able
to
click
a
button,
then
some
doesn't
be
cover
all
them,
but
within
some
backed
up
installations
and
say,
dump
the
data
and
then
have
another
backup
installation
they
can
suck.
In
that
same
data
like
when
you
have
those
two
endpoints
and
I'd
be
satisfied
with
that.
E
The
next
two
I
believe
we're
added
by
another
user
that
I'm
not
familiar
with
somebody
fairly
new
to
the
community,
better
caching
and
mobile
approach
and
I
I.
Don't
know
what
more
to
say
about
that:
I
think
it's
fairly
descriptive,
better
editorial
compatibility
is
an
SEO.
I
was
just
looking
at
again
the
same
person
added
this
one
and
I
think
they
were
look
things
like
Gutenberg
and
WordPress
and
suggesting
that
kind
of
usability
issues.
Although
we,
you
would
need
to
look
at
that
closer.
E
E
E
The
last
one
I
just
a
few
minutes
ago,
just
to
throw
it
out
there,
which
again
we've
already
we're
already
doing
work
on
this,
but
I
could
envision
a
usability
sort
of
testing
initiative
that,
to
some
extent
we
already
have
the
usability
and
design
weekly
meeting.
So
I
know
if
this
is
necessary,
but
I
thought
it
least
worth
considering
whether
or
not
that
was
a
good
initiative.
E
E
Mice,
I'm
gonna,
not
hearing
anyone
else,
jump
forward
sort
of
my
goal.
It
would
be
to
sort
of
send
how
did
I
this
is
a
fairly
arbitrary
would
be
like
this
forward.
Three
of
these
to
the
PMC
and
again,
this
is
where
the
including
them
in
a
package
gives
us
the
ability
to
sort
of
pick
three
complementary
ones,
sort
of
get
started
with,
and
then
additional
ones
could
be
added
later
and
so
I
think
I've.
You
know,
I,
don't
know
it.
E
C
E
That
makes
me
think
that
what
a
good
way
to
do
would
be
to
quickly
just
sort
of
go
around
who's
at
the
table
right
now
and
ask
everybody
to
indicate
what
their
tops
say.
Two
or
three
are,
and
that
would
give
us
all
a
sense
of
what
other
people
see
as
priorities
and
and
then
we
could
see
if
there's
a
common
theme
that
emerges
so
Luke,
do
you
have
I
think
the
theme?
One
is
your
top
priority.
You
want
to
name
one
or
two
more.
That
would
be
your
second
and
third
choice:
Oh,
probably
telemetry.
B
The
theme
one
is
important
to
me
too:
I
also
like
the
idea
of
Drupal
compatibility
helpers,
especially
between
now
I
need
to
play
for
triple7
I,
think
easier.
We
can
make
it
for
people
to
move
from
Drupal
7,
the
better
her
backdrop
home
and
I,
like
them
all
I,
like
telemetry
you'd,
probably
be
my
third
one,
but
also
the
SEO,
and
that
are
cashing
in
mobile
kind
of
go
hand
in
hand.
B
E
E
A
Yeah
I
thought
that
one
was
was
pretty
interesting,
though
nonetheless
is
being
something
that,
if
given
dedicated
resources,
could
have
some
valuable
outcomes,
but
I'd
probably
put
that
one,
as
my
second
one
I
think
my
first
mozi
telemetry
we've
been
talking
about
it
for
a
long
time
and
haven't
had
like
that.
The
interest
is
strong
there
and
the
scoping
of
it
seems
like
we
could
solidify
that,
but
yeah,
it's
always
been
like
we,
the
complexity
of
building,
something
that
is
both
server-side.
You
know
like
backdrop,
CMS
org,
+
backdrop
like
those
that.
F
A
E
E
Good
well
I
think
that
just
leaves
me
and
my
probably
top
two
so
about
you
know.
My
criteria
are
a
little
bit
issues
I
understand
the
best
and
in
you
know,
things
like
better
caching
and
mobile
approach.
I,
don't
really
know
what
an
initiative
would
address
there.
So
it's
hard
for
me
to
be
as
excited
about
that,
not
that
it's
not
important
but
I
like
telemetry
and
and
because
also
there's
already
some
momentum
there,
but
I
think
it
also
it's
broad
enough
and
and
could
really
use
sort
of
the
structure
of
a
committee.
E
I
think
that
the
theming
one
is
also
that
really
me
at
the
top
of
my
list.
Usability
would
be,
although
and
I
think
that
it
would
benefit
from
being
an
initiative,
but
I
I'm,
fairly,
confident
that
will
make
some
progress,
whether
it's
an
initiative
or
not.
I
think
those
are
probably
my
three
top
you
know.
Documentation
is
sort
of
on
the
edge
I
guess,
I'm
least
convinced
that
we
have
sort
of
the
energy
around
documentation
right
now
it's
important,
but
that
might
if
I
were
to
propose
one
six
months
from
now
it
might
be
documentation.
E
B
E
B
E
E
B
E
C
E
It's
fair
to
say
one
of
the
criteria
and
picking
them
should
be
which
ones
are
going
to
benefit
the
most
right.
If
something
is
moving
along,
fine
are
likely
to
move
along
without
it
being
initiative,
there's
less
incentive.
On
the
other
hand,
we
don't
want
to
pick
an
initiative
that
has
no
momentum
and
isn't
going
to
get
anywhere
so
yeah.
D
E
B
Don't
we
say
like
these:
are
the
two
committee
in
the
meeting
like
universally
really
likes
and
then
the
other
close
followers
were
these
ones?
And
that's
a
you
know,
proposal
for
the
PMC
won't
say
like
our
proposals
that
we
accept
these
two
initiatives
and
then
the
follow
would
be
like
here
are
the
other
ones.
If
any
of
you
feel
strongly
that
one
of
these
also
deserves
attention
discussed
below.
But
that
way
the
proposal
could
be
like
yes
and
they're
like
a
follow-up
would
be
like
you
want
to
add
anything
else
and
I.
E
I
think
that's
fair.
Do
we
have
I
think
we
have
like
leadership
for
especially
if
we
just
have
to
because
I
think
Luke
you've
either
just
said
it
now
or
said
it?
The
last
meeting
right
that
you
would
take
some
leadership
for
a
theming
one?
Is
that
correct,
I
I
said
it
in
good
places.
I
thought
you
did
it,
but
I
wanted
to
be
sure.
E
I
have
already,
although
if
somebody
else
wanted
to
do
it,
I've
already
taken
a
little
bit
of
leadership
on
the
telemetry
one,
although
then
it
fell
off
and
I'm
not
again,
not
sure
what
the
next
two
months
are
gonna
be
for
me,
I'd
open
to
someone
else,
taking
leadership
on
that,
but
I
could
otherwise
trying
to
push
that
one
forward.
I
have
for
the
last
six
months
been
thinking
to
advocate
for
that
as
an
issue
and
so
sort
of
helping
with
the
an
initiative
would
be
the
next
step.
Yeah.
C
Well,
yeah
I
think
actually
I
want
to
throw
a
little
support
for
the
better
support
for
contribute.
Maintainer
x'
one
because,
like
I
I,
think,
that's
not
quite
right
hands
I
remember
I
did
it
might
not
be
quite
shovel
ready,
but
it
it
has
a
similar
notion
to
me.
It's
hitting
a
parallel
thing
to
the
telemetry
one
where
telemetry
is
we're
looking
to
get.
You
know,
direct
feedback
from
our
users.
E
I
suggested
that
one
and
partly
around
I,
think
some
of
the
reasons
you
just
said.
I
feel
like
our
contribute
is
that
contribute
include
themes,
and
maybe
one
of
the
reasons
I'm
not
like
advocating
for
it
strongly
today
is
I
feel
like
if
we
got
simply
boosted
contributed
theming,
which
the
other
initiative
might
cover,
that
that
would
get
us
part
way
and
that's
where
it's
needed
even
more
than
with
modules.
E
But
I
do
feel
a
little
bit
like
well
that
one
of
the
things
that
initiative
could
be
good
at
is
addressing
sort
of
process
issues
that
it's
hard
for
any
individual
to
deal
with
and
for
me
sort
of
like
supporting
contreras
as
a
broad
topic
which
it's
hard
for
any
one
individual
to
deal
with.
But
a
group
of
people
could
talk
about
it.
It
makes
some
steps
forward.
So
it
feels
to
me
like
it
would
be
a
good
initiative,
but
I
think
probably
I
I
backed
off
of
it
a
bit
just
because
of
it.
B
E
E
B
B
B
E
B
E
There's
somebody
who's.
Let
me
take
a
stab
at
this
at
drawing
up
sort
of
a
proposal
based
on
the
feedback
we
got
today.
I
share
it
with
a
couple
of
you
weeks
of
a
meeting.
I,
don't
know
if
we
wanted
to
bring
it
back
like
a
week
from
now
to
this
meeting
or
not,
we
can
decide
that
as
we
go
I
guess,
it
would
benefit
from
that
or
not
I.
Think.
B
It
would
be
good
if
we
create
the
PMC
issue
soon,
so
that
we
can
get
pantsies
eyes
on
it,
but
I
think
if
we
can
do
that
between
now
and
the
next
meeting
we
can
use
next
week's
meeting
to
say
this
is
what
was
proposed
to
the
PMC
and
that
way,
if
there's
anyone
at
next
week's
meeting
who
wants
to
weigh
in
on
it,
we
have
a
chance
to
adjust
if
necessary.
Okay,.
E
E
Part
of
my
motivation
is
I'm,
hoping
that
the
initiative
process
might
start
of
creating
different
groups,
that
this
is
an
opportunity
to
bring
new
people
and
get
them
involved
in
in
a
very
specific
initiative.
I,
don't
know
if
that'll
work
or
not,
but
one
of
our
goals
should
beat
again
that,
as
I've
said
many
times,
it's
not
to
have
the
same
four
or
five
of
us
working
on
all
the
initiatives,
but
really
to
figure
out
ways
to
bring
in
new
people
to
help
on
these
specific
projects.