►
From YouTube: Backdrop Design & UX - Mar 28
Description
Today’s design agenda: http://bit.ly/2Ybls8w
A
All
right
we
are
on
air,
it
is
Thursday
March
28,
and
this
meeting
is
check-in
on
design
and
usability
tasks
for
Makarov
CMS.
So
if
we
start
with
our
web
sites,
backdrops
we
musta
org
has
a
couple
of
long-standing
issues
that
we
would
love
to
make
some
progress
on
both
of
them
to
be
blocked.
At
the
moment,
one
of
them
is
improving
the
user
experience
for
finding
modules,
themes
and
layouts,
or
checking
to
see
if
modules
and
themes
of
lives
you're
using
his
equal,
seven
are
built
on
a
backdrop.
A
This
issue
has
also
turned
into
a
rabbit
hole
because
we
are
trying
to
rework
the
way
the
search
worked
and
the
Miranda
some
issues
with
the
core
search,
and
then
we
thought
you
should
see
different
search
than
we've
cited,
fix
the
core
search
and
them
that's
trend.
We
come
on
ball
of
yarn
that
we're
untangling,
so
my
plan
was
to
undo
the
reworking
of
the
search
and
start
with
the
redeeming
of
the
page
so
that
it
will
use
view
modes
instead
of
fields
and
that
will
allow
us
to
later
switch
that
to
search
pretty
easily.
A
But
what
more
importantly
also
allow
us
to
place
other
things
on
the
page
like
listing
not
only
of
the
moccasins
layouts,
but
we
have
these
things.
They're
called
a
placeholder
projects
and
those
are
things
like
token
in
path,
auto
and
modules
that
have
been
moved
into
core
have
a
little
placeholder
patients
say:
hey,
you
don't
need
this
anymore.
A
This
is
why
and
so,
I
think
if
somebody's
searching
for
pathauto,
rather
than
not
returning
anything
at
all,
we
should
return
the
thing
that
says:
oh,
we
have
that
already
you
don't
need
it
and
that'll
give
some
people
some
more
confidence
in
choosing
back
up,
because
it
will
look
like
more
of
their
stuff.
It's
our
demon.
It
actually
is
ready,
so
that
I
think
is
the
next
step.
There
I
think
they
have
so
I
have
a
branch
on
my
local
site,
which
probably
needs
to
be
updated.
A
Now
they've
had
several
security
updates
for
doctor
of
CMS
org.
That
includes
just
the
change
to
you
modes
and
the
new
theming
for
the
view
modes.
So
my
plan
would
be
to
push
that
Brandt
update
the
branch
rebates
update
the
branch
push
it
up
and
then,
if
somebody
can
help
me
test
that
I
don't
want
to
push
it
live
until
someone
else's
looked
at
it,
because
sometimes,
if
I
own
get
it
way,
I
look
at
it
doesn't
work
and
I,
don't
think
we
have
a
test
site
set
up.
A
However,
we
do
have
a
new
server,
and
this
is
in
the
next
issue,
something
on
with
that
lunch
that
next
so
that's
gonna
make
soon.
We
have
a
plan
for
move
forward.
It
just
kind
of
blocked
by
the
fact
that
you
haven't
had
I,
haven't
particular
had
very
much
time
lately
to
work
on
on
Joseph's
Lance.
The
next
issue.
A
Me
pushing
something
testable
up
to
a
place
where
you
can
test
it.
The
second
place
is,
we
need
a
place
to
test
it,
and
then
the
third
thing
is
the
person
that
doesn't
testing
so
the
place
to
test.
It
would
be
fine
if
you
would
pull
it
down
to
your
local
and
you
could
test
join
your
local,
but
that's
a
little
complicated
because
you
have
to
get
databases
into
the
big
files
from
live.
A
B
B
A
We
have
something
like
that
in
our
up
phrase
page,
but
it
would
probably
be
good
to
have
a
more
specific
to
rupal.
Only
this
is
your
Drupal
7
site.
This
is
what
you
need
to
know
option
one
thing
I
would
love
to
have
as
part
of
is
not
just
a
documentation
page,
but
there's
a
module
called
upgrade
status
that
Drupal
uses
that
lets.
You
know
how
how
all
of
your
projects
are
in
a
status
verb?
What
they're
going
to
like
your
Drupal?
Seven,
it's
like!
A
What's
the
triple-eight
status
of
all
these
modules,
it
would
be
really
cool
if
we
could
take
that
module.
I
think
it
existed
for
seven
from
six
as
well
port
of
your
backdrop
and
then
use
that
to
go
through
their
list
and
say:
hey
all
of
these
exists
and
we
can
have
a
status
for
like
stable
release
versus
def
version
where
it
would
get
hub,
and
then
we
would
have
like
merchants
in
the
core.
So
we
can
have
like
little.
A
You
know
color-coded
checkboxes,
to
let
people
know
how
many
modules
or
last
it
might
also
be
able
to
do
something
like
random
checking
of
the
code.
It's
like
a
huge
amount
of
code
like
commerce
that
wouldn't
have
like
an
exclamation
point,
be
like
this
one's
gonna
be
hard
and
then,
if
it's
just
like
a
short
like
block,
module
is
good.
This
is
gonna,
be
easy,
and
so
it
would
help
people
kind
of
gauge
like
how
far
they
are
from
that
point.
A
B
C
A
It's
a
backdrop:
I
think
you
could
live
in
our
control
group
yeah.
We
just
need
to
very
clearly
state
like
this
is
for
turbo
and
then
maybe
not
even
give
it
an
official
release
just
like
in
the
documentation
page,
we
could
link
to
a
bill.
I
can
sell
this
and
your
Drupal
site
link
to
the
github
car
bomb,
and
then
that
way
we
wouldn't
have
any
issues
with
telling
a
lot
of
your
project
installer,
where
people
make
trying
to
talk
on
site,
but
we
could
also
use
it
in
the
future.
A
C
A
Yeah,
my
preference
would
be
to
fork
because
well
I,
don't
know
in
a
perfect
world,
we
still
had
stuff
weekly
contribute
to
the
cheerful
project
like
look
at
it.
So
maybe.
C
A
C
We
need
to
build
a
something
some
status
fades
on
beautiful.
There
is
a
ticket
that
we
have.
We
have
annex
like.
Where
are
we
at
or
something
like
that?
What's
the
status,
the
current
status
and
it
shows
which
modules
have
been
ported
which
are
being
planned
to
be
ported?
Maybe
that
would
also
be
a
good
idea.
I
think
we
have
the
top
100
modules.
C
A
A
A
A
Links
to
this
page
would
be
good,
and
then,
if
you
want
to
read
this
and
see,
if
there's
a
way,
we
can
make
it
less
heavy
reading
that
might
be
useful
and
then,
if
we
can
figure
out
how
so
we
update
those
slots
like
every
time,
we
give
a
talk.
I
would
love
it
if
we
could
figure
out
a
way
to
have.
A
So
any
ideas
on
how
to
do.
That
would
be
great
because
I
think
all
of
these
improve
all
of
these
resources
are
useful.
Like
you
know,
we
have
X
of
the
top
on
the
good
Drupal
modules
ready
for
backdrop.
We
have
X
triple
modules
included
in
them
core.
You
know
all
of
that
stuff
I
think
is
really
valuable
and
then
five
years
find
out,
if
your
site
is
ready
to
use
this
module,
I.
B
C
A
A
So
Gregory
will
you
please
create
an
issue
in,
or
you
that
says,
add
Drupal
7
info
to
home,
page
and
then
I
have
we
have
designs
for
putting
more
stuff
on
home
page?
We
just
have
less
stuff
on
the
home
page
right
now
that
fits
the
designs,
so
I
think
would
be
really
easy
to
just
repurpose.
One
of
those
bars
like
this
is
the
triple
7
line
and
I
think
we
should
put
three
things
in
there.
We
should
put
number
of
Drupal
7
controls
top
top
100
that
are
ready.
A
A
B
C
C
C
B
A
I
think
I
don't
think
we
should
over,
because
that's
gonna
there's
a
lot
of
places
that
check
module
status,
that
that
would
fax
that
we
maybe
don't
want
it
to,
but
I
think
telling
people
that
change
one
line.
An
info
file
is
totally
reasonable.
My
preference
would
actually
be
to
put
that
in
like
devel
module,
so
if
you
have
to
val
module
on,
you
definitely
know
enough
to
change
the
module.
If
you
don't,
maybe
we
shouldn't
be
telling
you
to
do
it,
because
there
are
some
modules
that
might
destroy
your
site.
Yeah.
C
Yeah,
then,
though,
this
is
this
is
the
this
might
be
my
reasoning
about
that.
If,
if
people
have
the
compatibility
Suites
on,
we
shouldn't
be
disallowing
them
to
enable
it,
but
what
we
can
do
is
for
these
modules.
We
should
have
a
confirmation
message,
the
same
way
that
we
have
when
we
install
modules
that
says
you're
gonna
break
your
site.
A
Of
saying,
but
the
problem
is
that
so
we
can
do
that
when
someone's
like
pushing
the
button
on
the
form
we
can
like
interrupts
that
pattern.
But
the
problem
is
like
if
they're
coming
from,
like
Drupal
upgrades
or
something
we
don't
have
any
way
to
interrupt
the
process
of
them,
they
already
have
it
enabled
so
there
and
there's
a
bunch
of
places
like
that.
Where,
like
we
there's,
we
I
think
it
would
be
really
dangerous
if
we
just
head
back
to
our
on
modules
that
didn't
have
a
backdrop
line
in
the
info
file.
A
I
think
like
if
we're
dealing
with
user
interface
stuff,
it
will
be
much
better
to
you
know,
put
this
in
Devon
modular.
It's
like
you
want
to
enable
override,
yes
and
then
Devon
module
will
go.
Make
that
change
for
you,
like
that's,
there's
still
kind
of
a
button
cookie
process,
but
I,
don't
think
it
should
happen
automatically
I
think
it's
just
too
dangerous.
Hello.
B
A
You
never
know
we
should
try
it
and
see
what
happens.
I
just
want
to
emphasize.
That
needs
to
be
done
with
caution,
because
there
are
a
lot
of
places
where
don't
think
we
can
notify
people
appropriately.
So
we
just
need
to
have
that
in
mind,
but
I
do
think
we
should
look
at
it
see
what
the
problem
space
looks
like
so.
C
It's
a
common
pattern
because
they
have
their
those
experimental
modules
and
they
say
that
you
enable
them
at
your
own
risk,
because
you
might
at
late
these
visit
later
one
may
be
removed
from
the
codebase,
and
then
you
might
be
left
stranded
with
features
that
you
cannot
uninstall
or
remove
or
do
something
about.
It.
I
think
that
we
could
treat
things
in
a
similar
way
with
you.
C
A
Know
most
of
the
people
that
backup
are
probably
not
capable
well
I,
don't
know,
but
I
would
hope
that
we
would
get
a
whole
bunch
of
people
using
backup
who
aren't
capable
fixing
those
kinds
of
problems
where
the
average
cheerful
site
is
probably
going
to
have
a
dev
team,
or
at
least
a
developer.
Who
would
be
able
to
do
that
so
I
think?
Even
though
Drupal
8
has
done
things,
we
should
look
at
that
and
be
like
what
are
they
doing?
Can
we
steal
from
that?
C
C
A
Sure
that
they
have
like
permission
set
up
really
to
do
the
writing.
Yeah
I,
think
that
would
be
good
because
then
you
could
be
like
start,
your
backdrop
upgrade
and
then
it
would
be
like.
Oh
sorry,
these
are
Drupal
modules.
Thinking.
Ok,
there
you
go
you're
done
yeah.
That
would
be
really
slick.
Yeah.
C
A
C
A
So
speaking
of
new
servers
exits,
you
on
our
agenda
is
number
four
22,
which
is
to
add
a
give
me
demo
button
on
backups
homepage,
we're
currently
enough
to
use
tugboat
for
some
reason.
Tuck,
both
stocks
working
with
our
folder
server
or
older
server,
was
running
an
older
version
of
PHP
for
building
a
newer.
A
Of
PHP,
that
issue
is
almost
done.
It
needs
testing.
So
for
those
of
you
who
want
to
hop
tests,
we
basically
just
need
to
make
sure
bankruptcy,
mesta
or
API.
No
fact,
I've
seen
this
or
form-factor
up
CMS
at
work,
localize,
a
vector,
Pianist,
org,
I,
think
that's
it
all
work
on
the
new
server
and
so
I
linked
to
a
specific
comment
in
the
queue
that
describes
how
you
can
test
that,
so
the
server
is
up.
A
A
So
we
just
need
to
make
sure
everything's
working
fine
go
ahead
and
log
in
to
the
sites,
if
you're
an
admin
on
name
of
them,
you
can
check
and
see
if
any,
like
errors
or
hearing
that
database
log
and
stuff
like
that.
But
in
theory
it
should
all
be
fine.
The
only
issue
is
the
local
inside
these
triple
seven
and
triple
seven,
doesn't
always
work
great
on
HP,
7
I.
A
Think
we've
got
a
you
know
we're
on
the
latest
version,
so
there
are
a
bunch
of
core
passion
patches
that
have
gone
in
to
fix
that,
but
there
could
be
some
controls.
We're
running
cost
me
at
least
to
make
it
look
better
on
HP's
own.
So
that's
the
only
thing
I'm
really
worried
about
my
local
instance
is
running
PHP.
C
Have
tested
these
brings
me
for
Justin
when
he
limited
it
like
the
site
and
then
I
think
shortly
after
could
have
been
a
few
hours
during
the
day
that
we
have
the
meeting
or
a
few
days
after
9:00
to
mention
that
it
might
be
a
bit
be
7
vs.
5
issue,
since
this
is
the
server
the
new
one
is
running
the
PHP
7.
Does
that
mean
that
the
button
might
work
there?
Yes,
you
should
test
about
detail.
Have
you
you
haven't
tested
it.
A
All
right
so
as
part
of
getting
a
new
server
right
now,
that's
a
good
place
where
I
was
thinking
about
pushing
the
branch
that
redoes
the
magis
things
and
layout
pages
to
use
the
view
modes.
We're
testing
there
as
well,
so
maybe
I'll
push
that
up.
We
can
see
if
that
works.
The
way
we
think
it
does.
Then
the
other
thing
was
in
general.
What
are
we
gonna
do
about
testing
and
I
was
thinking
we
probably
should
put
like
a
beta
version
of
every
site.
We
have
somewhere
we're
testing
for
this
purpose.
A
I'm,
not
sure
all
of
them
will
be
used
all
the
time,
but
I'm
pretty
sure,
backup,
CMS
Oracle,
that
get
used
to
time
so
just
having
them
there
so
that
we
can't
do
things
like
a
drastic
changes.
I
think
the
forum
site
that
it's
possible,
that
we'll
add
something
crazy
new
feature
there
and
we
want
to
customers.
A
The
API
said
doesn't
get
a
lot
of
attention,
but
yeah
and
localized
we've
got
a
bunch
of
people
easy
not
so
if
we
want
to
so
I
think,
there's
probably
an
issue
in
the
queue
that
talks
about
having
a
beta
site
somewhere.
I
think
there
is,
if
not,
we
might
just
mention
it
to
Justin
and
see
how
he
feels
about
it.
One
thing
we
could
do
is
we're
about
to
have
only
node,
that's
not
being
used
anymore
right
because
we're
moving
all
of
our
stuff
to
the
new
one.
A
We
could
scrap
the
old
one,
build
another
new
one
and
then
copy
like
the
node
has
like
a
copy,
the
solenoid
button.
We
could
copy
it
a
little
to
be
all
the
configures
and
everything
and
then
just
think
it
doesn't
get
going
and
change
since
they're
all
like
beta
sites
instead.
So
that
might
be
a
really
easy
way
to
get
us
like
an
exact
copy
here.
The
thing
server,
which
will
be
great
for
customers.
A
Okay,
backed
up
the
product,
so
version
1.1
three
will
have
feature
freeze
on
papers
which
is
just
over
a
month
away,
and
we
have
a
bunch
of
great
new
issues
for
core
that
we
would
love
to
see
and
specifically
are
gonna
improve
usability.
My
favorite
one
is
dashboard
module,
which
is
number
four.
Ninety
five
so
far,
I
think
three.
You
want
a
bunch
of
UI
inhairent.
It's
that
you're
gonna
submit
me.
A
Also
look
at
it
and
rejected
it,
saying
it
needs
tests,
of
course,
so
I
know
I
have
an
issue
or
I
would
like
to
revisit
it
and
start
looking
on
tests
so
that
we
can
get
that
tested
and
then,
if
you
have
an
extraneous
or
whatever
they
should
agree,
they're
replacing
test
and
then
we
have
saved
rafting
core
was
proposed
for
113
decision
number.
31
57
nobody's
actually
started
working
on
this,
yet
I
think
we
have
a
several
other
issues
with
parts
of
it.
A
A
It's
got
like
a
clear
title:
let's
just
do
this
thing,
but
since
then
there's
no
pull
requests
on
this
issue,
so
I
don't
know
if
it
would
make
sense
to
revisit
the
old
proquest
or
just
start
from
the
control
or
what
but
yeah
we
don't
have
one
for
you
yet
for
113.
So
if
we
want
to
get
this
in
in
the
next
month,
we
definitely
need
to
have
something
soon.
A
A
The
next
issue
on
usability
list
is
promoted
modules
on
the
installer
I.
Looked
at
this
again
today.
I
think
the
main
blocker
here
is
that
nobody
really
knows
where
it
start.
So
I
was
thinking
and
I
do
this
every
now
in
the
world,
when
there's
an
issue
that
has
a
whole
bunch
of
comments
on
it,
I
go
through
and
read
the
whole
thing.
I
have
like
open
to
to
text
edit.
A
A
I
know,
we've
talked
about
it
a
couple
of
times
where,
except
to
on
bankruptcy
meso
or
we
obsess
to
do
a
project
module,
it's
tough
to
do
or
a
bunch
of
different
places
that
all
have
to
get
tied
together,
I,
don't
think
any
of
those
need
to
happen
in
the
particular
order.
Just
the
fact
that
we
don't
have
them
written
down.
I
think
is
thinking.
A
A
C
I
had
some
half
way
sort
of
like
finished,
pull
requests
for
other
usability
issues
and
other
issues
ago.
So,
and
some
of
them
are
actually
are
TBC.
I
looked.
We
have
like
13
issues
that
are
TBC
now.
Part
of
them
are
bugs
and
there's
a
couple,
maybe
two
or
three
of
them
the
kind
of
series,
but
there's
a
few
other
things
that
we
are
trying
to
get
in
like
redesigning
water,
pumping
abate,
the
maintenance
mode.
Please
under.
A
That
book
in
our
design,
issues
which
is
great
but
yeah,
there
are
a
ton
of
usability
stuff.
I,
don't
know
if
that
all
came
from
you
but
I
feel
like
you've
been
on
every.
A
C
Might
be
I
might
be
annoying
at
times
because
I
when
I
could
not
not
annoying.
You
know
in
the
fact
that
there's
many
full
requests
that
have
filed
and
people
have
come
and
indignant
and
they're
in
need
work
in
each
work.
But
then
I
get
excited
about
about
all
this
stuff,
so
I
need
to
get
back
to
to
those
that
need
work
and
I
will
let
you
know
guys
if
I
need
help
with
anything,
because
sometimes
I
get
myself
into
way.
C
So
it
was
that
about
promoted,
oh
yeah,
the
other
one
was
the
one
about
the
names
of
the
fields,
the
fields
that
was
a
good
one,
thought
and
I
think
that
we
should
either
merge
your
cool
requests
first,
because
that's
I
didn't
take
a
look
at
it
and
they're
all
up
I
think
I
will
as
well.
If
we
made
your
pull
request
first,
then
you
should
have
take
mine
to
use
the
functions.
C
A
A
Another
function
think
it's
the
most
popular
name
for
a
given
field,
so
that
if
you're
gonna
build
something
like,
for
example,
a
note
you
there's
a
list
of
fields,
I
needed
to
it
was
showing
the
machine
name
and,
like
I,
know,
it's
easy
to
get
the
machine
name,
but
that,
like
when
you're
importing
from
Drupal
7
like
I
was
it
was
like
taxonomy
term.
One
type
something
we
term
two
text
I.
Let
me
trim
three
and
I'm
like
I,
don't
know
what
these
are
part.
A
Machine
names
are
really
not
useful,
so
I
was
like
I
need
the
field
labels
there,
and
so
then,
of
course,
I
went
into
the
rabbit
hole,
trying
to
get
a
field
label,
and
they
realized
was
really
hard
and
really
stated
function
and
I
said
well.
Where
can
I
implement
it?
And
then
I
found
their
like
field
list
page
and,
of
course,
period
already
creating
issue
that
was
like.
Why
are
there?
No
human
readable
names
of
the
field
is
pagers
and.
C
You
should
get
bothered
by
the
fact
that
we
have
a
separate
tab
that
says
using
views
and
now
that
we
have
the
the
list,
that
sort
of
like
lists
the
multiple
places
where
a
single
field
is
I,
don't
see
why
not
modes
that
but
I'm
not
gonna
bring
that
up,
because
I
really
want
that
to
get
merged,
and
then
we
can
follow
up
and
there's
also
the
use
case
that
we
have
fields
being
used
in
as
blocks
in
layouts.
So
this
would
be
listed
there.
C
So
if
one
person
needs
to
do
something
with
a
field
like
move
it
or
remove
it,
and
they
wanna
see
all
right,
where
is
this
being
used?
They
will
have
all
the
content
types
and
what
this
field
is
called
for,
its
content
type,
all
the
views
is
being
used
to
in
cuts
displays
and
then
all
the
layouts,
where
it's
being
used
in
what
regions.
So
they
have
our
you
know
a
big
overview,
but
let's
get
those
small
ones
that
are
almost
ready
aim
and
the
other
way.
A
A
Well,
he's
gonna,
say
minor
five
sets
anyway,
but
since
I'm
working
on
tests
for
dashboard,
I'm
gonna
have
to
get
my
head
into
test
land
and
they
might
as
well
just
very
test
for
everything.
There's
another
issue
that
that
broken
layout,
clone
thing
needs
tests
and
so
I
just
need
to
the
tricky
cuz
tests
are
hard,
but
once
you
like
at
your
head
in
them,
then
you're
like
oh
I,
get
how
they
work.
But
then
every
time
I
leave
them
alone.
C
C
A
Okay,
the
only
other
issue
we
haven't
yet
talked
about.
That's
in
our
agenda
is
adding
predefined.
Color
seems
to
basis
I
think
we
talked
about
this
in
our
last
design,
meaning
the
current
issue
is
that
we
ran
all
the
colors
through
an
accessibility
checker,
and
we
have
some
issues
with
our
color
palettes,
where
we
can't.
A
Combination
of
colors
with
the
current
number
of
settings
that
are
provided.
Sometimes
we
have
like
one
color
on
one
background
and
if
you
change
the
top
color,
then
it's
not
enough
accessible
background
check
the
background
color.
It's
not
exactly
contrast
with
the
foreground
and
so
we're
trying
to
figure
out
what
to
do
about
that.
I
had
an
idea
which
was
like
for
those
particular
color
palettes.
Maybe
we
could
add
some
kind
of
a
CSS
gradient
to
make
the
lighter
once
they're
too
late,
darker
or
the
darker
once
they're
too
dark
lighter.
B
A
Maybe
that
would
be
like
a
way
we
can
work
around
for
those
particular
color
palettes
how
to
adjust
the
contrast
so
make
it
accessible.
I,
don't
know
if
that's
possible,
I
don't
want
to
put
code
yet,
but
what's
my
idea,
I
keep
saying
it
a
lot,
but
already
in
an
issue
but
yeah.
So
that's
it
for
our
core
issues.
I
know,
there's
a
ton
of
usability
stuff
that
came
up
recently.
That's
tagged
for
the
113
miles
or
even
the
next
bug
fix
milestone.
A
C
C
The
only
thing
that
are
not
is
this:
as
I
mentioned
there,
the
error,
if
you
filter
the
issue
list
by
our
TBC
status,
we
have
30
issues.
Currently
there
and
I
think
there's
a
couple
of
more
they're.
Almost
there
and
quite
a
few
of
them.
Maybe
five
or
six
do
not
have
a
milestone
set,
but
they
have
the
candidate
that
would
be
great
like
if
you
and
or
innate
or
anyone
else
can
go
through
them
and
sort
of
like
see
if
they're
a
fit
for
the
112
or
113.
So.
A
Big
always
works
through
our
TVC
list.
That's
his
go-to.
He
doesn't
necessarily
look
at
what's
in
any
given
milestone,
so
that
will
get
his
attention.
That's
our
TV
Selig
as
attention
you
who
doesn't
have
a
milestone
on
it.
I
don't
know
her
jewels
working
process,
but
I
noticed
that
he's
been
super
on
top
of
stuff.
That's
been
coming
in
lately,
giving
it
like
technical
reviews
and
opinions
and
stuff
so
and
I
think
he
even
had
it
like
milestone
candidates.
A
C
Think
it
was,
it
was
heard
that
mentioned
that
we
need
another
status
like
we
have
the
RT
BC,
and
then
we
should
encourage
more
people
that
are
not
technical
to
mark
issues,
a
TB
see
if
it
works
and
then,
if
it
needs
code,
review,
have
a
separate
tag
for
that,
so
that
someone
with
more
skills
should
just
you
know
see
for
wise
if
things
are
looking
good.
Okay,.