Re: [OPEN-ILS-GENERAL] [Bug 1879983] [NEW] Curbside Pickup

[Diane Disbro]

This is exciting!

Diane Disbro
Pronouns: she/her
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
251 Union Plaza Drive
Union, MO 63084
(636) 583-3224
ddis...@scenicregional.org





On Thu, May 21, 2020 at 10:55 AM Andrea Neiman <1879...@bugs.launchpad.net>
wrote:

> Public bug reported:
>
> Equinox is working on a curbside pickup interface for Evergreen. This
> will sit alongside the existing holds interfaces and its main function
> will be to give staff a process checklist to follow for curbside pickup.
> Patrons will be able to schedule pickup times online or via a staff
> member. Existing notice structures via Action/Trigger will be leveraged
> to broker communication about curbside pickup.
>
> A basic outline and wireframes can be seen in this document:
>
> https://yeti.esilibrary.com/dev/public/techspecs/curbside.pdf
>
> This is very much a "v.1" feature, and our primary goal is to get
> something broadly functional together as quickly as possible. Details of
> the above plan are subject to change as we work through the code.
>
> Watch this space!
>
> ** Affects: evergreen
>  Importance: Undecided
>  Status: New
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: EV bug mail
> https://bugs.launchpad.net/bugs/1879983
>
> Title:
>   Curbside Pickup
>
> Status in Evergreen:
>   New
>
> Bug description:
>   Equinox is working on a curbside pickup interface for Evergreen. This
>   will sit alongside the existing holds interfaces and its main function
>   will be to give staff a process checklist to follow for curbside
>   pickup. Patrons will be able to schedule pickup times online or via a
>   staff member. Existing notice structures via Action/Trigger will be
>   leveraged to broker communication about curbside pickup.
>
>   A basic outline and wireframes can be seen in this document:
>
>   https://yeti.esilibrary.com/dev/public/techspecs/curbside.pdf
>
>   This is very much a "v.1" feature, and our primary goal is to get
>   something broadly functional together as quickly as possible. Details
>   of the above plan are subject to change as we work through the code.
>
>   Watch this space!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1879983/+subscriptions
>

Re: [OPEN-ILS-GENERAL] Bug Squashing Week: This week

[Terran McCanna]

I'm sure we could keep at least one of the sandboxes available for longer -
let's see how it goes this week. I'm not sure how many community members
are working virtually this week, versus being off of work.


Terran McCanna, PINES Program Manager
--

Georgia Public Library Service | University System of Georgia

2872 Woodcock Blvd, Suite 250 l Atlanta, GA 30341

(404) 235-7138 | tmcca...@georgialibraries.org

http://help.georgialibraries.org | h...@help.georgialibraries.org




Join our email list  for stories of Georgia
libraries making an impact in our communities.



On Mon, Mar 16, 2020 at 2:00 PM Frasur, Ruth  wrote:

> Terran,
>
> Has there been any discussion about this becoming Bug Squashing Week and a
> Half or something like that?
>
> *Ruth Frasur*
> *Evergreen Support and Development Administrator*
> Indiana State Library
> 140 N Senate Ave
> Indianapolis, IN  46204
> (317) 460-7556
> --
> *From:* Open-ils-general <
> open-ils-general-boun...@list.georgialibraries.org> on behalf of Terran
> McCanna 
> *Sent:* Monday, March 16, 2020 1:54 PM
> *To:* List, Evergreen ; Group,
> Evergreen ; Evergreen
> Community Catalogers ;
> eg-newd...@list.evergreen-ils.org 
> *Subject:* [OPEN-ILS-GENERAL] Bug Squashing Week: This week
>
>  This is an EXTERNAL email. Exercise caution. DO NOT open attachments
> or click links from unknown senders or unexpected email. 
> --
> Hello everyone,
>
> This week is the (perhaps unfortunately named) Evergreen Community Bug
> Squashing Week. If you have a little bit of time to spare, your involvement
> will be much appreciated! You can participate by contributing code and also
> by testing, providing feedback, writing/updating documentation, and more.
>
> There are several sandboxes (test servers) set up with patches that are
> ready to test load onto them. Huge thanks to Chris Sharp, Blake
> Graham-Henderson, and Bill Erickson! Also special shout out to Chris
> Burton, who has a test server up and running with an overhauled OPAC
> design. Please update the associated Launchpad tickets when you test. Links
> and login info here:
>
>
> https://docs.google.com/spreadsheets/d/1Xo6H5v7JSMJq9pU7yrh3hOgPoMtGCl2qPa2iV8gp3jM/edit?usp=sharing
>
> General info about Bug Squashing:
> https://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing
>
> Best wishes to all!
> Teran
>
> Terran McCanna, PINES Program Manager
> --
>
> Georgia Public Library Service | University System of Georgia
>
> 2872 Woodcock Blvd, Suite 250 l Atlanta, GA 30341
>
> (404) 235-7138 | tmcca...@georgialibraries.org
>
> http://help.georgialibraries.org | h...@help.georgialibraries.org
>
> 
> 
>
> Join our email list  for stories of Georgia
> libraries making an impact in our communities.
>
>

Re: [OPEN-ILS-GENERAL] Bug Squashing Week Starts Today!

[Terran McCanna]

Follow-up: Blake has the Bug Squashing test server set up with the
requested patches applied:

https://docs.google.com/spreadsheets/d/1qYNGrJBt42_ArQzbwlcnKxS3TobDnmquSXZzopOkZh4/edit#gid=0

(If you didn't request a sandbox, you can also use this to confirm "New"
bugs.)

Thanks, Blake!

Terran

Terran McCanna, PINES Program Manager
--

Georgia Public Library Service | University System of Georgia

2872 Woodcock Blvd, Suite 250 l Atlanta, GA 30341

(404) 235-7138 | tmcca...@georgialibraries.org

http://help.georgialibraries.org | h...@help.georgialibraries.org




Join our email list  for stories of Georgia
libraries making an impact in our communities.



On Mon, Sep 9, 2019 at 9:13 AM Terran McCanna 
wrote:

> Welcome to Bug Squashing Week!
>
> All bug reports, patches, sign-offs, and comments between today (Monday,
> September 9) and Friday, September 13 will be recorded here:
>
>
> https://docs.google.com/spreadsheets/d/1qYNGrJBt42_ArQzbwlcnKxS3TobDnmquSXZzopOkZh4/edit?usp=sharing
>
>
> How to Participate:
>
> You may participate in Bug Squashing Day by:
>
>
>-
>
>Submitting new bug fixes for reported bugs
>-
>
>Testing bug fixes that others have submitted (these should have the
>"pullrequest" tag)
>-
>
>Confirming bug reports that haven't been reviewed yet (this is a great
>way to participate if you're not a coder!)
>-
>
>Pushing bug fixes into Evergreen (for core committers)
>-
>
>Assisting with documentation updates
>
>
> (Don't worry, you don't need to set aside the entire week to
>
> participate - you can participate however much that you can fit into
>
> your schedule!)
>
>
> Bug Squashing Week Info and Guidelines:
>
> http://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing
>
>
> Sandboxes:
>
> Blake is working on setting up some sandboxes with requested bug fixes
> installed and we'll have those ready soon. These sandboxes will have the
> Concerto data set. You are welcome to use these sandboxes to confirm new
> bugs and to see if old bugs still exist as well. Details will be posted at:
>
>
> https://docs.google.com/spreadsheets/d/1CLnGL1lzD3EVc3ppbjClR373U_0D3GZZ9vwRBzcRqII/edit?usp=sharing
>
> 
>
>
> Please let me know if you have any questions.
>
> Thank you!
>
> Terran McCanna, PINES Program Manager
> --
>
> Georgia Public Library Service | University System of Georgia
>
> 2872 Woodcock Blvd, Suite 250 l Atlanta, GA 30341
>
> (404) 235-7138 | tmcca...@georgialibraries.org
>
> http://help.georgialibraries.org | h...@help.georgialibraries.org
>
> 
> 
>
> Join our email list  for stories of Georgia
> libraries making an impact in our communities.
>
>

Re: [OPEN-ILS-GENERAL] Bug Squashing: Mid-Week Update

[Terran McCanna]

Copy and paste problems -this is the correct link!

https://docs.google.com/spreadsheets/d/1oxM5dA2FqPhUD81IIhnsoTuVkbfB2VoYTBKfhGMPwjk/edit#gid=0



Terran McCanna, PINES Program Manager
--

Georgia Public Library Service | University System of Georgia

1800 Century Place NE Suite 580 l Atlanta, GA 30345

(404) 235-7138 | tmcca...@georgialibraries.org

http://help.georgialibraries.org | h...@help.georgialibraries.org




Join our email list  for stories of Georgia
libraries making an impact in our communities.



On Thu, May 23, 2019 at 11:00 AM Terran McCanna <
tmcca...@georgialibraries.org> wrote:

> Bug Squashing Week is going fantastically!
>
> So far, 31 people have actively participated by reporting new bugs,
> updating existing bugs with more info, updating bug tags, testing patches,
> submitting new patches, signing off on bugs, and committing code.
>
>
> There are 11 patches that were submitted this week with pullrequests for
> testing, so if anyone would like to test those, that would be great. (They
> are listed on the tracking spreadsheet below.)
>
>
> 15 patches have been signed off on, and 8 patches have been committed.
> Thank you testers and core committers!
>
> The tracking spreadsheet is at:
>
>
> https://docs.google.com/spreadsheets/d/1oxM5dA2FqPhUD81IIhnsoTuVkbfB2VoYTBKfhGMPwjk/edit#gid=0
> 
>
> And if you haven’t participated yet this week, there are still two more
> days to get your name on the charts! :)
>
>
> Thanks everyone!
>
> Terran
>
>
>
>
>
> Terran McCanna, PINES Program Manager
> --
>
> Georgia Public Library Service | University System of Georgia
>
> 1800 Century Place NE Suite 580 l Atlanta, GA 30345
>
> (404) 235-7138 | tmcca...@georgialibraries.org
>
> http://help.georgialibraries.org | h...@help.georgialibraries.org
>
> 
> 
>
> Join our email list  for stories of Georgia
> libraries making an impact in our communities.
>
>

Re: [OPEN-ILS-GENERAL] Bug Squashing Week is Here!

[Terran McCanna]

Sorry, I used last May's link for the tracking chart, here is the current
one:
https://docs.google.com/spreadsheets/d/1mDoSEY_f7JYNyn-sjYwOhB9L8Us4J0Nz_FDcCMf6DQA/edit?usp=sharing

Thanks to Ben Shum for alerting me!



Terran McCanna
PINES Program Manager
Georgia Public Library Service
tmcca...@georgialibraries.org

* The GPLS office is in the midst of relocating offices. We may be reached
by all of the current mechanisms during the transition, but to ensure the
most prompt response, please use the Help Desk:
https://help.georgialibraries.org


On Mon, Sep 10, 2018 at 9:04 AM, Terran McCanna <
tmcca...@georgialibraries.org> wrote:

> Hi everyone,
>
> Bug Squashing Week begins today!
>
> Bug Squashing Day Info and 
> Guidelines:http://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing
>
> Evergreen Bug List:https://bugs.launchpad.net/evergreen
>
> 'New' Bugs that need to be Confirmed:https://goo.gl/apLhQ9
> Bugs with the 'pullrequest' tag that need to be tested:https://goo.gl/p2yBEA
>
>
> I'll be tracking all of the bug-related work this week for posterity
> (based on the comments added to launchpad):
> https://docs.google.com/spreadsheets/d/1mDoSEY_f7JYNyn-sjYwOhB9L8Us4J0Nz_
> FDcCMf6DQA/edit?usp=sharing 
>
> If you need access to a current master sandbox for confirming bug reports
> that don't have  patches yet, here is one you can use this week (thanks,
> Blake!!!):
>
> Sandbox:  https://bugsquash.missourievergreen.org
> User: admin
> Password: demo123
>
>
> Please let me know if you have any questions! Feel free to email me
> directly, or I'll be in the Evergreen IRC channel most of the week as well.
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> tmcca...@georgialibraries.org
>
> * The GPLS office is in the midst of relocating offices. We may be reached
> by all of the current mechanisms during the transition, but to ensure the
> most prompt response, please use the Help Desk:
> https://help.georgialibraries.org
>
>

Re: [OPEN-ILS-GENERAL] Bug Squashing Week Tracking Chart

[Terran McCanna]

Sorry! Here is the correct link:

https://docs.google.com/spreadsheets/d/1pKdrHjwWpuQY-F0wGrIew5I65tAM4NxOZJfpJL33vDk/edit?usp=sharing



Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org


On Mon, May 21, 2018 at 10:30 AM, Terran McCanna <
tmcca...@georgialibraries.org> wrote:

> Here is the running chart for Bug Squashing Week Progress (based on
> updates made to Launchpad):
>
> https://bugs.launchpad.net/evergreen/+bug/1497322
>
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> Atlanta, GA 30345
> 404-235-7138
> tmcca...@georgialibraries.org
>
>

Re: [OPEN-ILS-GENERAL] Bug Squashing status

[Terran McCanna]

Hello Bug Squashers,

I've finally gotten the chart updated to the current week's status - my
apologies if I've missed anything or anyone:

https://docs.google.com/spreadsheets/d/1yrYuu6ieLFI3B21YGivpsA8Kb47ReP9tXl3pNBC5TQA/edit?usp=sharing



Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org

Re: [OPEN-ILS-GENERAL] Bug Squashing status

[Terran McCanna]

Hello Bug Squashers,

I finally have power restored, but still no internet either at home or in
the office. I'm doing my best to catch up today via a spotty mobile hotspot
connection and will let you know when I am able to get the bug squashing
week chart updated.

Thanks for your patience!



Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org


On Mon, Sep 11, 2017 at 9:21 AM, Terran McCanna <
tmcca...@georgialibraries.org> wrote:

> Hi everyone,
>
> I'm off today due to Hurricane Irma. I should be back online tomorrow
> barring any house disasters.
>
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> Atlanta, GA 30345
> 404-235-7138 <(404)%20235-7138>
> tmcca...@georgialibraries.org
>

Re: [OPEN-ILS-GENERAL] Bug Squashing Week Results

[Terran McCanna]

Thank you, Kathy!!!

Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org


On Wed, Mar 8, 2017 at 5:49 PM, Kathy Lussier  wrote:

> Hi all,
>
> I just wanted to let everyone know that the MassLNC community demo server
> has been updated to include all of the fixes that were merged during and
> since Bug Squashing week. Access information is available at
> https://wiki.evergreen-ils.org/doku.php?id=community_servers
>
> A list of those fixes is available at http://bit.ly/2mHmzg9.
>
> Kathy
>
> On 03/06/2017 10:28 AM, Terran McCanna wrote:
>
> Thank you to everyone who participated in last week's Bug Squashing Week!
>
> Due to the extended time period, more people were able to participate this
> time around, and the results positively reflected the amount of effort
> contributed by the community.
>
> A summary is posted on the wiki here:
> https://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing:2017-02-27
>
> And you can see the details broken down here:
> https://docs.google.com/spreadsheets/d/1RPR5gIL02EiIvsg5vDKLs40rgw0Da
> qy4_TRWPlqU0WY/edit?usp=sharing
>
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> Atlanta, GA 30345
> 404-235-7138 <(404)%20235-7138>
> tmcca...@georgialibraries.org
>
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative(508) 343-0128kluss...@masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>

Re: [OPEN-ILS-GENERAL] Bug Squashing Week Results

[Kathy Lussier]

Hi all,

I just wanted to let everyone know that the MassLNC community demo 
server has been updated to include all of the fixes that were merged 
during and since Bug Squashing week. Access information is available at 
https://wiki.evergreen-ils.org/doku.php?id=community_servers


A list of those fixes is available at http://bit.ly/2mHmzg9.

Kathy


On 03/06/2017 10:28 AM, Terran McCanna wrote:

Thank you to everyone who participated in last week's Bug Squashing Week!

Due to the extended time period, more people were able to participate 
this time around, and the results positively reflected the amount of 
effort contributed by the community.


A summary is posted on the wiki here:
https://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing:2017-02-27

And you can see the details broken down here:
https://docs.google.com/spreadsheets/d/1RPR5gIL02EiIvsg5vDKLs40rgw0Daqy4_TRWPlqU0WY/edit?usp=sharing


Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org 



--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Bug?

[Galen Charlton]

Hi,

On Fri, Jul 8, 2016 at 5:26 PM, Jim Lynch  wrote:
> make -f Open-ILS/src/extras/Makefile.install ubuntu-trusty
>
> Which is in the "Installing prerequisites" section.  Seems to me it
> shouldn't assume any utilities are loaded except for the basic system
> utilities.  a2enmod isn't installed  unless it's needed for Apache.

I think you may need to install OpenSRF first.  You can find it (and
installation instructions) here:

https://evergreen-ils.org/opensrf-downloads/

Apache gets pulled in as part of the OpenSRF installation; once you
have OpenSRF running, you can start the Evergreen installation again
from the Makefile.install step.

Regards,

Galen
-- 
Galen Charlton
Infrastructure and Added Services Manager
Equinox Software, Inc. / Open Your Library
email:  g...@esilibrary.com
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org &
http://evergreen-ils.org

Re: [OPEN-ILS-GENERAL] Bug Squashing Day in June 2015

[Kathy Lussier]

Hi all,

I'm putting out a reminder to please let us know when you're available 
for the next Bug Squashing Day by filling out the poll at 
http://doodle.com/g4b87nsp2d7s87gx .


I plan to close the poll on Friday.

Kathy

On 05/16/2015 12:08 PM, Kathy Lussier wrote:

Hi all,

We're scheduling our next Bug Squashing Day in June 2015. We're doing 
it a month later because I didn't want it bumping up against 
conference activities.


Bug Squashing Day is open to all community members who want to work to 
resolve bugs in the Evergreen system. Community members can use the 
day to focus on confirming bugs that have been submitted to Launchpad, 
testing proposed bug fixes, and creating fixes to bugs. Once again, 
MOBIUS and MassLNC will be providing Sandboxes to make it easy for 
community members to test bug fixes.


It's a great way to contribute to the Evergreen project and to make 
the software better for everyone who uses it.


If you're interested in helping out with Bug Squashing Day, please 
fill out the poll at http://doodle.com/g4b87nsp2d7s87gx so that we can 
find a date that works for the most people.


Feel free to let me know if you have any questions!

Kathy



--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[Kathy Lussier]

Hi all,

It looks like most people will be here, so let's move forward with Bug 
Squashing Day on Monday.


If you need to Sandbox to test a bug fix, I'm asking people to submit 
the request by the end of the day today. I know it doesn't give you much 
time to look through the bugs, but the Sandbox administrators need time 
to load the branches ahead of Bug Squashing Day.


With that in mind, please submit any Sandbox requests at 
http://goo.gl/forms/boKucpwnpz. The list of bugs with pullrequest tags 
is available at http://bit.ly/1lhUabq.


Kathy

On 02/26/2015 09:45 AM, Josh Stompro wrote:

I can participate on Monday also.
Josh


Josh Stompro - LARL IT Director


-Original Message-
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Kathy 
Lussier
Sent: Wednesday, February 25, 2015 12:57 PM
To: open-ils-general@list.georgialibraries.org
Subject: Re: [OPEN-ILS-GENERAL] Bug Squashing Day

Hi all,

Ack!

I closed the Doodle poll last month and set this Monday, March 2 as the date 
for our next Bug Squashing Day.  However, it looks like I failed to communicate 
the date with the rest of the community beyond adding it to the community 
calendar.

I would still like to see if we can get a group together to work on bugs on 
March 2. Does that day still work for everyone who responded to the poll?

Thanks and apologies for the oversight! I'm blaming it on the snow.

Kathy



On 01/21/2015 02:44 PM, Kathy Lussier wrote:

My apologies. The link for the Bug Squashing scheduling poll should be
http://doodle.com/umc27afh7akqczft.

That's what I get for working on two Doodle polls at the same time.

Kathy

On 01/21/2015 02:35 PM, Kathy Lussier wrote:

Hi all,

I'm sending out a reminder to let us know what your availability is
to participate in our next community Bug Squashing Day.
http://doodle.com/xwu55tseci3mf34e

I'll be closing the Doodle poll at the end of the day tomorrow.

Kathy
On 01/16/2015 11:56 AM, Kathy Lussier wrote:

Hi all,

It's hard to believe, but it's already time to schedule another Bug
Squashing Day. We're scheduling the next Bug Squashing Day to fall
after the 2.8 beta release, but before the RC1 release. The closer
we can schedule it to the beta release, the better.

Please let us know when you're available!
http://doodle.com/umc27afh7akqczft

Kathy


--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier



--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[Josh Stompro]

I can participate on Monday also.
Josh


Josh Stompro - LARL IT Director


-Original Message-
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Kathy 
Lussier
Sent: Wednesday, February 25, 2015 12:57 PM
To: open-ils-general@list.georgialibraries.org
Subject: Re: [OPEN-ILS-GENERAL] Bug Squashing Day

Hi all,

Ack!

I closed the Doodle poll last month and set this Monday, March 2 as the date 
for our next Bug Squashing Day.  However, it looks like I failed to communicate 
the date with the rest of the community beyond adding it to the community 
calendar.

I would still like to see if we can get a group together to work on bugs on 
March 2. Does that day still work for everyone who responded to the poll?

Thanks and apologies for the oversight! I'm blaming it on the snow.

Kathy



On 01/21/2015 02:44 PM, Kathy Lussier wrote:
 My apologies. The link for the Bug Squashing scheduling poll should be 
 http://doodle.com/umc27afh7akqczft.

 That's what I get for working on two Doodle polls at the same time.

 Kathy

 On 01/21/2015 02:35 PM, Kathy Lussier wrote:
 Hi all,

 I'm sending out a reminder to let us know what your availability is 
 to participate in our next community Bug Squashing Day.
 http://doodle.com/xwu55tseci3mf34e

 I'll be closing the Doodle poll at the end of the day tomorrow.

 Kathy
 On 01/16/2015 11:56 AM, Kathy Lussier wrote:
 Hi all,

 It's hard to believe, but it's already time to schedule another Bug 
 Squashing Day. We're scheduling the next Bug Squashing Day to fall 
 after the 2.8 beta release, but before the RC1 release. The closer 
 we can schedule it to the beta release, the better.

 Please let us know when you're available!
 http://doodle.com/umc27afh7akqczft

 Kathy




--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[Rogan Hamby]

I'll try to. It's hard to absoloutely commit since I get pulled away from
my desk for everything from patrons complaining about fines to ... well,
more dramatic things.  But I'm going to try!

On Wed, Feb 25, 2015 at 1:57 PM, Kathy Lussier kluss...@masslnc.org wrote:

 Hi all,

 Ack!

 I closed the Doodle poll last month and set this Monday, March 2 as the
 date for our next Bug Squashing Day.  However, it looks like I failed to
 communicate the date with the rest of the community beyond adding it to the
 community calendar.

 I would still like to see if we can get a group together to work on bugs
 on March 2. Does that day still work for everyone who responded to the poll?

 Thanks and apologies for the oversight! I'm blaming it on the snow.

 Kathy




 On 01/21/2015 02:44 PM, Kathy Lussier wrote:

 My apologies. The link for the Bug Squashing scheduling poll should be
 http://doodle.com/umc27afh7akqczft.

 That's what I get for working on two Doodle polls at the same time.

 Kathy

 On 01/21/2015 02:35 PM, Kathy Lussier wrote:

 Hi all,

 I'm sending out a reminder to let us know what your availability is to
 participate in our next community Bug Squashing Day. http://doodle.com/
 xwu55tseci3mf34e

 I'll be closing the Doodle poll at the end of the day tomorrow.

 Kathy
 On 01/16/2015 11:56 AM, Kathy Lussier wrote:

 Hi all,

 It's hard to believe, but it's already time to schedule another Bug
 Squashing Day. We're scheduling the next Bug Squashing Day to fall after
 the 2.8 beta release, but before the RC1 release. The closer we can
 schedule it to the beta release, the better.

 Please let us know when you're available!
 http://doodle.com/umc27afh7akqczft

 Kathy




 --
 Kathy Lussier
 Project Coordinator
 Massachusetts Library Network Cooperative
 (508) 343-0128
 kluss...@masslnc.org
 Twitter: http://www.twitter.com/kmlussier




-- 

Rogan Hamby, MLS, CCNP, MIA
Managers Headquarters Library and Reference Services,
York County Library System

“You can never get a cup of tea large enough or a book long enough to suit
me.”
― C.S. Lewis http://www.goodreads.com/author/show/1069006.C_S_Lewis

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[Kathy Lussier]

Hi all,

Ack!

I closed the Doodle poll last month and set this Monday, March 2 as the 
date for our next Bug Squashing Day.  However, it looks like I failed to 
communicate the date with the rest of the community beyond adding it to 
the community calendar.


I would still like to see if we can get a group together to work on bugs 
on March 2. Does that day still work for everyone who responded to the 
poll?


Thanks and apologies for the oversight! I'm blaming it on the snow.

Kathy



On 01/21/2015 02:44 PM, Kathy Lussier wrote:
My apologies. The link for the Bug Squashing scheduling poll should be 
http://doodle.com/umc27afh7akqczft.


That's what I get for working on two Doodle polls at the same time.

Kathy

On 01/21/2015 02:35 PM, Kathy Lussier wrote:

Hi all,

I'm sending out a reminder to let us know what your availability is 
to participate in our next community Bug Squashing Day. 
http://doodle.com/xwu55tseci3mf34e


I'll be closing the Doodle poll at the end of the day tomorrow.

Kathy
On 01/16/2015 11:56 AM, Kathy Lussier wrote:

Hi all,

It's hard to believe, but it's already time to schedule another Bug 
Squashing Day. We're scheduling the next Bug Squashing Day to fall 
after the 2.8 beta release, but before the RC1 release. The closer 
we can schedule it to the beta release, the better.


Please let us know when you're available!
http://doodle.com/umc27afh7akqczft

Kathy







--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[Yamil Suarez]

I can still participate.

Yamil


On Wed, Feb 25, 2015 at 1:57 PM, Kathy Lussier kluss...@masslnc.org wrote:
 Hi all,

 Ack!

 I closed the Doodle poll last month and set this Monday, March 2 as the date
 for our next Bug Squashing Day.  However, it looks like I failed to
 communicate the date with the rest of the community beyond adding it to the
 community calendar.

 I would still like to see if we can get a group together to work on bugs on
 March 2. Does that day still work for everyone who responded to the poll?

 Thanks and apologies for the oversight! I'm blaming it on the snow.

 Kathy



 On 01/21/2015 02:44 PM, Kathy Lussier wrote:

 My apologies. The link for the Bug Squashing scheduling poll should be
 http://doodle.com/umc27afh7akqczft.

 That's what I get for working on two Doodle polls at the same time.

 Kathy

 On 01/21/2015 02:35 PM, Kathy Lussier wrote:

 Hi all,

 I'm sending out a reminder to let us know what your availability is to
 participate in our next community Bug Squashing Day.
 http://doodle.com/xwu55tseci3mf34e

 I'll be closing the Doodle poll at the end of the day tomorrow.

 Kathy
 On 01/16/2015 11:56 AM, Kathy Lussier wrote:

 Hi all,

 It's hard to believe, but it's already time to schedule another Bug
 Squashing Day. We're scheduling the next Bug Squashing Day to fall after 
 the
 2.8 beta release, but before the RC1 release. The closer we can schedule it
 to the beta release, the better.

 Please let us know when you're available!
 http://doodle.com/umc27afh7akqczft

 Kathy




 --
 Kathy Lussier
 Project Coordinator
 Massachusetts Library Network Cooperative
 (508) 343-0128
 kluss...@masslnc.org
 Twitter: http://www.twitter.com/kmlussier




-- 





Yamil Suarez, MCS
Library System Administrator/Developer

Stan Getz Library
Berklee College of Music
1140 Boylston St
Boston, MA 02215

ysua...@berklee.edu
617-747-2617

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[McCanna, Terran]

I'm heading out of town due to a family illness. I do have a few little things 
I want to submit, but I won't have time before then. 



Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org


div Original message /divdivFrom: Kathy Lussier 
kluss...@masslnc.org /divdivDate:02/25/2015  1:57 PM  (GMT-05:00) 
/divdivTo: open-ils-general@list.georgialibraries.org /divdivSubject: 
Re: [OPEN-ILS-GENERAL] Bug Squashing Day /divdiv
/divHi all,

Ack!

I closed the Doodle poll last month and set this Monday, March 2 as the 
date for our next Bug Squashing Day.  However, it looks like I failed to 
communicate the date with the rest of the community beyond adding it to 
the community calendar.

I would still like to see if we can get a group together to work on bugs 
on March 2. Does that day still work for everyone who responded to the 
poll?

Thanks and apologies for the oversight! I'm blaming it on the snow.

Kathy



On 01/21/2015 02:44 PM, Kathy Lussier wrote:
 My apologies. The link for the Bug Squashing scheduling poll should be 
 http://doodle.com/umc27afh7akqczft.

 That's what I get for working on two Doodle polls at the same time.

 Kathy

 On 01/21/2015 02:35 PM, Kathy Lussier wrote:
 Hi all,

 I'm sending out a reminder to let us know what your availability is 
 to participate in our next community Bug Squashing Day. 
 http://doodle.com/xwu55tseci3mf34e

 I'll be closing the Doodle poll at the end of the day tomorrow.

 Kathy
 On 01/16/2015 11:56 AM, Kathy Lussier wrote:
 Hi all,

 It's hard to believe, but it's already time to schedule another Bug 
 Squashing Day. We're scheduling the next Bug Squashing Day to fall 
 after the 2.8 beta release, but before the RC1 release. The closer 
 we can schedule it to the beta release, the better.

 Please let us know when you're available!
 http://doodle.com/umc27afh7akqczft

 Kathy




-- 
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[Jennifer Pringle (Project Sitka)]

Still works for me.

Jennifer

Quoting Kathy Lussier kluss...@masslnc.org:


Hi all,

Ack!

I closed the Doodle poll last month and set this Monday, March 2 as  
the date for our next Bug Squashing Day.  However, it looks like I  
failed to communicate the date with the rest of the community beyond  
adding it to the community calendar.


I would still like to see if we can get a group together to work on  
bugs on March 2. Does that day still work for everyone who responded  
to the poll?


Thanks and apologies for the oversight! I'm blaming it on the snow.

Kathy



On 01/21/2015 02:44 PM, Kathy Lussier wrote:
My apologies. The link for the Bug Squashing scheduling poll should  
be http://doodle.com/umc27afh7akqczft.


That's what I get for working on two Doodle polls at the same time.

Kathy

On 01/21/2015 02:35 PM, Kathy Lussier wrote:

Hi all,

I'm sending out a reminder to let us know what your availability  
is to participate in our next community Bug Squashing Day.  
http://doodle.com/xwu55tseci3mf34e


I'll be closing the Doodle poll at the end of the day tomorrow.

Kathy
On 01/16/2015 11:56 AM, Kathy Lussier wrote:

Hi all,

It's hard to believe, but it's already time to schedule another  
Bug Squashing Day. We're scheduling the next Bug Squashing Day to  
fall after the 2.8 beta release, but before the RC1 release. The  
closer we can schedule it to the beta release, the better.


Please let us know when you're available!
http://doodle.com/umc27afh7akqczft

Kathy







--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier



--
Jennifer Pringle
Co-op Support
BC Libraries Cooperative
Tel: 1-888-848-9250
Email:jprin...@sitka.bclibraries.ca
Website: http://bc.libraries.coop

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[liam . whalen]

I am going to participate.

Liam

Quoting Kathy Lussier kluss...@masslnc.org:


Hi all,

Ack!

I closed the Doodle poll last month and set this Monday, March 2 as  
the date for our next Bug Squashing Day.  However, it looks like I  
failed to communicate the date with the rest of the community beyond  
adding it to the community calendar.


I would still like to see if we can get a group together to work on  
bugs on March 2. Does that day still work for everyone who responded  
to the poll?


Thanks and apologies for the oversight! I'm blaming it on the snow.

Kathy



On 01/21/2015 02:44 PM, Kathy Lussier wrote:
My apologies. The link for the Bug Squashing scheduling poll should  
be http://doodle.com/umc27afh7akqczft.


That's what I get for working on two Doodle polls at the same time.

Kathy

On 01/21/2015 02:35 PM, Kathy Lussier wrote:

Hi all,

I'm sending out a reminder to let us know what your availability  
is to participate in our next community Bug Squashing Day.  
http://doodle.com/xwu55tseci3mf34e


I'll be closing the Doodle poll at the end of the day tomorrow.

Kathy
On 01/16/2015 11:56 AM, Kathy Lussier wrote:

Hi all,

It's hard to believe, but it's already time to schedule another  
Bug Squashing Day. We're scheduling the next Bug Squashing Day to  
fall after the 2.8 beta release, but before the RC1 release. The  
closer we can schedule it to the beta release, the better.


Please let us know when you're available!
http://doodle.com/umc27afh7akqczft

Kathy







--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[Kathy Lussier]

My apologies. The link for the Bug Squashing scheduling poll should be 
http://doodle.com/umc27afh7akqczft.


That's what I get for working on two Doodle polls at the same time.

Kathy

On 01/21/2015 02:35 PM, Kathy Lussier wrote:

Hi all,

I'm sending out a reminder to let us know what your availability is to 
participate in our next community Bug Squashing Day. 
http://doodle.com/xwu55tseci3mf34e


I'll be closing the Doodle poll at the end of the day tomorrow.

Kathy
On 01/16/2015 11:56 AM, Kathy Lussier wrote:

Hi all,

It's hard to believe, but it's already time to schedule another Bug 
Squashing Day. We're scheduling the next Bug Squashing Day to fall 
after the 2.8 beta release, but before the RC1 release. The closer we 
can schedule it to the beta release, the better.


Please let us know when you're available!
http://doodle.com/umc27afh7akqczft

Kathy





--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[Kathy Lussier]

Hi all,

I'm sending out a reminder to let us know what your availability is to 
participate in our next community Bug Squashing Day. 
http://doodle.com/xwu55tseci3mf34e


I'll be closing the Doodle poll at the end of the day tomorrow.

Kathy
On 01/16/2015 11:56 AM, Kathy Lussier wrote:

Hi all,

It's hard to believe, but it's already time to schedule another Bug 
Squashing Day. We're scheduling the next Bug Squashing Day to fall 
after the 2.8 beta release, but before the RC1 release. The closer we 
can schedule it to the beta release, the better.


Please let us know when you're available!
http://doodle.com/umc27afh7akqczft

Kathy



--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Bug Squashing Day is almost here

[Kathy Lussier]

Hi all,

I'm sending along a reminder that if you would like us to set up a 
Sandbox for you on Bug Squashing Day, please submit your requests by the 
end of the day tomorrow. The request form is available at 
http://goo.gl/forms/boKucpwnpz.


Thanks!
Kathy

Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier
#evergreen IRC: kmlussier

On 11/3/2014 11:14 AM, Kathy Lussier wrote:

Hi all,

Our next community Bug Squashing day is November 10, just a week away 
from today. I have posted details about the day at 
http://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing:2014-11-10.


The goal of the day is for all members of the Evergreen community 
(developers, support staff, users, fans) to work together to reduce 
bugs in Evergreen. The recap from our last bug squashing day at 
http://evergreen-ils.org/bug-squashing-day-wrap-up/ can give you a 
sense of the type of activity that occurs during the day.


Anyone interested in improving Evergreen is invited to help out during 
the day by confirming (or, in some cases, unconfirming) bugs, testing 
bug fixes, fixing bugs, and/or merging bug fixes into Evergreen.


To make it as easy as possible for all members of the community to 
participate, MOBIUS and MassLNC will once again provide Sandboxes that 
can be used to test bug fixes. If you need to use a Sandbox, please 
fill out the request form at http://goo.gl/forms/boKucpwnpz by the end 
of the day Thursday, November 6, to give us sufficient time to load 
the code. We will have a limited number of Sandboxes available and may 
not be able to accommodate all requests, but we’ll do our best to see 
that everyone who wants to test a bug fix has the opportunity to do so.


If you have any questions or ideas to make Bug Squashing Day even 
better, feel free to let me know!


Kathy

Re: [OPEN-ILS-GENERAL] Bug squashing days

[Kathy Lussier]

Hi all,

I'm sending out a last call to fill out the Doodle poll for Bug 
Squashing Day at http://doodle.com/2dx9h3cccwbp84v4. I plan to close the 
poll at the end of the day tomorrow. As of now, it looks like Monday, 
August 25 to Wednesday, August 27 are the best dates.


Thanks!
Kathy

Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

On 8/1/2014 11:08 AM, Kathy Lussier wrote:

Hi all,

Unfortunately, it looks like I mistakenly added July dates to the poll 
instead of some of the August dates we were polling. I usually can 
edit a Doodle poll to fix these mistakes, but Doodle just isn't 
cooperating with me on this poll.


Therefore, I had to create a new poll for bug squashing day. The poll 
is available at http://doodle.com/2dx9h3cccwbp84v4. Anyone who filled 
out the first poll will need to enter their dates again on the new poll.


Sorry!

Kathy

Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

On 7/29/2014 1:45 PM, Kathy Lussier wrote:

Hi all,

Based on the discussion at yesterday's developers meeting, I'm 
putting out a poll to find out when people would be available for the 
Bug Squashing Day. To give us plenty of time to get ready, I'm 
targeting the final two weeks of August, but I have excluded days 
when we have previously-scheduled Evergreen meetings (EOB and web 
team.) The poll is available at http://doodle.com/6ush6hyx9pa39pv3.


Once again, this day is not just for developers. We're looking at 
setting up sandboxes to make it easier for people to make it easier 
to test bug fixes. If you think you might be interested in testing 
patches or in helping to confirm bugs, please take time to fill out 
the Doodle poll.


Thanks all! I think it will be a great day and, hopefully, a 
productive one as well!


Kathy

Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

On 7/25/2014 7:27 PM, Kathy Lussier wrote:

Hi all,

Last fall, I put out an e-mail message suggesting community bug 
squashing days- http://markmail.org/message/22six3nkgbhr3f3t. It 
received some support at the time, but I didn't do any 
follow-through to make it happen.


Last week, I took some time to update a local spreadsheet I'm 
maintaining on Launchpad bugs that are important to libraries in the 
three MassLNC networks. I was pleased to remove some bugs that have 
since been fixed, but then I added a whole lot more. We started with 
about 50 bugs on the list, and the number is now at 83. These 
numbers reminded me of how it important it is that we try to 
allocate some time on a community level to fix bugs.


I have a more formal proposal I would like to put forward and, if 
it's agreeable to others, I commit to doing my part to try to make 
these days happen.


Proposal: Evergreen Bug Squashing Days

Goal: The goal of bug squashing days is for contributors and 
volunteers to commit the entire day to the following activities:


* Fixing bugs
* Testing bugs that have pullrequests
* General bug wrangling activities (confirming bugs, marking 
duplicates, etc.)

* Pushing bug fixes into Evergreen (for core committers)

When:
I'm proposing that we try to schedule bug squashing days on a 
quarterly basis. I was thinking August/November/February/May would 
be a good schedule where the bug squashing days aren't running up 
against an Evergreen release.


What is Needed:
* Somebody to work on scheduling the day and set up a wiki page (I 
volunteer, but am happy to hand off the task or work with somebody 
else if needed.)
* Volunteers willing to devote a day of their time to the above 
activities. These volunteers do not need to just be developers or 
sys admins. Anyone can confirm bugs, look for duplicates, or perhaps 
team up with a sys admin to test patches.


Extras:
The idea for these bug squashing days came from similar days 
organized by the Koha community. 
http://wiki.koha-community.org/wiki/Category:Global_bug_squashing_days. 
They do a couple of things that I would love to see for Evergreen 
bug squashing days.


* The Koha community uses this great scoreboard on bug squashing 
days - http://scoreboard.koha-community.org/.  The code for the 
scoreboard is available at 
https://gitorious.org/scoreboard/scoreboard. It would be great if we 
had a volunteer who was willing to create a similar scoreboard for 
Evergreen bug squashing days.
* The Koha community also has Sandboxes available that makes it 
easier for librarians to test patches. It may be a little difficult 
to pull together something  for Evergreen that's as automated as 
these Sandboxes, but I think it's worthwhile to set a goal to 
eventually have some Sandbox servers available to the Evergreen 
community where patches can be tested (not just on Bug 

Re: [OPEN-ILS-GENERAL] Bug squashing days

[Kathy Lussier]

Hi all,

Unfortunately, it looks like I mistakenly added July dates to the poll 
instead of some of the August dates we were polling. I usually can edit 
a Doodle poll to fix these mistakes, but Doodle just isn't cooperating 
with me on this poll.


Therefore, I had to create a new poll for bug squashing day. The poll is 
available at http://doodle.com/2dx9h3cccwbp84v4. Anyone who filled out 
the first poll will need to enter their dates again on the new poll.


Sorry!

Kathy

Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

On 7/29/2014 1:45 PM, Kathy Lussier wrote:

Hi all,

Based on the discussion at yesterday's developers meeting, I'm putting 
out a poll to find out when people would be available for the Bug 
Squashing Day. To give us plenty of time to get ready, I'm targeting 
the final two weeks of August, but I have excluded days when we have 
previously-scheduled Evergreen meetings (EOB and web team.) The poll 
is available at http://doodle.com/6ush6hyx9pa39pv3.


Once again, this day is not just for developers. We're looking at 
setting up sandboxes to make it easier for people to make it easier to 
test bug fixes. If you think you might be interested in testing 
patches or in helping to confirm bugs, please take time to fill out 
the Doodle poll.


Thanks all! I think it will be a great day and, hopefully, a 
productive one as well!


Kathy

Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

On 7/25/2014 7:27 PM, Kathy Lussier wrote:

Hi all,

Last fall, I put out an e-mail message suggesting community bug 
squashing days- http://markmail.org/message/22six3nkgbhr3f3t. It 
received some support at the time, but I didn't do any follow-through 
to make it happen.


Last week, I took some time to update a local spreadsheet I'm 
maintaining on Launchpad bugs that are important to libraries in the 
three MassLNC networks. I was pleased to remove some bugs that have 
since been fixed, but then I added a whole lot more. We started with 
about 50 bugs on the list, and the number is now at 83. These numbers 
reminded me of how it important it is that we try to allocate some 
time on a community level to fix bugs.


I have a more formal proposal I would like to put forward and, if 
it's agreeable to others, I commit to doing my part to try to make 
these days happen.


Proposal: Evergreen Bug Squashing Days

Goal: The goal of bug squashing days is for contributors and 
volunteers to commit the entire day to the following activities:


* Fixing bugs
* Testing bugs that have pullrequests
* General bug wrangling activities (confirming bugs, marking 
duplicates, etc.)

* Pushing bug fixes into Evergreen (for core committers)

When:
I'm proposing that we try to schedule bug squashing days on a 
quarterly basis. I was thinking August/November/February/May would be 
a good schedule where the bug squashing days aren't running up 
against an Evergreen release.


What is Needed:
* Somebody to work on scheduling the day and set up a wiki page (I 
volunteer, but am happy to hand off the task or work with somebody 
else if needed.)
* Volunteers willing to devote a day of their time to the above 
activities. These volunteers do not need to just be developers or sys 
admins. Anyone can confirm bugs, look for duplicates, or perhaps team 
up with a sys admin to test patches.


Extras:
The idea for these bug squashing days came from similar days 
organized by the Koha community. 
http://wiki.koha-community.org/wiki/Category:Global_bug_squashing_days. 
They do a couple of things that I would love to see for Evergreen bug 
squashing days.


* The Koha community uses this great scoreboard on bug squashing days 
- http://scoreboard.koha-community.org/.  The code for the scoreboard 
is available at https://gitorious.org/scoreboard/scoreboard. It would 
be great if we had a volunteer who was willing to create a similar 
scoreboard for Evergreen bug squashing days.
* The Koha community also has Sandboxes available that makes it 
easier for librarians to test patches. It may be a little difficult 
to pull together something  for Evergreen that's as automated as 
these Sandboxes, but I think it's worthwhile to set a goal to 
eventually have some Sandbox servers available to the Evergreen 
community where patches can be tested (not just on Bug Squashing days).


I've also added this proposal to the agenda for Monday's developers 
meeting. If there is general support for this idea, then I'll put out 
a Doodle poll next week to see if we can schedule a day.


Thanks all!
Kathy

Re: [OPEN-ILS-GENERAL] Bug bounties

[Andrea Buntz Neiman]

I've been following this entire bug bounty conversation with interest, 
but this:



We also have our dashboard,http://dashboard.koha-community.org/  which
is designed to highlight where work is needed.
(Cloneable as well of course)


... is awesome.  I like the clarity, I like the details, I like the 
chart, I like the random bug, and I especially like that QA is tied 
into it.


How difficult would it be to also tie in things like documentation  
testing to this kind of one-stop dashboard?  I know there is also a 
conversation currently about using Launchpad for documentation 
requests/tracking.


I envision a place where coders, testers,  documenters can see what 
needs to be done all in one location, pick what they work on, and get it 
done -- even if it is just a front/landing page for something like 
Launchpad.


A.




Andrea Buntz Neiman, MLS
Librarian II, Public Services
Kent County Public Library
408 High Street
Chestertown, MD 21620
410-778-3636 x2115
www.kentcountylibrary.org

On 8/1/2013 5:08 AM, Chris Cormack wrote:

We also have our dashboard,http://dashboard.koha-community.org/  which
is designed to highlight where work is needed.
(Cloneable as well of course)

Re: [OPEN-ILS-GENERAL] Bug bounties

[Yamil Suarez]

Thinking out of the box for a moment. What about having documentation
bounties? I am sure there are can be Dilbertesque issues to those
too, but I had floated around the idea of group sponsoring a retired
librarian, consultant, or part time librarian to devote serious
amounts of hours to work on documentation projects. I have had success
with using an intern, but they still needed me to proofread everything
and be trained and supervised.

Just a thought.

Thanks,
Yamil

On Thu, Jul 18, 2013 at 6:58 PM, Rogan Hamby rogan.ha...@yclibrary.net wrote:
 I'll be honest it's partially unclear because this is bouncing it off people
 thing at this point in time.  This probably frustrates some people but I
 think these are things that as a community we should have dialogues about.

 If I were asked to put forth my personal vision it would be something like
 this:

 The community votes on bugs over X age (a year old?) using some kind of
 mechanism and presumably ranks based on priority.  We then offer bug
 bounties on a set rate to Y number of bugs based on how much we have in that
 fund.  Let's say we have $1,000 and pay $100 per bug, then we can offer it
 to the top ten bugs ranked by people's votes.

 There are flaws with that approach.  Some may say it does't give weight to
 payments based on complexity of bug (and that's true) and some would say it
 doesn't weigh importance of more recent bugs (and that's true).  Fixing
 those things add issues of their own and  maybe we want to take those issues
 on.  That's part of why I'm throwing it out.

Re: [OPEN-ILS-GENERAL] Bug bounties

[Rogan Hamby]

Doing some basic Googling for bug bounties I found mention of Koha
discussing it at KohaCon 12.  I didn't find mention past that but wether
they did or didn't implement one their experience may be educational to us.




On Tue, Jul 30, 2013 at 5:48 PM, Dan Scott d...@coffeecode.net wrote:

 On Tue, Jul 30, 2013 at 05:35:04PM -0400, Rogan Hamby wrote:
  I haven't heard any dissents and at least two in favors of (you and I) so
  in the spirit of a meritocracy I would say Kathy that at the least if you
  want to come up with a model of how to handle it, go ahead and let's
 start
  poking at the details.
 
  I won't derail things with my wishlist for accessibility.  :)
 
  I agree that wishlist bugs shouldn't be on the list.

 Okay, I'll offer a conditional dissent then. I worry that the
 introduction of financial incentives will disrupt the contributor
 ecology. As soon as money is in the picture, all sorts of interesting
 side effects can occur.

 For example, will this act as a disincentive for open communication
 and collaboration about potential alternatives for fixing a bug (because
 potential fixers jealously guard their approaches from one another)?
 Will it reduce the interest of current developers in providing
 assistance to new contributors? Will it introduce difficulties in trying
 to divvy up credit for bug fixes? Do reviewers of bug fixes get any
 share of the cash? Do reporters of bugs who provide reproducible test
 cases get any share of the cash? Is there any requirement to providing
 regression tests (to prevent the bug from ever rearing its head again)
 as part of the bug fix? Will contributors of new functionality bury bugs
 they know about in the interest of getting paid twice, once for the new
 functionality, and then later for the bug fixes?

 My conditional dissent would like some examples of projects where bug
 bounties have actually worked. The examples that I've seen have focused
 on reporting security vulnerabilities. If there are a few solid cases
 out there that can serve as a model for us, then I would turn my dissent
 into cautious assent.

 It could be that I've just read one too many Dilbert cartoons...




-- 

Rogan Hamby, MLS, CCNP, MIA
Managers Headquarters Library and Reference Services,
York County Library System

You can never get a cup of tea large enough or a book long enough to suit
me.
-- C.S. Lewis http://www.goodreads.com/author/show/1069006.C_S_Lewis

Re: [OPEN-ILS-GENERAL] Bug bounties

[Rogan Hamby]

I think we should high light that Dan Wells has helped push cleaning up a
lot of bugs with 2.5 including wishlist ones which as he pointed out is
characteristic of a maturing software project.

I like the idea of the bug squashing being something symbolic but
meaningful.  I don't mind giving out money but nor do I want it to be about
money.

I like the bug squashing idea too.

A big part of all this though is what do the developers think would be a
fun thing that they would rally behind.  A bug squashing day?  Should we
devote some time at the hack-a-way to reviewing long standing bugs and
seeing what can be done about them?  What do you think?


On Wed, Jul 31, 2013 at 3:46 PM, Kathy Lussier kluss...@masslnc.org wrote:

  Hi Rogan, Dan, et al.,


 Anyway, I think those are valid concerns and concerns I have as well but
 I'd like to see what Kathy comes up with for a proposal.


 Hmmm...I think what I said was I would be willing to *help* work out the
 details, but I guess I could poke around to see what other projects do and
 start with something bare bones for the community to react to.

 One of the reasons I was so quick to volunteer to help on this is because
 I do submit a lot of bugs and don't really have the ability to fix them,
 with the exception of some really, easy tpac bugs. In some cases, the bugs
 are resolved fairly quickly; others are collecting dust, not because the
 community doesn't care about fixing them, but because everyone has limited
 time and usually must address the needs important to their own
 organizations before working on other bugs. I just did a search of
 Launchpad and saw that I have 48 outstanding bugs that have not been
 committed or released, though a few do have code that needs to be tested.
 Since I'm limited in the amount of fixing I can do, I see this as another
 way I can contribute to help get Evergreen bugs resolved.

 I also understand some of Dan's concerns and was thinking it might be good
 to reframe this discussion. Maybe we should look at the underlying problem,
 which is the issue of valid bugs that languish in Launchpad, and then
 consider ways that the community can support getting those bugs fixed.

 One idea is to go with the bug bounty system, providing some type of
 incentive (monetary or otherwise) to developers who fix bugs of a certain
 age. In thinking about the monetary incentive, I couldn't help but think
 about all the money and staff time that many Evergreen sites (including
 MassLNC) put into new enhancements without giving the same attention to
 long-standing bugs that need to be fixed. Even when the new enhancement has
 gone through thorough testing, it isn't unusual for it to introduce even
 more bugs that then get added to the list of bugs that need to be fixed.
 When Rogan first raised the ideas of bug bounties, I was seeing it as a way
 to provide a little more balance between all of the funding that supports
 new enhancements and funding that supports fixing bugs.

 Swag could be another incentive, but, since I anticipate one developer may
 be submitting fixes for several bugs, we might need to do a scale where
 fixing 1-5 bugs gets you a sticker, 10 gets you a t-shirt, and 20 gets you
 a bike. Or maybe we could do something where the person who has submitted
 the most bug fixes during a certain month gets a spotlight on the community
 web site. Incentives can take many forms.

 Another idea is one I raised at the June developers meeting regarding an
 Evergreen bug squashing day. I was left with an action item to e-mail the
 list about this idea, but I never followed up on it, partially because of
 other time commitments, but also because Dan Wells has been so effective in
 encouraging developers to review active pullrequests that I wasn't sure it
 was still needed.

 However, it might be a good way to encourage contributors to spend one day
 where they can focus on fixing bugs. The idea came from a Koha global bug
 squashing day that was held last May -
 http://wiki.koha-community.org/wiki/2013-05-10_Global_bug_squashing_day.
 The Koha community even had a scorecard of number of kittens saved to
 highlight the contributors who had the most bug fixes, patches reviewed,
 etc. I can't remember all of the categories, and the scorecard doesn't
 appear to be available online anymore. We could designate one day where
 contributors are committed to submitting code to fix bugs, reviewing bugs,
 signing off on the fixes, etc. Koha even provided sandboxes for people who
 do not have access to a testing server, but are interested in testing
 fixes. I think this would be a great way to encourage more people to get
 involved in the process.

 I don't think these ideas need to be mutually exclusive of each other.
 Maybe we could organize a bug squashing day sometime after the 2.5 release
 to see how many old bugs can be knocked off before running a test of a bug
 bounty system. Maybe there are other ideas out there for addressing the
 issue of 

Re: [OPEN-ILS-GENERAL] Bug bounties

[Kathy Lussier]

Hi Rogan,

Sorry to be late in getting you feedback on this, but I just wanted to 
send along a vote of support for the idea of offering bug bounties. I 
think it's a great idea!


I think it should be limited to true bugs and not be used for wishlist 
bugs. I know there are plenty of bugs to tackle that are more than a 
year old, but, when working in two-releases per year cycle, I'm thinking 
bugs become old much sooner than that. Maybe six month or even less? I 
generally have found that if a bug doesn't receive some kind of 
attention in the first three months (attention being questions, 
confirmation, lots of me toos etc.), it is likely to be one of those 
bugs that ends up gathering dust. I think it's important that we give 
bugs a chance to get community attention before offering a bounty. Six 
months seems like it would be more than sufficient.


some would say it doesn't weigh importance of more recent bugs (and 
that's true). 


I think it was me who said that. :) Overall, I would say targeting the 
older bugs is important. However, as with anything, I think there are 
exceptions. The specific bug I had in mind was 
https://bugs.launchpad.net/evergreen/+bug/1187993 which is related to an 
accessibility issue in the catalog when autosuggest is enabled. I see 
this bug as an exception because I believe accessibility is something 
the community should be supporting/striving for in any way we can. 
Perhaps there are/will be other unique cases out there where priority 
will take precedence.


In any case, if the community decides to move forward with this, I would 
be willing to volunteer to help work out the details. We might not come 
up with the perfect system, but, whatever happens, it should lead to 
some fixes for issues that have been frustrating people.


Kathy

Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

On 7/18/2013 6:58 PM, Rogan Hamby wrote:
I'll be honest it's partially unclear because this is bouncing it off 
people thing at this point in time.  This probably frustrates some 
people but I think these are things that as a community we should have 
dialogues about.


If I were asked to put forth my personal vision it would be something 
like this:


The community votes on bugs over X age (a year old?) using some kind 
of mechanism and presumably ranks based on priority.  We then offer 
bug bounties on a set rate to Y number of bugs based on how much we 
have in that fund.  Let's say we have $1,000 and pay $100 per bug, 
then we can offer it to the top ten bugs ranked by people's votes.


There are flaws with that approach.  Some may say it does't give 
weight to payments based on complexity of bug (and that's true) and 
some would say it doesn't weigh importance of more recent bugs (and 
that's true).  Fixing those things add issues of their own and  maybe 
we want to take those issues on.  That's part of why I'm throwing it out.





On Thu, Jul 18, 2013 at 6:51 PM, Tim Spindler tjspind...@gmail.com 
mailto:tjspind...@gmail.com wrote:


Rogan,

It is a little unclear what you are proposing.  Are you proposing
that bounties are given for fixing bugs?  Finding bugs? or Both?

Don't get me wrong, I think it has some real potential.  If we are
to put resources to it, I would advocate for rewarding those who
fix bugs because I'm sure many are pressured to add features but
not rewarded to fix bugs.

Tim


On Thu, Jul 18, 2013 at 5:58 PM, Rogan Hamby
rogan.ha...@yclibrary.net mailto:rogan.ha...@yclibrary.net wrote:

I wanted to bring up an idea that has been kicked around by
several folks (including myself).  At this point I don't have
a fleshed out implementation proposal in mind but wanted to
throw it out for consideration.  The context of conversation
so far had been targeting older bugs though perhaps we should
weight them by priority as well.  What, how much and where are
big questions attached to funds.  But, I don't want to put the
cart before the horse.  This is a practice used successfully
by some other open source projects and I think there's merit
in considering it.

Excuse my brevity, sent from my iPhone

-- 


Rogan Hamby, MLS, CCNP, MIA
Managers Headquarters Library and Reference Services,
York County Library System

You can never get a cup of tea large enough or a book long
enough to suit me.
-- C.S. Lewis
http://www.goodreads.com/author/show/1069006.C_S_Lewis




-- 
Tim Spindler

tjspind...@gmail.com mailto:tjspind...@gmail.com

*P**   Go Green - **Save a tree! Please don't print this e-mail
unless it's really necessary.*




--

Rogan Hamby, MLS, CCNP, MIA
Managers Headquarters Library and Reference Services,
York County Library System

You can never get a cup 

Re: [OPEN-ILS-GENERAL] Bug bounties

[Dan Scott]

On Tue, Jul 30, 2013 at 05:35:04PM -0400, Rogan Hamby wrote:
 I haven't heard any dissents and at least two in favors of (you and I) so
 in the spirit of a meritocracy I would say Kathy that at the least if you
 want to come up with a model of how to handle it, go ahead and let's start
 poking at the details.
 
 I won't derail things with my wishlist for accessibility.  :)
 
 I agree that wishlist bugs shouldn't be on the list.

Okay, I'll offer a conditional dissent then. I worry that the
introduction of financial incentives will disrupt the contributor
ecology. As soon as money is in the picture, all sorts of interesting
side effects can occur.

For example, will this act as a disincentive for open communication
and collaboration about potential alternatives for fixing a bug (because
potential fixers jealously guard their approaches from one another)?
Will it reduce the interest of current developers in providing
assistance to new contributors? Will it introduce difficulties in trying
to divvy up credit for bug fixes? Do reviewers of bug fixes get any
share of the cash? Do reporters of bugs who provide reproducible test
cases get any share of the cash? Is there any requirement to providing
regression tests (to prevent the bug from ever rearing its head again)
as part of the bug fix? Will contributors of new functionality bury bugs
they know about in the interest of getting paid twice, once for the new
functionality, and then later for the bug fixes?

My conditional dissent would like some examples of projects where bug
bounties have actually worked. The examples that I've seen have focused
on reporting security vulnerabilities. If there are a few solid cases
out there that can serve as a model for us, then I would turn my dissent
into cautious assent.

It could be that I've just read one too many Dilbert cartoons...

Re: [OPEN-ILS-GENERAL] Bug bounties

[Ruth Frasur]

It's been mentioned elsewhere that maybe the bounties be something other
than money.  I think it was in the swag conversation.
On Jul 30, 2013 5:49 PM, Dan Scott d...@coffeecode.net wrote:

 On Tue, Jul 30, 2013 at 05:35:04PM -0400, Rogan Hamby wrote:
  I haven't heard any dissents and at least two in favors of (you and I) so
  in the spirit of a meritocracy I would say Kathy that at the least if you
  want to come up with a model of how to handle it, go ahead and let's
 start
  poking at the details.
 
  I won't derail things with my wishlist for accessibility.  :)
 
  I agree that wishlist bugs shouldn't be on the list.

 Okay, I'll offer a conditional dissent then. I worry that the
 introduction of financial incentives will disrupt the contributor
 ecology. As soon as money is in the picture, all sorts of interesting
 side effects can occur.

 For example, will this act as a disincentive for open communication
 and collaboration about potential alternatives for fixing a bug (because
 potential fixers jealously guard their approaches from one another)?
 Will it reduce the interest of current developers in providing
 assistance to new contributors? Will it introduce difficulties in trying
 to divvy up credit for bug fixes? Do reviewers of bug fixes get any
 share of the cash? Do reporters of bugs who provide reproducible test
 cases get any share of the cash? Is there any requirement to providing
 regression tests (to prevent the bug from ever rearing its head again)
 as part of the bug fix? Will contributors of new functionality bury bugs
 they know about in the interest of getting paid twice, once for the new
 functionality, and then later for the bug fixes?

 My conditional dissent would like some examples of projects where bug
 bounties have actually worked. The examples that I've seen have focused
 on reporting security vulnerabilities. If there are a few solid cases
 out there that can serve as a model for us, then I would turn my dissent
 into cautious assent.

 It could be that I've just read one too many Dilbert cartoons...

Re: [OPEN-ILS-GENERAL] Bug bounties

[Rogan Hamby]

I think I know the Dilbert cartoons you speak of and none of us want those
scenarios!  Wally made a fortune

Anyway, I think those are valid concerns and concerns I have as well but
I'd like to see what Kathy comes up with for a proposal.  I don't think we
have the resources to offer more than a minimal award so I would hope that
potential financial gain would be a big factor.  And unlike Wally hopefully
no one would create bugs just to fix them later.  :)

Also, in the spirit of it being largely symbolic, as Ruth points out, in a
discussion off list about swag the idea has been thrown out to use some
kind of swag.  I'm personally amused at the idea of a t-shirt that says
Bug Killer



On Tue, Jul 30, 2013 at 5:48 PM, Dan Scott d...@coffeecode.net wrote:

 On Tue, Jul 30, 2013 at 05:35:04PM -0400, Rogan Hamby wrote:
  I haven't heard any dissents and at least two in favors of (you and I) so
  in the spirit of a meritocracy I would say Kathy that at the least if you
  want to come up with a model of how to handle it, go ahead and let's
 start
  poking at the details.
 
  I won't derail things with my wishlist for accessibility.  :)
 
  I agree that wishlist bugs shouldn't be on the list.

 Okay, I'll offer a conditional dissent then. I worry that the
 introduction of financial incentives will disrupt the contributor
 ecology. As soon as money is in the picture, all sorts of interesting
 side effects can occur.

 For example, will this act as a disincentive for open communication
 and collaboration about potential alternatives for fixing a bug (because
 potential fixers jealously guard their approaches from one another)?
 Will it reduce the interest of current developers in providing
 assistance to new contributors? Will it introduce difficulties in trying
 to divvy up credit for bug fixes? Do reviewers of bug fixes get any
 share of the cash? Do reporters of bugs who provide reproducible test
 cases get any share of the cash? Is there any requirement to providing
 regression tests (to prevent the bug from ever rearing its head again)
 as part of the bug fix? Will contributors of new functionality bury bugs
 they know about in the interest of getting paid twice, once for the new
 functionality, and then later for the bug fixes?

 My conditional dissent would like some examples of projects where bug
 bounties have actually worked. The examples that I've seen have focused
 on reporting security vulnerabilities. If there are a few solid cases
 out there that can serve as a model for us, then I would turn my dissent
 into cautious assent.

 It could be that I've just read one too many Dilbert cartoons...




-- 

Rogan Hamby, MLS, CCNP, MIA
Managers Headquarters Library and Reference Services,
York County Library System

You can never get a cup of tea large enough or a book long enough to suit
me.
-- C.S. Lewis http://www.goodreads.com/author/show/1069006.C_S_Lewis

Re: [OPEN-ILS-GENERAL] Bug bounties

[Tim Spindler]

I generally like the idea and support but would have the same concerns as
Dan Scott.  I don't have a solution either.

Tim Spindler
C/W MARS

On Tuesday, July 30, 2013, Rogan Hamby wrote:

 I think I know the Dilbert cartoons you speak of and none of us want those
 scenarios!  Wally made a fortune

 Anyway, I think those are valid concerns and concerns I have as well but
 I'd like to see what Kathy comes up with for a proposal.  I don't think we
 have the resources to offer more than a minimal award so I would hope that
 potential financial gain would be a big factor.  And unlike Wally hopefully
 no one would create bugs just to fix them later.  :)

 Also, in the spirit of it being largely symbolic, as Ruth points out, in a
 discussion off list about swag the idea has been thrown out to use some
 kind of swag.  I'm personally amused at the idea of a t-shirt that says
 Bug Killer



 On Tue, Jul 30, 2013 at 5:48 PM, Dan Scott 
 d...@coffeecode.netjavascript:_e({}, 'cvml', 'd...@coffeecode.net');
  wrote:

 On Tue, Jul 30, 2013 at 05:35:04PM -0400, Rogan Hamby wrote:
  I haven't heard any dissents and at least two in favors of (you and I)
 so
  in the spirit of a meritocracy I would say Kathy that at the least if
 you
  want to come up with a model of how to handle it, go ahead and let's
 start
  poking at the details.
 
  I won't derail things with my wishlist for accessibility.  :)
 
  I agree that wishlist bugs shouldn't be on the list.

 Okay, I'll offer a conditional dissent then. I worry that the
 introduction of financial incentives will disrupt the contributor
 ecology. As soon as money is in the picture, all sorts of interesting
 side effects can occur.

 For example, will this act as a disincentive for open communication
 and collaboration about potential alternatives for fixing a bug (because
 potential fixers jealously guard their approaches from one another)?
 Will it reduce the interest of current developers in providing
 assistance to new contributors? Will it introduce difficulties in trying
 to divvy up credit for bug fixes? Do reviewers of bug fixes get any
 share of the cash? Do reporters of bugs who provide reproducible test
 cases get any share of the cash? Is there any requirement to providing
 regression tests (to prevent the bug from ever rearing its head again)
 as part of the bug fix? Will contributors of new functionality bury bugs
 they know about in the interest of getting paid twice, once for the new
 functionality, and then later for the bug fixes?

 My conditional dissent would like some examples of projects where bug
 bounties have actually worked. The examples that I've seen have focused
 on reporting security vulnerabilities. If there are a few solid cases
 out there that can serve as a model for us, then I would turn my dissent
 into cautious assent.

 It could be that I've just read one too many Dilbert cartoons...




 --

 Rogan Hamby, MLS, CCNP, MIA
 Managers Headquarters Library and Reference Services,
 York County Library System

 You can never get a cup of tea large enough or a book long enough to suit
 me.
 -- C.S. Lewis http://www.goodreads.com/author/show/1069006.C_S_Lewis



-- 
Tim Spindler
tjspind...@gmail.com

*P**   Go Green - **Save a tree! Please don't print this e-mail unless it's
really necessary.*

Re: [OPEN-ILS-GENERAL] Bug bounties

[Rogan Hamby]

I'll be honest it's partially unclear because this is bouncing it off
people thing at this point in time.  This probably frustrates some people
but I think these are things that as a community we should have dialogues
about.

If I were asked to put forth my personal vision it would be something like
this:

The community votes on bugs over X age (a year old?) using some kind of
mechanism and presumably ranks based on priority.  We then offer bug
bounties on a set rate to Y number of bugs based on how much we have in
that fund.  Let's say we have $1,000 and pay $100 per bug, then we can
offer it to the top ten bugs ranked by people's votes.

There are flaws with that approach.  Some may say it does't give weight to
payments based on complexity of bug (and that's true) and some would say it
doesn't weigh importance of more recent bugs (and that's true).  Fixing
those things add issues of their own and  maybe we want to take those
issues on.  That's part of why I'm throwing it out.




On Thu, Jul 18, 2013 at 6:51 PM, Tim Spindler tjspind...@gmail.com wrote:

 Rogan,

 It is a little unclear what you are proposing.  Are you proposing that
 bounties are given for fixing bugs?  Finding bugs? or Both?

 Don't get me wrong, I think it has some real potential.  If we are to put
 resources to it, I would advocate for rewarding those who fix bugs because
 I'm sure many are pressured to add features but not rewarded to fix bugs.

 Tim


 On Thu, Jul 18, 2013 at 5:58 PM, Rogan Hamby rogan.ha...@yclibrary.netwrote:

 I wanted to bring up an idea that has been kicked around by several folks
 (including myself).  At this point I don't have a fleshed out
 implementation proposal in mind but wanted to throw it out for
 consideration.  The context of conversation so far had been targeting older
 bugs though perhaps we should weight them by priority as well.  What, how
 much and where are big questions attached to funds.  But, I don't want to
 put the cart before the horse.  This is a practice used successfully by
 some other open source projects and I think there's merit in considering it.

 Excuse my brevity, sent from my iPhone

 --

 Rogan Hamby, MLS, CCNP, MIA
 Managers Headquarters Library and Reference Services,
 York County Library System

 You can never get a cup of tea large enough or a book long enough to
 suit me.
 -- C.S. Lewis http://www.goodreads.com/author/show/1069006.C_S_Lewis




 --
 Tim Spindler
 tjspind...@gmail.com

 *P**   Go Green - **Save a tree! Please don't print this e-mail unless
 it's really necessary.*






-- 

Rogan Hamby, MLS, CCNP, MIA
Managers Headquarters Library and Reference Services,
York County Library System

You can never get a cup of tea large enough or a book long enough to suit
me.
-- C.S. Lewis http://www.goodreads.com/author/show/1069006.C_S_Lewis

Re: [OPEN-ILS-GENERAL] Bug Tracking and Enhancment Requests

[Galen Charlton]

Hi,

On 09/16/2011 10:50 AM, Tim Spindler wrote:

We are beginning to look at software to track bug reports within our
consortium and enhancement requests for potential future development by
our member libraries.  We are looking for something that would be fairly
user friendly for our member libraries and allow us to easily group
requests and report back to member libraries what actions might have
been taken on the requests.

I appreciate whatever suggestions you might have.  We do run a Drupal
site on wamp so if it can integrate with Drupal (with an eye for the
ability to run on future versions of Drupal would be helpful.)


I've never seen a perfect bug tracker, but several ones that I know have 
been used with various degrees of success include:


[1] Bugzilla.

This might score a little low on the user friendly scale, although 
recent versions have had the benefit of some formal usability testing. 
Of particular note is the existence of the Launchpad-Bugzilla plugin.  I 
haven't used it myself, but being able to connect bug reports in your 
tracker to LP bugs seems like it would be useful and would help avoid 
atomizing enhancement requests.  Other F/OSS trackers that can integrate 
with LP are Trac and Mantis.


[2] RT (http://bestpractical.com/rt/)

I believe this is being used successfully by at least one other 
Evergreen consortium.


[2] HelpSpot

This is proprietary, unfortunately, but it's what Equinox and at least 
one other Evergreen consortium uses for support incident tracking.


Regards,

Galen
--
Galen Charlton
Director of Support and Implementation
Equinox Software, Inc. / Your Library's Guide to Open Source
email:  g...@esilibrary.com
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org  
http://evergreen-ils.org

Re: [OPEN-ILS-GENERAL] Bug Tracking and Enhancment Requests

[Aaron Zsembery]

On Friday, September 16, 2011 12:28:21 PM Galen Charlton wrote:
 [2] RT (http://bestpractical.com/rt/)
 I believe this is being used successfully by at least one other
 Evergreen consortium.
We use RT here at PLS.
I like it, it lets us setup permissions, add requestors to tickets, merge 
tickets, have automatic responses when something happens to a ticket, 
automatically BCC people when something happens to a ticket (ie: there are 4-5 
people who get BCCed with any updates are made to a ticket in the Evergreen 
queue), mark tickets as dependent on other tickets, depended on by other 
tickets, mark tickets as parents or children of other tickets, etc.
We have it setup with our mail system, so when you send an email, it will 
automatically open a ticket for the sender in the correct queue.
Also (unlike some ticketing systems) when you reply via email from the ticket, 
the reply goes into the ticket. You can either reply to the requestor or you 
can add a comment (added to the ticket, but not sent to the requestor) via 
email.

Downsides: The web UI on our version is clunky (but the libraries never use it, 
they just use email to interact with RT), and our antiquated version needs some 
tweaks to the config files from time to time.
See: http://issues.bestpractical.com/Dashboards/1408/RT?user=guest;pass=guest 
for the interface of a current version.

Aaron Z
Jr. Systems Administrator

Pioneer Library System
2557 State Rt. 21
Canandaigua, New York  14424
Phone: (585) 394-8260

Re: [OPEN-ILS-GENERAL] Bug Tracking and Enhancment Requests

[Justin Hopkins]

We use Request Tracker along with the ExternalAuth plugin to
authenticate against our Drupal site. We are happy with it, but it
isn't perfect. Contact me off list if you'd like to discuss.

Regards,
Justin Hopkins
Coordinator, IT  Web Services
MOBIUS Consortium Office
c: 573-808-2309

--sent from a mobile device--

On Sep 16, 2011, at 11:29 AM, Galen Charlton g...@esilibrary.com wrote:

 Hi,

 On 09/16/2011 10:50 AM, Tim Spindler wrote:
 We are beginning to look at software to track bug reports within our
 consortium and enhancement requests for potential future development by
 our member libraries.  We are looking for something that would be fairly
 user friendly for our member libraries and allow us to easily group
 requests and report back to member libraries what actions might have
 been taken on the requests.

 I appreciate whatever suggestions you might have.  We do run a Drupal
 site on wamp so if it can integrate with Drupal (with an eye for the
 ability to run on future versions of Drupal would be helpful.)

 I've never seen a perfect bug tracker, but several ones that I know have been 
 used with various degrees of success include:

 [1] Bugzilla.

 This might score a little low on the user friendly scale, although recent 
 versions have had the benefit of some formal usability testing. Of particular 
 note is the existence of the Launchpad-Bugzilla plugin.  I haven't used it 
 myself, but being able to connect bug reports in your tracker to LP bugs 
 seems like it would be useful and would help avoid atomizing enhancement 
 requests.  Other F/OSS trackers that can integrate with LP are Trac and 
 Mantis.

 [2] RT (http://bestpractical.com/rt/)

 I believe this is being used successfully by at least one other Evergreen 
 consortium.

 [2] HelpSpot

 This is proprietary, unfortunately, but it's what Equinox and at least one 
 other Evergreen consortium uses for support incident tracking.

 Regards,

 Galen
 --
 Galen Charlton
 Director of Support and Implementation
 Equinox Software, Inc. / Your Library's Guide to Open Source
 email:  g...@esilibrary.com
 direct: +1 770-709-5581
 cell:   +1 404-984-4366
 skype:  gmcharlt
 web:http://www.esilibrary.com/
 Supporting Koha and Evergreen: http://koha-community.org  
 http://evergreen-ils.org