►
From YouTube: Shifting Perspectives - Ed Veal & Jessie Zairo
A
B
A
Jay
z
and
I
worked
together
for
okay
jesse,
and
I
worked
together
for
a
couple
a
couple
of
years.
I
guess
when
I
was
with
bywater
and
we
did
a
lot
of
the
training
and
we
traveled
a
lot.
So
where
is
our
introductory
picture
come
on
there?
It
is
there
we
are
what
we're
going
to
be
talking
about
is
I
don't
want
to
call
them
misconceptions,
but
the
differences
between
working
with
a
proprietary
vendor
and
working
within
the
open
source
community.
A
Okay,
we're
going
to
talk
about
some
of
those.
You
know
the
differences,
how
they
pros
and
cons
all
of
those
kinds
of
things.
I
hear
a
lot
of
people
without
knowing
it
equating
by
water
and
quahog
and
that's
not
the
same
koha
is
an
open
source.
Software
bywater
is
a
support
vendor
we're
talking
about
that
in
some
detail
as
we
go,
so
let's
go
ahead
and
get
started
here.
There
are
lots
of
open
source
software
packages
out
there,
a
lot
of
which
you
probably
use
without
even
knowing
it.
You
know
things
like
firefox.
A
What
are
some
of
the
other
ones
on
here
vlc
we
have
recent
yeah.
We
have
recently
moved
to
open
office
or
libra
office
on
all
of
our
public
computers,
away
from
the
microsoft
suite
I'd
like
to
say
it
saved
us
some
money,
but
it
didn't
because
it's
a
city
contract,
but
it's
just
where
we
want
to
go.
We
are
interested
in
open
source.
What
that
means,
what
you
know
the
community.
So
we've
made
that
decision
a
number
of
other
sources
here.
Jesse
do
you
have
any.
B
Yeah,
you
know
is
another
option
for
those
of
you
who
want
to
use
photo
editing,
that's
a
great
one
for
photo
editing
gitlab.
So
if
you
ever
go
and
use
the
koha
community
manual,
gitlab
is
what
we
use
to
edit
that
document
and
and
have
that,
go
live
and
I'm
sure
people
have
used
wordpress
at
one
point
in
their
life,
whether
it
was
a
personal
blog
or
a
blog
for
a
girl
scout
troop
or
community
church.
A
All
right
we're
going
to
move
into
the
myths
and
the
reality.
There
are
a
lot
of
myths
out
there
about
open
source
and
then
there's
what
reality
is.
So,
let's
look
at
a
couple
of:
let's
look
at
security
to
start
with
there's
this
idea
that
open
source
is
less
secure.
If
you
talk
to
your
I.t
department,
they
tend
to
be
microsoft-centric
and
so
they're
going
to
naturally
say
you
know.
This
is
not
the
party
line.
We
can't
do
open
source,
it's
not
secure.
We
can't
they're,
you
know
we
don't
have
all
of
these
patches.
A
We
can't
do
our
job,
because
it's
this
unsecure
thing
that
is
not
truly
the
case.
Reality
is
open.
Source
can
be
much
more
secure.
There
are
so
many
more
eyes.
Looking
at
the
open
source
world
when
bugs
appear
when
security
holes
are
discovered,
the
volume
of
coders
and
people
out
there
that
find
them
patch
them
and
get
those
patches
out
at
a
much
more
rapid
pace
than
the
proprietary
world.
That
is
really
the
reality.
B
Yeah,
that's.
That
is
probably
the
number
one
thing.
The
number
one
question
that
we
get
when
we
go
out
and
we
talk
to
libraries.
You
know
they've
been
on
proprietary
systems
like
cersei
or
triple
I
for
20-plus
years,
and
they
get
really
really
nervous
about
moving
to
open
source
because
they've
heard
all
of
these
myths
throughout
the
years-
and
this
is
just
one
of
them
and
of
course
our
next
one,
where
I
think
we'll
talk
about
access
or
I.t
staff,
I.t
staff-
you
know-
that's,
that's
probably
the
next
one
we
hear
it's.
B
You
know
I
need
a
full,
robust
staff
to
deal
with
open
source
and
by
attending
this
conference
today,
I'm
sure
you've
heard
a
lot
of
people
talk
about
it.
There
are
multiple
support:
vendors
throughout
the
us
and
worldwide
that
support
different
open
source
projects.
I
heard
cecilia
mentioned
this
morning,
omeka
in
in
her
presentation.
You
know:
there's
vendors
out
there
that
support
that
subjects,
plus
another
popular
open
source
platform
very
similar
to
libguides.
You
know
there
are
vendors
throughout
the
the
world
that
support
them
and
they're
there
to
be
your
I.t
staff.
A
All
right
support,
as
jesse
was
just
saying
there
are
a
lot
of
different
support
companies
out
there.
There
is
a
great
deal
of
support,
there's
also
community,
and
that's
what
I
think
is
missing
in
a
lot
of
the
proprietary
world.
The
community
that
builds
around
open
source
software
is
is
amazing
and
it
doesn't
matter.
The
software
coha
is
a
great
example
of
it,
but
there's
great
communities
that
build
around
all
sorts
of
different
open
source
packages
through
the
koha
community.
A
B
You
know
I
I
will
just
echo
what
ed
says
about
community
if
anyone
attended
the
last
session
with
sam,
where
he
was
talking
about
aspen,
that's
how
I
met
mark
at
a
kohai
u.s
session
back
in
2019
and
pueblo
mark
was
talking
about
an
open
source
discovery
platform,
and
so
you
meet
so
many
more
people
you
find
out
about
products
that
you
haven't
known
and
there's
this
huge
support
network,
whether
you
have
a
small
question
or
a
large
question.
You
have
a
whole
community
of
users
to
communicate
with.
A
A
A
He
frequently
reaches
out
for
help
to
the
community
and-
and
he
provides
great
deals
of
help
to
other
members
of
the
community
I'll
give
fred
a
plug
here,
he's
doing
the
presentation
on
taking
coho
where
it
was
never
intended
to
go.
He's
done
wonderful
presentations
in
the
past
things
like.
If
you
have
a
hundred
dollars,
you
can
have
an
ils.
He
spun
coha
up
on
a
raspberry
pi
and
has
it
working
beautifully.
B
This
is
a
this
is
another
big
one.
We
hear
all
the
time
anyone
can
change
the
code.
You
know
the
reality
here
is.
There
is
a
lot
of
back
movement
that
happens
behind
the
code,
so
you
know
the
process
from
start
to
finish
with
any
open
source
product.
Is
you
have
some
type
of
platform
that
tracks
all
of
these
changes,
whether
it's
an
enhancement
or
a
bug
fix?
B
It
goes
through
a
process
of
quality
assurance,
and
then
it
makes
it
goes
through
a
process
of
making
sure
that
the
manager
for
that
particular
release
approves
it,
meaning
it
doesn't
break
anything
else
in
the
system
while
it
goes
through.
So
there
is
a
lot
of
moving
pieces
before
anyone
can
change
the
code
when
they're
getting
into
the
system.
A
I
want
to
take
this
in
a
slightly
different
direction
as
well
the
myth
anyone
can
change
the
code
is
also
a
reality.
If
you
download
the
software,
you
run
it
on
your
machine.
You
can
do
anything,
you
want
with
it.
It's
open
source,
it's
yours,
you
can
do
it,
you,
you
download
it
you
break
it,
you
fix
it!
That's
where
the
idea
of
needing
huge
it
stats
come
from,
because.
C
A
D
A
That
during
cephelia's
presentation
this
morning,
she
mentioned
a
number
of
other
open
source,
ils
type
things.
There
are
a
number
of
them
that
were
up
on
that
slide.
That's
foundation
was
within
koha
people
took
coha
and
decided.
You
know
it's
not
really
working
well
in
our
instance,
so
they
forked
it
and
they've
built
a
community
around
a
whole,
a
totally
new
product.
A
A
A
If,
if
I'm
using
a
proprietary
vendor,
I'm
sitting
here
in
my
library
waiting
for
the
next
thing
to
happen,
waiting
for
them
to
tell
me
what's
coming
down
the
pike,
I
have
no
responsibility.
I
have
no
control.
I
have
no
I'm
just
getting
what
they're
feeding
me
passively
sitting
here:
cutting
them
checks.
Every
year
the
open
source
community
thrives
on
engagement,
every
developments
that
come
into
quahog.
Let
me
change
the
slides
here.
A
All
of
the
developments
that
come
in
are
community
driven.
Everything
is
about
the
engagement
with
the
community,
so
if,
if
you're,
using
an
open
source
product
yet
you're
using
a
support
vendor
and
you've
decided
to
take
that
passive
path,
that's
that's
fine,
but
realize
you're,
acting
as
if
it's
a
proprietary
vendor
you're
missing
out
on
the
huge
world
of
open
source,
really
by
doing
that,
the
bywater
folks
over
here
don't
mind
when
we
push
them
to
come
up
with
things.
A
B
Yeah
I
mean
that
that
is
the
number
one
thing
that
we
look
for
from
any
type
of
staff
or
librarian.
Is
that
feedback,
because
it's
so
crucial
to
make
the
software
better?
You
know
we
most
of
us
in
the
support
world,
at
least
at
biowater
solutions
were
a
librarian
prior
to
coming
to
buy
water
solutions
so
about
85
percent
of
us
have
our
mlis
or
have
worked
in
a
library
prior
to
coming
to
bywater.
B
So
you
know
we
remember
working
in
a
system,
some
of
us
on
koha
some
of
us
on
proprietary
and
what
makes
it
so
crucial
for
us
to
help
the
community
is
getting
that
feedback
from
you.
So
you
tell
us,
you
know
what
needs
to
be
better.
We
want
to
know
if
it
takes
three
clicks
to
complete
something
and
you
think
it
should
only
take
one
click.
That's
what
we
want
to
know.
B
If
you
are,
you
know,
processing
a
stack
of
records
into
the
system
and
you
think
that
it
should
be
able
to
save
those
system
preferences
before
you
hit
stage
that
file.
We
want
to
know
that
which
ps
that's
coming
in
the
next
release,
but
those
are
things
that
we
hear
from
people
to
make
it
better
in
the
system,
and
so
I
think
that's
one
of
the
greatest
advantages
of
open
source
is
working
so
closely
with
the
community.
A
I'm
going
to
go
out
on
a
limb
here
and
I'm
going
to
suggest
that
at
least
95
of
the
front-facing
developments
that
have
happened
within
quahog.
If
not
a
hundred
percent
of
them
are
all
librarian-driven,
there's
some
back-end
security
stuff.
That
happens.
That's
not
librarian-driven,
but
from
the
front
end
facing
there's,
not
a
development
that
comes
down
the
pike
that
was
not
developed
because
a
librarian
and
some
quahog
library
decided
they
needed
that
tool,
and
then
it
went
through
the
process.
A
The
community
accepted
that
lots
of
conversation
about
it
and
we'll
talk
about
that
process
here
in
a
minute.
But
then
you
use
that
there
was
a
presentation
earlier
today
about
housebound
there's
a
module
in
quahog
talking
about
housebound.
That's
because
a
library
saw
a
need
and
got
that
into
coho
that
wasn't
a
company
a
vendor
saying
you
know
here
is
a
solution
to
a
problem.
B
B
You
know,
there's
so
many
different
roles
that
individuals
can
take
part
in
as
part
of
that
community,
as
we
just
mentioned,
you
know
telling
us
what
could
be
better
in
the
system
by
providing
that
little
piece
of
feedback,
even
sharing
a
little
screenshot
of
how
something
works
at
your
library.
You
know
whether
you're
checking
something
in
and
you're
using
the
claims
return
feature
you
take
a
screenshot
of
that.
You
know
we
could
take
it
a
step
further
and
put
it
in
the
manual
that
way.
B
It
helps
three
or
four
more
people
when
they
come,
and
you
know,
try
and
figure
out
how
to
use
that
claims
returns
module.
So
even
if
it's
just
you
know
a
basic
step-by-step
instruction
on
how
to
use
something
or
it's
a
piece
of
code,
I
know
ed
can
share
an
awesome
story.
One
time
he
was
training
out
at
the
college
of
california,
arts,
ed
and
didn't
they
make
a
little
change.
While
you
were
sitting
right
there
and
training
to
submit
it
back
to
the
community.
A
A
Now
not
all
of
us
can
do
that.
That
takes
somebody
who
really
has
some
coding
skills
to
jump
in
there
and
do
that
I'll.
Tell
another
story
on
somebody
who's,
not
here,
but
it's
being
recorded,
and
he
knows
this
tell
a
story
on
spencer,
our
library
director,
when
we
were
preparing
to
go
to
koha
khan
in
portland,
that's
the
the
international
convention.
A
I
told
him
we
needed
to
go
and
he
needed
to
come
along
and
he
needed
to
attend
the
last
two
days
of
the
of
the
program
which
is
all
about
they
called
it
a
hack
fest.
At
that
point
and
and
his
view
was
I'm
not
a
coder.
I
can't
fix
any
of
these
problems.
Why
am
I
going
to
this?
Why
do
you
want
me
to
go
to
this
trust
me
you'll
get
something
out
of
it.
A
He
became
a
great
resource
to
the
coders
in
the
room
everybody
kept
saying.
What
was
that
idea?
You
talked
about.
Well,
let's
do
this.
Let's
talk
about
this,
oh
well,
that
doesn't
work.
You
know
he
became
engaged
with
them,
didn't
have
to
write
the
code
but
was
engaged
in
conversing
and
saying
no.
That
doesn't
look
right.
What,
if
you
do
it
this
way,
having
all
of
those
conversations
and
then
the
realization
hit
him
that?
Yes,
this
really
is
a
community
and
yes,
you
need
to
be
there
whether
you
can
write
code
or
not.
A
Okay,
anything
else
on
the
passion
all
right
community.
The
whole
thing
is
about
community.
I'm
going
to
jump
forward
through
that
ideas.
It's
what
we're
all
talking
about
here.
Everybody
here
is
using
coho
you've
got
ideas.
You've
got
different
things.
You
need
to
express
those
there's
nothing
worse
than
having
a
problem
in
the
system
that
doesn't
work
for
you
and
you
just
come
up
with
a
workaround
and
never
tell
anybody,
and
it
just
goes
on
in
frustration
and
then
something
happens.
A
A
A
A
B
Yeah,
I
I
think
a
lot
of
the
things
my
background
was
proprietary
before
I
I
came
over
to
the
vendor.
Side
of
things
was
with
ballet
and
voyager.
So
at
the
time
I
was
still
a
newbie
librarian
and
I
didn't
really
know
where
to
hunt
and
peck
for
things,
and
I
remember
we
had
a
big
binder
sitting
on
one
of
our
shelves.
B
That
was
our
manual
and
you
know
it
became
very
outdated
quickly
and
I
could
not
always
find
what
I
was
looking
for
and
I
feel,
like
you
have
this
challenge
with
the
proprietary
vendor,
where
you
sometimes
get
halted.
Where
you
don't
get
an
answer,
it
takes
a
long
time
and
then
you
get
stuck,
you
don't
know
what
to
do,
and
you
know
with
the
open
source
community
you
try
once
you
can't
find
it.
If
you
try
again,
you
may
discover
a
different
outlet
whether
it
was
on
an
email
list
serve.
B
You
know
if
you're,
watching
the
youtube
chat
right
now
there
are
people
chatting
back
and
forth
about
where
they
have
found
things
or
where
they're
sharing
answers
with
fred
already
said,
you
know
he's
giving
a
shout
out
back
as
he
sees
we're
talking
about
him
tomorrow.
You
know
people
are
out
there
and
willing
to
respond.
We're
going
to
talk
about
irc
here
in
a
little
bit,
which
is
you
know
how
koha
has
their
general
meetings
and
you
can
figure
out
a
way
with
the
community.
You
know
bouncing
ideas
around.
A
Then
you
had
to
be
on.
That
was
to
get
the
basic
information.
But
then,
if
you
had
a
complex
question,
you
had
to
have
the
secret
keys
to
the
secret
password
for
the
api
particular
piece
of
secrets,
and
there
were
all
these
barriers
to
getting
information
and
it's
because
they
have
a
proprietary
piece
of
information
that
they
don't
want
to
share
with
anybody,
and
that
is
diametrically
opposite
of
the
quahog
community.
A
B
B
So
there's
various
roles
for
each
of
the
you
know
releases
that
come
through
two
major
releases
with
cohab,
so
for
each
release
you
have
a
release
manager
who
is
going
to
maintain
that
release,
make
sure
that
the
release
moves
forward
and
then
launches
it
by
the
release
date.
You
have
members
of
the
quality
assurance
team.
Those
are
the
members
who
are
checking
each
one
of
those
enhancements
or
bugs
that
are
being
fixed,
making
sure
that
they're
working
processly,
they
don't
break
anything
else.
You
know
not.
B
You
have
release
maintainers,
so
you
know
there
are
libraries
who
are
self-supported
or
supported
by
a
vendor
who
may
be
on
a
previous
release.
So
when
the
new
release
comes
out,
the
release
maintainers
will
make
sure
that
those
older
releases
are
also
getting
any
type
of
updates
as
they
go
through
and
then,
of
course,
we
have
documentation
again.
One
of
the
strengths
of
open
source
is
having
documentation
online
that
you
can
find
at
any
given
time
so
making
sure
we
have
an
up-to-date
release
manual.
So
all
of
those
pieces
are
so
important.
B
You
know
as
you're
working
with
that
shared
responsibility,
so
giving
that
feedback
and
sharing
that
information
and
then,
of
course,
working
with
a
support
vendor.
So
if
you
are
working
with
a
support
vendor
for
your
for
your
open
source
product,
you
want
to
make
sure
that
you
communicate
with
them
regularly.
That
is
the
most
important
piece
of
it.
Make
sure
that
you're
giving
them
feedback
asking
questions
share
your
workflows.
You
know
that's
one
of
the
little
pieces
of
the
puzzle
that
you
can
give
back.
B
You
know
if
you're
noticing
that
something's
not
working
properly
or
you
know,
you've,
catalogued,
something
and,
and
something
just
doesn't
seem
right.
One
of
the
values
are
broken.
You
know
giving
those
examples
back
is
what
helps
make
the
product
stronger.
You
know
I,
I
always
tell
people
share
real
life
examples.
You
know,
because
we
want
to
see
that
you
know
screenshots
or
step
by
steps
on
how
you
got
to
that
and
then,
if,
if
you
don't
listen
to
anything
else,
I
say
communicate
and
that's
the
most
important
piece
of
it.
A
I
want
to
step
back
real
quickly
and
talk
about
the
roles
again.
All
of
those
are
not
mysterious
roles.
Anybody
can
take
those
roles.
You
just
have
to
get
active
in
the
community.
It
it
simply
means
setting
up
a
bugzilla
account
being
active
in
the
irc
attending
the
meetings,
and
you
can
help
the
community.
A
They
are
always
looking
for
people
for
documentation.
The
community
is
always
trying
to
trying
to
drum
up
assistance
in
the
documentation
side
of
things.
It
takes
a
little
bit
of
takes
a
good
bit
of
know-how
to
do
be
a
release
manager.
The
qa
is
very
important.
I
tell
people
whether
you
know
anything
or
not
about
the
coding
get
on
the
bugzilla
and
find
the
test,
the
bugs
that
need
testing
and
run
them
through
a
a
sandbox
bywater
provides
some
really
nice
sandboxes
to
test
bugs
in
you
go
in
there
and
do
that.
A
A
A
E
A
Ways
to
get
plugged
into
the
community
irc
and
slack-
if
I
presume
this
is
almost
universally
true-
most
city
and
school
I.t
departments
block
irc.
I
hate
it,
but
that's
the
fact.
I've
never
worked
in
an
institution
that
will,
let
me
have
irc
access,
so
I
either
have
to
use
their
public
wi-fi
to
connect
to
irc
or
my
own
device.
The
bywater
vendors
provided
a
slack
access.
So
that's
a
way
to
talk
to
them.
A
There
are
monthly
meetings
for
both
the
quahog
community
at
large,
koha
us,
and
there
are
special
interest
groups
within
the
koha
u.s
community.
I
will
go
ahead
and
give
a
quick
plug
here.
We've
got
a,
we
started
a
north,
texas,
quahog
group,
and
then
this
little
problem
hit
called
covid
and
everything
kind
of
fell
apart.
A
This
is
pretty
much
a
north
texas
in
person
group
thanks
to
all
the
wonderful
people
worldwide
that
are
watching.
Most
of
the
people
here
are
from
and
around
this
area.
So
this
can
give
us
a
head
start
on
getting
that
going.
Once
again,
there
are
also
special
interest
groups
for
what
is
their
cataloging?
A
A
A
B
I
just
want
to
say:
even
if
you
just
want
to
lurk
and
see,
what's
going
on
and
see
what
people
are
talking
about,
it's
a
good
place
to
get
your
foot
in
the
door.
You
know
you
can
create
a
free
account.
All
you
need
is
an
email,
and
this
allows
you
to
go
in
and
you
can
search
for
bugs
by
a
certain
topic.
So
if
you
wish
that
the
holds
process
was
a
little
bit
easier
or
faster,
you
know
those
are
things
that
you
can
come
in
here
and
look
for
in
the
system.
B
There's
multiple
webinars
that
you
can
watch
you
know
basic
how
to
set
up
a
bugzilla
account
how
to
search
how
to
file
a
bug.
If
you're,
you
know
wanting
to
go
through
and
look
for
easy
sign-offs,
you
can
even
do
an
advanced
search
and
just
look
for
bugs
that
may
need
some
basics
by
again
using
the
sandboxes
that
ed
mentioned
earlier,
you
can
go
in
load
it
up.
You
don't
have
to
know
any
code
on
the
back
end.
B
A
A
A
You
know,
like
you
had
in
college,
where
you
had
the
one
laminated
page
that
had
all
the
algebra
or
all
the
physics
or
all
the
english
they've
created
a
number
of
those
for
different
circulation.
Different
different
get
started.
You
know
basically
get
started,
quick,
cheat
sheets
for
coho
they're,
very
well
done,
as
with
anything
we've
got
to
keep
them
maintained
or
they're
going
to
become
stale.
That's
another
way
to
become
active
in
this
community,
the
project
dashboard,
yeah
I'll.
Let
you
talk
about
that.
One.
B
A
When
the
international
conference
happens
and
they
do
their
bug,
fest
or
their
bug,
bug
squash,
you
know
hack,
fest
or
when
they're
bug
bug
squashing.
I
can't
ever
say
that
bug
squashing
events.
The
dashboard
tends
to
track
all
of
that
too,
and
it's
fun
to
see
who's
submitting.
You
know
the
patches
and
everything
barbara
who
was
sitting
in
here
earlier
today,
she's
from
bedford,
not
too
long
ago.
She
was
in
the
top
three
or
four
you
know
patch
submitters
or
past
qa.
A
C
C
A
All
right,
the
question
is
about
from
an
individual
here:
who's
not
on
cohort
still
in
the
proprietary
world,
how
to
make
that
transition
with
the
staff
once
you've
already
made
the
leap
to
the
open
source
software.
It's
hard-
and
I
I
will
say
this:
there
are
a
couple
of
people
here
that
I
trained
when
I
was
with
bywater
years
ago
and
I'm
we're
still
working
on
it.
A
D
I
think,
even
to
our
director
that
somebody
has
got
to
spend
time
not
at
the
circulation
desk,
but
back
in
the
little
cubicle
somewhere
doing
some
of
this
stuff
getting
into
the
community
and
learning
and
presenting
issues
and
feedback
that
that's
part
of
the
process,
as
opposed
to
maybe
picking
a
phone
call
or
calling
the
guy
biblionyx
and
saying:
can
we
do
this?
No
okay,
thank
god!
It'd
be
done
so
in
case.
If
it
gets
a
very
good
mindset,
then.
A
Let's
step
back,
are
you?
Are
you
have
you
you?
Are
you
using
koha
independently,
or
are
you
using
a
support
vendor
to
help
manage
it?
Okay,
so
you're
doing
it
independently?
Okay,
yes,
there
is
a
great
community.
There's
no
money
involved
in
that
there
is
a
great
community
out
there.
Some
of
these
resources
we
went
to
there
are
these
addresses.
A
A
There's
another
gentleman
here,
john
who's,
the
treasurer
of
koha
us
who
was
who
also
spent
a
long
time
self-supported
in
in
the
quahog
world.
There
are
lots
of
there's
a
community
that
can
help
you
that's
what
this
is
all
about.
All
right,
there's
also
vendors,
that
you
can
pay
to
help
you
with
that,
but
you
know,
and
they
come
with
a
price
tag.
A
F
F
A
B
Yeah
that
that's
a
hundred
percent,
like
think
about
I'm
sure,
you've
all
seen
this
little
video
clip
where
there's
like
one
person,
that's
dancing
like
that,
a
festival
that
one
person
goes
out
and
starts
dancing
and
you
you
need
that
one
person,
because
then
everybody
else.
It
was
a
ted
talk
and
then
everybody
else
starts
and
goes
out
and
gets
dancing
because
he
made
the
first
move
so
find
that
person
who
is
your
open
source
believer
and
once
you
find
that
person,
then
everybody
else
will
just
come
and
and
keep
following
that
person.
B
If
anyone
ever
has
questions
about
the
open
source
community
or
you
don't
know
where
to
get
started,
or
you
just
need
someone
to
talk
to
no
ed-
and
I
are
always
here-
we,
we
love
helping
people
get
involved
in
the
community.
I
learned
everything
from
ed.
Ed
was
my
mentor
when
I
first
started
so
I
am
always
happy
to
share
that
same
passion
that
he
shared
with
me
almost
six
or
seven
years
ago.