►
From YouTube: Jan 23, 2020 - Backdrop Weekly Dev 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
Let's
work:
okay,
hi
everybody,
its
January
23rd
2020.
We're
really
excited
to
have
this
meeting
and
get
that
broadcast
for
once
up
on
YouTube
we've
been
having
some
technical
difficulties
week
after
week,
but
we're
back
and
what's
really
exciting
this
week
is
that
it
is
the
first
back
drop
meeting
after
the
release
of
1:15.
So
let's
give
ourselves
a
little
celebration
for
the
release
of
1:15.
A
Yeah
very
excited
to
have
1:15
out
and
we
can
discuss
what
kind
of
made
it
and
what
didn't
real.
Briefly,
of
course,
the
release
notes
and
announcement,
and
all
of
those
things
cover
that
in
more
detail.
But
before
we
get
to
that,
we'll
do
the
usual.
Thank
you
to
the
new
contributes.
They'd
have
come
out
in
the
past
couple
of
weeks.
That
includes
new
projects.
Tugboats
tugboat
is
the
system
that
we
use
on
backups
unit,
org
itself
for
spinning
ups
and
boxes.
A
We
had
written
a
custom
module
to
integrate
it
with
backdrop,
CMS
org
beat
heavy
panda,
took
that
custom
module
and
then
turned
it
into
a
generic
contributed
to
use
the
new
REST
API
that
didn't
exist
when
we
set
the
demo.
Sandbox
is
so
awesome,
BW
panda
for
making
that
project
and
making
a
release
really
appreciate
that
Allan
Mills
has
been
doing
a
couple
of
backdrop,
projects,
including
brush,
which
is
backdrop
specific
brush,
basically,
which
I
haven't
looked
into
it
at
all,
but
does
seem
like
it
could
be.
A
A
Alan
Mouse
also
made
profile,
switcher
module,
which
I
don't
know
much
about,
but
it's
out
there
now
herb
dual
ported
webform
references
as
well
as
I
think
that
I
don't
want
to
give
this
to
one
credit,
but
there's
also
the
serial
module,
which
was
ported
in
the
past
couple
weeks,
which
is
also
made
by
her
bill.
So
Thank
You,
herb
dual
BW
panda
and
Alan
Mouse
for
making
these
awesome
new
contributes
and
growing
our
code
base.
It's
really
awesome
to
see
all
those
projects
coming
together.
A
Yeah
looks
like
Jeff
threw
in
the
agenda
here,
also
something
he
wrote
up
a
year
in
review,
blog
post
on
the
backdrop,
drush
extension
that
you
can
find
I
think
that
backdrop
CMS
org
retweeted
it,
but
you
can
also
get
it
from
Sarah
and
deputy
IO,
his
blog
post
on
the
year
and
their
view
on
Josh,
which
is
interesting
in
poetry,
thanks
Jeff,
for
putting
it
together
thumbs
up.
Thank
you.
B
A
That's
yeah
thanks
Tim,
that
happens
pretty
frequently.
The
people
will
move
modules
or
create
modules.
In
the
backdrop,
contribute
and
I've
been
seeing.
Emails
come
in
frequently
probably
like
every
other
day
or
once
every
three
days
that
a
new
King
trip
project
is
transferred
into
the
backdrop
to
trip
which
usually
means
a
new
application
has
been
approved
or
somebody
wrote
a
module
separately
and
then
once
they
got
it
to
a
working
state.
They
they
move
to
do
the
contribute
by
transferring
it
within
github.
A
But
then
those
projects
don't
show
up
in
the
project
installer
or
on
backup.
Cms
organ
tell
a
release
is
created,
so
yeah
there's
a
number
of
other
backup
control
projects,
and
if
we
can
push
those
two
releases,
then
that
increases
their
visibility
to
make
it
so
that
they're
accessible
through
the
project
installer
and
on
the
backdrop
CMS
org.
A
Thanks
Tim
great
idea,
and
if
there
are
those
projects
that
people
have
found
and
are
using
it,
it
really
does
prove
everybody
to
get
a
final
release
created.
Because
then
we
can
push
out
notifications
for
security
updates
and
new
versions
and
all
those
things
until
a
release
is
made.
There's
really
none
of
that
functionality.
A
Okay,
server
side
wise.
We
have
a
little
bit
of
a
discussion
before
the
meeting
started.
I
just
want
to
call
it
out
again
that
Alan
Mouse
has
opened
an
issue
about
properly
sending
emails
from
backdrop,
CMS
bourget's
issue,
six
or
seven
and
six.
Oh
eight.
In
the
backdrop,
CMS
org
issue
queue
related
to
encrypting,
our
outgoing
email
at
six
to
eight
and
DKIM
addy
March
records,
which
is
six
or
seven,
and
there's
a
lot
of
discussion
going
on
over
there.
But
I
think
what
we'll
probably
end
up
doing
is.
A
It's
gonna
be
difficult
for
our
emails
to
get
into
people's
inboxes
directly
and
I
know
right
now,
when
you
sign
up
for
backup
CMS
start
or
go
to
a
password.
Reset
probably
goes
into
your
spam
folder,
which
is
not
just
not
an
ideal
experience,
so
those
issues,
six
or
seven
and
six
to
eight
we've
been
discussing
that
and
yeah
we'll
kind
of
continue
evolving
that
discussion
over
the
next
couple
of
weeks.
A
Okay,
let's
talk
about
the
product
so,
like
we
mentioned
back
up,
CMS
115
came
out
on
January
15th,
we're
very
excited
about
that.
We
also
had
a
large
number
of
bugs
get
fixed
as
part
of
the
115
release
and
also
the
release
of
114
point
three.
So
issues
that
were
fixed
recently
include
menu
items,
not
alpha
sorting
within
the
admin
bar
that's
issued
26:55.
A
This
is
actually
an
all
new
algorithm
that
was
implemented
into
the
generic
back
drop,
underscore
sort
function,
which
is
pretty
cool.
We
use
backup
sort
pretty
much
anywhere.
We
have
to
sort
something
by
weight
and
then
by
title
or
something
like
some
combination
of
those
things,
and
so
that
generic
sorting
function
that
we
use
in
dozens
and
dozens
of
places
through
our
core
has
been
updated
to
a
more
efficient
model.
A
Also,
the
code
seems
a
bit
simpler
if
a
little
trickier
and
that's
very
exciting
that
that
also
solved
some
bugs
so
26:55
was
merged
into
one
fourteen
three
and
is
also
in
115
of
course,
number
fields
if
you
left
them
empty.
That
caused
a
fatal
error,
sometimes
been
saving
content.
That's
issue,
3873.
That
issue
was
merged
in
fixed
date
time
tests
failing
intermittently
issue,
4180
Indigo's,
oh
and
Gregory-
were
going
back
and
forth
on
this
one
for
a
while
trying
to
figure
out
why
we
were
getting
intermittent
test
failures.
A
C
A
C
Was
so
annoying
and
I
think
it
was
only
affecting
people
in
certain
times
of
the
day
when
they
were
filing
for
requests
a
second
time
of
the
day,
and
it
was.
It
happened
to
sort
of
like
be
testing
times
of
the
day
when
I
started
doing
what
compiling
for
requests,
so
it
was
really
annoying
for
me.
Oh.
A
Let's
see,
we
also
have
a
regression
that
was
fixed
in
ckeditor.
If
you
used
really
long
links
in
the
link
dialog,
they
were
just
getting
truncated.
That
was
a
really
silly
obvious
fix
that
was
merged
in
in
2843
Jen
had
another
issue
that
has
been
bothering
her
recently
forty
to
sixty
three.
There
is
a
fatal
error
in
date,
module
under
some
circumstances.
A
But
she
opened
this
two
weeks
ago,
it's
42
67
part
of
the
g8
module
updates.
It
looks
like
cross
ports
from
Drupal
7.
This
is
a
particular
issue.
It
doesn't
look
like
she
described
exactly
when
it
happens,
though
so
I
can't
really
describe
much
more
about
it,
but
42
67
seems
like
something
that
we
should
prioritize
for
one
15.1,
which
would
be
the
next
bug
fix
release.
A
Let's
see
things
that
we
got
into
115.
Actually
it
doesn't
look
like
all
of
them
are
listed
here.
So
I
guess:
I
won't
recap
what
is
there
because
it's
not
in
our
agenda.
We
do
still
need
to
decide
relating
to
the
new
news
notifications
that
we
now
can
push
to
the
dashboard
that
come
out
of
the
box
issue.
A
625
is
a
discussion
continuing
about
what
kind
of
news
should
appear
on
the
dashboard
again
like
redoing
how
this
works.
We
have
a
new
content
type
on
backdrop:
CMS
org
I
think
it's
called
notification,
dashboard
notification
and
that
content
types
specifically
when
you
create
a
piece
of
content
it
it
populates
a
feed
that
thing's
consumed
by
backdrop
installations,
possibly
everywhere
so
6
issue
625.
A
B
Yeah,
well,
it's
it's
live
I,
just
I
I,
actually,
just
posted
a
I
did
a
blog
post
about
these
planning
meetings
and
I
created
a
public
notification
for
that
and
it's
showing
up
in
and
crap
or
bankrupt
sites.
Now
in
the
news,
the
dashboard,
so
that's
the
first
official
one
that
was
created
since
release.
A
Awesome
so
we're
still
discussing
it
seems
like
in
that
issue
what
sort
of
stuff
will
actually
be
listed
there
and
across
this
crowd,
to
do
it
once
we
figure
out
what
that
process
is,
we
can
put
that
in
the
content
creation
guidelines
that
you
see
on
backdrops.
You
must
org
when
creating
a
piece
of
content
of
that
type.
A
A
A
There
we're
a
little
bit
stuck
at
the
moment,
because
we
we
need
to
actually
test
out
how
it
works
on
touch
devices
like
iPads
in
particular,
in
order
to
accurately
make
a
description
and
text
options
for
you
know
what
toggling
that
functionality
actually
does
on
an
iPad
I
tried
using
browser
stack
this
week
to
define
that,
but
I
would
the
positive
tackles
being
horribly
slow
and
it
seems
as
though
possibly
we
need
to
renew
our
agreement
with
them.
I
think
that
it
may
have
expired
at
the
beginning
of
the
year.
A
A
A
Okay,
let's
see
some
other
things
so
I
won't
recap:
everything
got
into
115,
although
is
always
pretty
exciting.
It
particularly
like
the
image
browser,
but
there's
a
lot
of
things
that
didn't
get
in
and
so
far
these
things
have
been
bumped
to
116,
but
it's
not
definitive
like
if
we're
going
to
continue
with
some
of
these
that
some
of
them
have
been
dragging
along
for
two
releases
now,
and
so
we
plan
on
doing
the
planning
meeting
in
the
near
future.
A
Generally,
it
looks
like
that
we're
reaching
the
conclusion
that
will
probably
happen.
February
6th
and,
like
Tim
mentioned,
there's
a
notification
that
we
ought
to
back
drop
sites,
saying
that
we're
planning
on
doing
planning
meetings
and
so
February
6
is,
is
when
we'll
do
those
things
both
for
outreach
and
preliminary
ly.
We're
working
on
doing
that
for
the
dev
meeting
as
well,
so
February
6
is
probably
wooden.
A
Will
dis
better
what
goes
into
1/16,
but
the
things
that
didn't
get
in
that
we
can
still
continue
to
work
on
include
better
workflow
states
issue
1475
that
duck
woman
has
been
working
on
this
also.
We
could
generally
refer
to
this
as
the
thing
that
allows
forward
revisions
or
creating
new
revisions
without
publishing
them.
So
you
could
create
drafts
basically
of
content
like
drafts
to
updates
of
content,
or
at
least
add
that
capability
that
didn't
quite
come
together,
because
there
were
too
many
other
weird
things
that
started
happening
as
we
added
that
functionality.
A
A
C
It's
really
cause
it's
just
laziness
or
holiday,
I
would
say
season,
laziness
or
maybe
it
didn't
cause.
This
sounds
like
mr.
release.
We're
really
close
like
there
is
a
clear
way
forward,
so
what
I
was
leaving
it
a
few
last
moment
for
this
release,
but
I
think
I'm
gonna
start
early
on,
so
we
can
get
it
in
and
have
some
time
to
test
it
and
flesh
out
anything
I
think
it's
a
very
plan
that
way
yeah
it's
a
public
holiday
on
Monday.
So
this
is
a
long
weekend
for
me.
A
A
Combining
the
contents
of
the
manage
file
display
with
the
manage
display
tab
on
on
file
entities.
I,
don't
think
there
is
any
activity
through
this
whole
release.
So
that
should
be
something
we
might
discuss
in
the
planning
meeting.
If
that's
something
that
we
should
continue
putting
an
emphasis
on
sort
of
the
same.
For
my
issue
issued
in
1992
digital
signatures
on
packages,
you
made
some
progress
like
giving
that
into
contribut
for
deployment
to
backup
CMS
org.
A
You
know
really
not
a
whole
lot
of
progress
happen
this
release
and
is
it
a
high
priority
issue
really
I
know
it's
part
of
automatic
updates,
so
possibly
but
yeah
I'm,
gonna
I,
don't
know
it
would
possibly
pivot
attention
to
other
things
that
are
more
like
end-user
feature
functionality
and
possibly
less
difficult,
but
yeah.
We
can
discuss
that
in
the
planning
meeting,
but
basically
there's
not
a
lot
of
things
to
happen
on
that.
But
lastly,
entity
cache
in
core
which
Joseph
lat
put
together
is
issue
number
74.
A
I
marked
this
one,
our
TBC
at
the
end
of
the
release
and
said
you
know
as
soon
as
we
branch
for
116,
which
we
have
done
now
when
one
dot
X
is
116
now
and
the
115
dot.
X
branch
has
been
cut,
that
we
can
merge
that
into
the
1
dot
X
branch
and
start
doing
and
include
that
in
the
116
version,
pretty
much
right
away
and
so
I
haven't
yet
merged
it.
A
A
C
E
A
A
What
something
that
I
picked
up
and
the
very
tail
end
of
the
release?
Well,
I've
got
a
couple
of
irons
in
the
fire.
I've
got
one
that
one
issue
that
changes
the
way
Ajax
requests
work
so
that
they
don't
make
entries
in
the
temp
store
table.
When
you
view
the
page
and
that
solves
some
issues
where
people
have
put
Ajax
forms,
Ajax
enabled
forms
that
are
accessible
to
anonymous.
A
Users
at
the
temp
store
only
lasts
six
hours,
and
so
that
makes
it
say
your
cache
can't
be
longer
than
six
hours
your
page
cache,
because
otherwise
the
temp
store
entries
will
expire
anyway.
It's
a
it's
a
technical
like
heavy
issue,
but
it
causes
bugs
ultimately
and
I
have
an
issue
to
change
the
way
the
Ajax
framework
works.
That's
one
issue,
I
think,
could
be
helpful.
A
One
approach
sure
we
we
might
do
or
that
I
would
like
to
see
done,
is
that
we
have
a
lot
of
unfinished
stuff.
You
know
like
a
couple
of
hundred
pull
requests,
which.
A
Oh
no,
no,
some
of
them
are
huge
lots
of
functionality
that
are
like
3/4
of
the
way
there
and
it
might
be
kind
of
nice
to
just
like
go
through
and
like
try
to
minimize
the
amount
of
work
wasted.
You
know,
like
we've,
got
a
huge
amount
of
stuff
that
people
put
effort
in
that
hasn't
gone
anywhere
and
it
would
be
great
to
you
know,
did
to
get
fulfillment
on
all
of
that
work.
That's
been
been
done.
Thank.
B
A
I
think
there's
two
approaches
we
could
do
to
that.
We
could
use
them.
The
labels
that
already
exists
has
pull
requests
and
it's
still
open.
That's
not
100%
accurate.
When
we
might,
it
might
be
more
tedious,
but
it
would
be
more
accurate
if
we
actually
went
through
the
open,
pull
requests
and
triage
those,
because
sometimes
we've
got
two
or
three
pull
requests
that
might
be
open
for
the
same
issue.
Only
one
of
them
is
actually
valid
anymore
and
worked
backwards
from
the
open,
pull
requests
and
then
updated
the
related
issues.
A
A
C
Maybe
what
needs
to
be
done
is
for
also
for
the
people
I'm
talking
about
myself
now
just
go
through
my
pull,
requests
and
note,
where
I'm
being
blocked
at
and
tag
them
as
need
help,
because,
usually
that's
that's.
What
happens?
I
sometimes
usually
work
in
the
user,
interface
and
I
hit
blockers
with
form
or
states
quickness.
That
is
a
general
Drupal
bug
as
well
and
there's
nothing
much
that
can
be
done,
but
yeah
I
guess,
but.
A
But
that's
just
one
idea:
you
know
that
I
just
hate
to
see
work
wasted
and
I'm
sure
people
hate
to
have
their
work.
Their
work
wasted.
Do
you
know,
on
the
on
the
flip
side
of
that
dark
moment,
has
posted
a
couple
of
comments
to
get
er
that
were
in
the
vein
of
being
more
intentional
about
the
work
that
we
do,
which
is
literally
almost
the
opposite
of
what
I'm
suggesting
now
we
just
have
a
lot
of
work.
That's
not
done.
Maybe
we
should
finish
it.
A
His
commentary
was
that
we
seem
to
tend
to
focus
on
just
whatever
work.
People
have
started,
and
then
we've
got
a
lot
of
excitement
about
that
and
if
it
doesn't
get
done,
then
it
just
dies
and
then
something
else
get
started.
And
then
we
got
excited
about
that
and
then
then
that
may
or
may
not
get
done
too,
and
our
focus
is
just
kind
of
drifting
a
lot
of
the
time
to
whatever
is
just
receiving
the
most
activity.
I
think
that's
a
derivative
of
us
not
wanting
to
waste
work
yeah,
but
it
still
everybody.
E
A
But
it's
totally
not
a
good
way
to
you
know,
plan
a
project.
You
know
targeting
features
that
end
users
are
actually
going
to
find
the
most
helpful
and
then
prioritizing
them
and
then
doing
them.
But
that
has
its
own
problems
that
we
can't
force
anybody
to
do
work
or
even
incentivize
them
hardly
to
do
any
particular
work.
We
can
just
kind
of
say
we
would
like
these
things
to
be
done
and
then
and
then
solicit
volunteers.
That's
all
about.
We
can
do.
C
C
Instead
of
hitting
a
you
know,
plant
release,
yes
with
only
one
feature,
yeah
and,
and
also
it
has
merits
in
the
fact
that
when
people
start
making
comments
to
an
issue
and
against
activity,
it
means
that
it's
so
like
organically
evolved.
It's
something
that
is
of
interest,
so
there
is
merit
in
focusing
there
if
it
started
annoying
people.
If
it's
a
bug,
for
example,
we've.
B
Had
two
other
people,
then
doc
gubelman
and
the
issue
or
in
get
her
in
the
last
week,
complaining
about
the
number
of
open
bugs
and
pointing
it
what
they
consider
to
be
like
important,
bugs
that
have
been
open
for
three
years
and
aren't
giving
any
attention
then
I,
don't
know.
I
am
Remmick
feelings
because
it's
hard
to
you
know
it's
like.
B
If
it's
important
enough,
it
seems
like
it
should
rise
to
the
top,
but
that
doesn't
always
happen
and
I
think
the
case
like
there's
a
case
right
where
there's
an
important
issue,
but
it's
just
really
hard.
So
most
of
us
can't
do
anything
about
it.
So
it's
kicked.
The
can
gets,
kicked
down
the
road
it.
Definitely
we
don't
have
a
good
way
of
surfacing
and
finishing
those
issues
and
I,
don't
know
what
the
answer
is.
C
A
C
Would
like
to
see
more
media
sort
of
like
features
and
consolidation
of
what
weeks
we
currently
have
with
the
media
library,
like
reusing
existing
code,
not
for
only
for
image
fields,
but
for
files
in
general.
Sorry,
yeah
not
only
for
images
but
for
files
fire.
Our
browser
is
that
only
miss
Belton
yeah.
A
C
And
yeah,
and
this
through
my
daily
work,
I'm
being
exposed
to
pain
points
of
regular
content
editors
when
it
comes
to
managing
files
with
Drupal
7
and
with
the
new
media
inclusions
in
Drupal
8,
there's
a
lot
of
failures
there.
So
if
we
could
address
those,
we
could
sort
of
like
keep
that
audience
the
one
that
expect
better
media
management
lead
me.
You
know
CMS
yep,.
A
C
Thing
that
keeps
coming
up
and
it
annoys
people
because
they
expect
their
content
management
system
to
act
more
like
a
file,
browser
or
file.
Monitor
I,
would
say.
Is
that
the
way
that
Drupal
impact
rock,
when
you
upload
a
new
file
trying
to
replace
it,
you
used
to
replace
it
with
another
store,
something
else,
and
they
have
links
pointing
to
that
file
and
the
new
version
of
the
file
is
now
a
different
link
and
they
have
to
do
all
kinds
of
tricks
or
sometimes
hit
roadblocks
when
it
comes
to
that.
C
B
A
slightly
different
topic
I
wanted
to
raise
when
we've
asked
recently
what
what
people
want
to
see
in
background
search
seems
to
keep
coming
up.
It's
not
been
a
priority
of
mine,
but
I
keep
hearing
that.
Like
you,
you
know
when
we've
asked
on
Twitter
or
in
the
forum,
it
seems
like
a
really
consistent
theme
is
work
on
search
and
I'm,
not
secret.
Actually,
I
think
Allen
might
have
done
a
little
bit
of
work
search
recently,
which
is
good
yeah.
C
B
An
idea
that
I've
had
that
requires
a
little
bit
of
coordination.
Like
take
the
search
scenario,
that's
not
been
a
pressing
issue
for
me.
It
also
seems
like
it
required
some
special
expertise,
but
if
we
were
to
determine
that,
it's
like
a
priority
for
our
users,
one
possible
way,
I've
thought
of
addressing
that
is
like
having
a
search
sprint
where
we
actually
like
reach
out
to
the
Drupal
community
or
a
friends,
maybe
recruit
somebody
who's,
an
expert
on
Google
search.
If
you
help
us
out
just
for
a
weekend,
how.
B
C
C
A
A
629,
let's
see,
and
that
is
oh
it's
on
but
backdrop,
CMS
org
is
issue
queue
issue
629,
that's
important,
well,
hashed
out
in
that
issue,
kind
of
the
preferred
way
that
we
even
make
this
decision.
Some
people
I
mentioned
like
vote
with
your
feet
and
just
use
that
system
instead
or
possibly.
If
we
want
to
make
this
official,
you
know
delegate
that
to
the
PMC
and
they'll
have
a
vote
on
it
and
if
we
make
it
official,
then
that
means
that
we
would
do
things
like
remove
Gator
from
the
resources
page
on
bankruptcy.
A
Most
org
update
the
bots
like
redirect
people
over
to
Zoo
loop.
Instead,
you
know
and
we
could
officially
basic
shut
down
Kidder
and
then,
if
we
go
that
route
and
and
then
and
then
direct
people
to
the
preferred
chat
platform,
so
yeah
issue
six,
trying
on
lots
of
great
conversation
happening
over
there.
In
the
backdrop
CMS
or
issue
queue,
if
you
have
opinions
on
that
way
in
over
there,
oh
and
also
just
give
zoo
loop
a
shot.
It's
pretty
interesting,
yeah.
B
A
B
C
A
B
Is
and
I'm
feeling
like
I,
don't
want
to
put
time
into
trying
to
get
working
on,
get
her
if
we're
about
to
make
a
decision
about
get
her
so
but
but
it
did,
the
chat.
Matt
has
a
number
of
improvements
in
julep,
but
all
of
those
I
think
would
work
just
as
well
in
here.
If
we
worked
it
together,
the
only
the
only
technical
thing
we're
running
into
with
dinner
is
that
we
have
like
all
the
karma
in
the
database,
and
we
transferring
the
database
is
just
kind
of
I
haven't.
F
B
A
Without
paying
$7
a
month
yeah,
you
know
an
interesting
thought
on
that
is
that
we're
paying
for
an
entire
Linode
server.
That
is
wildly
out
of
date
and
is
only
running
exactly
as
far
as
I
know
that
get
her
bought
that
we
could
spin
that
down
and
pay
for
a
specific
node
service
at
a
lower
monthly
cost
and
save
money
overall
and
and
then
pull
that
out
of
fact
drops
funds
good
I'm,.
C
C
G
G
B
Originally
started
a
thread
and
github
just
about
what
other
services
we
might
use
and
all
of
those
came
up,
but
the
one
that
some
people
tried
was
julep
that
people
like
julep
and
so
you
know,
nobody's,
went
through
and
did
a
pro/con
of
each
of
the
different
alternatives.
But
they
were
all
actually.
C
Actually,
someone
did
I
think
that
PW
panda
went
and
just
did
a
matrix
of
things,
and
then
we
tested
a
few
of
the
platforms
we
sink
to
sort
of
like,
like
the
the
feature
that
really
pairs
of
threads
within
specific
channels.
It
helps
people
that
do
not
regularly
sort
of
like
follow
their
chat
to
come
and
catch
up
easily,
focusing
only
on
the
topics
that
matter
them
to
them.
B
C
Yeah
I
think
that
most
of
the
regulars
in
consider
sort
of
like
created,
accounts
and
started
playing
with
Zulu
yeah.
It's
my
understanding
that
90%
of
them
are
impressed
by
the
features
provided
the
only
stuff
like
if
you
can
call
it
corn
there
is
that
it's
an
its
interface
seems
a
bit
paid.
It
does.
It
needs
some
getting
used
to.
It.
Doesn't
look
modern
or
something
yeah
comments
along
that
line.
A
Okay,
well,
we've
got
lots
of.
We
open
lots
of
avenues
of
discussion
here
and
lots
of
things
to
think
about.
So
I
think.
That's
that's
where
we're
going
to
be
for
the
next
couple
of
weeks
is
you
know,
hashing
some
things
out,
making
some
decisions
and
yeah
well
next
week
we
will
probably
still
be
getting
together,
I'm,
not
sure
if
I'll
be
able
to
make
next
week
during
retreat,
but
next
week
will
be
a
normal
meeting
kind
of
like
this
one
and
then
the
one
after
that
will
be
a
big
Road
mapping
session.