►
From YouTube: Backdrop Weekly - 2021/01/28
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
today
is
thursday
january
28th,
and
this
is
our
weekly
development
check-in
meeting
they're
going
to
go
around
and
do
some
quick
introductions.
I
will
start
my
name
is
jen
lampton,
I'm
joining
from
oakland
california,
where
the
sun
came
out
today
for
the
first
time,
which
I'm
very
excited
about.
B
Sorry
who
was
called
next
was
it
me?
Okay,
sorry,
sorry,
hi!
Sorry,
I
was
typing
something
else.
My
name
is
greg.
I'm
joining
from
greece,
I'm
usually
in
australia.
Melbourne
though
I
haven't,
joined
the
meetings
for
a
week
or
two,
so
I'm
just
trying
to
catch
up
with
things
and
help
wherever
I
can
nate.
C
E
I
have
the
award
out
of
wichita
kansas.
I
don't
have
anything
specific
discussed
today,
just
kind
of
want
to
see
how
things
are
progressing
and
moving
along
I'll
go
to
who
is
left
tim.
Have
you
gone
yet.
F
Nope,
my
name
is
tim
erickson,
I'm
in
deerwood,
minnesota
and
I'll
just
call
out
the
last
week
I
sort
of
spontaneously
showed
off
this
mock-up
of
a
survey
site
that
I
had
did
and
after
some
feedback
we
went
ahead
and
launched
that
and
some
people
have
been
voting
on
what
their
priorities
are
for
backdrop,
development.
So
please
take
a
look
at
survey.bankruptcms.org.
F
Is
that
ever
ready,
john
you'd
win?
Didn't
you
or
not,.
F
A
All
right,
let's
see
so
this
week
we
have
a
handful
of
new,
contributed
projects.
User
emerge,
abuse,
ipdb
report
and
user
prune
all
came
out
this
week.
So
thank
you,
everybody
for
continuing
to
create
and
contributed
things
for
backdrop.
Also.
We
don't
usually
have
updates
from
the
pmc,
but
a
couple
weeks
ago
we
announced
a
change
to
our
policy
on
contrib
maintainer
permissions,
the
blog
post,
for
that
I
just
published
today.
So
I
had
a
schedule
for
tomorrow,
but
then
I
figured
if
I'm
gonna
announce
it
today
in
the
meeting.
A
We
might
as
well
put
the
post
up
today,
so
that
should
be
visible.
If
anyone
wants
to
take
a
look
at
it
just
to
make
it
public
and
the
important
takeaway
there
is
that
if
you
are
a
maintainer
on
a
project
in
the
backdrop
contrib
group
and
you
need
admin
access
on
it,
please
open
an
issue
in
the
queue
because
we
have
not
rolled
out
our
automated
process
to
fix
all
of
the
repositories.
Yet
so
we
will
be
granting
permission
as
requested
until
that
gets
resolved
all
right.
A
I
want
to
turn
it
over
to
nate.
To
talk
about
backdrop
releases,
oh,
wait,
wait,
there's
a
few
more
things
hold
on.
The
community
has
been
very
active
in
the
last
few
weeks
and
I'm
very
excited
about
it,
and
I
wanted
to
throw
out
a
couple
of
thank
yous.
In
the
last
meeting
we
mentioned
that
we
have
a
survey
going
out
to
collect
feedback
on
what
people
want
to
see
in
future
versions
of
backdrop.
As
far
as
priorities,
tim's
been
a
lot
of
work
working
on
the
survey
site.
A
Please,
if
you
have
thoughts
on
it,
go
to
survey.backdropcms.org
and
let
us
know
it's
an
experiment
if
it
works
really
well,
we'll,
probably
try
and
implement
this
for
future
releases.
Also,
I
have
a
feeling
it'll
work.
Well,
so
thank
you.
Tim
for
working
on
that
justin
also
spent
a
bunch
of
time
last
night
setting
up
new
sites
for
us,
so
bw
panda
peter,
has
also
been
working
on
the
doc
site.
So
thank
you,
peter
for
all
the
work
on
the
documentation
site.
Thank
you.
A
Justin
for
helping
get
the
documentation
site
switched
over.
It
used
to
be
api.backgroundcms.org.
It's
now
docs.backdrop
cms.org.
That
looks
like
it's
working
really
smoothly.
So
that's
fantastic.
We
also
have
a
new
events
site
coming
soon.
That
will
help
us
with
backdrop,
live
and
justin
set
that
up
for
us
last
night
as
well
so
cool
stuff
afoot
for
backdrop
cms.org
these
days,
which
is
great,
okay.
Oh
also,
I
wanted
to
thank
phil
for
help
with
the
dns
records
for
backdrop
semester.org.
A
C
All
right
so
over
in
the
product
land
118.1
came
out
yesterday
as
well
as
117.6.
Those
were
security,
fixes
that
updated
our
tar,
gzip
library
for
an
external
library,
vulnerability
that
has
now
been
fixed.
That
also
included
other
11
bug
fixes
as
well.
It
was
great
to
get
a
lot
of
those
small
little
things
cleared
out
of
the
rtbc
queue,
so
that's
it
for
118.
C
One
definitely
recommended
to
update.
If
you
have
not
yet
118
2
will
be
the
next
bug
fix
release
created
as
necessary.
C
C
A
It
also
needs
core
committer
review.
I
don't
know
if
anyone's
got.
I
need
approval
that
that
process
of
altering
the
message
is
acceptable.
C
Okay,
let's
see
some
new
issues:
language
names
not
translated
into
their
native
languages,
native
names,
issue,
45
11..
I
think
indigozella
opened
this
issue
just
saying
that
you
know
when
you
select
the
language
it
should
be
shown
in
that
actual
language,
so
that
pull
request
needs
review.
It
adds
new
capabilities
to
the
languages
list,
to
allow
you
to
enter
the
a
translation
of
the
language
name
itself
and
then
use
that
when
lists
of
languages
are
shown.
C
One
that
will
become
important
as
time
goes
on.
Php
8
support
is
issue.
4772
joseph
joseph
made
a
pull
request
to
get
that
moving.
It
looks
like
primarily
this
has
to
do
with
the
database
and
testing
frameworks
that
they
just
have
some
adjustments
that
are
necessary
regarding,
like
consistency
of
the
arguments,
need
to
be
the
same
between
parents
and
children
and
stuff
like
that.
So
so
far
it
doesn't
look
like
it's.
It's
a
real
big
lift
to
get
that
moving.
C
And
there's
lots
of
other
issues
in
the
118-2
milestone.
There's
several
not
so.
Maybe,
let's
see
two
rtbc
issues
and
one
that
got
bumped
from
one
eighteen,
one
that
was
almost
ready.
These
rtpc
issues
I
think
we
can
get
in
almost
at
any
time.
There
were
just
some
that
they
required
update
hooks
and
we
didn't
want
to
push
out
a
a
core
update
that
required
update
hooks.
C
A
C
Go
yeah,
we
upgraded
the
main
flagship
site
of
backdrop,
cms.org
and
some
other
peripheral
ones
right
did
you
have
to
run
updates,
updated
php
on
this.
A
B
C
B
C
C
One
more
thing:
we
can
go
ahead
and
bring
in
this
discussion
that
bwpanda
brought
up
and
put
at
the
end
of
the
agenda,
notes
that
there
is
a
small
well,
an
issue
with
color
module
and
short
hex
codes
issue:
49
13.,
that's
when
we
switched
color
module
over
to
use
the
color
input,
html
form
element,
it
dropped
support
for
short
hex
codes
like
hex
codes,
that
are
only
three
characters
accidentally,
and
so
he
filed
a
pull
request
that
fixes
that
problem.
C
C
For
hex
codes
from
being
three
characters
to
saying
we
should
always
use
six
characters,
which
is
another
thing
I
I
think
that
might
not
be
bad
to
do
both
like
make
color
modules
support
three
character
codes,
because
it
should
and
also
update
our
coding
standards
to
say
longer.
Hex
codes
are
fine
or
longer
hex
codes
are
preferred,
I'm
not
really
sure
where
that
short
versus
long
comes
from
and
what
the
current
trend
is
in
front
end.
So
I
I
think
some.
C
A
I
think
it
I've
looked
at
this
back
in
drupal
8
front-end
stuff,
and
it
came
from
a
really
really
long
time
ago
there
was
a
preference
for
typing
three
fewer
characters.
B
C
That's
really
interesting,
okay.
Well,
there
are
issues
for
both
of
those
things.
Changing
the
coding
standards
for
css
looks
like
joseph
actually
opened
this
issue
back
in
2018..
It's
issue,
oh
wait!
Oh
I'm!
Sorry!
This
is
on
the
dock
site.
There's
a
docs
issue,
issue
number
50.
C
C
A
C
C
Issue
4127,
advanced
caching,
support
for
cash
tags
and
a
dynamic
max
age.
Header
joseph,
is
the
advocate
for
this
one.
There
is
a
pull
request
now
currently
needs
work.
C
Let's
see
jen
you
have
issue.
4728
at
a
field
has
value
visibility
condition.
Do
you
have
any
updates
on
that?
No.
A
I
was
working
on
it
yesterday
because
I
obviously
updated
my
website
and
had
to
reapply
the
core
patch,
so
hopefully
I'll
have
enough
to
get
a
new
patch
soon.
For
that.
C
Okay,
next
up
is
adding
support
for
relationships
to
layout
contexts,
issue
21
34..
We
had
a
big
rush
on
this
one
right
before
the
release
of
118,
and
it's
it's
definitely
90
percent
there.
C
The
only
thing
that
really
is
holding
this
up
is
some
naming
convention
stuff
around
the
names
of
some
of
the
classes
and
how
they're
displayed
in
the
user
interface
there's
also
opportunities
to
streamline
the
user
interface
for
layouts
a
little
bit,
although
I'd
be
completely
fine
with
doing
this
first
and
then
streamlining
the
user
interface
after
words,
because
we
have
both
the
concept
of
custom
contexts,
which
is
a
little
bit
confusing
and
then
relationships
in
addition
to
that,
and
so
both
of
those
things
are
kind
of
advanced
functionality
that
could
be
grouped
together
or
hidden
away
or
done
something
to
remove
them
from
the
normal
workflow.
C
Okay
and
then
lastly,
this
issue
that
I
I
bumped
just
recently-
it
was
marked
for
118.1,
but
I
moved
into
the
119
queue
because
it
involves
url
changing,
and
this
is
for
user
roles.
C
Long
time
ago
we
went
around
and
changed
the
word
edit
to
configure
everywhere
that
you
were
saving
something
into
configuration
well,
almost
everywhere,
and
one
of
the
places
that
we
missed
is
user
roles,
that
user
roles
are
still
edited
in
the
url,
that's,
but
in
the
in
the
user
interface
it
says
configure,
but
you
end
up
at
a
url
that
says
edit
in
it.
C
Yeah
at
least
a
policy
for
how
we
deal
with
redirects
and
urls
and
so
issue.
48.99
makes
that
change.
It
switches,
those
urls.
I
I
felt
that
that
was
more
appropriate
to
be
in
a
minor
release
than
in
a
bug
fix
release,
because
I
don't
know
it
gets
a
little
bit.
It
walks
the
line
a
little
bit,
but
there
is
also
a
derivative
issue
related
to
that
that
we
don't
have
support
for
wild
cards
in
deprecated
redirects.
So
we
have
backdrop.
A
Oh
too
deprecated,
but
I
was
reading.
I
was
reading
that
issue
yesterday
and
it
looks
like
the
current
solution
is
to
have
an
entirely
new
menu
call
back
that,
rather
than
using
the
backdrop,
go
to
deprecated
function
and
the
menu
callback
could
handle
the
arguments
and
then
we
could
call
from
the
handler
for
the
menu
we
could
call
go
to
deprecated,
rather
than
altering
go
to
deprecated.
To
take
the
arguments.
So
there
is,
I
think,
a
lot
more
work
required
on
that.
C
E
C
And
just
added
to
the
agenda
gregory,
your
issue
update,
combine
all
of
the
updates
update
core
module
theme
layout
pages
into
a
single
page
issue.
27
14..
Do
you
have
a
status
update
on
that.
B
Yeah,
I
think
that
the
main
functionality
was
rtbc.
There
was
a
slight
justificated
scope
grip
at
the
end
to
also
update
the
dashboard
baseblock
and
there
was
a
breakage
there.
So
that's
the
last
remaining
bit
to
be
fixed,
pointing
out
that
this
is
not
a
new
feature.
It's
classified
as
a
task,
but
because
of
the
change
it
was
deemed
better
to
wait
for
the
next
minor
release,
so
yeah,
pretty
close.
C
Okay,
that's
it
for
the
119
issues
that
we
have
slated
so
far
tim.
I!
I
would
love
it
sorry
to
spring
this
on
you,
since
it
wasn't
in
the
agenda,
but
I
would
love
it
if
you
could
tell
us
about
the
survey
site
that
you've
built
and
what
that
could
mean
for
deciding
features
for
119.
F
F
F
There
we
go,
I
have
the
site
up.
Actually
let
me
do
this,
it's
a
little
bit
ugly.
So
some
quick
background
the
I
popped
this
idea
in
the
meeting
last
week.
F
It's
just
something
I
had
played
around
with
my
initial
thought
was
to
just
sort
of
do
an
internal
survey
in
the
active
members
of
the
community
to
sort
of
test
the
id
out
and
see
where
this
would
go,
because
it
was
a
bit
ugly
and
unpolished,
but
we
have
gotten
some
pressure
to
to
broaden
it
and
to
invite
others
to
participate.
So
we've
expanded
the
scope
a
little
bit.
It's
basically
a
website
uses
the
flag
module,
so
users
can
log
in
this.
F
My
idea
was
that
anybody
can
we
we
seated
it
with
a
number
of
issues
that
had
been
brought
up
in
some
recent
discussions,
but
also
allowed
anybody
who
creates
an
account
to
add
issues,
issues
don't
have
to
be
in
github.
You
could
add
a
new
issue
completely,
although
all
of
the
issues
we
currently
list
are
do
do
currently
have
existing
github
issues.
F
I
will
say
that
if
you
click
on
some
of
these,
the
text
here
was
sort
of
cut
and
paste
quickly,
and
so
it
may
not
be
a
great
description
and
the
best
thing
to
do
is
to
follow
through
and
actually
read
the
github
issue
where
there
is
one.
Presumably,
if
somebody
creates
a
new
one,
they'll
do
a
better
job
at
describing
it,
for
those
of
us
who
are
involved
will
recognize
a
lot
of
these
issues,
although
maybe
not
all
of
them.
F
This
is
me
logged
in
and
I
can
with
the
flag
module.
I
can
just
click
on
any
one
of
these,
so
the
yeses
are
the
ones
I
I
removed.
The
word
and
I
appreciate
feedback
on
this.
If,
after
the
meeting
I
had
the
word
vote
a
lot
and
I
removed
the
word
vote
because
I'm
just
uncomfortable
with
that
word
because
that
makes
it
sound
too
binding.
F
F
Let
me
know
if
anybody
thinks
that
in
removing
the
word
vote,
that's
made
it
harder
to
understand
what's
going
on,
but
anyway,
so
each
individual
can
see
their
what
they've
currently
voted
and
or
what
they've
currently
clicked
on,
and
they
can
just
click
on
and
change
their
preference.
The
totals
are
the
number
of
people
who've
accepted
those
that
doesn't
get
updated
until
you
refresh
the
page
we
do
have.
All
of
this
is
done.
F
You
know
pretty
quickly
you
can
sort
by
like
we
can
sort
and
see
what
the
priority
you
know
with
the
vote.
I
keep
wanting
to
use
that
word
vote.
What
the
priority
count
is.
So
far,
the
issue-
that's
winning
so
far,
pretty
handily
is
field
group
functionality
to
core
add
field
functionality
followed
by
allow
multiple
field
file,
image
uploads.
So
and
if
you
click
on
any
one
of
these,
you
can
see
if
you're
logged
in
you
can
see.
F
So
that's
how
the
site
is
working,
there's
no
formal
way
that
this
is
affects
the
next
release.
I
think,
theoretically,
the
idea
is
just
that
by
exposing
what's
most
important
to
people,
that's
going
to
help
those
of
us
advocating
for
issues
pick
our
pick
our
issues.
You
know
we'll
be
able
to
look
at
this
and
pick
things
that
we
know
are
popular
and
other
people
want.
I
know
that
some
people
that
are
active
in
core
development-
really,
you
know
some
people
just
have
their
their
personal
issue.
F
F
Great,
so
we've
got
12
people
so
far
that
have
filled
it
out
and
we
did
just
start
tweeting
about
it.
I
was
a
little
reluctant
to
tweet
about
it
again
because
I
feel
like
here
are
my
I'll
explain
my
reservations.
My
reservations
are
one
that
you
know.
This
is
a
little
bit
cumbersome.
It's
a
new
site
to
log
into
for
people
who
aren't
active
and
super
motivated.
F
F
You
know
that's
not
a
a
digestible,
easy
to
read
description,
and
I
just
don't
have
the
time
to
sort
of
polish
all
of
these,
although
you
know
I'm
open
to
discussion
about
how
we
might
as
a
group
if
we
want
to
to
try
and
make
this
better
or
to
just
accept
it
the
way
it
is
for
now
and
and
accept
that
you
know,
if
we
do
this
another
time
we
can
improve
on
it,.
C
Agree
with
the
login
thing:
I'd
I'd
love
it
if
we
could
get
a
single
sign-on
across
all
of
the
backdrop
properties
which
has
been
something
that's
been
kicking
around
for
a
while.
Now
that
it
would
be
nice
if
we
could
make
new
sites
like
this,
and
you
could
just
log
in
with
your
backdrop,
cms.org
credentials
or
if
you
were
logged
in
you
would
just
already
be
logged.
G
F
F
You
know,
and
that
makes
sense,
but
our
fear
was
that
that
would
be
a
much
bigger
task
to
try
and
integrate
it
into
an
existing
site
and
that
might
have
killed
it
for
now,
but
it's
certainly
something
to
consider
for
a
phase
two
I'll
also
say
my
idea
was
to
do.
You
know
that
this
could
be
an
annual
thing.
Other
people
have
suggested
every
release.
F
B
Well,
you
can,
you
can
stay
there
all
the
time,
but
when
we
solicit
more
input
can
be
if
every
release,
but
it
can
still
well
that's
a
good
point
too
yeah
yeah.
We
remove
things
as
they
get
added.
F
Yeah
I
hadn't
even
considered,
that
is
that
it
could
just
be
an
ongoing
thing
because,
in
my
view,
you
know
sort
of
the
rules,
the
other.
The
other
reason
I
was
reluctant
to
make
this
public
is
that
the
sort
of
I'm
not
even
calling
them
rules,
but
you
know
we
don't
have
like
limited
number
of
items
that
you
can
pick.
F
We
I
I
just
threw
out
five
to
eight-
is
a
good
number
of
issues
for
each
person
to
pick
clearly
the
fewer
you
pick,
the
more
influence
it
has,
because
a
sort
of
bullet
voting
in
a
sense
is
going
to
give
your
one
issue
the
most
kick,
but
we
don't
limit
it,
and,
and
the
other
idea
is
that
at
least
temporarily,
I
put
a
deadline
and
the
idea
was
that
like
submit
ideas
through
february
first
and
then
to
allow
two
weeks
for
people
to
sort
of
think
about
this
and
change
their
votes
or
their
selections.
F
You
know
based
on
discussion
or
just
seeing
what
other
people
are
to
me.
This
isn't,
like
you
know,
an
absolute
thing
that
you
know
people
might
change
their
mind
or
just
or
or
through
yeah
through
the
process
they
might,
as
they
see
other
people
indicating
an
interest
in
something
they
might
agree
with
that
and
want
to
change
their
their
selection
so
yeah,
but
that's
how
that
all
works,
but
that's
hasn't
been.
You
know
fully
thought
through.
B
One
thing
we
can
do
is
we
can
link
to
that
page
that
survey
from
the
roadmap
page,
because
our
roadmap
page
says
what
has
gone
in
the
latest
release
and
then
what
we
are
planning
for
the
next
one
and
it
has
a
link
that
says
to
be
determined
so.
F
B
F
Peter
plans
to
put
it
in
the
newsletter
that
hopefully
will
go
out
tomorrow,
yeah
cool,
and
so
we
should
see
I
my
original
goal
was
just
to
get
20
people
like
sort
of
just
through
zulu.
Hopefully,
if
we
get
this
in
the
newsletter,
we
can
see
more
than
that,
although
I
still
think
you
know,
if
we
got
30
or
40,
that
would
be
huge.
A
We
have
one
other
item
in
the
agenda.
I
think
we
should
talk
about
dr
wilma
requested
that
we
try
and
figure
out
how
to
test
github
release
web
hooks,
he's
working
on
the
pull
request
to
add
more
info
to
or
more
information
to,
info
files
and
needs
to
test
the
web
hook,
integration
with
project
module
and
is
having
a
hard
time
figuring
out
a
place
that
we
can
get
that
to
work
for
testing
purposes.
C
Yeah
it's
cumbersome,
but
pretty
I
wouldn't
say
standard,
but
not
not
unusual,
for
decoupled
systems.
What
what
I
do
is,
if
I'm
not
wanting
to
test
on
actual
project,
set
up
a
github
repository
that
has
releases,
and
then
I
set
up
the
like
an
artificial
web
hook
to
sometimes
I'll
actually
make
it
right
to
my
local
but
other
times
I'll,
just
make
it
not
actually
go
anywhere
and
then
github
will
fire
off
the
web
hook
and
go
back
and
look
at
the
web
hook.
C
Log
and
I
can
see
the
failed
web
hook
request
that
I
made
send
into
the
ether
basically
and
I
can
copy
the
payload
out
of
github's
log,
and
then
I
put
it
into
well.
Sometimes
what
you
can
do
is
you
can
just
use
copy
paste
that
and
use
it
in
a
curl
request
and
just
send
curl
requests
to
your
local
hosts
to
make
your
local
host
fire
the
web
hooks
as
though
github
was
sending
them.
C
That's
that
can
be
useful
if
your
public,
if
your
local
host
computer,
isn't
accessible
publicly
on
the
web,
a
even
more
capable
way
than
using
curl
is
to
set
up
a
postman
pet
collection.
That's
like
postman
is
a
a
tool
for
making
api
requests
to
any
server.
C
Github
actually
even
has
a
collection
of
postman
scripts,
so
you
don't
have
to
set
up
your
own
like
examples,
but
probably
you
would
need
to
set
up
your
own
example
anyway
in
this
case,
because,
like
what
the
payload
contains
and
like
it
would
probably
be
specific
to
your
package
or
your
project,
you
probably
would
need
to
do
a
little
bit
of
tweaking.
C
C
Yeah
that
that's
the
the
way
to
do
it,
that
requires
no
additional
permissions
that
requires
there.
That
makes
it
so
you
can
iterate
the
most
quickly
because
it
even
like
exposing
your
local
computer
to
the
internet
so
that
you
can
test
it
like
on
an
actual
github
project
that
can
be
difficult
in
itself.
It's
that,
in
my
opinion,
preferable
to
make
it
so
you
can
just
like
fake
the
requests
from
a
local
like
local
local,
rather
than
having
the
real
requests
come
from
github.
A
The
other
item
was
from
bw
panda,
wanted
an
official
direction
on
the
css
coding
standards.
I
added
a
comment
in
the
issue
saying
it
sounded
like
we
were
all
in
agreement
to
move
to
six
characters,
but
maybe
we
should
get
more
feedback
from
other
people.
If
you
want
to
add
you
have
thoughts
on
it.
The
answer
in
the
issue,
but
that's
what
it
sounded
like
to
me.
So
if
I'm
wrong,
let
me
know.
C
And
I
think
that
the
the
issue
is
where
that
consensus
needs
to
come
from,
but
yeah.
I
I
I'm
in
favor
of
doing
both
of
these
things,
like
color
modules,
should
should
support
short
codes
because
it
was
supposed
to
and
that's
just
a
bug,
but
we
also
should
make
our
coding
standards
be
six
characters
and
kind
of
fix
both.
C
Problems:
okay,
let's
see
we
have
oh,
I
only
have
a
couple
of
minutes.
Let's
see,
I
don't.
C
Update
bw
panda
isn't
here
at
the
moment,
but
jen
do
you
have
some
information
on
how
the
new
stock
site
is
coming
along.
A
Yeah,
I
mean
so,
I
think
it's
I
don't
know
if
anything's
happened
to
it
yet
other
than
the
domain
name
change.
But
what
used
to
be
api
dot
backed
up
cms
to
org,
is
now
doc
site,
backed
up
cms.org
and
there's
a
redirect
to
casual
incoming
traffic
to
api
and
send
it
to
docs.
I
updated
links
from
backdrop
cms.org
the
forum
site
anywhere
that
was
linking
to
the
api
site
should
now
link
to
the
doc
site.
Instead,
I
don't
know
what's
happening
with
content.
A
A
I'm
going
to
be
working
on
feed
stuff
today
anyway,
so
I
have
a
tab
open
to
work
on
the
github
issue
importer
for
the
survey,
which
we
probably
won't
need
this
time
around,
but
for
next
time
will
be
useful
and
I
can
also
start
working
on
and
that
I'm
going
to
do
on
the
forum
site,
and
so
I
will
be
happy
to
also
put
importer
on
the
doc
site
if
that
would
be
valuable
to
pull
stuff
around
so
I'll
paint
a
vfan
about
it,
but
yeah
a
lot
of
progress.
Momentum
on
that.
A
Oh
and
if
anyone's
curious
about
the
new
documentation
outline,
there
is
an
issue
in
the
backdrop,
cms.org
queue
with
a
proposed
organization
of
content
that
bw
spent
a
bunch
of
time.
Working
on
everything
looks
great.
So
if
anyone's
curious
about
stuff
have
a
look
there.
F
I'm
going
to
make
a
quick
bureaucratic
point,
which
is
that
technically,
when
we
set
up
initiatives
that
they
were
approved
by
the
pmc.
Of
course,
that
doesn't
mean
that
people
can't
work
on
documentation.
F
F
A
We
have
a
little
pmc
housekeeping
to
do
anyway,
since
it's
january,
so
I
thought
I
was
just
looking
through
the
queue
to
see
if
we
have
an
issue,
that's
like
every
january.
We
need
to
do
these
things,
but
if
anyone
remembers
what
we're
supposed
to
do,
I
think.
B
A
F
One
other
just
quick
announcement
sort
of
because
we
have
a
newsletter
to
go
out.
I
wanted
to
get
some
virtual
user
group
meetings
on
the
agenda
and
peter
there
has
been
a
long
desire
for
one
on
writing
tests
and
when
we've
often
done
them
the
first
tuesday
of
the
month.
F
Janet
might
be
able
to
be
there
to
sort
of
like
help
with
some
of
the
lighter
stuff,
but
if
anybody
feels
like
they're
really
knowledgeable
about
writing
tests
and
willing
to
help
present
on
that
for
as
soon
as
next
tuesday
or
if,
if
that
doesn't
work,
and
you
want
to
do
it
later,
we
could
pick
a
different
date.
But
we
talked
to
me
quickly.
C
All
right,
well,
let's
close
for
today
and
yeah.
Thank
you
guys
all
for
being
here.
As
always,
and
it
was
great
to
get
out
the
bug
fix
release
yesterday
and
we
have
lots
of
exciting
things
to
work
on
for
119..
So
yeah
great
work
see
you
guys
all
next
week.