►
From YouTube: November 5, 2020 - Weekly Developer Meeting
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
All
right,
hello,
everyone,
it's
november,
5th
2020..
This
is
the
weekly
dev
meeting
for
backdrop
cms.
Let's
do
a
quick
round
of
introductions
for
those
presents.
I'm
nate
lampton,
I'm
core
committer
and
we've
had
some
exciting
progress
on
tugboat
pull
request
sandboxes
this
week
that
I'll
be
happy
to
report.
Let's
go
to
gregory.
Can
you
give
us
a
quick
update
on
yourself.
B
Hi,
so
I'm
greg,
I'm
usually
in
australia,
but
now
joining
from
greece
interested
in
anything
related
about
trucking
bachelor,
poor,
just
joining
to
see
what's
the
status
and
get
things
going
for
the
next
minor
release
in
january,
passing
on
to
justly.
D
I
am
not
muted,
so
I
didn't
have
to
go
through
that.
Thank
you.
Erickson
up
in
st
paul
tim
up
in
deerwood,
minnesota
yep,
there's
a
few
deer
out
there.
Today.
Deer
hunting
starts
tomorrow,
so
things
get
exciting
and
deer
with
during
deer
hunting.
D
Everybody
stays
at
home.
We
got
more
reasons
to
quarantine
ourselves
now,
anyway.
Sorry
about
that,
we
totally
lost
my
thought.
The
big
thing
I
think
I'm
working
on
right
now
is
the
telemetry
initiative,
but
also
got
a
few
other
things
going:
we're
trying
to
build
up
a
distribution,
maybe
maybe
the
first
official
distribution
for
backdrop
around
events,
although
whether
or
not
it
turns
out
to
be
a
distribution
is
up
for
grabs.
But
contact
me
if
you're
interested
in
that.
That's
all
bye.
A
Thanks
tim,
so
our
contrib
project
updates
for
this
week,
we've
had
four
new
contrib
modules
released
this
past
week.
Those
include
the
eva
module
entity,
views
attach
module
language,
icons
dismiss
and
registration
modules,
thanks
to
alan
mels,
bw
panda,
herb
dual
and
joseph
for
making
those
new
modules.
A
Let's
see
we'll
move
right
on
into
the
current
progress
report
on
the
project,
starting
with
117,
the
current
bug
fix
release.
117.2
will
be
the
next
minor.
Sorry
bug
fix
release
just
two
issues
to
discuss
today.
A
One
of
them
is
just
a
an
issue
that
you
can't
place
blocks
into
a
layout
that
pull
fields
from
the
current
user.
So
if
you
try
to
pull
out
like
the
users,
I
don't
know
bio
field
or
something
like
that
that
you've
added
to
their
account.
You
can't
do
that
for
the
current
user,
you
can
do
it
for
any
hard-coded
user
or
on
a
user
profile
page,
but
not
for
the
current
one
and
the
issue.
2398
is
simply
to
fix
that
bug.
A
It
seems
like
the
alternative
approach
that
we've
discussed
seems
to
be
accessible
or
sorry
acceptable,
and
so
the
there
is
a
working
pull
request,
but
there's
a
suggested
new
approach
that
seems
to
be
going
forward.
That
is
a
lower
impact
change
that
fixes
exactly
that
problem
without
trying
to
touch
other
parts
of
the
broader
like
global
user
account
or
loading,
the
user
account
on
every
single
page
load.
A
Yeah,
I
think
that
would
be
a
good
idea,
because
it's
it's
rtbc
the
current
approach,
like
you
know
that
would
work,
but
there
are
repercussions
to
it
that
we
did
collect
more
feedback.
It
looks
like
both
bw
panda
and
brad
bulger.
Both
say.
If
that
new
approach
will
work,
then
that
would
be
good
I'll.
I
will
go
ahead
or
would
you
do
that?
Gregory.
A
Okay,
next
up
is
tugboat
qa
for
pull,
request,
sandboxes
issue
4351.
A
This
is
something
that
we've
been
working
out
for
a
little
while
now
that
we're
considering
switching
our
sandboxes
when
we
make
a
pull
request
to
switching
from
zen
ci
or
current
provider
over
to
tugboat,
and
so
we
now
have
that
set
up
for
evaluation
and
all
new
poll
requests.
A
I
think
that
means
that
all
the
poll
requests
are
currently
getting
two
sandboxes
one
on
tugboat
and
one
on
zen
ci,
and
so
that
will
help
us
with
our
evaluation,
big
shout
out
to
bw
panda,
who
did
all
of
the
work
in
setting
up
what
was
necessary
inside
of
the
core
repository
configuring,
the
tugboat
account
on
the
tugboat
side
and
raising
the
request
to
get
our
tugboat
account
promoted.
A
We
did
reach
out
to
the
tugboat
qa
organization
or
company,
and
they
fronted
us
another
like
maximum
tier
account
before
you
get
into
enterprise
plans,
which
gives
us
40
gigabytes
of
available
space
and
right
now,
all
new
sandboxes
are
just
being
spun
up
on
every
poll
request
in
the
future.
A
We
probably
will
want
to
refine
the
configuration
a
little
bit
to
perhaps
put
an
expiration
time
on
sandboxes
like
pretty
generous.
We
could
probably
go
like
as
long
as
six
months
right
now
without
it
being
a
problem
and
then,
if
you
needed
to
regenerate
a
sandbox,
you
might
close
and
reopen
it,
and
that
would
regenerate
a
new
sandbox
and
I
think
that
would
be
relatively
low
impact
and
also
keep
us
underneath
that
40
gigabyte
limit.
A
Currently,
if
we
were
to
have
a
sandbox
on
every
one
of
our
open,
500
pull
requests,
we
would
exceed
our
limit,
but
by
being
a
little
bit
more
judicious
with
our
who
gets
the
sandbox
requirements,
I
think
we'll
be
able
to
fit
within
that
40
gig
limit
for
at
least
several
years.
It
seems
at
our
current
trajectory.
B
Yeah,
I
would
like
to
add
that
tested
it
in
the
tugboat.
Sandboxes
are
spun
up
equally
fast,
as
the
previous
unboxing
that
we
had
just
the
the
difference
is
yeah.
It's
like
it
takes
a
few
seconds,
like
maybe
10
seconds,
20
seconds.
It's
there
up.
The
only
difference
is
that
if
you
revisit
the
sandbox
after
some
days
it
idles,
so
it
takes
a
couple
of
seconds,
maybe
five
seconds
to
spin
up
again,
but
that's
not
a
big
issue.
A
I,
since
I
haven't
actually
seen
one
of
the
sandboxes
in
action
since
peter
set
it
up,
do
you
have
to
run
through
the
installer
or
is
it
already
installed?
It's
like
it.
No.
B
So
it's
admin
so
like
before,
and
the
password
is
automatically
like
randomized,
something
like
a
little
bit
more.
Maybe
eight
characters
instead
of
six,
something
like
that,
but
still
randomized
one
thing
that
might
be
inaccurate
on
what
she
said,
but
I'm
not
entirely
sure
is
that
we
don't
have
two
some
boxes.
I
think
that
only
the
time
mode,
some
boxes
are
being
spun
up
for
new
pull,
requests,
I'll
double
check
now
and
tell
you
but
the
old
ones.
They
still
have
the
the
zen
ci
sandboxes.
B
A
Okay,
we
might
check
with
peter
I
mean
I
can
look
at
the
organization
settings
too.
I
bet
that
he
may
have
disabled
the
web
hooks
to
send
out
to
zen
ci.
It
is
confusing
to
have
two
different
options,
so
I
don't
think
that
that
is
a
bad
call
on
his
part.
If
he
did
make
that
change.
B
A
Great
yeah,
that's
awesome,
well,
big
thanks
again
peter
for
doing
all
the
work
and
setting
that
up
it's
very
exciting.
It
also
kind
of
precedes
us
down
like
we
also
have
other
opportunities.
A
I
think
we
have
some
issues
that
I
don't
have
them
pulled
up
in
the
agenda
this
week,
but
for
things
like
php,
syntax,
checking
and
other
automated
testing
that
we
could
move
to
github
actions
as
being
like
an
available
free,
unlimited
processing
solution
for
us
and
now
that
it's
built
into
github
and
so
widely
available
and
free,
there's
a
lot
of
good
reasons
why
we
might
pursue
that
as
well.
A
So
that
would
kind
of
give
us
more
direct
control
over
the
way
that
all
of
our
ci
processes
work,
and
that
was
the
big
appeal
for
tugboat-
is
that
we
had
more
access
and
configuration
to
controlling
the
way
that
it
works
and,
in
particular
doing
things
like
upgrading,
php
versions
or
if
we
get
automated
testing
like
things
that
are
infrastructure.
Specific.
Like
this
issue
about
my
sql
8
support,
we
could
potentially
have
an
infrastructure
that
we
could
say
just
give
me
my
sql
8
and
run
the
tests
against
it.
A
So
more
flexibility
is,
is
what
we're
after
here
and
it
seems
like
you
know,
tools
are
evolving
and
we're
trying
to
just
keep
up
with
using
the
best
tools
that
are
available
to
us.
A
So
118
118
is
the
next
minor
version
of
backdrop.
It
will
be
released
january,
15th,
2021,
now
that
it's
november,
it
always
seems
like
every
time
the
calendar
rolls
over.
It
seems
ever
so
much
closer
than
than
it
was
the
day
before
my
sequel.
8
support
is
an
issue
that
we
want
to.
We
we
definitely
are
going
to
get
into
118..
The
issue
of
4238
is
has
a
pull
request
that
has
been
merged
into
the
1.x
version,
so
it
is
in
118
already.
A
So
far
since
that
issue
has
been
merged,
we
haven't
had
any
additional
feedback
saying
one
way
or
the
other,
that
there
have
been
any
problems
or
confirmations
that
it's
working
but
prior
to
merging.
We
had
three
or
four
different
people
all
come
in
and
say
that
the
new
approach
was
working
great,
so
still
undetermined.
You
know
if
we
will
pull
that
into
117
2
or
not.
A
It
might
be
good
for
us
if
we
do
decide
to
put
into
117
2
to
get
that
out
prior
to
being
forced
into
another
security
release.
When
drupal
makes
security
updates,
it
might
not
be
a
good
move
of
us
to
put
a
potentially
risky
update
into
also
a
security
update,
because
that
forces
people
to
upgrade-
and
if
things
go
wrong,
then
they
don't
have
many
options
to
both
be
secure
and
have
their
site
still
work
anyway.
Just
thinking
rambling
a
little
bit
next
up
is
webp
support.
A
Webp
is
a
new
image
format
that
replaces
jpegs.
The
issue
is
45.09
indigo
zella
is
the
advocate
for
it
that
pull
request
is
out.
There
has
tests
it's
currently
in
a
state
of
needs
review.
A
I
was
looking
into
web
p's
recently
just
non-sequitur
web
p's
are
cool
they're
they're
like
jpegs,
but
they
support
transparency.
So
you
get
the
options
of
lossy
quality
images
like
photographs,
but
you
also
can
add
transparency
to
them
like
pings,
so
it's
kind
of
a
best
of
both
worlds.
A
Webp
also
supports
lossless
format,
unlike
jpeg,
so
you
can
have
a
ping-like
image,
a
lossless
one
or
you
can
have
a
jpeg-like
image
that
is
like
slightly
compromising
file
size
for
image
quality,
but
also
supports
transparency,
very
cool.
A
A
B
Yeah,
so
he
just
popped
in
a
few
minutes
ago
in
our
chat
requesting
some
attention,
because
he
has
two
specific
things
that
he
needs
feedback
for.
So
it's
the
last
comment
in
that
issue
and
he
points
to
specific
comments.
One
is.
B
B
A
All
right,
that's
fine,
we
can
move
on
next
up
is
adding
a
setting
to
menu
blocks
for
changing
the
break
point
at
which
the
mobile
navigation
becomes
activated.
The
issue
is
46.63.
Bw
panda
is
the
advocate
for
this.
A
Thanks
to
indiegogo
and
herbduel
for
reviewing
there's
some
commentary
in
there
we
talked
extensively
about
overwriting,
css
and
changing
css
safely
in
the
ux
meeting
prior
to
this.
So
if
you're
interested
in
that
discussion,
there's
an
extensive
video
on
on
us
debating
merits
of
various
approaches.
A
A
However,
the
authors
of
the
issue
think
that
the
changes
are
made
in
a
backwards
compatible
manner
that
doesn't
affect
existing
sites
and.
C
A
Does
that
make
it
so
that
this
change
can
be
implemented
without
also
addressing
the
4167
issue
of
changing
css
and
core
safely?
As
a
general
problem,
I
think
that
discussion
is
kind
of
still
ongoing
inside
of
that
issue.
I'm
not
not
sure
if
weighing
in
anything
here
is
is
valuable
but
tim.
Yes,.
D
Well,
I
have
a
question
that
you
might
be
able
the
broader
context,
question
that
might
be
helpful,
which
is
my
understanding
is
that
what
this
issue
is
doing,
which
would
differ
from
the
other
case,
is
that
it's
all
it's
basically
uploading
or
overriding
css.
Only
if
you
turn
this
feature
on,
so
it
would
only
affect
it.
If
you
change
that-
and
my
question
is,
do
we
do
that
in
other
places?
Is
that
something
is
that
already
a
practice?
D
A
D
A
Because
this
kind
of
thing
that
an
option
turns
on
additional
css
or
applies
additional
css,
isn't
that
common.
But
I
think
that
the
module
has
dedicated
pages
that
need
specific
css
or,
like
adds
a
new
field
element.
And,
of
course,
the
field
element
requires
css
to
output.
Its.
C
A
So
the
issue
of
that
one
is
that
currently
I
don't
think
that
actually
needs
work.
I
think
that
hang
on
this,
my
agenda
might
not
be
fully
updated.
It
says
it
needs
more
feedback
currently,
but
I
think
that
it
actually
has
a
pull
request
that
is
working.
D
A
The
ambiguous
policy,
which
is
also
the
problem
yeah
okay,
next
up
tim,
is
the
issue
that
you're
the
advocate
for
excuse
me:
changing
the
name
of
the
full
html
text,
format
to
raw
html
44.99.
A
B
So
it's
it's!
Finally,
okay
bc,
the
the
the
thing
that
was
pending
for
a
week
or
two
was
to
rename
a
final
thing,
just
instead
of
login
name
same
username,
so
that
we're
consistent
across
the
ui
and
it's
finally
over
as
soon
as
it's
committed.
I
can
advocate
for
publishing,
excited.
A
Yay
time
to
do
almost
time
to
declare
victory
right,
it's
rtbc
everybody's
happy
with
it.
We
did.
A
A
Okay,
that's
great
yeah
that
one's
rtbc.
We
could
move
that
in
at
any
time.
Now
I
think,
being
rtbc.
Does
that
let
you
advocate.
A
Finally,
finally,
lastly,
the
current
issues
that
we
have
in
the
118
milestone
is
a
backdrop
port
of
advanced
caching,
adding
tags
and
more
granular
control
over
the
max
age.
Header
issue
is
4127..
A
Joseph
is
the
advocate
for
this
one
and
is
the
one
pushing
it
forward.
He
seems
he's,
there's
no
update
for
this
week,
but
last
we've
heard
he's
been
running
into
some
problems,
but
he's
also
making
some
progress
so
he's
attempting
to
work
from
the
drupal
7
port
of
triple
eight's
cache
tags
and
then
work
from
there.
A
B
I'm
excited
I'm
excited
about
this
feature
if
it
gets
in
118
and
I
don't
have
immediate
use
for
it,
but
the
thing
is,
and
we
have
many
issues
that
are
tagged
as
d8
sort
of
like
parity
feature
parity,
but
this
one
is
one
that
keeps
being
brought
up
very
often
as
a
selling
point.
When
people
are
choosing
v8
over
backdrop,
so
yeah,
it
would
be
great
to
have
that
in
core
and
say
you
know.
One
less
reason
to
have
people
have
doubts,
they're,
really
cool.
A
Okay
and
that's
it
for
the
118
issues,
we
also
have
our
initiatives
led
by
tim
and
luke.
Currently,
luke
is
not
present
in
this
meeting,
so
we'll
just
get
an
update
from
tim
if
any
on
the
telemetry
telemetry
initiative.
D
Trying
to
remember
whether
I'm
muted
or
unmuted,
the
the
not
much
of
an
update,
although
small
progress,
we,
I
think
primarily
the
state
we're
at
with
the
telemetry
issue,
is
testing
and
if
anyone
else
is
able
to
help
with
testing
that
and
providing
some
feedback
on
what
nate
has
already
done.
That
would
be
really
helpful.
I
personally
am
trying
to
get
there.
It
does
require.
Unfortunately,
we
can't
just
do
it
in
sandboxes,
you'll
have
to
spin
up
a
local
version
of
backdrop,
cms.org
right.
A
No,
not
a
local
version
of
backdrop.
Cms.Org
you
can
the
testing
instructions
that
I
have.
You
can
set
up
one
site
that
actually
reports
to
itself,
which
is
a
little
bit
silly,
but
you
also
could
set
up
two
sites
if
you
so
wanted,
but
for
the
sake
of
simplicity,
a
site
that
reports
to
itself
is
probably
the
easiest
thing,
because
you
only
need
one
backdrop:
install
okay,.
D
I
was
under
the
impression
it
would
have
to
be
a
copy
of
bankruptcms.org,
a
dub
version,
and
I
needed
to
do
that
for
other
reasons,
anyways.
So
that's
where
I
spent
my
time
last
weekend
getting
backdrop
cms.org
working
locally
and
trying
to
integrate
it
with
civic
crm
thinking.
It
would
also
help
me
with
this
issue,
but
maybe
it
doesn't
my
my
goal
is
to
do
some
testing
on
that,
and
I
should
be
able
to
do
that
this
weekend.
A
Yeah,
if
we
wanted
to
ease
the
testing
for
some
people,
we
could
tentatively
install
the
project
equivalent
the
project,
telemetry
module
onto
backdrop
backdropcms.org,
it's
fairly
simple.
A
If
we
can
get
approval
on
that,
we
could
tentatively
put
it
on
backdrop
cms.org
and
have
it
start
collecting
data,
and
then
you
would
only
have
to
test
the
the
client
portion
of
things.
However,
in
order
to
see
the
results,
you'd
have
to
be
an
administrator
on
backdrop
cms.org,
and
so
that
might
be
a
better
way
for
us
to
proceed
for
those
interested,
because
I
think
the
people
that
are
active
like
such
as
yourself
are
also
administrators
on
backdrop
cms.org,
but
yeah.
A
My
initial
approach
was
that
you
know
this
should
be
available
to
anyone
who's
interested,
not
only
those
who
are
administrators,
but
perhaps
going
that
route.
Just
because
it's
purely
less
technical
and
if
someone
was
interested
in
testing,
then
we
could
simply,
you
know,
grant
them
permissions
to
use
the
new
capabilities.
D
So
the
other
thing
sorry
go
ahead.
The
other
thing
that
I'm
trying
to
do
is
get
backdrop
cms.org
working
with
civic
crm,
and
I
was
hoping
to
do
that
locally,
but
locally,
I've
been
using
lando
and
I'm
having
problems
with
two
data.
Well,
I'm
having
problems
with
doing
lando
within
cbcrm
locally,
whereas
I
was
able
to
easily
connect
lando
to
or
easily
connect
civvy
crm
to
a
backdrop
on
a
server
well,
actually
I
think
I
was
able
to
do
that
locally
as
well
anyways.
D
The
point
I'm
getting
into
is,
if
I
put
up
a,
is
there
any
reason
any
reasons
I
can't
or
shouldn't
put
up
a
backdrop
cms.org
just
sandbox
site
on
my
dev
server,
if
I
like
ht
password,
so
nobody
can
just
stumble
into
it
and
experiment
with
it,
and
if
I
did
that,
then
could
we
also
use
that
for
testing.
A
C
A
That
and
that
would
really
be
preferable,
so
you
setting
something
like
that
up
would
be
great
sure
the
backdrop
cms
locals
that
you
pulled
down.
They
are
sanitized
thanks
to
the
work
that
justin
has
done,
so
they
already
shouldn't
be
any
concerns
about
leaking
hashed
passwords,
for
example,
email
addresses
because
those
things
are
cleaned
up.
B
A
Interesting,
it
would
be
a
bit
hacky,
because
you'd
have
to
open
pull
requests
that
didn't
actually
change.
A
D
Non-Ideal,
okay,
well,
I'm
gonna!
I
might
go
ahead
and
and
spin
up
my
own
dev
version
of
backdrop
cms.org
on
a
server
that
I
could
then
give
other
people
access
to
for
testing
purposes.
If
that's
helpful,
we
might-
I
don't
know
if
there's
any.
If
we
is
there
a
reason,
we
don't
have
sort
of
a
dev
version
of
backdrop,
cms.org
already
on
a
server.
B
You
would
need
to
be
cautious
with
the
who
you
give
access
to,
because
this
or
who
you
give
have
been
access
to
right
because
yeah,
because
they
would
be
able
to
see
all
their
settings
that
we
have
configuration
things
that
we
have.
D
B
A
Yeah,
which,
right
now,
the
only
way
to
get
access
to
those
things
is
from
the
live
server.
You
can
still
set
up
a
sandbox
that
doesn't
have
like
api
keys
to
tugboat,
for
example,
or
api
keys
to
zen
or
api
keys
to
our
mail
provider.
All
of
those
things
are,
the
keys
for
all
of
them
are
stored
only
on
backdrop
cms.org
on
the
actual
server,
so
your
local
just
won't
have
those
capabilities.
D
On
a
related
topic,
like
nate's
opinion
on
this
gregory,
you
weighed
in
it's
what
you
were
just
saying
it
looked
bw
panda
was
suggesting
that
we
have
that
he
update
the
lando
script
for
for
setting
up
a
local
version
of
backdrop
cms,
so
that
it
automatically
pulled
down
the
sanitized
database,
and
I
think
gregory
was
saying
that
that's
a
security
issue,
because
if
anybody
off
the
internet
were
able
to
pull
down
this
lando
script
and
set
up
a
local
version
of
backdrop
cms.org,
even
if
the
data
is
sanitized,
they
would
be
getting
more
access
than
we'd
want
them
to
have.
A
Yeah,
I'd
probably
concur
with
that.
It
might
be
nice
if
the
atlantoscript
could
be
updated
in
a
way
that
says
you
know
just
says:
if
you
want
to
download
the
database
then
run
this
command,
but
it
would
also
prompt
you
for
a
password
or
you'd
have
to
enter
one.
Then
that
would
be.
A
We
could
still
facilitate
it
being
easier
and
automatic
through
scripting,
and
that
would
be
great,
but
we
probably
can't
just
make
it
automatic
with
no
no
password
whatsoever,
even
though
it's
sanitized
there's
just
sensitive
things
that
could
be
on
there.
Unpublished
security
releases
that
sort
of
thing
sure.
A
Okay,
let's
see
that's
it,
for
initiative
updates.
B
Before
we
move
on,
I
just
wanted
to
point
out
that
there's
like
nine
issues
in
the
rtbc
queue
and
two
of
them
are
feature
requests,
but
the
rest
of
them
are
bug
fixes
just
wanted
to
say:
do
we
have
any
rough
idea
for
a
new
bad
mix
release?
I
know.
There's
no
rust,
there's
no
critical
issue
that
we
have
at
the
moment,
but
were
we
planning
for
any.
A
I
do
not
have
any
plans
for
it,
but,
like
I
said,
if
we
want
to
get
that
mysql8
fix
out,
it
would
be
better
to
do
it
in
a
release
that
wasn't
a
security
release
and
so
looks
like
117.2
has
16
closed
issues
already,
so
that
is
kind
of
a
substantial
number.
If
you
add
that
on
top
of
the.
A
B
Rtbc,
I
see,
nine
are
tbc,
two
of
them
are
for
a
feature
request,
so
they
go
in
118.
So
seven
should
be
four
one.
Seventeen
two.
A
Yep,
I
I
would
be
in
favor
of
that,
like
let's
go
ahead
and
get
a
minor
release
out
once
we
have
these
things
all
collected
yeah.
If,
if
you
want
to
facilitate
that
gregory,
we
could
go
ahead
and
make
a
release
issue
for
it
for
117
too,
and
then
possibly
give
it
a
date.
A
I
would
be
comfortable
with
as
soon
as
this
weekend.
If
that
would
work.
D
A
Okay,
do
you
want
to
go
ahead
and
say
sunday,
sunday,
november,
8th.
A
Okay,
well
generally,
we'll
we'll
plan
on
that
we
can
work
out.
The
details
of
scheduling,
generally
kind
of
afternoonish
seems
to
work
well
for
me,.
D
B
Issue,
what
was
the
number
four
triple
six,
so
we
have
the
rule
about
not
exiting
80
character
limits
and
we
have
some
exceptions,
and
all
that
is
clear.
What
is
not
clear
is
if
the
80
character
limit
is
try
to
fit
as
many
as
until
80
or
anyone
can
wrap
at
any
time
below
80
characters.
B
So
some
sections
have
of
inline
comments,
have
less
than
80
characters,
but
they
wrap
much
sooner
than
80
characters,
whereas
the
next
line
could
fit
in
the
previous
line.
So
I
don't
know
what
some
explanations
were,
that
the
the
character
limit
was
set
to
70
or
60
before
and
that's
remnant
of
the
past.
Some
other
people
feel
that
the
creators
of
those
comments
felt
that
it
was
more
readable,
so
they've
done
it
as
such.
B
A
C
B
That's
what
I'm
asking
yeah,
because
the
the
the
the
d
dot
org,
the
respective
d
dot
coding
standards,
which
we
actually
sort
of
like
we
have
a
copy
of-
we
didn't
change
to
that.
They
don't
clarify
that
and
it's
kind
of
vague
there's
what
you
call
it
subject
to
interpretation.
B
A
Yeah
interesting
I'll
I'll
put
my
voice
in
that.
I
don't
think
wrapping
early
is
a
big
deal
if
you
think
it
makes
it
more
readable
but
yeah.
I
think
that
would
be
great
to
clarify
that
in
in
our
coding
standards
and
say
you
know
if,
for
purposes
of
readability
shorter
line,
just
line
breakpoint
is
more
readable
than
that
could
be
acceptable.
That
sort
of
thing.
D
A
D
E
D
We
were
talking
earlier
about
the
pr
sandboxes.
Did
you
have
any
questions
for
peter
about
that,
or
did
we
solve
all
that?
I
was
oh.
Okay,
no.
E
Many
people
are
working
now,
yep
good.
I
got
one
question
for
nate
about
that
sure,
so
people
have
been
saying
that
with
the
new
tugboat
ones
because
of
the
limited
space
we
have
that
they
should
be
more
selective
as
to
which
ones
are
made
into
like
spun
up
sort
of
thing.
But
how
do
we
determine
that?
Because,
as
far
as
I
know,
it's
just
automatic
and
every
call
request
is
going
to
get
one
from
now
on.
C
A
Automatically
expire
them
so
give
them
like
six
months
or
something
like
that
until
six
months,
if
that
becomes
a
problem,
that
we
have
too
many
sandboxes,
but
right
now
we
have
500
pull
requests
which
would
exceed
our
limit.
But
some
of
those
are
two
three
years
old,
and
so
I
think,
if
we
put
a
limit
on
them
of
six
months,
they
automatically
tear
down
after
that
time
and
then,
if
we
need
a
new
one,
the
people
can
close
and
reopen
the
pull
request
and
that'll
make
a
new
sandbox.
It
lasts
for
another
six
months.
C
A
It
actually
becomes
like
problematic
that
we
need
to
increase
the
size
of
the
plan
on
the
tugboat
side.
A
Yet,
but
at
this
point
like
for
us
just
getting
started
and
we're
not
really
even
officially
discontinuing
cnci
like
entirely
so
I
think
I
think
at
this
point
we
don't
need
to
rush
asking
tug
what
for
a
size
larger
than
we
really
need.
Yeah.
B
Even
if
it
comes
to
that,
I
think
we
already
have
a
section
where
we
sort
of
like
provide
kudos
for
agencies.
Sorry
companies
or
people
that
provide
us
services
and
the
the
dribble
association
started.
Putting
out
some
some
small
ads
indeed.
provide
revenue.
We
could
do
the
same
for
tagbot
because
they
are
providing
the
the
sandboxes
for
the
demos
and
now
for
our
cool
requests.
So
maybe
we
could
make
an
exception
and
have
a
a
small
ad
on
our
homepage.
B
A
Well,
I
don't
even
think
that
there's
necessarily.
A
I
don't
know,
I
don't
even
think
that
it's
it's
a
matter
of
us
providing
more
changes
right
now.
I
I
think
that
it's
really
perhaps
us
being
courteous
and
not
asking
for
more
than
we
need.
A
A
D
A
No,
I
I
don't
have
anything
else.
I
don't
think
justin
anything
from
you,
okay!
Well,
thanks
for
jumping
in
and
hanging
out
with
us
peter
thanks
for
being
here
just
for
a
couple
of
minutes.
A
Unless
there's
anything
else,
I
think
we
can
end
okay.
Well,
thanks
everybody
out
there
we're
gonna,
shut.