►
From YouTube: Backdrop Weekly - Sept 15th
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
hello,
it's
september,
15
2022-
and
this
is
the
weekly
backdrop
developer
meeting
today
is
release
day
of
backdrop
123.0
and
we
haven't
made
the
release
yet,
but
we'll
be
talking
about
any
last
items
very,
very
last
items
and
then
making
the
release
pretty
shortly
after
this
meeting
today,
let's
do
some
introductions.
A
B
My
name
is
tim
erickson,
I'm
st
paul
tim,
I'm
here
in
deerwood
minnesota
today
and
yeah
excited
about
all
the
upcoming
events
we
have
and
about
a
release,
we're
launching
a
backdrop
site
this
week.
It's
exciting!
That's
it.
A
All
colorado
thanks
again
everyone
all
right.
So,
let's
see
before
we
get
into
the
core
updates
jen,
we
have
a
couple
of
community
oriented
announcements.
I
think.
C
A
All
right,
fantastic
and,
let's
see
also
in
the
realm
of
community,
we
have
a
big
code
sprint
like
day
tomorrow.
It
is
correct
me,
it's
called
open
source
day
is
it?
Is
it
under
umbrella
called
grace,
hopper
celebration
series,
hopper
celebration,
open
source
day,
great
and
yeah?
We
have
a
large
number
of
contributors
that
have
volunteered
to
participate
in
that.
I
don't
think
that
this
was
discussed
during
the
outreach
meeting,
so
we
can
talk
a
little
bit
about
what
that's
going
to
look
like
here.
A
Jen
tem
and
I
are
the
mentors
for
the
the
backdrop
group
there's
a
slack
channel
that
apparently
looks
like
it
will
be
the
central
place
for
coordination
and
yeah.
I'm
I'm
really
curious
what
this
is
going
to
look
like.
You
know
how
many
like
issues
do
we
have
queued
up
you
know
to
handle
an
influx
of
developers
could
be
really
interesting.
So
tim,
do
you
know
any
any
more
details
on
this.
B
Well,
a
minor
correction,
we're
technically
project
representatives,
they
provide
their
own
mentors
and
then
so
they
have
mentors
in
addition
to
us
that
are
available
to
sort
of
help
with
technical
issues.
Of
course,
we
know
that
the
project
the
best
so
we're
there
to
help
with
the
backdrop
process,
but
they
do
have
other
mentors
anyways.
You
know
not
too
much
more
than
that.
B
B
A
B
A
B
Perfect
issue
I
mean
it
could
be
as
simple
as
a
text
change,
but
I
think
even
better
would
be
like
a
simple
css
chain
or
something
like
that.
Those
are
those
are
sometimes
really
good
kind
of
issues,
and
we
should
be
pr.
We
should
have
some
issues
available
in
a
sort
of
flag
that
we
can
do
that
with,
although
the
walking
through
the
process
of
finding
an
issue
now
that
I
think
about
it,
that's
also
valuable
right.
It's
like
going
through.
How
do
you
spread?
B
A
Thanks
tim
now,
I'm
very
excited
about
this
and
I'm
yeah,
I'm
I'm
curious.
Sorry,
I've
gotta,
I'm
gonna,
pull
you
back
in
and
talk
about
it
a
little
bit
more.
How
did
the
volunteers
land
on
backdrop
as
the
project
that
they
wanted
to
participate
in?
We
we
don't.
A
We
have
an
estimate
that
is
private
right
now,
but
it's
very
number
fairly
large
number
of
people
and
I'm
curious
like
how
how
did
they
land
on
on
backdrop,
because
I
mean
there's
tons
of
other
projects
that
look
like
they're
kind
of
intimidating,
but
my
perspective
like
like
node.js,
some
other.
Let's
hang
on,
I
saw
some
other
ones
that
I
mean
there's
like
representatives
from
like
microsoft
and
git
lab
and
like
all
of
these.
C
C
They
have
a
handful
of
projects
like
maybe
15
of
them,
and
each
project
was
able
to
specify
the
number
of
people
that
they
were
capable
of
helping
on
open
source
day,
and
so
we
limited
ours
like
the
smallest
number,
which
was
like
50
or
under,
or
something
like
that,
and
then
they
asked
you
to
list
the
languages
required
for
working
on
your
project.
C
So
we
included
like
php,
html,
css
stuff
like
that,
and
then
people
would
be
able
to
indicate
like
I
want
a
specific
project
you
could
choose
or
you
could
say,
I
don't
have
a
choice
and
they
will
assign
you
at
random
to
different
projects.
So
maybe
not
everybody
chose
us.
There
might
have
been
people
who
are
like.
I
have
php
and
html
experience
choose
one
for
me
and
osd
might
have
just
filtered
them
into
our
group.
A
Okay,
thanks,
that's
really
helpful
yeah,
I'm
curiou,
like
you
know,
I
want
to
respond
to
people
appropriately.
You
know
when
they
start
coming
in,
like.
A
C
Yeah
and
most
of
these
people
are
women
with
either
degrees
in
computer
science,
often
fresh
out
of
college
or
grad
school
or
women
who
are
interested
in
changing
into
computer
science
as
a
new
career,
so
they
might
have
some
experience
in
whatever
their
current
job
is
and
be
like.
Oh,
this
is
a
lot
of
fun.
I
want
to
switch
to
it
so
there's
a
lot
of
people
who
are
just
like
if
contributing
to
open
source
is
going
to
make
me
a
better
developer.
C
B
All
of
that
is
true.
The
one
extra
thing
is,
it's
usually
super
international
right,
like
most
of
the
participants,
are
scattered
throughout
the
world.
From
the
you
know,
africa,
asia,
you
know
some
in
europe,
you
know
I
would
it's
so
it's
very
international.
At
least
that
was
our
experience
in
the
past.
A
A
Okay,
wow,
that's
great
yeah,
we're
looking
forward
to
that
tomorrow.
Let's
see,
is
there
any
thing
that
our
community
should
be
doing
to
help
support
them?
Are
we
just
going
to
say
like
hey,
you
might
be
seeing
a
little
higher
than
active
core
issue
activity
and
if
you
can
participate
and
be
extra
friendly,
then
please
do
so.
That
sort
of
thing.
B
I
I
think
exactly
that
I
mean.
Fortunately,
this
is
like
our
fourth
time.
We've
done
this,
so
I
think
most
of
our
active
contributors
have
been
through
this
before
and
seen
it.
But
if
you,
if
you're
watching
this
and
you're
going
to
be
in
the
issue,
queue
tomorrow
feel
free,
please
do
help
these
folks.
Sometimes
you
know
we're
we're
telling
them
to
ask
questions
in
the
issue
queue
as
well
as
talking
to
us
in
the
zoom
channel.
B
But
if
you
see
questions
in
the
issue
too
and
are
able
to
help
them
out,
please
do
that.
Please
be
very
friendly
and
patient.
I
don't
know
what
else
yeah
I
mean
that
that's
primarily
it
and
again.
Just
repeat
if
you
have
ideas
for
good
first
issues.
Please
help
fly
them
so
that
we
have
them
available.
B
That's
all
we
might.
I
don't
john.
Have
we
ever
pointed
people
to
our?
I
think
we've
had
people,
you
know
we
will
mention
our
zulu
channel
to
them,
usually
mostly
because
there's
already
a
slack
channel
people
stay
there
for
the
day,
but
it
just
be
prepared
that
some
people
could
show
up
in
zulu.
But
I
wouldn't
necessarily
expect
that.
A
Okay,
all
right.
Well,
let's
move
on
to
the
backdrop
core
update.
So
as
mentioned
at
the
beginning
of
the
meeting
today
is
release
day
for
backdrop.
123
1.23.0
releases
come
out
every
four
months
and
today
is
once
again
going
to
be
just
consistent
and
rolled
out
as
usual.
A
Let's
see,
we've
had
the
backdrop
preview
release
out
for
two
weeks.
The
one
item
that
has
been
flagged
as
being
a
concern
is
issue
5764
that
some
of
our
tests
for
comment
module
we're
not
running
because
of
a
syntax
error.
Actually
so
issue
5764
has
been
addressed
and
merged.
A
A
So
I'm
really
stoked
about
the
state
of
things
we're
in
like
a
really
good
place
for
releases.
Let's
see
the
the
122
milestone
has
19
closed
issues,
so
that's
19
bug
fixes
that
will
be
going
out
today
as
well.
A
We
make
the
last
release
of
the
previous
minor
version
simultaneously,
so
122.3
will
also
be
coming
out
today
shortly
as
far
as
scheduling
is
concerned,
today
has
been
really
hectic
for
for
jen,
and
I
at
least,
and
so
the
scheduling
of
the
release
is
going
to
happen,
not
quite
right
after
this
meeting,
but
an
hour
about
4
p.m.
A
So
yeah
I
I
don't
think
that
we
have
any
major
items
or
anything
that
need
help.
We
do
have
the
checklist
for
the
release.
Let's
see
that
is
issue.
A
It's
right
at
the
top
of
the
issue
cute
because
it
was
just
created
a
couple
hours
ago:
issue:
5781
is
the
checklist
for
the
minor
release.
So
if
you
want
to
see
how
things
are
progressing,
you
can
check
out
5781
and
follow
along
with
the
checklist.
As
we
get
things
done.
We
also
normally
have
a
fair
amount
of
back
channel
in
zulip.
A
If
anything
comes
up
so
yeah,
we
didn't
have
anything
in
the
forum
post
for
today
and
it's
generally
really
pretty
quiet
anyway,
because
today's
release
day
anything
that
that
could
have
gotten
in
basically
has
at
this
point
and
most
of
the
activity
is
most
has
been
just
around
normal
bug,
fixes
and
changes.
A
So
I
think
that
you
know
there's
a
lot
of
pressure
leading
up
to
releases
as
people
rush
to
get
in
the
last
things
that
they
can
and
then
usually
after
a
release,
people
like
to
take
a
little
bit
of
a
breather
which
is
completely
fine
and
and
healthy,
so
I'm
not
sure
like
if
we
have
anything
else
to
discuss
today,
we've
got
the
the
release
coming
up
in
a
couple
hours
and
then,
after
that,
it'll
it'll
just
be
back
to
business
as
usual,
we'll
start
up
with
backdrop
124
the
next
miner
release.
A
A
You
know,
124
milestone.
Let's
take
a
look
at
that,
so
we
have
opened.
The
124
milestone
on
github
looks
like
the
only
issue
we
have
so
far.
Is
a
proposal
to
potentially
add
alt
and
title
fields
to
the
image
entity
and
looks
like
yorkshire.
Pudding
is
the
advocate
for
this.
A
Interesting,
I
haven't,
I
haven't
read
through
this
issue,
yet
it's
4007..
This
could
be
an
interesting
proposal.
A
One
consequence
of
this
would
be
that
if
we
move
the
alt
and
title
attributes
to
the
entity
instead
of
being
part
of
the
file
well,
a
couple
of
things
will
happen.
One
is
that,
right
now
the
alt
and
title
are
stored
with
the
node
like
on
the
image
field,
so
you
can
set
a
different
alt
and
title
everywhere.
An
image
is
used,
it's
the
same
image,
but
as
different
alt
and
title,
and
if
you
put
it
in
one
location
on
the
entity,
then
that
one
alton
title
gets
used
everywhere.
A
If
you
leave
it
blank,
then
the
default
will
be
used
that
sort
of
thing,
but
it
also
raises
a
a
complication
that
this
would
make
it
so
that,
when
inserting
a
an
image
using
an
image
field,
you
would
probably
need
to
be
able
to
edit
the
entity
inline
if
you're
going
to
be
putting
attributes
on
the
entity
and
not
on
the
field,
so
that
could
open
up
a
whole
slew
of
potential
difficulties,
but
I'm
yeah.
I'm
really
curious
to
see
where
this
issue
goes.
It's
marked
as
something
that's
like
hey.
A
This
is
something
d7
already
does
drupal
7
and
if
that's
the
case,
then
we'll
probably
adopt
whatever
approach
had
been
used
from
drupal
7.,
I'm
guessing
that
that's
the
direction
that
this
is
heading
well
anyway,
that's
the
only
issue,
besides
file
group,
that
has
been
moved
into
the
124
milestone,
which
means
just
generally
speaking,
you
know
the
door
is
open
for
new
features,
new
feature
requests.
A
Obviously,
there's
lots
of
feature
requests
already
out
there,
but
the
door
is
open
for
people
to
start
picking
up
the
the
issues
that
they're
interested
in
become
an
advocate
for
it,
which
is
just
as
simple
as
saying
I'd
like
to
advocate
for
this
issue
and
then
adding
the
label
milestone
candidate
dash
minor
saying.
I
would
like
this
to
be
in
the
next
minor
release.
A
Let's
see,
I'm
going
to
take
a
look
actually
at
that
label
milestone
candidate
miner
there's
actually
a
lot
of
issues
in
the
files.
It's
no
candidate,
minor,
there's
80
of
them,
that's
incredible,
most
of
those.
Usually
that
means
that
they're
waiting
for
an
advocate,
because
it
really
just
means
an
advocate-
can
come
into
any
one
of
those
issues
and
then
move
it
into
the
milestone.
A
So,
anyway,
lots
of
lots
of
options
for
people
looking
for
things
to
do.
I
don't
have
anything
else
in
really
to
to
cover.
Does
anyone
have
anything
they'd
like
to
bring
up
or
mention.
A
It's
all
quiet,
okay!
Well,
maybe
we'll
have
a
short
meeting
today,
happy
release
day,
everyone
looking
forward
to
getting
that
cut
and
and
pushed
out
later
this
afternoon,
and
thank
you,
everyone
for
your
patience.
I
know
having
a
release
of
backdrop
come
out,
you
know
at
6,
00
pm
in
some
parts
of
the
americas
or
after
midnight,
and
europe
really
isn't
ideal,
but
I
think
that
just
means
that
the
majority
of
our
promotion
and
hey
the
release
is
out
will
be
happening
tomorrow.
So
that's
fine.
A
C
Issue
issue
cleanup
on
titles
and
summaries
for
all
of
the
issues
in
the
milestone,
but
other
than
that
is
there
anything
you
want
me
to
do
while
you're
at
the
dentist.
A
Yep,
okay
and
tim
tim
dropped
off.
Have
we
I
haven't
checked
on
on
our
the
state
of
a
blog
post.
C
Yeah
we
talked
about
it
a
little
in
the
outreach
meeting.
He
said
he
has
time
to
do
it
over
the
weekend
and
if
anyone
else
wanted
to
do
it
before,
then
they
would
be
welcome
to
part
of
what
I'm
gonna
do
today
with
my
issue.
Summary
update
is
adding
that
paragraph
at
the
bottom.
That's
what
would
you
put
in
the
newsletter
to
announce
this
feature
so,
hopefully
that'll
help
when
someone
does
get
to
it.
I'll
just
have
to
pull
those
out
and
like
rephrase
them.
However,
they
feel
is
sensible.
A
Okay,
so
for
today,
and
probably
tomorrow,
announcements
likely
will
be
pointing
to
the
really
the
release
on
github
rather
than
then
a
blog
post
and
we'll
follow
up
with
a
blog
post,
covering
like
hey,
check
out
all
the
new
stuff.
That's
in
123.
A
C
A
Okay,
well,
let's
call
it
a
day,
then
thanks
and
yeah
we'll
see
everybody
online
soon
and
yeah
big
grace,
hopper
celebration
day
tomorrow.
Please
keep
your
eyes
peeled
for
new
contributors
and
be
nice.