►
From YouTube: Backdrop Virtual User Group
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
Okay,
we
are
on
the
live
on
the
air,
live
for
this,
our
second
or
our
third
I.
Think
our
third
virtual
user
group
well
for
backdrop,
CMM
we're
going
to
talk
a
little
bit
about
upgrades
from
Drupal,
6
and
7
today,
and
ideally,
what
I'd
like
is
for
each
of
us
to
we've
got
four
people
in
the
room.
Now
we
may
have
some
people
join
us.
A
Is
we
don't
have
a
really
solid
prepared
presentation
today,
but
if
we
could
try
to
go
around
the
room
and
talk
about
what
our
experience
is
and
how
you
know
what
sort
of
success
we've
had
with
upgrades
and
what
sort
of
problems
we
have
and
then
I
think
my
plan?
Is
that
we'll
talk
about
the
current
documentation
for
doing
upgrades
on
backdrop,
CMS
work
and
they're
sort
of
walk
through
those
explain
them,
and
if
people
have
questions,
ask
them
and
maybe
identify
some
things
that
could
be
improved
there.
So
I
can
start.
A
My
first
we've
done
to
actually
to
my
upgrades
from
Drupal
one
from
a
drupal
6
site
and
one
from
a
Drupal
7
site
on
the
first
one,
I
mean
I.
Think
it's
worth
talking
briefly
about
well
the
difference
between
upgrades
and
migrations,
because
I
hadn't
done
neither
before
the
backdrop
site
and
sort
of
tried
them
both
and
learned
a
little
bit
about
the
difference
and
would
like
to
share
that.
But
I
think
well,
I'll
come
back
to
that.
Maybe
after
we've
finished
our
introduction.
A
So
on
the
whole,
my
experiences
with
the
upgrade
process
have
been
pretty
smooth.
We've
run
into
some
little
glitches
here
there
it's
been
a
while,
though,
since
I
death
did
them
so
I
think
as
we
as
we
go
through
the
discussion,
I'll
try
to
remember
exactly
how
things
went
and
offer
I
feedback
who
would
like
to
go
next.
B
And
at
the
same
time,
also
I
work
with
Drupal
2,
/,
7
and
also
two
great
sites
and
recently
I
tried,
because
I
built
some
new
backdrop
size
and
with
the
first
I
first
tried
to
upgrade
my
own
website
much
backdrop,
because
I
thought
it
was
time
and
I
found
it
quite
difficult,
more
difficult
than
I
expected,
so
I
run
arrows
and
so
on.
I
think
it's
very
important
to
improve
the
documentation
and
also
include
process.
A
C
Oh
great
yeah,
so
my
name
is
Greg
young
fans
in
Melbourne,
Australia
I
do
backdrop
for
like
the
moment
that
it
started
out
almost
but
I
actually
do
not
need
that
or
use
that
for
work.
So
I
haven't
done
any
migrations.
um
I'm
a
Drupal
douchiest
and
a
nitric
enthusiast
and
I
care
a
lot
about
user
experience
and
including
the
user
interface
and
making
everything
that
has
to
do
with
Patrick
to
find
smoothly
for
people
who
just
make
it
easy
for
them.
C
I
don't
have
experience
migrating
or
operating
sites
from
these
six
or
this
seven,
but
it's
something
that
is
always
on
my
backlog
and
I
would
like
to
I,
have
access
to
a
lot
of
sites
and
databases.
So
I
can
play
in
my
local
I'm
aware
of
a
few
problems,
but
not
personally
it
from
what
people
heard
so
I'm
interested
about
that
and
I'm
here
to
help
them.
Try
to
make
things
with
the
flash
process
is
wrong.
I
drop
rate.
D
A
First
of
all,
a
really
common
question,
I
think,
is
the
dip
or
the
path
from
tuple
six
or
from
Drupal
7,
and
there's
really
only
an
upgrade
path
or,
frankly,
I
think
even
with
a
migration
path
from
tuple
7
to
backstop.
So
what
people
have
been
doing
if
they're
in
group
6
is
doing
a
Drupal
6
to
Drupal
7
upgrade
without
doing
any
kind
of
theming
or
anything.
A
You
know
we're
moving
data
and
mapping.
It
directly
from
one
site
to
another
and
we're
very
manually
making
decision
making
a
lot
of
decisions
about
what
data
we
want
to
move
and
how
we
want
to
move
it.
The
benefit
being
you're,
not
bringing
a
lot
of
crops,
but
you
don't
need
right,
there's
a
lot
of
metadata
and
other
data
and
the
triple
stores.
That
sometimes,
is
it
necessary
from
one
version
to
another
changes
and
I.
Think
a
big
difference
between
an
upgrade
or
a
migration.
Is
that
oftentimes
with
an
upgrade?
A
Is
it
sort
of
trying
to
bring
this
much
data
along
as
you
can
we're
with
the
migration
you're
being
much
more
selective
and
careful,
and
it
has
the
advantage
of
giving
McQueen
or
certain
point
in
your
news
right,
but
it
has
the
disadvantage
of,
for
example,
I
think
the
claim
we
ran
into
was
we've
heard
of.
Did
this
migration
and
then
realize
the
site
had
a
whole
bunch
of
custom
code
that
was
written
based
on
you
know
the
theme
being
with,
and
things
like
that
that
we,
you
know
hadn't
migrated.
A
C
Not
aware
of
distinction
between
the
two,
so
are
you
saying
that
an
upgrade
transfers,
both
content
and
slowly
when
you
adapt
the
theme
and
the
whole
site,
whereas
the
migration
is
sort
of
like
a
more
selective
process?
Where
you
pick
and
choose
which
bits
of
content
you
will
move
to
the
new
site?
Is
that
what
you
say
me
I
think.
A
Maybe
this
is
a
good
way
to
say
it
with
a
migration,
you're
kind
of
rebuilding
the
site
from
scratch
and
then
just
pulling
your
data
into
this
a
new
site
with
an
upgrade.
Yet
the
you
know
backdrop
is
actually
trying
to
make
assumptions
for
you,
based
on
your
own
site,
it's
trying
to
take
your
old
content
and
configuration
and
adapt
that
for
backdrop,
does
that
I've
just
got
a
good
distinction.
B
A
When
we
did
it,
we
think
there's
a
G's
there's
a
I
think
we
have
to
migrate
module.
So
it's
been
quite
a
while,
and
my
colleague
actually
did
a
lot
of
the
work
of
mapping
the
fields
I
was
involved,
so
I
thought
but
I
believe
we've
just
used
the
Drupal
but
I
think
there's
a
couple
of
different
purple
migrate
module
so
and
we
was
one
in
particular
and
I.
Don't
remember
up
the
top
of
my
head
separate.
You
know
where
tour
would
be
the
most
likely
migrate
module
Yogi's
from
from
d7
background.
D
D
C
A
C
Yeah,
thank
you
makes
more
sense.
Now.
I
was
just
under
the
impression
that
it
was
only
one
thing.
It
was
just
an
in
place
sort
of
like
upgrade
instead
of
requiring
emigration,
but
I
can
see
now
why
some
people
wanna
migrate
and
sort
of
like
did
you
get
after
the
whatever
it
was
in
the
news
outlets
I
understand
that
that
might
be
a
more
a
more
complex
situation
to
produce
documentation
for,
but
still
yeah.
B
And
maybe
we
should
also
have
a
look
at
your
data
structure
to
give
a
sort
of
indication
if
it's
worth
by
an
upgrade
or
migration,
but
there's
think
it
depends
very
of
all
the
site
was
built
from
how
the
custom
the
content
types
were
built.
For
example,
when
I
started
to
named
the
content
types
in
a
weird
way,
snow
and
and
migration
was
an
occasion
to
make
it
better.
I
wouldn't
upgrade
one
of
these
old
sites
because
they
are
not
built
very
well
and
so
on.
So
that's
one
of
the
questions
yeah.
C
My
other
thought
is
that
why
would
one
when
I
did
that
cleanup
as
I
see
it
during
the
migration
and
not
either
clean
things
up,
while
they're
in
D?
Seven
I
know
that
there
are
some
module
that
can
help
whatever,
like
I,
think
the
one
is
note
copy
or
not
long,
which
can
help
you
map
fields
from
one
content
type
to
another?
C
And
then,
when
you're
ready,
you
do
the
jump
to
blood
job
when
your
database
is
sort
of
like
in
the
place
that
you
like
or
you
perform
the
homeland
creation
as
an
upgrade.
And
then
you
do
the
cleanup,
with
respective
modules,
once
you're
in
battery
I'm
sure
that
they
might
be
valid
reasons.
But
I
would
like
to
know
what
the
process
is
and
maybe
I'll
understand
more
if
I,
actually
in
practice,
when
Shopp
migrations,
myself
back
curious,
what
your
experience
guys
is.
Yes,.
B
C
I'm,
actually,
following
the
official
slack
channel
or
migrate
channel
Ojo,
which
is
the
migration
initiative,
it's
not
anywhere
near
right
now
to
have
a
user
interface
and
be
easy
for
people.
It
requires
a
lot
of
coding,
but
my
understanding
was
also-
or
my
thought
was,
that
the
move
from
the
7th
to
Batroc
was
a
pretty
straightforward
thing
that
would
not
require
a
rebuild.
C
E
C
I
would
expect
that
that
is
a
separate
aspect
would
be
teased,
but
for
the
content
right
part
of
it,
I
would
expect
it
to
be
more
straight
straight
forward
and,
as
I
hear,
you
guys
I
understand
that
it's
not
depending
on
the
situation,
as
we
said,
if
you
choose
to
do
a
migration
and
data
cleanup,
it's
really
sad.
That
Zen
is
not
about
me
for
this,
but
I
know,
let's
see,
migrated
a
lot
of
sites,
so
you
might
be
able
okay.
A
So
Jenny's
upgraded
a
lot
of
sites.
Jen
has
very
strong
feelings
about
you.
Upgrading
and
the
reason
she
does
is
partly
because
part
of
the
whole
philosophy
a
backdrop
right
at
the
base.
Is
it
simple
is
possible
for
site
builders,
or
you
know,
people
with
maybe
limited
skill
if
you're
a
hardcore
back-end
developer
in
our
profession
at
migrating
data?
There's
a
lot
of
benefits
from
my
doing
a
migration
I
think
right,
because
you
get
to
sort
of
rethink
this
I'd
clean
up
past
mistakes
and
do
all
of
that.
A
B
C
Want
to
display
that,
on
my
end,
there's
a
little
bit
of
a
feedback
line
icon.
So
when
you
try
to
just
mute
yourself,
you
know
yeah
Tim,
it
was
okay.
Noise.
Just
real
quick
I
wanted
to
say
that
the
module
that
is
being
promoted,
sort
of
and
I
intended
to
be
making
course
the
reference
one
from
all
the
references
mike
has
done
some
work
on
it,
but
it's
been
a
while,
since
he
last
worked
on
it.
That's
my
understanding
at
least
so.
C
A
A
It
up,
isn't
so
easy
unless
you're
going
into
the
database,
because
it's
my
understanding
that
there
are
fields
that
get
brought
along
that
aren't
even
used
anymore
right,
so
you're
not
going
to
see
them
in
the
UI
and
basically
your
database
over
time
is
getting
sort
of
cluttered
with
fields.
That
is
the
new
version
isn't
even
touching
or
looking
at
so
you
won't.
There
is
no
option
to
sort
of
clean
it
up
through
the
UI
in
order
to
clean
it
up
afterwards.
A
A
Should
should
we
move
on
to
talk
I
think
that
we'd
like
to
kind
of
focus
a
little
bit
on
the
upgrade
process?
And
you
know
again,
my
thought
was
to
sort
of
look
over
that
so
take
a
look
at
the
documentation
and
talk
about
some
of
the
major
steps
of
doing
the
upgrade
process
and
answering
any
questions
that
come
up
so
I
have
I,
put
a
link
in
the
the
chat
session
for
this
and
I.
Have
it
open
I
mean
I.
A
My
recollection
is
one
of
the
big
things
that
you
need
to
do
is
go
through
your
modules.
There
contributive
modules
in
one
look
at
what
modules
have
been
ported
to
backdrop
which
ones
haven't
I.
Think
from
what
I
hear
like
Jen
talking
a
lot
about.
Is
that
you'll
find
that
most
of
our
modules
now
and
a
lot
of
sites
have
been
ported
and
if
you
haven't,
and
then
she
just
has
to
deal
with
them
afterwards
right,
so
you
go
ahead
and
upgrade
upgrade
all
the
modules
you
have
bring
in
your
content.
A
Yeah
I
mean
I
still,
even
when
I
talk
about
upgrades,
I.
Think
of
it
is
moving
day,
but
it
isn't
right.
It's
upgrading
the
data,
it's
just
changing
the
database,
so
your
data
doesn't
actually
Freitas
in
your
module
anyway,
so
like.
If
there
are
certain
modules
that
aren't
working
with
back
draft,
then
you
just
have
to
figure
that
out
afterwards.
C
C
Unfortunately,
because
it's
it
might
be
considered
of
like
quote-unquote
horse
style,
it
can
be
hosted
on
Lido
toyed
with
that
module
was
going
to
be
called
back
shot
ready.
So
you
would
install
it
to
your
d6
through
d7
side,
and
you
will
automatically
look
at
all
the
modules
that
you
have,
that
the
country
wants
not
the
custom
ones
and
and
then
compare
that
to
our
country.
C
B
I've
a
question
at
this
point
also
regarding
documentation
and
our
custom
vector
no,
not
controversial
factor
of
modules
and
are
they
supposed
to
work
when
they
are
product
from
Drupal,
so
that
I
can
also
find
an
issue
in
the
queue
and
say
it
doesn't
work
or
do
I
have
when
I
bought
the
module.
Do
I
have
to
do
something
special
to
make
it
compatible
for
not
great
a
custom
module.
Sorry
said
no
no
I
said
custom
and
contributed
in.
C
Theory,
contrib
modules:
do
we
have
a
backward
compatibility
layers
or
the
simple
modules
should
work
as
they
are
as
the
ones
that
have
not
been
folded.
So
my
understanding
is
that
the
process
would
be
you
change
the
jubal
7
for
you
swap
it
with
the
codebase
for
backup,
and
then
you
go
to
all
the
contributors
that
you
have
and
you
spot
those
with
the
respective
purported
ones.
If
there
are
not
faulted
ones,
then
you
just
leave
the
d7
months
and
they
should
most
of
them
should
work.
C
But
if
you
have,
for
example,
I
know
that
huge
modules
like
webform
or
rules
have
already
been
working,
but
if
you
would
try
to
bring
a
d7
module
of
that
magnitude,
let
me
say
I
think
that
you
most
likely
have
it
not
working
on
baby
website.
For
example,
if
you
try
to
bring
on
the
internationalization
module
that
that
is
a
lot
of
sort
of
like
low-level
api
is
I
think
that
this
will
be
better
side.
B
That's
the
process
of
of
start
over
should
be
documented
because
in
the
documentation
is,
is
so
now
make
the
database
up
dates
and
then
look
at
your
new
site,
but
that's
not
the
realistic
way.
First,
you
see
some
error
messages,
it
doesn't
work
and
so
on
and
we
have
to
drop
a
few
lines
minimum
about
how
to
restart
and
so
on.
C
In
in
our
documentation,
knowledge
and
video
talk,
we
have
a
setting
where
it
allows
you
to
say
what
status
the
documentation
page.
Is
that
I
think
that
for
that
specific
page,
we
need
to
sort
of
like
mark
it
as
it
has
problems,
it
needs
to
be
updated
cuz.
We
have
that
that
option
yeah
as
its
either
outdated
on
it
or
the
information,
is
not
correct.
I've.
B
C
A
Sorry
I
missed
your
question,
but
I
am
is
a
first
of
all
I'd
like
to
clarify,
because
I
heard
a
couple
of
people
say
then
sometimes
modules
will
just
work
in
backdrop
and
that's
not
my
understanding.
My
understanding
is
that
even
the
simplest
module
needs
at
least
like
one
or
two
lines
changed.
Maybe
Geoffrey
could
or
Jeff
could
say
that,
but
that's
misleading
and
I
heard
people
say
that
way:
oh
just
drop
it
in
and
see
if
it
works
and
yeah.
A
A
Think
that's
a
good
thing
to
do
beforehand,
but
the
I
don't
think
anything
was
gonna
work
directly
right,
so
you're
gonna
have
to
do
work
or
really
start
over.
You
know
it
may
be
in
the
future
that
in
there
maybe
in
the
future,
there'll
be
some
way
that
sort
of
like
run
an
upgrade
on
a
theme.
I
don't
know,
but
I
haven't
heard
of
that.
So
far,
yeah.
B
C
The
whole
part
of
improving
the
color
module
with
places
and
in
general
was
part
of
the
idea
of
that
did
option
that
you
mentioned,
which
says:
are
you
prepared
eh?
Are
you
prepared
to
use
a
comparable
module?
Would
it
be
install
something
like
Isis
which
allows
you
to
mess
around
with
the
colors
so
that
you
can
approximate
what
the
previous
film
was?
But
then
you
will
have
to
do
some
work
on
your
own.
C
I
recall
that
a
mother,
another
roadblock
in
this
whole
situation
and
I've
mentioned
it
before-
is
there's
an
extensive
usage
in
these
seven
sites
of
the
features
module
and
before
you
do
any
work
you
need
to.
There
is
a
d7
conceive
mo
job
that
is
called
defeat.
Your
eyes.
You
need
to
convert
your
features
yeah,
it's
a
really
like
this
needs
to
be
mentioned
in
the
documentation.
C
E
So
I
am
Aldila
Eric
I'm
from
Belgium
I
am
a
triple
seven
core
maintainer
and
I'm
a
bit
frustrated
on
the
fact
that
Drupal
7
is
not
evolving
at
the
speed
that
I
would
like
to
I'm
not
alone
to
to
have
to
do
it.
So
I
have
to
count
on
other
people
to
review
what
I
did,
but
it
takes
time
it
takes
month.
It
takes
weeks
and
it's
a
bit
pissing
me
off
so
I'm
trying
to
find
a
way
to
to
to
let
other
people
enjoy
these
patches
and
these
these
good
stuff
that
aren't
4:7.
E
That
needs
to
be
committed.
So
the
first
step
for
me
was
to
do
a
full
docker
stack.
So
I
can
spell
any
backdrop.
Instances
in
towards
recommends
maximum
and
then
work
on
it
and
then
I
also
ported,
my
first
module
last
week,
which
is
BG
image,
formatter
and
created
optimum,
but
since
I
think
last
year,
I
did
it,
but
III
gave
up
because
I
had
too
much
work
for
work
and
I
just
started
again
last
week.
E
A
C
Yeah
so
so
most
of
the
modules
that
have
been
ported,
they
have
Hoops
to
convey
variables
to
config
I.
Think
that
part
of
the
review
process
and
help
is
a
really
good
at.
It
is
to
also
watch
for
small
things
like
that,
although
it's
not
required
for
a
contributor
to
be
for
it,
but,
as
you
said
team,
it
can
be
done
afterwards.
It
is
my
understanding
that,
if
your
module
has
the
compatibility
layer
would
still
use
the
database
to
store
its
value,
so
it
will
continue
working
and
when
you
implement
the
obtain
install
cook.
C
Sorry,
the
update
hooks
later
on
and
you
upgraded
version
of
the
module.
You
would
just
convert
the
database
values
to
contiguous
that
working
difficulty.
So
the
only
for
those
simple
modules,
the
only
thing
that
you
will
miss
out
on
is
the
configuration
management
until
it's
ready
for
that
module.
That's
my
understanding,
but
I,
don't
think.
Don't
expect
the
single
module
time.
Breakage
is
because
of
that.
D
Yeah
so
essentially,
most
of
what
we're
talking
about
here
is
bullet
point
3
under
step
1.
So
we
probably
need
to
elaborate
on
all
these
bullet
points
here
and
give
some
more
context
than
around
kind
of
real-world.
They're
kind
of
abstract
bullet
points,
they're,
correct
and
I'm,
not
sure
what
the
best
way
I
mean
maybe
make
this
page
quite
a
bit
longer
or
link
out
to
other
pages
that
have
more
details.
D
C
C
Besides,
besides
the
substantial
effort,
that
might
be
why
it
might
also
be
a
good
thing
to
mention
the
thing
that
is
me
to
me:
the
the
difference
between
upgrade
and
migration
and
wits,
in
which
case
you
would
like
to
do
no
one
on
the
other
and
pros
and
cons
at
this
point,
I
would
like
to
mention.
There
was
a
member
of
the
Drupal
community
and
I
mentioned
that
here
in
Australia
that
had
a
question
and
I
would
like
to
iterate
that
question.
A
Things
like
I,
don't
remember
whose
taxonomy
or
something
but
the
kinds
of
things
that
I
don't
necessarily
look
at
laid
away
and
then
later
on
in
the
process
or
suddenly
realize
okay,
that
part
didn't
upgrade
that
smoothly.
If
I
thought
at
the
end,
and
now
I
only
have
to
back
up
and
figure
that
out
and
I'm
pretty
sure
that
we
were
able
to
like
solve
all
of
those
problems
without
too
much
effort.
But
you
have
to
understand
that
there
are
some
you
know
like
when
you
finish
that
upgrade
process
and
it
looks
really
smooth.
A
You
know
dig
a
little
bit
deeper.
Another
thing
I
just
want
to
bring
up
I,
remember
struggling
a
little
bit
with.
It
was
like
image
paths,
because
the
the
image
files
have
been
moved
and
depending
on
how
you're
managing
images
I
think
that's
a
really
common
problem.
Is
that
you're
just
going
to
have
to
be
there
sort
of
read,
create
a
symlink
or
or
change
configurations
in
terms
of
where
your
images
are,
and
that's
probably
in
the
instructions
already?
But
if
it's
not,
we
should
have
it
and
anybody
else.
Think
of
anything
are.
C
A
Don't
remember
the
specific
case:
I
just
know
that,
like
some
m8
I
think
that
there
are
a
couple
of
different
ways
that
images
get
added
to
a
site
and
one
of
the
differences
is
the
WYSIWYG
and
I.
Don't
remember,
which
ones
I
had
problems
with
right,
but
definitely
the
five.
You
know
the
files
directory
is
not
in
the
same
place
that
it
used
to
be
and,
and
that
did
cause
some
very
minor
problems.
It
was
an
easily
solved
problem
and
again
I'm
not
even
saying
that
the
documentation
doesn't
cover
it.
C
C
It
was
not
the
case
with
siquiera
27,
so
the
image
will
be
added
there
as
part
of
the
content,
but
it
wouldn't
be
able
you
wouldn't
be
able
to
manage
it
from
the
files
sort
of
like
listing
and
I
know
that
we
have
taken
a
lot
of
care
to
build
that
feature,
but
we
have
not
I
think
thought
of
the
migrations.
So
how
you?
How
images
within
content,
when
migrated,
needs
to
go
through
that
process
of
being
added
as
a
managed
file,
then,
if
that
is
possible
at
all.
D
So
I
would
say:
that's
the
first
three
bullet
points
and
step
one.
You
know
research,
what
will
be
necessary
to
upgrade
backdrop
CMS
and
that's
gonna,
point
to
time
cost
and
effort,
and
you
do
a
similar
thing
for
Drupal
8
and
then
you
have
to
make
a
decision
based
on
the
data
you
get
out
of
that
research,
but
there's
no
way
around
doing
the
research.
C
Actually,
I
lasted
III,
muted
myself
when
I
finished
the
question,
but
everybody
said
all
that's
difficult,
all
that's
alone,
and
that's
actually
my
did
my
a
reply
to
that
person.
It's
like
that's
a
good
question
and
when
I
say
it
would
I
mean
one
with
a
lengthy
discussion
required
in
order
to
get
an
answer
cool
but
yeah.
A
For
me,
as
I
talk
to
my
clients
about
whether
or
not
background
drop
might
be
appropriate
them
when
prefer
or
not
the
biggest
thing.
I
look
for
are
some
of
these
large
modules,
with
like
multiple
sub
modules
that
haven't
been
ported
right,
so
I
have
one
client
that
makes
extensive
use
of
the
domain,
access
module
and
all
of
its
sub
modules
right.
That
would
be
a
big
deal
hope
to
get
all
of
them.
A
Access,
okay,
but
another
one
would
be
commerce
right
if
you're
doing
a
you're
relying
heavily
on
the
commerce
module.
That's
a
red
flag
right,
so
you're,
either
gonna
have
to
take
it
an
entirely
different
approach
to
your
commerce
or
take
that
ownership
of
affording
the
commerce
modules,
which
would
be
huge.
So
I
look
for
those
kinds
of
things
and
I
think
you
know
the
groups.
A
Module
might
be
another
example
right:
that's
heavily
dependent
on
the
groups
module
so
there's
a
certain
sort
of
ecosystem
systems
that
would
that
aren't
trivial
to
port
and
are
you
using
any
of
those
and
if
you're
not
then
you're
in
a
really
good
shape?
But
if
you
are
that
you're
gonna
have
to
do
some
hard
thinking.
C
A
C
A
I
agree
Thanks,
so
I'd
love
for
there
to
I
mean
if
anybody
has
any
other
questions
on
this
I
think
it's
also
appropriate.
I'd
love
this,
like
save
ten
minutes
at
the
end
of
each
of
these
user
groups,
to
just
bring
up
any
questions,
but
people
have
so
I
guess
first
I
think
we're
going
to
need
to
revisit
the
upgrade
path.
A
A
C
People
might
not
decide
the
to
actually
move
to
backdrop
and
that's
something
that
should
not
make
a
sad.
We
should
try
to
make
it
easier
and
as
smoother
as
possible
for
the
ones
that
do
decide
to
do
it.
So
yeah
I
know
that
we
are
all
excited
about
working
in
new
features
and
at
least
personally
I'm
attracted
to
that
and
I
neglect
documentation
or
in
fact
trying
to
do
some
migrations
and
upgrades
from
these
seven
too.
But
chops
I
can
have
more
knowledge
but
yeah.
So
we
need
to
collectively
start
doing
that.
B
B
So
it's
not
an
issue
and
because
yeah,
it's
quite
interesting,
and
if
you
don't
try
it,
it
helps
to
tell
so
which
kind
of
I
have
a
long
list
of
arrows
where
I
didn't
know
where
to
post
them
and
so
on
and
but
at
the
end,
I
managed
to
do
the
upgrade
so,
but
especially
if
we
want
to
improve
the
documentation.
I
think
it's
good.
If
people
try
to
make
actually
the
upgrade
and
then
I
had
to
improve
the
talks,
I.
C
Like
the
get
er
comments
and
I
do
like
these
recordings
that
we
have,
but
it's
these
are
hard
sources
for
one
to
browse
two
sets
for
in
browse
for
specific
things.
So
I
think
that
we
should
also
now
that
you
mentioned
all
of
that.
You
have
a
long
list
of
errors
that
we
should
be
opening
tickets
in
the
queue
and
we
need
to
find
a
tag,
and
it's
not
just
anti
Valletta
label
also
see
how
we
do.
We
have
the
UX
&,
DX
issues
or
the
metals.
C
We
should
have
something
specific
to
my
creations
so
that
people
can
put
their
experience
there
and
also
do
the
same
on
the
forum.
So
the
forum
should
be
mostly
about
people
sharing
experiences
and
what
their
solution
was,
and
ideally
most
of
these
forum
topics
should
have
responded,
corresponding
issues
where
we
are
actually
trying
to
find
a
solution
for
the
problem.
A
I'm
just
gonna
say
on
that
you've
all
heard
me
encourage
people
to
post
questions
to
the
to
the
forum.
Is
it
my
imagination
or
not
that,
like,
if
I'm
searching
for
a
problem,
that
the
forum
reply
is
more
likely
to
come
up
at
Google,
then
get
help
to
me?
It?
Maybe
that's
not
true,
but
that's
one
of
the
reasons
I,
like
posting
things
that
aren't
bug
reports
into
the
forum,
because
it
feels
like
they're,
more
findable,
but
that
might
help
I
think
I.
D
C
A
In
the
spirit,
I
was
allowing
a
little
bit
of
time
to
just
talk
about
other
things.
The
fact
that
we
have
again,
if
I'm
saying
it
like
wow,
if
I
could
put
you
on
the
spot
and
get
or
or
and
or
give
you
the
opportunity
to
talk
quickly
about
your
you've
done
a
couple
of
big
things
for
backdrop
in
the
last
couple
of
days,
the
soccer
thing
and
importing
it
at
home.
How
do
you
think
autonomy?
D
Bluff,
are
you
willing
to
share
the
database
that
produced
so
many
errors,
or
is
there
private
information
in
it
or
anything
like
that?
um
No
I'm
going
to
show
it
yeah
yeah.
That
would
be
a
cool
test
case
to
like,
maybe
even
if
we
all
tried
out
great
on
the
same
exact
starting
set,
we
might
be
able
to
make
some
good
headway
and
improve
in
this
documentation.
D
C
B
So
I
think
the
data
privacy
is
not
a
problem
because
it's
my
personal
website
that
no
other
useless,
but
it's
localized
website
in
German.
That
may
be
difficult
because
you
can't
read
the
user
interface
without
switching
its
and
but
it's
so
maybe
that's
a
bit
complicated,
but
I
could
also
think
about,
or
we
all
think
about
another.
B
C
B
C
C
A
I'm
gonna
I
have
a
sort
of
a
hackathon
site
that
we
don't
in
triple7
that
has
some
geo
fields
and
stuff.
It's
not
too
complicated,
but
it's
complicated
enough
that
it
could
be
a
good,
a
good
test
case
and
it's
also
all
public
data.
It
was
done
for
free
of
the
hackathons,
so
we
could
totally
of
share
the
database
and,
like
you
know,
I,
could
give
anybody
access
to
it.
That
might
be
a
great
test
case
and
I'd
be
happy
to
take
a
first
pass
and
upgrading
it.
E
E
A
C
E
E
C
E
For
the
docker
stuff,
you
have
a
readme
file
that
explains
how
to
install
it,
and
it's
basically
tweet
three
comments:
that's
it
and
for
atomium,
it's
just
a
regular
team.
So
there
are
instructions,
I
think
as
far
as
I.
Remember
yes,
so
what
what's?
The
concept
of
the
Atomium
see?
Okay,
the
Atomium
team
was
developed
more
than
a
year
ago
for
the
european
commission
for
drupal
seven
and
I
started
the
project
and
I
am
still
the
active
maintainer
of
it.
So
the
idea
was
the
the
idea
was
to
decouple
everything.
E
So
we
know
that
in
Drupal,
just
like
in
backdrops,
we
have
hook
teams
that
are
defined.
Those
who
team
I
personally
call
them
components,
because
they
are
HTML
components
and
in
Drupal,
just
like
in
Bandra
either
a
hook
team
is
a
component
is
defined
using
a
template
or
a
function,
a
PHP
function.
The
purpose
of
atonium
is
to
rewrite
every
function
using
a
template.
So
there
are
many
advantages
using
templates,
because
you
can
extend
easily
your
templates
through
pre
processes
and
through
file
naming
differences
and
atomium.
E
E
You
just
have
to
have
a
couple
of
files
differently
named
and
it
worked
basically
it's
that
it
fixes
a
lot
of
stuff
within
Drupal
regarding
the
the
teaming-
and
it's
very
handy
actually
very,
very
handy
so
far,
people
that
are
so
far
all
the
people
that
are
using
it
and
the
European
Commission
said
basically
the
same
thing
this
this
team
should
have
been
released
five
years
ago.
That's
that's
mostly
what
they
did.
C
E
A
Do
it
now
I
think
the
Atomium
editor
not
any,
do
it
knocker
so
I
mean,
but
on
the
other
hand,
we
win
an
hour
and
so
I
think
we
should
quit
recording,
but
I
would
be
happy
to
schedule
another
user
group
not
just
on
the
work
we've
been
doing,
maybe
in
a
while
two
weeks
or
something
any
time
really
anything.
Let's
schedule
another
one
on
that
and
give
you
a
chance
to
show
it
off.
In
fact,
I
was
just
as
you
were
talking
thinking
that
we
could
be
an
upcoming
user
group.
A
A
Actually
do
that
for
an
excuse,
a
group,
okay,
so
think
about
think
about
what
projects
you'd
like
to
show
up
so
I'm
gonna
wrap
this
one
up:
I'm
gonna,
try
and
get
another
user
group
dead
filled
pretty
quickly
like
that,
get
it
on
the
schedule,
I
mean
so
that
we
have
time
to
plan
for
it
and
we
don't
wait
too
long.
Okay,
anybody,
a
ping
me
in
dinner
or
Twitter.
If
you
have
thoughts
or
I,
go
to
feedback,
okay,
okay,
anyway,
any
other
lab
spots
or
should
I
well,
okay,
thanks
everyone
for
coming!