►
Description
Backdrop CMS is a member organization of the Software Freedom Conservancy. In this discussion, we talk about:
1) What is the Software Freedom Conservancy and what do they do?
2) An update on the new "Get off of Github" campaign that the SFC is leading.
3) Other opportunities for Backdrop CMS to work with the Software Freedom Conservancy.
B
Yeah
yeah,
I'm
sure
I'm
pono
I've
been
with
conservancy
for
a
little
bit
over
a
year.
Now
I
help
do
community,
organizing
for
conservancy
and
social
media
and
some
other
efforts.
I
used
to
be
a
software
engineer
and
have
moved
in
the
more
non-technical
role,
so
I've
been
excited
to
work
on
that
and
yeah.
B
I
prepared
a
couple
paragraphs
about
kind
of
just
an
update,
so
if
that,
if
that
sounds
good,
then
cool
yeah,
so
we've
been
staffing
up
so
we're
currently
at
six
and
a
half
employees,
which
is
the
largest
the
organization's
ever
been
we're
also
growing
in
projects.
So
that's
those
are
sort
of
two
tensions,
but
we're
really
hopeful
that
we're
able
to
handle
more
tasks
and
keep
up
with
some
of
the
things
that
we've
been
able
to
in
the
past.
We've
got
a
chat
service,
so
we're
on
irc
and
xmpp.
B
C
B
Focusing
on
making
a
lot
more
material
for
people
outside
of
the
normal
free
software
movement,
I
think
that's
been
a
real
like
that's
been
a
difficulty
for
us.
Communicating
in
the
past
is
just
letting
people
know
that
software
freedom's
for
everybody,
not
just
for
developers
and
free
software
developers,
particularly
so
we
we,
we
made
a
a
new
introduction,
video
to
kind
of
what
we
do
and
we're
really
excited
about
that
and
think
that
it
really
communicates
a
lot
of
the
ideas
that
we
hold
dear
to
the
general
public.
B
So,
like
I
mentioned
before,
we're
working
with
outreachy,
so
outreach
is
a
conservancy
project
and
they
provide
internships
for
historically
excluded
people.
Right
now.
In
this
may
session,
we
had
over
468
people
apply
for
66
internship
spots,
so
this
is
one
of
the
biggest
rounds
we've
ever
had
and
at
the
end
of
this
session,
we'll
have
had
a
total
of
over
900
internships
for
for
students
and
people
all
over
the
world,
which
is
really
great.
There's
a
couple.
B
B
So
if
anybody's
around-
for
that
please
come
say
hi,
and
so
with
that
we've
sort
of
been
amending
our
travel
policy
and
as
the
situation's
developing
we're
talking.
Other
folks
and
you
know
backdrop-
is
leading
the
way
on
how
to
do
an
online
conference.
So
it's
really
cool
to
see
some
other
updates
are
so
we've
got
the
lawsuit
against
vizio.
The
idea
here
is
that
we're
opening
a
new
legal
path
for
end
users
to
be
able
to
be
treated
as
equal
parties
in
use
of
the
gpo.
B
So
the
idea
is
that
a
third-party
beneficiary
is
an
end
user.
In
the
past,
we've
typically
only
been
able
to
bring
copyright
cases
with
people
that
have
written
code,
not
consumers
of
code,
but
we
think
that
users
are
just
as
equal
participant
as
developers
when
it
comes
to
this,
so
we
had
a
preliminary
hearing
in
may
and
that
went
really
well
and
so,
as
things
develop,
we're
excited
to
keep
everybody
apprised
yeah
and
then
the
other.
The
other
campaign
that
that
we
just
announced
a
couple
weeks
ago.
B
Is
this:
give
up
github
campaign
after
a
year
of
trying
to
get
into
contact
with
microsoft
and
talking
to
everybody
there
and
at
github
they've
got
a
product
called
copilot
which
has
consumed
all
of
the
all
this
code
on
github
and
uses
machine
learning
as
a
trained
algorithm
to
produce
new
code
and
microsoft's
assertion
is
that
this
is
that
the
copyright
belongs
to
the
user
that
used
co-pilot.
However,
we
take
issue
with
this
because
we
think
that
you
know
public
license.
B
Code
belongs
under
the
license
and
needs
to
be
treated
as
such,
and
so
this
is
sort
of
a
long
string.
The
last
event,
in
a
long
string
of
things
where
we've
been
trying
to
talk
with
microsoft
and
github
about
their
about
their
politic
around
these
things,
and
so
we're
asking
projects
to
to
move
off
of
github.
D
B
But
this
is
sort
of
like
a
problem
we've
seen
over
the
years
where
companies
will
donate
resources
to
free
software
projects
and
then
you're,
enticed
for
a
couple
years.
But
then,
once
the
free
credits
run
out
now
you're
sort
of
locked
in
to
this
wild
garden
of
products.
We've
seen
this
recently
with
the
cancelling
of
cloud
computing,
storage
and
cloud
computing
resources
for
a
lot
of
conservancy
projects
where
they've
been
on
certain
cloud
hosters
with
free
resources.
B
B
I
think
that's
kind
of
a
nice
update
and
I'm
curious
if
there's
any
questions
or
anything
that
people
wanted
to
talk
about.
In
regards
to
that,
I
know
that
particularly
the
github
campaign.
People
have
a
lot
of
thoughts
on,
and
so
I'd
love
to
be
able
to
hear
concerns
and
hear
hear
what
people
were
thinking
about
that.
So
one
thing
I
would
like
to
add
is
that
we're
not
asking
any
of
our
projects
to
get
off
of
github.
B
We
know
that
you
know
what's
best
for
your
communities,
and
this
is
really
a
public
campaign
to
talk
more
about
the
issue
more
openly
and
as
as
we've
we've
drawn
sort
of
these
lines
in
the
sand.
We
realize
that
not
all
the
projects
are
going
to
agree
with
us
and
we
do
welcome
the
conversation
and
want
to
make
sure
that
there's
no
pressure
or
no
no
feelings
of
animosity
there.
We
support
you
in
your
decision.
A
A
B
And
I
think
that
there
is,
I
think,
that's
a
really
good
point
because,
like
I
think
that
it's
a
really
nuanced
issue
that,
like
I
think
it's
important
for
us
to
to
take
a
harder
stance.
But
I
I
do
think
it
is
important
to
recognize
that
they
have
been
doing
a
lot
more
efforts
in
in
development
with
open
source
over
the
past.
You
know,
let's
say
five
years,
versus
what
their
opinion
was
in
the
in
the
late
90s
and
early
2000s.
A
A
Drupal
was
around
before
github
and
they
did
have
to
build
all
of
their
infrastructure
themselves
from
scratch,
and
that
was
a
huge
expense
in
resource
sync
for
developers
who
could
have
been
working
on
the
project.
So
the
fact
that
we
were
able
to
just
sort
of
get
up
and
go
without
that
was
really
beneficial
to
backdrop.
We've
also
found
a
lot
of
benefit
in
just
being
where
all
the
developers
are.
A
A
Aficionados
just
grab
good
first
issues
and
contribute
to
our
project,
even
if
they
know
nothing
about
it,
just
because
they
want
to
work
on
open
source,
and
so
that's
something
that
we
also
benefit
a
lot
from
not
having
to
do
as
much
outreach
in
order
to
find
people
to
work
on
our
projects.
So
yeah
there's
a
lot
of
things
that
immediately
come
up
as
oh.
A
No,
if
we
have
to
get
up
get
up
it's
to
be
so
much
work,
so
much
more
work
for
us,
but
it
is
definitely
something
to
keep
in
mind,
especially
when
it
comes
to
not
treating
the
open
source
licenses
the
way
they're
supposed
to
be
treated,
because
that's
something
that's
really
important
to
us,
obviously
being
a
project
that
was
able
to
fork
because
of
the
license.
We
still
you
know
have
that
license.
A
We
understand
some
of
the
nuance
about
you
know
having
software
become
infected
with
the
license
of
its
parent
software,
just
with
the
nature
of
backdrop,
plus
all
of
its
modules,
so
yeah
thinking
about
how
a
big
organization
might
choose
to
not
respect.
That
is
something
that
we
need
to
sort
of
consider
about
where
we
would
stand
on
something
like
that.
So
excellent,
yeah.
B
Yeah,
I
think
your
your
comments
about
like
github
being
giving
you
the
tools
to
be
able
to
fork
and
build
a
community.
I
think
that's
a
really
really
good
one,
and
I
think
that,
like
you
know,
of
course
these
are
valuable
tools,
and
so
I
think
that
that's
that's
definitely
an
aspect
of
the
problem
that
it's
great
to
hear
that
people
have
been
able
to
build
that
community
and
and
the
issue
with
newcomers
I
think,
is
a
really
really
good
one.
D
A
A
Of
developers
are
already
there
where,
like
I,
I
think
I
have
a
gitlab
account,
but
it
was
part
of
some
client
project
that
I
was
on
a
long
time
ago,
like
I
don't
have
my
own
stuff
over.
It's
just
not
quite
not
quite
the
same
and
then
like
when
we
go
to
participate
in
things
like
open
source
day
like
events
but
in
tan
and
tangentially
relate
to
something
their
requirements
are
like.
A
A
We've
also
built
a
lot
of
custom
integration
with
github,
maybe
not
a
lot
some
custom
integration
with
github.
That
would
we
would
just
need
to
reinvest
that
into
what
other.
Whatever
other
platform
we
chose,
there's
like
a
small
technical
cost
there
in
just
not
just
moving
but
also
re
reintegrating
in
various
ways
like
our
project
system,
is
all
integrated
with
all
of
the
releases
and
stuff
the
way
they
come
out
on
github
and
the
air
apis.
A
So
yeah
there's
just
some
some
cost
there,
but
yeah.
I
think.
Technically,
there
are
a
lot
of
platforms
that
are
equivalent
in
terms
of
what
they
offer.
There
are
probably
some
platforms
that
offer
better
features
that
might
be
a
better
fit
for
us,
but
the
community
aspect
and
the
brand
recognition,
I
think,
outweigh
the
technical
benefits
we
might
get
from
a
different
option.
D
B
Like
it
feels
it
feels
difficult
to
have
the
conversation
of
this
large
issue,
we're
trying
to
tackle
when
we're
asking
individuals
to
sort
of
like
make
an
effort
to
solve
a
systemic
problem
yeah.
So
we
really
want
to
be
conscious
about
how
that
affects
communities
and
so
yeah.
I
do
just
want
to
reiterate
that
you
know
your
communities,
and
so
we
we
trust
you
to
make
that
make
those
decisions.
B
B
To
give
is
open
source
yeah,
yeah
git
is
with
open
source,
which
is
really
nice,
because
that
means
that
your
repositories,
you
can
move
over
to
ditsy,
to
get
lab
to
code
bird
source
sites.
All
these
other
places,
which
is
really
easy,
the
github
interface
is
not,
and
so
that's
all
proprietary
there's
a
bunch
of
proprietary
features
built
on
top
of
git,
which
does
make
it
harder
to
leave
so
like
wikis
and
issues
are
really
hard
to
export.
That's
one
problem.
B
Another
problem
that
we've
been
hearing
more
as
we've
been
going
into
this
process
is
that
github
has
had
a
lot
of
work
done
as
far
as
its
accessibility
of
interface
goes
and
a
lot
of
these
free
software
alternatives
have
some
are
really
lacking
in
accessibility
options,
so
it
does
feel
negligent
to
sort
of
talk
about
this
sort
of
mass
migration.
Without
acknowledging
that,
like
there
is
this
huge
upside
to
having
really
accessible
options,
both
you
know
from
a
financial
aspect
and
from
a
usability
aspect.
B
B
Right
right,
so
so
git
lab
is
sort
of
the
one
that
people
point
to
as
sort
of
a
feature
by
feature:
parity
kind
of
equivalent,
there's
a
couple
different
tiers.
So
there's
the
the
enterprise
edition,
which
I
think
was
the
one
that
was
linked
and
then
the
community
edition.
The
community
edition
is
free
software.
The
enterprise
edition
is,
has
their
own
kind
of
special
sauce
wrapped
up
into
it,
and
then
you
pay
for
that.
B
There's
also
options
like
codeberg,
which
is
built
on
getty,
so
those
have
some
really
nice
interfaces,
but
again
when
you're
competing
with
such
a
enterprise
scale
software
like
github,
it's
going
to
be
hard
to
even
get
feature
parity
and
all
those
other
things
so
yeah,
yeah,
there's,
there's
huge
trade-offs
between
between
these
programs.
And
you
know,
accessibility
is
one
aspect
feature
parodies
another
I
think
community
is
the
biggest
one
is
just
getting
enough
community.
A
Yeah,
I
think
it's
important
to
sort
of
keep
an
eye
on
what
everyone
else
is
doing
too,
because
I
think
if
you
can't
get
enough
people
in
mass
to
be
like
no,
we
won't
stand
for
this
and
move
somewhere
else.
Then
it
makes
sense
for
us
to
be
part
of
that
movement
too,
because
what
we
want
to
be
is
where
everywhere
else,
when.
A
I
think
everyone's,
probably
having
that
same
like
what
what's
everyone
else
doing
kind
of
moment,
because
there
are
a
lot
of
projects
that
probably
benefit
just
from
everybody
being
in
the
same
place.
So
if
everybody
moved
somewhere
else,
then
it
wouldn't
matter,
we
would
still
get
the
same
benefit
that
we
get
now
from
being
on
github.
A
C
B
You
know
you're
not
going
to
get
everything
that
you
want,
you're
going
to
have
to
make
some
compromises,
and
I
think
that
demonstrating
that
and
that
part
of
the
nuance
will
really
both
catalyze
people
to
move
because
it'll
be
demonstrated
that
projects
are
doing
it
but
also
bring
to
light
some
of
the
pain
points
of
just
where
the
free
software
movement
is
lagging
behind.
But.
C
D
We
have
in
our
core
issue
key.
We
have
2.3
000,
open
issues.
You
know
we're
approaching
6
000
total
issues
including
closed
issues
which
now
the
numbers
themselves
may
not
matter.
If
the
right
tools
are
there
to
move
them,
but
I
think
the
numbers
matter
if
the
right
tools
aren't
there,
for
example,
if
we
can't
move
our
if
we
can't
easily
move
our
issues
and
we've
got,
you
know,
2
000
open
issues,
some
of
which
have
been
open
for
five.
D
B
Yeah,
just
attracting
users
across
systems
is
a
really
hard
problem.
So
I
linked
the
mailing
list
where
we've
got
some
discussion
and
people
talking
about
some
of
the
migratory
issues
and
that
kind
of
thing
but
yeah,
just
even
giving
people
credit
from
github
in
a
repository
on
another
platform,
is
sort
of
an
open
problem.
If
you're
using
a
bunch
of
different
email
addresses
unifying
that
and
giving
people
credit.
Is
that
that's
sort
of
an
unsolved
problem
and
yeah?
D
B
That
I
think
that,
like
you,
knowing
github
and
knowing
how
your
community
uses
it
is,
is
a
benefit
so
like.
I
don't
think
that
I
don't
think
that
the
you
know
we
want
to
say
you're
the
biggest,
so
it's
most
important
for
you
to
give
it
up.
I
think
that
it's,
it's
almost
better,
in
a
sense
to
say,
you're
you're,
a
very
productive
user
of
this
tool.
So
you
know
better
than
most
about
how
it's
used
in
a
variety
of
community
settings.
A
Yeah,
but
I
do
think
that
each
community
probably
uses
it
in
slightly
different
ways,
and
I
think
that
you
know
like
we
don't
use
the
wikis
very
much
and
just
the
way
our
community
tends
to
operate.
There's
so
many
pages
out
there,
but
they're
not
collaborative
documentation
in
the
way
that
other
projects
use
them,
and
there
are
probably
other
issues
that
are
other
projects
that,
like
don't
use
the
issue,
queue
the
way
we
do.
A
B
Right
and
I
think
that
that
also
brings
to
light
sort
of
one
of
the
one
of
the
problems
and
why
we
think
it's
important
to
move,
which
is
that,
like
when
we're
when
we're
all
rely
upon
upon
one
proprietary
system,
we
do
need
to
use
match
our
workflows
to
what's
available
there.
So
I
think
that,
like
in
this
abstract
sense,
that's
something
that
we
that
we
are
looking
to
the
foss
options
to
sort
of
liberate
us
from,
but
also
people
are
really
robust
and
versatile
and
will
figure
out
creative
ways
to
do
things.
B
D
So
you
know
I
looked
at
the
900
repos
and
I
think
about
how
one
might
make
the
argument
that,
like
we
could
never
change
because
of
that,
but
it
also
it
occurred
to
me,
as
you
started
talking
today,
that
the
risk
is
the
other
way
as
well,
which
is
that
if,
for
example,
microsoft
decides
to
suddenly
they're
going
to
start
charging
for
repo
at
some
point
in
the
future,
our
risk
is
much
higher.
If
we
don't
think
about,
if
we
don't
have
a
backup
plan
right.
D
B
One
of
the
things
that
I
really
respect
about
backdrop
is
the
use
of
zulip.
I
think
that
not
being
on
slack
is
huge.
I
think
that
being
on
an
open
chat
platform
means
that
you
do
have
some
sense
of
where
your
community
is
so,
even
if
you
were
cut
off
from
that.
That's
that's,
really
huge,
there's
so
many
projects,
so
many
free
software
projects
that
are
being
developed
on
proprietary
chat
systems
and
that's
something
that
really
scares
me.
So
I'm
really
like
happy
that
that
that
platform
exists.
D
Yeah
there
was
a
group
of
us
yeah,
so
I
mean
I
in
general.
I
think
we
try
to
think
about.
You
know
how
to
the
larger
free
software
community
when
we
make
decisions
but
we're
not
as
embedded
in
it
or
as
connected
as
maybe
other
projects
are
in
some
ways.
Sometimes
I
feel
like
we're
off
in
our
own
and
I'm
speaking
for
myself
here
john
might
feel
differently,
but
I
do
feel
sometimes
like.
D
I
should,
because
I
think
I'd
have
a
lot
to
gain
and
learn
from
that,
but
I
haven't,
and
I
need
to
figure
that
out,
and
so
you
know
some
of
it
is
just
being
aware
of
what
the
options
are,
because
to
be
honest,
most
of
them
don't
come
across
my
desk.
I
often
learn
about
the
opportunities
after
they've
happened
or
when
I'm
seeing
all
the
tweets
in
the
middle
of
the
right
that
somebody's
had.
B
Yeah
yeah,
I
think
you
bring
up
a
really
good
thing.
I
think
I
think
that
that
that
is
one
place,
that
conservancy
could
do
a
lot
better
is
getting
our
member
projects
to
talk
to
each
other.
You
know,
there's
a
lot
that
that
sort
of
we
gate
that
there
there
could
be
a
lot
of
trading
of
information
between
projects
so
yeah.
B
I
think
that
two
of
the
things
that
are
on
my
plate,
that
I'm
hoping
to
to
get
up
pretty
soon
or
one
is
a
member
project
handbook
for
advice
on
governance
and
reimbursement
and
these
kind
of
things,
but
also
just
a
chat
room
for
member
projects
to
to
talk
to
each
other.
I
think
that
you're
right
that,
like
there's,
there's
so
much
information
in
the
free
software
and
so
much
community
there,
but
just
tapping
into
it,
is,
is
sort
of
you
know.
We
are
all
in
our
own
silos.
B
A
I
wonder
if
it
might
be
valuable,
so,
like
you
know,
we
would
be
happy
to
set
aside
an
sfc
slot
at
every
backdrop.
Live
it
doesn't
mean
you
have
to
be
here,
but
we
could
invite
other
member
projects
if
they
wanted
to
drop
in
and
just
talk
about
things
like
governance
and
accounting
or
whatever
things
that
affect
open
source
projects.
A
I
think
that
would
be
good,
but
it
might
be
better
rather
than
having
it
like
a
specific
backdrop
live
event,
do
something
like
offcon
right,
where
it
would
be
not
just
sfc
projects,
but
it
could
be
like
anyone
who's
an
open
source
software
leadership
person,
in
whatever
role
that
is,
could
attend
and
have
some
sort
of
a
structured
conversation
about
it
there
too,
and
that
might
be
something
that,
like
tim
and
I
would
find
out
about
oscar
because
there's
this
dedicated
spot
there
specifically
for
that
sort
of
thing.
So
that
could
be
something.
D
B
So
yeah,
I
think
that
I
think
that
you're
right,
I
think
that
there's
a
lot
of
these
conversations
happening
among
the
ospos
and
among
the
corporate
channels
that
are
that
are
doing
their
own
sort
of
big
money
open
source.
But
I
think
that
the
the
the
sort
of
smaller
project
governance,
let's
talk
and
build
community.
I
think
that
is
a
space
that
that
would
be
really
really
valuable
to
a
lot
of
people.
So.
C
B
D
C
B
D
D
D
A
D
Just
go,
let
me
say
one
more
thing
and
then
you
can
talk,
but
in
case
jen
is
scratching
your
head
and
wondering
what
I'm
talking
about.
My
idea
would
be
that
you
know.
Maybe
we
did
a
fundraising
drive
or
something
to
raise
funds
to
hire
an
intern
through
a
program
like
the
ones.
You
seem
to
be
talking
about
to
work
on
some
particular
issues
within
the
queue
or
something
I
don't
know
that
we
identify.
D
B
Yeah
yeah
yeah,
so
we've
had
we've
had
a
lot
of
conservancy
projects
that
have
participated
in
outreachy,
so
outreachy
has
had
over
40
communities
and
85
individual
software
projects
that
interns
have
worked
on,
but
the
goal
is
to
sort
of
pair
up
an
intern
and
then
get
them
embedded
in
the
community,
so
they're
getting
mentorship
they're
getting
connected
they're
working
on
their
technical
skills,
their
non-technical
skills
so
yeah.
We
should
absolutely
talk
about
that.
B
D
D
People
like
this
idea,
but
I'm
intrigued
by
it,
and
I
think
we
have
a
community
that
would
support
an
intern,
that
we
have
some
skill
developers
who
like
to
help
beginners
and
that
we
would
be
able
to
provide.
You
know
that
it
would
be
a
very
much
a
two-way
street
where
we
could
support
and
you
know
and
provide
guidance
and
mentorship
towards
an
intern.
But
but
I
need
to
talk,
you
know
we
need
to
talk
to
the
community
about
that.
That's
just
my
idea.
Oh.
C
D
C
So
then
there
should
be
software
projects
to
replicate
that
functionality
so
that
it's
available
in
an
open
source
format
and
yeah
seems
like
there
needs
to
be
some
fundraising
from
somewhere,
and
I
don't
know
where
that
money
would
come
from,
but
there
must
be
someone
who
has
an
interest
in
open
source
that
would
maybe
fund
those
things.
You're
saying
corporations.
Businesses
are
funding
open
source
projects
if
it's
to
their
benefit,
and
if
it's
true
that
all
of
a
sudden,
microsoft
could
start
charging
for
things
that
people
are
using.
B
You
know
I
would
have
given
an
arm
and
a
leg
for
that,
and
this
is
sort
of
a
free
thing
that
you
get.
That's
one.
That's
one
thing,
so
I
think
that
you're
right
that
they're
trying
to
figure
out
which
companies
are
using
this
and
trying
to
see
if
we
could
get
them
to
help
fund
development
of
this
right.
B
Now,
we're
really
fortunate
that
there
are
some
organizations
we
work
with
the
osu,
the
oregon
state
university,
open
source,
lab
and
they're
working
on
building
out
a
replacement
for
this
kind
of
feature
for
git
lab.
So
this
is
like
one
place
where
we've
been
able
to
direct
some
money
to
an
organization
to
replace
you
know
a
little
bit
of
it
to
replicate
the
the
functionality.
That's
that's
over
there.
B
A
A
It
was
really
slow
and
we
had
to
like
optimize
all
of
our
tests,
make
it
work
there,
and
then
it
was
like
wait
a
minute.
We
can
get
this
on
get
up,
and
so
we
moved
everything
over
yeah,
so
yeah
I
had.
I
hadn't
even
considered
that
as
being
one
of
the
add-ons
that
we
rely
on
so
heavily
from
github.
This
is
the
kind
of
thing
where
it'll
be.
Do
you
know
if
there's
like
a
checklist
for
moving
off
of
gitlab?
It's
like?
Do
you
use
any
of
the
following
features?
B
B
D
B
You
know
we
do
want
people
to
have
a
realistic
sense
of
the
kind
of
resourcing
that
they're
getting
for
free,
and
this
kind
of
subsidized
cost
is
like
you
know,
such
a
boon
to
projects
that
it's
really
hard
to
ask
people
to
spend
their
own
limited
resources
to
to
do
that
so
yeah
yeah,
but
the
ci
is
a
huge
one
right
now.
So
that's
that's
a
problem
that
I've
been
working
on
for
the
past,
like
three
or
four
years,
is
how
to
how
to
get
better
ci
for
projects.
B
A
Another
thing
that
we
found
really
valuable
is
the
fact
that
we
can
have
people
contribute
to
our
project
using
the
edit
interface
on
github
yup.
So
they
don't
need
to
worry
about
setting
up
a
local
environment
because
they
can
change
the
code
file
file,
a
pull
request.
The
pull
request
opens
a
sandbox
where
they
get
a
fresh,
install
of
backed
up
with
their
changes
on
it
and
runs
all
of
the
tests,
and
so
we
don't
even
need
people
to
have
local
development
environments
anymore.
A
C
A
Was
going
to
say
that
drupal
already
built
all
of
their
solutions
before
github
existed,
so
they
already
had
an
issue
queue.
They
already
had
a
test
system.
They
already
had
a
process
for
all
of
this.
They
don't
have
all
of
the
features
to
github
has
but
they've
created
a
workflow
around
it,
and
so,
when
they
moved
to
get
lab,
they
only
brought
the
list
of
like
this
is
our
set
of
requirements
is
what
we
have
currently
and
they're,
making
sure
that
maps
to
what
they're
getting
from
gitlab.
A
A
I
think
they
are
already
investing
in
drupal's
implementation
on
gitlab,
I'm
not
sure
how
much
of
that
is
turning
into
an
open
source
alternative
or
how
much
of
it
is
direct
integration
for
the
drupal
project.
So
you
know
it's
really
easy
to
create
tools.
It's
really
easy
to
create
a
direct
integration
for
your
your
custom
system,
but
it's
really
hard
to
create
a
public
tool
to
solve
the
need
for
the
custom
integration
of
your
system.
A
A
D
I
think
it's
important
to
know
that
they
just
took
like
two
years
to
decide
on
using
git
lab
like
about
two
years
ago
or
three
years
ago
right,
so
they
you
know,
I
would
probably
would
probably
be
pretty
hard
for
them
to
turn
around
and
move
or
do
something
different
right
now,
because
they
went
through
a
long
process
to
find
an
alternative.
They
settled
on
github,
and
that
was
really
just
about
three
years
ago.
I
think
so.
B
Right
but
right,
like
jen,
pointed
out
one
of
the
problems
is
that,
like
even
if
gitlab
supports
it,
you're
gonna
build
your
own
workflow
around
that,
so
even
if
they
have
invested
a
lot
of,
it
is
going
to
be
personal
to
them,
which
is
just
sort
of
an
unfortunate
problem
that
all
projects
will
have.
It's
really
hard
right
now,
there's
not
really
an
open
standard
for
this
kind
of
testing
suite.
So
since
people
did
so
much
development
on
github
sort
of
the
ways
that
people
are
even
thinking
about,
the
problem
are
shaped
by
that.