►
From YouTube: Backdrop Weekly - Oct 10, 2019
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
A
So
let's
see
bad
camp
was
last
week
we
didn't
have
a
weekly
meeting
last
because
we
were
all
busy
doing
bad
camp
stuff
on
Wednesday
the
day
before
our
mini
camp,
we
had
a
half
day
training,
but
I
thought
it
went
pretty.
Well,
we
had
a
bunch
of
people
in
the
room
who
were
impressed
with
Vectra,
which
is
great.
They
all
seemed
to
be
more
out
of
it
than
they
were
expecting.
So
that's
good
and
I.
Like
a
half
day,
timing
worked
really
well
for
our
existing
material.
I
thought
was
also
really
good.
B
A
It
end
I
did
a
pretty
good
job
of
adjusting
alternate
schedule
for
the
day
that
included
things
that
we
thought
would
be
a
better
fit
for
the
current
audience,
as
opposed
to
the
anticipated
audience
and
I
felt
that
it
went
really
well.
In
spite
of
that
last-minute
change
of
schedule,
so
I'm
not
sure
we
did
anything
live
on
YouTube,
but
we
did
do
a
couple
of
various
sessions.
We
did
a
couple
of
brainstorming
sessions.
A
We
did
a
tell
us
what
you
want
from
backdrop
hour,
which
I
thought
was
pretty
exciting:
yeah
I,
don't
know
Nate
Jack,
you
guys
were
there.
If
you
want
to
jump
in
there,
what
you
thought
of
mini
camp
you're,
all
muted,
they're,
all
thinking
we.
C
Took
notes
and
some
people
found
that
to
be
interesting
to
read
through
the
agenda
and
then
the
summary
of
everything
that
we
did
Jack
presented
on
Suri
see
him.
They
were
City
Sierra
and
backdrop,
integration
which
I've
found
to
be
pretty
interesting
to
see
in
action
like
on
either
production
site
or
soon
to
be
a
production
site.
B
Yeah
that
was
exciting
to
share
it's
a
soon
to
be
a
production
site
for
a
large
nonprofit
organization
and
many
of
their
affiliates
and
not
tons
of
backdrop
integration
yet,
but
looking
forward
to
more
of
it,
especially
via
views
and
possibly
a
port
of
the
full
calendar
module.
So
we
shall
see
how
that
goes,
and
yeah
I
really
enjoyed
the
conversations
we
had
at
the
mini
camp.
I.
Think
my
main
thing
is
thinking
about
how
to
get
more
attendance
next
year.
B
You
know
like
how
we
can
try
to
do
outreach
earlier
on
and
maybe
like
yeah
just
figure
out
how
to
make
an
agenda
that
gets
folks
there,
there's
always
so
much
competing
every
day
at
that
camps.
So
there's
like
trainings,
there's
other
summits,
things
like
that,
but
you
know,
even
with
that,
you
know
figuring
out
how
to
how
to
get
more
folks
in
the
room
next
time
around.
A
And
so
we
did
it
like
a
last-minute
reshuffle
of
all
of
the
areas
so
that
we
moved
the
board
table
in
front
of
the
television
or
the
couch
used
to
be,
and
we
moved
the
couch
over
to
where
the
board
room
table
used
to
be
so
that
we
could
have
a
projection
area
where
we
were
using.
The
TV
is
our
projector
and
discussion
area.
So
not
too
much.
D
C
C
A
Great,
let's
move
on
and
talk
about
other
things
in
the
two
weeks
since
we've
last
had
a
meeting
different,
a
bunch
of
contributed
projects
released.
There's
a
project
called
P,
which
is
a
back
draft
command-line
tool
equivalent
to
Josh,
had
a
first
stable
release.
This
week,
a
new
module
called
utility
CSS
that
I
think
was
written
by
Wes
last
week
during
our
code
sprint,
a
module
called
range
in
a
module
called
configurable
block
style
that
both
came
out
last
week.
A
A
Let's
see,
we
talked
pretty
extensively
about
back
drug
CMS
org
and
it's
updates
in
the
design
meeting.
But
since
you're
here,
I
just
wanted
to
see
if
you
wanted
to
say
anything
about
the
translation
site.
Since
it's
been
a
while
I
personally
like
every
time,
I
look
at
it.
There's
new
translations
there's
a
lot
of
stuff
going
on
there,
which
makes
me
really
happy
so
no
need
for
an
update.
A
C
Let's
see
we
discussed
it
two
weeks
ago,
one
of
the
bugs
in
the
new
flexible
layout
system
issued
forty
sixty
six
is
that
the
header
and
footer
regions
do
not
have
this
special
classes
on
them.
L
dash
header
and
L
dash
footer
that
are
necessary
for
things
like
the
hero
block
and
menu
navigation
to
display
properly.
So
we
fixed
that
one
in
that
same
issue.
Thank
you,
Tim,
for
putting
together
the
pull
request
on
that.
C
That
just
makes
it
so
that,
if
you
use
the
header
and
footer
wrapper
elements,
then
we
add
those
special
L,
another
an
L
for
your
classes
to
that
region,
but
not
no
other
regions
receive
that
same
special
treatment.
There
are
no
other
types
of
tags
anyway.
It
makes
it
so
that
if
you
create
a
new
flexible
layout,
it's
going
to
work
by
defaults,
putting
the
header
and
footer
blocks
into
the
header
and
the
footer.
So
it's
big
improvement
and
definitely
makes
things,
look
a
lot
less
broken
if
you're
using
flexible
layouts.
C
So
that's
great
I've
gotten
that
one
fixed
up
as
soon
as
we
hit
one
fourteen
one
pushed
out.
At
least
this
would
long-standing
issue
issue.
36
fourteen
views
is
none
of
operator
says
it's
been
broken
since
backdrop,
one
dot
12.5,
when
we
back
when
when
when
we
cross
ported
some
views
fixes,
we
finally
got
this
one
put
away.
C
But
there
are
two
sections
of
those
new
tests
that
are
commented
out
with
follow-up
issue
to
uncomment
them
once
we
have
more
of
the
cross
ports
from
fuse
pulled
over,
because
the
theory
is
that
that
some
parts
of
the
new
tests
are
dependent
upon
cross
voice
that
aren't
yet
and
backdrop.
So
so
I
think
that's
a
fine
workaround
to
make
that
happen,
and
that
will
be
finally
out
in
114
one.
C
Let's
see
the
FIA's
cross
ports
issue
it's
worth,
noting
is
also
something
that
we're
working
through.
There's
a
bunch
of
poll
requests
that
are
ready
to
be
committed
that
are
listed
in
the
issues
under
the
big
meta
at
36
85.
So
we've
got
a
lot
of
BOE
trusts
to
get
merged
in
there.
Although
I
don't
think
that
will
prioritize
that
for
the
next
couple
of
days
for
114
1,
let's
see
also
related
flexible
templates,
have
a
number
of
follow-up
issues.
There's
a
big
metaphor
that
at
issue
40
46,
there's
lots
of
issues
in
there.
C
Some
of
them
have
pull
requests,
one
that
I
reviewed
during
the
code-
sprint
I'm
just
going
to
bring
it
up
here,
because
they
provide
feedback
but
hasn't
been
any
update
on,
is
that
flexible
templates
got
put
under
the
existing
settings
page
for
for
layout,
which
previously
just
lets
you
turn
on
and
off
templates.
But
now
it
allows
you
to
create
new,
flexible
templates
and
so
there's
a
suggestion
that
we
renamed
the
page,
including
the
path
and
the
tab
name
from
settings
to
templates.
C
C
The
current
approach
is
kind
of
aggressive
and
then
it
renames
the
existing
pads,
which
honestly
I'm
kind
of
okay
with
because
all
of
those
paths
are
should
I
knew
but
slash
settings.
The
layout
settings
page
has
been
there
since
backdrop
1.0
and
so
there's
a
lot
of
things
that
could
potentially
be
linking
to
it.
You
know
in
documentation
or
other
modules,
and
things
like
that,
so
my
only
suggestion
is
that
we
question.
A
About
that,
so
we
have
another
issue
to
actually
move
other
settings
to
the
layouts
settings
page,
which
is
why
I
thought
that
we
shouldn't
be
combining
settings
in
like
layout
templates
on
the
same
page.
What,
if,
for
this
issue,
we
left
the
layout
settings
URL
and
just
put
the
new
settings
on
it.
So
we
actually
have
a
settings
page
and
the
layout
templates
page,
because
that
way
the
settings,
because
I
think
if
we
have
any
links
in
anywhere
that
are
pointing
to
the
settings
page
they'd,
expect
settings
and
not
templates.
A
So
you
actually
put
the
settings
like
that.
The
one
thing
that
I
know
we
talked
about
moving.
There
was
the
permissions.
So
if
we
moved
those
over
there,
so
we
actually
had
a
settings
page
and
then
existing
links
link
to
a
settings
page
that
might
be
a
better
solution.
I,
don't
know
if
it
needs
yeah.
D
I
think
I
think
I
think
that
114
1
is
a
great
chance
to
do
it
like
as
soon
as
we
do
it
less
people
get
confused
about
it
so
or
at
the
very
least,
rename
the
Settings
tab
now,
which
is
the
user
facing
thing
too
available
templates,
but
yeah.
It
would
be
nice
if
we
thing
come
up
with
something
really
quick
over
the
next
couple
of
days
before
we
cut
the
release
and
then
we
can
fix
properly
the
links
in
whatever,
but.
C
A
C
Yeah,
so
I
thought
you
were
saying
that
we
would
combine
the
permission
of
page
and
the
templates
onto
one
page:
okay,
yeah
yeah,
yeah
yeah.
That's
that's
fine,
but
we
don't
have
that
page
apparently,
and
that
would
probably
be
in
the
next
minor
release
that
we
would
do
something
like
that.
Add
the
permissions
to
that
settings,
page
yeah,
so.
A
A
A
E
C
D
C
A
I
think
like
it
could
be
permission-based
if
it
had
to
be,
but
I
know
that
on
90%
of
the
sites
that
I've
delivered
I've
not
wanted
people
to
be
able
to
break
they're
like
theme
by
using
lands
that
weren't,
supported
and
I
think
flexible.
Yes,
it's
a
really
good
way.
They
give
people
that
told
to
shoot
themselves
in
the
foot,
so
I
think
it's
a
great
site
builder
tool,
but
I'm
not
sure
it's
an
editorial
tool
and
so
having
a
good
way
to
like
what
you
build.
D
D
E
D
A
E
D
A
D
I'm
not
mentioning
the
permissions
thing
that
we
mentioned
before,
so
you
know
we
have
a
listing
and
it
says
these
are
standard.
These
are
flexible,
those
written
it.
It
knows
it
not
and
I
was
thinking
that
in
general-
and
maybe
this
is
a
2.0
thing,
but
I
would
be
if
we
had
only
flexible
layouts.
So
what
is
offered.
A
Really
hard
because
all
of
the
template
file
is
gonna,
be
full
of
like
variables
and
loops,
and
you
can't
just
put
in
like
a
row
so
I
think
it's
just
I
learned
it's
a
learning
curve
thing
we're
like
having
a
simple
example
for
people
to
work
from
this
really
invaluable.
Now
we
did
this
once
before,
though,
where
we
had
like
legacy
layouts,
and
then
we
had
new
one,
but
I
would
prefer
yeah
I,
don't
know.
Let's
talk
about
it
screen
as
you
announce
the
sides
of
that
fence.
Yeah.
B
D
So
I
was
working
on
the
issue
to
generate
automatically
icons
for
the
flexible
layouts
and
what
came
to
mind
is
that
yeah,
maybe
maybe
I?
Can
we
had
a
column
there
that
sends
your
data?
Does?
This
is
flexible?
This
is
standard
and
maybe
I
thought
that
I
could
overlay
the
ones
that
are
flexible
with
the
pencil
icon.
As
in
these
R&D
table,
the
other
ones
are
read-only,
but
then
I
call
like
if
we
are
to
implement
this
cloning
thing,
then
what's
the
point
of
having
standard
non
editable
layouts,
but
let's
make
them
all
editable
yeah.
B
I
would
say
so
that
you
don't
accidentally
mess
it
up.
Cuz
like
I,
could
even
see
myself
like
going
in
and
wanting
to
revert
that
back
to
its
original
state,
and
it
seems
maybe
easier
to
implement
something
where
we
clone
a
layout
into
a
new
editable
one,
then
to
figure
out
how
to
program
so
that
we
can
revert
back
to
the
old
ones.
B
D
D
Most
of
the
things
that
come
as
default,
we
do
have
a
revert
thing
if
I'm
not
mistaken,
like
we
have
a
way
to
detect
if
we
provide
those
as
JSON
files,
the
detective
thing
has
changed
from
the
original
one,
like
a
configuration,
that's
provided
by
core
and
it
can
revert
back
to
from
what
I
recall
yeah
but
yeah.
That's
a
big
discussion
as
well.
I
just
wanted
to
bring
it
up.
Yeah.
C
Okay,
yeah
that's
anyway.
The
one
that
you
brought
up
is
a
good
one,
great
great
issue,
4072
that
but
it's
a
fairly
straightforward
one,
that
the
flexible
template
machine
IDs
are
just
super
unfriendly
on
the
reports
page
and
we
could
tidy
that
up.
I
post
a
comment
saying
it'd
be
nice.
If
we
could
simplify
that
a
little
bit
just
in
the
implementation,
because
the
idea
and
the
result
is
good.
But
the
implementation
makes
me
a
little
sad.
D
C
C
Well,
let's
wrap
up
then
for
141
and
move
on
to
the
new
features
portion,
which
will
be
in
backdrop.
115
115,
coincidentally,
will
come
out
on
115
January
15th
2020,
with
code
freeze
on
January
1st,
let's
see
so
the
first
item
that
we've
got
here.
We
have
some
new
advocates.
Recent
advocates
I
think
they
actually
were
in
the
last
name
too,
but
Larrin
started
advocating
for
issue
3297,
which
is
to
add
an
image
library.
C
Modal
to
image
fields
is
a
great
issue,
big
huge
improvement
that
we
already
have
the
ability
to
use
the
image
library
when
inserting
an
image
into
a
rich
text
editor.
But
we
do
not
have
that
same
image:
library
modal,
when
you're
using
an
image
field,
so
it
would
make
it
so
you
can
reuse
images
on
image
fields
and
not
just
in
the
rich
text.
Editor,
there's
no
more
request.
Yet
on
this
we
may
need
some
advising
on
the
approach,
because
we
we
need
to
consolidate
the
implementation.
C
B
D
This
is
the
my
last
comment
there
an
image
library,
but
we
can
sort
of
like
apply
the
same
thing
in
all
fields,
as
in
allow
allow
even
two
simple
files
to
select
from
already
uploaded
once
I'm,
not
sure
if
we
have
a
ticket
for
it,
because
now
we
have
that
ability
only
for
images,
but
it
should
be
there
for
all
files,
all
kind
of
files.
So
maybe
it's
worth
making
a
median
like
not
just
the
an
image
library
yeah
or
at
least
at
least
developing
towards
that
goal.
C
B
Like
it,
I
mean
like
when
I
think
about
it
in
with
whatever
combination
of
Drupal
like
I,
think
I
am
seee,
WYSIWYG
I
like
being
able
to
do
that
in
the
rich
text
area.
It
does
get
trickier
when
you
like.
You
have
an
image
field.
You
have
to
make
sure
that
the
image
field
only
allows
you
to
select
images
and
not
other
things,
but
yet
working
towards
that
eventually
seems
cool.
And,
having
is
that
already
possible
in
the
rich
text
area
I
haven't
tried
like
selecting
yeah,
so
you
not.
D
Not
with
us
in
background,
but
in
VH
at
least
with
the
media
initiative.
What
you
can
do
is
like
you
can
browse
for
files
int
and
not
just
images
and
when
you
add
PDS,
for
example,
or
documents,
it's
like
you
can
select
how
they
cannot
be
displayed
as
if,
like
just
a
link
to
the
file
to
be
downloaded
or
the
PF
to
just
open
it,
because
you
have
browser
support
for
it,
etc.
D
C
Am
strongly
not
strong
right,
I,
don't
know.
I
am
the
complexity
of
the
media
approach
really
is
a
turn-off
for
me.
The
way
that
it's
it
rendering
display
modes
inside
of
other
display
modes
like
it's
rendering
it's
literally
rendering
an
entity
inside
of
the
text
area,
which
is
super
flexible,
and
it's
the
way
the
media
module
worked
in
Drupal
7
as
well,
but
it's
also
like
just
so.
It
gets
really
complicated
and
that
dependencies
start
getting
really
gnarly
yeah.
C
All
right,
well,
anyway,
it's
you
3297
is
it's
a
really
great
thing.
I
didn't
see.
Graham
had
already
started
on
that.
So
that's
wonderful,
yeah,
let's
see
Auto
menu
settings
module
that
contributor
Drupal,
7
BW
panda
is
advocating
for
this
issue,
which
is
issue
1610,
I'm,
not
sure
I'm.
The
best
person
to
talk
about
this
one
is:
if
anybody
else
who
wants
to
some.
C
D
So
BW
kinda
just
went
to
bed.
We
had
a
discussion
before
that
meeting,
so
he
filed
their
full
request.
He
just
needs
some
help
with
the
tests
that
are
failing
and
they're.
Failing
for
a
pretty
simple
reason
like
this.
Previously
we
didn't
saw
the
test
that
is
failing
specifically,
is
that
the
checkbox
is
ticked
for
allowing
to
have
a
protocol
at
a
menu
item.
D
But
then
we
have
this
functionality
when,
where
you
change
the
that
the
not
idle
it
automatically
populates
them,
not
that
sorry
that
menu
link
title
as
well,
whereas
the
old
test,
what
we
was
doing,
he
was
trying
to
tick
the
check
box,
but
leave
the
title
blank.
So
you
would
expect
the
link
to
not
be
created,
but
now
it
is
being
created
because
we
are
Auto
populating.
D
It
anyway
point
is
that
I
offered
to
help
with
the
tests
over
the
weekend,
so
I
and
I
think
I
should
be
able
like
to
copy
some
of
the
tests.
The
simple
piston
check
for
the
new
functionality
being
added,
which
is
then
at
some
point.
You
tested
it,
and
you
mentioned
in
the
in
the
PR
that
I
tried
to
to
edit
try
to
create
a
pates
knowledge
and
the
check
box
was
not
ticked
what
it
was
meant.
D
D
So,
just
to
make
a
note
there,
if
we
the
the
test,
the
current
test
that
is
failing,
tries
to
do
whatever
it
is
to
do
with
the
horse.
Sorry,
with
the
page
content
type.
If
we
switch
that
to
the
post,
it
will
just
succeed
because
we
didn't
enable
that
for
posts,
so
I
don't
want
to
take
change
the
current
functionality.
So
my
intention
is
to
do
add,
on
top
of
that,
to
account
for
the
new
teacher
that
we
have
I.
A
C
A
Case
for
this
is
like
you
have
a
content
type
and
every
time
you
create
an
item
of
this
type,
you
want
it
to
have
a
menu
entry,
and
so
what
you
want
to
do
is
that
the
default
values
for
the
menu
on
this
thing
so
like
if
I,
have
a
new
content,
type
called
meetings
and
I
have
a
section
of
my
top-level
menu
called
meetings.
I
want
every
new
meeting
I
add
to
show
up
as
a
link
underneath
that
section,
so
I
want
to
be
able
to
go
into
content.
A
I
can
say,
create
a
menu
item,
put
it
in
the
main
menu
put
it
under
readings,
save
and
then
every
time
I
create
a
meeting.
It'll
automatically
have
that
setting
and
either
I
can
restrict
my
editors
from
having
access
to
menus
or
it'll
just
be
a
good
catch-all
to
make
sure
that
it
won't
get
overlooked.
A
So
I
had
originally
recommended
that
we
just
allow
the
ability
to
set
a
default
menu
and
then
I'd
be
able
to
panda
came
along.
It
said,
oh
there's
a
module
for
that.
It's
this
one
and
it
looks
like
ho.
Never
even
know
there
was
a
module
for
that,
but
yeah
it's
the
kind
of
thing
I
have
they
need.
What's
it
called
auto,
there's
something
else:
menu
position,
module
or
something
that
helps
with
like
URLs,
with
having
an
item
in
the
menu
for
like
all
content
types
without
having
a
menu
entry
is.
A
C
So,
and,
and
is
the
out
of
box
functionality
saying
that,
because
the
original
issue
description
is
saying
that
you
create
a
piece
of
content,
you
save
it,
but
then
it
doesn't
end
up
in
the
menu.
So
you
think
that
it
might
not
exist
like
as
a
new
user.
The
piece
of
content
like
disappears
into
the
content
bucket
it
does
this
affect
the
out
of
box
functionality
to
make
it
so
the
pages
when
you
create
them.
C
A
D
So
this
is
also
for
people
that
are
coming
from
other
CMS's
I.
Think
word.
Chris
automatically!
Does
that
so
that
people
like
it
adds
a
menu
item
so
that
people
don't
have
to
go
looking
for
the
for
the
page,
so
this
is
mainly
for
not
not
for
people
that
are
already
savvy
in
back
troppa
troppa,
it's
for
people
that
are
new
to
pack.
For
you,
oh.
C
Okay,
great
just
saying
yeah,
it's
just
me
one,
that's
odd!
We
even
have
we
even
have
a
default
parent
for
new
links.
We
already
have
that
option.
Apparently
it
just
doesn't
create
a
pretty
fault.
Wow,
that's
really
ridiculous!
So
it's
literally
just
checking
the
box.
It
says
you
make
a
menu
link.
Uh-Huh,
that's
really
surprising.
C
Sometimes
things
are
easier
than
you
expect.
Yes,
okay,
great
yeah,
very
cool.
C
F
C
A
D
And
in
the
same
for
me
for
the
next
one,
so
so
we
got
the
that's
issue
1575
and
that's
providing
a
way
to
be
enabled
disabled
text
format.
This
is
fixing
aux
sort
of
like
WTF.
We
we've
got
it
really
close
with
the
114
release.
It's
just
that
there
were
certain
things
that
were
needed
to
be
looked
into
and
we
were
breaking
certain
things:
we're
trying
to
work
around
and
fix
the
test,
but
then
doc
Wilmot
suggested
much
better
or
a
less
intrusive
way
of
implementing
it,
and
I
would
like
to
explode
with
that.
D
C
Done
yeah
yeah,
I
totally
suck
in
that
mentality
too,
and
maybe
that'll
we're
talking
offline
before
the
meeting
that
dr.
Ouma
was
requesting,
that
we
focus
on
on
bug,
fixes
and
actually
I.
Think
that's
where
a
lot
of
our
efforts
are
concentrated
right
now
is
exactly
on
that,
because
the
next
feature
release
is
so
far
away
and
the
bug
fixes
can
go
in
right
now
and
so
I
think
that's
I
mean
I
think
in
many
ways
it's
kind
of
a
positive
mentality
too.
C
You
know
we
always
want
to
be
working
on
something
and
because,
because
we're
human
I
guess
we
want
to
work
on
the
things
that
will
go
in
the
soonest,
so
so
everyone's
very
good
or
a
lot
of
people
that
working
out
bug-fix
releases,
their
bug
fix
issues
right
now,
because
that's
what
we'll
go
out,
the
soonest
so
I
think
it's
great
to
see
that
and-
and
we
have
more
than
enough
bugs
to
fix
so
that's
I.
It.
D
C
Could
so,
let's,
let's
just
move
right
along
yes,
yeah
yeah,
so
we
don't
have
anything
else
for
it.
115
at
this
juncture-
and
we
have
a
first
journal
discussion
item-
is
trying
to
figure
out
a
way
to
organize
and
prioritize
the
bugs
that
are
currently
you
know
on
the
docket
and
Gregory
I
think
you're
the
best
person
to
summarize
this,
because
here
you're,
the
one
that's
been
working
on
trying
to
manage
it.
Yes,.
D
D
D
Process
that
we
are
using
the
key
again
so
like
this,
this
the
milestone
can
be
used.
If
the
the
bug-fix
is
a
small
one
that
can
quickly
be
fixed,
it
doesn't
necessarily
mean
that
it's
a
serious
one
that
needs
to
you
know
have
attention
or
if
a
person
has
some
capacity
to
work
on
things
and
they
would
rather-
and
they
have
the
skill
set,
because,
speaking
from
my
own
experience,
I
usually
grab
the
smaller
issues
just
to
get
them
out
of
the
way.
Maybe
dr.
D
Ouma
wants
to
address
the
bigger
ones
and
says
there's
so
many
issues
in
the
queue
I
would
like
to
know,
which
ones
are
the
highest
priority.
So
this
is
what
gave
birth
to
the
projects
the
bugs
project.
It
initially
started
with
just
a
couple
of
columns,
but
what
I've
done
is
I
created
a
low
priority,
a
medium
priority
in
a
high
priority
column,
and
then
a
1/4
fix
that
first
month,
so
that
we
have
an
overview
of
what's
going
in
the
next
up
each
release.
D
D
A
B
D
Priority
yeah,
so
the
high
priority
one
can
have
the
exceptions
and
they
usually
gonna
be
a
few
of
them
that
we're
like
we
have
like
the
usual
people
that
are
working
on
the
bags
at
that
moment
is
like
maybe
a
handful,
like
maybe
the
Dozen
of
people,
so
they
cannot
be
possibly
working
on
all
the
issues
all
the
time.
So
I
was
thinking
that
we
can
cut
every
column
at
10
and
move
them
forward
and,
as
you
can
see,
the
high
priority
ones
are
only
three.
D
B
A
D
A
D
D
A
Like
views
is
broken
or
flexible
layouts
is
it
has
that,
like
header
tag,
missin
King
that
was
like
if
they
a
big
deal,
make
make
something
super
broken,
but
all
of
the
other
bugs
are
sort
of
equivalent
in
terms
of
priority
and
I.
Think
that
if,
if
you
want
to
manage
these
lists,
that's
fine,
but
maybe
they
shouldn't
be
labeled
by
a
priority.
Maybe
they
should
be
like,
like
these
are
the
10?
A
D
A
D
I
see
what
you're
saying
now,
but
on
the
other
hand,
if,
if
we
keep
adding
all
the
bugs
in
the
low
priority,
one
say
which
is
the
the
smallest
of
like
the
first
thing,
the
first
column.
Let's
just
call
it
the
first
one
I
think
a
big
bucket.
Then
it
defeats
the
purpose
of
why
this
was
created,
because
what
dr.
Elmont
said
is
that
you
needed
a
way
to
prioritize
bugs
I
guess.
So.
My
idea
was
that
we
pick
the
most
important
ones
and
then
we
split
them
to
low
medium
priority
and
high
priority.
A
F
Just
want
to
make
a
few
observations
right.
Any
number
one
I
understand
the
motivation
for
this
right,
but
I
think
it's
a
perpetual
problem
open
source.
The
goal
is
ultimately
I,
think
try
and
help
direct
people
towards
working
on
issues
which
the
community
has
somehow
decided.
That's
like
a
challenge
in
any
other
church,
community
and
I.
Don't
know
if
gonna
be
a
mansion.
Oh
right,
some
people
are
gonna
work
on
what
they
want.
Work
out
and
so
I
have
real
like
emerging
motivation.
F
I
have
no
objection
to
creating
this
project
so
far
it
hasn't
influenced
me
I,
just
going
back
and
looking
at
you
the
same
way,
I
did
so
I
mean
I
would
say.
Imagine
the
two
things
I
think
with
this.
You
know:
I
am
here
gender,
but
I
think
the
motivation
was
just
like
what
is
the
most
important,
not
what
is
I.
F
Think
that
some
people
were
looking
or
like
I,
don't
know
another
a
more
focused
way,
but
then
I
I'm
not
really
seeing
how
we
make
this
work
like
as
a
project
I
could
see.
A
group
of
people
like
I
could
see
Gregory,
saying:
hey,
I'm,
gonna,
enlist
a
couple
of
people,
we're
gonna,
make
some
decisions,
we're
gonna,
prioritize
them
and
we're
gonna
work
on
them.
That
way,
but
somehow,
like
expected,
everybody
else
is
gonna
see
it.
A
Okay,
but
so
they
think
definitely
will
fight
her
priority.
Maybe
isn't
good,
but
break
so
call
them
buckets
right
bucket.
One
bucket
two
bucket
three,
whatever
yeah
amorphous
label
is
but
I
still
want
somebody
who's
like
motivated
to
come
up
with
bugs
to
be
able
to
come
to
a
place
where
they
can
pick
one
they
can
fix,
and
so
I
think
like
having
a
list
of
all
issues.
Tagged
with
bug
is
good
in
the
sense
that,
yes,
it's
overwhelming
for
somebody
who
doesn't
who
can't
have
priority
like
doctor,
oh
I
can
fix
any
book.
A
You
wanted
to
right,
give
them
a
list.
It's
like
here.
You
know
here.
Here's
the
mount
here.
The
two
bugs
that
we
care
about
fixing
this
issue
and
this
milestone
everything
else
in
this
everything
else.
That's
tagged
with
a
milestone
should
be
really
easy
to
get
done,
should
be
their
high
priority
list.
Every
bug,
that's
tagged
with
the
next
bug,
fix,
milestone
and
I.
Don't
know
how
many
that
is,
it's
probably
like
30
or
something
that's
currently
in
that
list,
but
then,
after
that,
all
bugs
are
equal
unless
they're
on
that
list.
A
So
that's
where
it's
hard
to
like
okay,
great
great
I,
like
the
things
that
you
defined
as
bugs
there
most
with
usability
issues,
I
think
they're,
really
important,
so
maybe
think
have
you
curating
a
list
of
like
here's
bucks
but
I
feel
like
that's.
Also
kind
of
a
it
is,
are
always
arbitrary
as
to
which
ones
are
gonna
be
on
that
list,
and
it
seems
like
I
wonder
what
then,
what
the
value
is
of
having
so.
D
A
Think,
like
so
another
thing
and
concerned
about
is
like
hi
like
time
up
the
person
who
has
to
organize
the
list,
and
so
I
think
if
we
have
people
who,
like
feel
like
managing
the
bug,
licks
list
is
something
that
like
they
can
do
like
it's
a
place
for
them
to
contribute
where
maybe
they
can't
don't
feel
like
they
can
fix
the
bugs
that
they
can
do
the
list
and
choose
things
they're
most
important.
That's
great,
but
I
also
wouldn't
want
that
to
take
away
time
from
people
who
can
fix
the
bugs.
Unless.
D
D
If
you
sow
that
in
action
in
the
fastest,
the
tickets
are
currently
in
the
fixed
cost,
you
think
was
in
the
wearing
the
high-priority
projects,
so
this
has
changed
because
Nate
has
reviewed
and
merged
most
of
them.
So
what
this
has
created
in
comparison
to
last
week
is
that
there's
only
three
a
priority
now,
so
we
could
pick
some
from
like
a
couple
from
the
medium
probably
want
to
move
them.
So
this
was
my
idea
now
there's
a
gap
in
this
column.
G
D
D
D
A
D
Don't
I
would
I
would
hate
to
be
to
have
a
specific
person,
because
that
will
be
being
a
much
about
it.
Overhead
I
think
that
this
would
evolve
organically,
so
long
as
if
we
see
a
person
adding
to
that
least,
we
sort
of
like
say
in
the
community
that
you
know
what
the
medium
back
at
least
has
reached.
D
I
don't
know
12
Mike,
so
we
shouldn't
be
adding
this
things
are
getting
fixed
or
if
we
see
that
David's
15,
because
some
people
got
interested,
we
go
to
the
ones
that
didn't
see
any
activity
in
the
long
in
a
long
time,
and
then
we
remove
them
from
that
least
temporarily.
They
can
be
added
at
a
later
point.
It's
just
sort
of
like
a
thing
that
will
help
us
out,
like
even
during
the
meetup
meetings
that
we
have
now.
D
D
So
you
see
how
people
complain
that,
how
do
we
add
things
in
the
agenda
or
what
have
you
they
can?
They
can
just
go
ahead
if
they
think
that
something
is
critical,
they
flip
the
priority
and
we
will
have
some
rules
in
place
so
that
we
don't
suddenly,
you
know
end
up
with
like
30
issues
in
the
high
priority
is
that's
not
feasible
to
be
fixed,
but
we
need
to
keep
it
in
the
same
sort
of
like
level.
This
is
my
idea
of
what
how
this
could
work.
Yeah.
A
They
just
think
it
would
be.
We
need
to
be
careful
that
all
of
our
sources
are
identical.
All
the
time
right,
like
so
things
that
are
here,
marked
as
high
priority
votes
need
to
be
tagged
to
the
next
bug,
fix
release
and
the
things
that
are
in
the
bug
fix,
release
need
to
be
here,
and
this
high
priority
column,
yeah.
D
D
G
D
Think
I
think
that
that
sort
of
like
we'll
find
some
resistance.
We
can
discuss
that
especially
decides
to
join
me
their
own.
One
of
those
meetings
were
maybe
the
discussion
can
fire
up
again
on
gator,
but
I
think
that
as
Jen
said-
and
this
was
my
first
reaction
basically
told
the
framework
look
within
fix
bugs,
but
whichever
point
it
doesn't
have
to
wait
for
that
release
and
people
do
expect
new
features
in
new
releases.
Sorry,
my
new
releases,
so
it
would
be
sort
of
like
that.
You.
A
Can
limit
them
right
like
we?
Have
we
have
a
bunch
I
don't
know.
Maybe
this
is
how
how
like
last
release,
went.
I'm,
not
sure,
though
well
I,
guess
they're
like
and
they're,
like.
Oh
we've
got
like
a
week
left
like
what
and
these
things
like
know.
If
it's
not
on
the
list,
we
do
bug
fixes
inside
and
we
could
kind
of
rein
in
everybody's
excitement
on
that.
Getting
new
features
and
thing
and
focus
on
like
changed,
want
to
keep
contributing.
That's
fine
but
switch
gears
and
do
a
bug
fixes
yeah.
D
A
D
Is
what
yes-
and
this
is
why
this
discussion
is
happening?
I
would
ideally
like
to
formulate
a
page
that
we
the
similar
to
what
we
have
a
bit
of
work
for
the
milestones
and
stuff.
So
if
we
can
put
glue
there
that
you
know
the
first
column
doesn't
get
more
than
12
or
high-priority
means
that
this
x
and
y
in,
like
like
criteria,
there
need
to
be
met.
D
A
And
you
still
feel
like
there's
no
difference
between
the
first
column
and
second
column
here,
except
for
that
somebody
has
to
manually,
add
them
to
either
like
there's
no
difference
between
the
first
column
here,
the
second
column
here
and
the
tag
in
terms
of
priority.
It's
just
a
matter
of
like
how
do
you
want
to
look
at
it
like
if
looking
at
a
little
bits
is
too
long
like
a
long
list
is
overwhelming,
looking
at
a
short
list
might
be
less
overwhelming,
but
there's
no
difference
between
any
of
the
books
and
these
lists,
and
yes,.
D
Yes,
if
this
might
be
right,
but
it
could
have
been
sort
of
thing
over
the
lasts
a
couple
weeks
when
I
started
working,
it
is
that
things
the
mentality
was
that
is
this
a
really
serious,
but
how?
How
sort
of
like
often
does
it
happen?
So
if
it
doesn't
happen,
there's
not
many
changes
that
might
come
across
that
time.
D
So
this
was
my
mentality
on
tree
housing.
This
last
week,
for
example,
you
will
see
you
will
see
that
there
is
a
task
about
the
task
busting
thing
on
high
priority.
This
is
not
high
priority.
It's
there,
just
because
it's
blocking
me
from
working
on
anything
on
a
thing
that
I
would
degree
non
115
and
if
that
does
not
get
fixed,
you
will
never
get.
C
So
I
don't
know
if
this
is
an
option
with
github
I'm
sure
it
is
with
the
API
and
stuff
like
that,
but
with
the
tools
that
we
have
so
I
shared
somebody
concerned
with
with
gem
didn't
like
just
having
one
big
board
for
bugs
ultimately
will
get
overwhelms
like.
Even
if
it's
just
like
things
like
every
closed
issue
that
we
ever
fix,
you
know
we'd
have
to
take
it
back
out
in
the
bugs
project
in
order
to
keep
lists
from
having
the
hundreds
of
items
in
it.
C
C
It's
is
it
in
the
miles
or
not,
and
we
use
the
same
milestone
like
approach
up
things
and
then
the
board
could
be
used
for
determining
priorities
within
that
release
or
within
that
you
know
with
within
the
set
of
bugs,
and
then
it
then,
when
the
next
release
comes
out.
Well,
we
close
the
board.
We
move
all
of
the
issues
that
did
get
done
into
the
same
priority,
columns
in
the
next
board
and
then
we'd
end.
C
Up
with,
like
you
know,
a
constant,
like
the
management
of
the
board
might
be
a
little
bit
more
labor-intensive,
but
at
least
it
would
always
be
scoped.
You
know
it
would
always
just
be
whatever
is
milestone,
because
we
do
have
like
46
issues
right
now
in
the
next
milestone.
The
bug
fix,
milestone
and
I
mean
46.
Issues
is
way
too
many
issues
to
say
these
are
all
high
priority.
You
know
yeah
and
so
I
think.
B
D
Don't
I
don't
object
to
that,
but
just
just
make
it
the
closed
column
is
there
until
the
release
is
cut.
So
there's
a
like
the
three
dots
for
its
issued.
There
has
an
archive
option
which
actually
just
takes
it
off
the
boil.
It's
like
removing
it,
so
they
nia
would
be
that
once
we
cut
the
release,
we
remove
everything
from
the
cause
list.
It's
not
gonna
kill,
like
all
the
fixed
issues
ever.
A
B
A
Also
feel
like
all
the
ones
that
are
tagged
in
the
next
milestone,
those
should
all
be
really
close,
like
they
all
have
poor
requests.
Most
of
them
are
working,
it's
just
a
matter
of
like
we
need
a
review
or
it
needs
a
rebase
or
something,
and
so
I
think
that
even
though
they're
26
might
be
overwhelming
I
don't
know.
A
Maybe
you
do
like
eight
of
those
in
a
day
or
something
the
list
would
get
really
short,
and
so
I
won't
hate
to
drive
people
away
from
working
on
stuff,
that's
already
fixed,
but
not
in
yet,
and
towards
something
that
might
take
a
really
long
time
to
fix.
I,
don't
know,
I,
don't
know
how
to
just
capture
as.
D
I
said
all
the
issues
that
I
buy,
that
there
are
sort
of
like
experimenting
with
how
this
would
work.
It
doesn't
mean
that
they're
the
definite
list,
but
if
you
look
at
the
high-priority
cogs,
for
example,
none
of
them
is
milestones
yeah
and
taking
taking
the
first
one
in
the
list
aside,
which
is
less
just
like
it's
there,
because
as
a
blocker
yeah,
it's
a
blocker
for
the
for
adding
automated
images
to
the
flexible
layouts.
D
So
so
the
the
flexible
layouts.
It's
time
that
you
added
it.
The
image
is
updated
to
reflect
the
new
regions
or
what
have
you,
but
it's
not
reflected
in
the
user
interface
and
it
doesn't
get
refreshed
if
I
cast
clear,
you
need
to
clear
your
browser
class
see
the
new
thing,
so
this
is
a
blocker,
otherwise
that
other
issue
is
ready
for
review
and
very
close
to
be
done
so
yeah.
That
was
my
mentality.
Buddy,
there
doesn't
mean
this
big
bug.
You
know
it's
just
a
blocker
for
something
else
and
then
the
other.
D
The
second
one
in
the
list
is
the
one
with
the
font
weight
things
which
is
again.
It's
not
a
big
thing.
Ux
wise,
it
is
a
big
thing.
It
hasn't
been
milestone
either
for
some
kind.
So
so
it
was
my
way
of
saying:
hey,
I,
don't
see
anything
in
their
priority
list.
That
is
more
important
than
those
I
just
added
it
there.
D
If
you
disagree,
just
move
it
up,
Big
Sur
to
the
prettiest
column,
and
then
you
move
something
else
in
its
place,
so
it
wasn't,
it
wasn't
sort
of,
like
meant
as
a
binding,
think
we
should
so
forget
here
to
just
keep
working
on
that,
but
what's
that
it
was
just
sort
of
like
a
general
way
to
to
have
an
idea.
This
is
like
the
issues
now
are
1800.
G
What
about
another
ideas
if
there
was
a
so-called
box
quit
not
for
the
modules
but
for
core
and
or
people
who
say?
Oh,
we
for
this
release
cycle
we're
interested
in
focusing
on
packs,
and
then
this
group
can
decide
to
organize
that
sets
how
they
want
and
it
hasn't
to
be
a
solution
for
everybody,
but
for
these
people
for
this
certain
time,
yeah
and
then
then
they
go.
So
we
could
ask
round,
for
example,
Peter
or
anywhere
else,
just
who's
interested
to
do
that.
Yeah.
E
G
G
B
C
Can
sort
and
github
by
the
most
reactions
to
the
issue
and
we
could
use
like
the
most
thumbs
up
as
being
the
highest
priority
or
the
most
Rockets
the
highest
priority
or
whatever.
But
then
we
need
to
just
kind
of
establish
that
as
being
a
legitimate
way
of
sorting
issues,
rather
than
just
a
convenient
like
fun
cute
thing
to
do
on
issues.
You
know.
D
Yeah,
if
it
is
the
then
okay,
but
if
one
comment
and
a
thumbs
up
learns,
it
is
a
way
of
people
to
manipulate.
If
you
like,
the
the
cute
like
as
in
finding
a
look
to
come
with
the
make
sure
that
they
like
yeah,
looks
like
it's
just
how
my
issue
itself
thing
more
than
once,
when
you
say
the
issue
itself,
as
in
the
first
report,
reports.
C
D
C
We're
good
posture,
yeah,
let's
see
I
know
we
don't
haven't
really
reached
in
these
firm
conclusions,
but
we've
got
a
lot
of
things
to
think
about.
At
least
let's
postpone
the
last
Q&A
item,
which
is
also
talking
about
scheduling
for
this
meeting.
We
can
talk
about
it
next
week
as
an
ongoing
topic
about
whether
we
could
schedule
these
meetings
to
alternate
the
scheduling
anything
to
make
it,
so
it
would
get
more
geographically
diverse
people
participating
in
the
development
of
backdrop.
So
that's
someone
to
think
about
for
next
week.
C
Let's,
let's
grandpa,
you
guys
have
any
less
things
serious
like
that.