►
From YouTube: Backdrop Weekly - August 6th, 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
C
Sure
I'm
greg
I'm
joining
from
greece
and
I'm
just
keeping
up
with
weekly
events
trying
to
help
us
again.
D
I'm
tim,
I'm
in
st
for
deerwood
minnesota
with
the
ducks
oops.
I
can't
see
right
now,
yeah
and
that's
it
I'm
trying
to
trying
to
track
trucks
ducks
into
the
meeting
today.
A
Jason,
are
you
there?
Would
you
like
to
introduce
yourself.
F
Yeah,
I'm
jason,
I'm
from
las
vegas
as
well,
mostly
just
looking
all
the
way
from
some
infrastructure
stuff.
A
A
All
right
first
item
on
the
agenda
today,
since
last
week
we've
had
a
ton
of
new
contrib
modules
created.
We
have
localization
client,
the
stripe
module
got
its
first
official
release,
uber
card
stripe,
ubercart,
civic
crm
integration
and
content
access.
So
that's
a
great
set
of
modules
integrations,
which
is
cool
integration
subscribe,
integrations
with
ubercart
integration.
Specific
content
access
is
a
one
of
the
top
models
for
drupal
7..
So
it's
good
to
get
that
one
done
and
localization
client
is
good,
because
that
means
more
people
are
using
backdrop
in
other
languages.
A
B
All
right,
our
current
release
is
backdrop
116.2
and
the
next
bug
fix
for
this
would
be
116.3.
B
We
have
a
number
of
issues
that
are
getting
merged
in
and
getting
piled
up
into
that
bug
fix
release
a
couple
of
these
ones
that
we
have
on
the
agenda
have
been
carrying
over
from
week
to
week
without
a
whole
lot
of
updates.
B
I'm
just
going
to
read
over
what
those
issues
are,
but
not
give
them
updates,
because
there
hasn't
been
any
changes
in
them.
So
update.php
throws
an
error
about
install.php
and
gives
an
inaccurate
message
about
your
configuration.
That's
issue,
3846,
no
updates!
It's
like
gets
stuck
in
maintenance
mode
when
you're
using
self
updates.
That's
95,
sorry,
39,
56,.
B
Since
this
first
meeting
we've
had
that
joseph
and
jason
have
been
in
for
a
little
while,
I'm
gonna
try
to
solicit
you
guys,
joseph
in
particular.
This
seems
like
it's
one
of
those
things
that
could
be
right
up
your
alley
issue:
32
13,
phpcs,
automated
code
checks.
Jeff
did
some
work
on
it
a
while
back
to
get
it.
A
B
F
Submit
some
changes
to
that
month
or
two
again.
E
I
did
some
php
7.4
things
a
while
back.
Oh,
I
did
there's
a
branch
where
we've
already
started
working
on
coding
standards
fixes
and
I
rebased.
I
made
a
pull
request
to
rebase
that
against
the
1.x
branch,
but
that
didn't
get
merged
in
and
I
don't
have
permission
to
merge
the
branches
there
so
yeah,
I
don't
know.
I
need
somebody
to
do
that.
E
Module
is
that,
right
on
on
backdrop,
core,
there's
a
phpcs
branch.
I
need
someone
to
merge
one.x
into
that
branch.
Okay,
because
the
it
was
forked
from
the
one.x
branch
over
a
year
ago,
and
so
it's
way.
E
B
That's
the
thing
yeah,
that's
that's!
That
could
be
fine
because
we
can
run
the
code
checks
on
a
particular
version
of
php.
You
know
it
can
be.
We
can
run
the
code
checks
on
php
7
and
that's
fine.
B
Yeah,
that
would
be
wonderful.
It's.
It
is
something
that
I
think
would
help
with
our
feedback
loop,
making
it
so
people
get
feedback
immediately,
even
though
it's
from
a
machine,
it
still
saves
a
lot
of
time
from
code
reviewers.
A
B
Okay
thanks
joseph,
let's
see
one
issue
that
we've
had
going
on
since
116.
Is
that
ordering
text
formats
has
a
visual
regression
on
the
administration
form
that
you
change
the
order
of
the
text
formats,
but
then
the
table
that
shows
the
list
of
text
formats
doesn't
appear
to
reflect
those
changes
after
you
save
it.
That's
issue
4407..
B
We
have
a
pull
request
now
for
that
one
yay
indigo
zella
has
reviewed
it
as
well
and
marked
it
works
for
me.
I
think
that
could
use
another
I'd,
use
a
second
look
and
confirmation.
There
are
tests
in
there
as
well,
but
I
think
that
that
one
will
probably
be
able
to
get
tidied
up
here
before
the
next
meeting.
B
Okay,
then
we
have
this
list
of
issues
that
are
almost
almost
done.
That's
are
relatively
easy,
like
low-hanging
fruit
issues
at
this
issue,
to
set
a
reasonable
amount
of
max
input,
vars
and
max
input
variables.
It's
issued
38
3824..
B
This
makes
a
notification
on
the
status
report
as
well
as
some
changes
to
the
htaccess
file
to
make
it
so
that
that
variable
gets
set
and
doesn't
trip
people
up.
The
only
thing
we're
missing
here
is
a
link
to
the
document
link
to
a
documentation
page
describing
how
to
increase
your
max
input
vars.
If
the
automated
changes
don't
work,
so
I
should
it's
not
just
a
link
to
a
documentation
page.
We
need
the
documentation
page
as
well.
So
that's
probably
the
real
kicker.
B
If
I
don't
think
that
documentation
page
needs
to
be
perfect,
like
we
can
put
in
a
pretty
minimal
set
of
instructions
there
just
to
get
a
url
to
link
to,
and
then
we
can
merge
the
pull
request
and
then
iterate
on
that
documentation.
Page.
C
B
If
I
happen
to
find
some
time,
we
even
if
there
are
good
sources
doing
it
in
different
systems,
we
could
also
even
just
say
aggregate
some
links
like
here's:
how
to
set
max
input
bars
for
you
know,
apache
on
ubuntu.
You
know
apache
on
windows,
but
I
think
officially
we
only
really.
Officially
we
only
support
apache.
Is
that
right,
yeah.
I
know
that
we
don't
officially
support
iis
and
nginx
is
like
well.
You've
got
to
do
that
all
manually
anyway.
B
So
so
really,
I
guess
that
page,
for
the
most
part,
is
probably
talking
about
the
unofficially
supported
ones.
Unless
your
apache
isn't
reading
hdx's
files,
I
see
what
you're
saying
there's
a
lot
of
things
that
could
potentially
go
wrong.
There.
C
A
People
information
section.
A
A
B
Okay,
just
like
other
documentation
pages,
though
it's
best,
if
it's
a
nice
short
url,
you
would
give
them
a
top-level
link.
So
it
doesn't
matter
if
we
move
it
later.
Yeah
yeah,
okay,.
C
A
C
C
B
B
Yeah
the
the
section
about
run,
the
installer
is
a
little
bit
weird.
C
Yeah,
so
so
my
my
take
is
always
that
if
you
have
installation
instructions
and
you're
throwing
a
huge
space
at
people,
it's
a
bit
of
pudding.
So
if
you
sort
of
like
list
the
steps
like
one
to
five
and
then
you
have
subsections
for
each
one
of
them,
sort
of
like
makes
it
less
daunting.
I
guess.
C
B
All
right
so
anyway,
that
that's
related
to
3824
the
max
input
vars
thing
documentation
holding
that
one
up
next
up,
we've
got
a
couple
of
issues
that
just
need
review,
removing
the
search,
title
or
sorry
removing
the
block
title
for
the
search
box
issue
3476,
it's
just
a
aesthetic
thing
to
make
it.
B
So
if
you
place
the
search
block
on
the
site,
it
doesn't
have
a
search
title
on
the
block
and
then
the
search
label
in
front
of
the
search
and
then
the
search
word
inside
of
the
search
box.
It's
a
lot
of
redundancy
there.
3476
just
need
to
review
this
slightly
weirder
problem
with
views
oring
together,
multiple
filters.
It
doesn't
work
quite
right
issue.
3415
currently
needs
review.
B
Then
there's
a
nice
section
here
of
things
that
got
merged
this
week.
Hooray
seek
editor,
is
not
respecting
language
that
actually
got
merged.
Two
weeks
ago,
44
92,
that
if
you
have
your
site
in
another
language,
the
button
labels
and
seek
editor
were
not
respecting
the
language
that
has
been
corrected.
B
Simple
title:
when
you're
registering
an
account
that
the
page
title
is
not
getting
translated
issue
4493
that
got
merged
in
this
helpful
change
to
make
it
so
that
our
php
files,
the
syntax,
highlighting
now
works
on
github
issue
4404.
B
We
don't
have
the
link
for
it
in
here,
but
we
brought
it
up
last
week,
gregory
your
issue
to
move
the
license
into
the
root,
which
is
also
github
related
that
we
moved
license.txt
out
of
the
core
directory
back
into
the
root
of
the
repository,
and
that
makes
it
so
that
github
now
automatically
picks
up
and
identifies
backdrop
as
being
a
gpl
v2
piece
of
software.
B
Let's
see
and
then
lastly,
in
the
merged
section,
allowing
partial
path
matching
on
autocompletes
issue
4478,
this
just
makes
it
so
whenever
you
link
to
a
node
or
view
like
in
cq
editor,
for
example,
when
you're
making
a
link
or
in
a
link
field,
there's
an
auto
complete
on
it
and
issue
four
for
issue.
4478
just
makes
it
so
that
it
now
matches
in
the
middle
of
strings
is
instead
of
just
the
beginning.
So
a
real,
simple
change
to
allow
slightly
looser.
C
Title
matching
there
yeah
the
initial
decision.
There
was
to
just
add
some
checkbox
to
enable
or
disable
that,
but
we
decided
that
we
didn't.
We
couldn't
find
a
easily,
obviously
sort
of
like
a
fitting
place
for
it
in
the
subsections
of
the
admin.
So
we
said
we
decided
to
just
leave
it
and
go
without
any
setting
up.
B
Let's
see
next
up
sick
editor
isn't
saving
in
source
mode.
I
haven't
checked
in
on
this
one.
I
can
do
an
update,
yeah
tim.
That
would
be
great
yeah.
D
And
I
can
keep
it
pretty
simple,
because
so
last
week
nate,
you
articulated
what
you
thought.
The
problem
might
be
you
needed
investigation
and
it
it
has
to
do
with
the
the
javascript
sort
of
event
things
and
after
you
explained
it,
I
asked
if
you
could
summarize
it
because
I
didn't
quite
understand,
but
I
went
back
later
re-listened
to
what
you
said
and
it
made
a
lot
of
sense,
the
second
time.
D
So
I
updated
the
issue
with
your
comments
and
I
think
we
just
ideally
would,
if
somebody
with
a
little
bit
more
javascript
experience,
could
look
at
this
issue
and
I
think,
there's
a
number
of
people
here
who
might
not
be
familiar
with
the
issue.
The
issue
is
just
that,
if
you
save,
if
you,
if
you're
using
the
text,
editor
ck
editor
in
source
mode
inside
of
a
dialog
box
and
you
hit
save,
it,
doesn't
save
your
changes.
D
If
you,
if
you
do
the
same
thing
and
you're
not
in
a
dialog
box,
it
works.
Fine
and
nate
is
speculating
that
it
has
to
do
with
the
the
handlers
or
events
that
we're
using
in
the
ajax.js
file
for
the
in
the
dialogue.ajax.js
file.
D
B
Yeah
great
great
thing,
I
think
thanks
tim
for
doing
that
summary
and
then
gregory
for
digging
up
the
line
of
code,
where
I
suggested
that
maybe
we're
not
triggering
enough
handlers-
and
you
said
we're
already
triggering
triggering.
B
B
D
D
B
C
I
I
really
like
the
ever
since
jen
introduced
this
section.
Maybe
we
shouldn't
be
calling
it
almost
done,
but
low
hanging
fruits.
So
I've
proposed
that
we
have.
We
keep
this
section
of
like
up
to
ten
small
issues
that
we
get
out
of
the
way
so
to
clean
up
the
queue.
Maybe
we
can
remove
the
ones
that
got
merged
for
next
time
and
we
add
a
few
more.
B
A
B
B
And
a
half
thousand,
that's
true:
we
do
have
more
close
issues
than
we
have
open
ones,
but
still
2000
open
issues
is
a
lot
of
open
issues.
B
I
think
thanks
gregory,
okay,
let's
see
these
next
issues,
I
haven't
been
real
close
to
them.
John,
do
you
know
the
status
of
these
blacklist?
Whitelist
master
slave
terminology
issues.
A
They
all
need
work.
The
blacklist
whitelist
one,
I
think,
is
close.
The
master
slave
one
has
a
ton
of
test
failures
because
of
how
the
slave
database
was
used.
Before
I
don't
think
I
got
all
of
the
primary
secondary
updates
in
correctly,
so
I
think
that
is
actually
breaking
stuff.
The
blacklist
whitelist
one
didn't.
I
don't
think
I
don't
think
there
was
very
much
that
could
be
broken.
B
It
needs
work,
okay,
all
right,
well,
moving
right
along
there,
then
we'll
wrap
up
for
the
bug,
fixes
and
then
we'll
move
on
to
117,
which
is
the
next
feature
release
we
are
now
in
the
last
month
of
development
for
117
feature
freeze
is
september
1st,
which
is
a
little
bit
nerve-racking,
but
on
the
other
hand
we
don't
really
have
it's
been.
This
has
been
a
strange
summer
period.
B
But
it's
also
been
a
strange
summer
for
backdrop,
development
and
that
we
haven't
been
pushing
new
features,
really
strong
for
this
release,
and
so
117
is
looking
pretty
light.
It's
a
good
chance.
It
may
stay
that
way,
because
we
only
have
one
two
three
four
little
extra
weeks
left
before
feature
grease.
B
The
one
feature
that
I
think
we
are
very
likely
to
get
in
is
this
issue
that
dr
cuomo
has
been
working
on:
adding
support
for
custom
contexts
issued
37.50
and
we've
recapped
this
issue
several
times
over
the
last
couple
of
weeks,
and
that
the
status
has
been
the
same,
that
we
need
a
code
review
on
that,
and
I
I
think
specifically
it's
been
requested
that
I
take
a
look
at
and
I
haven't
had
a
chance
yet
but
yeah
that
requires
getting
pretty
deep
into
the
layout
functionality
to
give
that
a
code
review.
B
So
that's
I'm
gonna
say
it's
mostly
on
my
plate,
although
additional
eyeballs
are
definitely
helpful
there
as
well.
D
I'm
just
gonna
add
that
I
think
the
other
thing
that
somebody
else
could
do
is
help
with
use
cases.
We've
talked
about
that
some
of
us
are
still
grappling
with
that
and
a
full
understanding
of
this,
and
it's
been
suggested
that
a
few
use
cases
would
be
would
be
helpful
because,
like
I'm,
really
hesitant
to
comment
on
this
issue
anymore,
until
I
have
a
better
understanding
of
what
I'm
looking
for.
C
D
C
Started
I
started
a
separate
issue,
it's
linked
to
that
one
and
I'm
sort
of
like
collating
any
information
or
examples
that
people
have
been
giving
out.
So
in
the
hopes
that
once
this
feature
is
in
we'll
produce
a
documentation
page
with
some
examples
like
real
life,
examples
of
where
it's
being
used
and
possibly
linked
to
it
from
the
ui
like
have
a
short
description
of
what
it
does
and
then
for
more
information.
Just
check
that
page.
B
So
other
than
that
issue,
the
admin
used.
The
admin
theme
for
the
login
form
issue.
44
10
has
stalled
out
due
to
some
access
problems
that
hadn't
we
hadn't
considered
when
we
started
that
issue
4487
spun
out
of
that
removing
the
view
administration
theme
permission,
possibly
kicking
that
into
contrib
jen.
Do
you
know
of
the
status
of
that?
One?
B
No
okay
looks
like.
B
B
A
thing
or
was
she
an
advocate
for
overlay?
Oh,
I
see
oh,
she
got
at
mentioned.
I
see
because
jen
copy
and
pasted
some
comments,
that's
funny
from
somewhere
else.
That's
funny,
so
she
just
got
notified.
A
I
think
the
last
time
I
looked
at
this
it
was
too
contentious
to
move
forward
without
resolving
all
of
the
related
issues.
So
I'm
not
sure
this
is
going
to
get
in
for
117.,
but
like
there
are
other
ones
that,
like
the
related
issues,
might.
A
B
Okay,
so
basically,
we
all
need
to
take
a
look
at
that.
The
related
issues
to
the
admin
theme
for
the
login
form
is
that
what
you're
saying.
A
B
Okay,
the
initiative
updates.
I
don't
think
that
we
have
our
leads
here.
Telemetry,
I
don't
think
has
been
making
much
progress
and
the
ready
to
wear
initiative
for
the
most
part
isn't
actually
impacting
core
directly.
So
I
don't
think
that
there's
product
updates
to
be
had
there.
D
I'll
just
say
that
I've
also
been
pushing
which
could
be
related
to
that
initiative.
The
safe
way
to
upgrade
the
basis
theme
coming
up
with
a
solution
for
that,
and
I
feel
a
little
bit
like
the
discussion
is
starting
to
fragment
and
I'm
it
needs
to
be
like
there's
a
number
of
people
that
seem
to
be
like.
Oh,
I
don't
think
they
see
the
need
for
this
and
so
they're
sort
of
pushing
like,
oh
that
we
not
do.
D
If
I
can,
the
the
overall
issue
is:
how
do
we
introduce
minor
css
changes
to
bases
that
could
potentially
break
backwards,
compatible
sites
and
there's
four
or
five
different
options
that
have
been
laid
out,
including
the
ability
to
add
a
supplemental
style
sheet?
D
And
I
see
a
lot
of
people
like
criticizing
that,
because
it's
too
complicated
but
then
suggesting
that
I
don't
know
like
we
just
tell
people
their
sites
might
break.
I
don't
know
I'm
not
I'd
like
to
move
on
this,
but
I'm
not
seeing
the
consensus.
I
think,
but
my
current
thought
is
to
just
create
a
pr
for
the
supplemental
style
sheet,
so
people
are
responding
to
something
real
and
not
an
idea.
D
A
It
also
might
help
that
it's
too
complicated
argument
if
the
pull
request
is
not
complicated.
C
A
Not
even
sure
we
need
the
check
boxes
like
a
ui
component
of
it
because-
and
we
can
debate
this
in
the
issue,
because
when
you
install
backdrop
like
we
know
which
version
is
installed,
we
could
just
set
that
secretly
be
like
from
here
on
out,
don't
add
any
additional
style
sheets
and
then
every
new
version
of
backdrop
would
get
all
the
style
sheets
and
then,
if
somebody
later
is
like,
oh
actually,
I
want
the
style
sheets
from
the
newer
version.
A
C
C
Yeah
and
just
to
clarify
things,
the
idea
is
that
only
potentially
breaking
things
will
be
sort
of
like
forked
to
say
so.
C
A
And
in
the
few
issues
that
we
have,
it's
like
not
very
much
css
either.
So
if
you
were
running
your
own
version,
you
might
just
put
that
in
your
own
theme,
rather
than
trying
to
find
that
setting
in
core
that's
going
to
include
that
amount
of
css.
So
I
think
it's
a
lot
of
concern
for
a
problem
that
will
happen
rather
infrequently,
but
it
will
give
core
a
lot
of
power
to
be
able
to
make
improvements
without
worrying
about
breaking
stuff.
So.
C
A
A
I
think
for
that
particular
issue.
There
was
also
the
maybe
we
should
rethink
the
css
on
it,
but
I
don't
know
then,
if,
after
that,
we're
like-
let's
not
risk
doing
it
again
and
put
it
into
a
conditionally
included
style
sheet
or
if
it
would
just
be
like
we're
sure,
it's
not
going
to
break
anything
and
we'll
put
it
in
yep
again,
we'll
see
issue
by
issue
will
decide
where
to
go.
E
B
D
Yeah
to
me,
the
problem,
though,
is
the
the
problem
is,
for
I
want
people
to
be
able
to
you
to
not
have
to
something
basis
right.
That
basis
should
work.
You
should
be
able
to
do
certain
things
in
the
ui
that
don't
break.
I
mean,
if
you're
already
to
the
point
where
you're
sub
theming,
then
these
things
aren't
big
issues
because
most
of
us
that
sub
theme
can
fix
them
pretty
easily,
but
it's
like
I
would
you
know
it's.
It's
like
a
gap
between
two
blocks
that
just
shouldn't
be
there
right.
A
D
I
think
we
have
our
next
steps,
though.
Let's
try
to
get
a
pr
for
that,
the
supplemental
style
sheet
and
play
with
that
a
bit
and
then
see
if
people
once
they
see
it,
maybe
feel
better
about
it.
D
So
I
have
one
other
issue
that
I
added
to
the
list,
which
has
been
getting
a
lot
of
activity
and
I
think,
could
be
a
small
new
feature
in
the
next
backdrop.
I
was
afraid
like
two
hours
ago
that
it
was
also
getting
a
bike
shutted
to
death,
and
then
this
is
the
password
constraints
issue
and
then
I
noticed
that
I
think
herb
posted
another
update
that
seems
to
be
taking
that
in
the
right
direction,
looks
really
good
to
me.
Just
at
the
point
I
was
getting
frustrated
in
despair.
D
He
came
and
did
a
pr
that
seems
to
be
bringing
together
all
the
comments.
So
maybe
we
don't
need
to
talk
about
it,
although
I
would
suggest
that
people
look
at
this
because
I'm
really,
this
has
got
like
150
comments.
Some
great
ideas
have
went
into
it,
but
I'm
afraid
that
if
we
don't
land
this
soon
it's
going
to
get
lost
and
hopefully
there
won't
be
any
like
nate.
You
won't
like
have
any
vetoes
on
it.
When
you
now
would
be
a
good
time
to
look
at
it
quickly,.
D
And
I
think
that
you
may
have
just
had
a
con
at
some
point.
There
might
have
been
like
a
default
that
that
changed
the
behavior
and
you
said
well,
the
default
should
be
the
existing
behavior
and
I
think
that's.
The
current
thought
is
that
this.
I
think
that
I
I
haven't
looked
at
the
actual
sandbox,
but
I
think
there's
a
reject
weak
passwords,
which
my
only
concern
is.
D
I
don't
know
if
I
like
that
wording,
but
it's
not
that's
not
a
major
problem
so,
but
that
box
would
not
be
deleted
or
not
be
enabled
by
default,
because
that's
not
the
current
behavior.
C
Yeah
one
thing
that
might
change
the
current
behavior
is
that
email
has
been
treated
differently
in
the
logic
that
grades
this
the
strength
of
that,
but
that
can
be
a
follow-up,
because
it's
a
this
thing.
C
C
So
the
the
the
reason
why
I
brought
that
up
is
because
the
initial
sort
of
like
title
or
intent
of
the
the
ticket
is
doing
force
constraints
which
were
two
of
them:
no
username,
no
email
the
same
so
effectively.
If
we're
keeping
all
the
logic
as
it
was
the
second
bit
which
says
no
email
won't
be
effective,
so
it
won't
be
that,
but
I'm
I'm
for
changing
that
bit
of
logic
to
also
include
email
as
sort
of
like
a
restriction,
because
it
makes
it
makes
reason
it
makes
logic.
C
D
B
B
Is
extensible
but
I'm
I'm
not
sure
if
it
is
or
not
like,
so
that
country
can
come
and
do
things
right,
yeah.
A
B
B
All
of
he
did
a
lot
of
nice
things
here,
password
entropy,
okay
yeah.
I
I
would
say
generally
like
it
looks
like
he's
going
down
a
good,
a
good
route
here,
good
real,
simple
disabled
by
default.
I
would
I
would
want
that,
but
because,
well
I
don't
know
now,
I'm
not
now,
I'm
not
sure
this
option
is
so
simple.
Now,
I'm
not
sure
if
it
should
be
disabled
by
default.
C
C
A
C
B
That
makes
it
so
you
don't
actually
need
to
know
your
password
and
you
don't
even
need
to
do
the
installation
so
for
I'm
not
sure
about
numbers
about
like
if
you're
evaluating
backdrop.
What's
the
likelihood
that
you
use
the
sandbox
and
that's
your
first
experience
versus
you
install
it
locally.
B
Yeah,
although
the
gentleman
we
had
joined
our
ux
meeting
last
week,
he
was
like.
A
B
E
I
think
a
lot
of
a
lot
of
pieces
of
software
have
demos
that
are
like
either
put
in
a
state
where
there's
not
actually
a
lot.
You
can
do
or
they're
totally
broken,
and
I
think
that
colors
a
lot
of
people's
opinions
about
demos
yeah.
I
think
our
demos
are
kick-ass.
B
D
C
There's
at
least
four
people
heard
team
indicazella
and
myself
that
are
working
actively
on
that.
So.
D
I
mean
the
advocate
role,
it
hasn't
been,
we
haven't
been
using
it
as
well.
This
release,
ideally
like
that
was
the
issues
that
had
advocates
were
the
ones
that
got
talked
about
each
week
and
we
just
haven't
quite
got
there,
but
I
still
feel
like
I've
got
that
advocate
mindset
in
my
mind,
so
it's
still
helping
me.
C
I
kind
of
see
this
cycle
as
a
nate
say
that
it's
going
to
be
sort
of
like
poor
when
it
comes
to
features.
But
we've
done
a
lot
of
cleanup,
some
tiny
fixes
here
and
there,
and
then
I
had
a
private
chat
with
doc
and
decided
that,
when
we're
sort
of
like
at
a
shape
where
most
of
the
things
that
are
considered
pitches
are
in
then
he's
going
to
help
me
out
with
reviews
and
pushing
some
of
the
pull
requests
for
tiny
things
that
I've
put
around
so
that
they
don't
linger.
A
C
D
A
B
Okay,
do
you
guys
have
anything
else?
You
would
like
to
bring
up.
B
Okay,
let's
finish
kind
of
on
time,
then
thank
you
guys
for
joining
the
meeting,
and
thanks
to
those
out
there
that
watch
these
jen
one
last.
A
Tim
and
I
are
gonna
chat
for
half
an
hour
about
a
plan
for
the
backdrop
event
that
we're
gonna
do
at
the
end
of
september.
So
if
anyone
wants
to
hang
out
and
chat
about
that
now,
we'll
stop
the
recording
but
probably
stay
in
the
meeting.