►
Description
Today’s development agenda: http://bit.ly/1VbY8Cd
B
We
accept
donations.
So
if
you
want
to
make
a
donation
to
vector
of
CMS,
you
can
go
to
backdrop.
Cms
org,
slash,
contribute
and
we're
currently
fifty
dollars
away
from
being
able
to
order
a
new
batch
of
t-shirts.
If
you're
interested
in
new
t-shirts,
you
can
get
a
make
a
donation
today
and
we'll
send
you
either
a
thank
you
gift
of
a
t-shirt
or
hoodie
and
then
we'll
get
some
more
teachers
ordered
for
everyone
and
I
free
Calla
box.
B
Beta
is
out
now,
if
you're
interested
in
something
of
a
local
develop
environment
that
works
natively
with
backdraft
Caleb
axis
the
way
to
go,
it
is
out
and
you
can
get
it
at
in
Kalibak
stock
I.
Oh,
don't
update
ground
with
Ian
seriously.
What
I
don't
know
there?
Any
other
thing
see
rivers
you
want
to
make
it
a
fate
for
any
reason:
I
don't
have
anything
all
right.
So
with
that,
let's
turn
it
over
to
neat
to
talked
about
community
growth.
C
B
C
We
have
266
total
projects
available
for
backdrop,
CMS
on
github,
that's
for
new
projects.
Since
last
week,
182
projects
have
official
releases
on
backdrop,
CMS
org
five
new
projects
have
had
official
releases
since
last
week
and
262
total
releases
of
all
of
those
modules,
including
10
new
releases
since
last
week.
C
So
lots
of
activity
going
on
in
the
world
of
contributes
awesome
to
see
those
new
modules
coming
in
and
and
continuing
to
be
ported
and
new
versions
coming
out
of
those
those
modules
or
themes
or
layouts
I
know
lots
of
work
has
been
done,
updating
layouts
to
make
them
all
1.4
compatible.
That's
just
excellent
to
have
those
updates
all
coming
in.
We
have
53
total
members
of
the
backdrop
can't
rib.
We
have
12
pending
applications
of
people
that
have
applied
but
haven't
actually
put
up
their
projects
anywhere
at
this
point.
C
There
are
241
total
user
accounts
on
backdrop,
semester
like
three
new
users
signed
up
since
last
week.
We
had
some
reports
this
best
week
that
the
login
link
isn't
visible,
because
we
have
too
many
links
down
the
left-hand
side
now
of
our
of
our
website.
So
a
lot
of
people
don't
know
or
possibly
can't
scroll
down
in
the
left-hand,
sidebar
I
think
it's
mostly
just
the
scrolling.
On
the
left
hand,
side
bright
throws
people
off,
but
we'll
talk
about
that
more.
D
C
The
agenda
here
things
around
backdrop:
the
software
that
aren't
packed
Rupp
itself.
First
item
on
the
list
here
is
testing
infrastructure,
update.
We've
started
a
new
issue
for
looking
at
our
overall
testing
structure
at
1906.
Is
the
issue
number
and
we've
already
done
some
tremendous
work
to
speed
up
Travis,
since
we
ended
on
their
kind
of
slower
infrastructure.
C
C
As
so
many
CI
providers,
yeah
get-get
LC.
Thank
you.
I
previously
been
called
get
LC,
but
now
he's
rebranded
it
or
working
to
rebrand
it
as
n,
CI
and
so's
NCI
is
what
he's
been
working
on.
It
already
is
the
infrastructure
that
provides
our
sandboxes
and
they
sing
if
he
can
expand
that
to
be
a
test
runner
as
well,
and
we
already
have
some
preliminary
proof
of
concepts
that
are
up
and
running
doing
our
testing
suite
right
now.
It
takes
about
eight
minutes.
C
C
To
start
up
a
Travis
test
by
couple
minutes,
or
so
sometimes
so
that's
really
exciting
work
really
great
to
see
that
that
coming
along
and
it
will
be
so
great
to
have
our
testing
infrastructure
be
fast.
We
also,
since
we
moved
to
the
new
Travis
infrastructure,
have
also
been
getting
more
inconsistent
test
results
than
previously,
which
we
haven't
quite
figured
out.
What
the
cause
of
that
has
been
so,
hopefully
those
things
will
go
hand
in
hand
and
they
may
all
get
fixed
together.
C
Some
more
of
that
issue
at
is
at
1906
we're
actually
still
looking
at
other
providers
as
well
I've
been
in
talks
with
shippable
people.
There
was
a
another
one
that
I
was
just
working
with
today.
That
pretty
well
has
completely
been
ruled
out
at
this
point.
I
guess
it's
not
really
worth
mentioning,
but
anyway,
we're
sorry
still
looking
alternatives,
but
it
looks
like
there's
a
good
chance
that
you
know
gorse
doing
all
of
this
work.
C
C
E
Just
wanted
to
say
that
we're
making
progress
on
brush
up
and
brush
enable/disable
on
the
brush
enable
and
disable
like
you
to
look
at
the
methodology
be
user.
It's
not
quite
working
on
kind
of
leverage.
The
backdrop
api
functions.
So,
if
you
wouldn't
mind
giving
a
quick
look
at
that
at
some
fun
and
that's
what
I
want
to
say
about
rush
cool
yeah.
C
E
C
Okay,
yeah,
that
would
that
would
just
be
excellent
to
get
tongue
to
get
it
so
that
when
we'd
push
out
new
updates
to
pantheon
that
run,
update
dot,
PHP
button
just
doesn't
do
anything
right
now
and
I
think
that
if
we
put
it
in
there,
then
it
then
it
would
okay
cool
thanks,
Jeff
all
right.
Let's
see
next
item
on
the
agenda
is
backdrop
CMS
org
and
all
the
work
that's
going
on
there
Jen
do
you
wanna,
take
the
lead.
I
have.
B
B
C
Tomorrow,
yeah
it's
moderately
important,
but
on
the
other
hand,
we've
had
a
lot
of
bug,
fixing
releases
that
also
required
running
update
HP
like
pretty
much
every
third
time,
we've
pushed
to
Pantheon.
It's
required
running,
update
PHP.
So
for
anybody
that's
been
using
it.
It's
already
been
a
requirement,
so
it's
not
really
something
that
needs
to
be
tied
and
in
conjunction
with
1.4
I,
don't
think
I
just.
B
Think
that
you
know
the
more
time
goes
by
and
we
don't
have
that,
like
the
more
risk
increases
with
all
of
the
people
that
might
not
be
running,
update,
HP
and
especially
like
we
have
it's
in
the
newsletter
yet
for
14
I
think
we
should
wait
until
that
gets
pushed
to
Pantheon
and
then
it'll
drive
people
to
the
one
of
these
in
a
new
version
and
maybe
they'll,
update
and
I
think
we
can
get
dress
up
in
there
before
all
of
that,
that
would
be
awesome.
I
agree.
B
We
shouldn't
probably
hold
it
up,
but
I'll
try
and
I'll
try
and
work
some
more
on
Trish
up
today
and
I.
Don't
know
if
Jeff
do
you
want
to
try
and
work
on
if
you
have
time
to
work
on
Josh
up
today
for
Pantheon,
but
maybe
that
it
would
be
good
to
kind
of
prioritize
that
over
some
of
the
other
stuff,
just
because
the
more
time,
the
more
updates
we
push
without
it,
the
where
we
increase
our
risk?
Are
you
meaning
up
DB
yeah
yeah.
E
C
B
E
Yeah,
I
think
I
have
one
that
Greg
Anderson
put
on
PHP
55
I,
don't
know
when
he
did
that
he
made
made
it
so
that
all
backup
instances
go
to
PHP
5.5
because
they
were
going
to
5.3,
which
was
also
from
because
rushed
on
the
work.
That
has
to
be
five
point.
Four
plus
four
roshni
and
I
wasn't
clear
if
he
did
that
kind
of
tweaked.
That
instance,
that
we
were
working
on
her,
he
did
that
for
that
job
across
the
board.
Maybe
I
can
ask
him
that
ticket
when
I
look
at
it
today,
okay,.
B
Sounds
good,
alright,
sorry,
those
a
little
hot
check
back
Josie
mustard
org,
so
we've
got
a
bunch
of
great
progress
going
on
Gore
I
saw
you
have
a
poor
request,
ready
for
review
that
will
set
up
single
sign-on
I
can't
wait
to
try
that
I'm.
Looking
forward
to
doing
that
today,
that
is
fantastic
and
then
I
noticed
you
had
a
question
there
about
how
to
pull
in
user
data
and
save
it
to
the
user
object
in
backdrop.
B
Well,
I,
don't
know
if
your
audits
for
that
yeah
or
not-
but
I
can,
I
can
add,
a
comment
there
and
get
that
going
and
that
will
label
us
to
pull
over
the
username
profile
picture
in
the
checkbox
for
being
available
for
hire
from
github,
which
I
think
will
be
fantastic
and
so
yeah.
We
will
get
that
going
any
day
now,
which
is
really
exciting,
and
then
we
also
have
started
working
on
the
backdrop.
B
Cómo
está
art
showcase
I
know
eric,
is
working
on
setting
up
a
content
type
for
us
and
just
in
the
design
meeting
minutes
ago,
we
agreed
on
a
direction
for
design
for
our
showcase
pages
for
each
site,
which
I
think
is
going
to
be
super
exciting
to
looks
really
great
and
they
can't
wait
to
see
it
and
Weiss
had
some
great
ideas
about
how
to
build
it.
So
I
think
we're
moving
forward
on
that
as
well,
which
is
good,
I
know
we
had
a
little
bit
of
a
delay,
as
we
were
all
focused
on
dr.
B
B
I
think
we've
got
that
result
and
we're
going
to
move
forward
on
actual
setting
up
of
what
types
of
content
we're
going
to
need
to
figure
out
how
to
get
on
some
technical
Manish
deals
details
sorted
at,
but
we
should
have
more
on
that
shortly.
I
need
to
get
that
issue
link
and
throw
it
to
the
agenda.
I'll
do
that
wait
and
then
we
have
a
bunch
of
old
kind
of
long-standing,
lower
priority
issues
on
the
website,
but
we
could
definitely
use
some
help
with
and
we
have
usage
statistics
now.
B
We
want
to
make
them
visible
on
the
project
pages
and
also
for
for
backdrop
itself,
maybe
somewhere
important
like
the
home
page.
We
have
improvements
that
can
be
made
to
the
find
module.
Seen
some
layouts
pages.
We've
got
designs
for
some
of
those
and
need
them
implemented.
Some
of
them
need
a
little
design
love
and
then
we
need
a
couple
follow-ups
on
the
blog
news
announcement
section,
as
well
as
the
event
listings
in
service
provider
listings.
So
all
those
pages
are
there
and
they're
working,
but
there's
always
room
for
improvement.
B
So
we've
got
issues
for
each
of
those
that
talk
about
the
other
things
we'd
like
to
add
to
those
sections.
If
anyone
has
time
and
ability
and
lots
to
help
with
site
building
stuff,
we
definitely
could
use
lots
of
help
with
that
I
know.
Just
in
the
past
few
weeks,
I
made
a
couple
of
additional
people
administrator
on
the
sites.
They
could
start
looking
around
and
building
more
stuff
for
us.
So
if
you
want
to
work
on
those
issues,
let
us
know
we
can
get
you
what
you
need
in
type
tag.
B
Next
up
here
is
our
official
blog
schedule,
as
we
me
talk
about
this
last
week,
yeah,
maybe
we
didn't,
but
Nate
did
manage
to
get
his
blog
post
out
for
benchmarking
on
backdrop
on
different
backdrop
and
in
Drupal
7,
which
I
think
is
fantastic,
so
that
is
on
our
website
right
now.
If
you
want
to
give
that
a
read
in
the
news
section,
we
do
have
a
couple
of
other
blog
posts
in
the
works.
I
know
everybody
wants
to
write.
One
I,
don't
know
that
we
have.
B
B
We
have
a
newsletter
that
is
going
to
go
out
as
soon
as
we
push
that
update
to
pantheon
so
that
people
don't
get
the
newsletter
and
try
and
update
their
Pantheon
sites
and
wonder
why
they
can
I
have
a
draft
of
it
in
a
google
doc.
But
it's
not
it's
not
in
MailChimp.
Yet.
So
if
anyone
wants
to
review
the
newsletter
I'll,
throw
that
in
MailChimp
today
and
send
out
a
test
who
wants
to
take
a
look
that
for
us
make
sure
don't
have
any
typos
in
there?
That
would
be
great.
C
Sorry
mute
all
right,
yes,
so
backdrop
CMS
itself,
as
you
guys
all
know,
one
point
for
Team
act
on
May
fifteenth,
which
was
very
exciting
yeah
I
can
remove
that.
Now
we
have
the
last
release
of
1.3,
which
was
one
point
three
point:
seven
and
that's
available
kind
of
as
the
last
legacy
release
of
1.3.
C
There
are
a
number
of
issues
that
we've
got
as
follow.
Ups
for
the
mechs
bug-fix
release
of
1.4,
we
found
a
couple
of
minor
issues
that
have
been
fixed
by
a
couple
of
minor
issues
that
haven't
one
issue.
That
I
was
looking
at.
That
I
could
use
some
help
with
since
I.
See
doc
moment
is
here
is
a
the
Installer
project
browser
project
installer
module
there
we
go
the
project.
Installer
module
doesn't
work
with
the
manual
uploading
of
archives
right
now.
F
C
Overall,
actually,
fairly
minor
issue
for
41.4.
So
let's
see
that,
just
as
things
come
up
keep
filing
those
bug
reports
we
love
to
have
them,
we've
been
running
through
them
pretty
quickly
and
trying
to
get
them
all
fixed.
So
next
release
is
sep.
Tember
15th.
We
have
almost
four
months
to
make
some
awesome
new
projects
and
build
some
amazing
new
features
into
backdrop.
C
C
Definitely
probably
the
largest
challenge
in
that
that
issue
issue
1301.
If
you'd
like
to
take
a
look
at
that
new
front
and
diamond
core,
this
one
almost
made
it
into
1.4,
but
we
really
put
a
focus
on
layouts
to
make
it
so
that
the
new
layouts
happen,
but
that
made
it
so.
The
new
core
theme
slipped
its
issued
1361
the
new
core
theme
called
basis.
C
A
A
E
A
B
C
Come
on
yeah,
actually
kind
of
related
to
some
of
the
mock-ups
that
were
dumb
for
basis
way
back
in
the
day.
It
looks
like
Jenrry
added
this
to
the
agenda
is
that
we
need
a
new
home
page
layout,
that
is
just
a
single-column
layout.
Instead
of
being
the
two
column
layout
and
that's
been
added
back
into
the
agenda,
which
is
great,
we
nixed
it
prior
to
1.4
being
released.
C
That
issue
is
1042
in
which
we're
going
to
add
a
new
front
page
layout,
that
is
there
out
of
the
box,
so
that
way
can
position
some
things
on
the
front
page.
Besides
just
the
river
news,
traditional
a
slash,
node
front
page
that
we've
had
in
Drupal
since
forever
so
yeah.
That
would
that
definitely
opens
up
our
options
as
far
as
making
a
better
out
of
box
experience
for
the
front
page.
C
And
then
there's
also
on
1.5
mile
stone,
there's
a
whole
bunch
of
model.
There's
quite
a
few
things
in
here.
Anything
they
didn't
make
it
into
1.4
was
built
to
the
1.5
mile
stone
and
you
can
find
that
on
github
and
then
under
milestones.
Then
click
on
one
point,
five
point:
oh
and
you
can
find
there's
a
whole
bucket
load
of
other
issues
that
we'd
like
to
see
for
that
September
release
in
general.
C
We've
kind
of
we
mentioned
this
last
year
or
last
last
week,
we're
kind
of
angling,
the
1.5
release
to
be
the
editorial
experience,
release
which
will
improve
the
the
way
that
we
edit
and
create
content.
So
the
rich
text
editor
fits
into
that
references
fits
into
that
the
front
end
theme,
but
but
a
good
thing
that
it's
good
for
us
to
have
a
focus
and
put
our
attentions
towards
a
particular
area,
and
I
think
that
the
node
forum
for
this
release
is
really
where
we
should
be
putting
some
effort
so
yeah.
C
C
So
a
primary
place
of
communication
is
on
github,
get
up,
calm,
/
backdrop
/
backdrop
dash
issues.
You
can
also
meet
up
with
us
in
git
er.
It's
a
web-based
chat,
get
er,
IM
/
backdrop,
/
backdrop
dash
issues.
We
have
an
IRC
channel
pound
backdrop
in
a
free
note
on
IRC
and
a
reddit
channel
for
doing
water,
cooler,
type
discussions,
reddit
com,
/,
r,
/
backdrop.
C
Let's
see
upcoming
events,
there
are
some
exciting
ones.
Silicon
is
coming
up
in
the
very
near
future.
It's
in
Fort,
Collins,
Colorado
and
June
second
and
june
third,
and
then
right
after
that,
next,
the
weekend
after
that
is
Twin,
Cities,
drupalcamp,
June,
seventh
and
June
tenth
I'm,
not
sure
about
civic
on
it,
had
been
on
our
agenda
to
swing
through
there,
but
I'm
not
sure
what
are
our
situation
is
for
that.
Yet
I
know
jen
and
I
will
be
at
Twin
Cities
drupalcamp.
C
We
will
be
having
a
full
day,
training
at
Twin,
Cities
drupalcamp,
as
well
as
presentation.
So
if
you're
in
the
Midwest
area
and
like
to
hear
more
about
backdrop,
it's
a
great
opportunity
to
get
a
full
day
of
backdrop,
as
well
as
just
catch
up
session,
on
how
backdrop
is
standing
overall,
there's
a
bunch
more
events
on
the
website
by
trusting
rest
of
the
work.
/
events.
C
I'll
just
wrap
this
up
books.
Beginning
backdrop:
CMS
will
be
coming
out
next
month,
a
little
less
than
30
days
from
now.
So
it's
really
exciting.
It'll
be
the
first
full-length
book
on
a
backdrop
brought
to
you
by
a
press
and
author
Tom
Tom
Wilson.
He
also
has
a
existing
book
migrating
from
Drupal
the
backdrop
available
now
from
amazon
and
it's
a
short
little
book
on
on
how
to
move
your
site
from
Drupal,
6
or
Drupal
7
to
backdrop,
that's
it
for
the
agenda.
B
B
It
kind
of
aligns
with
those
of
us
are
doing
to
push
on
improving
to
editorial
experience
in
the
software,
but
yeah
I
think
having
a
focus
on
getting
our
documentation
up
to
do
is
going
to
be
good
and
so
I'm,
just
gonna
put
it
in
the
agenda,
so
we
can
talk
about
it,
so
there
any
blockage
or
anything
we
need
to
get
moving
every
week.
We
can
follow
up
on
that
as
well.
B
C
So
I'll
elaborate
on
on
what
I
found
is
that
Drupal
community
member
I
am
eat
which
I
don't
know
his
real
name.
But
that's
his
handle
he's
been
doing
some
historical
analysis
of
the
Drupal
community
and
he
found
that
the
peak
of
contributions
to
the
Drupal
contribute
happened
in
2012
and
it's
been
declining
ever
since,
and
that
had
a
coincidental
or
maybe
not
so
fun
to
know
a
very
strong
correlation
to
win
the.
C
So
I
don't
know
that
that
I
do
think
that
it's
worth
looking
at
and
some
things
like
license
texts.
We
really
don't
need
the
license
text
requirements
because
we
can
do
that
at
the
packager.
These
days
we
didn't
have
the
packager
when
we
started,
but
it's
also
kind
of
nice
to
have
the
license
txt
file
in
the
repository
in
the
first
place,
because
a
lot
of
get
analysis
analyses
that
people
do
on
github.
They
check
for
license
files
in
the
repositories
rather
than
whatever
we
would
tend
to
read
me.
B
G
The
only
thing
that
might
be
there
is
access
rights.
If
anyone
can
just
ask
do
we
have
limitations
in
place
now
that
a
thing
I
recall
and
me
shoot
some
time
that
we
could
adapt,
it
did
happen.
L
do
to
limit
the
authors
better
project,
whereas
the
be
the
way
that
I
understand
it
is
anyone
who
is
a
contributor
and
commit
to
any
project,
and
we
rely
on
their
ethics.
Do
not
do
so.
G
Maybe
they
might
be
malicious
intent,
thereby
I,
don't
know
whoever
that's
the
only
thing
that
I'm
worried.
We
said
that
that,
at
some
point
that
we
could
make
it
author
web
project
and
like
illness,
that
could
help
like
if
we
plement
that
first
then
maybe
maybe
we
can
so
like,
make
it
open
to
the
rest.
That's.
C
Like
personality
conflict
there
that
it
actually
was
a
very
good
thing
that
we
had
the
review
process
in
place
because
they
actually
prevented
what
could
have
been
kind
of
a
an
uncooperative
community
member
from
being
in
charge
of
a
rather
important
module.
And
he
was
doing
it
because
he
was
mad
at
drupal
and
which
isn't
very,
very
great
motive
to
be
minus
good.
Maintainer.
C
B
Do
we
still
have
I
mean
so
I
know
when
we
first
set
up
the
kinship
group,
anyone
whose
number
of
the
group
could
commit
to
any
project
and
so
having
that
agreement?
That
was
like,
don't
do
it
unless
it's
your
project
was
important,
but
we
don't
have
that
limitation
anymore
right
because
get
have
changed
the
way
their
permissions
work
so
that
people
can
own
their
own
projects.
Even
another
group
is
that
is
that
true
that.
B
Is
it
is
it,
but
maybe
we
should
look
into
changing
that
I
mean
I,
don't
I
think
maybe
like
we're
all
kind
of
on
the
fence
as
to
whether
this
is
a
good
idea
or
not.
But
if
we
look
into
figuring
out
if
it's
possible
to
change
an
existing
group
to
work
that
way
and
it
turns
out
not
to
be
that'll
answer
shin.
So
that's
one
thing
we
could
look
into
to
see
if
it's
even
possible
to
change
it.
If
it
is
possible,
then
that
brings
us
back
to
the
you
know.
B
Can
we
solve
most
of
our
review
via
automation
and
do
we
want
to
do
that?
Instead,
I
would
love
personally
to
lower
the
barrier
to
entry
to
getting
more
ACTRA
contributi
contributed
project
people,
whether
they're,
maintainer
zor,
just
throw
their
code
up
and
I,
don't
necessarily
see
a
downside
to
getting
a
ton
of
sandbox
projects
that
don't
end
up
having
official
releases
either
I
know
trying
to
find
things
on.
Github
is
hard,
but
I
feel
like.
B
C
Might
have
yeah
we
could
also,
if
we,
if
we
wanted
to
keep
the
agreement.
For
example,
we
could
also
add
a
button
like
on
backdrop
semester.
Org,
that's
like
here
is
how
you
have
to
apply
and
then
they'd
still
need
to
go
through
the
agreement,
but
the
agreement
basically
would
then
grant
them
access
to
the
repository
sort
of
thing,
which
would
also
be
kind
of
I.
Think
it's
important
that
we
keep
that
in
place
as
well.
D
You
can
probably
keep
it
somewhat
informal
in
that
you
know
ever
as
long
as
I
as
you
don't
there.
As
long
as
we
don't
commit
to
providing
people
access,
you
can
kind
of
open
it
up
a
little
bit,
but
you
keep
an
eye
on
it
and
there's
something
to
go
squirrely.
You
know
be
ready
to
jump
on
it
right
at
the
moment.
C
Yeah
yeahs
in
a
really
short
term.
We
also
could
just
go
back
to
the
current
applications
and
just
tell
people
hey.
We
don't
need
to
review
your
code
anymore.
You're
now
accepted
and
people
that
are
applying
applying.
If
they
just
file
an
issue
and
we
immediately
give
them
the
agreement
and
then,
if
they
agree,
then
then
we
let
them
in
and
we
just
get
the
modules
entirely.
So
that
would.
B
Make
is
it
I
think
that
would
be
good
too,
because
there
are
a
lot
of
people
who
are
like
I
want
to
join,
but
I
don't
have
any
code
and
then
we're
like
well,
you
could
become
a
co
maintainer
or
like
find
someone
to
help,
and
it
is,
it
seems
a
little
weird
where
it's
like,
if
you,
if
they
want
to
join
me,
want
to
let
them
join.
You
don't
have
to
have
good
today.
B
G
Are
you
guys
talking?
It
reminds
me
of
another
thing.
Sorry,
sorry,
I'll
avoid
that
answer.
For
just
just
a
moment
see
we
have
the
sandbox
that
the
pr
sandbox
is,
and
we
have
the
automated
and
stutter
as
well,
and
we
have
the
ability
to
point
to
repositories
or
the
vom
be
official
country.
So
you
have
people,
you
empower
them
to
have
a
server
somewhere
that
they
can
upload
any
model
they
they
create
doing
whatever
they
want
and
sort
of
like
I'm
using
our
server
to
do
whatever
their
model
does
so
I.
G
These
things
are
always
on
my
head,
I'm
and
I.
Understand
that
we
need
to
lower
the
barrier,
but
perhaps
we
can
put
a
war
is
not
online.
Now
you
went
away
back.
Perhaps
we
can
automate
that
by
implementing
some
karma
points
system
or
something
like
that.
So
if,
if
other
people
actually
recommend
or
this
but
main
thing
just
ideas
popping
in
my
is
like
we
cannot
simply
allow
someone
that
has
created
a
jit,
have
proper
profile
the
past
day
and
give
them
full
access.
That's
you
know,
I
mean.
G
B
Contributes
an
official
release,
it'll
show
up
in
project
browser
and
other
people
can
install
things
that
may
be
malicious.
It
will
be
really
easy
for
them
to
install
things
if
there's
no
review
process
anywhere
along
the
way
there.
So
if
we
could
automate
something
that
would
do
a
test
that
would
be
fine
on
even
on
the
like
published,
a
vector
of
CM,
esta
or
step,
but
leaving
it
open,
especially
for
like
robots
to
comment
into
it
would
be
bad
news.
B
C
B
Mean
I
think
I
think
it
ever
started
to
give
access
to
the
contribute,
but
I
didn't
I
do
see
the
worry
about
skipping
the
code
review
in
letting
them
publish
official
release
that
shows
up
on
factor
of
CMS
org
in
in
the
project
installer,
so
I
think
we
should
not
step
skip
the
code
review
at
all
until
we
make
sure
that
we
have
the
right
kind
of
protections
on
the
publish
project,
part
of
the
step.
Otherwise
we
could
end
up
with
malicious
robots,
doing
whatever
to
everybody's
websites.
Oh.
C
Robots
well,
no,
no
I'm
talking
about
like
so
the
people.
They
still
need
to
go
through
the
agreement,
so
they
don't
need
to
post
an
issue
to
the
backdrop,
ops,
/,
contribute
group
and
say
I
would
like
to
join
and
we
say:
okay
I'm,
going
to
look
at
your
account,
see
who
you
are
and
then
I'm
gonna,
say:
okay,
you
look
fine,
here's
the
agreement
and
if
there's
something
suspicious,
then
I
would
ask
them
a
question
about.
Like
you
know,
happy
worked
with
Drupal
before
have
you
worked
with
vector
before
or
something
to
validate?
C
Yeah
and-
and
that
would
be
it
right
and
so
I
mean
yeah
right
right
now.
I
was
mostly
just
saying:
we
can
still
have
an
acceptance
policy,
but
we
would
just
own
it.
The
code
review
from
it
and
John
Taylor
actually
posted
over
here
in
the
agenda
chat
that
a
new
contributor
should,
of
course
be
able
to
request
a
review
or
request
help
if
they're
nervous
about
their
own
code
quality
and,
of
course
we
would
help
them.
B
B
C
We
can
add,
we
can
change
your
process
so
that
it
would
be
user
user
post
request.
We
respond
with
boilerplate
type
response
that
says,
you
know,
welcome
to
the
contribute
and
welcome
to
the
community.
Would
you
like
a
review
of
your
code?
If
so,
please
let
us
know
where
it
is.
You
know
this
step
is
optional.
If
you
would
just
like
to
commit,
then
please
let
us
know,
and
then
they
respond,
and
then
we
posted
you
know
either
either
feedback
or
or
just
the
agreement
in
them.
B
C
Okay,
yeah
everybody
science,
a
groom,
is
best
okay.
Let's,
let's
move
this
offline
from
our
online.
Let's
move
it
online
into
into
the
back
drop
off
/
contribs,
because
that's
also
where
we
discuss
the
processes
around
Caen
trip
and
we
can
kind
of
outline
a
you
know
what
we've
discussed
here
as
well
as
they
deposed
skipping.
The
review
step.
Gregory
could
I
ask
you
to
write
that
up.