►
From YouTube: Funding QA and Joint Development
Description
Presenters:
- Brendan Gallagher (ByWater Solutions)
- Andrew Auld (PTFS Europe Limited)
- Jonathan Field (PTFS Europe Limited)
- Nate Curulla (ByWater Solutions)
Slides:
- https://docs.google.com/presentation/d/1cxQjKO841zpcO4ecSfO2UyK0k7kJi0sxOHzNOJXyVaM/edit?usp=sharing
A
A
We
vendors
in
the
cover,
Community
work
really
well
together
and
I,
think
that's
a
really
good
sign
for
the
community.
So
that
was
the
first
point
to
make.
This
presentation,
though,
is
about
how
well
the
community
is
working.
How
well
the
project
is
working
in
terms
of
keeping
the
quality
of
the
code
going,
keeping
development
going,
keeping
all
those
Wheels
spinning,
and
we
want
to
raise
a
few
questions
more
than
anything
else.
A
But
we've
got
some
thoughts
too,
but
it
would
be
good
to
have
discussion
Beyond
this
conference
at
this
conference
in
the
next
couple
of
days
and
then
beyond
this
conference,
about
how
we
keep
going
on
this
on
this
great
journey
that
we're
all
on
we've.
As
these
three
organizations
we've
actually
been
something
some
of
you
may
not
know,
is
that
we've
been
funding
directly
funding
as
in
paying
money
QA
in
the
community
by
actually
paying
Jonathan
Drew
out
on
a
monthly
basis.
A
A
You
can
use
it
free,
it's
freely
available,
code's
freely
available,
but
one
thing
not
to
confuse
with
the
word
free
is
that
it's
free,
because
we
all
in
this
room
you
all
and
lots
of
people
out
there
put
a
lot
of
time
and
effort
and
money
into
this
software
to
make
it
as
good
as
it
is.
So
it's
it's
free
in
many
senses
and
it's
also
not
free
in
other
senses.
A
So
that's
kind
of
something
to
to
bear
in
mind
as
we
talk
too
and
again,
just
thinking
about
what
has
gone
into
it
over
the
years.
I'm
not
going
to
spend
a
lot
of
time
talking
about
the
history
of
code,
because
you
all
a
lot
of
you
will
know
that
and
and
there's
lots
of
information
out
there
about
this.
A
But
carers
come
from
a
great
deal
of
effort,
so
people
put
effort
in
from
library
organizations
do
development
individual
interested
developers
just
around
the
world
do
great
work
and
spend
a
lot
of
time
developing
in
koha,
and
also
the
support
companies
do
a
bit
as
well.
So
we
do
that
either
we're
directly
funded
by
libraries
to
continue
with
development
am
I.
Is
it
not
getting
my
good
side.
A
Okay-
and
we
also
put
in
some
in-kind
work
as
well
as
I'm
sure
you'd
expect
us
to
do,
and
then
there's
loads
of
people
have
done
stuff
and
I
looked
on
the
KOA
website.
The
history
site,
just
yesterday
and
I
saw
that
there's
been
449
developers.
Who've
had
patches
pushed
into
Co-op,
which
is
amazing.
A
I
did
also
see
that
the
last
one
was
in
December
2021.
So
listen
to
the
presentation
tomorrow
about
getting
involved,
and
maybe
you
could
be
the
next
one
in
the
first
in
2022
to
have
a
patch
push
that
would
be
really
cool,
so
yeah
get
on
with
that.
There
have
been
loads
of
releases,
there's
loads
of
minor
releases,
there's
people
involved
in
translations
and
and
the
release
teams,
quality
teams
and
so
on.
A
There's
loads
of
stuff
that
happens
in
the
community,
and
that's
just
if
you
don't
ever
go
to
the
cover
dashboard
then
go
to
the
code
dashboard
and
see
just
how
many
people
put
stuff
in
and
and
and
this
hap.
This
is
updated
each
time.
There's
a
new
release.
The
dashboard
starts
again
and
and
every
year
you
can
see
how
many
sign-offs
are
happening.
A
How
many,
how
much
stuff
has
been
passed
through
QA
and
the
other
interesting
thought
about
I
thought
about
this
and
we'll
reflect
on
it
in
a
minute
or
two
when
I
do
some
slides
about
diversity?
It's
quite
a
diverse
list
of
names
up
there
as
well.
So
that's
a
good
thing
to
reflect
on,
but
nonetheless
it's
not
free,
so
it
we
do
need
to
find
a
way
of
keeping
this
thing
going
and
keeping
it
growing.
There's
a
tree
theme
in
my
images.
A
If
you
pick
up
on
that
as
well,
so
what
do
we
mean
by
funding?
These
are
some
of
our
questions:
how
how
does
the
community
better
facilitate
joint
development
investment
and
how
do
we
keep
things
moving
along
in
bugzilla
and
in
the
QA
pile,
and
also
how
do
we
ensure
that
the
code
gift
is
available
for
future
Generations?
So
we
talk
about
COA
and
the
meaning
of
Cohen.
A
Following
proposal,
incubation,
mature,
core
and
archived,
and
there's
many
who
will
be
able
to
tell
you
all
about
the
history-
and
there
was
a
great
presentation
at
koicon
2020
about
those
first
couple
of
phases
for
koha
and
there's
a
link
there
to
the
presentation
that
who
gave
the
presentation,
Rosalie,
Rachel
and
Chris
cormack
gave
that
presentation
in
Wellington.
So
if
you
want
to
go
back
and
learn
about
where
it
came
from,
then
do
that
we
went
through
presumably
an
incubation
station.
A
This
is
way
before
my
time,
I
wasn't
even
born
and
and
then
I
was
debating
to
myself
about
whether
we
were
in
mature
or
whether
we'd
reached
core
yet
so
mature.
Being
it's
had
several
successive
releases.
It's
on
track
with
its
Vision
challenges
might
still
exist.
That
feels
a
bit
like
us,
but
maybe
we're
a
bit
further
on
than
that.
Actually,
we've
got
a
broad
audience
due
to
the
value.
A
So
we
don't
want
that
to
happen
back
to
some
tree.
Images,
so
is
cover
a
core
project,
and
what
does
that
mean?
We
need
to
do
to
keep
it
going
and
keep
its
life
going
and
visiting
the
Rockies
a
couple
of
things
that
really
struck
us
one:
how
beautiful
two
lots
of
dead
trees
I,
don't
know
whether
any
of
you've
been
there,
but
it's
just
full
of
dead
trees,
and
this
is
a
global
warming
issue.
A
A
This
is
the
result
of
what
happened
with
all
those
dead
trees,
so
they
had
a
wildfire
in
2020
and
it
devastated
a
huge
area,
and
it
was
because
there
were
so
many
dead
trees
already,
because
the
Beetles
the
fire
got,
hold
and
spread
and
spread
and
spread.
So
we
certainly
don't
want
that
to
happen
to
our
our
wonderful
curve
project.
So
it's
it's
really
worth
thinking
about
how
we
fend
off
the
dying
trees,
the
the
worm,
the
beetle
or
whatever.
A
So
I
had
a
question
about
whether
we're
diverse
enough,
whether
we
are
welcoming
enough
it
was
an
excuse
to
put
an
elk
photo
in
I'm,
not
suggesting
there
are
any
big
bulls
in
the
KOA
Community
who
dominate
at
all.
Please
out
there
anywhere
in
this
room.
That's
not
the
suggestion.
It
was
just
a
good
photo,
but
are
we
diverse
enough
and
if
you
look
at
open
source
projects
more
generally,
this
is
some
research
from
2017.
A
Certainly
that
was
greater
than
five
percent,
and
that
was
just
on
an
eyeball,
but
we're
also
massively
diverse
in
terms
of
how
Global
we
are
as
a
community.
How
well
adopted
Co
is
globally,
where
cocon
has
been
held,
and
it's
a
great
feature
of
the
community
that
cocon
has
held
on
a
different
continent
every
year
and
that's
meant
that
it's
been
held
in
all
of
those
locations.
A
But
can
we
do
better?
Of
course
we
can
do
better.
This
is
the
level
up
conference,
so
we
want
to
think
about
ways
that
we
can
do
better.
We
don't
actually
measure
how
diverse
how
welcoming
and
how
inclusive
we
are,
and
should
we
or
could.
We
are
the
ways
that
we
could
track
some
of
that
stuff
and
therefore,
just
you
know,
benchmark
ourselves
and
do
a
bit
better.
A
Our
code
of
contact
then
there's
recommendations
that
all
open
source
software
projects
should
have
a
code
of
conduct.
Ours
actually
refers
to
holding
the
conference,
so
it's
a
code
of
conference,
the
code
of
conduct
around
holding
the
conference,
which
is
great
and
we
should
have
one,
but
we
could
also
have
a
code
of
conduct.
That's
about
the
project
itself,
about
how
we
welcome
new
people.
How
we
make
people
make
sure
people
up
don't
feel
excluded.
A
How
people
getting
involved
in
I
was
talking
to
Nick
yesterday
about
ways
of
encouraging
new
developers
and
not
putting
them
off
at
the
first
hurdle.
Just
because
they
get
some.
You
know
they
need
to
get
some
honest
feedback
if
they're
new
and
they
need
to
be
helped
but
keep
them
in
keep
them
involved,
because
we
need
them.
A
A
B
Thank
you
very
much,
so
it's
it's
sort
of
concerning
this
Twilight
is
how
do
we
keep
cover
going?
Keeping
a
vibrant
and
I
think
new
features
are
a
huge
important
part
of
that,
because
we,
we
also
have
to
remember
that
you
know
not
only
you
know
the
world's
changing
around
us.
It's
things
that
are
appearing
now
that
maybe
weren't
around
before
and
Co
has
always
got
to
keep
up
with
that.
B
B
You
know
what
are
we
going
to
do
about
this?
We
we
need
an
ERM.
Are
we
just
going
to
sit
back
and
do
nothing
or
we
can?
Actually?
You
know
do
something
about
this
and
it's
important
to
say
that
it
is.
It
is
jointly
sponsored
by
us,
which
is,
which
is
great,
and
you
know
you
maybe
would
expect
us
to
do
that,
but
it
also
highlights
a
few
things.
I
felt
and
one
is
that
actually
we're
not
financially
poor.
B
B
You
know,
we've
got
other
projects
on
the
go.
You
know
we
can
contract
out
work
but
they're
only
a
limited
number
of
hours
and
there's
there's
work
to
be
done
on
it.
So
a
problem
is
that
we
are
time
poor,
so
we
need
more
people
involved
looking
at
these
things,
and
it
also
highlights
the
challenges
of
sort
of
bringing
together
just
input
into
these
sort
of
projects.
B
So
you
know
we're
effectively
defined
the
specification
for
this
piece
of
work,
but
you
know
how
do
we
open
it
up
to
solicit
opinion
from
other
people?
And
you
know,
as
Andrew
mentioned,
you
know
what
channels
are
there,
that
people
feel
comfortable
engaging
in
and
we
can
quickly
solicit
feedback
and
input,
and
that
does
make
it
hard
to
solicit
input,
particularly
when
we
are
a
global
Community,
which
is
a
great
thing
but
also
provides.
B
You
know,
presents
a
challenge
because
we
have
people
across
the
world
who
are
using
different
knowledge
bases
in
the
context
of
ERM.
How
do
we
make
sure
that
we
cater
for
these
people?
So,
although
it's
a
you
know,
it's
great
that
we
are
thinking
about
the
future
and
we
don't
want
it
code
to
reach
its
Twilight
years.
B
C
Hello,
everybody,
hello
world,
all
right,
yeah,
so
I'm
going
to
talk
a
little
bit
about
what
we're
doing
to
try
and
make
it
easier
to
do
devs.
So
for
a
while.
Now,
we've
had
this
crowd
sourcing
development
page
and
what
this
allows
our
partners
or
other
members
in
the
community
to
do
is
cherry
pick.
C
A
portion
of
that
is
sometimes
earmarked
towards
future
developments,
which
is
awesome
because
that
gives
companies
like
us
the
ability
to
hire
more
Developers,
which
we
are
planning
on
doing
in
the
future,
to
expand
our
development
capacities
and
to
be
able
to
kind
of
handle
a
larger
influx
of
custom
development
requests.
So
anybody
who's
listening
that
may
want
to
apply
stay
tuned.
C
So
this
is
one
very
easy
way
to
do
that.
So
if
a
library
is
fortunate
enough
to
have
a
couple
Grand
laying
around
in
their
budget
at
the
end
of
the
year,
they
can
scroll
through
this
page
and
say:
okay,
you
know
I
want
to
see
I
want
to
move
along
over
dukron
config
into
Goa
and
I've
got
a
couple.
Bucks
left
over
boom
I'll
throw
it
at
it.
C
So
this
really
kind
of
highlights
the
point
that
even
if
you're
a
small
library-
and
you
might
only
have
a
couple
hundred
dollars
to
contribute
to
a
development
that
doesn't
mean
that
you
can't,
if
we
have
a
thousand
dollar
development,
we
don't
care
if
it's
10
libraries
with
100
each
or
if
it's
you
know,
whatever
the
more
people
that
are
involved
the
better,
because
then
we
get
different
perspectives
of
people
who
think
you
know
who
are
thinking
about
how
this
develop.
It
should
work
perspectives
that
a
single
funder
may
not
even
consider.
C
C
So
this
is
kind
of
like
what
a
detailed
view
would
look
like
on
the
website
and
you
can
see
there's
a
five
thousand
dollar
goal.
We've
raised
a
thousand
bucks.
This
is
a
great
opportunity
if
someone
was
like.
Oh
I
got
a
couple
thousand
dollars
sitting
around
boom
hit
it
another
thing:
that's
important
for
our
company
at
least,
is
that
you
know
if
a
lot
of
our
customers
are
requesting
a
development,
but
the
funding
isn't
getting
done.
Buy
water
will
kick
in
the
extra
money.
C
We
want
everybody's
experience
that
are
currently
using
KOA
to
be
the
best
possible
and
we
want
to
make
KOA
as
attractive
to
Future
libraries
as
possible,
so
everybody
wins
right:
the
vendor
side
and
the
user
side.
It's
pretty
cool,
so
typical
development
roadmap.
You
know
we
break
out
the
roadmap
into
two
pieces
architecture
and
feature
developments
a
lot
of
the
times.
The
architecture
isn't
that
sexy
and
it's
hard
to
get
money
for
it.
C
So
most
of
our
internal
funding
goes
towards
architecture,
development
and
that's
where
you're
going
to
see
a
lot
of
the
COA
vendors
coming
together
and
being
like
look,
you
know
we're
not
going
to
get
this
funding
because
it's
not
going
to
pass
the
board,
because
you
know
the
the
people
with
the
purse
strings
are
gonna,
be
scratching
their
heads
and
saying
what
the
heck
is
this.
So,
let's
just
get
it
done
instead
of
wasting
time.
C
But
you
know
the
vast
majority
of
all
the
features
and
enhancements
that
we
develop
come
from
you,
our
partners,
so
you're,
the
ones
who
direct
the
flow
of
this
development.
We
listen
to
what
you
say:
we
don't
develop
based
on
what
we
think
we
can
sell
and
that's
a
big
difference
between
koha
and
proprietary
Solutions.
You
know,
you've
got
proprietary
vendors
that
are
like.
Well,
you
know
we're
going
to
push
this
out.
C
We're
going
to
make
people
think
this
is
important,
whether
or
not
it
is
and
we're
just
going
to
grind
it
into
your
head
until
you
think
that
our
system's
the
best,
you
know
I'm
a
little
jaded,
but
but
you
know
in
the
KOA
Community,
it's
like
all
right.
You
know
tell
us
what
you
want
we'll
develop.
It
we'll
make
suggestions
on
how
it
can
be
better.
C
D
All
right,
first
of
all,
there's
two
interesting
comments
that
I've
heard
this
week
that
were
said
to
me
that
the
first
one
was
we
all
use
software
every
day.
But
when
you
get
a
chance
to
have
an
impact
on
that
software,
you
like
using
it
a
lot
more.
That
was
said
to
me
by
Christopher
when
I
first
got
here
and
then
like
right
when
we
were
walking
up
here
to
sit
down.
D
There's
this
another
person,
I
just
met
David
and
what
he
said
is
he
said
that
I
have
to
keep
reminding
myself
that
this
is
not
a
product,
that
this
is
a
project
and
that
what
I
wanted
to
talk
a
little
bit
about
was
just
how
it's
important
for
all
of
us
to
be
involved
in
this
and
so
like.
How
can
we
do
that?
D
That
Institute
needs
to
find
someone
else
from
a
different
Institute
to
sign
off
on
that,
so
the
sign
off
is
testing
it
and
just
making
sure
that
the
code
is
good
and
then
that
is
passed
on
to
another
team
and
that's
the
QA
team.
Now,
if
someone
from
Bywater,
so
we
always
have
people
that
work
on
the
QA
team
and
we
are
the
ones
who
submitted
development.
We
are
not
the
ones
that
can
pass
it
through
QA.
D
So
that's
why
we
were
talking.
Andrew
was
talking
a
little
bit
more
about.
We
do
a
joint
QA
of
a
third
party
so
that
way,
some
of
our
developments
that
get
out
there.
Hopefully
he
has
time
to
do
that,
but
also
we
want
to
be
fair
and
make
sure
that
he's
QA
and
everyone
else's
too,
so
that
we
can
keep
the
bottleneck
going.
D
So
that's
when
Andrew
was
talking
a
lot
about
these
questions
that
we
need
to
ask.
So
are
there
barriers
to
this
that
that
could
be
slowing
the
project
down?
Should
we
investigate
maybe
some
different
rules
on
that
now
there
are
meetings,
another
barrier
IRC
for
Andrew,
so
he
may
not
be
able
to
get
up
there
to
ask
this
question
of
a
bunch
of
other
developers.
D
D
A
A
E
F
D
So
our
next
presentation
that's
come
in
was
how
I'm
not
sure
how
to
say
their
name
correctly.
It's
Aisha
I
think
she
started
as
an
intern
in
New
Zealand
and
then
eventually
did
enough.
Through
this
program.
They
have
called
classmates
and
it's
where
a
bunch
of
high
school
kids
come
together
and
they
learn
how
to
sign
off
on
patches
and
test
some
code
and
and
write
some
simple
patches.
But
it
could
be
a
good
program
for
koha
us
to
have
that
and
you
could
get
support
from
developers.
D
I
mean
we
would
offer
developers
from
buy
water
to
like
help
Shepherd
that
kind
of
thing
with
interns,
usually
if
they
can
have
some
kind
of
little
stipend.
There
you'll
get
a
little
bit
of
a
bigger
pool,
and
so
that
could
be
something
that,
like
the
kohai
US
group,
would
like
stand
up
or
sponsor
and
then,
like
you
know,
of
course,
we'll
have
resources
to
help
with
the
actual
technical
teaching
and
stuff,
and
then
Kelly
can
do
her
class.