►
Description
Presenters:
- Jessie Zairo (ByWater Solutions)
- Kelly McElligott (ByWater Solutions)
- Nick Clemens (ByWater Solutions)
Slides:
- https://drive.google.com/file/d/1S10JrDpgYFmkoK1pKpMkg897b0V1sN0p/view?usp=sharing
A
B
I
think
we've
heard
a
lot
about
this
presentation
all
week,
but
to
remember
to
remind
you
all
why
we're
here
to
get
today
our
presentation
we're
going
to
really
talk
about
how
to
engage
in
the
Quahog
Community
a
lot
of
presentations
this
week
have
talked
about
koha
and
getting
involved
and
volunteering
and
how
we
can
make
this
software
better
and
that's
really.
What
we're
here
to
talk
about
today
is
how
to
do
that.
B
B
We're
also
going
to
talk
about
how
to
efficiently
use
bugzilla.
So
if
you've
you're
like
what
is
bugzilla,
it
sounds
scary.
We
will
show
you
all
the
things
about
bugzilla
create
an
account,
make
a
comment,
we'll
talk
about
the
statuses
and
then
also
during
that
conversation,
we'll
talk
about
the
development
cycle.
So
what
it
exactly
means
in
all
the
stages
that
you
see
it
in
bugzilla
and
then
yes,
how
to
sign
off
on
a
bug.
It
is
not
scary.
It
is
super
easy
and
we're
going
to
do
that
today.
So
are
we
excited?
B
A
A
A
You
make
these
connections
with
people
and
you're
talking
to
different
users,
you're
talking
to
people
about
how
they
can
connect,
how
they're,
using
cohort
their
Library
you're
sharing
report
ideas
you're,
seeing
how
they
make
tweaks
on
their
OPAC
to
make
things
easier
to
use
and
you're
getting
ideas.
If
you
worked
on
a
different
system
prior
to
this,
did
you
have
that
same
type
of
feeling?
Did
you
have
that
same
type
of
connection.
A
Right,
that's
good!
That's
what
we
like
to
hear.
That's
one
of
the
things
that
we
love
about.
Kohan
is
the
community
which
takes
us
to
our
next
one.
Having
that
inclusion,
which
we
heard
them
talk
about
yesterday
being
part
of
a
community
where
you
can
share
ideas
and
joining
the
conversation.
That's
one
of
the
things
we're
going
to
talk
about
today
is
being
able
to
put
comments
on
it's
not
just
about
signing
off.
A
It's
also
about
giving
feedback
telling
users
how
things
work
at
your
library
discussing
the
workflow
saying
you
know
this
works
at
my
library,
or
this
doesn't
work
at
my
library
and
then,
of
course,
the
development
process.
We're
really
going
to
talk
a
lot
about
how
that
process
works,
how
you
can
be
a
part
of
it
from
start
to
finish.
B
Foreign,
maybe
at
some
point
during
maybe
a
training
or
reading
about
koha.
You
learned
how
Koh
was
created.
You
know
in
essence,
it
was
created
by
Librarians.
So
if
anything,
this
software
is
speaking
to
you
by
Librarians
and
it's
every
time
I've
been
on
it
for
10
years.
It
has
improved
drastically
by
The
Librarians
itself,
like
saying,
wouldn't
it
be
great
so
remember
that
koha
was
created
by
Librarians
for
librarians,
we're
speaking
for
you
through
the
software.
So
again
we
will
say
this
over
and
over,
but
the
power
is
in
your
hands
like
it's.
B
It's
up
to
all
of
us
to
say:
wouldn't
it
be
great,
so
we
should
just
Embrace
this
power.
We
could
wear
a
little
super
Cape
if
we
wanted
and
really
just
you
know,
be
that
person
that's
going
to
make
that
difference
or
say
I
would
love
to
see
it.
And
then,
when
you
see
it,
it's
a
pretty
awesome
experience.
A
A
C
B
Thank
you.
So
you
know,
unfortunately,
we're
not
all
together
most
of
the
year,
so
we
have
to
figure
out
ways
to
communicate
with
each
other
and
that's
really
important
to
have
those
conversations
throughout
the
year
again
through
a
couple
different
ways.
The
quahoga
community
has
created
that
you
could
do
it
through
the
listserv.
Is
everyone
signed
up
for
the
Kohala
serve?
B
Yes?
Yes,
yes,
okay,
good
I
can
say
honestly,
I,
don't
read
them
all.
Is
there
anybody
that
reads
them
all?
Probably
Liz,
oh
Chris,
Christopher
back
there
Katrin
probably
does
but
I
do
put
him
in
a
folder,
because
I
know
if
I
get
asked
the
question.
I
can
refer
back
to
it
because
I
know
we
get
a
lot
of
emails,
but
that's
just
a
great
way
to
get
involved
and
to
know
what
the
community
is
talking
about.
B
For
example,
they're
talking
of
their
the
staff
interface
is
getting
a
facelift.
So
that's
a
big
conversation,
that's
happening
on
the
list.
Serve
and
I
just
want
to
be
involved.
I
want
to
know,
what's
happening.
What
are
the
changes
and
again
I
have
a
voice,
so
I
can
make
a
comment
and
say:
ew
I,
don't
like
that,
but
I,
but
I,
wouldn't
I
mean
like
I
would
but
I
wouldn't
I,
don't
know,
go
to
a
quahoga
community
event.
B
We
talked
about
the
sigs
yesterday,
you
know
join
a
zoom
meeting
with
any
of
these
sigs
would
be
an
opportunity
to
also
Network
meet
people
find
out
what
other
libraries
are
doing
and
then
just
to
get
that
you
know,
conversation
going
in
the
koha
community
buy
water.
If
you're
a
buy
water
partner.
We
have
a
slack
channel.
That
slack
channel
is
like
on
fire
most
days.
The
report
channel
is
an
amazing
place
to
just
like
lurk
and
see
all
their
amazing
reports
that
are
coming
through.
B
C
So
the
whole
point
of
this,
the
most
important
thing
is
just
to
get
involved
and
to
kind
of
reach
out
to
the
community
for
the
community.
The
main
chat
space
right
now
is
going
to
be
IRC.
That
is
where
you
can
find
the
developers
other
Librarians.
All
of
us
live
there's
almost
always
somebody
there.
C
Now,
if
somebody
doesn't
answer
you
that
doesn't
mean
that
you're
being
ignored,
we
are
all
in
different
time
zones,
so
you
may
get
you
may
get
lucky
you
may
get
not,
but
it's
a
good
place
to
go,
see
who's
there
and
just
ask
around
you
can
just
go
into
the
channel
and
say
hi.
If
any
of
you
want
to
connect
right
now,
you
can
go
to
the
koha
website.
Click
on
connect
and
it'll.
C
C
So
this
is
bugzilla
before
we
get
too
deep
into
this
I
just
want
to
say
we
call
them
all
bugs
that
doesn't
mean
they're
all
bad.
Our
software
is
not
full
of
bugs
bugs
are
also
our
enhancements.
They're,
the
new
features
they're
all
the
good
things,
sometimes
the
bad
things,
but
bugzilla
is
where
all
of
that
happens.
C
So
one
of
the
first
things
you
should
do
to
get
involved.
I
cannot
stress
enough.
The
importance
of
registering
signing
up
for
things
if
you
join
bugzilla
you'll
be
able
to
then
go
in
and
comment
on,
all
of
the
bugs
that
are
there
we'll
go
into
this
deeper,
but
it
really
is.
This
is
where
you
can
have
an
impact
directly
on
developers.
You
can
go,
look
at
a
bug,
see
the
workflows
and
let
them
know
how
that
affects
your
library.
C
C
C
Where
does
it
start?
Okay,
like
where
do
I
go
so
developments?
How
do
how
does
koha
get
new
features?
How
do
these
things
you
know
get
into
koha?
Where
does
the
idea
come
from?
It
starts
from
contributors
and
that's
largely
going
to
be
the
libraries
and
our
partners,
people
who
reach
out
and
say
hey,
wouldn't
it
be
cool?
If
koha
did
this,
that's
really
the
first
step,
that's
where
all
of
you
can
get
involved.
You
can
go
and
file
a
bug.
C
C
So
once
you
have
that
you
have
contributors,
you
get
someone
to
do
the
work,
a
developer
is
either
paid
or
just
does
it
for
fun
comes
along.
They
write
the
code,
then
there's
testing,
so
the
code
is
submitted
to
the
community.
The
first
step
of
that
is
having
a
test.
It's
a
sign
off
step,
and
that's
really
just
you
go
to
the
bug.
Read
the
test
plan
that
the
developer
has
provided
or
ask
them
to
give
you
a
better
test
plan.
C
C
Fulan
gave
a
presentation
about
how
anyone
can
sign
off
of
a
bug
and
I
was
like
I
can
sign
off
on
a
bug
and
that's
really
how
I
got
involved
in
the
first
place
anyway,
once
it
has
been
tested,
QA,
quality
assurance.
They
are
your
friends,
sometimes
the
developers
out
there.
We
get
a
little
sad
because
they
fail
QA
and
they
say
you
need
to
rework
this
code,
but
they're
doing
it
to
make
the
product
better
and
that's
really.
C
The
important
step
of
this
is
making
sure
that
the
code
not
only
does
what
it
says
it
does
but
improves
koha.
It
doesn't
affect
anyone
else's
workflow,
it's
not
going
to
make
it
harder
to
use,
and
it's
just
good
once
that
has
all
been
done.
Sometimes
from
this
step,
it'll
go
right
back
over
here
and
kind
of
loop
around
in
this
circle.
For
a
while,
and
that's
not
a
bad
thing,
that's
how
we
refine
our
ideas,
rework
them
until
we
finally
get
them
forward
to
the
release.
Maintainer
the
release.
C
Maintainer
is
basically
the
one
who
sits
at
the
head
of
the
code
and
just
pushes
all
the
new
developments
they
are.
They
have
the
final
say
about
each
release.
What's
going
to
go
in,
what's
not
going
to
go
in
and
it's
a
great
job
if
you've
been
involved
in
the
community
for
a
while
I've
been
a
release,
maintainer
Lucas
has
been
a
release.
C
Maintainer,
we
don't
have
release
manager,
but
anyone
else
been
Brendan's
been
a
release,
maintainer
and
a
release
manager,
it's
fun
and
then
finally
they
get
the
they
get
the
really
fun
job
of
saying
it's
released,
so
they
they
push
it
out
to
the
community.
They
make
a
big
announcement.
We
see
all
the
changes
and
everyone
is
happy.
You
get
upgrades,
we
love
it.
E
B
B
B
B
B
Yeah
I'd
add
to
Google
Calendar
yeah
and
then
documentation.
Oh
yeah.
We
wanted
to
talk
about
that
included
in
part
of
the
KOA
Community
I
mean
the
manual
comes
out
twice
a
year.
So
that's
a
lot
of
work.
David
nind
right
now
is
currently
in
charge
of
documentation
for
2211.
Is
that
right,
Carolyn
yeah
and
he
has
a
huge
job.
So
he
wants
people
to
help
him
with
that
documentation.
If
you
are
interested
in
that
there
is
a
a
group
of
folks
that
do
that
and
that's
also
in
bugzilla.
B
So
there
is
a
different
status
or
cue
I,
don't
know
what
it's
called
that
says.
This
needs
documentation.
You
can
even
do
that
if
you
go
to
the
manual
and
you
find
something
that
is
not
well
documented
or
is
glossed
over
or
you
think
it
needs
more
work.
That
is
also
something
you
can
file
with
in
bugzilla.
C
The
dashboard
is
kind
of
the
Hub
of
development.
It's
a
really
easy
view
of
kind
of
what's
going
on
what
bugs
are
out
there
and
it
just
also
kind
of
highlights
our
oldest
bugs
just
to
make
sure
that
we're
kind
of
paying
attention
to
these
things,
just
an
important
tip
up
at
the
top
we've
got
overall
bug
tracker
health
status-
that
is
a
that
is
a
expandable
menu
if
you
click
on
that
it
pops
down,
and
it
shows
us
all
the
kind
of
major
issues
right
now.
C
So
you've
got
need
to
sign
off.
As
I
said.
That's
the
first
step.
That's
the
easy!
The
testing
needs
QA.
This
is
done
by
the
QA
team,
but
anyone
is
welcome
to
join
once
you've
done
enough.
You
know
some
sign
offs.
You
know
the
community.
If
you
can
read
the
code
a
little
bit
and
you
can
kind
of
understand
that
stuff
join
the
QA
team.
It's
great
needs
documenting.
C
This
is
the
list
of
the
ones
where
you
need
to
go
in
and
write
new
code
for
the
manual
easy
enough
to
do,
especially
if
you
sponsored
a
development
write
up.
Some
documentation
explain
to
people
what
it
does
now.
It's
useful
and
then
over
here
you've
just
got
kind
of
interesting
stuff.
The
last
sign
offs
and
the
newest
features
push
to
koha.
So
if
you
want
to
kind
of
see
previews
of
what's
going
to
be
in
the
next
release,
yeah,
okay
scroll
down
a
little
bit-
this
is
actually
where
I
always
come.
C
And
I
start
is
right
here
at
the
bug,
statuses,
you
can
click
on
any
one
of
those
links
there
and
that
will
take
you
to
the
a
view
in
bugzilla
of
all
the
bugs
that
are
currently
in
that
status.
So,
if
you're
looking
for
things
to
test
you
come
here,
you
click
on
need,
sign
off,
and
here
is
a
list
of
them.
You
can,
or
you
know
it's
a
their
list.
You
can
order
them.
However,
you
want
to
you,
can
add
different
fields
and
see
it.
C
C
C
I
really
just
wanted
to
see
myself
here
and
be
able
to
keep
track
of
it.
Oh
look
at
Kyle
go
so
this
just
kind
of
shows
us
an
example
of
what
what
everybody's
been
up
to
and
who's
been
doing.
The
things
here.
This
name
you're
almost
always
going
to
see
right
at
the
top
there
David
min
Katrin.
Surprisingly,
Kyle
is
ahead
of
her
in
QA,
which
is
almost
never
the
case,
but
that's
amazing.
C
C
C
So
when
you
do
the
search
it
gives
you
a
list,
these
are
organized,
it
looks
like
by
assignee
and
then
by
status.
Right
now,
so
we
can
see
all
of
those
new
bugs
assigned
bugs
in
discussion.
All
great
places
to
jump
in
if
you
just
kind
of
want
to
talk
about
it
in
discussion,
is
where
a
bug
goes.
When
we
say
we
need
input,
we
need
either
ideas
from
library,
libraries
or
developers.
We
just
kind
of
need
to
unlock
this
bug.
C
Oh
good
call,
okay,
so
importance
the
this
part.
We
don't
really
use
so
much.
However,
anyone
can
feel
free
to
change
it
if
you
think
that
something
is
very
important,
go
ahead
and
set
that
there
there
are
no
rules
about
setting
these
fields.
Let
me
be
clear:
do
you
know
be
cool
man,
but
you
can
come
in
and
change
these
things
enhancement?
This
is
really
this
part.
C
Enhancement
is
just
an
improvement
to
existing
behavior
and
then
the
rest
of
these
are
bug
statuses,
trivial,
meaning
something
that
you
know
we're
fixing
it
because
it
it
doesn't
look
right
or
something
like
that,
but
it's
not
actually
breaking
any
workflows
minor.
Very
you
know
an
inconvenience
normal
is
just
the
default
status
for
bugs.
Now,
when
you
hit
major,
that's
something
that
is
affecting
library
workflows
in
the
real
world
and
we
really
need
to
address
it.
C
C
Okay,
so
yes,
every
six
months,
there's
a
release,
usually
in
November
it's
May,
but
in
between
we
have
stable
releases
every
month.
So
once
a
cohort
version
is
released
every
month
we
do
a
point
release,
so
there'll
be
2111.01
2011.02
and
that
happens
every
month.
That's
the
job
of
the
maintainers.
They
work
very
hard
to
back
Port,
all
the
bugs
that
have
been
fixed
and
master
and
get
those
into
those
versions
and
release
them
to
everybody.
C
There,
it
is
vote
I
mentioned
this
yesterday.
This
is
a
cool
feature
that
you
can.
You
can
use
to
come
here.
You
get
30
out
of
200
or
you
have
200
allowed
Kelly.
No
Jesse
has
used
30
of
them.
So
far.
Votes
are
really
just
kind
of
a
way
to
indicate
that
this
is
very
important
to
you.
You
can
allocate
those
votes.
However,
you
want
to
just
to
kind
of
give
a
clue
to
the
developers
it
doesn't.
You
know
it's
not
a
promise.
C
C
C
Yeah
so
change
sponsored
that
is
when
a
library
or
Consortium
or
individual
has
has
paid
for
development.
That
just
indicates
that
this
is
probably
something
that
is
going
to
move
ahead.
Changes
that
aren't
sponsored.
You
know
you're
kind
of
at
the
at
the
whim
of
the
community
waiting
for
somebody
to
find
it,
but
a
Sponsor
Change
usually
means
that
something
somebody
has
paid
for
this,
we're
actively
working
on
it
and
is
going
to
move
ahead.
When
you
sponsor
things
too,
your
name
ends
up
in
the
koha
release.
C
C
Oh
okay,
so
CC
list
when
once
you're
signed
in
because,
of
course,
you've
registered
everybody
registers
for
everything.
No
one
forgets
when
you
come
and
look
at
a
bug
without
even
having
to
make
any
changes
on
the
bug.
That
little
add
me
to
CC
list
box
will
be
checked
and
all
you
have
to
do
is
hit
save
changes
and
you
will
be
subscribed
to
that
bug.
Every
time.
There's
a
change
and
update.
You
will
get
an
email
that
tells
you
what's
going
on
with
that.
C
C
C
Oh,
let's
go
back
Okay,
so
all
right,
so
these
two
sections
depends
on
means
that
there
is
another
bug
that
this
code
is
being
developed
on
top
of
so
that
somewhere
somebody
else
has
written
code
and
you
need
to
have
that
code
before
this
one
can
go
on
when
when
a
bug
depends
on
another
bug,
then
it
blocks
that
bug.
So
this
means
that
17873
depends
on
I,
don't
know
1818042,
so
it's
kind
of
it's
just
kind
of
which
way
does
that
relationship
goes.
C
C
B
Yesterday
I
talked
about
adding
a
a
bug
for
a
search
on
my
plugin
page,
so
I
thought
this
would
be
a
good
example,
so
we
can
walk
through
those
steps
because
it
may
sound
very
overwhelming
so
Jesse
just
went
ahead
and
once
you're
signed
in
you
have
to
be
signed
in
register.
It's
all
free
and
go
ahead
and
create
a
new
one.
Pick
koha.
B
The
next
big
thing
is
the
component
I'm
sometimes
I'm
wrong
when
I
pick
my
component,
because
I'm
not
sure,
but
there
are
people
like
Katrin
and
and
other
developers
that
will
come
in
and
correct
it
if
it's
in
the
wrong
component.
So
this
is
could
be
plug-in
architecture,
but
I
also
think
it
could
be
administration,
because
really
all
I'm
doing
is
adding
a
a
search
box
to
the
to
the
page
sis
system,
administration.
Perfect,
then
I
once
I
pick
that
I
will
see
the
description,
so
if
I
think
I'm
in
the
right
place.
B
If
I
read
the
description,
I'm
like
no,
not
so
much
now
from
for
version,
it
currently
doesn't
exist,
so
I
could
just
say
master
it's
right
now.
Nothing
exists
for
a
search
option
in
the
plugin
page.
Severity
talked
about
those
I'm
going
to
pick
enhancement,
and
that's
really
all
I'm
going
to
do
in
that
top
half.
What
I
love
about
putting
in
the
summary.
This
is
that
title
of
my
enhancement
as
I
start
to
type
koha
is
going
to
give
me
choices
to
say.
B
Yeah,
that's
perfect,
that's
perfect,
I
think
description
is
the
most
important
part
is
to
be
as
clear
as
you
can
to
tell
the
developer
what
you
want
to
say
now.
You
know
when
I,
when
I
learned
it
was
like
make
sure
you
identify
the
page
you're
on
so
like
that
URL
of
admin.pl,
or
something
like
that
so
to
say,
I'm
on
this
page
and
I
would
like
to
add
a
search
box,
so
Jesse's
gonna
pop
in
there.
So
we
make
sure
I'm
the
right
PL.
B
B
Maybe
put
existing
yeah
again
we're
trying
to
make
sure
that
we're
clear
on
what
we're
looking
for,
if
I
experience
more
of
a
a
minor
bug,
I
may
do
the
steps
that
I
went
through
to
get
to
the
point
where
I
said
this
is
a
bug
so
I
started
here.
I
did
this
I
did
this
and
then
this
is
what
happened
so
instead,
I
don't
really
have
a
workflow
other
than
to
say
on
this
page.
It
would
be
great
Jesse's
going
to
go
ahead
and
do
steps
too,
oh
and
I
could
add.
B
Has
anyone
filed
a
bug
in
the
room,
I'm
sure
there's
quite
a
few
of
you
Yay
good
job,
good
job,
okay
and
then
all
you
have
to
do
is
hit
submit
because
Jesse's
logged
in
she
is
automatically
going
to
be
cc'd
on
that
on
that
bug
automatically
and
then
from
there
you
can
yeah
perfect.
Thank
you.
Thank
you
for
subscribing
me.
C
C
And
and
usually
on,
this
I
will
just
go
ahead
and
hit
throw
away
my
changes
and
revisit
it
so
that
you
don't
undo
George
as
subscribing
to
the
bug
we
want
to
leave
that
there.
We
just
also
want
to
add
our
thing.
So
don't
be
scared
if
you
see
a
mid-air
Collision,
it
just
means
that
somebody
else
is
loving
the
same
bug.
You
are
we're
all
hugging
it
foreign.
B
G
This
is
an
example
of
kind
of
what
I
talked
about
in
the
keynote
to
the
cohathon
conference.
That
I
did.
This
was
a
bug
that
Nick
wrote
a
patch
he
he
wrote
this
book
and
he
said.
Sometimes
you
may
want
to
report
to
have
an
all
option
and
so
Nick
had
developed
this
patch
where
he
said
you
know
when
you
when
you're
writing
a
report,
you
it
all,
would
just
be
the
option
at
the
top
and
then
all
of
the
like
for
branches.
G
You
would
see
an
option,
that's
at
all,
and
then
you
would
have
a
list
of
all
the
branches
underneath
and
I
said.
I
really
like
that
idea.
But
I
have
some
reports
that
if
you
run
them
for
all
the
report's
going
to
crash
because
we've
got
55
libraries
and
if
you
try
and
do
some
of
the
reports
for
all
the
libraries
they're
just
going
to
fail,
because
it's
too
much
data
and
so
I
said
I
like
this,
but
could
all
be
optional.
G
And
so
then
an
hour
later,
Nick
wrote
back
and
he
had
Rewritten
the
patch
and
he
said
in
order
to
get
the
all
option.
You
have
to
add,
like
a
colon
to
your
SQL,
parameter
to
get
that
all
option
to
come
in
there
and
then
and
then
I
did
he.
He
wrote
it
so
fast
that
I
didn't
even
get
a
chance
to
sign
off
on.
It
was
at
a
late
talk.
B
System
works.
Okay,
so
we
are.
Oh,
let's
hit
the
sandbox
link
of
the
wiki
link.
This
is
also
included
in
the
presentation
just
where
you
can
find
the
sandboxes
a
little
bit
about
sandboxes
as
well.
So
a
nice
information
page
and
those
links
to
those
available,
sandboxes
documentation,
step
by
step,
I'm
going
to
talk
about
when
the
sandboxes
are
down.
B
B
C
The
idea
is,
the
sandbox
is
kind
of
a
protected
area
like
a
Sandbox
on
a
playground
where
you
can
sit
and
play
around
with
things,
and
it's
not
going
to
affect
the
real
world.
So
you
can
go
in
there
make
changes.
Well,
you
can
use
them
sign
up
for
bugs.
You
can
also
just
spin
up
a
spin
up
a
Sandbox.
B
Okay,
so
here
we
are
in
the
sandboxes,
can
you
go
to
the
other
sandbox,
because
I
can't
use
a
create
option
there
yeah,
so
up
at
the
top,
you
can
see
sandboxes,
we
can
see
any
existing
sandboxes
that
are
out
there.
They
do
have
an
expiration
date,
so
once
you
create
it,
you
just
have
a
few
days
now.
You
can
of
course
renew
that,
but
just
know
that
they
do
expire
when
you
go
ahead
and
create
very
easy,
your
name.
B
This
is
going
to
be
useful
when
you
sign
off
on
that
bug
that
will
be
attached
to
your
name,
your
email.
So
we
know
you
are
a
person,
the
sandbox
name,
very
specific,
don't
do
a
lot
of
stuff.
It's
like
a
couple
letters
or
just
lower
case
the
bug
number
and
then
everything
else
is
fine,
except
for
the
security
question.
C
B
B
B
B
B
B
So
this
says
materials
specified
notes
should
include
an
ID
on
both
the
check-in
and
checkout
page
ooh
sounds
exciting,
so
Lucas
created
this
bug
and
also
gave
us
on
comment
two
or
comment
one.
The
test
plan
to
test
apply
patch.
That's
what
you've
done
by
creating
the
sandbox
you're
applying
the
patch
that
he's
created,
find
an
item
and
add
a
material
specified
note
to
it.
So
we're
going
to
go
over
to
our
sandbox
grab
a
record
within
the
system.
B
B
Add
this
CSS
to
the
internet,
user,
CSS
system
preference,
so
we're
not
going
to
go
to
the
cohort
Administration.
This
is
why
it's
really
important
to
know
steps
are
important,
so
you
know
exactly
what
to
do
and
what
to
add
you're,
not
user
CSS
there.
It
is.
We've
pasted
that
in
WoW
great
job,
Jesse
Lucas.
Thank
you.
What's
the
next
step,
no
Edna.
B
A
B
B
B
E
C
We
were
up
here
looking
regretful,
we're
like
oh
no,
but
because
we
know
Lucas
but
really
failing.
Qa
is
a
way
to
tell
the
developer.
This
isn't
working
if
you
leave
it
signed
off,
and
you
just
put
a
comment
that
says:
hey
this
didn't
work
for
me.
The
developer
may
not
notice
that
as
much
as
noticing
that
our
bug
is
in
a
failed
QA
status
and
knowing
that
we
have
to
do
something
to
move
it
forward
so
yeah
we
don't
we're
not
sad
about
it,
we're
not
mad
about
it.
C
So,
in
this
case
it
worked
but
not
where
it
said
it
should
it
worked
on
one
page,
but
it
didn't
work
on
the
other
page,
so
you
could
fail
it.
And
yes,
but
yes,
if
you
have,
if
you
know
you
test
it,
and
you
were
like
this
red
is
awful,
you
can
fail
it
and
you
can
just
say
that
red
really
bothers
me
and
what,
in
this
case,
Lucas
would
see
that
and
he
would
say:
hey
it's
just
the
CSS.
We
can
make
it
blue
if
you
want.
C
Correct
the
red
in
this
case
is
an
example
of
the
fact
that
you
can
apply
CSS
to
it,
but
again,
but
what
I
want
to
be
clear?
Is
that
may
not
that's
clear
to
Owen
who
does
a
lot
of
design?
That's
clear
to
me
because
I
do
development?
If
it's
not
clear
to
you
fail
QA,
because
they
need.
We
need
to
write
test
plans
that
are
clear
for
the
users,
not
for
us.
Sorry,
Lucas.
B
The
sandbox
and
just
show
the
the
steps
if
we
could
pass
it
or
the
actions
that
are
involved
in
here,
so
we
went
into
whichever
one
we
were
in
under
this
action.
There
is
a
drop
down
menu
that
would
allow
us
to
do
a
few
things,
because
there's
a
few
steps
that
you
might
find
in
a
test
plan
like
you
have
to
do
is
re-index
or
you
have
to
refresh
the
schema.
B
B
Do
yourself,
then
again,
you're
going
to
give
your
name
I,
think
the
hardest
part
for
me
was
the
number
of
patches
to
sign
off
on,
and
so
that
is
something
you're
going
to
find
in
the
bug
where
the
patches
are
and
that's
it
yeah.
Can
we
pop
over
there
to
the
any
bug
and
just
show
the
the
very
top
a
little
bit
lower
a
little
bit
lower
a
little
bit
lower?
G
So
the
first
question
I
have
since
we're
still
right
here
with
the
sandboxes
and
all
that
what
if
you're
you
come
across
a
test
plan
that
says
something
like
prove
and
then
there's
a
long.
You
know
if
it
has
steps
in
it
that
you
don't
understand
and
that
you
can't
do
in
the
sandboxes.
What
do
you
do
then?.
C
So
what
I
usually
suggest
in
those
cases
is
test
everything
that
you
can
do
the
parts
that
you
can
and
you
can
just
say
what
you
did
now
approve
those
just.
Those
are
specifically
unit
tests.
The
unit
tests
are
code
that
we
write
that
can
run
and
check
that
everything
works
as
it's
supposed
to
it's.
Essentially
automated
testing
and
it's
it's
generally
lower
level
testing.
It's
not
kind
of
front-end
testing,
but
it's
testing
that
back
end
to
make
sure
that
all
the
changes
make
sense.
That
is
really
a
QA
step.
C
C
G
C
One
of
the
options
you
can
do
is
change
it
to
result
and
when
you
click
resolved,
you're
going
to
get
a
second
little
pop-up
box
go
ahead
and
click
that
and
it
gives
you
these
options.
So
one
if
you
come
into
bugzilla-
and
you
realize
that
you
have
you
know,
there's
a
development
that
you
paid
for
or
something
that
you
just
noticed
in
koha
and
you
see,
there's
a
bug
open
that
says:
hey,
it
would
be
nice
if
it
does.
This
go
ahead
and
Mark
it
fixed.
C
C
And
now
it's
going
to
give
you
a
number
and
you
just
pick
one
of
the
two.
It
doesn't
really
matter
which,
one
generally
we
pick
the
one
that
either
has
more
information
or
more
comments
like
if
one
just
describes
the
bug
and
the
other
says
how
to
recreate
it,
let's
keep
the
one
that
says
how
to
create
it
and
when
you
type
that
bug
number
in
there,
it
will
close
this
bug
and,
on
the
other
bucket,
we'll
link
them
together
to
say
that
that
was
a
duplicate
of
this
one.
C
C
Do
it
all
the
time
I
have
come
in
here?
There
have
been
times
where
I
have
come
in
and
I've
been
like.
I
want
to
fix
this
thing
and
I
file
a
patch
only
to
find
out
that
Lucas
has
already
filed
a
patch
and
Owen
has
already
signed
off
on
it,
and
Brendan
has
already
curated
because
I,
you
can't
be
aware
of
everything
that's
going
on
in
the
community,
and
we
don't
expect
you
to.
C
We
understand
that
Librarians
are
Librarians,
not
developers,
so
we
really
want
your
input,
but
we
also
value
your
time
and
we
know
that
it
is
important,
so
do
not
be
afraid
of
commenting.
If
you,
if
you
don't
understand
the
test
plan,
ask
no
one
will
get
upset
about
it.
We
we
want
you
there.
We
are
a
very
inclusive
community
who's
happy
to
have
your
input,
so
don't
be
afraid.
None
of
us
are
mean.
C
So
the
question
was:
there's
only
one
sign
off
needed
per
bug.
Yes,
as
long
as
it
doesn't
fail,
QA
again,
sometimes
the
bug
will
get
signed
off
and
the
QA
team
will
have
questions,
maybe
about
how
it
works
or
if
a
library
wants
it.
So
they
may
say
I'd
like
to
see
a
second
sign
off
here,
but
generally
yes,
just
one.
H
C
I
Just
a
comment
about
writing
submitting
a
new
bug.
I
always
find
that
if
you're
doing
a
bug
like
into
Library
loans,
I
was
put
both
ill
and
interlibrary
Loans.
As
one
word
and
the
three
words,
because
if
people
are
searching,
they're
often
set
they
search
for
ill
and
if
you've
written
into
Library
loans,
they
don't
find
it
and
same
withholds
and
reserves.
Really
I
tend
to
put
both
words
in
the
comments
somewhere
in
the
comments
section.
So
it's
findable
thank.
C
F
Yeah,
this
is
sort
of
a
deeper
existential
question,
so
our
library
went
through
covid
and
we
went
through
kova
without
a
director
I'm
sorry
I'm,
going
to
get
a
little
emotional.
So
for
two
years
we
had
no
direction.
We
had
this
wonderful
product,
nothing
could
be
done
with
it.
We
and
then
for
another
year
we
had
no
catalogger,
so
my
mentality
has
been
I,
just
live
with
it.
F
F
C
But
talking
to
me
you
kind
of
realized
like
hey
I
can
just
have
a
conversation
about
I
mean
I
hope
you
did
I
hope,
that's
yeah,
and
so
that's
sort
of
the
point
is
that
that's
that's
kind
of
what
we're
trying
to
say
here
is
just
we
are
a
community
and
we're
we
are
here
for
you
when
you're
ready
when
you're
not
ready.
We
understand
we'll
give
you
space,
but
if
you
ever,
you
know
you
can
even
just
reach
out
to
us.
C
C
J
C
K
C
I
would
say
both
submit
it
to
the
community
file
the
bug,
especially
if
you
have
the
steps
that
recreate
it.
But
if
you
work
with
us
also
file
a
ticket
with
us
to,
let
us
know
about
the
bug,
because
that
way,
it'll
kind
of
just
yeah
it
both
are
good.
If
you
file
in
the
community
that
lets
other
community
members
know
so
that
if
they're
seeing
it,
they
can
also
say
that
they've
found
it.
You
know,
see
your
bug
and
they
can
confirm
the
behavior.
B
And
again,
if
you're
a
one-person
show
or
feeling
overwhelmed
just
submit
a
ticket,
don't
even
file
the
bug.
Just
have
us
do
it
if
you
are
a
partner,
so
you
don't
have
to
feel
that
responsibility
to
say,
I
have
to
add
one
more
thing
to
my
to-do
list.
Maybe
next
week,
I
could
do
it,
but
I
want
to
I
wanted
to
do
it
right
now
in
that
filing
that
ticket
would
be
the
quickest
way
and
the
easiest
way
you
can
do
that
or
later
touch
base.
We're.