►
From YouTube: Backdrop Weekly - Aug 13th 2020
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
Hi,
I'm
greg
I'm
joining
from
grace
just
to
catch
up
on
the
weekly
things
that
are
happening
with
core
and
helpless
message.
C
Sure
my
name
is
tim,
st
paul
tim
in
many
places.
I
am
here
in
minnesota,
dearwood
minnesota
and
I
have
been
indulging
myself
in
the
issue-
queue
the
last
two
weeks,
so
lots
of
things
that
I'm
interested
in,
but
that's
all.
A
D
Hello,
my
name
is
mohammed
and
I
am
from
bangladesh
and
bedrock
going
good
and
I'm
working
with
volit
thanks.
E
F
Yeah,
I
guess
my
name
is
justin,
I'm
in
denver
colorado
and
I
just
help
out
where
I
can,
with
infrastructure
or
whatever.
G
A
G
A
E
I
A
Great
I'm
john
langton
from
california,
I'm
very
excited
about
getting
to
all
of
the
stuff
in
the
agenda
to
start
off.
There's
new
contributed
module
this
week,
the
anti-scan
module
which
I'm
excited
about,
because
it
will
prevent
known
thoughts
from
causing
problems
on
your
site.
So
I
think
it's
like
scrape
scraper,
so
try
and
visit
like
wp
admin,
pages
and
stuff
like
that,
will
get
blocked,
which
is
great,
and
we
have
a
bunch
of
stuff
in
the
general
discussion
section,
so
we're
going
to
skip
everything
else,
except
for
project
updates.
E
Okay,
so
we
have
a
number
of
issues
that
haven't
seen
a
lot
of
progress
and
I'm
not
going
to
go
over
them
again,
because
I
haven't
seen
any
updates
this
past
week,
but
three
issues
that
we
have
that
are
still
in
a
state
that
they
all
need.
E
Testing,
include
update.php,
throwing
errors
about
installation
and
telling
you
to
delete
your
config
directories
issued
38.46
that
has
not
progressed
but
still
needs
manual,
testing
the
site
getting
stuck
in
maintenance
mode
when
updating
modules,
issue,
3956
same
story
there
and
reviewing
the
views
pager
by
date,
functionality
that
is
useful
for
calendaring
issue.
2766
also
still
just
needs
some
review,
so
those
three
issues
same
status
there.
E
This
next
issue,
visual
regression
in
the
text-
format
order
form
in
the
text
format
order
on
overview
form
this
issue
4407.
This
was
a
regression
in
116,
that's
reordering!
The
text
formats
didn't
appear
to
make
any
change
didn't
appear
to
save
when
you
changed
the
order
that
one
got
merged.
Finally,
so
I'm
really
happy
to
see
that,
let's
see,
I
believe
that
indigozala.
E
Thank
you
for
doing
the
review
on
that
bw
panda.
Thank
you
for
filing
the
issue
this
next
one
php
cs
automated
code
checks.
There's
been
some
progress
on
that
I
know.
Jen
has
been
it's
been
working
on
that
today
joseph
has
been
working
on
it
for
the
past
week,
at
least
I'm
not
the
best
person
to
give
the
update
here.
A
Sure
so
the
big
picture
goal
here
is
that
we
want
to
make
it
so
that
anytime,
anyone
submits
a
pull
request
against
backdrop
core
or
any
contrib
project
that
they
choose
to
add
it
to
will
get
automatic
syntax
checking
so
that
the
pull
request
will
fail
with
useful
messages
to
the
user.
If
there's
something
that
they
need
to
fix,
that
isn't
going
to
require
a
human
reviewer
to
catch
and
return,
there's
a
module
for
drupal
called
coder
that
includes
syntax
checking.
We
have
a
version
of
that
for
backdrop
and
backdrop.
A
It's
called
code
or
review,
but
the
syntax
checks
use
a
tool
called
php
cs
or
php
code
snipper,
that
is
very
out
of
date
and
the
backdrop
version,
and
there
are.
C
A
Drupal
issues
to
bring
it
up
to
various
different
versions
for
drupal
7
and
drupal
8,
and
so
we
just
need
to
figure
out
how
to
get
the
backdrop
version
up
to
recent
versions,
and
then
we
can
write
a
patch
against
core
that'll
set
up
automatic
code
checking
so
there's
kind
of
two
pieces
involved.
One
is
getting
our
quota
review,
module,
updated
and
the
other
one
is
getting
that
applied
to
backdrop
core
to
apply
the
checks
and
joseph
has
done
a
bunch
of
work
this
week
on
getting
coder
review
updated.
A
So
I
don't
know
joseph
if
you
want
to
do
any
work
or
any
give
us
an
update
on
how
that's
going.
H
Yeah
so
well,
I
was
kind
of
just
updating
it.
I
started
working
on
this
back
in
march,
where
I've
updated
all
of
our
our
sniff
files
so
that
they
work
with
the
3.x
version
of
php
code
sever
and
I've
created
a
pull
request
against
a
coder
review,
and
then
we've
been
trying
to
test
getting
that
to,
I
don't
know,
run
against
a
pull
request
on
one
of
jen's
contrib
projects
and
it
seems
to
work
so
far.
A
So
I
don't
know
how
to
run
it
locally,
but
it
failed
in
actions,
but
it
looks
like
it
ran.
Okay
like
it,
but
it
didn't
work
like
so
I
could
told
it
to
run
and
it
ran.
I
shouldn't
actually
do
it
supposed
to.
H
A
A
I
have
no
idea
okay.
Well
so
so
I
just
took
the
pull
request
from
14,
but
I
don't
know:
what's
happened
between
when
photo
review
was
released
and
the
latest
head-
and
I
imagine,
you're
focused
against
your
latest
head
so
I'll
see
if
I
can
get
github
actions
to
full
head
instead
of
the
latest
release.
H
You
can
you
can
directly
pull
the
branch
from
my
repo.
A
E
Seems
like
a
reasonable
thing
to
do.
There
is,
you
know,
merge
the
pull
request
so
that
you
don't
have
to
apply
the
patch.
But
if
we're
updating
the
api
version
of
the
underlying
code,
sniffer
library,
we
should
probably
make
a
new
branch
like
a
2.x
branch
of
code,
coder
review
and
say,
like
the
2.x
branch,
uses
the
newer
code
sniffer
and
then
leave
the
current
one,
not
x
branch
as
it
is.
E
Okay,
let's
see
I
lost
my
notes
here
we
go
all
right,
okay,
so
we
also
have
this
kind
of
low
hanging
fruit
section
of
the
current
release,
things
that
are
potentially
pretty
easy.
First
one
we
have
is
setting
a
reasonable
max
input,
vars
setting
issue
38
to
24..
E
I
generate
a
documentation
page
for
that.
Thank
you,
jen.
It
looks
really
good.
The
status
that
I'm
having
the
agenda
here
is
needs
work,
but
isn't
the
is
the
pull
request,
ready
to
go
or
is,
and
the
documentation
just
needs
work
or
does
the
pull
request
need
to
be
updated
for
the
new
page
that
was
just
created.
A
E
E
Let's
see
removing
the
block
title
for
the
search
box
issue
34.76,
I
don't
think
there's
been
progress
on
this
one.
It
just
needs
review.
That's
a
nice
fix,
it's
just
and
real
simple.
I
don't
think
there's
much
to
it.
E
Fixing
the
views
or
behavior
issue
34
a
similar
story
here.
This
is
another
one
that
needs
some
review.
Some
manual
testing
in
particular
this
next
one,
I'm
not
sure
if
this
one's
really
an
almost
done
or
an
easy
one,.
E
High
importance
bug
fixes
that
are
not
necessarily
very
easy.
Yeah,
it's
not
easy
or
close
yeah,
so
ck
editor
is
not
saving
in
source
mode.
This
issue
1259
that
if
you're
editing
a
block,
a
custom
block
and
you
switch
ck
editor
to
source
mode
and
then
hit
save,
it
doesn't
actually
save
the
changes
that
have
been
made
in
ck
editor,
so
status.
Is
that
still
needs
pull
requests?
C
E
A
There
hasn't
been
any
change
since
last
week.
The
blacklist
whitelist
issues,
there's
some
questions
on
the
pull
request
for
a
core
committer
or
someone
who
might
have
some
recommendations
on
how
to
handle
some
of
the
issues
like
on
setting
a
session
variable
and
then
the
database
master
slave
issue
still
has
some
problems
with
how
the
tests
are
running.
I
think
I'm
hooking
everything
up,
there's
a
lot
of
test
failures
and
I
think
the
problems
are
actually
with
the
how
the
new
databases
stuff
is
going
so
that
definitely
needs
work.
A
B
Those
views
have
quite
a
few
changes,
so
we
don't
have
to
get
everything
right
from
the
get
go
like
we
can
iterate.
So
if
there's
easy
ones
that
we
can
get
read
from
the
code
base,
I
mean
instances
just
do
it
and
then
do
follow-up
requests.
That's
my
thing
because
there's
gonna
be
certain
things
that
are
reason
to
fix
like
comments
or
just
text
that
is
output
in
messages
and
then
it's
gonna
be
some
some
variables
changing,
and
these
can
be
followed.
E
We
also
have
eight
rtbc
issues
that
are
in
the
116
3q.
That's
super
duper
awesome
I'll,
be
going
through
those.
When
I
get
a
chance
and
yeah
it's
great
to
see
all
the
activities
that's
been
happening
as
we
were
bantering
before
we
started
the
recording.
I
also
give
a
shout
out
to
peter
bw
panda,
who
has
been
doing
an
awesome
job,
not
only
reviewing
pull
requests
as
they've
been
coming
in,
but
we've
also
been
getting
some
merging
happening
both
in
the
117
q
and
the
116
3
q.
So
that's
that's.
Super
duper.
E
E
Let's
see
next
up
on
the
agenda
is
the
117
item
lists
the
features
that
we're
planning
on
getting
into
the
next
minor
version
of
backdrop,
which
will
be
coming
out
september,
15th,
2020.,
sort
of
that
one
of
the
banner
features
here
I
think
that
will
be
in
117-
is
doc
wilmont's
work
on
adding
support
for
custom
contexts
to
layouts.
E
This
is
on
my
plate
to
take
a
look
at
it.
I
I
really
have
been
trying
to
make
time
to
take
a
look
at
this,
and
I
think
that
I'm
the
right
person
to
do
that.
So
that's
on
my
plate
to
take
an
eye
to
take
a
look
through
it
and
read
it
and
check
it
out
tim.
Did
you
have
something
that
you
weren't
going
to
add?
Okay,
let's
see
next
up,
let's
see
the
administration
theme
for
the
login
form
issue
4410.
E
That
issue
is
blocked,
probably
not
going
to
happen
in
117
because
of
the
complexities
of
showing
administrative,
only
pages
to
anonymous
users
or
administrative,
only
theming
and
block
positioning,
most
importantly,
to
anonymous
users.
We
may
still
do
some
other
peripheral
actions
like
splitting
out
the
view
administration
theme
permission
into
contrib.
That
will
make
that
issue
easier
in
the
future.
That's
issue
44.87
current
stats,
so
that
one
is
that
needs
some
work.
E
No
okay,
it
looks
like
indigozella
was
the
last
person
to
take
a
look
at
it
and
they
just
simply
said
that
that
the
tests
are
failing.
So
it's
too
early
to
look
at
because
the
tests
aren't
even
passing
yet.
Okay.
E
Let's
see
this
one,
I
haven't
seen
before
using
htaccess
for
securing
the
config
directories.
Issue
number.
H
E
And
aldi,
but
a
goodie,
an
update
from
bw
panda
who's,
not
actually
in
the
meeting,
but
I'll
read
the
issue
here.
Oh
bwk
is
now
the
advocate
for
this
issue.
B
Yeah
he's
actually
working
in
the
israeli
chat.
He
just
both
the
dimensions.
E
Yeah,
this
is
a
great
issue.
It's
been
a
long-standing
thing.
Ever
since
we've
had
a
file
based
config
system,
he
opened
this
issue
in
february
of
2015,
which
seems
hard
to
believe
that
we
have
five-year-old
issues,
but
there
we
go
so.
This
issue
is
that
the
config
directories
right
now
are
hidden
essentially
by
obscurity.
E
They
get
random
names
attached
to
them
and
that
you
can't
access
the
config
because
they
have
a
random
name,
and
we
also
suggest,
in
the
installation,
instructions
advanced
installation
instructions
that
you
move
the
config
directory
outside
of
your
web
route,
so
that
they're
not
accessible
over
the
web
anyway.
Even
if
you
did
know
the
path-
and
this
is
a
further
security
hardening-
that
would
make
it
so
that,
if
you're
running
apache
htaccess
would
protect
access
to
that
directory,
it's
very
similar
to
what
we
do
for
like
private
files.
E
We
encourage
you
to
put
private
files
outside
of
the
web
root,
but
if
you
have
to
leave
it
inside
of
the
web
root
or
or
you
prefer
to
keep
it
in
there
for
some
reason,
then
hd
access
protects
the
private
files
directory,
and
this
is
the
same
thing
essentially
for
the
config
directory
current
status.
If
it
looks
like
it
needs
testing
a
code
review,
which
is
great,
that
means
it
has
a
pull
request
already.
D
I
am
thinking
about
file
permission
444
or
like
that
drupal
doing
for
configure
444
and
5g.
E
Yeah
that
that
would
prevent.
Oh,
I
see
right.
E
A
Doesn't
work
in
like
the
installer
would
need
to
write
that
directory.
So
that
would
also
be
like
a
very
like
manual
issue,
or
I
think,
if
we
can
like
automate
it,
that
would
be
better.
D
For
people
who
don't
because,
because
I
am
thinking
anyone
can
get
access
to
htxs,
so
he
can
remove
the
htxs,
so
he
can
get
configured
file
permission
or
something.
D
E
Yeah,
I
agree
that,
having
having
multiple
approaches
to
it
are
probably
best
rather
than
doing
one
versus
the
other,
there
are
some
situations
where
changing
the
file
system.
Permissions
isn't
feasible
and
there's
some
situations
where
apache
isn't
the
web
server
and
so
having
alternatives
that
don't
use.
Hd
access
is
also
a
good
thing.
E
Okay,
that's
great!
I'm
not
familiar
with
this
next
issue.
Add
url,
alias
as
a
machine
name
like
field
to
node
titles.
It's
issued
33
93,
pull.
G
B
This
is
another
issue
that
peter
has
studied
sort
of
like
as
an
idea
noticed
some
similarities
between
the
way
that
the
machine
names
work
like
how,
as
you
type
a
name
for
a
certain
thing,
it
automatically
generates
the
machine
name
and
it
has
a
link
to
allow
you
to
edit
the
machine
name,
and
he
thought
that
maybe
that
reusing
that
ui
pattern
for
your
aliases
would
also
be
an
improvement,
and
it's
something
that
wordpress
has
been
doing
in
its
4.x
versions.
B
C
I
A
E
Into
a
big
discussion
here
that
there's
on
a
lot
of
my
client
sites
that
we
have
a
feature
or
we
try
to
create
a
feature
where
a
user
can
modify
only
part
of
the
url
alias,
but
not
all
of
it.
So
we
like
to
enforce
things
like
the
menu
structure.
Part
of
it
is
locked,
but
then
the
title
part
they
can
change,
and
so
this
kind
of
fits
into
that
sort
of
thing
where
it's
making
the
title
first
exposed.
D
D
E
C
B
B
B
But
the
idea
is
that,
for
example,
how
machine
machine
names
work
is
as
you
type
then
they
start
showing
up,
whereas
with
your
aliases,
you
might
already
have
that
showing
and
instead
of
having
it
when
you
type
the
first
letter.
That's
what
I'm
saying
because
then
it
sort
of
like
appears
out
of
nothing
out
of
nowhere.
B
It
doesn't
make
as
anyways
one
of
the
the
things
that
peter
wanted
to
ask.
Was
he
reused
the
machine
name,
a
form
api
element
to
do
that,
so
what
hijacked
it?
And
he
said
that,
maybe
we
will
need
to
have
a
dedicated
form
element
which
would
be
a
similar
sort
of
a
clone
of
the
machine
name
but
sort
of
like
tweaked
so
that
it
fits
for
that
purpose
for
the
url
okay.
So
yes,
also.
B
The
counter
argument
is
from
doc
willmott,
which
says
that
he
thinks
that
this
was
not
as
a
feature
that
should
be
right
in
the
face
of
content.
Editors.
D
D
E
Well,
look
this!
This
has
some
challenges
still
that
I
mean
they
clearly
need
to
be
worked
out
like
if
there's
things
in
your
url,
alias
besides
the
node
title,
giving
the
user
an
accurate
preview
becomes
a
lot
more
challenging
like
if
you
start,
including
the
date
or
menu
item
parents
or
the
author's
name,
because,
as
you're
editing,
the
note
form
all
of
those
values
can
change
and
before
you've
saved
the
node.
None
of
those
values
exist.
E
E
So
I'm
yeah
I'm
not
quite
sure
how
big
of
a
scope
this
problem
is
trying
to
solve.
If
we're
only
demonstrating
the
node
title,
then
we
need
to
reconcile
that
with
the
rest
of
the
url
or,
if
we're
trying
to
not
give
an
accurate
demonstration
of
the
entire
url,
we
need
to
figure
out
a
way
to
represent
that
as
well
or
maybe
we
continue
showing
the
placeholders
and
only
swap
out
the
node
title
token.
E
You
know
I
don't
I
don't
know
quite
how
that
would
work,
but
yeah
lots
of
things
here.
C
D
I
am
thinking
to
keep
on
keep
on
note
id
and
not
idea
will
be
there,
no
need
to
change
to
to
paste
title
or
something
if
need
they
can
use
seo
plugin
or
something
or
they
can
type
their
permalink
or
page
link,
because
otherwise
it's
too
much
task
about
machine
language
to
paste
title
or
something
because
that's
I
am
thinking.
J
Okay,
yeah
yeah.
I
think
in
order
to
really-
and
I'm
agree
with
the
niche.
E
Yeah,
I
think,
in
order
to
really
move
this
issue
forward,
there's
so
many
different
ways
that
we
could
handle
it
and
there's
lots
of
ways
that
we
can
describe
it
working
that
might
not
be
technically
feasible.
You
know
like
that,
might
be
actually
impossible.
I
I
think
that
this
needs
more
experimentation.
E
A
A
Is
with
that
field?
That's
blank
until
it
exists
and
then
once
it's
exist,
we
put
in
the
alias
that
was
generated
from
the
tokens
and
we
could
do
the
same
thing.
Just
take
that
field
and
move
it
to
the
top
of
the
page
and
it'll
be
empty
until
you
save
the
node
and
then
once
the
node
is
saved
and
there's
a
database
record,
we
pull
the
record
from
the
database
and
display
it
there.
So
it
might
not
show
what
will
happen
when
you
hit
save
on
the
form.
A
E
G
I
think-
and
they
know
it
very
well,
but
for
content
editors,
it's
not
so
important,
it's
kind
of
clutters
the
note
form
in
my
opinion,
so
I'm
not
clear.
What's
about
the
motivation,
if
it's
just
people
know
it
from
wordpress-
and
I
think
wordpress
doesn't
do
a
very
good
job
in
this
place.
So
it
doesn't
look
very
good.
In
my
opinion,
even
in
wordpress,
so
not
all
from
wordpress
is
good
yeah.
I
agree.
E
D
E
E
E
So,
as
I
mentioned
earlier,
bw
panda
has
been
doing
some
merging
of
issues
and
has
two
issues
that
went
into
117.
Only
adding
a
node
id
to
the
node
block
class
is
issued
3730
a
real,
simple
change
that
just
adds
an
additional
default
class
when
you
place
a
block
that
contains
a
hard-coded
node.
E
So
that's
a
really
simple
change
and
then
another
issue
4425,
is
allowing
the
selection
of
an
existing
date
format
for
log
messages.
I
think
the
intention
here
is
that
we
allow
users
to
specify
a
format
for
log
messages
that
isn't
shown
anywhere
else.
Just
on
the
watchdog
page-
and
this
issue
makes
it
so
that
you
can
use
the
same
user
interface
for
specifying
a
date
format
to
make
it
so
that
you
have
one
place
where
you
enter
date
formats
into
the
two
places.
E
It
was
a
real
short-lived
issue,
though,
if
you
want
to
hop
in
and
provide
some
feedback
on
it.
I
think
that
would
be
fair
enough.
I
guess
it
wasn't
that
short-lived.
It
was
open
back
in
may.
E
But
yeah,
I'm
still
I'm
I'm
thrilled
to
have
things
happen.
Without
my
knowledge,
I
find
that
to
be
the
best
thing
ever
that
stuff
can
be
opened,
discussed,
reviewed
and
then
merged,
like
all,
amongst
you
know
the
the
community
members
that
we
have
like
it
without
my
participation.
I
know
I
do
most
of
the
code
reviewing
or
I
don't
do
most
of
the
backup
I
do
most
of
the
merging,
and
I
really
appreciate
having
other
core
committers
in
there
pushing
all
these
things
all
the
way
to
completion.
E
So
that's
it
for
117,
generally
speaking,
there's
kind
of
going
to
be
probably
a
light
release
in
117,
but
there's
so
many
bug
fixes
that
are
happening,
that
it's
just
really
wonderful
and
I
know
some
of
our
community
members
have
been
clamoring
for.
Can
we
just
slow
down
on
the
features
and
fix
some
of
the
issues
we
have,
whether
it
was
intentional
or
not
that's
the
way
117
is
shaping
up
so
so
I'm
still
really
happy
with
all
of
the
things
that
are
happening
throughout
all
of
the
development
in
backdrop
court.
E
A
Thanks.
Thank
you
thanks
all
right,
there's
a
section
here
for
initiative
updates,
but
neither
jeff
nor
luke
are
around
today
for
updates,
so
we'll
skip
over
those
and
move
on
to
general
discussion.
C
I'll
just
say
what
it
was:
the
there
was
a
there's,
a
long
issue
about
being
the
ability
to
copy
blocks
in
regions
and
core
and
bw
panda.
This
week
basically
said
it
looked
like
the
consensus
was
to
move
this
to
concrete
and
he
closed
the
issue,
and
I
was
afraid
that
that
issue
would
get
lost,
and
then
I
think
doc
wilmot
pointed
out
that
in
fact
a
contrib
module
had
already
been
made.
C
Based
on
that,
so
my
fear
was
that,
like
that
a
contrib
module
hadn't
been
made,
I
didn't
realize
that
and
that
just
closing
the
issue
would
lose
all
of
that
discussion.
I
do
think
that
there
is
an
interesting
discussion
about
like
if
we
do
decide
something
should
be
better
done
in
core.
What
is
the
best
way
to
preserve
and
carry
on
that
that
conversation,
but
it's
not
urgent
that
we
do
this
right
now.
A
Okay,
yeah,
I
agree,
I
think,
like
long
term,
we'll
probably
end
up
with
another
issue-
that's
like
at
that
module
to
core,
and
then
we
can
have
the
discussion
all
over
again,
but
it
would
be
great
to
not
for
someone
to
remember
that
we've
had
the
discussion
before
and
even
if
we
just
link
from
the
old
issue
to
the
new
one.
That
would
be
fine,
but
I
have
no
strong
feelings
about
keeping
the
old
issue
open
or
not.
If
that's
what
people
want
to
do
so,
the
discussion.
C
Sure
my
fear
in
this
case
was
that
this
was
a
feature
that
people
really
wanted.
The
decision
was
made
that
it
should
happen
in
contrib.
Well,
if
you
close
the
core
issue,
then
there's
no
discussion
anywhere
about
the
fact
that
we
want
to
have
this
issue.
In
this
case
it
turned
out
that
wasn't
the
case
because
the
module
had
already
been
made,
but
if
the
module
hadn't
been
made,
it's
like
it's
no
longer
on
our
to-do
list
anywhere,
and
that
was
my
fear.
C
I
wanted
it
even
if
it's
going
to
be
in
contrib,
it
should
be
on
a
contribute
to
do
list
right
so
like
maybe
the
appropriate
thing
is
to
open
a
contribution
saying
we
want.
You
know
we
want
this
issue
or
we
want
a
contrib
module
for
this.
That
doesn't
exist.
Yet
we
have
port
requests,
but
do
we
have
a
place
where
we
can
say
hey
this
feature.
A
F
A
Okay
next
issue
under
general
discussion.
This
is
something
that
came
up
in
our
last
meeting
we
were
talking
about.
There
are
a
couple
of
issues
related
to
design
and
usability
right
now
that
seem
to
be
very
contentious
and
I'm
not
sure
they're
exactly.
You
know,
I'm
not
sure
that
this
is
necessary,
but
I
wanted
to
talk
about
the
process
of
escalating
an
issue
to
the
pmc
for
review,
because
I've
been
feeling
a
little
bit
like.
A
There
isn't
a
very
clear
outline
for
anyone
who's,
not
a
pmc
member,
to
escalate
an
issue
to
the
pmc,
and
so
I
thought
it
might
be
useful
to
talk
about
what
that
process
might
look
like
and
if
there
could
be
some
very
clear
criteria
that
pmc
members
could
use
to
decide
when
an
issue
should
be
escalated,
because
if
there
was
something
that
said,
you
know
any
issue
with
more
than
100
comments
could
be
escalated
to
the
pmc.
Then,
as
a
pmc
member,
I
would
feel
much
better
about
going
in
and
being
like.
A
Hey
guys,
do
you
want
this
escalated
pmc,
rather
than
feeling
like
we're,
taking
the
conversation
out
of
the
hands
of
people
who
feel
really
passionate
about
those
particular
issues?
So
I
don't
know
how
we
should
handle
this,
but
like.
How
do
we
even
move
forward
on
deciding
when
to
decide?
Something
should
go
to
the
pmc?
A
Should
we
create
a
pmc
issue,
requesting
criteria
for
when
an
issue
should
be
escalated
to
the
pmc
and
have
them
decide
if
those
are
correct,
or
is
that
something
we
should
decide
as
a
community
without
the
pmc?
Or
should
we
decide
as
the
community
and
then
like
run
it
by
the
pmc?
A
Nobody
knows
anything
all
right:
here's
what
I'm
going
to
propose
I'm
going
to
create
a
pmc
issue
that
asks
for
some
clear
asks
for
us
to
establish
some
clear
criteria
about
when
it
will
be
okay
for
someone
to
come
into
an
issue
and
say
we're
escalating
this
to
the
pmc
and
one
of
those
criteria
is
going
to
be
we're
going
to
ask
people
on
the
issue
if
they
want
this
escalated
to
the
pmc,
and
that
way,
if
there's
a
place
where
I
feel
like,
we
need
to
interrupt
like
if
there
is
some
conflicts
that
needs
to
be
resolved
and
we
need
to
immediately
take
it
out
of
the
hands
of
the
people
who
are
in
the
conversation.
A
We
have
the
power
to
do
that,
but
in
most
cases
so
far
it
hasn't
been
a
conflict
so
much
as
just
a
bunch
of
people
with
different
opinions,
and
so
I
didn't
feel
good
about
like
seeing
the
pmc
is
definitely
doing
this.
I
would
want
it
to
be
like
up
to
those
people
like
hey.
Would
you
want
some
help
coming
to
a
consensus
or
a
decision
on
what
approach
we
should
take
for
a
particular
problem
and
I'll
open
that
in
the
pmcq
and
say
hey?
A
How
would
you
guys
feel
about
making
these
particular
criteria
when
we
can
escalate
an
issue?
A
I'd
like
to
you
know
we
have
a
process
in
place
in
theory
to
stop
that
from
happening.
I
would
like
there
to
be
more
concrete
examples
on
how
to
use
that
so,
okay
I'll
create
a
forum
issue
and
a
pmc
issue
to
try
and
figure
out
what
those
criteria
should
be,
and
once
we
have,
it
figured
out
we'll
put
something
public
somewhere.
A
So
everybody
knows
at
any
point:
these
are
the
things
you
can
do
to
get
something
escalated
like
you
can
either
specifically
request
it
or
a
pnc
member
can
come
and
ask
if
you
want
to
request
it,
and
you
can
say
yes
or
if
the
issue
reaches
100
comments,
which
is
my
threshold,
I'm
guessing
then,
okay.
This
is
too
much
we're
escalating
to
pmc.
A
C
B
Feel
I
feel
that
I
feel
that
going
doing
the
similar
similar
thing
to
the
thing
that
we're
doing
with
the
pmc,
but
instead
of
doing
it
at
the
top
initial
comment,
we
just
someone
from
the
pmc
can
go
and
say
or
anyone
from
the
community.
Would
you
like
this
to
be
escalated,
and
then
people
vote
with
thumbs
up
thumbs
down
and
then,
if
there's
too
many
thumbs
up,
then
we
know
that
it's
a
sign
that
we
should
take.
A
What
that
too,
many
can
be,
I
think,
over
time
like
right
now,
maybe
just
more
than
one
and
then
as
our
community
grows,
we
could
increase
that
to
be
like
has
to
be
at
least
three
has
to
be
at
least
four,
but
I
don't
want
it
to
be.
H
B
B
A
Okay
and
then
we
have
some
old
business
from
last
week.
I
don't
know
tim,
did
you
add
the
stuff?
Should
we
revisit
great.
A
Okay,
I
didn't
know
if
there
was
anything
unresolved
that
we
wanted
to
revisit
a
week
later,.
C
The
I
mean
I
would
I've
sort
of
stepped
back
a
bit
from
the
enforced
password
constraints
discussion,
but-
and
it
feels
like
that
that
that
issue
is
moving
okay
right
now,.
B
C
A
Okay,
yeah,
I
I
have
your
pull
requests
open
and
I'm
looking
forward
to
reviewing
that.
So,
if
you
want
to
stay
on
and
talk
about
it
later
and
I'm
all
in
favor
of
that
before
we
get
to
that,
does
anybody
else
have
anything
you
want
to
bring
up
today?
That's
not
currently
on
the
agenda.
B
B
And
the
other
one
is
my
c
yeah,
so
so
the
the
pr
that
nate
has
created
for
for
that
one
for
my
sequoia
was
back
in
december
and
there's
another
parts
available
or
many
other
in
the
d
dot
org.
A
All
right,
okay!
Well!
Thank
you!
Everybody
for
joining
and
anyone
who's
interested
in
talking
about
conditionally
added
style
sheets
turn
off
the
livestream.