►
From YouTube: Backdrop Weekly Meeting - Feb 6, 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).
B
Okay,
I've
been
nominated
and
were
volunteered
I
guess
to
help
facilitate
today's
goal-setting
discussion
for
the
deaf
group,
we're
going
to
as
we
just
give
in
a
recent
outreach
meeting,
tried
to
structure
this
a
little
bit
more
and
hopefully
engage
as
many
people
on
the
call
as
possible.
So
we
are
taping.
This
I
should
make
that
disclaimer
too.
This
is
being
videotaped
on
YouTube.
B
So
if
you
anything,
you
say
or
your
appearance
will
be
recording
if
you
want
to
add
or
turn
off
your
camera,
do
that
if
you
I,
don't
think
they're
raising
hands
things
work
so
good
in
the
last
meeting,
but
we
could
try
to
do
that.
It's,
although
it's
not
required,
but
do
try
one
of
the
things
we
want
to
do
in
this
meeting.
Let's
give
everybody
a
chance
to
talk
and
to
get
ideas
out
there
and
I'm.
C
B
D
Yeah
sure
so
my
name
is
Greg
currently
logged-in
here
joining
from
Australia
I
do
not
have
any
as
I
mentioned
at
the
previous
meeting.
Any
professional
sort
of
like
goes
out
of
backdrop
I
do
that
as
a
as
a
hobby
and
because
I
love
the
community.
My
personal
goals,
when
it
comes
to
backdrop,
is
to
do
my
best
to
help
build
a
product
that
is
as
less
annoying
frustrating
and
as
easy
to
use,
as
can
be
so
that
people
being
on
board
to
the
project,
find
it
fun
to
work
with.
B
F
The
I
think
the
biggest
reason
I'm
here
today
is
just
to
be
available
to
be
part
of
the
conversation,
but
I
guess
I
could
add.
I
have
a
slight
focus
even
though
I'm
a
back-end
developer,
not
a
front-end,
developer,
I,
think
user
experience
is
probably
the
thing
that
I
do
the
most
to
try
to
help
with
when
I
see
something
that
looks
like
a
problem
in
workflow
or
something
like
that.
Usually
in
forms
I
try
to
see
if
they
can
help
fix
things
like
that,
make
it
easier
for
the
end
user.
G
G
H
I
B
Anything
else
look
so
I'm
Tim
I'm
in
Minnesota
in
the
US,
and
they
have
been
participating
in
this
college
for
over
a
year.
I
think
you
know
I'm
always
interested
in
the
process
and
how
to
improve
it.
B
I
know
I've
heard
from
a
number
of
other
people
and
I
agree
that
setting
priorities
like
how
we
set
priorities
on
addition,
that's
a
process
option
that
will
help
us,
reduce
waste
problem
possible
or
maybe
not
I,
don't
know
but
figuring
out,
better
ways
of
of
helping
people
the
right
people
who
want
to
help,
but
don't
have
a
particular
issue
to
work
on
sort
of
know
where
best
to
focus
their
time.
That's
a
key
issue
that
I
am
interested
in
I
want
to
acknowledge
something.
B
Jen
said
about
defining
initiatives
because
I
think
last
week,
during
our
our
dumb
meeting,
we
were
just
sort
of
rain
storming
for
this
meeting,
and
this
idea
of
initiatives
came
up.
This
sort
of
that
process.
Change
I,
think
that
there
might
be
some
I
wasn't
convinced
that
any
decision
had
made
to
use
initiatives
but
I.
Don't
you
hear
with
people's
feedback
and
I
think
that
should
be
part
of
our
discussion
connecting
and
I?
Think
sort
of
the
next
thing
we
kind
of
want
to
do
is
talk
about.
B
Not
quite
as
nimble
as
jackets
here
who
wanted
to
talk
about
what
I
had
suggested
talking
about
where
people
see
the
pain
points
on
or
what
are
the
the
problems
were
trying
to
solve
in
process
and
I?
Think
a
couple
have
come
up
like
a
wastage
that
better
use
of
people's
time
is
kind
of
a
pain
point.
The
one
I
brought
up
is
prioritization.
A
A
So
the
road
map
pages
is
kind
of
not
loose,
not
not
really
a
too
much
of
a
planning
document.
So
much
as
a
like
as
a
reactive,
like
here's
what's
being
worked
on
document,
but
at
least
it's
you
know
it's
more
accurate
that
way,
rather
than
saying
something,
because
we
don't
have
the
ability
to
really
make
anything
be
done
if
there's
no
enthusiasm
or
effort
behind
it.
A
A
B
A
A
I
C
I
B
Prior
to
this
meeting,
we
had
a
little
bit
of
a
discussion
about
the
PMC
and
exactly
what
its
role
is.
I,
don't
know
that
we
need
to
have
that
again,
just
a
certificate
that
that
discussion
is
going
on.
I,
think
I.
Think
a
number
of
the
ideas
people
have
suggested
about
improving
our
process
involved,
the
PMC
and
we'll
need
to
work
out
some
of
those
issues.
So
is
there
anything?
D
I
have
something
generic
to
add.
It's
not
specifically
to
features
because
features
usually
have
a
three
month
cycle
unless
they
get
pushed
to
the
one,
but
in
general,
how
the
issue
queue
works
and
recently
there's
been
voices
saying
that
this
confusion
or
that
it
makes
it
harder
for
people
to
sort
of
like
get
a
focus
and
get
things
done,
because
either
there's
too
many
opinions
or
there's
no
guidance
or
what
what
we
have
where
I
work.
D
D
Then
I,
guess
if
that's
a
pair,
so
some
people
expressed
concern
and
they
would
sort
of
like
prefer
that
there's
a
clear
sort
of
like
spec
specified
at
the
beginning
of
when
they
start
to
do
the
work
and
they
would
prefer
to
sort
of
like
work
in
whole
chunks,
I,
respect
that
nevertheless
I'm
one
of
those
people
that
work
I
contribute
a
lot
by
contribute.
Sporadically.
So
I
don't
have
big
chunks
of
time,
maybe
if
it
seems
so
it's
because
that
means
for
me.
D
D
So,
although
I
agree
that
we
should
get
an
official
plan
of
how
goals
and
specific
issues
are
being
worked
on,
being
structured,
I
would
still
like
to
leave
some
room
for
people
like
me
to
just
jump
whenever
we
want
to
have
fun
and
just
contribute
without
being
annoying
for
the
rest
of
the
people.
That
is
one
of
the
points
that
was
mentioned
last
week
was
or
the
week
before.
D
That
was
that
we
already
were
working
on
an
issue
and
there
was
a
pull
request,
but
I
had
a
different
sort
of
like
idea
and
a
father
pull
request,
and
some
people
said
now.
This
is
sort
of
like
disruptive,
which
all
requests
are
we
looking
at
now,
and
might
you
express
this
in
the
past?
It's
it's
really
bad.
That
get
love
did
I'm.
Sorry
does
not
offer
some
sort
of
collaborative
pool
request
system
so
that
we
can
sort
of
like
easily.
D
A
I
also
things
in
the
category
of
things
that
are
working
I
would
say
that
small
changes
in
iterative
changes
like
are
happening
and
an
adequate
pace
like
the
the
ability
for
people
to
say,
I.
Don't
like
this
word
or
there's
a
typo
here
or
fix
this
doc
block
I
feel
like
those
changes
are,
for
the
most
part
in,
like
they're
being
suggested.
B
B
E
Other
people,
like
I,
don't
think
he
might
be
calling
out
by
name
Wilma
and
I
were
sometimes
like.
You
know,
begging
for
a
review,
and
then
we
get
frustrated
so
so
not
to
not
to
sleep
the
the
fact
that
what
Nate
said
I
agree
with
like
when
it's
small
bug
fix-
and
everybody
agrees.
It
goes
through.
It's
totally
fine,
but
there
are
also
sometimes
small
bug
fixes
that
that
bike
shed
are
really
a
lot
I.
B
Want
to
pick
up
on
something
you
just
said:
you
like
tie
their
membership
in
the
PMC
to
that
and
I
don't
give
in
to
that
discussion
about
the
PMC
I.
Don't
know
that
the
PC
itself
really
has
a
role
in
deciding
making
those
decisions.
The
fact
that
somebody's
on
the
P-
and
he
might
just
give
them
work
but.
D
D
D
E
G
B
A
difference
between
what
is
it
is
actually
happening
and
what
people's
perceptions
might
be.
So
you
might
disagree
with
people's
perceptions
and
believe
them
to
be
completely
false,
but
if
they
have
those
perceptions,
they
have
them
and
I
think
that
there
could
be
a
perception
that
that
the
pmc
is
more
involved
than
it
is
or
or
that
it
should
be
more
involved.
One.
That's
just
something
we
need
to
be
aware
of,
like
also.
I
Be
facing
a
situation
here
where,
like
we
want
the
pmc
to
do
the
things
that
it
says
on
that
page,
but
they
won't
and
I
think
that
that's
kind
of
what
I
was
getting
to
before
the
meeting
started,
we're
like.
Maybe
we
need
to
change
the
PNC
so
that
they
are
more
active
right
like
so.
We
take
the
people,
we
know
we
don't
have
time
who
or
who
aren't
actively
contributing
and
replace
them
with
people
who
are
and
then
the
PNC
can
have
those
roles
and
I
feel.
I
Like
you
know,
we
set
out
the
job
of
the
p.m.
seats
before
we
had
a
PNC
with
like
what
do
we
want
the
PNC
to
do
and
I
don't
think
we
should
sacrifice
that
because
it's
not
happening
unless
that's
what
we
want
is
to
have
happen
what's
happening
now.
I
think
it
might
be
better
to
kind
of
review
that
holistically
and
be
like.
I
Is
this
what
we
want
the
PMC
to
do,
and
if
it
is,
then
let's
just
change
that
and
make
sure
the
PMC
does
it,
rather
than
being
like
we're
asking
you
to
do
these
things?
But
you
know
three
of
you
haven't
been
around
in
six
months
and
it's
really
hard
like
ping,
you
and
poke
you
and
email
you
and
try
and
get
you
to
respond
to
an
issue
where
so
we
had
people
in
the
community
who
are
active
contributors
and
who
are
doing
all
the
work
and
need
answers.
I
We
need
to
be
a
better
support
structure
for
them,
and
so
I'd
like
to
be
careful
about
changing
the
language
on
the
page
sort
of
like
what's
happening
versus
changing,
what's
happening
to
reflects
what
we
want.
That
might
might
be
something
we
should
consider.
Maybe
tap
away,
McLean
right
like
update
the
page
and
say
this
what's
happening
now
and
then
be
like
this
is
what
we
want
next
month
and
then
at
least
we're
both
being
honest
about
what's
going
on
and
what
we're
trying
to
get
one.
D
Thing
one
thing
that
I
would
like
to
that:
we
already
have
the
process
there.
When
the
PNC
was
fully
formed.
Sorry,
it
was
stating
something
along
the
lines
of
two
years
of
service,
or
maybe
at
least
two
years
of
service.
I
guess
and
one
of
the
goals
was
to
have
the
members
of
the
PMC,
be
a
diverse
group
of
people
and
to
have
diversity.
You
need
numbers.
B
D
I
B
Okay.
What
do
we
do
now
and
there's
been
some
suggestions
from
some
people
that,
like
oh,
this
is
where
the
pmc
should
jump
in,
but
Gregory
I
think
is
adequately
pointed
out
that
that
might
not
be
the
level
of
Union
the
decision
that
the
pmc
should
be
making
but
I
do
think
it's
fair
to
say
that
there
should
be
some
way,
that's
commonly
understood
of
like
okay.
What
do
we
do
now?
And
my
experience
has
been
that
those
issues
just
not
right,
that
they
don't
get
resolved
that
it.
D
This
is
where
Jen
mentioned,
that
we
need
to
find
some
Authority
or
a
person
that
that
has
some
level
of
authority.
So
if
the
problem
is
a
code
decision,
it
needs
to
be
one
of
the
core
committers
with
experience
in
coding.
If
it
is
a
you,
a
UX,
UI
issue
to
be
a
person
that
has
ideally
would
be
a
professional
in
the
field.
That's
what
I'm
saying
so
yeah
or
if
it's
a
design
issue
a
designer.
I
Think
that's
why
we
were
gonna
have
like
someone
who
was
officially
like
backdrops
design,
Authority,
and
so,
if
you
have
like
three
professional
designers,
but
one
of
them
is
the
design
authority.
That's
the
person
who
has
the
final
say,
and
so
this
would
become
like
another
section
in
our
leadership
page,
but
we
be
like
this
is
our
design
Authority.
C
I
This
is
our
you
know:
code
tiebreaker
or
whatever.
We
want
to
end
up
calling
these
people,
it
should
be
noted
somewhere
and
maybe
even
some
like
how
to
reach
them.
Like
hang
on
Gary
versus
email
versus
whatever,
and
have
some
kind
of
method
for
we're
having
a
conflict,
we
need
your
opinion
and
get
them
to
weigh
in
and
that
person
needs
to
be
willing
to
do
that.
I
D
D
The
last
thing
that
I
would
like
us
to
do
guys
become
have
certain
aspects
of
their
I
know
that
this
is
impossible
to
avoid
to
a
hundred
percent
thing.
But
I
would
like
to
us
to
avoid
as
much
as
possible
having
opinionated
things
introduced
in
the
in
the
product.
It
shouldn't
be
an
opinion.
It
should
be
a
solve
like
an
educated,
researched
decision,
yeah.
I
D
If
this,
if
this
user
studies,
if
there's
things
that
make
up
certain
things,
yes,
but
if
it's
controversial
by
nature,
like
even
in
the
broader
like
internet
thing,
then
that
I
think
that
we
have
like
at
some
point
to
just
make
a
decision.
I,
don't
know
how
that
would
be.
Maybe
that's
the
point
where
the
PMC's
that's
in:
let's,
let's.
B
Get
to
that
in
just
a
minute.
Yes,
I
think
people
want
to
talk
about
solutions
and
I
do
too
and
I
think
we
can
get
there.
I,
but
the
big
issues
that
I'm
hearing
right
now.
How
do
we
set
priorities,
who's
responsible
to
break
laws
Sam's?
How
improving
that
process
so
better
communicating
whose
role
as
what
and
you
know,
maybe
having
people
that
are
able
to
write
log
jams
or
do
certain
things
that
there
are
might
be
some
gaps
in
our
process
that
need
to
be
filmed.
B
D
I
guess
the
be
like
us
to
be
a
considerate
community
as
a
whole,
so
I
generally
don't
want
us
to
be
getting
in
the
way
of
each
other.
So
if
there's
people
that
think
that
a
more
structured
process,
driven
use
of
like
workflow
of
developing
is
the
way
to
do
things,
I
would
like
to
have
the
people
like
myself.
We
who
are
coming
to
bactrim
to
contribute,
as
a
form
of
you,
know,
pastime
or
having
fun
enjoying
it
not
get
in
the
way
of
that
and
the
other
way
around
as
well
so
yeah.
D
Time,
but
at
the
same
time,
if
it
becomes
a
problem,
a
real
problem
for
people
I,
don't
want
that
to
happen
like
I,
don't
want
a
structure
with
structural
workflow
of
getting
things
done
to
get
in
the
way
of
people
that
are
having
time
to
stop
having
fun
and
I.
Don't
want
people
that
are
having
time
to
stop
the
way.
If
you
know
people
that
are
having
a
more
structured
sort
of
like
workflow
of
doing
things,
they
just
you
know,
feel
frustrated
about
things
getting
done.
I
don't
have
the.
B
Solution
for
it
right
the
it
occurred
to
me,
the
other
problem
that
we
started
out
with
was
not
wasting
your
effort
but
being
efficient
and
how
we
use
people's
time
and
resources
so
sort
of
before
we
move
on
to
solutions
is
one
last
chance.
Is
there
other
sort
of
problems
that
we're
trying
to
solve
with
these
solutions
that
stand
out
for
anybody.
I
Don't
say,
I
would
really
like
to
find
a
way
to
reduce
burnout
and
I.
Think,
especially,
you
know,
being
being
good
with
people's
time
is
important,
but
also
helping
people
get
through
the
issue.
Queue,
conflicts
and
just
the
process
and
anything
that
we
find
is
adding
like
more
barriers
between
I
want
to
help
and
I
feel
good
about
helping.
And
if
it's
you
know,
I've
tried
four
times
to
reorders
polar
question.
I
can't
figure
out
the
system
or
there's
this
person
who
I
don't
agree
with
on
opinion
or
I.
A
I'm
not
sure
if
this
is
a
legitimate
concern,
but
these
meetings
that
we
have
the
people
that
show
up
to
them
have
an
outsized
influence
and
I'm,
not
sure.
If
that's
a
good
thing
or
a
bad
thing,
you
know
it
writes.
It
me
like
an
equal
opportunity
currently
for
pretty
much
anyone
in
the
community
to
to
have
a
face
time
with
people
that
can
actually
solve
most
of
the
problems.
Right
I
mean
we've
got
usually
several
PMC
members
on
these
calls.
D
That's
what
I
try
to
do
and
we
have
all
sort
of
like
been
nominated
as
constituents
of
a
specific
part
of
the
community,
as
in
multilingual
group
or
non
coders
or
UX,
or
developers
and
I
think
that
for
the
most
part,
we're
doing
a
really
good
job
of
not
being
but
I've
no
more
time.
So
that
expects
the
opinion
of
other
people's
people
that
are
signed.
D
Builders
where
it
contradicts
with
my
opinion,
my
personal
opinion
and
I
think
that
if,
if
we
make
a
better
job
or
keep
doing
the
job,
that
would
that
we're
doing
as
BMC
members
to
be
impartial
and
keep
our
personal
opinions
separate.
Then
this
will
work.
It's
the
moment
where
BMC
members
may
be
abusing
their
position
to
solve
a
steer
to
one
direction
or
another
where
things
become
dangerous,
I
mean
this
is
not
being
the
case.
That's
my
understanding!
D
That's
my
take,
but
it's
it's
the
it's
the
job
of
the
rest
of
the
members
of
the
PMC.
If
that
happens,
this
of
like
pointed
out-
and
it's
like
work
it
out
between
ourselves
and
I-
think
I
think
we're
sort
of
like
very
people's
people.
All
of
us-
and
it's
like
we're
doing
a
good
job
I,
don't
think
that
that
anyone
has
been
abusing
their
power
right.
B
Now,
what
we're
trying
to
do
is
define
the
problems.
People
want
us
to
talk
about
so
I
I
want
to
just
mention
another
one
quick
which
is
I,
think
in
terms
of
processes
doing
a
better
job
of
maybe
recruiting
or
improvement
or
increasing
our
contributor
base.
A
number
of
the
problems
that
we're
talking
about
are
directly
related
to
the
number
of
people
that
we
have
working
on
the
project,
and
this
is
related
to
Jen's
about
retaining
members,
but
also
getting
new
ones.
B
Should
we
move
on
to
some
of
the
ideas
that
we
have
to
address
these
problems
and
maybe
well
let
me
do
it
a
check.
We
started
this
meeting
at
about
a
quarter
after
I.
Think
so
should
we
shoot
for
4:15
is
the
end
time?
Does
that
agreed
kind
of
look
at
it?
Anybody
object
to
that
anything
Erick's,
let's
shoot,
for
that
is
the
end
time
of
the
meeting,
and
it
may
be
for
efficiency
sake.
B
Well,
now,
let
me
just
let
people
present
your
own
ideas
if
I
was
going
to
suggest
that
maybe
I
threw
out
some
things
that
I'd
seen
in
the
forum,
but
rather
than
me
doing
that
the
goal
right
now
is
for
people
to
say
here
are
some
things
that
they'd
like
to
see
us.
Try
that
will
solve
one
of
these
problems
that
we've
talked
about
and
not
to
get
into
a
debate
about
whether
or
not
that's
the
right
solution
or
the
best
solution,
but
just
to
get
a
number
of
solutions
out
on
the
table.
D
Before
we
go
to
that,
I
know
that
some
people
don't
like
to
work
with
time
constraints,
and
it's
good
that
you
brought
up
that
when
is
the
limit,
but
we
don't
have
to
limit
the
decision
to
where
the
what
was
expected
out
of
this
meeting
to
this
meeting,
we
can
set
the
foundation
now
and
then
do
it
for
the
next
meeting.
So
just
let's
not
worry,
let's
do
a
good
job
have
to
wait.
Yeah
I
don't
mean
that's
the
end
of
the
discussion.
Only
the
end
of
today's
just
yes
I
agree
fully
agree.
B
D
Yeah
so
I'm,
not
so
Drupal
has
initiatives
as
well.
They
call
them
strategic
initiatives,
and
this
is
usually
four
or
five
or
six
of
them.
It's
just
very,
very
broad
goals
for
the
entire
year
Oh
for
the
next
version.
The
next
release,
I'm,
not
sure
if
we
want
to
have
it
work
for
backed
up
the
exact
same
way
or
we
want
to
solve
like
adapt
it,
because
we
are
smaller
community
and
have
more
frequent
releases
or
what-have-you.
D
But
the
way
that
I
see
initiatives
being
is
that
if
we
had
the
advocating
thing
being
towards
specific
features,
I
would
like
to
see
the
initiatives
be
specific
matters.
As
in
we
have
a
meta
initiative
about
better
multilingual.
We
have
an
initiative
of
being
improving.
Ux
were
getting
cross,
portent,
fixes
from
DX,
sorry
v7.
B
I
I
mean
I'm
just
curious
about
like
how
we
can
better
drive
backdropped
towards
its
goals
and
I
feel
like
what
we've
been
doing
for
the
last
few
releases
has
been
like.
Oh
here's,
a
thing
we
need
to
fix,
but
it's
been
very
focused
on
like
an
issue
or
something
that
I
think
that
you
know
was
missing
from
Drupal
7,
which
makes
sense
but
long
term.
It
would
go
to
feel
like
water.
I
What
is
what
are
our
priorities,
and
if
our
priority
is
something
big
like
making
backdrop
translatable,
then
it
would
be
good
to
have
a
topic
that
spans
multiple
releases
rather
than
being
one
issue.
We
work
on
until
their
release
is
done
and
then
it's
over
and
then
another
one,
then
actually
students
over.
That's
something
it's
like.
I
What
can
we
do
this
release
to
make
translation
better,
and
what
can
we
do
next
release
to
make
translation
better
so
something
that's
not
just
for
one
feature
or
release,
but
something
that
will
continue
to
move
us
closer
towards
that
goal
with
every
release,
and
so
that's
what
I'm
most
interested
in
figuring
out
is
how
we
can
continue
to
drive
the
product
towards
our
desired
goals,
rather
than
just
working
on
desired
features
for
every
release.
Yeah.
D
D
Ongoing
so
I
think
this,
that's
not
a
problem.
It's
maybe
just
specifying,
because
we're
trying
to
solve
like
understand
initiatives
would
work
and
what
they
would
be,
what
form
they
would
have.
But,
yes,
you're
right
it
shouldn't
be
limited
to
one
release.
We
would
say
that
it's
a
strategic
goal
for
for
Mack
truck
to
be
an
easy
product
to
use,
then
that's
that
should
be
ongoing.
D
It
may
not
be
limited
to
one
year
and
what
that
means
in
my
head
is
that
if
we
have
certain
candidate
features
to
be
advocated
for
the
next
release,
if
the
general
goal
is
to
improve
the
user
experience-
and
we
sort
of
like
need
to
choose
between
two
of
the
possible
candidate
features,
then
we
we
pick
the
one
that
is
improving
the
UX
and
I.
Think
that
in
my
head,
I
feel
that
this
would
work
I
also.
I
Think,
though,
that
it
might
be
good
like
if
we
had
a
set
of
five
initiatives
or
something
in
these
meetings
immediately
after
a
ruse
or
we're
trying
to
decide
what
we're
gonna
do
in
the
next
release,
we
can
be
like
okay.
So
what
are
we
doing
for
usability?
And
actually
what
are
we
doing
for
translation
in
the
next
release?
What
are
we
doing
whatever
and
it'll
help
rather
than
me?
Oh,
we
really
need
this
new
feature
that
everybody
thinks
is
gonna
be
great
but
maybe
doesn't
align
with
our
goals.
I
It'll
help
us
kind
of
keep
true
or
to
all
of
the
things
that
we
think
are
most
important,
getting
attention
in
every
release,
and
maybe
not
ever
really.
So
maybe
you
skip
one
and
say
well,
we
don't
have
any
issues
that
are
urgent
enough,
that
we
need
this
release,
but
then
the
next
release
we
still
review
that
list
and
say:
okay
next
release.
What
are
we
doing
for
translation
or
usability
or
whatever
it
is,
and
I
think
that'll
help
us
keep
on
track.
One
and.
H
B
C
H
I
Two
pages:
there's
the
roadmap,
which
is
only
really
stating
what's
going
on
in
the
next
release,
and
then
there's
our
philosophy
and
I.
Think
that
backdrop
sets
the
PMC's.
The
philosophy
is
set
by
the
PMC,
but
we're
not
doing
a
good
enough
job
in
every
release.
To
making
sure
that
backdrop
is
moving
closer
towards.
What's
stated
in
the
philosophy
and
I
think
if
we
had
initiatives
that
might
help
that
a
little
bit,
and
so
it
would
make
sure
that
the
people
who
are
doing
the
work
are
doing
what
the
PMC
has
said.
H
D
And
also
initiatives
don't
have
to
be
tied
to
the
product
or
specific
releases.
It
could
be
community
initiatives.
So
yes
having
chains
at
least
working
in
Drupal.
It
might
be
the
initiative
for
morning
inclusiveness
or
reaching
out
to
people
work
and
there's
it's
twofold
like
it's
also
to
allow
people
that
are
not
coders
out
or
do
not
want
to
invoke
get
involved.
B
D
B
F
Do
that
so
I
think
when
defining
what
the
initiative
is,
you
need
to
consider
what
these
people
are
allowed
to
do
and
make
sure
that
those
people
are
aware
of
that
before
they
even
start,
so
they
say
well,
if
I'm
not
allowed
to
write,
commit
court
code
and
I'm
not
being
initially
just
for
an
example.
I
think
that's
important
I
mean
I
think
these
people
need
to
understand
where
their
limits
are,
what
the
responsibilities
are,
what
they're
allowed
to
do?
What
they're
not
allowed
to
do.
B
E
Yeah,
the
basic
idea
of
it
is
to
separate
the
initial
issue:
queue
from
the
dev
issue,
queue
so
that
people
can
think
about
an
idea
and
say
whatever
they
want
anybody
can
say
whatever
they
want
about.
The
idea.
I
think
this
should
be
a
drop-down
I
think
this
should
be
pink
whatever
and
then,
once
a
consensus
is
made,
move
it
to
an
actual
Devesh.
You
queue
with
an
original
post.
That
says
you
know
this
has
been
fleshed
out.
It's
decided,
and
this
is
what
we
want.
We
want
to
change
the
behavior
on
this
page.
E
To
do
these
things.
Those
could
be
big
things
or
small
things.
The
kind
of
roadblock
there
is
who
decides
when
a
thing
is
fleshed
out
and
done
from
the
initial
proposal:
q
and
I
guess
a
lot
of
us
were
thinking
that
was
pmc,
but
maybe
that
could
be
initiative
leads.
That's
the
that's
the
outline
of
the
idea
of
long
lines
that
I
was
thinking
of.
B
E
B
What
right
the
way,
I'm
understanding
your
proposal
is
that
there
would
be
the
opportunity
for
either
if
an
issue
got
blocked
down
for
us
to
say,
let's
pause
this
and
have
somebody
make
a
decision
about
what
the
spec
should
be,
instead
of
just
having
competing
ideas
and
maybe
move
that
into
this
official
queue
or
if
somebody,
this
would
also
apply
to
more
complicated
problems
where
you
developer,
isn't
really
mostly
it
to
write
a
whole
request.
If
they
don't
know
that
there's
some
kind
of
consensus
and
it
sort
of
allows
the
opportunity.
B
Get
some
consensus
or
to
talk
about
what
people
want
before
they
write
a
full
request
and
then
settle
on
that
right,
so
we've
decided
okay,
we've
decided
we
want
X.
Now,
let's
start
on
the
full
request,
they're
supposed
to
writing
one
and
then
having
somebody
step
in
and
say:
oh
no,
that's
not
what
we
want.
Yeah.
E
It's
to
me,
it
speaks
to
the
different
kinds
of
contributors
that
we
have
in
the
community.
We've
we've
expressed
that
there
are
different
kinds
of
contributors
and
we
need
all
kinds
of
contributors
for
sure,
but
for
the
developer
minded
contributors
that
the
way
they
want
to
contribute
is
by
code.
They're
gonna
want
to
see
a
commit
to
in
my
experience.
D
That
process
in
your
head:
how
would
if
someone
comes
late
to
the
party
and
they
want
to
contribute
an
idea?
How
would
that
work?
Do
we
block
that
from
ever
reaching
the
this
Dave?
Do
we
keep
on
banging
away
with
it's
the
commit,
the
code
of
what
was
decided,
and
then
we
act
upon
the
idea
that
the
person
has
suggested,
as
in
a
fix
on
that
yeah.
E
D
Like
that,
it's
not
in
a
place
like
that
I
work
in
a
very
iterative
way,
I
expect
feedback
from
others
and
when
they
say
oh,
we
changed
our
mind
to
change
what
everybody
just
wrote:
I
just
do
it
yeah
census,
but
I
understand
that
there's
other
people
that
do
not
do
not
sort
of
like
work
that
way
they
can
like
it's
not
fun
for
them
to
work.
That
way.
It.
I
Would
be
good
if
we
could
figure
out
a
way
to
do
this
without
needing
to
queues.
Just
decrease
the
overhead
on
all
the
people
who
are
currently
working
on
stuff,
like
that,
the
possibility
of
like
for
things
getting
lost
in
one
place
are
filed
in
the
wrong
place
or
whatever
just
seems
like
it
might
be
more.
I
I
D
I
B
D
I
think
I'm
not
sure
we
have
to
yes,
because
I've
seen
people
asking
can
someone
change
the
labels?
Can
somebody
please
update
the
the
initial
cost?
How
about
if
we
agree
that
the
developers
just
look
at
the
first
post
and
that's
where
the
acceptance
criteria
is,
but
we
still
allow
discussion
that
discussion
does
not
necessarily
need
to
affect
what
the
work
that
the
developer
is
doing.
I
No
I
mean
I
feel
like
there's
so
much
good
conversation
that
happens
in
the
queue
that,
if
you
only
look
at
the
first
class
you're
gonna
miss
everything
that
happens
a
lot
now
where
it's
like,
oh
by
the
time
it
gets
to
the
bottom
of
the
issue,
it's
a
totally
different
feature
than
it
was
in
the
first
one
and
that
doesn't
get
updated
enough.
I
think
we
should
just
fix
the
issue
where
people
don't
have
access.
I
mean
that's
unrelated.
Maybe
we
should
do
that
anyway,
yeah
I,
don't
think
it's
supposed
to
be
that
way.
I
I
D
I
B
We
are
scheduled
time.
We've
got
about
five
minutes.
I'd
like
it.
I
have
like
a
completely
different
solution
to
some
of
these
problems
that
I'd
like
to
just
throw
on
the
table
or
talk
about
which
is
just
better
volunteer
management
in
this
addresses
fruit.
Men
and
the
burnout
issue,
I
think
is
I
feel
like
we
can
do
better.
It's
a
community
sort
of
tracking,
like
who
our
contributors
are
well
and
I'd
like
opinions
on
this
on.
B
If
people
think
this
is
a
good
idea,
not
necessarily
opinions
to
make
it's
our
time
to
do
a
better
job
at
tracking
who
our
volunteers
are
sort
of
staying
in
touch
with
them
and
having
somebody,
that's
like
volunteer
coordinator
would
be
great
it
could
you
know
when
somebody
gets
into
the
issue,
queue
and
seems
really
active
for
a
week,
and
then
we
don't
hear
from
them
anymore.
Sometimes
I
think
it's
not
bad
to
reach
out
to
them,
and
just
say:
hey
are
you,
okay?
Is
there
something
we
could
do
or
or
not?
Anyways?
B
That's
something
I'd
like
to
think
about.
Instead,
it's
a
goal.
I
often
think
that
my
skills
would
be
better
put
to
use
and
like
valent,
volunteer
management
than
they
aren't
writing
forward
unless
there
are
other
people
that
are
much
better
at
that
than
me,
but
I'm
not,
but
we
don't
really
have
a
system
in
place
to
do
that.
Volunteer
management,
sometimes
I'm,
not
sure
I,
think.
D
Although
it
is
manual,
try
because
I've
had
a
recent
case
in
last
looking
last
week,
where
there's
a
new
person
that
maybe
have
seen
his
name
around
he's
Greek
as
well.
That's
why
I
pointed
it
out
then
offered
to
do
a
pull
request
and
he's
never
come
back
today.
She
queue
in
like
a
few
days.
Maybe
just
walking
there
and
saying
hey:
did
you
manage
to
get
that?
So
this
is
what
you
tried
to
do
right.
I
D
Cuz,
what
we
end
up
doing
now
is
like
people
that
Peter
just
go
through
the
queue
with
old
issues
and
like
we
haven't,
responded
to
some
people
and
I
came
in
a
year
or
two
here
anymore,
and
we
just
say:
oh,
this
is
obsolete,
that
now,
okay,
so
that's
that's
sort
of
like
a
lost
opportunity
to
have
an
active
member
of
the
community.
I
mean
most
of
the
cases
is
that
we
go
back
and
say:
oh,
this
has
been
fixed
and
the
person
might
say
yeah
great,
but
it's
been
three
years
later
so.
D
These
problems,
I'm,
not
sure
if
you
guys,
have
tried
anything
equivalent
to
what
will
be
the
google
Summer
of
Code
like
grabbing
people
that
are
graduating
from
yes.
So
this
this.
This
does
sound
like
something
that
should
have
been
with
discussed
in
the
previous
meeting,
but
because
it's
closely
related
to
coding.
D
B
D
That
creating
more
monsters
like
me
is
a
good
thing.
So
I
was
one
of
those
annoying
people
that
was
hanging
around
in
the
Drupal
queue
and
then
the
virtual
queue
and
I
was
like
brainstorming
and
throwing
ideas
here
and
there,
and
it
was
Jeff
that
jumping
and
said
you
know
that
you
can
file
a
cool
request
right,
so
so
I'm
not
sure
if
we
can
grab
more
people
like
that.
D
Because
that's
what
started
me
and
it's
been
thrilling
for
me,
like
it's-
been
very
rewarding
to
be
able
to
just
fix
the
tiny
things
here
and
there
so
that
others
do
not
have
to
worry
about
those
and
it's
the
tiny
fixes
here
and
there
that
make
eventually
a
better
product.
So
if
we
can
get
more
people
that
are,
you
know
willing
to
do
the
tiny
bits
here
and
there
documentation
help
takes
like
polishing
here
and
there.
It
would
eventually
sort
of
like
make
a
good
product.
B
Anything
else
anything
else,
people
want
to
get
on
the
list
of
things
we
should
be
thinking
about
for
solving
these
problems.
I
think
we
should
go
back
through
the
forum
and
see
if
there
were
any
other
good
ideas
there
that
we
want
to
talk
about,
but
why
don't?
We
then
take
a
couple
extra
minutes
if
everybody's
okay
just
decide
what's
next,
like
this
idea
of
initiative,
seems
to
be
getting
some
momentum
here.
B
D
As
I
said
at
the
beginning,
I
don't
think
that
we,
this
is
the
meeting
that
we
come
up
with
every
solution
and
we
do
everything.
This
is
the
groundwork.
So
if
we
have
the
bullet
points
for
the
next
meeting,
one
bullet
point
could
be
clearly
sort
of
like
defined
what
the
initiative
is
and
processes.
That's
it,
and
we
can.
We
can
discuss
that
in
the
next
name
like
we
had
very
good
ideas
and
there's
a
recording
of
them
as
we
speak.
D
So
if
we
can
make
bullet
points
of
that
and
and
try
in
the
next
the
meeting
that
we
have
to
sort
of
like
flesh
out
what
an
initiative
is
formulated
like
a
good
studies.
Like
start
a
unpublished
range
in
video
talk,
because
that's
that's
where
it
will
end
up
saying
initiatives
and
then
maybe
creating
a
content,
type
called
initiative
so
that
we
can
serve
like
list
them.
D
D
Pmc,
well,
we
need
to
happen
to
one
of
the
meetings
it
doesn't.
It
doesn't
feel
like
a
design
or
outreach
topic.
No,
but
it
could
be
a
PMC
me.
It
might
not
be
so.
I
wouldn't
like
to
limit,
though
the
the
brainstorming
on
what
initiatives
should
be
look
like
to
do
only
PMC
members.
So
if
it's
better,
if
we,
if
we
can
make
a
separate
meeting
for
that,
yes
I'm
all
for
it,
it's.
B
D
B
So
there's
a
couple
of
the
ideas
like
this
idea
of
doing
better
volunteer
outreach,
which
I
don't
know
that
that
needs
to
be
some
people
can
talk
about
that.
We
can
do
some
things.
We
don't
have
to
put
that
on
the
agenda,
for
a
future
doesn't
mean
it,
but
ideas
like
the
initiatives
I
think
this
idea,
that
of
Justice
about
how
the
triaging
the
issue
queue
and
be
more
proactive.
These
are
things
that
are
gonna,
need
more
discussion
and
I'm
kind
of.
What
is
your
feeling
about
like?
How
much
is
this?
B
A
Think
using
the
dev
meeting
is
a
valid
way
to
proceed.
The
the
dev
meetings
tend
to
be
a
little
bit
wrote.
You
know
like
we
do
the
same
thing
over
and
over
again
and
if
we
want
to
take
more
than
one
more
than
just
this
meeting
and
continue
kind
of
doing
some
of
these
investigations
than
great
you
know.
Okay,.
D
And
I
think
this
would
be.
This
should
be
established
like
every
beginning
of
each
year
like
we
should
dedicate
a
couple
of
meetings
as
long
as
it
as
many
as
it
takes
to
sort
of
like
better
organized
the
direction
and
the
initiatives
that
so
like
yeah
will
make
us
so
like
work,
better
yeah,
I
agree.
I
But
I
would
I
want
to
add
one
thing
that
we
haven't
talked
about
since
we
started
doing
all
these
planning
meetings
and
that's
that
we
need
to
push
the
release
of
1.5
and
we've
been
skipping
doing
our
actual,
like
usually
work
to
talk
about
big-picture
stuff,
but
we're
now
really
late
on
getting
that
out.
So
doesn't
look
like
we
have
any
critical
bugs
in
it.
Can
we
just
push
one
point?
Five
point:
oh
you.
I
A
I
So
that's
the
thing
I
think
like
before
we
can
make
a
bunch
of
noise
about
all
the
great
features
we
just
released,
which
I'd
love
to
do.
We
need
to
release
the
features
to
everybody,
get
them
so
like
I,
just
got
a
little
bunch
of
Facebook
posts
and
then
I
was
like.
Oh
wait.
We
can't
actually
post
about
these,
because
if
these
people
try
and
like
to
try
it
on
Pantheon,
they
won't
see
the
new
features.
I
A
I
B
D
D
B
D
I
agree
with
with
only
one
thing
that
it's
not
that
there's
not
consensus
for
Jeff's
thing:
it's
just.
We
need
to
sort
of
like
find
how
that
will
work.
There
is
consensus,
so
we
should
make
it
less
frustrating
for
people
that
are
more
organized
and
every
data
to
just
make
it
fun
for
them
to
contribute
and
less
frustrating
I.
Think.